Jenkins build is back to normal : lintian-tests_sid #2830

2018-04-23 Thread jenkins 
See

Build failed in Jenkins: lintian-tests_sid #2829

2018-04-23 Thread jenkins 
See 

--
[...truncated 253.64 KB...]
tests::lintian-output-letter:dh_link
tests::lintian-output-letter:dh_strip_nondeterminism
tests::lintian-output-letter:dh_compress
tests::lintian-output-letter:dh_fixperms
tests::lintian-output-letter: sh: 0: Cannot fork
tests::lintian-output-letter: dh_fixperms: find debian/lintian-output-letter 
-type f \( -name '*.so.*' -o -name '*.so' -o -name '*.la' -o -name '*.a' -o 
-name '*.js' -o -name '*.css' -o -name '*.scss' -o -name '*.sass' -o -name 
'*.jpeg' -o -name '*.jpg' -o -name '*.png' -o -name '*.gif' -o -name '*.cmxs' 
\) -a -true -a -true -print0 2>/dev/null | xargs -0r chmod 0644 returned exit 
code 2
tests::lintian-output-letter: dh_fixperms: Aborting due to earlier error
tests::lintian-output-letter: make: *** [debian/rules:3: binary] Error 2
tests::lintian-output-letter: dpkg-buildpackage: error: debian/rules binary 
subprocess returned exit status 2
tests::lintian-output-letter:  END BUILD LOG
error tests::lintian-output-letter: internal error: cd 
/tmp/testrun/debian/test-out/tests/lintian-output-letter/lintian-output-letter-1.0+dsfg
 && dpkg-buildpackage -rfakeroot -us -uc -d -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --source-option=--auto-commit 
>/tmp/testrun/debian/test-out/tests/lintian-output-letter/build.lintian-output-letter
 2>&1 at t/runtests line 466.

tests::lintian-output-xml:  START BUILD LOG
tests::lintian-output-xml: dpkg-buildpackage: info: source package 
lintian-output-xml
tests::lintian-output-xml: dpkg-buildpackage: info: source version 1.0+dsfg-1.1
tests::lintian-output-xml: dpkg-buildpackage: info: source distribution unstable
tests::lintian-output-xml: dpkg-buildpackage: info: source changed by Debian 
Lintian Maintainers 
tests::lintian-output-xml:  dpkg-source -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --auto-commit --before-build lintian-output-xml-1.0+dsfg
tests::lintian-output-xml: dpkg-buildpackage: info: host architecture amd64
tests::lintian-output-xml: dpkg-source: warning: --auto-commit is not a valid 
option for Dpkg::Source::Package::V1
tests::lintian-output-xml:  debian/rules clean
tests::lintian-output-xml: dh clean
tests::lintian-output-xml:dh_clean
tests::lintian-output-xml:  dpkg-source -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --auto-commit -b lintian-output-xml-1.0+dsfg
tests::lintian-output-xml: dpkg-source: warning: --auto-commit is not a valid 
option for Dpkg::Source::Package::V1
tests::lintian-output-xml: dpkg-source: info: using source format '1.0'
tests::lintian-output-xml: dpkg-source: info: building lintian-output-xml using 
existing lintian-output-xml_1.0+dsfg.orig.tar.gz
tests::lintian-output-xml: dpkg-source: info: building lintian-output-xml in 
lintian-output-xml_1.0+dsfg-1.1.diff.gz
tests::lintian-output-xml: dpkg-source: warning: file 
lintian-output-xml-1.0+dsfg/debian/copyright has no final newline (either 
original or modified version)
tests::lintian-output-xml: dpkg-source: warning: executable mode 0755 of 
'debian/tests/test' will not be represented in diff
tests::lintian-output-xml: dpkg-source: warning: file 
lintian-output-xml-1.0+dsfg/debian/upstream/metadata has no final newline 
(either original or modified version)
tests::lintian-output-xml: dpkg-source: warning: the diff modifies the 
following upstream files: 
tests::lintian-output-xml:  Changes
tests::lintian-output-xml: dpkg-source: info: use the '3.0 (quilt)' format to 
have separate and documented changes to upstream files, see dpkg-source(1)
tests::lintian-output-xml: dpkg-source: info: building lintian-output-xml in 
lintian-output-xml_1.0+dsfg-1.1.dsc
tests::lintian-output-xml:  debian/rules binary
tests::lintian-output-xml: dh binary
tests::lintian-output-xml:dh_update_autotools_config
tests::lintian-output-xml:dh_autoreconf
tests::lintian-output-xml:create-stamp debian/debhelper-build-stamp
tests::lintian-output-xml:dh_testroot
tests::lintian-output-xml:dh_prep
tests::lintian-output-xml:dh_installdirs
tests::lintian-output-xml:dh_install
tests::lintian-output-xml:dh_installdocs
tests::lintian-output-xml:dh_installchangelogs
tests::lintian-output-xml: dh_installchangelogs: fork: Resource temporarily 
unavailable
tests::lintian-output-xml: make: *** [debian/rules:3: binary] Error 11
tests::lintian-output-xml: dpkg-buildpackage: error: debian/rules binary 
subprocess returned exit status 2
tests::lintian-output-xml:  END BUILD LOG
error tests::lintian-output-xml: internal error: cd 
/tmp/testrun/debian/test-out/tests/lintian-output-xml/lintian-output-xml-1.0+dsfg
 && dpkg-buildpackage -rfakeroot -us -uc -d -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --source-option=--auto-commit 
