Bug 2391717 - Build liblockfile for EPEL10
Summary: Build liblockfile for EPEL10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: liblockfile
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Emmanuel Seyman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2391716
TreeView+ depends on / blocked
 
Reported: 2025-08-29 06:53 UTC by Emmanuel Seyman
Modified: 2025-10-07 01:49 UTC (History)
9 users (show)

Fixed In Version: liblockfile-1.17-11.el10_2 liblockfile-1.17-11.el10_1
Clone Of: 2391716
Environment:
Last Closed: 2025-10-07 00:27:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Emmanuel Seyman 2025-08-29 06:53:10 UTC
lockfile-progs depends on liblockfile-devel

Comment 1 Zdenek Dohnal 2025-09-15 12:41:26 UTC
liblockfile is in Centos Stream 10, so it cannot be in EPEL 10.

If you want to build anything for Centos Stream 10 and it requires liblockfile-devel, file an issue at https://issues.redhat.com to move the liblockfile-devel package into CRB repository.

Comment 2 Troy Dawson 2025-09-23 14:08:28 UTC
liblockfile is NOT in CentOS Stream 10, or RHEL 10.
It was part of the original set of packages synced from Fedora to CentOS Stream 10 but was removed back in May 2024.
It can be in EPEL 10

Comment 4 Zdenek Dohnal 2025-09-23 16:32:25 UTC
Emmanuel, are you a packager, so I can add you to the co-maintainer of liblockfile? I don't plan to maintain the package for EPEL 10 at the moment, but I'm okay with you becoming the EPEL maintainer of the package.

Comment 5 Emmanuel Seyman 2025-09-23 20:07:48 UTC
(In reply to Zdenek Dohnal from comment #4)
> Emmanuel, are you a packager, so I can add you to the co-maintainer of
> liblockfile?

Yes. My fas name is eseyman and I would be glad to be the maintainer of the epel* branches.

Comment 6 Zdenek Dohnal 2025-09-24 13:14:34 UTC
Thanks, Emmanuel! I've added you as collaborator on epel* branches - I hope it gives you enough rights to create branch and build for EPEL 10.

I'll switch the bug to you now.

Comment 7 Fedora Update System 2025-09-28 10:40:11 UTC
FEDORA-EPEL-2025-095e063f73 (liblockfile-1.17-11.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-095e063f73

Comment 8 Fedora Update System 2025-09-28 10:40:12 UTC
FEDORA-EPEL-2025-d55a2b4787 (liblockfile-1.17-11.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d55a2b4787

Comment 9 Fedora Update System 2025-09-29 01:49:22 UTC
FEDORA-EPEL-2025-095e063f73 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-095e063f73

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

Comment 10 Fedora Update System 2025-09-29 01:54:51 UTC
FEDORA-EPEL-2025-d55a2b4787 has been pushed to the Fedora EPEL 10.1 testing repository.

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

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

Comment 11 Fedora Update System 2025-10-07 00:27:36 UTC
FEDORA-EPEL-2025-095e063f73 (liblockfile-1.17-11.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2025-10-07 01:49:32 UTC
FEDORA-EPEL-2025-d55a2b4787 (liblockfile-1.17-11.el10_1) has been pushed to the Fedora EPEL 10.1 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.