|Summary:||rpm.rpmsave backup directory created by installer|
|Product:||[Retired] Red Hat Linux||Reporter:||Chris Ricker <chris.ricker>|
|Component:||installer||Assignee:||Jeremy Katz <katzj>|
|Status:||CLOSED NOTABUG||QA Contact:||Brock Organ <borgan>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2002-04-04 20:21:48 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Chris Ricker 2001-11-27 23:56:15 UTC
Back in September, I upgraded a system from RH 7.1 to RH 7.2. I was just freeing up wasted space on the system, and discovered that the installer apparently backed up the /var/lib/rpm directory to /var/lib/rpm.rpmsave, wasting 20 megs on the system: [root@hanuman lib]# ls -ld rpm* drwxr-xr-x 2 root root 1024 Nov 27 15:55 rpm drwxr-xr-x 2 rpm rpm 1024 Sep 16 21:02 rpm.rpmsave [root@hanuman lib]# du -s rpm* 7975 rpm 12403 rpm.rpmsave [root@hanuman lib]#
Comment 1 Michael Fulbright 2001-12-03 21:07:45 UTC
I believe this is necessary because we want to backup the original database before preforming a rebuild on it. Assigning bug to an engineer.
Comment 2 Chris Ricker 2001-12-03 23:45:14 UTC
Well, I'll agree that the backup is necessary, but the installer should have removed it afterwards....
Comment 3 Jeremy Katz 2002-04-04 20:36:08 UTC
But we don't want to remove it after install. There is no way for me to tell that the new RPM database is actually valid and has correct information. Leaving the old one there gives you at least something to fall back to in the case that there is a problem.