>/tmp/testrun/debian/test-out/tests/lintian-output-xml/build.lintian-output-xml 
2>&1 at t/runtests line 466.

error

Build failed in Jenkins: lintian-tests_buster #796

2018-04-23 Thread jenkins 
See 


Changes:

[lamby] Clarify that we should add an extra bit of whitespace for annotated

[lamby] Include the offending version numbers in the output of the

[lamby]  Prevent false-positives in the non-consecutive-debian-revision and

--
[...truncated 264.76 KB...]
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.
Can't fork, trying again in 5 seconds at (eval 27) line 89.

tests::lintian-overrides: diff -u t/tests/lintian-overrides/tags 
/tmp/testrun/debian/test-out/tests/lintian-overrides/tags.lintian-overrides
--- t/tests/lintian-overrides/tags  2018-04-23 17:47:52.779454725 +
+++ /tmp/testrun/debian/test-out/tests/lintian-overrides/tags.lintian-overrides 
2018-04-23 19:07:52.851056608 +
@@ -1,2 +0,0 @@
-E: lintian-overrides: malformed-override Possibly wrong package in override at 
line 1 (got lintian-override, expected lintian-overrides)
-I: lintian-overrides:

Bug#896671: lintian: false positive description-synopsis-might-not-be-phrased-properly on 'e.g.'

2018-04-23 Thread Chris Lamb 
tags 896671 + pending
thanks

Nice report, thanks... I liked the "stretc." corner case! Fixed
in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/2c6fcf72575342bb874a4f983db825f4abd1e03d

  checks/description.pm  |   7 +-
  debian/changelog   |   6 ++
  .../description-general/debian/debian/control.in   |  23 +---
  t/tests/description-general/desc   |   3 +-
  t/tests/description-general/tags   |   2 -
  .../debian/debian/control.in   | 117 +
  .../desc   |   5 +
  .../tags   |   5 +
  8 files changed, 141 insertions(+), 27 deletions(-)


Regards,

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

Processed: Re: lintian: false positive description-synopsis-might-not-be-phrased-properly on 'e.g.'

2018-04-23 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 896671 + pending
Bug #896671 [lintian] lintian: false positive 
description-synopsis-might-not-be-phrased-properly on 'e.g.'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#896696: marked as done (lintian: please improve tag description to explain that python 2 modules are only questioned on 1st upload)

2018-04-23 Thread Debian Bug Tracking System 
Your message dated Mon, 23 Apr 2018 18:12:40 +
with message-id <20180423181239.y3zum2kp6bj42...@layer-acht.org>
and subject line Re: Bug#896696: lintian: please improve tag description to 
explain that python 2 modules are only questioned on 1st upload
has caused the Debian Bug report #896696,
regarding lintian: please improve tag description to explain that python 2 
modules are only questioned on 1st upload
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.)


-- 
896696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: lintian
severity: wishlist
x-debbugs-cc: debian-de...@lists.debian.org

On Mon, Apr 23, 2018 at 06:33:20PM +0100, Chris Lamb wrote:
> For example, I think Holger is interpreting this particular tag as
> "this source package is shipping a Python 2.x" module. This is not
> the case. 
> 
> Rather, Lintian detects that this is the *initial* upload of the
> source package and, if so, asks the maintainer just to double-check
> that there is any requirement for it.
> 
> If there is such a need, the maintainer just needs to add a short,
> quick justification in the initial changelog entry and Lintian will
> then be silent on the matter.
> 
> It is thus not asking maintainers to drop Python 2 support…

Then the lintian message should be appended to say this only happens on
the first upload.

Thanks.

> As there can only be one initial upload by definition, adding an
> override here is not only a little silly given that it will trigger
> an "unused override" warning on the next upload, it can simply be
> avoided in the changelog entry as previously discussed, which 
> implicitly serves as some documentation too.

Maybe it's also worth pointing this out.

> (This talk of overrides was why I believe Holger is accidentally
> confusing the tag.)
 
Yes. And because the tag description needs improving. ;)


-- 
cheers,
Holger


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Mon, Apr 23, 2018 at 07:05:41PM +0100, Chris Lamb  wrote:
> It does, no? The current text is:

ah, thanks for clarifying. I indeed filed the bug only by judging what
was said and quoted on -devel@. Sorry for the noise!


-- 
cheers,
Holger


signature.asc
Description: PGP signature
--- End Message ---

Bug#896696: lintian: please improve tag description to explain that python 2 modules are only questioned on 1st upload

2018-04-23 Thread Chris Lamb 
Hi Holger,

> > For example, I think Holger is interpreting this particular tag as
> > "this source package is shipping a Python 2.x" module. This is not
> > the case. 
>
> Then the lintian message should be appended to say this only happens on
> the first upload.

It does, no? The current text is:

  Info: This package appears to be the initial packaging of a new upstream
   software package (ie. it contains a single changelog entry).

:)


Best wishes,

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

Bug#896696: lintian: please improve tag description to explain that python 2 modules are only questioned on 1st upload

2018-04-23 Thread Holger Levsen 
package: lintian
severity: wishlist
x-debbugs-cc: debian-de...@lists.debian.org

