Processed: severity of 816101 is serious, tagging 816101

[Debian Bug Tracking System]

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

> severity 816101 serious
Bug #816101 [src:petsc] FTBFS on mipsel - broken openmpi breaks petsc build
Severity set to 'serious' from 'important'
> tags 816101 + sid stretch
Bug #816101 [src:petsc] FTBFS on mipsel - broken openmpi breaks petsc build
Added tag(s) sid and stretch.
> # FTBFS on release arch, built before there
> thanks
Stopping processing here.

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

Bug#740111: Fixed in unstable

[Tobias Frost]

On Tue, 25 Feb 2014 23:26:48 +0100 Yann Dirson  wrote:
> fixed 740111 1.4.2-1
> thanks
> 
> 

Can the bug be closed then?
(marking it fixed won't do that)

If so, just reply to 740111-d...@bugs.debian.org ;-)

--
tobi

Bug#821910: marked as done (gnupg1: fails to upgrade from 'sid' - trying to overwrite /usr/share/info/gnupg1.info.gz)

[Debian Bug Tracking System]

Your message dated Fri, 22 Apr 2016 04:24:05 +
with message-id 
and subject line Bug#821910: fixed in gnupg 1.4.20-6+exp2
has caused the Debian Bug report #821910,
regarding gnupg1: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/info/gnupg1.info.gz
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnupg1
Version: 1.4.20-6+exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package gnupg1.
  (Reading database ... 
(Reading database ... 7352 files and directories currently installed.)
  Preparing to unpack .../gnupg1_1.4.20-6+exp1_amd64.deb ...
  Unpacking gnupg1 (1.4.20-6+exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gnupg1_1.4.20-6+exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/info/gnupg1.info.gz', which is also in 
package gnupg 1.4.20-6
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/gnupg1_1.4.20-6+exp1_amd64.deb


cheers,

Andreas


gnupg1_1.4.20-6+exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gnupg
Source-Version: 1.4.20-6+exp2

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated gnupg 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, 22 Apr 2016 00:06:39 -0400
Source: gnupg
Binary: gnupg1 gnupg1-curl gpgv1 gpgv1.4-udeb
Architecture: source
Version: 1.4.20-6+exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian GnuPG-Maintainers 
Changed-By: Daniel Kahn Gillmor 
Description:
 gnupg1 - GNU privacy guard - a free PGP replacement ("classic" version)
 gnupg1-curl - GNU privacy guard - a free PGP replacement (cURL helpers for "cla
 gpgv1  - GNU privacy guard - signature verification tool ("classic" versio
 gpgv1.4-udeb - minimal signature verification tool (udeb)
Closes: 821910
Changes:
 gnupg (1.4.20-6+exp2) experimental; urgency=medium
 .
   * corrected Conflicts with older gnupg binaries (Closes: #821910)
Checksums-Sha1:
 25e468ca11f327271569fa7aedd6d2f76e1bcf2c 2403 gnupg_1.4.20-6+exp2.dsc
 ff8719556f1e0eab976bfd02a3757c0bcd71655e 29952 
gnupg_1.4.20-6+exp2.debian.tar.xz
Checksums-Sha256:
 c7c3c5115da9bc6bb028552fa7fcb18c902e5af3d47dd947c3307354f0516821 2403 
gnupg_1.4.20-6+exp2.dsc
 302b10ee09fae4fa3293a49a5ccbb1fe5bee58ff5689137d255309ab9c636214 29952 
gnupg_1.4.20-6+exp2.debian.tar.xz
Files:
 07674edda7a3e8962a148fa8a2c0173f 2403 utils important gnupg_1.4.20-6+exp2.dsc
 976c13104614c6b04f479bdecc0d3fc6 29952 utils important 
gnupg_1.4.20-6+exp2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXGaPGXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFREIyRTc0RjU2RkNGMkI2NzI5N0I3MzUy
NEVDRkY1QUZGNjgzNzBBAAoJECTs/1r/aDcKs0MP/2eumXPbAr+TylAG/KtoWKHF
tkFoAjEi2JOKwRV819rfo3DrvPrVz+nm6mq7sOWqkw7x9S8D4WYAU8nMPsdlNVxj
CmsWHfNDJVSHaSiu80ay8qH+kDqug36IfE5cINqiqiDz0kXXe+3OTILDSKOGD48W
055QnJgd2FAzHIvNTmXVWL6YWVXVrP7j5ca5WbWg5AAfM1Hjh+IBNcWNl7/63yVV
YszT+642h2456xR/cWPz1DmdbgYBOhCem3fA6Dl5b9EtNsGtYDQRPWecPCHkC8qY
+zT+YTAA8U5Ub8WeTenqe1DENt3YYUHKEEL/NBRt56kSwifE5Ei79Cm77x5oyHOa
lWEofvPlMTYv3aiRn9oZt8yzcLWncIFAkhmxnL7SCTGKgSVSQaj8S07Na+dSxjIK

Bug#821910: marked as pending

[Daniel Kahn Gillmor]

tag 821910 pending
thanks

Hello,

Bug #821910 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-gnupg/gnupg.git;a=commitdiff;h=165850d

---
commit 165850d676f25c80d6836ae01773dc0a3ace0693
Author: Daniel Kahn Gillmor 
Date:   Fri Apr 22 00:07:37 2016 -0400

corrected Conflicts with older gnupg binaries (Closes: #821910)

diff --git a/debian/changelog b/debian/changelog
index acb69ab..d516bc3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+gnupg (1.4.20-6+exp2) experimental; urgency=medium
+
+  * corrected Conflicts with older gnupg binaries (Closes: #821910)
+
+ -- Daniel Kahn Gillmor   Fri, 22 Apr 2016 00:06:39 
-0400
+
 gnupg (1.4.20-6+exp1) experimental; urgency=medium
 
   * ship binary packages gpgv1 and gnupg1, since gnupg2 source package is

Processed: Bug#821910 marked as pending

[Debian Bug Tracking System]

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

> tag 821910 pending
Bug #821910 [gnupg1] gnupg1: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/info/gnupg1.info.gz
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#821942: marked as done (libnet-dns-sec-perl: Errors were encountered while processing: libnet-dns-sec-perl)

[Debian Bug Tracking System]

Your message dated Fri, 22 Apr 2016 00:19:05 +
with message-id 
and subject line Bug#820332: fixed in libnet-dns-perl 1.05-2
has caused the Debian Bug report #820332,
regarding libnet-dns-sec-perl: Errors were encountered while processing: 
libnet-dns-sec-perl
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.)


-- 
820332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-dns-sec-perl
Version: 0.21-1
Severity: important

Hi,
I try to install nagios-plugins-contrib which needs libnet-dns-sec-perl but its 
not installable
because of 
Unpacking libnet-dns-sec-perl (0.21-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libnet-dns-sec-perl_0.21-1_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/Net::DNS::RR::KEY.3pm.gz', which is 
also in package libnet-dns-perl 1.05-1
Preparing to unpack .../nagios-plugins-contrib_16.20151226_amd64.deb ...
Unpacking nagios-plugins-contrib (16.20151226) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libnet-dns-sec-perl_0.21-1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

Versions of packages libnet-dns-sec-perl depends on:
ii  libcrypt-openssl-bignum-perl0.06-1+b2
ii  libcrypt-openssl-dsa-perl   0.15-1+b2
ii  libcrypt-openssl-random-perl0.11-1+b1
ii  libcrypt-openssl-rsa-perl   0.28-2+b3
ii  libdigest-bubblebabble-perl 0.02-2
ii  libmime-base32-perl 1.02a-1
ii  libnet-dns-perl 0.81-2+b1
ii  libperl5.22 [libdigest-sha-perl]5.22.1-9
ii  perl5.22.1-9
ii  perl-modules-5.22 [libtime-local-perl]  5.22.1-9

libnet-dns-sec-perl recommends no packages.

libnet-dns-sec-perl suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libnet-dns-perl
Source-Version: 1.05-2

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated libnet-dns-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Apr 2016 01:45:09 +0200
Source: libnet-dns-perl
Binary: libnet-dns-perl
Architecture: source all
Version: 1.05-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Axel Beckert 
Description:
 libnet-dns-perl - Perform DNS queries from a Perl script
Closes: 820332
Changes:
 libnet-dns-perl (1.05-2) unstable; urgency=medium
 .
   * Team upload.
   * Update versioned Breaks and add versioned Replaces on
 libnet-dns-sec-perl << 1.01. (Closes: #820332)
   * Declare compliance with Debian Policy 3.9.8.
   * Remove netdns.* stanza from debian/copyright: Files no more included
 in upstream tar ball.
   * Switch back to arch:all since no more C code is included.
Checksums-Sha1:
 086708333e010b3f68df84cfd0228bdeefc38126 2116 libnet-dns-perl_1.05-2.dsc
 51955510279230668c774447308feb0097da223a 6180 
libnet-dns-perl_1.05-2.debian.tar.xz
 0d438743e695b831386964add28d3c1945aad947 364908 libnet-dns-perl_1.05-2_all.deb
Checksums-Sha256:
 9c16d066a3f17e3042b0f045909544f3d732405ff51cc3b7883bbb5049e67aa4 2116 
libnet-dns-perl_1.05-2.dsc
 7cb74663f19aed8d7e55c4e3008b1ca4926eb38ac7ede4ed012209f527cadf70 6180 
libnet-dns-perl_1.05-2.debian.tar.xz
 964bacf8e38ad69fbc35f1c331fecb6a6c55754bd0578718ac4c849bc82bd47c 364908 

Bug#820332: marked as done (libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in Conflicts)

[Debian Bug Tracking System]

Your message dated Fri, 22 Apr 2016 00:19:05 +
with message-id 
and subject line Bug#820332: fixed in libnet-dns-perl 1.05-2
has caused the Debian Bug report #820332,
regarding libnet-dns-perl: Conflict with libnet-dns-sec-perl but not in 
Conflicts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
820332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-dns-perl
Version: 1.05-1
Severity: serious
Justification: Policy 7.4



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

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

Versions of packages libnet-dns-perl depends on:
ii  libc6   2.22-5
ii  libdigest-hmac-perl 1.03+dfsg-1
ii  libio-socket-inet6-perl 2.72-2
ii  libnet-ip-perl  1.26-1
ii  perl5.22.1-9
ii  perl-base [perlapi-5.22.1]  5.22.1-9

libnet-dns-perl recommends no packages.

libnet-dns-perl suggests no packages.

-- no debconf information

Trying to install the new version I get a problem with a file being
overwritten in libnet-dns-sec-perl.

Performing actions...
(Reading database ... 392443 files and directories currently installed.)
Preparing to unpack .../libnet-dns-perl_1.05-1_amd64.deb ...
Unpacking libnet-dns-perl (1.05-1) over (0.81-2+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libnet-dns-perl_1.05-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/perl5/Net/DNS/RR/DLV.pm', which is also in 
package libnet-dns-sec-perl 0.21-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libnet-dns-perl_1.05-1_amd64.deb
 
--- End Message ---
--- Begin Message ---
Source: libnet-dns-perl
Source-Version: 1.05-2

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated libnet-dns-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Apr 2016 01:45:09 +0200
Source: libnet-dns-perl
Binary: libnet-dns-perl
Architecture: source all
Version: 1.05-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Axel Beckert 
Description:
 libnet-dns-perl - Perform DNS queries from a Perl script
Closes: 820332
Changes:
 libnet-dns-perl (1.05-2) unstable; urgency=medium
 .
   * Team upload.
   * Update versioned Breaks and add versioned Replaces on
 libnet-dns-sec-perl << 1.01. (Closes: #820332)
   * Declare compliance with Debian Policy 3.9.8.
   * Remove netdns.* stanza from debian/copyright: Files no more included
 in upstream tar ball.
   * Switch back to arch:all since no more C code is included.
Checksums-Sha1:
 086708333e010b3f68df84cfd0228bdeefc38126 2116 libnet-dns-perl_1.05-2.dsc
 51955510279230668c774447308feb0097da223a 6180 
libnet-dns-perl_1.05-2.debian.tar.xz
 0d438743e695b831386964add28d3c1945aad947 364908 libnet-dns-perl_1.05-2_all.deb
Checksums-Sha256:
 9c16d066a3f17e3042b0f045909544f3d732405ff51cc3b7883bbb5049e67aa4 2116 
libnet-dns-perl_1.05-2.dsc
 7cb74663f19aed8d7e55c4e3008b1ca4926eb38ac7ede4ed012209f527cadf70 6180 
libnet-dns-perl_1.05-2.debian.tar.xz
 964bacf8e38ad69fbc35f1c331fecb6a6c55754bd0578718ac4c849bc82bd47c 364908 
libnet-dns-perl_1.05-2_all.deb
Files:
 7ca2e5731d7a80d95c52bf3f43fb2edc 2116 perl optional libnet-dns-perl_1.05-2.dsc
 ec36c4a1a44521c48c1299636e733baa 6180 perl optional 
libnet-dns-perl_1.05-2.debian.tar.xz
 51e8dd3bed09b65c5c1378fa3b4fb74c 364908 perl optional 
libnet-dns-perl_1.05-2_all.deb

-BEGIN PGP SIGNATURE-

Processed: reassign 821942 to libnet-dns-perl,libnet-dns-sec-perl, forcibly merging 820332 821942

[Debian Bug Tracking System]

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

> reassign 821942 libnet-dns-perl,libnet-dns-sec-perl
Bug #821942 [libnet-dns-sec-perl] libnet-dns-sec-perl: Errors were encountered 
while processing: libnet-dns-sec-perl
Bug reassigned from package 'libnet-dns-sec-perl' to 
'libnet-dns-perl,libnet-dns-sec-perl'.
No longer marked as found in versions libnet-dns-sec-perl/0.21-1.
Ignoring request to alter fixed versions of bug #821942 to the same values 
previously set
> forcemerge 820332 821942
Bug #820332 [libnet-dns-perl,libnet-dns-sec-perl] libnet-dns-perl: Conflict 
with libnet-dns-sec-perl but not in Conflicts
Bug #821942 [libnet-dns-perl,libnet-dns-sec-perl] libnet-dns-sec-perl: Errors 
were encountered while processing: libnet-dns-sec-perl
Severity set to 'serious' from 'important'
Marked as found in versions libnet-dns-sec-perl/0.21-1 and 
libnet-dns-perl/1.05-1.
Added tag(s) pending, confirmed, stretch, and sid.
Merged 820332 821942
> thanks
Stopping processing here.

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

Bug#822201: ca-certificates-java: postinst and trigger should fail if no known jvm is found

[Andreas Beckmann]

Package: ca-certificates-java
Version: 20160321
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

the setup_path routine in ca-certificates-java.postinst does not take
into account that it might not find a known jre.
In that case $jvm and $JAVA_HOME will be invalid.
This usually happens if a new package starts providing java7-runtime-headless.

I simulated this in a minimal chroot by creating a java7-runtime-headless
package with equivs and installing it (but installing no other jre).
Thereafter installing ca-certificates-java results in:


# apt-get install ca-certificates-java
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libnspr4 libnss3
The following NEW packages will be installed:
  ca-certificates-java libnspr4 libnss3
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1286 kB of archives.
After this operation, 4204 kB of additional disk space will be used.
Do you want to continue? [Y/n]
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76, <> line 3.)
debconf: falling back to frontend: Readline
Selecting previously unselected package libnspr4:amd64.
(Reading database ... 16913 files and directories currently installed.)
Preparing to unpack .../libnspr4_2%3a4.12-2_amd64.deb ...
Unpacking libnspr4:amd64 (2:4.12-2) ...
Selecting previously unselected package libnss3:amd64.
Preparing to unpack .../libnss3_2%3a3.23-2_amd64.deb ...
Unpacking libnss3:amd64 (2:3.23-2) ...
Selecting previously unselected package ca-certificates-java.
Preparing to unpack .../ca-certificates-java_20160321_all.deb ...
Unpacking ca-certificates-java (20160321) ...
Processing triggers for libc-bin (2.22-6) ...
Processing triggers for ca-certificates (20160104) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Setting up libnspr4:amd64 (2:4.12-2) ...
Setting up libnss3:amd64 (2:3.23-2) ...
Setting up ca-certificates-java (20160321) ...
/var/lib/dpkg/info/ca-certificates-java.postinst: line 57: java: command not 
found
/var/lib/dpkg/info/ca-certificates-java.postinst: line 70: java: command not 
found
done.
Processing triggers for libc-bin (2.22-6) ...
Processing triggers for ca-certificates (20160104) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

/etc/ca-certificates/update.d/jks-keystore: 86: 
/etc/ca-certificates/update.d/jks-keystore: java: not found
E: /etc/ca-certificates/update.d/jks-keystore exited with code 1.
done.
# echo $?
0


Postinst and trigger spew a lot of errors, no java keystore has been
created/updated, but apt-get finished successfully.
I assume that ca-certificates-java is *not correctly installed* in
this situation and will cause failures in packages that Depend on it
and actually do use it. Thus the Severity: serious.

I noticed this problem in a piuparts log where ca-certificates-java (20140324)
was installed along openjdk-8-jre-headless:amd64 (8u72-b15-2), producing the 
same
'java: command not found' errors. The piuparts test finished successfully, that
logfile is attached.
equivs was just an easy way to reproduce it with current ca-certificates-java.

Current ca-certificates-java knows about openjdk-{7,8,9} and the oracle
equivalents, but there will probably be a -10 in the future (or some
vendor might provide yet another implementation of java7-runtime-headless
in yet another path ... /usr/lib/jvm/vendor-java-42-yet-another-jre).


Andreas


libeasymock-java_3.3.1+ds-3.log.gz
Description: application/gzip

Processed: Pending fixes for bugs in the libnet-dns-perl package

[Debian Bug Tracking System]

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

> tag 820332 + pending
Bug #820332 [libnet-dns-perl,libnet-dns-sec-perl] libnet-dns-perl: Conflict 
with libnet-dns-sec-perl but not in Conflicts
Ignoring request to alter tags of bug #820332 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#820332: Pending fixes for bugs in the libnet-dns-perl package

[pkg-perl-maintainers]

tag 820332 + pending
thanks

Some bugs in the libnet-dns-perl package are closed in revision
e99ccedccbc29784b9fdd4096c039373cb5c4dbd in branch 'master' by Axel
Beckert

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-dns-perl.git/commit/?id=e99cced

Commit message:

Update versioned Breaks/Replaces on libnet-dns-sec-perl << 1.01

Closes: #820332

Processed: tagging 820332

[Debian Bug Tracking System]

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

> tags 820332 + pending
Bug #820332 [libnet-dns-perl,libnet-dns-sec-perl] libnet-dns-perl: Conflict 
with libnet-dns-sec-perl but not in Conflicts
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822194: libdebug: FTBFS: No rule to make target 'libdebug.so.0', needed by 'with-depends'

[Jakub Wilk]

Source: libdebug
Version: 0.5.1-1
Severity: serious
Justification: fails to build from source

libdebug FTBFS when built in parallel:
| make with-depends
| make[3]: Entering directory '/«PKGBUILDDIR»/src'
| gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security  -pipe 
-Wall -W -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts 
-Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -Wall 
-Wno-trigraphs -pipe -fno-strict-aliasing -fno-common -Wall -Wno-trigraphs 
-pipe -fno-strict-aliasing -fno-common -fPIC -Wall -Wno-trigraphs -pipe 
-fno-strict-aliasing -fno-common -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -I./include -DGETHOSTBYNAME -DGETSERVBYNAME 
-I/usr/local/include -I../include -DGETHOSTBYNAME -DGETSERVBYNAME 
-I/usr/local/include -I../include -DGETHOSTBYNAME -DGETSERVBYNAME  -c -o log.o 
log.c
| gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security  -pipe 
-Wall -W -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts 
-Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -Wall 
-Wno-trigraphs -pipe -fno-strict-aliasing -fno-common -Wall -Wno-trigraphs 
-pipe -fno-strict-aliasing -fno-common -fPIC -Wall -Wno-trigraphs -pipe 
-fno-strict-aliasing -fno-common -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -I./include -DGETHOSTBYNAME -DGETSERVBYNAME 
-I/usr/local/include -I../include -DGETHOSTBYNAME -DGETSERVBYNAME 
-I/usr/local/include -I../include -DGETHOSTBYNAME -DGETSERVBYNAME  -c -o 
memory.o memory.c
| gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security  -pipe 
-Wall -W -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts 
-Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -Wall 
-Wno-trigraphs -pipe -fno-strict-aliasing -fno-common -Wall -Wno-trigraphs 
-pipe -fno-strict-aliasing -fno-common -fPIC -Wall -Wno-trigraphs -pipe 
-fno-strict-aliasing -fno-common -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -I./include -DGETHOSTBYNAME -DGETSERVBYNAME 
-I/usr/local/include -I../include -DGETHOSTBYNAME -DGETSERVBYNAME 
-I/usr/local/include -I../include -DGETHOSTBYNAME -DGETSERVBYNAME  -c -o hex.o 
hex.c
| make[3]: *** No rule to make target 'libdebug.so.0', needed by 
'with-depends'.  Stop.
| make[3]: *** Waiting for unfinished jobs
| make[3]: Leaving directory '/«PKGBUILDDIR»/src'
| ../rules.mk:65: recipe for target 'without-depends' failed
| make[2]: *** [without-depends] Error 2
| make[2]: Leaving directory '/«PKGBUILDDIR»/src'
| rules.mk:48: recipe for target 'all' failed
| make[1]: *** [all] Error 2
| make[1]: Leaving directory '/«PKGBUILDDIR»'
| dh_auto_build: make -j8 returned exit code 2
| debian/rules:34: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Full build log:
https://buildd.debian.org/status/fetch.php?pkg=libdebug=amd64=0.5.1-1=1461276685

--
Jakub Wilk

Processed: Re: eagle: cannot be rebuilt against libssl1.0.2

[Debian Bug Tracking System]

Processing control commands:

> found -1 7.5.0-1
Bug #804531 {Done: Scott Howard } [eagle] eagle: cannot be 
rebuilt against libssl1.0.2
Marked as found in versions eagle/7.5.0-1; no longer marked as fixed in 
versions eagle/7.5.0-1 and reopened.

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

Bug#804531: eagle: cannot be rebuilt against libssl1.0.2

[Andreas Beckmann]

Followup-For: Bug #804531
Control: found -1 7.5.0-1

eagle still (Build-)Depends: libssl1.0.0 and the binary is still
linked against libssl.so.1.0.0

Since the only API/ABI difference between libssl1.0.0 and libssl1.0.2 is
the removal of some symbols, you could try the following:

* switch build-depends to libssl1.0.2
* build-depend on rpl
* edit the eagle binary to reference the .1.0.2 libraries instead:
rpl 'libcrypto.so.1.0.0' 'libcrypto.so.1.0.2' eagle
rpl 'libssl.so.1.0.0' 'libssl.so.1.0.2' eagle
  this should work unless eagle uses some of the removed symbols (which
  is unlikely)


Andreas

Processed: Re: Bug#783876: Seriously, these binaries should be stripped by default

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #783876 [gcc-5] gcc-5: consider stripping lto1 / cc1 / cc1plus
Severity set to 'important' from 'serious'

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

Bug#783876: Seriously, these binaries should be stripped by default

[Matthias Klose]

Control: severity -1 important

On 21.04.2016 19:28, Steve McIntyre wrote:

Control: severity -1 serious
Justification: wasting many megabytes of space and download


sorry, I don't see this as a justification.


We're shipping broken toolchain packages


please stop trolling. Nothing is broken.

No, we don't ship these, as clearly stated in this report. They are in the 
archive as unstripped versions.  Other software stacks as the Go stack ship 
unstripped binaries as well, because they need these.



that are intentionally too
large, and this is causing issues elsewhere. The "netinst" CD image
that we advertise to people as the default Debian image to use for
most installations is now huge. The multi-arch netinst no longer even
fits on a single CD due to this waste of space.


So why does the netinst image need a compiler?


There's not been any visible progress on this bug in since last
year. If upstream want to ship uncompressed binaries for diagnostics
and can't cope with separate debug symbols, maybe ship separate
alternative unstripped toolchain packages and point to those if people
want them?


The unstripped binaries should be installed by default on porter boxes and 
buildds.  Yes, this is a trade-off between (largely my) developer time, the 
ability for Debian developers to produce complete bug reports, and an increase 
on machine/bandwidth resources.  If I have the choice to select between human 
and other resources, I'll try to keep the time I have to spend on reproducing 
things rather small.


> There's not been any visible progress on this bug in since last
> year.

So you step in here like a bull in a china shop, raising the severity without 
doing anything else?  You are working for a Linux and open source aware 
organization, have you tried to get developer time to address issues like these? 
 Have you sent a patch proposal to implement such a change either upstream or 
on the packaging side?


Not that amused, Matthias

Bug#822182: dvbtune: FTBFS: error: unknown type name 'uint16_t'

[Martin Michlmayr]

Package: dvbtune
Version: 0.5.ds-1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> gcc -Wall -I /usr/include/libxml2 -I ../DVB/include -DVERSION=\"0.5\" 
> -DNEWSTRUCTdvbtune.c tune.o   -o dvbtune
> In file included from tune.h:25:0,
>  from dvbtune.c:81:
> dvb_defaults.h:83:2: warning: #warning No DVB-T country defined in 
> dvb_defaults.h [-Wcpp]
>  #warning No DVB-T country defined in dvb_defaults.h
>   ^
> dvb_defaults.h:84:2: warning: #warning defaulting to UK [-Wcpp]
>  #warning defaulting to UK
>   ^
> dvb_defaults.h:85:2: warning: #warning Ignore this if using Satellite or 
> Cable [-Wcpp]
>  #warning Ignore this if using Satellite or Cable
>   ^
> dvbtune.c:411:27: error: unknown type name 'uint16_t'
>  void set_ts_filter(int fd,uint16_t pid)
>^
> dvbtune.c: In function 'scan_nit':
> dvbtune.c:716:16: warning: variable 'network_id' set but not used 
> [-Wunused-but-set-variable]
>int info_len,network_id;
> ^
> dvbtune.c: At top level:
> dvbtune.c:1024:23: error: unknown type name 'uint32_t'
>  int FEReadBER(int fd, uint32_t *ber)
>^
> dvbtune.c:1072:37: error: unknown type name 'uint32_t'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#783876: Seriously, these binaries should be stripped by default

[Matthias Klose]

On 21.04.2016 20:08, Ondřej Surý wrote:

From reading the bug comments I can see both sides of the argument, so

why we don't ship just two versions that would be exchangeable - one
with symbols and one (default) stripped?

The stripped one would be installed by default and if you need to
produce trace, you would install the second variant. GCC plugins also
could depend on unstripped variant of the package. That would provide
both parties what they need.


so how do the unstripped ones get installed by default on porter boxes? How are 
the unstripped ones installed on the buildds by default?


Matthias

Bug#822178: cargo: FTBFS: error: Cannot declare a non-inline module inside a block unless it has a path attribute

[Martin Michlmayr]

Package: cargo
Version: 0.8.0-2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> /libgit2-0_3_3.rlib --extern toml=/<>/deps/libtoml-0_1_25.rlib 
> --extern curl=/<>/deps/libcurl-0_2_14.rlib --extern 
> log=/<>/deps/liblog-0_3_4.rlib --extern 
> num_cpus=/<>/deps/libnum_cpus-0_2_10.rlib --extern 
> url=/<>/deps/liburl-0_2_38.rlib --extern 
> crates_io=/<>/deps/libcrates_io-0_1_0.rlib --extern 
> docopt=/<>/deps/libdocopt-0_6_78.rlib --extern 
> libgit2_sys=/<>/deps/liblibgit2_sys-0_3_8.rlib --extern 
> rustc_serialize=/<>/deps/librustc_serialize-0_3_16.rlib --extern 
> time=/<>/deps/libtime-0_1_34.rlib --extern 
> crossbeam=/<>/deps/libcrossbeam-0_1_6.rlib --extern 
> tar=/<>/deps/libtar-0_3_2.rlib --extern 
> semver=/<>/deps/libsemver-0_2_0.rlib --extern 
> flate2=/<>/deps/libflate2-0_2_11.rlib --extern 
> filetime=/<>/deps/libfiletime-0_1_8.rlib --extern 
> glob=/<>/deps/libglob-0_2_10.rlib --extern 
> regex=/<>/deps/libregex-0_1_44.rlib --extern 
> term=/<>/deps/libterm-0_2_14.rlib --extern 
> git2_curl=/<>/deps/libgit2_curl-0_3_0.rlib
> cargo: /<>/src/bin/cargo.rs:64:15: 64:20 error: Cannot declare a 
> non-inline module inside a block unless it has a path attribute
> cargo: /<>/src/bin/cargo.rs:64 $mac!(bench);
> cargo:   ^
> cargo: /<>/src/bin/cargo.rs:64:15: 64:20 note: Maybe `use` the 
> module `bench` instead of redeclaring it
> cargo: /<>/src/bin/cargo.rs:64 $mac!(bench);
> cargo:   ^
> cargo: /<>/src/bin/cargo.rs:65:15: 65:20 error: Cannot declare a 
> non-inline module inside a block unless it has a path attribute
> cargo: /<>/src/bin/cargo.rs:65 $mac!(build);
> cargo:   ^
> cargo: /<>/src/bin/cargo.rs:65:15: 65:20 note: Maybe `use` the 
> module `build` instead of redeclaring it
> cargo: /<>/src/bin/cargo.rs:65 $mac!(build);
> cargo:   ^
> cargo: /<>/src/bin/cargo.rs:66:15: 66:20 error: Cannot declare a 
> non-inline module inside a block unless it has a path attribute
> cargo: /<>/src/bin/cargo.rs:66 $mac!(clean);
> cargo:   ^
> cargo: /<>/src/bin/cargo.rs:66:15: 66:20 note: Maybe `use` the 
> module `clean` instead of redeclaring it
> cargo: /<>/src/bin/cargo.rs:66 $mac!(clean);
> cargo:   ^
> cargo: /<>/src/bin/cargo.rs:67:15: 67:18 error: Cannot declare a 
> non-inline module inside a block unless it has a path attribute
> cargo: /<>/src/bin/cargo.rs:67 $mac!(doc);
> cargo:   ^~~
> cargo: /<>/src/bin/cargo.rs:67:15: 67:18 note: Maybe `use` the 
> module `doc` instead of redeclaring it
> cargo: /<>/src/bin/cargo.rs:67 $mac!(doc);
> cargo:   ^~~
> cargo: /<>/src/bin/cargo.rs:68:15: 68:20 error: Cannot declare a 
> non-inline module inside a block unless it has a path attribute
> cargo: /<>/src/bin/cargo.rs:68 $mac!(fetch);
> cargo:   ^
> cargo: /<>/src/bin/cargo.rs:68:15: 68:20 note: Maybe `use` the 
> module `fetch` instead of redeclaring it
> cargo: /<>/src/bin/cargo.rs:68 $mac!(fetch);
> cargo:   ^
> cargo: /<>/src/bin/cargo.rs:69:15: 69:32 error: Cannot declare a 
> non-inline module inside a block unless it has a path attribute
> cargo: /<>/src/bin/cargo.rs:69 $mac!(generate_lockfile);
> cargo:   
> ^
> cargo: /<>/src/bin/cargo.rs:69:15: 69:32 note: Maybe `use` the 
> module `generate_lockfile` instead of redeclaring it
> cargo: /<>/src/bin/cargo.rs:69 $mac!(generate_lockfile);
> cargo:   
> ^
> cargo: /<>/src/bin/cargo.rs:70:15: 70:27 error: Cannot declare a 
> non-inline module inside a block unless it has a path attribute
> cargo: /<>/src/bin/cargo.rs:70 $mac!(git_checkout);
> cargo:   
> ^~~~
> cargo: /<>/src/bin/cargo.rs:70:15: 70:27 note: Maybe `use` the 
> module `git_checkout` instead of redeclaring it
> cargo: /<>/src/bin/cargo.rs:70 $mac!(git_checkout);
> cargo:   
> ^~~~
> cargo: /<>/src/bin/cargo.rs:71:15: 71:19 error: Cannot declare a 
> non-inline module inside a block unless it has a path attribute
> cargo: 

Processed: same issue, merge

[Debian Bug Tracking System]

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

> reassign 818331 src:aac-tactics
Bug #818331 [aac-tactics] aac-tactics: FTBFS: constructor vcons (in type vT) 
expects 2 arguments
Bug reassigned from package 'aac-tactics' to 'src:aac-tactics'.
No longer marked as found in versions 0.4-5.
Ignoring request to alter fixed versions of bug #818331 to the same values 
previously set
> forcemerge 813459 818331
Bug #813459 [src:aac-tactics] aac-tactics: FTBFS: Error: The constructor vcons 
(in type vT) expects 2 arguments.
Bug #818331 [src:aac-tactics] aac-tactics: FTBFS: constructor vcons (in type 
vT) expects 2 arguments
Marked as found in versions aac-tactics/0.4-5.
Merged 813459 818331
> --
Stopping processing here.

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

Processed (with 1 error): same issue, merge

[Debian Bug Tracking System]

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

> forcemerge 813459 818331
Bug #813459 [src:aac-tactics] aac-tactics: FTBFS: Error: The constructor vcons 
(in type vT) expects 2 arguments.
Unable to merge bugs because:
package of #818331 is 'aac-tactics' not 'src:aac-tactics'
Failed to forcibly merge 813459: Did not alter merged bugs.

> --
Stopping processing here.

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

Bug#821233: perlbal: FTBFS: Unable to start socket: Address already in use

[Niko Tyni]

Control: reopen -1
Control: severity -1 important

On Sun, Apr 17, 2016 at 12:41:15AM +0200, gregor herrmann wrote:
> Control: tag -1 + unreproducible
> 
> On Sat, 16 Apr 2016 23:23:50 +0100, Chris Lamb wrote:
> 
> > perlbal fails to build from source in unstable/amd64:
> 
> >   Didn't get 200 OK: GET /reqdecr,status HTTP/1.0
> >   Unable to start socket: Address already in use
> >   # Looks like your test exited with 29 before it could output anything.
> >   t/32-selector.t .. 
> >   1..38
> >   Dubious, test returned 29 (wstat 7424, 0x1d00)
> >   Failed 38/38 subtests 
> 
> The tests pass for me, both during build and in autopkgtest.

It has just failed on ci.debian.net in the same way for the first time
in a year or so.

I can (eventually) reproduce it locally by running t/32-selector.t in
a loop.  Caught it with strace, and it looks like

- the main process checks that the local port (in my case 60070) is free
  in Perlbal::Test::test_port() by making a new socket there and closing
  it immediately
- later, in Perlbal::Test::WebServer::start_webserver() a server child
  process is forked off and then the main process
  tries to connect it. It gets a connection on something which doesn't
  respond properly but rather echoes the request back
- in parallel but a bit later, the child process starts a server but gets
  EADDRINUSE from bind(2).

I'm not aware of having any other process running that's greedy for
local ports, and it seems really improbable that something would hit
by chance in the window between the first check and the actual use.

I wonder if the kernel is just slow to actually release the port after
the first check. But surely at least the connect(2) call should have
failed when the port was already closed. And why does the peer look
like an echo service?

I'm reopening but downgrading this. Perhaps we should just have
start_webserver() retry a couple of times somehow if it fails the
first time.
-- 
Niko Tyni   nt...@debian.org

Processed: Re: Bug#821233: perlbal: FTBFS: Unable to start socket: Address already in use

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #821233 {Done: Chris Lamb } [src:perlbal] perlbal: FTBFS: 
Unable to start socket: Address already in use
Bug reopened
Ignoring request to alter fixed versions of bug #821233 to the same values 
previously set
> severity -1 important
Bug #821233 [src:perlbal] perlbal: FTBFS: Unable to start socket: Address 
already in use
Severity set to 'important' from 'serious'

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

Bug#820845: marked as done (openstack-dashboard-apache: modifies conffiles (policy 10.7.3): /etc/apache2/sites-available/openstack-dashboard{, -ssl}.conf)

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 19:34:54 +
with message-id 
and subject line Bug#820845: fixed in horizon 2:9.0.0-2
has caused the Debian Bug report #820845,
regarding openstack-dashboard-apache: modifies conffiles (policy 10.7.3): 
/etc/apache2/sites-available/openstack-dashboard{, -ssl}.conf
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.)


-- 
820845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-dashboard-apache
Version: 2:9.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

3m22.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  /etc/apache2/sites-available/openstack-dashboard.conf
  /etc/apache2/sites-available/openstack-dashboard-ssl.conf


cheers,

Andreas


openstack-dashboard-apache_2:9.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: horizon
Source-Version: 2:9.0.0-2

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

Debian distribution maintenance software
pp.
Ivan Udovichenko  (supplier of updated horizon 
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, 13 Apr 2016 23:34:27 +0300
Source: horizon
Binary: python-django-horizon openstack-dashboard openstack-dashboard-apache 
horizon-doc
Architecture: source all
Version: 2:9.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Ivan Udovichenko 
Changed-By: Ivan Udovichenko 
Description:
 horizon-doc - web application to control an OpenStack cloud - doc
 openstack-dashboard - web application to control an OpenStack cloud
 openstack-dashboard-apache - web application to control an OpenStack cloud - 
Apache support
 python-django-horizon - Django module providing web interaction with OpenStack
Closes: 820845 821868
Changes:
 horizon (2:9.0.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Standards-Version is 3.9.8 now (no change)
 .
   [ Ivan Udovichenko ]
   * d/openstack-dashboard-apache.postinst: Revert changes. (Closes: #820845)
 - Do not modify provided Apache configuration files.
 - Enable site provided by openstack-dashboard-alias-only.conf .
   * d/openstack-dashboard.triggers: Trigger package configuration
 only once. (Closes: #821868)
   * d/control: Fix documentation build by adding git to build-dependencies.
   * Add myself to Uploaders 

Bug#821868: marked as done (openstack-dashboard: causes trigger loop)

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 19:34:54 +
with message-id 
and subject line Bug#821868: fixed in horizon 2:9.0.0-2
has caused the Debian Bug report #821868,
regarding openstack-dashboard: causes trigger loop
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.)


-- 
821868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-dashboard
Version: 2:9.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package causes a trigger loop.
This was observed during a testing -> sid upgrade test (where
openstack-dashboard had the same versions in testing and sid, and the
installation in testing went without problems).

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

  Processing triggers for libc-bin (2.22-6) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
openstack-dashboard -> openstack-dashboard
   packages' pending triggers which are or may be unresolvable:
openstack-dashboard: /usr/share/javascript/jquery: 
/usr/share/javascript/angular.js
  dpkg: error processing package openstack-dashboard (--configure):
   triggers looping, abandoned
  Errors were encountered while processing:
   openstack-dashboard


cheers,

Andreas


openstack-dashboard_2:9.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: horizon
Source-Version: 2:9.0.0-2

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

Debian distribution maintenance software
pp.
Ivan Udovichenko  (supplier of updated horizon 
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, 13 Apr 2016 23:34:27 +0300
Source: horizon
Binary: python-django-horizon openstack-dashboard openstack-dashboard-apache 
horizon-doc
Architecture: source all
Version: 2:9.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Ivan Udovichenko 
Changed-By: Ivan Udovichenko 
Description:
 horizon-doc - web application to control an OpenStack cloud - doc
 openstack-dashboard - web application to control an OpenStack cloud
 openstack-dashboard-apache - web application to control an OpenStack cloud - 
Apache support
 python-django-horizon - Django module providing web interaction with OpenStack
Closes: 820845 821868
Changes:
 horizon (2:9.0.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Standards-Version is 3.9.8 now (no change)
 .
   [ Ivan Udovichenko ]
   * d/openstack-dashboard-apache.postinst: Revert changes. (Closes: #820845)
 - Do not modify provided Apache configuration files.
 - Enable site provided by openstack-dashboard-alias-only.conf .
   * d/openstack-dashboard.triggers: Trigger package configuration
 only once. (Closes: #821868)
   * d/control: Fix documentation build by adding git to build-dependencies.
   * Add myself to Uploaders field.
   * Uploading to unstable.
Checksums-Sha1:
 a81627c6cb53c6ac518481276624d15e9b45c2d8 4149 horizon_9.0.0-2.dsc
 82da7f0453cbd1b90333d076771087154b49ed10 24500 horizon_9.0.0-2.debian.tar.xz
 be58d661cad9b43c3ed89d56009ab05187ddf386 1168458 horizon-doc_9.0.0-2_all.deb
 ea155dd6f9057cbc4053222510bea3e98092d8ee 12932 
openstack-dashboard-apache_9.0.0-2_all.deb
 716775360e4193a278ed748ed818652d6c382c49 2567428 
openstack-dashboard_9.0.0-2_all.deb
 deea3f0033374be76a7cc88f4aca84c7f494d8f3 2119186 
python-django-horizon_9.0.0-2_all.deb
Checksums-Sha256:
 69b6fdfe007324b6fdb8c1909a2edc37a5d0a96db43cf97cfc18765a8c2798f4 4149 
horizon_9.0.0-2.dsc
 f467a75869dc2cf6d859f258ac79831f3821d060de3b4c848e2147160716498f 24500 
horizon_9.0.0-2.debian.tar.xz
 57148f3bb2676899024471ab0c1f1a66ae3cbbd9b8a6c34da63974b7103093fd 1168458 
horizon-doc_9.0.0-2_all.deb
 341885023b30f2d2f40a0657dda522f25ee3fe5649cc331afa27a43c870b5636 12932 

Processed: untag #754838

[Debian Bug Tracking System]

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

> tags 754838 - pending
Bug #754838 [grr.app] grr.app: Cannot add new feeds
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

[Muammar El Khatib]

On Thu, Apr 21, 2016 at 9:13 PM, Tobias Frost  wrote:
> Thanks Muammar,
>

:)

> I have filed the RM.
>
> Kudos for maintaining smc..

Thanks for having filled the RM.

Have a nice day.

-- 
Muammar El Khatib.
Linux user: 403107.
GPG Key = 71246E4A.
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

[Tobias Frost]

Thanks Muammar,

I have filed the RM.

Kudos for maintaining smc..

-- 
tobi

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

[Muammar El Khatib]

Hi Tobias,

On Thu, Apr 21, 2016 at 7:58 AM, Tobias Frost  wrote:
> Sorry, I overread the "Yes."...

Don't worry.

> As the rest of it confuses me: Does that mean you are OK with filing an
> RM at this point of time?

Yes, I am ok with filling an RM for SMC. Upstream is not developing, I
don't have the time to do such an effort either.

> (We can also file a RM for the binaries alone, but there is no
> guarantee that the source will be retained; an ftp-master might think
> it is cruft and delete it)
>
> Let me know! (libpng1.2 removal, you know...)

Yes, let's proceed to request the RM.


Cheers,

-- 
Muammar El Khatib.
Linux user: 403107.
GPG Key = 71246E4A.
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Bug#819782: marked as done (libdatabase-dump-perl: FTBFS: t/dumptruck.t failure)

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 21:47:38 +0300
with message-id <20160421184738.GA11716@estella.local.invalid>
and subject line Re: Bug#819782: libdatabase-dump-perl: FTBFS: t/dumptruck.t 
failure
has caused the Debian Bug report #819782,
regarding libdatabase-dump-perl: FTBFS: t/dumptruck.t 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.)


-- 
819782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdatabase-dumptruck-perl
Version: 1.2-2
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest
X-Debbugs-Cc: sqli...@packages.debian.org

As noticed by the ci.debian.net test setup, this package
currently fails its test suite, making it fail to build.

 https://ci.debian.net/packages/libd/libdatabase-dumptruck-perl/unstable/amd64/

  #   Failed test 'Array variable retrieved'
  #   at t/dumptruck.t line 133.
  # Structures begin differing at:
  #  $got = '[666]'
  # $expected = ARRAY(0x29fbef8)
  # Looks like you failed 1 test of 43.
  
  [...]
  Test Summary Report
  ---
  t/dumptruck.t (Wstat: 256 Tests: 43 Failed: 1)
Failed test:  34
Non-zero exit status: 1
 
This was broken by the recent sqlite3_3.12.0-1 upgrade in unstable.
The libdbd-sqlite3-perl test suite is still passing, though. 

I don't see anything clearly fitting in the SQLite 3.12 release notes at
 http://sqlite.org/releaselog/3_12_0.html
so maybe it's a regression?

Needs further investigation, but cc'ing the sqlite3 maintainer as a heads-up.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
On Wed, Apr 20, 2016 at 07:37:41PM +0200, László Böszörményi wrote:
> On Sun, Apr 10, 2016 at 2:14 PM, gregor herrmann  wrote:
> > On Sat, 02 Apr 2016 12:02:51 +0300, Niko Tyni wrote:
> >> As noticed by the ci.debian.net test setup, this package
> >> currently fails its test suite, making it fail to build.
> >>
> >>  
> >> https://ci.debian.net/packages/libd/libdatabase-dumptruck-perl/unstable/amd64/
> [...]
> >> This was broken by the recent sqlite3_3.12.0-1 upgrade in unstable.
> >> The libdbd-sqlite3-perl test suite is still passing, though.
> >>
> >> I don't see anything clearly fitting in the SQLite 3.12 release notes at
> >>  http://sqlite.org/releaselog/3_12_0.html
> >> so maybe it's a regression?
> >>
> >> Needs further investigation, but cc'ing the sqlite3 maintainer as a 
> >> heads-up.
> >
> > Still the same failure with today's upload of sqlite3 3.12.1-1.
>  Please retest with the just uploaded sqlite3 3.12.2-1 package
> version. Works now on my box, but waiting for your confirmation.

Looks good indeed. Presumably this was fixed by
 http://www.sqlite.org/src/info/ab9d279f40f81e5a

Thank you for your help. I'm closing this.
-- 
Niko Tyni   nt...@debian.org--- End Message ---

Bug#822118: RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages

[Corentin Desfarges]

Hi

As I said to Andreas a few weeks ago, the FW4SPL team is currently
working on a new version of the framework using VTK6, ITK4, and the
new Boost version.
We should be able to remove the dependences to the old versions of
these packages over the next week.

About libpng, I'm not sure to understand. FW4SPL depends on
libpng-dev, and if I refers to the sid packages list, libpng-dev is
related to libpng1.6, not libpng1.2.

Best regards,

Corentin


On Thu, 21 Apr 2016 14:39:26 +0200 Tobias Frost  wrote:
> Package: fw4spl
> Severity: serious
> Justification: blocks-transitions
>
> Dear maintainer / ftp-masters,
>
> fw4spl is RC buggy with 5 bugs:
>  #797475 fw4spl: does not support parallel build
>  #797481 fw4spl: FTBFS - Doesn't support boost 1.58
>  #809935 fw4spl: FTBFS with libpng16
>  #820632 fw4spl: depends on vtk 5
>  #821957 fw4spl: Depends on insighttoolkit, which is about to be removed. 
> Please port to insighttoolkit4
>
> With the first two filed August 2015; both of them did not receive any 
> response from the maintainer, though
> extra triggered again by Andreas in December.
>
> (The other two bugs do not ahve a response too, but they are only a few days 
> old)
>
> The package blocks the boost, libpng and vtk transitions.
>
> As it is now blocking other packages, I raise the question if it should be
> removed from Debian.
>
> Please response to this bug, if there is no response within a week, I will
> reassign this bug to ftp.debian.org.
>
> Please note, that if decide to keep it, you need to fix your pacakge ASAP.
> The removal of libpng1.2 will NOT wait for root-system, and when removed,
> at least the binary packages must go with it. (Which can lead to src removal)
>
> Thanks for your understanding,
>
> --
> tobi
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
>

Bug#783876: Seriously, these binaries should be stripped by default

[Ondřej Surý]

>From reading the bug comments I can see both sides of the argument, so
why we don't ship just two versions that would be exchangeable - one
with symbols and one (default) stripped?

The stripped one would be installed by default and if you need to
produce trace, you would install the second variant. GCC plugins also
could depend on unstripped variant of the package. That would provide
both parties what they need.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

Bug#821894: marked as done (cluster-glue: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 17:49:05 +
with message-id 
and subject line Bug#821894: fixed in cluster-glue 1.0.12-5
has caused the Debian Bug report #821894,
regarding cluster-glue: copyright file missing after upgrade (policy 12.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.)


-- 
821894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cluster-glue
Version: 1.0.12-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This seems to affect all (most?) lib*X and lib*-dev packages built from
src:cluster-glue.

This was observed on the following upgrade paths:

  jessie -> stretch

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

1m55.3s ERROR: WARN: Inadequate results from running adequate!
  libpils2: missing-copyright-file /usr/share/doc/libpils2/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libpils2/copyright
  # ls -lad /usr/share/doc/libpils2
  drwxr-xr-x 2 root root 40 Apr 14 14:20 /usr/share/doc/libpils2
  # ls -la /usr/share/doc/libpils2/
  total 0
  drwxr-xr-x   2 root root   40 Apr 14 14:20 .
  drwxr-xr-x 155 root root 3340 Apr 14 14:20 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

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

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


cheers,

Andreas


libpils2_1.0.12-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cluster-glue
Source-Version: 1.0.12-5

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated cluster-glue package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 21 Apr 2016 19:24:54 +0200
Source: cluster-glue
Binary: cluster-glue cluster-glue-dbg cluster-glue-dev liblrm2 libpils2 
libplumb2 libplumbgpl2 libstonith1 liblrm2-dev libpils2-dev libplumb2-dev 
libplumbgpl2-dev libstonith1-dev
Architecture: source
Version: 1.0.12-5
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Christoph Berg 
Description:
 cluster-glue - Reusable cluster components for Linux HA
 cluster-glue-dbg - Reusable cluster libraries debugging symbols
 cluster-glue-dev - Development files for the cluster glue components
 liblrm2- Reusable cluster libraries -- liblrm2
 liblrm2-dev - Reusable cluster development files -- liblrm
 libpils2   - Reusable cluster libraries -- libpils2
 libpils2-dev - Reusable cluster development files -- libpils2
 libplumb2  - Reusable cluster libraries -- libplumb2
 libplumb2-dev - Reusable cluster development files -- libplumb2
 libplumbgpl2 - Reusable cluster libraries -- libplumbgpl2
 libplumbgpl2-dev - Reusable cluster development files -- libplumbgpl2
 libstonith1 - Reusable cluster libraries -- libstonith1
 libstonith1-dev - Reusable cluster development files -- libstonith1
Closes: 821129 821894
Changes:
 cluster-glue (1.0.12-5) unstable; urgency=medium
 .
   * Drop --link-doc=cluster-glue, it's a nice idea but causes too much
 trouble.  Closes: #821129, #821894.

Bug#821154: chromium: crashes on video

[Sebastian Ramacher]

Control: tags -1 + patch

On 2016-04-20 21:49:23, Gedalya wrote:
> On 04/20/2016 08:13 PM, Gedalya wrote:
> > Going to try this patch now.
> 
> Built with pbuilder against sid. /usr/lib/chromium/chromium is now ~2MB 
> smaller.
> New packages pulled in from sid: libavcodec57 libavformat57 libavutil55 
> libswresample2 - version 7:3.0.1-3
> ldd does show it's actually using them.
> Video sites work fine.
> Will report if anything interesting happens.

Thanks for testing. Tagging accordingly.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#821154: chromium: crashes on video

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #821154 [chromium] chromium: crashes on video
Added tag(s) patch.

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

Processed: Seriously, these binaries should be stripped by default

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #783876 [gcc-5] gcc-5: consider stripping lto1 / cc1 / cc1plus
Severity set to 'serious' from 'wishlist'

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

Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Wed, Apr 20, 2016 at 08:20:56AM +0200, Salvatore Bonaccorso wrote:
> Hi Lars,
> 
> On Tue, Apr 19, 2016 at 12:27:51PM -0700, Lars Tangvald wrote:
> > We've prepared MySQL 5.5.49 packages for Debian Wheezy and Jessie
> > with fixes for the CVEs listed in Oracle's April CPU.
> > The packages are built and tested and should be ready for upload,
> > and I've attached the debdiff output for review.
> > Of note is that due to upstream source changes we needed to remake a
> > patch that was added for 5.5.46 to fix arm and powerpc build
> > failures. New patch is larger, but should have the same behavior.
> 
> Okay.
> 
> Assuming some additional tests apart the testsuite have been done,
> please proceed with the update (but with the following small change).
> 
> Use 5.5.49-0+deb7u1 instead of 5.5.49-0+deb7u1.1 for the version,
> respectively 5.5.49-0+deb8u1 instead of 5.5.49-0+deb8u1.1.
> 
> Please remember to build the first upload for security master with -sa
> to include the original source, then the second one without -sa.[*].
> 
> I (or someone else of the team) will release the DSA once the builds
> are available.
> 
> Thanks already for your work on this update,
> 
> Regards,
> Salvatore
> 
>  [*] since you (your sponsor) will not get a dak accepted mail, please
>  either wait ~15 Minutes for the second upload to wait the first one
>  is correctly processed or drop in in #debian-security to shortly
>  confirm (or via mail is as well fine).

Do you have any status-update for this for us?

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#820939: marked as done (Non-free file test/srgb.icm)

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 16:52:46 +
with message-id 
and subject line Bug#820939: fixed in ruby-rmagick 2.15.4+dfsg-1
has caused the Debian Bug report #820939,
regarding Non-free file test/srgb.icm
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.)


-- 
820939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rmagick
Version: 2.15.4-2

Building ruby-rmagick yields this lintian problem:

E: license-problem-md5sum-non-free-file test/srgb.icm usual name is sRGB.icm. 
This file may not be distributed without fee if modified. See also 
https://bugs.debian.org/657281.
N: 
N:The following file is not suitable for main or contrib.
N:
N:Please re-package the package without the file (if possible) or ask the
N:FTP-masters to remove the package.
N:
N:You could also split this package and move this file into the non-free
N:archive.
N:
N:If this is a false-positive, please report a bug against Lintian.
N:
N:Severity: serious, Certainty: certain
N:
N:Check: cruft, Type: source


-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Source: ruby-rmagick
Source-Version: 2.15.4+dfsg-1

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-rmagick 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 21 Apr 2016 13:29:35 -0300
Source: ruby-rmagick
Binary: ruby-rmagick ruby-rmagick-doc
Architecture: source
Version: 2.15.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-rmagick - ImageMagick API for Ruby
 ruby-rmagick-doc - ImageMagick API for Ruby (documentation)
Closes: 820939
Changes:
 ruby-rmagick (2.15.4+dfsg-1) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * Remove non-free file test/srgb.icm (Closes: #820939)
   * debian/copyright: list test/srgb.icm in Files-Excluded so it is
 automatically removed from future new upstream release tarballs.
   * Add patch to ignore removed file when running tests
 .
   [ Christian Hofstaedtler ]
   * Explicitly Build-Depend on ruby-setup. Previously, gem2deb depended on
 ruby-setup, but to enable cross-building, it will drop that dependency.
 .
   [ Cédric Boutillier ]
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.7 (no changes needed)
Checksums-Sha1:
 354038d5e9c218dd354a1d09580f4f174daa5317 2367 ruby-rmagick_2.15.4+dfsg-1.dsc
 dabb67fbc92b4997360a1b2f633b569866bffe20 1558676 
ruby-rmagick_2.15.4+dfsg.orig.tar.gz
 c590332e89f9e20b228d3f5b9cd5172682527517 7220 
ruby-rmagick_2.15.4+dfsg-1.debian.tar.xz
Checksums-Sha256:
 12a46b3eec788cebd20abbc6b61bd8ca8af6dc01e5a1d3cde6cf5515d497cfc2 2367 
ruby-rmagick_2.15.4+dfsg-1.dsc
 c330250def5aabb46175ec12f6dab3b6c0421910406e70a0e9154197e570af0a 1558676 
ruby-rmagick_2.15.4+dfsg.orig.tar.gz
 3a9226ed72c58914ea2aa61b39d8c7c05093557ddab2eae3d7d29bd839618cc8 7220 
ruby-rmagick_2.15.4+dfsg-1.debian.tar.xz
Files:
 6f80c5da96b55f7e868c7ec645e73ae9 2367 ruby optional 
ruby-rmagick_2.15.4+dfsg-1.dsc
 68dba45bfc7abfd4037a6e82cb162bf6 1558676 ruby optional 
ruby-rmagick_2.15.4+dfsg.orig.tar.gz
 5f2412fd3ed8566a545d0826c9a0817c 7220 ruby optional 
ruby-rmagick_2.15.4+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXGQC0AAoJEPwNsbvNRgveaScQAPJcPvb3x6PNBlQ99HohtQK3
x2Yk0Ylu34+UBUBfFDolB5QPGSp8SqVmmkFCKH6G3mlTWNx4HzyAzs7z/S3/CmKW
Zy9VwJ5BCb8uQDpLv1N6MJ23g3QCkdKe7I/vbMrCgM7zE95TXf7vgy1lmgYoO/mA
ihJUKxkzc/flpsYVbFbafcSitB06gIq3vJsLfHYbIyv1XTf0sDPK9pntqjDJCfcg
zucV6x6Xf5MzV5q6HB5zTtMiLbfvHE3qW/Srpd/HN1oX+L+npKxKaf7duM6gOPXb

Bug#796611: ferm causes a unit ordering cycle that breaks booting

[Felix Geyer]

On Tue, 29 Mar 2016 13:34:33 +0200 Alexander Wirt  wrote:
> > OK. I sent a github PR with both commits to ease your work. You could
> > have just asked for them...
> I already integrated them, but thanks. And sorry for being grumpy, but I
> really dislike those 0-day nmus.

FWIW ferm 2.2-4 doesn't contain the fixes from 2.2-3.2

Felix

Processed: python-future hides and breaks python-configparser

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/PythonCharmers/python-future/issues/118
Bug #822157 [src:python-future] python-future hides and breaks 
python-configparser
Set Bug forwarded-to-address to 
'https://github.com/PythonCharmers/python-future/issues/118'.
> affects -1 python-configparser
Bug #822157 [src:python-future] python-future hides and breaks 
python-configparser
Added indication that 822157 affects python-configparser

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

Bug#822157: python-future hides and breaks python-configparser

[Raphaël Hertzog]

Source: python-future
Version: 0.15.2-1
Severity: serious
Tags: upstream
User: de...@kali.org
Usertags: origin-kali
Control: forwarded -1 https://github.com/PythonCharmers/python-future/issues/118
Control: affects -1 python-configparser

python-future provides the "configparser" module and so does
the python-configparser package... unfortunately, nobodby caught
this as there is no file conflict (configparser/__init__.py on one side
and configparser.py on other side).

But package depending on python-configparser (and there are 7 of them)
can't use the backported configparser when python-future is installed.

Upstream has not yet dropped the module but I believe we should do it
in Debian and replace it with a dependency on python-configparser. They
are not 100% API compatible but you can't get it both ways and using
the 3.X API is the way forward anyway for anyone who is looking to use
python-future.

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

Kernel: Linux 4.4.0-1-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)

Processed: tag #820707 and #618456

[Debian Bug Tracking System]

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

> tags 820707 + pending
Bug #820707 [src:camera.app] camera.app: FTBFS: DigitalCamera.m:15:21: fatal 
error: gphoto2.h: No such file or directory
Added tag(s) pending.
> tags 618456 + pending
Bug #618456 [camera.app] Typo in a .desktop entry
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822115: xarchiver: X server crashes when cancelling file extraction

[Markus Koschany]

Am 21.04.2016 um 16:19 schrieb g66...@tfwno.gf:
[...]
> Apologies, I didn't realize there was significant difference between
> running Xarchiver and extracting, versus using the Extract Here/To
> option in Thunar. But apparently the latter pops up a progress box and
> that's the one that crashes, whereas the former indicates progress in
> the main window, and it's safe to cancel that.
> 
> So it's probably a bug in thunar-archive-plugin, maybe, I'm worried
> about how it crashes the desktop.

Thanks for your clarification. I still don't know what kind of archive
and compression you tried to extract but this might be irrelevant now
that I know the crash is related to the thunar-archive-plugin.

After doing some research this seems to be a well known issue and a long
standing bug in Xarchiver:

https://sourceforge.net/p/xarchiver/bugs/27/
https://bugs.archlinux.org/task/27547

It seems someone forked Xarchiver at github.com:

https://github.com/ib/xarchiver

Maybe this issue is fixed already. I'm not sure about the severity but
it is definitely something I would like to see fixed rather sooner than
later, so I will keep the RC severity. This is also most likely the same
bug as https://bugs.debian.org/802019.

Thanks for reporting

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#822115: xarchiver: X server crashes when cancelling file extraction

[g6672d]

On 2016-04-21 21:37, Markus Koschany wrote:

Am 21.04.2016 um 13:07 schrieb mai:

Package: xarchiver
Version: 1:0.5.4-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

Pretty much as per the description: If I select an archive and 
"extract here"
then attempt to cancel the extraction, the desktop crashes and drops 
me back

to text console.

I'm not actually sure where to direct this report, the problem likely 
lies
elsewhere and Xarchiver is just the trigger. My system is Debian 
Jessie amd64

and I am running Xfce through startx. .xsession-errors follows:


[...]

Hello,

do you mean by "extract here" that you use Thunar or another file
manager to extract the archive by right-clicking on it? What happens if
you try to extract the same archive within Xarchiver? What kind of
archive is that? Is this crash reproducible and can you describe the
steps to reproduce it?

Thanks

Markus


Apologies, I didn't realize there was significant difference between
running Xarchiver and extracting, versus using the Extract Here/To
option in Thunar. But apparently the latter pops up a progress box and
that's the one that crashes, whereas the former indicates progress in
the main window, and it's safe to cancel that.

So it's probably a bug in thunar-archive-plugin, maybe, I'm worried
about how it crashes the desktop.

Processed: tagging 733693, tagging 817504

[Debian Bug Tracking System]

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

> # NMU in DELAYED/5
> tags 733693 + pending
Bug #733693 [ipkungfu] please do not depend on module-init-tools
Added tag(s) pending.
> tags 817504 + pending
Bug #817504 [src:ipkungfu] ipkungfu: Removal of debhelper compat 4
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#822120: Boost 1.55 to be removed; your attention required

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #822120 [feel++] Boost 1.55 to be removed; your attention required
Added tag(s) pending.
> severity -1 serious
Bug #822120 [feel++] Boost 1.55 to be removed; your attention required
Severity set to 'serious' from 'normal'

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

Bug#821785: marked as done (sipwitch: FTBFS: service.cpp:256:28: error: invalid conversion from 'const sockaddr*' to 'sockaddr*' [-fpermissive])

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 13:21:06 +
with message-id 
and subject line Bug#821785: fixed in sipwitch 1.9.15-1
has caused the Debian Bug report #821785,
regarding sipwitch: FTBFS: service.cpp:256:28: error: invalid conversion from 
'const sockaddr*' to 'sockaddr*' [-fpermissive]
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.)


-- 
821785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sipwitch
Version: 1.6.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

sipwitch fails to build from source in unstable/amd64:

  [..]

if test -e $i.cdbs-orig ; then \
mv $i.cdbs-orig $i ; \
fi ; \
  done
  rm -f debian/copyright_newhints
  rm -f debian/cdbs-install-list debian/cdbs-package-list 
debian/stamp-copyright-check
  rm -rf "debian/upstream-cruft"
  rm -f debian/stamp-upstream-cruft
  rm -f debian/stamp-autotools-files
  dh_clean 
  for file in Makefile.in common/Makefile.in inc/Makefile.in 
inc/sipwitch/Makefile.in server/Makefile.in test/Makefile.in utils/Makefile.in 
aclocal.m4 autoconf/ltmain.sh configure sipwitch.spec; do \
[ ! -e $file.upstream ] || mv -f $file.upstream $file; \
  done
  rm -f debian/stamp-upstreamtmpstuff
  rm -rf m4
  rm -f autoconf/compile autoconf/test-driver
  rm -f debian/sipwitch.init
  rm -f debian/stamp-local-shlibs-libsipwitch
   debian/rules build
  sed -e 's/__LIBPKGNAME__/libsipwitch1/g' debian/control.in
  test -x debian/rules
  mkdir -p "."
  /usr/share/cdbs/1/rules/buildcore.mk:110: CDBS WARNING:DEB_DH_STRIP_ARGS 
is deprecated since 0.4.85
  
  Scanning upstream source for new/changed copyright notices...
  
  licensecheck -c '.*' -r --copyright -i 
'^debian/(changelog|copyright(|_hints|_newhints))' -l '9' * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
  16 combinations of copyright and licensing found.
  WARNING: The following (and possibly more) new or changed notices discovered:
  
   server/system.cpp
   utils/cgiserver.cpp
   utils/sippasswd.cpp
   utils/sipquery.cpp
   utils/sipwitch.cpp
   README
  Copyright: 1994-2002, 2003-2011, Free Software
   utils/sippasswd.1
2010, David Sugar 
   autoconf/ltmain.sh
  Copyright: 1992-1999, 2000-2012, Free Software Foundation, …
1996-1997, 1999-2000, 2002-2006, 2008-2012, Free Software …
1996-2001, 2003-2006, 2007-2011, Free Software Foundation…
1999-2000, 2003-2007, 2009-2010, 2011-2012, Free Software …
and license
  Copyright: 1996-2004, 2005-2011, Free Software Foundation,
  Files: configure
  Copyright: 1992-1996, 1998-2012, Free Software Foundation, …
  Copyright: 2007, Free Software Foundation, Inc. 

Bug#822116: marked as done (bzr: FTBFS in testing (test fail))

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 13:19:39 +
with message-id 
and subject line Bug#822116: fixed in bzr 2.7.0-5
has caused the Debian Bug report #822116,
regarding bzr: FTBFS in testing (test fail)
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.)


-- 
822116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bzr
Version: 2.7.0-4
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch.

--
Traceback (most recent call last):
  File 
"/<>/build/lib.linux-x86_64-2.7/bzrlib/plugins/weave_fmt/test_bzrdir.py",
 line 426, in te
st_lock_file
b = branch.Branch.open(self.get_url())
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/branch.py", line 
186, in open
possible_transports=possible_transports, _unsupported=_unsupported)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", line 
689, in open
_unsupported=_unsupported)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", line 
718, in open_from_transport
find_format, transport, redirected)
  File 
"/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/__init__.py", 
line 1719, in do_catching_
redirections
return action(transport)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", line 
706, in find_format
probers=probers)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", line 
1151, in find_format
return prober.probe_transport(transport)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/bzrdir.py", line 
1237, in probe_transport
format_string = transport.get_bytes(".bzr/branch-format")
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/sftp.py", 
line 422, in get_bytes
f = self.get(relpath)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/sftp.py", 
line 414, in get
f.prefetch()
TypeError: prefetch() takes exactly 2 arguments (1 given)
--

I can send the full build log if required, or you can also get the one
from reproducible builds, as it fails in the same way:

https://reproducible.debian.net/rbuild/testing/amd64/bzr_2.7.0-4.rbuild.log

Thanks.
--- End Message ---
--- Begin Message ---
Source: bzr
Source-Version: 2.7.0-5

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated bzr 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, 09 Apr 2016 14:45:18 +
Source: bzr
Binary: bzr python-bzrlib python-bzrlib-dbg python-bzrlib.tests bzr-doc
Architecture: source all amd64
Version: 2.7.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazaar Maintainers 
Changed-By: Jelmer Vernooij 
Description:
 bzr- easy to use distributed version control system
 bzr-doc- easy to use distributed version control system (documentation)
 python-bzrlib - distributed version control system - python library
 python-bzrlib-dbg - distributed version control system - debug extension
 python-bzrlib.tests - distributed version control system - testsuite
Closes: 822116
Changes:
 bzr (2.7.0-5) unstable; urgency=medium
 .
   * Enable PGP checking of upstream tarball.
   * Cope with paramiko making argument to SFTPFile.prefetch() mandatory.
 Closes: #822116
Checksums-Sha1:
 849d2066499a590a156335214d0be0f226f867ef 2299 bzr_2.7.0-5.dsc
 7be64cd17de193baffc39a07038f699a469e1210 64592 bzr_2.7.0-5.debian.tar.xz
 53c427a6a3d2d5690630644b368f70cf07113b8e 3795392 bzr-doc_2.7.0-5_all.deb
 657b2775b9cd33e4d327194094332a2c7b14fcc8 54942 bzr_2.7.0-5_all.deb
 c1735f76bbe37f9e7160b6ca61e2779a448d8e36 2132754 
python-bzrlib-dbg_2.7.0-5_amd64.deb
 6b7ffb9049d8144e7a6843791979e99a1a1af431 1026596 
python-bzrlib.tests_2.7.0-5_all.deb
 096810b6da9e876390ec8ec514efd382ec53e5fb 1632448 

Bug#822070: marked as done (courier-mta: Transition from "daemon" user to "courier" user is handled terribly)

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 13:19:50 +
with message-id 
and subject line Bug#822070: fixed in courier 0.75.0-19
has caused the Debian Bug report #822070,
regarding courier-mta: Transition from "daemon" user to "courier" user is 
handled terribly
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.)


-- 
822070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-mta
Version: 0.75.0-18
Severity: grave
Justification: renders package unusable

Recently I decided to upgrade courier (mta and imap) on one of my mail servers. 
It was a disaster. The quality of these packages is abysmal and dangerous. This 
is one of the many serious, grave, and critical bugs I ran into during that 
process.



It appears that recently a change was made to transition the courier-* system 
away from the generic "daemon" user towards the "courier" user. This is good 
and probably should have been a done a long time ago.

However, this process is being handled terribly and will almost certainly 
result in broken mail systems and possibly (confirmed in my case) data loss.

First, the administrator needs to be made aware of this change. It needs to be 
a NEWS item, there should probably be a confirmation dialog prompting the user 
for acknowledgment, and it needs to be documented, which it currently is not 
short of a tiny changelog line.

In the case of /etc/courier/esmtpd, the MAILUSER and MAILGROUP parameters need 
to be checked and the administrator should be VIOLENTLY notified if these need 
to get updated. There may be other configuration items which need updating 
which I am not aware of. I use only a portion of the courier suite.

Proper file permissions need to be set. in my case, the courier system could 
not read any of my .pem files and some other files/directories because they 
were set to ownership root:courier but had permissions -rw---. A chmod g+r 
should probably be done against similar files.

A change like this needs to be done carefully and with consideration.



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

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

Versions of packages courier-mta depends on:
ii  courier-authlib0.66.4-7
ii  courier-base   0.75.0-18
ii  debconf [debconf-2.0]  1.5.59
ii  libc6  2.22-7
ii  libcourier-unicode11.4-2
ii  libgcc11:5.3.1-14
ii  libgdbm3   1.8.3-13.1
ii  libidn11   1.32-3
ii  libnet-cidr-perl   0.17-1
ii  libperl5.225.22.1-10
ii  libstdc++6 5.3.1-14
ii  sysvinit-utils 2.88dsf-59.3

courier-mta recommends no packages.

Versions of packages courier-mta suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.20160123cvs-2
ii  courier-doc  0.75.0-18
ii  courier-filter-perl  0.200+ds-4
pn  couriergrey  
ii  emacs24 [mail-reader]24.5+1-6+b2
ii  mutt [mail-reader]   1.5.24-1+b1
ii  s-nail [mail-reader] 14.8.8-1

-- Configuration Files:
/etc/courier/aliases/system [Errno 13] Permission denied: 
u'/etc/courier/aliases/system'
/etc/courier/courierd changed [not included]
/etc/courier/dsnheader.txt changed [not included]
/etc/courier/esmtpauthclient [Errno 13] Permission denied: 
u'/etc/courier/esmtpauthclient'
/etc/courier/esmtpd changed [not included]
/etc/courier/esmtpd-msa changed [not included]
/etc/courier/esmtpd-ssl changed [not included]
/etc/courier/esmtpd.cnf [Errno 13] Permission denied: u'/etc/courier/esmtpd.cnf'
/etc/courier/smtpaccess/default [Errno 13] Permission denied: 
u'/etc/courier/smtpaccess/default'
/etc/init.d/courier-mta changed [not included]
/etc/init.d/courier-mta-ssl changed [not included]

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 0.75.0-19

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

Debian distribution maintenance 

Bug#822071: marked as done (maildrop: Upgrade from courier-maildrop: Default delivery location changed from Maildirs $/HOME/Maildir to /var/mail/$USER)

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 13:19:50 +
with message-id 
and subject line Bug#822071: fixed in courier 0.75.0-19
has caused the Debian Bug report #822071,
regarding maildrop: Upgrade from courier-maildrop: Default delivery location 
changed from Maildirs $/HOME/Maildir to /var/mail/$USER
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.)


-- 
822071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maildrop
Version: 2.8.3-0.1
Severity: grave
Justification: causes non-serious data loss

Recently I decided to upgrade courier (mta and imap) on one of my mail servers. 
It was a disaster. The quality of these packages is abysmal and dangerous. This 
is one of the many serious, grave, and critical bugs I ran into during that 
process.



It appears that the default mail delivery location in maildrop/courier-maildrop 
has changed from being Maildirs ($HOME/Maildir) to spool files (/var/mail/).

Upon upgrading my courier system, I found that new mail was being delivered to 
mailspool files in /var/mail instead of Maildirs, as it was previously.

I don't know why this change has happened as I don't have much time to look 
into it, but it is definitely a default behavior change. This could definiely 
lead to data loss, and at the very least will be a pain if the admin has 
re-deliver the mail spool contents back to the Maildirs.

A workaround is to configure the new /etc/maildroprc file DEFAULT parameter, 
which is convinently already typed out with the correct arguments and just 
needs to be uncommented.



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

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

Versions of packages maildrop depends on:
ii  courier-authlib  0.66.4-7
ii  libc62.22-7
ii  libcourier-unicode1  1.4-2
ii  libgcc1  1:5.3.1-14
ii  libgdbm3 1.8.3-13.1
ii  libpcre3 2:8.38-3.1
ii  libstdc++6   5.3.1-14

Versions of packages maildrop recommends:
ii  courier-mta [mail-transport-agent]  0.75.0-18

maildrop suggests no packages.

-- Configuration Files:
/etc/maildroprc changed:
DEFAULT="$HOME/Maildir"


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 0.75.0-19

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated courier package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 21 Apr 2016 14:40:26 +0200
Source: courier
Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail 
courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap 
courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl
Architecture: source
Version: 0.75.0-19
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Ondřej Surý 
Description:
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax<->mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-imap-ssl - Courier mail server - IMAP over SSL [transitional]
 courier-ldap - Courier mail server - LDAP support
 courier-maildrop - Courier mail server - mail delivery agent [transitional 
package]
 courier-mlm - Courier mail server - mailing list manager
 courier-mta - Courier mail server - ESMTP daemon
 courier-mta-ssl - Courier mail server - ESMTP over SSL
 courier-pcp - Courier mail server - PCP server
 courier-pop - Courier mail server - POP3 server
 courier-pop-ssl - Courier mail server - 

Processed: severity of 822076 is important

[Debian Bug Tracking System]

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

> severity 822076 important
Bug #822076 [src:linux] linux-image-4.4.0-1-amd64: Monitor becomes blank during 
boot on built-in Intel i915 chip
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#822118: RM: fw4spl -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages

[Tobias Frost]

Package: fw4spl
Severity: serious
Justification: blocks-transitions

Dear maintainer / ftp-masters,

fw4spl is RC buggy with 5 bugs:
 #797475 fw4spl: does not support parallel build
 #797481 fw4spl: FTBFS - Doesn't support boost 1.58
 #809935 fw4spl: FTBFS with libpng16
 #820632 fw4spl: depends on vtk 5
 #821957 fw4spl: Depends on insighttoolkit, which is about to be removed. 
Please port to insighttoolkit4

With the first two filed August 2015; both of them did not receive any response 
from the maintainer, though
extra triggered again by Andreas in December.

(The other two bugs do not ahve a response too, but they are only a few days 
old)

The package blocks the boost, libpng and vtk transitions.

As it is now blocking other packages, I raise the question if it should be
removed from Debian.

Please response to this bug, if there is no response within a week, I will
reassign this bug to ftp.debian.org.

Please note, that if decide to keep it, you need to fix your pacakge ASAP.
The removal of libpng1.2 will NOT wait for root-system, and when removed,
at least the binary packages must go with it. (Which can lead to src removal)

Thanks for your understanding,

-- 
tobi



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

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

Bug#822091: libxmlbeans-java: Embeds classes without source

[Emmanuel Bourg]

Le 21/04/2016 09:29, Markus Koschany a écrit :

> While I was working on #820839, I discovered that the source package
> ships external jar and zip files in external/.
> 
> I tried to repack the tarball but then the package failed to build
> from source. Apparently the build system requires the piccolo classes
> and it also embeds them in the resulting xmlbeans.jar.

Good catch. It looks like the jar was already embedded in the first
upload 6 years ago. XMLBeans has an option to use an alternative XML
parser (with XmlOptions.setLoadUseXMLReader()) but it's never used in
Debian. So the Piccolo parser is indeed used.

Piccolo is a rather old parser, I don't think it's worth packaging it. I
suggest patching xmlbeans to use the standard JDK parser instead.

Emmanuel Bourg

Processed: Re: aptitude: artificial report to prevent migrating the package to testing

[Debian Bug Tracking System]

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

> found 802958 aptitude/0.8-1
Bug #802958 [aptitude] aptitude: artificial report to prevent migrating the 
package to testing
Marked as found in versions aptitude/0.8-1.
> stop
Stopping processing here.

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

Bug#822115: xarchiver: X server crashes when cancelling file extraction

[Markus Koschany]

Am 21.04.2016 um 13:07 schrieb mai:
> Package: xarchiver
> Version: 1:0.5.4-1
> Severity: grave
> Justification: causes non-serious data loss
> 
> Dear Maintainer,
> 
> Pretty much as per the description: If I select an archive and "extract here"
> then attempt to cancel the extraction, the desktop crashes and drops me back
> to text console.
> 
> I'm not actually sure where to direct this report, the problem likely lies
> elsewhere and Xarchiver is just the trigger. My system is Debian Jessie amd64
> and I am running Xfce through startx. .xsession-errors follows:

[...]

Hello,

do you mean by "extract here" that you use Thunar or another file
manager to extract the archive by right-clicking on it? What happens if
you try to extract the same archive within Xarchiver? What kind of
archive is that? Is this crash reproducible and can you describe the
steps to reproduce it?

Thanks

Markus




signature.asc
Description: OpenPGP digital signature

Bug#822116: bzr: FTBFS in testing (test fail)

[Jelmer Vernooij]

On Thu, Apr 21, 2016 at 01:12:02PM +0200, Santiago Vila wrote:
> Package: src:bzr
> Version: 2.7.0-4
> Severity: serious
> 
> Dear maintainer:
> 
> This package currently fails to build from source in stretch.
> 
> --
> Traceback (most recent call last):
>   File 
> "/<>/build/lib.linux-x86_64-2.7/bzrlib/plugins/weave_fmt/test_bzrdir.py",
>  line 426, in te
> st_lock_file
> b = branch.Branch.open(self.get_url())
>   File "/<>/build/lib.linux-x86_64-2.7/bzrlib/branch.py", line 
> 186, in open
> possible_transports=possible_transports, _unsupported=_unsupported)
>   File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", 
> line 689, in open
> _unsupported=_unsupported)
>   File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", 
> line 718, in open_from_transport
> find_format, transport, redirected)
>   File 
> "/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/__init__.py", 
> line 1719, in do_catching_
> redirections
> return action(transport)
>   File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", 
> line 706, in find_format
> probers=probers)
>   File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", 
> line 1151, in find_format
> return prober.probe_transport(transport)
>   File "/<>/build/lib.linux-x86_64-2.7/bzrlib/bzrdir.py", line 
> 1237, in probe_transport
> format_string = transport.get_bytes(".bzr/branch-format")
>   File 
> "/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/sftp.py", line 
> 422, in get_bytes
> f = self.get(relpath)
>   File 
> "/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/sftp.py", line 
> 414, in get
> f.prefetch()
> TypeError: prefetch() takes exactly 2 arguments (1 given)
> --
> 
> I can send the full build log if required, or you can also get the one
> from reproducible builds, as it fails in the same way:
> 
> https://reproducible.debian.net/rbuild/testing/amd64/bzr_2.7.0-4.rbuild.log

