apt/apt-pkg/pkgcachegen.h, branch 3.1.15Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=3.1.152025-05-19T15:19:23ZAdd 'Include'/'Exclude' options to limit packages used from a repository2025-05-19T15:19:23ZJulian Andres Klodejulian.klode@canonical.com2025-01-29T18:01:06Zurn:sha1:93416f3227685c390c7ab579981efde526134181
'Include' allows limiting a repository to a allowlist of packages,
'Exclude' allows removing packages from a repository.
Implementation wise this is not the nicest as it goes via the
IndexTarget options, so we first parse our option value into a
vector, then we turn the vector into a string, and then vectorize
it again. That said, we support both "," and " " as separators due
to the construction (we split by "," then we join using " ").
Gbp-Dch: full
Fix crash in VersionExtra using --with-source etc2025-02-24T12:24:17ZJulian Andres Klodejulian.klode@canonical.com2025-02-24T12:18:08Zurn:sha1:55d3bc60f933faf5f46e31c0522bed8320409dcf
VersionExtra holds, at runtime, the SHA256 of the packages being
added to try to avoid deduplicating obviously different packages;
the SHA256 itself is too large to store in the cache.
When volatile sources are used, the VersionExtra array is not
initialized, or rather it used to be initialized to 32*1024
zero elements as a performance optimization.
This meant that specifying --with-source with a package that
looks like a duplicate of a version with an ID >= 32*1024 triggered
the assertion; so we could not reproduce it easily in the test
suite.
Remove the optimized initialization to make the behavior more
uniform; and treat too large version IDs as having no SHA256.
Closes: #1098702
Add missing #include <string_view>2025-02-15T15:57:45ZJulian Andres Klodejulian.klode@canonical.com2025-02-15T15:57:45Zurn:sha1:957de0abd4a3c5fe9142b48455165498ea785b3cstd::string_view const & -> std::string_view2024-11-14T17:41:26Zнабnabijaczleweli@nabijaczleweli.xyz2024-11-14T17:37:57Zurn:sha1:323fcee3730fc8e3edd555f458bf260382f6d3ef
Fixes: 2c03eed649068c8838d971ceeb1a09603dcc8e9c
apt-pkg/pkgcachegen.cc, apt-pkg/pkgcachegen.h: APT::StringView -> std::string_view2024-11-12T19:36:20Zнабnabijaczleweli@nabijaczleweli.xyz2024-11-12T16:59:23Zurn:sha1:e900ad1a727912b340aa43417bff895294854d3bapt-pkg/edsp/edsplistparser.cc: APT::StringView -> std::string_view2024-11-12T19:36:16Zнабnabijaczleweli@nabijaczleweli.xyz2024-11-12T16:59:21Zurn:sha1:982998a061461a503352d85b1d0a76a99c8480cdCompare SHA256 to check if versions are really the same2023-08-02T10:04:32ZJulian Andres Klodejulian.klode@canonical.com2023-08-01T11:59:09Zurn:sha1:5576e7f76da73f3f5217f90d816cc19b6c0a5a77
If we know both SHA256, and they're different, the packages are. This
approach stores the SHA256 only at runtime, avoiding the overhead of
storing it on-disk, because when we update repositories we update all
of them anyhow.
Note that pkgCacheGenerator is hidden, so we can just modify its
ABI, hooray.
Closes: #931175
LP: #2029268
Avoid undefined pointer arithmetic while growing mmap2021-02-04T10:00:00ZDavid Kalnischkiesdavid@kalnischkies.de2020-06-08T15:07:43Zurn:sha1:f7e6eaf84bebac565f462e2ce48f30808cc771eb
The undefined behaviour sanitizer complains with:
runtime error: addition of unsigned offset to 0x… overflowed to 0x…
Compilers and runtime do the right thing in any case and it is a
codepath that can (and ideally should) be avoided for speed reasons
alone, but fixing it can't hurt (too much).
Do not require libxxhash-dev for including pkgcachegen.h2020-12-17T15:20:48ZJulian Andres Klodejulian.klode@canonical.com2020-12-17T15:17:12Zurn:sha1:ece7f5bb0afee0994a4fb4380e756ce725fe67a9Use XXH3 for cache, hash table hashing2020-12-15T12:47:22ZJulian Andres Klodejulian.klode@canonical.com2020-12-13T20:07:03Zurn:sha1:1460eebf2abe913df964e031eff081a57f043697
XXH3 is faster than both our CRC32c implementation as well
as DJB hash for hash table hashing, so meh, let's switch to
it.