Build failed in Jenkins: lintian-tests_buster #1435

[jenkins]

See 


Changes:

[lamby] Add /lib/runit/invoke-run as a known interpreter to avoid false

--
[...truncated 428.04 KB...]
debian/test-out/tags/checks/scripts/scripts-skip-systemd-native/generic.t 
. ok
debian/test-out/tags/checks/scripts/scripts-ocamlrun/generic.t 
 ok
debian/test-out/tags/checks/scripts/scripts-missing-versioned-depends-on-init-system-helpers/generic.t
  ok
debian/test-out/tags/checks/scripts/scripts-unconditional-use-of-dpkg-statoverride/generic.t
 .. ok
debian/test-out/tags/checks/scripts/scripts-supports-ancient-package-version/generic.t
  ok
debian/test-out/tags/checks/scripts/scripts-multi-arch-same-calls-pycompile/generic.t
 . ok
debian/test-out/tags/checks/scripts/scripts-udevadm-called-without-guard/generic.t
  ok
debian/test-out/tags/checks/scripts/scripts-missing-dep/generic.t 
. ok
debian/test-out/tags/checks/scripts/scripts-udevadm-called-without-guard-unrel/generic.t
 .. ok
debian/test-out/tags/checks/scripts/scripts-uses-perl4-libs-without-dep/generic.t
 . ok
debian/test-out/tags/checks/scripts/scripts-uses-perl4-libs-with-dep/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/binaries-missing-depends-on-libc/generic.t
  ok
debian/test-out/tags/checks/shared-libs/files-pkgconfig/generic.t 
. ok
debian/test-out/tags/checks/shared-libs/binaries-missing-depends/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/binaries-multiarch/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/binaries-doesnt-match-sonames/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/binaries-multiarch-same/generic.t 
. ok
debian/test-out/tags/checks/shared-libs/files-wrong-ma-foreign/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/shared-libs-non-pic-i386/generic.t 
 skipped: Architecture mismatch
debian/test-out/tags/checks/shared-libs/shared-libs-dev-symlink-fp/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/shared-libs-exec-bit/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-exit-fork/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/legacy-maintainer-scripts/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/shared-libs-dev-symlink/generic.t 
. ok
debian/test-out/tags/checks/shared-libs/legacy-debug/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-exec-stack/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/shared-libs-la-files/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/legacy-debconf/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/legacy-libbaz/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/shared-libs-exit/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-control-file/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-ldconfig-wrong-file/generic.t
 . ok
debian/test-out/tags/checks/shared-libs/shared-libs-missing-ldconfig-symlink/generic.t
  ok
debian/test-out/tags/checks/shared-libs/shared-libs-ldconfig-not-symlink/generic.t
  ok
debian/test-out/tags/checks/shared-libs/shared-libs-missing-soname/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/shared-libs-ldconfig-scripts/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-no-shared-lib/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/shared-libs-multi-arch-foreign/generic.t
 .. ok

Bug#930702: lintian: warn about /usr/bin -> /usr/sbin mismatch

[Chris Lamb]

Dmitry Bogatov wrote:

>  * upstream build system incorrectly installs binary into $(prefix)/bin
>  * package maintainer moves it into $(prefix)/sbin
>  * there still may be files around, that refer to previous location of
>binary

Interesting idea. This sounds like you are speaking from experience;
can you cite an example?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Processed: Bug#930701 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #930701 [lintian] lintian: unusual-interpreter /lib/runit/invoke-run
Added tag(s) pending.

-- 
930701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#930700: lintian: support "suppress-tags-from-file" in configuration file

[Chris Lamb]

Chris Lamb wrote:

> It seems reasonable that this option could be allowed so I am
> therefore retitling (etc.) this bug to match.

