Hello EPEL people, apparently, all EPEL 8 Python 3.8 and 3.9 packages that should only provide python3.8dist(...)/python3.9dist(...) also provide python3dist(...).
That means, any Python 3.6 package that BuildRequires python3dist(...) might get a Python 3.8/3.9 package instead.
This has been fixed via https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/47 (and accidentally pushed without epel-rpm-macros maintainers ack).
I propose that we ship the fix and rebuild all affected packages. That would be:
$ repoquery --repo=epel8{,-testing} --whatprovides 'python3.8dist(*)' --whatprovides 'python3.9dist(*)' --source | pkgname | sort | uniq
ansible lutris python38-click-epel python38-dateutil-epel python38-freezegun-epel python38-hvac python38-hypothesis-epel python38-itsdangerous-epel python38-jmespath python38-jsonschema-epel python38-netaddr-epel python38-ntlm-auth-epel python38-pynetbox python38-pyrsistent-epel python38-pytest-runner-epel python38-requests_ntlm-epel python38-setuptools_scm-epel python38-textfsm-epel python38-toml-epel python38-winrm-epel python38-xmltodict-epel python39-click-epel radicale
+ new packages that have not yet reached the either EPEL 8 repo + probably the same query in EPEL 8 next, but I miss a repo file for it ATM
On 22/07/19 07:00PM, Miro Hrončok wrote:
I propose that we ship the fix and rebuild all affected packages.
I agree. This issue has the potential to result in confusing, hard to debug issues for packagers (mainly) but also users.
- new packages that have not yet reached the either EPEL 8 repo
I checked Bodhi and there are no python38-* or python39-* packages in epel8{,-next} pending or in testing.
- probably the same query in EPEL 8 next, but I miss a repo file for it ATM
sudo dnf repoquery --repo=epel-next{,-testing} --whatprovides 'python3.8dist(*)' --whatprovides 'python3.9dist(*)' --qf='%{source_name}' --latest-limit 1 ansible
ansible is in both epel8 and epel8-next, as there's a newer version in epel8-next to correspond to the newer ansible-core in c8s. To whoever ends up rebuilding the packages: please let me to handle that package. I have an update for it in testing that needs to be synced with some upcoming updates in c8s in order to avoid an FTI, and I don't want the karma to be reset.
I'm already handling the go rebuild, but I wouldn't mind handling this one as well.
On 22/07/19 07:00PM, Miro Hrončok wrote:
apparently, all EPEL 8 Python 3.8 and 3.9 packages that should only provide python3.8dist(...)/python3.9dist(...) also provide python3dist(...).
That means, any Python 3.6 package that BuildRequires python3dist(...) might get a Python 3.8/3.9 package instead.
This has been fixed via https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/47 (and accidentally pushed without epel-rpm-macros maintainers ack).
I propose that we ship the fix and rebuild all affected packages.
We discussed this issue in the EPEL SCo meeting, and I volunteered to handle it.
I built the fixed epel-rpm-macros and submitted a Bodhi update[0] and a buildroot override. I also rebuilt the affected packages and submitted [1]. I would appreciate testing and karma!
[0]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5e2dae8961 [1]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-781937ed73
Out of all of the packages, only python38-itsdangerous-epel FTBFS, and I filed [2] for that one.
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=2109363
epel-devel@lists.fedoraproject.org
-
Maxwell G -
Miro Hrončok