I have upgraded from F-9 to F-10 with preupgrade. After I have finished the upgrade and type in a 'yum update' over 150 packages was provided for updating. I think is should be nice, if preupgrade could downloading availlable updates before starting the upgrade process, becouse it's annouying to have to downloading over 750 Meg of updates after the upgrade process.
*** Bug 477558 has been marked as a duplicate of this bug. ***
As it was said in bug 477558 a working option to enable additional repositories, not only those on a "built-in" list, would be a really helpful too.
*** Bug 492403 has been marked as a duplicate of this bug. ***
Current code in bzr (eventually to be released as 1.1.0) will search for updated versions of every repo you have enabled. This should enable updates, updates-testing (if you have that turned on), and even third-party repos.
This bug has a subtle difference to my bug. I was suggesting that it have an OPTION to turn on this 'latest update' behavior and therefore you could either have it work as it does today just downloading the distribution as bundled OR you could have it download the distribution but with the very latest packages from 'updates'. Is that what the new code will do?
No on/off switch planned. I can't see a use case for *not* installing updates.
Use case for having an option would be if some package is broken in updates then you can always fall back to the bundled distro and then exclude the broken package in a followup 'yum update'. OR If preupgrade would respect the yum excludes then we could just list it there and keep going. Also, will the user be able to select a list of update repos to use from the repos that the user has enabled?
preupgrade-1.1.0-0.pre2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/preupgrade-1.1.0-0.pre2.fc10
preupgrade-1.1.0-0.pre2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update preupgrade'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4211
preupgrade-1.1.0-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/preupgrade-1.1.0-1.fc9
preupgrade-1.1.0-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/preupgrade-1.1.0-1.fc11
*** Bug 500647 has been marked as a duplicate of this bug. ***
*** Bug 477562 has been marked as a duplicate of this bug. ***
preupgrade-1.1.0-1.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update preupgrade'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4211
preupgrade-1.1.0-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
preupgrade-1.1.0-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
preupgrade-1.1.0-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
I used preupgrade-1.1.0-1.fc9.noarch (the GUI method) to upgrade from F9 to F11 today. Even though the correct repositories were enabled after the installer ran, when I ran "yum update" immediately after the upgrade, I had several hundred updates waiting for download. (I assume they were all the updates for F11 that have been posted since the final release.) I think the expectation of the original reporter (and my own hope) was that preupgrade would have downloaded these updates instead of the originally-released versions of these RPMs. In response to comment #7, I had also considered that reason not to just always download updates, but on reflection, the solution would be to simply issue another update that *does* work. (Assuming the person who encounters it has another computer they can use to report the bug, or a LiveCD, or something.)
I'm suspecting you got a mirror change of state, especially if you did it in the last couple of days as we've been having issues with our mirroring and things have just started to get back into sync.