Oh wait, I read to fast, the issue is now fixed it seems:

Faustin Lammler <faus...@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

Attachment: signature.asc
Description: PGP signature

Reply via email to