Description of problem: Aforementioned package is not there anymore. Version-Release number of selected component (if applicable): Two days ago it was: 2021-09-01T15:34:57.376098867Z python2-qpid-proton x86_64 0.34.0-2.el7 epel 333 k How reproducible: Always Steps to Reproduce: 1. Try to install the package. Actual results: It's not there. Expected results: It's there like it was 2 days ago: 2021-09-01T15:34:57.376098867Z python2-qpid-proton x86_64 0.34.0-2.el7 epel 333 k Additional info:
Upstream is no longer supporting python2, we can't provide this sub-package.
python2-qpid-proton is required by python2-pyngus, which is required during Openstack installation. centos-openstack-train repo provide an outdated one, and can't meet requirement of python2-pyngus of current version in epel. To prevent breaking Openstack installation, please consider to provide it again. ... Error: Package: python2-pyngus-2.3.0-1.el7.noarch (epel) Requires: python2-qpid-proton >= 0.28.0 Available: python2-qpid-proton-0.26.0-2.el7.x86_64 (centos-openstack-train) python2-qpid-proton = 0.26.0-2.el7 ...
Yep, I encountered this during OpenStack installation too.
It seems that: 1) Although EPEL main repo no longer provide it, an old version of python2-qpid-proton can be installed from EPEL archive(https://archives.fedoraproject.org/pub/archive/epel/) 2) RDO don't reqire EPEL to install, my installation goes smoothly on a clean CentOS without EPEL. IMO python2-pyngus dependency failure at main repo still should be fixed though.
Upstream is no longer supporting python 2, and we cannot build python2-qpid-proton. I made it available in copr: https://copr.fedorainfracloud.org/coprs/g/qpid/qpid/build/2783962/ And we will remove python2-pyngus from EPEL 7 as well. The only other way to continue distributing both packages in EPEL 7 is to remove recent update to 0.35.0 and stop updating it for newer releases. Is this what you want?
And if copr distribution works for you, I can add python2-pyngus to copr as well. Please let me know. @
*** Bug 1710668 has been marked as a duplicate of this bug. ***