Bug 2047407 - Please branch and build isl in epel9
Summary: Please branch and build isl in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: isl
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Davide Cavalca
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPELPackagersSIG
TreeView+ depends on / blocked
 
Reported: 2022-01-27 19:03 UTC by Davide Cavalca
Modified: 2022-04-13 16:13 UTC (History)
4 users (show)

Fixed In Version: isl-0.16.1-15.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-13 16:13:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Davide Cavalca 2022-01-27 19:03:59 UTC 
Please branch and build isl in epel9.

If you do not wish to maintain isl in epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packaging SIG would be happy to be a co-maintainer of the package.
Comment 1 Davide Cavalca 2022-02-08 18:28:06 UTC 
Will you be able to branch and build isl in epel9?
The EPEL Packagers SIG would be happy to be a co-maintainer
if you do not wish to build it on epel9.
Comment 2 Davide Cavalca 2022-02-17 17:44:13 UTC 
Filed stalled package ticket: https://pagure.io/releng/issue/10652
Comment 3 Davide Cavalca 2022-02-21 16:39:17 UTC 
$ fedpkg request-branch epel9
https://pagure.io/releng/fedora-scm-requests/issue/42473
Comment 4 Fedora Update System 2022-04-05 01:22:39 UTC 
FEDORA-EPEL-2022-3a685e3091 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-3a685e3091

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2022-04-13 16:13:36 UTC 
FEDORA-EPEL-2022-3a685e3091 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.