Forums

Resolved
0 votes
After not having done updates in some time, I did a yum update, which was going along fine until shortly after the cleanup process started, when the process crashed. Now, according to the system, I have two versions of 132 packages installed.

If I try to do this:
yum reinstall app-accounts app-accounts core


I get:
Error:  Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:

1. You have an upgrade for app-accounts which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of app-accounts of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude app-accounts.otherarch ... this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of app-accounts installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.

3. You have duplicate versions of app-accounts installed already.
You can use "yum check" to get yum show these errors.

...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).

Protected multilib versions: 1:app-accounts-2.1.20-1.v7.noarch != 1:app-accounts-2.1.19-1.v7.noarch


If I do yum check, it just sits like this, even though I have no problem downloading updates:

[root@filegate media]# yum check
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...


I have laboriously prepared a list of the 132 package names. Is there some automated way I can force the system to uninstall the older version of each, or do I have to do rpm -e app-accounts, let it give me the two versions, then do rpm -e [old version] for every one?
Saturday, February 18 2017, 01:03 AM
Share this post:

Accepted Answer

Saturday, February 18 2017, 10:51 AM - #Permalink
Resolved
0 votes
I am a bit of a hacker. I'd bring all the logs or errors into a file then into a spreadsheet. Parse the file in the s/s (Text to Columns) to isolate all the file names of all packages to be erased then add a " \" to the end of each package name except the last. Then in a terminal type "rpm -e --nodeps " and paste the list you've just created in the s/s then cross my fingers and hit enter.
The reply is currently minimized Show
Responses (2)
  • Accepted Answer

    Saturday, February 18 2017, 02:39 AM - #Permalink
    Resolved
    0 votes
    Did it manually. Still having issues, will post another thread.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 18 2017, 01:20 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    I am a bit of a hacker. I'd bring all the logs or errors into a file then into a spreadsheet. Parse the file in the s/s (Text to Columns) to isolate all the file names of all packages to be erased then add a " \" to the end of each package name except the last. Then in a terminal type "rpm -e --nodeps " and paste the list you've just created in the s/s then cross my fingers and hit enter.


    Thank you.
    That's sort of what I did, I took the output of yum check, pasted it into a spreadsheet, and did rpm -e on the lower-version packages. The system now has no more duplicate installs, so that issue is fixed. I now have to resolve a broken mount command (can't mount a network share) and roundcube database error, but those are topics for other threads.
    The reply is currently minimized Show
Your Reply