Description of problem: Running a routine "yum update" this morning on a RHEL6 machine, I get ---> Package fedora-cert.noarch 0:0.5.10.7-1.el6 will be updated ---> Package fedora-cert.noarch 0:0.6.0.0-1.el6 will be an update ---> Package fedora-packager.noarch 0:0.5.10.7-1.el6 will be updated ---> Package fedora-packager.noarch 0:0.6.0.0-1.el6 will be an update --> Processing Dependency: krb5-workstation >= 1.14.3-4 for package: fedora-packager-0.6.0.0-1.el6.noarch --> Processing Dependency: python-yubico for package: fedora-packager-0.6.0.0-1.el6.noarch ---> Package fedpkg.noarch 0:1.24-3.el6 will be updated ---> Package fedpkg.noarch 0:1.26-4.el6 will be an update ... Error: Package: fedora-packager-0.6.0.0-1.el6.noarch (epel) Requires: python-yubico Error: Package: fedora-packager-0.6.0.0-1.el6.noarch (epel) Requires: krb5-workstation >= 1.14.3-4 Installed: krb5-workstation-1.10.3-57.el6.x86_64 (@rhel-6-workstation-rpms) Version-Release number of selected component (if applicable): fedora-packager-0.5.10.7-1.el6.noarch is the installed version How reproducible: Probably 100%, but I didn't actually try to repeat it Steps to Reproduce: 1. sudo yum update Actual results: fail Expected results: success Additional info:
fedora-packager-0.6.0.1-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-3cc24b7566
fedora-packager-0.6.0.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
As of Jan 10, the required bits ( as described in https://bugzilla.redhat.com/show_bug.cgi?id=1411027#c0 ) are in epel-testing, not in epel-stable.
fedora-packager-0.6.0.1-1.el6.noarch is still broken: --> Finished Dependency Resolution Error: Package: fedora-packager-0.6.0.1-1.el6.noarch (epel) Requires: python-yubico You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
As of this morning, "yum update" succeeds --- looks like python-yubico is now available in epel 6. So this is fixed, thanks.