Bug 2367761 - Please branch and build lua-bitop in epel10
Summary: Please branch and build lua-bitop in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: lua-bitop
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-21 11:39 UTC by Jakub Ružička
Modified: 2025-06-12 01:36 UTC (History)
2 users (show)

Fixed In Version: lua-bitop-1.0.2-17.el10_1
Clone Of:
Environment:
Last Closed: 2025-06-12 01:36:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jakub Ružička 2025-05-21 11:39:23 UTC
Please branch and build lua-bitop in epel10 OR add me as admin and I will do it.

lua-bitop is Required by lua-http and in turn knot-resolver.

Please feel free to add me (jruzicka) as package co-maintainer, as I already maintain most `lua-*` packages required by knot-resolver.

Comment 1 Orion Poplawski 2025-05-22 04:30:16 UTC
I've added you as an admin.

Comment 2 Fedora Update System 2025-06-03 09:51:14 UTC
FEDORA-EPEL-2025-c9ad9fb28d (lua-bitop-1.0.2-17.el10_1 and lua-http-0.3-17.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c9ad9fb28d

Comment 3 Fedora Update System 2025-06-04 04:43:22 UTC
FEDORA-EPEL-2025-c9ad9fb28d 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-c9ad9fb28d

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

Comment 4 Fedora Update System 2025-06-12 01:36:07 UTC
FEDORA-EPEL-2025-c9ad9fb28d (lua-bitop-1.0.2-17.el10_1 and lua-http-0.3-17.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.