Description of problem: python3-certbot-nginx requires python3.6dist(pyparsing) which is not provided in RHEL 8 Version-Release number of selected component (if applicable): python3-certbot-nginx-1.12.0-1.el8.noarch How reproducible: Always reproducible. Steps to Reproduce: 1. execute the following command on RHEL8 with EPEL8 repository enabled # dnf install python3-certbot-nginx Actual results: The packages cannot be installed/upgraded. The output of dnf is: Updating Subscription Management repositories. Last metadata expiration check: 0:14:03 ago on Mon Feb 22 06:39:31 2021. Package python3-certbot-nginx-1.11.0-1.el8.noarch is already installed. Error: Problem: cannot install the best candidate for the job - nothing provides python3.6dist(pyparsing) >= 2.2.0 needed by python3-certbot-nginx-1.12.0-1.el8.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Expected results: Package python3-certbot-nginx should be installed successfully. Additional info: certbot-nginx 1.12.0 requires pyparsing>=2.2.0. Please see the link: https://github.com/certbot/certbot/blob/v1.12.0/certbot-nginx/setup.py
My workaround is to add patch for epel to lower the requirements of pyparsing version. It seems that mock for epel-8 can also pass the packaging procedure, too https://gist.github.com/holishing/cde18be7fde099364ab1c4dc4acf92bd Please help to check if it is proper to add this patch or there's better way (e.g. upgrade pyparsing to 2.2.0 for epel 8/7) to solve it, thanks! I don't know about semantic release number and the version naming rule here, please also change version number to proper one (e.g. "1.12.0-2.el8") for EPEL project:p
I am facing this issue, and I don't seem to be able to install an older working version - is this possible? Currently CD is broken for us
(In reply to holishing from comment #1) > My workaround is to add patch for epel to lower the requirements of > pyparsing version. > It seems that mock for epel-8 can also pass the packaging procedure, too > https://gist.github.com/holishing/cde18be7fde099364ab1c4dc4acf92bd > > Please help to check if it is proper to add this patch or there's better way > (e.g. upgrade pyparsing to 2.2.0 for epel 8/7) to solve it, thanks! > I don't know about semantic release number and the version naming rule here, > please also change version number to proper one (e.g. "1.12.0-2.el8") for > EPEL project:p You are right @holishing, this must be resolved asap as you propose.
Sorry folks, seems like the updated version requirement slipped through and Fedora's update system does not prevent maintainers from shipping broken RPMs... :-/ holishing: I think you were on the right track and just lowering the version requirement is the right fix. I rebuilt the RPM and all tests still pass so I guess it should be fine. Unless I hit some last-minute problems I'll trigger a new build in a few minutes. > I am facing this issue, and I don't seem to be able to install an older working version - is this possible? Currently CD is broken for us Unfortunately EPEL does not keep older versions available in the main repos but you can find the older RPMs in the archive: https://archives.fedoraproject.org/pub/archive/epel/ It is a bit of a hassle downloading these manually but it might be help to work around issues quickly. Here is what you can to do prevent such an issue in the future: - use epel-testing at least on one machine and leave feedback via https://bodhi.fedoraproject.org/updates/
FEDORA-EPEL-2021-4c2bba15fa has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4c2bba15fa
The updated package should be available via epel-testing in a few hours. Please test this and leave karma in bodhi so other users can benefit from the update as soon as possible (otherwise everyone will have to wait 14 days).
FEDORA-EPEL-2021-4c2bba15fa has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4c2bba15fa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 1933482 has been marked as a duplicate of this bug. ***
FEDORA-EPEL-2021-4c2bba15fa has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.