Build failed in Jenkins: lintian-tests_sid #3886

2019-08-12 Thread jenkins 
See 

Changes:

--
[...truncated 314.45 KB...]
Building in debian/test-out/tags/checks/debconf/debconf-is-not-registry
Building in debian/test-out/tags/checks/debconf/debconf-config-not-executable
Building in debian/test-out/tags/checks/debconf/debconf-config-general
Building in debian/test-out/tags/checks/deb-format/debhelper-compat-old
Building in debian/test-out/tags/checks/deb-format/deb-format-wrong-order
Building in debian/test-out/tags/checks/deb-format/deb-format-udeb-compression
Building in debian/test-out/tags/checks/deb-format/deb-format-record-size
Building in debian/test-out/tags/checks/deb-format/deb-format-no-compress
Building in debian/test-out/tags/checks/deb-format/deb-format-lzma
Building in 
debian/test-out/tags/checks/deb-format/deb-format-extra-underscore-member-before-data
Building in 
debian/test-out/tags/checks/deb-format/deb-format-extra-underscore-member-before-control
Building in debian/test-out/tags/checks/deb-format/deb-format-extra-member
Building in debian/test-out/tags/checks/deb-format/deb-format-errors-tar
Building in 
debian/test-out/tags/checks/deb-format/control-file-rules-requires-root-no
Building in 
debian/test-out/tags/checks/deb-format/control-file-rules-requires-root-binary-targets
Building in debian/test-out/tags/checks/dbus/dbus-services
Building in debian/test-out/tags/checks/dbus/dbus-policy
Building in debian/test-out/tags/checks/cruft/legacy-filenames
Building in debian/test-out/tags/checks/cruft/legacy-debconf
Building in debian/test-out/tags/checks/cruft/files-r-data
Building in debian/test-out/tags/checks/cruft/files-r-data-unrel
Building in debian/test-out/tags/checks/cruft/files-doxygen-documentation
Building in debian/test-out/tags/checks/cruft/cruft-wasm
Building in debian/test-out/tags/checks/cruft/cruft-upstream-binaries
Building in debian/test-out/tags/checks/cruft/cruft-updated-libtool
Building in debian/test-out/tags/checks/cruft/cruft-unsafe-symlinks
Building in debian/test-out/tags/checks/cruft/cruft-sphinx-documentation
Building in debian/test-out/tags/checks/cruft/cruft-source-is-missing-unrel
Building in 
debian/test-out/tags/checks/cruft/cruft-source-contains-empty-directory
Building in debian/test-out/tags/checks/cruft/cruft-readme-source
Building in debian/test-out/tags/checks/cruft/cruft-python
Building in debian/test-out/tags/checks/cruft/cruft-perl
Building in 
debian/test-out/tags/checks/cruft/cruft-package-does-not-install-examples
Building in 
debian/test-out/tags/checks/cruft/cruft-package-does-not-install-examples-unrel
Building in 
debian/test-out/tags/checks/cruft/cruft-package-does-not-install-examples-symlink
Building in debian/test-out/tags/checks/cruft/cruft-obsolete-upstream-metadata
Building in debian/test-out/tags/checks/cruft/cruft-nvidia-intellectual
Building in debian/test-out/tags/checks/cruft/cruft-non-free-utf
Building in debian/test-out/tags/checks/cruft/cruft-non-free-rfc
Building in debian/test-out/tags/checks/cruft/cruft-non-free-md5sums
Building in debian/test-out/tags/checks/cruft/cruft-non-free-img
Building in debian/test-out/tags/checks/cruft/cruft-minified-js
Building in debian/test-out/tags/checks/cruft/cruft-gfdl-invariants
Building in debian/test-out/tags/checks/cruft/cruft-gfdl-fp-sliding-win
Building in debian/test-out/tags/checks/cruft/cruft-general-wig-pen
Building in debian/test-out/tags/checks/cruft/cruft-general-upstream
Building in debian/test-out/tags/checks/cruft/cruft-general-test-suite
Building in debian/test-out/tags/checks/cruft/cruft-general-quilt
Building in debian/test-out/tags/checks/cruft/cruft-general-native
Building in debian/test-out/tags/checks/cruft/cruft-general-diff
Building in debian/test-out/tags/checks/cruft/cruft-fixme-placeholders
Building in 
debian/test-out/tags/checks/cruft/cruft-file-contains-trailing-whitespace
Building in debian/test-out/tags/checks/cruft/cruft-evil-json
Building in debian/test-out/tags/checks/cruft/cruft-empty-diff
Building in debian/test-out/tags/checks/cruft/cruft-doxygen-documentation
Building in debian/test-out/tags/checks/cruft/cruft-current-libtool
Building in debian/test-out/tags/checks/cruft/cruft-crlf-eols
Building in debian/test-out/tags/checks/cruft/cruft-contains-waf
Building in debian/test-out/tags/checks/cruft/cruft-contains-waf-stripped
Building in debian/test-out/tags/checks/cruft/cruft-cc-by-nc-sa
Building in debian/test-out/tags/checks/cruft/cruft-bad-php
Building in debian/test-out/tags/checks/cruft/cruft-bad-php-unrel
Building in 
debian/test-out/tags/checks/cruft/cruft-autotools-pkg-config-macro-not-cross-compilation-safe
Building in debian/test-out/tags/checks/cruft/cruft-autogenerated
Building in debian/test-out/tags/checks/cruft/cruft-ancient-libtool
Building in debian/test-out/tags/checks/cruft/cruft-ancient-libtool-2
Building in debian/test-out/tags/checks/copyright-file/spelling-general
Building in debian/test-ou

