On Sun, May 24, 2009 at 1:28 PM, Kåre Fiedler Christiansen fedora@kaarefc.dk wrote:
On Sun, May 24, 2009 at 21:16, Reid Rivenburgh reidr@pobox.com wrote:
<snip>
Is it possible that some of my pre-upgrade rpms (when I was using F10's updates-testing, not rawhide) were newer versions than the F11 ones, and therefore they didn't get upgraded? That's what these versions seem to suggest. I guess I can force install the F11 versions now and get things in order?
There's an updates-testing-repository for Fedora 11 as well. You can find the same version of qt-mysql in that repository.
See e.g. http://mirrors.kernel.org/fedora/updates/testing/11/x86_64/
If you have upgraded F10 with updates-testing enabled, you should probably enable updates-testing on your F11 installation as well. I guess it could be considered a preupgrade/anaconda bug that it isn't done so by default?
(Non-critical updates now end up in the "updates" repository for Fedora 11, rather than getting pushed to rawhide - and before that updates-testing)
I see. I also just realized that I don't have rawhide enabled. For some reason, I thought it would be, and that having rawhide enabled was a good thing until the post-release update that moves me from rawhide back to non-rawhide F11 (if I understand that process correctly).
In any case, enabling rawhide didn't give me any new packages, as you suggest. I assumed rawhide was always at least as new (in terms of version number) as update-testing, and similarly for updates-testing for updates. I guess that's not necessarily true around release time. I enabled updates-testing, and I do have lots of updates available now. So I guess I do want both updates-testing and rawhide enabled?
Thanks for all of the help. I hope this hasn't been hashed out lots of times already. I just re-joined the testing list when I upgraded.
Reid