Red Hat Bugzilla – Bug 119946
up2date not deleting (or deleting when it should not)
Last modified: 2007-11-30 17:10:39 EST
Description of problem:
selinux enforce ON (setenforce 1).
Using the packages from development on 3 April 04, I selected the
following for update:
I ended up with two version of policy-sources in the rpm db.
While I still have everything, what information do you wnat me to capture.
Version-Release number of selected component (if applicable):
FC2T2 plus current (development) up2date and rpm-*
Yes. First time on x86_64 and then reporduced it on a ix86 system.
While this "did not delete old package" is clear, I have also had
occurances of a new package failing to install but up2date did not
detect this and removed the old package (leaving nothing installed).
One of these occurances was for gdm IIRC. What I am not sure of is if
the actual files were deleted or just the rpm DB screwed up.
I have more or less all of the updates issued since FC2T1 was released
in a local repository and could possibly recreate the situation if
needed ... but it would not be easy and I would prefer not to do that.
selected results of rpm -qa --last
selinux-doc-1.8-3 Sat 03 Apr 2004 04:32:42
policy-sources-1.9.2-9 Sat 03 Apr 2004 04:32:37
elfutils-devel-0.95-2 Sat 03 Apr 2004 04:32:34
elfutils-libelf-devel-0.95-2 Sat 03 Apr 2004 04:32:33
arts-devel-1.2.1-2 Sat 03 Apr 2004 04:32:33
policycoreutils-1.9.2-1 Sat 03 Apr 2004 04:32:32
policy-1.9.2-9 Sat 03 Apr 2004 04:32:32
elfutils-0.95-2 Sat 03 Apr 2004 04:32:30
arts-1.2.1-2 Sat 03 Apr 2004 04:32:29
elfutils-libelf-0.95-2 Sat 03 Apr 2004 04:32:09
rp-pppoe-3.5-14 Fri 02 Apr 2004 05:01:04
rpmdb-fedora-1.91-0.20040402 Fri 02 Apr 2004 03:52:58
policy-sources-1.9.2-5 Fri 02 Apr 2004 03:52:47
libselinux-devel-1.9-1 Fri 02 Apr 2004 03:52:45
It is interesting that something in up2date detected that packages had
not been processed or processed properly because the total progress
bad was not at the complete point when the "finished" message appears.
er, no idea... afaik nothing in the code has changed to
cause anything to not delete (especially on "-U" style
updates). Might be an rpm issue, trying to reproduce...
I am closing this as I do not believe it happens with the latest policy.