Bug#934512: lintian false positive for source-is-missing for pmccabe2html output

2019-08-12 Thread Paul Wise 
On Mon, 12 Aug 2019 14:12:09 -0700 Chris Lamb wrote:

> Therefore, please add an override with a suitably detailed comment to
> your package.

This file seems like the sort of thing that will get quickly outdated
as the source code of the upstream project evolves. So it would be
appropriate to always build the file from source. I suggest another
option to solve this would be to have upstream remove the file from
their VCS and tarballs so that it is always generated at build time. 

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#934512: marked as done (lintian false positive for source-is-missing for pmccabe2html output)

2019-08-12 Thread Debian Bug Tracking System 
Your message dated Mon, 12 Aug 2019 14:12:09 -0700
with message-id <9fbbd05a-dd6f-40df-8c2e-5fb7d5280...@www.fastmail.com>
and subject line Re: Bug#934512: lintian false positive for source-is-missing 
for pmccabe2html output
has caused the Debian Bug report #934512,
regarding lintian false positive for source-is-missing for pmccabe2html output
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.)


-- 
934512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian

Hi.  Lintian complains about gsasl -- see 
https://lintian.debian.org/maintainer/pkg-xmpp-de...@lists.alioth.debian.org.html#gsasl

E: gsasl source: source-is-missing doc/cyclo/cyclo-gsasl.html line
length is 567 characters (>512)

The source of the following file is missing. Lintian checked a few
possible paths to find the source, and did not find it.

Please repack your package to include the source or add it to
"debian/missing-sources" directory.

If this is a false-positive, please report a bug against Lintian.

Please note, that insane-line-length-in-source-file tagged files
are likely tagged source-is-missing. It is a feature not a bug.

Severity: serious, Certainty: possible

Check: cruft, Type: source

However the file is generated by upstream rules that uses pmccabe (from
Debian) and pmccabe2html (from gnulib), see:

https://salsa.debian.org/xmpp-team/gsasl/blob/master/doc/cyclo/Makefile.am

https://salsa.debian.org/xmpp-team/gsasl/blob/master/lib/build-aux/pmccabe2html

As such, I believe this is a false positive, and I'm reporting it as
such.  I'll tell lintian to ignore this error for gsasl, unless you
tell me I'm mistaken somehow.

/Simon



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Hi Simon,

> E: gsasl source: source-is-missing doc/cyclo/cyclo-gsasl.html line
> length is 567 characters (>512)

Whilst this is a false positive I don't think Lintian could ever
really determine that it is generated by the the package itself.
Therefore, please add an override with a suitably detailed comment to
your package.

Thanks for reporting and caring about Lintian.


Best wishes,

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

