apt/test/integration, 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:a3fca052ca21ad222ac7f2fdd7f3fe84b44beb60Enable the new solver by default in 0.31, 1.21, 2.11, 3.12025-10-25T20:16:54ZJulian Andres Klodejak@debian.org2025-10-25T15:42:11Zurn:sha1:c5c5d10d1b2ac0a589102315840c4f2a075b18c1
Enable the new solver by default and remove the vendor-specific
configuration change in Ubuntu's drop-in.
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";
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:cb8df17ff8e59192ae2ab864006eea120d408a7aExecFork: Use close_range() if available2025-10-20T15:16:45ZJulian Andres Klodejak@debian.org2025-10-20T15:14:31Zurn:sha1:6aca3716f051b5b6bff63d51fff68b9c7ebc7474
Use close_range() if we have it in preference to iterating
over /proc/self/fd and falling back to closing all possible
fds.
This builds sets of ranges to close that take into account
the APT::Keep-Fds vector, and a test case is provided to
ensure correctness of the splitting logic.
Preference is given to close_range() over /proc as in the
optimal case, this results in a single system call!
Let APT::Get::Mark-Auto satisfy APT::Get::Build-Dep-Automatic2025-10-07T10:25:20ZJochen Sprickerhofjspricke@debian.org2025-09-16T06:29:39Zurn:sha1:f17371c879bd4eedb0fee56ded4bc8a9b766c8e3
This allows:
apt build-dep --mark-auto apt
Closes: #973260
Fix history command error when no ID was given2025-10-06T21:15:50ZSimon Johnssonsimon.johnsson@canonical.com2025-10-06T21:15:50Zurn:sha1:bcc245651becca2ce226589e76a7c7f0177e40a5Add history undo, redo, and rollback features2025-10-02T10:49:58ZSimon Johnssonsimon.johnsson@canonical.com2025-10-02T10:49:58Zurn:sha1:a65dca5d5e9b4bc71722bc91a5641126a1b0ec61test-history: Adjust for as-installed testing2025-09-30T11:01:28ZJulian Andres Klodejak@debian.org2025-09-30T11:01:28Zurn:sha1:b1e10340d5b9cd6fd12f968b5ddd9b7a70b827cb
When testing as installed, we inadvertently do not replace
the command-line with dummy in the "apt history-list"
command.