Bug#864733: marked as done (Error: "Download error: Download Error: 404 Not Found", Debian stable)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 21:28:10 +0900
with message-id 

and subject line Re: [Pkg-privacy-maintainers] Bug#864733: Error: "Download 
error: Download Error: 404 Not Found", Debian stable
has caused the Debian Bug report #864733,
regarding Error: "Download error: Download Error: 404 Not Found", Debian stable
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.)


-- 
864733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.1.9-1+deb8u3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

torbrowser-launcher fails to download a new version of tor browser:

niehaus@host:~$ LC_ALL=C torbrowser-launcher 
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.1.9+deb8u3
https://github.com/micahflee/torbrowser-launcher
Initializing Tor Browser Launcher
Importing keys
gpg: key 63FEE659: "Erinn Clark " not changed
gpg: Total number processed: 1
gpg:  unchanged: 1
gpg: key 93298290: "Tor Browser Developers (signing key) 
" not changed
gpg: Total number processed: 1
gpg:  unchanged: 1
Starting launcher dialog
LATEST VERSION 6.5.2
Checked for update within 24 hours, skipping
TBB is not installed, attempting to install 6.5.2
Running task: download_sig
Downloading 
https://dist.torproject.org/torbrowser/6.5.2/tor-browser-linux64-6.5.2_en-US.tar.xz.asc
Updating over Tor
Download error: Download Error: 404 Not Found 


I think it might have happened because even 6.5.2 is not the latest version but 
7.0 is now out. 

Renders torbrowser-launcher unusable to most users on stable ...


Thank you very much!


Sebastiab



-- System Information:
Debian Release: 8.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages torbrowser-launcher depends on:
ii  gnupg1.4.18-7+deb8u3
ii  python-gtk2  2.24.0-4
ii  python-lzma  0.5.3-2+b1
ii  python-parsley   1.2-1
ii  python-psutil2.1.1-1+b1
ii  python-twisted   14.0.2-3
ii  python-txsocksx  1.13.0.3-1
ii  tor  0.2.5.14-1
ii  wmctrl   1.07-7

torbrowser-launcher recommends no packages.

Versions of packages torbrowser-launcher suggests:
pn  apparmor   
pn  python-pygame  

-- no debconf information
--- End Message ---
--- Begin Message ---
It's fixed in sid/buster release, so closing this ticket.
If it occurs on your side, please reopen or create a new ticket.
Thanks!

-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1--- End Message ---

Bug#845989: marked as done (browser can't be downloaded because of invalid SSL certificate)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 21:33:27 +0900
with message-id 

Bug#871057: marked as done (synapse: FTBFS with vala 0.36)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:36:55 +
with message-id 
and subject line Bug#871057: fixed in synapse 0.2.99.2-3
has caused the Debian Bug report #871057,
regarding synapse: FTBFS with vala 0.36
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.)


-- 
871057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synapse
Version: 0.2.99.2-2
Severity: important
User: pkg-vala-maintain...@lists.alioth.debian.org
Usertags: vala-0.36
Tags: buster sid

synapse fails to build from source with vala 0.36 which is currently
in experimental and will be uploaded to unstable soon.

You can find a build log from Ubuntu 17.10 Alpha at
https://launchpad.net/~jbicha/+archive/ubuntu/vala36/+build/12762656

There were a few commits on the upstream bzr branch to fix some of the
vala 0.36 issues but I don't think all were fixed.

On behalf of the Debian Vala maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: synapse
Source-Version: 0.2.99.2-3

