- 01 Jan, 2019 7 commits
-
-
Chris Lamb authored
-
Chris Lamb authored
-
Chris Lamb authored
Apply a patch series from Felix Lechner to ensure the tests pass under groff 1.22.4-1. (Closes: #917752, #917844)
-
New versions of groff-base have changed their output format. One test required adjustment, but will not pass with older versions. Imposes a minimum version of groff-base for this test as a prerequisite.
-
The man page that triggers the tag is included by another man page. Such errors were apparently not detected before groff-base 1.22.4-1. Adding tag here. The tag format is a bit longer. It includes a partial path to the included file. This test should be split up into several smaller tests.
-
groff-base 1.22.4-1 prepends the name of the input file to any error output. In Lintian, the messages look like '<standard input>:' for regular man pages, and 'man/man3/XXX.3.gz:' if the error occurs in a file included from elsewhere. For standard input, skip the information to match the old tag output. For files included from elsewhere, the extra information may be useful; it is retained. If a file included from elsewhere causes an error but is also tested on its own, the new behavior results in two similar tags being issued that point out the same error (it would not be a duplicate). Perhaps the tag should not be skipped for included files.
-
In its error output, groff-base 1.22.4-1 seems to delimit the left side of macro names with a single quote instead of an apostrophe, which was used until now. Adjust the expected tags in the test 'manpage-general' and a line in check/manpages.pm that skips some such lines. It may be worthwhile to send a note to all maintainers of packages that override such a tag. The change is hard to see and can be frustrating to find.
-
- 31 Dec, 2018 1 commit
-
-
When running Lintian under sbuild or pbuilder, the call to gpg errors out with: gpg: Fatal: can't create directory '/sbuild-nonexistent/.gnupg': No such file or directory Provides a writable temporary home directory to gpg to avoid the error. Signed-off-by:
Chris Lamb <lamby@debian.org>
-
- 30 Dec, 2018 16 commits
-
-
Chris Lamb authored
Apply a patch series from Felix Lechner to update the Debhelper compatibility level in tests. (MR: !111)
-
Someone with more gcc experience may be able to correct the debug format for the two tests. For now, dwz was non-essential. It was disabled. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Parameterizes the custom debian/control.in and updates a tag. Signed-off-by:
Chris Lamb <lamby@debian.org> -
The functionality of debian/conffiles was disabled in debhelper 12. Moves the file into DEBIAN manually before building the deb. Signed-off-by:
Chris Lamb <lamby@debian.org> -
A python-related test now requires the explicit declaration of a build system. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Increases the compat level in the test for debhelper's experimental version to 13, which is a level above the one currently recommended. Signed-off-by:
Chris Lamb <lamby@debian.org> -
The option dh_clean -k was completely removed in compat 12. The test warning about its obsolescence requires compat 11 or lower. The alternative would be to remove the test. For another test, the command passing with '--' to dh_installdebs fails. This likewise seems to be a new debhelper restriction. It also requires compat 11. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Some tags issue compat levels as part of their message. Those tags are fixed here. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Some tests do not use templates and also require this change to avoid the tag 'skip-systemd-native-flag-missing-pre-depends'. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Many tests throw 'skip-systemd-native-flag-missing-pre-depends' without this. Signed-off-by:
Chris Lamb <lamby@debian.org> -
With some luck, this component will not have to be updated again when the debhelper compat level changes. Signed-off-by:
Chris Lamb <lamby@debian.org> -
An enviroment variable allows the use of the value in separate test runners and spawned executables. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Works better than the two other routines nearby, which determine either the debhelper version required in Lintian's own debian/control or the debhelper version installed on the system. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Chris Lamb authored
Was a premature attempt at releasing but I left this commit locally which I then accidentally pushed in e0871779. This reverts commit b9f9ad46.
-
Together with Dh-Compat-Level: 12 in 'desc', the default builder supplies the correct dependency via: Default-Build-Depends: debhelper (>= {$dh_compat_level}~) The tag complaining about lack of a version is no longer issued. Removing it from the list of expected tags. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Chris Lamb authored
-
- 28 Dec, 2018 8 commits
-
-
Chris Lamb authored
-
Chris Lamb authored
Include the debhelper-compat method of setting the compatibility level in a number of tag descriptions. (Closes: #917345)
-
Signed-off-by:
Chris Lamb <lamby@debian.org> -
Signed-off-by:
Chris Lamb <lamby@debian.org> -
Signed-off-by:
Chris Lamb <lamby@debian.org> -
Signed-off-by:
Chris Lamb <lamby@debian.org> -
Signed-off-by:
Chris Lamb <lamby@debian.org> -
Paul Wise authored
-
- 27 Dec, 2018 3 commits
-
-
Chris Lamb authored
Bump the recommended and experimental debhelper compat levels to 12 and 13 respectfully. (Closes: #917344)
-
Chris Lamb authored
-
Chris Lamb authored
Clarify that "Build-Depends-Package" lines should start in column 1 of the file and not be indented to align with the symbols themselves.
-
- 26 Dec, 2018 1 commit
-
-
Paul Wise authored
-
- 25 Dec, 2018 2 commits
-
-
Following-on from #916095, tag "invariant sections" modified by upstream versions as non official. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Chris Lamb authored
Update dependency-on-python-version-marked-for-end-of-life's description to mention that a commented override would be useful. (Closes: #917264)
-
- 24 Dec, 2018 2 commits
-
-
For repeated runs, it was until now necessary to run 'rm -rf debian/test-out'. Otherwise, unfilled templates would pollute the test working directories. They would trigger unexpected Lintian tags such as 'unknown-file-in-debian-source format.in'. Such polluting templates are now deleted and no longer impede repeated runs. Signed-off-by:
Chris Lamb <lamby@debian.org> -
Chris Lamb authored
Avoid false-positives in changelog-file-missing-explicit-entry when uploading updates to updates such as "1.2-3+nmu2" or "1.2-3deb8u2".
-