Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1004262: mariadb-server: Instead of being upgraded, mariadb-server gets removed after apt update
99 views
Skip to first unread message
Rutger van Sleen
Jan 23, 2022, 2:40:04 PM1/23/22
to
Package: mariadb-server
Version: 1:10.5.12-1
Severity: important
Dear Maintainer,
mariadb-server-10.6 has hit testing, after `apt update` I found that
`apt full-upgrade` want to remove mariadb-server package, along with the
10.5 packages
I have mariadb-server manually installed, to keep my system up to date
when a new version of mariadb-server-?? hits the repository. I expected
that mariadb-server-10.6 would be installed, but that didn't happen.
What puzzles me, is that I don't see any reason why the metapackage
mariadb-server gets removed, there is clearly a new candidate for it.
-- Policy
$ apt-cache policy mariadb-server
mariadb-server:
Installed: 1:10.5.12-1
Candidate: 1:10.6.5-2
Version table:
1:10.6.5-2 500
500 http://ftp.nl.debian.org/debian testing/main amd64 Packages
100 http://ftp.nl.debian.org/debian unstable/main amd64 Packages
*** 1:10.5.12-1 100
100 http://ftp.nl.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
-- installed mariadb/mysql packages:
$ aptitude search -F%p '~imariadb|~imysql'
libdbd-mysql-perl
libmariadb3
mariadb-client-10.5
mariadb-client-core-10.5
mariadb-common
mariadb-server
mariadb-server-10.5
mariadb-server-core-10.5
mysql-common
php-mysql
php7.4-mysql
zabbix-server-mysql
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mariadb-server depends on:
ii mariadb-server-10.5 1:10.5.12-1
mariadb-server recommends no packages.
mariadb-server suggests no packages.
-- no debconf information
Version: 1:10.5.12-1
Severity: important
Dear Maintainer,
mariadb-server-10.6 has hit testing, after `apt update` I found that
`apt full-upgrade` want to remove mariadb-server package, along with the
10.5 packages
I have mariadb-server manually installed, to keep my system up to date
when a new version of mariadb-server-?? hits the repository. I expected
that mariadb-server-10.6 would be installed, but that didn't happen.
What puzzles me, is that I don't see any reason why the metapackage
mariadb-server gets removed, there is clearly a new candidate for it.
-- Policy
$ apt-cache policy mariadb-server
mariadb-server:
Installed: 1:10.5.12-1
Candidate: 1:10.6.5-2
Version table:
1:10.6.5-2 500
500 http://ftp.nl.debian.org/debian testing/main amd64 Packages
100 http://ftp.nl.debian.org/debian unstable/main amd64 Packages
*** 1:10.5.12-1 100
100 http://ftp.nl.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
-- installed mariadb/mysql packages:
$ aptitude search -F%p '~imariadb|~imysql'
libdbd-mysql-perl
libmariadb3
mariadb-client-10.5
mariadb-client-core-10.5
mariadb-common
mariadb-server
mariadb-server-10.5
mariadb-server-core-10.5
mysql-common
php-mysql
php7.4-mysql
zabbix-server-mysql
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mariadb-server depends on:
ii mariadb-server-10.5 1:10.5.12-1
mariadb-server recommends no packages.
mariadb-server suggests no packages.
-- no debconf information
Rutger van Sleen
Jan 23, 2022, 4:20:04 PM1/23/22
to
I've been digging around with some help from folks over at #debian-nl
and came eventually to this. Not sure if it really helps, but it might
give a clue of what is going on. I aborted the command, so if I can
provide anything else, I'm happy to do so.
$ apt -oDebug::pkgDepCache::Marker=yes full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Hold prevents MarkInstall of php-common:amd64 < 2:76 | 2:92 @hi umH >
MarkInstall hdparm:amd64 < 9.60+ds-1 @ii mK NPb IPb > FU=0
MarkInstall easy-rsa:amd64 < 3.0.8-1 @ii mK NPb IPb > FU=0
MarkInstall mariadb-server:amd64 < 1:10.5.12-1 -> 1:10.6.5-2 @ii umU
Ib > FU=0
MarkInstall mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
MarkInstall mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
MarkInstall mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib > FU=0
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK
Ib > FU=0
MarkDelete mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
MarkInstall mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib > FU=0
MarkInstall libpmem1:amd64 < none -> 1.11.1-3 @un uN Ib > FU=0
MarkInstall libdaxctl1:amd64 < none -> 71.1-1 @un uN > FU=0
MarkInstall libndctl6:amd64 < none -> 71.1-1 @un uN > FU=0
MarkDelete mariadb-server-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib
> FU=0
MarkInstall libhtml-template-perl:amd64 < none -> 2.97-1.1 @un
umN Ib > FU=0
MarkInstall libcgi-pm-perl:amd64 < none -> 4.53-1 @un uN Ib > FU=0
MarkInstall libhtml-parser-perl:amd64 < none -> 3.76-1 @un uN
Ib > FU=0
MarkInstall libhtml-tagset-perl:amd64 < none -> 3.20-4 @un
uN > FU=0
MarkInstall liburi-perl:amd64 < none -> 5.10-1 @un umN > FU=0
MarkInstall libhttp-message-perl:amd64 < none -> 6.36-1 @un
uN Ib > FU=0
MarkInstall libencode-locale-perl:amd64 < none ->
1.05-1.1 @un uN > FU=0
MarkInstall libhttp-date-perl:amd64 < none -> 6.05-1 @un
uN Ib > FU=0
MarkInstall libtimedate-perl:amd64 < none -> 2.3300-2
@un uN > FU=0
MarkInstall libio-html-perl:amd64 < none -> 1.004-2 @un
uN > FU=0
MarkInstall libclone-perl:amd64 < none -> 0.45-1+b1 @un
umN > FU=0
MarkInstall libcgi-fast-perl:amd64 < none -> 1:2.15-1 @un uN
Ib > FU=0
MarkInstall libfcgi-perl:amd64 < none -> 0.82+ds-1 @un uN
Ib > FU=0
MarkInstall libfcgi0ldbl:amd64 < none -> 2.4.2-2 @un uN
IPb > FU=0
MarkInstall libfcgi-bin:amd64 < none -> 2.4.2-2 @un uN
> FU=0
MarkDelete mariadb-server-10.5:amd64 < 1:10.5.12-1 @ii mK NPb Ib > FU=0
MarkInstall samba-vfs-modules:amd64 < 2:4.13.14+dfsg-1+b1 @ii mK NPb
IPb > FU=0
MarkInstall php:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1:amd64 < none -> 8.1.1-4 @un uN Ib > FU=0
MarkInstall libapache2-mod-php8.1:amd64 < none -> 8.1.1-4 @un uN
> FU=0
MarkInstall libqt5core5a:amd64 < 5.15.2+dfsg-14 @ii mK NPb IPb > FU=0
MarkInstall python3-virtualenv:amd64 < 20.12.1+ds-1 -> 20.13.0+ds-1
@ii umU Ib > FU=0
MarkInstall python3-pip-whl:amd64 < none -> 21.3.1+dfsg-3 @un uN Ib
> FU=0
MarkDelete python-pip-whl:amd64 < 20.3.4-4 @ii mK > FU=0
MarkInstall python3-setuptools-whl:amd64 < none -> 59.6.0-1.2 @un
uN > FU=0
MarkInstall python3-wheel-whl:amd64 < none -> 0.37.1-2 @un uN > FU=0
MarkKeep python-pip-whl:amd64 < 20.3.4-4 @ii mR > FU=0
MarkInstall php-gd:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-gd:amd64 < none -> 8.1.1-4 @un uN > FU=0
Hold prevents MarkInstall of php-common:amd64 < 2:76 | 2:92 @hi umH >
MarkInstall php8.1-imagick:amd64 < 3.6.0-4 @ii mK NPb IPb > FU=0
MarkInstall php-imagick:amd64 < 3.6.0-4 @ii mK NPb IPb > FU=0
MarkInstall po-debconf:amd64 < 1.0.21+nmu1 @ii mK NPb IPb > FU=0
MarkInstall libjson-perl:amd64 < 4.04000-1 @ii mK NPb IPb > FU=0
MarkInstall libwmf0.2-7:amd64 < 0.2.8.4-17+b1 @ii mK NPb IPb > FU=0
MarkInstall libgs9-common:amd64 < 9.55.0~dfsg-3 @ii mK NPb IPb > FU=0
MarkInstall php-curl:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-curl:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkInstall libvdpau1:amd64 < 1.4-3 @ii mK NPb IPb > FU=0
MarkKeep mariadb-server-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkInstall libmoo-perl:amd64 < 2.005004-3 @ii mK NPb IPb > FU=0
MarkInstall php-intl:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-intl:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkInstall dpkg-dev:amd64 < 1.21.1 @ii mK NPb IPb > FU=0
MarkInstall libkrb5-3:amd64 < 1.18.3-7 @ii mK NPb IPb > FU=0
MarkInstall vim-latexsuite:amd64 < 1:1.10.0-1 @ii mK NPb IPb > FU=0
MarkInstall libuuid1:amd64 < 2.37.2-6 @ii mK NPb IPb > FU=0
MarkInstall php-mbstring:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-mbstring:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkInstall php-fpm:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-fpm:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkInstall php-gmp:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-gmp:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkInstall ienglish-common:amd64 < 3.4.02-2 @ii mK NPb IPb > FU=0
MarkInstall ispell:amd64 < 3.4.02-2 @ii mK NPb IPb > FU=0
MarkInstall php-mysql:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-mysql:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkKeep mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkInstall libtool:amd64 < 2.4.6-15 @ii mK NPb IPb > FU=0
MarkInstall php-xml:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-xml:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkInstall libmagickcore-6.q16-6:amd64 < 8:6.9.11.60+dfsg-1.3 @ii mK
NPb IPb > FU=0
MarkInstall php-zip:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-zip:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkInstall rkhunter:amd64 < 1.4.6-10 @ii mK NPb IPb > FU=0
MarkInstall libdpkg-perl:amd64 < 1.21.1 @ii mK NPb IPb > FU=0
MarkInstall ruby2.7:amd64 < 2.7.4-1+b1 @ii mK NPb IPb > FU=0
MarkInstall libglib2.0-0:amd64 < 2.70.2-1 @ii mK NPb IPb > FU=0
MarkInstall ipset:amd64 < 7.15-1 @ii mK NPb IPb > FU=0
MarkInstall tiger:amd64 < 1:3.2.4~rc1-3 @ii mK NPb IPb > FU=0
MarkInstall php-bcmath:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-bcmath:amd64 < none -> 8.1.1-4 @un uN > FU=0
MarkInstall youtube-dl:amd64 < 2021.12.17-1 @ii mK NPb IPb > FU=0
MarkInstall debian-goodies:amd64 < 0.87 @ii mK NPb IPb > FU=0
MarkKeep mariadb-server-10.5:amd64 < 1:10.5.12-1 @ii mR NPb > FU=0
MarkInstall firewalld:amd64 < 1.0.3-1 @ii mK NPb IPb > FU=0
MarkInstall weechat-curses:amd64 < 3.4-2 @ii mK NPb IPb > FU=0
MarkInstall shim-signed:amd64 < 1.38+15.4-7 @ii mK NPb IPb > FU=0
MarkKeep mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkInstall php-ldap:amd64 < 2:7.4+76 -> 2:8.1+92 @ii umU Ib > FU=0
MarkInstall php8.1-ldap:amd64 < none -> 8.1.1-4 @un uN > FU=0
Hold prevents MarkInstall of php-common:amd64 < 2:76 | 2:92 @hi umH >
MarkDelete python-pip-whl:amd64 < 20.3.4-4 @ii mK > FU=0
MarkDelete mariadb-server-10.5:amd64 < 1:10.5.12-1 @ii mK NPb Ib > FU=0
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
MarkKeep mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib > FU=0
MarkKeep mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkKeep mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
MarkKeep mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib > FU=0
MarkKeep mariadb-server:amd64 < 1:10.5.12-1 -> 1:10.6.5-2 @ii umU Ib
> FU=0
MarkDelete mariadb-server:amd64 < 1:10.5.12-1 | 1:10.6.5-2 @ii umH Ib
> FU=0
MarkKeep mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
MarkKeep mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
MarkDelete mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
Calculating upgrade... Done
MarkDelete libcgi-fast-perl:amd64 < none -> 1:2.15-1 @un ugN > FU=0
MarkDelete libcgi-pm-perl:amd64 < none -> 4.53-1 @un ugN IPb > FU=0
MarkDelete libclone-perl:amd64 < none -> 0.45-1+b1 @un ugN > FU=0
MarkDelete libdaxctl1:amd64 < none -> 71.1-1 @un ugN > FU=0
MarkDelete libencode-locale-perl:amd64 < none -> 1.05-1.1 @un ugN > FU=0
MarkDelete libfcgi-bin:amd64 < none -> 2.4.2-2 @un ugN > FU=0
MarkDelete libfcgi-perl:amd64 < none -> 0.82+ds-1 @un ugN > FU=0
MarkDelete libfcgi0ldbl:amd64 < none -> 2.4.2-2 @un ugN IPb > FU=0
MarkDelete libhtml-parser-perl:amd64 < none -> 3.76-1 @un ugN > FU=0
MarkDelete libhtml-tagset-perl:amd64 < none -> 3.20-4 @un ugN > FU=0
MarkDelete libhtml-template-perl:amd64 < none -> 2.97-1.1 @un ugN Ib
> FU=0
MarkDelete libhttp-date-perl:amd64 < none -> 6.05-1 @un ugN > FU=0
MarkDelete libhttp-message-perl:amd64 < none -> 6.36-1 @un ugN Ib > FU=0
MarkDelete libio-html-perl:amd64 < none -> 1.004-2 @un ugN > FU=0
MarkDelete libndctl6:amd64 < none -> 71.1-1 @un ugN Ib > FU=0
MarkDelete libpmem1:amd64 < none -> 1.11.1-3 @un ugN Ib > FU=0
MarkDelete libtimedate-perl:amd64 < none -> 2.3300-2 @un ugN > FU=0
MarkDelete mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2 @un
ugN > FU=0
The following packages were automatically installed and are no longer
required:
galera-4 libconfig-inifiles-perl libdbd-mysql-perl libdbi-perl
libterm-readkey-perl mariadb-server-core-10.5 php7.4-gmp socat
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server
mariadb-server-10.5 python-pip-whl
The following NEW packages will be installed:
libapache2-mod-php8.1 liburi-perl php8.1 php8.1-bcmath php8.1-curl
php8.1-fpm php8.1-gd php8.1-gmp php8.1-intl php8.1-ldap php8.1-mbstring
php8.1-mysql php8.1-xml php8.1-zip python3-pip-whl
python3-setuptools-whl python3-wheel-whl
The following packages have been kept back:
php-common
The following packages will be upgraded:
libmariadb3 libncurses6 libncursesw6 libpango-1.0-0
libpangocairo-1.0-0 libpangoft2-1.0-0 libpython3.10
libpython3.10-minimal libpython3.10-stdlib libpython3.9 libpython3.9-dev
libpython3.9-minimal libpython3.9-stdlib libtinfo6
mariadb-common ncurses-base ncurses-bin ncurses-term php php-bcmath
php-curl php-fpm php-gd php-gmp php-intl php-json php-ldap php-mbstring
php-mysql php-xml php-zip python3-distutils python3-lib2to3 python3-pip
python3-pkg-resources
python3-setuptools python3-tk python3-virtualenv python3.9
python3.9-dev python3.9-minimal
41 upgraded, 17 newly installed, 5 to remove and 1 not upgraded.
Need to get 26,8 MB of archives.
After this operation, 82,7 MB disk space will be freed.
Otto Kekäläinen
Jan 23, 2022, 5:00:03 PM1/23/22
to
Thanks for the bug report.
Highlighting lines:
>The following packages will be REMOVED:
> mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server
>mariadb-server-10.5 python-pip-whl
The package 'mariadb-server' should not be here but instead
'mariadb-server-core-10.5'.
Highlighting lines:
>The following packages will be REMOVED:
> mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server
>mariadb-server-10.5 python-pip-whl
'mariadb-server-core-10.5'.
Rutger van Sleen
Jan 27, 2022, 5:40:04 AM1/27/22
to
On 23-01-2022 22:49, Otto Kekäläinen wrote:
> The package 'mariadb-server' should not be here but instead
> 'mariadb-server-core-10.5'.
Yesterday I did an `apt update && apt full-upgrade`, which to my
> The package 'mariadb-server' should not be here but instead
> 'mariadb-server-core-10.5'.
surprise turned up with the mariadb*-10.5 packages going to be removed,
mariadb*-10.6 to be installed and mariadb-server being upgraded. In
other words: expected behavior.
Just to see if this was a fluke or not, I aborted and tried again today.
First an `apt update` followed by `apt full-upgrade`. And behold, the
previous behavior had returned.
So, apt is confused somehow it seems.
Paul Gevers
Jan 27, 2022, 6:20:04 AM1/27/22
to
Hi all,
I asked some feedback on IRC (#debian-devel) today.
<elbrus> DonKult: juliank: can either of you have a look at this apt
output to see why apt seems to not find the desired solution:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004262#10
<elbrus> mariadb-server not being removed would be a better solution
than removing it
<elbrus> we tried to debug this in #debian-nl but ran out of knowledge
<juliank> elbrus: this is missing debugging information
<juliank> elbrus: this needs to be rerun with -o
Debug::pkgProblemResolver=yes
<juliank> or attach an EDSP file
<elbrus> ack, I'll pass it on
<juliank> elbrus: they can use APT_EDSP_DUMP_FILENAME=<some path> and
--solver dump to dump the state and request, then it is easily
reproducible for everyone
<juliank> If needed, the upgrade can likely be eased using Conflicts:
mariadb-server-10.5 from the mariadb-server package
<juliank> Things are tricky, but the basic is
<juliank> If A depends B, and B becomes unsatisfiable (because it's a
versioned dep, for example), A will be removed
<juliank> Here we see that mariadb-server-10.6:amd64 was marked for
keep, so not going to be installed, so mariadb-server (10.6) became
uninstallable
<juliank> It would have been nice to rollback to previous version there,
maybe
<juliank> but clearly there's a conflict somewhere which runs in
pkgProblemResolver
<juliank> (In the above A depends B case, pkgProblemResolver might also
chose to reinstate A and keep B satisfied)
<jochensp> I think it is reproducible in a chroot with unstable with apt
install mariadb-server=1:10.5.12-1; apt full-upgrade
<juliank> I can try in a podman container
<juliank> jochensp: elbrus: I can reproduce, thanks jochensp
<juliank> https://paste.debian.net/1228561/
<juliank> Broken mariadb-client-10.6:amd64 Conflicts on
virtual-mysql-client:amd64 < none @un H >
<juliank> Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-8.0 but that is not InstVer, ignoring
<juliank> Considering mariadb-client-10.5:amd64 -1 as a solution to
mariadb-client-10.6:amd64 -1
<juliank> Holding Back mariadb-client-10.6:amd64 rather than change
virtual-mysql-client:amd64
<juliank> full log: https://paste.debian.net/1228562/
<elbrus> Otto[m]: ^
<juliank> those conflicts between the versioned packages are just asking
for trouble
<elbrus> juliank: are you OK if I copy/paste this into the bug report?
<juliank> elbrus: yeah
<juliank> Either do co-installable versioned packages, or don't version them
<juliank> like that works
<juliank> There are a lot of Breaks for mariadb upto 10.4
<juliank> but none for 10.5?
<juliank> in 10.6
<juliank> elbrus: This also seems to be a duplicate of bug 990922
<juliank> #990922
[zwiebelbot] Debian#990922: apt resolves differently than apt-get:
mariadb-server dist-upgrade Buster to Bullseye fails -
https://bugs.debian.org/990922
<juliank> elbrus: or similar
<juliank> we're a bit tired of mariadb packaging
<juliank> Really, the packages ought to install versioned file paths and
binary names, and then the meta packages provide symlinks to whatever is
default, like anything else does
<juliank> Also maybe apt should try to find a solution where it keeps
all manually installed packages installed and only then try to remove
some of them (well apt-get should)
<juliank> But that's hard
<juliank> well the fallback :D
<juliank> If we forbid the solver from removing manually installed
packages automatically, then it likely would work
<juliank> but some people are like: I installed exim, now I install
postfix, apt should remove exim for me
<juliank> I'd like apt to tell you "Can't install exim because postfix
is installed"
<juliank> And then you have to go apt install postfix exim-
<juliank> yeah I swapped names :D
<juliank> if exim was automatically installed because you installed
"smtp-meta-package" then by all means, apt install postfix would replace
exim
<jcristau> seems better to just fix mariadb packaging
<elbrus> thanks
Copy/pasting the content of the two pastes to not loose them:
https://paste.debian.net/1228562/
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade... MarkInstall mariadb-server:amd64 < 1:10.5.12-1
MarkInstall libkmod2:amd64 < none -> 29-1 @un uN > FU=0
MarkInstall libndctl6:amd64 < none -> 72.1-1+b1 @un uN > FU=0
MarkInstall liburing2:amd64 < none -> 2.1-2 @un uN > FU=0
MarkInstall debconf:amd64 < 1.5.79 @ii mK NPb IPb > FU=0
MarkInstall libgpg-error0:amd64 < 1.43-3 @ii mK NPb IPb > FU=0
> FU=0
MarkInstall bash:amd64 < 5.1-6 @ii mK NPb IPb > FU=0
MarkKeep mariadb-server-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
IPb > FU=0
MarkInstall e2fsprogs:amd64 < 1.46.5-2 @ii mK NPb IPb > FU=0
MarkInstall passwd:amd64 < 1:4.8.1-2 @ii mK NPb IPb > FU=0
MarkInstall bash:amd64 < 5.1-6 @ii mK NPb IPb > FU=0
Starting pkgProblemResolver with broken count: 8
Starting 2 pkgProblemResolver with broken count: 8
Investigating (0) mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib >
Broken mariadb-client-10.6:amd64 Conflicts on virtual-mysql-client:amd64
< none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for mysql-client-8.0
but that is not InstVer, ignoring
Considering mariadb-client-10.5:amd64 -1 as a solution to
mariadb-client-10.6:amd64 -1
virtual-mysql-client:amd64
Investigating (0) mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-server-core-10.6:amd64 Conflicts on
virtual-mysql-server-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-server-core-8.0 but that is not InstVer, ignoring
Considering mariadb-server-core-10.5:amd64 -1 as a solution to
mariadb-server-core-10.6:amd64 -1
virtual-mysql-server-core:amd64
Investigating (0) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Broken mariadb-client-core-10.6:amd64 Breaks on
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
mariadb-client-core-10.5:amd64
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Investigating (0) mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib >
Broken mariadb-server-10.6:amd64 Depends on mariadb-client-10.6:amd64 <
none | 1:10.6.5-2 @un uH > (>= 1:10.6.5-2)
Considering mariadb-client-10.6:amd64 -1 as a solution to
mariadb-server-10.6:amd64 -1
mariadb-client-10.6:amd64
Investigating (1) mariadb-server:amd64 < 1:10.5.12-1 -> 1:10.6.5-2 @ii
umU Ib >
Broken mariadb-server:amd64 Depends on mariadb-server-10.6:amd64 < none
| 1:10.6.5-2 @un uH > (>= 1:10.6.5-2)
Considering mariadb-server-10.6:amd64 -1 as a solution to
mariadb-server:amd64 0
mariadb-server-10.6:amd64
Investigating (1) mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Broken mariadb-client-10.5:amd64 Depends on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > (>= 1:10.5.12-1)
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-10.5:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
mariadb-client-core-10.5:amd64
Investigating (1) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Broken mariadb-client-core-10.6:amd64 Breaks on
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
mariadb-client-core-10.5:amd64
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Try to Re-Instate (2) mariadb-server:amd64
Broken mariadb-client-10.5:amd64 Depends on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > (>= 1:10.5.12-1)
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-10.5:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
mariadb-client-core-10.5:amd64
Investigating (2) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -1 as a solution to
mariadb-client-core-10.6:amd64 -1
MarkKeep mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
Holding Back mariadb-client-core-10.6:amd64 rather than change
virtual-mysql-client-core:amd64
Done
MarkDelete libdaxctl1:amd64 < none -> 72.1-1+b1 @un ugN > FU=0
MarkDelete libkmod2:amd64 < none -> 29-1 @un ugN > FU=0
MarkDelete libndctl6:amd64 < none -> 72.1-1+b1 @un ugN Ib > FU=0
MarkDelete libnuma1:amd64 < none -> 2.0.14-3 @un ugN > FU=0
The following packages have been kept back:
mariadb-server
The following packages will be upgraded:
bsdutils libblkid1 libc-bin libc6 libgnutls30 libmount1 libsmartcols1
libsystemd0 libudev1 libuuid1 mawk mount util-linux
13 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 7946 kB of archives.
After this operation, 1207 kB of additional disk space will be used.
Do you want to continue? [Y/n] N
Abort.
https://paste.debian.net/plain/1228561
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...Starting pkgProblemResolver with broken count: 8
Starting 2 pkgProblemResolver with broken count: 8
Investigating (0) mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib >
Broken mariadb-client-10.6:amd64 Conflicts on virtual-mysql-client:amd64
< none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for mysql-client-8.0
but that is not InstVer, ignoring
Considering mariadb-client-10.5:amd64 -1 as a solution to
mariadb-client-10.6:amd64 -1
Holding Back mariadb-client-10.6:amd64 rather than change
virtual-mysql-client:amd64
Investigating (0) mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-server-core-10.6:amd64 Conflicts on
virtual-mysql-server-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-server-core-8.0 but that is not InstVer, ignoring
Considering mariadb-server-core-10.5:amd64 -1 as a solution to
mariadb-server-core-10.6:amd64 -1
Holding Back mariadb-server-core-10.6:amd64 rather than change
virtual-mysql-server-core:amd64
Investigating (0) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Broken mariadb-client-core-10.6:amd64 Breaks on
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Investigating (0) mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib >
Broken mariadb-server-10.6:amd64 Depends on mariadb-client-10.6:amd64 <
none | 1:10.6.5-2 @un uH > (>= 1:10.6.5-2)
Considering mariadb-client-10.6:amd64 -1 as a solution to
mariadb-server-10.6:amd64 -1
Holding Back mariadb-server-10.6:amd64 rather than change
mariadb-client-10.6:amd64
Investigating (1) mariadb-server:amd64 < 1:10.5.12-1 -> 1:10.6.5-2 @ii
umU Ib >
Broken mariadb-server:amd64 Depends on mariadb-server-10.6:amd64 < none
| 1:10.6.5-2 @un uH > (>= 1:10.6.5-2)
Considering mariadb-server-10.6:amd64 -1 as a solution to
mariadb-server:amd64 0
Holding Back mariadb-server:amd64 rather than change
mariadb-server-10.6:amd64
Investigating (1) mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Broken mariadb-client-10.5:amd64 Depends on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > (>= 1:10.5.12-1)
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-10.5:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Fixing mariadb-client-10.5:amd64 via keep of
mariadb-client-core-10.5:amd64
Investigating (1) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Broken mariadb-client-core-10.6:amd64 Breaks on
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Try to Re-Instate (2) mariadb-server:amd64
Investigating (2) mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Broken mariadb-client-10.5:amd64 Depends on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > (>= 1:10.5.12-1)
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-10.5:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Fixing mariadb-client-10.5:amd64 via keep of
mariadb-client-core-10.5:amd64
Investigating (2) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -1 as a solution to
mariadb-client-core-10.6:amd64 -1
Holding Back mariadb-client-core-10.6:amd64 rather than change
virtual-mysql-client-core:amd64
Done
The following packages have been kept back:
mariadb-server
The following packages will be upgraded:
bsdutils libblkid1 libc-bin libc6 libgnutls30 libmount1 libsmartcols1
libsystemd0 libudev1 libuuid1 mawk mount util-linux
13 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 7946 kB of archives.
After this operation, 1207 kB of additional disk space will be used.
Do you want to continue? [Y/n] N
Abort.
Paul
I asked some feedback on IRC (#debian-devel) today.
<elbrus> DonKult: juliank: can either of you have a look at this apt
output to see why apt seems to not find the desired solution:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004262#10
<elbrus> mariadb-server not being removed would be a better solution
than removing it
<elbrus> we tried to debug this in #debian-nl but ran out of knowledge
<juliank> elbrus: this is missing debugging information
<juliank> elbrus: this needs to be rerun with -o
Debug::pkgProblemResolver=yes
<juliank> or attach an EDSP file
<elbrus> ack, I'll pass it on
<juliank> elbrus: they can use APT_EDSP_DUMP_FILENAME=<some path> and
--solver dump to dump the state and request, then it is easily
reproducible for everyone
<juliank> If needed, the upgrade can likely be eased using Conflicts:
mariadb-server-10.5 from the mariadb-server package
<juliank> Things are tricky, but the basic is
<juliank> If A depends B, and B becomes unsatisfiable (because it's a
versioned dep, for example), A will be removed
<juliank> Here we see that mariadb-server-10.6:amd64 was marked for
keep, so not going to be installed, so mariadb-server (10.6) became
uninstallable
<juliank> It would have been nice to rollback to previous version there,
maybe
<juliank> but clearly there's a conflict somewhere which runs in
pkgProblemResolver
<juliank> (In the above A depends B case, pkgProblemResolver might also
chose to reinstate A and keep B satisfied)
<jochensp> I think it is reproducible in a chroot with unstable with apt
install mariadb-server=1:10.5.12-1; apt full-upgrade
<juliank> I can try in a podman container
<juliank> jochensp: elbrus: I can reproduce, thanks jochensp
<juliank> https://paste.debian.net/1228561/
<juliank> Broken mariadb-client-10.6:amd64 Conflicts on
virtual-mysql-client:amd64 < none @un H >
<juliank> Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-8.0 but that is not InstVer, ignoring
<juliank> Considering mariadb-client-10.5:amd64 -1 as a solution to
mariadb-client-10.6:amd64 -1
<juliank> Holding Back mariadb-client-10.6:amd64 rather than change
virtual-mysql-client:amd64
<juliank> full log: https://paste.debian.net/1228562/
<elbrus> Otto[m]: ^
<juliank> those conflicts between the versioned packages are just asking
for trouble
<elbrus> juliank: are you OK if I copy/paste this into the bug report?
<juliank> elbrus: yeah
<juliank> Either do co-installable versioned packages, or don't version them
<juliank> like that works
<juliank> There are a lot of Breaks for mariadb upto 10.4
<juliank> but none for 10.5?
<juliank> in 10.6
<juliank> elbrus: This also seems to be a duplicate of bug 990922
<juliank> #990922
[zwiebelbot] Debian#990922: apt resolves differently than apt-get:
mariadb-server dist-upgrade Buster to Bullseye fails -
https://bugs.debian.org/990922
<juliank> elbrus: or similar
<juliank> we're a bit tired of mariadb packaging
<juliank> Really, the packages ought to install versioned file paths and
binary names, and then the meta packages provide symlinks to whatever is
default, like anything else does
<juliank> Also maybe apt should try to find a solution where it keeps
all manually installed packages installed and only then try to remove
some of them (well apt-get should)
<juliank> But that's hard
<juliank> well the fallback :D
<juliank> If we forbid the solver from removing manually installed
packages automatically, then it likely would work
<juliank> but some people are like: I installed exim, now I install
postfix, apt should remove exim for me
<juliank> I'd like apt to tell you "Can't install exim because postfix
is installed"
<juliank> And then you have to go apt install postfix exim-
<juliank> yeah I swapped names :D
<juliank> if exim was automatically installed because you installed
"smtp-meta-package" then by all means, apt install postfix would replace
exim
<jcristau> seems better to just fix mariadb packaging
<elbrus> thanks
Copy/pasting the content of the two pastes to not loose them:
https://paste.debian.net/1228562/
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade... MarkInstall mariadb-server:amd64 < 1:10.5.12-1
-> 1:10.6.5-2 @ii umU Ib > FU=0
MarkInstall mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
MarkInstall mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
MarkInstall mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib > FU=0
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK
Ib > FU=0
MarkDelete mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
MarkInstall mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib > FU=0
MarkInstall libnuma1:amd64 < none -> 2.0.14-3 @un uN > FU=0
MarkInstall mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
MarkInstall mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
MarkInstall mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib > FU=0
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK
Ib > FU=0
MarkDelete mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
MarkInstall mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib > FU=0
MarkInstall libpmem1:amd64 < none -> 1.11.1-3 @un uN Ib > FU=0
MarkInstall libdaxctl1:amd64 < none -> 72.1-1+b1 @un uN Ib > FU=0
MarkInstall libkmod2:amd64 < none -> 29-1 @un uN > FU=0
MarkInstall libndctl6:amd64 < none -> 72.1-1+b1 @un uN > FU=0
MarkInstall liburing2:amd64 < none -> 2.1-2 @un uN > FU=0
MarkDelete mariadb-server-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib
> FU=0
MarkDelete mariadb-server-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
> FU=0
MarkInstall debconf:amd64 < 1.5.79 @ii mK NPb IPb > FU=0
MarkInstall libgpg-error0:amd64 < 1.43-3 @ii mK NPb IPb > FU=0
MarkKeep mariadb-server-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkInstall libkrb5-3:amd64 < 1.18.3-7 @ii mK NPb IPb > FU=0
MarkInstall libuuid1:amd64 < 2.37.3-1 -> 2.37.3-1+b1 @ii umU NPb IPb
> FU=0
MarkInstall bash:amd64 < 5.1-6 @ii mK NPb IPb > FU=0
MarkKeep mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkInstall libc-bin:amd64 < 2.33-3 -> 2.33-5 @ii umU NPb IPb > FU=0
MarkKeep mariadb-server-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkKeep mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
MarkInstall bsdutils:amd64 < 1:2.37.3-1 -> 1:2.37.3-1+b1 @ii umU NPb
IPb > FU=0
MarkInstall e2fsprogs:amd64 < 1.46.5-2 @ii mK NPb IPb > FU=0
MarkInstall passwd:amd64 < 1:4.8.1-2 @ii mK NPb IPb > FU=0
MarkInstall bash:amd64 < 5.1-6 @ii mK NPb IPb > FU=0
Starting pkgProblemResolver with broken count: 8
Starting 2 pkgProblemResolver with broken count: 8
Investigating (0) mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib >
Broken mariadb-client-10.6:amd64 Conflicts on virtual-mysql-client:amd64
< none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for mysql-client-8.0
but that is not InstVer, ignoring
Considering mariadb-client-10.5:amd64 -1 as a solution to
mariadb-client-10.6:amd64 -1
MarkKeep mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib > FU=0
Holding Back mariadb-client-10.6:amd64 rather than change
virtual-mysql-client:amd64
Investigating (0) mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-server-core-10.6:amd64 Conflicts on
virtual-mysql-server-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-server-core-8.0 but that is not InstVer, ignoring
Considering mariadb-server-core-10.5:amd64 -1 as a solution to
mariadb-server-core-10.6:amd64 -1
MarkKeep mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
Holding Back mariadb-server-core-10.6:amd64 rather than change
Ib > FU=0
virtual-mysql-server-core:amd64
Investigating (0) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Broken mariadb-client-core-10.6:amd64 Breaks on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Investigating (0) mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib >
Broken mariadb-server-10.6:amd64 Depends on mariadb-client-10.6:amd64 <
none | 1:10.6.5-2 @un uH > (>= 1:10.6.5-2)
Considering mariadb-client-10.6:amd64 -1 as a solution to
mariadb-server-10.6:amd64 -1
MarkKeep mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib > FU=0
Holding Back mariadb-server-10.6:amd64 rather than change
mariadb-client-10.6:amd64
Investigating (1) mariadb-server:amd64 < 1:10.5.12-1 -> 1:10.6.5-2 @ii
umU Ib >
Broken mariadb-server:amd64 Depends on mariadb-server-10.6:amd64 < none
| 1:10.6.5-2 @un uH > (>= 1:10.6.5-2)
Considering mariadb-server-10.6:amd64 -1 as a solution to
mariadb-server:amd64 0
MarkKeep mariadb-server:amd64 < 1:10.5.12-1 -> 1:10.6.5-2 @ii umU Ib
> FU=0
Holding Back mariadb-server:amd64 rather than change
> FU=0
mariadb-server-10.6:amd64
Investigating (1) mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Broken mariadb-client-10.5:amd64 Depends on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > (>= 1:10.5.12-1)
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-10.5:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
MarkKeep mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
Fixing mariadb-client-10.5:amd64 via keep of
mariadb-client-core-10.5:amd64
Investigating (1) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Broken mariadb-client-core-10.6:amd64 Breaks on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
MarkDelete mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib > FU=0
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Try to Re-Instate (2) mariadb-server:amd64
MarkKeep mariadb-server:amd64 < 1:10.5.12-1 -> 1:10.6.5-2 @ii umU Ib
> FU=0
Investigating (2) mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
> FU=0
Broken mariadb-client-10.5:amd64 Depends on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > (>= 1:10.5.12-1)
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-10.5:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
MarkKeep mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > FU=0
Fixing mariadb-client-10.5:amd64 via keep of
mariadb-client-core-10.5:amd64
Investigating (2) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -1 as a solution to
mariadb-client-core-10.6:amd64 -1
MarkKeep mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2 @un uN
Ib > FU=0
Holding Back mariadb-client-core-10.6:amd64 rather than change
virtual-mysql-client-core:amd64
Done
MarkDelete libdaxctl1:amd64 < none -> 72.1-1+b1 @un ugN > FU=0
MarkDelete libkmod2:amd64 < none -> 29-1 @un ugN > FU=0
MarkDelete libndctl6:amd64 < none -> 72.1-1+b1 @un ugN Ib > FU=0
MarkDelete libnuma1:amd64 < none -> 2.0.14-3 @un ugN > FU=0
MarkDelete libpmem1:amd64 < none -> 1.11.1-3 @un ugN Ib > FU=0
MarkDelete liburing2:amd64 < none -> 2.1-2 @un ugN > FU=0
The following packages have been kept back:
mariadb-server
The following packages will be upgraded:
bsdutils libblkid1 libc-bin libc6 libgnutls30 libmount1 libsmartcols1
libsystemd0 libudev1 libuuid1 mawk mount util-linux
13 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 7946 kB of archives.
After this operation, 1207 kB of additional disk space will be used.
Do you want to continue? [Y/n] N
Abort.
https://paste.debian.net/plain/1228561
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...Starting pkgProblemResolver with broken count: 8
Starting 2 pkgProblemResolver with broken count: 8
Investigating (0) mariadb-client-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib >
Broken mariadb-client-10.6:amd64 Conflicts on virtual-mysql-client:amd64
< none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for mysql-client-8.0
but that is not InstVer, ignoring
Considering mariadb-client-10.5:amd64 -1 as a solution to
mariadb-client-10.6:amd64 -1
Holding Back mariadb-client-10.6:amd64 rather than change
virtual-mysql-client:amd64
Investigating (0) mariadb-server-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-server-core-10.6:amd64 Conflicts on
virtual-mysql-server-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-server-core-8.0 but that is not InstVer, ignoring
Considering mariadb-server-core-10.5:amd64 -1 as a solution to
mariadb-server-core-10.6:amd64 -1
Holding Back mariadb-server-core-10.6:amd64 rather than change
virtual-mysql-server-core:amd64
Investigating (0) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Broken mariadb-client-core-10.6:amd64 Breaks on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Investigating (0) mariadb-server-10.6:amd64 < none -> 1:10.6.5-2 @un uN Ib >
Broken mariadb-server-10.6:amd64 Depends on mariadb-client-10.6:amd64 <
none | 1:10.6.5-2 @un uH > (>= 1:10.6.5-2)
Considering mariadb-client-10.6:amd64 -1 as a solution to
mariadb-server-10.6:amd64 -1
Holding Back mariadb-server-10.6:amd64 rather than change
mariadb-client-10.6:amd64
Investigating (1) mariadb-server:amd64 < 1:10.5.12-1 -> 1:10.6.5-2 @ii
umU Ib >
Broken mariadb-server:amd64 Depends on mariadb-server-10.6:amd64 < none
| 1:10.6.5-2 @un uH > (>= 1:10.6.5-2)
Considering mariadb-server-10.6:amd64 -1 as a solution to
mariadb-server:amd64 0
Holding Back mariadb-server:amd64 rather than change
mariadb-server-10.6:amd64
Investigating (1) mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Broken mariadb-client-10.5:amd64 Depends on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > (>= 1:10.5.12-1)
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-10.5:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Fixing mariadb-client-10.5:amd64 via keep of
mariadb-client-core-10.5:amd64
Investigating (1) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Broken mariadb-client-core-10.6:amd64 Breaks on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-core-10.6:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Fixing mariadb-client-core-10.6:amd64 via remove of
mariadb-client-core-10.5:amd64
Try to Re-Instate (2) mariadb-server:amd64
Investigating (2) mariadb-client-10.5:amd64 < 1:10.5.12-1 @ii mK Ib >
Broken mariadb-client-10.5:amd64 Depends on
mariadb-client-core-10.5:amd64 < 1:10.5.12-1 @ii mR > (>= 1:10.5.12-1)
Considering mariadb-client-core-10.5:amd64 -2 as a solution to
mariadb-client-10.5:amd64 -1
Added mariadb-client-core-10.5:amd64 to the remove list
Fixing mariadb-client-10.5:amd64 via keep of
mariadb-client-core-10.5:amd64
Investigating (2) mariadb-client-core-10.6:amd64 < none -> 1:10.6.5-2
@un uN Ib >
Broken mariadb-client-core-10.6:amd64 Conflicts on
virtual-mysql-client-core:amd64 < none @un H >
Conflicts//Breaks against version 8.0.23-3+b1 for
mysql-client-core-8.0 but that is not InstVer, ignoring
Considering mariadb-client-core-10.5:amd64 -1 as a solution to
mariadb-client-core-10.6:amd64 -1
Holding Back mariadb-client-core-10.6:amd64 rather than change
virtual-mysql-client-core:amd64
Done
The following packages have been kept back:
The following packages will be upgraded:
bsdutils libblkid1 libc-bin libc6 libgnutls30 libmount1 libsmartcols1
libsystemd0 libudev1 libuuid1 mawk mount util-linux
13 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 7946 kB of archives.
After this operation, 1207 kB of additional disk space will be used.
Do you want to continue? [Y/n] N
Abort.
Paul
Otto Kekäläinen
Jan 27, 2022, 1:20:04 PM1/27/22
to
Note that apt-get and apt use different resolvers. Did you
specifically run 'apt' or 'apt-get'?
specifically run 'apt' or 'apt-get'?
Otto Kekäläinen
Jan 27, 2022, 1:20:05 PM1/27/22
to
Since 'apt' always outputs 'WARNING: apt does not have a stable CLI
interface. Use with caution in scripts.' we don't use it in our CI
infra. Instead our install/upgrade testing uses apt-get, see
https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/salsa-ci.yml
Latest run shows no upgrade regressions:
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/335209
interface. Use with caution in scripts.' we don't use it in our CI
infra. Instead our install/upgrade testing uses apt-get, see
https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/salsa-ci.yml
Latest run shows no upgrade regressions:
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/335209
Rutger van Sleen
Jan 27, 2022, 5:00:04 PM1/27/22
to
On 27-01-2022 19:05, Otto Kekäläinen wrote:
> Note that apt-get and apt use different resolvers. Did you
> specifically run 'apt' or 'apt-get'?
apt, apt-get and aptitude are showing all the same behavior in this one.
> Note that apt-get and apt use different resolvers. Did you
> specifically run 'apt' or 'apt-get'?
Paul Gevers
Jan 29, 2022, 3:00:04 PM1/29/22
to
Hi Otto,
On Thu, 27 Jan 2022 10:05:55 -0800 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
<ot...@debian.org> wrote:
> Note that apt-get and apt use different resolvers.
To be pedantic, I don't think this is correct. Yes, apt and apt-get
behave slightly different, but the resolver they use by default is the same.
Paul
On Thu, 27 Jan 2022 10:05:55 -0800 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
<ot...@debian.org> wrote:
> Note that apt-get and apt use different resolvers.
behave slightly different, but the resolver they use by default is the same.
Paul
Otto Kekäläinen
Feb 22, 2022, 2:20:03 AM2/22/22
to
Hello!
As part of our CI we run a Bullseye MariaDB 10.5 to Debian Sid MariaDB
10.6 upgrade on every commit. If passes correctly with:
The following packages will be REMOVED:
mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5
mariadb-server-core-10.5
libpmem1 liburing2 mariadb-client-10.6 mariadb-client-core-10.6
mariadb-server-10.6 mariadb-server-core-10.6
To continue with solving this issue I would like to first get it
reproduced in the CI. The root cause why we have an upgrade issue is
that there is a scenario users can hit that is not covered by our CI.
Fixing that would ensure proper testing coverage and forever working
MariaDB upgrades.
Latest CI run:
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/350897
Bullseye to Sid upgrade test:
https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/2492192
Source.
https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/salsa-ci.yml
How to contribute:
https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
As part of our CI we run a Bullseye MariaDB 10.5 to Debian Sid MariaDB
10.6 upgrade on every commit. If passes correctly with:
The following packages will be REMOVED:
mariadb-server-core-10.5
The following NEW packages will be installed:
libdaxctl1 libkmod2 libndctl6 libnuma1 libodbc2 libodbccr2 libpcre2-posix3
libpmem1 liburing2 mariadb-client-10.6 mariadb-client-core-10.6
mariadb-server-10.6 mariadb-server-core-10.6
To continue with solving this issue I would like to first get it
reproduced in the CI. The root cause why we have an upgrade issue is
that there is a scenario users can hit that is not covered by our CI.
Fixing that would ensure proper testing coverage and forever working
MariaDB upgrades.
Latest CI run:
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/350897
Bullseye to Sid upgrade test:
https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/2492192
Source.
https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/salsa-ci.yml
How to contribute:
https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
Faustin Lammler
Aug 23, 2022, 5:50:03 AM8/23/22
to
Hi!
I can still reproduce this with:
| ❯ podman run -it debian:11 bash -c "apt-get update && \
| apt-get upgrade -y && \
| apt-get -y install mariadb-server && \
| echo 'deb http://deb.debian.org/debian sid main' >/etc/apt/sources.list && \
| apt-get update && \
| apt-get full-upgrade"
| ...
| libregexp-ipv6-perl libsemanage2 libsepol2 libssl3 liburing2 mariadb-client-10.6
| mariadb-client-core-10.6 mariadb-server-10.6 mariadb-server-core-10.6 perl-modules-5.34
| sensible-utils sgml-base util-linux-extra
| The following packages will be upgraded:
| adduser apt base-files base-passwd bash bsdutils coreutils dash debconf debianutils diffutils dpkg
| e2fsprogs findutils galera-4 gcc-10-base gcc-9-base gpgv grep gzip init-system-helpers iproute2
| libacl1 libaio1 libapt-pkg6.0 libatm1 libattr1 libaudit-common libaudit1 libblkid1 libbpf0 libbsd0
| libbz2-1.0 libc-bin libc6 libcap-ng0 libcgi-pm-perl libclone-perl libcom-err2 libcrypt1 libdb5.3
| libdbd-mariadb-perl libdbi-perl libdebconfclient0 libedit2 libelf1 libencode-locale-perl
| libext2fs2 libfcgi-perl libgcc-s1 libgcrypt20 libgdbm-compat4 libgdbm6 libgmp10 libgnutls30
| libgpg-error0 libgpm2 libgssapi-krb5-2 libhogweed6 libhtml-parser-perl libhtml-template-perl
| libhttp-message-perl libidn2-0 libio-html-perl libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0
| liblzma5 libmariadb3 libmd0 libmount1 libncurses6 libncursesw6 libnettle8 libp11-kit0
| libpam-modules libpam-modules-bin libpam-runtime libpam0g libpcre2-8-0 libpcre3 libperl5.32
| libpopt0 libprocps8 libreadline8 libseccomp2 libselinux1 libsemanage-common libsigsegv2
| libsmartcols1 libsnappy1v5 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6 libterm-readkey-perl
| libtinfo6 libtirpc-common libtirpc3 libudev1 libunistring2 liburi-perl libuuid1 libxtables12
| libxxhash0 libzstd1 login logsave lsb-base lsof mariadb-common mariadb-server mawk mount
| mysql-common ncurses-base ncurses-bin passwd perl perl-base perl-modules-5.32 procps psmisc
| readline-common rsync sed socat sysvinit-utils tzdata util-linux zlib1g
| 133 upgraded, 21 newly installed, 5 to remove and 0 not upgraded.
| Need to get 73.6 MB of archives.
| After this operation, 60.6 MB of additional disk space will be used.
21/02/2022 – 23:10:00 (-0800):
> As part of our CI we run a Bullseye MariaDB 10.5 to Debian Sid MariaDB
> 10.6 upgrade on every commit. If passes correctly with:
>
> The following packages will be REMOVED:
> mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5
> mariadb-server-core-10.5
> The following NEW packages will be installed:
> libdaxctl1 libkmod2 libndctl6 libnuma1 libodbc2 libodbccr2 libpcre2-posix3
> libpmem1 liburing2 mariadb-client-10.6 mariadb-client-core-10.6
> mariadb-server-10.6 mariadb-server-core-10.6
Yes, this is also still true, but unfortunately it does not reproduce
exactly the problem IMO.
> To continue with solving this issue I would like to first get it
> reproduced in the CI. The root cause why we have an upgrade issue is
> that there is a scenario users can hit that is not covered by our CI.
> Fixing that would ensure proper testing coverage and forever working
> MariaDB upgrades.
So we should create a new step that would:
- install the produced package on Debian stable;
- full-upgrade to Debian testing;
- verify that mariadb-server was upgraded (and not removed).
@Otto, does that look like something good to have in the CI? I will
propose a MR then...
Cheers!
--
Faustin
I can still reproduce this with:
| ❯ podman run -it debian:11 bash -c "apt-get update && \
| apt-get upgrade -y && \
| apt-get -y install mariadb-server && \
| echo 'deb http://deb.debian.org/debian sid main' >/etc/apt/sources.list && \
| apt-get update && \
| apt-get full-upgrade"
| ...
| The following packages were automatically installed and are no longer required:
| libaio1 libffi7 libperl5.32 libsepol1 libssl1.1 perl-modules-5.32
| Use 'apt autoremove' to remove them.
| The following packages will be REMOVED:
| libsemanage1 mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5
| mariadb-server-core-10.5
| The following NEW packages will be installed:
| gcc-12-base libdaxctl1 libffi8 libkmod2 libndctl6 libnuma1 libperl5.34 libpmem1
| The following NEW packages will be installed:
| libregexp-ipv6-perl libsemanage2 libsepol2 libssl3 liburing2 mariadb-client-10.6
| mariadb-client-core-10.6 mariadb-server-10.6 mariadb-server-core-10.6 perl-modules-5.34
| sensible-utils sgml-base util-linux-extra
| The following packages will be upgraded:
| adduser apt base-files base-passwd bash bsdutils coreutils dash debconf debianutils diffutils dpkg
| e2fsprogs findutils galera-4 gcc-10-base gcc-9-base gpgv grep gzip init-system-helpers iproute2
| libacl1 libaio1 libapt-pkg6.0 libatm1 libattr1 libaudit-common libaudit1 libblkid1 libbpf0 libbsd0
| libbz2-1.0 libc-bin libc6 libcap-ng0 libcgi-pm-perl libclone-perl libcom-err2 libcrypt1 libdb5.3
| libdbd-mariadb-perl libdbi-perl libdebconfclient0 libedit2 libelf1 libencode-locale-perl
| libext2fs2 libfcgi-perl libgcc-s1 libgcrypt20 libgdbm-compat4 libgdbm6 libgmp10 libgnutls30
| libgpg-error0 libgpm2 libgssapi-krb5-2 libhogweed6 libhtml-parser-perl libhtml-template-perl
| libhttp-message-perl libidn2-0 libio-html-perl libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0
| liblzma5 libmariadb3 libmd0 libmount1 libncurses6 libncursesw6 libnettle8 libp11-kit0
| libpam-modules libpam-modules-bin libpam-runtime libpam0g libpcre2-8-0 libpcre3 libperl5.32
| libpopt0 libprocps8 libreadline8 libseccomp2 libselinux1 libsemanage-common libsigsegv2
| libsmartcols1 libsnappy1v5 libss2 libssl1.1 libstdc++6 libsystemd0 libtasn1-6 libterm-readkey-perl
| libtinfo6 libtirpc-common libtirpc3 libudev1 libunistring2 liburi-perl libuuid1 libxtables12
| libxxhash0 libzstd1 login logsave lsb-base lsof mariadb-common mariadb-server mawk mount
| mysql-common ncurses-base ncurses-bin passwd perl perl-base perl-modules-5.32 procps psmisc
| readline-common rsync sed socat sysvinit-utils tzdata util-linux zlib1g
| 133 upgraded, 21 newly installed, 5 to remove and 0 not upgraded.
| Need to get 73.6 MB of archives.
| After this operation, 60.6 MB of additional disk space will be used.
| Do you want to continue? [Y/n]
Otto Kekäläinen <ot...@debian.org>,
21/02/2022 – 23:10:00 (-0800):
> As part of our CI we run a Bullseye MariaDB 10.5 to Debian Sid MariaDB
> 10.6 upgrade on every commit. If passes correctly with:
>
> The following packages will be REMOVED:
> mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5
> mariadb-server-core-10.5
> The following NEW packages will be installed:
> libdaxctl1 libkmod2 libndctl6 libnuma1 libodbc2 libodbccr2 libpcre2-posix3
> libpmem1 liburing2 mariadb-client-10.6 mariadb-client-core-10.6
> mariadb-server-10.6 mariadb-server-core-10.6
exactly the problem IMO.
> To continue with solving this issue I would like to first get it
> reproduced in the CI. The root cause why we have an upgrade issue is
> that there is a scenario users can hit that is not covered by our CI.
> Fixing that would ensure proper testing coverage and forever working
> MariaDB upgrades.
- install the produced package on Debian stable;
- full-upgrade to Debian testing;
- verify that mariadb-server was upgraded (and not removed).
@Otto, does that look like something good to have in the CI? I will
propose a MR then...
Cheers!
--
Faustin
Faustin Lammler
Aug 23, 2022, 6:00:04 AM8/23/22
to
Oh wait, I read to fast, the issue is now fixed it seems:
Faustin Lammler <fau...@fala.red>,
23/08/2022 – 11:43:48 (+0200):
> | The following packages were automatically installed and are no longer required:
> | libaio1 libffi7 libperl5.32 libsepol1 libssl1.1 perl-modules-5.32
> | Use 'apt autoremove' to remove them.
> | The following packages will be REMOVED:
> | libsemanage1 mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5
> | mariadb-server-core-10.5
> | The following NEW packages will be installed:
> | gcc-12-base libdaxctl1 libffi8 libkmod2 libndctl6 libnuma1 libperl5.34 libpmem1
> | libregexp-ipv6-perl libsemanage2 libsepol2 libssl3 liburing2 mariadb-client-10.6
> | mariadb-client-core-10.6 mariadb-server-10.6 mariadb-server-core-10.6 perl-modules-5.34
> | sensible-utils sgml-base util-linux-extra
So mariadb-server-10.6 is installed.
> So we should create a new step that would:
> - install the produced package on Debian stable;
> - full-upgrade to Debian testing;
> - verify that mariadb-server was upgraded (and not removed).
>
> @Otto, does that look like something good to have in the CI? I will
> propose a MR then...
Still this is maybe good to have in the CI?
--
Faustin
Faustin Lammler <fau...@fala.red>,
23/08/2022 – 11:43:48 (+0200):
> | The following packages were automatically installed and are no longer required:
> | libaio1 libffi7 libperl5.32 libsepol1 libssl1.1 perl-modules-5.32
> | Use 'apt autoremove' to remove them.
> | The following packages will be REMOVED:
> | libsemanage1 mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5
> | mariadb-server-core-10.5
> | The following NEW packages will be installed:
> | gcc-12-base libdaxctl1 libffi8 libkmod2 libndctl6 libnuma1 libperl5.34 libpmem1
> | libregexp-ipv6-perl libsemanage2 libsepol2 libssl3 liburing2 mariadb-client-10.6
> | mariadb-client-core-10.6 mariadb-server-10.6 mariadb-server-core-10.6 perl-modules-5.34
> | sensible-utils sgml-base util-linux-extra
> So we should create a new step that would:
> - install the produced package on Debian stable;
> - full-upgrade to Debian testing;
> - verify that mariadb-server was upgraded (and not removed).
>
> @Otto, does that look like something good to have in the CI? I will
> propose a MR then...
--
Faustin
Otto Kekäläinen
Aug 24, 2022, 3:10:04 AM8/24/22
to
@Otto, does that look like something good to have in the CI? I will
propose a MR then...
Yes
Sounds like this is a scenario users hit and thus makes sense to have in Salsa-CI.
Faustin Lammler
Sep 5, 2022, 12:00:03 PM9/5/22
to
A new step in Salsa CI that should cover this scenario is waiting for
review:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/18
I believe that we could close this once it's merged.
Cheers!
--
Faustin
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
review:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/18
I believe that we could close this once it's merged.
Cheers!
--
Faustin
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
Otto Kekäläinen
Mar 7, 2023, 2:40:04 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