We believe that the bug you reported is fixed in the latest version of
synapse, 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 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tomasz Buchert  (supplier of updated synapse 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: SHA512

Format: 1.8
Date: Tue, 19 Sep 2017 01:08:00 +0200
Source: synapse
Binary: synapse synapse-dbg
Architecture: source
Version: 0.2.99.2-3
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Buchert 
Changed-By: Tomasz Buchert 
Description:
 synapse- semantic file launcher
 synapse-dbg - semantic file launcher - debug package
Closes: 871057
Changes:
 synapse (0.2.99.2-3) unstable; urgency=medium
 .
   * d/patches: import changes from bzr repo to fix FTBFS (Closes: #871057)
   * d/control: use debhelper 10
   * d/watch: use watch version 4
   * d/rules: drop obsolete dbg package
   * Bumped Standards-Version to 4.0.0 (no changes needed)
Checksums-Sha1:
 0aa90597c796cfc3e6c6a11c23cb54740deeb659 1718 synapse_0.2.99.2-3.dsc
 12d1df46159aa9959197eb1c80307bea45526c21 24380 synapse_0.2.99.2-3.debian.tar.xz
 9f74c281c79c5be7d0b638e170f355ba1e6bb135 14125 
synapse_0.2.99.2-3_amd64.buildinfo
Checksums-Sha256:
 1564d679f301a89401006f4b8493dcfc302199677b566742e486aa563475a3ae 1718 
synapse_0.2.99.2-3.dsc
 e93a21728beb7b65279b47bfc8f06df097c07dc8ef45fddce1035c3e9bc93ba5 24380 
synapse_0.2.99.2-3.debian.tar.xz
 9e6bf337e81a540a90743e862b7a64511c7308ee96eab073406d7af109754883 14125 
synapse_0.2.99.2-3_amd64.buildinfo
Files:
 b1c6bc10f83b576f5c9a31ec22f8b9c9 1718 utils optional synapse_0.2.99.2-3.dsc
 b5662c7ae291b665456d0ecfc71c387d 24380 utils optional 
synapse_0.2.99.2-3.debian.tar.xz
 891d1f0e6ca2e234670e186ab30f6ccb 14125 utils optional 
synapse_0.2.99.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEs7i9UOfOjw7pOBilgsIKSinLv9UFAlnCFsAACgkQgsIKSinL
v9V7dAgAv5oxjbtvKnBkLaVzSoJ/bpVw/L3obqeq8j3jeyCGZmitJjT5dIyhuOZm
wfa0no2qWUCSmLzn3o8GmrUoX7owGSE8SPIv8i72lqlzcfglSxZtIAZMMDTYr2YG
IFMCuC4nYpRZmT1ECC4Dt/tzgNLN7cxflyr1WPjzSlVy3UGs9jKd9SFURvm7V0sC
X0if+ulPGaDgcX1sCprG08n3uY122KFh+wO7OFI1lemyUPa3NYm5dUc/y7+mm8Er
bcGjUGPM4jNBmrruRCl0CxqDhX8VRlIstTeiU5H6dnnrYm7/KzQOV5AeAyWhPp+m
3oU2ilqnJwtcxPSimO+bznO35Wyusw==
=ylz7
-END PGP SIGNATURE End Message ---

Bug#871637: marked as done (ITP: silx -- Toolbox for X-Ray data analysis)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:31 +
with message-id 
and subject line Bug#871637: fixed in silx 0.5.0+dfsg-1
has caused the Debian Bug report #871637,
regarding ITP: silx -- Toolbox for X-Ray data analysis
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.)


-- 
871637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?Picca_Fr=C3=A9d=C3=A9ric-Emmanuel?= 

* Package name: silx
  Version : 0.5.0
  Upstream Author : European Synchrotron Radiation Facility Data analysis unit 
(s...@esrf.fr)
* URL : https://github.com/silx-kit/silx
* License : LGPL, MIT
  Programming Lang: Python
  Description : Toolbox for X-Ray data analysis

 The silx project aims at providing a collection of Python packages to
 support the development of data assessment, reduction and analysis
 applications at synchrotron radiation facilities. It aims at
 providing reading/writing different file formats, data reduction
 routines and a set of Qt widgets to browse and visualize data.
 .
 The current version provides :
 .
  * reading HDF5 file format (with support of SPEC file format)
  * histogramming
  * fitting
  * 1D and 2D visualization using multiple backends (matplotlib or OpenGL)
  * image plot widget with a set of associated tools (See changelog file).
  * Unified browser for HDF5, SPEC and image file formats supporting inspection
and visualization of n-dimensional datasets.
  * Unified viewer (silx view filename) for HDF5, SPEC and image file formats
  * OpenGL-based widget to display 3D scalar field with
isosurface and cutting plane.

I need to package this because it is a new dependency for PyFAI and the next 
Pymca
--- End Message ---
--- Begin Message ---
Source: silx
Source-Version: 0.5.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
silx, 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 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated silx 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: Wed, 02 Aug 2017 11:00:20 +0100
Source: silx
Binary: silx python-silx python-silx-dbg python3-silx python3-silx-dbg 
python-silx-doc
Architecture: source i386 all
Version: 0.5.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 python-silx - Toolbox for X-Ray data analysis - Python2 library
 python-silx-dbg - Toolbox for X-Ray data analysis - Python2 debug
 python-silx-doc - Toolbox for X-Ray data analysis - Documentation
 python3-silx - Toolbox for X-Ray data analysis - Python3
 python3-silx-dbg - Toolbox for X-Ray data analysis - Python3 debug
 silx   - Toolbox for X-Ray data analysis - Executables
Closes: 871637
Changes:
 silx (0.5.0+dfsg-1) unstable; urgency=medium
 .
   * Initial release (Closes: #871637)
Checksums-Sha1:
 cb87d3b38ede67d7918417e98bf248b47159e985 3525 silx_0.5.0+dfsg-1.dsc
 644cdbb329874d97f8f75bb7ef190a0f0a36d60e 7225431 silx_0.5.0+dfsg.orig.tar.gz
 6d19eb8735f167cea7d4213b57ec5b42096a7919 9640 silx_0.5.0+dfsg-1.debian.tar.xz
 948ceb21c838c21d9af7e167e864daf591d0bee0 2774704 
python-silx-dbg-dbgsym_0.5.0+dfsg-1_i386.deb
 7531995f516ef601d5b7848b2291470a5e0700b5 750820 
python-silx-dbg_0.5.0+dfsg-1_i386.deb
 6285a42ab90ccf615b95e12dd5a5d91886565c8f 2494514 
python-silx-dbgsym_0.5.0+dfsg-1_i386.deb
 a439b6aa6fd986de180af6d928cbcb9617c98343 6597576 
python-silx-doc_0.5.0+dfsg-1_all.deb
 856c4922ede2e616ecf16b74ffc2519d93fd9e2f 1453620 
python-silx_0.5.0+dfsg-1_i386.deb
 3f84c7bff17e5582c9c1d627c92534036e19f683 3078542 
python3-silx-dbg-dbgsym_0.5.0+dfsg-1_i386.deb
 786024a6a48b9eebe014de2d56b0439e311aa711 730288 
python3-silx-dbg_0.5.0+dfsg-1_i386.deb
 b585615a9955c40a0a9fedc487d397c3258e2e0a 2761400 
python3-silx-dbgsym_0.5.0+dfsg-1_i386.deb
 

Bug#874576: marked as done (ITP: ruby-diaspora-federation-json-schema -- diaspora federation json schemas)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:27 +
with message-id 
and subject line Bug#874576: fixed in ruby-diaspora-federation-json-schema 
0.2.1-1
has caused the Debian Bug report #874576,
regarding ITP: ruby-diaspora-federation-json-schema -- diaspora federation json 
schemas
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.)


-- 
874576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Kartik Kulkarni 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: ruby-diaspora-federation-json-schema
  Version : 0.2.1
  Upstream Author : Benjamin Neff
cmrd Senya
* URL : https://github.com/diaspora/diaspora_federation
* License : AGPL-3.0
  Programming Lang: Ruby
  Description : diaspora federation json schemas
  This gem provides JSON schemas (currently one schema) for validating JSON
  serialized federation objects.

  It is a dependency of gitlab 9

  I am not a debian member and would like to maintain this package for
a long term and would like to join the Ruby maintainers group, Praveen
had agreed to sponsor this package.
--- End Message ---
--- Begin Message ---
Source: ruby-diaspora-federation-json-schema
Source-Version: 0.2.1-1

We believe that the bug you reported is fixed in the latest version of
ruby-diaspora-federation-json-schema, 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 874...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kartik Kulkarni  (supplier of updated 
ruby-diaspora-federation-json-schema 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: Thu, 07 Sep 2017 12:28:47 +
Source: ruby-diaspora-federation-json-schema
Binary: ruby-diaspora-federation-json-schema
Architecture: source all
Version: 0.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Kartik Kulkarni 
Description:
 ruby-diaspora-federation-json-schema - diaspora federation json schemas
Closes: 874576
Changes:
 ruby-diaspora-federation-json-schema (0.2.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #874576)
Checksums-Sha1:
 ee4cd778f35c591cac4e8df72a9f65651ad17a9e 2333 
ruby-diaspora-federation-json-schema_0.2.1-1.dsc
 41946840c07bb49db5b8502ca25a85b05b6e6ae3 2173 
ruby-diaspora-federation-json-schema_0.2.1.orig.tar.gz
 e485a888aac16d9a89f73a09ec58e84204d19b23 12636 
ruby-diaspora-federation-json-schema_0.2.1-1.debian.tar.xz
 698d81e3d21eac1468aa0ed71b4cd3ae1317d7e6 14912 
ruby-diaspora-federation-json-schema_0.2.1-1_all.deb
 560b07e7e5b88bb3c309db858c9185822c6a6dc2 6697 
ruby-diaspora-federation-json-schema_0.2.1-1_amd64.buildinfo
Checksums-Sha256:
 6282225aa835a00265a75de1c8802e61ca4cd9c0c306d487cae89f5add20be60 2333 
ruby-diaspora-federation-json-schema_0.2.1-1.dsc
 fc0088659f80cc4562a34f066f36fe7e38d10f00a29721ff6585b8562e08b2b7 2173 
ruby-diaspora-federation-json-schema_0.2.1.orig.tar.gz
 9c43428f18a09ef714b91950328639af017184950e314e41020a7ee2d60c1552 12636 
ruby-diaspora-federation-json-schema_0.2.1-1.debian.tar.xz
 502a2e672df3c225b47bdb5a0695ed58c4324a92419d7e27c61298774aec692d 14912 
ruby-diaspora-federation-json-schema_0.2.1-1_all.deb
 41ee90c8fd06c00f6b2d07a6a5dc5a0ccf14d2a255a7e109fee325038f9892ca 6697 
ruby-diaspora-federation-json-schema_0.2.1-1_amd64.buildinfo
Files:
 ef7d9450117201c2ba16272ca4443e99 2333 ruby optional 
ruby-diaspora-federation-json-schema_0.2.1-1.dsc
 bc113370d94144be1d58816b46fd2b7b 2173 ruby optional 
ruby-diaspora-federation-json-schema_0.2.1.orig.tar.gz
 fe1a57723957e2177a9f6699d77198e3 12636 ruby optional 
ruby-diaspora-federation-json-schema_0.2.1-1.debian.tar.xz
 66d90d4591a6a667f0273c8ac50b7b2a 14912 ruby optional 
ruby-diaspora-federation-json-schema_0.2.1-1_all.deb
 35afdab7228aa9d959932476d98dee05 6697 ruby optional 
ruby-diaspora-federation-json-schema_0.2.1-1_amd64.buildinfo

-BEGIN 

Bug#872717: marked as done (klatexformula: Fails to start due to missing sqlite driver)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:16 +
with message-id 
and subject line Bug#872717: fixed in klatexformula 4.0.0-1
has caused the Debian Bug report #872717,
regarding klatexformula: Fails to start due to missing sqlite driver
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.)


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

Package: klatexformula
Version: 3.3.0~beta-1+b2
Severity: normal

Dear Maintainer,

When attempting to start klatexformula, I get the following error 
message:

/home/debian/.klatexformula/library.klf.db
(SQLITE database):
Driver not loaded Driver not loaded

(and then the application crashes).

I did some digging and found an older, but similar bug report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712019

After installing libqt4-sql-sqlite as discussed there, the application
started without issues. It is possible this issue has regressed.

(Originally reported in Ubuntu as
https://bugs.launchpad.net/ubuntu/+source/klatexformula/+bug/1708772)

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages klatexformula depends on:
ii  libc6  2.24-14
ii  libgcc11:7.2.0-1
ii  libklatexformula3  3.3.0~beta-1+b2
ii  libqt4-dbus4:4.8.7+dfsg-11
ii  libqt4-sql 4:4.8.7+dfsg-11
ii  libqt4-xml 4:4.8.7+dfsg-11
ii  libqtcore4 4:4.8.7+dfsg-11
ii  libqtgui4  4:4.8.7+dfsg-11
ii  libstdc++6 7.2.0-1

klatexformula recommends no packages.

klatexformula suggests no packages.

-- no debconf information

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
--- End Message ---
--- Begin Message ---
Source: klatexformula
Source-Version: 4.0.0-1

We believe that the bug you reported is fixed in the latest version of
klatexformula, 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 872...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Winchen  (supplier of updated klatexformula 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: SHA512

Format: 1.8
Date: Sun, 17 Sep 2017 20:52:18 +0200
Source: klatexformula
Binary: klatexformula libklatexformula4 libklatexformula4-dev 
libklatexformula4-doc
Architecture: source amd64 all
Version: 4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Winchen 
Changed-By: Tobias Winchen 
Description:
 klatexformula - GUI to easily get an image from a LaTeX formula or equation
 libklatexformula4 - Runtime libraries for klatexformula
 libklatexformula4-dev - Runtime libraries for klatexformula, development files
 libklatexformula4-doc - Runtime libraries for klatexformula, API documentation
Closes: 872717
Changes:
 klatexformula (4.0.0-1) unstable; urgency=medium
 .
   [ Tobias Winchen ]
   * New upstream release
   * Updated to standards version 4.0.0
   * Added dependency on libqt5sql5-sqlite (Closes: #872717)
   * Updated maintainer e-mail address and vcs-git repository
   * Use manpage generated with help2man
 .
   [ Juhani Numminen ]
   * Update further to standards version 4.1.0
 - Priority changed to optional as extra is now deprecated
   * Update to dh compat 10
 - Drop --parallel from dh $@
   * Call cmake through dh_auto_configure, allowing us to drop debian/clean
   * Enable Multi-Arch and mark lib* binary packages accordingly
   * Enable all hardening flags
   * Enable -Wl,--as-needed to avoid unnecessary dependencies
   * Disable rpaths using -DCMAKE_SKIP_RPATH=TRUE, drop Build-Dep on chrpath
   * Disable bundling of Computer Modern Unicode fonts into the executable
   * Add new binary package libklatexformula4-doc
 - New Build-Depends-Indep on doxygen and graphviz
 - New Build-Depends 

Bug#876180: marked as done (ITP: ruby-rblineprof -- line-profiler for ruby)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:29 +
with message-id 
and subject line Bug#876180: fixed in ruby-rblineprof 0.3.7-1
has caused the Debian Bug report #876180,
regarding ITP: ruby-rblineprof -- line-profiler for ruby
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.)


-- 
876180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

from rubygems.org/gems/rblineprof
dependency of gitlab 9.5









signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-rblineprof
Source-Version: 0.3.7-1

We believe that the bug you reported is fixed in the latest version of
ruby-rblineprof, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-rblineprof 
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: Tue, 19 Sep 2017 15:06:45 +0530
Source: ruby-rblineprof
Binary: ruby-rblineprof
Architecture: source amd64
Version: 0.3.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-rblineprof - line-profiler for ruby
Closes: 876180
Changes:
 ruby-rblineprof (0.3.7-1) unstable; urgency=medium
 .
   * Initial release (Closes: #876180)
Checksums-Sha1:
 0bede8d1812e83d42136259714bc0ee255af148c 2126 ruby-rblineprof_0.3.7-1.dsc
 f7730035719e777c9d95b74c579c77013515c836 9182 ruby-rblineprof_0.3.7.orig.tar.gz
 3d4b0147e5672498b23c1a691de55f557949e8ed 1944 
ruby-rblineprof_0.3.7-1.debian.tar.xz
 683f70f9ec8d2d20f9475744500819e88a9f4f83 14642 
ruby-rblineprof-dbgsym_0.3.7-1_amd64.deb
 ca093d56eaaf1eeca4c5d5afc9a57241a9f233a8 6706 
ruby-rblineprof_0.3.7-1_amd64.buildinfo
 233fb7ce1f0c333be19abfa27a6b865b2ff3b8f3 7956 ruby-rblineprof_0.3.7-1_amd64.deb
Checksums-Sha256:
 178e5b0fac478fd330c3cf969967c882e278db25adfa2f87e32b6f0ce4e5c3c5 2126 
ruby-rblineprof_0.3.7-1.dsc
 75ca245c55c18c0892f9a164aaa7d2e5abc535340d4e64a430cfd8ee5af600a0 9182 
ruby-rblineprof_0.3.7.orig.tar.gz
 b53bac97aeb2d8c7a91cada4ef60de8582b6852464901b5698a762d09ff149de 1944 
ruby-rblineprof_0.3.7-1.debian.tar.xz
 cc4bacaad1a7ff833268ffbcf23c1bcd99ccc916fbd9530968804a0ead5a8c24 14642 
ruby-rblineprof-dbgsym_0.3.7-1_amd64.deb
 e237f968b5e9b45e6e2d2149462a8991cf8179f2cf31b25e8263c1bf2f966c43 6706 
ruby-rblineprof_0.3.7-1_amd64.buildinfo
 4d413f88aefa184ca093b0fbf1afdec51683a512981139782a4388ddcb2a 7956 
ruby-rblineprof_0.3.7-1_amd64.deb
Files:
 f9f1106c047cfe43bb23fa7054e2b155 2126 ruby optional ruby-rblineprof_0.3.7-1.dsc
 fb75a34411e9968ed8759065c49f159a 9182 ruby optional 
ruby-rblineprof_0.3.7.orig.tar.gz
 fe6e74050b7d4a13b0ae85c65291f8bb 1944 ruby optional 
ruby-rblineprof_0.3.7-1.debian.tar.xz
 6fb2d602a44a40d605d7670ce342101c 14642 debug optional 
ruby-rblineprof-dbgsym_0.3.7-1_amd64.deb
 783f37ebc9adadadf68ab23e862701f7 6706 ruby optional 
ruby-rblineprof_0.3.7-1_amd64.buildinfo
 07eb7b09554c4d22fadd7f69543538fd 7956 ruby optional 
ruby-rblineprof_0.3.7-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlnA5xoACgkQzh+cZ0US
wirszA//XAS1Qvv01XdfT2qz6M4blgOFsBT8aHvpLd9ZXwTZkvfXaRCM0C99pZGY
ruSP2NHxlTYIkraxSaXrldMno/29r3m7g/UZy9dksTgSp8T/YOeELM4YPMTRTdoZ
JnmKmlRaN4GWDmYOWfP/d4ZFYi+4b8k+es9zW60tbaBKgOQQUeJa2lUzhDg+Esd5
keKcatoNIZqtIklkDHzAQmJTJBGqig57Zu+1Rx0A+LkeMJXut/REgAkNsoHIJ22i
t4DQ9zFGNd4h/G2vT9B0JeQkTDXLXDfvG5qF8eoPmkeT7UY6dbrH3BcJDUe5IN0S
+CYiEMqg9BBRDpyYW1uIdBHg1jo0q28FHAHqVtsscigxQ2xq8obP5igholZ7mmCy
Hl0FmIHimFGaOGgpOtaf5cYiJb9ru7D3jR9f06g8hKq7AKYlEP986MGUTOvjLw2t
61bhrsUPNs6TcQx2Nq+pi9yEZOuIcK9DClflvwaPNGItIOt3SbkN1utxMM00T0zG
z8Nazc7PPoheI8hYEt27h3ox0V6u1yRtTjVnYxz149EpeRXwoGR6kOGpRrovNhQF
IQ9I+tmpHmvyIUM17s/sg0PMAjL5EjqK2AErPZC+CsNLLZpgxtvhNBMDaR13xq7r
pez5AkzktQ0AkXAAx8i01d4LEuTxp1fDurBQgmxHJUxisw2qoKI=
=opNv
-END PGP 

Bug#876244: marked as done (libpng1.6 FTBFS with debhelper 10.9)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:34:58 +
with message-id 
and subject line Bug#876244: fixed in libpng1.6 1.6.32-2
has caused the Debian Bug report #876244,
regarding libpng1.6 FTBFS with debhelper 10.9
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.)


-- 
876244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpng1.6
Version: 1.6.32-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

libpng1.6 fails to build from source since the debhelper 10.9 upload fixing
#795432:

| make[1]: Entering directory '/<>'
| dh_installexamples -plibpng16-dev example.c pngtest.c pngtest.png
| dh_installexamples: Requested unknown package libpng16-dev via -p/--package, 
expected one of: libpng16-16 libpng-dev libpng-tools libpng16-16-udeb
| dh_installexamples: unknown option or error during option parsing; aborting
| debian/rules:28: recipe for target 'override_dh_installexamples' failed
| make[1]: *** [override_dh_installexamples] Error 25
| make[1]: Leaving directory '/<>'
| debian/rules:14: recipe for target 'binary-arch' failed
| make: *** [binary-arch] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

I believe debhelper is quite right in making this fatal as it was hiding
errors (i.e. violating policy section 4.6). This should be fixed in
libpng1.6.

Helmut
--- End Message ---
--- Begin Message ---
Source: libpng1.6
Source-Version: 1.6.32-2

We believe that the bug you reported is fixed in the latest version of
libpng1.6, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated libpng1.6 
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: Sun, 17 Sep 2017 10:37:44 +0200
Source: libpng1.6
Binary: libpng16-16 libpng-dev libpng-tools libpng16-16-udeb
Architecture: source
Version: 1.6.32-2
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Gianfranco Costamagna 
Description:
 libpng-dev - PNG library - development (version 1.6)
 libpng-tools - PNG library - tools (version 1.6)
 libpng16-16 - PNG library - runtime (version 1.6)
 libpng16-16-udeb - PNG library - minimal runtime library (version 1.6) (udeb)
Closes: 876244
Changes:
 libpng1.6 (1.6.32-2) unstable; urgency=medium
 .
   * Bump std-version to 4.1.0, now priority is extra
   * Add missing newline on copyright entry, making lintian sad
   * Move the examples into the main libpng-dev (Closes: #876244)
 - thanks Helmut Grohne for the useful bug report!
Checksums-Sha1:
 95af1fc7f3bc172ae16636254558bcf54f020a73 2191 libpng1.6_1.6.32-2.dsc
 1d6dd8c804b25e984ec21eb6998a19f3dcf53764 23340 libpng1.6_1.6.32-2.debian.tar.xz
Checksums-Sha256:
 13c5b05d7cbe21ab7b4d88476a830bd9c34eed9731cb94fac584274e39a6f66f 2191 
libpng1.6_1.6.32-2.dsc
 d5dd3d4366e24aeade7e637735de2ff838bb0b89f3470f4da55c0ad7bc5e4efe 23340 
libpng1.6_1.6.32-2.debian.tar.xz
Files:
 462b874bb692d8353a9ea7e183e7e92c 2191 libs optional libpng1.6_1.6.32-2.dsc
 c393617c5e65479f46d58deb37c109ac 23340 libs optional 
libpng1.6_1.6.32-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZwhjyAAoJEPNPCXROn13ZPEMQAMOZr/1n3j8hUAaCnM0ddFdl
+rsURKM1x52vfA0WqqEUnoyVMrSm7q18HT22Y3Ax+9CvGJJ73s9YcHeQ1my194Bm
9abNKa9haB5pmRCAGhCXwrA3ZQAEYm8WmRuCl0n3S9EHTQ3+15KsgHoIU+f4j7wr
FscRsDrKnJtRhI+fI3snDgjzBqOVMpVpn0M1mDvMeZ6hC+X6Gfeq0PlGuuPPflOW
GufhHrLzpQ4g0XHfm9WiYKIc7OkV2rrI84KlbBnfxA0WM96HCXjr/eD5eQJs17A2
s8VVUDa/tSr0VosBjaJWOLbHjGcpIeMXBI90waFFdMd1x2DS07Iy7X5JZVAYbOCO
R+OWEI2wFrNNWdgwgV0Po1jwoto3ZZ0ToDdHlEJnpNuuiZiYfUr0VB0lbK831xR0
G2CeZMnQvl4VGPt0Q+cjVuyWEZXejvUjk2+HAIXZaC9ybXGK0ADtsAwp/d8Oh/sx
+wjbwnxiY9XjLDvuwjvFc10YMzkSV7c8hWc0QzBWenT2Q+bePVRl6qZJnyG70/HC
7A6yL7+hiJBOBZlV2oCD47fCTPxhV3T38FeDa2oT0paX4Qjaewhoqql4WLAdQnRr
/blHSyblt5rNkdQEAkOpy6yStinesPIlC4OeXg4qe9oum1j503JRpUgdBnmHs/pY
yzkhUGwaH7WQe00fg8NK
=6//m
-END PGP SIGNATURE End 

Bug#872259: marked as done (sagemath: FTBFS with Sphinx 1.6: TypeError: frompickle() takes exactly 3 arguments (4 given))

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:36:47 +
with message-id 
and subject line Bug#872259: fixed in sagemath 8.0-8
has caused the Debian Bug report #872259,
regarding sagemath: FTBFS with Sphinx 1.6: TypeError: frompickle() takes 
exactly 3 arguments (4 given)
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.)


-- 
872259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sagemath
Version: 7.6-3
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.6

Dear maintainer,

sagemath fails to build with Sphinx 1.6, currently available in experimental:

  [dochtml] Building reference manual, first pass.
  [dochtml]
  [dochtml] Error building the documentation.
  [dochtml] Traceback (most recent call last):
  [...]
  [dochtml]   File 
"/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py",
 line 510, in _wrapper
  [dochtml] build_many(build_ref_doc, L)
  [dochtml]   File 
"/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py",
 line 266, in build_many
  [dochtml] results.append(target(arg))
  [dochtml]   File 
"/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py",
 line 70, in build_ref_doc
  [dochtml] getattr(ReferenceSubBuilder(doc, lang), format)(*args, **kwds)
  [dochtml]   File 
"/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py",
 line 705, in _wrapper
  [dochtml] for module_name in self.get_modified_modules():
  [dochtml]   File 
"/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py",
 line 834, in get_modified_modules
  [dochtml] env = self.get_sphinx_environment()
  [dochtml]   File 
"/<>/debian/build/usr/lib/python2.7/dist-packages/sage_setup/docbuild/__init__.py",
 line 779, in get_sphinx_environment
  [dochtml] env = BuildEnvironment.frompickle(self.dir, config, env_pickle)
  [dochtml] TypeError: frompickle() takes exactly 3 arguments (4 given)
  Makefile:1093: recipe for target 'doc-html' failed

This looks like a result of upstream commit [1], where the signature of
frompickle method changed from:

  def frompickle(cls, srcdir, config, filename):

to:

  def frompickle(cls, filename, app):

The full build log is available at [2] (it is from Ubuntu, but there should
be no difference with Debian).

[1]: https://github.com/sphinx-doc/sphinx/commit/c7bec75bcd12530a
[2]: 
https://launchpadlibrarian.net/17873/buildlog_ubuntu-artful-amd64.sagemath_7.6-3ubuntu3_BUILDING.txt.gz

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.0-8

We believe that the bug you reported is fixed in the latest version of
sagemath, 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 872...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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: Wed, 20 Sep 2017 07:18:46 +
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca 
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu 
sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr
Architecture: source
Version: 8.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical 

Bug#853568: marked as done (nanopolish: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 08:37:24 +0200
with message-id <20170920063724.3ue5ec2iur6kz...@an3as.eu>
and subject line Closes statement was hidden in changelog
has caused the Debian Bug report #853568,
regarding nanopolish: ftbfs with GCC-7
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.)


-- 
853568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nanopolish
Version: 0.5.0-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/nanopolish_0.5.0-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /usr/include/c++/7/cstdlib:77:0,
 from /usr/include/c++/7/stdlib.h:36,
 from src/nanopolish_call_variants.cpp:9:
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double 
std::abs(double)
   abs(double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float 
std::abs(float)
   abs(float __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double 
std::abs(long double)
   abs(long double __x)
   ^~~
src/nanopolish_call_variants.cpp:599:209: warning: format '%d' expects argument 
of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' 
[-Wformat=]
fprintf(stderr, 
"SUM_VAR\t%zu\t%d\t%d\t%d\t%d\t%.5lf\t%.2lf\n", ref_hp_start, hp_length, 
var_sequence_length, call_window, variant_offset_end - variant_offset_start, 
sum_duration, log_gamma);


 ^
src/nanopolish_call_variants.cpp:599:209: warning: format '%d' expects argument 
of type 'int', but argument 7 has type 'size_t {aka long unsigned int}' 
[-Wformat=]
Makefile:98: recipe for target 'src/hmm/nanopolish_profile_hmm.o' failed
make[1]: *** [src/hmm/nanopolish_profile_hmm.o] Error 1
make[1]: *** Waiting for unfinished jobs
src/alignment/nanopolish_eventalign.cpp: In function 'void 
emit_sam_header(samFile*, const bam_hdr_t*)':
src/alignment/nanopolish_eventalign.cpp:225:18: warning: ignoring return value 
of 'int sam_hdr_write(samFile*, const bam_hdr_t*)', declared with attribute 
warn_unused_result [-Wunused-result]
 sam_hdr_write(fp, hdr);
 ~^
src/alignment/nanopolish_eventalign.cpp: In function 'void 
emit_event_alignment_sam(htsFile*, const SquiggleRead&, const bam_hdr_t*, const 
bam1_t*, const std::vector&)':
src/alignment/nanopolish_eventalign.cpp:364:15: warning: ignoring return value 
of 'int sam_write1(samFile*, const bam_hdr_t*, const bam1_t*)', declared with 
attribute warn_unused_result [-Wunused-result]
 sam_write1(fp, base_hdr, event_record);
 ~~^~~~
Makefile:98: recipe for target 'src/common/nanopolish_variant.o' failed
make[1]: *** [src/common/nanopolish_variant.o] Error 1
Makefile:98: recipe for target 

Bug#876100: marked as done (libglvnd-dev: libglvnd-dev not coinstallable with nvidia packages)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 06:51:00 +
with message-id 
and subject line Bug#876100: fixed in nvidia-graphics-drivers 375.82-4
has caused the Debian Bug report #876100,
regarding libglvnd-dev: libglvnd-dev not coinstallable with nvidia packages
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.)


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

Dear Maintainer,

libglvnd depends on many OpenGL related packages like libgl1, specified
by concrete version. This means those dependencies can't be satisfied
with virtual packages, ie. nvidia packages providing libgl1. However,
those nvidia packages conflict with any other packages providing those
names, particularly libgl1 et al. provided by libglvnd.

In effect, this makes development packages like
 - libegl1-mesa-dev
 - libsdl2-dev
 - qtbase5-dev
uninstallable on systems with nvidia packages installed. This
restriction didn't exist with mesa packages older than 17.2.0.

Please check if that conflict can be rectified, either on the
libglvnd-dev side, or the nvidia packages (CC-d).

Regards
Jiri Palecek

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.13.0-trunk-686-pae (SMP w/2 CPU cores)
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ 
(charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 375.82-4

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Wed, 20 Sep 2017 08:19:58 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglvnd0-nvidia libopengl0-glvnd-nvidia libglx0-glvnd-nvidia libglx-nvidia0 
libgl1-glvnd-nvidia-glx libgl1-nvidia-glvnd-glx libgl1-nvidia-glx 
libnvidia-glcore libegl1-glvnd-nvidia libegl1-nvidia libegl-nvidia0 
libgles1-glvnd-nvidia libgles1-nvidia libgles-nvidia1 libgles2-glvnd-nvidia 
libgles2-nvidia libgles-nvidia2 libnvidia-eglcore nvidia-egl-common 
nvidia-egl-icd libnvidia-egl-wayland nvidia-vulkan-common nvidia-vulkan-icd 
nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 
nvidia-alternative nvidia-kernel-support nvidia-kernel-dkms 
nvidia-kernel-source nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 
libcuda1-i386 libnvidia-compiler libnvidia-fatbinaryloader 
libnvidia-ptxjitcompiler libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 
libnvidia-fbc1 libnvidia-ml1 nvidia-opencl-common nvidia-opencl-icd 
nvidia-libopencl1
 nvidia-detect
Architecture: source
Version: 375.82-4
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library${nvidia:LegacyDesc}
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
 libegl-nvidia0 - NVIDIA binary EGL library${nvidia:LegacyDesc}
 libegl1-glvnd-nvidia - Vendor neutral GL dispatch library -- libEGL
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND 
variant)${nvidia:LegacyDesc}
 libgl1-glvnd-nvidia-glx - Vendor neutral GL dispatch library -- libGL
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND 
variant)${nvidia:LegacyDe
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND 
variant)${nvidia:Lega
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x 

Bug#784505: marked as done ([paraview] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:04:41 +
with message-id 
and subject line Bug#784505: fixed in paraview 5.4.1+dfsg1-1
has caused the Debian Bug report #784505,
regarding [paraview] Qt4's WebKit removal
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.)


-- 
784505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paraview
Version: 4.1.0+dfsg+1-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Science Team ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: paraview
Source-Version: 5.4.1+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
paraview, 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 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated paraview 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: SHA512

Format: 1.8
Date: Wed, 20 Sep 2017 08:51:19 +0200
Source: paraview
Binary: paraview paraview-dev paraview-doc paraview-python
Architecture: source
Version: 5.4.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Description:
 paraview   - Parallel Visualization Application
 paraview-dev - Parallel Visualization Application. Development header files
 paraview-doc - Parallel Visualization Application. Comprehensive documentation
 paraview-python - Parallel Visualization Application. python-support
Closes: 784505 835002
Changes:
 paraview (5.4.1+dfsg1-1) unstable; urgency=medium
 .
   * [663aeb8] New upstream version 5.4.1+dfsg1
   * [df8c7f2] Refresh patches
   * [6c0e2d3] Some minor changes in d/rules and install files
   * [2dd50c2] Remove libqtwebkit-dev from build-depends. (Closes: #784505)
   * [546b2fd] Remove Christophe from uploaders. (Closes: #835002)
   * [e3a8012] Update d/copyright
Checksums-Sha1:
 5f038f77f8f4ff6b55b8cd48958a26c5819811ca 2899 paraview_5.4.1+dfsg1-1.dsc
 d1882f7bd3daf55d5c385373a6d35c301bc05a61 23840212 
paraview_5.4.1+dfsg1.orig.tar.xz
 99440ea88758d01e0aba8fe11c2be7d0d5d929da 31252 
paraview_5.4.1+dfsg1-1.debian.tar.xz
 

Bug#835002: marked as done (Updating the paraview Uploaders list)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:04:41 +
with message-id 
and subject line Bug#835002: fixed in paraview 5.4.1+dfsg1-1
has caused the Debian Bug report #835002,
regarding Updating the paraview Uploaders list
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.)


-- 
835002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paraview
Version: 5.0.1+dfsg1-5.1 5.1.2+dfsg1-1 5.1.0+dfsg1-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christophe Prud'homme  has not been working on
the paraview package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: paraview
Source-Version: 5.4.1+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
paraview, 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 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated paraview 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: SHA512

Format: 1.8
Date: Wed, 20 Sep 2017 08:51:19 +0200
Source: paraview
Binary: paraview paraview-dev paraview-doc paraview-python
Architecture: source
Version: 5.4.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Description:
 paraview   - Parallel Visualization Application
 paraview-dev - Parallel Visualization Application. Development header files
 paraview-doc - Parallel Visualization Application. Comprehensive documentation
 paraview-python - Parallel Visualization Application. python-support
Closes: 784505 835002
Changes:
 paraview (5.4.1+dfsg1-1) unstable; urgency=medium
 .
   * [663aeb8] New upstream version 5.4.1+dfsg1
   * [df8c7f2] Refresh patches
   * [6c0e2d3] Some minor changes in d/rules and install files
   * [2dd50c2] Remove libqtwebkit-dev from build-depends. (Closes: #784505)
   * [546b2fd] Remove Christophe from uploaders. (Closes: #835002)
   * [e3a8012] Update d/copyright
Checksums-Sha1:
 5f038f77f8f4ff6b55b8cd48958a26c5819811ca 2899 paraview_5.4.1+dfsg1-1.dsc
 d1882f7bd3daf55d5c385373a6d35c301bc05a61 23840212 
paraview_5.4.1+dfsg1.orig.tar.xz
 99440ea88758d01e0aba8fe11c2be7d0d5d929da 31252 
paraview_5.4.1+dfsg1-1.debian.tar.xz
 82cac3de57d8900156352f9416ef51bba342f190 21766 
paraview_5.4.1+dfsg1-1_source.buildinfo
Checksums-Sha256:
 c22fc4382529e5f7ccb5fc252e66fd68056b1b6e2f58ae51128524cf8feec2a7 2899 
paraview_5.4.1+dfsg1-1.dsc
 8aca83f98c1b00f0ee85297ca8c98ee4d67d06a93e294a1d42f808e6cd8ee93a 23840212 
paraview_5.4.1+dfsg1.orig.tar.xz
 d1375c950b0ec6294ac95ac9679646e6e374d588e8532a2bb9971d581134811c 31252 
paraview_5.4.1+dfsg1-1.debian.tar.xz
 61f9c722129157f85276a82214606e110bed5c80b8bee0652b807f692be3db7f 21766 
paraview_5.4.1+dfsg1-1_source.buildinfo
Files:
 992095fe59e7bc48ec350e1a4111afd8 2899 science extra paraview_5.4.1+dfsg1-1.dsc
 8a4ba614f20939b4e1e26d6325c5c699 23840212 science extra 
paraview_5.4.1+dfsg1.orig.tar.xz
 47715036f424527f649ee22ad134230b 31252 science extra 
paraview_5.4.1+dfsg1-1.debian.tar.xz
 33f547f820119f00e22a71aa0e2d0e2a 21766 science extra 
paraview_5.4.1+dfsg1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlnCEE4ACgkQ0+Fzg8+n
/wbWcA/+L1R5cXjhaOI30ZjgQ+Gm3eJUzYnQnJGgVE0IbAzzQDkSOzeJdZTv4lP3
WSAAqfQfkmJfmW9rnQ1SC4RI6pUc3QWEEmoRF/ApTsHTMwTqOutv9GvkrmZceRDY
7xmcg1YCZTq5yOp8aLgQZlulrGcvHQSuQR5N6yCTugwOQzwYT5+X4nRiBuUueNxd
2JRiNrrn73T3pA9JW0Y0jfNokGxvo8DA5dD8wIdXyS74V6ArnomzD+WKo5gKSqQ9
sJo09OVOTA5Y9lkBuA0PAgpiabuQh0aTs0JrTDwjj4fRXIK6ZrCouUe+hrPAAnM4
MicqyZSJAXcFwH0pNDVuOqfhcWhy+H/87BO6xcgGCzrXOApL8qhJ8uMmciEIz817
bIKHaSRxKKNsdCbQ47KfoxLX2eymdBlzGDvsdhEYrh32OyINmPeNT26meX7u9uap

Bug#875683: marked as done (nvidia-graphics-drivers: libGL.so.1 missing with libglvnd libs)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 06:50:59 +
with message-id 
and subject line Bug#875683: fixed in nvidia-graphics-drivers 375.82-4
has caused the Debian Bug report #875683,
regarding nvidia-graphics-drivers: libGL.so.1 missing with libglvnd libs
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.)


-- 
875683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-graphics-drivers
Version: 375.82-3
Severity: serious

On 2017-09-12 22:01, Luca Boccassi wrote:
> I built and installed, it pulled in libglvnd0 (:i386), but then
> libGL.so.1 is gone from /usr/lib/(32|64 bit subdirs) so most things
> fail to run, including Gnome.
> 
> There was no particular error during the installation. I ran update-glx 
> --config glx|nvidia to no avail.
> 
> Do you know off the top of your head what the problem might be, before
> I dive in as well?

looks like a problem with the alternatives, I'll look into it


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 375.82-4

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, 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 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Wed, 20 Sep 2017 08:19:58 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglvnd0-nvidia libopengl0-glvnd-nvidia libglx0-glvnd-nvidia libglx-nvidia0 
libgl1-glvnd-nvidia-glx libgl1-nvidia-glvnd-glx libgl1-nvidia-glx 
libnvidia-glcore libegl1-glvnd-nvidia libegl1-nvidia libegl-nvidia0 
libgles1-glvnd-nvidia libgles1-nvidia libgles-nvidia1 libgles2-glvnd-nvidia 
libgles2-nvidia libgles-nvidia2 libnvidia-eglcore nvidia-egl-common 
nvidia-egl-icd libnvidia-egl-wayland nvidia-vulkan-common nvidia-vulkan-icd 
nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 
nvidia-alternative nvidia-kernel-support nvidia-kernel-dkms 
nvidia-kernel-source nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 
libcuda1-i386 libnvidia-compiler libnvidia-fatbinaryloader 
libnvidia-ptxjitcompiler libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 
libnvidia-fbc1 libnvidia-ml1 nvidia-opencl-common nvidia-opencl-icd 
nvidia-libopencl1
 nvidia-detect
Architecture: source
Version: 375.82-4
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library${nvidia:LegacyDesc}
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
 libegl-nvidia0 - NVIDIA binary EGL library${nvidia:LegacyDesc}
 libegl1-glvnd-nvidia - Vendor neutral GL dispatch library -- libEGL
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND 
variant)${nvidia:LegacyDesc}
 libgl1-glvnd-nvidia-glx - Vendor neutral GL dispatch library -- libGL
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND 
variant)${nvidia:LegacyDe
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND 
variant)${nvidia:Lega
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library${nvidia:LegacyDesc}
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library${nvidia:LegacyDesc}
 libgles1-glvnd-nvidia - NVIDIA binary OpenGL|ES 1.x GLVND stub library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library 
(transitional)${nvidia:Legacy
 libgles2-glvnd-nvidia - NVIDIA binary OpenGL|ES 2.x GLVND stub library
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library 
(transitional)${nvidia:Legacy
 libglvnd0-nvidia - Vendor neutral GL dispatch library -- libGLdispatch
 libglx-nvidia0 - NVIDIA binary GLX library${nvidia:LegacyDesc}
 libglx0-glvnd-nvidia - Vendor neutral GL dispatch library -- libGLX
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime 

Bug#870031: marked as done (ITP: gsettings-qt -- QML bindings for GSettings)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:14 +
with message-id 
and subject line Bug#870031: fixed in gsettings-qt 0.1+16.04.20170729-1
has caused the Debian Bug report #870031,
regarding ITP: gsettings-qt -- QML bindings for GSettings
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.)


-- 
870031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Boyuan Yang <073p...@gmail.com>

* Package name: gsettings-qt
  Version : 0.1+16.04+bzr20170110
  Upstream Author : Canonical Ltd.
* URL : https://launchpad.net/gsettings-qt
* License : LGPL-3
  Programming Lang: C++
  Description : QML bindings for GSettings

This package provides a QML binding for GSettings.

This package is the build-dependency of various Deepin software to be packaged
by pkg-deepin team.

Gsettings-qt was a Ubuntu-only package. I intend to put it into Debian and fix
any problem encountered.

I intend to co-maintain this package inside debian-qt-kde team and put its
packaging repository (converted to Git with the help of git-bzr) into collab-
maint to ease external contribution and co-maintenance.

Anyone interested is welcomed to co-maintain and review the status of this
library package.
--- End Message ---
--- Begin Message ---
Source: gsettings-qt
Source-Version: 0.1+16.04.20170729-1

We believe that the bug you reported is fixed in the latest version of
gsettings-qt, 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 870...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated gsettings-qt 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: SHA512

Format: 1.8
Date: Fri, 04 Aug 2017 11:25:48 +0800
Source: gsettings-qt
Binary: libgsettings-qt-dev libgsettings-qt1 qml-module-gsettings1.0
Architecture: source amd64
Version: 0.1+16.04.20170729-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 libgsettings-qt-dev - library to access GSettings from Qt (development files)
 libgsettings-qt1 - library to access GSettings from Qt (shared libraries)
 qml-module-gsettings1.0 - QML Bindings for GSettings
Closes: 870031
Changes:
 gsettings-qt (0.1+16.04.20170729-1) unstable; urgency=medium
 .
   * New upstream snapshot from bzr src repository.
   * Initial Release in Debian. (Closes: #870031)
   * Fix FTBFS problem due to incorrect link path. (LP: #1706682)
Checksums-Sha1:
 7aedca47203ea711244f7288d277f0c66cf6ade8 2421 
gsettings-qt_0.1+16.04.20170729-1.dsc
 450479b0577f701f069e308db5a26959ee22be68 18434 
gsettings-qt_0.1+16.04.20170729.orig.tar.gz
 fbc923accb06d7356eae7ae0a6bcfb08b9a17dad 6392 
gsettings-qt_0.1+16.04.20170729-1.debian.tar.xz
 ee04a8c96859780dcbae0a1a05aefad2941d0962 12242 
gsettings-qt_0.1+16.04.20170729-1_amd64.buildinfo
 b59dfd776564f3a68325b430ea580990e1dc754f 6504 
libgsettings-qt-dev_0.1+16.04.20170729-1_amd64.deb
 4e6b2145229d9cc5285a92fb2440a250547f5272 332306 
libgsettings-qt1-dbgsym_0.1+16.04.20170729-1_amd64.deb
 06eef2860b4e0e610dc052550f4e3d81e04128a1 19562 
libgsettings-qt1_0.1+16.04.20170729-1_amd64.deb
 8e78dea95ac52d94c31681b38574eae074fde8e6 531986 
qml-module-gsettings1.0-dbgsym_0.1+16.04.20170729-1_amd64.deb
 fe772e9df09df52eff71d434a7eadc813411b220 18424 
qml-module-gsettings1.0_0.1+16.04.20170729-1_amd64.deb
Checksums-Sha256:
 4ba3a9459623d2f4dad1372a1494a6f2b374d4010068954dfa0d84274a1cc948 2421 
gsettings-qt_0.1+16.04.20170729-1.dsc
 08e445260e28ffb66098f7ddcfc3ca356dd05b1fcfb720c8b4e5a87be0c8ed47 18434 
gsettings-qt_0.1+16.04.20170729.orig.tar.gz
 fb12a180635a54c59d91c700d0878758be2a3ad08ac79141e5adf05c16a77940 6392 
gsettings-qt_0.1+16.04.20170729-1.debian.tar.xz
 62b16ba0751997e668637b52e7dd09d5fa6913fbd7ce617f40ff8762373786d5 12242 
gsettings-qt_0.1+16.04.20170729-1_amd64.buildinfo
 d64846a3d73e39de22c346ba7b007fea8ce21dbdbf9d38b3645af283680d7b72 6504 

Bug#874690: marked as done (ITP: ruby-jsonapi-renderer -- Ruby gem for rendering JSON API documents)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:28 +
with message-id 
and subject line Bug#874690: fixed in ruby-jsonapi-renderer 0.1.3-1
has caused the Debian Bug report #874690,
regarding ITP: ruby-jsonapi-renderer -- Ruby gem for rendering JSON API 
documents
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.)


-- 
874690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: ruby-jsonapi-renderer
  Version : 0.1.3
  Upstream Author : Lucas Hosseini
* URL : https://github.com/jsonapi-rb/jsonapi-renderer
* License : Expat
  Description : Ruby gem for rendering JSON API documents
-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEsclPZxif+sAmSPvz1N6yL8C5bhUFAlh9FhwRHHNydWRAZGlz
cm9vdC5vcmcACgkQ1N6yL8C5bhWeoQ//bzHXLt9wL8qoV8VN+hWowblH7NfLO/bn
J8y7BqCqyWkinDux16OOyfxC7e4BCw2t1rgAgUj4X0/Y+9LWFsx3wPHseb/u2TWC
Wqz1k9LLjF0XYvi/oeNA2v7Tot1WvTZCcKyQssItTclJ1UbCxhSY8dhovwrk8cKK
hu1FL+vMVaTxcifYpSdXxRmXP7zCKVt2Wp871OjgRJ40leHHqsNT0jgMRgCmMsXB
vLIMCTpyMbnm8NuPoyLdc6Khr+oEqyUXTnxkyMPtN0bR7kxo57PQ/Y0QiFvW6+19
dMaGIGS1ii9jTr98txoLYzVxd1rKHElVOnhJWSxZ+0PnnZVCvBRhbYoRlceZ+4e1
P5Ocesg9OVerO/0F4yBh4sUczVc4d0hFs7QPrYmNjnzEdmHsp+lgNNQfbaZlkG6L
Nc8gKUefZnIB66o7+/7zDsITU76dVnTKv13FxlWa0rBFRAf469aa7atRe9265SgS
hMe1/6vM8kHtwtCnrK5JbwFBjZ3G+fLtNgkILihJMhk5rlgudkhZUVO4LhnChmlS
HotjzJNnuNfruRx4l92bZDZLlR3U4zKfc8Hgc4lPHEEN+aD07EJFQgf+rtTfvmW1
9HRqzk3OBWcKYD6qiXgOZvB77eRwQSq/oGYi73nvl0P2c+CqffwWFrr2GK+OYGlK
F8YfEPRhpS0=
=FVw1
-END PGP SIGNATURE-


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-jsonapi-renderer
Source-Version: 0.1.3-1

We believe that the bug you reported is fixed in the latest version of
ruby-jsonapi-renderer, 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 874...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sruthi Chandran  (supplier of updated ruby-jsonapi-renderer 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Sep 2017 23:33:37 +0530
Source: ruby-jsonapi-renderer
Binary: ruby-jsonapi-renderer
Architecture: source all
Version: 0.1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Sruthi Chandran 
Description:
 ruby-jsonapi-renderer - Render JSONAPI documents
Closes: 874690
Changes:
 ruby-jsonapi-renderer (0.1.3-1) unstable; urgency=medium
 .
   * Initial release (Closes: #874690)
Checksums-Sha1:
 7d15b3b7eeffbd1bb0b763c28b22aa310bbcdb0c 2157 ruby-jsonapi-renderer_0.1.3-1.dsc
 dbe4fedaf97acfbee7309ffb4bded2c6f57e5086 4162 
ruby-jsonapi-renderer_0.1.3.orig.tar.gz
 ef76e2e23077ae850ccc5f40dc3ba2aee9e1311a 1764 
ruby-jsonapi-renderer_0.1.3-1.debian.tar.xz
 1a24e9be92131b4e8930bd7e91369f366c508c36 6002 
ruby-jsonapi-renderer_0.1.3-1_all.deb
 6a04794f50beaf26794fa9562961452f0e4fb8fc 6540 
ruby-jsonapi-renderer_0.1.3-1_amd64.buildinfo
Checksums-Sha256:
 ae417b2262e92c08b68cac55203ef51bfd184be92b28e9c2e235b419f5750d12 2157 
ruby-jsonapi-renderer_0.1.3-1.dsc
 832eb5185a5859641c66709a1ce45500b7763fe5f0976384e093810ccdb72827 4162 
ruby-jsonapi-renderer_0.1.3.orig.tar.gz
 cc30a2068d24a104564c748415011222caa12c5daac6a2cde2f40446e11af9bb 1764 
ruby-jsonapi-renderer_0.1.3-1.debian.tar.xz
 127c209b3823a05da767c7182f5c95a83898d84b0ef3d538654e7be4cb8569b4 6002 
ruby-jsonapi-renderer_0.1.3-1_all.deb
 0c7be3d075fb23bedbfaf47f897a458c4798c634ed73aec515a782be0ba15e8a 6540 
ruby-jsonapi-renderer_0.1.3-1_amd64.buildinfo
Files:
 65ee6ad698119a466bdc921b1a4a0fad 2157 ruby optional 
ruby-jsonapi-renderer_0.1.3-1.dsc
 a488f34fb9bdb743b11dd86ca5f2a11c 4162 ruby optional 
ruby-jsonapi-renderer_0.1.3.orig.tar.gz
 6d00c08f2a24d9b65e45b99655cac10f 1764 ruby optional 
ruby-jsonapi-renderer_0.1.3-1.debian.tar.xz
 1be7cf1aca15d80c6272d27fe33b4b92 6002 ruby optional 

Bug#876181: marked as done (ITP: ruby-peek-rblineprof -- Peek into how much each line of your Rails application takes throughout a request)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:29 +
with message-id 
and subject line Bug#876181: fixed in ruby-peek-rblineprof 0.2.0-1
has caused the Debian Bug report #876181,
regarding ITP: ruby-peek-rblineprof -- Peek into how much each line of your 
Rails application takes throughout a request
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.)


-- 
876181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

from rubygems.org/gems/peek-rblineprof
dependency of gitlab 9.5











signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-peek-rblineprof
Source-Version: 0.2.0-1

We believe that the bug you reported is fixed in the latest version of
ruby-peek-rblineprof, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-peek-rblineprof 
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: Tue, 19 Sep 2017 15:34:36 +0530
Source: ruby-peek-rblineprof
Binary: ruby-peek-rblineprof
Architecture: source all
Version: 0.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-peek-rblineprof - rails integration for rblineprof
Closes: 876181
Changes:
 ruby-peek-rblineprof (0.2.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #876181)
Checksums-Sha1:
 52c690d97df61c4ba3558d394bde10ccfcced00e 2168 ruby-peek-rblineprof_0.2.0-1.dsc
 ddfb5ebca749b4d8e3f4ee9ac378ea62706189b5 6375 
ruby-peek-rblineprof_0.2.0.orig.tar.gz
 8a036aea15fa39fc6a263b3502f6078ec9227e0c 1920 
ruby-peek-rblineprof_0.2.0-1.debian.tar.xz
 28d9817bb9049aa8d9360cefdbc514b16a3c6f3d 7778 
ruby-peek-rblineprof_0.2.0-1_all.deb
 0a5a737bda50cdec0ead933accf60baf58b61687 7326 
ruby-peek-rblineprof_0.2.0-1_amd64.buildinfo
Checksums-Sha256:
 1fe4ce8613e1ff841eca0b7ea4251017c0fd51f0036d18aeb4d81d51cf0d1a94 2168 
ruby-peek-rblineprof_0.2.0-1.dsc
 505aa143ea1ced6c01e8c3973617b624f3e626be0c4ad010ce1081b91a6c38ed 6375 
ruby-peek-rblineprof_0.2.0.orig.tar.gz
 59f33bc6891bf8cd90acbe4a3b1b482e96647fd733e21af692740789aa3cd4fe 1920 
ruby-peek-rblineprof_0.2.0-1.debian.tar.xz
 85c1b84781c22ceb7228c897ec552ac4d57c10f437ab31e67c480233accfe58d 7778 
ruby-peek-rblineprof_0.2.0-1_all.deb
 3bc9c53591137b762cd633e463ebdd882434b1a0e4b044489071d21b03e2f057 7326 
ruby-peek-rblineprof_0.2.0-1_amd64.buildinfo
Files:
 571e159cc445f0f54635df68fb8755e0 2168 ruby optional 
ruby-peek-rblineprof_0.2.0-1.dsc
 25206ed42010a5be7f8d6278228417d3 6375 ruby optional 
ruby-peek-rblineprof_0.2.0.orig.tar.gz
 b4be6cf1085949bf25d5c06cdc30ecb0 1920 ruby optional 
ruby-peek-rblineprof_0.2.0-1.debian.tar.xz
 d9a91ec38326475e475535129be064af 7778 ruby optional 
ruby-peek-rblineprof_0.2.0-1_all.deb
 9d986cb5632332029ae5ed6eebf9c84e 7326 ruby optional 
ruby-peek-rblineprof_0.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlnA7EoACgkQzh+cZ0US
wiq3lRAAomOVxZnPR3l8m8eGiGhIZoJjAnpDfgGn0uWQqIisazV/Q9Y+7pmf9/jo
P8xa/e0H35bEDKlZAjGHwxpF5tf3PNtS8PYRAj8X3L7FSyEyEeP9kOzE7oEkwrMh
way2QV1U+4F/eg+IOCUF5rA3NGAm5GbY0htWACHJwzgQ7tQ1Gxh9hh8y4bfW2vNm
PwMmmRMw7YtVlWOL+g6YLjYC7WMXwjB5b4acyxMuUxwSR+FjBi7/WV9bR/s/CL5C
3qSCI9sTTqkgvUF26j1Sp5fG4abE+Xzo0os/U2mrhK4FDId7LEWTeoyGep+o2Hys
TTvaif4A42lI1FVW1g98AdrBarZT3A8dMDU1HTVnS+C2KxQYWML6qg9f1YHfJdyO
yhlrB0M4UULYKWPHrchL1hgnkjP3Gelvby1wWttD1XqSUO8U/PYebUM9tBU8WL1s
k7+Ga66kC4tKQiEqW1py3B+o8d58BonJtHFHzx/F57m54rVdX6IAz7+rxHsox2gB
GFwiZ5Y+5Jm4XQ4eg1ie8vpc/seIC4aTZGC29HQtrmGvC5r5JALZp/cGy0kQztyI
7RJd+PtELche5EE8j3R0Lc4WqrRgqxVRYJw8NAAINZsKOBHL4FlMdPRauyrCIPrE
rwfOht+LxzP8oje8c6lVbTPuEGcT3WdO1D63VNSMt8ep89SXdrY=
=XI9j
-END PGP SIGNATURE End Message ---

Bug#874728: marked as done (ITP: ruby-flipper-activerecord -- active record support for flipper)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:27 +
with message-id 
and subject line Bug#874728: fixed in ruby-flipper-active-record 0.10.2-1
has caused the Debian Bug report #874728,
regarding ITP: ruby-flipper-activerecord -- active record support for flipper
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.)


-- 
874728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

from rubygems.org/gems/flipper-active_record

dependency of gitlab 9.5









signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-flipper-active-record
Source-Version: 0.10.2-1

We believe that the bug you reported is fixed in the latest version of
ruby-flipper-active-record, 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 874...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-flipper-active-record 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: Sat, 09 Sep 2017 15:22:49 +0530
Source: ruby-flipper-active-record
Binary: ruby-flipper-active-record
Architecture: source all
Version: 0.10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-flipper-active-record - ActiveRecord adapter for Flipper
Closes: 874728
Changes:
 ruby-flipper-active-record (0.10.2-1) unstable; urgency=medium
 .
   * Initial release (Closes: #874728)
Checksums-Sha1:
 f6ec98bb7a73152eb9e660e4fa50c59e98512607 2313 
ruby-flipper-active-record_0.10.2-1.dsc
 fcd3cdee9d2e4d2e0fca494487ee855d6ccec356 4636 
ruby-flipper-active-record_0.10.2.orig.tar.gz
 a0357806719450b152cb2cf8c802a6a9f502b5c6 2044 
ruby-flipper-active-record_0.10.2-1.debian.tar.xz
 2aff0cad2ed9b4837cd16375a069226727f0477a 4808 
ruby-flipper-active-record_0.10.2-1_all.deb
 dde27f17e9e474a2bac21ad4265d4cd931d66734 7225 
ruby-flipper-active-record_0.10.2-1_amd64.buildinfo
Checksums-Sha256:
 d7af790b9dadfce5875b862dc02eacd90c833e85bc19a6f74dc9bc0bc8e6514d 2313 
ruby-flipper-active-record_0.10.2-1.dsc
 2cbf148c5b705b620ab6a25f886a823d54feddce4f623a3c0f343e4e0981e653 4636 
ruby-flipper-active-record_0.10.2.orig.tar.gz
 8e1c908f9544798042cc28044e60388613b078224ee404a8a23bca6a1c2b86d6 2044 
ruby-flipper-active-record_0.10.2-1.debian.tar.xz
 6cfb02872e456d3422a4e68a2840b811ebc8a9cbe4e4a46d5e91af249223f769 4808 
ruby-flipper-active-record_0.10.2-1_all.deb
 8b43f9b0278e437cbd7e9a8e46a5f662547b0b04d35de1f22bc8f8be0fa7de39 7225 
ruby-flipper-active-record_0.10.2-1_amd64.buildinfo
Files:
 0c10f9151f31ebe874e8171c9a95b108 2313 ruby optional 
ruby-flipper-active-record_0.10.2-1.dsc
 154628246a1f8d5ee55455af237b6002 4636 ruby optional 
ruby-flipper-active-record_0.10.2.orig.tar.gz
 fd7e7a1b453c4b77e9111fe7052baa2c 2044 ruby optional 
ruby-flipper-active-record_0.10.2-1.debian.tar.xz
 eb76fd52960721f327211015eb7ab607 4808 ruby optional 
ruby-flipper-active-record_0.10.2-1_all.deb
 59b36607029cd259044fc4291ab5aa20 7225 ruby optional 
ruby-flipper-active-record_0.10.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlmzu/oACgkQzh+cZ0US
wiqPLg//X1ZO186cXSUhL958FviJ0HOvvL3laItBl0EldFP7MZDT1EOIDlt7feZn
uOZLbutg2da/PueBozhr7BCnMQP0TcGQnx9uajpw0ovo2kHBhrtkUAwBthjaoXYw
N4xpWZosVsAvvEKhFTA4bYBIxg0m2Dc6nd9TcDFAwhTHVJnEbxXcqZgxg02A+JHv
BAKf9g8k8tLgQshaUxCqD/1goV1+jlrJIoFZeiMBpwGF0e8ByQqNlYzj7ozy4fsJ
xa9x1zVTett/OfwtnVYdUz2Z3Q8xRc6Oq25tcvPNi2ubMV2FxBGCD8dYHQVfc3K6
4sMMVeaNNJJawQq33TVLfhE4TA5ULVwMhg4bZrnDuugEG9LqYJbnnfgLXHP8eOHz
CmuKIAQG++GYUGpBGjI80whlI7x2kWYjoHwGSu3Mjpch4zgO1Jwycy/rTtSLhA/0
/RHuvXoDmtPyib6Nz3D+FXhuABkiGQlTJPMJMU803QNZyCMRb2wXY8VHFMfry9Nl
8XmGTOJs7T5hB0DI3c1t0HEzPX0tbkcpvkpezRjLT55sa8Gyi4FWvOTCd9sdzuaf
9nO6d5zTncoccdELVNlh1zma9R6ABs9/eiBbK1lhqi78a5CyNl1XaY9DrH7i0mzn
RCIzyI3RNENf2KzlO54u6yhczK+a5hKp0kct4Jg+/c7dgMSfVVw=
=saye
-END 

Bug#873242: marked as done (ITP: ruby-lograge -- Tame Rails' multi-line logging into a single line per request)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:28 +
with message-id 
and subject line Bug#873242: fixed in ruby-lograge 0.5.0-1
has caused the Debian Bug report #873242,
regarding ITP: ruby-lograge -- Tame Rails' multi-line logging into a single 
line per request
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.)


-- 
873242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

from rubygems.org/gems/lograge
dependency of gitlab 9.5









signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-lograge
Source-Version: 0.5.0-1

We believe that the bug you reported is fixed in the latest version of
ruby-lograge, 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 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-lograge package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Aug 2017 23:09:23 +0530
Source: ruby-lograge
Binary: ruby-lograge
Architecture: source all
Version: 0.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-lograge - Tame Rails' multi-line logging into a single line per request
Closes: 873242
Changes:
 ruby-lograge (0.5.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #873242)
Checksums-Sha1:
 607db45ee4e3c18eaf22e1ccbfe12ad40b789849 2120 ruby-lograge_0.5.0-1.dsc
 d15cd640e398c103b13ce08b4c012bbb4de2e9df 5177 ruby-lograge_0.5.0.orig.tar.gz
 60222f3e40b3ab0f5d11ebb875a6467628b48245 1972 
ruby-lograge_0.5.0-1.debian.tar.xz
 3461952088662a4ebd36ad862b331e0e5b130197 7388 ruby-lograge_0.5.0-1_all.deb
 f2e74fc9bfad09c0728471552c37a60f5c85b912 7140 
ruby-lograge_0.5.0-1_amd64.buildinfo
Checksums-Sha256:
 620f46e42c5543ef11239c87cc564d37e46328f0ad7dd094c4627d6a614c421b 2120 
ruby-lograge_0.5.0-1.dsc
 d9c7762a3c982767b1d68f59e30d79f4577e5e56fc46bb46a802423fe944bd2f 5177 
ruby-lograge_0.5.0.orig.tar.gz
 d2eede89f012e0f39aae0a64a53edbfe20d2cbd2a6bccbb65990dc33902d2856 1972 
ruby-lograge_0.5.0-1.debian.tar.xz
 1b1037a3b9614e3eb2b548af1e2dccdd5cfcf21d3e5c88cc37dc92a514a9720b 7388 
ruby-lograge_0.5.0-1_all.deb
 9204fc1722fa7dfe64825b96cf20407d25a9e0fad05ec2589e73146787c1541b 7140 
ruby-lograge_0.5.0-1_amd64.buildinfo
Files:
 e2fd49ebd8ecf0cc10ab38a03840 2120 ruby optional ruby-lograge_0.5.0-1.dsc
 c8b8372ff652e2948bc088adf1060f00 5177 ruby optional 
ruby-lograge_0.5.0.orig.tar.gz
 ebb4e9a305cd7678f773af2eca79a748 1972 ruby optional 
ruby-lograge_0.5.0-1.debian.tar.xz
 c1ce8ab93fafb927a7175b147e62f08d 7388 ruby optional 
ruby-lograge_0.5.0-1_all.deb
 f90cab02326594e6a1be707d9f8b59f6 7140 ruby optional 
ruby-lograge_0.5.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlmgZUIACgkQzh+cZ0US
wiqeEhAAnJ0rxi2V0bV6XbQrc33S2Tj/Z5+g12ve7LAtobaEnkYiLiX86F3n40pe
deR0yFazVUPOmbYNvewzfVKYziDpoA32BWBs4tbFpxs3hks1jjZUsuSS+JAP5YvO
+itZfULc8JURqzRG0ZIih5cgJi5ycyUi0JN8uC4Gq5UcojH5UWxNGX7jdAkh1NPe
8XFD87fQY1rSihpWwBeSVcv1PZHduzDCA5ljDmJSXxNqdfOboTg6PEnLQkoB+Jtd
VXmbahRN/q39mjlg2xQnBbp0odIqnjBQS4at3J0bc0B16zFrsHW0UtUIB3TXje9T
zOEYDLlOOtHXMkOIsHWGn4Ph8/xDbidtiL9C+ME0jPj8xnSbyXWNQFQUg6m92Jyr
iLHMXJxvV0ebfN1fQuuuiytNbB/qwCAzfP/l70dPm/ivsGGlQHhKfLVGRvFpDS4I
vt7huzICkh2sPJrmOCnmy8NthSD8Dwf1IeszrqQ5RX9NZkceQgXGDkEYlIeZ4cM+
0G3YM4nUwB9h5PtLrKGxvjVsbvfG1PQPFBdGJY9Z/9NrAuFMuMspti+kAfUn522h
crdotle6m4/2P+1kLnrJotzUmzaeJqVvv/OrrrXHyg2aIxq7L2aJP7SIT+JjAcpQ
tkTzyq7vC0UUB48l+zHIh7PBalJ78qbK0dUJ2bMJLXTCWHZucAo=
=O+8S
-END PGP SIGNATURE End Message ---

Bug#865497: marked as done (check-mk: CVE-2017-9781: reflected XSS in webapi.py)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:14 +
with message-id 
and subject line Bug#865497: fixed in check-mk 1.4.0p9-1
has caused the Debian Bug report #865497,
regarding check-mk: CVE-2017-9781: reflected XSS in webapi.py
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.)


-- 
865497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: check-mk
Version: 1.2.8p16-1
Severity: grave
Tags: patch upstream security
Justification: user security hole

Hi,

the following vulnerability was published for check-mk.

CVE-2017-9781[0]:
| A cross site scripting (XSS) vulnerability exists in Check_MK versions
| 1.4.0x prior to 1.4.0p6, allowing an unauthenticated remote attacker to
| inject arbitrary HTML or JavaScript via the _username parameter when
| attempting authentication to webapi.py, which is returned unencoded
| with content type text/html.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-9781
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9781

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: check-mk
Source-Version: 1.4.0p9-1

We believe that the bug you reported is fixed in the latest version of
check-mk, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matt Taggart  (supplier of updated check-mk 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: SHA512

Format: 1.8
Date: Thu, 22 Jun 2017 15:44:37 -0700
Source: check-mk
Binary: check-mk-agent check-mk-agent-logwatch check-mk-server 
check-mk-config-icinga check-mk-livestatus check-mk-multisite check-mk-doc 
check-mk-common check-mk-monitoring-plugins
Architecture: source all amd64
Version: 1.4.0p9-1
Distribution: experimental
Urgency: high
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Matt Taggart 
Description:
 check-mk-agent - general purpose monitoring plugin for retrieving data
 check-mk-agent-logwatch - general purpose monitoring plugin for retrieving data
 check-mk-common - general purpose monitoring plugin for retrieving data 
(common lib
 check-mk-config-icinga - general purpose monitoring plugin for retrieving data
 check-mk-doc - general purpose monitoring plugin for retrieving data 
(documentat
 check-mk-livestatus - general purpose monitoring plugin for retrieving data
 check-mk-monitoring-plugins - general purpose monitoring plugin for retrieving 
data (monitoring
 check-mk-multisite - general purpose monitoring plugin for retrieving data
 check-mk-server - general purpose monitoring plugin for retrieving data
Closes: 865497
Changes:
 check-mk (1.4.0p9-1) experimental; urgency=high
 .
   * new upstream release
   * fixes CVE-2017-9781 (Closes: #865497)
   * move to the way upstream now does defaults
   * add new librrd-dev, libboost-dev, libboost-system-dev, g++-6 build-deps
   * new -common package for private python libs
Checksums-Sha1:
 5c431d542e1ae9276f7959af6e9c290c8925540b 2811 check-mk_1.4.0p9-1.dsc
 00d4c64f2051e8f432d9e0df7d5d5bcf2a6a00e0 22948802 check-mk_1.4.0p9.orig.tar.gz
 4ce803f8d0a55e23c564d2e5865c26557312f7a0 13929 check-mk_1.4.0p9-1.diff.gz
 ef3997b2ce59252627f3710099a44c799ed5a878 208186 
check-mk-agent-logwatch_1.4.0p9-1_all.deb
 1fe35779e21d44c24a94747691839f9f30659f5e 215670 
check-mk-agent_1.4.0p9-1_amd64.deb
 327a5ec94f795a65f48e8f735b47eba6e8ad9579 238758 
check-mk-common_1.4.0p9-1_all.deb
 5a89caace1dd5ff52cd75a65d218a91800cba12b 211144 
check-mk-config-icinga_1.4.0p9-1_amd64.deb
 ff63b5cdfcefaeda322c336b5f582b3ef5474b1e 990782 check-mk-doc_1.4.0p9-1_all.deb
 2b40e942a44956d05915e3ffc2b1097c33a1 90412 
check-mk-livestatus-dbgsym_1.4.0p9-1_amd64.deb
 78b6f1d7d6446e2fb638e428f9378fefa02b79c1 969002 
check-mk-livestatus_1.4.0p9-1_amd64.deb
 ef2a2017a8aaacdc718b7a2e3e092412bb0a6b62 227060 

Bug#876168: marked as done (ITP: ruby-debugger-ruby-core-source -- Provide Ruby core source files)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 07:00:26 +
with message-id 
and subject line Bug#876168: fixed in ruby-debugger-ruby-core-source 1.3.8+ds-1
has caused the Debian Bug report #876168,
regarding ITP: ruby-debugger-ruby-core-source -- Provide Ruby core source files
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.)


-- 
876168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

from rubygems.org/gems/debugger-ruby_core_source
dependency of gitlab 9.5

see https://lists.debian.org/debian-ruby/2017/09/msg00015.html for a
discussion







signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-debugger-ruby-core-source
Source-Version: 1.3.8+ds-1

We believe that the bug you reported is fixed in the latest version of
ruby-debugger-ruby-core-source, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-debugger-ruby-core-source 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: Tue, 19 Sep 2017 14:28:41 +0530
Source: ruby-debugger-ruby-core-source
Binary: ruby-debugger-ruby-core-source
Architecture: source all
Version: 1.3.8+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-debugger-ruby-core-source - Provide Ruby core source files
Closes: 876168
Changes:
 ruby-debugger-ruby-core-source (1.3.8+ds-1) unstable; urgency=medium
 .
   * Initial release (Closes: #876168)
Checksums-Sha1:
 b59add5705440e5544eb97ff3c4a64cc5e4dfaa2 2298 
ruby-debugger-ruby-core-source_1.3.8+ds-1.dsc
 0736b5548975c19294941900c85eafb24c52fa0c 2784 
ruby-debugger-ruby-core-source_1.3.8+ds.orig.tar.xz
 abf1c5306a1ce9b76190a6e29b4e90e1a86e872c 2584 
ruby-debugger-ruby-core-source_1.3.8+ds-1.debian.tar.xz
 0183c18221c027f6e2a573fde24fdf60e79d3e97 4708 
ruby-debugger-ruby-core-source_1.3.8+ds-1_all.deb
 c943d4885b8f37dc3d81cf7d958058a67aa1ebd5 6541 
ruby-debugger-ruby-core-source_1.3.8+ds-1_amd64.buildinfo
Checksums-Sha256:
 64c1eadaa789506496a55e37e671c560503a2bbfd90edad6773fbb09deabba48 2298 
ruby-debugger-ruby-core-source_1.3.8+ds-1.dsc
 a14aa0a48c1a904ba86361c35763d3d40b4183a5ca42faff65cebbd7a2421319 2784 
ruby-debugger-ruby-core-source_1.3.8+ds.orig.tar.xz
 8ab72727da4eaaffc53d87b13a9d33048b0d46e5a480d224c9a18bd7ca20ac54 2584 
ruby-debugger-ruby-core-source_1.3.8+ds-1.debian.tar.xz
 8cb5905d0efc9471d6ebcb264f71780c8920abc84589bda925c374dc1c6f76b3 4708 
ruby-debugger-ruby-core-source_1.3.8+ds-1_all.deb
 3e900e4e4f79c652ca1064cb9719a662dc7905d72369bc67e0d9fc37db4d5d6e 6541 
ruby-debugger-ruby-core-source_1.3.8+ds-1_amd64.buildinfo
Files:
 d697716a3f426d11bb7d01699ba90dc4 2298 ruby optional 
ruby-debugger-ruby-core-source_1.3.8+ds-1.dsc
 4562b8a8ddfede57439ca1b8259fa659 2784 ruby optional 
ruby-debugger-ruby-core-source_1.3.8+ds.orig.tar.xz
 14600bf1c0b92abafd6c25cb5ba84a33 2584 ruby optional 
ruby-debugger-ruby-core-source_1.3.8+ds-1.debian.tar.xz
 ac42e26d553e76f2be45127c32139ac5 4708 ruby optional 
ruby-debugger-ruby-core-source_1.3.8+ds-1_all.deb
 6b0d70929c5de1cda6105c402ec430c9 6541 ruby optional 
ruby-debugger-ruby-core-source_1.3.8+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlnA4DsACgkQzh+cZ0US
wiqcbA//ZVG5J9EvqB3Gn/hgrA/kN/4P61rUHgsl5funTugQAgfn9LTpO5DXyi4y
zHyo05GzC7afjzdYtDrj0pQtPCKRktS3pkVGjyetG4ssW0mfU+y7UL3WnWCW3KbJ
/6Tho6pyIPjPVtD2lpDKWp5+rDbSdrmaz8TfZYdVUhgMiZ7uSuZAZ+oBsoytX6Js
uJo2aH1JcAh6QnFuTUXDAegt4hQW22l94rCc58RXvKDwiMTUotXwmkUP34mmsOLL
gogsPlQoFM1VFt+zmGJ4ZWzCW1xwU2CgTEpI74YVpYDCTwI2U1sLWxa3Uou6UldO
mEYu4N4QM6RXYB4vtnM1HTg97Un+pvigEDEbOQ0LqCyop57+u3oopzb+Z4U/Zsc7
FUTsxn7thdCgBiMCBxh5gWIKElK0FXeXPS7jE+xcx57STlvjc9GQYaLWcYKIQleI

Bug#873513: marked as done (live-build: Running with LB_BUILD_WITH_CHROOT=false fails)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:00:41 +
with message-id <e1duas5-0008im...@fasolo.debian.org>
and subject line Bug#873513: fixed in live-build 1:20170920
has caused the Debian Bug report #873513,
regarding live-build: Running with LB_BUILD_WITH_CHROOT=false fails
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.)


-- 
873513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: live-build
Version: 1:20170807
Severity: normal
Tags: patch

Hi,

I've run into some problems running live-build with
LB_BUILD_WITH_CHROOT. I understand that this is not a recommended or
supported configuration (though I'm not entirely sure why not, given the
amount of code for it), but it's being used in the Webconverger project
since quite some time and it mostly works.

When running lb `lb config --build-with-chroot=false` followed by `lb
build`, the build fails with:

[2017-08-28 15:52:15] lb binary_syslinux
P: Begin installing syslinux...
E: /usr/share/ISOLINUX

It seems the check for ISOLINUX is using an old path, which is
corrected for chroot builds only.

I'm attaching a patch that unifies the dependency handling for with and
without chroot, which fixes this problem as well as adds some dependency
checks with LB_BUILD_WITH_CHROOT=false and simplifies some code. There
is a second patch (the first in the series), that makes sure that these
dependency checks actually give a proper error message for missing
packages on the host.

With these patches applied, the commands mentioned above produce a
working image.

Gr.

Matthijs

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing'), (500, 'oldstable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages live-build depends on:
ii  debootstrap  1.0.87

Versions of packages live-build recommends:
ii  apt-utils   1.3.1
ii  cpio2.11+dfsg-5
ii  live-boot-doc   1:20160511
ii  live-config-doc 5.20160608
ii  live-manual-html [live-manual]  2:20151217.1
ii  wget1.18-4

live-build suggests no packages.

-- no debconf information
>From 406ed00e806abb84252033ac609fcc9bcd83 Mon Sep 17 00:00:00 2001
From: Matthijs Kooijman <matth...@stdin.nl>
Date: Mon, 28 Aug 2017 15:14:34 +0200
Subject: [PATCH 1/2] Error out when needed packages are missing on the host

Previously, Check_package would only show an error when host packages
are missing on a non-apt system. On apt system, the packages would be
added to _LB_PACKAGES, which causes them to be installed in the chroot,
not in the host (or not at all if Install_package is not called). This
behaviour could break the build.

This applies to either packages that must be present in the host (as
checked with `Check_package host ...`), as well as packages that can be
either in the chroot or host (as checked with `Check_package chroot`)
when LB_BUILD_WITH_CHROOT=false.
---
 functions/packages.sh | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/functions/packages.sh b/functions/packages.sh
index c2f7cfabf..7c3592dac 100755
--- a/functions/packages.sh
+++ b/functions/packages.sh
@@ -16,16 +16,16 @@ Check_package ()
 
 	Check_installed "${CHROOT}" "${FILE}" "${PACKAGE}"
 
-	case "${INSTALL_STATUS}" in
-		1)
+	if [ "${INSTALL_STATUS}" -ne 0 ]
+	then
+		if [ "${LB_BUILD_WITH_CHROOT}" != "false" ]
+		then
 			_LB_PACKAGES="${_LB_PACKAGES} ${PACKAGE}"
-			;;
-
-		2)
+		else
 			Echo_error "You need to install %s on your host system." "${PACKAGE}"
 			exit 1
-			;;
-	esac
+		fi
+	fi
 }
 
 Install_package ()
-- 
2.11.0

>From 034bb0c00788f0927a068d151c53a8f341e215fa Mon Sep 17 00:00:00 2001
From: Matthijs Kooijman <matth...@stdin.nl>
Date: Mon, 28 Aug 2017 11:29:54 +0200
Subject: [PATCH 2/2] Check all dependencies independent of
 LB_BUILD_WITH_CHROOT

Since commit fdc9250bc (Changing package dependency checks within chroot
to work outside as well), Check_package automatically checks for
LB_BUILD_WITH_CHROOT and works inside as well as outside of the chroot,
so no need to check LB

Bug#873640: marked as done (live-build: Hdd image fails due to hard links in binary directory)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:00:41 +
with message-id <e1duas5-0008is...@fasolo.debian.org>
and subject line Bug#873640: fixed in live-build 1:20170920
has caused the Debian Bug report #873640,
regarding live-build: Hdd image fails due to hard links in binary directory
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.)


-- 
873640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: live-build
Version: 1:20161202
Severity: normal
Tags: patch

Hi Raphaël,

building a hdd image currently fails. After fixing #865586 (mkfs
complaining about existing partitions) I see:

  $ sudo lb config -b hdd --bootloader syslinux
  $ sudo lb build
  (...)

  P: Copying binary contents into image...
  cp: error writing 'chroot/binary.tmp/live/initrd.img': No space left on device
  cp: error writing 'chroot/binary.tmp/live/initrd.img-4.9.0-3-amd64': No space 
left on device

To generate an hdd image, binary_hdd first estimates the needed size of
the image using du. By default, when du finds multiple hardlinked copies
of a file, it counts them only once. However, when the target filesystem
is FAT, which does not support hardlinks, these files will take up more
space when finally copying the contents.

To fix this I've attached a patch that, passes --count-links to du when
the target is FAT, to make the space estimation correct.

This problem is exposed by commit 9c974b26b (Instead of renaming kernel
for syslinux, create hardlinks), which might need to be separately fixed
(to not waste space on FAT targets), but binary_hdd should handle
hardlinks more gracefully in any case.

I've tested with version 1:20170807 and 1:20170829, but marked this bug
as found in 1:20161202 since that is the first version that has the
above commit.

Gr.

Matthijs
>From 0c313e9ed3d0de7cfa6ef8e8e21c01a08b8e4a8c Mon Sep 17 00:00:00 2001
From: Matthijs Kooijman <matth...@stdin.nl>
Date: Tue, 29 Aug 2017 14:50:46 +0200
Subject: [PATCH 4/4] Handle hardlinks in binary_hdd

To generate an hdd image, binary_hdd first estimates the needed size of
the image using du. By default, when du finds multiple hardlinked copies
of a file, it counts them only once. However, when the target filesystem
is FAT, which does not support hardlinks, these files will take up more
space when finally copying the contents, breaking the build:

	P: Copying binary contents into image...
	cp: error writing 'chroot/binary.tmp/live/initrd.img-4.9.0-3-amd64': No space left on device
	cp: error writing 'chroot/binary.tmp/efi/boot/bootx64.efi': No space left on device
	cp: error writing 'chroot/binary.tmp/efi/boot/bootia32.efi': No space left on device
	cp: cannot create directory 'chroot/binary.tmp/boot/grub': No space left on device
	cp: cannot create directory 'chroot/binary.tmp/isolinux': No space left on device

To fix this, pass --count-links to du when the target is FAT, to make
the space estimation correct.

This problem is exposed by commit 9c974b26b (Instead of renaming kernel
for syslinux, create hardlinks), which might need to be separately fixed
(to not waste space on FAT targets), but binary_hdd should at least
handle hardlinks more gracefully.
---
 scripts/build/binary_hdd | 17 +++--
 1 file changed, 15 insertions(+), 2 deletions(-)

diff --git a/scripts/build/binary_hdd b/scripts/build/binary_hdd
index 400403c0a..c6b842e95 100755
--- a/scripts/build/binary_hdd
+++ b/scripts/build/binary_hdd
@@ -97,6 +97,19 @@ then
 	rm -f ${LIVE_iMAGE_NAME}.img
 fi
 
+case "${LB_BINARY_FILESYSTEM}" in
+	fat*)
+		# If the target does not support hardlinks, tell du to
+		# count them double
+		DU_OPTIONS="--count-links"
+		;;
+
+	*)
+		DU_OPTIONS=""
+		;;
+esac
+
+
 # Enforce fat32 if we find individual files bigger than 2GB
 if [ "${LB_BINARY_FILESYSTEM}" = "fat16" ] && [ -n "$(find binary -size +1999M)" ]
 then
@@ -107,7 +120,7 @@ then
 fi
 
 # Enforce fat32 if we have images in total bigger than 2GB
-if [ "${LB_BINARY_FILESYSTEM}" = "fat16" ] && [ "$(du -s binary | awk '{ print $1 }')" -gt "190" ]
+if [ "${LB_BINARY_FILESYSTEM}" = "fat16" ] && [ "$(du ${DU_OPTIONS} -s binary | awk '{ print $1 }')" -gt "190" ]
 then
 	Echo_warning "FAT16 doesn't support partitions larger than 2GB, automatically enforcing FAT32"
 
@@ -127,7 +140,7 @@ fi
 # Everything which comes here needs to be

Bug#865586: marked as done (live-build: binary_hdd failed with mkfs.vfat error)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:00:41 +
with message-id <e1duas5-0008ig...@fasolo.debian.org>
and subject line Bug#865586: fixed in live-build 1:20170920
has caused the Debian Bug report #865586,
regarding live-build: binary_hdd failed with mkfs.vfat error
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.)


-- 
865586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: live-build
Version: 1:20170213
Severity: important

Dear Maintainer,

   The 'lb binary_hdd' script halt with a mkfs.vfat error when build a FAT32 or 
FAT16 hdd image
   
   With a simple live-build config, I launched the whole building process that 
halt with this error (that is not shown as error):

   [2017-06-22 20:12:00] lb binary_hdd
   P: Begin building binary hdd image...
   0+0 records in
   0+0 records out
   0 bytes copied, 2.743e-05 s, 0.0 kB/s
   !!! The following error/warning messages can be ignored !!!
   P: Mounting /dev/loop1 with offset 0
   1+0 records in
   1+0 records out
   440 bytes copied, 0.0265552 s, 16.6 kB/s
   P: Mounting /dev/loop1 with offset 1048576
   mkfs.fat 4.1 (2017-01-24)
   mkfs.vfat: Partitions or virtual mappings on device '/dev/loop1', not making 
filesystem (use -I to override)
   P: Begin unmounting filesystems...
   P: Saving caches...
   Reading package lists... Done
   Building dependency tree
   Reading state information... Done


   It seems that mkfs.vfat gives the answer: '-I' in command call


-- Package-specific info:

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages live-build depends on:
ii  debootstrap  1.0.90

Versions of packages live-build recommends:
ii  apt-utils   1.4.6
ii  cpio2.11+dfsg-6
ii  live-boot-doc   1:20170112
ii  live-config-doc 5.20170316
ii  live-manual-html [live-manual]  2:20151217.1
ii  wget1.19.1-3

live-build suggests no packages.

-- no debconf information
--- binary_hdd-orig 2017-06-22 20:16:11.927603985 +0200
+++ binary_hdd  2017-06-22 20:16:39.211437132 +0200
@@ -223,13 +223,13 @@
 
fat16)
MKFS="vfat"
-   MKFS_OPTIONS="-F 16 -n ${LB_HDD_LABEL}"
+   MKFS_OPTIONS="-F 16 -n ${LB_HDD_LABEL} -I"
MOUNT_OPTIONS=""
;;
 
fat32)
MKFS="vfat"
-   MKFS_OPTIONS="-F 32 -n ${LB_HDD_LABEL}"
+   MKFS_OPTIONS="-F 32 -n ${LB_HDD_LABEL} -I"
MOUNT_OPTIONS=""
    ;;
 
--- End Message ---
--- Begin Message ---
Source: live-build
Source-Version: 1:20170920

We believe that the bug you reported is fixed in the latest version of
live-build, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog <hert...@debian.org> (supplier of updated live-build 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: SHA512

Format: 1.8
Date: Wed, 20 Sep 2017 10:01:42 +0200
Source: live-build
Binary: live-build
Architecture: source
Version: 1:20170920
Distribution: unstable
Urgency: medium
Maintainer: Debian Live <debian-l...@lists.debian.org>
Changed-By: Raphaël Hertzog <hert...@debian.org>
Description:
 live-build - Live System Build Components
Closes: 865586 873513 873640
Changes:
 live-build (1:20170920) unstable; urgency=medium
 .
   * Auto-update version strings in manual pages.
   * Update default value of PREPARER to correct the embedded URL.
   * Pass --partscan to losetup to clean up partition devices lingering
 from former operations. Closes: #865586
 Thanks to Matthijs Kooijman <

Bug#876128: marked as done (manpages-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man4/console_ioctl.4.gz)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:00:50 +
with message-id 
and subject line Bug#876128: fixed in manpages 4.13-3
has caused the Debian Bug report #876128,
regarding manpages-dev: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/man/man4/console_ioctl.4.gz
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.)


-- 
876128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-dev
Version: 4.13-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package manpages-dev.
  Preparing to unpack .../manpages-dev_4.13-2_all.deb ...
  Unpacking manpages-dev (4.13-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manpages-dev_4.13-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man4/console_ioctl.4.gz', which is also 
in package manpages 4.12-2
  Errors were encountered while processing:
   /var/cache/apt/archives/manpages-dev_4.13-2_all.deb


cheers,

Andreas


manpages=4.12-2_manpages-dev=4.13-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: manpages
Source-Version: 4.13-3

We believe that the bug you reported is fixed in the latest version of
manpages, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated manpages 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: Wed, 20 Sep 2017 10:07:04 +0200
Source: manpages
Binary: manpages manpages-dev
Architecture: source
Version: 4.13-3
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze 
Changed-By: Dr. Tobias Quathamer 
Description:
 manpages   - Manual pages about using a GNU/Linux system
 manpages-dev - Manual pages about using GNU/Linux for development
Closes: 876128
Changes:
 manpages (4.13-3) unstable; urgency=medium
 .
   * Add Breaks/Replaces to manpages and manpages-dev.
 Thanks to Andreas Beckmann  (Closes: #876128)
   * Fail if there is no Breaks/Replaces for a newly moved file
Checksums-Sha1:
 32071ccdb480db1294c54c78520982e3be0ea31b 1948 manpages_4.13-3.dsc
 304305972fb9fd630016e32a6e07c788fae06a78 75580 manpages_4.13-3.debian.tar.xz
 fe32e9a06c1185ba1acebf96d6056028084fd230 5454 manpages_4.13-3_amd64.buildinfo
Checksums-Sha256:
 bbae4a4cceb7615352da0b69a4a693144c165d79000df1a6aff33e152d1e7207 1948 
manpages_4.13-3.dsc
 a5b8e765f83cb97ff2fc0c8a29fad7ce2ae46065510c2ccd0e8c56daac62d6cc 75580 
manpages_4.13-3.debian.tar.xz
 2bdccb3fff3e048b55f7593654e1719ecc64ccd5daa3bc3c22e5d8bcc5ffcf74 5454 
manpages_4.13-3_amd64.buildinfo
Files:
 425819a8d1f79b000bb26910068a4f51 1948 doc standard manpages_4.13-3.dsc
 1df263c0bc6bc5009f852f273be52d0e 75580 doc standard 
manpages_4.13-3.debian.tar.xz
 4371d9d27ca86b552b73afab739b6f82 5454 doc standard 
manpages_4.13-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlnCIjEACgkQEwLx8Dbr
6xnuTA/+KnMLFkuIAVQMXL6uFRBszs86shxrqvmM60Rl3LOHx1FCOqFcY/g/iOgh
UjI4ZClldda7Nj2GxMQ8Fhii55XdkBWGkKnw/Ps3Ly1VJ4l+XujXhkeOliWJOzVh
bByLoAyUYkPqxrzHNUIzz3kxLGaTWP/uULUo/45RrgmqO3mSjcNZqw11CG5HcWuv
6T53x/Ph3uHTyQnzc35t+C94tQIUru7JdoPk7bfOVaDllzJ+UMdiQ8gApm13xDjl
NalRU+TXKEAOJeMOv/ovh3C3EkErpilkkRp49/XWXi3RnjRaYvfpMy362U+7KzSt
cbdp+hbF9kEgrvShlF1Eqvfriet95hD1N4M4oLlNXjyWsW1i6RycvU266hUpCvK3
PUG14FM7qREAZ+ahxxgPBLAHx7dY+vhad3YZretHnE5z5R6nmJcmE/Qq84Xub9Hn
90aQ7C8yqzIJwgGwU+eFxKeZAWzbskRyKnU20Kv+/ZAe18DpcKh1G0w7zn0Ha2tW
XX3VcU/f3AfcmKsunaRCxMppPkeZQ7dMMRJB6ni0vfTWH9SnjkRMylAWED9KdYxu

Bug#876246: marked as done (gcc-7 fails to build fortran cross compiler since debhelper became strict about -p)

[Debian Bug Tracking System]

libn32go11-dbg - Runtime library for GNU Go applications (n32 debug symbols)
 libn32gomp1 - GCC OpenMP (GOMP) support library (n32)
 libn32gomp1-dbg - GCC OpenMP (GOMP) support library (n32 debug symbols)
 libn32objc-7-dev - Runtime library for GNU Objective-C applications (n32 
development
 libn32objc4 - Runtime library for GNU Objective-C applications (n32)
 libn32objc4-dbg - Runtime library for GNU Objective-C applications (n32 debug 
symbo
 libn32stdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libn32stdc++6 - GNU Standard C++ Library v3 (n32)
 libn32stdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libobjc-7-dev - Runtime library for GNU Objective-C applications (development 
fil
 libobjc4   - Runtime library for GNU Objective-C applications
 libobjc4-dbg - Runtime library for GNU Objective-C applications (debug symbols)
 libquadmath0 - GCC Quad-Precision Math Library
 libquadmath0-dbg - GCC Quad-Precision Math Library (debug symbols)
 libstdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libstdc++-7-doc - GNU Standard C++ Library v3 (documentation files)
 libstdc++-7-pic - GNU Standard C++ Library v3 (shared library subset kit)
 libstdc++6 - GNU Standard C++ Library v3
 libstdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libtsan0   - ThreadSanitizer -- a Valgrind-based detector of data races (runti
 libtsan0-dbg - ThreadSanitizer -- a Valgrind-based detector of data races 
(debug
 libubsan0  - UBSan -- undefined behaviour sanitizer (runtime)
 libubsan0-dbg - UBSan -- undefined behaviour sanitizer (debug symbols)
 libx32asan4 - AddressSanitizer -- a fast memory error detector (x32)
 libx32asan4-dbg - AddressSanitizer -- a fast memory error detector (x32 debug 
symbo
 libx32atomic1 - support library providing __atomic built-in functions (x32)
 libx32atomic1-dbg - support library providing __atomic built-in functions (x32 
debug
 libx32cilkrts5 - Intel Cilk Plus language extensions (x32)
 libx32cilkrts5-dbg - Intel Cilk Plus language extensions (x32 debug symbols)
 libx32gcc-7-dev - GCC support library (x32 development files)
 libx32gcc1 - GCC support library (x32)
 libx32gcc1-dbg - GCC support library (debug symbols)
 libx32gfortran-7-dev - Runtime library for GNU Fortran applications (x32 
development fil
 libx32gfortran4 - Runtime library for GNU Fortran applications (x32)
 libx32gfortran4-dbg - Runtime library for GNU Fortran applications (x32 debug 
symbols)
 libx32go11 - Runtime library for GNU Go applications (x32)
 libx32go11-dbg - Runtime library for GNU Go applications (x32 debug symbols)
 libx32gomp1 - GCC OpenMP (GOMP) support library (x32)
 libx32gomp1-dbg - GCC OpenMP (GOMP) support library (x32 debug symbols)
 libx32gphobos-7-dev - Phobos D standard library (x32 development files)
 libx32gphobos71 - Phobos D standard library (runtime library)
 libx32gphobos71-dbg - Phobos D standard library (debug symbols)
 libx32itm1 - GNU Transactional Memory Library (x32)
 libx32itm1-dbg - GNU Transactional Memory Library (x32 debug symbols)
 libx32lsan0 - LeakSanitizer -- a memory leak detector (x32)
 libx32lsan0-dbg - LeakSanitizer -- a memory leak detector (x32 debug symbols)
 libx32objc-7-dev - Runtime library for GNU Objective-C applications (x32 
development
 libx32objc4 - Runtime library for GNU Objective-C applications (x32)
 libx32objc4-dbg - Runtime library for GNU Objective-C applications (x32 debug 
symbo
 libx32quadmath0 - GCC Quad-Precision Math Library (x32)
 libx32quadmath0-dbg - GCC Quad-Precision Math Library (x32 debug symbols)
 libx32stdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libx32stdc++6 - GNU Standard C++ Library v3 (x32)
 libx32stdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libx32ubsan0 - UBSan -- undefined behaviour sanitizer (x32)
 libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols)
Closes: 872672 876246
Changes:
 gcc-7 (7.2.0-6) unstable; urgency=medium
 .
   * Update to SVN 20170920 (r253002) from the gcc-7-branch.
 - Fix PR target/82112 (PPC), PR c++/81355, PR tree-optimization/82084,
   PR tree-optimization/82108, PR target/81325 (PPC), PR c++/81236,
   PR c++/80767, PR c++/82030, PR c++/80935, PR c++/81671, PR c++/81525,
   PR c++/81314, PR libgfortran/78387.
   * Fix fortran cross compiler build with debhelper 10.9. Closes: #876246.
   * Strip the compiler binaries again. Closes: #872672.
   * Bump binutils dependency to 2.29.1 for sid/buster.
Checksums-Sha1:
 b6ef89e31d0c3236ae9368fcf1cf0a31d1f19c5f 26322 gcc-7_7.2.0-6.dsc
 41d3cd873d099e5ecfe9e12dbb980401b1bd8494 3061771 gcc-7_7.2.0-6.diff.gz
 08c0939fbef4a040d9798b2291557c0c32f987ac 9774 gcc-7_7.2.0-6_source.buildinfo
Checksums-Sha256:
 7a51f944ad88447d1c1f76b3e60427b418296b7c686e81cd2945e9d3048cf260 26322 
gcc-7_7.2.0-6.dsc
 c5c5155c5661b5b3440a31a9000c9b564cea70adab47b9f838bdf38b0e642da0 3061771 
gcc-7_7.2.0-6.diff.gz
 27ea9dd6c094259d58d122be8324297fa2d8c5529ce5e3e31b926af4f1

Bug#873514: marked as done (golang-google-cloud: FTBFS due to changes in dependency)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:36:25 +
with message-id 
and subject line Bug#873514: fixed in golang-google-cloud 0.9.0-1
has caused the Debian Bug report #873514,
regarding golang-google-cloud: FTBFS due to changes in dependency
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.)


-- 
873514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-google-cloud
Version: 0.5.0-2
Severity: serious
Justification: fails to build from source

Since the latest update to golang-google-genproto-dev, this package FTBFS.

The fix for this is in release 0.7.0, but that requires also updating
golang-github-googleapis-gax-go-dev, and I am not sure about the effect on
other rdeps like kubernetes, docker, and cadvisor.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: golang-google-cloud
Source-Version: 0.9.0-1

We believe that the bug you reported is fixed in the latest version of
golang-google-cloud, 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 873...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated golang-google-cloud 
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: Wed, 20 Sep 2017 09:02:31 +
Source: golang-google-cloud
Binary: golang-google-cloud-dev golang-google-cloud-compute-metadata-dev
Architecture: source
Version: 0.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 golang-google-cloud-compute-metadata-dev - Google Cloud Platform APIs (only 
cloud/compute/metadata)
 golang-google-cloud-dev - Google Cloud Platform APIs
Closes: 873514
Changes:
 golang-google-cloud (0.9.0-1) unstable; urgency=medium
 .
   [ Martín Ferrari ]
   * debian/control: Update Standards-Version (no changes).
   * debian/control: Mark package as autopkgtest-able.
   * debian/control: Remove unneded versioned deps.
   * debian/copyright: Format uses http protocol instead of https.
   * Add watch file.
 .
   [ Shengjing Zhu ]
   * New upstream release (Closes: #873514)
   * Refresh patches
 + Drop 0001-Bug#840311-fix-test-timeouts.patch
 + Drop 0002-Failing_test.patch
 + Rework patch that disable network access in testing
   * Update new Build-Depends
 + Add golang-github-golang-mock-dev Build-Depends
 + Bump golang-google-grpc-dev to 1.6.0
 + Bump golang-github-googleapis-gax-go-dev to 0.0~git20170902.8c160ca
 + Bump golang-google-api-dev to 0.0~git20170907.b1ecfb3
   * Update compat and dh to 10
   * Update pkg-go team name
   * Change priority to optional
   * No more internal/cloud.go in golang-google-cloud-compute-metadata-dev
   * Run short test only
Checksums-Sha1:
 2e69ed0de49e5385f671014bb341a82b815574d3 2709 golang-google-cloud_0.9.0-1.dsc
 188fe5d177f976f37bfb8fcdc023fc9cd5e0fb3b 1054705 
golang-google-cloud_0.9.0.orig.tar.gz
 7a4a66c43f387758cd2c96e20eefa22eb10a2f57 5620 
golang-google-cloud_0.9.0-1.debian.tar.xz
 715d5f57ba8fd21436cca6798ee232c5a4835349 6904 
golang-google-cloud_0.9.0-1_amd64.buildinfo
Checksums-Sha256:
 e4d81c1251585d7772aa2d4487037fb20192b38ca418163f008df4af8b5a6a4c 2709 
golang-google-cloud_0.9.0-1.dsc
 c0342af11242770c9db92252ccc728325ddc133216f23ae5954e007f8d0838d8 1054705 
golang-google-cloud_0.9.0.orig.tar.gz
 227020a7fc8d9f5be39f8733ed098c1507506d65b8d067322d15be28dc3fafc0 5620 
golang-google-cloud_0.9.0-1.debian.tar.xz
 00b90075adc08daa7207248e00e9ce41631470fa70d14757ad10231dedc1a00d 6904 
golang-google-cloud_0.9.0-1_amd64.buildinfo
Files:
 

Bug#875905: marked as done (mark discount Multi-Arch: foreign)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 08:52:13 +
with message-id 
and subject line Bug#875905: fixed in discount 2.2.3b8-1
has caused the Debian Bug report #875905,
regarding mark discount Multi-Arch: foreign
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.)


-- 
875905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: discount
Version: 2.2.2-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:unpaper

unpaper fails to cross build from source, because running discount fails
with:

| /usr/bin/markdown: 1: /usr/bin/markdown: Syntax error: word unexpected 
(expecting ")")

A shell is trying to interpret markdown after failing to execute it with
-ENOEXEC. It needs the build architecture discount rather than the host
architecture discount. This can either be achieved by annotating the
discount dependency with :native or by marking discount Multi-Arch:
foreign. Since discount only contains command line utilities and it
looks like their output does not depend on the architecture discount was
compiled for, the latter looks correct to me. Please consider applying
the attached patch.

Helmut
diff --minimal -Nru discount-2.2.2/debian/changelog 
discount-2.2.2/debian/changelog
--- discount-2.2.2/debian/changelog 2017-01-19 23:42:00.0 +0100
+++ discount-2.2.2/debian/changelog 2017-09-15 20:35:33.0 +0200
@@ -1,3 +1,10 @@
+discount (2.2.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark discount binary package Multi-Arch: foreign (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 15 Sep 2017 20:35:33 +0200
+
 discount (2.2.2-1) unstable; urgency=medium
 
   * New upstream release
diff --minimal -Nru discount-2.2.2/debian/control discount-2.2.2/debian/control
--- discount-2.2.2/debian/control   2017-01-19 23:42:00.0 +0100
+++ discount-2.2.2/debian/control   2017-09-15 20:35:12.0 +0200
@@ -10,6 +10,7 @@
 
 Package: discount
 Architecture: any
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}, libmarkdown2 (= ${binary:Version})
 Conflicts: markdown, libtext-markdown-perl
 Description: implementation of the Markdown markup language in C
--- End Message ---
--- Begin Message ---
Source: discount
Source-Version: 2.2.3b8-1

We believe that the bug you reported is fixed in the latest version of
discount, 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 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alessandro Ghedini  (supplier of updated discount 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: SHA512

Format: 1.8
Date: Wed, 20 Sep 2017 09:33:51 +0100
Source: discount
Binary: discount libmarkdown2 libmarkdown2-dev
Architecture: source
Version: 2.2.3b8-1
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini 
Changed-By: Alessandro Ghedini 
Description:
 discount   - implementation of the Markdown markup language in C
 libmarkdown2 - implementation of the Markdown markup language in C (library)
 libmarkdown2-dev - implementation of the Markdown markup language in C (dev 
files)
Closes: 875905
Changes:
 discount (2.2.3b8-1) unstable; urgency=medium
 .
   * New upstream release
   * Bump Standards-Version to 4.1.0 (no changes needed)
   * Mark discount Multi-Arch: foreign (Closes: #875905)
   * Update 03_fix-typo.patch
Checksums-Sha1:
 1bf4c756bd987ae9b265c0133d16317d08f44f26 2029 discount_2.2.3b8-1.dsc
 aea4b01e61ddadccc3e9de3f0be43ef031f7ffad 119963 discount_2.2.3b8.orig.tar.gz
 1f879a440c620717def6f04e5fee01a46b4ca5e0 5436 discount_2.2.3b8-1.debian.tar.xz
 e3782f4c43c84d5fb422bcc457b8cc45eb345eb9 6465 
discount_2.2.3b8-1_amd64.buildinfo
Checksums-Sha256:
 80eea3b88ed1f696f580e846815363a21ad91eb1b1a785b1486227d4180408e2 2029 
discount_2.2.3b8-1.dsc
 5d69aa20c43e0da5ac8509c4f95880720655a9b9e36206c5b5adcbba75f80391 119963 
discount_2.2.3b8.orig.tar.gz
 31beabc3ccdaf3aba7248f50cb891e8b6c2795cf0513503ef413f325ba0cca7c 5436 

Bug#875913: marked as done (plplot-tcl,libplplot-{java,lua}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:03:20 +
with message-id 
and subject line Bug#875913: fixed in plplot 5.13.0+dfsg-1~exp2
has caused the Debian Bug report #875913,
regarding plplot-tcl,libplplot-{java,lua}: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
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.)


-- 
875913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plplot-tcl,libplplot-java,libplplot-lua
Version: 5.13.0+dfsg-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  sid -> experimental

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (scroll to the bottom...):

0m18.0s INFO: dirname part contains a symlink:
  /usr/share/doc/plplot-tcl/changelog.Debian.gz (plplot-tcl) != 
/usr/share/doc/libplplot12/changelog.Debian.gz (?)
/usr/share/doc/plplot-tcl -> libplplot12
  /usr/share/doc/plplot-tcl/changelog.gz (plplot-tcl) != 
/usr/share/doc/libplplot12/changelog.gz (?)
/usr/share/doc/plplot-tcl -> libplplot12
  /usr/share/doc/plplot-tcl/copyright (plplot-tcl) != 
/usr/share/doc/libplplot12/copyright (?)
/usr/share/doc/plplot-tcl -> libplplot12

0m15.9s INFO: dirname part contains a symlink:
  /usr/share/doc/libplplot-java/changelog.Debian.gz (libplplot-java) != 
/usr/share/doc/libplplot12/changelog.Debian.gz (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/changelog.gz (libplplot-java) != 
/usr/share/doc/libplplot12/changelog.gz (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/copyright (libplplot-java) != 
/usr/share/doc/libplplot12/copyright (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/examples (libplplot-java) != 
/usr/share/doc/libplplot12/examples (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/examples/CMakeLists.txt.gz (libplplot-java) != 
/usr/share/doc/libplplot12/examples/CMakeLists.txt.gz (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/examples/Makefile.examples.in (libplplot-java) 
!= /usr/share/doc/libplplot12/examples/Makefile.examples.in (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/examples/README.javademos (libplplot-java) != 
/usr/share/doc/libplplot12/examples/README.javademos (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/examples/x00.java (libplplot-java) != 
/usr/share/doc/libplplot12/examples/x00.java (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/examples/x01.java.gz (libplplot-java) != 
/usr/share/doc/libplplot12/examples/x01.java.gz (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/examples/x02.java.gz (libplplot-java) != 
/usr/share/doc/libplplot12/examples/x02.java.gz (?)
/usr/share/doc/libplplot-java -> libplplot12
  /usr/share/doc/libplplot-java/examples/x03.java (libplplot-java) != 
/usr/share/doc/libplplot12/examples/x03.java (?)

Bug#875911: marked as done (libqsastime-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:03:20 +
with message-id 
and subject line Bug#875911: fixed in plplot 5.13.0+dfsg-1~exp2
has caused the Debian Bug report #875911,
regarding libqsastime-dev: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
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.)


-- 
875911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqsastime-dev
Version: 5.13.0+dfsg-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  sid -> experimental

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (scroll to the bottom...):

0m14.6s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libqsastime-dev/changelog.Debian.gz (libqsastime-dev:amd64) != 
/usr/share/doc/libqsastime0/changelog.Debian.gz (libqsastime0:amd64)
/usr/share/doc/libqsastime-dev -> libqsastime0
  /usr/share/doc/libqsastime-dev/changelog.gz (libqsastime-dev:amd64) != 
/usr/share/doc/libqsastime0/changelog.gz (libqsastime0:amd64)
/usr/share/doc/libqsastime-dev -> libqsastime0
  /usr/share/doc/libqsastime-dev/copyright (libqsastime-dev:amd64) != 
/usr/share/doc/libqsastime0/copyright (libqsastime0:amd64)
/usr/share/doc/libqsastime-dev -> libqsastime0


cheers,

Andreas


libqsastime-dev_5.13.0+dfsg-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: plplot
Source-Version: 5.13.0+dfsg-1~exp2

We believe that the bug you reported is fixed in the latest version of
plplot, 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 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated plplot 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: SHA512

Format: 1.8
Date: Wed, 20 Sep 2017 09:26:16 +0200
Source: plplot
Binary: libplplot15 libplplot-dev libplplotcxx13 libplplotfortran0 
libplplot-java libcsironn0 libcsirocsa0 libqsastime0 libqsastime-dev 
plplot-driver-xwin plplot-driver-wxwidgets libplplotwxwidgets1 plplot-tcl 
plplot-tcl-bin plplot-tcl-dev plplot-driver-cairo plplot-driver-qt libplplotqt2 
python-plplot python-plplot-qt python3-plplot python3-plplot-qt octave-plplot 
libplplotada2 libplplot-ada-dev plplot-doc libplplot-ocaml libplplot-ocaml-dev 
libplplot-lua
Architecture: source
Version: 5.13.0+dfsg-1~exp2
Distribution: experimental
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Ole Streicher 
Description:
 libcsirocsa0 - Scientific plotting library (CSIRO csa 

Bug#876227: marked as done (release.debian.org: nmu: cheese, gnome-dvb-daemon, grilo-plugins, gstreamer-vaapi, webkit2gtk)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 11:11:55 +0200
with message-id 
and subject line Re: release.debian.org: nmu: cheese, gnome-dvb-daemon, 
grilo-plugins, gstreamer-vaapi, webkit2gtk
has caused the Debian Bug report #876227,
regarding release.debian.org: nmu: cheese, gnome-dvb-daemon, grilo-plugins, 
gstreamer-vaapi, webkit2gtk
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.)


-- 
876227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi team!

A new version of gst-plugins-bad1.0 was uploaded yesterday and all its
reverse dependencies are now in need of a binNMU to fix the wrong shlibs
versioning.

  nmu cheese_3.26.0-1 . ANY . -m 'Rebuild against new gst-plugins-bad1.0 
version'
  nmu gnome-dvb-daemon_1:0.2.91~git20170110-2 . ANY . -m 'Rebuild against new 
gst-plugins-bad1.0 version'
  nmu grilo-plugins_0.3.5-2 . ANY . -m 'Rebuild against new gst-plugins-bad1.0 
version'
  nmu gstreamer-vaapi_1.12.2-1 . ANY . -m 'Rebuild against new 
gst-plugins-bad1.0 version'
  nmu webkit2gtk_2.18.0-2 . ANY . -m 'Rebuild against new gst-plugins-bad1.0 
version'

Thanks.


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

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Tue, 19 Sep 2017 22:49:11 +0200 "Matteo F. Vescovi"  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> Hi team!
> 
> A new version of gst-plugins-bad1.0 was uploaded yesterday and all its
> reverse dependencies are now in need of a binNMU to fix the wrong shlibs
> versioning.
> 
>   nmu cheese_3.26.0-1 . ANY . -m 'Rebuild against new gst-plugins-bad1.0 
> version'
>   nmu gnome-dvb-daemon_1:0.2.91~git20170110-2 . ANY . -m 'Rebuild against new 
> gst-plugins-bad1.0 version'
>   nmu grilo-plugins_0.3.5-2 . ANY . -m 'Rebuild against new 
> gst-plugins-bad1.0 version'
>   nmu gstreamer-vaapi_1.12.2-1 . ANY . -m 'Rebuild against new 
> gst-plugins-bad1.0 version'
>   nmu webkit2gtk_2.18.0-2 . ANY . -m 'Rebuild against new gst-plugins-bad1.0 
> version'

Scheduled.

Emilio--- End Message ---

Bug#867247: marked as done (tomcat8: Package tomcat8 or libtomcat8-java should depends package libservlet3.1-java)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:09:06 +
with message-id 
and subject line Bug#867247: fixed in tomcat8 8.5.21-1
has caused the Debian Bug report #867247,
regarding tomcat8: Package tomcat8 or libtomcat8-java should depends package 
libservlet3.1-java
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.)


-- 
867247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tomcat8
Version: 8.5.16-1
Severity: normal
Tags: patch

Dear Tomcat Maintainers,

t the moment a whole installation of the tomcat8 packages does not require the 
installation of libservlet3.1-java caused by missing of a dependency within the 
control file.

The following error messages occured in catalina.out after Tomcat has been 
started.

5-Jul-2017 05:44:03.147 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file:/usr/share/java/el-api-3.0.jar] from classloader hierarchy
 java.io.FileNotFoundException: /usr/share/java/el-api-3.0.jar (No such file or 
directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:219)
at java.util.zip.ZipFile.(ZipFile.java:149)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
at 
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
at org.apache.jasper.servlet.TldScanner.scanJars(TldScanner.java:262)
at org.apache.jasper.servlet.TldScanner.scan(TldScanner.java:104)
at 
org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:101)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at 
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1144)
at 
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1878)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

05-Jul-2017 05:44:03.147 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file:/usr/share/java/jsp-api-2.3.jar] from classloader hierarchy
 java.io.FileNotFoundException: /usr/share/java/jsp-api-2.3.jar (No such file 
or directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:219)
at java.util.zip.ZipFile.(ZipFile.java:149)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
at 
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
at org.apache.jasper.servlet.TldScanner.scanJars(TldScanner.java:262)
at org.apache.jasper.servlet.TldScanner.scan(TldScanner.java:104)
at 
org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:101)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at 

Bug#871892: marked as done (tomcat8: Please update the Uploaders list)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:09:06 +
with message-id 
and subject line Bug#871892: fixed in tomcat8 8.5.21-1
has caused the Debian Bug report #871892,
regarding tomcat8: Please update the Uploaders list
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.)


-- 
871892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tomcat8
Severity: minor
Tags: pending
User: nomad...@debian.org
Usertags: cleanup

As title says.

I haven't been involved in the maintenance of this package since several
years ago.

I intend to keep an eye on this package for the current oldstable and
stable release lifecycles. However, it's very unlikely I'll be involved
in its current development cycle (buster).

I removed myself from uploaders list, so the fix for this issue should
be included in the next upload.

Cheers,
Miguel.


-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: tomcat8
Source-Version: 8.5.21-1

We believe that the bug you reported is fixed in the latest version of
tomcat8, 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 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated tomcat8 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: SHA512

Format: 1.8
Date: Wed, 20 Sep 2017 10:06:56 +0200
Source: tomcat8
Binary: tomcat8-common tomcat8 tomcat8-user libtomcat8-java 
libtomcat8-embed-java libservlet3.1-java libservlet3.1-java-doc tomcat8-admin 
tomcat8-examples tomcat8-docs
Architecture: source
Version: 8.5.21-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libservlet3.1-java - Servlet 3.1, JSP 2.3, EL 3.0 and WebSocket 1.0 Java API 
classes
 libservlet3.1-java-doc - Servlet 3.1, JSP 2.3, EL 3.0 and WebSocket 1.0 Java 
API documenta
 libtomcat8-embed-java - Apache Tomcat 8 - Servlet and JSP engine -- embed 
libraries
 libtomcat8-java - Apache Tomcat 8 - Servlet and JSP engine -- core libraries
 tomcat8- Apache Tomcat 8 - Servlet and JSP engine
 tomcat8-admin - Apache Tomcat 8 - Servlet and JSP engine -- admin web 
application
 tomcat8-common - Apache Tomcat 8 - Servlet and JSP engine -- common files
 tomcat8-docs - Apache Tomcat 8 - Servlet and JSP engine -- documentation
 tomcat8-examples - Apache Tomcat 8 - Servlet and JSP engine -- example web 
applicati
 tomcat8-user - Apache Tomcat 8 - Servlet and JSP engine -- tools to create user
Closes: 867247 871892
Changes:
 tomcat8 (8.5.21-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Emmanuel Bourg ]
   * New upstream release
 - Refreshed the patches
 - Disabled Checkstyle
   * Changed the Class-Path manifest entry of tomcat8-jasper.jar to use
 the specification jars from libtomcat8-java instead of libservlet3.1-java
 (Closes: #867247)
 .
   [ Miguel Landaeta ]
   * Remove myself from uploaders. (Closes: #871892)
   * Update copyright info.
Checksums-Sha1:
 4fe734bd6e81d5901d07486037d9bf07a8a33418 2923 tomcat8_8.5.21-1.dsc
 33d85a95bb3ebacf0669631a492eafff7b3bed5a 3360132 tomcat8_8.5.21.orig.tar.xz
 1f677e572fe2c23ec79c794086ac422e0a85493e 42080 tomcat8_8.5.21-1.debian.tar.xz
 5058c14c3bf9cc1695c59f113d068cc99ab0f7f9 10321 
tomcat8_8.5.21-1_source.buildinfo
Checksums-Sha256:
 d78919b3f69db9fb24f2c502bf8f53298eeed8541dd03e281e734d0628486174 2923 

Bug#876257: marked as done (libwebkit2gtk-4.0-37: blocks upgrade path for libgstreamer-plugins-bad1.0-0 1.12.3)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 11:09:28 +0200
with message-id 
and subject line Re: libwebkit2gtk-4.0-37: blocks upgrade path for 
libgstreamer-plugins-bad1.0-0 1.12.3
has caused the Debian Bug report #876257,
regarding libwebkit2gtk-4.0-37: blocks upgrade path for 
libgstreamer-plugins-bad1.0-0 1.12.3
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.)


-- 
876257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwebkit2gtk-4.0-37
Version: 2.18.0-2
Severity: important

Dear Maintainer,

it looks like libwebkit2gtk-4.0-37 is blocking the upgrade path for
libgstreamer-plugins-bad1.0-0 1.12.3, looking at the package
dependencies I spotted these constraints:

libgstreamer-plugins-bad1.0-0 (>= 1.12.2), libgstreamer-plugins-bad1.0-0 (<< 
1.12.3)

which explain the issue.

However I am not sure about why both constraints are there.

Thanks,
   Antonio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), 
LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwebkit2gtk-4.0-37 depends on:
ii  libatk1.0-0 2.26.0-2
ii  libc6   2.24-17
ii  libcairo2   1.14.10-1
ii  libegl1 0.2.999+git20170802-4
ii  libenchant1c2a  1.6.0-11+b2
ii  libfontconfig1  2.12.3-0.2
ii  libfreetype62.8-0.2
ii  libgcc1 1:7.2.0-5
ii  libgcrypt20 1.7.9-1
ii  libgdk-pixbuf2.0-0  2.36.10-1
ii  libgl1  0.2.999+git20170802-4
ii  libglib2.0-02.54.0-1
ii  libgstreamer-plugins-bad1.0-0   1.12.2-1+b1
ii  libgstreamer-plugins-base1.0-0  1.12.3-1
ii  libgstreamer1.0-0   1.12.3-1
ii  libgtk-3-0  3.22.21-1
ii  libharfbuzz-icu01.4.2-1
ii  libharfbuzz0b   1.4.2-1
ii  libhyphen0  2.8.8-5
ii  libicu5757.1-6
ii  libjavascriptcoregtk-4.0-18 2.18.0-2
ii  libjpeg62-turbo 1:1.5.2-2
ii  libnotify4  0.7.7-2
ii  libpango-1.0-0  1.40.12-1
ii  libpng16-16 1.6.32-1
ii  libsecret-1-0   0.18.5-3.1
ii  libsoup2.4-12.60.0-1
ii  libsqlite3-03.20.1-1
ii  libstdc++6  7.2.0-5
ii  libtasn1-6  4.12-2.1
ii  libwayland-client0  1.14.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  17.2.1-1
ii  libwayland-server0  1.14.0-1
ii  libwebp60.6.0-3
ii  libx11-62:1.6.4-3
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-3
ii  libxml2 2.9.4+dfsg1-4
ii  libxslt1.1  1.1.29-2.1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages libwebkit2gtk-4.0-37 recommends:
ii  gstreamer1.0-plugins-base  1.12.3-1
ii  gstreamer1.0-plugins-good  1.12.3-1
ii  libgl1-mesa-dri17.2.1-1

Versions of packages libwebkit2gtk-4.0-37 suggests:
ii  libwebkit2gtk-4.0-37-gtk2  2.18.0-2

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
--- End Message ---
--- Begin Message ---

Hi!

On Wed, 20 Sep 2017 10:53:07 +0200 Antonio Ospite  wrote:

Package: libwebkit2gtk-4.0-37
Version: 2.18.0-2
Severity: important

Dear Maintainer,

it looks like libwebkit2gtk-4.0-37 is blocking the upgrade path for
libgstreamer-plugins-bad1.0-0 1.12.3, looking at the package
dependencies I spotted these constraints:

libgstreamer-plugins-bad1.0-0 (>= 1.12.2), libgstreamer-plugins-bad1.0-0 (<< 
1.12.3)

Bug#872672: marked as done (gcc-7: packages are *huuuge*)

[Debian Bug Tracking System]

MP) support library (n32)
 libn32gomp1-dbg - GCC OpenMP (GOMP) support library (n32 debug symbols)
 libn32objc-7-dev - Runtime library for GNU Objective-C applications (n32 
development
 libn32objc4 - Runtime library for GNU Objective-C applications (n32)
 libn32objc4-dbg - Runtime library for GNU Objective-C applications (n32 debug 
symbo
 libn32stdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libn32stdc++6 - GNU Standard C++ Library v3 (n32)
 libn32stdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libobjc-7-dev - Runtime library for GNU Objective-C applications (development 
fil
 libobjc4   - Runtime library for GNU Objective-C applications
 libobjc4-dbg - Runtime library for GNU Objective-C applications (debug symbols)
 libquadmath0 - GCC Quad-Precision Math Library
 libquadmath0-dbg - GCC Quad-Precision Math Library (debug symbols)
 libstdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libstdc++-7-doc - GNU Standard C++ Library v3 (documentation files)
 libstdc++-7-pic - GNU Standard C++ Library v3 (shared library subset kit)
 libstdc++6 - GNU Standard C++ Library v3
 libstdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libtsan0   - ThreadSanitizer -- a Valgrind-based detector of data races (runti
 libtsan0-dbg - ThreadSanitizer -- a Valgrind-based detector of data races 
(debug
 libubsan0  - UBSan -- undefined behaviour sanitizer (runtime)
 libubsan0-dbg - UBSan -- undefined behaviour sanitizer (debug symbols)
 libx32asan4 - AddressSanitizer -- a fast memory error detector (x32)
 libx32asan4-dbg - AddressSanitizer -- a fast memory error detector (x32 debug 
symbo
 libx32atomic1 - support library providing __atomic built-in functions (x32)
 libx32atomic1-dbg - support library providing __atomic built-in functions (x32 
debug
 libx32cilkrts5 - Intel Cilk Plus language extensions (x32)
 libx32cilkrts5-dbg - Intel Cilk Plus language extensions (x32 debug symbols)
 libx32gcc-7-dev - GCC support library (x32 development files)
 libx32gcc1 - GCC support library (x32)
 libx32gcc1-dbg - GCC support library (debug symbols)
 libx32gfortran-7-dev - Runtime library for GNU Fortran applications (x32 
development fil
 libx32gfortran4 - Runtime library for GNU Fortran applications (x32)
 libx32gfortran4-dbg - Runtime library for GNU Fortran applications (x32 debug 
symbols)
 libx32go11 - Runtime library for GNU Go applications (x32)
 libx32go11-dbg - Runtime library for GNU Go applications (x32 debug symbols)
 libx32gomp1 - GCC OpenMP (GOMP) support library (x32)
 libx32gomp1-dbg - GCC OpenMP (GOMP) support library (x32 debug symbols)
 libx32gphobos-7-dev - Phobos D standard library (x32 development files)
 libx32gphobos71 - Phobos D standard library (runtime library)
 libx32gphobos71-dbg - Phobos D standard library (debug symbols)
 libx32itm1 - GNU Transactional Memory Library (x32)
 libx32itm1-dbg - GNU Transactional Memory Library (x32 debug symbols)
 libx32lsan0 - LeakSanitizer -- a memory leak detector (x32)
 libx32lsan0-dbg - LeakSanitizer -- a memory leak detector (x32 debug symbols)
 libx32objc-7-dev - Runtime library for GNU Objective-C applications (x32 
development
 libx32objc4 - Runtime library for GNU Objective-C applications (x32)
 libx32objc4-dbg - Runtime library for GNU Objective-C applications (x32 debug 
symbo
 libx32quadmath0 - GCC Quad-Precision Math Library (x32)
 libx32quadmath0-dbg - GCC Quad-Precision Math Library (x32 debug symbols)
 libx32stdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libx32stdc++6 - GNU Standard C++ Library v3 (x32)
 libx32stdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libx32ubsan0 - UBSan -- undefined behaviour sanitizer (x32)
 libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols)
Closes: 872672 876246
Changes:
 gcc-7 (7.2.0-6) unstable; urgency=medium
 .
   * Update to SVN 20170920 (r253002) from the gcc-7-branch.
 - Fix PR target/82112 (PPC), PR c++/81355, PR tree-optimization/82084,
   PR tree-optimization/82108, PR target/81325 (PPC), PR c++/81236,
   PR c++/80767, PR c++/82030, PR c++/80935, PR c++/81671, PR c++/81525,
   PR c++/81314, PR libgfortran/78387.
   * Fix fortran cross compiler build with debhelper 10.9. Closes: #876246.
   * Strip the compiler binaries again. Closes: #872672.
   * Bump binutils dependency to 2.29.1 for sid/buster.
Checksums-Sha1:
 b6ef89e31d0c3236ae9368fcf1cf0a31d1f19c5f 26322 gcc-7_7.2.0-6.dsc
 41d3cd873d099e5ecfe9e12dbb980401b1bd8494 3061771 gcc-7_7.2.0-6.diff.gz
 08c0939fbef4a040d9798b2291557c0c32f987ac 9774 gcc-7_7.2.0-6_source.buildinfo
Checksums-Sha256:
 7a51f944ad88447d1c1f76b3e60427b418296b7c686e81cd2945e9d3048cf260 26322 
gcc-7_7.2.0-6.dsc
 c5c5155c5661b5b3440a31a9000c9b564cea70adab47b9f838bdf38b0e642da0 3061771 
gcc-7_7.2.0-6.diff.gz
 27ea9dd6c094259d58d122be8324297fa2d8c5529ce5e3e31b926af4f1044fb8 9774 
gcc-7_7.2.0-6_source.buildinfo
Files:
 79915c6fb80c2cc335c0a2e189aa5989 26322 devel op

Bug#490657: marked as done (gpm: new upstream stable version 1.20.5)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 11:50:21 +0200
with message-id <20170920095021.ga22...@sym.noone.org>
and subject line Re: Bug#490657: gpm: new upstream stable version 1.20.5
has caused the Debian Bug report #490657,
regarding gpm: new upstream stable version 1.20.5
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.)


-- 
490657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpm
Version: 1.20.4-2
Severity: wishlist

We're getting closer to the final freeze for lenny, so this is the
time for final changes. Is there any chance to package the latest 
stable release for 1.x branch (1.20.5)?

If there is no big trouble please fix some of the recommendations from
lintian [1].

Thanks


[1]  
http://lintian.debian.org/full/pkg-gpm-de...@lists.alioth.debian.org.html#gpm

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gpm depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  debianutils   2.28.4 Miscellaneous utilities specific t
ii  libc6 2.7-10 GNU C Library: Shared libraries
ii  libgpm2   1.20.4-2   General Purpose Mouse - shared lib
ii  lsb-base  3.2-12 Linux Standard Base 3.2 init scrip
ii  ucf   3.007  Update Configuration File: preserv

gpm recommends no packages.

-- debconf information:
* gpm/responsiveness:
* gpm/repeat_type: none
* gpm/append:
  gpm/restart: false
* gpm/sample_rate:
* gpm/type: exps2
* gpm/device: /dev/input/mice


--- End Message ---
--- Begin Message ---
Version: 1.20.7-1

Teodor wrote:
> We're getting closer to the final freeze for lenny, so this is the
> time for final changes. Is there any chance to package the latest
> stable release for 1.x branch (1.20.5)?

Well, we didn't get it into Lenny, but we will likely get it into
Buster.

I've adopted the package together with Samuel Thibault and uploaded
1.20.7-1 a few weeks ago to Debian Experimental. (But missed this bug
report, hence the manual closing.)

Here's the full changelog entry from that upload:

gpm (1.20.7-1) experimental; urgency=low

  [ Samuel Thibault ]
  * Adopt package (Closes: Bug#852224)
  * control: Update maintainer mailing list.

  [ Axel Beckert ]
  * Adding myself as Maintainer. (c.f. #852224)
  * Apply wrap-and-sort.
  * Update upstream download URL in debian/copyright. Issue found by
  DUCK.
  * Add not yet cleaned up build artifacts to debian/clean.
  * Switch to source format "3.0 (quilt)" and rewrite debian/rules as dh
v7 style minimal rules file with debhelper compatibility level 10.
+ Bump versioned debhelper build-dependency accordingly.
+ Drop build-dependencies on quilt, autoconf and autotools-dev.
+ Refresh 021_libgpm_dev_gpmctl_debug_msg.patch to remove fuzz.
+ Use dh-exec and executable debian/*.install files instead of
  $(INSTALL_PROGRAM) and $(INSTALL_DATA) in debian/rules.
+ Add patch to fix FTBFS with -Wformat-security.
  * Enable all hardening build flags.
+ Update 014_has_mouse_control.patch to properly pass compile flags.
  * Add patch to fix spelling errors found by lintian.
  * Declare compliance with Debian Policy 4.0.1.
+ Use /run/ instead of /var/run/ in init script.
  * Import stable upstream release 1.20.7. (Closes: #490657)
+ Refresh patches where necessary.
+ Manually extend 050_dont_link_libcurses to make package compile
  again independently of libncurses5-dev being installed or not.
+ Drop 020_daemon_quit_noverbose.patch,
  021_libgpm_dev_gpmctl_debug_msg.patch,
  022_libgpm_no_log_debug_msg.patch, 030_fd_set_negative_int.patch and
  040_no_OPEN_MAX.patch, applied upstream.
+ Update debian/libgpm2.install wrt. to minor SONAME version.
+ No more symlink config.{sub,guess}, call ./autogen.sh instead.
  * Add DEP-3 headers to all patches.
  * Add an initial symbols file.

  [ Peter Eisentraut ]
  * Add init.d status support. (Closes: #525677)

 -- Axel Beckert   Sun, 13 Aug 2017 05:11:33 +0200

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 

Bug#838386: marked as done (network-manager-strongswan: Configuration menus aren't showing on network-manager UIs)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 12:08:47 +0200
with message-id <99a5336c-5fbf-88f4-462e-8a50b5c63...@afaics.de>
and subject line Re: network-manager-strongswan: Configuration menus aren't 
showing on network-manager UIs
has caused the Debian Bug report #838386,
regarding network-manager-strongswan: Configuration menus aren't showing on 
network-manager UIs
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.)


-- 
838386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-strongswan
Version: 1.3.1-2
Severity: important
Justification: As far as I can tell, no UI works to edit or create new 
connections

Howdy!

I'm having trouble using the UI. It broke sometime after an apt-get
upgrade, where it may have upgraded any of GNOME or the strongswan
plugin.

Here's some UIs I tried:

First I tried to edit the existing connection that I have, which failed
saying "Error: unable to load VPN connection editor".

http://imgur.com/r898hia.png

So, next I tried to re-create that VPN connection by clicking on "Add
VPN". The UI doesn't show an option for strongswan

http://imgur.com/EH7oJwI.png

So, I tried to go back and add it using nm-connection-editor, wondering
if the old UI could work, but it was also not showing up there either

http://imgur.com/eAumwwV.png

Although, running `nm-connection-editor` in my bash shell did give me
some interesting output:

| [paultag@cassiel:~][⌚ 02:55 PM] ♥  nm-connection-editor 
| ** Message: vpn: 
(strongswan,/etc/NetworkManager/VPN/nm-strongswan-service.name) cannot load 
legacy-only plugin

Happy to test and fiddle as needed!
  Paul


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager-strongswan depends on:
ii  gconf-service3.2.6-3
ii  libart-2.0-2 2.3.21-2
ii  libatk1.0-0  2.21.90-2
ii  libbonobo2-0 2.32.1-3
ii  libbonoboui2-0   2.24.5-3
ii  libc62.23-5
ii  libcairo21.14.6-1+b1
ii  libdbus-1-3  1.10.10-1
ii  libdbus-glib-1-2 0.108-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgconf-2-4 3.2.6-3
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.49.6-1
ii  libgnome-2-0 2.32.1-5
ii  libgnome-keyring03.12.0-1+b1
ii  libgnomecanvas2-02.30.3-2
ii  libgnomeui-0 2.24.5-3.1
ii  libgnomevfs2-0   1:2.24.4-6.1+b1
ii  libgtk2.0-0  2.24.30-4
ii  libice6  2:1.0.9-1+b1
ii  libnm-glib-vpn1  1.2.4-2
ii  libnm-glib4  1.2.4-2
ii  libnm-util2  1.2.4-2
ii  liborbit-2-0 1:2.14.19-1+b1
ii  libpango-1.0-0   1.40.2-1
ii  libpangocairo-1.0-0  1.40.2-1
ii  libpangoft2-1.0-01.40.2-1
ii  libpopt0 1.16-10
ii  libsm6   2:1.2.2-1+b1
ii  network-manager  1.2.4-2
ii  strongswan-nm5.5.0-1

network-manager-strongswan recommends no packages.

network-manager-strongswan suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Sorry, but I cannot reproduce this problem.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#876225: marked as done (Switch schroot to use overlay fs)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:39:51 +
with message-id <20170920093951.ga27...@layer-acht.org>
and subject line Re: [Qa-jenkins-dev] Bug#876225: Switch schroot to use overlay 
fs
has caused the Debian Bug report #876225,
regarding Switch schroot to use overlay fs
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.)


-- 
876225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jenkins.debian.org
Severity: normal
Tags: patch

Branch for jenkins.debian.net "schroot-overlay" available at:

  
https://anonscm.debian.org/cgit/users/vagrant/jenkins.debian.net.git/log/?h=schroot-overlay

Patch included below for easy reference.

live well,
  vagrant

From e6fde8ffe8a01b594670e8dd1b9a9fd8a08a3f58 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 19 Sep 2017 13:15:19 -0700
Subject: [PATCH] Switch schroot to use overlay fs, as aufs is no longer
 supported out of the box in linux 4.x kernels.

---
 bin/schroot-create.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bin/schroot-create.sh b/bin/schroot-create.sh
index 5418b180..6c8bcb5b 100755
--- a/bin/schroot-create.sh
+++ b/bin/schroot-create.sh
@@ -275,7 +275,7 @@ sudo tee /etc/schroot/chroot.d/jenkins-"$TARGET" <<-__END__
type=directory
root-users=jenkins
source-root-users=jenkins
-   union-type=aufs
+   union-type=overlay
__END__
 
 echo "schroot $TARGET set up successfully in $SCHROOT_BASE/$TARGET - exiting 
now."
-- 
2.11.0



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Tue, Sep 19, 2017 at 01:19:06PM -0700, Vagrant Cascadian wrote:
> Subject: [PATCH] Switch schroot to use overlay fs, as aufs is no longer
>  supported out of the box in linux 4.x kernels.

thanks, merged and deploying now, curious what/if things will break.


-- 
cheers,
Holger


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

Bug#876221: marked as done (log uninitialized stack in non-default configuration [CVE-2017-0380])

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:39:11 +
with message-id 
and subject line tor_0.3.1.7-1_weasel.changes ACCEPTED into unstable
has caused the Debian Bug report #876221,
regarding log uninitialized stack in non-default configuration [CVE-2017-0380]
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.)


-- 
876221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Severity: serious
Version: 0.2.7.2-alpha-1
Control: forwarded -1 https://bugs.torproject.org/23490

tor could log uninitialized stack when a certain hidden service error occurred
while SafeLogging was disabled.

This is also tracked as TROVE-2017-008 and CVE-2017-0380.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/
--- End Message ---
--- Begin Message ---


pgpoXPOjqudbS.pgp
Description: PGP message
--- End Message ---

Bug#876239: marked as done (reproducible: re-deploy cbxi4a (disk failure))

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 09:44:17 +
with message-id <20170920094417.gb27...@layer-acht.org>
and subject line Re: [Qa-jenkins-dev] Bug#876239: reproducible: re-deploy 
cbxi4a (disk failure)
has caused the Debian Bug report #876239,
regarding reproducible: re-deploy cbxi4a (disk failure)
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.)


-- 
876239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jenkins.debian.org
Severity: normal
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

cbxi4a-armhf-rb.debian.net had a critical disk failure.

It's been reinstalled, so the ssh keys have changed:

256 SHA256:C8nL+YAOEhjWYH2tkeoP00sfiWi4bI2ZlI400idPBqU root@cbxi4a (ECDSA)
256 SHA256:oxxy+996R6nClC9ors/Py20vsJEjN2HrGgzvhsSwKfw root@cbxi4a (ED25519)
2048 SHA256:EDUXTiDwa7/W2WAooNdHJNTJJd+GJZypCsqcJ7axLEM root@cbxi4a (RSA)

hostname, ip address, ssh port should all be the same, and it hasn't
been removed from jenkins git... so everything just needs to be
re-deployed on the new install.


live well,
  vagrant


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Tue, Sep 19, 2017 at 05:38:35PM -0700, Vagrant Cascadian wrote:
> It's been reinstalled, so the ssh keys have changed:
> 256 SHA256:C8nL+YAOEhjWYH2tkeoP00sfiWi4bI2ZlI400idPBqU root@cbxi4a (ECDSA)

readded, thanks.


-- 
cheers,
Holger


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

Bug#876003: marked as done (lintian: Wrong description of tag unknown-testsuite)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:48 +
with message-id 
and subject line Bug#876003: fixed in lintian 2.5.53
has caused the Debian Bug report #876003,
regarding lintian: Wrong description of tag unknown-testsuite
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.)


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

Package: lintian
Version: 2.5.52
Severity: normal

Dear Maintainer,

Please, change the description of tag unknown-testsuite.  It contains now:

  The dsc file sets Testsuite to a value other than autopkgtest, the
  only one allowed. This field is most probably copied by dpkg-source
  from Testsuite in debian/control.

but autopkgtest is not the only value allowed.

Best,

Rafael

-- System Information:

Debian Release: 9.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (550, 
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.28-5
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1
ii  dpkg  1.18.22
ii  file  1:5.29-3
ii  gettext   0.19.8.1-2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.22
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-1
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-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.18.22
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 876...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
   

Bug#875985: marked as done (lintian: Allow Testsuite: autopkgtest-pkg-octave)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:48 +
with message-id 
and subject line Bug#875985: fixed in lintian 2.5.53
has caused the Debian Bug report #875985,
regarding lintian: Allow Testsuite: autopkgtest-pkg-octave
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.)


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

Package: lintian
Version: 2.5.52
Severity: normal

Dear Maintainer,

Version 0.10 of autodep8 has support for Octave packages.  Please, add 
autopkgtest-pkg-octave to the list of known test suites.


Also, please change the description of tag unknown-testsuite.  It 
contains now:


   The dsc file sets Testsuite to a value other than autopkgtest, the
   only one allowed. This field is most probably copied by dpkg-source
   from Testsuite in debian/control.

but autopkgtest is not the only value allowed.

Thanks,

Rafael Laboissière

-- System Information: 
Debian Release: 9.0 
 APT prefers testing 
 APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (550, 'stable'), (500, 'oldstable') 
Architecture: amd64 (x86_64) 
Foreign Architectures: i386


Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on: 
ii  binutils  2.28-5 
ii  bzip2 1.0.6-8.1 
ii  diffstat  1.61-1 
ii  dpkg  1.18.22 
ii  file  1:5.29-3 
ii  gettext   0.19.8.1-2 
ii  intltool-debian   0.35.0+20060710.4 
ii  libapt-pkg-perl   0.1.33 
ii  libarchive-zip-perl   1.59-1 
ii  libclass-accessor-perl0.34-1 
ii  libclone-perl 0.38-2+b2 
ii  libdpkg-perl  1.18.22 
ii  libemail-valid-perl   1.202-1 
ii  libfile-basedir-perl  0.07-1 
ii  libipc-run-perl   0.94-1 
ii  liblist-moreutils-perl0.416-1+b3 
ii  libparse-debianchangelog-perl 1.2.0-12 
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-1 
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5 
ii  libtext-levenshtein-perl  0.13-1 
ii  libtimedate-perl  2.3000-2 
ii  liburi-perl   1.71-1 
ii  libxml-simple-perl2.24-1 
ii  libyaml-libyaml-perl  0.63-2+b2 
ii  man-db2.7.6.1-2 
ii  patchutils0.3.4-2 
ii  perl  5.26.0-5 
ii  t1utils   1.40-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.18.22 
ii  libhtml-parser-perl3.72-3+b2 
ii  libtext-template-perl  1.46-1


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 875...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 

Bug#874078: marked as done (lintian: improve binary-file-built-without-LFS-support info field)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#874078: fixed in lintian 2.5.53
has caused the Debian Bug report #874078,
regarding lintian: improve binary-file-built-without-LFS-support info field
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.)


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

Package: lintian
Version: 2.5.52
Severity: normal
Tags: patch lfs

Dear Maintainers,


CONTEXT:

Mpgrafic-0.3.15-1 is flagged with the binary-file-built-without-LFS-support 
lintian

flag despite my attempts to follow the lintian recommendations, after having
searched for LFS info in obvious places:
https://lintian.debian.org/full/debian-astro-maintain...@lists.alioth.debian.org.html#mpgrafic

Discussion at this other lintian bug looks like it will solve the mpgrafic
LFS bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871956


PROBLEM:

Version 2.5.52 of the binary-file-built-without-LFS-support section of
binaries.desc has two problems that make applying LFS support
corrections difficult for someone (such as me) who is not yet familiar
with LFS, AC_SYS_LARGEFILES and their portability:

(i) It says in one sentence that we must "ensure _FILE_OFFSET_BITS is
defined and set to 64", but in the following sentence that
"this can be done by using the AC_SYS_LARGEFILE macro with autoconf".
However, AC_SYS_LARGEFILE does not seem to define _FILE_OFFSET_BITS
on amd64, since it does not seem to be needed.

In other words, these two sentences are contradictory. Either lintian
should request everyone to hardwire everything with _FILE_OFFSET_BITS and
recommend *not* using AC_SYS_LARGEFILE, or it needs to indicate that
_FILE_OFFSET_BITS is not needed on all systems and that AC_SYS_LARGEFILE
can decide on which systems _FILE_OFFSET_BITS is needed.

(ii) I have not been able to find good documentation to give more
hints on functions that may need to be modified, or even better, on
functions that only need to be modified for some architectures
(pwrite, pread in the case of mpgrafic). So a brief comment in the
lintian info field could help improve the probability of people
responding to the warning rather than ignoring it.

I'm setting this as a normal level bug, because the aim of lintian
is not only to warn package maintainers, but also to help them
fix problems.


PATCH:

My proposed updated second paragraph is here:

 To support large files, code review might be needed to make sure that
 those files are not slurped into memory or mmap(2)ed, and that correct
 64-bit data types are used (ex: off_t instead of ssize_t), etc.  Once
 that has been done ensure, if needed, that _FILE_OFFSET_BITS
 is defined and
 set to 64 before the relevant files are included. This can be done
 conditionally by
 using the AC_SYS_LARGEFILE macro with autoconf, or by appending
 the output of getconf LFS_CFLAGS and getconf LFS_LDFLAGS
 to CFLAGS and LDFLAGS respectively. Functions such
 as pwrite and pread should be replaced by pwrite64 and pread64 in
 cases where _FILE_OFFSET_BITS is defined and set to 64.

I'm also attaching it as a patch file.

Cheers
Boud

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)--- checks/binaries.desc.orig	2017-06-17 17:38:57.0 +0200
+++ checks/binaries.desc	2017-09-02 21:57:08.929153000 +0200
@@ -439,11 +439,15 @@
  To support large files, code review might be needed to make sure that
  those files are not slurped into memory or mmap(2)ed, and that correct
  64-bit data types are used (ex: off_t instead of ssize_t), etc.  Once
- that has been done ensure _FILE_OFFSET_BITS is defined and
- set to 64 before the relevant files are included.  This can be done by
+ that has been done ensure, if needed, that _FILE_OFFSET_BITS
+ is defined and
+ set to 64 before the relevant files are included. This can be done
+ conditionally by
  using the AC_SYS_LARGEFILE macro with autoconf, or by appending
  the output of getconf LFS_CFLAGS and getconf LFS_LDFLAGS
- to CFLAGS and LDFLAGS respectively.
+ to CFLAGS and LDFLAGS respectively. Functions such
+ as pwrite and pread should be replaced by pwrite64 and pread64 in
+ cases where _FILE_OFFSET_BITS is defined and set to 64.
  .
  Take into account that even if this tag is not emitted, that does not
  mean the binary is LFS-safe (ie. no OOM conditions, file truncation
--- End Message ---
--- Begin Message ---
Source: lintian

Bug#874381: marked as done (lintian: false-positive source-is-missing bug for css_browser_selector.js)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#874381: fixed in lintian 2.5.53
has caused the Debian Bug report #874381,
regarding lintian: false-positive source-is-missing bug for 
css_browser_selector.js
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.)


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

Hi there,

lintian gives a false-positive source-is-missing for
css_browser_selector.js (though in my case the file has been
renamed).  The upstream source is
https://github.com/rafaelp/css_browser_selector/ and the original
source is just one really long line (plus some informational header
comments).  And it's been manually written as one long line, it seems,
as there are spaces after semicolons...

Best wishes,

   Julian
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 874...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and 

Bug#864102: marked as done (fis-gtm: Please stop Build-Depending on libgcrypt11-dev transition package)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 18:00:12 +
with message-id 
and subject line Bug#864102: fixed in fis-gtm 6.3-002-1
has caused the Debian Bug report #864102,
regarding fis-gtm: Please stop Build-Depending on libgcrypt11-dev transition 
package
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.)


-- 
864102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fis-gtm
Version: 6.3-000A-1
Severity: normal

fis-gtm build-depends on libgcrypt11-dev. This is a transition package,
please use libgcrypt20-dev instead.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Source: fis-gtm
Source-Version: 6.3-002-1

We believe that the bug you reported is fixed in the latest version of
fis-gtm, 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 864...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Amul Shah  (supplier of updated fis-gtm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Aug 2017 11:12:55 -0400
Source: fis-gtm
Binary: fis-gtm fis-gtm-6.3-002
Architecture: source amd64 all
Version: 6.3-002-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Amul Shah 
Description:
 fis-gtm- metapackage for the latest version of FIS-GT.M database
 fis-gtm-6.3-002 - package for FIS-GT.M database
Closes: 864102
Changes:
 fis-gtm (6.3-002-1) unstable; urgency=medium
 .
   * Update to fis-gtm V6.3-002
   * Update Standards to match the most recent 4.1.0
   * Remove dh_strip override as binaries are stripped. Fixes lintian error
 file-contains-fixme-placeholder
   * Build-Depends bumped to libgcrypt20
 Closes: #864102
Checksums-Sha1:
 5bc8fbd3479385628fad2a35c8d0d01413c06350 2391 fis-gtm_6.3-002-1.dsc
 41f9a7bd4323d8f426ece9b985989819e5bdc12a 5737524 fis-gtm_6.3-002.orig.tar.gz
 54517ca14ab73d5b70ce3fdb3a12aec0b115c7d5 22928 fis-gtm_6.3-002-1.debian.tar.xz
 dde62062338a618aaa2dff928f735989d0dd1228 85605514 
fis-gtm-6.3-002-dbgsym_6.3-002-1_amd64.deb
 529e99b7cb3caaebb1bbcd68b5fc728b4fafdbe8 9190694 
fis-gtm-6.3-002_6.3-002-1_amd64.deb
 a79e7b58b0de4a17335c77df77272f9ff37359cf 20914 fis-gtm_6.3-002-1_all.deb
 21f9632a9d22c8d1e4c8cde98deade8533005ddb 8688 fis-gtm_6.3-002-1_amd64.buildinfo
Checksums-Sha256:
 6e0c8f3ae28c37568288e37e4f28960558f81d0d4a57318c2d4736031071f182 2391 
fis-gtm_6.3-002-1.dsc
 ddae4ef0c4efbac42ba5fdc45fca6605c6beb1e4c1bb1099a1fcfe2287616a46 5737524 
fis-gtm_6.3-002.orig.tar.gz
 326eef8622db047f2286afe6c85855bf9ed9fc25fc61a8747331af54c780bfed 22928 
fis-gtm_6.3-002-1.debian.tar.xz
 07e2ff52de3b6e44c576bd0de074675cbd9f1322b2717ae9c437c8c0612fd8b6 85605514 
fis-gtm-6.3-002-dbgsym_6.3-002-1_amd64.deb
 fe9cde8a09a6fef196156c9b5f5734201e75f0f409eb5a218d75df68c23278c1 9190694 
fis-gtm-6.3-002_6.3-002-1_amd64.deb
 c911a80697be9ad71abf801ec228da0b0fcabf5cedad8e6491131351b0b12750 20914 
fis-gtm_6.3-002-1_all.deb
 b4af383539ff2e866bd6ec9545f7758caecbcaff4faf1a53889a26fe0f036088 8688 
fis-gtm_6.3-002-1_amd64.buildinfo
Files:
 188c881841ab85f09b2d23dfa9c41d3c 2391 database optional fis-gtm_6.3-002-1.dsc
 7ed5c28ed1957bdb20940c7744fbb64a 5737524 database optional 
fis-gtm_6.3-002.orig.tar.gz
 367cc117586407c8d1d6782ae0b0bdd8 22928 database optional 
fis-gtm_6.3-002-1.debian.tar.xz
 a0d449615cf019354f708c058bfdc54a 85605514 debug optional 
fis-gtm-6.3-002-dbgsym_6.3-002-1_amd64.deb
 d96594dcf980895aa04f2f91a7282e44 9190694 database optional 
fis-gtm-6.3-002_6.3-002-1_amd64.deb
 748db6dbc8400a157f48d692110abbee 20914 database optional 
fis-gtm_6.3-002-1_all.deb
 163101f0cd20021f6425b4c7f6e5914b 8688 database optional 
fis-gtm_6.3-002-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZtobvAAoJEFeKBJTRxkbRDKIP/2Rab/wUi+JV2s+L0wVLJzn4

Bug#874383: marked as done (torbrowser-launcher: AppArmor failures)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 15:26:20 +
with message-id 
and subject line Bug#874383: fixed in torbrowser-launcher 0.2.8-2
has caused the Debian Bug report #874383,
regarding torbrowser-launcher: AppArmor failures
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.)


-- 
874383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.2.8-1
Severity: important
User: pkg-apparmor-t...@lists.alioth.debian.org 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

0.2.8-1 changes the AppArmor profile to include:

+  # Required for multiprocess Firefox (aka Electrolysis, i.e. e10s)
+  owner /dev/shm/org.chromium.* rw,

in /etc/apparmor.d/torbrowser.Browser.firefox.


This doesn't seem to be enough, the syslog is full of:

Sep  5 18:21:18 jadzia kernel: [848718.105570] audit: type=1400 
audit(1504628478.309:7268): apparmor="DENIED" operation="mknod" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 name="/run/shm/org.chromium.Ob3qhH" pid=19088 comm=57656220436F6E74656E74 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
Sep  5 18:21:18 jadzia kernel: [848718.105724] audit: type=1400 
audit(1504628478.310:7269): apparmor="DENIED" operation="mknod" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 name="/run/shm/org.chromium.LvK8f0" pid=19088 comm=57656220436F6E74656E74 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
Sep  5 18:21:18 jadzia kernel: [848718.105884] audit: type=1400 
audit(1504628478.310:7270): apparmor="DENIED" operation="mknod" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 name="/run/shm/org.chromium.bchSej" pid=19088 comm=57656220436F6E74656E74 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
Sep  5 18:21:20 jadzia kernel: [848720.361627] audit: type=1400 
audit(1504628480.565:7271): apparmor="DENIED" operation="mknod" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 name="/run/shm/org.chromium.MaBrQI" pid=19088 comm=57656220436F6E74656E74 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
Sep  5 18:21:20 jadzia kernel: [848720.361713] audit: type=1400 
audit(1504628480.566:7272): apparmor="DENIED" operation="mknod" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 name="/run/shm/org.chromium.7Jb2r8" pid=19088 comm=57656220436F6E74656E74 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
Sep  5 18:21:20 jadzia kernel: [848720.361769] audit: type=1400 
audit(1504628480.566:7273): apparmor="DENIED" operation="mknod" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 name="/run/shm/org.chromium.YQpD3x" pid=19088 comm=57656220436F6E74656E74 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

and loading any page just hangs.


Cheers,
gregor

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

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates  20170717
ii  gnupg2.1.23-2
ii  python   2.7.13-2
ii  python-gtk2  2.24.0-5.1
ii  python-lzma  0.5.3-3
ii  python-parsley   1.2-1
ii  python-psutil5.0.1-1+b1
ii  python-twisted   17.5.0-2
ii  python-txsocksx  1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.0.10-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor   2.11.0-10
ii  python-pygame  1.9.3+dfsg-2+b1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlmu0EdfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZpfA//Z1RbMmzli4uSM50q74VFOq5mmzs1UeG8wawIKQ1Eu0IFU/xf3aW134oq
Qm2BSmOXakHWNRDkKek+uTK9XjPzCH3LraCLrwd0faRLsJl3jwoqzwbLQ87ecn+8
d8F2icBI/rDE9cqsuKU6LhDQ/5Q8qKawkGsl+tptS56604ezGz+BR3xPKiXdriMd
g/c2s6gntrJ5YmzZaDrzi5siBy58Y2jfAxvLT0Kw17o8u7Yv1xVbMDqTM9n595rY

Bug#742777: marked as done (grisbi: qif export - wrong amount format (french while should be english in all cases))

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:49:30 +
with message-id 
and subject line Bug#742777: fixed in grisbi 1.0.2-2
has caused the Debian Bug report #742777,
regarding grisbi: qif export - wrong amount format (french while should be 
english in all cases)
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.)


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

Dear Maintainer,

I wanted to move back to gnucash and thus though export from grisbi via
qif is the best option.


Though I faced a localization issue : namely the amount are exported
with a french locale which conflict with what is expected by the
software that import the qif (here gnucash).
That is should be :
comma could be used to separate thousands and dot is the decimal
separtor.
while grisbi does:
comma as decimal separator and space as thousands separator.


I made use of sed and all is fine with the abovementionned fixes.
I cannot tell if grisbi 1.0.0 still suffer this issue (will try asap
though it is medium priority only now that I manage to import the fixes
qif into gnucash).

the sed scripts :
- thousands separator (here removal)
sed -ie 's/\(T[^ ]*\) /\1/' *.qif
- the decimal separator :
 sed -ie 's/\(T[^,]*\),/\1./' *.qif


NB: it also could be that grisbi export with the current used locale
(which here is fr_FR.UTF-8

Best regards
Alban


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

Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages grisbi depends on:
ii  grisbi-common   0.8.9-1
ii  libatk1.0-0 2.11.90-1
ii  libc6   2.18-4
ii  libcairo2   1.12.16-2
ii  libfontconfig1  2.11.0-5
ii  libfreetype62.5.2-1
ii  libgdk-pixbuf2.0-0  2.30.6-1
ii  libglib2.0-02.39.92-2
ii  libgtk2.0-0 2.24.22-1
ii  libofx4 1:0.9.4-2.1
ii  libpango1.0-0   1.36.3-1
ii  libssl1.0.0 1.0.2~beta1-1
ii  libxml2 2.9.1+dfsg1-3
ii  xdg-utils   1.1.0~rc1+git20111210-7
ii  zlib1g  1:1.2.8.dfsg-1

grisbi recommends no packages.

Versions of packages grisbi suggests:
ii  chromium [www-browser]  33.0.1750.152-1
ii  elinks [www-browser]0.12~pre6-4
ii  epiphany-browser [www-browser]  3.10.1-1
ii  google-chrome-stable [www-browser]  33.0.1750.152-1
ii  iceweasel [www-browser] 27.0.1-1
ii  konqueror [www-browser] 4:4.11.5-2
ii  links2 [www-browser]2.8-1+b1
ii  lynx-cur [www-browser]  2.8.8pre5-1
ii  texlive 2013.20140314-1
ii  w3m [www-browser]   0.5.3-15

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: grisbi
Source-Version: 1.0.2-2

We believe that the bug you reported is fixed in the latest version of
grisbi, 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 742...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ludovic Rousseau  (supplier of updated grisbi 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: Wed, 20 Sep 2017 18:09:27 +0200
Source: grisbi
Binary: grisbi grisbi-common
Architecture: source all amd64
Version: 1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Stéphane Glondu 
Changed-By: Ludovic Rousseau 
Description:
 grisbi - personal finance management program
 grisbi-common - shared files for the finance management program Grisbi
Closes: 742777
Changes:
 grisbi (1.0.2-2) unstable; urgency=medium
 .
   * Fix "qif export - wrong amount format (french while should be
 english in all cases)" Use patch from upstream (Closes: #742777)
Checksums-Sha1:
 580db67617bc4f6ce1588962d4775059672535ae 2113 

Bug#875540: marked as done (ejabberd: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 18:04:48 +
with message-id 
and subject line Bug#875540: fixed in ejabberd 17.08-2
has caused the Debian Bug report #875540,
regarding ejabberd: [INTL:pt_BR] Brazilian Portuguese debconf templates 
translation
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.)


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

Package: ejabberd
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: ejabberd
Source-Version: 17.08-2

We believe that the bug you reported is fixed in the latest version of
ejabberd, 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 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Huebner  (supplier of updated ejabberd 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: SHA512

Format: 1.8
Date: Wed, 20 Sep 2017 19:45:22 +0200
Source: ejabberd
Binary: ejabberd
Architecture: source amd64
Version: 17.08-2
Distribution: unstable
Urgency: high
Maintainer: Ejabberd Packaging Team 
Changed-By: Philipp Huebner 
Description:
 ejabberd   - distributed, fault-tolerant Jabber/XMPP server
Closes: 875540 875814
Changes:
 ejabberd (17.08-2) unstable; urgency=high
 .
   [ Neil Castelino ]
   * Fix mixed indentation
   * Do not force existing users to change their configuration
 .
   [ Philipp Huebner ]
   * Update pt_BR.po (Closes: #875540)
   * Update de.po (Closes: #875814)
Checksums-Sha1:
 73cfaa19c2926c30c21913a6c22d509eefdcefb0 2745 ejabberd_17.08-2.dsc
 b861f79da32ed7c938db5160739d7f2263a0a5cd 62056 ejabberd_17.08-2.debian.tar.xz
 a33e57a388682aac1ebd9183f8a187b0b199e42b 10030 ejabberd_17.08-2_amd64.buildinfo
 3fdee1f4a8cea2fb513d03cb427e99130f2136f0 5440512 ejabberd_17.08-2_amd64.deb
Checksums-Sha256:
 1bd398dddf0a0f6d2305691ec2bef0d7249870e6ea0a353c966301e8638b6594 2745 
ejabberd_17.08-2.dsc
 104bf6edf4525b3345fbf10d6e89612536e185b1439eb7017ea4224f7d80fea5 62056 
ejabberd_17.08-2.debian.tar.xz
 fc01add24f27c8edccbeb59361c7df62c9511988099f31a8b35461806e39cfdf 10030 
ejabberd_17.08-2_amd64.buildinfo
 23aeded868672ce54f27e52bbcb8fbe3962724a2f34e5d483d4c7679888bfbbb 5440512 
ejabberd_17.08-2_amd64.deb
Files:
 131bb2f99c6dee615ba1f534e079d75f 2745 net optional ejabberd_17.08-2.dsc
 04c0888e79406ea1ca736c9c5190abf9 62056 net optional 
ejabberd_17.08-2.debian.tar.xz
 49da33325daf32e44b33e22a0f59500c 10030 net optional 
ejabberd_17.08-2_amd64.buildinfo
 9aa488c867aab395cd2229d94e2dcda9 5440512 net optional 
ejabberd_17.08-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEECEGLvkRyDy26xQXsunokltrkDRwFAlnCqpAVHGRlYmFsYW5j
ZUBkZWJpYW4ub3JnAAoJELp6JJba5A0c450P/i4tACJGmkPOWk+pnY5Iyu7BaeW0
V9sFZWKp6xaHGWCuvUHlypViN3wfGiCx/pvRiEK914JCgQw6Ny7VWCId9syGHe7s
2DdeB/sbG+sI/NMKd8pdNwM492iu9jzEISJE/0n+BowutEmDFk+JGJAsL9qZygyS
CNSaKm9ckg7b/mhrVF8ny4PZ8S8DJsAIQD9BO37aPi4VYQeImmAGZscDes/x3D7X
+sxXX7bbqvvV8H89DICwowQD+c2NqFNFSyl39SoC1y0XWzdR8d0bk6Xc8PguqLLo
FfVLHNKT6evkmyuaVMpXBrU5si2SavluasgUUCu8+2r6HHSzs3tzQP5ZaqrpPc94
2OsDuZRiqzq4o6RdYoPr96wOPg1b0pbkAptcBAdztHX6uUf0sRZ7NbFjLcKb+nvB
ZTITf2XI825AHdd1zIShLWScpDlKGvPeYBdMyCJRabYEqpRZ0oJ3F/dUH+tycZFy
8Omr89wB7fhCJ9010EammxvXhw3jbBkZ3x+ULcxHSjw4hBIgmTQez0ao7Y7k/J3h
OvqWCuZ9dO2YSPdo4eXaQGCDVyuqSh36f3wdrg1KMrSpa7TAPkprAIcrr/x/R6wz
t8y4U1t/EL3Y2XZxFcJBUw3ToRH43McvQrOn4CrBfkxfpNwactSx1GAeaCGkyklc
3B+SibC2LzUU0iwU
=+Jg6
-END PGP SIGNATURE End Message ---

Bug#869010: marked as done (cglib: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 19:10:40 +0100
with message-id <20170920181040.ga19...@alice.nomadium.lan>
and subject line Re: cglib: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
has caused the Debian Bug report #869010,
regarding cglib: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
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.)


-- 
869010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cglib
Version: 3.2.5-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibcglib-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for cglib:cglib-nodep:jar:3.2.5
> [WARNING] 'build.plugins.plugin.version' for 
> org.sonatype.plugins:jarjar-maven-plugin is missing. @ line 27, column 12
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because 
> they threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer 
> support building such malformed projects.
> [WARNING] 
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Code Generation Library
> [INFO] cglib
> [INFO] cglib-nodep
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-install-plugin:jar:2.5.2 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-install-plugin:2.5.2: Plugin 
> org.apache.maven.plugins:maven-install-plugin:2.5.2 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-install-plugin:jar:2.5.2 has not been 
> downloaded from it before.
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
> org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
> from it before.
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency 
> information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> 

Bug#875814: marked as done (ejabberd: [INTL:de] updated German debconf translation)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 18:04:48 +
with message-id 
and subject line Bug#875814: fixed in ejabberd 17.08-2
has caused the Debian Bug report #875814,
regarding ejabberd: [INTL:de] updated German debconf translation
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.)


-- 
875814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ejabberd
Version: 17.07-2
Severity: wishlist
Tags: patch l10n

Please find the updated German debconf translation for ejabberd
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# translation of po-debconf template to German
# Copyright (C) 2006 Matthias Julius 
# Copyright (C) 2008,2015,2017 Helge Kreutzmann 
# Copyright (C) 2015 Philipp Huebner 
# Copyright (C) 2015 Torsten Werner 
# This file is distributed under the same license as the ejabberd package.
#
msgid ""
msgstr ""
"Project-Id-Version: ejabberd 15.03-2\n"
"Report-Msgid-Bugs-To: ejabb...@packages.debian.org\n"
"POT-Creation-Date: 2017-08-27 23:58-0400\n"
"PO-Revision-Date: 2017-09-14 20:25+0200\n"
"Last-Translator: Torsten Werner \n"
"Language-Team: de \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: string
#. Description
#: ../templates:2001
msgid "Hostname for this Jabber server:"
msgstr "Rechnername für diesen Jabber-Server:"

#. Type: string
#. Description
#: ../templates:2001
msgid "Please enter a hostname for this Jabber server."
msgstr "Geben Sie bitte den Rechnernamen dieses Jabber-Servers an."

#. Type: string
#. Description
#: ../templates:2001
msgid ""
"If you would like to configure multiple hostnames for this server, you will "
"have to do so manually in /etc/ejabberd/ejabberd.yml after installation."
msgstr ""
"Falls Sie mehrere Rechnernamen für diesen Server konfigurieren möchten, "
"müssen Sie dies nach der Installation manuell in /etc/ejabberd/ejabberd.yml "
"vornehmen."

#. Type: string
#. Description
#: ../templates:3001
msgid "Jabber server administrator username:"
msgstr "Benutzername des Jabber-Server-Administrators:"

#. Type: string
#. Description
#: ../templates:3001
msgid ""
"Please provide the name of an account to administrate the ejabberd server. "
"After the installation of ejabberd, you can log in to this account using "
"either any Jabber client or a web browser pointed at the administrative "
"https://${hostname}:5280/admin/ interface."
msgstr ""
"Geben Sie bitte den Namen für ein Konto an, das den Ejabberd-Server "
"verwalten kann. Nach der Installation können Sie sich an diesem Konto mittels "
"eines beliebigen Jabber-Clients oider mit einem Webbrowser, der auf die "
"administrative Schnittstelle https://${hostname}:5280/admin/ zeigt, anmelden."

#. Type: string
#. Description
#: ../templates:3001
msgid ""
"You only need to enter the username part here (such as ${user}), but the "
"full Jabber ID (such as ${user}@${hostname}) is required to access the "
"ejabberd web interface."
msgstr ""
"Sie müssen hier nur den Benutzernamen-Anteil (z.B. ${user}) eingeben, "
"verwenden Sie aber die komplette Jabber-ID (z.B. ${user}@${hostname}), um "
"sich an der Ejabberd-Webschnittstelle anzumelden."

#. Type: string
#. Description
#: ../templates:3001
msgid ""
"Please leave this field empty if you don't want to create an administrator "
"account automatically."
msgstr ""
"Bitte lassen Sie dieses Feld leer, falls Sie kein privilegiertes Konto "
"automatisch anlegen möchten."

#. Type: password
#. Description
#: ../templates:4001
msgid "Jabber server administrator password:"
msgstr "Passwort des Jabber-Server-Administrators:"

#. Type: password
#. Description
#: ../templates:4001
msgid "Please enter the password for the administrative user."
msgstr "Geben Sie das Passwort für den Administrator an."

#. Type: password
#. Description
#: ../templates:5001
msgid "Re-enter password to verify:"
msgstr "Zur Kontrolle Passwort erneut eingeben:"

#. Type: password
#. Description
#: ../templates:5001
msgid ""
"Please enter the same administrator password again to verify that you have "
"typed it 

Bug#855569: marked as done (dumpasn1: wrong output when reading from file)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 19:07:34 +
with message-id 
and subject line Bug#855569: fixed in dumpasn1 20170309-1
has caused the Debian Bug report #855569,
regarding dumpasn1: wrong output when reading from file
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.)


-- 
855569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dumpasn1
Version: 20150808-3
Severity: normal
Tags: upstream

Dear Maintainer,

dumpasn1 prints a wrong decoding of a single octet octetstring when
reading from file (as opposed to stdin).

Create a simple test file:

$ echo -ne "\x04\x01\x00" > test

dumpasn1 decodes this as:

$ dumpasn1 test
  0   1: OCTET STRING 01

0 warnings, 0 errors.

The expected result is what dumpasn1 gives when reading from stdin:

$ cat test | dumpasn1 -
Warning: Input is non-seekable, some functionality has been disabled.
  0   1: OCTET STRING 00

0 warnings, 0 errors.

(I know this is an upstream bug, not a Debian one, but upstream seems to
just be a university homepage, so I am reporting this here.)

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=et_EE.utf8, LC_CTYPE=et_EE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dumpasn1 depends on:
ii  libc6  2.24-9

dumpasn1 recommends no packages.

dumpasn1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dumpasn1
Source-Version: 20170309-1

We believe that the bug you reported is fixed in the latest version of
dumpasn1, 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 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated dumpasn1 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: Wed, 20 Sep 2017 20:41:48 +0200
Source: dumpasn1
Binary: dumpasn1
Architecture: source
Version: 20170309-1
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Malaterre 
Changed-By: Mathieu Malaterre 
Description:
 dumpasn1   - ASN.1 object dump program
Closes: 855569
Changes:
 dumpasn1 (20170309-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #855569
   * Bump Std-Vers to 4.1.0, no changes needed
Checksums-Sha1:
 89c8af896c459d01ae917924e4c4c3c82d71d4d8 1914 dumpasn1_20170309-1.dsc
 8e955cf6fd0c4dde4e0bb8b7f7f95ef6c69d8cca 62599 dumpasn1_20170309.orig.tar.gz
 026ed57bcafd66a5f2e7e745e63b83ec5c1a38c5 6532 dumpasn1_20170309-1.debian.tar.xz
 f743a13b4db564f940a3405edcdd34ef0b2d10b8 5297 
dumpasn1_20170309-1_source.buildinfo
Checksums-Sha256:
 b09bb25c734a34ce065cedab50edd8bcd2fceff2d93faa2e7b3ccbdb82f2da3e 1914 
dumpasn1_20170309-1.dsc
 3667392d04502c096b0dcde827f33429ed675ec60851f119ef02fa82a3c22335 62599 
dumpasn1_20170309.orig.tar.gz
 beb4ac07a491ce78ffb0780fa6a9012c38b7f9b871030f0d643e5c639dfdfb6a 6532 
dumpasn1_20170309-1.debian.tar.xz
 55171c59f31c2dfc5f3d63b9ca51d4f84218b7797f25782a5a6c11e9e413d902 5297 
dumpasn1_20170309-1_source.buildinfo
Files:
 af3b462353e0e80cd81a593395c69afd 1914 utils optional dumpasn1_20170309-1.dsc
 a7a1215026a9c22e6eb5d9c5e44d1c6e 62599 utils optional 
dumpasn1_20170309.orig.tar.gz
 77a239dc1142fa9456439ee690c06593 6532 utils optional 
dumpasn1_20170309-1.debian.tar.xz
 8291dd7da3601aa6e7ab212371496686 5297 utils optional 
dumpasn1_20170309-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAlnCtrYRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0Wnsw/7Bd0EX4+t0xkODa0rOqgNYT6EJcFPhtar
pN01tPFdUCFOd02Yq4CBT9gW5VbmiQtszldquTFs7GRSF+PMHWetPAoyjvQ5TwME
Mkl6ShrdLuQC4j4ih0D0JyZEIbp67Vtn/zl0Xd0Xyax2dwsit0RN1A8MKO/a3n3F
oWfwNmdugV58JbL+toiVPuDBlLr+WMZxa8ifxSwT9AtJQMq1WSi0TG56mQ/KK6uU

Bug#851308: marked as done ([abi-dumper] New upstream release)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 19:04:34 +
with message-id 
and subject line Bug#851308: fixed in abi-dumper 1.1-1
has caused the Debian Bug report #851308,
regarding [abi-dumper] New upstream release
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.)


-- 
851308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: abi-dumper
Severity: wishlist

I could co maintain this one. I suppose they are some interest to put it on 
debian-qa umbrella

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: abi-dumper
Source-Version: 1.1-1

We believe that the bug you reported is fixed in the latest version of
abi-dumper, 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 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated abi-dumper 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: Wed, 20 Sep 2017 20:45:58 +0200
Source: abi-dumper
Binary: abi-dumper
Architecture: source
Version: 1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Malaterre 
Changed-By: Mathieu Malaterre 
Description:
 abi-dumper - tool to dump ABI of an ELF object containing DWARF debug info
Closes: 851308
Changes:
 abi-dumper (1.1-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #851308
   * Bump Std-Vers to 4.1.0, no changes needed.
Checksums-Sha1:
 5d38b01d3d2fc83c8eba582e5305835266afa2b4 1906 abi-dumper_1.1-1.dsc
 46b3ebf9fbd42d48aa33bde1b5d84638b6893480 49012 abi-dumper_1.1.orig.tar.gz
 c1ba88071a479f068278850683ef9dfed01e6026 2448 abi-dumper_1.1-1.debian.tar.xz
 34751dd715617ef95126f29cfface2d6ad1e1561 5348 abi-dumper_1.1-1_source.buildinfo
Checksums-Sha256:
 843253e3840b4dd1f306f4cd0f27550998b8318d97c7acca6a0f32e262cf0111 1906 
abi-dumper_1.1-1.dsc
 ef63201368e0d76a29d2f7aed98c488f6fb71898126762d65baed1e762988083 49012 
abi-dumper_1.1.orig.tar.gz
 c2e0e264b73b7678f5b6b57fa24d46fece6ed2b63ec8e7b22a17dfbf48c8663d 2448 
abi-dumper_1.1-1.debian.tar.xz
 2478fe609295e955690945456d290813182397dc0e73755d871b74f33813a4a2 5348 
abi-dumper_1.1-1_source.buildinfo
Files:
 47e12235bcdef08dcf3fffc2da2be662 1906 devel optional abi-dumper_1.1-1.dsc
 b4540063202fe7bd1d4fee58b31a2b22 49012 devel optional 
abi-dumper_1.1.orig.tar.gz
 e7d7e6d45a7ef0ba73f924f1cb4785d6 2448 devel optional 
abi-dumper_1.1-1.debian.tar.xz
 39871ae77d146d71e90da6de25a312cc 5348 devel optional 
abi-dumper_1.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAlnCt3kRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0V1KA//XeaY9mtn5r1lg+xUZSjowuImTsQg5UPo
VTJhskXnd8eRctwtJfeeDL38RuY7dY/jChHx3SxG6Tpi2tfZzU7aFs0MOS783fIp
JhS07bkXI6+gnG2XcokedgNali9mDfa8LUlP/FwkmJIbCHXkdN/wm5XB1FEc8QLs
ICSl/3KtdzQN6BjU9U6q1LPpnAp3TUoqpZgEFbi7VC3ldLKJOoypCm5H4lY8fpZu
UQqkMtSzcJtKGOegeXHyDaVYRmp44JN7vL4Y2NcgR1j55TlNvsQFvztLR/g7JkXA
QF3LrobolGvGPGmalpdThxzK+qqJRU+eALKDvssx9JZ33/3ds6I5pwjH5zXQOVM9
SOlYC4vV4dZQsVclqfsad6M3I3p+GHICSQIu3W2fAsx05IWe52muJZdk/pyBVWSc
xtA03WbN+q3D0N+Mu/G8YcPlwh8kRrzG1Uq7d6dqAo6cRixVRUDVKkY15ajISTlm
n2QVCOyyHlaBXuH7BPxxJu35CF5zwVU7GHtE1ocXIS0CVdBDmvK1o7GW6a8wzDKt
QrPI6Nt41YNbQfY9CwY5ON5N4qUCx6naU5A+rBfisPVzPtjuNgzI4nraSjfnxgAY
Ya/rbgLIXYZthuzM4fmAnyFwZ5K2MXd59ndQU8jKLSmIPCjlafQuxHKCgKOYqADJ
hpl7FqCds20=
=Jq3c
-END PGP SIGNATURE End Message ---

Bug#876269: marked as done (ftbfs, building indep packages)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 18:30:37 +0100
with message-id <20170920173037.ga19...@alice.nomadium.lan>
and subject line Re: ftbfs, building indep packages
has caused the Debian Bug report #876269,
regarding ftbfs, building indep packages
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.)


-- 
876269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-psych
Version: 2.2.4-6
Severity: serious
Tags: sid buster

The package fails to build the indep packages:

   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
jruby -S rake compile
/usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in
`require':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
rake aborted!
LoadError: no such file to load -- psych
/<>/Rakefile:1:in `(root)'
/<>/Rakefile:13:in `block in (root)'
(See full trace by running task with --trace)
debian/rules:9: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
--- End Message ---
--- Begin Message ---
Source: jruby
Source-Version: 9.1.8.0-3

On Wed, Sep 20, 2017 at 12:37:28PM +0200, Matthias Klose wrote:
> Package: src:ruby-psych
> Version: 2.2.4-6
> Severity: serious
> Tags: sid buster
> 
> The package fails to build the indep packages:
> 

This was not a bug in ruby-psych but in jruby 9.1.8.0-2 that was
missing an explicit dependency on ruby-psych.

jruby 9.1.8.0-3 is available in sid now and this FTBFS bug is not
present anymore.

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


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

Bug#835120: marked as done (lintian: false positive: virtual-package-depends-without-real-package-depends for bacula-director)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:46 +
with message-id 
and subject line Bug#835120: fixed in lintian 2.5.53
has caused the Debian Bug report #835120,
regarding lintian: false positive: 
virtual-package-depends-without-real-package-depends for bacula-director
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.)


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

Dear Maintainer,

lintian reports the following for bacula 7.4.3+dfsg-3, which is
currently in experimental:

bacula-server
W virtual-package-depends-without-real-package-depends
depends: bacula-director

Probably the confusion comes from the fact that it's a virtual package
in unstable, but in experimental it's a real package.

Carsten

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 10.3-0-amd64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lintian depends on:
ii  binutils  2.27-6
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.28-4
ii  gettext   0.19.8.1-1
ii  hardening-includes2.8+nmu2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.29+b5
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2
ii  libdata-alias-perl1.20-1+b1
ii  libdpkg-perl  1.18.10
ii  libemail-valid-perl   1.200-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1
ii  libparse-debianchangelog-perl 1.2.0-10
ii  libperl5.22 [libdigest-sha-perl]  5.22.2-3
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.41-6+b1
ii  man-db2.7.5-1
ii  patchutils0.3.4-1
ii  perl  5.22.2-3
ii  t1utils   1.39-2
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages lintian recommends:
ii  dpkg 1.18.10
ii  libperlio-gzip-perl  0.19-1+b1
ii  perl 5.22.2-3
ii  perl-modules-5.22 [libautodie-perl]  5.22.2-3

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.10
ii  libhtml-parser-perl3.72-2
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 835...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * 

Bug#814599: marked as done (lintian: package-installs-into-obsolete-dir: mention filename requirements for /usr/share/bash-completion/completions/)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:46 +
with message-id 
and subject line Bug#814599: fixed in lintian 2.5.53
has caused the Debian Bug report #814599,
regarding lintian: package-installs-into-obsolete-dir: mention filename 
requirements for /usr/share/bash-completion/completions/
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.)


-- 
814599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash-completion
Version: 1:2.1-4.2
Severity: important

Responding to Lintian's warning (package-installs-into-obsolete-dir 
etc/bash_completion.d) I moved a completion script to the new 
/usr/share/bash-completion/completions/ location. The script is not sourced at 
all. However, if I move it back to the old location, it is instantly available 
again.

The completion script involved:

8X-
_chlogin()
{
local cur files
[ -r /srv/chroot/ ] || return 0
COMPREPLY=()
cur=${COMP_WORDS[COMP_CWORD]}
files=$( ls --color=never /srv/chroot )
if [ $COMP_CWORD -eq 1 ]
then
COMPREPLY=( $( compgen -W "$files" -- "$cur" ) )
fi
return 0
} &&
complete -F _chlogin chlogin
8X-

The Bash configuration fragment used to enable bash-completion:

8X-
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
  fi
fi
8X-


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages bash-completion depends on:
ii  bash  4.3-14+b1
ii  dpkg  1.18.4

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 814...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an 

Bug#847144: marked as done (lintian: Please reword init.d-script-needs-depends-on-lsb-base, drop versioned dependency)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#847144: fixed in lintian 2.5.53
has caused the Debian Bug report #847144,
regarding lintian: Please reword init.d-script-needs-depends-on-lsb-base, drop 
versioned dependency
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.)


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

Dear Maintainer,

the recently introduced check for a depedency on the no longer
pseudo-essential lsb-base package suggests a versioned dependency on
"lsb-base (>= 3.0-6)".

Can you please drop the version number part from that text? It's
superflous and confusing, even wheezy has lsb-base in 4.1-ish so an
unversioned dependency is always satisfied. Or I missed something,
please enlighten me then.

Christoph



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 847...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, 

Bug#849622: marked as done (lintian: unexpected description-starts-with-leading-spaces)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#849622: fixed in lintian 2.5.53
has caused the Debian Bug report #849622,
regarding lintian: unexpected description-starts-with-leading-spaces
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.)


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

Hi,

Although my debian/control file looks as such:

...
Suggests: nginx
Description:front-end for the rTorrent torrent client
   ruTorrent is a web front-end for rTorrent designed to emulate the
   ...

I am getting a W: rutorrent: description-starts-with-leading-spaces

I don't think this makes sense as I have zero spaces between
"Description:" and "front-end"

Thanks for your attention,
-Taylor

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.27.51.20161201-1
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.29-2
ii  gettext   0.19.8.1-1
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.30
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b1
ii  libdpkg-perl  1.18.18
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1~rc4-1
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.63-1+b1
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.24.1~rc4-1
ii  t1utils   1.39-2
ii  xz-utils  5.2.2-1.2

Versions of packages lintian recommends:
ii  dpkg 1.18.18
ii  libperlio-gzip-perl  0.19-1+b2
ii  perl 5.24.1~rc4-1
ii  perl-modules-5.24 [libautodie-perl]  5.24.1~rc4-1

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.18
ii  libhtml-parser-perl3.72-3
pn  libtext-template-perl  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 849...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag 

Bug#857123: marked as done (lintian: warning about missing classpath is confusing)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#857123: fixed in lintian 2.5.53
has caused the Debian Bug report #857123,
regarding lintian: warning about missing classpath is confusing
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.)


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

Hi,

I think the Lintian warning about a "missing classpath" in Java
libraries and applications is not very helpful at the moment.
Newcomers and even seasoned Java developers are either confused by it
or simply ignore it thus its usefulness is greatly diminished.

The problem is that the current check does not take different build
systems like Maven or Gradle into account and was probably created
with Javahelper and Ant in mind. Especially when Maven takes care of
calculating the classpath it is not always necessary to declare the
classpath manually. So Lintian's assumption is not correct that a
missing Class-Path entry in the jar's manifest file automatically
means that the dependency is not needed or one of the JARs should
include a classpath.

I suggest to remove this Lintian tag or lower the severity from
warning to info.

Regards,

Markus
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 857...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
   

Bug#690342: marked as done (corosync: cannot set lrm parameters)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 18:55:46 +0200
with message-id <87fubh48dp@lant.ki.iif.hu>
and subject line Re: corosync: cannot set lrm parameters
has caused the Debian Bug report #690342,
regarding corosync: cannot set lrm parameters
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.)


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

Dear Maintainer,

I need to set the lrm max-children parameter when corosync/pacemaker starts as 
it is not persisted, but the corosync init script provides no way to do this. I 
have inserted the following code into /etc/init.d/corosync:

maxwait=10
while [ $maxwait -gt 0 -a "`pidof lrmd`" = "" ]
do
echo waiting $maxwait
maxwait=`expr $maxwait - 1`
sleep 1
done
/usr/sbin/lrmadmin -p max-children 16

 at the end of the start function, but something a bit more flexible is 
required. Also the "wait 10 seconds for lrmd to appear" code might be a a bit 
fragile - it might still be possible for lrmd to have started but not be ready 
to accept lrmadmin requests so the script could race.

I'm thinking something along the lines of LRM_MAX_CHILDREN= in 
/etc/default/corosync file and parsing that in the init script.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages corosync depends on:
ii  adduser 3.113+nmu2
ii  libc6   2.13-32
ii  libcfg4 1.4.2-3
ii  libconfdb4  1.4.2-3
ii  libcoroipcc41.4.2-3
ii  libcoroipcs41.4.2-3
ii  libcpg4 1.4.2-3
ii  libevs4 1.4.2-3
ii  liblogsys4  1.4.2-3
ii  libpload4   1.4.2-3
ii  libquorum4  1.4.2-3
ii  libsam4 1.4.2-3
ii  libtotem-pg41.4.2-3
ii  libvotequorum4  1.4.2-3
ii  lsb-base4.1+Debian4

corosync recommends no packages.

corosync suggests no packages.

-- Configuration Files:
/etc/corosync/corosync.conf changed [not included]
/etc/default/corosync changed [not included]
/etc/init.d/corosync changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 13 Oct 2012 09:37:37 +1100 root  wrote:

> I need to set the lrm max-children parameter when corosync/pacemaker
> starts as it is not persisted, but the corosync init script provides
> no way to do this.

Almost five years later, this is accomplished by the node-action-limit
cluster property, see man crmd.  For a node-local override you can set
the PCMK_node_action_limit variable in /etc/default/pacemaker.
-- 
Feri--- End Message ---

Bug#681713: marked as done (lintian: Please add a test which checks Vcs-Browser headers for hardcoded revisions/commits)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:46 +
with message-id 
and subject line Bug#681713: fixed in lintian 2.5.53
has caused the Debian Bug report #681713,
regarding lintian: Please add a test which checks Vcs-Browser headers for 
hardcoded revisions/commits
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.)


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

Dear Lintian Maintainers,

today I noticed that the Vcs-Browser header of the debian-junior source
package included query string ?rev=0=0 which leads to an empty view
of the repository (due to containing no commit). See
http://bugs.debian.org/681709 for details.

To keep the header useful even for people without any knowledge of the
used VCS viewer, suffixes like this should never be included in the
Vcs-Browser header.

After filing the bug report I noticed that many more package are
affected by the same issue, although mostly from the Debian Pure Blend,
Debian Science and Debian Med teams (X-Debbugs-Cc'ed):

$ fgrep -h rev= 
/var/lib/apt/lists/ftp.ch.debian.org_debian_dists_{experimental,sid}_main_source_Sources
 | sort -u
Vcs-Browser: 
https://labs.riseup.net/code/projects/backupninja/repository/show?rev=debian
Vcs-Browser: http://svn.debian.org/wsvn/blends/blends/trunk/blends/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/blends/projects/debichem/trunk/debichem/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/blends/projects/ezgo/trunk/debian-ezgo/?rev=0=0
Vcs-Browser: http://svn.debian.org/wsvn/blends/projects/gis/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/blends/projects/junior/trunk/debian-junior/?rev=0=0
Vcs-Browser: http://svn.debian.org/wsvn/cdd/cdd/trunk/cdd/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/collab-maint/ext-maint/alpine/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-edu/trunk/src/debian-edu/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-edu/trunk/src/libpam-mklocaluser/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-edu/trunk/src/sitesummary/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/pkg-games/packages/trunk/box2d/box2d-2.0.1/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/community/infrastructure/getData/?rev=0=0trunk
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/abacas/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/alien-hunter/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/amap-align/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/ampliconnoise/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/biococoa/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/ctn/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/dialign/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/dialign-t/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/dotur/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/emboss-explorer/trunk/?rev=0=0trunk
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/ensembl/libbio-das-lite-perl/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/figtree/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/glam2/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/igstk/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/insighttoolkit/wrapitk/python/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/libace-perl/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/libbio-mage-perl/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/libbio-mage-utils-perl/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/libctapimkt/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/libg2/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/libgenome/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/libgo-perl/trunk/?rev=0=0
Vcs-Browser: 
http://svn.debian.org/wsvn/debian-med/trunk/packages/libjam-java/trunk/?rev=0=0
Vcs-Browser: 

Bug#873702: marked as done (lintian: False positive: desktop-entry-lacks-keywords-entry)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#873702: fixed in lintian 2.5.53
has caused the Debian Bug report #873702,
regarding lintian: False positive: desktop-entry-lacks-keywords-entry
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.)


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

Package: lintian
Version: 2.5.52
Severity: normal

Dear Lintian maintainers,

The tool suggest to add a Keywords field to .desktop file which has
Type=Link, but this is not allowed by the current specification[1].

I faced it on my .desktop file[2] with an URL link. Lintian says:

I: phpliteadmin: desktop-entry-lacks-keywords-entry 
usr/share/applications/phpliteadmin.desktop

N:
N:This .desktop file does either not contain a "Keywords" entry 
or it does

N:not contain any keywords not already present in the "Name" or
N:"GenericName" entries.
N:
N:.desktop files are organized in key/value pairs (similar to 
.ini files).
N:"Keywords" is the name of the entry/key in the .desktop file 
containing

N:keywords relevant for this .desktop file.
N:
N:The desktop-file-validate tool in the desktop-file-utils 
package is

N:useful for checking the syntax of desktop entries.
N:
N:Refer to
N: 
https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s05.html,

N:https://bugs.debian.org/693918, and
N: 
https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords for

N:details.
N:
N:Severity: wishlist, Certainty: certain
N:
N:Check: menu-format, Type: binary
N:

 [1]: 
https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.1.html#recognized-keys
 [2]: 
https://anonscm.debian.org/git/collab-maint/phpliteadmin.git/tree/debian/phpliteadmin.desktop?id=65a5c8cc4294ef0247e7327ceca745c4b38d69d5
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 873...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by 

Bug#874121: marked as done (lintian: Please add more packagename to section mappings)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#874121: fixed in lintian 2.5.53
has caused the Debian Bug report #874121,
regarding lintian: Please add more packagename to section mappings
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.)


-- 
874121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.52
Severity: wishlist
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-violations

Hi!

Here's an untested update of the packagename to section mapping
including several other common patterns.

Thanks,
Guillem
From cfe345d523ced980fcea149cca7b09d85b2e375c Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Sun, 3 Sep 2017 15:42:26 +0200
Subject: [PATCH] data/fields/name_section_mappings: Add more mappings

---
 data/fields/name_section_mappings | 21 +++--
 1 file changed, 19 insertions(+), 2 deletions(-)

diff --git a/data/fields/name_section_mappings b/data/fields/name_section_mappings
index 116fa3885..e7d2af9c2 100644
--- a/data/fields/name_section_mappings
+++ b/data/fields/name_section_mappings
@@ -3,17 +3,34 @@
 -docs?$  => doc
 -dbg(?:sym)?$=> debug
 ^node-   => javascript
+^lib(?:apache2|nginx)-mod-  => httpd
+^lighttpd-mod   => httpd
+\.(?:framework|tool|app)(?:-common)?$   => gnustep
+^gnustep-   => gnustep
 ^(?:python-)?zope=> zope
 ^python3?-   => python
 ^r-(?:cran|bioc|other)-  => gnu-r
+^(?:cl|elpa)-=> lisp
+-elisp(?:-.*)$   => lisp
 ^lib.*-perl$ => perl
 lib.*-cil(?:-dev)?$  => cli-mono
-^lib.*-(?:java|gcj)$ => java
-^(?:lib)php- => php
+^lib.*-(?:java|gcj|jni)$ => java
+^(?:lib)php(?:\d(?:\.\d)?)?- => php
+^lib-.*-php$ => php
+^haskell-=> haskell
 ^lib(?:hugs|ghc6?)-  => haskell
 ^lib.*-ruby(?:1\.\d)?$   => ruby
+^ruby-   => ruby
 ^lib.*-(?:ocaml|camlp4)-dev$ => ocaml
 ^libjs-  => javascript
 ^gir\d+\.\d+-.*-\d+\.\d+$=> introspection
+^(?:x?fonts|ttf)-   => fonts
+^(?:aspell|hunspell|myspell|mythes)-=> localization
+^hyphen-[a-z]{2}(?:-[a-z]{2})?$ => localization
+^dict-freedict- => localization
+^gcompris-sound-=> localization
+-l10n(?:-.*)?$  => localization
+-(dkms|firmware)$   => kernel
+^moblin-=> embedded
 # catch remaining should be after specific lib
 ^lib.*-dev$  => libdevel
-- 
2.14.1

--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 874...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - 

Bug#873434: marked as done (lintian: Please check for @import url(http://...) in /usr/share/doc)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#873434: fixed in lintian 2.5.53
has caused the Debian Bug report #873434,
regarding lintian: Please check for @import url(http://...) in /usr/share/doc
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.)


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

I have discovered various files in /usr/share/doc/*/html on my system
which do things like this:
  @import url(http://fonts.googleapis.com/css?family=Open+Sans);

Eg,
  /usr/share/doc/python-scipy-doc/html/_static/less/spc-bootstrap.less
  /usr/share/doc/libfreetype6-dev/css/freetype2.css

Please would you make lintian complain about @import url(), or about
fonts.googleapis.com, or something.

Thanks,
Ian.

-- System Information:
Debian Release: 9.0
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lintian depends on:
ii  binutils  2.28-5
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  file  1:5.30-1
ii  gettext   0.19.8.1-2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.32
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b1
ii  libdigest-sha-perl5.96-1+b1
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-2
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.63-2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.24.1-2
ii  t1utils   1.39-2
ii  xz-utils  5.2.2-1.2+b1

Versions of packages lintian recommends:
ii  dpkg 1.18.24
ii  libperlio-gzip-perl  0.19-1+b2
ii  perl 5.24.1-2
ii  perl-modules-5.22 [libautodie-perl]  5.22.2-1
ii  perl-modules-5.24 [libautodie-perl]  5.24.1-2

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.24
ii  libhtml-parser-perl3.72-3
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 873...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 

Bug#873323: marked as done (lintian -- False positives on copyright-year-in-future)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#873323: fixed in lintian 2.5.53
has caused the Debian Bug report #873323,
regarding lintian -- False positives on  copyright-year-in-future
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.)


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

Package: lintian
Version: 2.5.52
Severity: normal


The license of package oysttyer contains an example, which gives a false 
positive for "copyright-year-in-future":

* If you choose to create and distribute a derivative work based on
   this package, your derivative work must clearly make reference to
   this package, any other packages your work or the original work
   might be based on, and all applicable copyrights, either in your
   documentation, your work's standard human-readable output, or both.
   A suggested method might be

 Contains or is based on the Foo software package.
 Copyright (C) 2112 D. Original Author. All rights reserved.
 http://their.web.site.invalid/

 Thorsten
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 873...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore 

Bug#873458: marked as done (lintian: Please add autopkgtest-pkg-elpa as a valid value for Testsuite)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#873458: fixed in lintian 2.5.53
has caused the Debian Bug report #873458,
regarding lintian: Please add autopkgtest-pkg-elpa as a valid value for 
Testsuite
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.)


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

Hi,

Currently, lintian complains about the pkg-go testsuite, but autodep8 has
support for it since 0.9.

source: unknown-testsuite autopkgtest-pkg-go

Can you add pkg-go to the list of valid testsuites?

Moreover, autodep8 already supports a few other automatic test suites, so those
should be added too:

dkms
elpa
go
nodejs
perl
python
r
ruby

Thanks.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lintian depends on:
ii  binutils  2.29-7
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.31-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-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.18.24
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 873...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - 

Bug#873096: marked as done (Warn about using deprecated /usr/bin/nodejs location)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#873096: fixed in lintian 2.5.53
has caused the Debian Bug report #873096,
regarding Warn about using deprecated /usr/bin/nodejs location
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.)


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

Hi,

since a recent decision of the technical comity, the nodejs package
provides /usr/bin/node, in addition to /usr/bin/nodejs for backward
compatibility.

It would be nice if lintian were warning about nodejs uses in script
(and in particular in debian/tests/).

Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 873...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and matching specific and general street
 addresses.  (Closes: #869788)
   - Match all violating years in a line, not just the first (eg.
 

Bug#872843: marked as done (lintian shouldn't check copyright_hints file for FIXME)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#872843: fixed in lintian 2.5.53
has caused the Debian Bug report #872843,
regarding lintian shouldn't check copyright_hints file for FIXME
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.)


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

Hi,

I believe that lintian shouldn't check d/copyright_hints file for FIXME
entries.
Check should be limited to d/copyright file.

The very _purpose_ of the copyright_hints file is to _hint_ about
copyright and licensing information, and to distinguish hints from facts
- i.e. to avoid maintainers blindly trusting the hints by copying over
to copyright file without double-checking.

best regards

mira



-- System Information:
Debian Release: buster/sid
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable'), 
(500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-8.3-liquorix-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.29-4
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.31-1
ii  gettext   0.19.8.1-2+b1
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.32+b2
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-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.18.24
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 872...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl 

Bug#875933: marked as done (lintian: Please ignore debian/copyright_hints file from file-contains-fixme-placeholder tag checking)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#872843: fixed in lintian 2.5.53
has caused the Debian Bug report #872843,
regarding lintian: Please ignore debian/copyright_hints file from 
file-contains-fixme-placeholder tag checking
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.)


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

Dear Maintainer,

debian/copyright_hints file is a hint file for maintainer of package
providing possible license information as detected by licensecheck
tool. So they tend to have FIXME which should be used as hint to update
actual debian/copyright file.

Additionally file also helps in tracking of new additions to source during
version update. 

As such giving lintian error for this particular file does not make sense.
And this tag is creating lintian error in most of CDBS packages employing
copyright check functionality.

So please ignore debian/copyright_hints file while checking for FIXME.

Cheers,



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

Kernel: Linux 4.11.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IN:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.29-10
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-8
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-8
ii  t1utils   1.40-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.18.24
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 872...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 

Bug#875509: marked as done (lintian: please upload a version that knows about Policy 4.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:48 +
with message-id 
and subject line Bug#875509: fixed in lintian 2.5.53
has caused the Debian Bug report #875509,
regarding lintian: please upload a version that knows about Policy 4.1.0
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.)


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

Hello!

A new version of the Debian Policy has been recently published
and [announced]. This new version has been almost immediately [added]
to the list of standards known to lintian.

[announced]: 

[added]: 


However, this change has not yet materialized in a new lintian
version uploaded to unstable.
This means that the lintian version currently in unstable is
not able to check for compliance with Debian Policy 4.1.0 and
complains about newer-standards-version, when it encounters
a Standards-Version: 4.1.0 package...

Please upload a new lintian version to unstable.
Thanks for your time!

Bye.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.29-9
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-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.18.24
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 875...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 

Bug#872076: marked as done (lintian: please warn about build-dependency on dh-systemd)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#872076: fixed in lintian 2.5.53
has caused the Debian Bug report #872076,
regarding lintian: please warn about build-dependency on dh-systemd
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.)


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

dh-systemd is a transitional package in stretch, pointing to a new
enough debhelper.  Please emit a warning about an explicit
build-dependency on it.

See also https://bugs.debian.org/871312

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 872...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in 

Bug#872611: marked as done (lintian: Please warn on package using sensible-utils w/o relationship)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#872611: fixed in lintian 2.5.53
has caused the Debian Bug report #872611,
regarding lintian: Please warn on package using sensible-utils w/o relationship
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.)


-- 
872611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.52
Severity: wishlist
X-Debbugs-CC: Clint Adams 

Hi!

As part of the long transition to split sensible-utils out from
debianutils, the remaining Depends from debianutils was removed
recently in version 4.8.2.

I asked Clint whether he could send a mail with the current callers
so that they'd be aware of the change and they could fix it, but
thinking about it, it seems more effective and easier to let lintian
check this, as this should be a local and trivial (?) thing to check
for.

Any package that contains references to one of the sensible-utils
binary in non-documentation pathnames/filenames, and does not have any
kind of relationship (Pre-Depends/Depends/Recommends/Suggests) would
get a warning.

This way we do not need to care whether the program is using it
conditionally or not. :)

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

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 872...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the 

Bug#871957: marked as done ([lintian] orig-tarball-missing-upstream-signature should exclude repacks)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#871957: fixed in lintian 2.5.53
has caused the Debian Bug report #871957,
regarding [lintian] orig-tarball-missing-upstream-signature should exclude 
repacks
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.)


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

Upstream does not sign my repacks :o).

Please don't trigger orig-tarball-missing-upstream-signature if the
version contains +ds, +debian, or +dfsg.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 871...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and matching specific and general street
 addresses.  (Closes: #869788)
   - Match all violating years in a line, not just the first (eg.
 "2000-2107").
   - 

Bug#873211: marked as done (Please warn about binary packages shipping .class files)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#873211: fixed in lintian 2.5.53
has caused the Debian Bug report #873211,
regarding Please warn about binary packages shipping .class files
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.)


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

Dear Maintainer,

While improving the packaging of a Debian package, I found that the
source release included .class files (pre compiled java files).  Those
.class files were also part of the upstream release.  These upstream
compiled files were also included in the binary release.

While running lintian, I saw no warning about their presence.  This
can be reproduced with the imagej package 1.51i+dfsg-2 or older.

Best Regards,
Carnë

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/32 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.28-5
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  file  1:5.30-1
ii  gettext   0.19.8.1-2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.32
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b1
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3+deb9u1
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.63-2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.24.1-3+deb9u1
ii  t1utils   1.39-2
ii  xz-utils  5.2.2-1.2+b1

Versions of packages lintian recommends:
ii  dpkg 1.18.24
ii  libperlio-gzip-perl  0.19-1+b2
ii  perl 5.24.1-3+deb9u1
ii  perl-modules-5.22 [libautodie-perl]  5.22.2-1
ii  perl-modules-5.24 [libautodie-perl]  5.24.1-3+deb9u1

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.24
ii  libhtml-parser-perl3.72-3
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 873...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) 

Bug#874659: marked as done (orig-tarball-missing-upstream-signature should not trigger on repacked tarballs)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#871957: fixed in lintian 2.5.53
has caused the Debian Bug report #871957,
regarding orig-tarball-missing-upstream-signature should not trigger on 
repacked tarballs
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.)


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

Hi,
We can't use the signatures for these. We don't have a recommended
mechanisms to detect these but looking for +dfsg in the upstream version
and looking for a filter in debian/copyright should catch most of these.
Cheers,
 -- Guido

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

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.28-6
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-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.18.24
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 871...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - 

Bug#870822: marked as done (lintian: [checks/python] Check for applications using Python 2.x)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870822: fixed in lintian 2.5.53
has caused the Debian Bug report #870822,
regarding lintian: [checks/python] Check for applications using Python 2.x
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.)


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

Hi,

The 2.x series of Python is due for deprecation and will not be
maintained past 2020.

Please emit a warning for applications (ie. regular packages, not Python
modules) that Depend etc. on Python 2.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and matching specific and general street
 addresses.  (Closes: #869788)
   - Match all 

Bug#871046: marked as done (ruby-json FTBFS: It seems your ruby installation is missing psych (for YAML output).)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 18:39:26 +0100
with message-id <20170920173926.ga19...@alice.nomadium.lan>
and subject line Re: ruby-json FTBFS: It seems your ruby installation is 
missing psych (for YAML output).
has caused the Debian Bug report #871046,
regarding ruby-json FTBFS: It seems your ruby installation is missing psych 
(for YAML 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.)


-- 
871046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-json
Version: 2.1.0+dfsg-1
Severity: serious

Some recent change in unstable makes ruby-json FTBFS:

https://tests.reproducible-builds.org/debian/history/ruby-json.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-json.html

...
   dh_ruby --clean
jruby -S rake clean
GNU Make 4.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
/usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in 
`require':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
rake aborted!
LoadError: no such file to load -- psych
/build/1st/ruby-json-2.1.0+dfsg/Rakefile:108:in `(root)'
(See full trace by running task with --trace)
debian/rules:16: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1
--- End Message ---
--- Begin Message ---
Source: jruby
Source-Version: 9.1.8.0-3

On Sun, Aug 06, 2017 at 11:22:00PM +0300, Adrian Bunk wrote:
> Source: ruby-json
> Version: 2.1.0+dfsg-1
> Severity: serious
> 
> Some recent change in unstable makes ruby-json FTBFS:
> 
> https://tests.reproducible-builds.org/debian/history/ruby-json.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-json.html
> 
> [...]

This was not a bug in ruby-json but in jruby 9.1.8.0-2 that was
missing an explicit dependency on ruby-psych.

jruby 9.1.8.0-3 is available in sid now and this FTBFS bug is not
present anymore.

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


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

Bug#870758: marked as done (lintian: [checks/python] Please check for packages build-depending on "python-sphinx | python3-sphinx")

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870758: fixed in lintian 2.5.53
has caused the Debian Bug report #870758,
regarding lintian: [checks/python] Please check for packages build-depending on 
"python-sphinx | python3-sphinx"
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.)


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

Hi,

Please check for packages that alternatively Build-Depend on the Python
2 or Python 3 version of the Sphinx documentation generator.

The 2.x series of Python is due for deprecation and will not be
maintained past 2020.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and matching specific and general 

Bug#872042: marked as done (lintian: please check for missing calls to dpkg-maintscript-helper)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#872042: fixed in lintian 2.5.53
has caused the Debian Bug report #872042,
regarding lintian: please check for missing calls to dpkg-maintscript-helper
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.)


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

Hi

Please check for missing calls to dpkg-maintscript-helper(1) in
maintainer scripts.

They require coordinated actions from several maintainer scripts
and can be easily missed.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 872...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and matching specific and general street
 addresses.  (Closes: #869788)
   - Match all violating years in a line, not just the 

Bug#873701: marked as done (lintian: False positive: apache2-unparsable-dependency)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#873701: fixed in lintian 2.5.53
has caused the Debian Bug report #873701,
regarding lintian: False positive: apache2-unparsable-dependency
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.)


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

Package: lintian
Version: 2.5.52
Severity: normal
X-Debbugs-CC: debian-apa...@lists.debian.org

Dear Lintian maintainers,

It seems Lintian offers to make modifications that break work of the
a2enconf script. At least if I add `mod_` in the next line, a2enconf
fails due to a disabled module.

# Depends: php7.0

I faced this when I checked an Apache configuration[1] in my new package.
Lintian says:

W: phpliteadmin: apache2-unparsable-dependency 
etc/apache2/conf-available/phpliteadmin.conf php7.0

N:
N:The package is declaring a module dependency within an Apache
N:configuration file which does not meet the requirements. 
Dependencies
N:must be declared without paths, leading "mod_" prefix and 
without file

N:extension.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: apache2, Type: binary
N:

 [1]: 
https://anonscm.debian.org/git/collab-maint/phpliteadmin.git/tree/debian/phpliteadmin.conf?id=65a5c8cc4294ef0247e7327ceca745c4b38d69d5
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 873...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" 

Bug#762956: marked as done (lintian: add embedded-library libopenjpeg)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:46 +
with message-id 
and subject line Bug#762956: fixed in lintian 2.5.53
has caused the Debian Bug report #762956,
regarding lintian: add embedded-library libopenjpeg
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.)


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

hi

it would be nice to add a embedded-library openjpeg check. Currently
there are at least two packages shipping openjpeg as convenient
library:

$ dpkg -L libinsighttoolkit3.20 | grep openjpeg
/usr/lib/libitkopenjpeg.so.3.20.1

and

$ dpkg -L libinsighttoolkit4.6 | grep openjpeg
/usr/lib/libitkopenjpeg-4.6.so.1


Thanks.
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 762...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and matching specific and general street
 addresses.  (Closes: #869788)
   - Match all violating years in a line, not just the first (eg.
 

Bug#779675: marked as done (lintian: Add flag --list-tags that will list all tags Lintian knows about)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:46 +
with message-id 
and subject line Bug#779675: fixed in lintian 2.5.53
has caused the Debian Bug report #779675,
regarding lintian: Add flag --list-tags that will list all tags Lintian knows 
about
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.)


-- 
779675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.6ubuntu0.1
Severity: wishlist

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

I would like to avoid having to maintain multiple 

If I ask Lintian to suppress a tag that is known to a later version of Lintian 
but not known to the current version it will exit with an error.  This can
be problematic in an environment where a package gets built on different
versions of OSes running different versions of Lintian (potentially).

Having a --list-tags option will allow me to take a set of tags I have and 
create a new set that consists exclusively of tags known to the current
version of Lintian so that I do not need to maintain a separate list of 
override tags for each platform I run lintian on

There could be other uses to for this option

*** End of the template - remove these lines ***


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-23-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils   2.22-6ubuntu1.2
ii  bzip2  1.0.6-1
ii  diffstat   1.54-1
ii  file   5.09-2ubuntu0.6
ii  gettext0.18.1.1-5ubuntu3
ii  intltool-debian0.35.0+20060710.1
ii  libapt-pkg-perl0.1.25build2
ii  libc-bin   2.15-0ubuntu10.11
ii  libclass-accessor-perl 0.34-1
ii  libclone-perl  0.31-1build3
ii  libdpkg-perl   1.16.1.2ubuntu7.5
ii  libemail-valid-perl0.185-1
ii  libipc-run-perl0.90-1
ii  libparse-debianchangelog-perl  1.2.0-1ubuntu1
ii  libtimedate-perl   1.2000-1
ii  liburi-perl1.59-1
ii  locales2.13+git20120306-3
ii  man-db 2.6.1-2
ii  patchutils 0.3.2-1.1
ii  perl [libdigest-sha-perl]  5.14.2-6ubuntu2
ii  unzip  6.0-4ubuntu1

lintian recommends no packages.

Versions of packages lintian suggests:
ii  binutils-multiarch 
ii  dpkg-dev   1.16.1.2ubuntu7.5
ii  libhtml-parser-perl3.69-1build1
ii  libtext-template-perl  
ii  man-db 2.6.1-2
ii  xz-utils   5.1.1alpha+20110809-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 779...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) 

Bug#865570: marked as done (lintian: description of testsuite-autopkgtest-missing is unhelpful/incorrect)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#865531: fixed in lintian 2.5.53
has caused the Debian Bug report #865531,
regarding lintian: description of testsuite-autopkgtest-missing is 
unhelpful/incorrect
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.)


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

Dear Maintainer,

I was updating one of my packages today and received the testsuite-autopkgtest-
missing information warning from lintian. This appears to have been added due
to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859467.

This is very good, because there isn't a testsuite in my package, and thanks to
the prompt I will now provide one (I keep forgetting to check if this is one of
the packages for which I haven't done it yet).

However, reading the information about the warning, it sounds like lintian will
only be checking if there is a Testsuite field in debian/control (I have not
tested this). Unfortunately, this field is optional (it is added automatically
by dpkg-source version 1.17.11 or later) and lintian would give false positives
in cases where a testsuite is provided, but not declared in debian/control.

A more reliable way to check if a testsuite is provided, is to look for a
control file in the debian/tests directory.

Or if I am wrong about lintian, and it already checks there too, then the
description for the lintian tag should be updated.

Regards,

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers yakkety-updates
  APT policy: (500, 'yakkety-updates'), (500, 'yakkety-security'), (500, 
'yakkety'), (100, 'yakkety-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 865...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an 

Bug#865531: marked as done (lintian: description of testsuite-autopkgtest-missing is unhelpful/incorrect)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#865531: fixed in lintian 2.5.53
has caused the Debian Bug report #865531,
regarding lintian: description of testsuite-autopkgtest-missing is 
unhelpful/incorrect
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.)


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

lintian complains with testsuite-autopkgtest-missing when debian/control
is missing the "Testsuite" field but that field is usually not present
in the unpacked source package because it is automatically added by
dpkg-source to the .dsc when it finds debian/tests/control.

So instead you should check that field in the .dsc or directly
debian/tests/control in the unpacked source package.

Cheers,

-- System Information:
Debian Release: 9.0
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.28-6
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.30-1
ii  gettext   0.19.8.1-2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.32
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b1
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.63-2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.24.1-3
ii  t1utils   1.39-2
ii  xz-utils  5.2.2-1.2+b1

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

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.24
ii  libhtml-parser-perl3.72-3
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 865...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + 

Bug#871767: marked as done (lintian: [checks/cruft] use substr instead of substring in example)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#871767: fixed in lintian 2.5.53
has caused the Debian Bug report #871767,
regarding lintian: [checks/cruft] use substr instead of substring in example
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.)


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

Dear Maintainers,
the mentions-deprecated-usr-lib-perl5-directory check show an
example to add in debian/rules that uses a misspelled Perl
function that gives an error:

$ perl -MConfig -wE'say substring($Config{vendorarch},1)'
Undefined subroutine ::substring called at -e line 1.

The right spelling would be substr (patch attached at the end).

Cheers!
Alex


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages lintian depends on:
ii  binutils  2.29-4
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.31-1
ii  gettext   0.19.8.1-2+b1
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.32+b2
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

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


diff --git a/checks/cruft.desc b/checks/cruft.desc
index 57ed5cc95..e3948565b 100644
--- a/checks/cruft.desc
+++ b/checks/cruft.desc
@@ -857,7 +857,7 @@ Info: As of Perl 5.20, the vendorarch directory is /usr/lib/triplet/perl
  but this package still uses usr/lib/perl5 in some of the files under debian/.
  Please replace that with the value of $Config{vendorarch} configuration
  parameter, e.g.
-  $(shell perl -MConfig -wE'say substring($$Config{vendorarch},1)')
+  $(shell perl -MConfig -wE'say substr($$Config{vendorarch},1)')
 
 Tag: readme-source-is-dh_make-template
 Severity: important


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 871...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 

Bug#871575: marked as done (lintian: maintainer-address-causes-mail-loops-or-bounces should be fixed to allow @packages.debian.org emails)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#871575: fixed in lintian 2.5.53
has caused the Debian Bug report #871575,
regarding lintian: maintainer-address-causes-mail-loops-or-bounces should be 
fixed to allow @packages.debian.org emails
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.)


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

I believe that the check maintainer-address-causes-mail-loops-or-bounces
should no longer refuse "*@packages.debian.org" in the Maintainer field.

I did patch the code generating the aliases on packages.debian.org to
avoid mail loops:
https://anonscm.debian.org/cgit/webwml/packages.git/commit/?h=debian-master=5f4f27920e996e521d32dfb5a9693a09348d18d5

The current downsides of using such emails is:
- it might generate bounces for ftp-masters for the first emails
  until the package has been accepted in unstable
- Package Tracker subscribers will get duplicate emails from
  various services

Those downsides will need to be fixed but in the mean time I would
like the requirement to be relaxed so that we can try on a test package
and see what services are generating duplicate emails.

Cheers,

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

Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.28-6
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.30-1
ii  gettext   0.19.8.1-2+b1
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.32
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b1
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-7
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.63-2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.24.1-7
ii  t1utils   1.39-2
ii  xz-utils  5.2.2-1.3

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

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.24
ii  libhtml-parser-perl3.72-3
ii  libtext-template-perl  1.46-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 871...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker

Bug#870681: marked as done (lintian: [checks/python] Check for python-foo without python3-foo)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870681: fixed in lintian 2.5.53
has caused the Debian Bug report #870681,
regarding lintian: [checks/python] Check for python-foo without python3-foo
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.)


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

The 2.x series of Python is due for deprecation and will not be
maintained past 2020.

We should therefore warn about packages not providing a corresponding
Python 3 version.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and matching specific and general street
 addresses.  (Closes: #869788)
   - Match all violating years in a line, not just the first (eg.

Bug#870272: marked as done (lintian: Should warn about python3-foo not in "Section: python")

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870272: fixed in lintian 2.5.53
has caused the Debian Bug report #870272,
regarding lintian: Should warn about python3-foo not in "Section: python"
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.)


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

Hi,

Lintian should warn about python3-foo not in "Section: python", not
just python2-foo. I found this as my python-gunicorn package was being
flagged but the corresponding python3-gunicorn package was curiously
not.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard numbers and matching specific and general street
 addresses.  (Closes: #869788)
  

Bug#870649: marked as done (lintian: false positive codeless-jar with Clojure reader conditionals)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870649: fixed in lintian 2.5.53
has caused the Debian Bug report #870649,
regarding lintian: false positive codeless-jar with Clojure reader conditionals
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.)


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

Dear Maintainer,

The codeless-jar check expects a jar to contain .class and/or .clj 
files. Clojure Reader Conditionals[1], introduced in Clojure 1.7, rely 
on a new file extension (.cljc) which lintian should also count as code.  
Otherwise, jars containing only .cljc files are erroneously reported as 
"codeless".

The attached patch fixes this.

[1] https://clojure.org/guides/reader_conditionals 

Regards,
Apollon
>From 7d51503e8834c85b727da9a6fbf726e27ebe0abc Mon Sep 17 00:00:00 2001
From: Apollon Oikonomopoulos 
Date: Thu, 3 Aug 2017 15:40:16 -0400
Subject: [PATCH] c/java.pm: handle .cljc when looking for code

Clojure >= 1.7 supports the so-called "reader conditionals" which allow
different dialects of Clojure to share common code[1]. Reader
conditionals add a new class of code files (.cljc) which lintian should
know about.

[1] https://clojure.org/guides/reader_conditionals
---
 checks/java.pm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/checks/java.pm b/checks/java.pm
index e8a55be94..83bd97085 100644
--- a/checks/java.pm
+++ b/checks/java.pm
@@ -79,10 +79,10 @@ sub run {
 $has_public_jars = 1;
 }
 # check for common code files like .class or .clj (Clojure files)
-foreach my $class (grep { m/\.(?:class|clj)$/oi } sort keys %{$files}){
+foreach my $class (grep { m/\.(?:class|cljc?)$/oi } sort keys %{$files}){
 my $mver = $files->{$class};
 $classes = 1;
-next if $class =~ m/\.clj$/;
+next if $class =~ m/\.cljc?$/;
 # .class but no major version?
 next if $mver eq '-';
 if (   $mver <= $MAX_BYTECODE->value('min-bytecode-version') - 1
-- 
2.11.0

--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - 

Bug#870069: marked as done (orig-tarball-missing-upstream-signature error breaks rebuilding existing packages and more)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870069: fixed in lintian 2.5.53
has caused the Debian Bug report #870069,
regarding orig-tarball-missing-upstream-signature error breaks rebuilding 
existing packages and more
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.)


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

Hi,

I think "error" is a rather unfortunate choice for the severity level of
"orig-tarball-missing-upstream-signature".

* I have some (existing) packages uploaded on build.opensuse.org, and
  they now fail to build for "Debian_Next" (buster).  I'd rather avoid
  modifying the upstream debian package just for this.

* I also generate snapshot builds automatically.  These are (on purpose)
  not signed with the "upstream key" - because they are automatically
  generated.

  I want to stay as close as possible to the debian package, and this
  error makes this a lot harder.

I like the check, but would prefer to see it downgraded to a warning.

I already had to enable lintian manually for my build.opensuse.org
projects (I was told they disabled it because it broke too many builds
[1]); I'd prefer to keep it enabled at least for my projects.

cheers,
Stefan

[1]: https://build.opensuse.org/project/prjconf/Debian:8.0
 https://build.opensuse.org/project/prjconf/Debian:9.0
 https://build.opensuse.org/project/prjconf/Debian:Next
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + 

Bug#869788: marked as done (lintian: false positives in copyright-year-in-future)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#869788: fixed in lintian 2.5.53
has caused the Debian Bug report #869788,
regarding lintian: false positives in copyright-year-in-future
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.)


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

Hi,

Just to collect some of these in one place:

  https://sources.debian.net/src/album-data/4.05-7/debian/copyright/#L55
  https://sources.debian.net/src/libb2/0.97-2/debian/copyright/#L16
  https://sources.debian.net/src/sympa/6.2.16~dfsg-5/debian/copyright/#L161
  
https://sources.debian.net/src/insubstantial/7.3%2Bdfsg3-2/debian/copyright/#L53
  
https://sources.debian.net/src/insubstantial/7.3%2Bdfsg3-2/debian/copyright/#L129


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 869...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in 

Bug#870722: marked as done (lintian: orig-tarball-missing-upstream-signature has inflated severity)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870722: fixed in lintian 2.5.53
has caused the Debian Bug report #870722,
regarding lintian: orig-tarball-missing-upstream-signature has inflated severity
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.)


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

Hi,

Until tools such as git-buildpackage make producing a source tarball
along with the signatures easier, the "E:" tag for the
orig-tarball-missing-upstream-signature tag seems excessive at the moment.

See:

  https://lists.debian.org/debian-devel/2017/07/msg00451.html
  https://lists.debian.org/debian-devel/2017/08/msg00072.html

etc. etc.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, 

Bug#870730: marked as done (lintian: [checks/python] Please check for packages that Build-Depend on Python 2.x version of Sphinx)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870730: fixed in lintian 2.5.53
has caused the Debian Bug report #870730,
regarding lintian: [checks/python] Please check for packages that Build-Depend 
on Python 2.x version of Sphinx
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.)


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

Hi,

Please check for packages that Build-Depend on the Python 2.x version
of the Sphinx documentation generator as the 2.x series of Python is
due for deprecation and will not be maintained past 2020.

Some Python modules may need to depend on both python-sphinx and
python3-sphinx, however.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in port numbers, email addresses, ISO
 standard 

Bug#870199: marked as done (lintian: file-contains-fixme-placeholder is "Certainty: certain" but has false positives)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#870199: fixed in lintian 2.5.53
has caused the Debian Bug report #870199,
regarding lintian: file-contains-fixme-placeholder is "Certainty: certain" but 
has false positives
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.)


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

E: geany-plugins source: file-contains-fixme-placeholder debian/control:119 
FIXME
N: 
N:This file appears to be incomplete or insufficiently modified as it
N:contains a "FIXME" placeholder text. These can often be generated by
N:package generation tools such as dh_make or npm2deb.
N:
N:Please double-check the file and replace the placeholder with the
N:required command or information.
N:
N:Severity: important, Certainty: certain
N:
N:Check: cruft, Type: source
N: 


That's a false positive:


Package: geany-plugin-addons
Source: geany-plugins
...
Description-en: miscellaneous plugins for Geany
 This plugin adds various small addons to Geany which aren't worth an
 individual plugin, but might still be useful for people.
  * DocList: This addon places a new item in the toolbar and when clicked
offers a menu listing all open files plus the 'Close All' and 'Close Other
Documents' menu items. This can be useful to quickly access open files and
switch to them.
  * OpenURI: Adds 'Open URI' and 'Copy URI' menu items to the editor menu when
the word under the cursor looks like a URI. 'Open URI' uses the browser
command configured in Geany to open it.
  * Tasks: The tasks plugin goes through a file being edited and picks out
lines with "TODO" or "FIXME" in them. It collects the text after those words
and puts them in a new "Tasks" tab in the message window. Clicking on a task
in that tab takes you to the line in the file where the task was defined.
  * Systray: Adds a status icon to the notification area (systray) and
provides a simple popup menu with some basic actions. It can also be used
to quickly show and hide the Geany main window.
 .
 Geany is a small and lightweight integrated development environment using the
 Gtk+ toolkit.
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 870...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - 

Bug#869541: marked as done (lintian warns both with and without autotools-dev build-dep)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#869541: fixed in lintian 2.5.53
has caused the Debian Bug report #869541,
regarding lintian warns both with and without autotools-dev build-dep
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.)


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

I added calls to dh_autotools-dev_{update,restore}config to the debian/rules
for vile* in order to update/restore the config.guess/config.sub.  I added a
versioned build-dependency for the version of autotools-dev which added these
commands:

  autotools-dev (>= 20100122.1)

lintian issued the folowing warning:

  W: vile source: useless-autoreconf-build-depends autotools-dev

If I remove the dependency, lintian then gives the error:

  E: vile source: missing-build-dependency-for-dh_-command 
dh_autotools-dev_restoreconfig => autotools-dev

* https://anonscm.debian.org/gitweb/?p=collab-maint/vile.git
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 869...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a 

Bug#869587: marked as done (lintian: false positive for unconditional-use-of-dpkg-statoverride)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#869587: fixed in lintian 2.5.53
has caused the Debian Bug report #869587,
regarding lintian: false positive for unconditional-use-of-dpkg-statoverride
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.)


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

Hi,

Not quite sure why, but am seeing in src:redis:

 29 if ! dpkg-statoverride --list ${CONFFILE} >/dev/null 2>&1
 30 then
 31 dpkg-statoverride --update --add ${USER} ${GROUP} 
640 ${CONFFILE}
 32 fi

... resulting in:

 W: redis-server: unconditional-use-of-dpkg-statoverride postinst:31


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 869...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the binary-file-built-without-LFS-support tag.
   (Closes: #874078)
   * checks/changes.{pm,desc}:
 + [CL] Ignore DFSG-repacked packages when checking for upstream
   source tarball signatures as they will never match by definition.
   (Closes: #871957)
 + [CL] Downgrade severity of orig-tarball-missing-upstream-signature
   from "E:" to "W:" as many common tools do not make including the
   signatures easy enough right now.  (Closes: #870722, #870069)
 + [CL] Expand the explanation of the
   orig-tarball-missing-upstream-signature tag to include the location
   of where dpkg-source will look. Thanks to Theodore Ts'o for the
   suggestion.
   * checks/copyright-file.pm:
 + [CL] Address a number of issues in copyright-year-in-future:
   - Prevent false positives in 

Bug#868897: marked as done (en_US help uses British spelling)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#868897: fixed in lintian 2.5.53
has caused the Debian Bug report #868897,
regarding en_US help uses British spelling
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.)


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

Package: lintian
Version: 2.5.51
Severity: minor

A British-spelled word, "Behaviour", occurs in Lintian's command line 
help and man page even when the locale is explicitly set to en_US.



$ LANG=en_US.UTF-8 lintian | grep Behaviour
Behaviour options:

$ LANG=en_US.UTF-8 man 1 lintian|grep Behaviour
  Behaviour options for lintian.


The fix is trivial, nonetheless a patch is attached.
diff -urN lintian-2.5.51_/commands/lintian.pm lintian-2.5.51/commands/lintian.pm
--- lintian-2.5.51_/commands/lintian.pm	2017-07-19 21:41:08.900334847 +0700
+++ lintian-2.5.51/commands/lintian.pm	2017-07-19 21:41:51.515893173 +0700
@@ -164,7 +164,7 @@
 -q, --quiet   suppress all informational messages
 -v, --verbose verbose messages
 -V, --version display Lintian version and exit
-Behaviour options:
+Behavior options:
 --color never/always/auto disable, enable, or enable color for TTY
 --default-display-level   reset the display level to the default
 --display-source Xrestrict displayed tags by source
diff -urN lintian-2.5.51_/man/lintian.pod.in lintian-2.5.51/man/lintian.pod.in
--- lintian-2.5.51_/man/lintian.pod.in	2017-07-19 21:41:08.824335637 +0700
+++ lintian-2.5.51/man/lintian.pod.in	2017-07-19 21:42:17.331626486 +0700
@@ -160,7 +160,7 @@
 
 =back
 
-Behaviour options for B.
+Behavior options for B.
 
 =over 4
 
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 868...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   - script-needs-depends-on-sensible-utils
   - script-uses-deprecated-nodejs-location
   - transitional-package-should-be-oldlibs-optional
   - unnecessary-testsuite-autopkgtest-header
   - vcs-browser-links-to-empty-view
 + Removed:
   - debug-package-should-be-priority-extra
   - missing-classpath
   - transitional-package-should-be-oldlibs-extra
 .
   * checks/apache2.pm:
 + [CL] Fix an apache2-unparsable-dependency false positive by allowing
   periods (".") in dependency names.  (Closes: #873701)
   * checks/binaries.pm:
 + [CL] Apply patches from Guillem Jover & Boud Roukema to improve the
   description of the 

Bug#869750: marked as done (lintian: fix for readelf parsing with binutils 2.29 on ppc64el)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:34:47 +
with message-id 
and subject line Bug#869750: fixed in lintian 2.5.53
has caused the Debian Bug report #869750,
regarding lintian: fix for readelf parsing with binutils 2.29 on ppc64el
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.)


-- 
869750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.52
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear maintainers,

In Ubuntu, lintian's autopkgtests now fail on ppc64el due to a test error,
which results from binutils 2.29 on ppc64el outputting symbols in a
different format; e.g. from the readelf -WltdVs output:

 3:  0 FUNCGLOBAL DEFAULT [: 8]   UND 
exit@GLIBC_2.17 (2)

(This appears to be a difference in the behavior of binutils' binary output
rather than a change in the behavior of readelf in reading the binary.)

The attached patch adjusts the regexp used for matching symbols to account
for the optional [ ...] field.  With this change, the
autopkgtest passes again on ppc64el.

Please consider applying this patch in Debian.  I have not tested on
Debian/ppc64el, but if the issue exists there also with binutils 2.29-1,
then the severity of this bug should arguably be raised to serious.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru lintian-2.5.52/helpers/coll/objdump-info-helper 
lintian-2.5.52ubuntu1/helpers/coll/objdump-info-helper
--- lintian-2.5.52/helpers/coll/objdump-info-helper 2017-06-17 
08:38:58.0 -0700
+++ lintian-2.5.52ubuntu1/helpers/coll/objdump-info-helper  2017-07-25 
22:02:58.0 -0700
@@ -200,7 +200,7 @@
 push @symbol_versions, $verstring;
 }
 } elsif ($line
-=~ m/^\s*(\d+):\s*[0-9a-f]+\s+\d+\s+(?:(?:\S+\s+){3})(\S+)\s+(.*)\Z/
+=~ 
m/^\s*(\d+):\s*[0-9a-f]+\s+\d+\s+(?:(?:\S+\s+){3})(?:\[.*\]\s+)(\S+)\s+(.*)\Z/
 and $section eq 'DS') {
 # We (sometimes) need to read the "Version symbols section" first to
 # use this data and readelf tends to print after this section, so
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.53

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 869...@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: Wed, 20 Sep 2017 09:25:06 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.53
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 681713 762956 779675 814599 835120 847144 849622 857123 865531 868897 
869541 869587 869750 869788 870069 870199 870272 870649 870681 870722 870730 
870758 870822 871575 871767 871957 872042 872076 872611 872843 873096 873211 
873323 873434 873458 873701 873702 874078 874121 874381 875509 875985 876003
Changes:
 lintian (2.5.53) unstable; urgency=medium
 .
   The "we are all Perl developers now" release.
 .
   * Summary of tag changes:
 + Added:
   - alternatively-build-depends-on-python-sphinx-and-python3-sphinx
   - build-depends-on-python-sphinx-only
   - dependency-on-python-version-marked-for-end-of-life
   - maintainer-script-interpreter
   - missing-call-to-dpkg-maintscript-helper
   - node-package-install-in-nodejs-rootdir
   - override-file-in-wrong-package
   - package-installs-java-bytecode
   - python-foo-but-no-python3-foo
   

Bug#869022: marked as done (guice: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 19:15:31 +0100
with message-id <20170920181531.ga19...@alice.nomadium.lan>
and subject line Re: guice: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
has caused the Debian Bug report #869022,
regarding guice: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
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.)


-- 
869022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guice
Version: 4.0-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibguice-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] The project com.google.inject:guice-parent:pom:4.0 uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Google Guice
> [INFO] Google Guice - Bill of Materials
> [INFO] Google Guice - Core Library
> [INFO] Google Guice - Extensions
> [INFO] Google Guice - Extensions - AssistedInject
> [INFO] Google Guice - Extensions - MultiBindings
> [INFO] Google Guice - Extensions - Grapher
> [INFO] Google Guice - Extensions - JMX
> [INFO] Google Guice - Extensions - JNDI
> [INFO] Google Guice - Extensions - Servlet
> [INFO] Google Guice - Extensions - Spring
> [INFO] Google Guice - Extensions - ThrowingProviders
> [INFO] 
> [INFO] 
> 
> [INFO] Building Google Guice 4.0
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-javadoc-plugin:2.10.4:jar 
> (default) @ guice-parent ---
> [INFO] Not executing Javadoc as the project is not a Java 
> classpath-capable package
> [INFO] 
> [INFO] --- maven-javadoc-plugin:2.10.4:jar 
> (default-cli) @ guice-parent ---
> [INFO] Not executing Javadoc as the project is not a Java 
> classpath-capable package
> [INFO] 
> [INFO] 
> 
> [INFO] Building Google Guice - Bill of Materials 4.0
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-javadoc-plugin:2.10.4:jar 
> (default) @ guice-bom ---
> [INFO] Not executing Javadoc as the project is not 

Bug#874972: marked as done ([klatexformula] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 17:11:41 +0200
with message-id <24690485.XSWhZ5zyHY@guymontag>
and subject line Re: Bug#874972: [klatexformula] Future Qt4 removal from Buster
has caused the Debian Bug report #874972,
regarding [klatexformula] Future Qt4 removal from Buster
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.)


-- 
874972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: klatexformula
Version: 3.3.0~beta-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: klatexformula
Version: 4.0.0-1

The new upstream release is based on Qt5.

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

Bug#810428: marked as done (lcdproc: please switch to libusb 1.0)

[Debian Bug Tracking System]

Your message dated Wed, 20 Sep 2017 15:55:24 +
with message-id 
and subject line Bug#810428: fixed in lcdproc 0.5.9-2
has caused the Debian Bug report #810428,
regarding lcdproc: please switch to libusb 1.0
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.)


-- 
810428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lcdproc
Version: 0.5.7-4
Severity: wishlist

Dear Maintainer,

lcdproc has a build-depends on libusb-dev. A few years ago upstream
has released a new major version libusb 1.0 with a different API which
aims to fix design deficiencies with USB 2.0 and 3.0 in mind.

The old libusb 0.1 package is not supported upstream anymore and should
be considered deprecated.

If lcdproc supports the new libusb 1.0 library, please consider
switching the build-depends from libusb-dev to libusb-1.0-0-dev. If not
please inform upstream that porting the software to the new API is
recommended.

Thanks,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- End Message ---
--- Begin Message ---
Source: lcdproc
Source-Version: 0.5.9-2

We believe that the bug you reported is fixed in the latest version of
lcdproc, 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 810...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated lcdproc 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: SHA512

Format: 1.8
Date: Tue, 19 Sep 2017 12:15:53 +0200
Source: lcdproc
Binary: lcdproc lcdproc-extra-drivers lcdproc-dbg
Architecture: source
Version: 0.5.9-2
Distribution: unstable
Urgency: medium
Maintainer: Dominique Dumont 
Changed-By: Dominique Dumont 
Description:
 lcdproc- LCD display driver daemon and clients
 lcdproc-dbg - debugging symbols for lcdproc
 lcdproc-extra-drivers - extra drivers for the LCD display driver daemon
Closes: 810428
Changes:
 lcdproc (0.5.9-2) unstable; urgency=medium
 .
   * control: rm build-dep on libftdi-dev and libusb-dev (Closes: #810428)
 As a consequence, the IOWarrior i2500vfd lis ula200 and shuttleVFD
 drivers are no longer delivered.
Checksums-Sha1:
 a20c5c8a6dfaca924210c3701600c8e5354b8c49 2578 lcdproc_0.5.9-2.dsc
 8a5e2d3f9e768ae8617e06f2280fd31c4068242d 18656 lcdproc_0.5.9-2.debian.tar.xz
 09e7484d9efabde685901a651dde9f4330fbdcc4 8199 lcdproc_0.5.9-2_source.buildinfo
Checksums-Sha256:
 2e993b49371d5fd050652469d5ef077d4797cac51371d0a057da0b6d79589f32 2578 
lcdproc_0.5.9-2.dsc
 6bee709f548b60d181e9c8dd03431914be90d95ff8a6703a8e45efa71ae4efc5 18656 
lcdproc_0.5.9-2.debian.tar.xz
 3541b1e907a89d92657fefb88865395e05dfdd78de923cba25a73f8ee16abb63 8199 
lcdproc_0.5.9-2_source.buildinfo
Files:
 5e7c45ab02e23e646a13f9f5ec364ef3 2578 utils extra lcdproc_0.5.9-2.dsc
 ecdb86fe90a1ba39b15b830235221091 18656 utils extra 
lcdproc_0.5.9-2.debian.tar.xz
 b54b872f9affd4c203d1c7fab48498ed 8199 utils extra 
lcdproc_0.5.9-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAlnChN8ACgkQwx9P2Umr
K2z0jg//XezhmIVldxoJWWkQlmNt2z5Lnkjv8Tkyx7Ofg2+V9qba54/q3bN1oYLs
GzkL6AFiJwGtvaxxsRRWm1W5v9gvp8cdMlfbdKQ73nrgQluHta3onmY3K+X7/3zM
F8zo3wC0dyyUJfwH1Dfou3fwDdXWrTyYxOLs3/cZnh25j82JyLRPNXv7gilu57XQ
fBLeVe4gpGc88xNEpfO2488Tst/dj0ow1sJaHdjCaXlTnJXN6P+99rfykeziSRA0
SI3W1Yj4yPNS0fTPhis4yycecEitGEche04B7d7GNu6MhP15AfgHOq/pTW91Sd8i
FkcWK1g6M8mh9iCENXJelSpsKjzq1wx6QtYcCDx+y1rz2YezhcjQ72EAYVEH5Hy/
WkLRfNpvexDAaAd+oI32V+ZfuxO04rhM1RYta0QGS1YC9gOxntsW6pdeeVbmiXm2
cuXpdHd+m41z/NTVHjF7vun+/SfqdecXiEo8iKOuKIwm42h6TQ6vyJuFZqNXFfYT
sbKTQlglOYcfz/o9pGKonVlXIoEGFeifrRFOm3qIBD9syi9t5b3mDv0EGXWNG1AI
4+sAknwnM9V1g26vs3J8eUhq6XvcxUMwNmj9lrJpAorUNywoQYVyDZ0Tf0t5+PXK
KYdqXu3TkNhEUpW43l+Zcw0o61H14FxnmA1sqNhfl653xGLXzyw=
=Zbkj
-END PGP SIGNATURE End Message ---