0 votes

i'm getting the error during yum update

---> Package clearsdn-intrusion-protection.noarch 0:6.1-20191115.1613 will be updated
---> Package clearsdn-intrusion-protection.noarch 0:6.1-20191129.0954 will be an update
---> Package distribution-gpg-keys.noarch 0:1.34-1.el7 will be updated
---> Package distribution-gpg-keys.noarch 0:1.35-1.el7 will be an update
---> Package mock.noarch 0:1.4.19-1.el7 will be updated
---> Package mock.noarch 0:1.4.21-1.el7 will be an update
---> Package mock-core-configs.noarch 0:31.2-1.el7 will be updated
---> Package mock-core-configs.noarch 0:31.7-1.el7 will be an update
---> Package python36-rpm.x86_64 0:4.11.3-4.el7 will be updated
---> Package python36-rpm.x86_64 0:4.11.3-7.el7 will be an update
--> Processing Dependency: rpm >= 4.11.3-40 for package: python36-rpm-4.11.3-7.el7.x86_64
--> Finished Dependency Resolution
Error: Package: python36-rpm-4.11.3-7.el7.x86_64 (clearos-epel-verified)
Requires: rpm >= 4.11.3-40
Installed: rpm-4.11.3-35.el7.x86_64 (@clearos-centos-verified)
rpm = 4.11.3-35.el7
You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
python-sleekxmpp-1.1.11-9.2.noarch has missing requires of python-dnspython

Both are from the verified repos, but looks like a version difference
Saturday, November 30 2019, 08:16 AM
Share this post:
Responses (1)
  • Accepted Answer

    Saturday, November 30 2019, 08:50 AM - #Permalink
    0 votes
    Yes I was fearing that was going to happen some time.The cause is because Epel updates are still being pushed, but Home/Business is still not at 7.7 so we've hit a version mismatch. I'll ping a message over but don't expect a response until next week. It is the intention to release 7.7 Home/Business on Tuesday and I would hope this would fix it. If not, they'll need to look at rolling back last weeks clearos-epel-verified update.
    The reply is currently minimized Show
Your Reply