I'm hoping someone can point me to what is wrong here, I can't figure it out.
running "yum update" on my C7.6 box I get:
Resolving Dependencies --> Running transaction check ---> Package glibc-debuginfo.x86_64 0:2.17-260.el7_6.4 will be updated ---> Package glibc-debuginfo.x86_64 0:2.17-260.el7_6.5 will be an update ---> Package glibc-debuginfo-common.x86_64 0:2.17-260.el7_6.4 will be updated ---> Package glibc-debuginfo-common.x86_64 0:2.17-260.el7_6.5 will be an update ---> Package google-chrome-stable.x86_64 0:74.0.3729.157-1 will be updated ---> Package google-chrome-stable.x86_64 0:74.0.3729.169-1 will be an update ---> Package kmod-nvidia.x86_64 0:418.74-1.el7_6.elrepo will be updated ---> Package kmod-nvidia.x86_64 0:430.14-1.el7_6.elrepo will be an update ---> Package libgpg-error.x86_64 0:1.12-3.el7 will be updated ---> Package libgpg-error.x86_64 0:1.13-1.el7.centos will be an update ---> Package libgpg-error-debuginfo.x86_64 0:1.12-3.el7 will be updated ---> Package libgpg-error-debuginfo.x86_64 0:1.13-1.el7.centos will be an update ---> Package libgpg-error-devel.x86_64 0:1.12-3.el7 will be updated ---> Package libgpg-error-devel.x86_64 0:1.13-1.el7.centos will be an update ---> Package mkvtoolnix.x86_64 0:33.1.0-1 will be updated ---> Package mkvtoolnix.x86_64 0:34.0.0-1 will be an update ---> Package nvidia-x11-drv.x86_64 0:418.74-1.el7_6.elrepo will be updated ---> Package nvidia-x11-drv.x86_64 0:430.14-1.el7_6.elrepo will be an update ---> Package nvidia-x11-drv-libs.i686 0:418.74-1.el7_6.elrepo will be updated ---> Package nvidia-x11-drv-libs.x86_64 0:418.74-1.el7_6.elrepo will be updated ---> Package nvidia-x11-drv-libs.i686 0:430.14-1.el7_6.elrepo will be an update ---> Package nvidia-x11-drv-libs.x86_64 0:430.14-1.el7_6.elrepo will be an update ---> Package systemd-debuginfo.x86_64 0:219-62.el7_6.6 will be updated ---> Package systemd-debuginfo.x86_64 0:219-62.el7_6.6.0.1 will be an update ---> Package vivaldi-stable.x86_64 0:2.5.1525.43-1 will be updated ---> Package vivaldi-stable.x86_64 0:2.5.1525.46-1 will be an update ---> Package wget.x86_64 0:1.14-18.el7 will be updated ---> Package wget.x86_64 0:1.14-18.el7_6.1 will be an update --> Finished Dependency Resolution 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 libgpg-error which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libgpg-error 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 libgpg-error.otherarch ... this should give you an error message showing the root cause of the problem.
2. You have multiple architectures of libgpg-error 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 libgpg-error 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: libgpg-error-1.13-1.el7.centos.x86_64 != libgpg-error-1.12-3.el7.i686
I don't know what it's complaining about, I have several i686 packages installed that yum thinks need the libgpg-error package. here's all the libgpg stuff installed:
libgpg-error.i686 1.12-3.el7 @base libgpg-error.x86_64 1.12-3.el7 @anaconda libgpg-error-debuginfo.x86_64 1.12-3.el7 @base-debuginfo libgpg-error-devel.x86_64 1.12-3.el7 @base
When I encountered this a couple weeks ago I finally excluded libgpg from the updates, hoping there was some mirror problem that would go away, but apparently not.
I can't see any reason why having both i686 and x86_64 is a problem, I'm hoping someone here can enlighten me.
thanks in advance!
Fred
On 27/05/2019 12:26 pm, Fred Smith wrote:
I'm hoping someone can point me to what is wrong here, I can't figure it out.
running "yum update" on my C7.6 box I get:
Resolving Dependencies --> Running transaction check -On 27/05/2019 12:26 pm, Fred Smith wrote: I'm hoping someone can point me to what is wrong here, I can't figure it out.
running "yum update" on my C7.6 box I get:
---> Package libgpg-error.x86_64 0:1.12-3.el7 will be updated ---> Package libgpg-error.x86_64 0:1.13-1.el7.centos will be an update ---> Package libgpg-error-debuginfo.x86_64 0:1.12-3.el7 will be updated ---> Package libgpg-error-debuginfo.x86_64 0:1.13-1.el7.centos will be an update ---> Package libgpg-error-devel.x86_64 0:1.12-3.el7 will be updated ---> Package libgpg-error-devel.x86_64 0:1.13-1.el7.centos will be an update
The update for libgpg-error.i686 1.13-1 seems to be missing
On Mon, 2019-05-27 at 14:05 +1000, Bill Maidment wrote:
---> Package libgpg-error.x86_64 0:1.13-1.el7.centos will be an update ---> Package libgpg-error-debuginfo.x86_64 0:1.13-1.el7.centos will be an update ---> Package libgpg-error-devel.x86_64 0:1.13-1.el7.centos will be an update
The update for libgpg-error.i686 1.13-1 seems to be missing
Where are the libgpg-error 1.13-1.el7.centos packages coming from? They're not in CentOS updates (or RHEL updates either).
On Tue, May 28, 2019 at 02:14:42AM +0000, Ian Mortimer wrote:
On Mon, 2019-05-27 at 14:05 +1000, Bill Maidment wrote:
---> Package libgpg-error.x86_64 0:1.13-1.el7.centos will be an update ---> Package libgpg-error-debuginfo.x86_64 0:1.13-1.el7.centos will be an update ---> Package libgpg-error-devel.x86_64 0:1.13-1.el7.centos will be an update
The update for libgpg-error.i686 1.13-1 seems to be missing
Where are the libgpg-error 1.13-1.el7.centos packages coming from? They're not in CentOS updates (or RHEL updates either).
bugzy-keepassxc
and disabling it solves the problem.
I'm using the priority plugin, so apparently I didn't choose a correct value for the bugzy repopriority. If I have more troubles, in the future, from having disabled it, I'll do a closer study of the priorities.
thanks for the rap on the head!
Fred