This is caused by an API change in paramiko's public API, making the file_size 
argument to prefetch() mandatory.

Jelmer

Bug#778599: Vulnerabilities in nanohttp

[Russell Coker]

On Thu, 21 Apr 2016 02:58:18 PM Salvatore Bonaccorso wrote:
> Given the package looks unmaintained (last update by maintainer back
> in 20 Jun 2010, I think it is the best option to remove the package as
> well from unstable). It is already gone in testing, so will not be
> included in stretch and neither was in jessie.

OK sounds reasonable.

Sorry I've been having problems maintaining my packages that are more useful 
than that one.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#822115: xarchiver: X server crashes when cancelling file extraction

[mai]

Package: xarchiver
Version: 1:0.5.4-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

Pretty much as per the description: If I select an archive and "extract here"
then attempt to cancel the extraction, the desktop crashes and drops me back
to text console.

I'm not actually sure where to direct this report, the problem likely lies
elsewhere and Xarchiver is just the trigger. My system is Debian Jessie amd64
and I am running Xfce through startx. .xsession-errors follows:

Xarchiver 0.5.4 (©)2005-2008 Giuseppe Torelli
nm-applet-Message: PID 3949 (we are 3859) sent signal 2, shutting down...
xfce4-panel-Message: Plugin battery-6 has been automatically restarted after 
crash.
xfce4-panel-Message: Plugin cpufreq-7 has been automatically restarted after 
crash.
xfce4-panel-Message: Plugin systray-8 has been automatically restarted after 
crash.
xfce4-panel-Message: Plugin xfce4-sensors-plugin-2 has been automatically 
restarted after crash.
xfce4-panel-Message: Plugin netload-10 has been automatically restarted after 
crash.

(xfsettingsd:3879): libxfce4ui-WARNING **: ICE I/O Error

(xfsettingsd:3879): libxfce4ui-WARNING **: Disconnected from session manager.
xfwm4: Fatal IO error 4 (Interrupted system call) on X server :0.0.
xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.0.
xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.0.

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

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

Versions of packages xarchiver depends on:
ii  libc6   2.19-18+deb8u4
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u4
ii  libglib2.0-02.42.1-1+b1
ii  libgtk2.0-0 2.24.25-3+deb8u1
ii  libpango-1.0-0  1.36.8-3

Versions of packages xarchiver recommends:
ii  bzip2   1.0.6-7+b3
ii  p7zip-full  9.20.1~dfsg.1-4.1+deb8u1
ii  unzip   6.0-16+deb8u2
ii  xdg-utils   1.1.0~rc1+git20111210-7.4
ii  xz-utils5.1.1alpha+20120614-2+b3

Versions of packages xarchiver suggests:
pn  arj
ii  lhasa  0.2.0+git3fe46-1+deb8u1
pn  rar
pn  rpm
pn  unar   
ii  zip3.0-8

-- no debconf information

Bug#822116: bzr: FTBFS in testing (test fail)

[Santiago Vila]

Package: src:bzr
Version: 2.7.0-4
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch.

