Timeline for How can I resolve "duplicates" in yum?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2016 at 23:33 | review | Low quality posts | |||
| Sep 30, 2016 at 1:24 | |||||
| May 17, 2015 at 1:47 | comment | added | adam.r | Thanks for the tips. I'll let you know if they work (and update my answer if they do). The question "is this a good solution?" was meant as a section header... sorry for the ambiguity. | |
| May 15, 2015 at 8:05 | comment | added | doktor5000 | Proposed approach: First install yum-utils if not installed yet, and run package-cleanup --dupes which will only list duplicates, but will not remove anything. Then run yum-complete-transaction to try to complete any pending yum transactions. Then run yum repolist --enablerepo="*"; yum check and post the output in some pastebin service and post that link here. Be sure to not automatically uninstall all those duplicates if you don't want to make it worse. See e.g. stackoverflow.com/questions/19418301/… for more information. | |
| May 15, 2015 at 7:52 | comment | added | doktor5000 | You asked: Is this a good solution? referring to what exactly? rpm -e --justdb should basically never be used, that's the easiest way to completely mess your RPM database, and it will not solve your problem, as the files contained in those rpm packages that you only remove from the database will stay where they are. | |
| May 13, 2015 at 22:34 | history | answered | adam.r | CC BY-SA 3.0 |