apt/test/integration/test-apt-tagfile-fields-order, branch 2.7.11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.7.112022-04-01T12:16:19ZDo 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
Do not unique the field names in test to catch duplicates2022-04-01T10:11:14ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-26T11:08:12Zurn:sha1:7e339dce78e6d00346999c9cf730bd9b1cb75837
It happens to the best, so it might happen for us, too, one day.
Better to catch it directly instead.
Gbp-Dch: Ignore
tests: support spaces in path and TMPDIR2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:20:26Zurn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2
This doesn't allow all tests to run cleanly, but it at least allows to
write tests which could run successfully in such environments.
Git-Dch: Ignore
sync TFRewrite*Order arrays with dpkg and dak2015-05-11T15:22:32ZDavid Kalnischkiesdavid@kalnischkies.de2015-05-09T16:55:41Zurn: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.