Bug 2039819 - Please branch and build perl-Curses for EPEL 9
Summary: Please branch and build perl-Curses for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Curses
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Traylen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-12 13:57 UTC by Paul Howarth
Modified: 2022-02-06 02:15 UTC (History)
2 users (show)

Fixed In Version: perl-Curses-1.38-2.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-06 02:15:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul Howarth 2022-01-12 13:57:16 UTC
Please branch and build perl-Curses in epel9.

If you do not wish to maintain perl-Curses 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 (FAS pghmcfc).

Comment 1 Paul Howarth 2022-01-20 10:51:59 UTC
Will you be able to branch and build perl-Curses in epel9?
I would be happy to be a co-maintainer if you do not wish
to build it on epel9 (FAS pghmcfc).

Comment 2 Fedora Update System 2022-01-28 07:51:21 UTC
FEDORA-EPEL-2022-2bf4b4402d has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2bf4b4402d

Comment 3 Fedora Update System 2022-01-29 06:45:06 UTC
FEDORA-EPEL-2022-2bf4b4402d 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-2bf4b4402d

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

Comment 4 Fedora Update System 2022-02-06 02:15:23 UTC
FEDORA-EPEL-2022-2bf4b4402d 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.