Bug 2320839

Summary: Please branch and build mosh in epel10
Product: [Fedora] Fedora EPEL Reporter: Romain Geissler <romain.geissler>
Component: moshAssignee: Michel Lind <michel>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel10CC: achernya, michel, pasik, romain.geissler
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mosh-1.4.0-7.el10_0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-12 03:47:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1914423    

Description Romain Geissler 2024-10-22 01:39:43 UTC
Please branch and build mosh in epel10.

Comment 1 Michel Lind 2024-11-05 17:24:54 UTC
*** Bug 2323773 has been marked as a duplicate of this bug. ***

Comment 2 Michel Lind 2024-11-05 17:26:40 UTC
Will you be able to branch and build mosh in epel10?
The EPEL Packagers SIG would be happy to be a co-maintainer
if you do not wish to build it on epel10.

Please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/mosh/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: salimma).

Comment 3 Michel Lind 2024-11-11 16:52:50 UTC
Asking releng for access - https://pagure.io/releng/issue/12450

Comment 4 Fedora Update System 2024-11-11 23:23:25 UTC
FEDORA-EPEL-2024-6e017a7ba6 (mosh-1.4.0-7.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-6e017a7ba6

Comment 5 Fedora Update System 2024-11-12 03:47:27 UTC
FEDORA-EPEL-2024-6e017a7ba6 (mosh-1.4.0-7.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.