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.conf
instead of /usr/lib/sysusers.d/mariadb.conf
I've easily reproduced the message:
>>> <stdin>:1: Conflict with earlier configuration for user 'mysql' in /usr/lib/sysusers.d/mariadb.conf:1, ignoring line.
when updating to the current version.
Then, during the package update process the old mariadb.conf
is removed (since it belongs to the old package) and the new mariadb10.11.conf
is 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 :)
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:
# cat mariadb-server-10.11.11-1.fc42.x86_64/usr/lib/sysusers.d/mariadb.conf
u mysql - "MariaDB" /var/lib/mysql
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
# cat mariadb-server-10.11.11-1.fc42.x86_64/usr/lib/sysusers.d/mariadb.conf
u mysql - 'MySQL Server' /var/lib/mysql -
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.
Perfect, it really does solve the BZ#2281416 for me, thanks !
This build fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1987860
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
Thanks for finding that out!
Known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1724283
However I'm looking forward to push it with this issue and resolve the replication later.
Known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1724283
However I'm looking forward to push it with this issue and resolve the replication later.
I disabled autopush due to bug: https://bugzilla.redhat.com/show_bug.cgi?id=1665643
This update won't reach stable upon the bug is fixed.
This update has been unpushed.
Reported as #1663478. Fix is on the way
@muench You are correct. It has been already fixed in 10.2:15, but I added it to this release. One of the reasons is, that even the upstream marked it fixed some time after release. (Maybe fixed it not knowing it was a CVE, marking it later)
I thought it would be good move to mention it atleast now, when I couldn't (or forgot to) do it with older release. Is that OK? Would you like me to change the formating somehow?
Thanks for the feedback @anonymous.
I filed a bug for that: #1563282, so I'd remember to fix that for the next version.
This update has been unpushed.
Thanks @gabrielo.
That is caused by an issue inside the ldconfig scriptlets change.
A new mariadb build is onthe way.
Alright :)
Pushing to testing again.
Can't reproduce your issue on my test machine.
.
/run in tmpfs is now standard an I do have it too
[root@test-machine tmp]# df -h /run
Souborový systém Velikost Užito Volno Uži% Připojeno do
tmpfs 999M 556K 998M 1% /run
.
Can you please check, that your /usr/lib/tmpfiles.d/mariadb.conf file has been properly updated to:
d /run/mariadb 0755 mysql mysql -
d /run/mariadb 0755 mysql mysql -
?
This update has been unpushed.