Bug#950589: lintian: collection/src-orig-index mishandles tarballs with whitespace in owner field
Package: lintian
Version: 2.47.0
Severity: minor
Lintian reports false warnings for src:libcryptx-perl_0.067-1
(only just uploaded, available at [1]):
% lintian -I libcryptx-perl_0.067-1.dsc
I: libcryptx-perl source: unused-file-paragraph-in-dep5-copyright paragraph at line 10
I: libcryptx-perl source: unused-file-paragraph-in-dep5-copyright paragraph at line 16
I: libcryptx-perl source: unused-file-paragraph-in-dep5-copyright paragraph at line 22
I: libcryptx-perl source: unused-file-paragraph-in-dep5-copyright ... use --no-tag-display-limit to see all (or pipe to a file/program)
I: libcryptx-perl source: wildcard-matches-nothing-in-dep5-copyright ppport.h (paragraph at line 10)
I: libcryptx-perl source: wildcard-matches-nothing-in-dep5-copyright src/ltc/* (paragraph at line 16)
I: libcryptx-perl source: wildcard-matches-nothing-in-dep5-copyright src/ltc/hashes/blake2b.c (paragraph at line 22)
I: libcryptx-perl source: wildcard-matches-nothing-in-dep5-copyright ... use --no-tag-display-limit to see all (or pipe to a file/program)
This is not a fault with the copyright file afaics, but rather with
the file name matching.
The original tarball from [2] includes ownership info with whitespace,
an example line:
-rw-r--r-- miko/Domain Users 220789 2019-06-07 10:40 CryptX-0.067/ppport.h
It looks like this confuses the common prefix removal in
collection/src-orig-index:index_orig() which relies on the file name
being in the sixth whitespace separated field.
I see #895175 was a similar issue and resulted in a rather complicated
regexp in Lintian::Collect::Package for parsing tar output (commit
a75f3edcb099bd4b8794e2ecb7fd19e129e77f03). I expect something like that
should work here as well. Sorry about the lack of a patch.
[1] https://salsa.debian.org/perl-team/modules/packages/libcryptx-perl.git
[2] https://cpan.metacpan.org/authors/id/M/MI/MIK/CryptX-0.067.tar.gz
Thanks for your work on lintian,
--
Niko Tyni ntyni@debian.org
Reply to: