Bug#701222: marked as done (RFP: dnsgraph -- trace and graph all resolution paths for DNS names)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 04:20:11 +
with message-id 
and subject line closing RFP: dnsgraph -- trace and graph all resolution paths 
for DNS names
has caused the Debian Bug report #701222,
regarding RFP: dnsgraph -- trace and graph all resolution paths for DNS names
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.)


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

* Package name: dnsgraph
  Upstream Author : Dennis Kaarsemaker
* URL : https://github.com/seveas/dnsgraph
* License : MIT
  Programming Lang: Python
  Description : trace and graph all resolution paths for DNS names

dnsgraph depends on python-whelk by the same author:

https://github.com/seveas/whelk

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
RFP 701222 has no visible progress for a long time, so closing.--- End Message ---

Bug#881985: marked as done (request-tracker4: Correctly set RT version in configure if a Debian epoch is used)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 00:08:11 +
with message-id 
and subject line Bug#881985: fixed in request-tracker4 4.4.2-2
has caused the Debian Bug report #881985,
regarding request-tracker4: Correctly set RT version in configure if a Debian 
epoch is used
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.)


-- 
881985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: request-tracker4
Severity: minor
Tags: patch

Dear Maintainer,

I need to build a custom RT package to include some custom patches that
haven't been accepted upstream yet. When I do that, I set an epoch on
the Debian version to ensure that we don't accidentally upgrade to a
newer version from Debian. With the 4.4.x packages this has caused
RT to think the version is 0.0.0, which causes a bunch of issues.

The attached patch modifies debian/patches/debian_version.diff to strip
off an epoch, if present, and the Debian patch level from the version
presented by RT. If you want to keep the Debian patch level, then
remove
the first call to sed.

I also note that the same diff currently sets the date to 2016 in the
footer.

Cheers,
Andrew

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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- 
Andrew Ruthven, Wellington, New Zealand
MIITP

At work: andrew.ruth...@catalyst.net.nz
At home: and...@etc.gen.nz
Cloud  : NZs only real cloud - https://catalyst.net.nz/cloud
GPG fpr: C603 FC4E 600F 1CEC D1C8  D97C 4B53 D931 E4D3 E863
LCA2018: Just a little bit of history repeating - http://linux.conf.au--- debian/patches/debianize_version.diff   2017-08-29 19:05:39.0 
+
+++ ../rt-patches/debianize_version.diff2017-11-14 23:42:45.762257327 
+
@@ -6,6 +6,9 @@
 Also make clear in the web interface that this version number is from
 Debian.
 
+Updated to strip the epoch and Debian patch off the version. Commands
+taken from /usr/share/dpkg/pkg-info.mk .
+
 Patch-Name: debianize_version.diff
 ---
  configure.ac   | 8 