--
Traceback (most recent call last):
  File 
"/<>/build/lib.linux-x86_64-2.7/bzrlib/plugins/weave_fmt/test_bzrdir.py",
 line 426, in te
st_lock_file
b = branch.Branch.open(self.get_url())
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/branch.py", line 
186, in open
possible_transports=possible_transports, _unsupported=_unsupported)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", line 
689, in open
_unsupported=_unsupported)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", line 
718, in open_from_transport
find_format, transport, redirected)
  File 
"/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/__init__.py", 
line 1719, in do_catching_
redirections
return action(transport)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", line 
706, in find_format
probers=probers)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/controldir.py", line 
1151, in find_format
return prober.probe_transport(transport)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/bzrdir.py", line 
1237, in probe_transport
format_string = transport.get_bytes(".bzr/branch-format")
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/sftp.py", 
line 422, in get_bytes
f = self.get(relpath)
  File "/<>/build/lib.linux-x86_64-2.7/bzrlib/transport/sftp.py", 
line 414, in get
f.prefetch()
TypeError: prefetch() takes exactly 2 arguments (1 given)
--

I can send the full build log if required, or you can also get the one
from reproducible builds, as it fails in the same way:

https://reproducible.debian.net/rbuild/testing/amd64/bzr_2.7.0-4.rbuild.log

