Bug#1121158: apt: 3.1.x no longer upgrades MariaDB Recommends on upgrade

David Kalnischkies <[email protected]> Sat, 22 Nov 2025 13:07:28 +0100

Newsgroups	gmane.linux.debian.apt.devel
Message-ID	<xioiq3ltjcvxgj5sqyr75syqbsqypsidqj6ccvxpqk2agatzk4__1423.80577033094$1763813846$gmane$org@pgvhxzlp6pxx>

Am Fri, Nov 21, 2025 at 05:17:10PM -0800, schrieb Otto Kekäläinen:
> Thanks for spotting this. This actually means that due to changes in
> how the apt resolver works, upgrades from Bookworm to Forky are broken
> for anyone running MariaDB.

Julian commented on the resolver bits and the bug in your packages.
Let me correct the (repeated) misconception here:
An upgrade from bookworm -> sid/forky is performed by apt/bookworm,
not by apt/forky, in the general case. More importantly, a call like
"apt install foo" is NOT representative of an upgrade.

In an upgrade (think apt full-upgrade) all installed packages are marked
for installation (which boils down to an upgrade of each package).
In an explicit install request only that package is marked for install.
Everything else happens only as needed. And as Julian explained, given
missing breaks, nothing is needed.

Now some people make these explicit install requests to selectively
upgrade ~ individual packages ~, but its not the norm. I would go as far
as saying it usually is a user error (think: "Oh my god, a CVE for foo!
Lets upgrade foo!" but foo uses the not upgraded CVE-buggy libfoo).
And as Julian mentioned the old resolver had (not always, just since
2.5.2, see NEWS) errata to make that work more consistently by assuming
the user meant to upgrade selectively the entire source package.

(A bug for restoring this exists already, but the number eludes me ATM)


Best regards

David Kalnischkies

signature.asc (application/pgp-signature, 833 B)