Your message dated Wed, 26 Nov 2025 21:08:20 -0800
with message-id
<caou6tack7hc5uk6xgicwp2_8l4p+glaatvpnlekuu8dacuz...@mail.gmail.com>
and subject line Re: [debian-mysql] Bug#1028273: Bug#996706: Bug#996706:
mariadb-server-10.5: run directory is not created in multi-instance mode
has caused the Debian Bug report #1028273,
regarding MariaDB systemd: make multiple systemd files compatible with
--build=all
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1028273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028273
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-server
Severity: wishlist
Tags: newcomer
Upstream MariaDB ships with multiple systemd service files but we
don't have it enabled in MariaDB packaging in Debian[1].
This issue is tagged newcomer friendly as it only requires a minimal
knowledge[2] of existing MariaDB packaging in Debian.
We need help from somebody who can deep dive into both systemd to
understand how this feature is supposed to work correctly, and to read
up on what the Debian Policy says about systemd usage and what the
conventions are for this specifically in Debian.
The section in debian/rules currently looks like this, explaining the problem:
# Install mariadb.socket without enabling it, keep using
mariadb.service by default
# @TODO: Temporarily disable extra and socket systemd file installation until
# a '--build=all' compatible mechanism is found
override_dh_systemd_enable:
dh_systemd_enable --name=mariadb
dh_systemd_enable --no-enable --name=mariadb@ # [email protected]
# dh_systemd_enable --no-enable --name=mariadb mariadb.socket
# dh_systemd_enable --no-enable --name=mariadb-extra mariadb-extra.socket
# dh_systemd_enable --no-enable --name=mariadb@ mariadb.socket
# dh_systemd_enable --no-enable --name=mariadb-extra@ mariadb-extra.socket
If these lines are enabled, the build fails with error:
dh_systemd_enable: warning: Requested unit "mariadb.socket" but it was
not found in any package acted on.
See example of failing CI job at
https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/3763077
[1] https://salsa.debian.org/mariadb-team/mariadb-server
[2]
https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
--- End Message ---
--- Begin Message ---
Hi!
I didn't get any confirmation on this, so I will just assume now it is
fixed and close the issue.
On Fri, 11 Apr 2025 at 08:57, Otto Kekäläinen <[email protected]> wrote:
>
> Hi!
>
> This was potentially fixed via
> https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/63
> a year ago, but I'd like to see a confirmation on the bug report from
> users that the fix was complete and confirmed to work well.
>
> On Mon, 22 Jan 2024 at 09:33, Otto Kekäläinen <[email protected]> wrote:
> >
> > Hi Peter and Toby!
> >
> > The issues about systemd are potentially fixed in
> > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/29
> >
> > Please test it (you can download the .deb packages from the pipeline
> > build artifacts
> > (https://salsa.debian.org/otto/mariadb-server/-/pipelines/628913) and
> > let me know how it went. If I get validation that it works now, I will
> > upload this to Debian and make the bugs you reported as fixed.
> >
> > Thanks!
--- End Message ---
