Package: mariadb-server-core
Version: 1:10.11.3-1
Severity: normal
Dear Maintainer,
after upgrading to bookworm, the4 init script for mariadb fails to
strat the server as it looks for mysqld_safe, which is not installed by
mariadb-server-core.
It appears that the init script comes from mariadb-server-10.5, which is
probably a leftover from bullseye.
I think if mariadb-server-10.5 is incompatible with bookworms mariadb
server, it should be uninstalled on upgrades.
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (990, 'stable-security'), (990, 'stable'), (500,
'unstable-debug'), (500, 'testing-debug'), (500, 'oldstable-debug'), (500,
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32
Kernel: Linux 6.1.35-schmorp (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_WARN,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mariadb-server-core depends on:
ii libc6 2.36-9
ii libcrypt1 1:4.4.33-2
ii libnuma1 2.0.16-1
ii libpcre2-8-0 10.42-1
ii libpmem1 1.12.1-2
ii libssl3 3.0.9-1
ii libstdc++6 12.2.0-14
ii libsystemd0 252.6-1
ii liburing2 2.3-3
ii mariadb-common 1:10.11.3-1
ii zlib1g 1:1.2.13.dfsg-1
mariadb-server-core recommends no packages.
mariadb-server-core suggests no packages.
-- no debconf information
