Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 171870
| Summary: | kdelibs and kde-i18n-Polish conflict during "yum update" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert P. J. Day <rpjday> |
| Component: | yum | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | dimitri.papadopoulos |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-04-19 20:20:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Robert P. J. Day
2005-10-27 10:14:46 UTC
i have taken a look in the specfile and did not find something which could cause this problem. Could you please try to update the kde packages with rpm (rpm -Fvh kde*) instead yum. Does this problem still appear? Many Thanks for your report. *** Bug 171958 has been marked as a duplicate of this bug. *** i have done a fresh fc4 installation on my test machine. First, i have tried to update KDE packages which rpm command and it works without any problem. With yum it breaks with above errors. It seems a bug in yum. can you please send the out put of this command: yum list installed thanks I've only ever seen this error immediately after a fresh install of FC4, followed by a "yum update". (Actually, you have to first delete a few kernel-related packages to get past a transaction error, but this error has happened *every* time for me in those circumstances.) I guess you need the output of 'yum list installed' before 'yum update'? I worked around the problem by removing package kde-i18n-Polish before running 'yum update'. I can't reinstall the workstation anymore (it's being tested) so I can't provide this output now. But really, to reproduce the bug you just need a complete FC4 installation. By the way, I also had to remove packages cman-kernel, dlm-kernel, GFS-kernel, and gnbd-kernel to be able to upgrade. They seem to be tied to a specific version of the kernel, but updates are not provided alongside kernel packages. For example, current updates are: kernel-2.6.13-1.1532_FC4 cman-kernel-2.6.11.5-20050601.152643.FC4.15 dlm-kernel-2.6.11.5-20050601.152643.FC4.15 GFS-kernel-2.6.11.8-20050601.152643.FC4.18 gnbd-kernel-2.6.11.2-20050420.133124.FC4.51 Here's the entire sequence of what happens when you do an "Everything" FC4 install and try to "yum update" in one operation these days -- this is from just a few days ago. The install works fine, but the first attempt at "yum update" complains about a conflict based on the four *-kernel packages listed above because they aren't compatible with the current kernel. You can either just remove those packages (most people don't need them anyway), or try again with: # yum --exclude="*-kernel" update That command is the one that complains about the clash between kdelibs and kde-i18n-Polish. To get around that, I just removed the "kde-i18n-Polish" package and then the above yum update command started to work. Finally, if you don't have enough free space in /usr, the yum command will eventually fail given that, these days, doing a yum update on a *fresh* install involves updating over 550 packages. To get around that last issue (obviously not really an error, just an annoyance), I did the update in two steps: # yum --exclude "*-kernel" update "kde*" # yum --exclude "*-kernel" update and everything was happy. comment #6: Yes - I need to see what was going on beforehand. Closing due to inactivity. Please reopen if you can add further information to the report. |