Bug 2418960 - [Lenovo] lua-libs licence files missing from filesystem
Summary: [Lenovo] lua-libs licence files missing from filesystem
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lua
Version: 43
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-04 21:51 UTC by Mark Pearson
Modified: 2025-12-09 15:18 UTC (History)
18 users (show)

Fixed In Version: lua-5.4.8-4.fc44 lua-5.4.8-4.fc43 lua-5.4.8-4.fc42
Clone Of: 2418959
: 2418961 2418962 (view as bug list)
Environment:
Last Closed: 2025-12-07 00:57:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Package Sources lua pull-request 11 0 None None None 2025-12-04 22:04:11 UTC

Description Mark Pearson 2025-12-04 21:51:27 UTC
Doing open source compliance review for Lenovo's Fedora 43 WS preload and found that lua-libs package does not have a licence in /usr/share/licences.

Looking at the spec file, it seems the licenses are all in the lua package - which is not in the default install image.
Can the Licence file be added to the lua-libs part of the spec file please?

Let me know if there's anything I can help with

Thanks
Mark

Reproducible: Always

Steps to Reproduce:
1. Install Fedora 43 Workstation edition
2. Confirm lua-libs is installed by default
3. Confirm lua-libs is not under /usr/share/licences

Comment 1 Miro Hrončok 2025-12-04 22:04:11 UTC
Fix in https://src.fedoraproject.org/rpms/lua/pull-request/11

Mark, the bugzilla dependency tree looks weird. Also, I am needlessly CC'ed on some of the other bugzzillas, perhaps they are cloned somehow?

Comment 2 Mark Pearson 2025-12-05 00:25:24 UTC
Thanks Miro - and apologies for the cc'ing (and the updates you likely just received as I cleaned up my mess).
I had a bunch of these to do and just cloned the original and modified without realising it added those extra fields. My bad :(
Mark

Comment 3 Fedora Update System 2025-12-05 10:56:39 UTC
FEDORA-2025-dc79f0f1fa (lua-5.4.8-4.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-dc79f0f1fa

Comment 4 Fedora Update System 2025-12-05 10:56:40 UTC
FEDORA-2025-fbc368b160 (lua-5.4.8-4.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-fbc368b160

Comment 5 Fedora Update System 2025-12-06 01:08:19 UTC
FEDORA-2025-dc79f0f1fa has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-dc79f0f1fa`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-dc79f0f1fa

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

Comment 6 Fedora Update System 2025-12-06 01:50:24 UTC
FEDORA-2025-fbc368b160 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-fbc368b160`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-fbc368b160

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

Comment 7 Fedora Update System 2025-12-07 00:57:04 UTC
FEDORA-2025-dc79f0f1fa (lua-5.4.8-4.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Mark Pearson 2025-12-08 00:45:45 UTC
Thanks for fixing this so fast!
mark

Comment 9 Fedora Update System 2025-12-09 01:11:08 UTC
FEDORA-2025-fbc368b160 (lua-5.4.8-4.fc42) has been pushed to the Fedora 42 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.