On Mon, Apr 23, 2018 at 06:33:20PM +0100, Chris Lamb wrote:
> For example, I think Holger is interpreting this particular tag as
> "this source package is shipping a Python 2.x" module. This is not
> the case. 
> 
> Rather, Lintian detects that this is the *initial* upload of the
> source package and, if so, asks the maintainer just to double-check
> that there is any requirement for it.
> 
> If there is such a need, the maintainer just needs to add a short,
> quick justification in the initial changelog entry and Lintian will
> then be silent on the matter.
> 
> It is thus not asking maintainers to drop Python 2 support…

Then the lintian message should be appended to say this only happens on
the first upload.

Thanks.

> As there can only be one initial upload by definition, adding an
> override here is not only a little silly given that it will trigger
> an "unused override" warning on the next upload, it can simply be
> avoided in the changelog entry as previously discussed, which 
> implicitly serves as some documentation too.

Maybe it's also worth pointing this out.

> (This talk of overrides was why I believe Holger is accidentally
> confusing the tag.)
 
Yes. And because the tag description needs improving. ;)


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Processed: Re: lintian: false positive non-consecutive-debian-revision on source package rename

2018-04-23 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 896675 + pending
Bug #896675 [lintian] lintian: false positive non-consecutive-debian-revision 
on source package rename
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#896675: lintian: false positive non-consecutive-debian-revision on source package rename

2018-04-23 Thread Chris Lamb 
tags 896675 + pending
thanks

Fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/ffbf44fcadc5d6e2160425d5cba446c80f2e80cf

  checks/changelog-file.pm |  3 ++-
  debian/changelog |  4 
  .../debian/debian/changelog.in   | 12 
  .../changelog-file-consecutive-debian-revision-unrel/desc| 10 ++
  .../changelog-file-consecutive-debian-revision-unrel/tags|  1 +
  5 files changed, 29 insertions(+), 1 deletion(-)


Regards,

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

Processed: your mail

2018-04-23 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 896012 lintian generates false positives for 
> library-not-linked-against-libc after gcc-7 7.3.0-16
Bug #896012 [lintian] Regression from gcc-7  7.3.0-16
Changed Bug title to 'lintian generates false positives for 
library-not-linked-against-libc after gcc-7 7.3.0-16' from 'Regression from 
gcc-7  7.3.0-16'.
>
End of message, stopping processing here.

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

Processed: your mail

2018-04-23 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 896012 lintian
Bug #896012 [gcc-7] Regression from gcc-7  7.3.0-16
Bug reassigned from package 'gcc-7' to 'lintian'.
No longer marked as found in versions gcc-7/7.3.0-16.
Ignoring request to alter fixed versions of bug #896012 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#896675: lintian: false positive non-consecutive-debian-revision on source package rename

2018-04-23 Thread Andreas Beckmann 
Package: lintian
Version: 2.5.83
Severity: normal

Hi,

I just forked src:nvidia-settings-legacy-390xx from src:nvidia-settings,
the changelog looks like this:

nvidia-settings-legacy-390xx (390.48-1) unstable; urgency=medium

  * Initial release of nvidia-settings for use with the legacy 390xx driver.
  * Build only a single binary package, no -dev package or shared library.

 -- Andreas Beckmann   Sun, 22 Apr 2018 20:34:56 +0200

nvidia-settings (390.48-2) unstable; urgency=medium

  * Add Provides+Conflicts: nvidia-settings-gtk-${nvidia:Version} to prevent
file conflicts with the legacy package built from the same upstream
version.
  * Use dh_missing --fail-missing.

 -- Andreas Beckmann   Sun, 22 Apr 2018 20:22:08 +0200

...

Reusing version numbers or going backwards is safe in this case since
the source package (and all remaining binary packages) got renamed, but
lintian triggers non-consecutive-debian-revision anyway.


Andreas

Bug#895574: lintian: binary-compiled-with-profiling-enabled test fails on Ubuntu's armhf

2018-04-23 Thread Steve McIntyre 
Hey Niels!

On Mon, Apr 23, 2018 at 05:42:00AM +, Niels Thykier wrote:
>
>When you write that it is a lot of effort to debug the lintian tests,
>then I wonder if it is because our documentation is lacking.  Like:
>
> * We can run the test in isolation (i.e. you don't have to run all the
>   tests).

No problem, I found that OK.

> * The output artefacts are left in the test directory (debian/test-out
>   by default) for manual analysis.

Ditto.

> * Lintian has a --keep-lab (-v) that leaves the lab behind (and prints
>   where it left it) for manual analysis.
> * Lintian can be run directly from the checkout (with any local
>   modifications) to able to experimental with changes.  Including
>   running it on the test artefacts to shave some overhead in the test
>   runner.
>
>Is there any of the above points, that would have made your debugging if
>you had known it ahead of time?  Or any of it, that we should have made
>more easily available in the documentation?

I've never done anything beyond the trivial with lintian before; my
normal initial approach of "grep the code for the error message"
didn't help very much when trying to find how things are run. Driving
thing from the "debuild" level (as I started) feels like you're 3 or 4
steps removed from the action, with *very* little clue as to where to
go next.

I started trying to find out how the binary "basic" was built, as that
was the target that was showing test problems. But I couldn't find any
output *anywhere* in the lintian build to show the compiler command
lines used for the test packages.

