Bug 33052 - Remove LSB packages
Summary: Remove LSB packages
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 10
Assignee: All Packagers
QA Contact:
Depends on:
Blocks: 33053
  Show dependency treegraph
Reported: 2024-04-03 14:54 CEST by Frédéric "LpSolit" Buclin
Modified: 2024-04-03 21:30 CEST (History)
0 users

See Also:
Source RPM: lsb-4.1-25.mga9.src.rpm
Status comment:


Description Frédéric "LpSolit" Buclin 2024-04-03 14:54:48 CEST
As explained in bug 19684 comment 14 and bug 19684 comment 16, I suggest to drop LSB packages entirely, except lsb_release which can stay (see bug 19684 comment 18). The reason is that per https://lists.linuxfoundation.org/pipermail/lsb-discuss/2023-February/008278.html, "the LSB project is essentially abandoned".

Also, per https://bugzilla.redhat.com/show_bug.cgi?id=2118596#c1, Fedora is not willing to waste energy on LSB 5.0 port either.

Debian and Ubuntu also dropped support for LSB:


The changelog mentions: "Drop all the LSB compatibility packages besides lsb-release and lsb-base".

And the lsb-base description mentions: "This is an empty package; it's needed only because of Provides: not being supported in debootstrap.  It can be safely removed.". So it's basically an empty package.

If Fedora, Debian and Ubuntu all dropped support for LSB, I see no point for Mageia to still support it.

If you agree with this proposal, then bug 19684 could be closed as WONTFIX.
Frédéric "LpSolit" Buclin 2024-04-03 14:57:36 CEST

Blocks: (none) => 33053

Comment 1 Lewis Smith 2024-04-03 21:30:26 CEST
Thank you for this well documanted case for dropping LSB.
It has been mooted for dropping for ages. Devs need to decide: via the mailList?

If agreed to, please add it to Bug 32127 "[TRACKER] Packages that need to be obsoleted for Mageia 10 release".

Source RPM: (none) => lsb-4.1-25.mga9.src.rpm
Assignee: bugsquad => pkg-bugs

Note You need to log in before you can comment on or make changes to this bug.