Description of problem:
The current version released is LSB 4.1 and the latest version is LSB 5. This is the first version we actually changes backwards compatibility with previous versions, prior to 3.
This update would also be able to remove older packages that are only needed for the 4.1 compatibility.
This is most likely just requiring updating some package version dependencies, and adding a few new ones.
Assigning to all packagers collectively, since there is no registered maintainer for this package.
geiger.david68210, jani.valimaa, marja11, pterjan, stewbintn
LSB 5.0 would also let us kill Qt3 entirely, per https://wiki.linuxfoundation.org/en/ReleaseNotes50#Qt_3_Removed
Current LSB version is old, 4.1 =>
Update LSB version to 5.0 (currently at 4.1)
Shouldn't it be promoted to release blocker so that we can kill Qt3 entirely?
Mageia 7 =>
This is release_blocker for a reason.
Making Mageia even better than ever is best direction.
In order to do right thing, this bug should be examined and fixed as soon as possible.
Packagers, please change the status to "Assigned" when you are working on this.
We will make a decision on the relevance of the release_blocker tag on 1st October 2020 QA meeting.
Ping! I'd like to see this being updated as well.
OpenMandriva has the updated version here: https://abf.openmandriva.org/build_lists/773973
I don't know why they name it as version 11.0 though.
I briefly looked into this but it's not clear at all what needs to be done. Loads of links plainly do not work. There's specifications, cool, but normally we get a tarball and package that up. I'm not going to go through a specification in detail and then hope for the best in some spec file. I'd rather drop the entire lsb thing.
If we drop it, we can more easily solve
Bug 24139 - Rename fastboot-android into just fastboot
This is really a blocker one?
Status is the same as it was; no movement on this (from us or Fedora). We made it a blocker because we'd like to not have to maintain Qt3 forever. It will probably not be fixed for Mageia 8 though. We can change the target milestone once 9 is added as an option in Bugzilla.
Yeah, I seriously doubt anyone want/can/will be able to go through all the docs and ensure we have all bits and what cant be dropped as we are now are in RC stage...
Lets try to get it done for mga9
Mageia 8 =>