On the other hand, I would be curious to know why you wish to suppress
*so* many tags. It sounds like there is a deeper, more fundamental,
issue at play here.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Processed: Re: Bug#930700: lintian: support "suppress-tags-from-file" in configuration file

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 930700 lintian: support "suppress-tags-from-file" in configuration 
> file
Bug #930700 [lintian] lintian: failed to set "suppress-tags-from-file"
Changed Bug title to 'lintian: support "suppress-tags-from-file" in 
configuration file' from 'lintian: failed to set "suppress-tags-from-file"'.
> severity 930700 wishlist
Bug #930700 [lintian] lintian: support "suppress-tags-from-file" in 
configuration file
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
930700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#930700: lintian: support "suppress-tags-from-file" in configuration file

[Chris Lamb]

retitle 930700 lintian: support "suppress-tags-from-file" in configuration file
severity 930700 wishlist 
thanks

Hi Dmitry,

> Somehow, I fail to get "suppress-tags-from-file" option work from
> ~/.config/lintian/lintain. I keep receiving following error:
> 
>   Unknown configuration variable suppress-tags-from-file at line: 1.

Only a subset of the --foo options are available in the configuration
file. Currently this is (quoting from commands/lintian.pm):
 
# Options that can appear in the config file
my %cfghash = (
'color'=> \$opt{'color'},
'display-experimental' => \$opt{'display-experimental'},
'display-info' => \_display_level,
'display-level'=> \_display_level,
'fail-on-warnings' => \$opt{'fail-on-warnings'},
'info' => \$opt{'info'},
'jobs' => \$opt{'jobs'},
'pedantic' => \_display_level,
'quiet'=> \_verbosity,
'override' => \_override,
'show-overrides'   => \$opt{'show-overrides'},
'suppress-tags'=> \_suppress_tags,
'tag-display-limit'=> \$opt{'tag-display-limit'},
'verbose'  => \_verbosity,
);

It seems reasonable that this option could be allowed so I am
therefore retitling (etc.) this bug to match.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#930701: lintian: unusual-interpreter /lib/runit/invoke-run

[Dmitry Bogatov]

Package: lintian
Version: 2.15.0
Severity: wishlist

Dear Maintainer,

