I am unable to find yum/rpm instructions on how to find/locate duplicate packages that might be on my system.
Does anyone know how this is done?
Thanks! Dan
Daniel B. Thurman wrote:
I am unable to find yum/rpm instructions on how to find/locate duplicate packages that might be on my system.
Does anyone know how this is done?
Thanks! Dan
Erm... I don't mean exact duplicates, but packages that are "left behind" and superseded by new packages. Sometimes newer packages are installed and older ones are not removed via the cleanup processes. There are exceptions of course, such as kernels, which must be removed manually, when desired.
I am basically looking for packages that are no longer needed when new packages are installed, so that I can reclaim disk space.
Thanks! Dan
Daniel B. Thurman wrote:
Daniel B. Thurman wrote:
I am unable to find yum/rpm instructions on how to find/locate duplicate packages that might be on my system.
Does anyone know how this is done?
Thanks! Dan
Erm... I don't mean exact duplicates, but packages that are "left behind" and superseded by new packages. Sometimes newer packages are installed and older ones are not removed via the cleanup processes. There are exceptions of course, such as kernels, which must be removed manually, when desired.
I am basically looking for packages that are no longer needed when new packages are installed, so that I can reclaim disk space.
Thanks! Dan
Do you mean those left in your yum cache? If so, they're in /var/cache/yum/<repo-name>/packages.
yum clean all should clean them up.
On Thu, Mar 26, 2009 at 11:04:41AM -0700, Daniel B. Thurman wrote:
I am unable to find yum/rpm instructions on how to find/locate duplicate packages that might be on my system.
Does anyone know how this is done?
Install the 'yum-utils' package. It includes the 'package-cleanup' utility that does what you want.
Paul W. Frields wrote:
On Thu, Mar 26, 2009 at 11:04:41AM -0700, Daniel B. Thurman wrote:
I am unable to find yum/rpm instructions on how to find/locate duplicate packages that might be on my system.
Does anyone know how this is done?
Install the 'yum-utils' package. It includes the 'package-cleanup' utility that does what you want.
Thanks for the tip!
Howevcr, I ran into this problem: ================================================== # package-cleanup --cleandupes Setting up yum Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile I will remove the following old duplicate packages: 2:lam-libs-7.1.2-11.fc9.i386 postgresql-pgpoolAdmin-1.0.0-7.fc8.noarch Is this ok [y/N]: y /usr/lib/lam/lam.ld.conf has not been configured as an alternative for mpilibs32 error: %preun(lam-libs-7.1.2-11.fc9.i386) scriptlet failed, exit status 2 =====================================================
So, how can I remove lam-libs?
On Thu, Mar 26, 2009 at 01:22:07PM -0700, Daniel B. Thurman wrote:
Paul W. Frields wrote:
On Thu, Mar 26, 2009 at 11:04:41AM -0700, Daniel B. Thurman wrote:
I am unable to find yum/rpm instructions on how to find/locate duplicate packages that might be on my system.
Does anyone know how this is done?
Install the 'yum-utils' package. It includes the 'package-cleanup' utility that does what you want.
Thanks for the tip!
Howevcr, I ran into this problem:
# package-cleanup --cleandupes Setting up yum Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile I will remove the following old duplicate packages: 2:lam-libs-7.1.2-11.fc9.i386 postgresql-pgpoolAdmin-1.0.0-7.fc8.noarch Is this ok [y/N]: y /usr/lib/lam/lam.ld.conf has not been configured as an alternative for mpilibs32 error: %preun(lam-libs-7.1.2-11.fc9.i386) scriptlet failed, exit status 2 =====================================================
So, how can I remove lam-libs?
This was a bug in that release of the lam-libs package, which was fixed in the newest lam-libs. I would do this (as root):
rpm -q --scripts lam-libs-7.1.2-11.fc9 > /tmp/lam-libs-scripts rpm -e --noscripts lam-libs-7.1.2-11.fc9
Then look at the /tmp/lam-libs-scripts, in particular %preun and %postun, and see if there's anything you need to handle manually.
Paul W. Frields wrote:
On Thu, Mar 26, 2009 at 01:22:07PM -0700, Daniel B. Thurman wrote:
Paul W. Frields wrote:
On Thu, Mar 26, 2009 at 11:04:41AM -0700, Daniel B. Thurman wrote:
I am unable to find yum/rpm instructions on how to find/locate duplicate packages that might be on my system.
Does anyone know how this is done?
Install the 'yum-utils' package. It includes the 'package-cleanup' utility that does what you want.
Thanks for the tip!
Howevcr, I ran into this problem:
# package-cleanup --cleandupes Setting up yum Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile I will remove the following old duplicate packages: 2:lam-libs-7.1.2-11.fc9.i386 postgresql-pgpoolAdmin-1.0.0-7.fc8.noarch Is this ok [y/N]: y /usr/lib/lam/lam.ld.conf has not been configured as an alternative for mpilibs32 error: %preun(lam-libs-7.1.2-11.fc9.i386) scriptlet failed, exit status 2 =====================================================
So, how can I remove lam-libs?
This was a bug in that release of the lam-libs package, which was fixed in the newest lam-libs. I would do this (as root):
rpm -q --scripts lam-libs-7.1.2-11.fc9 > /tmp/lam-libs-scripts rpm -e --noscripts lam-libs-7.1.2-11.fc9
Then look at the /tmp/lam-libs-scripts, in particular %preun and %postun, and see if there's anything you need to handle manually.
Interesting... this is what I have done:
# rpm -q --scripts lam-libs-7.1.2-11.fc9 > /tmp/lam-libs-scripts # rpm -e --noscripts lam-libs-7.1.2-11.fc9 # more /tmp/lam-libs-scripts postinstall scriptlet (using /bin/sh): alternatives --install /etc/ld.so.conf.d/mpi32.conf \ mpilibs32 /usr/lib/lam/lam.ld.conf 5 /sbin/ldconfig preuninstall scriptlet (using /bin/sh): alternatives --remove mpilibs32 /usr/lib/lam/lam.ld.conf postuninstall program: /sbin/ldconfig
I have no idea what the tmp file is telling me! Do you notice anything of significance?
Thanks! Dan
Daniel B. Thurman wrote:
I have no idea what the tmp file is telling me! Do you notice anything of significance?
No. There's just the alternatives --remove, which is what's failing in the first place because the alternatives are claimed not to be installed in the first place.
Kevin Kofler
Kevin Kofler wrote:
Daniel B. Thurman wrote:
I have no idea what the tmp file is telling me! Do you notice anything of significance?
No. There's just the alternatives --remove, which is what's failing in the first place because the alternatives are claimed not to be installed in the first place.
Kevin Kofler
I see! Thanks for the explanation!
Dan
Daniel B. Thurman wrote:
Erm... I don't mean exact duplicates, but packages that are "left behind" and superseded by new packages. Sometimes newer packages are installed and older ones are not removed via the cleanup processes. There are exceptions of course, such as kernels, which must be removed manually, when desired.
I am basically looking for packages that are no longer needed when new packages are installed, so that I can reclaim disk space.
You may want to look at the package-cleanup --orphans command. This lists all packages on your system that are not in a currently-configured repository (for example, because they’ve been removed from Fedora, because you’ve manually downloaded and installed them from a third party, or because you’ve installed something from updates-testing because you think you can usefully test it).
Hope this helps,
James.