apt/apt-pkg/pkgcache.h, branch 2.9.28Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.282025-01-30T19:10:50ZDrop unused version stanza size info from binary cache2025-01-30T19:10:50ZDavid Kalnischkiesdavid@kalnischkies.de2025-01-30T18:03:26Zurn:sha1:1bc8dab8df60c5da7cc817bec5f53e60f7eb9817
Same reason as with the description size before, but this one had
actually one extremely dated user in src:apt left with dumpavail,
which is changed to an implementation that is (in comparison) a bit
slower, but should be good enough for a command that is ideally not
used anymore (even if codesearch suggests otherwise).
After all, what makes this a bit slower is not that we don't know the
size, but that this one does additional work preparing for accessing
the fields which we don't do. In exchange pkgTagFile has a better
implementation for "Jitter" than the old code that we would "just"
need to copy here if speed were really an issue.
Drop unused description size info from binary cache2025-01-30T16:39:40ZDavid Kalnischkiesdavid@kalnischkies.de2025-01-30T16:39:40Zurn:sha1:1bc221a9dd22baa6e2e516d45dc858774cafddd0
Nothing in src:apt uses this information and that isn't all to
surprising as it is usually not that interesting to know how big
a specific stanza of a description is as the max size is available
and you are usually working with more than one description.
So this information just takes up space in our binary cache…
64 bits per structure which can quickly add up to whole MBs
depending on how many (and which) sources you have enabled.
Do not overflow ver/desc<->file relation counters2025-01-30T15:22:14ZDavid Kalnischkiesdavid@kalnischkies.de2025-01-30T15:22:14Zurn:sha1:2e39d0fdeff5f9db91b3490d6750c8033aca9057
The counters aren't used for anything really except for the 'stats'
command that is off in its display and calculation due to 16bit not
being enough for counting all the relations we have.
Semi-broken more than a decade ago as I accidentally aligned it with
the other file relation counters which count far less frequent ones
through, so 'unsigned long' should have been changed to the id type
rather than the smaller fileid type.
Of course, this commit only prepares the fix as this would be an ABI
break, so with the current ABI we are still overflowing.
Regression-of: 4ad8619bb1f0bf777d17c568bb7a6cf7f30aac34
Add pkgCache::{Priority,DepType}_NoL10n to avoid duplication2025-01-05T22:16:08ZDavid Kalnischkiesdavid@kalnischkies.de2024-12-26T20:43:34Zurn:sha1:6828ae2c2f9268c8187f0fa91b3c464ed84a8476
We don't have many places, but lets reduce the amount of duplicating
these short strings, so that we may find all the places we have to
change if that ever happens.
Modernize standard library includes2024-02-20T12:49:04ZJulian Andres Klodejulian.klode@canonical.com2024-02-20T12:43:08Zurn:sha1:40a75722c43ae24cb9a99d6730a3b25b65819c49
This was automated with sed and git-clang-format, and then I had to
fix up the top of policy.cc by hand as git-clang-format accidentally
indented it by two spaces.
Invalidate cached architecture list when building cache2021-10-19T16:25:51ZJulian Andres Klodejulian.klode@canonical.com2021-10-19T16:11:14Zurn:sha1:307912e8d74d9684875a791b0550c10afc14b0b0
Fix a regression in python-apt where switching the architectures
in the config between cache invocations regressed.
Regression-Of: 8ff4e226af55a9feb168477a2b1a99f9c5152e54
Gbp-Dch: full
All pkgCaches are MultiArch caches2021-09-04T13:35:15ZDavid Kalnischkiesdavid@kalnischkies.de2021-09-04T11:03:05Zurn:sha1:8ff4e226af55a9feb168477a2b1a99f9c5152e54
Back in 2015 the code inside libapt who was using this field was dropped
as even if we are on a system which is not configured for MultiArch,
there are still edge cases in which the cache can include very foreign
packages, so any assumption you could make thinking only a single
architecture will be in the cache is probably wrong.
Maintaining two different codepaths for Multi- and SingleArch is likely
not very beneficial for code and users alike and is surprisingly hard to
answer correctly and becoming even harder still, so always assuming the
"worst case" seems like the far better option.
References: 6c9937da76b9155d166092b9dda22d06200510c1
Add support for Phased-Update-Percentage2021-01-08T13:48:47ZJulian Andres Klodejulian.klode@canonical.com2020-08-10T18:16:11Zurn:sha1:c5bc86d45e003905ef411146e66b414d26fb1ff8
This adds support for Phased-Update-Percentage by pinning
upgrades that are not to be installed down to 1.
The output of policy has been changed to add the level of
phasing, and documentation has been improved to document
how phased updates work.
The patch detects if it is running in a chroot, and if so, always
includes phased updates, restoring classic apt behavior to avoid
behavioral changes on buildd chroots.
Various options are added to control this all:
* APT::Get::{Always,Never}-Include-Phased-Updates and their legacy
update-manager equivalents to always or never include phased updates
* APT::Machine-ID can be set to a UUID string to have all machines in a
fleet phase the same
* Dir::Etc::Machine-ID is weird in that it's default is sort of like
../machine-id, but not really, as ../machine-id would look up
$PWD/../machine-id and not relative to Dir::Etc; but it allows you to
override the path to machine-id (as opposed to the value)
* Dir::Bin::ischroot is the path to the ischroot(1) binary which is used
to detect whether we are running in a chroot.
Add correct std namespace to nullptr_t2020-04-26T16:13:19ZDavid Kalnischkiesdavid@kalnischkies.de2020-04-26T16:13:19Zurn:sha1:3824e0c49c7c43ac99d4f871d8404559070d7049
Reported-By: clangd
Gbp-Dch: Ignore
pkgcache: Add operator bool() to map_pointer2020-02-27T08:45:11ZJulian Andres Klodejulian.klode@canonical.com2020-02-27T08:45:11Zurn:sha1:0a076efd1b2b1cb2d57fd583af8031039ba03158