Bug 2034334 - Please branch and build rxvt-unicode in epel9
Summary: Please branch and build rxvt-unicode in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rxvt-unicode
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robbie Harwood
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2034331 2034332
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-20 17:43 UTC by Peter Georg
Modified: 2022-01-13 01:44 UTC (History)
4 users (show)

Fixed In Version: rxvt-unicode-9.30-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-13 01:44:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Peter Georg 2021-12-20 17:43:44 UTC
Please branch and build rxvt-unicode in epel9.

If you do not wish to maintain rxvt-unicode in epel9,
I would be happy to be a co-maintainer of the package.

I have tested and the rawhide package is currently missing two dependencies on CentOS Stream 9 (signify and libptytty). Adding these missing dependencies the rawhide package builds without any changes.

Note: The package also depends on libev-source which is already in epel9.

Comment 1 Fedora Update System 2022-01-04 19:58:56 UTC
FEDORA-EPEL-2022-71a7a38ff4 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-71a7a38ff4

Comment 2 Fedora Update System 2022-01-05 02:15:51 UTC
FEDORA-EPEL-2022-71a7a38ff4 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-71a7a38ff4

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

Comment 3 Fedora Update System 2022-01-13 01:44:24 UTC
FEDORA-EPEL-2022-71a7a38ff4 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.