Bug 2165165 - Please branch and build libserialport in epel9
Summary: Please branch and build libserialport in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libserialport
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alex G.
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-28 00:25 UTC by Neil Hanlon
Modified: 2023-02-06 01:00 UTC (History)
2 users (show)

Fixed In Version: libserialport-0.1.1-1.el9
Clone Of:
Environment:
Last Closed: 2023-02-06 01:00:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Neil Hanlon 2023-01-28 00:25:07 UTC 
Please branch and build libserialport in epel9.

If you do not wish to maintain libserialport 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 neil);
please add me through https://src.fedoraproject.org/rpms/libserialport/adduser
Comment 1 Dan Horák 2023-01-28 20:08:48 UTC 
Bbranch requested in https://pagure.io/releng/fedora-scm-requests/issue/50773 and I am going to add you as a co-maintainer, help with EPEL is always useful.
Comment 2 Fedora Update System 2023-01-28 20:56:23 UTC 
FEDORA-EPEL-2023-6b144aafc4 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6b144aafc4
Comment 3 Fedora Update System 2023-01-29 00:22:12 UTC 
FEDORA-EPEL-2023-6b144aafc4 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-2023-6b144aafc4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2023-02-06 01:00:28 UTC 
FEDORA-EPEL-2023-6b144aafc4 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.