Fedora + Yum Problems

[n2ize]

Hello. I need the help of someone who is well versed in understanding Linux and the YUM package manager. Maybe someone can help me out on this. I was in the middle of doing a routine update via yum on a Fedora 20 (64 bit) system. I was using the standard update notifier on the panel which has always worked problem free. For some crazy and unknown reason the system shut down on me during the update. Now when I try to complete the update transaction it fails with errors telling me there are duplicate packages. For example, trying to update libuuid gives me...

[root@galois ~]# yum update libuuid
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package libuuid.i686 0:2.24.2-1.fc20 will be updated
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: util-linux-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libmount-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libblkid-2.24.2-1.fc20.x86_64
---> Package libuuid.x86_64 0:2.24.2-1.fc20 will be updated
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libmount-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libblkid-2.24.2-1.fc20.x86_64
---> Package libuuid.i686 0:2.24.2-2.fc20 will be an update
---> Package libuuid.x86_64 0:2.24.2-2.fc20 will be an update
--> Running transaction check
---> Package libuuid.i686 0:2.24.2-1.fc20 will be updated
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libmount-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libblkid-2.24.2-1.fc20.x86_64
---> Package libuuid.x86_64 0:2.24.2-1.fc20 will be updated
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libmount-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libblkid-2.24.2-1.fc20.x86_64
---> Package util-linux.x86_64 0:2.24.2-1.fc20 will be updated
---> Package util-linux.x86_64 0:2.24.2-2.fc20 will be an update
--> Finished Dependency Resolution
Error: Package: libmount-2.24.2-1.fc20.x86_64 (installed)
Requires: libuuid = 2.24.2-1.fc20
Removing: libuuid-2.24.2-1.fc20.i686 (installed)
libuuid = 2.24.2-1.fc20
Updated By: libuuid-2.24.2-2.fc20.i686 (updates)
libuuid = 2.24.2-2.fc20
Available: libuuid-2.24-2.fc20.i686 (fedora)
libuuid = 2.24-2.fc20
Error: Package: libblkid-2.24.2-1.fc20.x86_64 (installed)
Requires: libuuid = 2.24.2-1.fc20
Removing: libuuid-2.24.2-1.fc20.i686 (installed)
libuuid = 2.24.2-1.fc20
Updated By: libuuid-2.24.2-2.fc20.i686 (updates)
libuuid = 2.24.2-2.fc20
Available: libuuid-2.24-2.fc20.i686 (fedora)
libuuid = 2.24-2.fc20
You could try using --skip-broken to work around the problem
** Found 17 pre-existing rpmdb problem(s), 'yum check' output follows:
1:autocorr-en-4.2.7.2-11.fc20.noarch is a duplicate with 1:autocorr-en-4.2.7.2-9.fc20.noarch
libblkid-2.24.2-2.fc20.x86_64 is a duplicate with libblkid-2.24.2-1.fc20.x86_64
libmount-2.24.2-2.fc20.x86_64 is a duplicate with libmount-2.24.2-1.fc20.x86_64
2:libnm-qt-0.9.8.3-1.fc20.x86_64 is a duplicate with 2:libnm-qt-0.9.8.2-5.fc20.x86_64
1:libreoffice-core-4.2.7.2-11.fc20.x86_64 is a duplicate with 1:libreoffice-core-4.2.7.2-9.fc20.x86_64
1:libreoffice-opensymbol-fonts-4.2.7.2-11.fc20.noarch is a duplicate with 1:libreoffice-opensymbol-fonts-4.2.7.2-9.fc20.noarch
1:libreoffice-ure-4.2.7.2-11.fc20.x86_64 is a duplicate with 1:libreoffice-ure-4.2.7.2-9.fc20.x86_64
libuuid-2.24.2-2.fc20.x86_64 is a duplicate with libuuid-2.24.2-1.fc20.x86_64
motion-3.3.0-trunkREV557.11.fc19.x86_64 has missing requires of libavcodec.so.54()(64bit)
motion-3.3.0-trunkREV557.11.fc19.x86_64 has missing requires of libavcodec.so.54(LIBAVCODEC_54)(64bit)
motion-3.3.0-trunkREV557.11.fc19.x86_64 has missing requires of libavformat.so.54()(64bit)
motion-3.3.0-trunkREV557.11.fc19.x86_64 has missing requires of libavformat.so.54(LIBAVFORMAT_54)(64bit)
php-cli-5.5.19-3.fc20.x86_64 is a duplicate with php-cli-5.5.18-1.fc20.x86_64
php-common-5.5.19-3.fc20.x86_64 is a duplicate with php-common-5.5.18-1.fc20.x86_64
php-pdo-5.5.19-3.fc20.x86_64 is a duplicate with php-pdo-5.5.18-1.fc20.x86_64
selinux-policy-3.12.1-195.fc20.noarch is a duplicate with selinux-policy-3.12.1-193.fc20.noarch
wireshark-1.10.11-1.fc20.x86_64 is a duplicate with wireshark-1.10.10-1.fc20.x86_64

