Bug 2370918 - Please branch and build lbzip2 in epel10
Summary: Please branch and build lbzip2 in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: lbzip2
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dominik 'Rathann' Mierzejewski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2335616 2439298
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-07 06:58 UTC by ledestin
Modified: 2026-04-28 01:26 UTC (History)
5 users (show)

Fixed In Version: lbzip2-2.5-31.20171011gitb6dc48a.el10_3
Clone Of:
Environment:
Last Closed: 2026-04-28 01:26:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Package Sources lbzip2 pull-request 1 0 None None None 2026-02-12 10:40:24 UTC

Description ledestin 2025-06-07 06:58:14 UTC
Comment 1 Dominik 'Rathann' Mierzejewski 2026-02-12 10:40:24 UTC 
Still failing to build due to gnulib bug:
+ gnulib-tool --avoid=xalloc-die --add-import pthread utimens warnings timespec-add timespec-sub dtotimespec stat-time lstat malloc-gnu fprintf-posix inttypes xalloc largefile gitlog-to-changelog
python3: can't open file '/usr/bin/.gnulib-tool.py': [Errno 2] No such file or directory
Comment 2 Dominik 'Rathann' Mierzejewski 2026-04-13 20:07:53 UTC 
https://forge.fedoraproject.org/releng/tickets/issues/13313
Comment 3 Fedora Update System 2026-04-15 13:44:58 UTC 
FEDORA-EPEL-2026-daaf6f42c0 (lbzip2-2.5-31.20171011gitb6dc48a.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-daaf6f42c0
Comment 4 Fedora Update System 2026-04-15 13:44:59 UTC 
FEDORA-EPEL-2026-31afc4f75e (lbzip2-2.5-31.20171011gitb6dc48a.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-31afc4f75e
Comment 5 Fedora Update System 2026-04-16 02:10:41 UTC 
FEDORA-EPEL-2026-31afc4f75e 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-2026-31afc4f75e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2026-04-16 02:13:16 UTC 
FEDORA-EPEL-2026-daaf6f42c0 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-2026-daaf6f42c0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2026-04-17 08:51:05 UTC 
FEDORA-EPEL-2026-6af414bfa7 (lbzip2-2.5-31.20171011gitb6dc48a.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-6af414bfa7
Comment 8 Fedora Update System 2026-04-18 01:18:12 UTC 
FEDORA-EPEL-2026-6af414bfa7 has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-6af414bfa7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2026-04-24 01:00:39 UTC 
FEDORA-EPEL-2026-daaf6f42c0 (lbzip2-2.5-31.20171011gitb6dc48a.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 10 Fedora Update System 2026-04-24 01:08:48 UTC 
FEDORA-EPEL-2026-31afc4f75e (lbzip2-2.5-31.20171011gitb6dc48a.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.
Comment 11 Fedora Update System 2026-04-28 01:26:06 UTC 
FEDORA-EPEL-2026-6af414bfa7 (lbzip2-2.5-31.20171011gitb6dc48a.el10_3) has been pushed to the Fedora EPEL 10.3 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.