Lintian complains on runscripts (/etc/sv/*/run) with following shebang:

#!/usr/bin/env /lib/runit/invoke-run

This is correct shebang. /lib/runit/invoke-run invokes script with
/bin/sh, with some additional checks and environment variables, not
unlike /lib/init/init-d-script.

Please, add this path to list of "usual" interpreters.


pgpTcl09sbFi3.pgp
Description: PGP signature

Bug#930700: lintian: failed to set "suppress-tags-from-file"

[Dmitry Bogatov]

Package: lintian
Version: 2.15.0
Severity: normal

Dear Maintainer,

Somewhy, I fail to get "suppress-tags-from-file" option work from
~/.config/lintian/lintain. I keep receiving following error:

Unknown configuration variable suppress-tags-from-file at line: 1.

when config file is very simple:

suppress-tags-from-file = ~/.config/lintian/suppressed-tags.txt

But, if I inline list of suppressed tags myself into config file:

suppress-tags = tag1, tag2, tag3

Unfortunatuly, it hits any reasonable line length limit quickly. I
failed to find any hints in lintian(1), why and/or whether
"suppress-tags-from-file" is unsupported in config file, nor I found any
way to make line continuation.


pgpbRFBYHDv0C.pgp
Description: PGP signature

Bug#930702: lintian: warn about /usr/bin -> /usr/sbin mismatch

[Dmitry Bogatov]

Package: lintian
Version: 2.15.0
Severity: wishlist

Dear Maintainer,

please consider following situation:

 * upstream build system incorrectly installs binary into $(prefix)/bin
 * package maintainer moves it into $(prefix)/sbin
 [ or via-verse, although it is more rare ]
 * there still may be files around, that refer to previous location of
   binary, like:

+ supplementary scripts
+ .desktop files
+ init-system integration files
+ hardcoded path in other binaries (yes, it happens)

So here is my proposal: for each binary /usr/bin/foo and /usr/sbin/bar,
scan all files for "/usr/sbin/foo" and "/usr/bin/bar" and report any
occurence for possible mismatch.

I believe, that if we exclude /usr/share/doc/ from examination, false
positive should not happen very often. Still, obliviously, this check is
to be of "wild-guess" category.

Opinions?


pgpHbMbCmpXUE.pgp
Description: PGP signature

Bug#930679: Please add overridable tag for not using dh sequencer

[Felix Lechner]

On Tue, Jun 18, 2019 at 8:00 AM Chris Lamb  wrote:
>
> tags 930679 + moreinfo
> thanks
>
> Sam Hartman wrote:
>
> > It would be even better to detect some of the adequate justifications
> > automatically like  Haskell packages.

I think Sam meant that some circumstances should always prevent the
issuance of the tag, so developers are not burdened with the override.
Apparently, Haskell packages do not use dh but cabal. [1]

[1] 
https://wiki.debian.org/Haskell/CollabMaint/GettingStarted#Debianize_the_Sources

Build failed in Jenkins: lintian-tests_buster #1434

[jenkins]

See 


Changes:

[lamby] Interpolate $DPKG_MAINTSCRIPT_PACKAGE in debconf(7) template names in

--
[...truncated 428.01 KB...]
debian/test-out/tags/checks/scripts/scripts-missing-versioned-depends-on-init-system-helpers/generic.t
  ok
debian/test-out/tags/checks/scripts/scripts-missing-dep/generic.t 
. ok
debian/test-out/tags/checks/scripts/scripts-multi-arch-same-calls-pycompile/generic.t
 . ok
debian/test-out/tags/checks/scripts/scripts-supports-ancient-package-version/generic.t
  ok
debian/test-out/tags/checks/scripts/scripts-ocamlrun/generic.t 
 ok
debian/test-out/tags/checks/scripts/scripts-udevadm-called-without-guard/generic.t
  ok
debian/test-out/tags/checks/scripts/scripts-udevadm-called-without-guard-unrel/generic.t
 .. ok
debian/test-out/tags/checks/scripts/scripts-skip-systemd-native/generic.t 
. ok
debian/test-out/tags/checks/scripts/scripts-uses-perl4-libs-without-dep/generic.t
 . ok
debian/test-out/tags/checks/scripts/scripts-unconditional-use-of-dpkg-statoverride/generic.t
 .. ok
debian/test-out/tags/checks/scripts/scripts-uses-perl4-libs-with-dep/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/binaries-missing-depends-on-libc/generic.t
  ok
debian/test-out/tags/checks/shared-libs/binaries-multiarch-same/generic.t 
. ok
debian/test-out/tags/checks/shared-libs/binaries-missing-depends/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/files-wrong-ma-foreign/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/binaries-multiarch/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/files-pkgconfig/generic.t 
. ok
debian/test-out/tags/checks/shared-libs/binaries-doesnt-match-sonames/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/legacy-libbaz/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/shared-libs-non-pic-i386/generic.t 
 skipped: Architecture mismatch
debian/test-out/tags/checks/shared-libs/legacy-debug/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-dev-symlink/generic.t 
. ok
debian/test-out/tags/checks/shared-libs/shared-libs-dev-symlink-fp/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/shared-libs-exec-bit/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-exec-stack/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/legacy-maintainer-scripts/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/shared-libs-la-files/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/legacy-debconf/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/shared-libs-exit/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-control-file/generic.t 
 ok
debian/test-out/tags/checks/shared-libs/shared-libs-exit-fork/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/shared-libs-ldconfig-wrong-file/generic.t
 . ok
debian/test-out/tags/checks/shared-libs/shared-libs-ldconfig-not-symlink/generic.t
  ok
debian/test-out/tags/checks/shared-libs/shared-libs-missing-ldconfig-symlink/generic.t
  ok
debian/test-out/tags/checks/shared-libs/shared-libs-no-shared-lib/generic.t 
... ok
debian/test-out/tags/checks/shared-libs/shared-libs-missing-soname/generic.t 
.. ok
debian/test-out/tags/checks/shared-libs/shared-libs-multi-arch-foreign/generic.t
 .. ok
debian/test-out/tags/checks/shared-libs/shared-libs-ldconfig-scripts/generic.t 
 ok

Processed: block 930679 with 930666

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 930679 with 930666
Bug #930679 [lintian] Please add overridable tag for not using dh sequencer
930679 was not blocked by any bugs.
930679 was not blocking any bugs.
Added blocking bug(s) of 930679: 930666
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
930679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#930679: Please add overridable tag for not using dh sequencer

[Sam Hartman]

I think that before providing a long description I'd like to see where
the policy process gets.  As DPL I think it's fine for me to put issues
onto people's radars based on project-level discussions as part of my
facilitator role.  I'm less comfortable proposing things like a long
description in that role.  Obviously I could do that as an individual
developer, but I'd rather see where the community gets.

I plan to block this bug with the policy bug at least until they get
further along.
> "Chris" == Chris Lamb  writes:


>> It would be even better to detect some of the adequate
>> justifications automatically like Haskell packages.

Chris> Unless I'm misunderstanding this request, we have no
Chris> functionality to "meta warn" when a tag is overridden without
Chris> an "adequate" or even a non-verbose justification. This would
Chris> seem overly error-prone.

I'm sorry, let me try to be more clear.  It would be nice if a
maintainer of a Haskell package did not need to override the tag.  That
is, in cases where we can adequately detect that the package is in one
of the exceptional cases, it would be nice if lintian didn't issue a
warning.

I understand lintian cannot judge whether a maintainer's
reasoning is adequate.  When lintian does gain that strong AI
functionality, I'm sure you can ask it to update this and a number of
other tags based on its best judgment.  I'm sorry that I was unclear to
the point of asking for the impossible.

Processed: Re: Bug#930679: Please add overridable tag for not using dh sequencer

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 930679 + moreinfo
Bug #930679 [lintian] Please add overridable tag for not using dh sequencer
Ignoring request to alter tags of bug #930679 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
930679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#930679: Please add overridable tag for not using dh sequencer

[Chris Lamb]

tags 930679 + moreinfo
thanks

Sam Hartman wrote:

> […] we'd like lintian to detect when dh is not used […]

Just in case you or -policy was unaware, please note that Lintian
actually currently warns — albeit at a pedantic level — when a
package uses neither cdbs nor debhelper:

  https://lintian.debian.org/tags/package-does-not-use-debhelper-or-cdbs.html

§

Anyway, whilst the technical implementation of the requested tag is
trivial, what we would need from you (etc.) at this point is:

  a) Name of this tag (eg. "package-does-not-use-dh")

  b) The "long description" of the tag with a brief rationale,
 references, etc.

  c) The severity (ie. E/W/I/P)

> It would be even better to detect some of the adequate justifications
> automatically like  Haskell packages.

Unless I'm misunderstanding this request, we have no functionality to
"meta warn" when a tag is overridden without an "adequate" or even a
non-verbose justification. This would seem overly error-prone.

As an aside, every tag in Lintian is overridable; the question of
non-overridable tags only concerns uploads and dak where such a subset
of tags operates on an opt-in basis for hopefully-obvious reasons.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Processed: Bug#930677 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #930677 [lintian] unused-debconf-template triggers when template is used in 
postrm only
Added tag(s) pending.

-- 
930677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#930679: Please add overridable tag for not using dh sequencer

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 930679 + moreinfo
Bug #930679 [lintian] Please add overridable tag for not using dh sequencer
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
930679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#930679: Please add overridable tag for not using dh sequencer

[Chris Lamb]

tags 930679 + moreinfo
thanks

Sam Hartman wrote:

> […] we'd like lintian to detect when dh is not used […]

Just in case you or -policy was unaware, please note that Lintian
actually currently warns — albeit at a pedantic level — when a
package uses neither cdbs nor debhelper:

  https://lintian.debian.org/tags/package-does-not-use-debhelper-or-cdbs.html

§

Anyway, whilst the technical implementation of the requested tag is
trivial, what we would need from you (etc.) at this point is:

  a) Name of this tag (eg. "package-does-not-use-dh")

  b) The "long description" of the tag with a brief rationale,
 references, etc.

  c) The severity (ie. E/W/I/P)

> It would be even better to detect some of the adequate justifications
> automatically like  Haskell packages.

Unless I'm misunderstanding this request, we have no functionality to
"meta warn" when a tag is overridden without an "adequate" or even a
non-verbose justification. This would seem overly error-prone.

As an aside, every tag in Lintian is overridable; the question of
non-overridable tags only concerns uploads and dak where such a subset
of tags operates on an opt-in basis for hopefully-obvious reasons.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#930679: Please add overridable tag for not using dh sequencer

[Sam Hartman]

package: lintian
severity: wishlist

Hi.
In
https://lists.debian.org/msgid-search/tslmuif7pwy@suchdamage.org

I document a consensus of a discussion  we had on debian-devel.

Based on that I think we'd like lintian to detect when dh is not used
and allow maintainers to override the tag if they have an adequate
justification for not using dh.
It would be even better to detect some of the adequate justifications
automatically like  Haskell packages.

I'm opening this bug to track the issue.
There's ongoing discussion in debian-policy about the specifics at the
policy level.

Bug#930677: unused-debconf-template triggers when template is used in postrm only

[Christoph Berg]

Package: lintian
Version: 2.15.0
Severity: normal

postgresql-12 is using debconf in the purge phase only:

purge_package () {
# ask the user if they want to remove clusters. If debconf is not
# available, just remove everything
if [ -e /usr/share/debconf/confmodule ]; then
db_set $DPKG_MAINTSCRIPT_PACKAGE/postrm_purge_data true
db_input high $DPKG_MAINTSCRIPT_PACKAGE/postrm_purge_data || :
db_go || :
db_get $DPKG_MAINTSCRIPT_PACKAGE/postrm_purge_data || :
[ "$RET" = "false" ] && return 0
fi

This triggers unused-debconf-template:

I: postgresql-12: unused-debconf-template postgresql-12/postrm_purge_data
N:
N:Templates which are not used by the package should be removed from the
N:templates file.
N:
N:This will reduce the size of the templates database and prevent
N:translators from unnecessarily translating the template's text.
N:
N:In some cases, the template is used but Lintian is unable to determine
N:this. Common causes are:
N:
N:- the maintainer scripts embed a variable in the template name in order
N:to allow a template to be selected from a range of similar templates
N:(e.g. db_input low start_$service_at_boot)
N:
N:- the template is not used by the maintainer scripts but is used by a
N:program in the package
N:
N:- the maintainer scripts are written in perl. Lintian currently only
N:understands the shell script debconf functions.
N:
N:If any of the above apply, please install an override.
N:
N:Severity: minor, Certainty: possible
N:
N:Check: debconf, Type: binary, udeb, source

I'm filing this bug because "postrm" isn't listed among the common
causes. Please either check postrm as well, or mention it there.

If the problem is rather $DPKG_MAINTSCRIPT_PACKAGE, please support
that use.

Thanks,
Christoph

Bug#930487: lintian: use GitLab caching of test packages to speed up test suite CI

[Chris Lamb]

[changing subject to match updated bug title]

Hi Felix,

> On Mon, Jun 17, 2019 at 4:03 PM Chris Lamb  wrote:

> We used filesystem timestamps for a while, but the standard resolution
> (1 sec) was not granular enough. AFAIR, we now generate everything
> every time.

By "filesystem timestamps" here are you referring to comparing the
timestamp of each generated test package and its source? If so, I am
unclear why one second was not enough to determine whether a *developer*
had changed something under "t/".

> We could probably skip the generation of test packages if they are
> already present and nothing in t/ has changed.

Indeed, but that is (roughly) what this entire bug report is about.

> > But are we barking up the wrong tree here and what we need to do is
> > use different GitLab CI stage altogether and pass "artifacts" around
> > instead?
> >
> >   https://docs.gitlab.com/ee/ci/caching/index.html#cache-vs-artifacts
> 
> Artifacts may work, but uploading them separately without a dependency
> scheme seems to invite other problems.   […]

Hm, I think you may have been accidentally misled about how the Gitlab
CI build stages — there would be no upload whatsoever. I am therefore
unsure how to effectively and productively respond to your remarks,
alas. :(


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-