@@ -21,7 +24,7 @@
  dnl Setup autoconf
  AC_PREREQ([2.53])
 -AC_INIT(RT, m4_esyscmd([( git describe --tags || cat ./.tag 2> /dev/null || 
echo "rt-3.9.EXPORTED" )| tr -d "\n"]), [rt-b...@bestpractical.com])
-+AC_INIT(RT, m4_esyscmd([( dpkg-parsechangelog -SVersion )| tr -d "\n"]), 
[https://www.debian.org/Bugs/Reporting])
++AC_INIT(RT, m4_esyscmd([( dpkg-parsechangelog -SVersion | sed -e 
's/-[^-]*$//' | sed -e 's/^[0-9]*://' )| tr -d "\n"]), 
[https://www.debian.org/Bugs/Reporting])
  AC_CONFIG_SRCDIR([lib/RT.pm])
  
  dnl Save our incant early since $@ gets overwritten by some macros.
--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.4.2-2

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated request-tracker4 
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, 08 Apr 2018 00:15:44 +0100
Source: request-tracker4
Binary: request-tracker4 rt4-clients rt4-standalone rt4-fcgi rt4-apache2 
rt4-db-postgresql rt4-db-mysql rt4-db-sqlite rt4-doc-html
Architecture: source
Version: 4.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: Dominic Hargreaves 
Description:
 request-tracker4 - extensible trouble-ticket tracking system
 rt4-apache2 - Apache 2 specific files for request-tracker4
 rt4-clients - mail gateway and command-line interface to request-tracker4
 rt4-db-mysql - MySQL database backend for request-tracker4
 

Bug#881984: marked as done (request-tracker4: Modify debian/rules to allow rebuilding)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 00:08:11 +
with message-id 
and subject line Bug#881984: fixed in request-tracker4 4.4.2-2
has caused the Debian Bug report #881984,
regarding request-tracker4: Modify debian/rules to allow rebuilding
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.)


-- 
881984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: request-tracker4
Version: 4.4.1
Severity: minor
Tags: patch

Dear Maintainer,

When retrying to rebuild the .debs for RT, I found that a few
generated files and directories we either not correctly removed, or
not even attemped to be removed. Also, if the configure wasn't 
present, then building failed.

The attached patch to debian/rules fixes these issues.

Cheers,
Andrew

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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- 
Andrew Ruthven, Wellington, New Zealand
MIITP

At work: andrew.ruth...@catalyst.net.nz
At home: and...@etc.gen.nz
Cloud  : NZs only real cloud - https://catalyst.net.nz/cloud
GPG fpr: C603 FC4E 600F 1CEC D1C8  D97C 4B53 D931 E4D3 E863
LCA2018: Just a little bit of history repeating - http://linux.conf.au--- debian/rules2017-08-29 19:05:39.0 +
+++ ../rules2017-11-15 00:45:17.548156696 +
@@ -23,6 +23,7 @@
 build-arch: build-stamp
 build-indep: build-stamp
 
+configure: build-stamp
 build-stamp: configure
dh_testdir
 
@@ -86,7 +87,8 @@
# Restore shipped generated files
-find bak -type f -print | sed -e 's/^bak\///' | while read f; do mv 
bak/$$f $$f; done
-rm -rf bak
-   rm -f config.status config.log config.pld bak html-docs
+   rm -rf html-docs
+   rm -f config.status config.log config.pld bak t/tmp/ports 
t/data/gnupg/keyrings/random_seed
dh_autoreconf_clean
dh_clean build-stamp
 
@@ -141,6 +143,9 @@
find $(RT_PKG)/usr/share/$(RT)/lib -type f -name '*.in' -print0 | xargs 
-0 --no-run-if-empty rm 
rm -f $(RT_PKG)/usr/share/$(RT)/etc/upgrade/*.in

+   # Remove a test file
+   rm -f .prove
+
# This is generated by the maintainer scripts
$(RM) $(RT_PKG)/usr/share/$(RT)/etc/RT_SiteConfig.pm
 
--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.4.2-2

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated request-tracker4 
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, 08 Apr 2018 00:15:44 +0100
Source: request-tracker4
Binary: request-tracker4 rt4-clients rt4-standalone rt4-fcgi rt4-apache2 
rt4-db-postgresql rt4-db-mysql rt4-db-sqlite rt4-doc-html
Architecture: source
Version: 4.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: Dominic Hargreaves 
Description:
 request-tracker4 - extensible trouble-ticket tracking system
 rt4-apache2 - Apache 2 specific files for request-tracker4
 rt4-clients - mail gateway and command-line interface to request-tracker4
 rt4-db-mysql - MySQL database backend for request-tracker4
 rt4-db-postgresql - PostgreSQL database backend for request-tracker4
 rt4-db-sqlite - SQLite database backend for request-tracker4
 rt4-doc-html - HTML documentation for request-tracker4
 rt4-fcgi   - External FastCGI support for request-tracker4
 rt4-standalone - Standalone web server support for request-tracker4
Closes: 881984 881985 883472
Changes:
 request-tracker4 (4.4.2-2) unstable; urgency=medium
 .
   

Bug#869382: marked as done (libwxgtk3.0-0: Drawing sample line test broken)

[Debian Bug Tracking System]

Your message dated Sun, 8 Apr 2018 11:26:02 +1200
with message-id <20180407232602.ga23...@survex.com>
and subject line Re: Bug#869382: libwxgtk3.0-0: Drawing sample line test broken
has caused the Debian Bug report #869382,
regarding libwxgtk3.0-0: Drawing sample line test broken
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.)


-- 
869382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwxgtk3.0-0v5
Version: 3.0.2+dfsg-4
Severity: normal
File: libwxgtk3.0-0

Dear Maintainer,

I was trying to use lines in my application which uses wxGTK. I've found that 
in the drawing sample shipped with wxGTK, the lines screen doesn't seem to give 
the correct visual output.

In the "Testing lines of width 0", the "dot/short dash/long dash/dot dash" 
lines appear visually identical. The same is true for the width 1 test.

In the width 2 testh however, the lines start ot be visually distinct.

It looks like the mapping between wxGTK and the gtk drawing code doesn't quite 
tee up.

To reproduce this install the wx3.0-examples package, navigate to
/usr/share/doc/wx3.0-examples/examples/samples, then copy out the drawing 
example to somewhere writeable, eg ~/tmp/wx/drawing. You need to copy 
sample.xpm as well, into the immediate parent path (eg ~/tmp/wx/). 

Then go into ~/tmp/wx/drawing/, and execute make to build the example. Now 
launch the example (./drawing), then in the file menu, select "Lines screen". 
Observe the incorrectly drawn lines.

I'm unsure if this is an upstream bug or not.

Thanks!


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

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

Versions of packages libwxgtk3.0-0v5:amd64 depends on:
ii  libc6 2.24-11
ii  libcairo2 1.14.8-1
ii  libgcc1   1:6.3.0-18
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglib2.0-0  2.50.3-2
ii  libgtk2.0-0   2.24.31-2
ii  libjpeg62-turbo   1:1.5.1-2
ii  libnotify40.7.7-2
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libpng16-16   1.6.28-1
ii  libsm62:1.2.2-1+b3
ii  libstdc++66.3.0-18
ii  libtiff5  4.0.8-2
ii  libwxbase3.0-0v5  3.0.2+dfsg-4
ii  libx11-6  2:1.6.4-3
ii  libxxf86vm1   1:1.1.4-1+b2

libwxgtk3.0-0v5:amd64 recommends no packages.

libwxgtk3.0-0v5:amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed 3.0.4+dfsg-3

On Mon, Jul 24, 2017 at 01:09:32PM +1200, Olly Betts wrote:
> Control: tags -1 upstream
> 
> On Sun, Jul 23, 2017 at 06:10:52PM +1200, Olly Betts wrote:
> > Thanks - I can reproduce this with packages based on 3.0.3.1 which I'm
> > working on (not yet uploaded).
> > 
> > On Sat, Jul 22, 2017 at 11:05:09PM +0100, D Haley wrote:
> > > I'm unsure if this is an upstream bug or not.
> > 
> > I'd imagine it is - we aren't patching anything in this area.
> > 
> > Testing with upstream git master using GTK3, the line patterns look
> > right there.  So this may be fixed upstream but need backporting (or
> > have been backported since 3.0.3.1).  Or it may be a GTK2 vs GTK3
> > bug - I'll try to narrow it down later.
> 
> I've tests all four comibinations, and it's specific to GTK2, and works
> with GTK3.  We're considering a switch to GTK3 for buster, which looks
> like it would fix this.

I've just retested with the latest upload (3.0.4+dfsg-3) and the width 0
lines which are meant to have different patterns now do, so it looks
like this was fixed upstream by 3.0.4 (since I tested 3.0.3.1 above).

Marking as fixed in the version I actually tested, but likely it was
fixed in 3.0.4+dfsg-1.

There are also GTK3 packages now, which we're encouraging people to
migrate to.

Cheers,
Olly--- End Message ---

Bug#883472: marked as done (request-tracker4: rt-externalize-attachments cron job should not be enabled by default)

[Debian Bug Tracking System]

Your message dated Sun, 08 Apr 2018 00:08:11 +
with message-id 
and subject line Bug#883472: fixed in request-tracker4 4.4.2-2
has caused the Debian Bug report #883472,
regarding request-tracker4: rt-externalize-attachments cron job should not be 
enabled by default
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.)


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

In RT 4.4, the rt-externalize-attachments cronjob was added to the list
of cronjobs to set up (if the user asked for cronjobs to be set up
automatically).

Unlike the other cronjobs, this one only works if additional configuration
to use external storage has been put in place, and produces a critical
error otherwise:

[16967] [Fri Dec  1 00:00:04 2017] [critical]: %ExternalStorage is not 
configured (/usr/share/request-tracker4/lib/RT.pm:394)
%ExternalStorage is not configured

This cron job should not be enabled by default, but should be left
commented out as a hint to the user.
--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.4.2-2

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated request-tracker4 
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, 08 Apr 2018 00:15:44 +0100
Source: request-tracker4
Binary: request-tracker4 rt4-clients rt4-standalone rt4-fcgi rt4-apache2 
rt4-db-postgresql rt4-db-mysql rt4-db-sqlite rt4-doc-html
Architecture: source
Version: 4.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Request Tracker Group 

Changed-By: Dominic Hargreaves 
Description:
 request-tracker4 - extensible trouble-ticket tracking system
 rt4-apache2 - Apache 2 specific files for request-tracker4
 rt4-clients - mail gateway and command-line interface to request-tracker4
 rt4-db-mysql - MySQL database backend for request-tracker4
 rt4-db-postgresql - PostgreSQL database backend for request-tracker4
 rt4-db-sqlite - SQLite database backend for request-tracker4
 rt4-doc-html - HTML documentation for request-tracker4
 rt4-fcgi   - External FastCGI support for request-tracker4
 rt4-standalone - Standalone web server support for request-tracker4
Closes: 881984 881985 883472
Changes:
 request-tracker4 (4.4.2-2) unstable; urgency=medium
 .
   * Don't break RT when epochs are used in the Debian version. Thanks
 to Andrew Ruthven for the patch (Closes: #881985)
   * Don't enable rt-externalize-attachments cron job by default
 (Closes: #883472)
   * Update Vcs-* fields to point to Salsa
   * Update clean target to work correctly, and ensure configure is run.
 Thanks to Andrew Ruthven for the patch (Closes: #881984)
   * Update Standards-Version (no changes)
Checksums-Sha1:
 16e381b63fb9a2abfc4183e28b9b3706b677468d 5461 request-tracker4_4.4.2-2.dsc
 79d22dd1f157445b554b03e9488e075032ea35dc 77880 
request-tracker4_4.4.2-2.debian.tar.xz
Checksums-Sha256:
 3e00a5215ba47b1ee9f69df686ea035b085f8191619c7efe926fb6696efd2c1d 5461 
request-tracker4_4.4.2-2.dsc
 20fc807cf6c8b2e6dba53d656a71c415c18e02c2a6f1d837566f3db917f23145 77880 
request-tracker4_4.4.2-2.debian.tar.xz
Files:
 74c17e5765f38c916e1a990e3ab9753b 5461 misc optional 
request-tracker4_4.4.2-2.dsc
 06b66523bc4caa0df5ff36d552b7d3ff 77880 misc optional 
request-tracker4_4.4.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJayVjuAAoJEMAFfnFNaU+yRYIP/j2SXKFI+rsurIgq1c7uqPij
eAGWndX7izJ/kVcWQClHa/Gi3IE8dBLpoThyUq1IMdXF3c0iYMn9/U9YIcrjuRhy
cWDdGo9Rj3CKS18BJMHZhz0LbgH/iIMM8A3CxmCfxEjkn9VM66lQvAuoekWk38Pp
fb5vU/ZcYfaH4blUpVz0kLbmUoxoo54wdEio0KFodR8vodZ7Fu8XMVBmkumCOpaA
1fubEmVBOxoz22yM3jPvbqhcT0i/hWpJVD6uF+m9w+IezvBT8tdDNTGh7c3+gQ/5

Bug#893525: marked as done (CVE-2018-1000097)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 23:02:09 +
with message-id 
and subject line Bug#893525: fixed in sharutils 1:4.15.2-2+deb9u1
has caused the Debian Bug report #893525,
regarding CVE-2018-197
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.)


-- 
893525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sharutils
Severity: grave
Tags: security

This has been assigned CVE-2018-197:
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html

Proposed patch at:
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg5.html

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: sharutils
Source-Version: 1:4.15.2-2+deb9u1

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated sharutils 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, 04 Apr 2018 19:46:18 +0200
Source: sharutils
Binary: sharutils sharutils-doc
Architecture: source
Version: 1:4.15.2-2+deb9u1
Distribution: stretch-security
Urgency: medium
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Description:
 sharutils  - shar, unshar, uuencode, uudecode
 sharutils-doc - Documentation for GNU sharutils
Closes: 893525
Changes:
 sharutils (1:4.15.2-2+deb9u1) stretch-security; urgency=medium
 .
   * Apply patch from Petr Pisar to fix heap buffer overflow in unshar.
 This is CVE-2018-197. Closes: #893525.
Checksums-Sha1:
 a6e0d7650346b779e2c344133d57d5cd4da3d67d 1494 sharutils_4.15.2-2+deb9u1.dsc
 250377131bcf7a081f066ed0f9c51a0b7e0b0c04 1122476 sharutils_4.15.2.orig.tar.xz
 11c8d8cbacdbd5a851e42f85efa584ad70a95523 7784 
sharutils_4.15.2-2+deb9u1.debian.tar.xz
 1c1c9f87a17b55871ab2c8c75157bf6786830ff9 5525 
sharutils_4.15.2-2+deb9u1_source.buildinfo
Checksums-Sha256:
 2ed67aadd23af01243c5152ffad01710a2008ee60ab0a1a3d2f899f5ce29d071 1494 
sharutils_4.15.2-2+deb9u1.dsc
 2b05cff7de5d7b646dc1669bc36c35fdac02ac6ae4b6c19cb3340d87ec553a9a 1122476 
sharutils_4.15.2.orig.tar.xz
 78c3acce44d7d087953eb8ff383f8f894e35f049ed9648c9ef7e389935ff233f 7784 
sharutils_4.15.2-2+deb9u1.debian.tar.xz
 a0289d008fbab956057bbd9a54012400a39b2f7f7ab1f914d56acbd75c269aea 5525 
sharutils_4.15.2-2+deb9u1_source.buildinfo
Files:
 0d091caea0cb8addb727af32c172f482 1494 utils optional 
sharutils_4.15.2-2+deb9u1.dsc
 5975ce21da36491d7aa6dc2b0d9788e0 1122476 utils optional 
sharutils_4.15.2.orig.tar.xz
 2f47f5632d3fee81fd925c9cf2786bcc 7784 utils optional 
sharutils_4.15.2-2+deb9u1.debian.tar.xz
 2326da64be87a053d334698a1ccc5305 5525 utils optional 
sharutils_4.15.2-2+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAlrFEWYACgkQQc5/C58b
izJVWQf/Zh/QKCfuyETYlxoMmHROnvQVT16cZ0cHV7cNESjmcxH0DfN02OWotbcF
qKF9Eq5enLhPo7cpiForBzq2RGqrbQmQzvskYCU6geTSznM7rLLawmLp58Eb00oA
nyo7fgr5kMuR25MCUK07zYX91PLn8Rx985IZUq7WUv9wIE9qXclutcMeq2L1vIip
/vUUIoz6KiTLRB4e3K4MtIRP/zoQjLdsnnuLL93vGsgphzic0EmeW+iK+CzKvgeL
VIILWm6mooIrr7GtNj46GkDgmwRb1V4raGhxoquckZjhr5q5lvu4QhmgrmcIZwYF
Kqorerji2oRZKzCR7EKwe9KbEoaiWQ==
=/dRH
-END PGP SIGNATURE End Message ---

Bug#895034: marked as done (wordpress: versions 4.9.4 and earlier are affected by three security issues)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 22:53:41 +
with message-id 
and subject line Bug#895034: fixed in wordpress 4.9.5+dfsg1-1
has caused the Debian Bug report #895034,
regarding wordpress: versions 4.9.4 and earlier are affected by three security 
issues
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.)


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

WordPress 4.9.5 fixes 3 security issues:
1) Don't treat localhost as same host by default.
2) Use safe redirects when redirecting the login page if SSL is forced.
3) Make sure the version string is correctly escaped for use in generator tags.

The patches are:
1) 42894 - https://core.trac.wordpress.org/changeset/42894
2) 42892 - https://core.trac.wordpress.org/changeset/42892
3) 42893 - https://core.trac.wordpress.org/changeset/42893

Sid, Buster, Stretch and Jessie all have these issues.

 - Craig

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 4.9.5+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
wordpress, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress 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, 08 Apr 2018 08:11:40 +1000
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentysixteen 
wordpress-theme-twentyfifteen wordpress-theme-twentyseventeen
Architecture: source all
Version: 4.9.5+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files
 wordpress-theme-twentyseventeen - weblog manager - twentyseventeen theme files
 wordpress-theme-twentysixteen - weblog manager - twentysixteen theme files
Closes: 895034
Changes:
 wordpress (4.9.5+dfsg1-1) unstable; urgency=medium
 .
   * New upstream source, fixes 3 Security issues Closes: #895034
 - CVE-2018-TBA
   Don't treat localhost as same host by default.
 - CVE-2018-TBA
   Use safe redirects when redirecting login page if SSL is forced
 - CVE-2018-TBA
   Make sure version string is correctly escaped for use in
   generator tags
   * Update to standards version 4.1.4
   * Remove get-orig-source in rules and use uscan
Checksums-Sha1:
 a2616b03d3d40c3ce27ad1619c80ec8f1a911077 2518 wordpress_4.9.5+dfsg1-1.dsc
 760b6bcf4837bac8cbbd6c8c7ccc7c6c3568603a 6757484 
wordpress_4.9.5+dfsg1.orig.tar.xz
 ca91f692d6e1443760288ea4b2534b27ba9be475 6779144 
wordpress_4.9.5+dfsg1-1.debian.tar.xz
 159dd12e1099403c26920d361a8a3a357d051a9c 4381856 
wordpress-l10n_4.9.5+dfsg1-1_all.deb
 bb021a1aa7c9590e1f763c176acd5c777ffc5d36 701108 
wordpress-theme-twentyfifteen_4.9.5+dfsg1-1_all.deb
 af62dd94db2f056413bd067915478e0edfbeb030 941908 
wordpress-theme-twentyseventeen_4.9.5+dfsg1-1_all.deb
 7f7ffd71e02321bb34d364514bbaa6a2e9001ae2 589612 
wordpress-theme-twentysixteen_4.9.5+dfsg1-1_all.deb
 93f921d2356274a20cf196c36b2e3d0ba184eb23 4503936 
wordpress_4.9.5+dfsg1-1_all.deb
 2195b52a1343ee5eee9c91f50df03755d4e401d3 7331 
wordpress_4.9.5+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 3208965666884b9886ad821b457da678b75a8863568ed5031b4bb61eac4d5f69 2518 
wordpress_4.9.5+dfsg1-1.dsc
 7db44a17f112c0955328b9051d3299449c86dcb706370283627e14912722a1ab 

Bug#888406: marked as done (qtcharts-opensource-src FTCBFS: does not pass cross flags to qmake)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 22:51:15 +
with message-id 
and subject line Bug#888406: fixed in qtcharts-opensource-src 5.10.1-2
has caused the Debian Bug report #888406,
regarding qtcharts-opensource-src FTCBFS: does not pass cross flags to qmake
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.)


-- 
888406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtcharts-opensource-src
Version: 5.9.2-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

qtcharts-opensource-src fails to cross build from source, because it
doesn't pass cross flags (such as -specs) to qmake. The easiest way of
doing so is letting dh_auto_configure handle that. After doing so,
qtcharts-opensource-src cross builds successfully. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru qtcharts-opensource-src-5.9.2/debian/changelog 
qtcharts-opensource-src-5.9.2/debian/changelog
--- qtcharts-opensource-src-5.9.2/debian/changelog  2017-10-26 
22:49:05.0 +0200
+++ qtcharts-opensource-src-5.9.2/debian/changelog  2018-01-25 
06:14:03.0 +0100
@@ -1,3 +1,10 @@
+qtcharts-opensource-src (5.9.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 25 Jan 2018 06:14:03 +0100
+
 qtcharts-opensource-src (5.9.2-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru qtcharts-opensource-src-5.9.2/debian/rules 
qtcharts-opensource-src-5.9.2/debian/rules
--- qtcharts-opensource-src-5.9.2/debian/rules  2017-10-26 22:49:05.0 
+0200
+++ qtcharts-opensource-src-5.9.2/debian/rules  2018-01-25 06:13:56.0 
+0100
@@ -14,7 +14,7 @@
dh $@ --with pkgkde_symbolshelper
 
 override_dh_auto_configure:
-   qmake QT_BUILD_PARTS+=tests
+   dh_auto_configure -- QT_BUILD_PARTS+=tests
 
 override_dh_auto_build-indep:
dh_auto_build -- docs
--- End Message ---
--- Begin Message ---
Source: qtcharts-opensource-src
Source-Version: 5.10.1-2

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtcharts-opensource-src 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, 07 Apr 2018 17:39:50 -0300
Source: qtcharts-opensource-src
Binary: libqt5charts5 libqt5charts5-dev qml-module-qtcharts qtcharts5-examples 
qtcharts5-doc qtcharts5-doc-html
Architecture: source
Version: 5.10.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 libqt5charts5 - Qt charts shared library
 libqt5charts5-dev - Qt charts development files
 qml-module-qtcharts - Qt charts QML module
 qtcharts5-doc - Qt charts QCH documentation
 qtcharts5-doc-html - Qt charts HTML documentation
 qtcharts5-examples - Qt chart examples
Closes: 888406
Changes:
 qtcharts-opensource-src (5.10.1-2) unstable; urgency=medium
 .
   * Switch to using plain dh_auto_configure instead of calling qmake
 (Closes: #888406).
 - Bump debhelper dependency to 10.9.2, required to do the change.
   * Release to unstable.
Checksums-Sha1:
 9f333b7046d7502b42cd9efba3d617059de44b99 2819 
qtcharts-opensource-src_5.10.1-2.dsc
 0d43f8c4b2a869918ff91f1ba72675bc64e12bcf 24424 
qtcharts-opensource-src_5.10.1-2.debian.tar.xz
 34958d1addbdaaa85e5df662a872cea6473521e5 11619 
qtcharts-opensource-src_5.10.1-2_source.buildinfo
Checksums-Sha256:
 188f6ba3bb8001ce2ea38b4ac0e411a6e6ae09e7c5e5eb25d931e4be1113c092 2819 
qtcharts-opensource-src_5.10.1-2.dsc
 a917e13afecbf95f29d15ec7ac3b038cc83f8737c953216a65eba59873898de3 24424 
qtcharts-opensource-src_5.10.1-2.debian.tar.xz
 

Bug#894626: marked as done (libsnmp-perl: undefined symbol: netsnmp_ds_toggle_boolean)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 22:50:46 +
with message-id 
and subject line Bug#894626: fixed in net-snmp 5.7.3+dfsg-3
has caused the Debian Bug report #894626,
regarding libsnmp-perl: undefined symbol: netsnmp_ds_toggle_boolean
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.)


-- 
894626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsnmp-info-perl
Version: 3.53-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first noticed by ci.debian.net, libsnmp-info-perl fails to build,
aka has testsuite failures, since the upload of net-snmp
5.7.3+dfsg-2.

   dh_auto_test
perl Build test --verbose 1

#   Failed test 'use SNMP::Info;'
#   at t/00_load.t line 10.
# Tried to use 'SNMP::Info'.
# Error:  Can't load 
'/usr/lib/x86_64-linux-gnu/perl5/5.26/auto/NetSNMP/default_store/default_store.so'
 for module NetSNMP::default_store: 
/usr/lib/x86_64-linux-gnu/perl5/5.26/auto/NetSNMP/default_store/default_store.so:
 undefined symbol: netsnmp_ds_toggle_boolean at 
/usr/lib/x86_64-linux-gnu/perl/5.26/DynaLoader.pm line 187.
#  at /usr/lib/x86_64-linux-gnu/perl5/5.26/SNMP.pm line 19.
# Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl5/5.26/SNMP.pm 
line 19.
# BEGIN failed--compilation aborted at 
/usr/lib/x86_64-linux-gnu/perl5/5.26/SNMP.pm line 19.
# Compilation failed in require at 
/build/libsnmp-info-perl-3.54/blib/lib/SNMP/Info.pm line 16.
# BEGIN failed--compilation aborted at 
/build/libsnmp-info-perl-3.54/blib/lib/SNMP/Info.pm line 16.
# Compilation failed in require at t/00_load.t line 10.
# BEGIN failed--compilation aborted at t/00_load.t line 10.
Use of uninitialized value $SNMP::Info::VERSION in concatenation (.) or string 
at t/00_load.t line 13.
# Testing SNMP::Info , Perl 5.026001, /usr/bin/perl
# Looks like you failed 1 test of 1.
t/00_load.t .. 
1..1
not ok 1 - use SNMP::Info;
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests 

Test Summary Report
- ---
t/00_load.t (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=1, Tests=1,  0 wallclock secs ( 0.02 usr  0.01 sys +  0.05 cusr  0.02 
csys =  0.10 CPU)
Result: FAIL
Failed 1/1 test programs. 1/1 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 1
make: *** [debian/rules:4: build] Error 2


(Same for the new 3.54 upstream release.)


Cc'ing the net-snmp maintainers.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlrCURxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbc+g//QlD2gDEloX3J0yGDa7PyDxPgA2wyc2WOxQS2hDO981HdYEGUTSwJJNNc
+7Cuxxr4vAhCWlBkjleMdOWSwJEbrckq3URgyuTkHYH40A9JVZTctTTXFLlZonAw
oI6lG/bmNN+ci4Dg63ZDmbqLvVASTw5Y5+6vZ+EA8nzmG5Hyq5jH4VHKnJ4slm4q
mr/a94CnJmWdh6Fq9pQ3nOL7qFmbAikjxyRG4Gq5nqmvD4f3ENC9E2X3mBog9MaP
riPeceZIzOy51fXRdw6Wl9zTMqenY2Jkjha5NA4UvasNJ2UvNVG4woyExT+v/zhR
wJ4bjsth0IW5x5zVpWJBYa57NbBr+W4BB62McmXvlzhbXbGbOIAJXGfZh+70Ps6i
tvMPvahDUokJeC/k587Noqr+m/YoJjDtMGU38qSFEVh0sioC2DidVfa2syIZAEOy
NIipYc4JKNfV0JrdKxUMGgz5EBX2IqwzIH39FnbvJQ4bT9B0wfuIjlbzFH4lrv2M
4k97qTfVJ6leUkzhXvGX/ps0pGpHxHDULVNU8bBQVsQ4G1lfPcaWWHwJs5dbsPVf
PZOgZA5m2Ld3uUhUeplTTWmD4EOD97RqX0Uqaz5J7oURa8ndq050LORqpNMnIZGA
3KCokAqAEtr4pYbESZd4QJnxi+w+LNc31Kqp+1YVKuoXuxKLs1M=
=7rkx
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: net-snmp
Source-Version: 5.7.3+dfsg-3

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated net-snmp 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, 04 Apr 2018 21:34:09 +1000
Source: net-snmp
Binary: snmpd snmptrapd snmp libsnmp-base libsnmp30 libsnmp30-dbg 

Bug#893525: marked as done (CVE-2018-1000097)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 22:48:07 +
with message-id 
and subject line Bug#893525: fixed in sharutils 1:4.14-2+deb8u1
has caused the Debian Bug report #893525,
regarding CVE-2018-197
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.)


-- 
893525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sharutils
Severity: grave
Tags: security

This has been assigned CVE-2018-197:
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html

Proposed patch at:
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg5.html

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: sharutils
Source-Version: 1:4.14-2+deb8u1

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated sharutils 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, 04 Apr 2018 19:49:02 +0200
Source: sharutils
Binary: sharutils sharutils-doc
Architecture: source all
Version: 1:4.14-2+deb8u1
Distribution: jessie-security
Urgency: medium
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Description:
 sharutils  - shar, unshar, uuencode, uudecode
 sharutils-doc - Documentation for GNU sharutils
Closes: 893525
Changes:
 sharutils (1:4.14-2+deb8u1) jessie-security; urgency=medium
 .
   * Apply patch from Petr Pisar to fix heap buffer overflow in unshar.
 This is CVE-2018-197. Closes: #893525.
Checksums-Sha1:
 c7fd75e63359185e79f7c23eedf14fa01314cf3f 1465 sharutils_4.14-2+deb8u1.dsc
 5d2d76caa6ee816202fb78395415bd863043d81b 1089052 sharutils_4.14.orig.tar.xz
 a69401184617dd8e3a6d03f30e37446446370ec6 6608 
sharutils_4.14-2+deb8u1.debian.tar.xz
 957347359889e5bf35735a05e84171f64d5aaa48 44234 
sharutils-doc_4.14-2+deb8u1_all.deb
Checksums-Sha256:
 eb7387cd9427c04d7caf5249db2c3b40eea4d31ef0fd8cbb3c8d7b31f04a4f4c 1465 
sharutils_4.14-2+deb8u1.dsc
 eae388efcf52aba0b081f09053189e0a3ad238561d88716b880b5c0676c07a0c 1089052 
sharutils_4.14.orig.tar.xz
 ecb9c2be1b57309681b5fd07cf2dff71a95e4d69114002a8bb1f9b5a66468b0b 6608 
sharutils_4.14-2+deb8u1.debian.tar.xz
 eaf3e411ac92819ae21ec2616edccdd0d0398b247f7adf20d3fe05307c7a8275 44234 
sharutils-doc_4.14-2+deb8u1_all.deb
Files:
 02b9d1f27b3e32c4ebf70a698dd2095d 1465 utils optional 
sharutils_4.14-2+deb8u1.dsc
 77ede22951bdb67279c6e78e79a04784 1089052 utils optional 
sharutils_4.14.orig.tar.xz
 e5580701d427c5c22a93f57e4c435349 6608 utils optional 
sharutils_4.14-2+deb8u1.debian.tar.xz
 3adaf0afb5e9793561b5d728e5518a60 44234 doc optional 
sharutils-doc_4.14-2+deb8u1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJaxRIVAAoJEEHOfwufG4sy8HMIAKgaeBEi0ADeIwKKZYl+bPWP
uTFB4stmC4oYUWvbFeNqG1GFl2+blBV1zjakaDaDCaICUURNj41R+FHkYnbUzgbE
9xvmGvJFr6WLrtfW6NfyHmTHe8LpdaSGhCJfOGR4sOluDHTd/Q6X6/NvUDPuGWUf
ljpLR4tf6Dx+6C4gwUGmQGkSkWg5rfRcTTEOCPwRGwBNh0NZm5lOgrj51DnFBNT5
HC7Gw+X7+i6UvG/YzXCRqbqMuBI1FOHPGOvLBfQqJE6XPU8KWogI/ynBTRaX57SI
u0QeWYSVer8Hwu6XcI7R1UPxBEnEGaEo1c1sJFRFBxssxJeXNvZamJFXQwETkVM=
=V9L7
-END PGP SIGNATURE End Message ---

Bug#894981: marked as done (nss: please package version 3.36)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 22:23:14 +
with message-id 
and subject line Bug#894981: fixed in nss 2:3.36-1
has caused the Debian Bug report #894981,
regarding nss: please package version 3.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.)


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

Dear Maintainer,

Dear Maintainer,

FF 60 and TB 60 need NSPR >= 3.36.
For now I switched the usage of the internal shipped source for working
on Thunderbird 60 betas but it's of course preferable to not use
embedded libraries.

Regards
Carsten

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: nss
Source-Version: 2:3.36-1

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated nss 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, 08 Apr 2018 06:53:15 +0900
Source: nss
Binary: libnss3 libnss3-tools libnss3-dev libnss3-dbg
Architecture: source
Version: 2:3.36-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Description:
 libnss3- Network Security Service libraries
 libnss3-dbg - Debugging symbols for the Network Security Service libraries
 libnss3-dev - Development files for the Network Security Service libraries
 libnss3-tools - Network Security Service tools
Closes: 894981
Changes:
 nss (2:3.36-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #894981.
Checksums-Sha1:
 b61823ab9189a28d6d7b4532b9a64e048b3b 2226 nss_3.36-1.dsc
 b4b86aad7406c9df1cdf9dd3752c84476e32df7c 23025578 nss_3.36.orig.tar.gz
 487bbb4d841310e57a32df0992737c4255439da7 24852 nss_3.36-1.debian.tar.xz
 4aa3b8cf3648b2a8f12c1a86ba29d11b29b44379 5940 nss_3.36-1_source.buildinfo
Checksums-Sha256:
 ba5ed8d95d1f5c6033c20a5960c298e744d059230d166618a971a29b3a8f6be3 2226 
nss_3.36-1.dsc
 a33cc7b8299b5ce3acf03f617c7896932ae26927ff9fb7c71c1b69a200c30095 23025578 
nss_3.36.orig.tar.gz
 2e6633aca85b63c603440e1cc57fa5e29d555909d7875186eeb5d848fe776a3c 24852 
nss_3.36-1.debian.tar.xz
 0cfc438e5fec3039df5c1c2afe28d6524966f1fbd0574d76854497090ddcceeb 5940 
nss_3.36-1_source.buildinfo
Files:
 12903dcb55651f9d9e08958ba0f22e8a 2226 libs optional nss_3.36-1.dsc
 c89cc279f03f55e76aefbb6cc946ad04 23025578 libs optional nss_3.36.orig.tar.gz
 3b885bb021174c47ff10716687dbb73c 24852 libs optional nss_3.36-1.debian.tar.xz
 23a382babfb0f7ed523649765868355f 5940 libs optional nss_3.36-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEGC4WHREwufzNfbFn5CqgT6aqjHIFAlrJPrkACgkQ5CqgT6aq
jHIZMA/+PCEI2yLaLrpaOCDzkUm1bxTPxFSAnc7zYDTCobesutqi8o2thdkQPJ53
P6MEzSVtu7l7TKiYnY4yq2cx5YpidBZ6mtXJAk+B6I770fFI5zg5yVr8IIt21lRR
W4LyVfRCBpHZcJhovuf6t4lQOyWHjaIVipWImI5ivNEyEB2ZM8xVYDsJVEZlhbIZ
vMcGlaNaGMynUANwpJYmGar7Zdy32JyS4sQbJJ5sEFqqhh5qf4VC4gnwlHa5fEiz
b+j5f84YocQdZycDhgMsan3+93JSNlhr96qHtVYGR44YUDSkOFV2J0A21HoB+rVL
P16w5QWrv37Z8kzKaK8OLMaBIswnsUjVg3ZSQUSIk2Uvlpv8aWeHVhT13th/8BLr
YhVBVhHXq+lC122n2XDaRvJhZ9Dsk2iUWrvUYWPholIBSrLQ/t27rWaM7Z3B9BND
3np92qbwHIBhq/ETgz09LE8YpVOroTXDUoLadCmO/STMDecfEAg+d/cTAgq+4kmD
ds9ABMxGpkJ36aI0bj8kyVU2qUWfsFSU2eXy6mY4cS/LQSB7CH7FZvJ3+XRSxXsU
tNP7wv9yvyVOfpjs8oQGE3jP3lQLoupNKgOVmHPDKblB8wqj3Dhx6MXzW5zQk1JX
AGEJQCbR8JxQgqVb2Cz0gXzBq/fA7PpKv7yQ7pctvBJ7ZP35u5U=
=uFFa
-END PGP SIGNATURE End Message ---

Bug#895111: marked as done (ohcount: FTBFS on arm64 due to buffer overflow)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 22:23:26 +
with message-id 
and subject line Bug#895111: fixed in ohcount 3.1.0-2
has caused the Debian Bug report #895111,
regarding ohcount: FTBFS on arm64 due to buffer overflow
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.)


-- 
895111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ohcount
Version: 3.1.0-1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Sylvestre,

ohcount 3.1.0-1 has been failing to build in unstable on arm64 (and in
Ubuntu on the same architecture) because an off-by-one error in the code
shows up as stack corruption in the build-time tests on this architecture. 
This buffer overflow may cause crashes on other architectures as well in
some circumstances, I haven't checked.

Please find attached the short patch for this issue, which has been uploaded
to Ubuntu to fix the build failure there.

Cheers,
-- 
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 ohcount-3.1.0/debian/patches/fix-buffer-overflow.patch 
ohcount-3.1.0/debian/patches/fix-buffer-overflow.patch
--- ohcount-3.1.0/debian/patches/fix-buffer-overflow.patch  1969-12-31 
16:00:00.0 -0800
+++ ohcount-3.1.0/debian/patches/fix-buffer-overflow.patch  2018-04-07 
00:24:49.0 -0700
@@ -0,0 +1,18 @@
+Description: fix a buffer overflow due to an off-by one
+ This manifests as a build failure on arm64 in Ubuntu.
+Author: Steve Langasek 
+Last-Modified: 2018-04-07
+
+Index: ohcount-3.1.0/src/diff.c
+===
+--- ohcount-3.1.0.orig/src/diff.c
 ohcount-3.1.0/src/diff.c
+@@ -315,7 +315,7 @@ static int hash(char *line) {
+ void prepare(int i, const char *buf) {
+   struct line *p;
+   int j;
+-  char bufcpy[strlen(buf)];
++  char bufcpy[strlen(buf)+1];
+   char *l;
+ 
+   p = malloc(3*sizeof(struct line));
diff -Nru ohcount-3.1.0/debian/patches/series 
ohcount-3.1.0/debian/patches/series
--- ohcount-3.1.0/debian/patches/series 2018-01-14 10:03:49.0 -0800
+++ ohcount-3.1.0/debian/patches/series 2018-04-07 00:19:07.0 -0700
@@ -1,3 +1,4 @@
 disabled_test_suite.patch
 conflicting-type.diff
 build-cflags.diff
+fix-buffer-overflow.patch
--- End Message ---
--- Begin Message ---
Source: ohcount
Source-Version: 3.1.0-2

We believe that the bug you reported is fixed in the latest version of
ohcount, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated ohcount 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, 07 Apr 2018 23:40:10 +0200
Source: ohcount
Binary: ohcount ohcount-doc
Architecture: source amd64 all
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sylvestre Ledru 
Changed-By: Sylvestre Ledru 
Description:
 ohcount- Source code line counter
 ohcount-doc - Source code line counter - Documentation
Closes: 895111
Changes:
 ohcount (3.1.0-2) unstable; urgency=medium
 .
   * Fix a FTBFS (arm64 due to buffer overflow)
 Thanks to Steve Langasek for the patch
 (Closes: #895111)
Checksums-Sha1:
 52791a6d9250e8e87ee1c1fb89617db3acdbaf16 1999 ohcount_3.1.0-2.dsc
 2b8e051c9f2a317832b570cdcd74cd9e6254807b 7344 ohcount_3.1.0-2.debian.tar.xz
 0e848ff7529eebd28fdd1fe780f89298083c 248168 
ohcount-dbgsym_3.1.0-2_amd64.deb
 fe2db755bc18b78ff122b4d4cbcd09bb89b399a1 141760 ohcount-doc_3.1.0-2_all.deb
 53b3f5488a0878c710b2e048e7f3f8352de6b6c2 7270 ohcount_3.1.0-2_amd64.buildinfo
 e620d2bb380e4c8d6e3b8783adc103a89d114da0 299368 

Bug#894982: marked as done (nspr: please package version 4.19)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 22:23:02 +
with message-id 
and subject line Bug#894982: fixed in nspr 2:4.19-1
has caused the Debian Bug report #894982,
regarding nspr: please package version 4.19
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.)


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

Dear Maintainer,

FF 60 and TB 60 need NSPR >= 4.19.
For now I switched the usage of the internal shipped source for working
on Thunderbird 60 betas but it's of course preferable to not use
embedded libraries.

Regards
Carsten

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: nspr
Source-Version: 2:4.19-1

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated nspr 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, 08 Apr 2018 06:49:27 +0900
Source: nspr
Binary: libnspr4 libnspr4-dev libnspr4-dbg
Architecture: source
Version: 2:4.19-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Description:
 libnspr4   - NetScape Portable Runtime Library
 libnspr4-dbg - Debugging symbols for the NetScape Portable Runtime library
 libnspr4-dev - Development files for the NetScape Portable Runtime library
Closes: 894982
Changes:
 nspr (2:4.19-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #894982.
Checksums-Sha1:
 db8627d610db2b3f13e0d21ca0b8b139be24f7c3 2061 nspr_4.19-1.dsc
 907221d51a1f8cca0c3a9e1af93c53e02f5e203b 1139967 nspr_4.19.orig.tar.gz
 c917341fb9a3defd77079841b3376d244fba6ec6 15320 nspr_4.19-1.debian.tar.xz
 5a9e2b6967bf66415af1d4cd8080d7b03bbc2fd4 5849 nspr_4.19-1_source.buildinfo
Checksums-Sha256:
 5a737b00e19488384e75c18fd59456a2327d1d2e30c648c0fd24f0532961757e 2061 
nspr_4.19-1.dsc
 2ed95917fa2277910d1d1cf36030607dccc0ba522bba08e2af13c113dcd8f729 1139967 
nspr_4.19.orig.tar.gz
 fdc6c83dec976487979da56d90da4dd897772df1f978e897136908ed24c4d933 15320 
nspr_4.19-1.debian.tar.xz
 5772550e8e7f27aef7ee7b9d02fe72c136e8af9d0108a99ca6a245df62b5d714 5849 
nspr_4.19-1_source.buildinfo
Files:
 875d5aa477cff9392ec56e40afc42f38 2061 libs optional nspr_4.19-1.dsc
 e1d27282ad6286b69d6b9fd07201d3dd 1139967 libs optional nspr_4.19.orig.tar.gz
 e1eef715bc5350607116a3b17daa6055 15320 libs optional nspr_4.19-1.debian.tar.xz
 aa936b240f8d1cbe1cb715b27980f88f 5849 libs optional 
nspr_4.19-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEGC4WHREwufzNfbFn5CqgT6aqjHIFAlrJPT8ACgkQ5CqgT6aq
jHKNbg/+IGPWRwS4u3noiHX0LDVhH/ndgxmABi5eKmZ4zhyfCR1h4m7xrRs7WCBm
gN6t7IV+PnoXxecIzRTgHbslgI4JrKz+gFgc7QC3xUCLFZKJn5ykWMoSTIy2a6fu
5fp4UmdktGp5lI+UqPRTOSI/72cD3dDz4Up3RpXsYQut3ZnzCTLaSIGnGr3BeYPr
Xz7gmcEBxxXPHLv73Si2t3Qiu+8BbAB3syduSw9rlYH3+V+o2jsjwE+dClawHBt2
jnmBHgOk2u4+Lncxjji+QjJ+ahITSjbW0VEqtR7MmUqVEysOj46ER4eRC8sQDq1t
A3UQ+a52kBRG2P43Ifs6Ea3pjjyCU9CpBFhr8UIk5iGvCBqaHlBJdOig2MTsgtco
XncmfLlPjvPmLHSvRyRSehRAeaixisvMiPQoRSnz02vvkeL8E1f/qDyKftQ3mZYF
vuJOfaVB1oEt/kJw7BNbsOLbKGsZeFhSe1lV8Do1e8qMLnTS/2w79YZOmbBYE7S6
1M+hszp5foEzQ9S9CVhsGEODISE3+zXwhObkysXTKsD1XdYqYaA9lsF9oXvnFSVA
DX47LCTW3uhZLMpLUdnYwwT0OXTsnP7CrW68uBUh7dBGvtpmqaROsEip4ZeNVY+0
RtFd9ZVJv9Ryf12E2HUbclxjcNcyMBt1kbMs2kL1Ugq/FWMKNhM=
=nHsu
-END PGP SIGNATURE End Message ---

Bug#869139: marked as done (syslog-ng-incubator FTBFS on s390x: FAIL: modules/grok/tests/test_grok)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 18:25:42 -0400
with message-id 

and subject line Re: syslog-ng-incubator FTBFS on s390x: FAIL: 
modules/grok/tests/test_grok
has caused the Debian Bug report #869139,
regarding syslog-ng-incubator FTBFS on s390x: FAIL: modules/grok/tests/test_grok
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.)


-- 
869139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syslog-ng-incubator
Version: 0.5.0-5
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=syslog-ng-incubator=s390x=0.5.0-5=1500577713=0

...
FAIL: modules/grok/tests/test_grok
PASS: modules/date/tests/test_date
=
   syslog-ng-incubator 0.5.0: ./test-suite.log
=

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: modules/grok/tests/test_grok
==

[2017-07-20T19:08:28.677347] WARNING: template: the default value for 
template-escape has changed to 'no' from syslog-ng 3.0, please update your 
configuration file accordingly;
[50431] [patterns] [grok_pattern_add:29] Adding new pattern 'STRING' => 
'[a-zA-Z]+'
[50431] [patterns] [grok_pattern_add:29] Adding new pattern 'NUMBER' => '[0-9]+'
[50431] [compile] [grok_compilen:66] Compiling '%{STRING:field}'
[50431] [regexpand] [grok_pattern_expand:179]  start of expand: 
%{STRING:field}
[50431] [regexpand] [grok_pattern_expand:190]start of loop: 
%{STRING:field}
[50431] [regexpand] [grok_pattern_expand:203] Pattern length: 15
[50431] [regexpand] [grok_pattern_expand:209] Pattern name: STRING
[50431] [patterns] [grok_pattern_find:41] Searching for pattern 'STRING' 
(found): 
[50431] [capture] [grok_capture_add:30] Adding pattern 'STRING:field' as 
capture 0 (pcrenum 0)
[50431] [regexpand] [grok_pattern_expand:281]   replace with (?<>): (?<>)
[50431] [regexpand] [grok_pattern_expand:288]   add capture id: (?<_>)
[50431] [regexpand] [grok_pattern_expand:297] :: Inserted: 
[50431] [regexpand] [grok_pattern_expand:298] :: STR: (?<_>)
[50431] [regexpand] [grok_pattern_expand:330] Fully expanded: (?<_>)
[50431] [compile] [grok_study_capture_map:407] Studying capture 0
[50431] [capture] [grok_capture_add:30] Adding pattern 'STRING:field' as 
capture 0 (pcrenum 1)
[50431] [exec] [grok_execn:128] value =~ /%{STRING:field}/ => 2
[50431] [capture] [grok_capture_walk_next:231] walknext ok 0
[50431] [match] [grok_match_walk_next:61] CaptureWalk 'STRING:field' is 0 -> 0 
of string 'value'
[50431] [capture] [grok_capture_walk_next:228] walknext null

  ###
  #
  # FAIL: ASSERTION FAILED: Named capture didn't stored;  actual_length=0 
expected_length=5,
  #  actual=   '',
  #  expected= 'value'
  #
  ###

FAIL modules/grok/tests/test_grok (exit status: 1)


Testsuite summary for syslog-ng-incubator 0.5.0

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to viktor.juh...@balabit.com

Makefile:2162: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.6.2-0.1

https://buildd.debian.org/status/package.php?p=syslog-ng-incubator

Thanks,
Jeremy Bicha--- End Message ---

Bug#853778: marked as done (libdigidoc: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 18:10:53 -0400
with message-id 

and subject line Re: libdigidoc: Please migrate to openssl1.1 in buster
has caused the Debian Bug report #853778,
regarding libdigidoc: Please migrate to openssl1.1 in 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.)


-- 
853778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdigidoc
Version: 3.10.1.1208+ds1-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libdigidoc_3.10.1.1208+ds1-2_amd64-20160529-1440

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
libdigidoc (3.10.1.1208+ds1-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Fix FTBFS by using OpenSSL 1.0.2. (Closes: #828391)
  * Drop the uninstallable libdigidoc-dbg package,
it was replaced by libdigidoc-dbgsym. (Closes: #851204)

 -- Adrian Bunk  Fri, 13 Jan 2017 20:53:25 +0200--- End Message ---

Bug#862600: marked as done (tests.r-b.o: tests version from sid in testing due to the source is in testing due to Built-Using:…)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 23:53:05 +0200
with message-id <20180407215304.gh17...@mapreri.org>
and subject line Re: [Qa-jenkins-dev] Bug#862600: tests.r-b.o: tests version 
from sid in testing due to the source is in testing due to Built-Using:…
has caused the Debian Bug report #862600,
regarding tests.r-b.o: tests version from sid in testing due to the source is 
in testing due to Built-Using:…
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.)


-- 
862600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jenkins.debian.org
Severity: normal
x-debbugs-cc: b...@debian.org

Dear Maintainer,

< bunk> 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-rackspace-gophercloud.html
< bunk> This seems confused by the more recent source that is in stretch due to 
Built-Using?
<  h01ger> | oh! it builds the sid version in stretch!
<  h01ger> | bunk: so the sid version "is in stretch" because some packages 
in stretch were build using the sid version and then migrated. wow. i think i 
have  discussed this with ivodd once in a corridor at the bsp at credativ in 
march 2017 or so…
<  h01ger> | i also think this is a topic for #-release
<  h01ger> | (unless they know)
<  h01ger> | and then its also a bug in the tests.r-b.o setup, to test the 
wrong version…
<  h01ger> | fwiw:
<  h01ger> | $ rmadison golang-github-rackspace-gophercloud
<  h01ger> | debian:
<  h01ger> |  golang-github-rackspace-gophercloud | 
1.0.0+git20160603.920.934dbf8-1   | stretch | source
<  h01ger> |  golang-github-rackspace-gophercloud | 
1.0.0+git20161013.1012.e00690e8-1 | sid | source
<  h01ger> | and tests.r-b.o only shows the sid version being tested in 
stretch+sid…
<   bunk> | h01ger: How does r-b pick the version? Sources?
<  h01ger> | etootired. check bin/reproducible_build.sh in jenkins.d.n.git 
please…
< bunk> 
https://anonscm.debian.org/cgit/qa/jenkins.debian.net.git/tree/bin/reproducible_build.sh#n540
< bunk> apt-get -- --download-only --only-source source ${SRCPACKAGE}
< bunk> (if I read the script correctly)
<  h01ger> | bunk: may i quote your initial question into the BTS?
<  h01ger> | +could be it… ;)
< bunk> sure

Thanks for the bug report, Adrian!


-- 
cheers,
Holger


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Mon, May 15, 2017 at 01:53:57AM +0200, Holger Levsen wrote:
> < bunk> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-rackspace-gophercloud.html
> < bunk> This seems confused by the more recent source that is in stretch due 
> to Built-Using?
> <  h01ger> | oh! it builds the sid version in stretch!

So, the very same day (May 15th 2017) we fixed the source importer to
ignore Extra-Source-Only:yes packages, but we didn't fix the several
affected entries.
I did it now, by manually hacking my way through the db...

The affected sources:

buster+stretch:
golang-github-rackspace-gophercloud is faulty: 
sources=1.0.0+git20160603.920.934dbf8-1 | db=1.0.0+git20161013.1012.e00690e8-1
runc is faulty: sources=0.1.1+dfsg1-2 | db=1.0.0~rc2+git20161109.131.5137186-2

stretch only:
golang-github-dgrijalva-jwt-go is faulty: sources=3.0.0+REALLY.2.6.0-1 | 
db=3.0.0.1+REALLY.2.6.0-1
golang-github-opencontainers-specs is faulty: sources=1.0.0~rc1-1 | 
db=1.0.0~rc2+git20160926.38.1c7c27d-1
golang-github-spf13-cobra is faulty: sources=0.0~git20161229.0.1dd5ff2-1 | 
db=0.0~git20170314.0.7be4bed-1
golang-github-vishvananda-netlink is faulty: 
sources=0.0~git20160629.0.e73bad4-1 | db=0.0~git20170117.0.ebdfb74-1
golang-gogoprotobuf is faulty: sources=0.3-1 | db=0.3+git20170120.144.265e960d-1
golang-goleveldb is faulty: sources=0+git20160825.6ae1797-2 | 
db=0.0~git20170302.0.3c5717c-4
influxdb is faulty: sources=1.0.2+dfsg1-1 | db=1.1.1+dfsg1-4
snappy is faulty: sources=1.1.3-3 | db=1.1.4-1


I've deleted the faulty builds as well, the scheduler should pick them
up (as they are "untested" now).

-- 
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 ---

Bug#889581: marked as done (syslog-ng-incubator: FTBFS with syslog-ng 3.13.2)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 21:31:21 +
with message-id 
and subject line Bug#889581: fixed in syslog-ng-incubator 0.6.2-0.1
has caused the Debian Bug report #889581,
regarding syslog-ng-incubator: FTBFS with syslog-ng 3.13.2
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.)


-- 
889581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syslog-ng-incubator
Version: 0.5.0-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

syslog-ng-incubator FTBFS with syslog-ng 3.13.2 that has merged
eventlog, s.t. it is no longer available as a separate package:

[...]
checking for strdup... yes
checking for strtoll... yes
checking for GLIB... yes
checking for SYSLOG_NG... yes
checking for EVENTLOG... no
configure: error: Package requirements (eventlog >= 0.2.10) were not met:

No package 'eventlog' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables EVENTLOG_CFLAGS
and EVENTLOG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


Andreas


syslog-ng-incubator.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: syslog-ng-incubator
Source-Version: 0.6.2-0.1

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated syslog-ng-incubator 
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: Sat, 07 Apr 2018 16:50:25 -0400
Source: syslog-ng-incubator
Binary: syslog-ng-mod-trigger syslog-ng-mod-rss syslog-ng-mod-basicfuncs-plus 
syslog-ng-mod-lua syslog-ng-mod-perl syslog-ng-mod-grok syslog-ng-mod-kafka 
syslog-ng-mod-zmq
Architecture: source
Version: 0.6.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: syslog-ng maintainers 

Changed-By: Jeremy Bicha 
Description:
 syslog-ng-mod-basicfuncs-plus - Enhanced system logging daemon (extra template 
functions)
 syslog-ng-mod-grok - Enhanced system logging daemon (Grok parser support)
 syslog-ng-mod-kafka - Enhanced system logging daemon (kafka destination)
 syslog-ng-mod-lua - Enhanced system logging daemon (Lua destination)
 syslog-ng-mod-perl - Enhanced system logging daemon (Perl destination)
 syslog-ng-mod-rss - Enhanced system logging daemon (RSS destination)
 syslog-ng-mod-trigger - Enhanced system logging daemon (trigger source)
 syslog-ng-mod-zmq - Enhanced system logging daemon (ZeroMQ destination)
Closes: 889581
Changes:
 syslog-ng-incubator (0.6.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * New upstream release compatible with syslog-ng >= 3.12
 (Closes: #889581)
   * Drop all patches: obsolete
   * Drop syslog-ng-mod-date and update install files for new version
   * Use dh_missing --fail-missing
Checksums-Sha1:
 c77cff6938f20f035cb276a7be4f377c49df0122 2917 syslog-ng-incubator_0.6.2-0.1.dsc
 41feacba6606e7a2bcb8eedc14652da941c34436 58549 
syslog-ng-incubator_0.6.2.orig.tar.gz
 f1a843f058c60cfcb0efaf6be056adfd01aff42b 4336 
syslog-ng-incubator_0.6.2-0.1.debian.tar.xz
 40cf3e911c9989014d30afcf9902a0a5ce82939f 7652 
syslog-ng-incubator_0.6.2-0.1_source.buildinfo
Checksums-Sha256:
 6980eda61489e1edb50183b33e659caff5233509bd300ba1c36c43eeb5a28ee8 2917 
syslog-ng-incubator_0.6.2-0.1.dsc
 ea9894ecb06ff4c2860a5210f7f993abf9aed240764daf56c264fb80dad2a35e 58549 
syslog-ng-incubator_0.6.2.orig.tar.gz
 ee2fe0aa940da4e1575584ff8ad1c731068ec2bd4100a38989dc2aea8632fe49 4336 
syslog-ng-incubator_0.6.2-0.1.debian.tar.xz
 db406f11d736cbef4b0cb7b042c8b1d8d7acef788d8e3c0b20731169e3347868 7652 
syslog-ng-incubator_0.6.2-0.1_source.buildinfo
Files:
 b1169c11570932f149d19e8a12252008 2917 admin optional 
syslog-ng-incubator_0.6.2-0.1.dsc
 

Bug#895032: marked as done (RFS: deepin-music/3.1.8+ds-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 22:35:26 +0200
with message-id <20180407203526.7hthace5y7jbk...@angband.pl>
and subject line Re: Bug#895032: [yanha...@gmail.com: Re: Bug#895032: RFS: 
deepin-music/3.1.8-1 [ITP]]
has caused the Debian Bug report #895032,
regarding RFS: deepin-music/3.1.8+ds-1 [ITP]
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.)


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

Dear mentors,

I am looking for a sponsor for my package "deepin-music"

* Package name: deepin-music
  Version : 3.1.8-1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/deepin-music
* License : GPL-3+
  Section : sound

It builds those binary packages:

  deepin-music - Awesome music player with brilliant and tweakful UI

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/deepin-music

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-music/deepin-music_3.1.8-1.dsc

More information about hello can be obtained from 
g...@salsa.debian.org:pkg-deepin-team/deepin-music.git

-- 
Yanhao Mo


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sat, Apr 07, 2018 at 06:11:39PM +0800, Yanhao Mo wrote:
> Thanks for the guidance, I have fix this according this solution.
[...]
> and this is fixed as well, Please consider recheck it.

Looks great now; in NEW.
Thanks for your work!


喵!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 
⢿⡄⠘⠷⠚⠋⠀ ... what's the frequency of that 5V DC?
⠈⠳⣄--- End Message ---

Bug#858242: marked as done (libwine: winemenubuilder creates .desktop files with invalid WINEPREFIX)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 15:38:03 -0400
with message-id 

Bug#894835: marked as done (dh_installxfonts: typo causes a misc:Depends on non-existing xfont-utils)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 19:34:21 +
with message-id 
and subject line Bug#894835: fixed in debhelper 11.2
has caused the Debian Bug report #894835,
regarding dh_installxfonts: typo causes a misc:Depends on non-existing 
xfont-utils
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.)


-- 
894835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.1.6
Severity: minor
Tags: patch

Hi.
My patch for #894227 has introduced a typo.
The fix is trivial:

--- a/dh_installxfonts
+++ b/dh_installxfonts
@@ -86,7 +86,7 @@
  { 'CMDS' => join(";", @cmds, @cmds_postrm) });
 
  if (@cmds_postrm) {
- addsubstvar($package, "misc:Depends", "xfont-utils", ">= 
1:7.5+2");
+ addsubstvar($package, "misc:Depends", "xfonts-utils", ">= 
1:7.5+2");
  } else {
  addsubstvar($package, "misc:Depends", "xfonts-utils");
  }
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 07 Apr 2018 19:23:32 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 894549 894573 894666 894835 894895 895011 895044
Changes:
 debhelper (11.2) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * debhelper.7: Add a ~ to the suggested Build-Depends to ensure
 backports also work for debhelper with single integer versions.
 Thanks to Trent W. Buck for the suggestion.  (Closes: #894666)
   * makefile.pm: Use -Oline with make.  This avoids make mistaking
 a target name for a value for -O and should make build time
 outs less likely for "long" targets.  (Closes: #894573)
   * Dh_Lib.pm: Fix bug that make debhelper trip on packages with
 the version "0".  Thanks to Chris Lamb for reporting the bug
 plus debugging the issue.  (Closes: #894895)
   * Buildsystem.pm: Rewrite to support build systems that generate
 build files for another build system (without using
 inheritance).  This enables generator build systems to have
 multiple backends.
   * cmake.pm: Support ninja as alternative backend (by using the
 build system cmake+ninja).  Thanks to Kyle Edwards for the
 suggestion.  (Closes: #895044)
   * meson.pm: Rewrite as a generator build system with ninja as
 the only backend.
   * debhelper.7: Recommend packagers to use "debian/."
 over "debian/" in most cases.  Thanks to Johannes
 Schauer for the suggestion.
   * dh_usrlocal: Implement a simple guard for directories that
 will likely cause issues in the shell snippets.
   * dh_usrlocal: Use the new rules from Debian Policy 4.1.4 to
 determine the default ownership and mode for directories.
   * d/control: Bump Standards-Versions to 4.1.4.  Beyond the
 dh_usrlocal change listed above, no changes were required.
 .
   [ Nicolas Boulenguez ]
   * dh_installxfonts: Fix typo that causes a misc:Depends on
 non-existing xfont-utils.  (Closes: #894835)
   * dh_installwm.1: Document --all.  (Closes: #895011)
   * dh_usrlocal: Fix bug where the generated prerm script generated
 by dh_usrlocal could remove a directory directly in /usr/local.
 (Closes: #894549)
 .
   [ Mattia Rizzolo ]
   * Lower the version restrictions on dpkg and dpkg-dev.  They are not
 needed anymore, as R³ support is not implied anymore, but requires
 an 

Bug#894549: marked as done (debhelper: dh_usrlocal may remove a direct subdirectory of /usr/local)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 19:34:21 +
with message-id 
and subject line Bug#894549: fixed in debhelper 11.2
has caused the Debian Bug report #894549,
regarding debhelper: dh_usrlocal may remove a direct subdirectory of /usr/local
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.)


-- 
894549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.1.6
Severity: minor
Tags: patch

Hello.

The attached script shows that dh_usrlocal generates a prerm script
removing a direct subdirectory of /usr/local.
As I understand the policy, it should not.

The fix is included.
It also suggests some minor related changes, which do not seem to change the 
behaviour.
--- a/dh_usrlocal
+++ b/dh_usrlocal
@@ -82,6 +82,8 @@
 		  wanted => sub {
 			my $fn = $File::Find::name;
 			if (-d $fn) {
+return if $fn eq  "$tmp/usr/local";
+
 my $user = 'root';
 my $group = 'staff';
 my $mode = '02775';
@@ -99,12 +101,13 @@
 
 
 $fn =~ s!^\Q$tmp\E!!;
-return if $fn eq '/usr/local';
-
-# @dirs is in parents-first order for dir creation...
-unshift @dirs, "$fn $mode $user $group";
-# ...whereas @justdirs is depth-first for removal.
-push @justdirs, $fn;
+
+push @dirs, "$fn $mode $user $group";
+
+# don't remove directories directly in /usr/local
+if ($File::Find::dir ne "$tmp/usr/local") {
+	push @justdirs, $fn;
+}
 doit('rmdir', $_);
 			}
 			else {
@@ -118,11 +121,10 @@
 		# This constructs the body of a 'sed' c\ expression which
 		# is parsed by the shell in double-quotes
 		my $dirs = join("$ebs\n", sort @dirs);
-		pop @justdirs; # don't remove directories directly in /usr/local
 		my $justdirs = join("$ebs\n", reverse sort @justdirs);
 		if (! $dh{NOSCRIPTS}) { 
 			autoscript($package,"postinst", "postinst-usrlocal",
-   "/#DIRS#/ c${ebs}\n${dirs}");
+   "/#DIRS#/ c${ebs}\n${dirs}") if length $dirs;
 			autoscript($package,"prerm", "prerm-usrlocal",
    "/#JUSTDIRS#/ c${ebs}\n${justdirs}") if length $justdirs;
 		}


dh_usrlocal-topdirs.sh
Description: Bourne shell script
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 07 Apr 2018 19:23:32 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 894549 894573 894666 894835 894895 895011 895044
Changes:
 debhelper (11.2) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * debhelper.7: Add a ~ to the suggested Build-Depends to ensure
 backports also work for debhelper with single integer versions.
 Thanks to Trent W. Buck for the suggestion.  (Closes: #894666)
   * makefile.pm: Use -Oline with make.  This avoids make mistaking
 a target name for a value for -O and should make build time
 outs less likely for "long" targets.  (Closes: #894573)
   * Dh_Lib.pm: Fix bug that make debhelper trip on packages with
 the version "0".  Thanks to Chris Lamb for reporting the bug
 plus debugging the issue.  (Closes: #894895)
   * Buildsystem.pm: Rewrite to support build systems that generate
 build files for another build system (without using
 inheritance).  This enables generator build systems to have
 multiple backends.
   * cmake.pm: Support ninja as alternative backend (by using the
 build system cmake+ninja).  Thanks to Kyle Edwards for the
 suggestion.  (Closes: #895044)
 

Bug#895011: marked as done (dh_installwm: please mention --all in manual page)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 19:34:21 +
with message-id 
and subject line Bug#895011: fixed in debhelper 11.2
has caused the Debian Bug report #895011,
regarding dh_installwm: please mention --all in manual page
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.)


-- 
895011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.1.6
Severity: minor
Tags: patch

A trivial patch is attached.
Thanks.
--- a/dh_installwm
+++ b/dh_installwm
@@ -49,6 +49,11 @@
 
 Do not modify F/F scripts. Turns this command into a no-op.
 
+=item B<-A>, B<--all>
+
+Modify scripts for window managers specified by command line
+parameters in ALL packages acted on, not just the first.
+
 =item I ...
 
 Window manager programs to register.
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2

We believe that the bug you reported is fixed in the latest version of
debhelper, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 07 Apr 2018 19:23:32 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 894549 894573 894666 894835 894895 895011 895044
Changes:
 debhelper (11.2) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * debhelper.7: Add a ~ to the suggested Build-Depends to ensure
 backports also work for debhelper with single integer versions.
 Thanks to Trent W. Buck for the suggestion.  (Closes: #894666)
   * makefile.pm: Use -Oline with make.  This avoids make mistaking
 a target name for a value for -O and should make build time
 outs less likely for "long" targets.  (Closes: #894573)
   * Dh_Lib.pm: Fix bug that make debhelper trip on packages with
 the version "0".  Thanks to Chris Lamb for reporting the bug
 plus debugging the issue.  (Closes: #894895)
   * Buildsystem.pm: Rewrite to support build systems that generate
 build files for another build system (without using
 inheritance).  This enables generator build systems to have
 multiple backends.
   * cmake.pm: Support ninja as alternative backend (by using the
 build system cmake+ninja).  Thanks to Kyle Edwards for the
 suggestion.  (Closes: #895044)
   * meson.pm: Rewrite as a generator build system with ninja as
 the only backend.
   * debhelper.7: Recommend packagers to use "debian/."
 over "debian/" in most cases.  Thanks to Johannes
 Schauer for the suggestion.
   * dh_usrlocal: Implement a simple guard for directories that
 will likely cause issues in the shell snippets.
   * dh_usrlocal: Use the new rules from Debian Policy 4.1.4 to
 determine the default ownership and mode for directories.
   * d/control: Bump Standards-Versions to 4.1.4.  Beyond the
 dh_usrlocal change listed above, no changes were required.
 .
   [ Nicolas Boulenguez ]
   * dh_installxfonts: Fix typo that causes a misc:Depends on
 non-existing xfont-utils.  (Closes: #894835)
   * dh_installwm.1: Document --all.  (Closes: #895011)
   * dh_usrlocal: Fix bug where the generated prerm script generated
 by dh_usrlocal could remove a directory directly in /usr/local.
 (Closes: #894549)
 .
   [ Mattia Rizzolo ]
   * Lower the version restrictions on dpkg and dpkg-dev.  They are not
 needed anymore, as R³ support is not implied anymore, but requires
 an environment variable to be passed.
Checksums-Sha1:
 71d3f409fbca3c667cfa0809447e658f4de008da 1681 debhelper_11.2.dsc
 9f3ad653d486721186056cc9b897c8b3f682bf97 455608 debhelper_11.2.tar.xz
 

Bug#895044: marked as done (debhelper: add support for Ninja with CMake)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 19:34:21 +
with message-id 
and subject line Bug#895044: fixed in debhelper 11.2
has caused the Debian Bug report #895044,
regarding debhelper: add support for Ninja with CMake
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.)


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

Dear Maintainer,

Large projects which use CMake, such as VTK, take a long time to build
with the Makefile generator, and see significant build time improvements
when being built with the Ninja generator instead. Please consider
adding support for using the Ninja generator with CMake. Perhaps
something like:

$ dh --buildsystem=cmakeninja

I realize this may be tricky given how the buildsystems are implemented
in debhelper. I don't know much about Perl, but if it supports multiple
inheritance, would it be possible to make a class like "cmakebase" and
then have "cmake" and "cmakeninja" inherit from both "cmakebase" and
then "makefile" and "ninja" respectively?


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

Kernel: Linux 4.15.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1
ii  dh-autoreconf17
ii  dh-strip-nondeterminism  0.040-1
ii  dpkg 1.19.0.5
ii  dpkg-dev 1.19.0.5
ii  file 1:5.32-2
ii  libdpkg-perl 1.19.0.5
ii  man-db   2.8.2-1
ii  perl 5.26.1-5
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  
pn  dwz  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2

We believe that the bug you reported is fixed in the latest version of
debhelper, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 07 Apr 2018 19:23:32 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 894549 894573 894666 894835 894895 895011 895044
Changes:
 debhelper (11.2) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * debhelper.7: Add a ~ to the suggested Build-Depends to ensure
 backports also work for debhelper with single integer versions.
 Thanks to Trent W. Buck for the suggestion.  (Closes: #894666)
   * makefile.pm: Use -Oline with make.  This avoids make mistaking
 a target name for a value for -O and should make build time
 outs less likely for "long" targets.  (Closes: #894573)
   * Dh_Lib.pm: Fix bug that make debhelper trip on packages with
 the version "0".  Thanks to Chris Lamb for reporting the bug
 plus debugging the issue.  (Closes: #894895)
   * Buildsystem.pm: Rewrite to support build systems that generate
 build files for another build system (without using
 inheritance).  This enables generator build systems to have
 multiple backends.
   * cmake.pm: Support ninja as alternative backend (by using the
 build system cmake+ninja).  Thanks to Kyle Edwards for the
 suggestion.  (Closes: #895044)
   * meson.pm: Rewrite as a generator build system with ninja as
 the only backend.
   * debhelper.7: Recommend 

Bug#894895: marked as done (debhelper: does not accept "0" (zero) as a valid version number in debian/changelog)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 19:34:21 +
with message-id 
and subject line Bug#894895: fixed in debhelper 11.2
has caused the Debian Bug report #894895,
regarding debhelper: does not accept "0" (zero) as a valid version number in 
debian/changelog
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.)


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

Hi,

The following changelog entry:

sourcepackage (0) UNRELEASED; urgency=low

… results in (eg. when running dh_installchangelogs):

changelog parse failure

The relevant code in isnative is:

# Get the package version.
$dh{VERSION} = $res->{'Version'};
# Did the changelog parse fail?
if ($dh{VERSION} eq q{}) {
error("changelog parse failure");
}

Where $dh{VERSION} is returned as '0'. I believe this is a valid
version number unless I'm missing something.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 07 Apr 2018 19:23:32 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 894549 894573 894666 894835 894895 895011 895044
Changes:
 debhelper (11.2) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * debhelper.7: Add a ~ to the suggested Build-Depends to ensure
 backports also work for debhelper with single integer versions.
 Thanks to Trent W. Buck for the suggestion.  (Closes: #894666)
   * makefile.pm: Use -Oline with make.  This avoids make mistaking
 a target name for a value for -O and should make build time
 outs less likely for "long" targets.  (Closes: #894573)
   * Dh_Lib.pm: Fix bug that make debhelper trip on packages with
 the version "0".  Thanks to Chris Lamb for reporting the bug
 plus debugging the issue.  (Closes: #894895)
   * Buildsystem.pm: Rewrite to support build systems that generate
 build files for another build system (without using
 inheritance).  This enables generator build systems to have
 multiple backends.
   * cmake.pm: Support ninja as alternative backend (by using the
 build system cmake+ninja).  Thanks to Kyle Edwards for the
 suggestion.  (Closes: #895044)
   * meson.pm: Rewrite as a generator build system with ninja as
 the only backend.
   * debhelper.7: Recommend packagers to use "debian/."
 over "debian/" in most cases.  Thanks to Johannes
 Schauer for the suggestion.
   * dh_usrlocal: Implement a simple guard for directories that
 will likely cause issues in the shell snippets.
   * dh_usrlocal: Use the new rules from Debian Policy 4.1.4 to
 determine the default ownership and mode for directories.
   * d/control: Bump Standards-Versions to 4.1.4.  Beyond the
 dh_usrlocal change listed above, no changes were required.
 .
   [ Nicolas Boulenguez ]
   * dh_installxfonts: Fix typo that causes a misc:Depends on
 non-existing xfont-utils.  (Closes: #894835)
   * dh_installwm.1: Document --all.  (Closes: #895011)
   * dh_usrlocal: Fix bug where the generated prerm script generated
 by dh_usrlocal could remove a directory directly in /usr/local.
 (Closes: #894549)
 .
   [ Mattia Rizzolo ]
  

Bug#894573: marked as done (savi: "make clean" fails with debhelper >= 11.1.5)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 19:34:21 +
with message-id 
and subject line Bug#894573: fixed in debhelper 11.2
has caused the Debian Bug report #894573,
regarding savi: "make clean" fails with debhelper >= 11.1.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.)


-- 
894573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 11.1.5
Severity: serious
Control: affects -1 src:savi

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/savi.html

...
dh clean --parallel
   dh_auto_clean -O--parallel
make -j16 -O clean
make[1]: Entering directory '/build/1st/savi-1.5.1'
/bin/rm -f *~ core 
making clean in manual...
make: Entering an unknown directory
make: *** unknown output-sync type 'clean'.  Stop.
make: Leaving an unknown directory
making clean in bin...
make: Entering an unknown directory
make: *** unknown output-sync type 'clean'.  Stop.
make: Leaving an unknown directory
making clean in maps...
make: Entering an unknown directory
make: *** unknown output-sync type 'clean'.  Stop.
make: Leaving an unknown directory
making clean in oogl...
make: Entering an unknown directory
make: *** unknown output-sync type 'clean'.  Stop.
make: Leaving an unknown directory
making clean in data...
make: Entering an unknown directory
make: *** unknown output-sync type 'clean'.  Stop.
make: Leaving an unknown directory
making clean in tcl...
make: Entering an unknown directory
make: *** unknown output-sync type 'clean'.  Stop.
make: Leaving an unknown directory
making clean in src...
make: Entering an unknown directory
make: *** unknown output-sync type 'clean'.  Stop.
make: Leaving an unknown directory
make[1]: *** [Makefile:22: clean] Error 2
make[1]: Leaving directory '/build/1st/savi-1.5.1'
dh_auto_clean: make -j16 -O clean returned exit code 2
make: *** [debian/rules:7: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 07 Apr 2018 19:23:32 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 894549 894573 894666 894835 894895 895011 895044
Changes:
 debhelper (11.2) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * debhelper.7: Add a ~ to the suggested Build-Depends to ensure
 backports also work for debhelper with single integer versions.
 Thanks to Trent W. Buck for the suggestion.  (Closes: #894666)
   * makefile.pm: Use -Oline with make.  This avoids make mistaking
 a target name for a value for -O and should make build time
 outs less likely for "long" targets.  (Closes: #894573)
   * Dh_Lib.pm: Fix bug that make debhelper trip on packages with
 the version "0".  Thanks to Chris Lamb for reporting the bug
 plus debugging the issue.  (Closes: #894895)
   * Buildsystem.pm: Rewrite to support build systems that generate
 build files for another build system (without using
 inheritance).  This enables generator build systems to have
 multiple backends.
   * cmake.pm: Support ninja as alternative backend (by using the
 build system cmake+ninja).  Thanks to Kyle Edwards for the
 suggestion.  (Closes: #895044)
   * meson.pm: Rewrite as a generator build system with ninja as
 the only backend.
   * debhelper.7: Recommend packagers to use "debian/."
 over "debian/" in most cases.  Thanks to Johannes
 Schauer for the suggestion.
   * 

Bug#894666: marked as done (Simplify backports - manpage should suggest >=11~ not >=11)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 19:34:21 +
with message-id 
and subject line Bug#894666: fixed in debhelper 11.2
has caused the Debian Bug report #894666,
regarding Simplify backports - manpage should suggest >=11~ not >=11
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.)


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

When backporting libpam-mount from experimental to stable, the only change I 
needed was

-Build-Depends: debhelper (>= 11), …
+Build-Depends: debhelper (>= 11~), …

The tilde allows ~bpo versions of debhelper to satisfy the constraint.

The debhelper(5) manpage suggestion has no tilde.
Can it have a tilde?


https://manpages.debian.org/unstable/debhelper/debhelper.7.en.html#COMPATIBILITY_LEVELS

https://manpages.debian.org/stretch/debhelper/debhelper.7.en.html#COMPATIBILITY_LEVELS
--- End Message ---
--- Begin Message ---
Source: debhelper
Source-Version: 11.2

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated debhelper 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, 07 Apr 2018 19:23:32 +
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.2
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers 
Changed-By: Niels Thykier 
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 894549 894573 894666 894835 894895 895011 895044
Changes:
 debhelper (11.2) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * debhelper.7: Add a ~ to the suggested Build-Depends to ensure
 backports also work for debhelper with single integer versions.
 Thanks to Trent W. Buck for the suggestion.  (Closes: #894666)
   * makefile.pm: Use -Oline with make.  This avoids make mistaking
 a target name for a value for -O and should make build time
 outs less likely for "long" targets.  (Closes: #894573)
   * Dh_Lib.pm: Fix bug that make debhelper trip on packages with
 the version "0".  Thanks to Chris Lamb for reporting the bug
 plus debugging the issue.  (Closes: #894895)
   * Buildsystem.pm: Rewrite to support build systems that generate
 build files for another build system (without using
 inheritance).  This enables generator build systems to have
 multiple backends.
   * cmake.pm: Support ninja as alternative backend (by using the
 build system cmake+ninja).  Thanks to Kyle Edwards for the
 suggestion.  (Closes: #895044)
   * meson.pm: Rewrite as a generator build system with ninja as
 the only backend.
   * debhelper.7: Recommend packagers to use "debian/."
 over "debian/" in most cases.  Thanks to Johannes
 Schauer for the suggestion.
   * dh_usrlocal: Implement a simple guard for directories that
 will likely cause issues in the shell snippets.
   * dh_usrlocal: Use the new rules from Debian Policy 4.1.4 to
 determine the default ownership and mode for directories.
   * d/control: Bump Standards-Versions to 4.1.4.  Beyond the
 dh_usrlocal change listed above, no changes were required.
 .
   [ Nicolas Boulenguez ]
   * dh_installxfonts: Fix typo that causes a misc:Depends on
 non-existing xfont-utils.  (Closes: #894835)
   * dh_installwm.1: Document --all.  (Closes: #895011)
   * dh_usrlocal: Fix bug where the generated prerm script generated
 by dh_usrlocal could remove a directory directly in /usr/local.
 (Closes: #894549)
 .
   [ Mattia Rizzolo ]
   * Lower the version restrictions on dpkg and dpkg-dev.  They are not
 needed anymore, as R³ support is not implied anymore, but requires
 an environment variable to be passed.
Checksums-Sha1:
 

Bug#879655: marked as done (debci: please document how to use an alternative mirror)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 18:49:49 +
with message-id 
and subject line Bug#879655: fixed in debci 1.9
has caused the Debian Bug report #879655,
regarding debci: please document how to use an alternative mirror
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.)


-- 
879655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debci
Version: 1.7.1
Severity: wishlist
Tags: patch

Hi,

I have a full local mirror on my laptop but it took a little while
to find the right voodoo to override the default mirror.

Patch attached to MAINTAINERS.md that makes this clearer to someone
getting started. :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/docs/MAINTAINERS.md b/docs/MAINTAINERS.md
index aa8817e..afbf6b6 100644
--- a/docs/MAINTAINERS.md
+++ b/docs/MAINTAINERS.md
@@ -70,6 +70,12 @@ $ sudo debci setup
 This might take a few minutes since it will create a fresh container from
 scratch.
 
+You can use an alternative mirror using, for example:
+
+```
+$ sudo env MIRROR=http://my.local.mirror/debian debci setup
+```
+
 Now to actually run tests, we'll use `autopkgtest` directly. The following
 examples assume your architecture is amd64, replace it by your actual
 architecture if that is not the case.
--- End Message ---
--- Begin Message ---
Source: debci
Source-Version: 1.9

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated debci 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, 07 Apr 2018 15:24:55 -0300
Source: debci
Binary: debci debci-worker debci-collector
Architecture: source
Version: 1.9
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro 
Changed-By: Antonio Terceiro 
Description:
 debci  - continuous integration system for Debian
 debci-collector - continuous integration system for Debian (collector daemon)
 debci-worker - continuous integration system for Debian (worker daemon)
Closes: 879654 879655 880804
Changes:
 debci (1.9) unstable; urgency=medium
 .
   [ Paul Gevers ]
   * Make building debci reproducible (Closes: #880804)
   * Move from http://http.debian.net to http://deb.debian.org (Closes: #879654)
   * Document the use of a local mirror (Closes: #879655)
   * Document the need for running chdist
   * docs: fix typo
 .
   [ Antonio Terceiro ]
   * debci-setup: mention suite in the logs
   * tools/build.sh: tell rerun that `make` exits
   * tools/init-dev.sh: initialize database
   * debci-worker: refuse invalid package names
   * api: reject invalid package names
   * Use salsa.debian.org in Vcs-* fields
Checksums-Sha1:
 4e8234810430c5ccba8f1bf8f4b945b69ec4bbca 2161 debci_1.9.dsc
 50a99db9e5dee48192a65638d0e2c3803adb15be 92360 debci_1.9.tar.xz
 9ed0c5cf99259e84b03cc3a5218acdb80708b077 9333 debci_1.9_source.buildinfo
Checksums-Sha256:
 44b7a158a4fd296012551e44fb5a0aff1c0ec4dc05605d7ec9707f0ffaaa689f 2161 
debci_1.9.dsc
 508539fa4056e2fa7a38676b00c293eaf211644c9e6ea584e2847551fa04fdb7 92360 
debci_1.9.tar.xz
 a5ce0a40218f2dad6edaacbf4ef41ab54b52a8d129c7591ab3ce509bdc9c4db0 9333 
debci_1.9_source.buildinfo
Files:
 6d42374ed57b77d003c4a01d46a06211 2161 devel optional debci_1.9.dsc
 1d8dec04ae4f17f5b06a025530d63c63 92360 devel optional debci_1.9.tar.xz
 8f82d66e8595630b93ce774d1764f7ca 9333 devel optional debci_1.9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlrJD94ACgkQ/A2xu81G
C94ZrA/+NDaFPnnDTZ763EpBeuzFFviJj5MH8yUAGohqIUMCfMFNDQeZ2hAnszWC
Mbf6pc9u/xlyTKVzPbOxAaXzbPp1urCZn0qK0vi835pYH0H2Z8Ap5yej23xe30x9
71PWiLClpTqxDrsRfv5tgGBXVyzkBqzLpK0uHDS69sQCw1tAZjTaLypAUW1CmSNi
U/z5IcFZOfg3rWJrNd7hTAY1dRknv1iPvkm+p6A7ZHycAtBLbZFoop1RTVRQymZn
9iC9eWhlZkFx6s1i7k1hAaMSjAPtRG31alhfPEeXrCFhe8WpUwCWLlKFzBD8rsJh

Bug#879654: marked as done (debci: Please use deb.debian.org over http.debian.net)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 18:49:49 +
with message-id 
and subject line Bug#879654: fixed in debci 1.9
has caused the Debian Bug report #879654,
regarding debci: Please use deb.debian.org over http.debian.net
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.)


-- 
879654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debci
Version: 1.7.1
Severity: wishlist
Tags: patch

Hi,

Please use deb.debian.org over http.debian.net. Whilst they may be some kind
of alias to each other, we should try and be consistent!

Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: debci
Source-Version: 1.9

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated debci 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, 07 Apr 2018 15:24:55 -0300
Source: debci
Binary: debci debci-worker debci-collector
Architecture: source
Version: 1.9
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro 
Changed-By: Antonio Terceiro 
Description:
 debci  - continuous integration system for Debian
 debci-collector - continuous integration system for Debian (collector daemon)
 debci-worker - continuous integration system for Debian (worker daemon)
Closes: 879654 879655 880804
Changes:
 debci (1.9) unstable; urgency=medium
 .
   [ Paul Gevers ]
   * Make building debci reproducible (Closes: #880804)
   * Move from http://http.debian.net to http://deb.debian.org (Closes: #879654)
   * Document the use of a local mirror (Closes: #879655)
   * Document the need for running chdist
   * docs: fix typo
 .
   [ Antonio Terceiro ]
   * debci-setup: mention suite in the logs
   * tools/build.sh: tell rerun that `make` exits
   * tools/init-dev.sh: initialize database
   * debci-worker: refuse invalid package names
   * api: reject invalid package names
   * Use salsa.debian.org in Vcs-* fields
Checksums-Sha1:
 4e8234810430c5ccba8f1bf8f4b945b69ec4bbca 2161 debci_1.9.dsc
 50a99db9e5dee48192a65638d0e2c3803adb15be 92360 debci_1.9.tar.xz
 9ed0c5cf99259e84b03cc3a5218acdb80708b077 9333 debci_1.9_source.buildinfo
Checksums-Sha256:
 44b7a158a4fd296012551e44fb5a0aff1c0ec4dc05605d7ec9707f0ffaaa689f 2161 
debci_1.9.dsc
 508539fa4056e2fa7a38676b00c293eaf211644c9e6ea584e2847551fa04fdb7 92360 
debci_1.9.tar.xz
 a5ce0a40218f2dad6edaacbf4ef41ab54b52a8d129c7591ab3ce509bdc9c4db0 9333 
debci_1.9_source.buildinfo
Files:
 6d42374ed57b77d003c4a01d46a06211 2161 devel optional debci_1.9.dsc
 1d8dec04ae4f17f5b06a025530d63c63 92360 devel optional debci_1.9.tar.xz
 8f82d66e8595630b93ce774d1764f7ca 9333 devel optional debci_1.9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlrJD94ACgkQ/A2xu81G
C94ZrA/+NDaFPnnDTZ763EpBeuzFFviJj5MH8yUAGohqIUMCfMFNDQeZ2hAnszWC
Mbf6pc9u/xlyTKVzPbOxAaXzbPp1urCZn0qK0vi835pYH0H2Z8Ap5yej23xe30x9
71PWiLClpTqxDrsRfv5tgGBXVyzkBqzLpK0uHDS69sQCw1tAZjTaLypAUW1CmSNi
U/z5IcFZOfg3rWJrNd7hTAY1dRknv1iPvkm+p6A7ZHycAtBLbZFoop1RTVRQymZn
9iC9eWhlZkFx6s1i7k1hAaMSjAPtRG31alhfPEeXrCFhe8WpUwCWLlKFzBD8rsJh
alcBHWvzRuRaVXRFE5ANxA43W0Ysrslbc9NKe5B+ug8Rzm5UlziooWW2xhaSVHG6
PdXUNAA85jHymDNsPDvQ9jaCnU9YNqNoVZutrRgfSPGTLHwgVJ+ysO9Himtzte0M
3lATaPTGzBeu7ENmPQIDLyUNh4QCsBsYTM3CHMuwFyCjlu/TIke8F85zKe7FXbnm
7/y29uXrT6F9HCwSQjt4DshGwsntq/lkPbMEvlW+EYAHplH22MswR9kXMPGNn0zV
K0U5a8QsSeiGZkNWi6l9EfWBn+u52KnadkRNPBQqq6yYokPJ/X3gJyYNDsTYnySF
4mcPYgsisF7KCPucppmhUQ6ZfwL+lLL5kIp64s9YaJF6smGosVA=
=w4di
-END PGP SIGNATURE End Message ---

Bug#880804: marked as done (debci: please make the build reproducible)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 18:49:49 +
with message-id 
and subject line Bug#880804: fixed in debci 1.9
has caused the Debian Bug report #880804,
regarding debci: please make the build reproducible
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.)


-- 
880804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debci
Version: 1.7.1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that debci could not be built reproducibly.

This is because the documentation generation depends on (non-
determinstic) filesystem ordering.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/Makefile  2017-11-04 20:39:49.834381915 +
--- b/Makefile  2017-11-04 20:43:51.787362179 +
@@ -59,7 +59,7 @@
 
 doc: public/doc/index.html public/doc/architecture.svg
 
-public/doc/index.html public/doc/jq/jquery.js: README.md docs/*.md $(shell 
find lib -name '*.rb')
+public/doc/index.html public/doc/jq/jquery.js: README.md $(sort $(wildcard 
docs/*.md)) $(shell find lib -name '*.rb' | LC_ALL=C sort)
$(RM) public/doc/js/jquery.js
yardoc --markup markdown --output-dir public/doc --main README.md lib - 
$^
ln -sf ../../jquery.js public/doc/js/jquery.js
--- End Message ---
--- Begin Message ---
Source: debci
Source-Version: 1.9

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated debci 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, 07 Apr 2018 15:24:55 -0300
Source: debci
Binary: debci debci-worker debci-collector
Architecture: source
Version: 1.9
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro 
Changed-By: Antonio Terceiro 
Description:
 debci  - continuous integration system for Debian
 debci-collector - continuous integration system for Debian (collector daemon)
 debci-worker - continuous integration system for Debian (worker daemon)
Closes: 879654 879655 880804
Changes:
 debci (1.9) unstable; urgency=medium
 .
   [ Paul Gevers ]
   * Make building debci reproducible (Closes: #880804)
   * Move from http://http.debian.net to http://deb.debian.org (Closes: #879654)
   * Document the use of a local mirror (Closes: #879655)
   * Document the need for running chdist
   * docs: fix typo
 .
   [ Antonio Terceiro ]
   * debci-setup: mention suite in the logs
   * tools/build.sh: tell rerun that `make` exits
   * tools/init-dev.sh: initialize database
   * debci-worker: refuse invalid package names
   * api: reject invalid package names
   * Use salsa.debian.org in Vcs-* fields
Checksums-Sha1:
 4e8234810430c5ccba8f1bf8f4b945b69ec4bbca 2161 debci_1.9.dsc
 50a99db9e5dee48192a65638d0e2c3803adb15be 92360 debci_1.9.tar.xz
 9ed0c5cf99259e84b03cc3a5218acdb80708b077 9333 debci_1.9_source.buildinfo
Checksums-Sha256:
 44b7a158a4fd296012551e44fb5a0aff1c0ec4dc05605d7ec9707f0ffaaa689f 2161 
debci_1.9.dsc
 508539fa4056e2fa7a38676b00c293eaf211644c9e6ea584e2847551fa04fdb7 92360 
debci_1.9.tar.xz
 a5ce0a40218f2dad6edaacbf4ef41ab54b52a8d129c7591ab3ce509bdc9c4db0 9333 
debci_1.9_source.buildinfo
Files:
 6d42374ed57b77d003c4a01d46a06211 2161 devel optional debci_1.9.dsc
 1d8dec04ae4f17f5b06a025530d63c63 92360 devel optional debci_1.9.tar.xz
 8f82d66e8595630b93ce774d1764f7ca 9333 devel optional debci_1.9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlrJD94ACgkQ/A2xu81G
C94ZrA/+NDaFPnnDTZ763EpBeuzFFviJj5MH8yUAGohqIUMCfMFNDQeZ2hAnszWC
Mbf6pc9u/xlyTKVzPbOxAaXzbPp1urCZn0qK0vi835pYH0H2Z8Ap5yej23xe30x9

Bug#794535: marked as done (wavemon: broken homepage and watchfile)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 18:36:37 +
with message-id 
and subject line Bug#794535: fixed in wavemon 0.8.2-1
has caused the Debian Bug report #794535,
regarding wavemon: broken homepage and watchfile
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.)


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

Dear Maintainer,

Project seems to have moved to github. The attached patch updates d/control and 
d/watch.



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

Kernel: Linux 4.0.5-revert-done (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages wavemon depends on:
ii  libc62.19-18
ii  libncurses5  5.9+20140913-1+b1
ii  libtinfo55.9+20140913-1+b1

wavemon recommends no packages.

wavemon suggests no packages.
diff -Naur wavemon-0.7.6-orig/debian/control wavemon-0.7.6/debian/control
--- wavemon-0.7.6-orig/debian/control	2015-08-04 09:43:48.010629392 +0200
+++ wavemon-0.7.6/debian/control	2015-08-04 09:44:34.727507041 +0200
@@ -5,7 +5,7 @@
 Build-Depends: autotools-dev, libncurses5-dev,
  debhelper (>= 9), linux-libc-dev
 Standards-Version: 3.9.5
-Homepage: http://www.erg.abdn.ac.uk/ergcms/wavemon/
+Homepage: https://github.com/uoaerg/wavemon
 
 Package: wavemon
 Architecture: linux-any
diff -Naur wavemon-0.7.6-orig/debian/watch wavemon-0.7.6/debian/watch
--- wavemon-0.7.6-orig/debian/watch	2015-08-04 09:43:48.010629392 +0200
+++ wavemon-0.7.6/debian/watch	2015-08-04 09:45:51.868956182 +0200
@@ -1,2 +1,3 @@
 version=3
-http://eden-feed.erg.abdn.ac.uk/wavemon/stable-releases/wavemon-(.+).tar.bz2
+opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/wavemon-$1\.tar\.gz/ \
+  https://github.com/uoaerg/wavemon/tags .*/v?(\d\S*)\.tar\.gz
--- End Message ---
--- Begin Message ---
Source: wavemon
Source-Version: 0.8.2-1

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

Debian distribution maintenance software
pp.
Jonathan McCrohan  (supplier of updated wavemon 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: Sat, 07 Apr 2018 19:16:24 +0100
Source: wavemon
Binary: wavemon
Architecture: source amd64
Version: 0.8.2-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan McCrohan 
Changed-By: Jonathan McCrohan 
Description:
 wavemon- Wireless Device Monitoring Application
Closes: 794535 825544 852784
Changes:
 wavemon (0.8.2-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #825544)
   * d/control: update homepage to reflect move to github (Closes: #794535)
   * d/changelog: remove trailing spaces
   * d/compat: bump to dh compat level to 11
   * d/control: bump Standards-Version to 4.0.1
 - Change Priority from Extra to Optional
   * d/control: remove autotools-dev as a dependency
   * d/patches: refresh patches
   * d/patches: add patch from Helmut Grohne to fix FTCBFS (Closes: #852784)
Checksums-Sha1:
 cd0a5d1becf6a0fa663518f52dc3dcbfcc5f95a7 1828 wavemon_0.8.2-1.dsc
 b890bba3596ebb0bd27d9a267a1c3010c109b604 194977 wavemon_0.8.2.orig.tar.gz
 adcf22602192c79ced0de9723e22f1cb46f161d1 5408 wavemon_0.8.2-1.debian.tar.xz
 10d3c78f14f1f8cd52f4ad8e0955bc74e0d6a348 98608 wavemon-dbgsym_0.8.2-1_amd64.deb
 e4e9f0ceba06946bd438867e907f10d3a9b22f12 6386 wavemon_0.8.2-1_amd64.buildinfo
 1eeff1a7fadd5608b07b2282b0d1e8a4da2d933d 51284 wavemon_0.8.2-1_amd64.deb
Checksums-Sha256:
 b68530c710b2339ecd304eedc4b48c0c83a367df11b9988f50d1c7adfd2c3cc8 1828 
wavemon_0.8.2-1.dsc
 4199e2ad11a036f4289f5ad42a8b0fe518f2b5ff77447f4c366dbcf3f23e91d5 194977 
wavemon_0.8.2.orig.tar.gz
 0e0408fc92f39dbd53b0cf64b295eb35155d4250d538b854be8c5cad52205e61 5408 
wavemon_0.8.2-1.debian.tar.xz
 

Bug#825544: marked as done (wavemon: please make the build reproducible)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 18:36:37 +
with message-id 
and subject line Bug#825544: fixed in wavemon 0.8.2-1
has caused the Debian Bug report #825544,
regarding wavemon: please make the build reproducible
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.)


-- 
825544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wavemon
Version: 0.8.0-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that wavemon could not be built reproducibly.
The order of object files varies during linking.

The attached patch fixes this by sorting the list.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/02-reproducible-build.patch b/debian/patches/02-reproducible-build.patch
new file mode 100644
index 000..f583e36
--- /dev/null
+++ b/debian/patches/02-reproducible-build.patch
@@ -0,0 +1,14 @@
+Author: Reiner Herrmann 
+Description: Sort object files for deterministic linking order
+
+--- a/Makefile.in
 b/Makefile.in
+@@ -21,7 +21,7 @@
+ MAIN	= @PACKAGE_NAME@.c
+ HEADERS	= $(wildcard *.h)
+ PURESRC	= $(filter-out $(MAIN),$(wildcard *.c))
+-OBJS	= $(PURESRC:.c=.o)
++OBJS	= $(sort $(PURESRC:.c=.o))
+ 
+ %.o: %.c $(HEADERS)
+ 	@echo ' CC  ' $<
diff --git a/debian/patches/series b/debian/patches/series
index 18ef635..d9aa474 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 01-patch-makefile.in-to-not-install-docs.patch
+02-reproducible-build.patch


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: wavemon
Source-Version: 0.8.2-1

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

Debian distribution maintenance software
pp.
Jonathan McCrohan  (supplier of updated wavemon 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: Sat, 07 Apr 2018 19:16:24 +0100
Source: wavemon
Binary: wavemon
Architecture: source amd64
Version: 0.8.2-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan McCrohan 
Changed-By: Jonathan McCrohan 
Description:
 wavemon- Wireless Device Monitoring Application
Closes: 794535 825544 852784
Changes:
 wavemon (0.8.2-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #825544)
   * d/control: update homepage to reflect move to github (Closes: #794535)
   * d/changelog: remove trailing spaces
   * d/compat: bump to dh compat level to 11
   * d/control: bump Standards-Version to 4.0.1
 - Change Priority from Extra to Optional
   * d/control: remove autotools-dev as a dependency
   * d/patches: refresh patches
   * d/patches: add patch from Helmut Grohne to fix FTCBFS (Closes: #852784)
Checksums-Sha1:
 cd0a5d1becf6a0fa663518f52dc3dcbfcc5f95a7 1828 wavemon_0.8.2-1.dsc
 b890bba3596ebb0bd27d9a267a1c3010c109b604 194977 wavemon_0.8.2.orig.tar.gz
 adcf22602192c79ced0de9723e22f1cb46f161d1 5408 wavemon_0.8.2-1.debian.tar.xz
 10d3c78f14f1f8cd52f4ad8e0955bc74e0d6a348 98608 wavemon-dbgsym_0.8.2-1_amd64.deb
 e4e9f0ceba06946bd438867e907f10d3a9b22f12 6386 wavemon_0.8.2-1_amd64.buildinfo
 1eeff1a7fadd5608b07b2282b0d1e8a4da2d933d 51284 wavemon_0.8.2-1_amd64.deb
Checksums-Sha256:
 b68530c710b2339ecd304eedc4b48c0c83a367df11b9988f50d1c7adfd2c3cc8 1828 
wavemon_0.8.2-1.dsc
 4199e2ad11a036f4289f5ad42a8b0fe518f2b5ff77447f4c366dbcf3f23e91d5 194977 
wavemon_0.8.2.orig.tar.gz
 0e0408fc92f39dbd53b0cf64b295eb35155d4250d538b854be8c5cad52205e61 5408 
wavemon_0.8.2-1.debian.tar.xz
 adf934d3cccdbabdf6e36e901dc295481676b34dca12c0de7f64e240677aa76b 98608 
wavemon-dbgsym_0.8.2-1_amd64.deb
 d4db353acf66cc6743c5292337f49dc1e8d5d178a59604d52ea686b14f3a9b3a 6386 
wavemon_0.8.2-1_amd64.buildinfo
 

Bug#852784: marked as done (wavemon FTCBFS: uses the build architecture compiler)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 18:36:37 +
with message-id 
and subject line Bug#852784: fixed in wavemon 0.8.2-1
has caused the Debian Bug report #852784,
regarding wavemon FTCBFS: uses the build architecture compiler
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.)


-- 
852784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wavemon
Version: 0.8.1-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

wavemon fails to cross build from source, because it uses the make
default of CC "cc" as the compiler rather than the cross compiler set up
by configure. Fixing the CC assignment in Makefile.in makes the cross
build succeed. Please consider applying the attached patch.

Helmut
diff --minimal -Nru wavemon-0.8.1/debian/changelog 
wavemon-0.8.1/debian/changelog
--- wavemon-0.8.1/debian/changelog  2017-01-03 00:02:03.0 +0100
+++ wavemon-0.8.1/debian/changelog  2017-01-27 09:41:51.0 +0100
@@ -1,3 +1,10 @@
+wavemon (0.8.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: 02-honour-CC.patch (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 27 Jan 2017 09:41:51 +0100
+
 wavemon (0.8.1-1) unstable; urgency=medium
 
   * New upstream release 
diff --minimal -Nru wavemon-0.8.1/debian/patches/02-honour-CC.patch 
wavemon-0.8.1/debian/patches/02-honour-CC.patch
--- wavemon-0.8.1/debian/patches/02-honour-CC.patch 1970-01-01 
01:00:00.0 +0100
+++ wavemon-0.8.1/debian/patches/02-honour-CC.patch 2017-01-27 
09:41:44.0 +0100
@@ -0,0 +1,19 @@
+From: Helmut Grohne 
+Subject: honour the CC variable from configure
+
+A ?= assignment to CC is a noop, because CC has a make default of "cc". This
+breaks e.g. cross compilation.
+
+Index: wavemon-0.8.1/Makefile.in
+===
+--- wavemon-0.8.1.orig/Makefile.in
 wavemon-0.8.1/Makefile.in
+@@ -8,7 +8,7 @@
+ exec_perms  = 0755
+ install-suid-root: exec_perms = 4755
+ 
+-CC ?= @CC@
++CC  = @CC@
+ CFLAGS ?= @CFLAGS@ @LIBNL3_CFLAGS@
+ CPPFLAGS ?= @CPPFLAGS@
+ LDFLAGS  ?= @LDFLAGS@
diff --minimal -Nru wavemon-0.8.1/debian/patches/series 
wavemon-0.8.1/debian/patches/series
--- wavemon-0.8.1/debian/patches/series 2016-01-30 19:25:56.0 +0100
+++ wavemon-0.8.1/debian/patches/series 2017-01-27 09:40:46.0 +0100
@@ -1 +1,2 @@
 01-patch-makefile.in-to-not-install-docs.patch
+02-honour-CC.patch
--- End Message ---
--- Begin Message ---
Source: wavemon
Source-Version: 0.8.2-1

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

Debian distribution maintenance software
pp.
Jonathan McCrohan  (supplier of updated wavemon 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: Sat, 07 Apr 2018 19:16:24 +0100
Source: wavemon
Binary: wavemon
Architecture: source amd64
Version: 0.8.2-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan McCrohan 
Changed-By: Jonathan McCrohan 
Description:
 wavemon- Wireless Device Monitoring Application
Closes: 794535 825544 852784
Changes:
 wavemon (0.8.2-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #825544)
   * d/control: update homepage to reflect move to github (Closes: #794535)
   * d/changelog: remove trailing spaces
   * d/compat: bump to dh compat level to 11
   * d/control: bump Standards-Version to 4.0.1
 - Change Priority from Extra to Optional
   * d/control: remove autotools-dev as a dependency
   * d/patches: refresh patches
   * d/patches: add patch from Helmut Grohne to fix FTCBFS (Closes: #852784)
Checksums-Sha1:
 cd0a5d1becf6a0fa663518f52dc3dcbfcc5f95a7 1828 wavemon_0.8.2-1.dsc
 b890bba3596ebb0bd27d9a267a1c3010c109b604 194977 wavemon_0.8.2.orig.tar.gz
 adcf22602192c79ced0de9723e22f1cb46f161d1 5408 wavemon_0.8.2-1.debian.tar.xz
 

Bug#895118: marked as done (libosmocore: FTBFS on big endian: 5 tests failed unexpectedly)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 18:36:15 +
with message-id 
and subject line Bug#895118: fixed in libosmocore 0.10.2-5
has caused the Debian Bug report #895118,
regarding libosmocore: FTBFS on big endian: 5 tests failed unexpectedly
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.)


-- 
895118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libosmocore
Version: 0.10.2-3
Severity: serious

Hi,

Your package failed to build on all big endian architectures (except for
e.g. m68k or powerpcspe but it was built with nocheck there). It fails
when running the test suite:

Regression tests.
 21: gsm0808 FAILED (testsuite.at:132)
 22: gsm0408 FAILED (testsuite.at:138)
 30: gprs-bssgp  FAILED (testsuite.at:190)
 31: gprs-ns FAILED (testsuite.at:196)
 44: endian  FAILED (testsuite.at:282)

Full logs at https://buildd.debian.org/status/package.php?p=libosmocore
--- End Message ---
--- Begin Message ---
Source: libosmocore
Source-Version: 0.10.2-5

We believe that the bug you reported is fixed in the latest version of
libosmocore, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated libosmocore 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: Sat, 07 Apr 2018 19:07:14 +0100
Source: libosmocore
Binary: libosmocore libosmocodec0 libosmocodec-doc libosmocore9 libosmocore-doc 
libosmogb5 libosmogsm8 libosmogsm-doc libosmovty4 libosmovty-doc libosmoctrl0 
libosmosim0 libosmocore-dev libosmocore-utils
Architecture: source all amd64
Version: 0.10.2-5
Distribution: sid
Urgency: medium
Maintainer: Debian Mobcom Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 libosmocodec-doc - Documentation for the osmo codec library
 libosmocodec0 - Osmo codec library
 libosmocore - Open Source MObile COMmunications CORE library (metapackage)
 libosmocore-dev - Development headers for Open Source MObile COMmunications 
CORE li
 libosmocore-doc - Documentation for the Osmo Core library
 libosmocore-utils - Utilities for gsm
 libosmocore9 - Osmo Core library
 libosmoctrl0 - Osmo control library
 libosmogb5 - Osmo GPRS GB library
 libosmogsm-doc - Documentation for the Osmo GSM utility library
 libosmogsm8 - Osmo GSM utility library
 libosmosim0 - Osmo SIM library
 libosmovty-doc - Documentation for the Osmo VTY library
 libosmovty4 - Osmo VTY library
Closes: 895118
Changes:
 libosmocore (0.10.2-5) unstable; urgency=medium
 .
   * add path-max.patch
   * debian/rules: fix typo for s390x
   * debian/rules: add sparc64 to no-test
   * endian bug was already fixed in 0.10.2-4 (Closes: #895118)
Checksums-Sha1:
 96678680671445d5750f922331bab157f7e753ad 3010 libosmocore_0.10.2-5.dsc
 d838ff0e6566289918b25a7abc90c1a1c370e0a8 543196 libosmocore_0.10.2.orig.tar.xz
 86bbb9795012e2fa2d1cdfe41e7317568adefb59 17712 
libosmocore_0.10.2-5.debian.tar.xz
 4e38d6fa1fcfaa4c082468f01c7bf32e9bbc316a 102252 
libosmocodec-doc_0.10.2-5_all.deb
 a37d9ec8db475a9dd1e954d39c09a3e2c411ca36 6616 
libosmocodec0-dbgsym_0.10.2-5_amd64.deb
 c70e6dbcbaa770d91777491326826fd084503cae 9876 libosmocodec0_0.10.2-5_amd64.deb
 a144fc0daf3f65b2101d245239f1007113b21e99 106644 
libosmocore-dev_0.10.2-5_amd64.deb
 4f4a4f8d65efcbb553a4760c73962c6a29d513e4 429872 
libosmocore-doc_0.10.2-5_all.deb
 b2423b737eac0da6e1f012118a5ba94943eddc37 13144 
libosmocore-utils-dbgsym_0.10.2-5_amd64.deb
 c5a26a09105e806e539756905dc6f5b6c1f247f1 11416 
libosmocore-utils_0.10.2-5_amd64.deb
 1f48983ead88ec1d7b17b84058cbe870d2fce94f 207044 
libosmocore9-dbgsym_0.10.2-5_amd64.deb
 a259335fd95afaf3b982645ecc569ec8ef28d483 80088 libosmocore9_0.10.2-5_amd64.deb
 dcb7ff8fe6e2769beb8f6b5191a16531ddd10025 12014 

Bug#769978: marked as done (cl-portable-aserve: diff for NMU version 1.2.42+cvs.2010.02.08-dfsg-1.2)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 17:49:19 +
with message-id 
and subject line Bug#769978: fixed in cl-portable-aserve 
1.2.42+cvs.2010.02.08-dfsg-2
has caused the Debian Bug report #769978,
regarding cl-portable-aserve: diff for NMU version 
1.2.42+cvs.2010.02.08-dfsg-1.2
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.)


-- 
769978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cl-portable-aserve
Version: 1.2.42+cvs.2010.02.08-dfsg-1.1
Severity: normal
Tags: patch pending
Control: tags 767811 + pending
Control: tags 769509 + pending
Control: tags 769512 + pending
Control: tags 769513 + pending

Dear maintainer,

I've prepared an NMU for cl-portable-aserve (versioned as
1.2.42+cvs.2010.02.08-dfsg-1.2) and uploaded it to DELAYED/2. Please
feel free to tell me if I should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -u cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/changelog cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/changelog
--- cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/changelog
+++ cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/changelog
@@ -1,3 +1,11 @@
+cl-portable-aserve (1.2.42+cvs.2010.02.08-dfsg-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add dependency on common-lisp-controller to all binary packages. (Closes:
+#767811, #769509, #769512, #769513)
+
+ -- Sebastian Ramacher   Tue, 18 Nov 2014 01:45:26 +0100
+
 cl-portable-aserve (1.2.42+cvs.2010.02.08-dfsg-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/control cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/control
--- cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/control
+++ cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/control
@@ -12,7 +12,7 @@
 
 Package: cl-aserve
 Architecture: all
-Depends: cl-acl-compat, cl-htmlgen, cl-ppcre, cl-puri, ${misc:Depends}
+Depends: cl-acl-compat, cl-htmlgen, cl-ppcre, cl-puri, ${misc:Depends}, common-lisp-controller
 Suggests: cl-webactions
 Description: Portable Aserve
  A portable version of AllegroServe which is a web application server
@@ -21,7 +21,7 @@
 
 Package: cl-acl-compat
 Architecture: all
-Depends: cl-ppcre, cl-puri, ${misc:Depends}
+Depends: cl-ppcre, cl-puri, ${misc:Depends}, common-lisp-controller
 Description: Compatibility layer for Allegro Common Lisp
  A thin compatibility-layer that emulates library functions provided
  by Allegro Common Lisp. It is used
@@ -30,7 +30,7 @@
 
 Package: cl-htmlgen
 Architecture: all
-Depends: cl-ppcre, cl-puri, ${misc:Depends}
+Depends: cl-ppcre, cl-puri, ${misc:Depends}, common-lisp-controller
 Description: HTML generation library for Common Lisp programs
  cl-htmlgen is Franz's library for generating HTML from Common Lisp programs.
  It is limited to generating HTML code, so you may want to use the cl-lml2
@@ -38,7 +38,7 @@
 
 Package: cl-webactions
 Architecture: all
-Depends: cl-aserve, cl-ppcre, cl-puri, ${misc:Depends}
+Depends: cl-aserve, cl-ppcre, cl-puri, ${misc:Depends}, common-lisp-controller
 Description: HTTP dispatch library for cl-aserve
  Webactions is Franz's library for dispatching HTTP requests as well as 
  processing HTML templates. It uses the cl-aserve package.


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: cl-portable-aserve
Source-Version: 1.2.42+cvs.2010.02.08-dfsg-2

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated 
cl-portable-aserve 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, 07 Apr 2018 18:54:36 +0200
Source: cl-portable-aserve
Binary: cl-aserve cl-acl-compat cl-htmlgen cl-webactions
Architecture: source
Version: 1.2.42+cvs.2010.02.08-dfsg-2
Distribution: unstable
Urgency: medium

Bug#894386: marked as done (libinstpatch: memory corruption in file IpatchSF2Reader.c)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 17:35:21 +
with message-id 
and subject line Bug#894386: fixed in libinstpatch 1.0.0-7
has caused the Debian Bug report #894386,
regarding libinstpatch: memory corruption in file IpatchSF2Reader.c
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.)


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

Dear Maintainer,

The file IpatchSF2Reader.c has seen in the upstream code base some fixes
of potential memory corruption. This can lead to undefined behaviour.

I provide a patch with the specific changes, fixing the issue.

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/24 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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- libinstpatch-1.0.0/libinstpatch/IpatchSF2Reader.c   2010-10-25 
12:46:26.0 -0400
+++ libinstpatch-1.0.0.orig/libinstpatch/IpatchSF2Reader.c  2018-03-29 
11:57:52.433939326 -0400
@@ -647,13 +647,13 @@
   if (!ipatch_file_read (riff->handle, bag_table, chunk->size, err))
 return (FALSE);   /* bag_table will be freed by finalize() */
 
-  pgenndx = IPATCH_FILE_SWAP16 (riff->handle, _table[0]);
-  pmodndx = IPATCH_FILE_SWAP16 (riff->handle, _table[1]);
+  pgenndx = IPATCH_FILE_SWAP16 (riff->handle->file, _table[0]);
+  pmodndx = IPATCH_FILE_SWAP16 (riff->handle->file, _table[1]);
 
   for (i=0; i < reader->pbag_count; i++)
 {
-  genndx = IPATCH_FILE_SWAP16 (riff->handle, _table[(i+1)*2]);
-  modndx = IPATCH_FILE_SWAP16 (riff->handle, _table[(i+1)*2+1]);
+  genndx = IPATCH_FILE_SWAP16 (riff->handle->file, _table[(i+1)*2]);
+  modndx = IPATCH_FILE_SWAP16 (riff->handle->file, _table[(i+1)*2+1]);
 
   if (genndx < pgenndx)
{
@@ -973,13 +973,13 @@
   if (!ipatch_file_read (riff->handle, bag_table, chunk->size, err))
 return (FALSE);   /* bag_table will be freed by finalize() */
 
-  pgenndx = IPATCH_FILE_SWAP16 (riff->handle, _table[0]);
-  pmodndx = IPATCH_FILE_SWAP16 (riff->handle, _table[1]);
+  pgenndx = IPATCH_FILE_SWAP16 (riff->handle->file, _table[0]);
+  pmodndx = IPATCH_FILE_SWAP16 (riff->handle->file, _table[1]);
 
   for (i=0; i < reader->ibag_count; i++)
 {
-  genndx = IPATCH_FILE_SWAP16 (riff->handle, _table[(i+1)*2]);
-  modndx = IPATCH_FILE_SWAP16 (riff->handle, _table[(i+1)*2+1]);
+  genndx = IPATCH_FILE_SWAP16 (riff->handle->file, _table[(i+1)*2]);
+  modndx = IPATCH_FILE_SWAP16 (riff->handle->file, _table[(i+1)*2+1]);
 
   if (genndx < pgenndx)
{
--- End Message ---
--- Begin Message ---
Source: libinstpatch
Source-Version: 1.0.0-7

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated libinstpatch 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: Sat, 07 Apr 2018 18:26:26 +0100
Source: libinstpatch
Binary: libinstpatch-1.0-0 libinstpatch-dev libinstpatch-doc
Architecture: source
Version: 1.0.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 libinstpatch-1.0-0 - MIDI instrument editing library
 libinstpatch-dev - MIDI instrument editing library development files
 libinstpatch-doc - MIDI instrument editing library documentation
Closes: 894386
Changes:
 libinstpatch (1.0.0-7) unstable; urgency=medium
 .
   * Team upload.
 .
   [ James Cowgill ]
   * debian/compat: Use debhelper compat 11.
   * debian/control:
 - Set Maintainer to debian-multimedia@lists.d.o.
 - Drop unneeded 

Bug#862794: marked as done (munin-plugins-core needs to depend on package time or http_loadtime plugin breaks)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 17:05:56 +
with message-id 
and subject line Bug#862794: fixed in munin 2.999.7-1
has caused the Debian Bug report #862794,
regarding munin-plugins-core needs to depend on package time or http_loadtime 
plugin breaks
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.)


-- 
862794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: munin-plugins-core
Version: 2.0.25-1+deb8u3
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

/usr/share/munin/plugins/http_loadtime
line 34
time_bin=`which time`

produces this error on server:
2017/05/07 04:55:23 [ERROR] In RRD: Error updating
/var/lib/munin/doublehp.org/rpi-08.doublehp.org-http_loadtime-loadtime-g.rrd:
/var/lib/munin/doublehp.org/rpi-08.doublehp.org-http_loadtime-loadtime-g.rrd:
found extra data on update argument:

The fix is trivial: install package time. So, the fix for the distro is to
make munin-plugins-core depend on time.

If you refuse to add this dep, you want to remove http_loadtime from
auto-install, and produce a warning telling admin how to get this plugin
to work.

*** End of the template - remove these template lines ***


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 8.0 (jessie)
Release:8.0
Codename:   jessie
Architecture: armv7l

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

Versions of packages munin-plugins-core depends on:
ii  munin-common  2.0.25-1+deb8u3
ii  perl  5.20.2-3+deb8u6

Versions of packages munin-plugins-core recommends:
ii  libnet-snmp-perl  6.0.1-2

Versions of packages munin-plugins-core suggests:
pn  conntrack
pn  libcache-cache-perl  
pn  libdbd-mysql-perl
pn  libnet-dns-perl  
pn  libnet-netmask-perl  
pn  libnet-telnet-perl   
pn  libxml-parser-perl   
ii  python   2.7.9-1
pn  ruby | ruby-interpreter  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: munin
Source-Version: 2.999.7-1

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated munin 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: Sat, 07 Apr 2018 16:45:48 +
Source: munin
Binary: munin-node munin-plugins-core munin-plugins-extra munin-plugins-http 
munin-plugins-mysql munin-plugins-pgsql munin-plugins-snmp munin-plugins-ldap 
munin-plugins-irc munin-plugins-dns munin-plugins-mail munin-plugins-time 
munin-plugins-network munin-plugins-jenkins libmunin-perl libmunin-master-perl 
libmunin-node-perl libmunin-plugin-perl libmunin-plugin-http-perl 
libmunin-plugin-snmp-perl libmunin-plugin-pgsql-perl munin munin-common 
munin-async munin-doc
Architecture: source
Version: 2.999.7-1
Distribution: experimental
Urgency: medium
Maintainer: Munin Debian Maintainers 
Changed-By: Holger Levsen 
Description:
 libmunin-master-perl - perl modules for munin master
 libmunin-node-perl - perl module Munin::Node
 libmunin-perl - common perl modules for munin
 libmunin-plugin-http-perl - perl bindings for HTTP munin plugins
 libmunin-plugin-perl - perl bindings for munin plugins
 libmunin-plugin-pgsql-perl - perl bindings for Postgresql munin plugins
 libmunin-plugin-snmp-perl - perl bindings for SNMP munin plugins
 munin  - network-wide graphing framework (grapher/gatherer)
 munin-async - network-wide graphing framework (async master/client)
 munin-common - network-wide graphing framework (common)
 munin-doc  - network-wide graphing framework (documentation)
 munin-node - network-wide graphing framework (node)
 munin-plugins-core - network-wide graphing 

Bug#886517: marked as done (munin-plugins-core: http_loadtime plugin depends on time package)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 17:05:56 +
with message-id 
and subject line Bug#862794: fixed in munin 2.999.7-1
has caused the Debian Bug report #862794,
regarding munin-plugins-core: http_loadtime plugin depends on time 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.)


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

Hi,

 munin http_loadtime plugin doesn't work.

> $ sudo munin-run http_loadtime auto
> http___localhost_.value /etc/munin/plugins/http_loadtime: line 105: -f: 
> command not found

 Then install time package, it works.

> $ sudo apt install time
(snip)
> $ sudo munin-run http_loadtime auto
> http___localhost_.value 0.00

 http_loadtime is automatically enabled if its host runs apache.
>From 01fd1edf215ff378ca9016e60d008392cc0adcd5 Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Sun, 7 Jan 2018 14:22:03 +0900
Subject: [PATCH] add Depends: time for http_loadtime

---
 debian/control | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index aa805521..b1138662 100644
--- a/debian/control
+++ b/debian/control
@@ -63,7 +63,8 @@ Description: network-wide graphing framework (node)
 Package: munin-plugins-core
 Provides: munin-plugins
 Architecture: all
-Depends: ${perl:Depends}, ${misc:Depends}, munin-common (>= ${binary:Version})
+Depends: ${perl:Depends}, ${misc:Depends}, munin-common (>= ${binary:Version}),
+ time,
 Recommends: libnet-snmp-perl
 Suggests:
  conntrack,
-- 
2.15.1

--- End Message ---
--- Begin Message ---
Source: munin
Source-Version: 2.999.7-1

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated munin 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: Sat, 07 Apr 2018 16:45:48 +
Source: munin
Binary: munin-node munin-plugins-core munin-plugins-extra munin-plugins-http 
munin-plugins-mysql munin-plugins-pgsql munin-plugins-snmp munin-plugins-ldap 
munin-plugins-irc munin-plugins-dns munin-plugins-mail munin-plugins-time 
munin-plugins-network munin-plugins-jenkins libmunin-perl libmunin-master-perl 
libmunin-node-perl libmunin-plugin-perl libmunin-plugin-http-perl 
libmunin-plugin-snmp-perl libmunin-plugin-pgsql-perl munin munin-common 
munin-async munin-doc
Architecture: source
Version: 2.999.7-1
Distribution: experimental
Urgency: medium
Maintainer: Munin Debian Maintainers 
Changed-By: Holger Levsen 
Description:
 libmunin-master-perl - perl modules for munin master
 libmunin-node-perl - perl module Munin::Node
 libmunin-perl - common perl modules for munin
 libmunin-plugin-http-perl - perl bindings for HTTP munin plugins
 libmunin-plugin-perl - perl bindings for munin plugins
 libmunin-plugin-pgsql-perl - perl bindings for Postgresql munin plugins
 libmunin-plugin-snmp-perl - perl bindings for SNMP munin plugins
 munin  - network-wide graphing framework (grapher/gatherer)
 munin-async - network-wide graphing framework (async master/client)
 munin-common - network-wide graphing framework (common)
 munin-doc  - network-wide graphing framework (documentation)
 munin-node - network-wide graphing framework (node)
 munin-plugins-core - network-wide graphing framework (plugins for node)
 munin-plugins-dns - munin plugins for monitoring DNS servers
 munin-plugins-extra - community contributed plugins for munin node
 munin-plugins-http - munin plugins for monitoring web servers
 munin-plugins-irc - munin plugins for monitoring IRC servers
 munin-plugins-jenkins - munin plugins for monitoring the Jenkins CI server
 munin-plugins-ldap - munin plugins for monitoring LDAP servers
 munin-plugins-mail - munin plugins for monitoring mail servers
 munin-plugins-mysql - munin plugins for 

Processed: Re: [Qa-jenkins-dev] Bug#871544: jenkins.debian.org: jtx1b runs armhf builds with wrong personality

[Debian Bug Tracking System]

Processing control commands:

> tag -1 wontfix
Bug #871544 [jenkins.debian.org] jenkins.debian.org: jtx1b runs armhf builds 
with wrong personality
Added tag(s) wontfix.
> close -1
Bug #871544 [jenkins.debian.org] jenkins.debian.org: jtx1b runs armhf builds 
with wrong personality
Marked Bug as done

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

Bug#895136: marked as done (debian-policy: §9.1.2 - Contains example that is misleadingly different than what the policy mandates)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 16:35:42 +
with message-id 
and subject line Bug#895136: fixed in debian-policy 4.1.4.1
has caused the Debian Bug report #895136,
regarding debian-policy: §9.1.2 - Contains example that is misleadingly 
different than what the policy mandates
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.)


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

Last paragraph of 9.1.2 reads:

"""
If /etc/staff-group-for-usr-local does not exist, /usr/local and all
subdirectories created by packages should have permissions 0755 and be
owned by root:root. If /etc/staff-group-for-usr-local exists,
/usr/local and subdirectories should have permissions 2775
(group-writable and set-group-id) and be owned by root:staff.
"""

In the middle of 9.1.2, there is the following example of how to do
directory creation in /usr/local:

"""
if [ ! -e /usr/local/share/emacs ]; then
if mkdir /usr/local/share/emacs 2>/dev/null; then
if chown root:staff /usr/local/share/emacs; then
chmod 2775 /usr/local/share/emacs || true
fi
fi
fi
"""

The example is way too simple to comply with policy.  A more compliant
example would be:

"""
if [ ! -e /usr/local/share/emacs ]; then
if mkdir /usr/local/share/emacs 2>/dev/null; then
if test -e /etc/staff-group-for-usr-local ; then
if chown root:staff /usr/local/share/emacs; then
chmod 2775 /usr/local/share/emacs || true
fi
elif chown root:staff /usr/local/share/emacs; then
chmod 2775 /usr/local/share/emacs || true
fi
fi
fi
"""

Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Source: debian-policy
Source-Version: 4.1.4.1

We believe that the bug you reported is fixed in the latest version of
debian-policy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated debian-policy 
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: Sat, 07 Apr 2018 09:13:01 -0700
Source: debian-policy
Binary: debian-policy
Architecture: all source
Version: 4.1.4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Policy Editors 
Changed-By: Sean Whitton 
Closes: 895136
Description: 
 debian-policy - Debian Policy Manual and related documents
Changes:
 debian-policy (4.1.4.1) unstable; urgency=medium
 .
   * Fix some errors in upgrading checklist.
 Thanks to several people for noticing these.
 Thanks to Jeremy Bicha for a patch.
   * Soften wording in upgrading checklist for removal of get-orig-source
 target.
 Thanks Helmut Grohne for the new wording.
   * Fix sample postinst in 9.1.2 to comply with new required permissions
 for /usr/local (Closes: #895136).
 Thanks to Niels Thykier for noticing the problem, and for the new
 sample script.
 - Reorder 9.1.2 so that details of the permissions requirement appear
   before the sample postinst.
   This ensures that the complexity of the sample postinst makes sense
   to the reader.
Checksums-Sha1: 
 d5fc8ce486af7c5b2fa8297e45feed4e1dadb310 2001 debian-policy_4.1.4.1.dsc
 8748ae98d9be997e21f7661edbc3ccaf3bbba92a 677248 debian-policy_4.1.4.1.tar.xz
 27ea7f496f630e5c5f6570e8985a0f2dc07be099 2387580 debian-policy_4.1.4.1_all.deb
 e493f96c7ce8f5414b5ef7c7788ab8daf7f32000 12126 
debian-policy_4.1.4.1_amd64.buildinfo
Checksums-Sha256: 
 5e87b0946a4321e97a7a86ef6a26c861baebe4227a76f184235e5a43b879ecd4 2001 
debian-policy_4.1.4.1.dsc
 35f043c70bc88ee1d094ad1877005eb09a21eb6f7a6fa06ba7410ebc07a0618d 677248 
debian-policy_4.1.4.1.tar.xz
 131cf8851a98a9465597b179a7d73e9bcb0b4c40a3c7084eb4d9206df22adc46 2387580 
debian-policy_4.1.4.1_all.deb
 d331f47b51058142406c37a24210a0bec6d94e9fc3021e49e426256f63f2069a 12126 
debian-policy_4.1.4.1_amd64.buildinfo
Files: 
 

Bug#891085: marked as done (aseba-plugin-blockly: missing build-dependency for python2)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 16:34:38 +
with message-id 
and subject line Bug#891085: fixed in aseba-plugin-blockly 20180211+git-2
has caused the Debian Bug report #891085,
regarding aseba-plugin-blockly: missing build-dependency for python2
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.)


-- 
891085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aseba-plugin-blockly
Version: 20180211+git-1
Severity: serious
Justification: fails to build from source

Hi,

aseba-plugin-blockly FTBFS since it uses python2 without depending on
it:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/aseba-plugin-blockly-20180211+git'
mkdir build
bash build.sh build/blocky.zip
+++ dirname build.sh
++ cd .
++ pwd
+ SRC_DIR=/build/aseba-plugin-blockly-20180211+git
+ BUILD_DIR=/build/aseba-plugin-blockly-20180211+git
++ mktemp -d
+ TEMP_DIR=/tmp/tmp.QJhv5lK8jV
+ trap atexit EXIT
+ cp -r /build/aseba-plugin-blockly-20180211+git/blockly 
/build/aseba-plugin-blockly-20180211+git/closure-library 
/build/aseba-plugin-blockly-20180211+git/thymio_blockly 
/build/aseba-plugin-blockly-20180211+git/index.html 
/build/aseba-plugin-blockly-20180211+git/media /tmp/tmp.QJhv5lK8jV
+ ARCHIVE=/build/aseba-plugin-blockly-20180211+git/blockly.zip
+ '[' '!' -z build/blocky.zip ']'
++ realpath build/blocky.zip
+ ARCHIVE=/build/aseba-plugin-blockly-20180211+git/build/blocky.zip
+ '[' -f /build/aseba-plugin-blockly-20180211+git/build/blocky.zip ']'
+ pushd /tmp/tmp.QJhv5lK8jV
/tmp/tmp.QJhv5lK8jV /build/aseba-plugin-blockly-20180211+git
+ pushd blockly
/tmp/tmp.QJhv5lK8jV/blockly /tmp/tmp.QJhv5lK8jV 
/build/aseba-plugin-blockly-20180211+git
+ echo 'Compiling blockly'
Compiling blockly
+ python2 ./build.py
build.sh: line 33: python2: command not found
+ atexit
+ rm -rf /tmp/tmp.QJhv5lK8jV
make[1]: *** [debian/rules:24: override_dh_auto_build] Error 127
make[1]: Leaving directory '/build/aseba-plugin-blockly-20180211+git'


Andreas


aseba-plugin-blockly_20180211+git-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: aseba-plugin-blockly
Source-Version: 20180211+git-2

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated 
aseba-plugin-blockly 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, 07 Apr 2018 17:26:09 +0200
Source: aseba-plugin-blockly
Binary: aseba-plugin-blockly
Architecture: source all
Version: 20180211+git-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 aseba-plugin-blockly - blockly plugin to enhance the package Aseba
Closes: 891085
Changes:
 aseba-plugin-blockly (20180211+git-2) unstable; urgency=medium
 .
   * added a build-dependency on python-all, python-bs4 and python-lxml.
 Closes: #891085
Checksums-Sha1:
 73e2886877439c0a4e26063ed34ad510b1ac034b 1984 
aseba-plugin-blockly_20180211+git-2.dsc
 e0fff26d34fa7b4f61d348bba3fe0424725bc229 341648 
aseba-plugin-blockly_20180211+git-2.debian.tar.xz
 55f098ebd02d8b9d1a29f534976894c91b8906cf 342272 
aseba-plugin-blockly_20180211+git-2_all.deb
 ed684ad998d31fd9b72e2a9e19942f583f6eb07c 6547 
aseba-plugin-blockly_20180211+git-2_amd64.buildinfo
Checksums-Sha256:
 6caa77e37aa4e3ec0478f04bda032bb5b2351fe5f15856c82eed5574956d68d5 1984 
aseba-plugin-blockly_20180211+git-2.dsc
 a430d2df42dc0457de25a5fecef7a5d1713979e70440660728857b77c3c2a867 341648 
aseba-plugin-blockly_20180211+git-2.debian.tar.xz
 c1f35266f216940182988ee528ac95526ddd22eb25e06a94641ed66df07c28e3 342272 
aseba-plugin-blockly_20180211+git-2_all.deb
 c859ccf30777956a3118321697be3ae1aa904d8318b000eff92042ec4ec1aaff 6547 
aseba-plugin-blockly_20180211+git-2_amd64.buildinfo
Files:
 f2b59f13ebb29d6bbd86cc4c1cb591b5 1984 non-free/devel optional 

Bug#886046: marked as done (soundconverter: Depends on gconf)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 16:21:17 +
with message-id 
and subject line Bug#886046: fixed in soundconverter 3.0.0-2
has caused the Debian Bug report #886046,
regarding soundconverter: Depends on gconf
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.)


-- 
886046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: soundconverter
Version: 3.0.0~beta1-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: soundconverter
Source-Version: 3.0.0-2

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated soundconverter 
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, 07 Apr 2018 18:02:43 +0200
Source: soundconverter
Binary: soundconverter
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 soundconverter - GNOME application to convert audio files into other formats
Closes: 886046
Changes:
 soundconverter (3.0.0-2) unstable; urgency=medium
 .
   * debian/patches: Only fetch profiles if gconf is available. (Closes: 
#886046)
Checksums-Sha1:
 c85e11ca550fc012fcf68e6f717db4ceb7c194bd 2099 soundconverter_3.0.0-2.dsc
 2beb7960db93cc46ed70c0a5764b596a0d9f4767 7164 
soundconverter_3.0.0-2.debian.tar.xz
Checksums-Sha256:
 59e3f2b3f874c25bffc07fbabc4e7bab2ce2c5a644b8c4a73f8f2ad91993bd59 2099 
soundconverter_3.0.0-2.dsc
 806f34be281a856e820f2142ef9a59f3e0609ed84a561690e74874061750abaf 7164 
soundconverter_3.0.0-2.debian.tar.xz
Files:
 5d89f7d584c143df917e3e27dbf6 2099 gnome optional soundconverter_3.0.0-2.dsc
 13f889f6c2bb388d2a9dafa943dcba51 7164 gnome optional 
soundconverter_3.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAcBQJayO1HFRxzcmFtYWNoZXJAZGViaWFuLm9yZwAKCRBp8vxRbqcZ
k7k2D/9KLUUl5Y6PigrAGZFw2qvhvszjz+nkQOWYruqolm6EsK6lyYgwb63q0zpW
1XX5Eff0N1DM0R9CqFe40U7TNpmR8pd1XSfjvbT8fF5zsyRdA90sq6yTOpHVF9nC
9/95r5c/hKm2vw2WFmyrKrPm4Ar8XkVA/bPJL04AlFLnvLFQ+XLHZea9zLso7cGJ
UsNZKxKPrGHDD38QocisEkGDAQ50xIaDkGonbfEPFXOso1JZn8+q6RQSVA5h/Wbc
Qrken/vcluADOtPbiz1XFxo5QSbOX4NW8dXNC+edQCZHH+sfT0DcSeNJZWhEjjN4
Gn7D70P4wM9PzvoZ+HKbMxFf8o7mIJHFOBbS3FJOGIlzjagtnrdMKdc4krW65QcS
oVUI7QPSdl9d/ngvVyii7MexoHAHRunMLeGfxzW80XFHFVi5c3VO+USlggqKiYIX
UEdakMw3hJgz0L0hDl/ioh8kbdgaUnijNsrfkP6YVk3oTgcOGyO7EuLQ9hht3QOe
8QHAvrmL2B+HnOMqxIPGn5o8O2BBQ/aU5n98foYfHGUZhYZIGWclI8A0EOBSZ+oJ
sTpwxmB5smlww8TCQHzGUgAvUslZQCkwZwgCYv0ICwnh4H9vYvRxM6GgoP4iQyuH
XZrKk+Jf7hA1u7ne6N+zFKDdse2eDU42YxEkCnWGlLdrKbdZ4Q==
=FjIH
-END PGP SIGNATURE End Message ---

Bug#891736: marked as done (node-marked-man FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 16:21:11 +
with message-id 
and subject line Bug#891736: fixed in node-marked-man 0.3.0-2
has caused the Debian Bug report #891736,
regarding node-marked-man FTBFS: test 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.)


-- 
891736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-marked-man
Version: 0.3.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-marked-man.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-marked-man-0.3.0'
nodejs test/compare.js
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/blockquotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/definition_list_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/dots_at_line_start_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/ellipses.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/entity_encoding_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/graves.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/links.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/markdown_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/nested_list_with_code.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/pre_block_with_quotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/table.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/underline_spacing_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/links.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/graves.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/entity_encoding_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/ellipses.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/dots_at_line_start_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/definition_list_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/blockquotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/nested_list_with_code.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/markdown_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/pre_block_with_quotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/underline_spacing_test.err
:173: warning [p 1, 2.0i, div `3tbd17,3', 0.0i]: cannot adjust 
line
:272: warning [p 1, 2.0i, div `3tbd28,3', 0.2i]: cannot adjust 
line
:671: warning [p 1, 2.0i, div `3tbd73,0', 0.0i]: cannot adjust 
line
warning: file `', around line 18:
  table wider than line width
warning: file `', around line 13:
  table squeezed horizontally to fit line length

Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/table.err
Failed tests:  12
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-marked-man
Source-Version: 0.3.0-2

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-marked-man 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: Sat, 07 Apr 2018 17:39:04 +0200
Source: node-marked-man
Binary: node-marked-man
Architecture: source
Version: 0.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: 

Bug#879187: marked as done (zsh-completion: add --clean for vim)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:27:57 +
with message-id 
and subject line Bug#879187: fixed in zsh 5.4.2-test-2-1
has caused the Debian Bug report #879187,
regarding zsh-completion: add --clean for vim
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.)


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


Hi,
Vim since patchlevel 8.0.0716 includes the --clean argument for starting 
in a clean mode (only loading defaults.vim and in non-cp mode). So 
please add this patch to the vim completion.

Thanks.

Christian

--- _vim.backup 2017-10-20 08:48:15.615046979 +0200
+++ _vim2017-10-20 08:52:07.185668608 +0200
@@ -74,6 +74,7 @@
   '(- *)--version[print version information and exit]'
   '(* -q)-t[edit file where tag is defined]:tag:_complete_tag'
   '(-t -q)*:file:_vim_files'
+  '--clean[start with defaults in non-compatible mode]'
 )
 [[ $service != *g* ]] && arguments+='-g[start with GUI]'
 [[ $service != r* ]] && arguments+='-Z[restricted mode]'

-- Package-specific info:

Packages which provide vendor completions:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion 
 Architecture Description
+++-===---===
ii  cmus1:2.8.0~rc0-dmo4
 amd64lightweight ncurses audio player
ii  curl7.55.1-1
 amd64command line tool for transferring data with URL 
syntax
ii  mpv 1:0.25.0-dmo2   
 amd64Free and open-source general-purpose video player
ii  pulseaudio  11.0-1  
 amd64PulseAudio sound server
ii  silversearcher-ag   2.0.0-1 
 amd64very fast grep-like program, alternative to 
ack-grep
ii  systemd 234-3   
 amd64system and service manager
ii  udev234-3   
 amd64/dev/ and hotplug management daemon
ii  vlc-bin 1:2.2.6-dmo2+deb9u1 
 amd64binaries from VLC

dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/


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

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: systemd (via /run/systemd/system)

Versions of packages zsh depends on:
ii  dpkg1.18.24
ii  libc6   2.24-17
ii  libcap2 1:2.25-1
ii  libtinfo5   6.0+20170902-1
ii  zsh-common  5.4.1-1

Versions of packages zsh recommends:
ii  libc6 2.24-17
ii  libncursesw5  6.0+20170902-1
ii  libpcre3  2:8.39-4

Versions of packages zsh suggests:
pn  zsh-doc  

-- no debconf information

Liebe Grüße
Christian
-- 
Unser Verlangen nach Lust verknüpft uns der Gegenwart. Die Sorge um
unser Heil macht uns von der Zukunft abhängig.
-- Charles Baudelaire
--- End Message ---
--- Begin Message ---
Source: zsh
Source-Version: 5.4.2-test-2-1

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated zsh package)

(This message was generated automatically at their request; if you
believe that 

Bug#823133: marked as done (subversion FTBFS on Alpha: misaligned strings in the test suite)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:26:08 +
with message-id 
and subject line Bug#823133: fixed in subversion 1.10.0~rc2-1
has caused the Debian Bug report #823133,
regarding subversion FTBFS on Alpha: misaligned strings in the test suite
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.)


-- 
823133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: subversion
Version: 1.9.4-1
Severity: important
Justification: fails to build from source (but built in the past)
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha

subversion FTBFS on Alpha due to a test suite failure [1]:

START: utf-test
PASS:  lt-utf-test 1: test is_valid/last_valid
PASS:  lt-utf-test 2: test last_valid/last_valid2
PASS:  lt-utf-test 3: test svn_utf_cstring_to_utf8_ex2
PASS:  lt-utf-test 4: test svn_utf_cstring_from_utf8_ex2
PASS:  lt-utf-test 5: test svn_utf__normcmp
PASS:  lt-utf-test 6: test svn_utf__glob
PASS:  lt-utf-test 7: test svn_utf__fuzzy_escape
PASS:  lt-utf-test 8: test svn_utf__is_normalized
svn_tests: E235000: In file 
'/«PKGBUILDDIR»/subversion/tests/libsvn_subr/utf-test.c' line 807: assertion 
failed (0 == strcmp(result->data, tc->result))
FAIL:  lt-utf-test 9: test svn_utf__utf{16,32}_to_utf8
END: utf-test
ELAPSED: utf-test 0:00:00.603655

This failure occurs because the test suite allocates char aligned
strings in function test_utf_conversions() of file
subversion/tests/libsvn_subr/utf-test.c and passes those strings
to functions svn_utf__utf16_to_utf8() and svn_utf__utf32_to_utf8()
which are defined (in file subversion/libsvn_subr/utf.c) to take
apr_uint32_t * and apr_uint16_t * args respectively.  On
architectures with strict alignment requirements this is undefined
behaviour.  On Alpha, gcc likes to add bugs..., I mean, _optimise_
code, when the args are declared to be aligned by using a particular
CPU load instruction that neither traps nor gives correct results
if the args are not actually aligned.

I attach a patch that aligns the test strings in utf-test.c to be
aligned to apr_uint32_t (i.e. 32-bit alignment).  With that patch
subversion builds successfully to completion on Alpha.

Cheers
Michael.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=subversion=alpha=1.9.4-1=1461928473
Index: subversion-1.9.4/subversion/tests/libsvn_subr/utf-test.c
===
--- subversion-1.9.4.orig/subversion/tests/libsvn_subr/utf-test.c   
2016-05-01 21:05:58.763536825 +1200
+++ subversion-1.9.4/subversion/tests/libsvn_subr/utf-test.c2016-05-01 
21:05:58.755722518 +1200
@@ -745,7 +745,7 @@
   {
 svn_boolean_t sixteenbit;
 svn_boolean_t bigendian;
-const char *source;
+const _Alignas(apr_int32_t) char *source;
 const char *result;
   } tests[] = {
 
--- End Message ---
--- Begin Message ---
Source: subversion
Source-Version: 1.10.0~rc2-1

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated subversion 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: Sat, 07 Apr 2018 11:09:43 -0400
Source: subversion
Binary: subversion libsvn1 libsvn-dev libsvn-doc libapache2-mod-svn 
python-subversion subversion-tools libsvn-java libsvn-perl ruby-svn
Architecture: source
Version: 1.10.0~rc2-1
Distribution: experimental
Urgency: medium
Maintainer: James McCoy 
Changed-By: James McCoy 
Description:
 libapache2-mod-svn - Apache Subversion server modules for Apache httpd
 libsvn-dev - Development files for Apache Subversion libraries
 libsvn-doc - Developer documentation for libsvn
 libsvn-java - Java bindings for Apache Subversion
 libsvn-perl - Perl bindings for Apache Subversion
 libsvn1- Shared libraries used by Apache Subversion
 python-subversion - Python bindings for Apache Subversion
 ruby-svn   - Ruby 

Bug#483040: marked as done ([thunar-thumbnailers] using more than one (processor-)core)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:26:15 +
with message-id 
and subject line Bug#483040: fixed in tumbler 0.2.1-1
has caused the Debian Bug report #483040,
regarding [thunar-thumbnailers] using more than one (processor-)core
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.)


-- 
483040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar-thumbnailers
Version: 0.3.0-1
Severity: wishlist

--- Please enter the report below this line. ---
It would be nice if thunar could use more than only one processor-core
when it creates the thumbnails for images.


Thank you for your fine work!Matthias Krüger
--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.24-1-amd64

Debian Release: lenny/sid
  500 testing security.debian.org
  500 testing 141.76.2.4

--- Package information. ---
Depends  (Version) | Installed
==-+-===
imagemagick| 7:6.3.7.9.dfsg1-2+b2
thunar  (>= 0.5.1) | 0.9.0-8



--- End Message ---
--- Begin Message ---
Source: tumbler
Source-Version: 0.2.1-1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated tumbler 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: Sat, 07 Apr 2018 15:57:21 +0200
Source: tumbler
Binary: tumbler tumbler-plugins-extra tumbler-common libtumbler-1-0 
libtumbler-1-dev
Architecture: source
Version: 0.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 libtumbler-1-0 - library for tumbler, a D-Bus thumbnailing service
 libtumbler-1-dev - library for tumbler, a D-Bus thumbnailing service 
(development)
 tumbler- D-Bus thumbnailing service
 tumbler-common - D-Bus thumbnailing service (common files)
 tumbler-plugins-extra - D-Bus thumbnailing service (additional plugins)
Closes: 483040
Changes:
 tumbler (0.2.1-1) unstable; urgency=medium
 .
   [ Yves-Alexis Perez ]
   * add patch to use multithreading (closes: #483040)
   * add a d/gbp.conf configuration file
 .
   [ Unit 193 ]
   * New upstream version 0.2.1
   * Update Standards-Version to 4.1.4.
   * d/changelog: Remove trailing whitespace from previous entry.
   * d/control, d/copyright, d/watch: Use https where possible.
   * d/control: Move libtumbler-1-0 to section 'libs'.
   * d/rules: Replace the override on dh_install with dh_missing.
Checksums-Sha1:
 515188ab50740ed68e54346d146304b5b6dc343d 2126 tumbler_0.2.1-1.dsc
 2783928a80875615d2decf0edad2c9ad8e99532e 784961 tumbler_0.2.1.orig.tar.gz
 8ac706eb7ddde3d6ba654e77d1d0cbe086953a36 5732 tumbler_0.2.1-1.debian.tar.xz
 ead9e2f3a5a3fd12d58fecbfedd56808604aee76 18369 tumbler_0.2.1-1_amd64.buildinfo
Checksums-Sha256:
 c89a5766fc99a54ec8f8b8630d2e6c4f961aa3da08172f56581ab07d45888bf2 2126 
tumbler_0.2.1-1.dsc
 78625b7a2c6a496b688caaf6b4c7a1522f2b09a5d6521b6e429342964d41ea65 784961 
tumbler_0.2.1.orig.tar.gz
 d367b462c5990dc1b85b43d11ecc5d67e4f9d6ecb56964f2e259296affe2a997 5732 
tumbler_0.2.1-1.debian.tar.xz
 12c28ba77a666ace3b2b07fea0f0aedb92f5dae8010c44099c8a54139fe2b76b 18369 
tumbler_0.2.1-1_amd64.buildinfo
Files:
 582c9a28bbe2df4a6e4742206f20a5ba 2126 xfce optional tumbler_0.2.1-1.dsc
 053272dd54bcf6db25550f1431703283 784961 xfce optional tumbler_0.2.1.orig.tar.gz
 1fde8d8bf50610fa673b0e0f2375898a 5732 xfce optional 
tumbler_0.2.1-1.debian.tar.xz
 6376303a8f70df62ff8064ff5963125c 18369 xfce optional 
tumbler_0.2.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlrIz2AACgkQ3rYcyPpX
RFtkCwgAofrPvVqxl8H8CaLWIQIIOs3uBrq3KTc3EUYYUQLtuyRqmt0wBhQ4RML7
VrzdXZHLBQ34y5KWNX8siZd83WLiN5AE0D9Ma/fVRe0FTgc/VmciUFd9kTbieWn4
z/M3B/MnoSZDOuGnWWR/1fAstbAWxIP4/8z/XyQ3QngazwqtthVErmqAvRvnYNn6

Bug#895133: marked as done (xandikos FTBFS with python3-dulwich 0.19.1-1)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:26:44 +
with message-id 
and subject line Bug#895133: fixed in xandikos 0.0.9-1
has caused the Debian Bug report #895133,
regarding xandikos FTBFS with python3-dulwich 0.19.1-1
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.)


-- 
895133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xandikos
Version: 0.0.7-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xandikos.html

...
==
ERROR: test_delete_one (xandikos.tests.test_store.TreeGitStoreTest)
--
Traceback (most recent call last):
  File "/build/1st/xandikos-0.0.7/xandikos/tests/test_store.py", line 145, in 
test_delete_one
self.assertEqual([], list(gc.iter_with_etag()))
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 217, in 
iter_with_etag
for (name, mode, sha) in self._iterblobs(ctag):
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 625, in 
_iterblobs
for (name, sha, mode) in index.iterblobs():
  File "/usr/lib/python3/dist-packages/dulwich/index.py", line 278, in iterblobs
warnings.warn(PendingDeprecationWarning, 'Use iterobjects() instead.')
TypeError: category must be a Warning subclass, not 'str'

==
ERROR: test_delete_one_invalid_etag (xandikos.tests.test_store.TreeGitStoreTest)
--
Traceback (most recent call last):
  File "/build/1st/xandikos-0.0.7/xandikos/tests/test_store.py", line 171, in 
test_delete_one_invalid_etag
self.assertEqual([], list(gc.iter_with_etag()))
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 217, in 
iter_with_etag
for (name, mode, sha) in self._iterblobs(ctag):
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 625, in 
_iterblobs
for (name, sha, mode) in index.iterblobs():
  File "/usr/lib/python3/dist-packages/dulwich/index.py", line 278, in iterblobs
warnings.warn(PendingDeprecationWarning, 'Use iterobjects() instead.')
TypeError: category must be a Warning subclass, not 'str'

==
ERROR: test_delete_one_with_etag (xandikos.tests.test_store.TreeGitStoreTest)
--
Traceback (most recent call last):
  File "/build/1st/xandikos-0.0.7/xandikos/tests/test_store.py", line 156, in 
test_delete_one_with_etag
self.assertEqual([], list(gc.iter_with_etag()))
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 217, in 
iter_with_etag
for (name, mode, sha) in self._iterblobs(ctag):
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 625, in 
_iterblobs
for (name, sha, mode) in index.iterblobs():
  File "/usr/lib/python3/dist-packages/dulwich/index.py", line 278, in iterblobs
warnings.warn(PendingDeprecationWarning, 'Use iterobjects() instead.')
TypeError: category must be a Warning subclass, not 'str'

==
ERROR: test_get_file (xandikos.tests.test_store.TreeGitStoreTest)
--
Traceback (most recent call last):
  File "/build/1st/xandikos-0.0.7/xandikos/tests/test_store.py", line 130, in 
test_get_file
[EXAMPLE_VCALENDAR1])
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 154, in 
import_one
self._check_duplicate(uid, name, replace_etag)
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 107, in 
_check_duplicate
self._scan_uids()
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 178, in 
_scan_uids
for (name, mode, sha) in self._iterblobs():
  File "/build/1st/xandikos-0.0.7/xandikos/store/git.py", line 625, in 
_iterblobs
for (name, sha, mode) in index.iterblobs():
  File "/usr/lib/python3/dist-packages/dulwich/index.py", line 278, in iterblobs
warnings.warn(PendingDeprecationWarning, 'Use iterobjects() instead.')
TypeError: category must be a Warning subclass, not 'str'

==
ERROR: test_get_raw (xandikos.tests.test_store.TreeGitStoreTest)
--
Traceback (most recent call last):
  File 

Bug#732628: marked as done (Please support squid-deb-proxy-client)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#732628: fixed in debootstrap 1.0.96
has caused the Debian Bug report #732628,
regarding Please support squid-deb-proxy-client
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.)


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

It would be nice if deboostrap would support the proxy auto discovery
from apt-get. Attached is a patch that adds it, please let me know if
that sounds reasonable and if the patch looks ok. Happy to adjust it
if you have any suggestions.

Cheers,
 Michael
>From 628f55068a60c72666dc45f3ff22f82346c60b35 Mon Sep 17 00:00:00 2001
From: Michael Vogt 
Date: Thu, 19 Dec 2013 15:36:58 +0100
Subject: [PATCH] try to auto-detect proxy if available

---
 debootstrap | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/debootstrap b/debootstrap
index dfa0abc..7bbb15e 100755
--- a/debootstrap
+++ b/debootstrap
@@ -48,6 +48,17 @@ PRIVATEKEY=""
 
 DEF_MIRROR="http://ftp.us.debian.org/debian;
 
+# do auto proxy discovery
+AUTOPROXY=""
+eval $(apt-config shell AUTOPROXY Acquire::http::ProxyAutoDetect)
+if [ -z "$http_proxy" ] && [ -x "$AUTOPROXY" ]; then
+http_proxy="$($AUTOPROXY)"
+if [ -n "$http_proxy" ]; then
+echo "Using auto-detected proxy: $http_proxy"
+export http_proxy
+fi
+fi
+
 export LANG USE_COMPONENTS
 umask 022
 
-- 
1.8.3.2

--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 debootstrap_1.0.96.dsc
 6abf18b0faa0a47a65e6b30aa9611df3d04127ed 69541 debootstrap_1.0.96.tar.gz
 c583d15df4f603d57079d0d3752051dcdf7ed1d4 19632 debootstrap-udeb_1.0.96_all.udeb
 7a01dd6e1d718cc7846832bfafaaeb08d7991e11 67130 debootstrap_1.0.96_all.deb
 9a8356d661e8bd165ab926c00695322483f0f022 5766 
debootstrap_1.0.96_amd64.buildinfo
Checksums-Sha256:
 

Bug#754318: marked as done (no warning if file specified via --keyring does not exist)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#775474: fixed in debootstrap 1.0.96
has caused the Debian Bug report #775474,
regarding no warning if file specified via --keyring does not exist
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.)


-- 
775474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: debootstrap

Dear Maintainer,

when running

  $ sudo debootstrap --keyring=/non/existing.gpg wheezy /tmp/wheezy

the output is something like:

  I: Retrieving Release
  I: Retrieving Release.gpg
  I: Checking Release signature
  E: Release signed by unknown key (key id 6FB2A1C265FFB764)

A warning that /non/existing.gpg was not even found would be good.

  $ gpgv --status-fd 1 --keyring "/non/existing.gpg"
- --ignore-time-conflict
  gpgv: keyblock resource `/non/existing.gpg': file open error

This is especially helpful because it was surprising to me that
- --keyring file-in-same-dir.gpg actually looks for
.gnupg/file-in-same-dir.gpg, which took me some time to figure out.

Best regards
Niklas Fiekas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJTva5dAAoJEC7KZsZbJVE4OEIP/3TQOaHRT6wEAWWtSWm7lxgS
thS/SXLWE280XoVjtQQDZ80rYarxLBsqjvNJH1WRnf9ETmPdhgp0X8I1f6+P0sjP
ykUhir5sCVxL8PBaWsZShi0sL7MXiUrc9JxGSxNVsTEuu7yzAZztR91OJsGOGanv
Bt3Z5M2KebRznjr16DF8cdkEYNu3uqpQKha3NWCvov5xZPdH21eGOX6URLL5wPV5
b2/w2jZlR25bwCLIHAr3u5fITcfXTzrHf4q+pjlVdYkyoOTJDD3klhUTS6+Vz0o2
YzxAw2qn7dF+cRigyBKkRABLpFvH2CtaLKX9nMSUZfpf+FqfLdBxLzkSEy9erRfF
Vt5D6ZwcWdwblPjJqLnEkvnL7/m37wKtWfv7icFdYbdeONAVOsgGXywid/v7Bjbg
85sOGagebU5Tx0wJoFI0/yjzi429x0MM6jMOKOniXmM3bFQlryWlfZBA+CO+ztRO
Pu3ZtBoDzL5/sD+xW7dwFCXFh5v3KLQTAS/3pF91M4sjnB8PRk/y3qKM9VEzFTYG
hJA83ZEsoc8G7P6U+rOt4xbSnTF1Vv+AmeEyveZaNsAwwIo+fHOA/Br86TuLrgFQ
qjx4yatduHM+Ti79/TzehQKmcDFKCZ3qaXXmRe6eJUU6iDlFzmP3yYw8E8QmR3Kb
qyfRe2LDZrLhSx+s8lYS
=rI/j
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available 

Bug#806780: marked as done (--foreign/--second-stage breaks with multiple components)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#806780: fixed in debootstrap 1.0.96
has caused the Debian Bug report #806780,
regarding --foreign/--second-stage breaks with multiple components
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.)


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

When passing multiple components to --second-stage things fail as debootstrap
tries to open debootstrap.invalid_dists_badger_snake|mushroom-armhf.Packages
rather then seperate Packages file for snake and mushroom.

Fixed in attached patch

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel

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

Versions of packages debootstrap depends on:
ii  wget  1.17-1

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.19-6

debootstrap suggests no packages.

-- no debconf information
>From 6621d8304cb79dcc6e07098caaf6eaa56fe8594a Mon Sep 17 00:00:00 2001
From: Sjoerd Simons 
Date: Tue, 1 Dec 2015 09:09:07 +0100
Subject: [PATCH] Fix multiple components usage for --foreign

commit e24e4b006736734e, bug #757819 made resolve_deps and
setup_available in the --foreign case. However this only worked when
using just one component as the USE_COMPONENTS variable is | delimited.

Translate the USE_COMPONENTS variable on the fly from | delimited to
space delimeted to allow multiple components to work again.

Signed-off-by: Sjoerd Simons 
---
 functions | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/functions b/functions
index 8bef5e6..64d76e4 100644
--- a/functions
+++ b/functions
@@ -1256,14 +1256,14 @@ resolve_deps () {
 	local ALLPKGS2="";
 	while [ "$PKGS" != "" ]; do
 		local NEWPKGS=""
-		for c in ${COMPONENTS:-$USE_COMPONENTS}; do
+		for c in ${COMPONENTS:-$(echo ${USE_COMPONENTS} | tr '|' ' ')}; do
 			local path="dists/$SUITE/$c/binary-$ARCH/Packages"
 			local pkgdest="$TARGET/$($DLDEST pkg "$SUITE" "$c" "$ARCH" "$m1" "$path")"
 			NEWPKGS="$NEWPKGS $("$PKGDETAILS" GETDEPS "$pkgdest" $PKGS)"
 		done
 		PKGS=$(echo "$PKGS $NEWPKGS" | tr ' ' '\n' | sort | uniq)
 		local REALPKGS=""
-		for c in ${COMPONENTS:-$USE_COMPONENTS}; do
+		for c in ${COMPONENTS:-$(echo ${USE_COMPONENTS} | tr '|' ' ')}; do
 			local path="dists/$SUITE/$c/binary-$ARCH/Packages"
 			local pkgdest="$TARGET/$($DLDEST pkg "$SUITE" "$c" "$ARCH" "$m1" "$path")"
 			REALPKGS="$REALPKGS $("$PKGDETAILS" PKGS REAL "$pkgdest" $PKGS | sed -n 's/ .*REAL.*$//p')"
@@ -1279,7 +1279,7 @@ resolve_deps () {
 setup_available () {
 	local m1="${MIRRORS%% *}"
 
-	for c in ${COMPONENTS:-$USE_COMPONENTS}; do
+	for c in ${COMPONENTS:-$(echo ${USE_COMPONENTS} | tr '|' ' ')}; do
 		local path="dists/$SUITE/$c/binary-$ARCH/Packages"
 		local pkgdest="$TARGET/$($DLDEST pkg "$SUITE" "$c" "$ARCH" "$m1" "$path")"
 		# XXX: What if a package is in more than one component?
-- 
2.6.2

--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 

Bug#754318: marked as done (no warning if file specified via --keyring does not exist)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#754318: fixed in debootstrap 1.0.96
has caused the Debian Bug report #754318,
regarding no warning if file specified via --keyring does not exist
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.)


-- 
754318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: debootstrap

Dear Maintainer,

when running

  $ sudo debootstrap --keyring=/non/existing.gpg wheezy /tmp/wheezy

the output is something like:

  I: Retrieving Release
  I: Retrieving Release.gpg
  I: Checking Release signature
  E: Release signed by unknown key (key id 6FB2A1C265FFB764)

A warning that /non/existing.gpg was not even found would be good.

  $ gpgv --status-fd 1 --keyring "/non/existing.gpg"
- --ignore-time-conflict
  gpgv: keyblock resource `/non/existing.gpg': file open error

This is especially helpful because it was surprising to me that
- --keyring file-in-same-dir.gpg actually looks for
.gnupg/file-in-same-dir.gpg, which took me some time to figure out.

Best regards
Niklas Fiekas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJTva5dAAoJEC7KZsZbJVE4OEIP/3TQOaHRT6wEAWWtSWm7lxgS
thS/SXLWE280XoVjtQQDZ80rYarxLBsqjvNJH1WRnf9ETmPdhgp0X8I1f6+P0sjP
ykUhir5sCVxL8PBaWsZShi0sL7MXiUrc9JxGSxNVsTEuu7yzAZztR91OJsGOGanv
Bt3Z5M2KebRznjr16DF8cdkEYNu3uqpQKha3NWCvov5xZPdH21eGOX6URLL5wPV5
b2/w2jZlR25bwCLIHAr3u5fITcfXTzrHf4q+pjlVdYkyoOTJDD3klhUTS6+Vz0o2
YzxAw2qn7dF+cRigyBKkRABLpFvH2CtaLKX9nMSUZfpf+FqfLdBxLzkSEy9erRfF
Vt5D6ZwcWdwblPjJqLnEkvnL7/m37wKtWfv7icFdYbdeONAVOsgGXywid/v7Bjbg
85sOGagebU5Tx0wJoFI0/yjzi429x0MM6jMOKOniXmM3bFQlryWlfZBA+CO+ztRO
Pu3ZtBoDzL5/sD+xW7dwFCXFh5v3KLQTAS/3pF91M4sjnB8PRk/y3qKM9VEzFTYG
hJA83ZEsoc8G7P6U+rOt4xbSnTF1Vv+AmeEyveZaNsAwwIo+fHOA/Br86TuLrgFQ
qjx4yatduHM+Ti79/TzehQKmcDFKCZ3qaXXmRe6eJUU6iDlFzmP3yYw8E8QmR3Kb
qyfRe2LDZrLhSx+s8lYS
=rI/j
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available 

Bug#775444: marked as done (Issue warning if falling back to sha1)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#775444: fixed in debootstrap 1.0.96
has caused the Debian Bug report #775444,
regarding Issue warning if falling back to sha1
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.)


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

Patch attached to output warning if falling back to sha1.
commit 0911f1a8ba757a013e4c97e017634eb0ab746997
Author: jnqnfe 
Date:   Thu Jan 15 19:22:17 2015 +

Issue warning if having to fall back to sha1

diff --git a/debootstrap b/debootstrap
index 3d45c9c..c383517 100755
--- a/debootstrap
+++ b/debootstrap
@@ -461,6 +461,7 @@ if [ -z "$SHA_SIZE" ]; then
SHA_SIZE=256
 fi
 if ! in_path "sha${SHA_SIZE}sum" && ! in_path "sha${SHA_SIZE}"; then
+   warning SHA_SIZE "Cannot find binary for checking sha%s checksums, 
falling back to sha1" "${SHA_SIZE}"
SHA_SIZE=1
 fi
 DEBOOTSTRAP_CHECKSUM_FIELD="SHA$SHA_SIZE"
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 debootstrap_1.0.96.dsc
 6abf18b0faa0a47a65e6b30aa9611df3d04127ed 69541 debootstrap_1.0.96.tar.gz
 c583d15df4f603d57079d0d3752051dcdf7ed1d4 19632 debootstrap-udeb_1.0.96_all.udeb
 7a01dd6e1d718cc7846832bfafaaeb08d7991e11 67130 debootstrap_1.0.96_all.deb
 9a8356d661e8bd165ab926c00695322483f0f022 5766 
debootstrap_1.0.96_amd64.buildinfo
Checksums-Sha256:
 d2949b1c59c6de220fdb8ca5992ddf7d4ef6680420604b7b0a5c8141f76cbf51 1991 
debootstrap_1.0.96.dsc
 5fe34b69069a8dcb425450f81d7e7c9eda9a6afd90082985d9e8f790868dae86 69541 
debootstrap_1.0.96.tar.gz
 c03783f84073f8bce653042b9a64179f616cc14352f975ab82e843c5d3c2bfce 19632 
debootstrap-udeb_1.0.96_all.udeb
 12ffc7d26021eefef8b9e667e78088c6a655439768e505e2c6d83999f3fed03c 67130 
debootstrap_1.0.96_all.deb
 

Bug#833525: marked as done (debootstrap: Deleted my entire /home partition using "mostly harmless" debootstrap --print-debs option)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#833525: fixed in debootstrap 1.0.96
has caused the Debian Bug report #833525,
regarding debootstrap: Deleted my entire /home partition using "mostly 
harmless" debootstrap --print-debs option
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.)


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

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
0) Okay, this will be embarrassing...
1) Occasional need to work on i386 software on an x86-64 machine.
2) Previous experiment led to a marginally usable "minimal"  /chroot/i386 
partition (without internet connection)
3) Desire to add internet connection to same, start by listing packages which 
would be installed by "debootstrap --print-debs"
4) Failure to understand that "debootstrap --print-debs" operated by performing 
the entire debootstrap operation, 
listing packages, then deleting the created directory, despite a note in the 
manfile to that effect.
5) Further failure to note that such deletion would apply recursively to any 
automounted partitions in said created directory. 
6) Previous experiment involved automounting /proc, /sys, /var/tp, and /home 
into said /chroot/i386 partition.
7) Re-using the /chroot/i386 directory name in the "debootstrap --print-files" 
command. Without the --keep-bootstrop-dir option, since I was about to replace 
it.
8) I said this was embarassing...

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Sadly, I no longer have my exact notes, as will become clear. But 
approximately, the command was (possibly with sudo, or after su):
debootstrap --print-debs /chroot/i386

   * What was the outcome of this action?
Well I briefly saw the list of packages flash past, before debootstrap got to 
the "The TARGET directory will be deleted" part.
At which point various strange things started happening, until it gradually 
dawned on me that /home and /var/tmp were slowly disappearing before my eyes...

   * What outcome did you expect instead?

Somehow I expected to be left with a list of .deb packages and a functioning 
computer. I now understand my expectations were unrealistic.

Perhaps I have been punished enough ... and perhaps it would be a good idea to 
modify the bit of debootstrap that implements 
"The TARGET directory will be deleted" and convince it to stop at 
automounted partitions in /etc/fstab (and/or mtab)?

It is too late for me, but it might be very pleasing to some future unwary 
operators to be left with their /home partition intact... 

(NB the packages/versions listed below apply to a reinstall, not the exact 
formerly-running system, for reasons that are hopefully clear)

*** End of the template - remove these template lines ***


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

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

Versions of packages debootstrap depends on:
ii  wget  1.18-1

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-6

debootstrap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 

Bug#798564: marked as done (debootstrap: Add scripts for kali releases)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#798564: fixed in debootstrap 1.0.96
has caused the Debian Bug report #798564,
regarding debootstrap: Add scripts for kali releases
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.)


-- 
798564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.72
Severity: wishlist
User: de...@kali.org
Usertags: origin-kali
Control: block -1 by 798562

Hello,

I'd like debootstrap to have native support of the various kali releases.
We don't need any special script compared to Debian except that we use a
different keyring and a different default archive.

In our forked package we do this currently:

override_dh_auto_build:
# Update kali script based on the debian one
(echo "default_mirror http://http.kali.org/kali;; sed -e 
"s/debian-archive-keyring.gpg/kali-archive-keyring.gpg/g" scripts/sid) 
>scripts/kali

So we need the above "base" script and then the following symlinks:
- moto
- sana
- kali-current
- kali-next
- kali-rolling
- kali-dev

That's all. You can either include the above hack or fix #798562 so that
we have a better way to share the bootstrapping code between Debian and
derivatives (my preference goes for the latter, hence the block but it's
definitely not mandatory).

Cheers,
 Raphaël.
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 debootstrap_1.0.96.dsc
 6abf18b0faa0a47a65e6b30aa9611df3d04127ed 69541 debootstrap_1.0.96.tar.gz
 c583d15df4f603d57079d0d3752051dcdf7ed1d4 19632 debootstrap-udeb_1.0.96_all.udeb
 7a01dd6e1d718cc7846832bfafaaeb08d7991e11 67130 debootstrap_1.0.96_all.deb
 9a8356d661e8bd165ab926c00695322483f0f022 5766 
debootstrap_1.0.96_amd64.buildinfo
Checksums-Sha256:
 d2949b1c59c6de220fdb8ca5992ddf7d4ef6680420604b7b0a5c8141f76cbf51 1991 
debootstrap_1.0.96.dsc
 

Bug#775474: marked as done (Issue helpful error if user specified keyring not found)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#754318: fixed in debootstrap 1.0.96
has caused the Debian Bug report #754318,
regarding Issue helpful error if user specified keyring not found
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.)


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

Patch attached to cause a helpful error to be issued to the user in the
event that they should specify a keyring file via the --keyring
parameter, but should the specified keyring file not be found (for
example should the user have made a typo). From a reading of the code I
believe that no such check already exists, and current behavior is to
just blunder on, resulting in a SIGCHECK gpgv state, and thus an
unhelpful "Error executing gpgv to check Release signature" message,
combined possibly with some degree of wasted time and bandwidth through
files being redownloaded after correcting the mistake (if the existing
copies aren't reused, I haven't yet read enough of the code carefully to
know at this point, nor have I run the code - been too busy to have time).
commit b066af054dad924641bd0cfa4dfd669a9db28bc5
Author: jnqnfe 
Date:   Fri Jan 16 05:24:50 2015 +

Issue error if user specified keyring file not found

diff --git a/debootstrap b/debootstrap
index e024560..e1a3fbf 100755
--- a/debootstrap
+++ b/debootstrap
@@ -321,6 +321,9 @@ if [ $# != 0 ] ; then
else
error 1 NEEDARG "option requires an argument %s" "$1"
fi
+   if [ ! -e "$KEYRING" ]; then
+   error 1 KEYRING "specified keyring file not found"
+   fi
;;
--no-check-gpg)
shift 1
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 

Bug#775474: marked as done (Issue helpful error if user specified keyring not found)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#775474: fixed in debootstrap 1.0.96
has caused the Debian Bug report #775474,
regarding Issue helpful error if user specified keyring not found
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.)


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

Patch attached to cause a helpful error to be issued to the user in the
event that they should specify a keyring file via the --keyring
parameter, but should the specified keyring file not be found (for
example should the user have made a typo). From a reading of the code I
believe that no such check already exists, and current behavior is to
just blunder on, resulting in a SIGCHECK gpgv state, and thus an
unhelpful "Error executing gpgv to check Release signature" message,
combined possibly with some degree of wasted time and bandwidth through
files being redownloaded after correcting the mistake (if the existing
copies aren't reused, I haven't yet read enough of the code carefully to
know at this point, nor have I run the code - been too busy to have time).
commit b066af054dad924641bd0cfa4dfd669a9db28bc5
Author: jnqnfe 
Date:   Fri Jan 16 05:24:50 2015 +

Issue error if user specified keyring file not found

diff --git a/debootstrap b/debootstrap
index e024560..e1a3fbf 100755
--- a/debootstrap
+++ b/debootstrap
@@ -321,6 +321,9 @@ if [ $# != 0 ] ; then
else
error 1 NEEDARG "option requires an argument %s" "$1"
fi
+   if [ ! -e "$KEYRING" ]; then
+   error 1 KEYRING "specified keyring file not found"
+   fi
;;
--no-check-gpg)
shift 1
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 

Bug#762431: marked as done (debootstrap: fails with spaces in pwd)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#762431: fixed in debootstrap 1.0.96
has caused the Debian Bug report #762431,
regarding debootstrap: fails with spaces in pwd
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.)


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

Dear Maintainer,

debootstrap fails if there are spaces in the $PWD directory. On my
machine the debootstrap versions 1.0.60 and 1.0.61 also fail. In
addition, the error also appears on a fresh jessie install.

Bug nr #586158 (debootstrap fails if the directory contains a space)
also fails with spaces in the directory, but observes other issues.

Shell output of failing call to debootstrap (the command finishes sucessfully
when executed in the directory "/home/mweigand/test_debootstrap").
-
root@pidwig:/home/mweigand/test debootstrap# debootstrap jessie
jessie_base
I: Retrieving Release 
I: Retrieving Release.gpg 
I: Checking Release signature
I: Valid Release signature (key id
A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553)
root@pidwig:/home/mweigand/test debootstrap# ls jessie_base/
debootstrap/ var/
root@pidwig:/home/mweigand/test debootstrap# cat
jessie_base/debootstrap/debootstrap.log 
gpgv: Signature made Mon Sep 22 04:48:17 2014 CEST using RSA key ID
46925553
gpgv: Good signature from "Debian Archive Automatic Signing Key
(7.0/wheezy) "
sed: can't read /home/mweigand/test: No such file or directory
-

As far as I investigated, the error is produced in the call to
'download_indices' (/usr/sbin/debootstrap, line 559), calling the
function defined in /usr/share/debootstrap/functions (line 423).

Best regards

Maximilian


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

Kernel: Linux 3.15.6-mx1 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debootstrap depends on:
ii  wget  1.13.4-3+deb7u1

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2012.4
ii  gnupg   1.4.12-7+deb7u6

debootstrap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

We believe that the bug you reported is fixed in the latest version of
debootstrap, 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.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with 

Bug#563647: marked as done (debootstrap: manpage neglects complete path for --unpack-tarball)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#563647: fixed in debootstrap 1.0.96
has caused the Debian Bug report #563647,
regarding debootstrap: manpage neglects complete path for --unpack-tarball
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.)


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

The manual page ought to mention that the option --unpack-tarball
needs a complete path to the archive created by --make-tarball.
All the more so since this contrasts to the lack of such prerequisite
for the creation with --make-tarball.

It would also do no harm to mention that the tarball created
with --make-tarball is constructed as a gzip'ed tar archive,
completely ignoring however the user decides to name the
intended file.

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable'), (90, 'testing'), (80, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=sv_SE, LC_CTYPE=sv_SE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages debootstrap depends on:
ii  binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii  wget1.11.4-2+lenny1  retrieves files from the web

Versions of packages debootstrap recommends:
ii  gnupg 1.4.9-3+lenny1 GNU privacy guard - a free PGP rep

debootstrap suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 debootstrap_1.0.96.dsc
 6abf18b0faa0a47a65e6b30aa9611df3d04127ed 69541 debootstrap_1.0.96.tar.gz
 c583d15df4f603d57079d0d3752051dcdf7ed1d4 19632 debootstrap-udeb_1.0.96_all.udeb
 7a01dd6e1d718cc7846832bfafaaeb08d7991e11 67130 debootstrap_1.0.96_all.deb
 

Bug#734324: marked as done (debootstrap: unavoidable keyring warning in second-stage)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#734324: fixed in debootstrap 1.0.96
has caused the Debian Bug report #734324,
regarding debootstrap: unavoidable keyring warning in second-stage
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.)


-- 
734324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: debootstrap
version: 1.0.56
severity: normal

The second stage always presents the keyring warning.  This, I think,
is unnecessary since all of the package verification is done during
the first stage.

One may think that this could be worked around by using "--keyring
/debian-archive-keyring.gpg" (after moving it there), but that makes
it worse since gpgv is not yet installed in the chroot.

Anyway, maybe it makes sense to disable all of the keyring stuff when
--second-stage is used.

Best wishes,
Mike
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 debootstrap_1.0.96.dsc
 6abf18b0faa0a47a65e6b30aa9611df3d04127ed 69541 debootstrap_1.0.96.tar.gz
 c583d15df4f603d57079d0d3752051dcdf7ed1d4 19632 debootstrap-udeb_1.0.96_all.udeb
 7a01dd6e1d718cc7846832bfafaaeb08d7991e11 67130 debootstrap_1.0.96_all.deb
 9a8356d661e8bd165ab926c00695322483f0f022 5766 
debootstrap_1.0.96_amd64.buildinfo
Checksums-Sha256:
 d2949b1c59c6de220fdb8ca5992ddf7d4ef6680420604b7b0a5c8141f76cbf51 1991 
debootstrap_1.0.96.dsc
 5fe34b69069a8dcb425450f81d7e7c9eda9a6afd90082985d9e8f790868dae86 69541 
debootstrap_1.0.96.tar.gz
 c03783f84073f8bce653042b9a64179f616cc14352f975ab82e843c5d3c2bfce 19632 
debootstrap-udeb_1.0.96_all.udeb
 12ffc7d26021eefef8b9e667e78088c6a655439768e505e2c6d83999f3fed03c 67130 
debootstrap_1.0.96_all.deb
 daad68829989b2c379478c97c1b60b6c48244f15cb8eead7a5d79a8ce14c8079 5766 
debootstrap_1.0.96_amd64.buildinfo
Files:
 7e77faea3139b192eca2ae83412818a1 1991 admin optional debootstrap_1.0.96.dsc
 

Bug#586158: marked as done (debootstrap fails if the directory contains a space)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 15:21:07 +
with message-id 
and subject line Bug#586158: fixed in debootstrap 1.0.96
has caused the Debian Bug report #586158,
regarding debootstrap fails if the directory contains a space
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.)


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

If the absolute path to the target directory contains a space,
debootstrap fails at the following step:
W: Failure trying to run: chroot /home/rdb/abc def/chroot mount -t proc
proc /proc

Steps to reproduce:
Create a directory with a name containing a space.
CD to it, and call "debootstrap dapper chroot" or something like that.

Forwarded from Ubuntu, initially reported at:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/539412

-- System Information:
Debian Release: squeeze/sid
  APT prefers lucid-updates
  APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 
'lucid-proposed'), (500, 'lucid-backports'), (500, 'lucid')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-23-generic (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debootstrap depends on:
ii  binutils 2.20.1-3ubuntu5 The GNU assembler, linker and bina
ii  wget 1.12-1.1ubuntu2 retrieves files from the web

Versions of packages debootstrap recommends:
ii  gnupg1.4.10-2ubuntu1 GNU privacy guard - a free PGP rep

debootstrap suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.96

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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, 06 Apr 2018 10:02:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 563647 586158 732628 734324 754318 762431 775444 775474 798564 806780 
833525
Changes:
 debootstrap (1.0.96) unstable; urgency=medium
 .
   * Escape spaces to fix debootstrap on path contains space fails
 Thanks to Tianon Gravi  for the based patch
 (Closes: #586158, #762431)
   * Add warning if file specified via --keyring does not exist
 Thanks to jnqnfe  for the patch
 (Closes: #754318, #775474)
   * Avoid unnecessary keyring warning with --second-stage option
 (Closes: #734324)
   * Output warning if falling back to sha1 (Closes: #775444)
 Thanks to jnqnfe  for the patch.
   * Prevent unintended removal with --print-debs option (Closes: #833525)
 Thanks to Johannes Schauer  for the patch
   * Add scripts for Kali Linux (Closes: #798564)
   * Improve manpage description for --{unpack,make}-tarball options
 (Closes: #563647)
 .
   * debian/control
 - Add "Suggests: squid-deb-proxy-client"
   * debian/rules
 - Add Kali for ${keyring} pattern
 .
   [ Sjoerd Simons ]
   * Fix multiple components usage for --foreign/--second-stage
 (Closes: #806780)
 .
   [ Michael Vogt ]
   * Try to auto-detect proxy if available (e.g. squid-deb-proxy-client)
 (Closes: #732628)
Checksums-Sha1:
 e283396a67afae3737229a54c142b2f26f6793b6 1991 debootstrap_1.0.96.dsc
 6abf18b0faa0a47a65e6b30aa9611df3d04127ed 69541 debootstrap_1.0.96.tar.gz
 c583d15df4f603d57079d0d3752051dcdf7ed1d4 19632 debootstrap-udeb_1.0.96_all.udeb
 

Bug#895108: marked as done (python-evdev: avoid unnecessary Build-Depends: python3-sphinx)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 13:51:21 +
with message-id 
and subject line Bug#895108: fixed in python-evdev 0.8.1+dfsg-1
has caused the Debian Bug report #895108,
regarding python-evdev: avoid unnecessary Build-Depends: 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.)


-- 
895108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-evdev
Version: 0.7.0+dfsg-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

python-evdev fails to cross build from source, because its build
dependency on python3-sphinx is unsatisfiable. We don't currently have a
good solution for sphinx, but python-evdev nicely splits the
documentation out into python-evdev-doc. Thus there is no need to build
the documentation during arch-only builds and we can demote the sphinx
dependencies to Build-Depends-Indep. The attached patch implements that.
I used reproducible builds to verify that this does not change the
contents of the arch-dependent packages. Please consider applying it.

Helmut
diff --minimal -Nru python-evdev-0.7.0+dfsg/debian/changelog 
python-evdev-0.7.0+dfsg/debian/changelog
--- python-evdev-0.7.0+dfsg/debian/changelog2017-10-07 11:49:45.0 
+0200
+++ python-evdev-0.7.0+dfsg/debian/changelog2018-04-07 08:40:25.0 
+0200
@@ -1,3 +1,10 @@
+python-evdev (0.7.0+dfsg-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't run sphinx during arch-only builds. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 07 Apr 2018 08:40:25 +0200
+
 python-evdev (0.7.0+dfsg-2) unstable; urgency=medium
 
   * Limit the architecture to linux-any. Closes: #875624.
diff --minimal -Nru python-evdev-0.7.0+dfsg/debian/control 
python-evdev-0.7.0+dfsg/debian/control
--- python-evdev-0.7.0+dfsg/debian/control  2017-10-07 11:48:59.0 
+0200
+++ python-evdev-0.7.0+dfsg/debian/control  2018-04-07 08:40:25.0 
+0200
@@ -7,11 +7,12 @@
python-setuptools,
python3-setuptools,
python3-docutils,
-   python3-sphinx,
-   python3-sphinx-rtd-theme,
python-all-dev,
python3-all-dev
-Build-Conflicts: python-sphinx
+Build-Depends-Indep:
+   python3-sphinx,
+   python3-sphinx-rtd-theme
+Build-Conflicts-Indep: python-sphinx
 Standards-Version: 4.1.1
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/python-evdev.git
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/python-evdev.git
diff --minimal -Nru python-evdev-0.7.0+dfsg/debian/rules 
python-evdev-0.7.0+dfsg/debian/rules
--- python-evdev-0.7.0+dfsg/debian/rules2017-09-01 21:04:03.0 
+0200
+++ python-evdev-0.7.0+dfsg/debian/rules2018-04-07 08:40:22.0 
+0200
@@ -2,11 +2,12 @@
 
 export PYBUILD_NAME=evdev
 
+DH_ADDONS = --with=python2 --with=python3
 %:
-   dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
+   dh $@ $(DH_ADDONS) --buildsystem=pybuild
+build build-indep binary binary-indep: DH_ADDONS+=--with=sphinxdoc
 
-override_dh_auto_build:
-   dh_auto_build
+override_dh_auto_build-indep:
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ 
build/html
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bman docs/ 
build/man
 
--- End Message ---
--- Begin Message ---
Source: python-evdev
Source-Version: 0.8.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
python-evdev, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated python-evdev 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: Sat, 07 Apr 2018 15:27:19 +0200
Source: python-evdev
Binary: python-evdev python3-evdev python-evdev-doc
Architecture: source
Version: 0.8.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 

Bug#894879: marked as done (more apparmor for chrony)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 15:38:44 +0200
with message-id <20180407133843.GB2756@lamella>
and subject line Re: Bug#894879: more apparmor for chrony
has caused the Debian Bug report #894879,
regarding more apparmor for chrony
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.)


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

Hi,
in [1] for Ubuntu we found that for hw timestamping the apparmor rule needs
to be extended.
You'll find more details in [1] but the TL;DR for you to consider picking
as well is [2] of [3].

[1]: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1761327
[2]:
https://git.launchpad.net/~paelzer/ubuntu/+source/chrony/commit/?id=877d858c3c21ec88099d47c40423491b7f69bd80
[3]:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/342710

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---

Version: 3.3-1

On Thu, Apr 05, 2018 at 11:07:38AM +0200, Vincent Blut wrote:

Control: tags -1 pending

Hi Christian,

On Thu, Apr 05, 2018 at 09:47:01AM +0200, Christian Ehrhardt wrote:

Package: chrony
Version: 3.2-5
Severity: normal

Hi,
in [1] for Ubuntu we found that for hw timestamping the apparmor rule needs
to be extended.
You'll find more details in [1] but the TL;DR for you to consider picking
as well is [2] of [3].


I committed the necessary change last night¹.

¹ 
https://salsa.debian.org/debian/chrony/commit/90f84785f15636dbb0695e64646753b89e08474c


Uploaded!

Cheers,
Vincent


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

Bug#802299: marked as done (thunar crashes and logouts session when visiting a folder containing video files)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 14:18:14 +0200
with message-id <06333dcb74813ca664aa92c77b83ec972efd8406.ca...@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#802299: thunar crashes and logouts 
session when visiting a folder containing video files
has caused the Debian Bug report #802299,
regarding thunar crashes and logouts session when visiting a folder containing 
video 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.)


-- 
802299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.6.3-2
Severity: important

Dear Maintainer,

Browsing the filesystem with Thunar, I suddently see my session crash and I'm 
sent to the
login screen again. After a few tests and comparing with the filesystem browsed 
in a terminal,
I deduced that this problem occurs only when Thunar visits a folder containing 
video files.

I tried nothing to fix the problem, sinceI had no idea of a relevant action to 
try, except sending
a bug report.

Adrien Licari

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

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.22-1
ii  exo-utils   0.10.2-4
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-18+deb8u1
ii  libcairo2   1.14.0-2.1
ii  libdbus-1-3 1.8.20-0+deb8u1
ii  libdbus-glib-1-20.102-1
ii  libexo-1-0  0.10.2-4
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u2
ii  libglib2.0-02.42.1-1
ii  libgtk2.0-0 2.24.25-3
ii  libgudev-1.0-0  215-17+deb8u2
ii  libice6 2:1.0.9-1+b1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-3
ii  libsm6  2:1.2.2-1+b1
ii  libthunarx-2-0  1.6.3-2
ii  libxfce4ui-1-0  4.10.0-6
ii  libxfce4util6   4.10.1-2
ii  libxfconf-0-2   4.10.0-3
ii  shared-mime-info1.3-1
ii  thunar-data 1.6.3-2

Versions of packages thunar recommends:
ii  dbus-x11 1.8.20-0+deb8u1
ii  gvfs 1.22.2-1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-3+deb8u1
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  thunar-volman0.8.0-4
ii  tumbler  0.1.30-1+b1
ii  xdg-user-dirs0.15-2
ii  xfce4-panel  4.10.1-1

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.1-3
ii  thunar-media-tags-plugin  0.2.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 2018-04-07 at 11:33 +0200, Adrien Licari-Guillaume wrote:
> Sorry, I won't be able to help you anymore, I changed both my hardware and
> my OS for Sparkylinux (still debian-based). I don't have this problem
> anymore.
> All I can tell you now is that I remember I "fixed" the problem by disabling
> thumbnails, as you suggest in your mail.

Thanks for the update. I'm closing the bug then, feel free to reopen if you
manage to reproduce.

Regards,
-- 
Yves-Alexis

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

Bug#833801: marked as done (thunar: intensive scrollig with mouse wheel ejects me to the login screen)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 14:17:28 +0200
with message-id <23ce5fb38359d7b5c9b6cc8b3906ed8cd100e7b5.ca...@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#833801: thunar: intensive scrollig 
with mouse wheel ejects me to the login screen
has caused the Debian Bug report #833801,
regarding thunar: intensive scrollig with mouse wheel ejects me to the login 
screen
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.)


-- 
833801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 1.6.3-2
Severity: important

I have a shortcut on panel #2 to launch Thunar. I use it to open my music
folder. When I start to scroll down the list with the mouse whell after
(usually) 3 movements I am sudenly presented with the login screen to enter my
login name and password. This behavior is 100% reproducible on my laptop - each
time I try it I get it.



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

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.22-1
ii  exo-utils   0.10.2-4
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-18+deb8u4
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libdbus-1-3 1.8.20-0+deb8u1
ii  libdbus-glib-1-20.102-1
ii  libexo-1-0  0.10.2-4
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u5
ii  libglib2.0-02.42.1-1+b1
ii  libgtk2.0-0 2.24.25-3+deb8u1
ii  libgudev-1.0-0  215-17+deb8u4
ii  libice6 2:1.0.9-1+b1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-3
ii  libsm6  2:1.2.2-1+b1
ii  libthunarx-2-0  1.6.3-2
ii  libxfce4ui-1-0  4.10.0-6
ii  libxfce4util6   4.10.1-2
ii  libxfconf-0-2   4.10.0-3
ii  shared-mime-info1.3-1
ii  thunar-data 1.6.3-2

Versions of packages thunar recommends:
ii  dbus-x11 1.8.20-0+deb8u1
ii  gvfs 1.22.2-1
ii  libfontconfig1   2.11.0-6.3+deb8u1
ii  libfreetype6 2.5.2-3+deb8u1
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  thunar-volman0.8.0-4
ii  tumbler  0.1.30-1+b1
ii  xdg-user-dirs0.15-2
ii  xfce4-panel  4.10.1-1

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.3.1-3
ii  thunar-media-tags-plugin  0.2.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 2018-04-07 at 07:47 +0200, Marian Kondrcik wrote:
> I am not able to reproduce this behavior anymore using thunar.
> (at the time to by-pass the problem I installed pcmanfm which worked fine)

Thanks, I'm closing it then.

Regards,
-- 
Yves-Alexis

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

Bug#895126: marked as done (plasma-discover-common_5.12.4-1 fails to install: 'lzma-Fehler: komprimierte Daten sind beschädigt')

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 15:14:40 +0300
with message-id <20180407121440.GY9516@localhost>
and subject line Re: Bug#895126: plasma-discover-common_5.12.4-1 fails to 
install: 'lzma-Fehler: komprimierte Daten sind beschädigt'
has caused the Debian Bug report #895126,
regarding plasma-discover-common_5.12.4-1 fails to install: 'lzma-Fehler: 
komprimierte Daten sind beschädigt'
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.)


-- 
895126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-discover-common
Version: 5.12.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On Sat, Apr 07, 2018 at 12:04:02PM +, Marcel Treis wrote:
> It worked like a charm. Thanks alot for your help!

Thanks for the quick reply, I'm closing this bug since there is nothing 
wrong with the package.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#870754: marked as done (ruby-berkshelf-api-client FTBFS with uby-buff-extensions 2.0.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 14:58:45 +0300
with message-id <20180407115845.GX9516@localhost>
and subject line This bug appears to be fixed now
has caused the Debian Bug report #870754,
regarding ruby-berkshelf-api-client FTBFS with uby-buff-extensions 2.0.0-1
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.)


-- 
870754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-berkshelf-api-client
Version: 2.0.2-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-berkshelf-api-client.html

...
GEM_PATH=debian/ruby-berkshelf-api-client/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -e gem\ \"berkshelf-api-client\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'buff-extensions' (~> 1.0) - did find: [buff-extensions-2.0.0] (Gem::LoadError)
Checked in 
'GEM_PATH=debian/ruby-berkshelf-api-client/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information
...
--- End Message ---
--- Begin Message ---
This bug appears to be fixed now:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-berkshelf-api-client.html

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#893901: marked as done (modem-manager-gui: FTBFS on various architectures - missing -lm)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 11:19:57 +
with message-id 
and subject line Bug#893901: fixed in modem-manager-gui 0.0.19.1-1
has caused the Debian Bug report #893901,
regarding modem-manager-gui: FTBFS on various architectures - missing -lm
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.)


-- 
893901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: modem-manager-gui
Version: 0.0.18-4
Severity: serious
Tags: sid buster

Hi,

modem-manager-gui FTBFS on various architectures with the error:
> gcc `pkg-config --cflags gtk+-3.0 gthread-2.0 gmodule-2.0 gtkspell3-3.0 
> appindicator3-0.1` -Wl,-z,relro -Wl,-z,now -Wl,--as-needed settings.o 
> strformat.o libpaths.o dbus-utils.o notifications.o addressbooks.o ayatana.o 
> smsdb.o trafficdb.o providersdb.o modem-settings.o ussdlist.o encoding.o 
> vcard.o netlink.o polkit.o svcmanager.o mmguicore.o contacts-page.o 
> traffic-page.o scan-page.o info-page.o ussd-page.o sms-page.o devices-page.o 
> preferences-window.o welcome-window.o connection-editor-window.o main.o 
> `pkg-config --libs gtk+-3.0 gthread-2.0 gmodule-2.0 gtkspell3-3.0 
> appindicator3-0.1` -lgdbm -o modem-manager-gui
> /usr/bin/ld: encoding.o: undefined reference to symbol 'ceil@@GLIBC_2.0'
> //lib/mips64el-linux-gnuabi64/libm.so.6: error adding symbols: DSO missing 
> from command line
> collect2: error: ld returned 1 exit status
> make[2]: *** [Makefile:17: modem-manager-gui] Error 1
> make[2]: Leaving directory '/<>/src'
> make[1]: *** [Makefile:8: modem-manager-gui] Error 2
> dh_auto_build: make -j4 -O returned exit code 2
> make: *** [debian/rules:6: build-arch] Error 25
> dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
> status 2

I'm guessing this only happens on some architectures because ceil was
inlined by the compiler as an intrinsic on those architectures.

In any case, modem-manager-gui should be linked against libm with -lm.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: modem-manager-gui
Source-Version: 0.0.19.1-1

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated modem-manager-gui 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: Sat, 07 Apr 2018 10:12:18 +
Source: modem-manager-gui
Binary: modem-manager-gui modem-manager-gui-help
Architecture: source
Version: 0.0.19.1-1
Distribution: unstable
Urgency: medium
Maintainer: Graham Inggs 
Changed-By: Graham Inggs 
Description:
 modem-manager-gui - GUI front-end for ModemManager / Wader / oFono
 modem-manager-gui-help - GUI front-end for ModemManager / Wader / oFono - 
documentation
Closes: 893901
Changes:
 modem-manager-gui (0.0.19.1-1) unstable; urgency=medium
 .
   * New upstream release
 - Fix linker errors (Closes: #893901)
 - Expand SMS folders on first messages
 - Fix spelling errors reported by Lintian
 - Fix polkit preventing module loading without systemd
 - Use generic term 'connection manager' instead of
   'network manager' in warning
 - Fix typo in Russian translation
 - Add Slovak localization
Checksums-Sha1:
 adc3d8ee730942e09d55ad845c6062e59eb1b2bf 2158 modem-manager-gui_0.0.19.1-1.dsc
 fe101d6fd8ac38c5e983887c56bb0eac8db7f6b2 1055105 
modem-manager-gui_0.0.19.1.orig.tar.gz
 45b3d7efcc338f07f2d6cc19ff27ccfffddbb489 12272 
modem-manager-gui_0.0.19.1-1.debian.tar.xz
Checksums-Sha256:
 fcff4ed1bdac68dab0666d5fd1852384be18013e63c2895bbbaae3549b49787f 2158 
modem-manager-gui_0.0.19.1-1.dsc
 0b9bae29f3cd3d99b3a61d5530097d576a5fa67d3215d54f3570cb20c6ca0bc2 1055105 
modem-manager-gui_0.0.19.1.orig.tar.gz
 73fe49b1a918f8bd8196a9c93b3b80e9e8957f537c92b398f1b0bb2eb9f4fd08 12272 
modem-manager-gui_0.0.19.1-1.debian.tar.xz
Files:
 

Bug#891345: marked as done (libosmocore-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libosmocoding.so -> libosmocoding.so.0.0.0)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 10:51:24 +
with message-id 
and subject line Bug#891345: fixed in libosmocore 0.10.2-4
has caused the Debian Bug report #891345,
regarding libosmocore-dev: broken symlink: 
/usr/lib/x86_64-linux-gnu/libosmocoding.so -> libosmocoding.so.0.0.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.)


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

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m24.7s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libosmocoding.so -> libosmocoding.so.0.0.0


libosmocoding.so.0.0.0 does not need to exist in any package in the archive.


cheers,

Andreas


libosmocore-dev_0.10.2-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libosmocore
Source-Version: 0.10.2-4

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated libosmocore 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: Sat, 07 Apr 2018 11:07:14 +0100
Source: libosmocore
Binary: libosmocore libosmocodec0 libosmocodec-doc libosmocore9 libosmocore-doc 
libosmogb5 libosmogsm8 libosmogsm-doc libosmovty4 libosmovty-doc libosmoctrl0 
libosmosim0 libosmocore-dev libosmocore-utils
Architecture: source all amd64
Version: 0.10.2-4
Distribution: sid
Urgency: medium
Maintainer: Debian Mobcom Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 libosmocodec-doc - Documentation for the osmo codec library
 libosmocodec0 - Osmo codec library
 libosmocore - Open Source MObile COMmunications CORE library (metapackage)
 libosmocore-dev - Development headers for Open Source MObile COMmunications 
CORE li
 libosmocore-doc - Documentation for the Osmo Core library
 libosmocore-utils - Utilities for gsm
 libosmocore9 - Osmo Core library
 libosmoctrl0 - Osmo control library
 libosmogb5 - Osmo GPRS GB library
 libosmogsm-doc - Documentation for the Osmo GSM utility library
 libosmogsm8 - Osmo GSM utility library
 libosmosim0 - Osmo SIM library
 libosmovty-doc - Documentation for the Osmo VTY library
 libosmovty4 - Osmo VTY library
Closes: 891345
Changes:
 libosmocore (0.10.2-4) unstable; urgency=medium
 .
   * debian/rules: deactivate testsuite for big endian architecture
   s390x and mips from supported archs
   lib has problem with one endian related test (gsm0808)
   * add libosmocoding to libosmocore9 (Closes: #891345)
   * add big-endian-problem.patch
Checksums-Sha1:
 dd5f404ccfdb836757eea4a1fbce60caba1452de 3010 libosmocore_0.10.2-4.dsc
 d838ff0e6566289918b25a7abc90c1a1c370e0a8 543196 libosmocore_0.10.2.orig.tar.xz
 97c3db3de145f1250fcaf70bb12505390eda588a 17464 
libosmocore_0.10.2-4.debian.tar.xz
 4348c280a3a1d8d7915e86fed2119e2af1f2f1a4 102160 
libosmocodec-doc_0.10.2-4_all.deb
 dd4c1de97ae9a48712dbcfc7c64a7adab8671c4c 6624 
libosmocodec0-dbgsym_0.10.2-4_amd64.deb
 eca7dd8b1382b5856cf3098350054dd3f41363be 9824 libosmocodec0_0.10.2-4_amd64.deb
 772d39c1138522fee5377eed44363deca8ef9a05 106576 
libosmocore-dev_0.10.2-4_amd64.deb
 bb3f17f5a7329a87ef2d9cfc8efa4946dc045c38 429896 
libosmocore-doc_0.10.2-4_all.deb
 f70876649fbcff88054c141f56845ce938c86153 13148 
libosmocore-utils-dbgsym_0.10.2-4_amd64.deb
 8feef25cd0e93be39bfc1797f803cb710ad5 11356 
libosmocore-utils_0.10.2-4_amd64.deb
 fa7cacaa93241f60c940a879dac729a42c6d07ac 207076 
libosmocore9-dbgsym_0.10.2-4_amd64.deb
 601a5b0b85fc7fcbbb1b388611f23ec48079 80080 libosmocore9_0.10.2-4_amd64.deb
 9000690484c6b14c0da130141b4b3356cea14ece 12014 
libosmocore_0.10.2-4_amd64.buildinfo
 

Bug#614818: marked as done (openssh-client: ssh(1) man page should note id_rsa encryption now uses AES, not 3DES)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 11:12:41 +0100
with message-id <20180407101241.3hdso6hgpdxfg...@riva.ucam.org>
and subject line Re: Bug#614818: openssh-client: ssh(1) man page should note 
id_rsa encryption now uses AES, not 3DES
has caused the Debian Bug report #614818,
regarding openssh-client: ssh(1) man page should note id_rsa encryption now 
uses AES, not 3DES
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.)


-- 
614818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-client
Version: 1:5.8p1-2
Severity: normal

In the FILES section of ssh(1), it says:

 ~/.ssh/id_rsa
 Contains the private key for authentication.  These files contain
 sensitive data and should be readable by the user but not acces‐
 sible by others (read/write/execute).  ssh will simply ignore a
 private key file if it is accessible by others.  It is possible
 to specify a passphrase when generating the key which will be
 used to encrypt the sensitive part of this file using 3DES.

However, in a recent release, ssh-keygen has switched to using AES, not
3DES, to encrpyt the private key. This is noted in the ssh-keygen(1) page,
in this same pkg:

 ~/.ssh/id_rsa
 Contains the protocol version 2 DSA, ECDSA or RSA authentication
 identity of the user.  This file should not be readable by anyone
 but the user.  It is possible to specify a passphrase when gener‐
 ating the key; that passphrase will be used to encrypt the pri‐
 vate part of this file using 128-bit AES.  [...]


This section should probably be the same across both man pages.

thanks much
calum.



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

Kernel: Linux 2.6.35.7 (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openssh-client depends on:
ii  adduser  3.112+nmu2  add and remove users and groups
ii  debconf [debconf-2.0 1.5.38  Debian configuration management sy
ii  dpkg 1.15.8.10   Debian package management system
ii  libc62.11.2-11   Embedded GNU C Library: Shared lib
ii  libedit2 2.11-20080614-2 BSD editline and history libraries
ii  libgssapi-krb5-2 1.8.1+dfsg-5MIT Kerberos runtime libraries - k
ii  libselinux1  2.0.96-1SELinux runtime shared libraries
ii  libssl0.9.8  0.9.8o-4SSL shared libraries
ii  passwd   1:4.1.4.2+svn3283-2 change and administer password and
ii  zlib1g   1:1.2.3.4.dfsg-3compression library - runtime

Versions of packages openssh-client recommends:
ii  openssh-blacklist 0.4.1  list of default blacklisted OpenSS
ii  openssh-blacklist-extra   0.4.1  list of non-default blacklisted Op
ii  xauth 1:1.0.5-1  X authentication utility

Versions of packages openssh-client suggests:
ii  gtk-led-askpass [ssh-askpass 0.11-1  GTK+ password dialog suitable for 
ii  keychain 2.6.8-2 key manager for OpenSSH
pn  libpam-ssh (no description available)
ii  ssh-askpass  1:1.2.4.1-9 under X, asks user for a passphras

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:7.7p1-1

On Wed, Oct 04, 2017 at 01:02:30PM +0100, Colin Watson wrote:
> Thanks.  I've belatedly confirmed that this is still the case in 7.6p1,
> and forwarded your bug upstream as
> https://bugzilla.mindrot.org/show_bug.cgi?id=2788.

Fixed in OpenSSH 7.7p1.

-- 
Colin Watson   [cjwat...@debian.org]--- End Message ---

Bug#895094: marked as done (python-paho-mqtt: Please replace 'c_rehash' with 'openssl rehash')

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 12:03:11 +0200
with message-id <20180407100311.xy2n6tw5sw5lsbvh@earth.universe>
and subject line Re: Bug#895094: python-paho-mqtt: Please replace 'c_rehash' 
with 'openssl rehash'
has caused the Debian Bug report #895094,
regarding python-paho-mqtt: Please replace 'c_rehash' with 'openssl rehash'
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.)


-- 
895094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-paho-mqtt
Version: 1.3.1-1
Severity: normal
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: c_rehash

This package is using the c_rehash command which is part of the
openssl package. The c_rehash script is considered by upstream as a
fallback script and will disappear at some point. The recommended way
is to use the "openssl rehash" command instead which appeared in
1.1.0. Please make sure that this package does not use the c_rehash
command anymore.

The "openssl rehash" command creates half that many symlinks (one per
certificate instead of two) because it uses only the newer hash.
There is also the -compat option which creates both symlinks (and
behaves like c_rehash currently does). The hash changed from md5 to
sha1 during the 0.9.8 to 1.0.0 transition so I doubt that the
"compat" mode will be required.

Should the c_rehash script be mentioned in the source code or script
of this package but is not used during the build process or in the
final package then feel free to close the bug saying so.

Sebastian 
--- End Message ---
--- Begin Message ---
Hi,

On Sat, Apr 07, 2018 at 12:48:24AM +0200, Sebastian Andrzej Siewior wrote:
> Source: python-paho-mqtt
> Version: 1.3.1-1
> Severity: normal
> Tags: sid buster
> User: pkg-openssl-de...@lists.alioth.debian.org
> Usertags: c_rehash
> 
> This package is using the c_rehash command which is part of the
> openssl package. The c_rehash script is considered by upstream as a
> fallback script and will disappear at some point. The recommended way
> is to use the "openssl rehash" command instead which appeared in
> 1.1.0. Please make sure that this package does not use the c_rehash
> command anymore.
> 
> The "openssl rehash" command creates half that many symlinks (one per
> certificate instead of two) because it uses only the newer hash.
> There is also the -compat option which creates both symlinks (and
> behaves like c_rehash currently does). The hash changed from md5 to
> sha1 during the 0.9.8 to 1.0.0 transition so I doubt that the
> "compat" mode will be required.
> 
> Should the c_rehash script be mentioned in the source code or script
> of this package but is not used during the build process or in the
> final package then feel free to close the bug saying so.
> 
> Sebastian 

This is only mentioned in some test script, that is not being used
during package build (and not part of the final package).

-- Sebastian


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

Bug#742177: marked as done (samba_backup missed in samba packages)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 11:28:26 +0200
with message-id 

and subject line Closing
has caused the Debian Bug report #742177,
regarding samba_backup missed in samba 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.)


-- 
742177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.1.6+dfsg-1~bpo70+1
Severity: normal

samba_backup file useful to do samba data backup and described in the official 
wiki page linked below is missed in samba packages.
https://wiki.samba.org/index.php/Backup_and_Recovery 

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

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

Versions of packages samba depends on:
ii  adduser 3.113+nmu3
ii  dpkg1.16.12
ii  libasn1-8-heimdal   1.6~git20120403+dfsg1-2
ii  libbsd0 0.4.2-1
ii  libc6   2.13-38+deb7u1
ii  libcomerr2  1.42.5-1.1
ii  libhdb9-heimdal 1.6~git20120403+dfsg1-2
ii  libkdc2-heimdal 1.6~git20120403+dfsg1-2
ii  libkrb5-26-heimdal  1.6~git20120403+dfsg1-2
ii  libldb1 1:1.1.16-1~bpo70+1
ii  libpam-modules  1.1.3-7.1
ii  libpam-runtime  1.1.3-7.1
ii  libpopt01.16-7
ii  libpython2.72.7.3-6+deb7u2
ii  libroken18-heimdal  1.6~git20120403+dfsg1-2
ii  libtalloc2  2.1.0-1~bpo70+1
ii  libtdb1 1.2.12-1~bpo70+1
ii  libtevent0  0.9.19-1~bpo70+1
ii  lsb-base4.1+Debian8+deb7u1
ii  multiarch-support   2.13-38+deb7u1
ii  procps  1:3.3.3-3
ii  python  2.7.3-4+deb7u1
ii  python-dnspython1.10.0-1
ii  python-ntdb 1.0-2~bpo70+1
ii  python-samba2:4.1.6+dfsg-1~bpo70+1
ii  python2.7   2.7.3-6+deb7u2
ii  samba-common2:4.1.6+dfsg-1~bpo70+1
ii  samba-common-bin2:4.1.6+dfsg-1~bpo70+1
ii  samba-dsdb-modules  2:4.1.6+dfsg-1~bpo70+1
ii  samba-libs  2:4.1.6+dfsg-1~bpo70+1
ii  tdb-tools   1.2.12-1~bpo70+1
ii  update-inetd4.43

Versions of packages samba recommends:
ii  attr   1:2.4.46-8
ii  logrotate  3.8.1-4
ii  samba-vfs-modules  2:4.1.6+dfsg-1~bpo70+1

Versions of packages samba suggests:
pn  bind9  
pn  bind9utils 
pn  ctdb   
ii  ldb-tools  1:1.1.6-1
ii  ntp1:4.2.6.p5+dfsg-2
pn  smbldap-tools  
pn  winbind

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

I'm closing this bug, as samba_backup will be removed in the future.
We'll wait for samba-tool to add "domain backup" and "domain restore"
for this request to be fixed.

Ref: https://github.com/samba-team/samba/pull/160#issuecomment-379455902

Regards

-- 
Mathieu Parent--- End Message ---

Bug#801327: marked as done (ctdb: Man page for ctdb_diagnostics)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 11:20:51 +0200
with message-id 

and subject line Done
has caused the Debian Bug report #801327,
regarding ctdb: Man page for ctdb_diagnostics
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.)


-- 
801327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ctdb
Version: 2.5.4+debian0-4
Severity: wishlist

Dear Maintainer,

I created a manpage for ctdb_diagnostics.
What do you think about it?

Kind regards,
Martijn van Brummelen

.TH ctdb_diagnostics "1" "October 2015" "ctdb_diagnostics" "User Commands"
.SH NAME
\ ctdb_diagnostics - test CTDB/Samba installation
.SH SYNOPSIS
.B ctdb_diagnostics
[\fI\,OPTION\/\fR] ...
.SH DESCRIPTION
A script to test the basic setup of a CTDB/Samba install
.TP
\fB\-n\fR 
Comma separated list of nodes to operate on
.TP
\fB\-c\fR
Ignore comment lines (starting with '#') in file comparisons
.TP
\fB\-w\fR
Ignore whitespace in file comparisons
.TP
\fB\-\-no\-ads\fR
Do not use commands that assume an Active Directory Server
.PP
.SH COPYRIGHT
Copyright   ©   2015   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.
.SH BUGS
No known bugs.
.SH AUTHOR
Martijn van Brummelen (mart...@brumit.nl)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 2:4.5.0+dfsg-1

This was fixed some time ago
(7f56384a8d9ff0e70969192491e4fdbd3c35391b). Thanks Martijn!

Regards
-- 
Mathieu Parent--- End Message ---

Bug#894747: marked as done (lintian: Re-enable YAML parsing for d/upstream/metadata files)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894747: fixed in lintian 2.5.81
has caused the Debian Bug report #894747,
regarding lintian: Re-enable YAML parsing for d/upstream/metadata 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.)


-- 
894747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.80
Severity: wishlist
Control: block 731340 by -1

Hi,

Currently, the lintian checks for validity of d/u/metadata are
disabled since 2.5.50.4 [1] due to a security problem [2]
(CVE-2017-8829), but now we can safety use YAML::XS with the
$LoadBlessed option [3]. I wondering if we can re-enable the
d/u/metadata checks in lintian using the safety method?

Best,
Dylan

[1] 
https://anonscm.debian.org/git/lintian/lintian.git/commit/checks/upstream-metadata.pm?id=6119d49c3b
[2] https://bugs.debian.org/861958
[3] https://bugs.debian.org/862373#59
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.81

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 894...@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: Sat, 07 Apr 2018 08:17:26 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.81
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 881491 893480 894077 894139 894356 894368 894397 894690 894747 894817 
894820 894834 895036
Changes:
 lintian (2.5.81) unstable; urgency=medium
 .
   The "Policy 4.1.4" release.
 .
   * Summary of tag changes:
 + Added:
   - debian-rules-contains-unnecessary-get-orig-source-target
   - source-contains-empty-directory
 + Removed:
   - debian-rules-missing-good-practice-target-dfsg
 .
   * checks/control-file.desc:
 + [CL] Correct location of "AutomaticDebugPackages" wiki page in the
   description of the debian-control-has-obsolete-dbg-package tag.
   Thanks to Antonio Ospite for the report.  (Closes: #893480)
   * checks/cruft.{desc,pm}:
 + [CL] Add a pedantic warning for upstream tarballs that contain empty
   directories as these can cause problems with git-buildpackage.
   Thanks to Balint Reczey for the idea!  (Closes: #894368)
   * checks/gir.{desc,pm}:
 + [CL] Apply a patch series from Simon McVittie to match the Gobject
   Introspection policy and fixing a series of false-positives. Thanks!
   (Closes: #881491)
   * checks/java.{desc,pm}:
 + [CL] Apply patch from Bas Couwenberg to bump the maximum permissible
   bytecode version number now that openjdk-9 is now the default-jdk.
   (Closes: #894397)
 + [CL] Apply patch from Bas Couwenberg to update the description of
   the unknown-java-class-version tag for openjdk-9.  (Closes: #894397)
   * checks/files.pm:
 + [CL] Add .ogg files to the list of non-license file extensions to
   avoid a false-positive in extra-license-file. Thanks to Innocent De
   Marchi for the report.  (Closes: #894139)
 + [CL] Avoid false-positives in Mallard XML files; 
   tags are anchor element and not followed automatically. Thanks to
   Simon McVittie for the report.  (Closes: #894690)
   * checks/rules.{desc,pm}:
 + [CL] Stop recommending that packages with repacked tarballs specify a
   get-orig-source target; this was removed in Debian Policy 4.1.4 in
   favour of uscan(1) and debian/watch.
 + [CL] Warn about packages that have apparently unnecessary
   "get-orig-source" targets such as single-line calls to uscan(1).
   Thanks to Mattia Rizzolo for the idea.  (Closes: #895036)
   * checks/scripts.pm:
 + [CL] Also include the offending/unknown shebang in the output of
 

Bug#894820: marked as done (lintian: Point testsuite references to salsa.d.o)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894820: fixed in lintian 2.5.81
has caused the Debian Bug report #894820,
regarding lintian: Point testsuite references to salsa.d.o
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.)


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

Hi,

The attached patch points the references in checks/testsuite.desc to
salsa.d.o.

Thanks for your work,
cheers,
Georg
From d9e30d4702140a9b1be2d085b18700f059fd5c19 Mon Sep 17 00:00:00 2001
From: Georg Faerber 
Date: Wed, 4 Apr 2018 16:26:25 +0200
Subject: [PATCH] checks/testsuite.desc: Point references to salsa.d.o
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

---
 checks/testsuite.desc | 24 
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/checks/testsuite.desc b/checks/testsuite.desc
index 226619377..1b03368dd 100644
--- a/checks/testsuite.desc
+++ b/checks/testsuite.desc
@@ -29,7 +29,7 @@ Certainty: certain
 Info: Runtime test names in debian/tests/control are only allowed to
  contain decimal digits, lowercase ASCII letters, plus or minus signs,
  dots or slashes.
-Ref: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
+Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
 
 Tag: inconsistent-testsuite-field
 Severity: wishlist
@@ -37,28 +37,28 @@ Certainty: certain
 Info: The package provides a debian/tests/control file but no
  Testsuite field in the dsc file, or the field exists but not the
  file.
-Ref: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
+Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
 
 Tag: missing-runtime-tests-field
 Severity: normal
 Certainty: certain
 Info: A mandatory field is missing in some paragraph of the
  debian/tests/control file.
-Ref: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
+Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
 
 Tag: exclusive-runtime-tests-field
 Severity: normal
 Certainty: certain
 Info: Exclusive field are specified in some paragraph of the
  debian/tests/control file.
-Ref: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
+Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
 
 Tag: missing-runtime-test-file
 Severity: normal
 Certainty: possible
 Info: A test file listed in the debian/tests/control file does not
  exist in the package source.
-Ref: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
+Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
 
 Tag: runtime-test-file-is-not-a-regular-file
 Severity: wishlist
@@ -66,7 +66,7 @@ Certainty: certain
 Info: A runtime test listed by debian/tests/control is not a regular
  file or a relative symbolic link to a regular file in the source
  package.
-Ref: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
+Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
 
 Tag: syntax-error-in-debian-tests-control
 Severity: normal
@@ -76,7 +76,7 @@ Info: The debian/tests/control file didn't pass Debian control file
  .
  This issue may hide other issues as Lintian skips some checks on the
  file in this case.
-Ref: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
+Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
 
 Tag: unknown-runtime-tests-feature
 Severity: pedantic
@@ -84,7 +84,7 @@ Certainty: wild-guess
 Info: A paragraph in debian/tests/control mentions a non-standard
  value for the Features field. Though allowed, this may indicate an
  error, as the value will be ignored.
-Ref: https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
+Ref: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
 
 Tag: unknown-runtime-tests-field
 Severity: pedantic
@@ -92,7 +92,7 @@ Certainty: wild-guess
 Info: A paragraph in debian/tests/control mentions a non-standard
  field. Though allowed, this may 

Bug#894817: marked as done (lintian: Missing autopkgtest 'needs-reboot' restriction (false positive))

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894817: fixed in lintian 2.5.81
has caused the Debian Bug report #894817,
regarding lintian: Missing autopkgtest 'needs-reboot' restriction (false 
positive)
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.)


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

Hi,

lintian is currently missing the autopkgtest 'needs-reboot' restriction,
see [1]. This leads to false positives. Patch attached.

Thanks for your work,
cheers,
Georg


[1] 
https://salsa.debian.org/ci-team/autopkgtest/blob/master/doc/README.package-tests.rst#L229
From f60201b03eb1cc6b341cca13895874e3232701eb Mon Sep 17 00:00:00 2001
From: Georg Faerber 
Date: Wed, 4 Apr 2018 15:30:42 +0200
Subject: [PATCH] checks/testsuite.pm: Add missing 'needs-reboot' restriction
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

---
 checks/testsuite.pm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/checks/testsuite.pm b/checks/testsuite.pm
index 58321e665..faff9391e 100644
--- a/checks/testsuite.pm
+++ b/checks/testsuite.pm
@@ -51,6 +51,7 @@ my %KNOWN_RESTRICTIONS = map { $_ => 1 } qw(
   build-needed
   isolation-container
   isolation-machine
+  needs-reboot
   needs-recommends
   needs-root
   rw-build-tree
-- 
2.17.0



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

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 894...@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: Sat, 07 Apr 2018 08:17:26 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.81
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 881491 893480 894077 894139 894356 894368 894397 894690 894747 894817 
894820 894834 895036
Changes:
 lintian (2.5.81) unstable; urgency=medium
 .
   The "Policy 4.1.4" release.
 .
   * Summary of tag changes:
 + Added:
   - debian-rules-contains-unnecessary-get-orig-source-target
   - source-contains-empty-directory
 + Removed:
   - debian-rules-missing-good-practice-target-dfsg
 .
   * checks/control-file.desc:
 + [CL] Correct location of "AutomaticDebugPackages" wiki page in the
   description of the debian-control-has-obsolete-dbg-package tag.
   Thanks to Antonio Ospite for the report.  (Closes: #893480)
   * checks/cruft.{desc,pm}:
 + [CL] Add a pedantic warning for upstream tarballs that contain empty
   directories as these can cause problems with git-buildpackage.
   Thanks to Balint Reczey for the idea!  (Closes: #894368)
   * checks/gir.{desc,pm}:
 + [CL] Apply a patch series from Simon McVittie to match the Gobject
   Introspection policy and fixing a series of false-positives. Thanks!
   (Closes: #881491)
   * checks/java.{desc,pm}:
 + [CL] Apply patch from Bas Couwenberg to bump the maximum permissible
   bytecode version number now that openjdk-9 is now the default-jdk.
   (Closes: #894397)
 + [CL] Apply patch from Bas Couwenberg to update the description of
   the unknown-java-class-version tag for openjdk-9.  (Closes: #894397)
   * checks/files.pm:
 + [CL] Add .ogg files to the list of non-license file extensions to
   avoid a false-positive in extra-license-file. Thanks to Innocent De
   Marchi for the report.  (Closes: #894139)
 + [CL] Avoid false-positives in Mallard XML files; 
   tags are anchor element and not followed automatically. Thanks to
   Simon McVittie for the report.  (Closes: #894690)
   * 

Bug#894834: marked as done (lintian: [PATCH] Spelling fixes)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894834: fixed in lintian 2.5.81
has caused the Debian Bug report #894834,
regarding lintian: [PATCH] Spelling fixes
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.)


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

Patch with spelling fixes against current git master is attached.
>From 9d696a6a60db01b3c069a46a5c33a31e179a8100 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ville=20Skytt=C3=A4?= 
Date: Wed, 4 Apr 2018 20:21:59 +0300
Subject: [PATCH] Spelling fixes

---
 checks/fields.desc   | 4 ++--
 checks/patch-systems.pm  | 2 +-
 checks/python.desc   | 2 +-
 checks/source-copyright.desc | 2 +-
 commands/lintian.pm  | 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/checks/fields.desc b/checks/fields.desc
index a832039c3..18f528f30 100644
--- a/checks/fields.desc
+++ b/checks/fields.desc
@@ -1458,7 +1458,7 @@ Info: This package has a relationship with the 
default-mta virtual
  default-mta and mail-transport-agent should only ever be in a set of
  alternatives together, with default-mta listed first.
  .
- Please add a "or" depedency on mail-transport-agent after
+ Please add a "or" dependency on mail-transport-agent after
  default-mta.
 
 Tag: mail-transport-agent-dependency-does-not-specify-default-mta
@@ -1471,7 +1471,7 @@ Info: This package has a relationship with the 
mail-transport-agent
  default-mta and mail-transport-agent should only ever be in a set of
  alternatives together, with default-mta listed first.
  .
- Please add a "or" depedency on default-mta before
+ Please add a "or" dependency on default-mta before
  mail-transport-agent.
 
 Tag: default-mta-dependency-not-listed-first
diff --git a/checks/patch-systems.pm b/checks/patch-systems.pm
index 06e1eaead..c98a33510 100644
--- a/checks/patch-systems.pm
+++ b/checks/patch-systems.pm
@@ -285,7 +285,7 @@ sub check_patch {
 my $tag_emitter
   = spelling_tag_emitter('spelling-error-in-patch-description',
 $patch_file);
-# Check the first line seperately to avoid duplicates
+# Check the first line separately to avoid duplicates
 foreach my $x (split(/\n/, $description, 2)) {
 check_spelling($x, $group->info->spelling_exceptions,$tag_emitter);
 }
diff --git a/checks/python.desc b/checks/python.desc
index c68b94bd3..9b5b9ad16 100644
--- a/checks/python.desc
+++ b/checks/python.desc
@@ -43,7 +43,7 @@ Info: This source package appears to generate the specified 
Python 2 package
  package and, if not, consider removing it.
  .
  Alternatively, ensure that the corresponding package specifies the
- ${python3:Depends} substvar in its binary depedencies.
+ ${python3:Depends} substvar in its binary dependencies.
 
 Tag: build-depends-on-python-sphinx-only
 Severity: normal
diff --git a/checks/source-copyright.desc b/checks/source-copyright.desc
index fbe3034dc..e848c893c 100644
--- a/checks/source-copyright.desc
+++ b/checks/source-copyright.desc
@@ -53,7 +53,7 @@ Severity: pedantic
 Certainty: certain
 Ref: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Info: Format URI of the machine-readable copyright file uses the plain HTTP
- unencrypted transport protocol.  Using HTTPS is prefered since policy 4.0.0.
+ unencrypted transport protocol.  Using HTTPS is preferred since policy 4.0.0.
  .
  Please use
  
https://www.debian.org/doc/packaging-manuals/copyright-format/version/
diff --git a/commands/lintian.pm b/commands/lintian.pm
index abcfed803..45ee25a18 100755
--- a/commands/lintian.pm
+++ b/commands/lintian.pm
@@ -194,7 +194,7 @@ EOT-EOT-EOT
 print <<"EOT-EOT-EOT";
 --tag-display-limit X Specify "tag per package" display limit
 --no-tag-display-limitDisable "tag per package" display limit
-  (equivalant to --tag-display-limit=0)
+  (equivalent to --tag-display-limit=0)
 EOT-EOT-EOT
 }
 
-- 
2.14.1

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

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 

Bug#895036: marked as done (lintian: please nag about get-orig-source targets that only call uscan)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#895036: fixed in lintian 2.5.81
has caused the Debian Bug report #895036,
regarding lintian: please nag about get-orig-source targets that only call uscan
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.)


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

Now with policy 4.1.4, people are encouraged to move from get-orig-source
to uscan + files-excluded.

Nonetheless, I know there are plenty of packages having that target with
the only goal of calling uscan (see for example all of pkg-mate
packages).

I find such target quite odd:
1) people ought to be able to call uscan themselves
2) people should call uscan with whatever options they prefer, I don't
   see why somebody should put some random preferences in d/rules
3) the duplication across packages is obnoxious, with all the effort
   than by debhelper to reduce it


-- 
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.81

We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lintian package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Apr 2018 08:17:26 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.81
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 881491 893480 894077 894139 894356 894368 894397 894690 894747 894817 
894820 894834 895036
Changes:
 lintian (2.5.81) unstable; urgency=medium
 .
   The "Policy 4.1.4" release.
 .
   * Summary of tag changes:
 + Added:
   - debian-rules-contains-unnecessary-get-orig-source-target
   - source-contains-empty-directory
 + Removed:
   - debian-rules-missing-good-practice-target-dfsg
 .
   * checks/control-file.desc:
 + [CL] Correct location of "AutomaticDebugPackages" wiki page in the
   description of the debian-control-has-obsolete-dbg-package tag.
   Thanks to Antonio Ospite for the report.  (Closes: #893480)
   * checks/cruft.{desc,pm}:
 + [CL] Add a pedantic warning for upstream tarballs that contain empty
   directories as these can cause problems with git-buildpackage.
   Thanks to Balint Reczey for the idea!  (Closes: #894368)
   * checks/gir.{desc,pm}:
 + [CL] Apply a patch series from Simon McVittie to match the Gobject
   Introspection policy and fixing a series of false-positives. Thanks!
   (Closes: #881491)
   * checks/java.{desc,pm}:
 + [CL] Apply patch from Bas Couwenberg to bump the maximum permissible
   bytecode version number now that openjdk-9 is now the default-jdk.
   (Closes: #894397)
 + [CL] Apply patch from Bas Couwenberg to update the description of
   the unknown-java-class-version tag for openjdk-9.  (Closes: #894397)
   * checks/files.pm:
 + [CL] Add .ogg files to the list of non-license file extensions to
   avoid a false-positive in extra-license-file. Thanks to Innocent De
   Marchi for the report.  (Closes: #894139)
 + [CL] Avoid false-positives in Mallard XML files; 
   tags are anchor element and not followed automatically. Thanks to
   Simon McVittie for the report.  (Closes: #894690)
   * checks/rules.{desc,pm}:
 + [CL] Stop recommending that packages with 

Bug#894368: marked as done (lintian: Please add check for empty directories in the source package)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894368: fixed in lintian 2.5.81
has caused the Debian Bug report #894368,
regarding lintian: Please add check for empty directories in the source 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.)


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

Dear Maintainers,

Please add check for empty directories in the source package to help
git-based workflows.
The proposed description of the check from the patch:

Tag: source-contains-empty-dir
Severity: pedantic
Certainty: certain
Info: The source contains an empty directory
 Having an empty directory in itself does not cause problems but empty
 directories can't be stored in Git, which is a very popular version
 control system for maintaining source packages.
 .
 Keeping the empty directory in the source package prevent others from
 easily contributing to the package by importing it in full to a local
 repository, making changes, then generating an updated source package
 with tools like git-buildpackage. In that workflow the empty directory
 would be lost potentially causing errors if the installed binary package
 relied on it or causing autopkgtest failures if tests used it.

-- 
Balint Reczey
Ubuntu & Debian Developer
From e2ab5268c055e48fe56a55fb21ab30b78d51e1b0 Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Mon, 26 Mar 2018 15:21:45 +0100
Subject: [PATCH] Emit warning if the source package contains empty dir

---
 checks/cruft.desc | 15 +++
 checks/cruft.pm   |  3 +++
 t/tests/cruft-general-test-suite/pre_upstream |  1 +
 t/tests/cruft-general-test-suite/tags |  1 +
 4 files changed, 20 insertions(+)

diff --git a/checks/cruft.desc b/checks/cruft.desc
index c469fdd59..6ce0d5664 100644
--- a/checks/cruft.desc
+++ b/checks/cruft.desc
@@ -61,6 +61,21 @@ Info: The Debian diff contains a CMake cache file.  These files embed the
  modify it in the Debian diff; instead, delete it before the build in
  debian/rules.
 
+Tag: source-contains-empty-dir
+Severity: pedantic
+Certainty: certain
+Info: The source contains an empty directory
+ Having an empty directory in itself does not cause problems but empty
+ directories can't be stored in Git, which is a very popular version
+ control system for maintaining source packages.
+ .
+ Keeping the empty directory in the source package prevent others from
+ easily contributing to the package by importing it in full to a local
+ repository, making changes, then generating an updated source package
+ with tools like git-buildpackage. In that workflow the empty directory
+ would be lost potentially causing errors if the installed binary package
+ relied on it or causing autopkgtest failures if tests used it.
+
 Tag: diff-contains-cvs-control-dir
 Severity: normal
 Certainty: certain
diff --git a/checks/cruft.pm b/checks/cruft.pm
index 9bdb20d2e..0ccde671a 100644
--- a/checks/cruft.pm
+++ b/checks/cruft.pm
@@ -615,6 +615,9 @@ sub find_cruft {
 tag 'package-does-not-install-examples', $entry
   if $basename eq 'examples' and not $ships_examples;
 }
+if (scalar($entry->children) == 0 and not $warned->{$name}) {
+tag 'source-contains-empty-dir', $entry;
+}
 
 push(@worklist, $entry->children);
 next ENTRY;
diff --git a/t/tests/cruft-general-test-suite/pre_upstream b/t/tests/cruft-general-test-suite/pre_upstream
index 8665c9269..58c8b58e2 100755
--- a/t/tests/cruft-general-test-suite/pre_upstream
+++ b/t/tests/cruft-general-test-suite/pre_upstream
@@ -7,6 +7,7 @@
 set -e
 dir="$1"
 
+mkdir -p "${dir}/empty-dir"
 mkdir -p "${dir}/t/CVS"
 echo 'source-contains-cvs-control-dir' > "${dir}/t/CVS/Entries"
 mkdir -p "${dir}/foo/t/.svn"
diff --git a/t/tests/cruft-general-test-suite/tags b/t/tests/cruft-general-test-suite/tags
index fa40db641..385e53154 100644
--- a/t/tests/cruft-general-test-suite/tags
+++ b/t/tests/cruft-general-test-suite/tags
@@ -1 +1,2 @@
 P: cruft-general-test-suite source: debian-watch-does-not-check-gpg-signature
+P: cruft-general-test-suite source: source-contains-empty-dir empty-dir/
-- 
2.15.1

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

We believe that the bug you reported is fixed in 

Bug#894690: marked as done (lintian: false positives for privacy-breach-generic when Mallard docs have a )

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894690: fixed in lintian 2.5.81
has caused the Debian Bug report #894690,
regarding lintian: false positives for privacy-breach-generic when Mallard docs 
have a 
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.)


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

Running Lintian against evolution reports lots of instances of
privacy-breach-generic, for example:

> usr/share/help/C/evolution/xinclude-filter-vfolder-conditions.xml [ href="https://bugzilla.gnome.org/show_bug.cgi?id=550796#c10;>] 
> (https://bugzilla.gnome.org/show_bug.cgi?id=550796#c10)
> usr/share/help/C/evolution/xinclude-filter-vfolder-conditions.xml [ href="https://en.wikipedia.org/wiki/regular_expression;>] 
> (https://en.wikipedia.org/wiki/regular_expression)

These are false positives: in Mallard XML,  is a clickable link that
will not be followed automatically, corresponding to  in HTML.
Mallard can be detected reasonably reliably by looking for
qr{ xmlns="http://projectmallard\.org/1\.0/"} in the first few lines.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.81

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 894...@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: Sat, 07 Apr 2018 08:17:26 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.81
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 881491 893480 894077 894139 894356 894368 894397 894690 894747 894817 
894820 894834 895036
Changes:
 lintian (2.5.81) unstable; urgency=medium
 .
   The "Policy 4.1.4" release.
 .
   * Summary of tag changes:
 + Added:
   - debian-rules-contains-unnecessary-get-orig-source-target
   - source-contains-empty-directory
 + Removed:
   - debian-rules-missing-good-practice-target-dfsg
 .
   * checks/control-file.desc:
 + [CL] Correct location of "AutomaticDebugPackages" wiki page in the
   description of the debian-control-has-obsolete-dbg-package tag.
   Thanks to Antonio Ospite for the report.  (Closes: #893480)
   * checks/cruft.{desc,pm}:
 + [CL] Add a pedantic warning for upstream tarballs that contain empty
   directories as these can cause problems with git-buildpackage.
   Thanks to Balint Reczey for the idea!  (Closes: #894368)
   * checks/gir.{desc,pm}:
 + [CL] Apply a patch series from Simon McVittie to match the Gobject
   Introspection policy and fixing a series of false-positives. Thanks!
   (Closes: #881491)
   * checks/java.{desc,pm}:
 + [CL] Apply patch from Bas Couwenberg to bump the maximum permissible
   bytecode version number now that openjdk-9 is now the default-jdk.
   (Closes: #894397)
 + [CL] Apply patch from Bas Couwenberg to update the description of
   the unknown-java-class-version tag for openjdk-9.  (Closes: #894397)
   * checks/files.pm:
 + [CL] Add .ogg files to the list of non-license file extensions to
   avoid a false-positive in extra-license-file. Thanks to Innocent De
   Marchi for the report.  (Closes: #894139)
 + [CL] Avoid false-positives in Mallard XML files; 
   tags are anchor element and not followed automatically. Thanks to
   Simon McVittie for the report.  (Closes: #894690)
   * checks/rules.{desc,pm}:
 + [CL] Stop recommending that packages with repacked tarballs specify a
   get-orig-source target; this was removed in Debian Policy 4.1.4 in
   favour of uscan(1) and debian/watch.
 + [CL] Warn about packages that have apparently 

Bug#881491: marked as done (lintian: update gir checks for gobject-introspection/1.54.1-3 mini-policy)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#881491: fixed in lintian 2.5.81
has caused the Debian Bug report #881491,
regarding lintian: update gir checks for gobject-introspection/1.54.1-3 
mini-policy
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.)


-- 
881491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.59
Severity: wishlist
Tags: patch
X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org

I've just uploaded gobject-introspection/1.54.1-3, with GIR mini-policy
updates aimed at reducing false positives from Lintian. The mini-policy
now recommends that when multiple GIR typelibs are bundled in a single
package (like gir1.2-gtk-3.0 containing Gtk-3.0, Gdk-3.0 and GdkX11-3.0),
that package should have Provides entries for those typelibs' canonical
package names (in this case gir1.2-gdk-3.0 and gir1.2-gdkx11-3.0).
This gives Lintian enough information to avoid some unnecessary warnings
when the attached patches are applied.

Additionally, patch 0001 silences a false-positive when packages ship
files other than GIR XML in /usr/share/gir-1.0 (gobject-introspection will
probably be the only package to do this, but it seemed more correct to
make this change rather than using an override).

Thanks,
smcv
>From 72fa7ee6c470b1c6051eb4f36342ff97b3550f91 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 2 Nov 2017 14:50:04 +
Subject: [PATCH 1/4] gir: Only treat *.gir files in usr/share/gir-1.0 as GIR

gir-1.2.rnc, a RELAX NG schema, is in this directory but is not itself
a GIR file.

Signed-off-by: Simon McVittie 
---
 checks/gir.pm | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/checks/gir.pm b/checks/gir.pm
index 59d7e4099..b64d19577 100644
--- a/checks/gir.pm
+++ b/checks/gir.pm
@@ -69,7 +69,10 @@ sub _run_binary {
 $madir = '${DEB_HOST_MULTIARCH}' unless defined $madir;
 
 if (my $xmldir = $info->index_resolved_path('usr/share/gir-1.0/')) {
-push @girs, $xmldir->children;
+foreach my $child ($xmldir->children) {
+next unless $child =~ m/\.gir$/;
+push @girs, $child;
+}
 }
 
 if (my $dir = $info->index_resolved_path('usr/lib/girepository-1.0/')) {
-- 
2.15.0

>From 4b5b78db2b0334d1e5f9baae9dca41bd10dbe403 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 11 Nov 2017 14:04:20 +
Subject: [PATCH 2/4] gir: Allow a Provides on the canonical name for typelib
 packages

It's OK for closely related typelibs to be grouped together, as was done
for packages like GLib, GTK+ and Tracker, as long as they are expected
to bump introspection ABI version at the same time. The new mini-policy
version in gobject-introspection/1.54.1-3 recommends that they have
a Provides on all the package names that would have been used if they
were separated (for example gir1.2-gtk-3.0 Provides gir1.2-gdk-3.0 and
gir1.2-gdkx11-3.0). If this is done, we can detect it and suppress the
typelib-package-name-does-not-match tag.

Signed-off-by: Simon McVittie 
---
 checks/gir.desc | 15 ++-
 checks/gir.pm   |  3 ++-
 2 files changed, 12 insertions(+), 6 deletions(-)

diff --git a/checks/gir.desc b/checks/gir.desc
index 611b4ac54..b154d6a88 100644
--- a/checks/gir.desc
+++ b/checks/gir.desc
@@ -48,11 +48,16 @@ Certainty: possible
 Info: GObject-Introspection binary typelibs (Foo-23.typelib)
  should normally be made available in a package named gir1.2-foo-23.
  .
- Please ignore and override this tag if the typelib is deliberately shipped
- in a package whose name does not match the typelib's machine-readable name.
- For example, gir1.2-glib-2.0 is named for the GLib-2.0
- typelib, but also contains the GObject-2.0 and Gio-2.0
- typelibs; this is unconventional, but is allowed.
+ If multiple typelibs are shipped in the same package, then that package
+ should have versioned Provides for the names that would have been
+ used for separate packages. This arrangement should only be used if the
+ included typelibs' versions are expected to remain the same at all times.
+ .
+ For example, gir1.2-gtk-3.0 is named for the Gtk-3.0
+ typelib, but also contains the Gdk-3.0 and GdkX11-3.0
+ typelibs. It should have versioned Provides entries for
+ gir1.2-gdk-3.0 (= ${binary:Version})
+ and gir1.2-gdkx11-3.0 (= ${binary:Version}) to indicate this.
 Ref: 

Bug#894397: marked as done (lintian: Update max-bytecode-version for Java 9)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894397: fixed in lintian 2.5.81
has caused the Debian Bug report #894397,
regarding lintian: Update max-bytecode-version for Java 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.)


-- 
894397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lintian
Version: 2.5.80
Severity: normal
Tags: patch

Dear Maintainer,

OpenJDK 9 is now the default-jdk in Debian unstable, causing lintian to
complain about the incompatible-java-bytecode-format.

The attached patch increases the max-bytecode-version for 53 for Java 9,
and adds the bytecode version for Java 10 as the new max existing.

Kind Regards,

Bas
diff --git a/checks/java.pm b/checks/java.pm
index dafe53122..31c0238d8 100644
--- a/checks/java.pm
+++ b/checks/java.pm
@@ -98,7 +98,7 @@ sub run {
 or $mver
 > $MAX_BYTECODE->value('max-bytecode-existing-version')) {
 # First public major version was 45 (Java1), latest
-# version is 52 (Java8).
+# version is 53 (Java9).
 tag 'unknown-java-class-version', $jar_file,
   "($class -> $mver)";
 # Skip the rest of this Jar.
@@ -213,6 +213,7 @@ sub run {
 # 50 -> Java6
 # 51 -> Java7
 # 52 -> Java8
+# 53 -> Java9
 my $bad = 0;
 
 # If the lowest version used is greater than the requested
diff --git a/data/java/constants b/data/java/constants
index c114857db..0c28b1e4a 100644
--- a/data/java/constants
+++ b/data/java/constants
@@ -4,11 +4,12 @@
 #  45-49 -> Java1
 # 50 -> Java6
 # 51 -> Java7
-# 52 -> Java8 - Current max version in Debian unstable
-# 53 -> Java9
-max-bytecode-version = 52
+# 52 -> Java8
+# 53 -> Java9 - Current max version in Debian unstable
+# 54 -> Java10
+max-bytecode-version = 53
 
-max-bytecode-existing-version = 53
+max-bytecode-existing-version = 54
 
 # The following should not change
 min-bytecode-version = 45
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.81

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 894...@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: Sat, 07 Apr 2018 08:17:26 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.81
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 881491 893480 894077 894139 894356 894368 894397 894690 894747 894817 
894820 894834 895036
Changes:
 lintian (2.5.81) unstable; urgency=medium
 .
   The "Policy 4.1.4" release.
 .
   * Summary of tag changes:
 + Added:
   - debian-rules-contains-unnecessary-get-orig-source-target
   - source-contains-empty-directory
 + Removed:
   - debian-rules-missing-good-practice-target-dfsg
 .
   * checks/control-file.desc:
 + [CL] Correct location of "AutomaticDebugPackages" wiki page in the
   description of the debian-control-has-obsolete-dbg-package tag.
   Thanks to Antonio Ospite for the report.  (Closes: #893480)
   * checks/cruft.{desc,pm}:
 + [CL] Add a pedantic warning for upstream tarballs that contain empty
   directories as these can cause problems with git-buildpackage.
   Thanks to Balint Reczey for the idea!  (Closes: #894368)
   * checks/gir.{desc,pm}:
 + [CL] Apply a patch series from Simon McVittie to match the Gobject
   Introspection policy and fixing a series of false-positives. Thanks!
   (Closes: #881491)
   * checks/java.{desc,pm}:
 + [CL] Apply patch from Bas Couwenberg to bump the maximum permissible
   bytecode version number now 

Bug#894077: marked as done (lintian: False positive spelling-error-in-manpage information)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894077: fixed in lintian 2.5.81
has caused the Debian Bug report #894077,
regarding lintian: False positive spelling-error-in-manpage information
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.)


-- 
894077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.77~bpo9+1
Severity: normal

Hello,

lintian reports:
I: glusterfs-server: spelling-error-in-manpage usr/share/man/man8/gluster.8.gz 
directorys directories
I: glusterfs-server: spelling-error-in-manpage usr/share/man/man8/gluster.8.gz 
directorys directories

I have found this in the manpage:
$ grep 'directory(s)' doc/gluster.8
Lists the  usage and limits configured on directory(s). If a path is given only 
the limit that has been configured on the directory(if any) is displayed along 
with the directory's usage. If no path is given, usage and limits are displayed 
for all directories that has limits configured.
Lists the inode usage and inode limits configured on directory(s). If a path is 
given only the limit that has been configured on the directory(if any) is 
displayed along with the directory's inode usage. If no path is given, usage 
and limits are displayed for all directories that has limits configured.

So it matches on "directory(s)", which is IMHO correct?

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.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+b1
ii  dpkg  1.18.24
ii  file  1:5.30-1+deb9u1
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+deb9u2
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libxml-simple-perl2.22-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+deb9u2
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:
ii  binutils-multiarch 2.28-5
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.81

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 894...@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: Sat, 07 Apr 2018 08:17:26 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.81
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 

Bug#894356: marked as done (lintian: udev-rule-missing-subsystem false positives when SUBSYSTEM GOTO is not the last GOTO)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894356: fixed in lintian 2.5.81
has caused the Debian Bug report #894356,
regarding lintian: udev-rule-missing-subsystem false positives when SUBSYSTEM 
GOTO is not the last GOTO
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.)


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

Package: lintian
Version: 2.5.79
Severity: normal

Dear Maintainer,

Last week I started to prepare a new package for inclusion in Buster.
Unfortunately, lintian reports 18 warnings on the following valid udev
rules file:

https://github.com/knxd/knxd/blob/master/debian/knxd.udev

Line 22 sends everything except subsystem "usb" to "knxd_end", so in 
lines
23-62 the subsystem is clearly defined. Nevertheless, lintian warns 
about

every other line in the range 26-60:

W: knxd: udev-rule-missing-subsystem 
lib/udev/rules.d/60-knxd.rules:26

vendor/product matching missing SUBSYSTEM specifier
[...]
W: knxd: udev-rule-missing-subsystem 
lib/udev/rules.d/60-knxd.rules:60

vendor/product matching missing SUBSYSTEM specifier

Currently lintian remembers the last goto rule it encounters and checks
whether that was a subsystem goto rule on every device rule it 
processes.

Unfortunately, this approach requires the subsystem goto rule to be the
last one right before the device rules. However, there is another goto
rule between these in the affected udev file, therefore lintian does not
recognize this situation.

Please pull the patch including updated test case to catch this from my
fork:

https://salsa.debian.org/dallmair-guest/lintian.git, branch
udev-rules-subsystem-goto

Thanks.
-Thomas


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

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

Versions of packages lintian depends on:
ii  binutils  2.30-7
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.19.0.5
ii  file  1:5.32-2
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.60-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.39-1
ii  libdpkg-perl  1.19.0.5
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.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.1-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.73-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.69+repack-1
ii  man-db2.8.2-1
ii  patchutils0.3.4-2
ii  perl  5.26.1-5
ii  t1utils   1.41-2
ii  xz-utils  5.2.2-1.3

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

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

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

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 894...@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

Bug#893480: marked as done (lintian: Wrong URL in debian-control-has-obsolete-dbg-package)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#893480: fixed in lintian 2.5.81
has caused the Debian Bug report #893480,
regarding lintian: Wrong URL in debian-control-has-obsolete-dbg-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.)


-- 
893480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.79
Severity: minor
Tags: patch

Dear Maintainer,

the current URL[1] in debian-control-has-obsolete-dbg-package brings to
a generic Wiki page, it misses a trailing 's'.

I am attaching a patch to use the correct URL[2] which gets directly to
the page about Automatic Debug Packages.

Ciao,
   Antonio

[1] https://wiki.debian.org/AutomaticDebugPackage
[2] https://wiki.debian.org/AutomaticDebugPackages

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

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

Versions of packages lintian depends on:
ii  binutils  2.30-7
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.19.0.5
ii  file  1:5.32-2
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.60-1
ii  libclass-accessor-perl0.51-1
ii  libclone-perl 0.39-1
ii  libdpkg-perl  1.19.0.5
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.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.1-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.73-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.69+repack-1
ii  man-db2.8.2-1
ii  patchutils0.3.4-2
ii  perl  5.26.1-5
ii  t1utils   1.41-2
ii  xz-utils  5.2.2-1.3

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

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

-- 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?
>From 8c29d57a53240fd4efc0beb92e20f9d1e92c82ea Mon Sep 17 00:00:00 2001
From: Antonio Ospite 
Date: Mon, 19 Mar 2018 10:33:15 +0100
Subject: [PATCH] Fix wrong URL in debian-control-has-obsolete-dbg-package
X-Face: z*RaLf`X<@C75u6Ig9}{oW$H;1_\2t5)({*|jhM/Vb;]yA5\I~93>J<_`<4)A{':UrE

The current URL brings to a generic Wiki page, use the correct URL which
gets directly to the page about Automatic Debug Packages.
---
 checks/control-file.desc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/checks/control-file.desc b/checks/control-file.desc
index 18b3d8cf4..ce13d48d4 100644
--- a/checks/control-file.desc
+++ b/checks/control-file.desc
@@ -49,7 +49,7 @@ Info: The debian/control file includes declaration of
 Tag: debian-control-has-obsolete-dbg-package
 Severity: wishlist
 Certainty: possible
-Ref: https://wiki.debian.org/AutomaticDebugPackage
+Ref: https://wiki.debian.org/AutomaticDebugPackages
 Info: The debian/control file includes declaration of
  -dbg package.
  .
-- 
2.16.2

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

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 

Bug#894139: marked as done (extra-license-file false positive)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 09:19:37 +
with message-id 
and subject line Bug#894139: fixed in lintian 2.5.81
has caused the Debian Bug report #894139,
regarding extra-license-file false positive
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.)


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

Dear Maintainer,

I have obtained the following message from lintian:

I: pinball-data: extra-license-file
usr/share/games/pinball/gnu/gplv1.ogg 
I: pinball-data: extra-license-file
usr/share/games/pinball/gnu/gplv2.ogg
I:pinball-data: extra-license-file usr/share/games/pinball/gnu/gplv3.ogg

* .ogg files are sound files, not licenses. Maybe Lintian could check
  the contents of the files (as well as warn of typographical errors).


Regards!


I. De Marchi
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.81

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 894...@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: Sat, 07 Apr 2018 08:17:26 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.81
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 881491 893480 894077 894139 894356 894368 894397 894690 894747 894817 
894820 894834 895036
Changes:
 lintian (2.5.81) unstable; urgency=medium
 .
   The "Policy 4.1.4" release.
 .
   * Summary of tag changes:
 + Added:
   - debian-rules-contains-unnecessary-get-orig-source-target
   - source-contains-empty-directory
 + Removed:
   - debian-rules-missing-good-practice-target-dfsg
 .
   * checks/control-file.desc:
 + [CL] Correct location of "AutomaticDebugPackages" wiki page in the
   description of the debian-control-has-obsolete-dbg-package tag.
   Thanks to Antonio Ospite for the report.  (Closes: #893480)
   * checks/cruft.{desc,pm}:
 + [CL] Add a pedantic warning for upstream tarballs that contain empty
   directories as these can cause problems with git-buildpackage.
   Thanks to Balint Reczey for the idea!  (Closes: #894368)
   * checks/gir.{desc,pm}:
 + [CL] Apply a patch series from Simon McVittie to match the Gobject
   Introspection policy and fixing a series of false-positives. Thanks!
   (Closes: #881491)
   * checks/java.{desc,pm}:
 + [CL] Apply patch from Bas Couwenberg to bump the maximum permissible
   bytecode version number now that openjdk-9 is now the default-jdk.
   (Closes: #894397)
 + [CL] Apply patch from Bas Couwenberg to update the description of
   the unknown-java-class-version tag for openjdk-9.  (Closes: #894397)
   * checks/files.pm:
 + [CL] Add .ogg files to the list of non-license file extensions to
   avoid a false-positive in extra-license-file. Thanks to Innocent De
   Marchi for the report.  (Closes: #894139)
 + [CL] Avoid false-positives in Mallard XML files; 
   tags are anchor element and not followed automatically. Thanks to
   Simon McVittie for the report.  (Closes: #894690)
   * checks/rules.{desc,pm}:
 + [CL] Stop recommending that packages with repacked tarballs specify a
   get-orig-source target; this was removed in Debian Policy 4.1.4 in
   favour of uscan(1) and debian/watch.
 + [CL] Warn about packages that have apparently unnecessary
   "get-orig-source" targets such as single-line calls to uscan(1).
   Thanks to Mattia Rizzolo for the idea.  (Closes: #895036)
   * checks/scripts.pm:
 + [CL] Also include the offending/unknown shebang in the output of
   missing (unversioned) interpreters.
   * checks/source-copyright.desc:
 + [CL] 

Bug#658597: marked as done (cl-contextl: Reported darcs url doesn't work.)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 08:50:01 +
with message-id 
and subject line Bug#658597: fixed in cl-contextl 1:0.61-2
has caused the Debian Bug report #658597,
regarding cl-contextl: Reported darcs url doesn't work.
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.)


-- 
658597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-contextl
Severity: minor
Hi,

When doing

  $ apt-get source cl-contextl

I get a helpful message:

  NOTICE: 'cl-contextl' packaging is maintained in the 'Darcs' version control 
system at:
  http://darcs.debian.org/darcs/pkg-common-lisp/cl-contextl

This is lovely, but then

  $ darcs get http://darcs.debian.org/darcs/pkg-common-lisp/cl-contextl

  darcs failed:  Not a repository: 
http://darcs.debian.org/darcs/pkg-common-lisp/cl-contextl (Failed to download 
URL http://darcs.debian.org/darcs/pkg-common-lisp/cl-contextl/_darcs/inventory: 
HTTP response code said error)

Very confusing! Of course, when you go to
http://darcs.debian.org/darcs/pkg-common-lisp/cl-contextl in a browser,
all becomes clear: there's a redirect to
http://anonscm.debian.org/darcs/pkg-common-lisp/cl-contextl.

I'm not sure whether darcs.debian.org should redirect the
_darcs/inventory url rather than give a 404 but, for this package, the
confusion can be removed by changing the Vcs-Darcs line in
debian/control to point at the new URL.

Thanks,

Rupert


--- End Message ---
--- Begin Message ---
Source: cl-contextl
Source-Version: 1:0.61-2

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated cl-contextl 
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, 07 Apr 2018 09:39:49 +0200
Source: cl-contextl
Binary: cl-contextl
Architecture: source
Version: 1:0.61-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Sébastien Villemot 
Description:
 cl-contextl - context orientation for Common Lisp
Closes: 658597
Changes:
 cl-contextl (1:0.61-2) unstable; urgency=medium
 .
   * Team upload.
   * Update Vcs-* fields for move to salsa. (Closes: #658597)
   * Set Maintainer to debian-common-lisp@l.d.o.
   * Update Homepage URL in d/control and d/copyright.
   * Move to 3.0 (quilt) source format.
   * Remove Build-Depends on dh-lisp.
   * Remove obsolete README.building and README.debian.
   * Update d/watch using uscan git HEAD mode.
Checksums-Sha1:
 2e3a880d0521d4a5f726577f66e7142dfbcca1a1 1939 cl-contextl_0.61-2.dsc
 e2bd08d9e5fd85636490a29d7dc111d92efd89da 3992 cl-contextl_0.61-2.debian.tar.xz
 443411cfa03585afce575c948eca34d115f52793 5404 
cl-contextl_0.61-2_amd64.buildinfo
Checksums-Sha256:
 a477f39a733a9ec2679d284f499c79b5d6002b637a44a8d65a81455fa9daa700 1939 
cl-contextl_0.61-2.dsc
 8d7f8b06f3615ca9533c80c4fd662a347116d6af84ea533a187c46f107020f58 3992 
cl-contextl_0.61-2.debian.tar.xz
 ef1a9b0b6fa04ca3dee067a90b2a21e91829b5ac44b863d326cabec21b0ee94a 5404 
cl-contextl_0.61-2_amd64.buildinfo
Files:
 46b6b28da71683070f100a8795dc0c06 1939 lisp optional cl-contextl_0.61-2.dsc
 590883c314ecf57a18da223583a242d0 3992 lisp optional 
cl-contextl_0.61-2.debian.tar.xz
 ca2eab9b14cc0cc4ae0529b60fc2adf4 5404 lisp optional 
cl-contextl_0.61-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlrIdlEACgkQLOzpNQ7O
vkolDBAAmtYP62QlRfggfGytPefkHsojjKEc8bgm7a10SwwPlvj9EGL0hQ8p1vWx
yawF6T7StLs0XqRHFW7dl4qxsemvFinHIiWcMU065WbgIkITsryTCy0+kL3S/YOS
TV+drYhrSrdwc2ntWVQZgCilpXPN6CtxQG7t9vt9NK4PoSqoOA2pwYfS3rn2J3rr
E6BpoHaq0IkJtEC4nVSZzl2gG340to2CeQ79ksmJ0+tkbNWzWlgjy5pIAUcw0ume
qqlK4I/WlCd78oWhSFNSz/q087M33aW3vZryWT9yjFDdR1qZU/NOCX5OJ6ZGlyaq
nbApbb3Bc8nihx2kHURciUq8+uMMU0LlHtF0AfUDk5rxptKqI6M/V1urxtfM17Bo
sODkJstOtsa7PUsUaocyCLT7VK3qTp5++phmEsC3x5slO3p4dyh8ip4cNqbmVtyC

Bug#637707: marked as done (cl-lw-compat: missing verb in package description)

[Debian Bug Tracking System]

Your message dated Sat, 07 Apr 2018 08:50:08 +
with message-id 
and subject line Bug#637707: fixed in cl-lw-compat 0.23-2
has caused the Debian Bug report #637707,
regarding cl-lw-compat: missing verb in package description
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.)


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

Package: cl-lw-compat
Severity: minor

In DDTSS I see:

This library a portable implementation of
^
|

I think it must be:

This library is a portable implementation of

Ciao
Davide

--
Dizionari: http://linguistico.sourceforge.net/wiki
Elenco di software libero: http://tinyurl.com/eddgj
GNU/Linux User: 302090: http://counter.li.org
Non autorizzo la memorizzazione del mio indirizzo su outlook



--- End Message ---
--- Begin Message ---
Source: cl-lw-compat
Source-Version: 0.23-2

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated cl-lw-compat 
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, 07 Apr 2018 09:56:51 +0200
Source: cl-lw-compat
Binary: cl-lw-compat
Architecture: source
Version: 0.23-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Sébastien Villemot 
Description:
 cl-lw-compat - LispWorks Compatibility Library
Closes: 637707
Changes:
 cl-lw-compat (0.23-2) unstable; urgency=medium
 .
   * Team upload.
   * Update Vcs-* fields for move to salsa.
   * Set Maintainer to debian-common-lisp@l.d.o.
   * Remove Build-Depends on dh-lisp.
   * Remove obsolete README.building and README.debian.
   * Update d/watch using uscan git HEAD mode.
   * Move to 3.0 (quilt) source format.
   * Fix wording of long description. (Closes: #637707)
   * Remove obsolete Conflicts against cl-aspectl.
Checksums-Sha1:
 648f14e7bcda2928582315835aa995e105831280 1946 cl-lw-compat_0.23-2.dsc
 8b9f79bc439a89d6b99181a2fe20fb3aae9283d1 2552 cl-lw-compat_0.23-2.debian.tar.xz
 e8fc56e34a98c94272b5ccfc28d41b759ffc2308 5409 
cl-lw-compat_0.23-2_amd64.buildinfo
Checksums-Sha256:
 0873ff267351a8274911dd9549af6170f91ca7722cbff5f530d15338a1eaa044 1946 
cl-lw-compat_0.23-2.dsc
 e2d0ae832e308f68744796f27e76be1887f19ed4e5fb4a205493339a18989aa1 2552 
cl-lw-compat_0.23-2.debian.tar.xz
 22e666c3d9a985e261422fce823b599e06004e9a2b3d798574d6927e0c5c2bc6 5409 
cl-lw-compat_0.23-2_amd64.buildinfo
Files:
 2c1c99f658505eac91c73384de17 1946 libs optional cl-lw-compat_0.23-2.dsc
 17761436f7dfa3e98f8422c9af6aceee 2552 libs optional 
cl-lw-compat_0.23-2.debian.tar.xz
 bf8379ae59b72765f50bcbab787e3095 5409 libs optional 
cl-lw-compat_0.23-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlrIgEQACgkQLOzpNQ7O
vkqvWw//RpT65tQLnwcB1KLgu0vucBCLQ8wba+NEuZOF3zsLuBjPUFXYmETyxX+y
VClj+GotGCUvqE59UgCebksjwEz4IF/Gkg6w4Qqtpqjcz0uDf8STZmoMwXBWy+hx
nzKd82eskkPqMqQU8D1TnFgYomIaOIjNLh5HeX5zCIrFxJHzXSANIHg8VJwci++m
+lFnIA95116mpL0yAOUyYCIWWdHrAgNJIMvFcF0j5Ts6HBL0zZkr4PmkPWI9ldOK
0enxEwYOISezfFVLXXmlrvBgJFrYbIKzz8/I1QjsPSbgHJ+9XIgA/VEfhVW58f+v
KY9XFyjHJb74TPoTXu4RCtnCFIJ1qGNePGNt9IwN0ef9ipDDonjtSNLRgy/R6rt3
jOpq+1QAzrpk5JQKsriw/R1zoVokrsVvyK93ViLI7QbYW+5uTgfHssJe0KfOhpeM
VWcGzM53PJjNzpAQBP5W9rfoS2WmA+QquDPXxCcxKaX2nq78IPDyVr6fttsewzG8
EQpX7BBeOkjOwT5cgsuMxLkkqWfky/yggeFQyTeqDiCDNvtMKwgd8L9vzVrlYaHr
q889JDk9PsbyCjBnb0m2c1ZvptQVSxKR3UkJTjurj1k2yWljdQ7OuAZeEdTHxvUK
Lo4AnySt72vLVqE3seejxclFyTWKfR/wYYqQ7Gr6G7OSFkX6KGM=
=vw/q
-END PGP SIGNATURE End Message ---

Bug#894893: marked as done (please avoid runtime dependency on distutils)

[Debian Bug Tracking System]

Your message dated Sat, 7 Apr 2018 16:17:33 +0800
with message-id 

and subject line Re: Bug#894893: please avoid runtime dependency on distutils
has caused the Debian Bug report #894893,
regarding please avoid runtime dependency on distutils
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.)


-- 
894893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: galternatives
Version: 0.92.3
Tags: patch

please avoid the runtime dependency on distutils. The standard library has
shutil.which available with the same functionality.

diff -Nru galternatives-0.92.3/debian/changelog galternatives-0.92.3ubuntu1/debian/changelog
--- galternatives-0.92.3/debian/changelog	2018-03-23 07:22:06.0 +
+++ galternatives-0.92.3ubuntu1/debian/changelog	2018-04-05 09:54:08.0 +
@@ -1,3 +1,9 @@
+galternatives (0.92.3ubuntu1) bionic; urgency=medium
+
+  * Avoid runtime dependency on distutils.
+
+ -- Matthias Klose   Thu, 05 Apr 2018 11:54:08 +0200
+
 galternatives (0.92.3) unstable; urgency=medium
 
   * Add Danish translation (by scootergrisen).
diff -Nru galternatives-0.92.3/debian/control galternatives-0.92.3ubuntu1/debian/control
--- galternatives-0.92.3/debian/control	2018-03-23 07:22:06.0 +
+++ galternatives-0.92.3ubuntu1/debian/control	2018-04-05 09:54:05.0 +
@@ -20,7 +20,6 @@
 Architecture: all
 Depends:
  gir1.2-gtk-3.0,
- python3-distutils,
  python3-gi,
  ${misc:Depends},
  ${python3:Depends},
diff -Nru galternatives-0.92.3/galternatives/app.py galternatives-0.92.3ubuntu1/galternatives/app.py
--- galternatives-0.92.3/galternatives/app.py	2018-01-30 16:11:54.0 +
+++ galternatives-0.92.3ubuntu1/galternatives/app.py	2018-04-05 09:52:56.0 +
@@ -9,7 +9,7 @@
 except ImportError:
 set_logger = None
 
-from distutils import spawn
+import shutil
 from gi.repository import Gio, GLib, Gtk
 import os
 
@@ -55,7 +55,7 @@
 if options.contains('normal'):
 logger.warn(_(
 'No root detected, but continue as in your wishes'))
-elif spawn.find_executable('pkexec'):
+elif shutil.which('pkexec'):
 self.use_polkit = True
 else:
 dialog = Gtk.MessageDialog(
diff -Nru galternatives-0.92.3/galternatives/gui.py galternatives-0.92.3ubuntu1/galternatives/gui.py
--- galternatives-0.92.3/galternatives/gui.py	2018-01-30 16:11:54.0 +
+++ galternatives-0.92.3ubuntu1/galternatives/gui.py	2018-04-05 09:53:44.0 +
@@ -9,7 +9,7 @@
 from .utils import GtkTemplate, stateful_property
 
 from copy import deepcopy
-from distutils import spawn
+import shutil
 from functools import wraps
 from gi.repository import GdkPixbuf, Gio, GLib, Gtk, GObject
 import os
@@ -348,7 +348,7 @@
 self.paths = paths
 self.group = alternative.Group(group, create=True) if group else None
 self.use_polkit = app.use_polkit if app else \
-os.getuid() and bool(spawn.find_executable('pkexec'))
+os.getuid() and bool(shutil.which('pkexec'))
 
 # glade XML
 self.builder = Gtk.Builder.new_from_file(
--- End Message ---
--- Begin Message ---
Source: galternatives
Source-Version: 0.92.4


I just uploaded a new version of galternatives. Note that I have added
python3-distutils as build-dependency since otherwise the package
would FTBFS.

--
Regards,
Boyuan Yang--- End Message ---