I used the FC4 CD to try to upgrade my laptop which had been running FC3.
Although the process seemed to finish normally, when I rebooted, I noticed that
many dozens of packages remained untouched by the upgrade, including the kernel
and glibc packages.
I had to upgrade the kernel and glibc packages with rpm, then use yum to grab
the remaining upgrades.
(Since I had been keeping my FC3 system relatively current with updated
packages, the installed FC3 glibc package actually had a higher version number
than the FC4 package. Perhaps this explains anaconda's confusion?)
See the attached upgrade.log.
Created attachment 120927 [details]
Yep, anaconda can't upgrade things to a lower version number... that's a bug in
the specific packages as they should be making sure that they keep their version
lower than the FC4 released version
I'm not sure I understand how this could be a bug in the specific packages.
What version number should an updated FC3 glibc use if it is based on 2.3.6? It
seems sort of odd to call it 2.3.5 just to keep FC4 happy.