On a server I don't use very often, I am trying to update
mock-core-configs with yum and I am seeing:
Resolving Dependencies
--> Running transaction check
---> Package mock-core-configs.noarch 0:36.9-1.el7 will be
updated
---> Package mock-core-configs.noarch 0:36.13-1.el7 will be an
update
--> Processing Dependency: distribution-gpg-keys >= 1.77 for
package: mock-core-configs-36.13-1.el7.noarch
--> Finished Dependency Resolution
Error: Package: mock-core-configs-36.13-1.el7.noarch
(epel-unverified)
Requires: distribution-gpg-keys >= 1.77
Installed: distribution-gpg-keys-1.75-1.el7.noarch
(@epel-unverified)
distribution-gpg-keys = 1.75-1.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
On another server I regularly use and update I have
distribution-gpg-keys-1.77-1.el7.noarch which I updated to a while
back, so it appears that the updated package has been removed?
Obviously this then breaks updating mock-core-configs. If
distribution-gpg-keys-1.77-1.el7.noarch was a bad release, perhaps
1.75 should be bumped to a later version so it gets installed over
1.77 rather than just removing the package?
Hi Nick,
Looking at the koji history, 1.77 never was untagged, but 1.75 was tagged in on Oct. 10th. Koji and the repo's only show what was the last tagged in.
I'm not sure why 1.75 was tagged in.
distribution-gpg-keys-1.78-1.el7 is currently in testing.
You can get things moving my using the epel-testing repo
yum --enablerepo=epel-testing update mock-core-configs
If it works for you (it works for me) give the update some karma so it will go out quicker.
Troy