apt/test/libapt, branch 2.1.4

Allow prefix to be a complete filename for GetTempFile

2020-05-18T13:55:36Z

Our testcases had their own implementation of GetTempFile with the feature of a temporary file with a choosen suffix. Merging this into GetTempFile lets us drop this duplicate and hence test more our code rather than testing our helpers for test implementation. And then hashsums_test had another implementation… and extracttar wasn't even trying to use a real tempfile… one GetTempFile to rule them all! That also ensures that these tempfiles are created in a temporary directory rather than the current directory which is a nice touch and tries a little harder to clean up those tempfiles.

Parse records including empty tag names correctly

2020-02-26T17:12:18Z

No sensible file should include these, but even insensible files do not gain unfair advantages with it as this parser does not deal with security critical files before they haven't passed other checks like signatures or hashsums. The problem is that the parser accepts and parses empty tag names correctly, but does not store the data parsed which will effect later passes over the data resulting e.g. in the following tag containing the name and value of the previous (empty) tag, its own tagname and its own value or a crash due to an attempt to access invalid memory depending on who passes over the data and what is done with it. This commit fixes both, the incidient of the crash reported by Anatoly Trosinenko who reproduced it via apt-sortpkgs: | $ cat /tmp/Packages-null | 0: | PACKAGE:0 | | : | PACKAGE: | | PACKAGE:: | $ apt-sortpkgs /tmp/Packages-null and the deeper parsing issue shown by the included testcase. Reported-By: Anatoly Trosinenko References: 8710a36a01c0cb1648926792c2ad05185535558e

Remove code tagged APT_PKG_590, add some missing includes

2020-02-18T11:48:38Z

Remove all code scheduled to be removed after 5.90, and fix files to include files they previously got from hashes.h including more headers.

patterns: test for empty terms, reject them

2020-02-03T11:55:54Z

Correctly stop parsing short form arguments on space, also on ?

2020-02-03T11:55:54Z

we have to stop parsing on space so that things like ~ramd64 | ~rall work correctly. aptitude does not stop parsing on ?, but we'll do as it gets very confusing otherwise if you write stuff like ~ramd64?name(foo), and it resolves to ?and(?architecture(amd64?name), (foo))...

patterns: Implement parsing of (...) groups

2020-02-03T11:55:54Z

Implement | as or

2020-02-03T11:55:54Z

patterns: Parse sequence of patterns as ?and

2020-02-03T11:55:54Z

patterns: Allow bare words only in arguments

2020-02-03T11:55:54Z

patterns: Implement unary !

2020-02-03T11:55:54Z