| Summary: | yum installs package obsoleted/provided by other package | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | nucleo <alekcejk> |
| Component: | yum | Assignee: | Seth Vidal <skvidal> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | ffesti, james.antill, john, kevin, maxamillion, pmatilai, rdieter, Schmed, tla, zpavlas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | yum-3.4.3-23.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-02 23:27:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
nucleo
2012-03-05 15:53:33 UTC
Yeah, further data point, both kdebase-4.7.2 and the newer newer kde-baseapps contain in their .spec the snippet:
Obsoletes: konq-plugins < 4.6.80-1
Provides: konq-plugins = %{version}-%{release}
and "fine on x86_64", the behavior of
yum install konq-plugins
is
Package konq-plugins is obsoleted by kde-baseapps, trying to install kde-baseapps-4.8.0-2.x86_64 instead
or
Package konq-plugins-4.6.1-1.fc15.x86_64 is obsoleted by kde-baseapps-4.8.0-2.x86_64 which is already installed
depending on if it's installed or not yet, of course.
could it be a repo metadata problem of some sort? just in case,
http://kdeforge.unl.edu/apt/kde-redhat/fedora/16/i386/kde48/repodata/
vs.
http://kdeforge.unl.edu/apt/kde-redhat/fedora/16/x86_64/kde48/repodata/
Ugh ... you've run into an edge case bug, the problem is that yum sees: kdebase obs. konq-plugins kde-baseapps obs. kdebase ...but then uses the wrong variable, and so tests that kdebase == kdebase (instead of kde-baseapps == kdebase) ... and decides there is a loop in the obsoletes, and ignores everything. Fix is a one-liner, but I'm not sure how easily you can work around it. Can you please push an update to yum to fix this? I don't think this is critical enough to worry about the case where people hit this when installing straight from a non-updated installation (they should get the Obsoletes triggered when they eventually update), but we should fix it now. yum-3.4.3-22.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/yum-3.4.3-22.fc16 Package yum-3.4.3-22.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing yum-3.4.3-22.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-3766/yum-3.4.3-22.fc16 then log in and leave karma (feedback). I have just run into this problem, but in Anaconda. We use a kickstart system that installs Fedora, and this adds the updates repository so that a newly installed system is up the "latest and greatest". Installs run this morning install all but one of the packages, and then Anaconda aborts trying to install konq-plugins, complaining of a checksum error. At this point I changed to the shell, chrooted to the almost installed system and tried: yum install konq-plugins This shows the 'Obsoletes' conflict as described here. So, an updated Yum RPM is not going to fix an Anaconda installation... Oh, my workaround for now is to edit the kickstart files and add: -konq-plugins to the package selection section. Ouch, konq-plugins was still listed in comps-f16, oops… This should help the Anaconda with updates case: http://git.fedorahosted.org/git/?p=comps.git;a=commitdiff;h=c8abd695933ee563e2316e403aff0ecd9c678d39 (In reply to comment #8) > Ouch, konq-plugins was still listed in comps-f16, oops… > > This should help the Anaconda with updates case: > http://git.fedorahosted.org/git/?p=comps.git;a=commitdiff;h=c8abd695933ee563e2316e403aff0ecd9c678d39 Not understanding the Yum update procedures, how/when does that change go live? As I understand it, comps gets regenerated at every update push. Package yum-3.4.3-23.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing yum-3.4.3-23.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-3766/yum-3.4.3-23.fc16 then log in and leave karma (feedback). yum-3.4.3-23.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 810543 has been marked as a duplicate of this bug. *** |