Red Hat Bugzilla – Bug 106106
up2date wants to reinstall packages already installed
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
After a full install of Severn 2 (happened with Severn 1 as well, but I think I
failed to file the bug report :-(, after subscribing to the updates channel,
up2date offers aspell and xemacs-el as options available for updating. However,
nothing newer than the versions installed by the installer is available.
Running rpm -U --replacepkgs for the two packages silences up2date, hopefully
forever, without even having to run up2date -p. The database on the server has
the correct information. It seems to be something odd on the client side.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Perform a full install of Severn 2
2.Register with RHN, and subscribe to the updates channel
Actual Results: aspell and xemacs-el will be listed as available for updates,
even though no newer releases are available. up2date -u -f will then fail to
install the updates, because the packages are already installed.
Expected Results: It shouldn't offer to update what's already updated.
I have exactly the same problem since quite a few versions of up2date!
it got me on severn-1 and severn-2 :)
Oddly enough, even though I'd already fixed the problem with both of xemacs-el
and aspell, after rpm --rebuilddb (long story), xemacs-el came back to the list
of candidates for update, but aspell didn't.
can folks provide name-version-release info for the package in
question when they see these cases?
rpm -q xenacs-el
the `rpm --rebuilddb` is odd.
What version of xemacs-el does
rpm claim to have installed?
$ rpm -q aspell xemacs-el
As stated before, these are the packages that shipped with Severn test2, since
there haven't been any updates to them.
I couldn't duplicate the rpm --rebuilddb problem, but a full install as
described in the original bug report is a sure way to duplicate the problem.
so, that implies up2date-3.9.29?
fixed a couple bugs in 4.0 and 4.0.1,
does the same problem occur with 4.0.1 from rawhide?
Nope. I got the problem with yesterday's up2date, I just don't know exactly how
to duplicate the problem that way. Probably install as described the up2date -u
up2date should suffice.
Note that FC2 is no longer supported even by Fedora Legacy. Also, up2date has
been replaced by pirut and pup since FC5. FC3 and FC4 are supported by Fedora
Legacy for security issues only. If this still occurs on FC3 or FC4 and is a
security issue, please reopen and assign to that version and Fedora Legacy. If
it occurs on RHEL 3 or 4, please reassign or refile against that product.
The codebase for pirut and pup is quite different, so existing bugs do not
apply, but please continue testing them on the still supported versions of
Fedora Core and file bugs as necessary.