- 25 Jan, 2019 8 commits
-
-
Chris Lamb authored
-
Chris Lamb authored
Gbp-Dch: ignore
-
Chris Lamb authored
Gbp-Dch: ignore
-
Chris Lamb authored
Gbp-Dch: ignore
-
Chris Lamb authored
Really fix summary generation code to match the "WIP" entry in the changelog after moving to gbp-dch(1).
-
The command for autopackage tests runs all tag-related tests but none of the 'scripts'. This behavior is maintained going forward. Removes reference to all suites except 'tags'. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
All four test suites related to Lintian tags are now found in the suite 'tags'. Moves the test specifications to their new locations. Test specifications can be located in any subdirectory of t/tags. From now on, it is possible to group them in more detailed ways, for example by Lintian check. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
In the future, all tests checking Lintian's tag functionality belong to suite 'tags'. Undefine the other suites for tests, changes, debs and source. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org>
-
- 24 Jan, 2019 17 commits
-
-
Ensure that "explicit skeletons" are now required, the first step to make tests freely groupable. (MR: !132)
-
Also updates the reference to a tests output data, including the log, in ../debian/test-out. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Remove suite references from the internal harness tests and explicitly declare the use of skeletons. Gbp-Dch: Ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Uses the new and more meaningful name of the same skeleton. Was previously known as default in suite source. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Uses the new and more meaningful name of the same skeleton. Was previously known as default in suite changes. Gbp-Dch: Ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Uses the new and more meaningful name of the same skeleton. Was previously known as default in suite debs. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Uses the new and more meaningful name of the same skeleton. Was previously known as default in suite tests. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Uses the new and more meaningful name of the same skeleton. Was previously known as non-native in suite tests. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Uses the new and more meaningful name of the same skeleton. Was previously known as builder-only in suite tests. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
The selection of skeletons was previously suite-specific. Remove all references to suites from the test runner, except for the suites 'tags' and 'scripts'. Also look for skeletons in a non-suite specific location. Also no longer store the suite in the 'desc' file recorded in a test's work directory. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Move all skeleton files to the common, non-suite specific folder one level above. Also give them meaningful names that are different from the overloaded 'default'. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
The default skeleton is 'default'. That was sufficient when skeletons were specific to suites: Each suite had a default skeleton. When the tag-related tests no longer have suites, those skeletons require more meaninful names. The name of each such skeleton will then have to be mentioned in any test specification that uses it. Removes the declaration of a default skeleton. Gbp-Dch: ignore Signed-off-by:
Chris Lamb <lamby@debian.org> -
Chris Lamb authored
Locate and process .buildinfo files if mentioned in a .changes file; previously it was only examined if explicitly referenced. Thanks to James Clarke. (Closes: #920228)
-
libcrypt.so.1 (part of glibc) used to provide a set of functions that allowed raw use of the DES block cipher. Encryption with DES is now inherently insecure (any use of single DES can be broken by brute force) and therefore these functions were made inaccessible to newly linked programs in glibc 2.28. Any program in the archive that unconditionally uses one of these functions will FTBFS with glibc 2.28. Any program that conditionally uses one of these functions may be falling back to an internal implementation of DES and therefore have a security bug. Therefore, I propose this new lintian check, which detects use of the functions that were removed from libcrypt.so.1. In sid it is arguably redundant (since any program that would fail this check will FTBFS anyway) but applying this check to the stable archive would detect programs that were conditionally using these functions and need to be audited for security bugs. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Chris Lamb authored
Gbp-Dch: Ignore
-
Chris Lamb authored
-
Chris Lamb authored
-
- 22 Jan, 2019 2 commits
-
-
Chris Lamb authored
If the changelog entry is missing a maintainer (eg. " -- <missing>"), don't assume that it is an NMU. (Closes: #920184)
-
Chris Lamb authored
Avoid some "Use of initialized value" warnings when the changelog entry contains a "-- <blank>" maintainer line. (re. #920184) Gbp-Dch: ignore
-
- 21 Jan, 2019 13 commits
-
-
Paul Wise authored
-
Paul Wise authored
-
Chris Lamb authored
-
Chris Lamb authored
-
Chris Lamb authored
Gbp-Dch: ignore
-
Chris Lamb authored
Gbp-Dch: ignore
-
Chris Lamb authored
Gbp-Dch: ignore
-
Chris Lamb authored
-
Chris Lamb authored
Implement package-contains-python-in-incorrect-dir using data/files/fnames as we already have Python checks there. (re. #919979) Gbp-Dch: ignore
-
Chris Lamb authored
Use "state cache" vs "state-cache" consistently between source and binary packages when printing warnings during report generation.
-
Chris Lamb authored
-
Chris Lamb authored
-
Chris Lamb authored
<Grinnz> multi-dimensional data structures are just data structures with refs to other data structures. those refs can already be copied around however you want, you don't need to take a ref to them. Gbp-Dch: Ignore
-