Bug 2407423 - Branch and build rust-libseccomp in epel9
Summary: Branch and build rust-libseccomp in epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-libseccomp
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Rust SIG
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-30 16:53 UTC by John Wass
Modified: 2025-11-11 19:59 UTC (History)
2 users (show)

Fixed In Version: rust-libseccomp-0.4.0-1.el9
Clone Of:
Environment:
Last Closed: 2025-11-11 19:59:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Wass 2025-10-30 16:53:02 UTC
Please branch and build rust-libseccomp in epel9.


Reproducible: Always

Comment 1 Fabio Valentini 2025-10-31 18:02:31 UTC
Any particular reason why you need this in EPEL 9?

The only dependent packages in Fedora are rust-glycin and rust-glycin-utils, and I doubt that you're working on merging those into EPEL 9 :)

Comment 2 John Wass 2025-11-01 12:41:16 UTC
>Any particular reason why you need this in EPEL 9?

For non-Fedora projects that need to create and apply filters, and that only pull dependencies from epel.

I'm surprised the libseccomp crate was not already requested and in there, seems like it would be a common need... Or am I overlooking something else?

I'd be happy to help with it if needed.


>The only dependent packages in Fedora are rust-glycin and rust-glycin-utils, and I doubt that you're working on merging those into EPEL 9 :)

Correct, I'm not working on those.

Comment 3 Fabio Valentini 2025-11-02 08:41:38 UTC
So this is only for third-party packages, i.e. in COPR, other unofficial / private repositories, or local builds?

Comment 4 John Wass 2025-11-02 14:20:50 UTC
Yeah that sounds right.

Comment 5 John Wass 2025-11-02 14:50:30 UTC
I'd be happy to be the EPEL maintainer.

Comment 6 Fabio Valentini 2025-11-02 20:57:49 UTC
In that case, why not just build that package in those COPRs / private repos too?
The Fedora SRPM should rebuild on EPEL 9 just fine.

Comment 7 John Wass 2025-11-04 19:08:42 UTC
Yeah that would normally work and I'd be happy to, but in this case even though the crate is to be consumed by private builds, the authoritative source of the package needs to be EPEL.

Comment 8 Fabio Valentini 2025-11-04 21:08:43 UTC
That sounds like a rather strange arrangement to me, but oh well.

I'm going ahead with branching and building this package and its dependencies.

Comment 9 John Wass 2025-11-04 21:15:38 UTC
Thank you.  I appreciate your time in the discussion and in the branching and maintaining of it.

Comment 10 Fedora Update System 2025-11-04 22:20:38 UTC
FEDORA-EPEL-2025-2e02246a5d (rust-libseccomp-0.4.0-1.el9 and rust-libseccomp-sys-0.3.0-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2e02246a5d

Comment 11 Fedora Update System 2025-11-05 04:21:45 UTC
FEDORA-EPEL-2025-2e02246a5d 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-2025-2e02246a5d

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

Comment 12 Fedora Update System 2025-11-11 19:59:54 UTC
FEDORA-EPEL-2025-2e02246a5d (rust-libseccomp-0.4.0-1.el9 and rust-libseccomp-sys-0.3.0-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.