Yes, please change to 'service mariadb start' or 'systemctl start mariadb'
(works also without systemd is systemctl-shim is installed).
Systemd supports aliases while init.d not, so that is why the other works
with both names and the other does not.
> >
> > Any comments to this
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971255 from anyone?
> >
> > Should we revert back to shipping /etc/init.d/mysql on fresh installs as
> > well?
>
> ___
&g
I don't think so.
There's no case for it.
In the direction of eliminating mysql names in MariaDB let's not take
a step back.
On Sun, Oct 4, 2020 at 9:04 PM Otto Kekäläinen wrote:
>
> Hello!
>
> Any comments to this
> https://bugs.debian.org/cgi-bin/bugrep
Hello!
Any comments to this
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971255 from anyone?
Should we revert back to shipping /etc/init.d/mysql on fresh installs as well?
Providing a different sysvinit service name different from the systemd
service name is a violation of the packaging guidelines
https://wiki.debian.org/Teams/pkg-systemd/Packaging?action=show#systemd_unit_files_naming_and_installation
Wasn't this covered already in
https://github.com/MariaDB/server
Package: kopanocore
Hello!
I noticed the autopkgtests at
https://ci.debian.net/data/autopkgtest/testing/amd64/k/kopanocore/7197598/log.gz
failed with:
# Restart MariaDB server... #
/tmp/autopkgtest-lxc.eq69zqgi/downtmp/build.no3/src/debian/tests/smoke:
3
6 matches
Mail list logo
