Bug 2033140 - Please branch and build python-execnet in epel9
Summary: Please branch and build python-execnet in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-execnet
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2034654 2040826
Blocks: 2032588
TreeView+ depends on / blocked
 
Reported: 2021-12-16 02:32 UTC by Scott Talbert
Modified: 2022-06-02 01:51 UTC (History)
7 users (show)

Fixed In Version: python-execnet-1.9.0-3.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-02 01:51:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Scott Talbert 2021-12-16 02:32:54 UTC
Please branch and build python-execnet in epel9.

If you do not wish to maintain python-execnet in epel9,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package.

Comment 1 Parag Nemade 2022-05-16 02:54:13 UTC
Can this package be built now for epel9?

Comment 2 Ken Dreyer 2022-05-18 14:08:54 UTC
There was a discussion about execnet in EPEL 9 a while ago on the epel-devel list. My conclusion was https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/FYY3C2E2I56TJ2N6AZSA2HEWMVRA6RMT/

Execnet is essentially abandoned upstream (see the warning on the upstream page, https://execnet.readthedocs.io/en/latest/). This is one of the reasons we're shifting away from execnet in Ceph. I don't think it's a good idea to put execnet into EPEL 9.

Can you remove pytest-xdist from your packages instead?

Comment 3 Thomas Moschny 2022-05-18 14:57:43 UTC
Given that it builds and installs, and we have the branch already, I'm inclined to build execnet anyway, knowing that it is in very low maintenance mode upstream-wise. But then, I hope c9 is not moving that fast either. After all, it _is_ possible to retire packages from epel later, if we think it cannot be maintained any longer.

Comment 4 Maxwell G 2022-05-22 02:08:42 UTC
(In reply to Thomas Moschny from comment #3)
> Given that it builds and installs, and we have the branch already, I'm
> inclined to build execnet anyway, knowing that it is in very low maintenance
> mode upstream-wise. But then, I hope c9 is not moving that fast either.
> After all, it _is_ possible to retire packages from epel later, if we think
> it cannot be maintained any longer.

+1. This is the only remaining blocker to branch and build python-pytest-xdist for epel9.

Comment 5 Fedora Update System 2022-05-24 11:10:56 UTC
FEDORA-EPEL-2022-f2b65f4dce has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f2b65f4dce

Comment 6 Fedora Update System 2022-05-25 02:08:17 UTC
FEDORA-EPEL-2022-f2b65f4dce has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f2b65f4dce

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-06-02 01:51:45 UTC
FEDORA-EPEL-2022-f2b65f4dce has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.