Description of problem: Last week I accidentally pushed an update with a bug in specfile - it has wrong provides/obsoletes and it get thru the testing repository to stable and broke other packages with deps on accidentally obsoleted package. So I did a new update with fixed prov/obs, pushed it, but yum is still trying to cover the missing dependency using the previous package, which fails (obviously). Version-Release number of selected component (if applicable): yum-3.2.29-9.fc16.noarch How reproducible: $ yum update - should bring new libreport-2.0.4-1.fc15 package, obsoleting report-gtk $ yum update libreport --enablerepo=updates-testing - this should pull libreport-2.0.4-2.fc15 with fixed prov/obs - this actually won't work, as the update got bad karma because of this problem and was removed from testing (you can download it here: http://koji.fedoraproject.org/koji/buildinfo?buildID=250462) - before it was removed from testing this failed with: Error: Protected multilib versions: libreport-gtk-2.0.4-2.fc15.x86_64 != libreport-gtk-2.0.4-1.fc15.i686 Error: Protected multilib versions: libreport-2.0.4-1.fc15.i686 != libreport-2.0.4-2.fc15.x86_64 Additional info: Seems to affect only x86_64.
It's going to be impossible to debug this without a clear understanding of what all the versions of packages were ... and probably the full -v output of the "yum update" or "yum update libreport".
Created attachment 512042 [details] output of ' yum -v install /home/chris/Desktop/libreport-*' Here you are.
Ok, that is the "original problem" AIUI where a new version had a missing report-gtk provide ... so yum started at: Searching pkgSack for dep: report-gtk ...and everything went downhill from there. This is "expected", although it could be clearer about why it's failing. Is there something else you think yum should be doing here?
(In reply to comment #3) > Ok, that is the "original problem" AIUI where a new version had a missing > report-gtk provide ... so yum started at: > > Searching pkgSack for dep: report-gtk > > ...and everything went downhill from there. This is "expected", although it > could be clearer about why it's failing. > Is there something else you think yum should be doing here? - in this case yum finds the old libreport package providing report-gtk and try to add it into the transaction which fails for obvious reasons, so how about it forgets about the older libreport package and continue looking for other alternatives?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping