Bug 2380825 - Please branch and build python-netifaces in epel10.0 [NEEDINFO]
Summary: Please branch and build python-netifaces in epel10.0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: python-netifaces
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rafael Jeffman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPELPackagersSIG
TreeView+ depends on / blocked
 
Reported: 2025-07-16 11:18 UTC by Jonathan Wright
Modified: 2025-11-24 20:57 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-11-24 20:57:33 UTC
Type: ---
Embargoed:
rjeffman: needinfo? (jonathan)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-12447 0 None None None 2025-07-16 11:21:41 UTC

Description Jonathan Wright 2025-07-16 11:18:55 UTC
Please branch and build python-netifaces in epel10.0.

If you do not wish to maintain python-netifaces in epel10.0,
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 (FAS: jonathanspw);
please add me through https://src.fedoraproject.org/rpms/python-netifaces/adduser

Comment 1 Rafael Jeffman 2025-07-22 14:05:45 UTC
@jonathan the upstream project for python-netifaces has been archived and is unmaintained since June 2021.

We can branch in for epel10.0, but I wonder if this is the best move, or should we simply point users to still maintained alternatives, like python-ifaddr.

Let me know if python-ifaddr (or any alternative) works for you, or if we should continue with the build for epel.

Comment 2 Rafael Jeffman 2025-09-26 19:04:38 UTC
python-netifaces will not be maintained in the future in Fedora, as it is not maintained in upstream anymore.

I strongly suggest you migrate to pyhton-ifaddr.

Comment 3 Rafael Jeffman 2025-11-24 20:57:33 UTC
As there has been no response, and as python-netifaces is not maintained in upstream anymore, I'm closing this issue.

If you believe there is another approach that should be done, please reopen with the proper reasons.


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