Please branch and build python-executing in epel9. If you do not wish to maintain python-executing in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/python-executing/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: salimma), and can be the primary contact for EPEL.
Proper build with tests requires pytest, but it's not present in epel9. Is it possible to get it first?
pytest is available in Centos 9 stream CRB repo: # dnf --enablerepo=crb repoquery --info python3-pytest Last metadata expiration check: 0:00:11 ago on Fri Feb 4 16:25:30 2022. Name : python3-pytest Version : 6.2.2 Release : 4.el9 Architecture : noarch Size : 521 k Source : pytest-6.2.2-4.el9.src.rpm Repository : crb Summary : Simple powerful testing with Python URL : https://pytest.org License : MIT Description : The pytest framework makes it easy to write small tests, yet scales to support : complex functional testing for applications and libraries.
Thanks, but I still cannot figure it out. I've sent a question to the mailing list: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/CU3LZJZBROYIX6ZBTMDOD3C3E6S34PLK/
I've added epel-packagers-sig group, since I cannot get it work (see the thread above).
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
Thanks Roman! python-executing on rawhide ❯ fedpkg request-branch epel9 https://pagure.io/releng/fedora-scm-requests/issue/46249 Tried building it locally, also needs asttokens so I'm making this depends on that bug
FEDORA-EPEL-2022-f01784bd99 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f01784bd99
FEDORA-EPEL-2022-f01784bd99 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.