Hide Forgot
Description of problem: Upgrade from previous version of Fedora (F15) left some of the files in place instead of their counterparts from F16. Version-Release number of selected component (if applicable): yum-3.4.3-5.fc16 How reproducible: If there are files with NVR greater then in the new version Steps to Reproduce: 1. Install Fedora 15 2. Update it using the latest updates repository 3. Perform an upgrade using Fedora 16 installation DVD 4. Now update using the update repository Actual results: At the moment not all updates are available for F16 that are newer than their corresponding updates in F15, e.g. sat4j-2.3.0-2.fc15 and sat4j-2.3.0-1.fc16. Old packages were left intact during an upgrade making it impossible to replace old distribution packages until there is a more recent update available in the new repository. Expected results: Shouldn't yum take into account a distribution version? What purpose for it's included in the package NVR then? Additional info:
It's just text to yum ... it's there so that foo-1-2.fc15 is older than foo-1-2.fc16 (and that they can/are two different packages with the NEVRA in the specfile -- but not in the packages). You can use "yum distro-sync", which syncs. the latest versions available with what you have installed ... which isn't quite what you want (real distro. number treated as EPOCH), but tends to work just as well (better, in some cases).
Oh, well. I'm not insisting that this is a real bug in yum per se. But this issue need to be fixed somehow. Until then, every Fedora offline upgrade by using install media is very probably utterly broken. I myself got broken upgrade, which prevented me from logging into gnome desktop, which match blocker criteria for Fedora release. Closing this bug without any resolution at all just sweep a serious issue under the rug. Where should it be reported then?
Ok. If distro-sync is doing the right thing, then anaconda should do exactly that during an upgrade. Reopening as anaconda bug.
Currently we don't export the distro_sync API ... it's not a lot work to do so though, and hasn't changed much ... so if the anaconda guys want to try it, let me know (or just copy/paste :). On a more general level the pro/cons are: 1. distro-sync does downgrades, which aren't tested. 2. distro-sync gets the "correct" versions installed much more often (by downgrading stuff).
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is 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" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.