releng

#11630 Unretire/unorphan libffi3.1 as EPEL-only package?
Closed: Fixed by humaton. Opened by jonathanspw.

Closed: Fixed
Reopen Issue
  • Describe the issue

I'd like to unretire and take ownership of https://src.fedoraproject.org/rpms/libffi3.1 to be maintained as an EPEL-only package specifically in EPEL9. I'm not totally sure how to go about this...is it just a matter of getting ownership of the package and only doing builds in the EPEL9 branch and ignoring the FTBFS errors on the Fedora branches?

I tried to "take" the package but was met with "Unable to change the point of contact: This project has been retired and cannot be unorphaned here, please open a releng ticket for it." but perhaps that's just because it's been orphaned for 16 days and IIRC the cutoff for "take" is at 14 days?

  • If we cannot complete your request, what is the impact?

libffi3.1 will not exist in EPEL9 which some software needs to run on EL9. We'll probably package it in AlmaLinux directly if I can't do it in EPEL, but EPEL will help more than just AlmaLinux users so I'd prefer to do it in EPEL.

Hi,

so the package is retired which means it was orphaned for some time. In the time when the package is in an orphaned state, you could just "take" it with that button.

If you are only interested in epel branches it needs to stay retired on f* rawhide and main branches.

I am making you the owner of the epel side of things, it will take a few hours to propagate to BZ. By tomorrow you should be able to request epel branches for the package.

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Note that not having a build in Fedora means we cannot track it in ELN properly. You may want to consider shipping it in Fedora too.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.