MariaDB + Galera - F42 sysusers.d fix
UID / GID number 27 is no longer enforced !!!
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-d0066caef6
Please log in to add feedback.
This update has been submitted for testing by mschorm.
This update's test gating status has been changed to 'passed'.
Problem?:
Hi @cmorris, thank you for the feedback.
Functionally, this shouldn't be an issue.
It was caused by sub-optimal handling of the Fedora Change regarding sysusers.d in MariaDB and MySQL packages, where the setup is complicated.
Until recently, we shipped the MariaDB upstream sysusers.d configuration file:
but it was not applied, and the user/group was set up by the '%pre' installation scriptlet.
Then, with the Fedora 42 sysusers.d change, the sysusers.d configuration file started to be applied instead of the '%pre' installation scriptlet. This was not intended.
Now, the package contains a proper fix, providing a downstream sysusers.d configuration file
So functionally, there is no change, only the user description differs.
I will check whether the problem will persist though subsequent updates and if it can be reasonably fixed.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
@mschorm Thank you for taking the time to explain the problem, and for your work on these packages.
I'm back with more details.
First - I've made a mistake in my previous message.
The sysusers.d file now match the name of the package source.
So now it's
/usr/lib/sysusers.d/mariadb10.11.confinstead of/usr/lib/sysusers.d/mariadb.confI've easily reproduced the message:
when updating to the current version.
Then, during the package update process the old
mariadb.confis removed (since it belongs to the old package) and the newmariadb10.11.confis installed (as it belongs to the new package).So during the sub-sequent updates to newer and newer version, the scriptlet message about the conflict is not present, as long as the sysusers.d config files remain unchanged during the update.
With the same logic, swapping between installations of MariaDB and MySQL will work fine, as I will keep the sysusers.d config file in both identical. (not yet in production though. At this moment, mysql8.0 does not contain any sysusers.d config file).
So anyone affected should only see this message once per the config file content change.
I'm thinking of adding one final tweak inside, so you may see it once again
But I hope once I'm done here, I won't need to touch it at least for a decade :)
mschorm edited this update.
mschorm edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by mschorm.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by bodhi.
There is an ongoing freeze; this will be pushed to stable after the freeze is over.
Works
This update has been pushed to stable.