Hi, a few years ago i got into a mess with yum as i ran out of memory whilst upgrading the system. I didn't really know what i was doing and after a lot of cleaning up and updating to CentOS 6.7, i want to remove the duplicates but am worried about it removing libraries that i may be using inadvertently.
Can i safely remove the duplicates from the list below ?
[root@forum ~]# package-cleanup --dupes
Loaded plugins: auto-update-debuginfo, fastestmirror, priorities
lvm2-2.02.118-3.el6_7.1.x86_64
lvm2-2.02.118-3.el6_7.2.x86_64
libXfont-1.4.5-3.el6_5.x86_64
libXfont-1.4.5-4.el6_6.x86_64
device-mapper-event-libs-1.02.95-3.el6_7.2.x86_64
device-mapper-event-libs-1.02.95-3.el6_7.1.x86_64
device-mapper-1.02.95-3.el6_7.2.x86_64
device-mapper-1.02.95-3.el6_7.1.x86_64
device-mapper-libs-1.02.95-3.el6_7.2.x86_64
device-mapper-libs-1.02.95-3.el6_7.1.x86_64
lvm2-libs-2.02.118-3.el6_7.2.x86_64
lvm2-libs-2.02.118-3.el6_7.1.x86_64
net-snmp-libs-5.5-54.el6_7.1.x86_64
net-snmp-libs-5.5-54.el6.x86_64
device-mapper-event-1.02.95-3.el6_7.1.x86_64
device-mapper-event-1.02.95-3.el6_7.2.x86_64
system-config-firewall-base-1.2.27-7.1.el6.noarch
system-config-firewall-base-1.2.27-7.2.el6_6.noarch
selinux-policy-3.7.19-279.el6.noarch
selinux-policy-3.7.19-279.el6_7.5.noarch
pam-1.1.1-20.el6_7.1.x86_64
pam-1.1.1-20.el6.x86_64
nss-softokn-freebl-3.14.3-23.el6_7.x86_64
nss-softokn-freebl-3.14.3-22.el6_6.x86_64
nss-softokn-3.14.3-23.el6_7.x86_64
nss-softokn-3.14.3-22.el6_6.x86_64
yum lvm2 update error (prior to 6.8 upgrade)
yum lvm2 update error (prior to 6.8 upgrade)
Hi, I am asking for your help again please.
Sorry but this is a sort of duplicate following my cleanup of duplicates. I have been updating the duplicates and the only one group is this critical system one. I may have a repolist issue ... here is the yum output (what shall i do to fix this as i know that when i upgrade to 6.8, i will have the same problem ?
[root@forum ~]# yum update lvm2
Loaded plugins: auto-update-debuginfo, fastestmirror, priorities, security
Setting up Update Process
Loading mirror speeds from cached hostfile
* base: ftp.jaist.ac.jp
* epel: kartolo.sby.datautama.net.id
* epel-debuginfo: kartolo.sby.datautama.net.id
* extras: ftp.jaist.ac.jp
* remi-php54: mirrors.thzhost.com
* remi-safe: mirrors.thzhost.com
* rpmforge: mirror.smartmedia.net.id
* updates: ftp.jaist.ac.jp
2424 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package lvm2.x86_64 0:2.02.118-3.el6_7.1 will be updated
---> Package lvm2.x86_64 0:2.02.118-3.el6_7.2 will be updated
---> Package lvm2.x86_64 0:2.02.143-12.el6 will be an update
--> Processing Dependency: lvm2-libs = 2.02.143-12.el6 for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: device-mapper-persistent-data >= 0.6.2 for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_113)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_110)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_104)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_103)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_101)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_100)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Running transaction check
---> Package device-mapper-libs.x86_64 0:1.02.95-3.el6_7.1 will be updated
--> Processing Dependency: device-mapper-libs = 1.02.95-3.el6_7.1 for package: device-mapper-1.02.95-3.el6_7.1.x86_64
---> Package device-mapper-libs.x86_64 0:1.02.95-3.el6_7.2 will be updated
--> Processing Dependency: device-mapper-libs = 1.02.95-3.el6_7.2 for package: device-mapper-1.02.95-3.el6_7.2.x86_64
---> Package device-mapper-libs.x86_64 0:1.02.117-12.el6 will be an update
---> Package device-mapper-persistent-data.x86_64 0:0.3.2-1.el6 will be updated
---> Package device-mapper-persistent-data.x86_64 0:0.6.2-0.1.rc7.el6 will be an update
---> Package lvm2-libs.x86_64 0:2.02.118-3.el6_7.1 will be updated
---> Package lvm2-libs.x86_64 0:2.02.118-3.el6_7.2 will be updated
---> Package lvm2-libs.x86_64 0:2.02.143-12.el6 will be an update
--> Processing Dependency: device-mapper-event = 1.02.117-12.el6 for package: lvm2-libs-2.02.143-12.el6.x86_64
--> Running transaction check
---> Package device-mapper.x86_64 0:1.02.95-3.el6_7.1 will be updated
---> Package device-mapper.x86_64 0:1.02.95-3.el6_7.2 will be updated
---> Package device-mapper.x86_64 0:1.02.117-12.el6 will be an update
---> Package device-mapper-event.x86_64 0:1.02.95-3.el6_7.1 will be updated
---> Package device-mapper-event.x86_64 0:1.02.95-3.el6_7.2 will be updated
---> Package device-mapper-event.x86_64 0:1.02.117-12.el6 will be an update
--> Processing Dependency: device-mapper-event-libs = 1.02.117-12.el6 for package: device-mapper-event-1.02.117-12.el6.x86_64
---> Package device-mapper-libs.x86_64 0:1.02.95-3.el6_7.1 will be updated
--> Running transaction check
---> Package device-mapper-event-libs.x86_64 0:1.02.95-3.el6_7.1 will be updated
---> Package device-mapper-event-libs.x86_64 0:1.02.95-3.el6_7.2 will be updated
---> Package device-mapper-event-libs.x86_64 0:1.02.117-12.el6 will be an update
--> Finished Dependency Resolution
Error: Package: device-mapper-1.02.95-3.el6_7.1.x86_64 (@updates)
Requires: device-mapper-libs = 1.02.95-3.el6_7.1
Removing: device-mapper-libs-1.02.95-3.el6_7.1.x86_64 (@updates)
device-mapper-libs = 1.02.95-3.el6_7.1
Updated By: device-mapper-libs-1.02.117-12.el6.x86_64 (base)
device-mapper-libs = 1.02.117-12.el6
Removing: device-mapper-libs-1.02.95-3.el6_7.2.x86_64 (installed)
device-mapper-libs = 1.02.95-3.el6_7.2
Updated By: device-mapper-libs-1.02.117-12.el6.x86_64 (base)
device-mapper-libs = 1.02.117-12.el6
You could try using --skip-broken to work around the problem
** Found 8 pre-existing rpmdb problem(s), 'yum check' output follows:
device-mapper-1.02.95-3.el6_7.2.x86_64 is a duplicate with device-mapper-1.02.95-3.el6_7.1.x86_64
device-mapper-event-1.02.95-3.el6_7.2.x86_64 is a duplicate with device-mapper-event-1.02.95-3.el6_7.1.x86_64
device-mapper-event-libs-1.02.95-3.el6_7.2.x86_64 is a duplicate with device-mapper-event-libs-1.02.95-3.el6_7.1.x86_64
device-mapper-libs-1.02.95-3.el6_7.2.x86_64 is a duplicate with device-mapper-libs-1.02.95-3.el6_7.1.x86_64
kernel-firmware-2.6.32-573.3.1.el6.noarch is a duplicate with kernel-firmware-2.6.32-573.1.1.el6.noarch
lvm2-2.02.118-3.el6_7.2.x86_64 is a duplicate with lvm2-2.02.118-3.el6_7.1.x86_64
lvm2-libs-2.02.118-3.el6_7.2.x86_64 is a duplicate with lvm2-libs-2.02.118-3.el6_7.1.x86_64
sqlite-3.6.20-1.el6_7.2.x86_64 is a duplicate with sqlite-3.6.20-1.el6.i686
Sorry but this is a sort of duplicate following my cleanup of duplicates. I have been updating the duplicates and the only one group is this critical system one. I may have a repolist issue ... here is the yum output (what shall i do to fix this as i know that when i upgrade to 6.8, i will have the same problem ?
[root@forum ~]# yum update lvm2
Loaded plugins: auto-update-debuginfo, fastestmirror, priorities, security
Setting up Update Process
Loading mirror speeds from cached hostfile
* base: ftp.jaist.ac.jp
* epel: kartolo.sby.datautama.net.id
* epel-debuginfo: kartolo.sby.datautama.net.id
* extras: ftp.jaist.ac.jp
* remi-php54: mirrors.thzhost.com
* remi-safe: mirrors.thzhost.com
* rpmforge: mirror.smartmedia.net.id
* updates: ftp.jaist.ac.jp
2424 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package lvm2.x86_64 0:2.02.118-3.el6_7.1 will be updated
---> Package lvm2.x86_64 0:2.02.118-3.el6_7.2 will be updated
---> Package lvm2.x86_64 0:2.02.143-12.el6 will be an update
--> Processing Dependency: lvm2-libs = 2.02.143-12.el6 for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: device-mapper-persistent-data >= 0.6.2 for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_113)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_110)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_104)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_103)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_101)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_100)(64bit) for package: lvm2-2.02.143-12.el6.x86_64
--> Running transaction check
---> Package device-mapper-libs.x86_64 0:1.02.95-3.el6_7.1 will be updated
--> Processing Dependency: device-mapper-libs = 1.02.95-3.el6_7.1 for package: device-mapper-1.02.95-3.el6_7.1.x86_64
---> Package device-mapper-libs.x86_64 0:1.02.95-3.el6_7.2 will be updated
--> Processing Dependency: device-mapper-libs = 1.02.95-3.el6_7.2 for package: device-mapper-1.02.95-3.el6_7.2.x86_64
---> Package device-mapper-libs.x86_64 0:1.02.117-12.el6 will be an update
---> Package device-mapper-persistent-data.x86_64 0:0.3.2-1.el6 will be updated
---> Package device-mapper-persistent-data.x86_64 0:0.6.2-0.1.rc7.el6 will be an update
---> Package lvm2-libs.x86_64 0:2.02.118-3.el6_7.1 will be updated
---> Package lvm2-libs.x86_64 0:2.02.118-3.el6_7.2 will be updated
---> Package lvm2-libs.x86_64 0:2.02.143-12.el6 will be an update
--> Processing Dependency: device-mapper-event = 1.02.117-12.el6 for package: lvm2-libs-2.02.143-12.el6.x86_64
--> Running transaction check
---> Package device-mapper.x86_64 0:1.02.95-3.el6_7.1 will be updated
---> Package device-mapper.x86_64 0:1.02.95-3.el6_7.2 will be updated
---> Package device-mapper.x86_64 0:1.02.117-12.el6 will be an update
---> Package device-mapper-event.x86_64 0:1.02.95-3.el6_7.1 will be updated
---> Package device-mapper-event.x86_64 0:1.02.95-3.el6_7.2 will be updated
---> Package device-mapper-event.x86_64 0:1.02.117-12.el6 will be an update
--> Processing Dependency: device-mapper-event-libs = 1.02.117-12.el6 for package: device-mapper-event-1.02.117-12.el6.x86_64
---> Package device-mapper-libs.x86_64 0:1.02.95-3.el6_7.1 will be updated
--> Running transaction check
---> Package device-mapper-event-libs.x86_64 0:1.02.95-3.el6_7.1 will be updated
---> Package device-mapper-event-libs.x86_64 0:1.02.95-3.el6_7.2 will be updated
---> Package device-mapper-event-libs.x86_64 0:1.02.117-12.el6 will be an update
--> Finished Dependency Resolution
Error: Package: device-mapper-1.02.95-3.el6_7.1.x86_64 (@updates)
Requires: device-mapper-libs = 1.02.95-3.el6_7.1
Removing: device-mapper-libs-1.02.95-3.el6_7.1.x86_64 (@updates)
device-mapper-libs = 1.02.95-3.el6_7.1
Updated By: device-mapper-libs-1.02.117-12.el6.x86_64 (base)
device-mapper-libs = 1.02.117-12.el6
Removing: device-mapper-libs-1.02.95-3.el6_7.2.x86_64 (installed)
device-mapper-libs = 1.02.95-3.el6_7.2
Updated By: device-mapper-libs-1.02.117-12.el6.x86_64 (base)
device-mapper-libs = 1.02.117-12.el6
You could try using --skip-broken to work around the problem
** Found 8 pre-existing rpmdb problem(s), 'yum check' output follows:
device-mapper-1.02.95-3.el6_7.2.x86_64 is a duplicate with device-mapper-1.02.95-3.el6_7.1.x86_64
device-mapper-event-1.02.95-3.el6_7.2.x86_64 is a duplicate with device-mapper-event-1.02.95-3.el6_7.1.x86_64
device-mapper-event-libs-1.02.95-3.el6_7.2.x86_64 is a duplicate with device-mapper-event-libs-1.02.95-3.el6_7.1.x86_64
device-mapper-libs-1.02.95-3.el6_7.2.x86_64 is a duplicate with device-mapper-libs-1.02.95-3.el6_7.1.x86_64
kernel-firmware-2.6.32-573.3.1.el6.noarch is a duplicate with kernel-firmware-2.6.32-573.1.1.el6.noarch
lvm2-2.02.118-3.el6_7.2.x86_64 is a duplicate with lvm2-2.02.118-3.el6_7.1.x86_64
lvm2-libs-2.02.118-3.el6_7.2.x86_64 is a duplicate with lvm2-libs-2.02.118-3.el6_7.1.x86_64
sqlite-3.6.20-1.el6_7.2.x86_64 is a duplicate with sqlite-3.6.20-1.el6.i686
Re: Ok to clean up these duplicate packages ?
I have mostly resolved these by updating each package BUT i started another topic as i am stuck on lvm2 / device-mapper.
Mods: you may remove this thread if you wish as the other one is now my main issue.
Mods: you may remove this thread if you wish as the other one is now my main issue.
Re: yum lvm2 update error (prior to 6.8 upgrade)
You need to use rpm -e --justdb --nodeps $package-full.version.number to remove all of the newer versions of each of the duplicate packages. That will remove the duplicates and then when you yum update it will bring down the newer one and put it on from scratch and make sure that it is on the system properly.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: yum lvm2 update error (prior to 6.8 upgrade)
thank you so much.
that makes a lot of sense.
I will report back when I have removed the db entries for each of the newer packages.
that makes a lot of sense.
I will report back when I have removed the db entries for each of the newer packages.
Re: yum lvm2 update error (prior to 6.8 upgrade)
you are e LEGEND ! I finally upgraded to CentOS 6.9 and my system is now totally free of any rpm db issues.
i have been worried about this for over a year and i'm really glad that i didn't try to run package-cleanup --dupes like i saw so much encouragement to.
I am forever grateful to this community and guys like you.
i have been worried about this for over a year and i'm really glad that i didn't try to run package-cleanup --dupes like i saw so much encouragement to.
I am forever grateful to this community and guys like you.