Bug 2044771 - Please build RCS for EPEL9
Summary: Please build RCS for EPEL9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rcs
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matej Mužila
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-25 07:37 UTC by Steve Traylen
Modified: 2022-03-13 18:39 UTC (History)
4 users (show)

Fixed In Version: rcs-5.10.1-1.el9
Clone Of:
Environment:
Last Closed: 2022-03-13 18:39:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Steve Traylen 2022-01-25 07:37:58 UTC 
Hi

Please can an EPEL9 version of rcs be branched and released.

Many Thanks

Steve.
Comment 1 Christoph Karl 2022-02-22 16:17:53 UTC 
Hello Matej!

Would it be OK if I try to do this?
(Branching and releasing for EPEL9.)

Thank you

Best Regards
Christoph
Comment 2 Matej Mužila 2022-02-24 12:34:55 UTC 
(In reply to Christoph Karl from comment #1)
> Hello Matej!
> 
> Would it be OK if I try to do this?
> (Branching and releasing for EPEL9.)
> 
> Thank you
> 
> Best Regards
> Christoph

Hi,

feel free to request the epel9 branch and release the package.
Comment 3 Fedora Update System 2022-03-03 18:46:09 UTC 
FEDORA-EPEL-2022-d60b9cd491 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d60b9cd491
Comment 4 Fedora Update System 2022-03-04 17:00:02 UTC 
FEDORA-EPEL-2022-d60b9cd491 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-d60b9cd491

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2022-03-13 18:39:28 UTC 
FEDORA-EPEL-2022-d60b9cd491 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.