Bug#865847: Use reStructuredText for Lintian manual

2019-08-12 Thread Chris Lamb 
Hi Felix,

> tldr; I am comfortable with any format you like, but please consider
> that I have to re-write much of the documentation. Could we convert to
> Markdown when I am done?

I would concede that RST might be more suitable for more complex
requirements indeed.

However, if you are to invest further time in $format it doesn't make
sense to convert to $another right at the end. Thus, if you really are
a +1 on RST then sense to start and finish with that.


Regards,

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

Bug#934322: Split reporting code from Lintian proper

2019-08-12 Thread Chris Lamb 
Felix Lechner wrote:

> > Indeed and even within this lindsay is running the unstable version
> > and is updated at the time of the release (instead of at time-of-
> > backport after I let the sid version mature and migrate to testing).
> 
> Would you both be comfortable if we returned to a stable-backports
> cycle on lindsay 

Returned? We have never been on one AIUI, or at least not in my time
here.

> [..] if I can solve the out of memory problems there and provide a
> way to preview new reporting features before they are released into
> master?

I think that there would be other excellent reasons why we would want
to release specific changes outside of this and not be limited to a
version in backports (that could be delayed by transitions, etc.) that
would not be offset by having to do a small bit of admin when we add a
new dependency.


Regards,

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

lintian_2.17.0~bpo9+1_amd64.changes ACCEPTED into stretch-backports->backports-policy, stretch-backports

