Bug 2306001 - Please branch and build tomcli in epel10
Summary: Please branch and build tomcli in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: tomcli
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Maxwell G
QA Contact:
URL:
Whiteboard:
Depends On: 2306000
Blocks: EPELPackagersSIG 2307084
TreeView+ depends on / blocked
 
Reported: 2024-08-20 11:53 UTC by Ben Beasley
Modified: 2024-08-25 02:13 UTC (History)
1 user (show)

Fixed In Version: tomcli-0.6.0-3.el10_0
Clone Of:
Environment:
Last Closed: 2024-08-25 02:13:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ben Beasley 2024-08-20 11:53:17 UTC 
Please branch and build tomcli in epel10.
Comment 1 Ben Beasley 2024-08-20 11:56:29 UTC 
Since tomcli is increasingly used in spec files for patching pyproject.toml and Cargo.toml files, it would be great to have it in EPEL10.

A local mock-build in an EPEL10 chroot succeeded once I built python-tomlkit first.
Comment 2 Maxwell G 2024-08-21 05:55:09 UTC 
Waiting on https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-6607147707. I've already requested the branch.
Comment 3 Fedora Update System 2024-08-23 15:33:06 UTC 
FEDORA-EPEL-2024-fa90bc004f (tomcli-0.6.0-3.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-fa90bc004f
Comment 4 Fedora Update System 2024-08-24 02:02:43 UTC 
FEDORA-EPEL-2024-fa90bc004f has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-fa90bc004f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2024-08-25 02:13:55 UTC 
FEDORA-EPEL-2024-fa90bc004f (tomcli-0.6.0-3.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.
Note You need to log in before you can comment on or make changes to this bug.