Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=3.3.0 2025-10-25T18:42:14Z 2025-10-25T18:42:14Z Julian Andres Klode julian.klode@canonical.com 2025-01-07T16:39:32Z urn: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"; 2022-04-01T12:16:19Z David Kalnischkies david@kalnischkies.de 2022-03-28T13:47:45Z urn:sha1:2005f1c263a942b37d179b9b8f9b7ab343ca7459 The dependency relation fields old names were deprecated in 1995 as the new ones were introduced. That seems barely long enough now as a transition period. 2022-04-01T12:16:15Z David Kalnischkies david@kalnischkies.de 2022-03-28T13:25:36Z urn:sha1:7b8da771e2061462b9196f38366c34e4f919d0df dpkg-dev stopped recognizing it in 2007 (1.14.7) while building packages. The rename itself happened in 1995 (0.93.72). 2022-04-01T12:15:26Z David Kalnischkies david@kalnischkies.de 2022-03-28T13:19:11Z urn:sha1:f6438ea9e726a1c13ce8d90ac78cc272346ab0f8 The previous regime of the file was to sort it on insert, but that changes the values in the generated enum, which is fine as long as we only use it in libapt itself, but breaks on other users. The header was always intended to be private to apt itself, so we just document this here now and lay the ground work to have the file in the future only appended to, so that it remains sufficiently ABI stable that we can use it outside the library in our apt tools. We also remove some fields apt is unlikely to need or only uses in certain cases outside of any (speed) critical path to have enough room to add more fields soon as currently we are limited to 128 fields max and it would be sad if we use up that allowance entirely already. 2022-04-01T09:44:17Z David Kalnischkies david@kalnischkies.de 2022-03-26T10:29:12Z urn:sha1:889462ec33480940a355589b0ae57987f17a86e2 dpkg added a new field (see there for details) which breaks our testcases due to an unknown field. apt doesn't make use of the field, but we can at least order it nicely in output we generate. References: dpkg commit 16c412439c5eac5f32930946df9006dfc13efc02 Closes: #1008759 2020-06-29T15:32:17Z Julian Andres Klode julian.klode@canonical.com 2020-06-29T15:31:06Z urn:sha1:ddd8fc3d28cd8e668868158049ced7fa3c8c71b8 This will be mapped to Important for the time being. 2017-10-20T21:40:53Z Julian Andres Klode jak@debian.org 2017-10-20T21:37:36Z urn:sha1:404dececf913d3c09368a73ca00aa8172dbf6865 tagfile-order.c: Add missing fields from dpkg 1.19 For binary packages, this is Build-Essential; for source packages, it is Description. test-bug-718329-...: Ignore control.tar.*, changes in dpkg 1.19 test-apt-extracttemplates: Fix for dpkg 1.19 2017-02-09T11:59:05Z David Kalnischkies david@kalnischkies.de 2017-02-09T09:15:18Z urn:sha1:f09735bfa051b8c830b467ee8d78138c9f1aa808 Added in dpkg commit 6c8203440bf443d3031ee2ab8485b16c1b6da3b6 2016-07-08T10:43:55Z David Kalnischkies david@kalnischkies.de 2016-07-08T09:49:36Z urn:sha1:13a6bb6d99da52cef1d195dfe37430b549ae62db Added in dpkg in commit 90324cfa942ba23d5d44b28b1087fbd510340502. 2015-05-11T15:22:32Z David Kalnischkies david@kalnischkies.de 2015-05-09T16:55:41Z urn:sha1:e8fb1cdfdd13e45f2b3abbd57a28b57ae6137f14 dpkg and dak know various field names and order them in their output, while we have yet another order and have to play catch up with them as we are sitting between chairs here and neither order is ideal for us, too. A little testcase is from now on supposed to help ensureing that we do not derivate to far away from which fields dpkg knows and orders.