apt/test, branch 2.5.0Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.5.02022-05-07T08:45:44ZInclude our config.h in all C++ files to avoid ODR violations2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-22T15:05:36Zurn:sha1:320245536a7ad21606286d9dcf54acf3bdf096c6
Some of our headers use APT_COMPILING_APT trickery to avoid exposing too
broadly details we don't want external clients to know and make use of.
The flip-side is that this can lead to different compilation units
seeing different definitions if they aren't all using the same config.
Ignore stty failures in testcases2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-21T10:51:20Zurn:sha1:e5aa5c04ecbd3cdab611794cebf9eb3aa8cbddd4
We use 'stty sane' to combat against stepped output and co caused by
(especially) failed tests, but it does so many things that it
occasionally fails to reset some bits in the parallel interaction we
have with it which fails the tests without a real problem in apt…
Ideally we would be better at stitching the output together, but for the
time being lets ignore these failures instead to stabilize the tests.
Link interactive helpers against system libapt for autopkgtest2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-20T23:45:45Zurn:sha1:8d8b45a96ceceb015f7836cf25b99279c2f377b9
Building the library just so we can build the helpers against it is not
only wasteful but as we are supposed to test the system we can use that
as an additional simple smoke test before the real testing starts.
Merge branch 'fix/tagfilekeys' into 'main'2022-05-06T16:20:52ZJulian Andres Klodejak@debian.org2022-05-06T16:20:52Zurn:sha1:97f16727b50dcaa4810e80d3c16639e0ce6a0958
Consistently dealing with fields via pkgTagSection::Key
See merge request apt-team/apt!233Only protect two kernels, not last installed one2022-04-07T11:19:52ZJulian Andres Klodejulian.klode@canonical.com2022-04-06T11:51:08Zurn:sha1:824651ded0bcf8603e9b508860b8fe5a68fc53ff
The kernel autoremoval algorithm was written to accomodate
for Ubuntu's boot partition sizing, which was written to
accomodate 3 kernels - 2 installed ones + a new one being
unpacked.
It seems that when the algorithm was designed, it was overlooked
that it actually kept 3 kernels.
LP: #1968154
Parse Checksum fields via pkgTagSection::Key, too2022-04-01T12:16:19ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-01T09:37:26Zurn:sha1:05fae6fae95d8ef6690f3d56863e3bb6a44d424c
We abstract hashes a fair bit to be able to add new ones eventually,
which lead us to building the field names on the fly. We can do better
through by keeping a central place for these names, too, which even
helps in reducing code as we don't need the MD5 → Files dance anymore.
Do not order long obsoleted fields anymore2022-04-01T12:16:19ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-28T13:47:45Zurn: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.
Drop support for long obsoleted Suggests alias: Optional2022-04-01T12:16:15ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-28T13:25:36Zurn:sha1:7b8da771e2061462b9196f38366c34e4f919d0df
dpkg-dev stopped recognizing it in 2007 (1.14.7) while building packages.
The rename itself happened in 1995 (0.93.72).
Document tagfile-keys.h as internal to apt2022-04-01T12:15:26ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-28T13:19:11Zurn: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.
Use extra-environment to point to dpkg/dak sources2022-04-01T10:11:14ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-26T11:40:31Zurn:sha1:f0227a5d4c0a2576348417c658ee93bfa19dc6a0
The hack is 7 years by now, so in an attempt to make that slightly
cleaner lets move this to proper variables that can be assigned via
an extra-environment file sources by the framework rather than relying
on my user name and locate in public.
Gbp-Dch: Ignore