If somehow multiple versions of a ordinary updateable RPMs are installed,
up2date 2.1.7-1 can fail to recognize that the most recent version is
already installed. In other words, during the "Removing installed packages
from list of updates..." phase, up2date appears to notice that an earlier
version of RPM foo is there (and therefore in need of update), but not that
the later version is also there (and therefore no need to update). Then
up2date fetches the duplicate newer-version RPM, and causes a failure
up2date should be more tolerant of the possibility of multiple generations
of the same package being installed.
I have the same problem with up2date-2.1.7-0.6.x on RedHat 6.2. In particular, I
have two versions of kernel-smp installed:
% rpm -q kernel-smp
and when I run up2date, it offers me to download kernel-smp-2.2.16-3
Ditto here, I had 2.2.14 and 2.2.16 kernels installed, including sources. This
also meant that it wanted to download over 100MB, both unnecercery and
time-consuming. (And in some places, quite expencive).
To cap it off I never got the updates installed, as I also didn't have the space
working on this. thanks.
Assigned QA to jturner
*** Bug 28536 has been marked as a duplicate of this bug. ***
fixed in CVS.
Also noticed the same problem today with a manual kernel upgrade in 7.0 from
2.2.16 to 2.2.17-14. Both kernels are currently installed, but up2date is
apparently seeing only 2.2.16 and ignoring 2.2.17, even after up2date -p.
addressed in errata due out today.