Red Hat Bugzilla – Bug 218159
Duplicate packages after upgrade to FC6 from a previous release
Last modified: 2013-01-09 23:08:52 EST
Description of problem:
All problems described bellow occur on a *stock* install of FC6 (i.e. an install
that only includes rpm packages from Core or Extras).
After performing an upgrade to FC6 from a previous release (I tested that with
FC5 and FC4), a "rpm -qa | sort" shows duplicate packages compiled for both the
new and the old distro (marked .fc6 AND .fc5).
Version-Release number of selected component (if applicable):
Fedora Core 6 distro + updates as for 12/01/2006
Steps to Reproduce:
1. Install a stock FC5
2. Use the standard FC6 CDs or DVD to upgrade the installation to FC6
3. Perform a rpm -qa | sort
There are duplicate packages from FC6 and previous releases, with identical
names. Disk space is unnecesarily lost.
No duplicate packages should exist after upgrade; distribution should provide a
script to automatically clean the packages from the old distro. This script
should be either integrated in anaconda, at the end, or in firstboot or provided
separately (to minimise the time used for upgrading). References to it should
explicitly exist in the docs.
Was this an x86_64 install/upgrade? What you're most likely seeing is that you
have multilib packages installed. an i386 match for the x86-64 package. Only
the different files are duplicated, identical files are not written out. You
can verify with:
rpm -q duppackage.x86_64
rpm -q duppackage.i386
You would get results for both if multilib is indeed what you're seeing. And
yes, this is by design.
Hello and thanks,
No, it is a simple i386 architecture and it happened to me on more than one machine.
Multiple machiens that were upgrades from FC5, or multiple machines that were
clean installs of FC6?
Can you give me an example of some of the packages? (output of rpm -q)
The described phenomenon happened to me on more than one machine that was
upgraded from FC5 (or FC4) to FC6. I have one or two machines that were "chainly
upgraded" FC4 -> FC5 -> FC6, but not just only on those...
Here are some examples of duplicated packages(randomly choosen, maybe not on the
*same* machine all of them):
and examples may continue...
What I did to those systems in their lifecycle is to:
- freshly install FC5 (from FC5's CDs ord DVD, using just packages from Core or
- keep the system up to date making an "yum -y upgrade" with the official
repositories for FC5 configured) or simply using the nightly yum cron;
- upgrade to FC6 (using the FC6's CDs or DVD in "upgrade" mode)
- upgrade the system to the lastest packages using "yum -y upgrade" with the
official repositories for FC6 configured) or using the nightly yum cron;
Is there any additional task/script necessary to keep those systems "clean" from
old packages ?
I'm reassigning this to anaconda. They might have a better idea whats going on
Please attach /var/log/anaconda* and /root/install.log, /root/upgrade.log, if
Created attachment 144698 [details]
Created attachment 144699 [details]
Created attachment 144700 [details]
Created attachment 144701 [details]
Created attachment 144703 [details]
Created attachment 144704 [details]
Created attachment 144705 [details]
I am pleased to provide the requested files (please see above).
There is another trace of old files/packages on some of my systems:
Some systems were upgraded from FC5 to FC6 and then kept regularily up-to-date
through yum. However, here is what I get today (January 27, 2007), agter a new
cman for FC6 is out:
file /usr/share/man/man8/fence_tool.8.gz from install of cman-2.0.60-1.fc6
conflicts with file from package fence-1.32.17-0.FC5.1
file /sbin/ccs_test from install of cman-2.0.60-1.fc6 conflicts with file from
(there are actually many such messages, but all of them refers to packages css
Now, IMHO, it is obvious that packages css and fence were neither upgraded when
passing from FC5 to FC6 nor deleted.
I resolved the issue by deleting them manually and I continued the upgrade, but
just wanted to make note oh this.