Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#993527: mariadb-server: At full-upgrade from buster to bullseye mariadb-server (and also client) are removed.
291 views
Skip to first unread message
Sven Wagner
Sep 2, 2021, 12:40:03 PM9/2/21
to
Package: mariadb-server
Version: 1:10.5.11-1
Severity: normal
Tags: a11y
Dear Maintainer,
I upgraded my Webserver from Buster to Bullseye. During the upgrade
mariadb-server and mariadb-client was removed from the server.
A apt install mariadb-server mariadb-client and everything was working
fine again, no loose of databases or other information. Only official
Debian sources in apt.sorces.list.
A friend of mine told me that this happens yesterday night, so I tried
today to report as bug if I can confirm.
Greetings and Thanks for your work on Debian
Sven
-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mariadb-server depends on:
ii mariadb-server-10.5 1:10.5.11-1
mariadb-server recommends no packages.
mariadb-server suggests no packages.
-- no debconf information
Version: 1:10.5.11-1
Severity: normal
Tags: a11y
Dear Maintainer,
I upgraded my Webserver from Buster to Bullseye. During the upgrade
mariadb-server and mariadb-client was removed from the server.
A apt install mariadb-server mariadb-client and everything was working
fine again, no loose of databases or other information. Only official
Debian sources in apt.sorces.list.
A friend of mine told me that this happens yesterday night, so I tried
today to report as bug if I can confirm.
Greetings and Thanks for your work on Debian
Sven
-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mariadb-server depends on:
ii mariadb-server-10.5 1:10.5.11-1
mariadb-server recommends no packages.
mariadb-server suggests no packages.
-- no debconf information
Otto Kekäläinen
Sep 2, 2021, 2:20:05 PM9/2/21
to
Please test with the version in Debian testing.
An identical version is about to enter Bullseye in next stable update.
sv...@hardwarepunk.de
Sep 2, 2021, 4:20:03 PM9/2/21
to
the output of /var/log/apt/history.log here.
The mariadb-server was upgraded, and after upgrade removed.
I removed anything, that has not mariadb in its name from the log:
Start-Date: 2021-09-02 18:00:08
Commandline: apt full-upgrade
Install: ....., mariadb-client-10.5:amd64 (1:10.5.11-1, automatic), ....., mariadb-client-core-10.5:amd64 (1:10.5.11-1, automatic), .....
Upgrade: ...., mariadb-client:amd64 (1:10.3.29-0+deb10u1, 1:10.5.11-1), ....
Remove: ...., mariadb-server:amd64 (1:10.3.29-0+deb10u1),......, mariadb-server-core-10.3:amd64 (1:10.3.29-0+deb10u1), ....., mariadb-client-10.3:amd64 (1:10.3.29-0+deb10u1), ......, mariadb-server-10.3:amd64 (1:10.3.29-0+deb10u1), ...., mariadb-client-core-10.3:amd64 (1:10.3.29-0+deb10u1), ....
End-Date: 2021-09-02 18:02:04
sv...@hardwarepunk.de
Sep 3, 2021, 6:40:03 AM9/3/21
to
> Please test with the version in Debian testing.
We did two tests today. First was an upgrade of the complete system from Buster
to Testing. This worked. mariadb-server and mariadb-client worked both after
upgrade.
Then we tried with apt pinning mariadb-server to testing, and the rest of the
system to bullseye with the following settings:
root@test:/etc/apt/preferences.d# apt-cache policy mariadb-server
mariadb-server:
Installed: (none)
Candidate: 1:10.5.12-1
Version table:
1:10.5.12-1 1000
1 http://ftp.de.debian.org/debian testing/main amd64 Packages
1:10.5.11-1 500
500 http://deb.debian.org/debian bullseye/main amd64 Packages
1:10.3.29-0+deb10u1 500
500 http://mirror.hetzner.de/debian/packages buster/main amd64 Packages
1:10.3.25-0+deb10u1 500
500 http://mirror.hetzner.de/debian/security buster/updates/main amd64 Packages
This output was after upgrade, that is why it says "Installed: (none)"
After this test, mariadb-server and client where again missing.
Extract of /var/log/apt/history.log:
Start-Date: 2021-09-03 12:07:44
Commandline: apt dist-upgrade
Install: ..., mariadb-client-core-10.5:amd64 (1:10.5.12-1, automatic), ..., libmariadb3:amd64 (1:10.5.12-1, automatic), ...
Upgrade: ..., mariadb-common:amd64 (1:10.3.29-0+deb10u1, 1:10.5.12-1),....
Remove: ..., mariadb-server-10.3:amd64 (1:10.3.29-0+deb10u1), ..., mariadb-client-10.3:amd64 (1:10.3.29-0+deb10u1), mariadb-server:amd64 (1:10.3.29-0+deb10u1), mariadb-client-core-10.3:amd64 (1:10.3.29-0+deb10u1), ...
End-Date: 2021-09-03 12:11:26
Greetings
Sven
Tobias Frost
Sep 3, 2021, 9:40:05 AM9/3/21
to
Hi Otto,
was helping Sven with triaging, so bit more info what I did...
First I tried the pinning setup like Sven did, but as I'm not 100%
sure that my pinning works as intended, I also tried another approach
The base for those experiments was a buster pbuilder chroot with
mariadb installed manually and then adding sources for bullseye and testing.
After pinning so that only '*mariadb*' and '*mysql'* packages might be pulled
from testing, apt policy maradb-server showed me the version from testing is
candidate while all other packages are not pulled from testing.
However, apt dist-upgrade still thought the solution is to remove mysql-server...
As I am not 100% sure that I understood pinning correctly, I did another approach:
I've repbuilt the packge from testing for bullseye, kind of something that would be
good for stable-proposed-updates. Rebuild has been done in a bullseye pbuilder env
without any changes, as in:
apt source mariadb-10.5
DIST=bullseye pbuilder build mariadb-10.5_10.5.12-1.dsc
I've placed the resulting packages in a local apt repository; and then loged in into
an buster pbuilder chroot (DIST=buster pbuilder login)
There, I installed mariadb and then activated in sources.list the local repo and bullseye,
followed by apt dist-upgrade.
Unfortunatly, this also tries to remove mariadb-server:
root@isildor:/# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
iproute2 libaio1 libapt-inst2.0 libboost-iostreams1.67.0 libboost-system1.67.0 libbpf0 libbsd0
libcap2 libcap2-bin libconfig-inifiles-perl libcwidget3v5 libdbi-perl libelf1 libmd0 libmnl0
libncurses6 libpopt0 libreadline5 libreadline7 libsnappy1v5 libwrap0 libxtables12 lsof
mariadb-common mariadb-server-core-10.3 mysql-common psmisc rsync socat
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
g++-8 galera-3 gcc-8 libgcc-8-dev libstdc++-8-dev mariadb-client-10.3 mariadb-client-core-10.3
mariadb-server mariadb-server-10.3
The following NEW packages will be installed:
cpp-10 g++-10 gcc-10 gcc-10-base gcc-9-base libapt-pkg6.0 libasan6 libboost-iostreams1.74.0 libbpf0
libbsd0 libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libcwidget4 libffi7 libgcc-10-dev libgcc-s1
libgssapi-krb5-2 libhogweed6 libisl23 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libmd0
libnettle8 libnsl-dev libnsl2 libpcre2-8-0 libperl5.32 libreadline8 libstdc++-10-dev libtirpc-common
libtirpc-dev libtirpc3 libxxhash0 logsave perl-modules-5.32
The following packages will be upgraded:
apt apt-utils aptitude aptitude-common base-files base-passwd bash binutils binutils-common
binutils-x86-64-linux-gnu bsdutils build-essential bzip2 ccache coreutils cpp dash debconf
debian-archive-keyring debianutils diffutils dpkg dpkg-dev e2fsprogs fdisk findutils g++ gawk gcc
gpgv grep gzip hostname init-system-helpers iproute2 libacl1 libaio1 libasan5 libatomic1 libattr1
libaudit-common libaudit1 libbinutils libblkid1 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev
libcap-ng0 libcap2 libcap2-bin libcc1-0 libcom-err2 libconfig-inifiles-perl libdb5.3 libdbi-perl
libdebconfclient0 libdpkg-perl libelf1 libext2fs2 libfdisk1 libgcrypt20 libgdbm-compat4 libgdbm6
libgmp10 libgnutls30 libgomp1 libgpg-error0 libgpm2 libidn2-0 libitm1 liblsan0 liblz4-1 liblzma5
libmnl0 libmount1 libmpc3 libmpfr6 libncurses6 libncursesw6 libp11-kit0 libpam-modules
libpam-modules-bin libpam-runtime libpam0g libpcre3 libpopt0 libquadmath0 libseccomp2 libselinux1
libsemanage-common libsemanage1 libsepol1 libsigc++-2.0-0v5 libsigsegv2 libsmartcols1 libsnappy1v5
libsqlite3-0 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6 libtinfo6 libtsan0 libubsan1
libudev1 libunistring2 libuuid1 libwrap0 libxapian30 libxtables12 libzstd1 linux-libc-dev login
lsb-base lsof make mariadb-common mawk mount mysql-common ncurses-base ncurses-bin passwd patch perl
perl-base psmisc readline-common rsync socat sysvinit-utils tar tzdata util-linux vim vim-common
vim-runtime xxd xz-utils zlib1g
143 upgraded, 39 newly installed, 9 to remove and 0 not upgraded.
Need to get 0 B/125 MB of archives.
After this operation, 22.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
root@isildor:/# apt policy mariadb-server
mariadb-server:
Installed: 1:10.3.29-0+deb10u1
500 file:/home/tobi/pbuilder_repo/deps ./ Packages
1:10.5.11-1 500
500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
*** 1:10.3.29-0+deb10u1 500
500 http://ftp.de.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
apt -s -o Debug::pkgProblemResolver=yes dist-upgrade 2>&1 | tee /tmp/apt-resolver
(apt-resolver is attachd to this mail.)
--
Cheers,
tobi
was helping Sven with triaging, so bit more info what I did...
First I tried the pinning setup like Sven did, but as I'm not 100%
sure that my pinning works as intended, I also tried another approach
The base for those experiments was a buster pbuilder chroot with
mariadb installed manually and then adding sources for bullseye and testing.
After pinning so that only '*mariadb*' and '*mysql'* packages might be pulled
from testing, apt policy maradb-server showed me the version from testing is
candidate while all other packages are not pulled from testing.
However, apt dist-upgrade still thought the solution is to remove mysql-server...
As I am not 100% sure that I understood pinning correctly, I did another approach:
I've repbuilt the packge from testing for bullseye, kind of something that would be
good for stable-proposed-updates. Rebuild has been done in a bullseye pbuilder env
without any changes, as in:
apt source mariadb-10.5
DIST=bullseye pbuilder build mariadb-10.5_10.5.12-1.dsc
I've placed the resulting packages in a local apt repository; and then loged in into
an buster pbuilder chroot (DIST=buster pbuilder login)
There, I installed mariadb and then activated in sources.list the local repo and bullseye,
followed by apt dist-upgrade.
Unfortunatly, this also tries to remove mariadb-server:
root@isildor:/# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
iproute2 libaio1 libapt-inst2.0 libboost-iostreams1.67.0 libboost-system1.67.0 libbpf0 libbsd0
libcap2 libcap2-bin libconfig-inifiles-perl libcwidget3v5 libdbi-perl libelf1 libmd0 libmnl0
libncurses6 libpopt0 libreadline5 libreadline7 libsnappy1v5 libwrap0 libxtables12 lsof
mariadb-common mariadb-server-core-10.3 mysql-common psmisc rsync socat
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
g++-8 galera-3 gcc-8 libgcc-8-dev libstdc++-8-dev mariadb-client-10.3 mariadb-client-core-10.3
mariadb-server mariadb-server-10.3
The following NEW packages will be installed:
cpp-10 g++-10 gcc-10 gcc-10-base gcc-9-base libapt-pkg6.0 libasan6 libboost-iostreams1.74.0 libbpf0
libbsd0 libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libcwidget4 libffi7 libgcc-10-dev libgcc-s1
libgssapi-krb5-2 libhogweed6 libisl23 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libmd0
libnettle8 libnsl-dev libnsl2 libpcre2-8-0 libperl5.32 libreadline8 libstdc++-10-dev libtirpc-common
libtirpc-dev libtirpc3 libxxhash0 logsave perl-modules-5.32
The following packages will be upgraded:
apt apt-utils aptitude aptitude-common base-files base-passwd bash binutils binutils-common
binutils-x86-64-linux-gnu bsdutils build-essential bzip2 ccache coreutils cpp dash debconf
debian-archive-keyring debianutils diffutils dpkg dpkg-dev e2fsprogs fdisk findutils g++ gawk gcc
gpgv grep gzip hostname init-system-helpers iproute2 libacl1 libaio1 libasan5 libatomic1 libattr1
libaudit-common libaudit1 libbinutils libblkid1 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev
libcap-ng0 libcap2 libcap2-bin libcc1-0 libcom-err2 libconfig-inifiles-perl libdb5.3 libdbi-perl
libdebconfclient0 libdpkg-perl libelf1 libext2fs2 libfdisk1 libgcrypt20 libgdbm-compat4 libgdbm6
libgmp10 libgnutls30 libgomp1 libgpg-error0 libgpm2 libidn2-0 libitm1 liblsan0 liblz4-1 liblzma5
libmnl0 libmount1 libmpc3 libmpfr6 libncurses6 libncursesw6 libp11-kit0 libpam-modules
libpam-modules-bin libpam-runtime libpam0g libpcre3 libpopt0 libquadmath0 libseccomp2 libselinux1
libsemanage-common libsemanage1 libsepol1 libsigc++-2.0-0v5 libsigsegv2 libsmartcols1 libsnappy1v5
libsqlite3-0 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6 libtinfo6 libtsan0 libubsan1
libudev1 libunistring2 libuuid1 libwrap0 libxapian30 libxtables12 libzstd1 linux-libc-dev login
lsb-base lsof make mariadb-common mawk mount mysql-common ncurses-base ncurses-bin passwd patch perl
perl-base psmisc readline-common rsync socat sysvinit-utils tar tzdata util-linux vim vim-common
vim-runtime xxd xz-utils zlib1g
143 upgraded, 39 newly installed, 9 to remove and 0 not upgraded.
Need to get 0 B/125 MB of archives.
After this operation, 22.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
root@isildor:/# apt policy mariadb-server
mariadb-server:
Installed: 1:10.3.29-0+deb10u1
Candidate: 1:10.5.12-1
Version table:
1:10.5.12-1 500
Version table:
500 file:/home/tobi/pbuilder_repo/deps ./ Packages
1:10.5.11-1 500
500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
*** 1:10.3.29-0+deb10u1 500
500 http://ftp.de.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
apt -s -o Debug::pkgProblemResolver=yes dist-upgrade 2>&1 | tee /tmp/apt-resolver
(apt-resolver is attachd to this mail.)
--
Cheers,
tobi
Otto Kekäläinen
Sep 4, 2021, 6:00:04 PM9/4/21
to
Thanks Tobias for looking into it.
When you do testing, please don't do any pinning or other stuff that
interferes with apt. There is no need to recompile anything either.
The versions of MariaDB and Galera in Debian Sid, Testing and Bullseye
are all compiled with the exact same toolchain and are still
identical.
Simply test a normal upgrade from Buster to Debian Testing and see if
the issue still repeats with all the MariaDB and Galera packages in
Debian Testing.
- Otto
When you do testing, please don't do any pinning or other stuff that
interferes with apt. There is no need to recompile anything either.
The versions of MariaDB and Galera in Debian Sid, Testing and Bullseye
are all compiled with the exact same toolchain and are still
identical.
Simply test a normal upgrade from Buster to Debian Testing and see if
the issue still repeats with all the MariaDB and Galera packages in
Debian Testing.
- Otto
Tobias Frost
Sep 5, 2021, 5:20:04 AM9/5/21
to
However, I thought you plan to have an update for the next bullseye point
release, because currently buster->bullseye update is broken, and this is what
this bug report is all about.
This is also why I tried only to have updated mariadb packages in the test, as
I thought you meant we should test if this package will fix the dist-upgrade
issue. I guess you'd agree that asking our users to upgrade severs to testing
would not be an acceptable solution...
I understand your message that galera will also needed an
stable-proposed-update upload.. Wont find time to test this path, though
--
tobi
> - Otto
sv...@hardwarepunk.de
Sep 6, 2021, 3:50:03 AM9/6/21
to
On Sun, 5 Sep 2021 11:14:01 +0200
Tobias Frost <to...@debian.org> wrote:
> On Sat, Sep 04, 2021 at 02:52:11PM -0700, Otto Kekäläinen wrote:
> > Simply test a normal upgrade from Buster to Debian Testing and see if
> > the issue still repeats with all the MariaDB and Galera packages in
> > Debian Testing.
>
> Yes, buster->testing seems to work. (Sven tested that on Friday and told me it works)
First sentence of my last reply:
Tobias Frost <to...@debian.org> wrote:
> On Sat, Sep 04, 2021 at 02:52:11PM -0700, Otto Kekäläinen wrote:
> > Simply test a normal upgrade from Buster to Debian Testing and see if
> > the issue still repeats with all the MariaDB and Galera packages in
> > Debian Testing.
>
> Yes, buster->testing seems to work. (Sven tested that on Friday and told me it works)
We did two tests today. First was an upgrade of the complete system from Buster
to Testing. This worked. mariadb-server and mariadb-client worked both after
upgrade.
--
to Testing. This worked. mariadb-server and mariadb-client worked both after
upgrade.
Sven
Tobias Frost
Apr 22, 2022, 3:50:04 PM4/22/22
to
Control: found -1 1:10.5.15-0+deb11u1
On Sat, 9 Oct 2021 19:13:33 -0700 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
<ot...@debian.org> wrote:
> Version: 1:10.5.12-0+deb11u1
>
> Your testing verified that the issue is fixed in Debian testing that
> had 1:10.5.12-1. Debian Bullseye now got 1:10.5.12-0+deb11u1 so I
> assume it is now fixed for Bullseye, as the code in those versions are
> identical. Hence, closing issue.
>
>
Unfortunatly it's not fixed...
Today I came around to upgrade one of my servers from buster to bullseye, and
after upgrade I've found mariadb-server was uninstalled and I had to manually
install it afterwards.
Attached var/log/apt/history.log of the apt dist-upgrade step, including the
manual fixing.
--
Cheers,
tobi
On Sat, 9 Oct 2021 19:13:33 -0700 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
<ot...@debian.org> wrote:
> Version: 1:10.5.12-0+deb11u1
>
> Your testing verified that the issue is fixed in Debian testing that
> had 1:10.5.12-1. Debian Bullseye now got 1:10.5.12-0+deb11u1 so I
> assume it is now fixed for Bullseye, as the code in those versions are
> identical. Hence, closing issue.
>
>
Unfortunatly it's not fixed...
Today I came around to upgrade one of my servers from buster to bullseye, and
after upgrade I've found mariadb-server was uninstalled and I had to manually
install it afterwards.
Attached var/log/apt/history.log of the apt dist-upgrade step, including the
manual fixing.
--
Cheers,
tobi
Faustin Lammler
May 23, 2022, 11:10:03 AM5/23/22
to
Hi Tobias!
Tobias Frost <to...@debian.org>,
22/04/2022 – 21:41:19 (+0200):
> Unfortunatly it's not fixed...
>
> Today I came around to upgrade one of my servers from buster to bullseye, and
> after upgrade I've found mariadb-server was uninstalled and I had to manually
> install it afterwards.
>
> Attached var/log/apt/history.log of the apt dist-upgrade step, including the
> manual fixing.
I can't reproduce this in a full-upgrade from buster (10.3.34-0+deb10u1)
to bullseye (10.5.15-0+deb11u1).
Here are my steps:
| $ podman run -it debian:10 bash
| root@33d890bad500:/# apt update && apt upgrade && apt install mariadb-server
Edit sources.list
| root@33d890bad500:/# apt full-upgrade
| libreadline7 perl-modules-5.28
| Use 'apt autoremove' to remove them.
| libcrypt1 libdbus-1-3 libedit2 libexpat1 libfcgi-bin libfcgi0ldbl libffi7 libgcc-s1 libgssapi-krb5-2
| libhogweed6 libip4tc2 libjson-c5 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libmd0
| libnettle8 libnsl2 libnss-nis libnss-nisplus libpam-systemd libpcre2-8-0 libperl5.32 libprocps8
| libreadline8 libtirpc-common libtirpc3 libxxhash0 logsave mariadb-client-10.5
| mariadb-client-core-10.5 mariadb-server-10.5 mariadb-server-core-10.5 perl-modules-5.32 procps
| systemd-timesyncd
| diffutils dmsetup dpkg e2fsprogs fdisk findutils gawk gpgv grep gzip hostname init-system-helpers
| iproute2 libacl1 libaio1 libapparmor1 libatm1 libattr1 libaudit-common libaudit1 libblkid1 libbz2-1.0
| libc-bin libc6 libcap-ng0 libcap2 libcap2-bin libcgi-fast-perl libcgi-pm-perl libcom-err2
| libconfig-inifiles-perl libcryptsetup12 libdb5.3 libdbd-mysql-perl libdbi-perl libdebconfclient0
| libdevmapper1.02.1 libelf1 libencode-locale-perl libext2fs2 libfcgi-perl libfdisk1 libgcrypt20
| libgdbm-compat4 libgdbm6 libgmp10 libgnutls30 libgpg-error0 libgpm2 libhtml-parser-perl
| libhtml-tagset-perl libhtml-template-perl libhttp-date-perl libhttp-message-perl libidn11 libidn2-0
| libio-html-perl libkmod2 liblwp-mediatypes-perl liblz4-1 liblzma5 libmariadb3 libmnl0 libmount1
| libmpfr6 libncurses6 libncursesw6 libp11-kit0 libpam-cap libpam-modules libpam-modules-bin
| libpam-runtime libpam0g libpcre3 libpopt0 libseccomp2 libselinux1 libsemanage-common libsemanage1
| libsepol1 libsigsegv2 libsmartcols1 libsnappy1v5 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6
| libterm-readkey-perl libtimedate-perl libtinfo6 libudev1 libunistring2 liburi-perl libuuid1 libwrap0
| libxtables12 libzstd1 login lsb-base lsof mariadb-common mariadb-server mawk mount mysql-common
| ncurses-base ncurses-bin netbase passwd perl perl-base psmisc readline-common rsync socat systemd
| systemd-sysv sysvinit-utils tar tzdata util-linux vim vim-common vim-runtime xxd zlib1g
| 137 upgraded, 46 newly installed, 5 to remove and 0 not upgraded.
| Need to get 81.3 MB of archives.
| After this operation, 62.4 MB of additional disk space will be used.
re-create your package environment to maybe spot the dependency
problem?).
Cheers!
--
Faustin
Tobias Frost <to...@debian.org>,
22/04/2022 – 21:41:19 (+0200):
> Unfortunatly it's not fixed...
>
> Today I came around to upgrade one of my servers from buster to bullseye, and
> after upgrade I've found mariadb-server was uninstalled and I had to manually
> install it afterwards.
>
> Attached var/log/apt/history.log of the apt dist-upgrade step, including the
> manual fixing.
to bullseye (10.5.15-0+deb11u1).
Here are my steps:
| $ podman run -it debian:10 bash
| root@33d890bad500:/# apt update && apt upgrade && apt install mariadb-server
Edit sources.list
| root@33d890bad500:/# apt full-upgrade
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| Calculating upgrade... Done
| The following packages were automatically installed and are no longer required:
| libapt-pkg5.0 libffi6 libhogweed4 libidn11 libip4tc0 libjson-c3 libnettle6 libperl5.28 libreadline5
| Building dependency tree
| Reading state information... Done
| Calculating upgrade... Done
| The following packages were automatically installed and are no longer required:
| libreadline7 perl-modules-5.28
| Use 'apt autoremove' to remove them.
| The following packages will be REMOVED:
| galera-3 mariadb-client-10.3 mariadb-client-core-10.3 mariadb-server-10.3 mariadb-server-core-10.3
| The following NEW packages will be installed:
| bsdextrautils dbus galera-4 gcc-10-base krb5-locales libapt-pkg6.0 libbpf0 libbsd0 libclone-perl
| libcrypt1 libdbus-1-3 libedit2 libexpat1 libfcgi-bin libfcgi0ldbl libffi7 libgcc-s1 libgssapi-krb5-2
| libhogweed6 libip4tc2 libjson-c5 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libmd0
| libnettle8 libnsl2 libnss-nis libnss-nisplus libpam-systemd libpcre2-8-0 libperl5.32 libprocps8
| libreadline8 libtirpc-common libtirpc3 libxxhash0 logsave mariadb-client-10.5
| mariadb-client-core-10.5 mariadb-server-10.5 mariadb-server-core-10.5 perl-modules-5.32 procps
| systemd-timesyncd
| The following packages will be upgraded:
| apt base-files base-passwd bash bsdutils coreutils dash debconf debian-archive-keyring debianutils
| diffutils dmsetup dpkg e2fsprogs fdisk findutils gawk gpgv grep gzip hostname init-system-helpers
| iproute2 libacl1 libaio1 libapparmor1 libatm1 libattr1 libaudit-common libaudit1 libblkid1 libbz2-1.0
| libc-bin libc6 libcap-ng0 libcap2 libcap2-bin libcgi-fast-perl libcgi-pm-perl libcom-err2
| libconfig-inifiles-perl libcryptsetup12 libdb5.3 libdbd-mysql-perl libdbi-perl libdebconfclient0
| libdevmapper1.02.1 libelf1 libencode-locale-perl libext2fs2 libfcgi-perl libfdisk1 libgcrypt20
| libgdbm-compat4 libgdbm6 libgmp10 libgnutls30 libgpg-error0 libgpm2 libhtml-parser-perl
| libhtml-tagset-perl libhtml-template-perl libhttp-date-perl libhttp-message-perl libidn11 libidn2-0
| libio-html-perl libkmod2 liblwp-mediatypes-perl liblz4-1 liblzma5 libmariadb3 libmnl0 libmount1
| libmpfr6 libncurses6 libncursesw6 libp11-kit0 libpam-cap libpam-modules libpam-modules-bin
| libpam-runtime libpam0g libpcre3 libpopt0 libseccomp2 libselinux1 libsemanage-common libsemanage1
| libsepol1 libsigsegv2 libsmartcols1 libsnappy1v5 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6
| libterm-readkey-perl libtimedate-perl libtinfo6 libudev1 libunistring2 liburi-perl libuuid1 libwrap0
| libxtables12 libzstd1 login lsb-base lsof mariadb-common mariadb-server mawk mount mysql-common
| ncurses-base ncurses-bin netbase passwd perl perl-base psmisc readline-common rsync socat systemd
| systemd-sysv sysvinit-utils tar tzdata util-linux vim vim-common vim-runtime xxd zlib1g
| 137 upgraded, 46 newly installed, 5 to remove and 0 not upgraded.
| Need to get 81.3 MB of archives.
| After this operation, 62.4 MB of additional disk space will be used.
| Do you want to continue? [Y/n]
Can you give me a bit more information on you setup (how could I
re-create your package environment to maybe spot the dependency
problem?).
Cheers!
--
Faustin
Faustin Lammler
Sep 6, 2022, 9:00:06 AM9/6/22
to
Hi!
As said in my previous message, I am not able to reproduce this so
unless reporter gives more information I will close this bug report
since it seems to be fixed.
In the mean time and to be sure that we do not hit this problem again, I
have implemented a full-upgrade test step in Salsa CI:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/19
Cheers!
---
Faustin
As said in my previous message, I am not able to reproduce this so
unless reporter gives more information I will close this bug report
since it seems to be fixed.
In the mean time and to be sure that we do not hit this problem again, I
have implemented a full-upgrade test step in Salsa CI:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/19
Cheers!
---
Faustin
Otto Kekäläinen
Mar 7, 2023, 2:40:05 AM3/7/23
to
Hi!
Latest version of MariaDB in Debian unstable/testing/Bookworm is
10.11.2. You might want to consider testing it.
If you want to contribute in the open source way to fix this or any
other issue, see
https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
on how to submit a Merge Request!
If you have time to help, please consider these (in order of importance):
1. Review current open MRs at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests
2. Review items highlighted by Debian QA systems (Lintian, builds etc)
and submit a fix to improve the quality:
https://tracker.debian.org/pkg/mariadb
3. Review what testing we have at
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and
think about potential gaps - CI is very important as it is the only
way we can prevent regressions in a scalable way
4. Review/follow-up on existing bugs that currently need more
information: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb&src=mariadb-10.6&src=mariadb-10.5&src=mariadb-10.3&src=mariadb-10.1
MariaDB and C++ skills are useful, but not required. For example
reviewing the NEWS for 10.11 requires no coding skills:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37
My request for help from debian-devel in
https://lists.debian.org/debian-devel/2023/02/msg00272.html did not
get many responses, so the future of this package depends on how
active the users and people who previously reported bugs are in
participating in the maintenance of the package.
- Otto
Latest version of MariaDB in Debian unstable/testing/Bookworm is
10.11.2. You might want to consider testing it.
If you want to contribute in the open source way to fix this or any
other issue, see
https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
on how to submit a Merge Request!
If you have time to help, please consider these (in order of importance):
1. Review current open MRs at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests
2. Review items highlighted by Debian QA systems (Lintian, builds etc)
and submit a fix to improve the quality:
https://tracker.debian.org/pkg/mariadb
3. Review what testing we have at
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and
think about potential gaps - CI is very important as it is the only
way we can prevent regressions in a scalable way
4. Review/follow-up on existing bugs that currently need more
information: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb&src=mariadb-10.6&src=mariadb-10.5&src=mariadb-10.3&src=mariadb-10.1
MariaDB and C++ skills are useful, but not required. For example
reviewing the NEWS for 10.11 requires no coding skills:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37
My request for help from debian-devel in
https://lists.debian.org/debian-devel/2023/02/msg00272.html did not
get many responses, so the future of this package depends on how
active the users and people who previously reported bugs are in
participating in the maintenance of the package.
- Otto
0 new messages