When did yum get all wordy?

Tom Horsley horsley1953 at gmail.com
Thu Mar 21 11:22:35 UTC 2013

I see this in my cron output from last night:

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 sip which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of sip 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 sip.otherarch ... this should give you an error
            message showing the root cause of the problem.
         2. You have multiple architectures of sip installed, but
            yum can only see an upgrade for one of those arcitectures.
            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 sip 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: sip-4.14.4-1.fc17.x86_64 != sip-4.13.2-1.fc17.i686

And if it is gonna spew out a big spiel like this, shouldn't it mention
that actual cause of 99.999999% of all multilib problems: The 32 and
64 bit versions are not in sync in the repos and if you wait a bit, they'll
be back in sync again.

More information about the users mailing list