Bug#935706: lintian: Make tag certainty a programmatic assessment
Hi Axel, [Thanks for the cc. I am on the list.] On Fri, Mar 20, 2020 at 4:57 PM Axel Beckert wrote: > > JFTR: I strongly disagree. The Certainty was a very helpful decision > helper for Lintian users who had a gut feeling about a lintian-emitted > tag being a false positive by seeing how reliable the author of the > tag suspected it's, well, Certainty — especially for heuristic checks. You are right. A lot of thought went into those ratings. There is a good likelihood we will revisit the issue. For example, we may implement an automatic tag reliability ranking based on the proportion of overrides in the archive. > > My impression is that the classification system is more fine-grained > > than the users of Lintian care about, At the same time, I agree even more strongly with Russ's sentiment. The system had too many levels. It was a burden to maintain. For each new tag, we had to look up what the result would be (i.e. error, warning, etc.). The new system is more direct. As one of the active Lintian maintainers, I don't think the concept of certainty is gone at all. First off, the fields are still around ( I am not sure about pkg-perl-tools). We just weakened the effect on each tag's everyday appearance—apparently based on a partial consensus, my apologies. In summary, I felt the concept of tag *certainty* fueled contentious (and unfortunately unfounded) debates over tag appearance. I am glad those days are gone. Going forward, the *reliability* of Lintian's heuristics, on the other hand, will become an important feature. It is an honest thing to do, and required for an expert system like Lintian. Kind regards Felix Lechner
Bug#935706: lintian: Make tag certainty a programmatic assessment
Hi again, taking Felix Lechner into Cc. Axel Beckert wrote: > to my dismay I discovered that Lintian's Certainty feature has been > removed. In addition to that I find it very bold to not even mention that removal explicitly in the debian/changelog entry: * Use the "Severity" field in tags to determine their display prominence directly. (Closes: #935706) I only found out about that removal via the bug report/fix against pkg-perl-tools. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#935706: lintian: Make tag certainty a programmatic assessment
Hi,
to my dismay I discovered that Lintian's Certainty feature has been
removed.
Chris Lamb wrote:
> Controversial opinion
Indeed controversial.
> the "certainty" of tags is of no actionable benefit to either the
> users of Lintian or its developers and should be removed.
JFTR: I strongly disagree. The Certainty was a very helpful decision
helper for Lintian users who had a gut feeling about a lintian-emitted
tag being a false positive by seeing how reliable the author of the
tag suspected it's, well, Certainty — especially for heuristic checks.
With removing the Certainty you basically removed the possibility to
write Lintian checks which are known to not be or in some cases even
never can be 100% perfect.
One such check is for example library-package-name-for-application and
application-not-library which had the Certainty: wildguess as there's
no chance to be really precise. (Which probably is also the reason why
there are still tons of true positives out there, mostly python
packages.
> a) fixing the problem
> c) adding an override the issue
The Certainty field was a good help to decide between these two..
> the "certainty" is highly subjective and only appears
> to result in annoying our users when there is a legitimate false-
> positive and lintian is patronisingly and obstinately telling them it
> is "certain".
I disagree here, too. If it's a fixable false-positive, especially for
"Certainty: certain", then it should be fixed. If it's not fixable,
the Certainty should be downgraded.
Russ Allbery wrote:
> The problem, though, was that in some cases the bug would be a serious
> Policy violation *if Lintian were right*, but Lintian was often wrong.
> Certainty was an attempt to somehow capture that so that Lintian could
> express to the maintainer "this is a serious problem with your package if
> what I found is true, but there's a good chance this is a false positive."
This.
> From my perspective, the certainty concept is more useful for the
> wild-guess end of the spectrum, where it's conveying useful
> information ("this would be a serious problem, but we're bad at
> reliably detecting it").
This.
> In practice, I don't think this has happened.
It happened. These fields were used.
> My impression is that the classification system is more fine-grained
> than the users of Lintian care about,
Definitely not.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#954335: lintian confuses Fortran and Modula-2 modules
Hi, > gzip: stdout: Broken pipe This commit reduces the program error to a misidentification: https://salsa.debian.org/lintian/lintian/-/commit/5b0bff88afd220ecee71897fa0cb2227f14d10dc The search should also be restricted to expected locations for gfortran modules. Please do not close the bug just yet! Kind regards Felix Lechner
lintian_2.57.0~bpo9+1_amd64.changes ACCEPTED into stretch-backports->backports-policy, stretch-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Mar 2020 09:51:51 + Source: lintian Binary: lintian Built-For-Profiles: nocheck Architecture: source all Version: 2.57.0~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Description: lintian- Debian package checker Closes: 929729 950115 950117 950238 950453 951513 952529 952539 953036 953099 953857 Changes: lintian (2.57.0~bpo9+1) stretch-backports; urgency=medium . * Rebuild for stretch-backports. . lintian (2.57.0) unstable; urgency=medium . * Summary of tag changes: + Added: - absolute-symbolic-link-target-in-source - bash-completion-with-hashbang - binary-is-wrong-architecture - copyright-excludes-files-in-native-package - explicit-default-in-package-type - new-package-uses-date-based-version-number - upstream-metadata-missing-bug-tracking - upstream-metadata-missing-repository + Removed: - pkg-config-references-unknown-shared-library . [ Chris Lamb ] * Check for debian/upstream/metadata files without bug tracking information and upstream repository locations. (Closes: #950115, #950117) * Check for new packages that use a date-based versioning scheme (eg. MMDD-1) without a 0~ suffix. (Closes: #953036) * Don't report about using a newer Standards-Version when uploading to backports. * Clarify the error message when tags are not covered in the testsuite. . [ Felix Lechner ] * Also analyse Ubuntu's automatic debug packages which have the non-standard suffix .ddeb. (Closes: #951513, #953857) * Parse newline escapes correctly in md5sum files. (Closes: #929729) * Remove tag pkg-config-references-unknown-shared-library; outside of Lintian's purview. (Closes: #953099) * Rewrite check for compressed gzip archives; print modification time of first member. (Re: #762105) * Add a new tag called bash-completion-with-hashbang. * Add tag and check for absolute symbolic link targets in source trees. * Reduce severity and mark PE32+ related tag experimental; set security features for test binary explicitly. * Offer to calibrate test results for literal matching strategy. * Strip leading slashes from absolute paths for file names and hard link targets. * Issue a tag when the Excluded-Files field is present in copyright within native packages. * Display Lintian's command-line options in the process table (eg. top(1), etc.) . [ Paul Wise ] * Add several spelling corrections. . [ Xavier Guimard ] * Extend NodeJS checks to modules that use naming such as "@foo/bar". . lintian (2.56.0) unstable; urgency=medium . * Summary of tag changes: + Added: - nodejs-lock-file . [ Chris Lamb ] * Check for NO_START and FOO_NO_START etc. in /etc/default scripts. (Closes: #950238) * Deprecate debhelper compat level 9. (Closes: #950453) . [ Felix Lechner ] * Fix POD markup in man page; indent level caused literal display of formatting codes. (Closes: #952529) * Fix the selection of classification tags with -T command line switch. (Closes: #952539) * Use JSON::MaybeXS instead of plain JSON in the NodeJS checks. * Remove and replace the open_gz, open and file_contents subroutines from File::Path. * Provide method for all ->descendants in File::Path and use it, retiring breadth-first recursion. . [ Xavier Guimard ] * Check if NodeJS modules install lock files. Checksums-Sha1: 08f2dc3bd45b01c86bf7a2793bbe85d48c2f9c83 4156 lintian_2.57.0~bpo9+1.dsc b6fe66613206ede06365ee5c8cb0929a76caeaa4 1922568 lintian_2.57.0~bpo9+1.tar.xz 082d198e909ec7ecd5c508ef4c1b25989804e2db 1309734 lintian_2.57.0~bpo9+1_all.deb 26a998fad4fb6c2b460d76aa20986d4e5c5ab9d7 6366 lintian_2.57.0~bpo9+1_amd64.buildinfo Checksums-Sha256: ae1053258c6a1032c927189cd827106c754a2d0b3295058aa0e5cbb6c2dd40e7 4156 lintian_2.57.0~bpo9+1.dsc 0afc6cfc48d4dc55cef67bf2912191772c095da50cca1705986b9630b5fcdcd5 1922568 lintian_2.57.0~bpo9+1.tar.xz 56812ab44d57b78c78003c62b2ea73e33536cb5cb95355325a6db50cbf201d4b 1309734 lintian_2.57.0~bpo9+1_all.deb 2174496d023493950f18116fc8d5a4f46ffc820f063bfe2715511384232af50a 6366 lintian_2.57.0~bpo9+1_amd64.buildinfo Files: 58ce05aba6940d885bd506c41fbdae7a 4156 devel optional lintian_2.57.0~bpo9+1.dsc 85902af34bbfc6cab915a6706c6beb4f 1922568 devel optional lintian_2.57.0~bpo9+1.tar.xz 57d6df82398f9aa8b533acfe2d0cdf96 1309734 devel optional lintian_2.57.0~bpo9+1_all.deb a88f6bdf1aa64932780961f1be1e3ad8 6366 devel optional lintian_2.57.0~bpo9+1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl50koEACgkQHpU+J9Qx Hlja3g/+LrfYcq63SksOAUtFxgkxFZIT7wFAUhDO64trXSxxhPGDeAZ73PW6LQa2 ax46l9dudbREAsHGdLC2Pb8a8mMS9fsupvt0zfM5CZsVfiifB5u+yEcf6B5rGg8C
Bug#954341: lintian: What's going on with "field-too-long Installed-Build-Depends"?
Hi, On Fri, Mar 20, 2020 at 8:03 AM Mattia Rizzolo wrote: > > field-too-long was added to prevent silliness in the archive. As such, it > only makes sense for binary control fields and .dsc, nothing else. Why should fields in buildinfo and changes files be treated differently from fields elsewhere? > ie. "sub binary" → "sub always" ? I could have used 'sub installable' to examine only deb and udeb, but I think it makes sense to examine fields everywhere. Fields that are allowed to be long can be exempt. The broader issue of duplicate tags across group components, which is related to the true issue here, will be addressed when tags are filtered and prioritized for printing. At that point, tags that point to the origin of something will suppress tags that merely received a value by copying. > E: pkg-perl-tools buildinfo: field-too-long Installed-Build-Depends (11190 > chars > 5000) I will disable the tag for this particular buildinfo field in the near future. Kind regards Felix Lechner
Processed: Bug#954338 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #954338 [src:lintian] lintian: Remove some '' annotations Added tag(s) pending. -- 954338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954341: lintian: What's going on with "field-too-long Installed-Build-Depends"?
Hi all, > Totally lintian is wrong here, imho I think this was a regression in: https://salsa.debian.org/lintian/lintian/commit/14fa5a80bbbf9e8b691bd9b61382d15b33e98b3d ie. "sub binary" → "sub always" ? Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#954341: lintian: What's going on with "field-too-long Installed-Build-Depends"?
Totally lintian is wrong here, imho. field-too-long was added to prevent silliness in the archive. As such, it only makes sense for binary control fields and .dsc, nothing else. On Fri, 20 Mar 2020, 3:21 pm gregor herrmann, wrote: > Package: lintian > Version: 2.58.0 > Severity: minor > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > With lintian 2.58.0 I got, for the first time, this error: > > E: pkg-perl-tools buildinfo: field-too-long Installed-Build-Depends (11190 > chars > 5000) > > I have no idea what to do with this information, and I've never seen > this tag before. Either lintian has changed and is right, then Some > Other Tool™ needs a fix, or lintian has changed and is wrong, or > something else :) > > > Cheers, > gregor > > > For reference, the .buildinfo file has: > > Installed-Build-Depends: > autoconf (= 2.69-11.1), > automake (= 1:1.16.1-4), > autopoint (= 0.19.8.1-10), > autotools-dev (= 20180224.1), > base-files (= 11), > base-passwd (= 3.5.47), > bash (= 5.0-6), > binutils (= 2.34-5), > binutils-common (= 2.34-5), > binutils-x86-64-linux-gnu (= 2.34-5), > bsdmainutils (= 11.1.2+b1), > bsdutils (= 1:2.34-0.1), > build-essential (= 12.8), > bzip2 (= 1.0.8-2), > ca-certificates (= 20190110), > coreutils (= 8.30-3+b1), > cpp (= 4:9.2.1-3.1), > cpp-9 (= 9.3.0-3), > dash (= 0.5.10.2-6), > debconf (= 1.5.73), > debhelper (= 12.9), > debianutils (= 4.9.1), > dh-autoreconf (= 19), > dh-strip-nondeterminism (= 1.6.3-2), > dictionaries-common (= 1.28.1), > diffstat (= 1.63-1), > diffutils (= 1:3.7-3), > dpkg (= 1.19.7), > dpkg-dev (= 1.19.7), > dwz (= 0.13-5), > emacsen-common (= 3.0.4), > fdisk (= 2.34-0.1), > file (= 1:5.38-4), > findutils (= 4.7.0-1), > g++ (= 4:9.2.1-3.1), > g++-9 (= 9.3.0-3), > gcc (= 4:9.2.1-3.1), > gcc-10-base (= 10-20200312-2), > gcc-9 (= 9.3.0-3), > gcc-9-base (= 9.3.0-3), > gettext (= 0.19.8.1-10), > gettext-base (= 0.19.8.1-10), > git (= 1:2.26.0~rc2-1), > git-man (= 1:2.26.0~rc2-1), > gpg (= 2.2.19-3), > gpgconf (= 2.2.19-3), > grep (= 3.4-1), > groff-base (= 1.22.4-4), > gzip (= 1.10-2), > hostname (= 3.23), > iamerican (= 3.4.00-8), > ienglish-common (= 3.4.00-8), > init-system-helpers (= 1.57), > intltool-debian (= 0.35.0+20060710.5), > ispell (= 3.4.00-8), > libacl1 (= 2.2.53-6), > libalgorithm-c3-perl (= 0.10-1), > libalgorithm-diff-perl (= 1.19.03-2), > libapt-pkg-perl (= 0.1.36+b3), > libapt-pkg6.0 (= 2.0.0), > libarchive-zip-perl (= 1.68-1), > libasan5 (= 9.3.0-3), > libassuan0 (= 2.5.3-7), > libatomic1 (= 10-20200312-2), > libattr1 (= 1:2.4.48-5), > libaudit-common (= 1:2.8.5-2), > libaudit1 (= 1:2.8.5-2+b1), > libb-hooks-endofscope-perl (= 0.24-1), > libb-hooks-op-check-perl (= 0.22-1+b2), > libbinutils (= 2.34-5), > libblkid1 (= 2.34-0.1), > libboolean-perl (= 0.46-1), > libbrotli1 (= 1.0.7-6), > libbsd0 (= 0.10.0-1), > libbz2-1.0 (= 1.0.8-2), > libc-bin (= 2.30-2), > libc-dev-bin (= 2.30-2), > libc6 (= 2.30-2), > libc6-dev (= 2.30-2), > libcache-lru-perl (= 0.04-1), > libcap-ng0 (= 0.7.9-2.1+b2), > libcapture-tiny-perl (= 0.48-1), > libcarp-assert-more-perl (= 1.20-1), > libcarp-assert-perl (= 0.21-1), > libcc1-0 (= 10-20200312-2), > libcgi-pm-perl (= 4.46-1), > libclass-c3-perl (= 0.34-1), > libclass-data-inheritable-perl (= 0.08-3), > libclass-inspector-perl (= 1.36-1), > libclass-method-modifiers-perl (= 2.13-1), > libclass-singleton-perl (= 1.5-1), > libclass-tiny-perl (= 1.006-1), > libclass-xsaccessor-perl (= 1.19-3+b3), > libclone-choose-perl (= 0.010-1), > libclone-perl (= 0.43-2), > libcom-err2 (= 1.45.5-2), > libcommon-sense-perl (= 3.74-2+b8), > libconfig-model-perl (= 2.138-2), > libconst-fast-perl (= 0.014-1), > libcontextual-return-perl (= 0.004014-2), > libconvert-binhex-perl (= 1.125-1), > libcroco3 (= 0.6.13-1), > libcrypt-dev (= 1:4.4.15-1), > libcrypt1 (= 1:4.4.15-1), > libctf-nobfd0 (= 2.34-5), > libctf0 (= 2.34-5), > libcurl3-gnutls (= 7.68.0-1), > libdata-optlist-perl (= 0.110-1), > libdatetime-format-dateparse-perl (= 0.05-2), > libdatetime-locale-perl (= 1:1.25-1), > libdatetime-perl (= 2:1.52-1), > libdatetime-timezone-perl (= 1:2.38-1+2019c), > libdb5.3 (= 5.3.28+dfsg1-0.6), > libdebconfclient0 (= 0.251), > libdebhelper-perl (= 12.9), > libdevel-callchecker-perl (= 0.008-1+b1), > libdevel-size-perl (= 0.83-1+b1), > libdevel-stacktrace-perl (= 2.0400-1), > libdigest-hmac-perl (= 1.03+dfsg-2), > libdpkg-perl (= 1.19.7), > libdynaloader-functions-perl (= 0.003-1), > libelf1 (= 0.176-1.1), > libemail-date-format-perl (= 1.005-1), > libemail-valid-perl (= 1.202-1), > libencode-locale-perl (= 1.05-1), > liberror-perl (= 0.17029-1), > libeval-closure-perl (= 0.14-1), > libexception-class-perl (= 1.44-1), > libexpat1 (= 2.2.9-1), > libexporter-tiny-perl (= 1.002001-1), > libfcgi-perl (= 0.79-1), > libfdisk1 (= 2.34-0.1), > libffi7 (= 3.3-3), > libfile-basedir-perl (= 0.08-1), >
Bug#954341: lintian: What's going on with "field-too-long Installed-Build-Depends"?
Package: lintian Version: 2.58.0 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 With lintian 2.58.0 I got, for the first time, this error: E: pkg-perl-tools buildinfo: field-too-long Installed-Build-Depends (11190 chars > 5000) I have no idea what to do with this information, and I've never seen this tag before. Either lintian has changed and is right, then Some Other Tool™ needs a fix, or lintian has changed and is wrong, or something else :) Cheers, gregor For reference, the .buildinfo file has: Installed-Build-Depends: autoconf (= 2.69-11.1), automake (= 1:1.16.1-4), autopoint (= 0.19.8.1-10), autotools-dev (= 20180224.1), base-files (= 11), base-passwd (= 3.5.47), bash (= 5.0-6), binutils (= 2.34-5), binutils-common (= 2.34-5), binutils-x86-64-linux-gnu (= 2.34-5), bsdmainutils (= 11.1.2+b1), bsdutils (= 1:2.34-0.1), build-essential (= 12.8), bzip2 (= 1.0.8-2), ca-certificates (= 20190110), coreutils (= 8.30-3+b1), cpp (= 4:9.2.1-3.1), cpp-9 (= 9.3.0-3), dash (= 0.5.10.2-6), debconf (= 1.5.73), debhelper (= 12.9), debianutils (= 4.9.1), dh-autoreconf (= 19), dh-strip-nondeterminism (= 1.6.3-2), dictionaries-common (= 1.28.1), diffstat (= 1.63-1), diffutils (= 1:3.7-3), dpkg (= 1.19.7), dpkg-dev (= 1.19.7), dwz (= 0.13-5), emacsen-common (= 3.0.4), fdisk (= 2.34-0.1), file (= 1:5.38-4), findutils (= 4.7.0-1), g++ (= 4:9.2.1-3.1), g++-9 (= 9.3.0-3), gcc (= 4:9.2.1-3.1), gcc-10-base (= 10-20200312-2), gcc-9 (= 9.3.0-3), gcc-9-base (= 9.3.0-3), gettext (= 0.19.8.1-10), gettext-base (= 0.19.8.1-10), git (= 1:2.26.0~rc2-1), git-man (= 1:2.26.0~rc2-1), gpg (= 2.2.19-3), gpgconf (= 2.2.19-3), grep (= 3.4-1), groff-base (= 1.22.4-4), gzip (= 1.10-2), hostname (= 3.23), iamerican (= 3.4.00-8), ienglish-common (= 3.4.00-8), init-system-helpers (= 1.57), intltool-debian (= 0.35.0+20060710.5), ispell (= 3.4.00-8), libacl1 (= 2.2.53-6), libalgorithm-c3-perl (= 0.10-1), libalgorithm-diff-perl (= 1.19.03-2), libapt-pkg-perl (= 0.1.36+b3), libapt-pkg6.0 (= 2.0.0), libarchive-zip-perl (= 1.68-1), libasan5 (= 9.3.0-3), libassuan0 (= 2.5.3-7), libatomic1 (= 10-20200312-2), libattr1 (= 1:2.4.48-5), libaudit-common (= 1:2.8.5-2), libaudit1 (= 1:2.8.5-2+b1), libb-hooks-endofscope-perl (= 0.24-1), libb-hooks-op-check-perl (= 0.22-1+b2), libbinutils (= 2.34-5), libblkid1 (= 2.34-0.1), libboolean-perl (= 0.46-1), libbrotli1 (= 1.0.7-6), libbsd0 (= 0.10.0-1), libbz2-1.0 (= 1.0.8-2), libc-bin (= 2.30-2), libc-dev-bin (= 2.30-2), libc6 (= 2.30-2), libc6-dev (= 2.30-2), libcache-lru-perl (= 0.04-1), libcap-ng0 (= 0.7.9-2.1+b2), libcapture-tiny-perl (= 0.48-1), libcarp-assert-more-perl (= 1.20-1), libcarp-assert-perl (= 0.21-1), libcc1-0 (= 10-20200312-2), libcgi-pm-perl (= 4.46-1), libclass-c3-perl (= 0.34-1), libclass-data-inheritable-perl (= 0.08-3), libclass-inspector-perl (= 1.36-1), libclass-method-modifiers-perl (= 2.13-1), libclass-singleton-perl (= 1.5-1), libclass-tiny-perl (= 1.006-1), libclass-xsaccessor-perl (= 1.19-3+b3), libclone-choose-perl (= 0.010-1), libclone-perl (= 0.43-2), libcom-err2 (= 1.45.5-2), libcommon-sense-perl (= 3.74-2+b8), libconfig-model-perl (= 2.138-2), libconst-fast-perl (= 0.014-1), libcontextual-return-perl (= 0.004014-2), libconvert-binhex-perl (= 1.125-1), libcroco3 (= 0.6.13-1), libcrypt-dev (= 1:4.4.15-1), libcrypt1 (= 1:4.4.15-1), libctf-nobfd0 (= 2.34-5), libctf0 (= 2.34-5), libcurl3-gnutls (= 7.68.0-1), libdata-optlist-perl (= 0.110-1), libdatetime-format-dateparse-perl (= 0.05-2), libdatetime-locale-perl (= 1:1.25-1), libdatetime-perl (= 2:1.52-1), libdatetime-timezone-perl (= 1:2.38-1+2019c), libdb5.3 (= 5.3.28+dfsg1-0.6), libdebconfclient0 (= 0.251), libdebhelper-perl (= 12.9), libdevel-callchecker-perl (= 0.008-1+b1), libdevel-size-perl (= 0.83-1+b1), libdevel-stacktrace-perl (= 2.0400-1), libdigest-hmac-perl (= 1.03+dfsg-2), libdpkg-perl (= 1.19.7), libdynaloader-functions-perl (= 0.003-1), libelf1 (= 0.176-1.1), libemail-date-format-perl (= 1.005-1), libemail-valid-perl (= 1.202-1), libencode-locale-perl (= 1.05-1), liberror-perl (= 0.17029-1), libeval-closure-perl (= 0.14-1), libexception-class-perl (= 1.44-1), libexpat1 (= 2.2.9-1), libexporter-tiny-perl (= 1.002001-1), libfcgi-perl (= 0.79-1), libfdisk1 (= 2.34-0.1), libffi7 (= 3.3-3), libfile-basedir-perl (= 0.08-1), libfile-find-rule-perl (= 0.34-1), libfile-homedir-perl (= 1.004-1), libfile-listing-perl (= 6.04-1), libfile-sharedir-perl (= 1.116-2), libfile-slurp-perl (= .29-1), libfile-stripnondeterminism-perl (= 1.6.3-2), libfile-which-perl (= 1.23-1), libfont-ttf-perl (= 1.06-1), libfuture-perl (= 0.43-1), libgcc-9-dev (= 9.3.0-3), libgcc-s1 (= 10-20200312-2), libgcc1 (= 1:10-20200312-2), libgcrypt20 (= 1.8.5-5), libgdbm-compat4 (= 1.18.1-5), libgdbm6 (= 1.18.1-5), libgit-repository-perl (= 1.324-1), libgit-version-compare-perl (= 1.004-1),
Bug#954338: lintian: Remove some '' annotations
Source: lintian Version: 2.58.0 Severity: important Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 lintian fails to build with (DEB_BUILD_OPTIONS=nocheck and) DEB_BUILD_PROFILES=nocheck because some packages marked as '' in Build-Depends are actually needed for building. Trivial patch: #v+ - --- a/debian/control +++ b/debian/control @@ -39,7 +39,7 @@ Build-Depends: libdigest-sha-perl , libdpkg-perl , libemail-valid-perl , - - libfile-basedir-perl , + libfile-basedir-perl, libfile-find-rule-perl , libfont-ttf-perl , libhtml-parser-perl , @@ -52,7 +52,7 @@ Build-Depends: libmoo-perl , libmoox-aliases-perl , libnamespace-clean-perl , - - libpath-tiny-perl , + libpath-tiny-perl, libpod-coverage-trustpod-perl , libsereal-decoder-perl , libsereal-encoder-perl , #v- Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl50yUxfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZclRAAh2M99Kw+3cDskOFhJ7dtFFu/8XSfC/U1vcPsqbZTqhE/IorBq7hc1SSQ +/1TO0viYAIqyfkarZjQdiIYww/eX1xqbuK3Lh4YiLMNxlDHU1CGyJCv6JvNjuYP fruez74kDS9+NFsooW3g7W11tPPYrrb3Zx0EEC6CQqzECXWdfFD76Z+TqMZ+1sEw b8JXGBFeWNZOg92ClINFvmvASVb7LpBRoNQOpkB4DEhcLLgABz8gRZ6vwhekz7Db kMFvs7DmeL5bzXgHGPwBggF/BfpjHYyV4OXfT2fQYGC89WN7PbuqFw7Z4cE6mJVb /jsF4Isf8CYqLRkZfvBdi8sPZzYnNOYzAP1N7TnezjQRwLq0m2+cb2y7IJs+9ugT ni6l9NStqt81c2JXaSKrBAsucPnaEdBxQgcWPljxCihRFhNeS5/3spijh4W0j9JI SUQCAF56qYU3ad9eZV+0WZfrOWNQJTH1aOu0AbIR16zvQffSkrIFtRdpQjIBYd3f YZOniKadPvoKLcds27t4S/KzMpd0Mx7xYj3URt3lzw8GKskpeTc7xvJKyVH09pDD NUuba7woNzIqbTm5zVUcG+5M+e91hD441PBpekW8l9EqT4fpP378rOLm3v3xEFpD xhua8RgPp/LBtwGDjRBX4GSfnEAa65Ys+5vm9+ZTv/wwGYIbeek= =tvPo -END PGP SIGNATURE-
Bug#954335: lintian confuses Fortran and Modula-2 modules
On 3/20/20 2:15 PM, Felix Lechner wrote: > Hi Matthias, > > On Fri, Mar 20, 2020 at 5:57 AM Matthias Klose wrote: >> >> so please differentiate between Fortran and Modula-2 modules. > > I have had some issues differentiating gfortran modules (#948033). In > which folders do they usually reside, please? > > Also, why are they not all named md.gz, as in libcoarrays-dev? CCing Alastair. He's behind the Fortran policies. Currently Modula-2 modules can only be found in the lib*gm2 packages. Nothing else is packaged using Modula-2.
Bug#954335: lintian confuses Fortran and Modula-2 modules
Hi Matthias, On Fri, Mar 20, 2020 at 5:57 AM Matthias Klose wrote: > > so please differentiate between Fortran and Modula-2 modules. I have had some issues differentiating gfortran modules (#948033). In which folders do they usually reside, please? Also, why are they not all named md.gz, as in libcoarrays-dev? Kind regards Felix Lechner
Bug#954335: lintian confuses Fortran and Modula-2 modules
Package: lintian running lintian on a gcc-10 build, I see gzip: stdout: Broken pipe gzip: /tmp/temp-lintian-lab-i1Mvu3Lp4j/pool/g/gcc-10/libgm2-10-dev_10-20200320-1_amd64_binary/unpacked/usr/lib/gcc/x86_64-linux-gnu/10/m2/m2cor/Debug.mod: not in gzip format and then continues with: libgm2-10-dev: ESC]8;;https://lintian.debian.org/tags/gfortran-module-does-not-declare-version.htmlESC\gfortran-module-does-not-declare-versionESC]8;;ESC \ usr/lib/gcc/x86_64-linux-gnu/10/m2/m2cor/Debug.mod so please differentiate between Fortran and Modula-2 modules.
Processed: Please adjust tag severities
Processing control commands: > reassign -1 pkg-perl-tools Bug #954331 [lintian] lintian: coercion for "original_severity" failed: Unknown tag severity minor Bug reassigned from package 'lintian' to 'pkg-perl-tools'. No longer marked as found in versions lintian/2.58.0. Ignoring request to alter fixed versions of bug #954331 to the same values previously set -- 954331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954331: Please adjust tag severities
Control: reassign -1 pkg-perl-tools Hi, > Jonas Smedegaard wrote: > > Upgrading to version 2.58.0 of lintian renders it totally unusable: That is not correct. Lintian just fails to work with pkg-perl-tools. > Lintian::Tag::Info::original_severity(Lintian::Tag::Info=HASH(0x565295307a18), > "minor") called at /usr/share/perl5/Lintian/Tag/Info.pm line 182 > Lintian::Tag::Info::load(Lintian::Tag::Info=HASH(0x565295307a18), > "/usr/share/lintian/tags/pkg-perl/nonteam-testsuite-header.desc") called at > /usr/share > > Lintian::Tag::Info::original_severity(Lintian::Tag::Info=HASH(0x55627b1c2e28), > "minor") called at /usr/share/perl5/Lintian/Tag/Info.pm line 182 > Lintian::Tag::Info::load(Lintian::Tag::Info=HASH(0x55627b1c2e28), > "/usr/share/lintian/tags/pkg-perl/nonteam-testsuite-header.desc") called at > /usr/share The meaning of the Severity field in tag declarations has changed. Please modify the tags in pkg-perl-tools accordingly. For details, please see #935706 or this and the surrounding commits: https://salsa.debian.org/lintian/lintian/-/commit/e1e12f7f4190ab5718e2317dd7e466d8b56d6043 Kind regards Felix Lechner
Bug#954331: lintian: coercion for "original_severity" failed: Unknown tag severity minor
Package: lintian
Version: 2.58.0
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upgrading to version 2.58.0 of lintian renders it totally unusable:
$ lintian *_amd64.changes --no-tag-display-limit
coercion for "original_severity" failed: Unknown tag severity minor
Lintian::Tag::Info::__ANON__("minor") called at (eval 123) line 28
eval {...} called at (eval 123) line 27
Lintian::Tag::Info::original_severity(Lintian::Tag::Info=HASH(0x565295307a18),
"minor") called at /usr/share/perl5/Lintian/Tag/Info.pm line 182
Lintian::Tag::Info::load(Lintian::Tag::Info=HASH(0x565295307a18),
"/usr/share/lintian/tags/pkg-perl/nonteam-testsuite-header.desc") called at
/usr/share/perl5/Lintian/Profile.pm line 224
Lintian::Profile::load(Lintian::Profile=HASH(0x565294d47398), undef,
ARRAY(0x5652925edde0), HASH(0x565292972ec0)) called at /usr/bin/lintian line 217
dplint::load_profile(undef) called at
/usr/share/lintian/commands/lintian.pm line 712
eval {...} called at /usr/share/lintian/commands/lintian.pm line 712
main::main() called at /usr/bin/lintian line 46
eval {...} called at /usr/bin/lintian line 46
main::__ANON__("/usr/share/lintian/commands/lintian.pm") called at
/usr/bin/lintian line 115
dplint::run_tool("/usr/bin/lintian", "lintian") called at /usr/bin/lintian
line 294
dplint::main() called at /usr/bin/lintian line 378
jonas@auryn:~/public_debian/pool-sid/OFFICIAL/monero$ lintian *_amd64.changes
--no-tag-display-limit
coercion for "original_severity" failed: Unknown tag severity minor
Lintian::Tag::Info::__ANON__("minor") called at (eval 123) line 28
eval {...} called at (eval 123) line 27
Lintian::Tag::Info::original_severity(Lintian::Tag::Info=HASH(0x55627b1c2e28),
"minor") called at /usr/share/perl5/Lintian/Tag/Info.pm line 182
Lintian::Tag::Info::load(Lintian::Tag::Info=HASH(0x55627b1c2e28),
"/usr/share/lintian/tags/pkg-perl/nonteam-testsuite-header.desc") called at
/usr/share/perl5/Lintian/Profile.pm line 224
Lintian::Profile::load(Lintian::Profile=HASH(0x55627ad428b8), undef,
ARRAY(0x5562785e8de0), HASH(0x55627896e290)) called at /usr/bin/lintian line 217
dplint::load_profile(undef) called at
/usr/share/lintian/commands/lintian.pm line 712
eval {...} called at /usr/share/lintian/commands/lintian.pm line 712
main::main() called at /usr/bin/lintian line 46
eval {...} called at /usr/bin/lintian line 46
main::__ANON__("/usr/share/lintian/commands/lintian.pm") called at
/usr/bin/lintian line 115
dplint::run_tool("/usr/bin/lintian", "lintian") called at /usr/bin/lintian
line 294
dplint::main() called at /usr/bin/lintian line 378
NB! Below was computed after I downgraded to 2.57.0.
- Jonas
- -- System Information:
Debian Release: bullseye/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1,
'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.0-rc5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_DIE, TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8),
LANGUAGE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lintian depends on:
ii binutils 2.34-5
ii bzip21.0.8-2
ii diffstat 1.63-1
ii dpkg 1.19.7
ii dpkg-dev 1.19.7
ii file 1:5.38-4
ii gettext 0.19.8.1-10
ii gpg 2.2.19-3
ii intltool-debian 0.35.0+20060710.5
ii libapt-pkg-perl 0.1.36+b3
ii libarchive-zip-perl 1.68-1
ii libcapture-tiny-perl 0.48-1
ii libcgi-pm-perl 4.46-1
ii libclass-xsaccessor-perl 1.19-3+b3
ii libclone-perl0.43-2
ii libdevel-size-perl 0.83-1+b1
ii libdpkg-perl 1.19.7
ii libemail-valid-perl 1.202-1
ii libfile-basedir-perl 0.08-1
ii libfile-find-rule-perl 0.34-1
ii libfont-ttf-perl 1.06-1
ii libio-async-loop-epoll-perl 0.20-1
ii libio-async-perl 0.75-1
ii libipc-run-perl 20180523.0-2
ii libjson-maybexs-perl 1.004000-1
ii liblist-compare-perl 0.53-1
ii liblist-moreutils-perl 0.416-1+b5
ii libmoo-perl 2.003006-1
ii libmoox-aliases-perl 0.001006-1
ii libnamespace-clean-perl 0.27-1
ii libpath-tiny-perl0.108-1
ii libsereal-decoder-perl 4.011+ds-1
ii libsereal-encoder-perl 4.011+ds-1
ii libtext-levenshtein-perl 0.13-1
ii libtimedate-perl 2.3200-1
ii libtry-tiny-perl 0.30-1
ii libtype-tiny-perl1.008001-2
ii liburi-perl 1.76-2
ii libxml-libxml-perl
lintian_2.58.0_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Mar 2020 09:56:18 + Source: lintian Architecture: source Version: 2.58.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Closes: 924449 935706 954146 954149 954224 Changes: lintian (2.58.0) unstable; urgency=medium . * Summary of tag changes: + Added: - executable-in-usr-lib . [ Felix Lechner ] * Fix interaction between two gzip timestamp tags. (Closes: #954146) * In terminal output, print overrides in a subdued color. (Closes: #954224) * Add tag and check for executables in /usr/lib, which violates the FHS. (Closes: #954149) * Use the "Severity" field in tags to determine their display prominence directly. (Closes: #935706) * Remove temporary directories for pools when they are no longer needed. (Closes: #924449) Checksums-Sha1: 930d1b308ceda3c977dd09e0c08f41e00ef17267 4141 lintian_2.58.0.dsc 1a9f1426f89f3d2833ea50cb9011f35db5a6c35a 1896132 lintian_2.58.0.tar.xz d28038f2076e7fdccbf54111f470197ba0519fee 16171 lintian_2.58.0_amd64.buildinfo Checksums-Sha256: c546e17e0907714bde02d12e5e22955cf1f1a8ce07da8919bd11ef8efb22c4cd 4141 lintian_2.58.0.dsc 711e41367ed3682f4b57861194d79137f66bbfafb1160ce9adb13f3ddc78ed8f 1896132 lintian_2.58.0.tar.xz 2d34ef131add0ae1f070904cdeed58c1b7b5cc36116009e27ac75f736576e465 16171 lintian_2.58.0_amd64.buildinfo Files: 959e61e13b34c8fec36075b366f8c739 4141 devel optional lintian_2.58.0.dsc a98441fdc819b1409b0b4502a2db2717 1896132 devel optional lintian_2.58.0.tar.xz 907c13a7a5ffdbc38a01aa58d508b075 16171 devel optional lintian_2.58.0_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl50mNEACgkQHpU+J9Qx Hlg+yxAAxWgfoWB9IbPUwto71/1uYaeI/kQ22Nn48fakwFMN2UwoFK4ENzMPR4Xd uFMfxQvKobm0WlBGWx8hQsVegVdLewIaGwrywfJZv1NCRft1krMHm5HIYALlr6jV i1baeWu1MQLo0faxeriWYcboihZ7T1hbr2A5vyM+GZYjBgLd/jKGNx9VRBJe//ia i2N84fRCpFnW7iwrOLRJZLzkHi0Il0zi/OBD2ChDyNjJWPBajfLUISMtoctL0CqY tW0Cf/QiBhMw3fvrTLY5c+AsEbR+0i1HCK7I7r5uQ2sCqcRzUv1oPDHKNpFjS/Zn n3kRzmpBgmACud+x2WJucVXPbqLoQz3EfnoGLRklPYGl6bdFWxruPm8knhHmO8Ol 8tr8NFEcpPI2uhfiKUj8oepUiVCl+cKOSakzjjtlK/X17g6dhT6vrxe29g3vU6Vy Xk3jT+5qpjAyrpxYes0x2YB0Vjg9h8GIBAcqFd+VayR/YYpbIxbLpIwDHwK4QrsB 6LFEI01W3mXPfFaCOfP4iiMDsTr+3VQWXEVmkJd4Rn2Ko5k9he0eIZdnBTSaaZOv T5Ul8SO0yVhGr9p2GJW/skyovMP1N+z7watnPiEcVCOFys7AjRpbgEViAkH+uS19 ILeGhNGseikHfB2ZwYnv55furjkhvek+/a8R1AZ71YadIx1RCVI= =KOYb -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#954146: marked as done (Lintian: false-positive gzip-file-is-not-multi-arch-same-safe)
Your message dated Fri, 20 Mar 2020 10:37:19 + with message-id and subject line Bug#954146: fixed in lintian 2.58.0 has caused the Debian Bug report #954146, regarding Lintian: false-positive gzip-file-is-not-multi-arch-same-safe to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian Version: 2.57.0 Severity: important Hi, Lintian issues gzip-file-is-not-multi-arch-same-safe although gzip is invoked with '-9nf'. $ apt source libutempter $ cd libutempter-1.1.6/ && dpkg-buildpackage -us -uc $ lintian libutempter*.changes > E: libutempter-dev: gzip-file-is-not-multi-arch-same-safe > usr/share/doc/libutempter-dev/changelog.Debian.gz > E: libutempter-dev: gzip-file-is-not-multi-arch-same-safe > usr/share/man/man3/utempter.3.gz > E: libutempter0: gzip-file-is-not-multi-arch-same-safe > usr/share/doc/libutempter0/changelog.Debian.gz Lintian 2.55 does not issue this error tag. --- End Message --- --- Begin Message --- Source: lintian Source-Version: 2.58.0 Done: Chris Lamb We believe that the bug you reported is fixed in the latest version of lintian, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Mar 2020 09:56:18 + Source: lintian Architecture: source Version: 2.58.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Closes: 924449 935706 954146 954149 954224 Changes: lintian (2.58.0) unstable; urgency=medium . * Summary of tag changes: + Added: - executable-in-usr-lib . [ Felix Lechner ] * Fix interaction between two gzip timestamp tags. (Closes: #954146) * In terminal output, print overrides in a subdued color. (Closes: #954224) * Add tag and check for executables in /usr/lib, which violates the FHS. (Closes: #954149) * Use the "Severity" field in tags to determine their display prominence directly. (Closes: #935706) * Remove temporary directories for pools when they are no longer needed. (Closes: #924449) Checksums-Sha1: 930d1b308ceda3c977dd09e0c08f41e00ef17267 4141 lintian_2.58.0.dsc 1a9f1426f89f3d2833ea50cb9011f35db5a6c35a 1896132 lintian_2.58.0.tar.xz d28038f2076e7fdccbf54111f470197ba0519fee 16171 lintian_2.58.0_amd64.buildinfo Checksums-Sha256: c546e17e0907714bde02d12e5e22955cf1f1a8ce07da8919bd11ef8efb22c4cd 4141 lintian_2.58.0.dsc 711e41367ed3682f4b57861194d79137f66bbfafb1160ce9adb13f3ddc78ed8f 1896132 lintian_2.58.0.tar.xz 2d34ef131add0ae1f070904cdeed58c1b7b5cc36116009e27ac75f736576e465 16171 lintian_2.58.0_amd64.buildinfo Files: 959e61e13b34c8fec36075b366f8c739 4141 devel optional lintian_2.58.0.dsc a98441fdc819b1409b0b4502a2db2717 1896132 devel optional lintian_2.58.0.tar.xz 907c13a7a5ffdbc38a01aa58d508b075 16171 devel optional lintian_2.58.0_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl50mNEACgkQHpU+J9Qx Hlg+yxAAxWgfoWB9IbPUwto71/1uYaeI/kQ22Nn48fakwFMN2UwoFK4ENzMPR4Xd uFMfxQvKobm0WlBGWx8hQsVegVdLewIaGwrywfJZv1NCRft1krMHm5HIYALlr6jV i1baeWu1MQLo0faxeriWYcboihZ7T1hbr2A5vyM+GZYjBgLd/jKGNx9VRBJe//ia i2N84fRCpFnW7iwrOLRJZLzkHi0Il0zi/OBD2ChDyNjJWPBajfLUISMtoctL0CqY tW0Cf/QiBhMw3fvrTLY5c+AsEbR+0i1HCK7I7r5uQ2sCqcRzUv1oPDHKNpFjS/Zn n3kRzmpBgmACud+x2WJucVXPbqLoQz3EfnoGLRklPYGl6bdFWxruPm8knhHmO8Ol 8tr8NFEcpPI2uhfiKUj8oepUiVCl+cKOSakzjjtlK/X17g6dhT6vrxe29g3vU6Vy Xk3jT+5qpjAyrpxYes0x2YB0Vjg9h8GIBAcqFd+VayR/YYpbIxbLpIwDHwK4QrsB 6LFEI01W3mXPfFaCOfP4iiMDsTr+3VQWXEVmkJd4Rn2Ko5k9he0eIZdnBTSaaZOv T5Ul8SO0yVhGr9p2GJW/skyovMP1N+z7watnPiEcVCOFys7AjRpbgEViAkH+uS19 ILeGhNGseikHfB2ZwYnv55furjkhvek+/a8R1AZ71YadIx1RCVI= =KOYb -END PGP SIGNATURE End Message ---
Bug#954224: marked as done (lintian: please dim/color --show-overrides)
Your message dated Fri, 20 Mar 2020 10:37:19 + with message-id and subject line Bug#954224: fixed in lintian 2.58.0 has caused the Debian Bug report #954224, regarding lintian: please dim/color --show-overrides to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian Version: 2.57.0 Severity: wishlist Hi! When reviewing packages, I find myself hardly ever look at overridden tags, as it's tedious to mentally weed them out when reading lintian output. I think it would be great if you could visually mark them. For example, using \e[2m (half-bright) would be nice -- and work on the vast majority of terminals. So would using \e[30;1m (bright black). The former looks like: printf ' W: libfoo-bar: \e[33ma-real-warning-tag\e[39m not enough cats E: lib-foo-bar: \e[31ma-real-error-tag\e[39m too many dogs \e[2mN: N: see Bug #954146 N: O: libsane-dev: \e[31mgzip-file-is-not-multi-arch-same-safe\e[39m xxx.gz\e[22m\n ' Meow! -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-rc6-00085-ge6fd0e58416e (SMP w/64 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages lintian depends on: ii binutils 2.34-4 ii bzip21.0.8-2 ii diffstat 1.63-1 ii dpkg 1.20.0 ii dpkg-dev 1.20.0 ii file 1:5.38-4 ii gettext 0.19.8.1-10 ii gpg 2.2.19-3 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.36+b3 ii libarchive-zip-perl 1.68-1 ii libcapture-tiny-perl 0.48-1 ii libcgi-pm-perl 4.46-1 ii libclass-xsaccessor-perl 1.19-3+b3 ii libclone-perl0.43-2 ii libdevel-size-perl 0.83-1+b1 ii libdpkg-perl 1.20.0 ii libemail-valid-perl 1.202-1 ii libfile-basedir-perl 0.08-1 ii libfile-find-rule-perl 0.34-1 ii libfont-ttf-perl 1.06-1 ii libio-async-loop-epoll-perl 0.20-1 ii libio-async-perl 0.75-1 ii libipc-run-perl 20180523.0-2 ii libjson-maybexs-perl 1.004000-1 ii liblist-compare-perl 0.53-1 ii liblist-moreutils-perl 0.416-1+b5 ii libmoo-perl 2.003006-1 ii libmoox-aliases-perl 0.001006-1 ii libnamespace-clean-perl 0.27-1 ii libpath-tiny-perl0.108-1 ii libsereal-decoder-perl 4.011+ds-1 ii libsereal-encoder-perl 4.011+ds-1 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3200-1 ii libtry-tiny-perl 0.30-1 ii libtype-tiny-perl1.008001-2 ii liburi-perl 1.76-2 ii libxml-libxml-perl 2.0134+dfsg-2 ii libyaml-libyaml-perl 0.81+repack-1 ii man-db 2.9.1-1 ii patchutils 0.3.4-2+b1 ii perl [libdigest-sha-perl]5.30.0-9 ii t1utils 1.41-3 ii xz-utils 5.2.4-1+b1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b6 Versions of packages lintian suggests: pn binutils-multiarch ii libhtml-parser-perl3.72-5 pn libtext-template-perl -- no debconf information --- End Message --- --- Begin Message --- Source: lintian Source-Version: 2.58.0 Done: Chris Lamb We believe that the bug you reported is fixed in the latest version of lintian, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format:
Bug#954149: marked as done (Please add check for executable in /usr/lib/)
Your message dated Fri, 20 Mar 2020 10:37:19 + with message-id and subject line Bug#954149: fixed in lintian 2.58.0 has caused the Debian Bug report #954149, regarding Please add check for executable in /usr/lib/ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian Version: 2.57.0 Severity: wishlist Hi, Now that the debian policy supports FHS 3.0 (since 4.1.5) and the FHS 3.0 describes /usr/libexec[0], it would be nice to have (all?) the executables installed in /usr/lib/ to /usr/libexec. Several packages have already migrated, could a (pedentic?) test be added? Kind regards, Laurent Bigonville [0] http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages lintian depends on: ii binutils 2.34-4 ii bzip21.0.8-2 ii diffstat 1.63-1 ii dpkg 1.19.7 ii dpkg-dev 1.19.7 ii file 1:5.38-4 ii gettext 0.19.8.1-10 ii gpg 2.2.19-3 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.36+b3 ii libarchive-zip-perl 1.68-1 ii libcapture-tiny-perl 0.48-1 ii libcgi-pm-perl 4.46-1 ii libclass-xsaccessor-perl 1.19-3+b3 ii libclone-perl0.43-2 ii libdevel-size-perl 0.83-1+b1 ii libdpkg-perl 1.19.7 ii libemail-valid-perl 1.202-1 ii libfile-basedir-perl 0.08-1 ii libfile-find-rule-perl 0.34-1 ii libfont-ttf-perl 1.06-1 ii libio-async-loop-epoll-perl 0.20-1 ii libio-async-perl 0.75-1 ii libipc-run-perl 20180523.0-2 ii libjson-maybexs-perl 1.004000-1 ii liblist-compare-perl 0.53-1 ii liblist-moreutils-perl 0.416-1+b5 ii libmoo-perl 2.003006-1 ii libmoox-aliases-perl 0.001006-1 ii libnamespace-clean-perl 0.27-1 ii libpath-tiny-perl0.108-1 ii libsereal-decoder-perl 4.011+ds-1 ii libsereal-encoder-perl 4.011+ds-1 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3200-1 ii libtry-tiny-perl 0.30-1 ii libtype-tiny-perl1.008001-2 ii liburi-perl 1.76-2 ii libxml-libxml-perl 2.0134+dfsg-2 ii libyaml-libyaml-perl 0.81+repack-1 ii man-db 2.9.1-1 ii patchutils 0.3.4-2+b1 ii perl [libdigest-sha-perl]5.30.0-9 ii t1utils 1.41-3 ii xz-utils 5.2.4-1+b1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b6 Versions of packages lintian suggests: pn binutils-multiarch ii libhtml-parser-perl3.72-5 ii libtext-template-perl 1.58-1 -- no debconf information --- End Message --- --- Begin Message --- Source: lintian Source-Version: 2.58.0 Done: Chris Lamb We believe that the bug you reported is fixed in the latest version of lintian, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Mar 2020 09:56:18 + Source: lintian Architecture: source Version: 2.58.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By:
Bug#935706: marked as done (lintian: Make tag certainty a programmatic assessment)
Your message dated Fri, 20 Mar 2020 10:37:19 +
with message-id
and subject line Bug#935706: fixed in lintian 2.58.0
has caused the Debian Bug report #935706,
regarding lintian: Make tag certainty a programmatic assessment
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
935706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Hi,
A tag's certainty is currently fixed but actually depends on the
programmatic circumstances of its issuance. Some heuristics are better
than others. The 'tag' command should offer alternatives, which then
result in different alert levels (error, warning, info, and so on).
An example are tags that depend on native or non-native sources. For a
source package, the determination is easy. For an installation package
(*.deb) there is no way to know for sure, but the version number may
offer a guess:
For source packages, the tag would be certain (from a pending version
of checks/source-changelog.pm):
my $maintainer_revision = $latest_version->maintainer_revision;
(full version for native)
tag->certain 'hyphen-in-native-debian-changelog-version',
$maintainer_revision
if $info->native && $maintainer_revision =~ qr/-/;
while for installation packages (*.deb) it would not:
my $version = $latest_entry->{Version}; (literal version string)
tag->possible 'hyphen-in-native-debian-changelog-version', $version
if [not sure this can be determined];
The first use would produce an error; the second, a warning.
For the new mechanism to work, overrides should exclude the alert
level. They would function more like the universal tag format used in
the test suite.
Kind regards,
Felix Lechner
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.58.0
Done: Chris Lamb
We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 935...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lamb (supplier of updated lintian package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 20 Mar 2020 09:56:18 +
Source: lintian
Architecture: source
Version: 2.58.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers
Changed-By: Chris Lamb
Closes: 924449 935706 954146 954149 954224
Changes:
lintian (2.58.0) unstable; urgency=medium
.
* Summary of tag changes:
+ Added:
- executable-in-usr-lib
.
[ Felix Lechner ]
* Fix interaction between two gzip timestamp tags.
(Closes: #954146)
* In terminal output, print overrides in a subdued color.
(Closes: #954224)
* Add tag and check for executables in /usr/lib, which violates the FHS.
(Closes: #954149)
* Use the "Severity" field in tags to determine their display prominence
directly. (Closes: #935706)
* Remove temporary directories for pools when they are no longer needed.
(Closes: #924449)
Checksums-Sha1:
930d1b308ceda3c977dd09e0c08f41e00ef17267 4141 lintian_2.58.0.dsc
1a9f1426f89f3d2833ea50cb9011f35db5a6c35a 1896132 lintian_2.58.0.tar.xz
d28038f2076e7fdccbf54111f470197ba0519fee 16171 lintian_2.58.0_amd64.buildinfo
Checksums-Sha256:
c546e17e0907714bde02d12e5e22955cf1f1a8ce07da8919bd11ef8efb22c4cd 4141
lintian_2.58.0.dsc
711e41367ed3682f4b57861194d79137f66bbfafb1160ce9adb13f3ddc78ed8f 1896132
lintian_2.58.0.tar.xz
2d34ef131add0ae1f070904cdeed58c1b7b5cc36116009e27ac75f736576e465 16171
lintian_2.58.0_amd64.buildinfo
Files:
959e61e13b34c8fec36075b366f8c739 4141 devel optional lintian_2.58.0.dsc
a98441fdc819b1409b0b4502a2db2717 1896132 devel optional lintian_2.58.0.tar.xz
907c13a7a5ffdbc38a01aa58d508b075 16171 devel optional
lintian_2.58.0_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl50mNEACgkQHpU+J9Qx
Hlg+yxAAxWgfoWB9IbPUwto71/1uYaeI/kQ22Nn48fakwFMN2UwoFK4ENzMPR4Xd
uFMfxQvKobm0WlBGWx8hQsVegVdLewIaGwrywfJZv1NCRft1krMHm5HIYALlr6jV
i1baeWu1MQLo0faxeriWYcboihZ7T1hbr2A5vyM+GZYjBgLd/jKGNx9VRBJe//ia
Bug#924449: marked as done (lintian: Periodic "out of disk space" errors from lindsay.d.o)
Your message dated Fri, 20 Mar 2020 10:37:19 +
with message-id
and subject line Bug#924449: fixed in lintian 2.58.0
has caused the Debian Bug report #924449,
regarding lintian: Periodic "out of disk space" errors from lindsay.d.o
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
924449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.10.0
Severity: important
We seem to be getting regular "out of disk space" errors on
lindsay.d.o after resuming the archive-wide processing.
I found the following in the [log file]. We see the following 3 issues
(AFAICT):
* linux
* python3-zaqar-ui
* Closing of the perf log ("/srv/lintian.debian.org/logs/lintian-perf.log")
This might have been the underlying root cause for #890873, it may be
a regression with the rewrite of L::Unpacker, or maybe unpacking Linux
simply takes more disk space that we have.
AFAICT, lintian correctly cleans up old packages during the run.
I.e. we are not accumulating disk usage from previous packages in the
run.
For reference, we currently have 32GB disk available for lintian ("all
inclusive"). About 23GB of that is available for checking with our
current usage for reports and stats.
Thanks,
~Niels
[log file]:
"""
N: Starting on group linux/4.19.20-1
N: Unpacking packages in group linux/4.19.20-1
gzip: stdout: No space left on device
gzip:
gzip: stdout: No space left on device
stdout: No space left on device
mkdir: cannot create directory
'/srv/lintian.debian.org/scratch/temp-lintian-lab-HPiNntNduD/pool/l/linux/linux-image-4.19.0-3-rt-amd64-unsigned_4.19.20-1_amd64_binary
/strings/lib/modules/4.19.0-3-rt-amd64/kernel/drivers/misc': No space left on
device
gzip: stdout: No space left on device
gzip: stdout: No space left on device
mkdir -p
/srv/lintian.debian.org/scratch/temp-lintian-lab-HPiNntNduD/pool/l/linux/linux-image-4.19.0-3-rt-amd64-unsigned_4.19.20-1_amd64_binary/strings/lib/modules/4.19.0-3-rt-amd64/kernel/drivers/misc
failed: 0
gzip: stdout: No space left on device
command failed with error code 1 at
/srv/lintian.debian.org/lintian/lib/Lintian/Command.pm line 344.
Lintian::Command::reap(HASH(0x55ea04300b40)) called at
/srv/lintian.debian.org/lintian/collection/objdump-info line 81
Lintian::coll::objdump_info::collect("linux-image-4.19.0-3-rt-686-pae-dbg",
"binary", "/srv/lintian.debian.org/scratch/temp-lintian-lab-HPiNntNduD/p"...)
called at /srv/lintian.debian.org/lintian/lib/Lintian/CollScript.pm line 242
Lintian::CollScript::collect(Lintian::CollScript=HASH(0x55ea043df688),
"linux-image-4.19.0-3-rt-686-pae-dbg", "binary",
"/srv/lintian.debian.org/scratch/temp-lintian-lab-HPiNntNduD/p"...) called at
/srv/lintian.debian.org/lintian/lib/Lintian/Unpacker.pm line 412
eval {...} called at
/srv/lintian.debian.org/lintian/lib/Lintian/Unpacker.pm line 412
Lintian::Unpacker::__ANON__() called at
/usr/share/perl5/IO/Async/Loop.pm line 1943
eval {...} called at /usr/share/perl5/IO/Async/Loop.pm line 1943
IO::Async::Loop::fork(IO::Async::Loop::Poll=HASH(0x55ea0436bfa0),
"code", CODE(0x55ea24cdc728), "on_exit", CODE(0x55ea313c8288)) called at
/srv/lintian.debian.org/lintian/lib/Lintian/Unpacker.pm line 461
eval {...} called at
/srv/lintian.debian.org/lintian/lib/Lintian/Unpacker.pm line 385
Lintian::Unpacker::__ANON__("objdump-info-binary:linux-image-4.19.0-3-rt-686-pae-dbg/4.19."...,
Lintian::CollScript=HASH(0x55ea043df688),
Lintian::Lab::Entry=HASH(0x55ea02c950f8),
Lintian::DepMap::Properties=HASH(0x55ea303ced58)) called at
/srv/lintian.debian.org/lintian/lib/Lintian/Unpacker.pm line 453
Lintian::Unpacker::__ANON__(2475, 0) called at
/usr/share/perl5/IO/Async/Loop.pm line 2604
IO::Async::Loop::_reap_children(HASH(0x55ea03de6920)) called at
/usr/share/perl5/IO/Async/Loop.pm line 2663
IO::Async::Loop::__ANON__() called at /usr/share/perl5/IO/Async/Loop.pm
line 805
IO::Async::Loop::__ANON__() called at /usr/share/perl5/IO/Async/OS.pm
line 577
IO::Async::OS::_Base::__ANON__(IO::Async::Handle=HASH(0x55ea05c557a8))
called at /usr/share/perl5/IO/Async/Loop/Poll.pm line 172
IO::Async::Loop::Poll::post_poll(IO::Async::Loop::Poll=HASH(0x55ea0436bfa0))
called at /usr/share/perl5/IO/Async/Loop/Poll.pm line 279
IO::Async::Loop::Poll::loop_once(IO::Async::Loop::Poll=HASH(0x55ea0436bfa0),
undef) called at /usr/share/perl5/IO/Async/Loop.pm line 524
Processing of lintian_2.58.0_amd64.changes
lintian_2.58.0_amd64.changes uploaded successfully to localhost along with the files: lintian_2.58.0.dsc lintian_2.58.0.tar.xz lintian_2.58.0_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
lintian_2.57.0~bpo10+1_amd64.changes ACCEPTED into buster-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Mar 2020 09:49:33 + Source: lintian Binary: lintian Built-For-Profiles: nocheck Architecture: source all Version: 2.57.0~bpo10+1 Distribution: buster-backports Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Description: lintian- Debian package checker Closes: 929729 950115 950117 950238 950453 951513 952529 952539 953036 953099 953857 Changes: lintian (2.57.0~bpo10+1) buster-backports; urgency=medium . * Rebuild for buster-backports. . lintian (2.57.0) unstable; urgency=medium . * Summary of tag changes: + Added: - absolute-symbolic-link-target-in-source - bash-completion-with-hashbang - binary-is-wrong-architecture - copyright-excludes-files-in-native-package - explicit-default-in-package-type - new-package-uses-date-based-version-number - upstream-metadata-missing-bug-tracking - upstream-metadata-missing-repository + Removed: - pkg-config-references-unknown-shared-library . [ Chris Lamb ] * Check for debian/upstream/metadata files without bug tracking information and upstream repository locations. (Closes: #950115, #950117) * Check for new packages that use a date-based versioning scheme (eg. MMDD-1) without a 0~ suffix. (Closes: #953036) * Don't report about using a newer Standards-Version when uploading to backports. * Clarify the error message when tags are not covered in the testsuite. . [ Felix Lechner ] * Also analyse Ubuntu's automatic debug packages which have the non-standard suffix .ddeb. (Closes: #951513, #953857) * Parse newline escapes correctly in md5sum files. (Closes: #929729) * Remove tag pkg-config-references-unknown-shared-library; outside of Lintian's purview. (Closes: #953099) * Rewrite check for compressed gzip archives; print modification time of first member. (Re: #762105) * Add a new tag called bash-completion-with-hashbang. * Add tag and check for absolute symbolic link targets in source trees. * Reduce severity and mark PE32+ related tag experimental; set security features for test binary explicitly. * Offer to calibrate test results for literal matching strategy. * Strip leading slashes from absolute paths for file names and hard link targets. * Issue a tag when the Excluded-Files field is present in copyright within native packages. * Display Lintian's command-line options in the process table (eg. top(1), etc.) . [ Paul Wise ] * Add several spelling corrections. . [ Xavier Guimard ] * Extend NodeJS checks to modules that use naming such as "@foo/bar". . lintian (2.56.0) unstable; urgency=medium . * Summary of tag changes: + Added: - nodejs-lock-file . [ Chris Lamb ] * Check for NO_START and FOO_NO_START etc. in /etc/default scripts. (Closes: #950238) * Deprecate debhelper compat level 9. (Closes: #950453) . [ Felix Lechner ] * Fix POD markup in man page; indent level caused literal display of formatting codes. (Closes: #952529) * Fix the selection of classification tags with -T command line switch. (Closes: #952539) * Use JSON::MaybeXS instead of plain JSON in the NodeJS checks. * Remove and replace the open_gz, open and file_contents subroutines from File::Path. * Provide method for all ->descendants in File::Path and use it, retiring breadth-first recursion. . [ Xavier Guimard ] * Check if NodeJS modules install lock files. Checksums-Sha1: 036278d52e973da51fe2cde7167058fe7ec37f0b 4173 lintian_2.57.0~bpo10+1.dsc a7b9617c42c733b629f149d1e6a3d0fc5fcc3e51 1927272 lintian_2.57.0~bpo10+1.tar.xz 16567c40269ea9724c8f86de7c406bddb72f9187 1303560 lintian_2.57.0~bpo10+1_all.deb 1240b32e9fe6fdfe816cd4fcb9da1a29ad0f002d 6042 lintian_2.57.0~bpo10+1_amd64.buildinfo Checksums-Sha256: 80750267401ccddca3644e91b33bca6006b61abf6949c59754f1db2f0d483ac9 4173 lintian_2.57.0~bpo10+1.dsc c3971abce1f2fc02daf62e6d6805e440d6962d09b30e728d237aa8130b6fb572 1927272 lintian_2.57.0~bpo10+1.tar.xz 42a7cc2bcc487581bbd53f9c2853950a9a597d407dcd7c289103710166767f0d 1303560 lintian_2.57.0~bpo10+1_all.deb 0298a4ff51b09ca0dddf0f124f7d38787a4f8ca52233635e6433ced0400e440f 6042 lintian_2.57.0~bpo10+1_amd64.buildinfo Files: b118b8e939c6d438769fc8c1ad70697c 4173 devel optional lintian_2.57.0~bpo10+1.dsc ed23726fb7dfedef30d9d2192c7138bc 1927272 devel optional lintian_2.57.0~bpo10+1.tar.xz fee5b3f1dc5d8129b47562cb0f6595bb 1303560 devel optional lintian_2.57.0~bpo10+1_all.deb 5b9e0899c41638e5f9e33d09170a90b8 6042 devel optional lintian_2.57.0~bpo10+1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl50kfkACgkQHpU+J9Qx HljVmBAAuLgrZCc7BYkEqS9f6sCryifN60D9dDsCCX8L4NCHG3ccsafijANwO1xt
lintian_2.57.0~bpo9+1_amd64.changes ACCEPTED into stretch-backports->backports-policy
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Mar 2020 09:51:51 + Source: lintian Binary: lintian Built-For-Profiles: nocheck Architecture: source all Version: 2.57.0~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Description: lintian- Debian package checker Closes: 929729 950115 950117 950238 950453 951513 952529 952539 953036 953099 953857 Changes: lintian (2.57.0~bpo9+1) stretch-backports; urgency=medium . * Rebuild for stretch-backports. . lintian (2.57.0) unstable; urgency=medium . * Summary of tag changes: + Added: - absolute-symbolic-link-target-in-source - bash-completion-with-hashbang - binary-is-wrong-architecture - copyright-excludes-files-in-native-package - explicit-default-in-package-type - new-package-uses-date-based-version-number - upstream-metadata-missing-bug-tracking - upstream-metadata-missing-repository + Removed: - pkg-config-references-unknown-shared-library . [ Chris Lamb ] * Check for debian/upstream/metadata files without bug tracking information and upstream repository locations. (Closes: #950115, #950117) * Check for new packages that use a date-based versioning scheme (eg. MMDD-1) without a 0~ suffix. (Closes: #953036) * Don't report about using a newer Standards-Version when uploading to backports. * Clarify the error message when tags are not covered in the testsuite. . [ Felix Lechner ] * Also analyse Ubuntu's automatic debug packages which have the non-standard suffix .ddeb. (Closes: #951513, #953857) * Parse newline escapes correctly in md5sum files. (Closes: #929729) * Remove tag pkg-config-references-unknown-shared-library; outside of Lintian's purview. (Closes: #953099) * Rewrite check for compressed gzip archives; print modification time of first member. (Re: #762105) * Add a new tag called bash-completion-with-hashbang. * Add tag and check for absolute symbolic link targets in source trees. * Reduce severity and mark PE32+ related tag experimental; set security features for test binary explicitly. * Offer to calibrate test results for literal matching strategy. * Strip leading slashes from absolute paths for file names and hard link targets. * Issue a tag when the Excluded-Files field is present in copyright within native packages. * Display Lintian's command-line options in the process table (eg. top(1), etc.) . [ Paul Wise ] * Add several spelling corrections. . [ Xavier Guimard ] * Extend NodeJS checks to modules that use naming such as "@foo/bar". . lintian (2.56.0) unstable; urgency=medium . * Summary of tag changes: + Added: - nodejs-lock-file . [ Chris Lamb ] * Check for NO_START and FOO_NO_START etc. in /etc/default scripts. (Closes: #950238) * Deprecate debhelper compat level 9. (Closes: #950453) . [ Felix Lechner ] * Fix POD markup in man page; indent level caused literal display of formatting codes. (Closes: #952529) * Fix the selection of classification tags with -T command line switch. (Closes: #952539) * Use JSON::MaybeXS instead of plain JSON in the NodeJS checks. * Remove and replace the open_gz, open and file_contents subroutines from File::Path. * Provide method for all ->descendants in File::Path and use it, retiring breadth-first recursion. . [ Xavier Guimard ] * Check if NodeJS modules install lock files. Checksums-Sha1: 08f2dc3bd45b01c86bf7a2793bbe85d48c2f9c83 4156 lintian_2.57.0~bpo9+1.dsc b6fe66613206ede06365ee5c8cb0929a76caeaa4 1922568 lintian_2.57.0~bpo9+1.tar.xz 082d198e909ec7ecd5c508ef4c1b25989804e2db 1309734 lintian_2.57.0~bpo9+1_all.deb 26a998fad4fb6c2b460d76aa20986d4e5c5ab9d7 6366 lintian_2.57.0~bpo9+1_amd64.buildinfo Checksums-Sha256: ae1053258c6a1032c927189cd827106c754a2d0b3295058aa0e5cbb6c2dd40e7 4156 lintian_2.57.0~bpo9+1.dsc 0afc6cfc48d4dc55cef67bf2912191772c095da50cca1705986b9630b5fcdcd5 1922568 lintian_2.57.0~bpo9+1.tar.xz 56812ab44d57b78c78003c62b2ea73e33536cb5cb95355325a6db50cbf201d4b 1309734 lintian_2.57.0~bpo9+1_all.deb 2174496d023493950f18116fc8d5a4f46ffc820f063bfe2715511384232af50a 6366 lintian_2.57.0~bpo9+1_amd64.buildinfo Files: 58ce05aba6940d885bd506c41fbdae7a 4156 devel optional lintian_2.57.0~bpo9+1.dsc 85902af34bbfc6cab915a6706c6beb4f 1922568 devel optional lintian_2.57.0~bpo9+1.tar.xz 57d6df82398f9aa8b533acfe2d0cdf96 1309734 devel optional lintian_2.57.0~bpo9+1_all.deb a88f6bdf1aa64932780961f1be1e3ad8 6366 devel optional lintian_2.57.0~bpo9+1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl50koEACgkQHpU+J9Qx Hlja3g/+LrfYcq63SksOAUtFxgkxFZIT7wFAUhDO64trXSxxhPGDeAZ73PW6LQa2 ax46l9dudbREAsHGdLC2Pb8a8mMS9fsupvt0zfM5CZsVfiifB5u+yEcf6B5rGg8C
Processing of lintian_2.57.0~bpo9+1_amd64.changes
lintian_2.57.0~bpo9+1_amd64.changes uploaded successfully to localhost along with the files: lintian_2.57.0~bpo9+1.dsc lintian_2.57.0~bpo9+1.tar.xz lintian_2.57.0~bpo9+1_all.deb lintian_2.57.0~bpo9+1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processing of lintian_2.57.0~bpo10+1_amd64.changes
lintian_2.57.0~bpo10+1_amd64.changes uploaded successfully to localhost along with the files: lintian_2.57.0~bpo10+1.dsc lintian_2.57.0~bpo10+1.tar.xz lintian_2.57.0~bpo10+1_all.deb lintian_2.57.0~bpo10+1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
