Probleme mit yum lösen

Aus Laub-Home.de Wiki
Zur Navigation springen Zur Suche springen

Kommt es beim Installieren von Updates zu einem Systemcrash, oder einem Abbruch kann es vorkommen, dass einige Abhängigkeiten nicht mehr funktionieren, dann können die folgenden Befehle eventuell weiterhelfen:

yum install yum-utils
yum-complete-transaction
yum clean metadata
yum clean all
package-cleanup --dupes
package-cleanup --cleandupes
yum check

Beispiel Fehlermeldung:

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 glibc which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of glibc 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 glibc.otherarch ... this should give you an error
            message showing the root cause of the problem.

         2. You have multiple architectures of glibc 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 glibc 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: glibc-2.12-1.132.el6.i686 != glibc-2.12-1.132.el6_5.4.x86_64
Error: Protected multilib versions: glibc-common-2.12-1.132.el6_5.4.x86_64 != glibc-common-2.12-1.132.el6.x86_64
 You could try using --skip-broken to work around the problem
** Found 5 pre-existing rpmdb problem(s), 'yum check' output follows:
glibc-2.12-1.132.el6_5.4.x86_64 is a duplicate with glibc-2.12-1.132.el6.i686
glibc-common-2.12-1.132.el6_5.4.x86_64 is a duplicate with glibc-common-2.12-1.132.el6.x86_64
kernel-firmware-2.6.32-431.29.2.el6.noarch is a duplicate with kernel-firmware-2.6.32-431.el6.noarch
nss-softokn-freebl-3.14.3-12.el6_5.i686 is a duplicate with nss-softokn-freebl-3.14.3-9.el6.x86_64
tzdata-2014h-1.el6.noarch is a duplicate with tzdata-2013g-1.el6.noarch