Bug 2103769 - Please build fortune-mod for EPEL 9
Summary: Please build fortune-mod for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: fortune-mod
Version: epel9
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jeff Sheltren
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPEL9MATE
TreeView+ depends on / blocked
 
Reported: 2022-07-04 20:03 UTC by Robert Scheck
Modified: 2022-07-14 01:41 UTC (History)
3 users (show)

Fixed In Version: fortune-mod-3.14.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-14 01:41:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2022-07-04 20:03:16 UTC
Please branch and build fortune-mod in epel9.

If you do not wish to maintain fortune-mod 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/fortune-mod/addgroup and grant it commit access, or collaborator access on epel* branches.

Comment 1 Shlomi Fish 2022-07-05 01:09:42 UTC
Access granted!

Comment 2 Fedora Update System 2022-07-05 19:00:44 UTC
FEDORA-EPEL-2022-2918c9d897 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2918c9d897

Comment 3 Fedora Update System 2022-07-06 02:22:58 UTC
FEDORA-EPEL-2022-2918c9d897 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-2918c9d897

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

Comment 4 Fedora Update System 2022-07-14 01:41:41 UTC
FEDORA-EPEL-2022-2918c9d897 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.