I am trying to fix this so "yum update" works again. I have already tried running "$ yum-complete-transaction" but it won't fix the problem. Searching around online has so far given me partial half-assed answers ranging from manually fixing the problem. Not sure how to go about fixing this. I tried running "$ package-cleanup --dupes" and it gives me a listing of all the duplicate packages so its definitely a multipackage issue. But where do I go from there ? Do I manually remove each of the older packages one by one ? Can I run "$ package-cleanup --cleandupes" to remove all the duplicates ? I was going to try this but I read that this can sometimes cause more problems.

In any even, short of reinstalling the entire system, what is the best way to fix this. Any helpful ideas, comments ,,etc. are appreciated.

[KC2UGV]

yum clean all

If that doesn't work, follow the steps here:
http://www.cyberciti.biz/tips/rebuil...-database.html

(You don't really need to drop to single user for this)

[n2ize]

yum clean all

If that doesn't work, follow the steps here:
http://www.cyberciti.biz/tips/rebuil...-database.html

(You don't really need to drop to single user for this)

Much thanks. I'll give it a try when I get back home. I'll let you know how it works out.

[n2ize]

yum clean all

If that doesn't work, follow the steps here:
http://www.cyberciti.biz/tips/rebuil...-database.html

(You don't really need to drop to single user for this)

Okay, so far "$yum clean all" doesn't do the trick. So, I am going to have to check out the link you provided and see if I can find an answer there.

In the future I will make sure to never interrupt a yum update, either accidentally (as in this case) or intentionally. I think I'll do all my future updates in single user mode with as few processes as needed running in the background.

[n2ize]

The problem seems to be that YUM is seeing 2 packages for each package it's trying to update. In other words it's seeing duplicates... the old version and the new version which is also yielding dependency issues. One would think it's a simple matter to fix an interrupted routine update but apparently it is not.

[KC2UGV]

The problem seems to be that YUM is seeing 2 packages for each package it's trying to update. In other words it's seeing duplicates... the old version and the new version which is also yielding dependency issues. One would think it's a simple matter to fix an interrupted routine update but apparently it is not.

No, it's really not... You could do a yum erase on the package it's seeing a dupe of. The rebuilding of the rpm db is a pretty safe maneuver. Do backups of the db files.

[n2ize]

No, it's really not... You could do a yum erase on the package it's seeing a dupe of. The rebuilding of the rpm db is a pretty safe maneuver. Do backups of the db files.

OK I'll try that. I was thinking of doing that earlier but I wasn't sure. I guess I would delete the older package assuming the newer package was properly installed ??

[NA4BH]

[n2ize]

Thanks. A little light hearted humor is always welcome. :) While I am dealing with a red fedora here I got a smile out of the green fedora. Cute classic cartoon.

[n2ize]

No, it's really not... You could do a yum erase on the package it's seeing a dupe of. The rebuilding of the rpm db is a pretty safe maneuver. Do backups of the db files.

Okay, so far so good. I first tried to use "# yum erase" to remove the dupes but it wanted to also remove all packages that were dependent on the dupe. So I used "rpm -e --nodeps <dupe-package-name>" and that seemed to clear the dupes. I did them manually one by one, fortunately there weren't too many, otherwise I would have had to write a shell program to do it quicker. Okay, once the dupes were cleared I did a "# yum clean all" and a "# rpm --rebuilddb" and all seems okay now. I did a system update and it went okay. So, as long as no unexpected glitches kick in I'll label this problem as FIXED. Much thanks for your help.