So I changed tack - I found where it was built by searching for it,
and manually ran readelf to check it. Fine, that showed it was ok and
I then found the Makefile for it.

However, going from there to the problem was still non-obvious. In my
case, it was difficult to work out exactly the commands run when a
test is performed. The particular example here comes from running
objdump against some binaries, then comparing error and warning
results against an expected set of results.

In the end, my path was:

 * dig, dig, dig
 * hack t/runtests to add "--debug" to the lintian invocation
 * that told me to run "t/runtests -v -v -k t
.../lintian-2.5.83/debian/test-out binaries-general" 
 * then I could add some simple printf-style debugging in the code for
   the profiling regex match
 * profit!

Some way of getting lintian to print the *actual commands run* for
its test would be helpful here.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.

Bug#896671: lintian: false positive description-synopsis-might-not-be-phrased-properly on 'e.g.'

2018-04-23 Thread Andreas Beckmann 
Package: lintian
Version: 2.5.83
Severity: normal

Hi,

this Description triggers a false positive:

Package: mysql-common
Description: MySQL database common files, e.g. /etc/mysql/my.cnf

I: mysql-common: description-synopsis-might-not-be-phrased-properly
N: 
N:The package synopsis (also known as the "short" description, ie. the
N:first line in the package's "Description:" field) either ends with a
N:full stop "." character or starts another sentence.

Probably add 'e\.?g|i\.?e' to the list of excluded words (currently 'etc').

if ($synopsis =~ m/(?

lintian_2.5.84_amd64.changes ACCEPTED into unstable

2018-04-23 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Apr 2018 11:50:51 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.84
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 895574 896010 896079 896133
Changes:
 lintian (2.5.84) unstable; urgency=medium
 .
   * checks/binaries.pm:
 + [CL] Apply patch from Steve McIntyre to fix profiling detection on
   armhf which was causing test failures in Ubuntu on that architecture.
   (Closes: #895574)
   * checks/fields.pm:
 + [CL] Don't warn about binary-package-depends-on-toolchain-package for
   Conflicts/Breaks relations.  Thanks to Guillem Jover for the report.
   (Closes: #896133)
   * checks/{files.desc,menu-format.*}, data/menu-format/known-desktop-keys:
 + [PW] Link to the latest version for all FreeDesktop standards
   * checks/python.desc:
 + [CL] Replace all instances of "specifies a dependency on Python 2.x
   which not be maintained past 2020" with a clarification that this
   refers to upstream's policy followed by a suggestion that it may be
   dropped after the release of Debian "buster".  Thanks to Adrian Bunk
   for the suggestion.  (Closes: #896079)
   * checks/source-copyright.pm:
 + [CL] Add the offending license name to the output of the
   "dep5-copyright-license-name-not-unique" tag.
 .
   * data/spelling/corrections:
 + [PW] Add a number of corrections.
 .
   * lib/Lintian/Collect/Package.pm:
 + [CL] Ensure directory names always end in a trailing "/" to prevent
   them being added multiple times to our index.  This was resulting in
   false-positives for the source-contains-empty-directory tag.  Thanks
   to James McCoy for the report.  (Closes: #896010)
 + [CL] Correct "as_anchored_root_dir" -> "has_anchored_root_dir" typo
   introduced in e0c833b3 and disable "anchored roots", otherwise
   resolve_path breaks (eg. systemd-complex-service-file).
 .
   * profiles/pureos/main.profile:
 + [CL] Also disable the "changelog-should-mention-nmu" and
   "source-nmu-has-incorrect-version-number" tags.
Checksums-Sha1:
 af73fae9ff23ff02787f6c847edc504ce386e13a 3511 lintian_2.5.84.dsc
 2bfc720d96ff19bf92adc30b0f8d7533a8f5b7cc 1553968 lintian_2.5.84.tar.xz
 ae583d3f24953a2970a48d76dbfb92f7b691b912 1116392 lintian_2.5.84_all.deb
 da6cbd3fd5ac2113ea667e3545d351a7e5b73473 16125 lintian_2.5.84_amd64.buildinfo
Checksums-Sha256:
 69ff88b5924f3c3218e451fb4d9fd024983270a65eb26db027833c3e79f39075 3511 
lintian_2.5.84.dsc
 89b963d28396c2cca9dc0afef9be49b819f7bf252e6e70d7d182839cd3b88f60 1553968 
lintian_2.5.84.tar.xz
 f41836946bb78677e7035f2b6887bba3770e4099ccab8c506c8b6e93d15a7215 1116392 
lintian_2.5.84_all.deb
 e30d1a81c44d25a5bdfe6a13b39ad7c3f4b489f4e58ce9545a09f481d4febf8f 16125 
lintian_2.5.84_amd64.buildinfo
Files:
 e31913614bcbc1bc5849e2e9843edc6b 3511 devel optional lintian_2.5.84.dsc
 4efc20bc8ca9a7b32dd062f01d1f08f7 1553968 devel optional lintian_2.5.84.tar.xz
 d56ccd8cc5f9fac56d6f93016bc49b8f 1116392 devel optional lintian_2.5.84_all.deb
 4093133be7359ba000949539e38928c3 16125 devel optional 
lintian_2.5.84_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlrdzbgACgkQHpU+J9Qx
HlhwQA/+MrLOtS/n643FW4Jb4qPCm5Jx5zOHt/NeETEyPQI6UByxou+tEZUBqR+0
OfpGSMxbxmo+6Px0jako9ixti1Kkj3NIdocRhso5RJ18yrfju87niCA7O6vgefAL
jZo4AImUEFBKa1BdSjnpeai8hMqaXePavZRP6vrv8+ZqS98o4/bFzBlpJZIS9jj5
BrWPEhtaXOJ9gtQ1w7AvW2x6IQzzQnRRyb5QDirGkql1+ymB6LRbWEZ06m49WtXp
8k3t3pe7izae4i3i377l6WDWX8QQ5L2msxfcHYt28vDuEOTQgWA/q+rjlzCHazYH
bnyWfldjKnKvuJQEw6jn0EQ5RJS7G34/6xDjW+b4OQ1C83g1iFvrcMd/PDw1Evmt
UAWGrw9+y2Ikt9ehBZtrVuJUdtOH4GezO4ucVaj1XuSauU/rt1XSZUNlJdgJg2F5
ny2clLowUCYV6pezDcFM2U52p8N0gHA20lEnsNPfLZSO4TFc8CSxIRz2Hxxtjs+p
xELE2muNdeSwO3Nx3VTqKeAKUe+B11GNPkepMffRNnVRid7z3sogr4eOxxCyyNFm
l4HVETwc20oC131LfbnRf5mfw4//gKIxam+IXIwzjypAcpLmH0HJqogYnrrreq/T
7/ZkEVdZ+8AjLLI9TWJ2YpLaBrpQZb/ZZGU/JfBEFACiAyCXpOE=
=Z8DQ
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of lintian_2.5.84_amd64.changes

2018-04-23 Thread Debian FTP Masters 
lintian_2.5.84_amd64.changes uploaded successfully to localhost
along with the files:
  lintian_2.5.84.dsc
  lintian_2.5.84.tar.xz
  lintian_2.5.84_all.deb
  lintian_2.5.84_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#896079: marked as done (lintian: misleading description for dependency-on-python-version-marked-for-end-of-life)

2018-04-23 Thread Debian Bug Tracking System 
Your message dated Mon, 23 Apr 2018 12:19:26 +
with message-id 
and subject line Bug#896079: fixed in lintian 2.5.84
has caused the Debian Bug report #896079,
regarding lintian: misleading description for 
dependency-on-python-version-marked-for-end-of-life
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.)


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

"The package specifies a dependency on Python 2.x which is due for deprecation 
and will not be maintained past 2020."

This is misleading, since Debian will (security) support Python 2.7
until at least mid-2022 (EOL for buster).

Please change this to:

"The package specifies a dependency on Python 2.x which will likely be dropped 
after buster."
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.84

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 896...@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: Mon, 23 Apr 2018 11:50:51 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.84
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 895574 896010 896079 896133
Changes:
 lintian (2.5.84) unstable; urgency=medium
 .
   * checks/binaries.pm:
 + [CL] Apply patch from Steve McIntyre to fix profiling detection on
   armhf which was causing test failures in Ubuntu on that architecture.
   (Closes: #895574)
   * checks/fields.pm:
 + [CL] Don't warn about binary-package-depends-on-toolchain-package for
   Conflicts/Breaks relations.  Thanks to Guillem Jover for the report.
   (Closes: #896133)
   * checks/{files.desc,menu-format.*}, data/menu-format/known-desktop-keys:
 + [PW] Link to the latest version for all FreeDesktop standards
   * checks/python.desc:
 + [CL] Replace all instances of "specifies a dependency on Python 2.x
   which not be maintained past 2020" with a clarification that this
   refers to upstream's policy followed by a suggestion that it may be
   dropped after the release of Debian "buster".  Thanks to Adrian Bunk
   for the suggestion.  (Closes: #896079)
   * checks/source-copyright.pm:
 + [CL] Add the offending license name to the output of the
   "dep5-copyright-license-name-not-unique" tag.
 .
   * data/spelling/corrections:
 + [PW] Add a number of corrections.
 .
   * lib/Lintian/Collect/Package.pm:
 + [CL] Ensure directory names always end in a trailing "/" to prevent
   them being added multiple times to our index.  This was resulting in
   false-positives for the source-contains-empty-directory tag.  Thanks
   to James McCoy for the report.  (Closes: #896010)
 + [CL] Correct "as_anchored_root_dir" -> "has_anchored_root_dir" typo
   introduced in e0c833b3 and disable "anchored roots", otherwise
   resolve_path breaks (eg. systemd-complex-service-file).
 .
   * profiles/pureos/main.profile:
 + [CL] Also disable the "changelog-should-mention-nmu" and
   "source-nmu-has-incorrect-version-number" tags.
Checksums-Sha1:
 af73fae9ff23ff02787f6c847edc504ce386e13a 3511 lintian_2.5.84.dsc
 2bfc720d96ff19bf92adc30b0f8d7533a8f5b7cc 1553968 lintian_2.5.84.tar.xz
 ae583d3f24953a2970a48d76dbfb92f7b691b912 1116392 lintian_2.5.84_all.deb
 da6cbd3fd5ac2113ea667e3545d351a7e5b73473 16125 lintian_2.5.84_amd64.buildinfo
Checksums-Sha256:
 69ff88b5924f3c3218e451fb4d9fd024983270a65eb26db027833c3e79f39075 3511 
lintian_2.5.84.dsc
 89b963d28396c2cca9dc0afef9be49b819f7bf252e6e70d7d182839cd3b88f60 1553968 
lintian_2.5.84.tar.xz
 f41836946bb78677e7035f2b6887bba3770e4099ccab8c506c8b6e93d15a7215 1116392

Bug#895574: marked as done (lintian: binary-compiled-with-profiling-enabled test fails on Ubuntu's armhf)

2018-04-23 Thread Debian Bug Tracking System 
Your message dated Mon, 23 Apr 2018 12:19:26 +
with message-id 
and subject line Bug#895574: fixed in lintian 2.5.84
has caused the Debian Bug report #895574,
regarding lintian: binary-compiled-with-profiling-enabled test fails on 
Ubuntu's armhf
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.)


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

Ubuntu runs its autopkgtests for all of its supported architectures.
One of lintian's tests (binary-compiled-with-profiling-enabled) fails
when the autopkgtest is run on armhf.

armhf is a bit different than the other Ubuntu architectures because
it uses a different kind of virtualization (sorry I don't remember the
details); not sure if that's relevant here or not.

You can see the test failures at
http://autopkgtest.ubuntu.com/packages/l/lintian/bionic/armhf

I'm letting you know that this issue prevents Ubuntu from being able
to automatically sync lintian, but instead we need to maintain a
manual diff. See http://ubuntudiff.debian.net/?query=-FPackage+lintian

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.84

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 895...@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: Mon, 23 Apr 2018 11:50:51 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.84
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 895574 896010 896079 896133
Changes:
 lintian (2.5.84) unstable; urgency=medium
 .
   * checks/binaries.pm:
 + [CL] Apply patch from Steve McIntyre to fix profiling detection on
   armhf which was causing test failures in Ubuntu on that architecture.
   (Closes: #895574)
   * checks/fields.pm:
 + [CL] Don't warn about binary-package-depends-on-toolchain-package for
   Conflicts/Breaks relations.  Thanks to Guillem Jover for the report.
   (Closes: #896133)
   * checks/{files.desc,menu-format.*}, data/menu-format/known-desktop-keys:
 + [PW] Link to the latest version for all FreeDesktop standards
   * checks/python.desc:
 + [CL] Replace all instances of "specifies a dependency on Python 2.x
   which not be maintained past 2020" with a clarification that this
   refers to upstream's policy followed by a suggestion that it may be
   dropped after the release of Debian "buster".  Thanks to Adrian Bunk
   for the suggestion.  (Closes: #896079)
   * checks/source-copyright.pm:
 + [CL] Add the offending license name to the output of the
   "dep5-copyright-license-name-not-unique" tag.
 .
   * data/spelling/corrections:
 + [PW] Add a number of corrections.
 .
   * lib/Lintian/Collect/Package.pm:
 + [CL] Ensure directory names always end in a trailing "/" to prevent
   them being added multiple times to our index.  This was resulting in
   false-positives for the source-contains-empty-directory tag.  Thanks
   to James McCoy for the report.  (Closes: #896010)
 + [CL] Correct "as_anchored_root_dir" -> "has_anchored_root_dir" typo
   introduced in e0c833b3 and disable "anchored roots", otherwise
   resolve_path breaks (eg. systemd-complex-service-file).
 .
   * profiles/pureos/main.profile:
 + [CL] Also disable the "changelog-should-mention-nmu" and
   "source-nmu-has-incorrect-version-number" tags.
Checksums-Sha1:
 af73fae9ff23ff02787f6c847edc504ce386e13a 3511 lintian_2.5.84.dsc
 2bfc720d96ff19bf92adc30b0f8d7533a8f5b7cc 1553968 lintian_2.5.84.tar.xz
 ae583d3f24953a2970a48d76dbfb92f7b691b912 1116392 lintian_2.5.84_all.deb
 da6cbd3fd5ac2113ea667e3545d351a7e5b73473 16125

Bug#896133: marked as done (lintian: False positives on binary-package-depends-on-toolchain-package with Breaks/Conflicts)

2018-04-23 Thread Debian Bug Tracking System 
Your message dated Mon, 23 Apr 2018 12:19:26 +
with message-id 
and subject line Bug#896133: fixed in lintian 2.5.84
has caused the Debian Bug report #896133,
regarding lintian: False positives on 
binary-package-depends-on-toolchain-package with Breaks/Conflicts
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.)


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

Hi!

The new tag binary-package-depends-on-toolchain-package seems to have
some false positives, as it checks all dependency fields, including
Breaks and Conflicts. But if another package uses those fields then it
most probably means it cannot work with those versions. So I think
these fields should be excluded?

This currently affects both dpkg-dev and dpkg-cross.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.84

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 896...@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: Mon, 23 Apr 2018 11:50:51 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.84
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 895574 896010 896079 896133
Changes:
 lintian (2.5.84) unstable; urgency=medium
 .
   * checks/binaries.pm:
 + [CL] Apply patch from Steve McIntyre to fix profiling detection on
   armhf which was causing test failures in Ubuntu on that architecture.
   (Closes: #895574)
   * checks/fields.pm:
 + [CL] Don't warn about binary-package-depends-on-toolchain-package for
   Conflicts/Breaks relations.  Thanks to Guillem Jover for the report.
   (Closes: #896133)
   * checks/{files.desc,menu-format.*}, data/menu-format/known-desktop-keys:
 + [PW] Link to the latest version for all FreeDesktop standards
   * checks/python.desc:
 + [CL] Replace all instances of "specifies a dependency on Python 2.x
   which not be maintained past 2020" with a clarification that this
   refers to upstream's policy followed by a suggestion that it may be
   dropped after the release of Debian "buster".  Thanks to Adrian Bunk
   for the suggestion.  (Closes: #896079)
   * checks/source-copyright.pm:
 + [CL] Add the offending license name to the output of the
   "dep5-copyright-license-name-not-unique" tag.
 .
   * data/spelling/corrections:
 + [PW] Add a number of corrections.
 .
   * lib/Lintian/Collect/Package.pm:
 + [CL] Ensure directory names always end in a trailing "/" to prevent
   them being added multiple times to our index.  This was resulting in
   false-positives for the source-contains-empty-directory tag.  Thanks
   to James McCoy for the report.  (Closes: #896010)
 + [CL] Correct "as_anchored_root_dir" -> "has_anchored_root_dir" typo
   introduced in e0c833b3 and disable "anchored roots", otherwise
   resolve_path breaks (eg. systemd-complex-service-file).
 .
   * profiles/pureos/main.profile:
 + [CL] Also disable the "changelog-should-mention-nmu" and
   "source-nmu-has-incorrect-version-number" tags.
Checksums-Sha1:
 af73fae9ff23ff02787f6c847edc504ce386e13a 3511 lintian_2.5.84.dsc
 2bfc720d96ff19bf92adc30b0f8d7533a8f5b7cc 1553968 lintian_2.5.84.tar.xz
 ae583d3f24953a2970a48d76dbfb92f7b691b912 1116392 lintian_2.5.84_all.deb
 da6cbd3fd5ac2113ea667e3545d351a7e5b73473 16125 lintian_2.5.84_amd64.buildinfo
Checksums-Sha256:
 69ff88b5924f3c3218e451fb4d9fd024983270a65eb26db027833c3e79f39075 3511 
lintian_2.5.84.dsc
 89b963d28396c2cca9dc0afef9be49b819f7bf252e6e70d7d182839cd3b88f60 1553968 
lintian_2.5.84.tar.xz

Bug#896010: marked as done (lintian: FP for source-contains-empty-directory if directory isn't listed with trailing slash)

2018-04-23 Thread Debian Bug Tracking System 
Your message dated Mon, 23 Apr 2018 12:19:26 +
with message-id 
and subject line Bug#896010: fixed in lintian 2.5.84
has caused the Debian Bug report #896010,
regarding lintian: FP for source-contains-empty-directory if directory isn't 
listed with trailing slash
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.)


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

While prepping the 1.10.0-1 subversion upload, I noticed that lintian
flagged every single directory in the upstream tarball with
"source-contains-empty-directory".

Comparing this to other tarballs I have available, it appears this is
due to the fact that tar doesn't show a trailing slash for the
directories.

$ tar -tavf subversion_1.10.0.orig.tar.gz | grep '^d.*1.10.0/build'
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 subversion-1.10.0/build
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/win32
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/hudson
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/hudson/jobs
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/hudson/jobs/subversion-1.6.x-ubuntu
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/hudson/jobs/subversion-trunk-solaris
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/hudson/jobs/subversion-1.6.x-solaris
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/hudson/jobs/subversion-trunk-ubuntu
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/hudson/jobs/subversion-doxygen
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/hudson/jobs/subversion-javadoc
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/generator
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/generator/util
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/generator/swig
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/generator/templates
drwxrwxr-x julianfoad/julianfoad  0 2018-04-11 02:47 
subversion-1.10.0/build/ac-macros

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.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.30-15
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.19.0.5
ii  file  1:5.32-2
ii  gettext   0.19.8.1-6
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.34
ii  libarchive-zip-perl   1.60-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.39-1
ii  libdpkg-perl  1.19.0.5
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.99-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.1-6
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.73-1
ii  libxml-simple-perl2.25-1
ii  libyaml-libyaml-perl  0.69+repack-1
ii  man-db2.8.3-2
ii  patchutils0.3.4-2
ii  perl  5.26.1-6
ii  t1utils   1.41-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b4

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.19.0.5
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.52-1

-- no debconf information
--- End

A

2018-04-23 Thread Maurice Sarfati 


Envoyé de mon iPhone

Jenkins build is back to normal : lintian-tests_sid #2826

2018-04-23 Thread jenkins 
See

Build failed in Jenkins: lintian-tests_sid #2825

2018-04-23 Thread jenkins 
See 


Changes:

[lamby] checks/binaries.pm: Apply patch from Steve McIntyre to fix profiling

[lamby] debian/changelog: Group all checks/* foo together.

--
[...truncated 234.64 KB...]
Adding debian:Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015.pem
Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
Adding debian:Go_Daddy_Class_2_CA.pem
Adding debian:Global_Chambersign_Root_-_2008.pem
Adding debian:GlobalSign_Root_CA_-_R3.pem
Adding debian:GlobalSign_Root_CA_-_R2.pem
Adding debian:GlobalSign_Root_CA.pem
Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem
Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem
Adding debian:GeoTrust_Universal_CA_2.pem
Adding debian:GeoTrust_Universal_CA.pem
Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem
Adding debian:GeoTrust_Primary_Certification_Authority.pem
Adding debian:GeoTrust_Global_CA.pem
Adding debian:GDCA_TrustAUTH_R5_ROOT.pem
Adding debian:Entrust_Root_Certification_Authority_-_G2.pem
Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem
Adding debian:Entrust_Root_Certification_Authority.pem
Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
Adding debian:EE_Certification_Centre_Root_CA.pem
Adding debian:EC-ACC.pem
Adding debian:E-Tugra_Certification_Authority.pem
Adding debian:DigiCert_Trusted_Root_G4.pem
Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
Adding debian:DigiCert_Global_Root_G3.pem
Adding debian:DigiCert_Global_Root_G2.pem
Adding debian:DigiCert_Global_Root_CA.pem
Adding debian:DigiCert_Assured_ID_Root_G3.pem
Adding debian:DigiCert_Assured_ID_Root_G2.pem
Adding debian:DigiCert_Assured_ID_Root_CA.pem
Adding debian:Deutsche_Telekom_Root_CA_2.pem
Adding debian:DST_Root_CA_X3.pem
Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
Adding debian:Cybertrust_Global_Root.pem
Adding debian:Comodo_AAA_Services_root.pem
Adding debian:Chambers_of_Commerce_Root_-_2008.pem
Adding debian:Certum_Trusted_Network_CA_2.pem
Adding debian:Certum_Trusted_Network_CA.pem
Adding debian:Certplus_Root_CA_G2.pem
Adding debian:Certplus_Root_CA_G1.pem
Adding debian:Certplus_Class_2_Primary_CA.pem
Adding debian:Certinomis_-_Root_CA.pem
Adding debian:Certigna.pem
Adding debian:COMODO_RSA_Certification_Authority.pem
Adding debian:COMODO_ECC_Certification_Authority.pem
Adding debian:COMODO_Certification_Authority.pem
Adding debian:CFCA_EV_ROOT.pem
Adding debian:CA_Disig_Root_R2.pem
Adding debian:Buypass_Class_3_Root_CA.pem
Adding debian:Buypass_Class_2_Root_CA.pem
Adding debian:Baltimore_CyberTrust_Root.pem
Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
Adding debian:Atos_TrustedRoot_2011.pem
Adding debian:Amazon_Root_CA_4.pem
Adding debian:Amazon_Root_CA_3.pem
Adding debian:Amazon_Root_CA_2.pem
Adding debian:Amazon_Root_CA_1.pem
Adding debian:AffirmTrust_Premium_ECC.pem
Adding debian:AffirmTrust_Premium.pem
Adding debian:AffirmTrust_Networking.pem
Adding debian:AffirmTrust_Commercial.pem
Adding debian:AddTrust_External_Root.pem
Adding debian:Actalis_Authentication_Root_CA.pem
Adding debian:AC_RAIZ_FNMT-RCM.pem
Adding debian:ACCVRAIZ1.pem
done.
Setting up openjdk-9-jdk-headless:amd64 (9.0.4+12-4) ...
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jlink to 
provide /usr/bin/jlink (jlink) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jmod to 
provide /usr/bin/jmod (jmod) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jhsdb to 
provide /usr/bin/jhsdb (jhsdb) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-amd64/bin/jrunscript to 
provide /usr/bin/jrunscript (jrunscript) in auto mode
update-alternatives: using

Processed: Re: lintian: binary-compiled-with-profiling-enabled test fails on Ubuntu's armhf

2018-04-23 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 895574 + pending
Bug #895574 [src:lintian] lintian: binary-compiled-with-profiling-enabled test 
fails on Ubuntu's armhf
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#895574: lintian: binary-compiled-with-profiling-enabled test fails on Ubuntu's armhf

2018-04-23 Thread Chris Lamb 
tags 895574 + pending
thanks

> […]

Awesome, thanks Steve! Applied in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/2fd37bce3554298dcaa1605c02da49be4c77090a

  checks/binaries.pm | 3 ++-
  debian/changelog   | 4 
  2 files changed, 6 insertions(+), 1 deletion(-)


Regards,

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

Bug#895574: lintian: binary-compiled-with-profiling-enabled test fails on Ubuntu's armhf

2018-04-23 Thread Niels Thykier 
Steve McIntyre:
> [...] Wow, debugging lintian tests is a lot of effort!
> 

Hi Steve,

Thanks for your work on lintian. :)

When you write that it is a lot of effort to debug the lintian tests,
then I wonder if it is because our documentation is lacking.  Like:

 * We can run the test in isolation (i.e. you don't have to run all the
   tests).
 * The output artefacts are left in the test directory (debian/test-out
   by default) for manual analysis.
 * Lintian has a --keep-lab (-v) that leaves the lab behind (and prints
   where it left it) for manual analysis.
 * Lintian can be run directly from the checkout (with any local
   modifications) to able to experimental with changes.  Including
   running it on the test artefacts to shave some overhead in the test
   runner.

Is there any of the above points, that would have made your debugging if
you had known it ahead of time?  Or any of it, that we should have made
more easily available in the documentation?


Thanks,
~Niels