2019-08-12 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Aug 2019 22:22:34 +0100
Source: lintian
Binary: lintian
Built-For-Profiles: nocheck
Architecture: source all
Version: 2.17.0~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 570998 931846 931889 931951 932128 932215 932411 933134 933383 933394
Changes:
 lintian (2.17.0~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
 .
 lintian (2.17.0) unstable; urgency=medium
 .
   * Summary of tag changes:
 + Added:
   - empty-debian-tests-control
 + Removed:
   - control-file-duplicate-field
   - control-file-syntax-error
   - debian-source-dir-unknown-source-format
   - debian-tests-control-is-not-a-regular-file
   - missing-runtime-tests-field
   - syntax-error-in-control-file
   - syntax-error-in-debian-tests-control
   - testsuite-control-missing-test-field
   - testsuite-control-not-file
   - testsuite-control-syntax-error
   - unknown-source-format
 .
   [ Chris Lamb ]
   * Don't emit command-in-sbin-has-manpage-in-incorrect-section for
 symlinks; they are invariably provided for legacy/compatibility
 reasons. (Closes: #931951)
   * Update regex matches against lines in debian/rules correctly identify
 debhelper calls starting with environment modification (eg.
 "LC_ALL=C.UTF-8"). (Closes: #932128)
   * Factor out mangling of fatal error messages in the frontend
 configuration and correct the exit code if the specified profile does
 not exist. (Closes: #932215)
   * Expand the long description of the duplicate-files check to suggest how
 to remove them. Thanks to Rebecca Palmer for the suggested text.
 (Closes: #932411)
   * Downgrade command-in-sbin-has-manpage-in-incorrect-section to pedantic
 severity for the time being. (Closes: #570998)
   * Downgrade the severity and certainty of the
 package-supports-alternative-init-but-no-init.d-script tag for the time
 being. (Closes: #931889)
   * Correct multiple "gobject-introspection" typos. Thanks to Simon
 McVittie (smcv) for the pointer. (Closes: #933394)
   * Ignore all initscripts provided by the initscripts binary package
 instead of whitelisting issues individually or requiring overrides;
 these will never be regular-style initscripts. (Closes: #933383)
 .
   [ Felix Lechner ]
   * Do not trigger repack requirement when the Debian revision includes the
 "repack" indicator. (Closes: #931846)
   * Drop Depends and Build-Depends on libparse-debianchangelog-perl.
 (Closes: #933134)
   * Quote the spelling corrections that consist of multiple words.
   * Use the null character as the line delimiter in collection/md5sums.
   * Show logs for tests with parse errors when unattended and show all
 parse errors in TAP.
   * Always show log when failing to build a test package.
   * Store tags is separate, small files under ./tags.
   * Remove MatchVars check from PerlCritic configuration.
   * In the test runner, add an option to accept all tag changes.
 .
   [ Paul Wise ]
   * Add several spelling corrections.
Checksums-Sha1:
 45cd81b4efc738e3969d01395d665b727744a8d9 3945 lintian_2.17.0~bpo9+1.dsc
 3dd9bf7ff6ee19ae98787316839a745e86c64558 1769640 lintian_2.17.0~bpo9+1.tar.xz
 b627a5e7594a4bd847ab165dcef75e80725fad59 1280424 lintian_2.17.0~bpo9+1_all.deb
 0fca5a374c7914dfb06ff6b7f55c855d731ccf3a 8875 
lintian_2.17.0~bpo9+1_amd64.buildinfo
Checksums-Sha256:
 e7393dda52527b2f3d99c547c5cde479e6a354741258d2618b928bc6ef599afe 3945 
lintian_2.17.0~bpo9+1.dsc
 d5f5ba3e01011f21dd478658cdc377433e1a8a46b26f8e60390972603a78a21f 1769640 
lintian_2.17.0~bpo9+1.tar.xz
 cb2651ce84f82a32043af996ce7f4f197b75d63355e83168e77d26cb7317ea8e 1280424 
lintian_2.17.0~bpo9+1_all.deb
 8eb62df42b3656383832faa6170b9f9d3a7e0eaeaf3f87e2a8b2b2e629dd50ee 8875 
lintian_2.17.0~bpo9+1_amd64.buildinfo
Files:
 71175b79af14b0e913f5bb9988a5ec89 3945 devel optional lintian_2.17.0~bpo9+1.dsc
 bcac30b2c787ad742c4687744924e64e 1769640 devel optional 
lintian_2.17.0~bpo9+1.tar.xz
 f665bd791570211c93a255bca5f985ac 1280424 devel optional 
lintian_2.17.0~bpo9+1_all.deb
 37e772d66f8fd13357292ac30629255b 8875 devel optional 
lintian_2.17.0~bpo9+1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl1N5UYACgkQHpU+J9Qx
Hlj9cBAAobDp+QjZfpB/PgyVN527ykQ38YlbOdSfhE9ESwlduNxlYzvstt3qz6fl
ZCukBD9nXj/3M+Ynr3gQkyQl1dVQ8IU0iavmw3rl+g8M5/djrOUxdT75hTCavmMI
j9Q2R7+GPVgugrF0REYkpw9+R9zOXEB9oa2dXYWdopnXuGnYKhbmCfPGFUheLGgw
eEK2JqxKzKE5Tn8rtE1F4h6M+4LRKIhIQjYoqONC0KMMGvLjYASFKkSRQnknz+rj
soNQc6+a4p7JG7KpXp3sPcx5aIE6d3gFNgLKlEmJ2LhpYumCoC9svxrBWyOX4vQC
funNahYZIF0oFbh8egBT2a8Hcsctn20dTflWFDd4RioQ8ytuS+38bG72D0FocZ/u
bnj+qrPl7BI07rhleWnQXtd2ZsqqdOGKDagltbyLrn2v0PsXAwa4XJCvnEdtoFD5
Z6wWPrAhkG2u2fGZ5CwAQkGfIrXNOWMGBojQ8mm2sFq6EerGX

Re: Adding Felix Lechner to the Lintian team

2019-08-12 Thread Chris Lamb 
Chris Lamb wrote:

> > Would anyone object to the formal addition of Felix Lechner to
> > the team?
> > 
> > I feel like his contributions at this stage have not only warranted
> > that but moreover his lack of membership is getting in his and our
> > way.
> 
> 9 months on (!) in lieu of any pushback I'll go ahead with this
> in ~7 days...

I did not receive any public or private censure of this proposal and I
would therefore like to follow through on adding Felix Lechner to the
Lintian team.

In terms of the specifics, whilst I have just added the @lechner-guest
user to the group on salsa, I may need to be educated on the DSA-
related parts of this, including but perhaps not limited to ensuring
Felix's access to lindsay.debian.org in parity with the other
maintainers of this package. Note that Felix is not (yet) a Developer
and thus this might complicate things in this regard.


Regards,

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