The package has an upper limit for python-cryptography that prevents me to update the package with latest security updates. The version pin is likely coming from upstreams setup.py, requirements.txt, or pyproject.toml. Please remove the version limit and update the package in my side tag for F41, F40, and F39, e.g. fedpkg build --target=f41-build-side-86213 - f41-build-side-86213 - f40-build-side-86215 - f39-build-side-86167 $ dnf repoquery --requires pgadmin4 | grep cryptography Last metadata expiration check: 0:21:33 ago on 2024-03-22T06:26:51 CET. (python3dist(cryptography) >= 41 with python3dist(cryptography) < 41.1) python3dist(cryptography) >= 40 Reproducible: Always
The requirement should already be unpinned in all current releases: $ dnf repoquery --requires pgadmin4 | grep cryptography python3dist(cryptography) >= 41 $ dnf --releasever=40 --disablerepo=* --enablerepo=updates --enablerepo=updates-testing repoquery --requires pgadmin4 | grep cryptography python3dist(cryptography) >= 41 $ dnf --releasever=39 --disablerepo=* --enablerepo=updates --enablerepo=updates-testing repoquery --requires pgadmin4 | grep cryptography python3dist(cryptography) >= 40 $ dnf --releasever=38 --disablerepo=* --enablerepo=updates --enablerepo=updates-testing repoquery --requires pgadmin4 | grep cryptography python3dist(cryptography) >= 3
Excellent! Sorry for the noise. I only checked current release and not updates-testing. I see that you are patching https://src.fedoraproject.org/rpms/pgadmin4/blob/rawhide/f/pgadmin4_requirements.patch . Did you ever find an easier solution? Is automatic removal of upper version bounds something that Fedora's tooling should be able to do?