Description of problem:
# LANG=C dnf upgrade
Last metadata expiration check: 0:08:02 ago on Mon May 16 10:39:29 2022.
Problem: package ocrmypdf-13.4.2-2.fc36.noarch requires ((python3.10dist(pdfminer-six) < 20200720 or python3.10dist(pdfminer-six) > 20200720) with python3.10dist(pdfminer-six) <= 20220319 with python3.10dist(pdfminer-six) >= 20191110), but none of the providers can be installed
- cannot install both python3-pdfminer-20220506-1.fc36.noarch and python3-pdfminer-20220319-1.fc36.noarch
- cannot install the best update candidate for package python3-pdfminer-20220319-1.fc36.noarch
- cannot install the best update candidate for package ocrmypdf-13.4.2-2.fc36.noarch
Package Architecture Version Repository Size
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
python3-pdfminer noarch 20220506-1.fc36 updates 5.4 M
Skip 1 Package
Nothing to do.
FEDORA-2022-7089937b45 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7089937b45
Thanks! Sorry about that—I normally check for version-pinning issues like this before updating a Python library, but it looks like I missed it this time.
FEDORA-2022-7089937b45 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-7089937b45`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7089937b45
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
(In reply to Ben Beasley from comment #2)
> Thanks! Sorry about that—I normally check for version-pinning issues like
> this before updating a Python library, but it looks like I missed it this
You're welcome Ben, but really, thanks to you!
FEDORA-2022-7089937b45 works and solves the issue.
FEDORA-2022-7089937b45 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.