Description of problem: Upgrading to koji-builder-1.10.1-8.el7 fails because yum can't satisfy a dependency of python-multilib. Version-Release number of selected component (if applicable): koji-builder-1.10.1-8.el7 How reproducible: Always Steps to Reproduce: 1. yum update Actual results: # yum update Loaded plugins: auto-update-debuginfo, fastestmirror, langpacks, refresh-packagekit, versionlock Loading mirror speeds from cached hostfile * base: mirror.nonstop.co.il * epel: mirror.nonstop.co.il * extras: mirror.nonstop.co.il * updates: mirror.nonstop.co.il Resolving Dependencies --> Running transaction check ---> Package koji.noarch 0:1.10.1-3.el7 will be updated ---> Package koji.noarch 0:1.10.1-8.el7 will be an update ---> Package koji-builder.noarch 0:1.10.1-3.el7 will be updated ---> Package koji-builder.noarch 0:1.10.1-8.el7 will be an update --> Processing Dependency: python2-multilib for package: koji-builder-1.10.1-8.el7.noarch ---> Package koji-hub.noarch 0:1.10.1-3.el7 will be updated ---> Package koji-hub.noarch 0:1.10.1-8.el7 will be an update ---> Package koji-hub-plugins.noarch 0:1.10.1-3.el7 will be updated ---> Package koji-hub-plugins.noarch 0:1.10.1-8.el7 will be an update ---> Package koji-utils.noarch 0:1.10.1-3.el7 will be updated ---> Package koji-utils.noarch 0:1.10.1-8.el7 will be an update ---> Package koji-vm.noarch 0:1.10.1-3.el7 will be updated ---> Package koji-vm.noarch 0:1.10.1-8.el7 will be an update ---> Package koji-web.noarch 0:1.10.1-3.el7 will be updated ---> Package koji-web.noarch 0:1.10.1-8.el7 will be an update --> Finished Dependency Resolution Error: Package: koji-builder-1.10.1-8.el7.noarch (epel) Requires: python2-multilib You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Expected results: The usual yum song Additional info:
It's been a month. It's still broken. What has to be done (who has to be killed?) to fix this?
This requirement is from a change that hasn't landed upstream yet.
*** This bug has been marked as a duplicate of bug 1340704 ***