apt/apt-pkg, branch 3.1.10Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=3.1.102025-10-25T20:16:54Zsolver3: Allow removing manually installed packages2025-10-25T20:16:54ZJulian Andres Klodejak@debian.org2025-10-25T19:31:34Zurn:sha1:a3fca052ca21ad222ac7f2fdd7f3fe84b44beb60solver3: Do not lose notion that we backtracked2025-10-25T20:16:54ZJulian Andres Klodejak@debian.org2025-10-25T19:25:23Zurn:sha1:8cd4bd5f708b69d536395675da4fce18d7f9c3f3
Record a silly string if we backtracked such that we are aware
of it. We need to handle this in a broader fashion, but
this was at least breaking test-apt-never-markauto-sections
with remove-manual
LP: #2129819
depcache: Allow changing multi-arch versions for removed siblings2025-10-25T20:16:54ZJulian Andres Klodejak@debian.org2025-10-25T19:24:10Zurn:sha1:74636b64a7ee56637a3ce4ddc1d060ca9f8b77e1
Do not prevent us from changing the version of a foreign package
because a sibling that is being removed has a different candidate.
Implement architecture variants2025-10-25T18:42:14ZJulian Andres Klodejulian.klode@canonical.com2025-01-07T16:39:32Zurn:sha1:9d62eef571ffd1fd2df8b97884d3689fced27fb1
Architecture variants are children of an architecture that share
the same ABI but are optimized for different ISA levels. They
are available in Ubuntu 25.10 and newer, and not supported in
Debian or other distributions.
A deb built for a variant contains the Architecture-Variant field,
and the Architecture field points to the baseline, for example:
Architecture: amd64
Architecture-Variant: amd64v3
However, the apt-get indextargets command reports the variant in the
Architecture: field, and most of the code in APT presents the variant
as the architecture.
There are two types of variants:
1. Standalone variants are recorded in the Architectures field of the
Release file as if they were a real architecture:
Architectures: amd64 amd64v3
Standalone architecture variants only fetch the standalone
architecture variant's Packages file. To do this, this patch
changes the code such that the variants indextargets "supplant"
the base targets.
This may have complicated outcomes on the apt-get indextargets
command.
2. Other variants can only be identified by their files being recorded
with hashes in the Release file.
APT fetches both the base architecture's as well as the variant's
Packages file.
Variants are configured in the
APT::Architecture-Variants
list.
Image builders may want to build specific variant images using
APT::Architecture-Variants { "amd64v3"; }
But this commit also implements an automatic discovery mechanism
using the varianttable and /proc/cpuinfo.
APT::Architecture-Variants "auto";
Move split() to APT::String::Split()2025-10-25T18:42:14ZJulian Andres Klodejak@debian.org2025-07-28T10:06:00Zurn:sha1:50d8703c785898d06463513896e37cbe7cedd471
This splits based upon contiguous whitespace as separators
solver3: Eagerly satisfy previously satisfied Recommends2025-10-25T16:10:32ZJulian Andres Klodejak@debian.org2025-10-07T19:49:44Zurn:sha1:ffc9001b513606869c3cf94fb85a792503974d1f
When a user ran `apt install gpg`, the solver decided to remove
`gnupg` and `seahorse` because `seahorse` was only pulled in as
a Recommends of ubuntu-desktop and Recommends were resolved after
all other dependencies.
Solve this to most extent by introducing eager optionality: These
dependencies, while they do not take part in classic unit propagation,
are otherwise treated like hard dependencies and resolved as soon
as possible rather than after any hard dependencies.
This ensures that the Recommends of ubuntu-desktop on seahorse
is retained correctly, and as a result, gnupg is updated to the
latest version.
Oops: 6c8e32eb-665d-11f0-a985-fa163ec8ca8c
configuration: Add MoveSubTree with overwrite=false2025-10-25T14:58:07ZJulian Andres Klodejak@debian.org2025-10-06T20:27:27Zurn:sha1:2e1243e3f582b1a68ac3fb313364a93128a3f918Correctly append or remove FD_CLOEXEC2025-10-20T18:26:49ZJulian Andres Klodejak@debian.org2025-10-20T18:26:49Zurn:sha1:bb1e6834e8a1cd6fd5b88b5a1962e9d813a080fc
Rather than just setting the flags to 0 or FD_CLOEXEC, read
the current value and append or remove as needed.
ExecFork: Simplify closing and make it safe2025-10-20T18:06:50ZJulian Andres Klodejak@debian.org2025-10-20T18:02:17Zurn:sha1:3dea3434bf2003b757d7ecdb5a8194c8a0c7023f
Implement a wrapper around FD_CLOEXEC and use it in place of
the raw fcntl(). This wrapper _Exit()s the child if the operation
failed.
Restructure the close_range() handling to simply mark all fds for
closing first and then "reopen" the ones we should keep.
Add some comments and tests around Keep-Fd ordering2025-10-20T17:42:57ZJulian Andres Klodejak@debian.org2025-10-20T17:41:57Zurn:sha1:cb8df17ff8e59192ae2ab864006eea120d408a7a