Bug 2440557 - rrdtool-1.9.0-10.fc45 FTBFS: File not found: /builddir/build/BUILD/rrdtool-1.9.0-build/BUILDROOT/usr/lib64/lua/5.5/*
Summary: rrdtool-1.9.0-10.fc45 FTBFS: File not found: /builddir/build/BUILD/rrdtool-1....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rrdtool
Version: 45
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org//pa...
Whiteboard:
Depends On: 2440977
Blocks: F45FTBFS
TreeView+ depends on / blocked
 
Reported: 2026-02-18 10:40 UTC by Petr Pisar
Modified: 2026-02-20 15:27 UTC (History)
1 user (show)

Fixed In Version: rrdtool-1.9.0-11.fc45
Clone Of:
Environment:
Last Closed: 2026-02-20 15:27:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Petr Pisar 2026-02-18 10:40:44 UTC 
rrdtool-1.9.0-10.fc45 fails to build in Fedora 45:

Processing files: rrdtool-lua-1.9.0-10.fc45.x86_64
error: File not found: /builddir/build/BUILD/rrdtool-1.9.0-build/BUILDROOT/usr/lib64/lua/5.5/*

A difference between passing and failing build root is at <https://koschei.fedoraproject.org/build/22481881>. An upgrade of lua-devel from 5.4.8-5.fc44 to 5.5.0-1.fc45 is suspicious.
Comment 1 Jaroslav Škarvada 2026-02-19 13:33:54 UTC 
Probably Lua bug: https://bugzilla.redhat.com/show_bug.cgi?id=2440977
Comment 2 Jaroslav Škarvada 2026-02-19 14:33:39 UTC 
So the change in Lua is intended, opened rrdtool upstream bug:
https://github.com/oetiker/rrdtool-1.x/issues/1304
Comment 3 Fedora Update System 2026-02-19 14:52:17 UTC 
FEDORA-2026-f7d8e5d8d1 (rrdtool-1.9.0-11.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-f7d8e5d8d1
Comment 4 Fedora Update System 2026-02-20 15:27:47 UTC 
FEDORA-2026-f7d8e5d8d1 (rrdtool-1.9.0-11.fc45) has been pushed to the Fedora 45 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.