Bug 2268512 - Please branch and build rust-configparser in epel9
Summary: Please branch and build rust-configparser in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-configparser
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Rust SIG
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-07 22:30 UTC by Dave Sugar
Modified: 2024-03-12 01:28 UTC (History)
2 users (show)

Fixed In Version: rust-configparser-3.0.4-1.el9
Clone Of:
Environment:
Last Closed: 2024-03-12 01:28:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Sugar 2024-03-07 22:30:48 UTC
Please branch and build rust-configparser in epel9.

Reproducible: Always

Comment 1 Fabio Valentini 2024-03-09 10:25:12 UTC
I'm building it right now.

Out of curiosity, what do you need this for on EPEL9?

Comment 2 Fedora Update System 2024-03-09 11:24:11 UTC
FEDORA-EPEL-2024-2361108412 (rust-configparser-3.0.4-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-2361108412

Comment 3 Dave Sugar 2024-03-09 23:20:59 UTC
Migrating some stuff to RHEL9 that happens to use rust configparser.  It was suggested that since this is in Fedora and it's dependencies are already in EPEL9 that it might not be difficult to include this also.  

Thanks for doing this so quickly!

Comment 4 Fedora Update System 2024-03-10 02:19:37 UTC
FEDORA-EPEL-2024-2361108412 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-2024-2361108412

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

Comment 5 Fedora Update System 2024-03-12 01:28:11 UTC
FEDORA-EPEL-2024-2361108412 (rust-configparser-3.0.4-1.el9) 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.