Thanks.

Bug#821868: marked as pending

[Ivan Udovichenko]

tag 821868 pending
thanks

Hello,

Bug #821868 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=openstack/horizon.git;a=commitdiff;h=7de3eba

---
commit 7de3ebade81d5862adc078fe9943f2aa16d0b314
Author: Ivan Udovichenko 
Date:   Thu Apr 21 13:52:16 2016 +0300

Trigger package configuration only once.

diff --git a/debian/changelog b/debian/changelog
index 64e6b7c..90c7536 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,8 @@ horizon (2:9.0.0-2) UNRELEASED; urgency=medium
   * d/openstack-dashboard-apache.postinst: Revert changes. (Closes: #820845)
 - Do not modify provided Apache configuration files.
 - Enable site provided by openstack-dashboard-alias-only.conf .
+  * d/openstack-dashboard.triggers: Trigger package configuration
+only once. (Closes: #821868)
 
  -- Ivan Udovichenko   Wed, 13 Apr 2016 23:34:27 
+0300
 

Processed: Bug#821868 marked as pending

[Debian Bug Tracking System]

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

> tag 821868 pending
Bug #821868 [openstack-dashboard] openstack-dashboard: causes trigger loop
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822103: light-locker: Cannot unlock screen

[Lars Behrens]

Screen cannot be unlocked after 'light-locker-command -l' as neither
keyboard nor mouse action brings up the unlocking dialog, screen just
stays dark. SSH access still working though.




smime.p7s
Description: S/MIME Cryptographic Signature

Bug#822104: guessnet: FTBFS: *** libiw not found. Check 'config.log' for more details.

[Chris Lamb]

Source: guessnet
Version: 0.56
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

guessnet fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'guessnet-build-deps' in 
'../guessnet-build-deps_0.56_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package guessnet-build-deps.
  (Reading database ... 22998 files and directories currently installed.)
  Preparing to unpack guessnet-build-deps_0.56_all.deb ...
  Unpacking guessnet-build-deps (0.56) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
cdbs dh-buildinfo libiw-dev libiw30 libnet1 libnet1-dev libpcap-dev
libpcap0.8 libpcap0.8-dev libtut-dev libwibble-dev pkgconf
  Suggested packages:
pkg-config
  The following NEW packages will be installed:
cdbs dh-buildinfo libiw-dev libiw30 libnet1 libnet1-dev libpcap-dev
libpcap0.8 libpcap0.8-dev libtut-dev libwibble-dev pkgconf
  0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 1831 kB of archives.
  After this operation, 18.4 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.130 
[76.4 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 dh-buildinfo all 
0.11+nmu1 [18.1 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libnet1 amd64 
1.1.6+dfsg-3 [60.4 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libnet1-dev amd64 
1.1.6+dfsg-3 [118 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libpcap0.8 amd64 
1.7.4-2 [136 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libpcap0.8-dev amd64 
1.7.4-2 [233 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libpcap-dev all 
1.7.4-2 [24.0 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 libtut-dev all 
0.0.20070706-1 [99.2 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 libwibble-dev amd64 
1.1-1+b1 [977 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 pkgconf amd64 
0.9.12-1 [29.5 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 libiw30 amd64 
30~pre9-9 [21.2 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libiw-dev amd64 
30~pre9-9 [38.8 kB]
  Fetched 1831 kB in 0s (85.0 MB/s)
  Selecting previously unselected package cdbs.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23002 files and directories currently installed.)
  Preparing to unpack .../archives/cdbs_0.4.130_all.deb ...
  Unpacking cdbs (0.4.130) ...
  Selecting previously unselected package dh-buildinfo.
  Preparing to unpack .../dh-buildinfo_0.11+nmu1_all.deb ...
  Unpacking dh-buildinfo (0.11+nmu1) ...
  Selecting previously unselected package libnet1:amd64.
  Preparing to unpack .../libnet1_1.1.6+dfsg-3_amd64.deb ...
  Unpacking libnet1:amd64 (1.1.6+dfsg-3) ...
  Selecting previously unselected package libnet1-dev.
  Preparing to unpack .../libnet1-dev_1.1.6+dfsg-3_amd64.deb ...
  Unpacking libnet1-dev (1.1.6+dfsg-3) ...
  Selecting previously unselected package libpcap0.8:amd64.
  Preparing to unpack .../libpcap0.8_1.7.4-2_amd64.deb ...
  Unpacking libpcap0.8:amd64 (1.7.4-2) ...
  Selecting previously unselected package libpcap0.8-dev.
  Preparing to unpack .../libpcap0.8-dev_1.7.4-2_amd64.deb ...
  Unpacking libpcap0.8-dev (1.7.4-2) ...
  Selecting previously unselected package libpcap-dev.
  Preparing to unpack .../libpcap-dev_1.7.4-2_all.deb ...
  Unpacking libpcap-dev (1.7.4-2) ...
  Selecting previously unselected package libtut-dev.
  Preparing to unpack .../libtut-dev_0.0.20070706-1_all.deb ...
  Unpacking libtut-dev (0.0.20070706-1) ...
  Selecting previously unselected package libwibble-dev.
  Preparing to unpack .../libwibble-dev_1.1-1+b1_amd64.deb ...
  Unpacking libwibble-dev (1.1-1+b1) ...
  Selecting previously unselected package pkgconf.
  

Bug#822103: light-locker: Cannot unlock screen

[Lars Behrens]

Package: light-locker
Version: 1.7.0-3
Severity: grave
Justification: renders package unusable



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

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

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  libc62.22-6
ii  libcairo21.14.6-1+b1
ii  libdbus-1-3  1.10.8-1
ii  libdbus-glib-1-2 0.106-1
ii  libglib2.0-0 2.48.0-1
ii  libgtk-3-0   3.18.9-1
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libsystemd0  229-4
ii  libx11-6 2:1.6.3-1
ii  libxext6 2:1.3.3-1
ii  libxss1  1:1.2.2-1
ii  lightdm  1.18.1-1

light-locker recommends no packages.

light-locker suggests no packages.

-- no debconf information

Bug#822085: RM: root-system: RoQA unmaintained, RC-buggy, FTBFS, blocks removal of old packages

[Mattia Rizzolo]

On Thu, Apr 21, 2016 at 08:14:31AM +0200, Tobias Frost wrote:
> As it is now blocking other packages, I raise the question if it should be
> removed from Debian.

It is indeed in a very bad state.


I tried to revive it some time back, and also committed something to git
for it, but really, it's a big thing and I can't deal with it within my
current spare time.  Also, that would be a (huge) one-time effort, and
clearly something like that can't be left as it is again.
So, I give up on my tentative for it, I have several other more pressing
commitments than such a huge package I'm not really even interested it
(if not for QA reasons, due to its dep chain).

The actual maintainer (explicitly CCed) seems to have disappear (note
that he is a DM, and from a quick lock at his DDPO page I see most of
his packages either uploaded long ago, with RC bugs and NMUed).

> Please response to this bug, if there is no response within a week, I will
> reassign this bug to ftp.debian.org

dak rm -Rn root-system fastjet rivet herwig++ thepeg pythia8 hepmc

This is a clean removal of root-system and everything that
(transitively) depends on it.  Most of those other packages don't have
that many issues if not the depends on root-system.
Rather than removing all of the right aways, I'd force the removal of 
libpng (and also the other old libs) breaking root-system (this will
make it uninstallable, which is yet another RC bug!) and possible all
its rdeps.
But if in some months nobody manages to have a buildable and up-to-date
root-system, I I'll go ahead and ask for RM myself.

> Please note, that if decide to keep it, you need to fix your pacakge ASAP.
> The removal of libpng1.2 will NOT wait for root-system, and when removed,
> at least the binary packages must go with it. (Which can lead to src removal)

That's not strictly needed: packages can be forcefully removed from the
archive even if something else depends on them, you "just" need to
convince ftpmasters that it's ok to break them.

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

Bug#822099: python-odf: depends on python3.4

[Julien Cristau]

Source: python-odf
Version: 1.3.2+dfsg1-1
Severity: serious

python-odf-tools depends on python3.4 which is going away.  It needs to
be rebuilt to lose that dependency.

Cheers,
Julien

Bug#822097: python3-future: depends on python3.4 which is going away

[Julien Cristau]

Package: python3-future
Version: 0.15.2-1
Severity: serious

python3-future depends on python3.4, which is being removed (replaced
with 3.5), so the package needs to be rebuilt to drop that dependency.

Cheers,
Julien

Bug#822098: python3-gear: depends on python3.4

[Julien Cristau]

Package: python3-gear
Version: 0.5.8-2
Severity: serious

python3-gear depends on python3.4 which is replaced by python3.5.  Your
package needs to be rebuilt to lose that dependency.

Cheers,
Julien

Processed: closing 820098

[Debian Bug Tracking System]

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

> close 820098
Bug #820098 [src:pcl] FTBFS: No rule to make target 
'/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#820098: closing 820098

[Jochen Sprickerhof]

close 820098 
thanks

This should be fixed with vtk6 (6.2.0+dfsg1-11.1).

Bug#821785: sipwitch: FTBFS: service.cpp:256:28: error: invalid conversion from 'const sockaddr*' to 'sockaddr*' [-fpermissive]

[Jonas Smedegaard]

Quoting peter green (2016-04-21 05:14:40)
>> service.cpp: In static member function 'static void 
>> sipwitch::service::publish(const char*)':
>>service.cpp:256:28: error: invalid conversion from 'const sockaddr*' to 
>> 'sockaddr*' [-fpermissive]
>> host = resolver.getAddr();
> This was easy enough to fix, just add a const to the type of the 
> variable "host".
> 
> Unfortunately after doing so the build failed with.
[...]
> I presume the first of those errors will be another easy fix, but I 
> have no idea about the second one.

Thanks for looking into this - and for reporting in the first place.

Upstream ChangeLog for 1.9.11→1.9.13 mentions "type cleanups for 
sockaddr, other cleanup for ucommon 7 prep", so likely these issues are 
solved by upgrading to newest upstream release 1.9.15.

I am looking into doing that now.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#821350: marked as done (dh-golang: generates rubbish in Built-Using; errors on invocation)

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 07:49:11 +
with message-id 
and subject line Bug#821350: fixed in dh-golang 1.16
has caused the Debian Bug report #821350,
regarding dh-golang: generates rubbish in Built-Using; errors on invocation
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.)


-- 
821350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-golang
Version: 1.15
Severity: serious

Recent upload of "rkt" was rejected

rkt_1.4.0+dfsg-1_amd64.deb: Built-Using refers to non-existing source 
package apt (= 1.0.9.10)

due to rubbish in Built-Using field:

apt (= 1.0.9.10), apt (= 1.0.10.2), apt (= 1.2.10)

Also invocation of dh-golang logged the following:


   dh_golang -O--buildsystem=golang -O--builddirectory=_build
can't load package: package github.com/coreos/rkt/api/v1alpha: cannot find 
package "github.com/coreos/rkt/api/v1alpha" in any of:
/usr/lib/go/src/github.com/coreos/rkt/api/v1alpha (from $GOROOT)

/build/rkt-1.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/coreos/rkt/api/v1alpha
 (from $GOPATH)
can't load package: package github.com/coreos/rkt/rkt: cannot find package 
"github.com/coreos/rkt/rkt" in any of:
/usr/lib/go/src/github.com/coreos/rkt/rkt (from $GOROOT)

/build/rkt-1.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/coreos/rkt/rkt (from 
$GOPATH)
can't load package: package .: no buildable Go source files in 
/build/rkt-1.4.0+dfsg
can't load package: package .: no buildable Go source files in 
/build/rkt-1.4.0+dfsg
dpkg-query: error: --search needs at least one file name pattern argument

Use --help for help about querying packages.


This is regression from "dh-golang" v1.12.

Please investigate.

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

Truth never damages a cause that is just.
-- Mahatma Gandhi


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: dh-golang
Source-Version: 1.16

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

Debian distribution maintenance software
pp.
Michael Stapelberg  (supplier of updated dh-golang 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 21 Apr 2016 09:38:34 +0200
Source: dh-golang
Binary: dh-golang
Architecture: source all
Version: 1.16
Distribution: unstable
Urgency: medium
Maintainer: Michael Stapelberg 
Changed-By: Michael Stapelberg 
Description:
 dh-golang  - debhelper add-on for packaging software written in Go (golang)
Closes: 821350
Changes:
 dh-golang (1.16) unstable; urgency=medium
 .
   [ Michael Hudson-Doyle ]
   * Make dh_golang more robust:
 - Initialize the buildsystem more correctly, so --builddirectory=_build
   works (Closes: 821350)
 - Exit with an error if any of the 'go list' or 'dpkg-search' commands
   fail.
 - Quote the current working directory in the regexp used to filter out
   files from the build directory.
 - Store package / directory lists in files and use xargs to avoid
   constructing over-long command lines.
   * Also trim dh_golang's use statements.
Checksums-Sha1:
 5ec8c99e61b6912b487d85ce677cae47d48dbc90 1559 dh-golang_1.16.dsc
 e3e7daeef0fbd94ed461f64271192148a2937b18 6668 dh-golang_1.16.tar.xz
 fa2c17b9e28da3514d14e92495268101bafb2651 8572 dh-golang_1.16_all.deb
Checksums-Sha256:
 c2d1137757ff154e7177177146a6bdc863419292e0ca6d52717c912e2c090e5a 1559 
dh-golang_1.16.dsc
 e308fa8e09e58a3e5a2b87df974bb6f2ff44164c4d071e396c8bc189ba62d3ed 6668 
dh-golang_1.16.tar.xz
 710fc095263294ced90a79bce4d528363bd9134d99e8c3f99f543077cff4d737 8572 
dh-golang_1.16_all.deb
Files:
 bde1779674409834e6b3afd3208ee10f 1559 devel extra dh-golang_1.16.dsc
 abcfb2bdcfd7a5d51e28e5c3abd20d60 6668 devel extra dh-golang_1.16.tar.xz
 75c7a1e9fa1c66b51475308c4ab6d3c6 8572 devel extra 

Processed: severity of 822065 is important, severity of 822066 is important

[Debian Bug Tracking System]

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

> severity 822065 important
Bug #822065 [courier-mta] courier-mta: init script references the wrong 
configuration file; completely broken.
Severity set to 'important' from 'grave'
> severity 822066 important
Bug #822066 [courier-mta] courier-mta-ssl init script broken
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: reassign 822067 to src:courier, reassign 822068 to src:courier, forcibly merging 822067 822068

[Debian Bug Tracking System]

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

> reassign 822067 src:courier
Bug #822067 [courier-mta] courier-mta: init scripts completely broken
Bug reassigned from package 'courier-mta' to 'src:courier'.
No longer marked as found in versions courier/0.75.0-18.
Ignoring request to alter fixed versions of bug #822067 to the same values 
previously set
> reassign 822068 src:courier
Bug #822068 [courier-imap] courier-imap: init scripts completely broken
Bug reassigned from package 'courier-imap' to 'src:courier'.
No longer marked as found in versions courier/0.75.0-18.
Ignoring request to alter fixed versions of bug #822068 to the same values 
previously set
> forcemerge 822067 822068
Bug #822067 [src:courier] courier-mta: init scripts completely broken
Bug #822068 [src:courier] courier-imap: init scripts completely broken
Severity set to 'important' from 'grave'
Added tag(s) moreinfo.
Merged 822067 822068
> thanks
Stopping processing here.

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

Processed: Re: Bug#822067: courier-mta: init scripts completely broken

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo
Bug #822067 [courier-mta] courier-mta: init scripts completely broken
Added tag(s) moreinfo.
> severity -1 important
Bug #822067 [courier-mta] courier-mta: init scripts completely broken
Severity set to 'important' from 'grave'

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

Bug#822091: libxmlbeans-java: Embeds classes without source

[Markus Koschany]

Package: libxmlbeans-java
Version: 2.6.0-4
Severity: serious


While I was working on #820839, I discovered that the source package
ships external jar and zip files in external/.

I tried to repack the tarball but then the package failed to build
from source. Apparently the build system requires the piccolo classes
and it also embeds them in the resulting xmlbeans.jar.

This is bad on many levels and needs fixing.

Markus


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

Kernel: Linux 4.5.0-1-amd64 (SMP w/2 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: unable to detect

Versions of packages libxmlbeans-java depends on:
ii  libxml-commons-resolver1.1-java  1.2-7

libxmlbeans-java recommends no packages.

libxmlbeans-java suggests no packages.

-- no debconf information

Bug#822067: courier-mta: init scripts completely broken

[Ondřej Surý]

Control: tags -1 +moreinfo
Control: severity -1 important

J, you probably should not fill bugs when you are pissed.

This bug report is not a bug report, but a complaint. If you have
anything you want to fix, you should say it. You are also more then
welcome to send patches or join the effort to package Courier MTA in
Debian as you clearly use it and understand the problems with the
packages.

O.
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Thu, Apr 21, 2016, at 01:43, J Mo wrote:
> Package: courier-mta
> Version: 0.75.0-18
> Severity: grave
> Justification: renders package unusable
> 
> Recently I decided to upgrade courier (mta and imap) on one of my mail
> servers. It was a disaster. The quality of these packages is abysmal and
> dangerous. This is one of the many serious, grave, and critical bugs I
> ran into during that process.
> 
> 
> 
> I have the following courier-related init scritps on my system:
> 
> courier-mta: /etc/init.d/courier
> courier-authdaemon: /etc/init.d/courier-authdaemon
> courier-mta: /etc/init.d/courierfilter
> courier-imap: /etc/init.d/courier-imap
> courier-imap: /etc/init.d/courier-imap-ssl
> courier-mta: /etc/init.d/courier-msa
> courier-mta: /etc/init.d/courier-mta
> courier-mta: /etc/init.d/courier-mta-ssl
> 
> 
> 
> Nearly all of these init scripts are broken in many ways. Almost nothing
> works. I would be shocked if any of this passes requirements of the
> Debian policy.
> 
> There is no stdout or stderr provided from the init script. Failures
> result in no output. Success results in no output. There is no
> error/sanity checking.
> 
> stop|status|restart|try-restart|force-reload are all broken.
> 
> start is broken on multiple init scripts.
> 
> The status argument fails and is not implemented on any of them that I
> can see.
> 
> The stop argument fails to stop running daemons/programs.
> 
> The only courier init script which behaves somewhat reasonably is
> /etc/init.d/courier-authdaemon
> 
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages courier-mta depends on:
> ii  courier-authlib0.66.4-7
> ii  courier-base   0.75.0-18
> ii  debconf [debconf-2.0]  1.5.59
> ii  libc6  2.22-7
> ii  libcourier-unicode11.4-2
> ii  libgcc11:5.3.1-14
> ii  libgdbm3   1.8.3-13.1
> ii  libidn11   1.32-3
> ii  libnet-cidr-perl   0.17-1
> ii  libperl5.225.22.1-10
> ii  libstdc++6 5.3.1-14
> ii  sysvinit-utils 2.88dsf-59.3
> 
> courier-mta recommends no packages.
> 
> Versions of packages courier-mta suggests:
> ii  bsd-mailx [mail-reader]  8.1.2-0.20160123cvs-2
> ii  courier-doc  0.75.0-18
> ii  courier-filter-perl  0.200+ds-4
> pn  couriergrey  
> ii  emacs24 [mail-reader]24.5+1-6+b2
> ii  mutt [mail-reader]   1.5.24-1+b1
> ii  s-nail [mail-reader] 14.8.8-1
> 
> -- Configuration Files:
> /etc/courier/aliases/system [Errno 13] Permission denied:
> u'/etc/courier/aliases/system'
> /etc/courier/courierd changed [not included]
> /etc/courier/dsnheader.txt changed [not included]
> /etc/courier/esmtpauthclient [Errno 13] Permission denied:
> u'/etc/courier/esmtpauthclient'
> /etc/courier/esmtpd changed [not included]
> /etc/courier/esmtpd-msa changed [not included]
> /etc/courier/esmtpd-ssl changed [not included]
> /etc/courier/esmtpd.cnf [Errno 13] Permission denied:
> u'/etc/courier/esmtpd.cnf'
> /etc/courier/smtpaccess/default [Errno 13] Permission denied:
> u'/etc/courier/smtpaccess/default'
> /etc/init.d/courier-mta changed [not included]
> /etc/init.d/courier-mta-ssl changed [not included]
> 
> -- debconf information excluded
> 

Bug#821350: dh-golang: generates rubbish in Built-Using; errors on invocation

[Michael Stapelberg]

I unfortunately don’t have time to test this package before uploading.

If anyone has the time to either contribute a working and comprehensive
test suite for the package and/or take over maintenance, that’d be much
appreciated.

I’m merely uploading these patches as-is to avoid blocking progress on the
package.

On Tue, Apr 19, 2016 at 11:10 PM, Dmitry Smirnov  wrote:

> On Tuesday, 19 April 2016 10:32:58 PM AEST Michael Stapelberg wrote:
> > Dmitry, please let us know if the patch works for you and I’ll be happy
> to
> > upload it.
>
> Hi Michael,
>
> Unfortunately I won't be able to spare time for testing at least till
> weekend.
> Please upload if patch looks good for you -- I doubt it could make
> situation
> worse than it already is.
>
> I should trust you to remember to test this important package before every
> upload. ;)
>
> Uploaded or not I'll have a look at first opportunity. Thanks.
>
> --
> Cheers,
>  Dmitry Smirnov.
>
> ---
>
> Truth — Something somehow discreditable to someone.
> -- H. L. Mencken, 1949
>



-- 
Best regards,
Michael

Bug#821933: marked as done (golang-github-azure-azure-sdk-for-go: package FTBFS due to fail of testsuite)

[Debian Bug Tracking System]

Your message dated Thu, 21 Apr 2016 07:19:03 +
with message-id 
and subject line Bug#821933: fixed in golang-github-azure-azure-sdk-for-go 
2.1.1~beta-1
has caused the Debian Bug report #821933,
regarding golang-github-azure-azure-sdk-for-go: package FTBFS due to fail of 
testsuite
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
821933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-azure-azure-sdk-for-go
Version: 1.2~git20150611.0.97d9593-2
Severity: serious
Justification: fails to build from source

Hi,

I've tried to build the package from the group repo and detected that
it currently fails to build:


=== RUN   TestTLS11Server
--- PASS: TestTLS11Server (0.04s)
=== RUN   TestAESGCM
--- PASS: TestAESGCM (0.02s)
=== RUN   TestRunServer
--- PASS: TestRunServer (0.00s)
=== RUN   TestSplitPreMasterSecret
--- PASS: TestSplitPreMasterSecret (0.00s)
=== RUN   TestKeysFromPreMasterSecret
--- PASS: TestKeysFromPreMasterSecret (0.00s)
=== RUN   TestX509KeyPair
--- PASS: TestX509KeyPair (0.04s)
=== RUN   TestX509MixedKeyPair
--- PASS: TestX509MixedKeyPair (0.02s)
FAIL
FAILgithub.com/Azure/azure-sdk-for-go/core/tls  0.397s
=== RUN   TestIsResourceNotFoundError
--- PASS: TestIsResourceNotFoundError (0.00s)
PASS
ok  github.com/Azure/azure-sdk-for-go/management0.011s
?   github.com/Azure/azure-sdk-for-go/management/hostedservice  [no 
test files]
?   github.com/Azure/azure-sdk-for-go/management/location   [no test files]
?   github.com/Azure/azure-sdk-for-go/management/networksecuritygroup   
[no test files]
?   github.com/Azure/azure-sdk-for-go/management/osimage[no test files]
?   github.com/Azure/azure-sdk-for-go/management/testutils  [no test files]
=== RUN   TestDocumentedDeploymentRequest
--- PASS: TestDocumentedDeploymentRequest (0.00s)


Thanks,
DS

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

Kernel: Linux 4.4.0-1-amd64 (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: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: golang-github-azure-azure-sdk-for-go
Source-Version: 2.1.1~beta-1

We believe that the bug you reported is fixed in the latest version of
golang-github-azure-azure-sdk-for-go, 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 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated 
golang-github-azure-azure-sdk-for-go package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Apr 2016 20:35:26 +0200
Source: golang-github-azure-azure-sdk-for-go
Binary: golang-github-azure-azure-sdk-for-go-dev
Architecture: source all
Version: 2.1.1~beta-1
Distribution: experimental
Urgency: medium
Maintainer: pkg-go 
Changed-By: Daniel Stender 
Description:
 golang-github-azure-azure-sdk-for-go-dev - Microsoft Azure SDK for Go
Closes: 821832 821933
Changes:
 golang-github-azure-azure-sdk-for-go (2.1.1~beta-1) experimental; 
urgency=medium
 .
   * Team upload.
   [ Tianon Gravi ]
   * Adjust Build-Depends relation ordering to appease the buildds
   [ Daniel Stender ]
   * New upstream release (Closes: #821832).
 + added golang-golang-x-crypto-dev to deps in deb/control.
 + bumped version of go-autorest deb in deb/control.
 + dropped export for DH_GOLANG_INSTALL_ALL in deb/rules.
   * deb/rules: added failsafe for dh_auto_test (Closes: #821933).
Checksums-Sha1:
 e2e5f80fd589eb05dba4bffcbf4bb242b78a59e4 2479 
golang-github-azure-azure-sdk-for-go_2.1.1~beta-1.dsc
 0784d0ccb65d5f5723fbd2172b82d8aede465edd 380948 
golang-github-azure-azure-sdk-for-go_2.1.1~beta.orig.tar.xz
 5f1fb5b69df1e4d647c2a75f6a5863e12612d535 2768 
golang-github-azure-azure-sdk-for-go_2.1.1~beta-1.debian.tar.xz
 

Bug#778599: Vulnerabilities in nanohttp

[Moritz Muehlenhoff]

B0;115;0cOn Thu, Apr 21, 2016 at 06:58:18AM +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Wed, Apr 20, 2016 at 11:01:29PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2015-03-15 06:42:08 [+0100], Salvatore Bonaccorso wrote:
> > > On Tue, Feb 17, 2015 at 10:07:06AM +, Patrick Coleman wrote:
> > > > * Remote null pointer dereference
> > > > A remote user can cause a null pointer dereference by sending a
> > > > malformed Authorization: header.
> > > > http://patrick.ld.net.au/libcsoap/nanohttp-nullp-1.patch
> > > 
> > > For this issue CVE-2015-2297 was assigned.
> > 
> > What do we do here? That bug is open for slightly over a year with a
> > security tag and zero activity. We had two patches here which do now
> > 404. popcon goes down and it could have something todo with not beeing
> > part of stable. The current binary depends on libssl1.0.0 which has no
> > source, a binNMU would fix it (just tried, that is why I stumbled over
> > it).
> > So we fix this? Do we remove it? In case we want to fix, has someone a
> > copy of the two patches?
> 
> Given the package looks unmaintained (last update by maintainer back
> in 20 Jun 2010, I think it is the best option to remove the package as
> well from unstable). It is already gone in testing, so will not be
> included in stretch and neither was in jessie.

Ack, let's remove this.

Cheers,
Moritz

Bug#822085: RM: root-system: RoQA unmaintained, RC-buggy, FTBFS, blocks removal of old packages

[Tobias Frost]

Source: root-system
Severity: serious
Justification: libpng1.2-removal

Dear maintainer / ftp-master,

root-system is RC-Buggy with 2 RC-Bugs:
 #778108 root-system: ftbfs with GCC-5
 #809874 root-system: FTBFS with libpng16

Both bugs do not have any maintainer response or action, the gcc bug is more
than one year old.

As it is now blocking other packages, I raise the question if it should be
removed from Debian.

Please response to this bug, if there is no response within a week, I will
reassign this bug to ftp.debian.org

Please note, that if decide to keep it, you need to fix your pacakge ASAP.
The removal of libpng1.2 will NOT wait for root-system, and when removed,
at least the binary packages must go with it. (Which can lead to src removal)

Thanks for your understanding,

-- 
tobi

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

Kernel: Linux 4.3.0-1-amd64 (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: systemd (via /run/systemd/system)

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

[Tobias Frost]

On Sun, 17 Apr 2016 15:24:28 +0200 Muammar El Khatib  wrote:
> Hi Tobias,
> 
> On Sun, Apr 17, 2016 at 3:18 PM, Tobias Frost 
wrote:
> > Maybe we should let it go?
> 
> Yes. There is other option, because some people has forked SMC. The
> project is called TSC: https://github.com/Secretchronicles/TSC/.  But
> there is no support for CEGUI 0.8.x yet.
> 
> Cheers,
> 
> 
> -- 
> Muammar El Khatib.
> http://muammar.me
> 
> 

Sorry, I overread the "Yes."...
As the rest of it confuses me: Does that mean you are OK with filing an
RM at this point of time?
(We can also file a RM for the binaries alone, but there is no
guarantee that the source will be retained; an ftp-master might think
it is cruft and delete it)

Let me know! (libpng1.2 removal, you know...)

-- tobi