> On my daily updated system, I today saw this: > The following NEW packages will be installed: > libdbd-mariadb-perl > The following packages have been kept back: > mariadb-server > The following packages will be upgraded: > chromium chromium-common chromium-driver chromium-sandbox > glib-networking glib-networking-common glib-networking-services > ibus-data imagemagick imagemagick-6-common imagemagick-6-doc > imagemagick-6.q16 klibc-utils libgraph-perl libibus-1.0-5 libklibc > liblzma-dev liblzma5 libmagickcore-6.q16-6 libmagickcore-6.q16-6-extra > libmagickwand-6.q16-6 libmariadb3 libyuv0 > libzstd-dev libzstd1 mariadb-common mercurial mercurial-common > r-cran-survival xz-utils zstd > 31 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. > > I've not accepted the change to help you debug the situation, but > apparently the upgrade path for the new unversioned src:mariadb isn't ideal. > > Can I help you with more information?
What does apt upgrade -o Debug::pkgDepCache::Marker=1 -o Debug::pkgDepCache::AutoInstall=1 -o Debug::pkgProblemResolver=1 yield? In this situation we need to debug what versions apt is seeing and how it is resolving them [1]. To be able to investigate, fix and validate that a fix is correct, I probably need a reproducible test case we can add to our Salsa-CI [2]. [1] https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/README.Contributor#L274-347 [2] https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/502070
