Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hello everyone
i was updating centos server then i got this error of dulicate packages( pls see the attached jpg)
i tried to cleanup duplicates as suggested online posts.
package-cleanup --cleandupes does not remove duplicates.
this problem occurred when server was rebooted due to power failure while server was updating.
now im not able to update my system. centos 7 64 bit
I'm not sure removing conflicting packages individually is a good idea. It probably makes no difference when it comes to 'avahi' for instance, but there could be important software installed on your operating system that depends on those packages and yum will uninstall that too if you remove the dependencies. So I'd also suggest rebuilding the yum clean all, update.
I'm not saying that it can't be done that way, I'm just saying that it's risky if other programs are dependent on those packages. So you kind of have to know what you're doing, otherwise you might end up deleting more than you actually intended. It's barely a universal solution for this situation. Fixing it through rpm and yum is a much cleaner solution.
i read few posts online that suggest to remove individual packages from database.
Code:
# rpm -e --justdb PakageName
there are more than 300 packages conflicting and which are dependent or have dependencies which requires the package on the system.
i yet in search to get it work.
The screen shot shows 'found 333 existing rpmdb problems'.
I really think you'll have rebuild the rpmdb to even stand a chance.
See the links in post #2
The screen shot shows 'found 333 existing rpmdb problems'.
I really think you'll have rebuild the rpmdb to even stand a chance.
See the links in post #2
Thanx chris,
i tried those links but that does not worked.Rebuild database as suggested and ran "yum clean all" "yum update"
still i got those conflicting packages.I ran those commands with sudo user as well as root.
Do you have more than one repo installed? I've seen this when there was more than one repo installed. The fix was to turn off the repo that was causing the conflicts.
For aborted updates, yum-complete-transaction can often resolve it. It's provided in the yum-utils package. When you run the command, it will tell you what it's going to do and ask for confirmation, so you can abort if you're worried.
You can find out information about the aborted transaction in /var/lib/yum. The transaction-all-<timestamp> file has the list of what was going to be done, and transaction-done-<timestamp> has what was actually completed, so the difference between the two is what is left to be completed.
One note, I've found that if the kernel was upgraded as part of the aborted yum update, the yum-complete-transaction doesn't seem to handle that correctly, and you either end up with missing modules or a corrupt initramfs or both. Because of that, I usually reinstall the kernel after the yum-complete-transaction just to be safe.
For aborted updates, yum-complete-transaction can often resolve it. It's provided in the yum-utils package. When you run the command, it will tell you what it's going to do and ask for confirmation, so you can abort if you're worried.
You can find out information about the aborted transaction in /var/lib/yum. The transaction-all-<timestamp> file has the list of what was going to be done, and transaction-done-<timestamp> has what was actually completed, so the difference between the two is what is left to be completed.
One note, I've found that if the kernel was upgraded as part of the aborted yum update, the yum-complete-transaction doesn't seem to handle that correctly, and you either end up with missing modules or a corrupt initramfs or both. Because of that, I usually reinstall the kernel after the yum-complete-transaction just to be safe.
no incomplete transactions left..! thats what i get
After updating to new kernel , i once again ran # package-cleanup --cleandupes and # package-cleanup --orphans. And then rebuild database then everything is now working as before.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.