Bug#843247: marked as done (opendmarc: Fails to upgrade)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2016 07:49:24 +
with message-id 
and subject line Bug#843247: fixed in opendmarc 1.3.2~Beta0+dfsg-3
has caused the Debian Bug report #843247,
regarding opendmarc: Fails to upgrade
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.)


-- 
843247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendmarc
Version: 1.3.2~Beta0+dfsg-2
Severity: serious

Hi,

I just ran into this when upgrading:
Setting up opendmarc (1.3.2~Beta0+dfsg-2) ...
Installing new version of config file /etc/default/opendmarc ...
/lib/opendmarc/opendmarc.service.generate: 83: 
/lib/opendmarc/opendmarc.service.generate: systemctl: not found
/lib/opendmarc/opendmarc.service.generate: 84: 
/lib/opendmarc/opendmarc.service.generate: systemctl: not found
dpkg: error processing package opendmarc (--configure):
 subprocess installed post-installation script returned error exit status 127

I do not have systemd installed.

When I then try to upgrade it again, it works.


Kurt
--- End Message ---
--- Begin Message ---
Source: opendmarc
Source-Version: 1.3.2~Beta0+dfsg-3

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated opendmarc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Nov 2016 00:48:22 -0500
Source: opendmarc
Binary: opendmarc libopendmarc2 libopendmarc-dev rddmarc
Architecture: source amd64 all
Version: 1.3.2~Beta0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Scott Kitterman 
Changed-By: Scott Kitterman 
Description:
 libopendmarc-dev - Headers and development libraries for the OpenDMARC library
 libopendmarc2 - Library for DMARC validation and reporting
 opendmarc  - Milter implementation of DMARC
 rddmarc- Sample DMARC report processing scripts collection
Closes: 843247 843327 843330 843366
Changes:
 opendmarc (1.3.2~Beta0+dfsg-3) unstable; urgency=medium
 .
   * Fixup opendmarc.service installation and update based on changes from the
 opendkim package (Closes: #843247, #843327)
 - /etc/default/opendmarc will be removed on systems using systemd (see
   opendmarc.NEWS)
   * Create run dir on install in postinst
   * Only override dh_fixperms instead of dh_install as it is more correct and
 only override for -arch, not indep to fix indep only build (Closes:
 #843366)
 - Thanks to Santiago Vila for the report and the fix
   * Cherry-pick additional changes from upstream bug tracker:
 - Correct processing if a domain has a size limit on its ruf address
   https://sourceforge.net/p/opendmarc/tickets/174/
 - Correct error in help processing for opendmarc-reports
   https://sourceforge.net/p/opendmarc/tickets/181/
 - Fix segfaults when invoked for local/ignored hosts (Closes: #843330)
   https://sourceforge.net/p/opendmarc/tickets/185/
 - Fix bug in dmarcf_config_reload function
   https://sourceforge.net/p/opendmarc/tickets/186/
 - Fix compile and functional fix for SPF result logging (more complete
   replacement for current fix_compile.patch)
   https://sourceforge.net/p/opendmarc/tickets/187/
 - Fix issue with deleting zip file too early in opendmarc-reports
   https://sourceforge.net/p/opendmarc/tickets/188/
 - Fix history file SPF results (use AR format)
   https://sourceforge.net/p/opendmarc/tickets/195/
 - Fix issue with wrong DMARC state in Auth-Res header
   https://sourceforge.net/p/opendmarc/tickets/194/
 - Fix RecordAllMessages = false so it works
   https://sourceforge.net/p/opendmarc/tickets/196/
Checksums-Sha1:
 af2d6362947b432ecf21be5e13ceb9a8a473d20c 2039 opendmarc_1.3.2~Beta0+dfsg-3.dsc
 5ab5917b765881dd6dd6ea54855a7cc92011b87a 20667 
opendmarc_1.3.2~Beta0+dfsg-3.diff.gz
 5f177ddb3270efa53c51a42014abba4f222c453b 68902 

Bug#843366: marked as done (opendmarc: FTBFS when built with dpkg-buildpackage -A (chmod: No such file or directory))

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2016 07:49:24 +
with message-id 
and subject line Bug#843366: fixed in opendmarc 1.3.2~Beta0+dfsg-3
has caused the Debian Bug report #843366,
regarding opendmarc: FTBFS when built with dpkg-buildpackage -A (chmod: No such 
file or directory)
to be marked as done.

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

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


-- 
843366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opendmarc
Version: 1.3.2~Beta0+dfsg-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with quilt, --with autoreconf --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   dh_quilt_patch -i -O--parallel
Applying patch fix-python-interpreter.diff
patching file contrib/rddmarc/dmarcfail.py

Applying patch ticket153.patch
patching file reports/opendmarc-reports.in

Applying patch ticket166.patch
patching file reports/opendmarc-reports.in

[... snipped ...]

make[3]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg/reports'
make[2]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg/reports'
Making install in opendmarc
make[2]: Entering directory '/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc'
Making install in tests
make[3]: Entering directory 
'/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc/tests'
make[4]: Entering directory 
'/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc/tests'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory 
'/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc/tests'
make[3]: Leaving directory 
'/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc/tests'
make[3]: Entering directory '/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc'
make[4]: Entering directory '/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc'
 /bin/mkdir -p '/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/sbin'
  /bin/sh ../libtool   --mode=install /usr/bin/install -c opendmarc 
opendmarc-check '/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/sbin'
libtool: warning: '../libopendmarc/libopendmarc.la' has not been installed in 
'/usr/lib'
libtool: install: /usr/bin/install -c .libs/opendmarc 
/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/sbin/opendmarc
libtool: warning: '../libopendmarc/libopendmarc.la' has not been installed in 
'/usr/lib'
libtool: install: /usr/bin/install -c .libs/opendmarc-check 
/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/sbin/opendmarc-check
 /bin/mkdir -p 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/share/doc/opendmarc'
 /usr/bin/install -c -m 644 opendmarc.conf.sample 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/share/doc/opendmarc'
 /bin/mkdir -p 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/share/man/man5'
 /usr/bin/install -c -m 644 opendmarc.conf.5 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/share/man/man5'
 /bin/mkdir -p 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/share/man/man8'
 /usr/bin/install -c -m 644 opendmarc.8 opendmarc-check.8 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/share/man/man8'
make[4]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc'
make[3]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc'
make[2]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg/opendmarc'
make[2]: Entering directory '/<>/opendmarc-1.3.2~Beta0+dfsg'
make[3]: Entering directory '/<>/opendmarc-1.3.2~Beta0+dfsg'
make[3]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/share/doc/opendmarc'
 /usr/bin/install -c -m 644 LICENSE LICENSE.Sendmail 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/tmp/usr/share/doc/opendmarc'
make[3]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg'
make[2]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg'
make[1]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg'
   debian/rules override_dh_install
make[1]: Entering directory '/<>/opendmarc-1.3.2~Beta0+dfsg'
dh_install
chmod +x 
/<>/opendmarc-1.3.2~Beta0+dfsg/debian/opendmarc/lib/opendmarc/opendmarc.service.generate
chmod: cannot access 
'/<>/opendmarc-1.3.2~Beta0+dfsg/debian/opendmarc/lib/opendmarc/opendmarc.service.generate':
 No such file or directory
debian/rules:25: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>/opendmarc-1.3.2~Beta0+dfsg'

Bug#843327: marked as done (opendmarc: generated systemd service file is completely non-functional)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2016 07:49:24 +
with message-id 
and subject line Bug#843327: fixed in opendmarc 1.3.2~Beta0+dfsg-3
has caused the Debian Bug report #843327,
regarding opendmarc: generated systemd service file is completely non-functional
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.)


-- 
843327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendmarc
Version: 1.3.2~Beta0+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The opendmarc.service file generated by opendmarc ends up trying to invoke
/usr/sbin/opendkim rather than /usr/sbin/opendmarc to start the daemon.  This
is clearly wrong (luckily it doesn't actually start opendkim, because opendkim
barfs at being given a conf file with opendmarc options).

This is coming from the opendmarc.service.generate script's ExecStart line:

echo "ExecStart=/usr/sbin/opendkim -p $SOCKET $DAEMON_OPTS -x 
/etc/$NAME.conf -u $USER -P $PIDFILE" >> $SERVICEFILE.new

That has at least three problems that I ran into trying to fix this:

- /usr/sbin/opendkim should be /usr/sbin/opendmarc

- the -x flag should be -c

- the -p $SOCKET bit is sometimes wrong; /etc/default/opendmarc says SOCKET
  overrides the Socket setting in the config file, and the
  /etc/init.d/opendmarc script indeed handles this.  If I fix the above two
  issues but comment out SOCKET in /etc/default/opendmarc (because I have the
  Socket specified in /etc/opendmarc.conf), I get a failure to start with bad
  argument output because SOCKET isn't set, so there is no argument following
  the "-p".


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

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

Versions of packages opendmarc depends on:
ii  adduser 3.115
ii  libbsd0 0.8.3-1
ii  libc6   2.24-5
ii  libmilter1.0.1  8.15.2-6
ii  libopendmarc2   1.3.2~Beta0+dfsg-2
ii  libspf2-2   1.2.10-7+b1
ii  lsb-base9.20161016
ii  publicsuffix20160826-1

Versions of packages opendmarc recommends:
ii  libdbd-mysql-perl 4.037-5
ii  libdbi-perl   1.636-1+b1
ii  libhttp-message-perl  6.11-1
ii  libopendbx1   1.4.6-11
pn  libopendbx1-mysql 
ii  libswitch-perl2.17-2
ii  perl  5.24.1~rc3-3
pn  perl:any  

opendmarc suggests no packages.

-- Configuration Files:
/etc/opendmarc.conf changed:
PidFile /var/run/opendmarc.pid
RejectFailures false
Syslog true
IgnoreAuthenticatedClients true
UMask 
Socket local:/var/spool/postfix/opendmarc/opendmarc.sock
HistoryFile /var/lib/opendmarc/history.dat
UserID opendmarc:opendmarc
PublicSuffixList /usr/share/publicsuffix/


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: opendmarc
Source-Version: 1.3.2~Beta0+dfsg-3

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated opendmarc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Nov 2016 00:48:22 -0500
Source: opendmarc
Binary: opendmarc libopendmarc2 libopendmarc-dev rddmarc
Architecture: source amd64 all
Version: 1.3.2~Beta0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Scott Kitterman 
Changed-By: Scott Kitterman 
Description:
 libopendmarc-dev - Headers and development libraries for the OpenDMARC library
 libopendmarc2 - Library for DMARC validation and reporting
 opendmarc  - Milter implementation of DMARC
 rddmarc- Sample DMARC report processing scripts collection
Closes: 843247 843327 843330 843366
Changes:
 opendmarc 

Bug#837485: marked as done (golang-1.6: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2016 07:39:56 +
with message-id 
and subject line Bug#843598: Removed package(s) from unstable
has caused the Debian Bug report #837485,
regarding golang-1.6: FTBFS with bindnow and PIE enabled
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.)


-- 
837485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-1.6
Version: 1.6.3-1
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening
Tags: patch

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
# Testing race detector
ok  runtime/race2.396s
ok  flag1.005s
ok  os/exec 2.014s
==3637==ERROR: ThreadSanitizer failed to allocate 0x271 (4096)
bytes at address 175c5ff8b0b00
(errno: 12)
unexpected fault address 0x0
fatal error: fault
[signal 0x7 code=0x80 addr=0x0 pc=0x55717f9dd245]

goroutine 1 [running, locked to thread]:
runtime.throw(0x0, 0x55717f808e88)
/<>/src/runtime/panic.go:547 +0x90
fp=0x7fff183185a0 sp=0x7fff18318588

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/<>/src/runtime/asm_amd64.s:1998 +0x1
fp=0xc820038fb8 sp=0xc820038fb0
exit status 2
FAIL_/<>/misc/cgo/test 0.005s
2016/09/05 20:38:54 Failed: exit status 1
==2753==ERROR: ThreadSanitizer failed to allocate 0x26e8000 (40796160)
bytes at address 17818149c4680
(errno: 12)
unexpected fault address 0x0
fatal error: fault
[signal 0x7 code=0x80 addr=0x0 pc=0x560604f0c0e5]

goroutine 1 [running, locked to thread]:
runtime.throw(0x0, 0x560604de0378)
/<>/src/runtime/panic.go:547 +0x90
fp=0x7ffe958b44c0 sp=0x7ffe958b44a8

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/<>/src/runtime/asm_amd64.s:1998 +0x1
FAILflag0.005s
==3009==ERROR: ThreadSanitizer failed to allocate 0x272 (41025536)
bytes at address 175e931970700
(errno: 12)
unexpected fault address 0x0
fatal error: fault
[signal 0x7 code=0x80 addr=0x0 pc=0x557a4c0f6405]

goroutine 1 [running, locked to thread]:
runtime.throw(0x0, 0x557a4bd46fa8)
/<>/src/runtime/panic.go:547 +0x90
fp=0x7ffdd2b7e910 sp=0x7ffdd2b7e8f8

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/<>/src/runtime/asm_amd64.s:1998 +0x1
FAILos/exec 0.006s
2016/09/05 20:38:54 Failed: exit status 1


...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/golang-1.6_1.6.3-1_amd64.build.gz

Ubuntu fixed the issue by disabling PIE for that test-case:
https://patches.ubuntu.com/g/golang-1.6/golang-1.6_1.6.3-1ubuntu1.patch

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Version: 1.6.3-2+rm

Dear submitter,

as the package golang-1.6 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/843598

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#843481: marked as done (asn1c: FTBFS: cannot stat 'asn1c-usage.pdf': No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2016 07:18:32 +
with message-id 
and subject line Bug#843481: fixed in asn1c 0.9.27+dfsg-3
has caused the Debian Bug report #843481,
regarding asn1c: FTBFS: cannot stat 'asn1c-usage.pdf': No such file or directory
to be marked as done.

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

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


-- 
843481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asn1c
Version: 0.9.27+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of asn1c covering only its main (architecture-dependent) binary
package have been failing (except, for some reason, on mips):

  Making install in docsrc
  make[4]: Entering directory '/«BUILDDIR»/asn1c-0.9.27+dfsg/doc/docsrc'
  make[5]: Entering directory '/«BUILDDIR»/asn1c-0.9.27+dfsg/doc/docsrc'
  make[5]: Nothing to be done for 'install-exec-am'.
  mkdir -p /«BUILDDIR»/asn1c-0.9.27+dfsg/debian/tmp/usr/share/doc/asn1c-doc
  cp -a asn1c-usage.pdf 
/«BUILDDIR»/asn1c-0.9.27+dfsg/debian/tmp/usr/share/doc/asn1c-doc
  cp: cannot stat 'asn1c-usage.pdf': No such file or directory
  Makefile:458: recipe for target 'install-data-local' failed
  make[5]: *** [install-data-local] Error 1

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: asn1c
Source-Version: 0.9.27+dfsg-3

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

Debian distribution maintenance software
pp.
Eugene Seliverstov  (supplier of updated asn1c package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Nov 2016 23:51:31 +0300
Source: asn1c
Binary: asn1c asn1c-doc
Architecture: source
Version: 0.9.27+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Eugene Seliverstov 
Changed-By: Eugene Seliverstov 
Description:
 asn1c  - ASN.1 compiler for C
 asn1c-doc  - ASN.1 compiler for C
Closes: 843481
Changes:
 asn1c (0.9.27+dfsg-3) unstable; urgency=medium
 .
   * Fixed FTBFS: docs install with arch/indep build (closes: #843481)
   * Fixed FTBFS: missing texlive-luatex build depend for reproducible build
   * Fixed mistypes at binary, manpage
Checksums-Sha1:
 fe154c6473d2f30ad006d6275ccfadaafa51a481 2080 asn1c_0.9.27+dfsg-3.dsc
 045423a922c03abf7edca7c99f13b9d602cf84f9 6976 asn1c_0.9.27+dfsg-3.debian.tar.xz
Checksums-Sha256:
 9affe90859fb942cc0cc532f2226c70afc25199bf96b22f00bdc03f50a7f9049 2080 
asn1c_0.9.27+dfsg-3.dsc
 384c8dcdf08a376e6c1f64b6ff88b68b15f237e87ee57aa6d31e8c6f60730560 6976 
asn1c_0.9.27+dfsg-3.debian.tar.xz
Files:
 5cc3139b32318c53d0d5ff150d95 2080 devel extra asn1c_0.9.27+dfsg-3.dsc
 9a2bf8f4639b9c5cbaa437e19ef6cba0 6976 devel extra 
asn1c_0.9.27+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYIXTjAAoJEPNPCXROn13Z6X0QAJp3FtxXWGpYto9mip+XPvS/
4LzTbwwy88EcFDPSKPymWCvpazdwSJblNIgTDQiDBChL8II5gg7SZVamhBT63BqB
ozytzsIgqm0xS6gdl7I1Q7Ebe+gwmieP2rOERKJ5spquRlAma4UM8bkaBhoh6ngC
ACTBwq4oW8oZSHLqOetjBC6phNK9/SFdgWD4/B+/75JUSOY6+jlg1+wxpcmlIPVk
tWMPj98p1Ux8p09aX4M3Lezc3celrUtbjvbe2BdmEXXoCYnfVsI/UJkqKHjysRIW
MdfPDzQ/tJcZ2cL69NoMJ+E+WVGHm8sE3xoMJTF6I7dkB6bb01mwpXQ9csio5aTT
cv6KvUIM5jlG9e8Bd937cwNrwAMi60GAX2ln5WP6FKFf0IoTjjqhoV1HICe3SU2o
5e3zc7sRe0xE2poyk95JA+f4roZWIBPVx0wdvSoopJeUffqtHSOIgHhW1QbRW8Sm
Ost3c6EUmL0RCbs+xw/RZKWd27fIEQeDJymnZxhLbvQQkj+jgJiko9QK2h5qKjvI
fEBU0vXDSyTjURbOivkQGc+pQtlH7YnABxPoNQNkpqYRy9xKg/G+/3Svr6FOfsvp
Q4Z1MhY7c5U70+N8MjWwu/9OPGhIlh5Mjmmn1l5sKTCrpkP93gFeDR8IuIP8c7ih
rPQhJu67PTu+YTuWPy7M
=g8mr
-END PGP SIGNATURE End Message ---

Bug#831236: klog: FTBFS: dh_install: missing files, aborting

[FanJun Kong]

Hi

fixed and upload package here:
https://mentors.debian.net/package/klog

Jaime, could you help me to review it?

Thanks very much

FanJun Kong
BH1SCW

Bug#828558: marked as done (sslsplit: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 08 Nov 2016 01:51:52 +
with message-id 
and subject line Bug#828558: fixed in sslsplit 0.5.0+dfsg-1
has caused the Debian Bug report #828558,
regarding sslsplit: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sslsplit
Version: 0.4.11+dfsg-2
Severity: important
Control: block 827061 by -1

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: sslsplit
Source-Version: 0.5.0+dfsg-1

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated sslsplit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Nov 2016 02:23:01 +0100
Source: sslsplit
Binary: sslsplit
Architecture: source
Version: 0.5.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description:
 sslsplit   - transparent and scalable SSL/TLS interception
Closes: 828558
Changes:
 sslsplit (0.5.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 0.5.0+dfsg
   * Rebase patches; drop NO_SSL3_METHOD patch
   * Drop session.pem patch, add OpenSSL 1.1 patch (Closes: #828558)
Checksums-Sha1:
 2c81df17d3b07c9ef2bb751bcc7cad5674e15904 1903 sslsplit_0.5.0+dfsg-1.dsc
 99ed585f3ce5002c3fcb013e4a24712585ebf0c3 106059 
sslsplit_0.5.0+dfsg.orig.tar.bz2
 16d15f54cc1cfb37c68e61dbd1a3ebc78f367cae 8140 
sslsplit_0.5.0+dfsg-1.debian.tar.xz
Checksums-Sha256:
 2ae155810665b58fc45395a4d16eaa9bc92de0189ec6497a7175db02b2398080 1903 
sslsplit_0.5.0+dfsg-1.dsc
 d7c5994474886218e0a0d7b1f2bf4b306f02b63a9078bb365cdc60e6dd508f04 106059 
sslsplit_0.5.0+dfsg.orig.tar.bz2
 c5439a9d03f72df452dcc5303b44fd150b99f861f23a41c8ba08863731715d82 8140 
sslsplit_0.5.0+dfsg-1.debian.tar.xz
Files:
 e0f66686f83f5048047d8e4c9161d18f 1903 net extra sslsplit_0.5.0+dfsg-1.dsc
 10ffe854b8454753cb9a5f2ed614f256 106059 net extra 
sslsplit_0.5.0+dfsg.orig.tar.bz2
 adab2e8d8be02eb3e15ded1787989d66 8140 net extra 
sslsplit_0.5.0+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYISquAAoJEHW3EGNcITp+Cj4P/Aosa29Inx1rUL4zTy+CB726
zOGvKIbHwx6M109IOlIHM6lBnY2gocdSz7+ac+8a4QNma+8KLnriSibvUsio4dTB
9k2THTxQIUHh54gWNrfcX3i13WhQ1Mhmre53/a0YUn+/wdLSfUHcAZMs9uk5urQZ
t/yiE1FhINKowtoRSfa7r2iv4rDziQeEexJ0kdY6ym33vDQcvtLD8H44Gkj5uw62
X2td9NdMTPpcI3a1IivrHUzv5vZa752I7+D6z10Z3vDrKoUtyOqGwBohEoC4IQwD
mi6jxcerRaYe+HY9NcUG9tSF+5lzs0/GSV0n8+TGI3gZqk3dcOmYHC0O4wp4M9LP
YHDnA7HFXWMRlPXAaULFBUvEcrnT661P/yvIhGrcvhFaFlAGVRzsCKjBVsOS75JZ
272043aCV004fC3dx82uEgKUHlpqBkLXqLMUtEl+1kr7TY8uYmYsJVGFpbDPTqGt
1RzwTW/LGdhMTIFGZu7ox2JGCehAMDbAMtBU6r7zsXnX1noIEsSrHcwnQVUTAuFR
NZek8Y/RDZJzEBMH+ozHDdZdMkwkEo7ZG6j7wP/ZZ8+JMDmd9clL78nlkyGrzeuQ
7NizyexvIVRydZcpg6oQOWpB0XWy7l8u0yXjUojw22YQMcdMl48zw5K+SizrQ4cm
pxaRyDG1WzLjXKnOb+VR
=+7rA
-END PGP SIGNATURE End Message ---

Bug#828252: qtcreator is marked for autoremoval from testing

[Christian Hofstaedtler]

Ondřej,

* Ondřej Surý  [161106 21:12]:
> In the end it was very easy (hopefully) - the OpenSSL module is optional
> and hopefully this won't break anything :). Ccing other botan1.10 users.
> 
> Please test with botan1.10 - 1.10.13-1 that just got uploaded to
> unstable.

Tested pdns 4.0.1-5 against the new botan1.10 1.10.13-1 and can
confirm that pdns still works (without rebuilding).

Thanks for taking care of this.

Cheers,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Processed: bug 828466 is forwarded to https://sourceforge.net/p/opendkim/patches/37/

[Debian Bug Tracking System]

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

> forwarded 828466 https://sourceforge.net/p/opendkim/patches/37/
Bug #828466 {Done: Scott Kitterman } [src:opendkim] 
opendkim: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://sourceforge.net/p/opendkim/patches/37/'.
> thanks
Stopping processing here.

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

Bug#837485: [pkg-golang-devel] Bug#837485: Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

[Niels Thykier]

Tianon Gravi:
> On 5 November 2016 at 09:00, Niels Thykier  wrote:
>> Cool! :)
>>
>> Should I file a bug against ftp.d.o, asking them to remove golang-1.6
>> from unstable? :)
> 
> If you're willing, that sounds great! (I always end up having to
> re-read the docs any time I use the BTS for more than simply replying,
> so I hadn't gotten around to doing so yet)
> 
> 
> ♥,
> - Tianon
>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
> 

Ack - filed as #843598.

Thanks,
~Niels

Bug#811960: pulseview NMU?

[Uwe Hermann]

Hi,

On Mon, Nov 07, 2016 at 04:25:14PM +, Jonathan McDowell wrote:
> Uwe, do you have any plans for this?

Yeah, might upload some new packages soonish, but long-term
I'd be happy to hand over the full sigrok suite of packages to another
interested + active developer, so I can focus more on upstream development.


Uwe.
-- 
http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org

Processed: severity of 843145 is grave

[Debian Bug Tracking System]

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

> severity 843145 grave
Bug #843145 [libjson-c-dev] files with the same name installed in / and /usr
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#837485: [pkg-golang-devel] Bug#837485: Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

[Tianon Gravi]

On 5 November 2016 at 09:00, Niels Thykier  wrote:
> Cool! :)
>
> Should I file a bug against ftp.d.o, asking them to remove golang-1.6
> from unstable? :)

If you're willing, that sounds great! (I always end up having to
re-read the docs any time I use the BTS for more than simply replying,
so I hadn't gotten around to doing so yet)


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#828252: qtcreator is marked for autoremoval from testing

[Lisandro Damián Nicanor Pérez Meyer]

On domingo, 6 de noviembre de 2016 21:12:14 ART Ondřej Surý wrote:
> In the end it was very easy (hopefully) - the OpenSSL module is optional
> and hopefully this won't break anything :). Ccing other botan1.10 users.
> 
> Please test with botan1.10 - 1.10.13-1 that just got uploaded to
> unstable.

Hi Ondřej! Will check for sure!


-- 
Una sola bomba nuclear puede arruinar el resto de tu día.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#833217: pycryptopp: Uses obsolete compressor for .deb data.tar member

[IOhannes m zmoelnig]

Package: src:pycryptopp
Followup-For: Bug #833217

Control: tags -1 pending
thanks

I've just uploaded an NMU with a fix (using gzip instead of bzip2) to DELAYED/5.

Please find the diff attached.

mfgards
IOhannes

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru pycryptopp-0.6.0.20120313/debian/changelog pycryptopp-0.6.0.20120313/debian/changelog
--- pycryptopp-0.6.0.20120313/debian/changelog	2013-08-22 23:07:55.0 +0200
+++ pycryptopp-0.6.0.20120313/debian/changelog	2016-11-07 22:43:57.0 +0100
@@ -1,3 +1,10 @@
+pycryptopp (0.6.0.20120313-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use gzip compression for package (Closes: #833217)
+
+ -- IOhannes m zmölnig (Debian/GNU)   Mon, 07 Nov 2016 22:43:57 +0100
+
 pycryptopp (0.6.0.20120313-1) unstable; urgency=low
 
   * Update debian/watch
diff -Nru pycryptopp-0.6.0.20120313/debian/rules pycryptopp-0.6.0.20120313/debian/rules
--- pycryptopp-0.6.0.20120313/debian/rules	2013-08-22 23:07:55.0 +0200
+++ pycryptopp-0.6.0.20120313/debian/rules	2016-11-07 22:43:57.0 +0100
@@ -69,7 +69,7 @@
 	dh_shlibdeps -a
 	dh_gencontrol -a
 	dh_md5sums -a
-	dh_builddeb -a -- -Z bzip2
+	dh_builddeb -a -- -Z gzip
 
 binary-indep:
 

Bug#837928: Bug#837925: usrmerge: fails to merge with molly-guard installed

[Jonas Smedegaard]

Quoting Francois Marier (2016-11-07 18:38:58)
> On 2016-11-02 at 03:02:29, Jonas Smedegaard wrote:
> > I am busy getting that system to production use (yes, stretch is not yet 
> > stable, but more stable than stable on the ARM device I use), but if you 
> > have suggestions for closer inspections that might help shed some light 
> > on this issue, please shoot - fast.
> 
> I reached out to Marco about this bug but have not heard back.
> 
> I don't know how dpkg-diverts are supposed to work in a usrmerge world and I
> can't see anything obviously wrong with the way it's done in molly-guard so
> I don't have any ideas on how to fix this.

I no longer believe this issue is tied to use with the usrmerge package: 
It happens also on freshly installed systems!

It seems that on a usrmerge+systemd system /bin/reboot is a symlink.

Perhaps molly-guard (in its use of dpkg-divert) wrongly assumes that if 
/bin/reboot already exists then it is _installed_ by a package rather 
than added in a package postinst script which seems to be the case with 
systemd (just guessing here, having looked closely at it).

 - Jonas

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

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

Bug#840494: marked as done (mono: FTBFS on mipsel: Assertion: should not be reached)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 21:27:20 +
with message-id 
and subject line Bug#840494: fixed in mono 4.6.1.3+dfsg-6
has caused the Debian Bug report #840494,
regarding mono: FTBFS on mipsel: Assertion: should not be reached
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.)


-- 
840494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mono
Version: 4.6.1.3+dfsg-4
Severity: serious

Your package failed to build on mipsel:

chmod +x _tmpinst/bin/al
if test -w /«BUILDDIR»/mono-4.6.1.3+dfsg/mcs; then :; else chmod -R +w 
/«BUILDDIR»/mono-4.6.1.3+dfsg/mcs; fi
cd /«BUILDDIR»/mono-4.6.1.3+dfsg/mcs && /usr/bin/make --no-print-directory -s 
NO_DIR_CHECK=1 PROFILES='binary_reference_assemblies net_4_x xbuild_12 
xbuild_14  ' CC='gcc' all-profiles
mkdir -p -- build/deps
build/profiles/basic.make:93: recipe for target 
'build/deps/basic-profile-check.exe' failed
make[7]: *** [build/deps/basic-profile-check.exe] Error 1
*** The compiler 'false' doesn't appear to be usable.
*** Trying the 'monolite' directory.
 long_mul R91 <- R76 R88
* Assertion: should not be reached at mini-mips.c:2229

Stacktrace:

  at  <0x>
  at System.IO.StreamReader.Init 
(System.IO.Stream,System.Text.Encoding,bool,int,bool) <0x00104>
  at System.IO.StreamReader..ctor 
(System.IO.Stream,System.Text.Encoding,bool,int,bool) <0x00100>
  at System.IO.StreamReader..ctor (System.IO.Stream,System.Text.Encoding) 
<0x00044>
  at System.IO.UnexceptionalStreamReader..ctor 
(System.IO.Stream,System.Text.Encoding) <0x00028>
  at (wrapper remoting-invoke-with-check) 
System.IO.UnexceptionalStreamReader..ctor 
(System.IO.Stream,System.Text.Encoding) <0x00070>
  at System.Console.SetupStreams (System.Text.Encoding,System.Text.Encoding) 
<0x002a8>
  at System.Console..cctor () <0x00250>
  at (wrapper runtime-invoke) object.runtime_invoke_void 
(object,intptr,intptr,intptr) <0x0008c>
  at  <0x>
  at Mono.CSharp.Driver.Main (string[]) <0x000a0>
  at (wrapper runtime-invoke) .runtime_invoke_int_object 
(object,intptr,intptr,intptr) <0x0013c>

Native stacktrace:

/«BUILDDIR»/mono-4.6.1.3+dfsg/mono/mini/mono() [0x4c2c68]

Debug info from gdb:


=
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=

Aborted
build/profiles/basic.make:93: recipe for target 
'build/deps/basic-profile-check.exe' failed

Full logs at
https://buildd.debian.org/status/logs.php?pkg=mono=mipsel

Emilio
--- End Message ---
--- Begin Message ---
Source: mono
Source-Version: 4.6.1.3+dfsg-6

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

Debian distribution maintenance software
pp.
Jo Shields  (supplier of updated mono 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: SHA1

Format: 1.8
Date: Mon, 07 Nov 2016 19:32:46 +
Source: mono
Binary: mono-runtime-common mono-runtime mono-runtime-sgen mono-runtime-boehm 
mono-runtime-dbg mono-utils ca-certificates-mono mono-complete libmono-2.0-1 
libmono-2.0-dev libmonosgen-2.0-1 libmonosgen-2.0-1-dbg libmonosgen-2.0-dev 
libmonoboehm-2.0-1 libmonoboehm-2.0-1-dbg libmonoboehm-2.0-dev libmono-profiler 
libmono-cil-dev libmono-posix4.0-cil libmono-codecontracts4.0-cil 
libmono-compilerservices-symbolwriter4.0-cil libmono-csharp4.0c-cil 
libmono-http4.0-cil libmono-cecil-private-cil libmono-webbrowser4.0-cil 
libmono-management4.0-cil libmono-messaging4.0-cil 
libmono-messaging-rabbitmq4.0-cil libmono-rabbitmq4.0-cil libmono-simd4.0-cil 
libmono-smdiagnostics0.0-cil libmono-corlib4.5-cil libmono-i18n4.0-all 
libmono-i18n4.0-cil libmono-i18n-cjk4.0-cil libmono-i18n-mideast4.0-cil 
libmono-i18n-other4.0-cil libmono-i18n-rare4.0-cil libmono-i18n-west4.0-cil 
libmono-parallel4.0-cil libmono-system4.0-cil 

Bug#843380: marked as done (libgvc6 fail to install on stretch)

[Debian Bug Tracking System]

Your message dated Mon, 7 Nov 2016 22:17:59 +0100
with message-id 

Bug#837402: [htcondor-debian] Bug#837402: Fix for the Condor PIE FTBFS

[Tim Theisen]

Hello,

Thank you for this fix. We needed to add -fnoPIC because of the severe 
performance impact on the benchmarks. Adding the -fPIE as well has a 
minimal performance impact. I will apply this patch to our upstream sources.


...Tim

On 11/04/2016 06:14 AM, Adrian Bunk wrote:

Control: tags -1 patch

A fix for the Condor PIE FTBFS is attached.

cu
Adrian



___
htcondor-debian mailing list
htcondor-deb...@cs.wisc.edu
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-debian


--
Tim Theisen
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736

Bug#828287: dsniff: FTBFS with openssl 1.1.0

[Christoph Biedl]

Sandro Tosi wrote...

> Hello Dug,
> in Debian we started the transition to OpenSSL 1.1.0: do you have any
> plan to port dsniff to that version?

Since I have some interest in keeping dsniff in Debian, I spent some
time on that bug.

The patch attached:
- replaces the access to struct elements with getter usage.
- disables 3des as it's no longer supported by OpenSSL.

It's pretty much untested and could also take a review.

Christoph


signature.asc
Description: Digital signature

Bug#828287: dsniff: FTBFS with openssl 1.1.0

[Christoph Biedl]

Christoph Biedl wrote...

> The patch attached:

Now really attached.
diff --git a/ssh.c b/ssh.c
index bb73ff3..ee6cb58 100644
--- a/ssh.c
+++ b/ssh.c
@@ -234,6 +234,8 @@ SSH_accept(SSH *ssh)
 	u_char *p, cipher, cookie[8], msg[1024];
 	u_int32_t num;
 	int i;
+	const BIGNUM *servkey_e, *servkey_n;
+	const BIGNUM *hostkey_e, *hostkey_n;
 
 	/* Generate anti-spoofing cookie. */
 	RAND_bytes(cookie, sizeof(cookie));
@@ -243,11 +245,13 @@ SSH_accept(SSH *ssh)
 	*p++ = SSH_SMSG_PUBLIC_KEY;			/* type */
 	memcpy(p, cookie, 8); p += 8;			/* cookie */
 	num = 768; PUTLONG(num, p);			/* servkey bits */
-	put_bn(ssh->ctx->servkey->e, );		/* servkey exponent */
-	put_bn(ssh->ctx->servkey->n, );		/* servkey modulus */
+	RSA_get0_key(ssh->ctx->servkey, _n, _e, NULL);
+	put_bn(servkey_e, );		/* servkey exponent */
+	put_bn(servkey_n, );		/* servkey modulus */
 	num = 1024; PUTLONG(num, p);			/* hostkey bits */
-	put_bn(ssh->ctx->hostkey->e, );		/* hostkey exponent */
-	put_bn(ssh->ctx->hostkey->n, );		/* hostkey modulus */
+	RSA_get0_key(ssh->ctx->hostkey, _n, _e, NULL);
+	put_bn(hostkey_e, );		/* hostkey exponent */
+	put_bn(hostkey_n, );		/* hostkey modulus */
 	num = 0; PUTLONG(num, p);			/* protocol flags */
 	num = ssh->ctx->encmask; PUTLONG(num, p);	/* ciphers */
 	num = ssh->ctx->authmask; PUTLONG(num, p);	/* authmask */
@@ -298,7 +302,7 @@ SSH_accept(SSH *ssh)
 	SKIP(p, i, 4);
 
 	/* Decrypt session key. */
-	if (BN_cmp(ssh->ctx->servkey->n, ssh->ctx->hostkey->n) > 0) {
+	if (BN_cmp(servkey_n, hostkey_n) > 0) {
 		rsa_private_decrypt(enckey, enckey, ssh->ctx->servkey);
 		rsa_private_decrypt(enckey, enckey, ssh->ctx->hostkey);
 	}
@@ -318,8 +322,8 @@ SSH_accept(SSH *ssh)
 	BN_clear_free(enckey);
 
 	/* Derive real session key using session id. */
-	if ((p = ssh_session_id(cookie, ssh->ctx->hostkey->n,
-ssh->ctx->servkey->n)) == NULL) {
+	if ((p = ssh_session_id(cookie, hostkey_n,
+servkey_n)) == NULL) {
 		warn("ssh_session_id");
 		return (-1);
 	}
@@ -328,10 +332,8 @@ SSH_accept(SSH *ssh)
 	}
 	/* Set cipher. */
 	if (cipher == SSH_CIPHER_3DES) {
-		ssh->estate = des3_init(ssh->sesskey, sizeof(ssh->sesskey));
-		ssh->dstate = des3_init(ssh->sesskey, sizeof(ssh->sesskey));
-		ssh->encrypt = des3_encrypt;
-		ssh->decrypt = des3_decrypt;
+		warnx("cipher 3des no longer supported");
+		return (-1);
 	}
 	else if (cipher == SSH_CIPHER_BLOWFISH) {
 		ssh->estate = blowfish_init(ssh->sesskey,sizeof(ssh->sesskey));
@@ -357,6 +359,8 @@ SSH_connect(SSH *ssh)
 	u_char *p, cipher, cookie[8], msg[1024];
 	u_int32_t num;
 	int i;
+	BIGNUM *servkey_n, *servkey_e;
+	BIGNUM *hostkey_n, *hostkey_e;
 
 	/* Get public key. */
 	if ((i = SSH_recv(ssh, pkt, sizeof(pkt))) <= 0) {
@@ -379,21 +383,23 @@ SSH_connect(SSH *ssh)
 
 	/* Get servkey. */
 	ssh->ctx->servkey = RSA_new();
-	ssh->ctx->servkey->n = BN_new();
-	ssh->ctx->servkey->e = BN_new();
+	servkey_n = BN_new();
+	servkey_e = BN_new();
+	RSA_set0_key(ssh->ctx->servkey, servkey_n, servkey_e, NULL);
 
 	SKIP(p, i, 4);
-	get_bn(ssh->ctx->servkey->e, , );
-	get_bn(ssh->ctx->servkey->n, , );
+	get_bn(servkey_e, , );
+	get_bn(servkey_n, , );
 
 	/* Get hostkey. */
 	ssh->ctx->hostkey = RSA_new();
-	ssh->ctx->hostkey->n = BN_new();
-	ssh->ctx->hostkey->e = BN_new();
+	hostkey_n = BN_new();
+	hostkey_e = BN_new();
+	RSA_set0_key(ssh->ctx->hostkey, hostkey_n, hostkey_e, NULL);
 
 	SKIP(p, i, 4);
-	get_bn(ssh->ctx->hostkey->e, , );
-	get_bn(ssh->ctx->hostkey->n, , );
+	get_bn(hostkey_e, , );
+	get_bn(hostkey_n, , );
 
 	/* Get cipher, auth masks. */
 	SKIP(p, i, 4);
@@ -405,8 +411,8 @@ SSH_connect(SSH *ssh)
 	RAND_bytes(ssh->sesskey, sizeof(ssh->sesskey));
 
 	/* Obfuscate with session id. */
-	if ((p = ssh_session_id(cookie, ssh->ctx->hostkey->n,
-ssh->ctx->servkey->n)) == NULL) {
+	if ((p = ssh_session_id(cookie, hostkey_n,
+servkey_n)) == NULL) {
 		warn("ssh_session_id");
 		return (-1);
 	}
@@ -422,7 +428,7 @@ SSH_connect(SSH *ssh)
 		else BN_add_word(bn, ssh->sesskey[i]);
 	}
 	/* Encrypt session key. */
-	if (BN_cmp(ssh->ctx->servkey->n, ssh->ctx->hostkey->n) < 0) {
+	if (BN_cmp(servkey_n, hostkey_n) < 0) {
 		rsa_public_encrypt(bn, bn, ssh->ctx->servkey);
 		rsa_public_encrypt(bn, bn, ssh->ctx->hostkey);
 	}
@@ -470,10 +476,8 @@ SSH_connect(SSH *ssh)
 		ssh->decrypt = blowfish_decrypt;
 	}
 	else if (cipher == SSH_CIPHER_3DES) {
-		ssh->estate = des3_init(ssh->sesskey, sizeof(ssh->sesskey));
-		ssh->dstate = des3_init(ssh->sesskey, sizeof(ssh->sesskey));
-		ssh->encrypt = des3_encrypt;
-		ssh->decrypt = des3_decrypt;
+		warnx("cipher 3des no longer supported");
+		return (-1);
 	}
 	/* Get server response. */
 	if ((i = SSH_recv(ssh, pkt, sizeof(pkt))) <= 0) {
diff --git a/sshcrypto.c b/sshcrypto.c
index 09a04e7..f66202d 100644
--- a/sshcrypto.c
+++ b/sshcrypto.c
@@ -28,10 +28,12 @@ struct blowfish_state {
 	u_char			iv[8];
 };
 
+#if 0
 struct des3_state {
 	des_key_schedule	k1, k2, k3;
 	des_cblock		iv1, iv2, iv3;
 };
+#endif
 
 void
 

Bug#843380: libgvc6 fail to install on stretch

[batta...@libero.it]

While checking for another bug, I found the cause of this also, libgd3 on my 
system was corrupted.After reinstalling it installation of libgvc6 has no 
problem.

Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

[Emmanuel Bourg]

Le 1/11/2016 à 07:58, 殷啟聰 a écrit :

> Here's the right link:
> 

I confirm the fix works. Do you know what triggered this error? Was this
caused by the recent changes to gradle-debian-helper?

Emmanuel Bourg

Bug#843532: dnssec-trigger: broken by OpenSSL 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 patch

On 2016-11-07 08:39:17 [-0500], Zack Weinberg wrote:
> Nov 07 08:34:17 moxana dnssec-triggerd[20281]: Nov 07 08:34:17 
> dnssec-triggerd[20281] error: could not set SSL_OP_NO_SSLv2 crypto 
> error:

could someone please check if the patch attached works? I am confident
but don't time todo it myself just now.

Sebastian
>From 05cd529e19d317b8bcc69f7d883873a27195b904 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Mon, 7 Nov 2016 20:59:11 +
Subject: [PATCH] dnssec-trigger: openssl 1.1.0 fixup

- SSL_OP_NO_SSLv2 / SSLv2 has been removed from openssl 1.1.0 and as
  such it can't be tested (the way it is) if disabling it worked.

- SSL_CTX_load_verify_locations() return 1 un success and 0 on failure.
  The check for the result code is bogus and has nothing to do with the
  switch to openssl 1.1.0 itself

- ERR_remove_state() and friends are NOPs in current openssl 1.1.0 due
  the threading model. This operations are nops therefore and do nothing
  and can be removed in a later version.

Signed-off-by: Sebastian Andrzej Siewior 
---
 riggerd/cfg.c  | 2 ++
 riggerd/net_help.c | 4 +++-
 riggerd/riggerd.c  | 2 ++
 riggerd/svr.c  | 2 ++
 4 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/riggerd/cfg.c b/riggerd/cfg.c
index 03f4f73..08b2028 100644
--- a/riggerd/cfg.c
+++ b/riggerd/cfg.c
@@ -540,9 +540,11 @@ cfg_setup_ctx_client(struct cfg* cfg, char* err, size_t errlen)
 	if(!ctx)
 		return ctx_err_ret(ctx, err, errlen,
 			"could not allocate SSL_CTX pointer");
+#if OPENSSL_VERSION_NUMBER < 0x1010
 	if(!(SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2) & SSL_OP_NO_SSLv2))
 		return ctx_err_ret(ctx, err, errlen, 
 			"could not set SSL_OP_NO_SSLv2");
+#endif
 	if(!SSL_CTX_use_certificate_file(ctx,c_cert,SSL_FILETYPE_PEM) ||
 		!SSL_CTX_use_PrivateKey_file(ctx,c_key,SSL_FILETYPE_PEM)
 		|| !SSL_CTX_check_private_key(ctx))
diff --git a/riggerd/net_help.c b/riggerd/net_help.c
index 21e79e7..b17486c 100644
--- a/riggerd/net_help.c
+++ b/riggerd/net_help.c
@@ -447,11 +447,13 @@ void* listen_sslctx_create(char* key, char* pem, char* verifypem)
 		return NULL;
 	}
 	/* no SSLv2 because has defects */
+#if OPENSSL_VERSION_NUMBER < 0x1010
 	if(!(SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2) & SSL_OP_NO_SSLv2)){
 		log_crypto_err("could not set SSL_OP_NO_SSLv2");
 		SSL_CTX_free(ctx);
 		return NULL;
 	}
+#endif
 	if(!SSL_CTX_use_certificate_file(ctx, pem, SSL_FILETYPE_PEM)) {
 		log_err("error for cert file: %s", pem);
 		log_crypto_err("error in SSL_CTX use_certificate_file");
@@ -517,7 +519,7 @@ void* connect_sslctx_create(char* key, char* pem, char* verifypem)
 		}
 	}
 	if(verifypem && verifypem[0]) {
-		if(!SSL_CTX_load_verify_locations(ctx, verifypem, NULL) != 1) {
+		if(SSL_CTX_load_verify_locations(ctx, verifypem, NULL) != 1) {
 			log_crypto_err("error in SSL_CTX verify");
 			SSL_CTX_free(ctx);
 			return NULL;
diff --git a/riggerd/riggerd.c b/riggerd/riggerd.c
index 9cb6023..2490a72 100644
--- a/riggerd/riggerd.c
+++ b/riggerd/riggerd.c
@@ -393,10 +393,12 @@ int main(int argc, char *argv[])
 #ifdef HAVE_OPENSSL_CONF_H
 	CONF_modules_free();
 #endif
+#if OPENSSL_VERSION_NUMBER < 0x1010
 	CRYPTO_cleanup_all_ex_data();
 	ERR_remove_state(0);
 	ERR_free_strings();
 	RAND_cleanup();
+#endif
 
 #ifdef USE_WINSOCK
 	if(WSACleanup() != 0) {
diff --git a/riggerd/svr.c b/riggerd/svr.c
index 0b46b1d..5f232f4 100644
--- a/riggerd/svr.c
+++ b/riggerd/svr.c
@@ -162,10 +162,12 @@ static int setup_ssl_ctx(struct svr* s)
 		return 0;
 	}
 	/* no SSLv2 because has defects */
+#if OPENSSL_VERSION_NUMBER < 0x1010
 	if(!(SSL_CTX_set_options(s->ctx, SSL_OP_NO_SSLv2) & SSL_OP_NO_SSLv2)){
 		log_crypto_err("could not set SSL_OP_NO_SSLv2");
 		return 0;
 	}
+#endif
 	s_cert = s->cfg->server_cert_file;
 	s_key = s->cfg->server_key_file;
 	verbose(VERB_ALGO, "setup SSL certificates");
-- 
2.10.2

Processed: Re: dnssec-trigger: broken by OpenSSL 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #843532 [src:dnssec-trigger] dnssec-trigger: broken by OpenSSL 1.1.0
Bug #828283 [src:dnssec-trigger] OpenSSL 1.1.0 Support
Ignoring request to alter tags of bug #843532 to the same tags previously set
Ignoring request to alter tags of bug #828283 to the same tags previously set

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

Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process

[dan]

For anyone needing a workaround. This bug also hit me this morning. I
looked through a bit of the code in runc/libcontainer and it looks like it
is caused by a cgroup issue.

I took an educated guess and downgraded systemd from 232-2 to 231-9 (which
is still available in stretch) and now docker works again.

Processed (with 1 error): Re: Processed: Re: Bug#840494: mono: FTBFS on mipsel: Assertion: should not be reached at mini-mips.c:2229

[Debian Bug Tracking System]

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

> retitle 840494 mono: FTBFS on mipsel: Assertion: should not be reached
Bug #840494 [src:mono] mono: FTBFS on several architectures
Changed Bug title to 'mono: FTBFS on mipsel: Assertion: should not be reached' 
from 'mono: FTBFS on several architectures'.
> at mini-mips.c:2229
Unknown command or malformed arguments to command.
> clone 840494 -1
Bug #840494 [src:mono] mono: FTBFS on mipsel: Assertion: should not be reached
Bug 840494 cloned as bug 843569
> retitle -1 mono: FTBFS on ppc64el (-pie -fPIE issue in __thread TLS)
Bug #843569 [src:mono] mono: FTBFS on mipsel: Assertion: should not be reached
Changed Bug title to 'mono: FTBFS on ppc64el (-pie -fPIE issue in __thread 
TLS)' from 'mono: FTBFS on mipsel: Assertion: should not be reached'.
> thanks
Stopping processing here.

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

Processed: cgsi-gsoap openssl ftbfs blocked by voms-dev

[Debian Bug Tracking System]

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

> block 828264 by 828595
Bug #828264 [src:cgsi-gsoap] cgsi-gsoap: FTBFS with openssl 1.1.0
828264 was not blocked by any bugs.
828264 was blocking: 827061
Added blocking bug(s) of 828264: 828595
> thanks
Stopping processing here.

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

Bug#840494: mono: FTBFS on mipsel: Assertion: should not be reached at mini-mips.c:2229

[Emilio Pozuelo Monfort]

Control: retitle -1 mono: FTBFS on several architectures

On 12/10/16 10:21, Emilio Pozuelo Monfort wrote:
> Source: mono
> Version: 4.6.1.3+dfsg-4
> Severity: serious
> 
> Your package failed to build on mipsel:
> 
> chmod +x _tmpinst/bin/al
> if test -w /«BUILDDIR»/mono-4.6.1.3+dfsg/mcs; then :; else chmod -R +w 
> /«BUILDDIR»/mono-4.6.1.3+dfsg/mcs; fi
> cd /«BUILDDIR»/mono-4.6.1.3+dfsg/mcs && /usr/bin/make --no-print-directory -s 
> NO_DIR_CHECK=1 PROFILES='binary_reference_assemblies net_4_x xbuild_12 
> xbuild_14  ' CC='gcc' all-profiles
> mkdir -p -- build/deps
> build/profiles/basic.make:93: recipe for target 
> 'build/deps/basic-profile-check.exe' failed
> make[7]: *** [build/deps/basic-profile-check.exe] Error 1
> *** The compiler 'false' doesn't appear to be usable.
> *** Trying the 'monolite' directory.
>  long_mul R91 <- R76 R88
> * Assertion: should not be reached at mini-mips.c:2229

This is now also failing to build on armel, armhf and ppc64el (in addition to
mipsel). At least the armel and armhf failures are rather similar, except the
assertion obviously comes from mini-arm.c. ppc64el fails with a segfault 
instead:

build/profiles/basic.make:93: recipe for target
'build/deps/basic-profile-check.exe' failed
make[7]: *** [build/deps/basic-profile-check.exe] Error 1
*** The compiler 'false' doesn't appear to be usable.
*** Trying the 'monolite' directory.
Stacktrace:

Segmentation fault

This is preventing mono 4.6.x from going into testing.

Cheers,
Emilio

Processed: Re: Bug#840494: mono: FTBFS on mipsel: Assertion: should not be reached at mini-mips.c:2229

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 mono: FTBFS on several architectures
Bug #840494 [src:mono] mono: FTBFS on mipsel: Assertion: should not be reached 
at mini-mips.c:2229
Changed Bug title to 'mono: FTBFS on several architectures' from 'mono: FTBFS 
on mipsel: Assertion: should not be reached at mini-mips.c:2229'.

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

Bug#828395: libexosip2 patch for openssl 1.1.0 build failure

[Andreas Henriksson]

Control: tags -1 + patch

Hello!

Please see attached patch which makes the package build against
openssl 1.1.0 (and hopefully also still against 1.0).
The patch has only been compile-tested so please review and
test carefully. There are still a number of deprecated warnings
which you might want to fix up as well.

Please forward the patch upstream for me if you find it useful.

Regards,
Andreas Henriksson
diff -urip libexosip2-4.1.0/src/eXtl_dtls.c libexosip2-4.1.0.openssl110/src/eXtl_dtls.c
--- libexosip2-4.1.0/src/eXtl_dtls.c	2014-01-06 19:30:21.0 +0100
+++ libexosip2-4.1.0.openssl110/src/eXtl_dtls.c	2016-11-07 20:23:01.503943171 +0100
@@ -233,7 +233,7 @@ shutdown_free_client_dtls (struct eXosip
 
   BIO_ctrl (rbio, BIO_CTRL_DGRAM_SET_PEER, 0, (char *) );
 
-  (reserved->socket_tab[pos].ssl_conn)->rbio = rbio;
+  SSL_set0_rbio((reserved->socket_tab[pos].ssl_conn), rbio);
 
   i = SSL_shutdown (reserved->socket_tab[pos].ssl_conn);
 
@@ -588,12 +588,11 @@ dtls_tl_read_message (struct eXosip_t *e
   rbio = BIO_new_mem_buf (enc_buf, enc_buf_len);
   BIO_set_mem_eof_return (rbio, -1);
 
-  reserved->socket_tab[pos].ssl_conn->rbio = rbio;
+  SSL_set0_rbio(reserved->socket_tab[pos].ssl_conn, rbio);
 
   i = SSL_read (reserved->socket_tab[pos].ssl_conn, dec_buf, SIP_MESSAGE_MAX_LENGTH);
   /* done with the rbio */
-  BIO_free (reserved->socket_tab[pos].ssl_conn->rbio);
-  reserved->socket_tab[pos].ssl_conn->rbio = BIO_new (BIO_s_mem ());
+  SSL_set0_rbio(reserved->socket_tab[pos].ssl_conn, BIO_new (BIO_s_mem ()));
 
   if (i > 5) {
 dec_buf[i] = '\0';
@@ -904,7 +903,7 @@ dtls_tl_send_message (struct eXosip_t *e
 _dtls_stream_used = >socket_tab[pos];
 rbio = BIO_new_dgram (reserved->dtls_socket, BIO_NOCLOSE);
 BIO_ctrl (rbio, BIO_CTRL_DGRAM_SET_PEER, 0, (char *) );
-reserved->socket_tab[pos].ssl_conn->rbio = rbio;
+SSL_set0_rbio(reserved->socket_tab[pos].ssl_conn, rbio);
 break;
   }
 }
@@ -918,7 +917,7 @@ dtls_tl_send_message (struct eXosip_t *e
   _dtls_stream_used = >socket_tab[pos];
   rbio = BIO_new_dgram (reserved->dtls_socket, BIO_NOCLOSE);
   BIO_ctrl (rbio, BIO_CTRL_DGRAM_SET_PEER, 0, (char *) );
-  reserved->socket_tab[pos].ssl_conn->rbio = rbio;
+  SSL_set0_rbio(reserved->socket_tab[pos].ssl_conn, rbio);
   break;
 }
   }
diff -urip libexosip2-4.1.0/src/eXtl_tls.c libexosip2-4.1.0.openssl110/src/eXtl_tls.c
--- libexosip2-4.1.0/src/eXtl_tls.c	2014-01-06 19:30:21.0 +0100
+++ libexosip2-4.1.0.openssl110/src/eXtl_tls.c	2016-11-07 20:27:51.568892332 +0100
@@ -838,7 +838,7 @@ verify_cb (int preverify_ok, X509_STORE_
* it for something special
*/
   if (!preverify_ok && (err == X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT)) {
-X509_NAME_oneline (X509_get_issuer_name (store->current_cert), buf, 256);
+X509_NAME_oneline (X509_get_issuer_name (X509_STORE_CTX_get_current_cert(store)), buf, 256);
 OSIP_TRACE (osip_trace (__FILE__, __LINE__, OSIP_ERROR, NULL, "issuer= %s\n", buf));
   }
 
@@ -1155,7 +1155,7 @@ initialize_client_ctx (struct eXosip_t *
   }
   else {
 /* this is used to add a trusted certificate */
-X509_STORE_add_cert (ctx->cert_store, cert);
+X509_STORE_add_cert (SSL_CTX_get_cert_store(ctx), cert);
   }
   BIO_free (bio);
 }

Processed: libexosip2 patch for openssl 1.1.0 build failure

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #828395 [src:libexosip2] libexosip2: FTBFS with openssl 1.1.0
Added tag(s) patch.

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

Bug#843528: hyperscan: FTBFS: boost/graph/graph_concepts.hpp:131:19: error: no matching function for call to 'degree(void*&, boost::reverse_graph<boost::adjacency_list<boost::listS, boost::listS, boos

[Robert Haist]

Thanks Chris.

This seems to be an already recognized upstream bug with the new
libboost 1.62.

Reference:

https://github.com/01org/hyperscan/issues/39

I will work with upstream if there is a plan to release a minor update.
Otherwise I will pin the libboost version for the Debian package.

Regards,
Robert

On 07.11.2016 14:30, Chris Lamb wrote:
> Source: hyperscan
> Version: 4.3.1-1
> 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,
> 
> hyperscan fails to build from source in unstable/amd64:
> 
>   […]
> 
>   /usr/bin/c++   -Dhs_shared_EXPORTS 
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/obj-x86_64-linux-gnu
>  
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1 
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src
>  -isystem 
> /home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/include
>   -g -O2 
> -fdebug-prefix-map=/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1=.
>  -fstack-protector-strong -Wformat -Werror=format-security -mssse3 
> -march=core2 -Wdate-time -D_FORTIFY_SOURCE=2  -DNDEBUG -std=c++11 -Wall 
> -Wextra -Wshadow -Wswitch -Wreturn-type -Wcast-qual -Wno-deprecated 
> -Wnon-virtual-dtor -fno-strict-aliasing -fabi-version=0 
> -Wno-unused-local-typedefs -Wno-maybe-uninitialized -fno-omit-frame-pointer 
> -fvisibility=hidden -Wvla -Wpointer-arith -Wno-unused-const-variable 
> -Wno-ignored-attributes -Wmissing-declarations -g -O2 -fPIC   -o 
> CMakeFiles/hs_shared.dir/src/nfa/goughcompile.cpp.o -c 
> /home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src/nfa/goughcompile.cpp
>   [ 30%] Building CXX object 
> CMakeFiles/hs_shared.dir/src/nfa/goughcompile_accel.cpp.o
>   /usr/bin/c++   -Dhs_shared_EXPORTS 
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/obj-x86_64-linux-gnu
>  
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1 
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src
>  -isystem 
> /home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/include
>   -g -O2 
> -fdebug-prefix-map=/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1=.
>  -fstack-protector-strong -Wformat -Werror=format-security -mssse3 
> -march=core2 -Wdate-time -D_FORTIFY_SOURCE=2  -DNDEBUG -std=c++11 -Wall 
> -Wextra -Wshadow -Wswitch -Wreturn-type -Wcast-qual -Wno-deprecated 
> -Wnon-virtual-dtor -fno-strict-aliasing -fabi-version=0 
> -Wno-unused-local-typedefs -Wno-maybe-uninitialized -fno-omit-frame-pointer 
> -fvisibility=hidden -Wvla -Wpointer-arith -Wno-unused-const-variable 
> -Wno-ignored-attributes -Wmissing-declarations -g -O2 -fPIC   -o 
> CMakeFiles/hs_shared.dir/src/nfa/goughcompile_accel.cpp.o -c 
> /home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src/nfa/goughcompile_accel.cpp
>   [ 30%] Building CXX object 
> CMakeFiles/hs_shared.dir/src/nfa/goughcompile_reg.cpp.o
>   /usr/bin/c++   -Dhs_shared_EXPORTS 
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/obj-x86_64-linux-gnu
>  
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1 
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src
>  -isystem 
> /home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/include
>   -g -O2 
> -fdebug-prefix-map=/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1=.
>  -fstack-protector-strong -Wformat -Werror=format-security -mssse3 
> -march=core2 -Wdate-time -D_FORTIFY_SOURCE=2  -DNDEBUG -std=c++11 -Wall 
> -Wextra -Wshadow -Wswitch -Wreturn-type -Wcast-qual -Wno-deprecated 
> -Wnon-virtual-dtor -fno-strict-aliasing -fabi-version=0 
> -Wno-unused-local-typedefs -Wno-maybe-uninitialized -fno-omit-frame-pointer 
> -fvisibility=hidden -Wvla -Wpointer-arith -Wno-unused-const-variable 
> -Wno-ignored-attributes -Wmissing-declarations -g -O2 -fPIC   -o 
> CMakeFiles/hs_shared.dir/src/nfa/goughcompile_reg.cpp.o -c 
> /home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src/nfa/goughcompile_reg.cpp
>   [ 30%] Building CXX object 
> CMakeFiles/hs_shared.dir/src/nfa/mcclellancompile.cpp.o
>   /usr/bin/c++   -Dhs_shared_EXPORTS 
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/obj-x86_64-linux-gnu
>  
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1 
> -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src
>  -isystem 
> /home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/include
>   -g -O2 
> 

Processed: Merge with the other bugs

[Debian Bug Tracking System]

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

> reassign 843550 libgtk-3-0
Bug #843550 [vim-gtk3] vim-gtk: gvim fails to display any text
Bug reassigned from package 'vim-gtk3' to 'libgtk-3-0'.
No longer marked as found in versions vim/2:8.0.0022-1.
Ignoring request to alter fixed versions of bug #843550 to the same values 
previously set
> forcemerge 842070 843550
Bug #842070 [libgtk-3-0] libgtk-3-0: Upgrade breaks gvim: Gtk-CRITICAL **: 
gtk_widget_set_size_request: assertion 'width >= -1' failed
Bug #842192 [libgtk-3-0] vim-gtk3: latest updates broke vim.gtk3
Bug #842819 [libgtk-3-0] vim-gtk3: gvim window is miss displayed
Bug #842990 [libgtk-3-0] vim-gtk3: gvim has the smallest possible text window
Bug #843146 [libgtk-3-0] /usr/bin/vim.gtk3: grey rectangle, no text shown or 
insertable
Bug #843550 [libgtk-3-0] vim-gtk: gvim fails to display any text
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=773387'.
Added indication that 843550 affects vim-gtk3
Marked as found in versions gtk+3.0/3.22.2-1.
Added tag(s) upstream.
Bug #842192 [libgtk-3-0] vim-gtk3: latest updates broke vim.gtk3
Bug #842819 [libgtk-3-0] vim-gtk3: gvim window is miss displayed
Bug #842990 [libgtk-3-0] vim-gtk3: gvim has the smallest possible text window
Bug #843146 [libgtk-3-0] /usr/bin/vim.gtk3: grey rectangle, no text shown or 
insertable
Merged 842070 842192 842819 842990 843146 843550
> thanks
Stopping processing here.

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

Bug#843564: /usr/bin/firewall-applet: Missing QT5 dependency

[Laurent Bigonville]

Package: firewall-applet
Version: 0.4.4-1
Severity: serious
File: /usr/bin/firewall-applet

Hi,

python3-dbus.mainloop.qt dependency should probably be changed to 
python3-dbus.mainloop.pyqt5.

Cheers,

Laurent Bigonville

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

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

Versions of packages firewall-applet depends on:
ii  firewall-config0.4.4-1
ii  firewalld  0.4.4-1
ii  gir1.2-networkmanager-1.0  1.4.2-2
ii  gir1.2-notify-0.7  0.7.7-1
ii  python3-dbus   1.2.4-1
ii  python3-dbus.mainloop.qt   4.11.4+dfsg-2
ii  python3-gi 3.22.0-1
ii  python3-pyqt5  5.7+dfsg-2+b1
ii  python3-slip-dbus  0.6.1-3
pn  python3:any

firewall-applet recommends no packages.

firewall-applet suggests no packages.

-- no debconf information

Bug#811444: closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#843479: Removed package(s) from unstable)

[Arian Sanusi]

Dear now-ex-Maintainers,

instead of citing other tools which also seem unfit, could you please mention a 
better alternative here?

thank you,

Arian



signature.asc
Description: OpenPGP digital signature

Bug#842928: marked as done (libboost-python1.62.0 exports Python 2 symbols for Python 3)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 19:04:57 +
with message-id 
and subject line Bug#842927: fixed in boost1.62 1.62.0+dfsg-3
has caused the Debian Bug report #842927,
regarding libboost-python1.62.0 exports Python 2 symbols for Python 3
to be marked as done.

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

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


-- 
842927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost-python1.62.0

Version: 1.62.0+dfsg-2

This fails with libboost-python 1.62, but works with 1.61:

 % g++ -I/usr/include/python3.5m/ conftest.cc -lboost_python-py35 -lpython3.5m
/tmp/cc6JvhrE.o: In function `PyInit_empty':
conftest.cc:(.text+0x8a): undefined reference to
`boost::python::detail::init_module(PyModuleDef&, void (*)())'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_Size'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyUnicodeUCS4_FromEncodedObject'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyFile_FromString'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_Type'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyInt_Type'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_FromString'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyUnicodeUCS4_AsWideChar'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_FromStringAndSize'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `Py_InitModule4_64'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_FromFormat'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyNumber_Divide'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyNumber_InPlaceDivide'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyInt_AsLong'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_InternFromString'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyClass_Type'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_AsString'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyInt_FromLong'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyFile_AsFile'
collect2: error: ld returned 1 exit status

The Debian version of `libboost_python-py35.so.1.62.0` does indeed
need these symbols, but they are not exported in Python 3 (they are
part of
the Python 2 C API):

$ readelf --dyn-syms
/usr/lib/x86_64-linux-gnu/libboost_python-py35.so.1.62.0 | grep
PyInt_Type
54:  0 NOTYPE  GLOBAL DEFAULT  UND PyInt_Type
$ readelf --dyn-syms /usr/lib/x86_64-linux-gnu/libpython3.5m.so | grep
PyInt_Type
$

`libboost_python-py35.so.1.61.0` didn't need those, and other
distributions packages don't either, so I think this is a Debian bug.
--- End Message ---
--- Begin Message ---
Source: boost1.62
Source-Version: 1.62.0+dfsg-3

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated boost1.62 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 

Bug#842927: marked as done (libboost-python1.62.0 exports Python 2 symbols for Python 3)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 19:04:57 +
with message-id 
and subject line Bug#842927: fixed in boost1.62 1.62.0+dfsg-3
has caused the Debian Bug report #842927,
regarding libboost-python1.62.0 exports Python 2 symbols for Python 3
to be marked as done.

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

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


-- 
842927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost-python
Version: 1.62.0+dfsg-2

This fails with libboost-python 1.62, but works with 1.61:

 % g++ -I/usr/include/python3.5m/ conftest.cc -lboost_python-py35 -lpython3.5m
/tmp/cc6JvhrE.o: In function `PyInit_empty':
conftest.cc:(.text+0x8a): undefined reference to
`boost::python::detail::init_module(PyModuleDef&, void (*)())'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_Size'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyUnicodeUCS4_FromEncodedObject'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyFile_FromString'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_Type'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyInt_Type'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_FromString'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyUnicodeUCS4_AsWideChar'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_FromStringAndSize'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `Py_InitModule4_64'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_FromFormat'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyNumber_Divide'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyNumber_InPlaceDivide'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyInt_AsLong'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_InternFromString'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyClass_Type'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyString_AsString'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyInt_FromLong'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python-py35.so:
undefined reference to `PyFile_AsFile'
collect2: error: ld returned 1 exit status

The Debian version of `libboost_python-py35.so.1.62.0` does indeed
need these symbols, but they are not exported in Python 3 (they are
part of
the Python 2 C API):

$ readelf --dyn-syms
/usr/lib/x86_64-linux-gnu/libboost_python-py35.so.1.62.0 | grep
PyInt_Type
54:  0 NOTYPE  GLOBAL DEFAULT  UND PyInt_Type
$ readelf --dyn-syms /usr/lib/x86_64-linux-gnu/libpython3.5m.so | grep
PyInt_Type
$

`libboost_python-py35.so.1.61.0` didn't need those, and other
distributions packages don't either, so I think this is a Debian bug.
--- End Message ---
--- Begin Message ---
Source: boost1.62
Source-Version: 1.62.0+dfsg-3

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated boost1.62 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Nov 2016 

Bug#823004: gplaycli: sensitive information in config file

[Matlink]

Re,


Le 07/11/2016 à 19:03, Lee Garrett a écrit :
> Hi,
>
> On 07/11/16 17:56, matlink wrote:
>> Hi Lee,
>>
>> Well the main goal for gplaycli was to provide a noconf and very easy to
>> use command line for downloading apks.
> I totally see the appeal, which is why I'm using it and want to see it in good
> shape in Debian. :)
> I'm personally working towards a way to have a phone without any google apps.
>
>> Creating a google account is for some people not the best idea, because
>> they either disagree with their ToS or they don't want to give Google
>> too many infos (AFAIK Google requires a phone number).
> Yes, good point.
>
>> I am totally aware of the issues that providing default credentials
>> includes. Anyway, I am tired of resetting that default credentials'
>> account password because a fool changes it. It's sad to see there are
>> always such persons to mess everything up.
> You can probably avoid people changing the password by activating 2FA. No idea
> if gplaycli still works then, needs to be tested.

If 2FA is enabled, I think  that every attempt to connect with gplaycli
will require a second authentication, which is not possible in such a
scenario. I'll give it a try right now, but I'm pretty sure Google will
refuse the connection since 2FA is enabled.

>
>> The approach you give seems interesting, however the simplicity of usage
>> falls down. But I'm ready to get rid of these default credentials. Maybe
>> the github version could provide defaults credentials, and the debian
>> one does not?
> How about the following:
>
> The updated package will ask via debconf if the user wants to provide
> credentials. If confirmed, google user/pass will be accepted and an Android ID
> generated. If denied, it will use your credentials, just as currently. In
> non-interactive installations it'll default to your credentials.
>
> We'll provide in a README how to generate the Android ID, in case people want
> to switch to their own credentials. Ideally it should just be adding new
> credentials to /etc/gplaycli/credentials.conf and then just re-run a command
> to generate the Android ID.

I approve, but we will still provide default credentials, then not
resolving the issue of misuse of this google account (password change,
spam, ...).

>
>> I will need to investigate again on how to generate an AndroidID (Racoon
>> does it well, Dummy Droid too, Hans-Christoph Steiner is on the way to
>> package it for debian).
> I'll look around. Last time I attempted it, I spent a few hours. Apparently
> many tools that achieve this have suffered bit rot due to API changes.
>
>> To be honest, I'm out of time these days and I don't think it'll go
>> better. Any help is greatly appreciated.
>>
>> Regards,
> Regards,
> Lee
>
>
>> Le 07/11/2016 à 17:11, Lee Garrett a écrit :
>>> Package: gplaycli
>>> Followup-For: Bug #823004
>>>
>>> Hi Matlink,
>>>
>>> the way gplaycli is shipped makes it problematic for several reasons:
>>> - Sharing account passwords violates Google's ToS
>>> - Someone could abuse that account for spamming via gmail, prompting Google 
>>> to disable the account
>>> - Everyone can change the password (just checked) breaking every 
>>> installation of gplaycli
>>> - It probably makes it easier to track gplaycli users
>>> (probably more problems if I'd dig more)
>>>
>>> So the right approach must be:
>>> Use debconf to ask for google account credentials (no defaults), then 
>>> generate the Android ID by
>>> some other means. AFAICS this currently means that another tools needs to 
>>> be included/packaged to
>>> generate this.
>>>
>>> You probably know better what the general approach is, if you could outline 
>>> them I'd be more than
>>> happy to help with implementing this.
>>>
>>> Bumping the bug severity accordingly.
>>>
>>> Regards,
>>> Lee
>>>
>>> -- System Information:
>>> Debian Release: stretch/sid
>>>   APT prefers testing
>>>   APT policy: (500, 'testing'), (101, 'unstable'), (1, 'experimental')
>>> Architecture: amd64 (x86_64)
>>> Foreign Architectures: i386
>>>
>>> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
>>> Locale: LANG=en_GB.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>>> Shell: /bin/sh linked to /bin/dash
>>> Init: systemd (via /run/systemd/system)

-- 
Matlink - Sysadmin matlink.fr
Sortez couverts, chiffrez vos mails : https://café-vie-privée.fr/
XMPP/Jabber : matl...@matlink.fr
Clé publique PGP : 0x186BB3CA
Empreinte Off-the-record : 572174BF 6983EA74 91417CA7 705ED899 DE9D05B2




signature.asc
Description: OpenPGP digital signature

Processed: tagging 842083

[Debian Bug Tracking System]

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

> tags 842083 + pending
Bug #842083 [fai-client] fai-client: fails to upgrade from 'jessie' - trying to 
overwrite /usr/lib/fai/mount2dir
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#823004: gplaycli: sensitive information in config file

[Hans-Christoph Steiner]

dummydroid is already included in Debian :-D  I think the best way
forward for this issue is for the gplaycli package to leave out the
default credentials.  Then make it as easy as possible for people to set
up the credentials using dummydroid.

Bug#823004: gplaycli: sensitive information in config file

[Lee Garrett]

Hi,

On 07/11/16 17:56, matlink wrote:
> Hi Lee,
> 
> Well the main goal for gplaycli was to provide a noconf and very easy to
> use command line for downloading apks.

I totally see the appeal, which is why I'm using it and want to see it in good
shape in Debian. :)
I'm personally working towards a way to have a phone without any google apps.

> Creating a google account is for some people not the best idea, because
> they either disagree with their ToS or they don't want to give Google
> too many infos (AFAIK Google requires a phone number).

Yes, good point.

> I am totally aware of the issues that providing default credentials
> includes. Anyway, I am tired of resetting that default credentials'
> account password because a fool changes it. It's sad to see there are
> always such persons to mess everything up.

You can probably avoid people changing the password by activating 2FA. No idea
if gplaycli still works then, needs to be tested.

> 
> The approach you give seems interesting, however the simplicity of usage
> falls down. But I'm ready to get rid of these default credentials. Maybe
> the github version could provide defaults credentials, and the debian
> one does not?

How about the following:

The updated package will ask via debconf if the user wants to provide
credentials. If confirmed, google user/pass will be accepted and an Android ID
generated. If denied, it will use your credentials, just as currently. In
non-interactive installations it'll default to your credentials.

We'll provide in a README how to generate the Android ID, in case people want
to switch to their own credentials. Ideally it should just be adding new
credentials to /etc/gplaycli/credentials.conf and then just re-run a command
to generate the Android ID.

> I will need to investigate again on how to generate an AndroidID (Racoon
> does it well, Dummy Droid too, Hans-Christoph Steiner is on the way to
> package it for debian).

I'll look around. Last time I attempted it, I spent a few hours. Apparently
many tools that achieve this have suffered bit rot due to API changes.

> To be honest, I'm out of time these days and I don't think it'll go
> better. Any help is greatly appreciated.
> 
> Regards,

Regards,
Lee


> Le 07/11/2016 à 17:11, Lee Garrett a écrit :
>> Package: gplaycli
>> Followup-For: Bug #823004
>>
>> Hi Matlink,
>>
>> the way gplaycli is shipped makes it problematic for several reasons:
>> - Sharing account passwords violates Google's ToS
>> - Someone could abuse that account for spamming via gmail, prompting Google 
>> to disable the account
>> - Everyone can change the password (just checked) breaking every 
>> installation of gplaycli
>> - It probably makes it easier to track gplaycli users
>> (probably more problems if I'd dig more)
>>
>> So the right approach must be:
>> Use debconf to ask for google account credentials (no defaults), then 
>> generate the Android ID by
>> some other means. AFAICS this currently means that another tools needs to be 
>> included/packaged to
>> generate this.
>>
>> You probably know better what the general approach is, if you could outline 
>> them I'd be more than
>> happy to help with implementing this.
>>
>> Bumping the bug severity accordingly.
>>
>> Regards,
>> Lee
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers testing
>>   APT policy: (500, 'testing'), (101, 'unstable'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=en_GB.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
> 

Bug#835801: vboot-utils openssl110 patch

[Andreas Henriksson]

Control: reopen -1
Control: severity -1 important
Control: unblock 827061 by -1

Hello!

Reopening and adjusting severity similar to how others who've opted
to take the libssl1.0-dev build-dep route has handled their bugreports.
(The idea seems to go that this bug is not really closed until the
package in question actually builds against 1.1.0, explicitly b-d
on libssl1.0-dev only makes it non-release-critical. for now.)

You'll find a patch attached to this mail which makes vboot-utils
build against openssl 1.1.0. It has only been compile-tested
(against openssl 1.1.0 but I don't see any particular reason
why it would fail against eg. 1.0). Please review and test it.
Feel free to poke me if you find any issues that you'd like me
to look into. Please forward the patch upstream  for me if
you find it useful.

(Rather than reusing the existing BIGNUM *n in one of the files
you might want to declare a new temporary pointer which you could
make const while at it to kill off a compiler warning.)

Regards,
Andreas Henriksson
diff -urip vboot-utils-0~R52-8350.B/futility/cmd_create.c vboot-utils-0~R52-8350.B.openssl110/futility/cmd_create.c
--- vboot-utils-0~R52-8350.B/futility/cmd_create.c	2016-05-23 10:39:35.0 +0200
+++ vboot-utils-0~R52-8350.B.openssl110/futility/cmd_create.c	2016-11-07 18:58:46.289506547 +0100
@@ -170,6 +170,7 @@ static int vb2_make_keypair()
 	enum vb2_signature_algorithm sig_alg;
 	uint8_t *pubkey_buf = 0;
 	int has_priv = 0;
+	const BIGNUM *d;
 
 	FILE *fp;
 	int ret = 1;
@@ -193,7 +194,8 @@ static int vb2_make_keypair()
 		goto done;
 	}
 	/* Public keys doesn't have the private exponent */
-	has_priv = !!rsa_key->d;
+	RSA_get0_key(rsa_key, NULL, NULL, );
+	has_priv = !!d;
 	if (!has_priv)
 		fprintf(stderr, "%s has a public key only.\n", infile);
 
diff -urip vboot-utils-0~R52-8350.B/futility/vb2_helper.c vboot-utils-0~R52-8350.B.openssl110/futility/vb2_helper.c
--- vboot-utils-0~R52-8350.B/futility/vb2_helper.c	2016-05-23 10:39:35.0 +0200
+++ vboot-utils-0~R52-8350.B.openssl110/futility/vb2_helper.c	2016-11-07 18:59:59.107601774 +0100
@@ -216,6 +216,7 @@ int ft_show_pem(const char *name, uint8_
 	uint8_t *keyb, *digest;
 	uint32_t keyb_len;
 	int i, bits;
+	const BIGNUM *n, *d;
 
 	/* We're called only after ft_recognize_pem, so this should work. */
 	rsa_key = rsa_from_buffer(buf, len);
@@ -223,10 +224,11 @@ int ft_show_pem(const char *name, uint8_
 		DIE;
 
 	/* Use to presence of the private exponent to decide if it's public */
-	printf("%s Key file:  %s\n", rsa_key->d ? "Private" : "Public",
+	RSA_get0_key(rsa_key, , NULL, );
+	printf("%s Key file:  %s\n", d ? "Private" : "Public",
 	 name);
 
-	bits = BN_num_bits(rsa_key->n);
+	bits = BN_num_bits(n);
 	printf("  Key length:  %d\n", bits);
 
 	if (vb_keyb_from_rsa(rsa_key, , _len)) {
diff -urip vboot-utils-0~R52-8350.B/host/lib/util_misc.c vboot-utils-0~R52-8350.B.openssl110/host/lib/util_misc.c
--- vboot-utils-0~R52-8350.B/host/lib/util_misc.c	2016-05-23 10:39:35.0 +0200
+++ vboot-utils-0~R52-8350.B.openssl110/host/lib/util_misc.c	2016-11-07 18:52:47.119194802 +0100
@@ -65,7 +65,8 @@ int vb_keyb_from_rsa(struct rsa_st *rsa_
 	int retval = 1;
 
 	/* Size of RSA key in 32-bit words */
-	nwords = BN_num_bits(rsa_private_key->n) / 32;
+	RSA_get0_key(rsa_private_key, , NULL, NULL);
+	nwords = BN_num_bits(n) / 32;
 
 	bufsize = (2 + nwords + nwords) * sizeof(uint32_t);
 	outbuf = malloc(bufsize);
@@ -94,7 +95,7 @@ int vb_keyb_from_rsa(struct rsa_st *rsa_
 	NEW_BIGNUM(B);
 #undef NEW_BIGNUM
 
-	BN_copy(N, rsa_private_key->n);
+	BN_copy(N, n);
 	BN_set_word(Big1, 1L);
 	BN_set_word(Big2, 2L);
 	BN_set_word(Big32, 32L);
diff -urip vboot-utils-0~R52-8350.B/host/lib21/host_key.c vboot-utils-0~R52-8350.B.openssl110/host/lib21/host_key.c
--- vboot-utils-0~R52-8350.B/host/lib21/host_key.c	2016-05-23 10:39:35.0 +0200
+++ vboot-utils-0~R52-8350.B.openssl110/host/lib21/host_key.c	2016-11-07 19:00:43.492879443 +0100
@@ -544,7 +544,11 @@ int vb2_public_key_hash(struct vb2_publi
 
 enum vb2_signature_algorithm vb2_rsa_sig_alg(struct rsa_st *rsa)
 {
-	int bits = BN_num_bits(rsa->n);
+	int bits;
+	const BIGNUM *n;
+
+	RSA_get0_key(rsa, , NULL, NULL);
+   	bits = BN_num_bits(n);
 
 	switch (bits) {
 	case 1024:
diff -urip vboot-utils-0~R52-8350.B/utility/dumpRSAPublicKey.c vboot-utils-0~R52-8350.B.openssl110/utility/dumpRSAPublicKey.c
--- vboot-utils-0~R52-8350.B/utility/dumpRSAPublicKey.c	2016-05-23 10:39:54.0 +0200
+++ vboot-utils-0~R52-8350.B.openssl110/utility/dumpRSAPublicKey.c	2016-11-07 18:57:06.438635603 +0100
@@ -20,8 +20,13 @@
  */
 
 int check(RSA* key) {
-  int public_exponent = BN_get_word(key->e);
-  int modulus = BN_num_bits(key->n);
+  int public_exponent;
+  int modulus;
+  const BIGNUM *n, *e;
+
+  RSA_get0_key(key, , , NULL);
+  public_exponent = BN_get_word(e);
+  modulus = BN_num_bits(n);
 
   if (public_exponent != 65537) {
 fprintf(stderr, "WARNING: Public 

Processed: vboot-utils openssl110 patch

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #835801 {Done: Sophie Brun } [src:vboot-utils] 
vboot-utils: FTBFS with openssl 1.1.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions vboot-utils/0~R52-8350.B-2.
> severity -1 important
Bug #835801 [src:vboot-utils] vboot-utils: FTBFS with openssl 1.1.0
Severity set to 'important' from 'serious'
> unblock 827061 by -1
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 828243 835797 828272 828443 828561 827068 828460 828236 
828388 828557 828595 828513 828265 828600 828616 828237 828420 828385 828281 
828503 828322 828412 828442 828434 828612 828524 828497 828411 828350 828273 
828374 828250 828343 828432 828441 828618 828295 828545 828342 828263 835549 
828531 828257 828585 828582 828459 828518 828562 828526 828333 828565 828242 
828229 828502 828277 828297 828314 835790 835811 828383 828539 828284 828598 
828246 828410 828535 828327 828278 828586 828252 828437 828329 828415 828293 
828584 828566 828287 828269 828258 828594 828466 828556 828402 828538 828267 
828543 828501 828421 828261 828326 828458 828241 828377 828408 828256 828461 
828431 828288 828351 828568 828334 828303 828308 828348 828390 828559 828517 
828591 828606 828575 828492 828515 828500 828275 828449 828491 828445 828615 
828264 828378 828403 828558 828367 827076 828588 828368 828300 828240 828552 
828318 828331 828298 828332 828248 828422 828546 828468 828244 828393 836419 
822380 808669 828436 828567 828596 828467 828280 828235 828392 828599 828249 
828234 828520 828262 828490 828478 828438 828296 828572 828510 828142 828590 
828352 828581 828361 828279 828597 828260 828542 828433 828560 828604 828317 
828424 828372 828540 828292 828381 828456 828347 828544 828395 828485 829465 
828516 828576 828259 828299 828523 828435 828614 828335 828611 828340 828521 
814600 828455 828266 828548 828602 828448 835789 828406 828416 828577 828471 
828512 828127 812166 828525 828488 828605 828413 828580 835799 828312 828357 
828359 828325 828399 835585 828290 828338 828376 828339 828483 828608 828607 
828401 828589 828274 828550 828304 828527 828375 828365 828255 828409 828354 
828360 828551 837960 828337 828484 828429 828592 828454 828564 828291 828447 
828345 828336 828487 835786 828470 828537 828519 828428 828610 828530 828370 
828319 828472 828511 828358 828587 828473 828380 828507 828349 828286 828464 
828356 828498 828384 828228 828230 828239 828276 841635 828404 828320 828083 
828253 828366 828462 828306 828400 828477 828480 835794 828469 828389 828419 
828619 828450 828476 828579 828496 828609 828494 828493 828139 828386 835798 
828486 828482 828563 828371 828316 828405 828578 828463 835800 828311 828398 
828536 828553 828440 828282 828341 828479 828323 828344 828232 828529 828285 
828305 828508 828396 828423 828489 835801 828439 828328 828355 828583 828554 
828417 828452 843532 828294 828309 828569 828302 828601 828570 828330 828509 
828426 828394 828444 828430 828593 835785 828364 835796 828245 828474 828362 
828427 828571 828238 828457 828270 828617 828574 828425 828387 828324 828307 
828082 828247 828451 835793 828391 828382 828499 828481 828465 828315 828251 
828514 828231 828522 828233 828407 828346 828363 828313 828534 828549 828555 
828547 809271 828495 828504 835804 828310 828353 828301 828379 828603 828533 
828532 828373 828506 828321 828505 828620 828453 828271 828369 829452 828289 
828397 828573 828418 828541 828414 828268 828283 828446 828254 828528
827061 was not blocking any bugs.
Removed blocking bug(s) of 827061: 835801

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

Bug#843136: marked as done (drumgizmo FTBFS on mips and mipsel: error: undefined reference to `__atomic_load_8')

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 18:03:33 +
with message-id 
and subject line Bug#843136: fixed in drumgizmo 0.9.11-2
has caused the Debian Bug report #843136,
regarding drumgizmo FTBFS on mips and mipsel: error:  undefined reference to 
`__atomic_load_8'
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.)


-- 
843136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drumgizmo
Version: 0.9.11-1
Severity: important
Tags: sid + patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch


Package drumgizmo_0.9.11-1 FTBFS on mips and mipsel with following error:

> plugingui-plugingui.o: In function `std::atomic::is_lock_free() 
> const':
> /usr/include/c++/6/atomic:212: undefined reference to `__atomic_is_lock_free'
> plugingui-plugingui.o: In function 
> `std::atomic::load(std::memory_order) const':
> /usr/include/c++/6/atomic:235: undefined reference to `__atomic_load_8'
> /usr/include/c++/6/atomic:235: undefined reference to `__atomic_load_8'
> /usr/include/c++/6/atomic:235: undefined reference to `__atomic_load_8'
> /usr/include/c++/6/atomic:235: undefined reference to `__atomic_load_8'
> plugingui-plugingui.o: In function `std::atomic::exchange(double, 
> std::memory_order)':
> /usr/include/c++/6/atomic:251: undefined reference to `__atomic_exchange_8'
> /usr/include/c++/6/atomic:251: undefined reference to `__atomic_exchange_8'
> plugingui-plugingui.o: In function 
> `std::atomic::load(std::memory_order) const':
> /usr/include/c++/6/atomic:235: undefined reference to `__atomic_load_8'
> /usr/include/c++/6/atomic:235: undefined reference to `__atomic_load_8'
> plugingui-plugingui.o: In function `SettingsNotifier::evaluate()':
> ./plugingui/../src/settings.h:152: undefined reference to `__atomic_load_8'
> plugingui-plugingui.o: In function 
> `std::atomic::load(std::memory_order) const':
> /usr/include/c++/6/atomic:235: undefined reference to `__atomic_load_8'
> /usr/include/c++/6/atomic:235: undefined reference to `__atomic_load_8'
> plugingui-plugingui.o:./plugingui/../src/settings.h:154: more undefined 
> references to `__atomic_load_8' follow
> collect2: error: ld returned 1 exit status
> Makefile:583: recipe for target 'plugingui' failed
> make[3]: *** [plugingui] Error 1

Full build log:
https://buildd.debian.org/status/fetch.php?pkg=drumgizmo=mips=0.9.11-1=1478043812

The problem is in configure.ac file. Code used for checking is libatomic needed 
to link 
always returns the same result. For mips and mipsel test passes but the build 
fails because of missing libatomic.
I have changed that test to provide linking with libatomic as needed.

Patch which corrects this test and resolves this issue is attached.
With this patch package builds successfully on mips*, i386 and amd64 
architectures.

Regards,
Radovan--- drumgizmo-0.9.11.orig/configure.ac
+++ drumgizmo-0.9.11/configure.ac
@@ -473,11 +473,12 @@ dnl ==
 AC_MSG_CHECKING([for the need for linkage with libatomic])
 AC_LANG_PUSH([C++])
 AC_LINK_IFELSE([AC_LANG_SOURCE[
+  #include 
   #include 
+  std::atomic x;
+  std::atomic y;	
   int main() {
-struct Test { int val; };
-std::atomic s;
-return s.is_lock_free()?1:0;
+	return x + y;
   }
 ]],
 [AC_MSG_RESULT([no])],
--- End Message ---
--- Begin Message ---
Source: drumgizmo
Source-Version: 0.9.11-2

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated drumgizmo 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: Mon, 07 Nov 2016 17:03:28 +
Source: drumgizmo
Binary: drumgizmo
Architecture: source
Version: 0.9.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 

Bug#828417: marked as done (libxr: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 18:00:14 +
with message-id 
and subject line Bug#843484: Removed package(s) from unstable
has caused the Debian Bug report #828417,
regarding libxr: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxr
Version: 1.0-2.2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libxr_1.0-2.2_amd64-20160529-1445

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Version: 1.0-2.2+rm

Dear submitter,

as the package libxr has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/843484

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#811444: marked as done (dnssec-tools fails to install: file conflict with dependency)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 17:59:39 +
with message-id 
and subject line Bug#843479: Removed package(s) from unstable
has caused the Debian Bug report #811444,
regarding dnssec-tools fails to install: file conflict with dependency
to be marked as done.

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

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


-- 
811444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-tools
Version: 2.2
Severity: grave
Justification: renders package unusable

dpkg-error gives all necessary info:

dpkg: error processing archive 
/var/cache/apt/archives/dnssec-tools_2.2-1_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/Net::DNS::ZoneFile::Fast.3pm.gz', 
which is also in package libnet-dns-zonefile-fast-perl 1.24-1

the package is uninstallable because it depends on libnet-dns-zonefile-fast-perl

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

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

Dear submitter,

as the package dnssec-tools has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/843479

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#754704: marked as done (rollerd crashes as soon as key rollover is started)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 17:59:39 +
with message-id 
and subject line Bug#843479: Removed package(s) from unstable
has caused the Debian Bug report #754704,
regarding rollerd crashes as soon as key rollover is started
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.)


-- 
754704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-tools
Version: 2.0-2
Severity: grave
File: /usr/sbin/rollerd

Hi!

  As soon as a zskrollover is started rollerd instanstly crashes and
it's impossible to restart it without manually removing the rollvoer
state from the rollerd file:

***  FATAL PROGRAM ERROR!!  Unknown method 'first'
***  which the program has attempted to call for the object:
***
***  faui2k9.de.86400   IN  DNSKEY  ; no data
***
***  This object does not have a method 'first'.  THIS IS A BUG
***  IN THE CALLING SOFTWARE, which incorrectly assumes that the
***  object would be of a particular type.  The type of an object
***  should be checked before calling any of its methods.
 at /usr/lib/perl5/Net/DNS/RR.pm line 210
 Net::DNS::RR::_new_hash called at /usr/lib/perl5/Net/DNS/RR.pm line
 62
 eval {...} called at /usr/lib/perl5/Net/DNS/RR.pm line 62
 Net::DNS::RR::new('Net::DNS::RR', 'algorithm', 8, 'protocol', 3,
 'first', 1, 'flags', 256, ...) called at
 /usr/share/perl5/Net/DNS/ZoneFile/Fast.pm line 202
 Net::DNS::ZoneFile::Fast::parse('file',
 '/etc/bind/zones/faui2k9.de.signed') called at
 /usr/share/perl5/Net/DNS/SEC/Tools/dnssectools.pm line 382
 Net::DNS::SEC::Tools::dnssectools::dt_parse_zonefile('file',
 '/etc/bind/zones/faui2k9.de.signed') called at /usr/sbin/rollerd
 line 2832
 main::maxttl('/etc/bind/zones/faui2k9.de.signed') called at
 /usr/sbin/rollerd line 2905
 main::ttlexpire('faui2k9.de', 'HASH(0xbbda50)', 1, 'ZSK') called
 at /usr/sbin/rollerd line 3296
 main::phasewait('faui2k9.de', 'HASH(0xbbda50)', 1, 'zsk') called
 at /usr/sbin/rollerd line 3189
 main::phasecmd('CODE(0xad6a70)', 'faui2k9.de', 'HASH(0xbbda50)',
 'zsk1') called at /usr/sbin/rollerd line 2051
 main::zsk_phaser('faui2k9.de', 'HASH(0xbbda50)') called at
 /usr/sbin/rollerd line 782
 main::rollkeys() called at /usr/sbin/rollerd line 601
 main::full_list_event_loop() called at /usr/sbin/rollerd line 440
 main::main() called at /usr/sbin/rollerd line 290
in new Net::DNS::RR( algorithm 8 protocol 3 first 1 flags 256 keybin
 ... ) at /usr/share/perl5/Net/DNS/ZoneFile/Fast.pm line 202 

-- System Information:
Debian Release: 7.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable')
Architecture: mipsel (mips64)

Kernel: Linux 3.2.0-4-loongson-2f
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dnssec-tools depends on:
ii  bind9utils   1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii  libmailtools-perl2.09-1
ii  libnet-dns-perl  0.77-3
ii  libnet-dns-sec-perl  0.19-2
ii  libtimedate-perl 1.2000-1
ii  perl 5.14.2-21+deb7u1

Versions of packages dnssec-tools recommends:
ii  bind91:9.8.4.dfsg.P1-6+nmu2+deb7u1
pn  perl-tk  

dnssec-tools suggests no packages.

-- Configuration Files:
/etc/default/rollerd changed:

/etc/dnssec-tools/dnssec-tools.conf changed:
admin-email christ...@siccegge.de
keyarch /usr/sbin/keyarch
rollchk /usr/sbin/rollchk
zonesigner  /usr/sbin/zonesigner
keygen  /usr/sbin/dnssec-keygen
rndc/usr/sbin/rndc
zonecheck   /usr/sbin/named-checkzone
zonesign/usr/sbin/dnssec-signzone
algorithm   rsasha256
ksklength   2048
zsklength   1024
random  /dev/urandom
usensec3yes
nsec3iter   100
nsec3salt   random:64
nsec3optout no
endtime +2592000# RRSIGs good for thirty days.
lifespan-max94608000
lifespan-min3600
ksklife 31536000
zsklife 10368000
archivedir  /var/lib/dnssec-tools/archive
entropy_msg 1
savekeys1
kskcount1
zskcount1
roll_loadzone   1
roll_logfile/var/log/dnssec-tools/rollerd.log
roll_loglevel   phase
roll_phasemsg   long
roll_sleeptime  3600
zone_errors 5
log_tz  gmt
tacontact   
tasmtpserverlocalhost
taresolvconflocalhost
tatmpdir/var/run/dnssec-tools/trustman
usegui  0

/etc/dnssec-tools/dnssec-tools.rollrec changed:
skip "info rollrec"

Bug#783721: marked as done (dnssec-tools: dnssec-signzone behaviour changed; new signed zonefiles unparseable by rollerd)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 17:59:39 +
with message-id 
and subject line Bug#843479: Removed package(s) from unstable
has caused the Debian Bug report #783721,
regarding dnssec-tools: dnssec-signzone behaviour changed; new signed zonefiles 
unparseable by rollerd
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.)


-- 
783721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-tools
Version: 1.13-1
Severity: grave
Justification: renders package unusable

After upgrading to jessie, rollerd will no longer start. 
It appears that the format of the signed zonefile has changed:

---

xen:/etc/bind# for i in db.andrewg.signed db.stibium.signed; do echo $i;head 
-16 $i; done
db.andrewg.signed
; File written on Mon Apr 27 10:40:38 2015
; dnssec_signzone version 9.9.5-9-Debian
andrewg.com.86400   IN SOA  xen.andrewg.com. root.xen.andrewg.com. (
2014120939 ; serial
28800  ; refresh (8 hours)
7200   ; retry (2 hours)
604800 ; expire (1 week)
86400  ; minimum (1 day)
)
86400   RRSIG   SOA 8 2 86400 (
20150527094038 20150427084038 11508 
andrewg.com.
oA4xSft7iCqdaxGyjj1blI0E8WNRJlKa+KFK
72xOSPIk8cYp6hdKdTel93WMPNU7l11KLKrd
E8uIOumut9jIdKoxjJ1d+dQMJyKtfYAd0tJY
TwrtCq3TZOHF1Pzy1pNdg3sHD/3Rptt1AU3Y
kK/ng1ieUVww30ipx/UZH4VRewM= )
db.stibium.signed
; File written on Sat Apr 18 08:21:32 2015
; dnssec_signzone version 9.8.4-rpz2+rl005.12-P1
stibium.net.86400   IN SOA  xen.andrewg.com. root.xen.andrewg.com. (
2014120938 ; serial
28800  ; refresh (8 hours)
7200   ; retry (2 hours)
604800 ; expire (1 week)
86400  ; minimum (1 day)
)
86400   RRSIG   SOA 8 2 86400 20150518082132 (
20150418072132 53691 stibium.net.
IAgXJGD1LzFfi09VDGFtQ4YOTObK4rKEHcXR
KSZGMqB11fOxCYMiXd+jN3h2qGvsO9iEVS/b
uNc0nKT9XouiYhPEjmQG7774sT86hEnqs2To
eD17BrD8t5CtAgYrcfDtnUVyt5AV569qAy+1
3gupeYBrmn7gYsEkn5WhcivyAfM= )
xen:/etc/bind# service rollerd restart
Restarting DNSSEC-Tools rollerd: rollerdUNIVERSAL->import is deprecated and 
will be removed in a future perl at 
/usr/share/perl5/Net/DNS/SEC/Tools/tooloptions.pm line 19.
.
xen:/etc/bind# bad RRSIG data 1, line 10
...propagated at /usr/share/perl5/Net/DNS/ZoneFile/Fast.pm line 164, 
 line 10.

---


This may be related to #642772. Fedora has a possibly related patch here:

http://pkgs.fedoraproject.org/cgit/dnssec-tools.git/plain/dnssec-tools-zonefile-fast-new-bind-1.13.patch?id2=HEAD

Note that the regular expression around line 800 has changed to match three 
sets 
of digits rather than four, matching the zonefile format changes observed.


Andrew


-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.18.5-x86-linode70 (SMP w/8 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 dnssec-tools depends on:
ii  bind9utils   1:9.9.5.dfsg-9
ii  libmailtools-perl2.13-1
ii  libnet-dns-perl  0.81-2
ii  libnet-dns-sec-perl  0.21-1
ii  libtimedate-perl 2.3000-2
ii  perl 5.20.2-3

Versions of packages dnssec-tools recommends:
ii  bind9  1:9.9.5.dfsg-9

dnssec-tools suggests no packages.

-- Configuration Files:
/etc/dnssec-tools/dnssec-tools.conf changed:
admin-email andr...@andrewg.com
keyarch /usr/sbin/keyarch
rollchk /usr/sbin/rollchk
zonesigner  

Bug#843463: marked as done (opendkim: fails to install: /lib/opendkim/opendkim.service.generate: systemctl: not found)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 17:50:59 +
with message-id 
and subject line Bug#843463: fixed in opendkim 2.11.0~alpha-8
has caused the Debian Bug report #843463,
regarding opendkim: fails to install: /lib/opendkim/opendkim.service.generate: 
systemctl: not found
to be marked as done.

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

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


-- 
843463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendkim
Version: 2.11.0~alpha-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package opendkim.
  (Reading database ... 
(Reading database ... 4633 files and directories currently installed.)
  Preparing to unpack .../opendkim_2.11.0~alpha-7_amd64.deb ...
  Unpacking opendkim (2.11.0~alpha-7) ...
  Setting up opendkim (2.11.0~alpha-7) ...
  /lib/opendkim/opendkim.service.generate: 83: 
/lib/opendkim/opendkim.service.generate: systemctl: not found
  /lib/opendkim/opendkim.service.generate: 84: 
/lib/opendkim/opendkim.service.generate: systemctl: not found
  dpkg: error processing package opendkim (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   opendkim


cheers,

Andreas


opendkim_2.11.0~alpha-7.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: opendkim
Source-Version: 2.11.0~alpha-8

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated opendkim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Nov 2016 09:07:28 -0500
Source: opendkim
Binary: opendkim opendkim-tools libopendkim11 libopendkim-dev libvbr2 
libvbr-dev librbl1 librbl-dev
Architecture: source amd64
Version: 2.11.0~alpha-8
Distribution: unstable
Urgency: medium
Maintainer: Scott Kitterman 
Changed-By: Scott Kitterman 
Description:
 libopendkim-dev - Headers and development libraries for the OpenDKIM library
 libopendkim11 - Library for signing and verifying DomainKeys Identified Mail 
sign
 librbl-dev - Headers/development libraries for the OpenDKIM RBL library
 librbl1- Library to support a DKIM based RBL system
 libvbr-dev - Headers and development libraries for the OpenDKIM VBR library
 libvbr2- Library for RFC 5518 Vouch By Reference (VBR)
 opendkim   - Milter implementation of DomainKeys Identified Mail
 opendkim-tools - Set of command line tools for OpenDKIM
Closes: 809089 842684 843463 843494
Changes:
 opendkim (2.11.0~alpha-8) unstable; urgency=medium
 .
   [ Peter Colberg ]
   * On systems using systemd, this version replaces /etc/default/opendkim
 with the files /etc/systemd/system/opendkim.service.d/overrride.conf
 and /etc/tmpfiles.d/opendkim.conf carrying over non-default settings
 (Closes: #843463, #843494)
 .
   [ Scott Kitterman ]
   * Fix undefined behavior in opendkim.postinst (Closes: #842684)
   * Fix pathfind invocation in sysv init script (Closes: #809089)
Checksums-Sha1:
 ba463e4c1b462cb2f64a8c415cc0300195832869 2394 opendkim_2.11.0~alpha-8.dsc
 0731584acf4695e17bdf1c3dca3cd7340ca1 23552 
opendkim_2.11.0~alpha-8.debian.tar.xz
 91968842badab2b2293ea97fc07e97ae37f58007 159680 
libopendkim-dev_2.11.0~alpha-8_amd64.deb
 9ccbf034afb5f42802477a0623aee9ec2bfb08be 238558 
libopendkim11-dbgsym_2.11.0~alpha-8_amd64.deb
 54ff2b161596317d3d26dec04e9b5c7c8362b33f 90962 
libopendkim11_2.11.0~alpha-8_amd64.deb
 6a7ecc07556587d5a98b12a686c882480b2883d2 50910 
librbl-dev_2.11.0~alpha-8_amd64.deb
 4ff3ea01bd1fb19919e2b686d30c1b14497c9f4a 12754 
librbl1-dbgsym_2.11.0~alpha-8_amd64.deb
 

Bug#843550: vim-gtk: gvim fails to display any text

[Doron Wloschowsky]

Package: vim-gtk3
Version: 2:8.0.0022-1
Severity: grave
File: vim-gtk
Justification: renders package unusable

Dear Maintainer,

When starting gvim (vim-gtk3) it either only partially displays the text
or it does not display any text at all. None of the normal navigation
keys have any effect.

When running from the command line, the terminal displays the following
text repeatedly:

gvim:22449): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion
'width >= -1' failed
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

The console version of vim works perfectly

-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk3
/usr/bin/vim is /usr/bin/vim.gtk3
/usr/bin/gvim is /usr/bin/vim.gtk3

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

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

Versions of packages vim-gtk3 depends on:
ii  libacl1  2.2.52-3
ii  libc62.24-5
ii  libcairo21.14.6-1.1
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.1-1
ii  libgpm2  1.20.4-6.2
ii  libgtk-3-0   3.22.2-1
ii  libice6  2:1.0.9-1+b1
ii  liblua5.2-0  5.2.4-1.1+b1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libperl5.24  5.24.1~rc3-3
ii  libpython3.5 3.5.2-7
ii  libruby2.3   2.3.1-5+b1
ii  libselinux1  2.6-3
ii  libsm6   2:1.2.2-1+b1
ii  libtcl8.68.6.6+dfsg-1
ii  libtinfo56.0+20160917-1
ii  libx11-6 2:1.6.3-1
ii  libxt6   1:1.1.5-1
ii  vim-common   2:8.0.0022-1
ii  vim-gui-common   2:8.0.0022-1
ii  vim-runtime  2:8.0.0022-1

vim-gtk3 recommends no packages.

Versions of packages vim-gtk3 suggests:
pn  cscope
ii  fonts-dejavu  2.37-1
ii  gnome-icon-theme  3.12.0-2
pn  vim-doc   

-- no debconf information

Bug#843136: marked as pending

[James Cowgill]

tag 843136 pending
thanks

Hello,

Bug #843136 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-multimedia/drumgizmo.git;a=commitdiff;h=67e1c5d

---
commit 67e1c5d66739928018f731e6116474fd98bc567e
Author: James Cowgill 
Date:   Mon Nov 7 17:02:38 2016 +

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index ed3d05f..7a71042 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,13 @@
-drumgizmo (0.9.11-2) UNRELEASED; urgency=medium
+drumgizmo (0.9.11-2) unstable; urgency=medium
 
   * Team upload.
+  * Use sse2 on amd64 instead of sse3. (Closes: #843149)
 
- -- James Cowgill   Mon, 07 Nov 2016 14:54:38 +
+  [ Radovan Birdic ]
+  * Ensure libatomic test checks for large integers. Fixes FTBFS on
+mips/mipsel. (Closes: #843136)
+
+ -- James Cowgill   Mon, 07 Nov 2016 17:03:28 +
 
 drumgizmo (0.9.11-1) unstable; urgency=medium
 

Processed: Bug#843136 marked as pending

[Debian Bug Tracking System]

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

> tag 843136 pending
Bug #843136 [drumgizmo] drumgizmo FTBFS on mips and mipsel: error:  undefined 
reference to `__atomic_load_8'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#842576: 842576: (caja: 1599): GTK-ERROR

[Vangelis Mouhtsis]

Hi Steve,
Thanks for reply, but no, debsums gives no error. The problem
is with the transistion to GTK+3 of some libs in caja and
caja-actions.
I did speak with upstreamers about, they are informed and hopfully
will be fixed.

Regards
Vangelis (gnugr)



signature.asc
Description: OpenPGP digital signature

Bug#759410: Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)

[Francois Marier]

On 2016-10-25 at 09:12:30, Sven Joachim wrote:
> >> In order to fix this while preserving safe-rm's default of automatic
> >> protection on installation, safe-rm will need to divert and replace
> >> /bin/rm.  This will require quite a bit of care to do safely; see dash's
> >> maintainer scripts for a safe procedure.
> > Merged /usr is the default since debootstrap 1.0.85, so the package
> > is uninstallable on new systems.
> 
> It's worse than that.  Because dpkg does not detect the file conflict
> between coreutils' /bin/rm and safe-rm's /usr/bin/rm, the package is
> installable but wreaks havoc, replacing the rm binary with its symlink.

I was hoping to fix 837925 first since molly-guard is already using
dpkg-divert instead of bare symlinks but I don't see what's wrong with the
way that molly-guard does things, so I don't know what's going to fix it for
safe-rm too.

Francois

-- 
https://fmarier.org/

Bug#837928: Bug#837925: usrmerge: fails to merge with molly-guard installed

[Francois Marier]

On 2016-11-02 at 03:02:29, Jonas Smedegaard wrote:
> I am busy getting that system to production use (yes, stretch is not yet 
> stable, but more stable than stable on the ARM device I use), but if you 
> have suggestions for closer inspections that might help shed some light 
> on this issue, please shoot - fast.

I reached out to Marco about this bug but have not heard back.

I don't know how dpkg-diverts are supposed to work in a usrmerge world and I
can't see anything obviously wrong with the way it's done in molly-guard so
I don't have any ideas on how to fix this.

Francois

-- 
https://fmarier.org/

Bug#840457: marked as done (linbox: FTBFS w/fflas-ffpack 1.x: No package 'fflas-ffpack' found)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 17:35:31 +
with message-id 
and subject line Bug#840457: fixed in linbox 1.4.2-2
has caused the Debian Bug report #840457,
regarding linbox: FTBFS w/fflas-ffpack 1.x: No package 'fflas-ffpack' found
to be marked as done.

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

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


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

Builds of linbox on architectures that still have fflas-ffpack 1.6.0-1
due to #840454 have been failing:

  checking pkg-config is at least version 0.9.0... yes
  checking for FFLAS_FFPACK... no
  configure: error: Package requirements (fflas-ffpack) were not met:
  
  No package 'fflas-ffpack' found
  
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.

Please version the build dependency on fflas-ffpack to ensure you get
a version that ships fflas-ffpack.pc.  (Alternatively, if the 1.6.0
API is sufficient for your purposes, you could explicitly set
FFLAS_FFPACK_{CFLAGS,LIBS}.)

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: linbox
Source-Version: 1.4.2-2

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated linbox package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Nov 2016 13:50:55 +
Source: linbox
Binary: liblinbox-dev liblinbox-1.4.2-0 liblinboxsage-dev liblinboxsage-1.4.2-0 
liblinbox-doc
Architecture: source amd64 all
Version: 1.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Tobias Hansen 
Description:
 liblinbox-1.4.2-0 - Library for exact linear algebra - shared library
 liblinbox-dev - Library for exact linear algebra - development files
 liblinbox-doc - LinBox Documentation
 liblinboxsage-1.4.2-0 - SAGE interface of LinBox - shared library
 liblinboxsage-dev - SAGE interface of LinBox - development files
Closes: 840457
Changes:
 linbox (1.4.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Add versioned Build-Depends and Depends on fflas-ffpack. (Closes: #840457)
   * Disable building with fplll.
Checksums-Sha1:
 d411efbc7a045f84ec5a542f4b91a60ac7d74f4f 2490 linbox_1.4.2-2.dsc
 230958d59d50b9990be3767fc1d7bbe66110cf42 7808 linbox_1.4.2-2.debian.tar.xz
 9064d40db0ecad7f98ba8084f0027c1b8d5fb178 332746 
liblinbox-1.4.2-0-dbgsym_1.4.2-2_amd64.deb
 9c25fe412e2e660de2ffb4c10c102cef37c44335 106726 
liblinbox-1.4.2-0_1.4.2-2_amd64.deb
 5e9a57dd78b8e1aa84e9eb3da6c2709745d4f5d2 1075584 
liblinbox-dev_1.4.2-2_amd64.deb
 d378152d715f4850e4422acbda92af680cc89a6a 63888458 liblinbox-doc_1.4.2-2_all.deb
 e1d2ee59f44563a5804ff9d97d5df2efd5b587fa 4251812 
liblinboxsage-1.4.2-0-dbgsym_1.4.2-2_amd64.deb
 77a20cae44313de91a296f154e0df7aa9f4cfa0f 584568 
liblinboxsage-1.4.2-0_1.4.2-2_amd64.deb
 1a024ab53b484b0c165d18bc17416ea0d8c09167 575104 
liblinboxsage-dev_1.4.2-2_amd64.deb
 c74abcad70cc2106bb987a5f5110df99d2051311 12622 
linbox_1.4.2-2_20161107T171404z-bd1ff250.buildinfo
Checksums-Sha256:
 1efab2c26537bc12d800a9736da397449523e401ae2876c5395c7b44985d919c 2490 
linbox_1.4.2-2.dsc
 88be02605e53732eaa41eeff24ce38e1e14e0b00af03e8750b1d133ea081b261 7808 
linbox_1.4.2-2.debian.tar.xz
 75e790d3fce320c752ac9f95a9f866d82b2541b7534bc5bb249600ef740658e0 332746 
liblinbox-1.4.2-0-dbgsym_1.4.2-2_amd64.deb
 0da606e0322208032ca6ca95f23973392a8c08173fac50a12b8f5e9ed4d38d36 106726 
liblinbox-1.4.2-0_1.4.2-2_amd64.deb
 e6938e7d0944c1aa2ef37abd4ccfcddf0be6a33b60f70bc669e2ccfb010dd931 1075584 
liblinbox-dev_1.4.2-2_amd64.deb
 

Bug#823004: gplaycli: sensitive information in config file

[matlink]

Hi Lee,

Well the main goal for gplaycli was to provide a noconf and very easy to
use command line for downloading apks.

Creating a google account is for some people not the best idea, because
they either disagree with their ToS or they don't want to give Google
too many infos (AFAIK Google requires a phone number).

I am totally aware of the issues that providing default credentials
includes. Anyway, I am tired of resetting that default credentials'
account password because a fool changes it. It's sad to see there are
always such persons to mess everything up.

The approach you give seems interesting, however the simplicity of usage
falls down. But I'm ready to get rid of these default credentials. Maybe
the github version could provide defaults credentials, and the debian
one does not?

I will need to investigate again on how to generate an AndroidID (Racoon
does it well, Dummy Droid too, Hans-Christoph Steiner is on the way to
package it for debian).

To be honest, I'm out of time these days and I don't think it'll go
better. Any help is greatly appreciated.

Regards,


Le 07/11/2016 à 17:11, Lee Garrett a écrit :
> Package: gplaycli
> Followup-For: Bug #823004
>
> Hi Matlink,
>
> the way gplaycli is shipped makes it problematic for several reasons:
> - Sharing account passwords violates Google's ToS
> - Someone could abuse that account for spamming via gmail, prompting Google 
> to disable the account
> - Everyone can change the password (just checked) breaking every installation 
> of gplaycli
> - It probably makes it easier to track gplaycli users
> (probably more problems if I'd dig more)
>
> So the right approach must be:
> Use debconf to ask for google account credentials (no defaults), then 
> generate the Android ID by
> some other means. AFAICS this currently means that another tools needs to be 
> included/packaged to
> generate this.
>
> You probably know better what the general approach is, if you could outline 
> them I'd be more than
> happy to help with implementing this.
>
> Bumping the bug severity accordingly.
>
> Regards,
> Lee
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (101, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

-- 
Matlink - Sysadmin matlink.fr
Sortez couverts, chiffrez vos mails : https://café-vie-privée.fr/
XMPP/Jabber : matl...@matlink.fr
Clé publique PGP : 0x186BB3CA
Empreinte Off-the-record : 572174BF 6983EA74 91417CA7 705ED899 DE9D05B2

Processed: Re: Bug#823004: gplaycli: sensitive information in config file

[Debian Bug Tracking System]

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

> severity 823004 serious
Bug #823004 [gplaycli] gplaycli: sensitive information in config file
Severity set to 'serious' from 'normal'
> tags 823004 upstream
Bug #823004 [gplaycli] gplaycli: sensitive information in config file
Added tag(s) upstream.
> kthxbye
Stopping processing here.

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

Bug#843073: More information

[Felipe Sateler]

Hi,

The problem seems to occur in the Shlibs perl module[1]. In
particular, the function find_library looks in a list of configured
paths. But for each path, it checks if the path is a link to another
known path, and if so, it does not use the original link but the
resolved path. Thus for /lib, it detects that it is a link to
/usr/lib and uses the latter instead. Complicating things:

1. Many libraries live in /usr/lib/$triplet, but /lib/$triplet is not
a link to the latter. Thus this link resolving is not done.
2. On at least my (usrmerged) amd64 machine, /usr/lib64 is not a
symlink to /usr/lib, and ld-linux-86_64 lives there instead of
/usr/lib.

It's unclear what the best solution for this is. The indirection is
there due to bug #453885. Maybe find_library should be changed to
return a list of possible matches, and have dpkg-shlibdeps decide
which one to use by using the first one for which dpkg-query returns a
positive result. That would be an API break on libdpkg-perl though.

[1] 
https://sources.debian.net/src/dpkg/1.18.13/scripts/Dpkg/Shlibs.pm/#L161-L166

-- 

Saludos,
Felipe Sateler

Bug#811960: pulseview NMU?

[Jonathan McDowell]

Graham, is there any reason you haven't performed an NMU with your
patch? I've applied it successfully to pulseview 0.2.0-1.1 (currently in
sid) and thrown it at my sbuild setup and it builds fine, and it would
be nice to get this package back into testing.

Even nicer would be an update both of PulseView and the rest of the
sigrok infrastructure, which all seems to be lagging behind upstream.
Uwe, do you have any plans for this?

J.

-- 
... I pretend to work. They pretend to pay me.


signature.asc
Description: Digital signature

Bug#831097: marked as done (eclipse-pydev: FTBFS with GCC 6: plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:237:25: error: expected initializer before 'pydevdTracingMod')

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 16:18:58 +
with message-id 
and subject line Bug#831097: fixed in eclipse-pydev 3.9.2-5
has caused the Debian Bug report #831097,
regarding eclipse-pydev: FTBFS with GCC 6: 
plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:237:25:
 error: expected initializer before 'pydevdTracingMod'
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.)


-- 
831097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-pydev
Version: 3.9.2-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -shared $CPPFLAGS $CXXFLAGS $LDFLAGS -fPIC -nostartfiles -o 
> attach_linux.so \
>   
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c: 
> In function 'int _PYDEVD_ExecWithGILSetSysStrace(bool, bool)':
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:237:25:
>  error: expected initializer before 'pydevdTracingMod'
>  auto PyObjectHolder pydevdTracingMod = PyObjectHolder(isDebug, 
> pyImportModFunc("pydevd_tracing"));
>  ^~~~
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:238:16:
>  error: 'pydevdTracingMod' was not declared in this scope
>  CHECK_NULL(pydevdTracingMod.ToPython(), "pydevd_tracing module null.\n", 
> 9);
> ^
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:124:45:
>  note: in definition of macro 'CHECK_NULL'
>  # define CHECK_NULL(ptr, msg, returnVal) if(ptr == 
> NULL){if(showDebugInfo){printf(msg);} return returnVal;}
>  ^~~
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:240:23:
>  error: 'pydevdTracingMod' was not declared in this scope
>  if(!pyHasAttrFunc(pydevdTracingMod.ToPython(), "_original_settrace")){
>^~~~
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:252:25:
>  error: expected initializer before 'settrace'
>  auto PyObjectHolder settrace = PyObjectHolder(isDebug, 
> pyGetAttr(pydevdTracingMod.ToPython(), "_original_settrace"));
>  ^~~~
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:253:16:
>  error: 'settrace' was not declared in this scope
>  CHECK_NULL(settrace.ToPython(), "pydevd_tracing._original_settrace 
> null!\n", 10);
> ^
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:124:45:
>  note: in definition of macro 'CHECK_NULL'
>  # define CHECK_NULL(ptr, msg, returnVal) if(ptr == 
> NULL){if(showDebugInfo){printf(msg);} return returnVal;}
>  ^~~
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:255:25:
>  error: expected initializer before 'pydevdMod'
>  auto PyObjectHolder pydevdMod = PyObjectHolder(isDebug, 
> pyImportModFunc("pydevd"));
>  ^
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:256:16:
>  error: 'pydevdMod' was not declared in this scope
>  CHECK_NULL(pydevdMod.ToPython(), "pydevd module null.\n", 10);
> ^
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:124:45:
>  note: in definition of macro 'CHECK_NULL'
>  # define CHECK_NULL(ptr, msg, returnVal) if(ptr == 
> NULL){if(showDebugInfo){printf(msg);} return returnVal;}
>  ^~~
> plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:258:25:
>  error: expected initializer before 'getGlobalDebugger'
>  auto PyObjectHolder getGlobalDebugger = PyObjectHolder(isDebug, 
> pyGetAttr(pydevdMod.ToPython(), "GetGlobalDebugger"));
>  ^
> 

Bug#842324: console-setup: During apt-get dist-upgrade stage, console-setup did not finish cleanly under ja_JP.UTF-8 locale.

[ISHIKAWA,chiaki]

On 2016/11/06 1:12, Anton Zinoviev wrote:

On Wed, Nov 02, 2016 at 02:44:13PM -0400, Sandro Tosi wrote:


in particular if the error in is `iconv` that program is part of
libc-bin so this bug should be reassigned to that pkg.


Yes, the bug belongs to libc-bin.  Unfortunately, I was unable to
reproduce the bug on my computer, so I won't be able to provide any
useful data to the libc-bin maintainers.  Therefore, I suppose it won't
do any good if I reassign the bug (but I can be wrong).


I'll let the console-setup maint decide what to do of course, just
posting my quick check on this RC bug.


I've commited a change that will make console-setup use untranslated
keyboard names in case of failed iconv.  This should fix the bug in
console-setup.  Of course, when we have more data or something
reproducible we can submit a bug against libc-bin.

Anton Zinoviev



I wish I could add more data point, but
iconv did fail on that particular PC I tested and LANG=C
cured the problem.

Let me look out if another iconv issue pops up on two PCs I use heavily.

TIA

Bug#809566: marked as done (eclipse-mylyn: FTBFS: Unsatisfied import package javax.mail_0.0.0.)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 16:04:07 +
with message-id 
and subject line Bug#809566: fixed in eclipse-mylyn 3.12.0-2
has caused the Debian Bug report #809566,
regarding eclipse-mylyn: FTBFS: Unsatisfied import package javax.mail_0.0.0.
to be marked as done.

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

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


-- 
809566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-mylyn
Version: 3.12.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.mylyn.builds.core:
[eclipse.buildScript]   Missing required plug-in org.eclipse.emf.ecore_0.0.0.
[eclipse.buildScript]   Missing required plug-in 
org.eclipse.emf.ecore.xmi_0.0.0.
[eclipse.buildScript] Bundle org.eclipse.mylyn.builds.tests:
[eclipse.buildScript]   Missing required plug-in org.eclipse.emf.ecore_0.0.0.
[eclipse.buildScript]   Missing required plug-in 
org.eclipse.mylyn.builds.core_0.0.0.
[eclipse.buildScript]   Missing required plug-in 
org.eclipse.mylyn.builds.ui_0.0.0.
[eclipse.buildScript]   Missing required plug-in org.mockito_[1.8.4,2.0.0).
[eclipse.buildScript]   Missing required plug-in org.objenesis_[1.0.0,2.0.0).
[eclipse.buildScript]   Missing required plug-in org.hamcrest_[1.0.0,2.0.0).
[eclipse.buildScript] Bundle org.eclipse.mylyn.builds.ui:
[eclipse.buildScript]   Missing required plug-in org.eclipse.emf.ecore_0.0.0.
[eclipse.buildScript]   Missing required plug-in 
org.eclipse.emf.databinding_0.0.0.
[eclipse.buildScript]   Missing required plug-in 
org.eclipse.mylyn.builds.core_0.0.0.
[eclipse.buildScript] Bundle org.eclipse.mylyn.cdt.tests:
[eclipse.buildScript]   Missing required plug-in org.eclipse.cdt.mylyn.ui_0.0.0.
[eclipse.buildScript]   Missing required plug-in org.eclipse.cdt.core_0.0.0.

...

BUILD FAILED
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
 The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91:
 The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
 The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/genericTargets.xml:111:
 Processing inclusion from feature org.eclipse.mylyn.commons: Bundle 
org.apache.axis_1.4.0 failed to resolve.:
Unsatisfied import package com.ibm.wsdl.extensions.soap_0.0.0.
Unsatisfied import package javax.mail_0.0.0.
Unsatisfied import package javax.mail.internet_0.0.0.
Unsatisfied import package javax.wsdl_0.0.0.
Unsatisfied import package javax.wsdl.extensions_0.0.0.
Unsatisfied import package javax.wsdl.extensions.http_0.0.0.
Unsatisfied import package javax.wsdl.extensions.mime_0.0.0.
Unsatisfied import package javax.wsdl.extensions.soap_0.0.0.
Unsatisfied import package javax.wsdl.factory_0.0.0.
Unsatisfied import package javax.wsdl.xml_0.0.0.
Unsatisfied import package javax.xml.rpc_0.0.0.
Unsatisfied import package javax.xml.rpc.encoding_0.0.0.
Unsatisfied import package javax.xml.rpc.handler_0.0.0.
Unsatisfied import package javax.xml.rpc.handler.soap_0.0.0.
Unsatisfied import package javax.xml.rpc.holders_0.0.0.
Unsatisfied import package javax.xml.rpc.server_0.0.0.
Unsatisfied import package javax.xml.rpc.soap_0.0.0.


Total time: 24 seconds
An error has occurred. See the log file
/eclipse-mylyn-3.12.0/debian/.eclipse-build/build/home/workspace/.metadata/.log.
jh_compilefeatures: cd debian/.eclipse-build && 
/usr/lib/eclipse/buildscripts/pde-build -o 
/eclipse-mylyn-3.12.0/debian/.eclipse-build/orbitdeps -a "-DjavacTarget=1.6 
-DjavacSource=1.6"  -f org.eclipse.mylyn.commons returned exit code 13

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/eclipse-mylyn.html

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

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

[Michael Biebl]

Am 07.11.2016 um 16:36 schrieb Yuri D'Elia:
> On Mon, Nov 07 2016, Michael Biebl wrote:
>>> Kernel: Linux 3.4.112-kvm-i386-20161024
>>
>> I suspect your kernel is too old and/or doesn't have all necessary
>> features enabled. Have you checked
> 
> As written, this is 3.4.
> 
>> See /usr/share/doc/systemd/README.gz
>> It explicitly mentions 3.12 as minimum required version and all
>> necessary config options.
> 
> Big bummer, I didn't notice the minimal version, as I didn't see
> anything relevant in the systemd changelog for 232.

One new requirement is CONFIG_SECCOMP_FILTER.

> I guess this bars me from using systemd for this system[!].

Mixing the latest userspace with very old kernels is going to be
problematic.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#828370: marked as done (kvirc: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 15:49:53 +
with message-id 
and subject line Bug#828370: fixed in kvirc 4:4.2.0-3
has caused the Debian Bug report #828370,
regarding kvirc: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kvirc
Version: 4.2.0-2
Severity: important
Control: block 827061 by -1

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: kvirc
Source-Version: 4:4.2.0-3

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated kvirc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Nov 2016 20:03:49 +0500
Source: kvirc
Binary: kvirc libkvilib4 kvirc-modules kvirc-data
Architecture: source
Version: 4:4.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Andrey Rahmatullin 
Description:
 kvirc  - KDE-based next generation IRC client with module support
 kvirc-data - Data files for KVIrc
 kvirc-modules - KVIrc (IRC client) modules
 libkvilib4 - KVIrc (IRC client) base library
Closes: 811908 828370
Changes:
 kvirc (4:4.2.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Switch to debhelper compat level 10.
   * Fix FTBFS in C++14 mode (Closes: #811908).
   * Build with libssl1.0-dev (Closes: #828370).
   * Drop explicit Pre-Depends: multiarch-support.
   * Remove obsolete lintian overrides for menu-icon-missing and
 package-needs-versioned-debhelper-build-depends.
   * Remove the menu file.
   * Use secure Vcs-* URLs.
   * Migrate to automatic debug packages.
   * Bump Standards-Version to 3.9.8.
Checksums-Sha1:
 86fff055376a66e099d5bcb233b0cc2f1831a7be 2290 kvirc_4.2.0-3.dsc
 217a1f8d73693e79326c53c88cee46ec765af628 28239 kvirc_4.2.0-3.debian.tar.bz2
Checksums-Sha256:
 01337814c63ce0025eabf779bba7c653c647697fe83c70f8073eac229a18cca3 2290 
kvirc_4.2.0-3.dsc
 0c539a31f2896cfcd815c717bfa521a82b691afb46978bcb111fdc38de81dfa1 28239 
kvirc_4.2.0-3.debian.tar.bz2
Files:
 71428f49df1f7a33be8d75de3fb14f74 2290 net optional kvirc_4.2.0-3.dsc
 60c0b0413ad8abc9b8880f780500fafc 28239 net optional 
kvirc_4.2.0-3.debian.tar.bz2

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYHKb2AAoJEDNi9wMaSZLhj0kP/RXyC33YG16Fhfrq3zs0/hzd
Zbz+5kCswDK2glKi6Bh5d4qTvJ0wV1j+QNyTQEvCiZxDzKH43wFkrArMzCPyD2Gn
IQz9lE58r7OEsqll/+KTPCtjOLM7hsZX908FvHuBFACK81F1adHwJhrUF34de4ez
KRA/DJNGyz8LpNz8NqXzVbe7o2RPlOoVR0mKQ1eymDKKF6quf0XQVRwh+dRol2om
Zb+njXECFKmpAkYP9jSppHLNiNfk43N5BjFaQ0F2HHlW3KM+clYBq7EeVsZ9gur0
GzPR1Bin/wJOyiwv+vC5bqXrv7nhNjsvrn8KukMpa8JsbFobk3yARUQMQcwwUntp
dDGUWYXTckCODkZhpf5/K5yHRr07AJL+PSZjWbIoIA0ezrJXQP1KNBd9OvjFR5tw
+YZ8qWRBqoqy5sGGFDBHVkmXjC6mX/73g2UEU3YRAh53JjL4LWzsWSuCVr9tzaV4
DjztiRUU4QYaMd05tM8cBIyG90iGpb48ehrEZPS+viDW5aQL1rHeJCbOG4Dk44uc
RdeohFFU7LVa0XrBaXTuCA0fbMtEwTCKPW7PAD0Sams2rhTuZiIkQWKS8r+9fSXE
XJZLL+cnRS4W15sSZ41M7XYG4pZJPCckzj8UA+tM9lT+TICbxKnafV0bD06UNrU7
ji/hmiNNc9dCWzoHuw7C
=D5sM
-END PGP SIGNATURE End Message ---

Bug#811908: marked as done (kvirc: FTBFS with GCC 6: invalid conversion)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 15:49:53 +
with message-id 
and subject line Bug#811908: fixed in kvirc 4:4.2.0-3
has caused the Debian Bug report #811908,
regarding kvirc: FTBFS with GCC 6: invalid conversion
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.)


-- 
811908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kvirc
Version: 4:4.2.0-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-invalid-convert

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [ 95%] Building CXX object 
> src/kvirc/CMakeFiles/kvirc.dir/ui/moc_KviCryptController.cxx.o
> cd /<>/obj-x86_64-linux-gnu/src/kvirc && /usr/bin/c++   
> -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=19 -DKDE_DEPRECATED_WARNINGS -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII 
> -DQT_NO_DEBUG -DQT_NO_STL -DQT_SQL_LIB -DQT_SVG_LIB -DQT_WEBKIT_LIB 
> -DQT_XML_LIB -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 
> -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns 
> -isystem /usr/include/qt4/QtXml -isystem /usr/include/qt4/QtWebKit 
> -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -isystem 
> /usr/include/qt4/QtSvg -isystem /usr/include/qt4/QtSql 
> -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript -isystem 
> /usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp 
> -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -isystem 
> /usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support -isystem 
> /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore -I/usr/include/qt4/Qt 
> -I/usr/share/qt4/mkspecs/default 
> -isystem /usr/include/qt4 -I/usr/include/python2.7 
> -I/<>/obj-x86_64-linux-gnu -I/<>/src/kvirc/kernel 
> -I/<>/src/kvirc/kvs -I/<>/src/kvirc/kvs/event 
> -I/<>/src/kvirc/kvs/object 
> -I/<>/src/kvirc/kvs/parser -I/<>/src/kvirc/kvs/tree 
> -I/<>/src/kvirc/module -I/<>/src/kvirc/sparser 
> -I/<>/src/kvirc/ui -I/<>/src/kvirc/../kvilib/tal 
> -I/<>/src/kvirc/../kvilib/config 
> -I/<>/src/kvirc/../kvilib/core 
> -I/<>/src/kvirc/../kvilib/ext 
> -I/<>/src/kvirc/../kvilib/file 
> -I/<>/src/kvirc/../kvilib/irc 
> -I/<>/src/kvirc/../kvilib/locale 
> -I/<>/src/kvirc/../kvilib/net 
> -I/<>/src/kvirc/../kvilib/system  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -O3 -fomit-frame-pointer -DNDEBUG --no-enforce-eh-specs 
> -pipe --exec-charset=UTF-8 --input-charset=UTF-8 --no-implement-inlines 
> --unit-at-a-time --fast-math -ggdb -fvisibility-inlines-hidden 
> -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts 
> -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS 
> -fno-check-new -fno-common -Woverloaded-virtual -O2 -DNDEBUG -DQT_NO_DEBUG   
> -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -o 
> CMakeFiles/kvirc.dir/ui/moc_KviCryptController.cxx.o -c 
> /<>/obj-x86_64-linux-gnu/src/kvirc/ui/moc_KviCryptController.cxx
> /<>/src/kvirc/kernel/KviIrcConnection.cpp: In member function 
> 'void KviIrcConnection::closeAllChannels()':
> /<>/src/kvirc/kernel/KviIrcConnection.cpp:672:102: error: 
> conversion from 'int' to 'QEventLoop::ProcessEventsFlags {aka 
> QFlags}' is ambiguous
>QApplication::processEvents(QEventLoop::ExcludeSocketNotifiers & 
> QEventLoop::ExcludeUserInputEvents);
>   
> ^
> 
> In file included from /usr/include/qt4/QtCore/QtGlobal:1:0,
>  from 
> /<>/src/kvirc/../kvilib/config/kvi_settings.h:37,
>  from /<>/src/kvirc/kernel/KviIrcConnection.h:33,
>  from 
> /<>/src/kvirc/kernel/KviIrcConnection.cpp:27:
> /usr/include/qt4/QtCore/qglobal.h:2438:29: note: candidate: constexpr 
> QFlags::QFlags(QFlags::Zero) [with Enum = 
> QEventLoop::ProcessEventsFlag; QFlags::Zero = void**] 
>  Q_DECL_CONSTEXPR inline QFlags(Zero = 0) : i(0) {}
>  ^~
> 
> 

Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process

[Tianon Gravi]

On 7 November 2016 at 05:34, Stef Walter  wrote:
> The docker package is unfortunately currently broken. It fails to run
> containers and instead produces the following message:
>
> rpc error: code = 2 desc = "oci runtime error: could not synchronise with 
> container process: no subsystem for mount"
>
> This can be reproduced by running something like:
>
> docker run -ti busybox /bin/sh
>
> Or any similar command.

Can you please provide the relevant log lines from the daemon?

(Either "/var/log/docker.log" or "journalctl -u docker.service")

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

[Yuri D'Elia]

On Mon, Nov 07 2016, Michael Biebl wrote:
>> Kernel: Linux 3.4.112-kvm-i386-20161024
>
> I suspect your kernel is too old and/or doesn't have all necessary
> features enabled. Have you checked

As written, this is 3.4.

> See /usr/share/doc/systemd/README.gz
> It explicitly mentions 3.12 as minimum required version and all
> necessary config options.

Big bummer, I didn't notice the minimal version, as I didn't see
anything relevant in the systemd changelog for 232.

I guess this bars me from using systemd for this system[!].

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

[Martin Pitt]

Hello Yuri,

Yuri D'Elia [2016-11-07 16:10 +0100]:
> Nov  7 15:26:03 e systemd[18963]: systemd-resolved.service: Failed at step 
> NAMESPACE spawning /bin/sh: Bad file descriptor

As Michael said, your kernel is likely too old. I suspect one of the
new hardening options in /lib/systemd/system/systemd-resolved.service:

  PrivateTmp=yes
  PrivateDevices=yes
  ProtectControlGroups=yes
  ProtectKernelTunables=yes
  RestrictRealtime=yes
  RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6

You can try commenting some or all of them.

Nevertheless, this is most likely a wontfix. We can't support ancient kernels
forever.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#841425: marked as done (dh_installxmlcatalogs: xmlcorever must be increased to 0.14 for sort)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 15:30:45 +
with message-id 
and subject line Bug#841425: fixed in xml-core 0.17
has caused the Debian Bug report #841425,
regarding dh_installxmlcatalogs: xmlcorever must be increased to 0.14 for sort
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.)


-- 
841425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dia-common
Version: 0.97.3+git20160930-1
Severity: normal
Tags: newcomer

Dear Maintainer,

I tried to upgrade dia, with an old version (0.13+nmu2) of xml-core installed.
It failed with the message "Unknown option: sort" and then the usage 
instructions of update-xmlcatalog.  It appears this sort-option was added to 
0.14, upgrading my version of xml-core let me upgrade dia successfully.
So I propose to bump the version dia-common requires accordingly.

Presumably the other dependants of xml-core are in the same situation, as
this new option is used by dh_installxmlcatalogs.

Thanks for maintaining!
-Steven


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

Kernel: Linux 4.7.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages dia-common depends on:
ii  python-gtk2  2.24.0-4
ii  xml-core 0.16

Versions of packages dia-common recommends:
ii  dia  0.97.3+git20160930-1

dia-common suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xml-core
Source-Version: 0.17

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated xml-core 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: Mon, 07 Nov 2016 14:53:35 +
Source: xml-core
Binary: xml-core
Architecture: source
Version: 0.17
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Mattia Rizzolo 
Description:
 xml-core   - XML infrastructure and XML catalog file support
Closes: 841425 843507
Changes:
 xml-core (0.17) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Helmut Grohne ]
   * Mark xml-core Multi-Arch: foreign.  Closes: #843507
 .
   [ Mattia Rizzolo ]
   * Bump generated dependency on xml-core to >= 0.14 for the sorting
 option.  Closes: #841425
   * d/rules: run dh_installxmlcatalogs after dh_installcatalogs,
 as the xml-core sequencer does.
Checksums-Sha1:
 a1969ac13c531743fa0a7ae71ddd62c8bedc2cfe 1686 xml-core_0.17.dsc
 e071f79f188b4f6b3fbd9e845827327aebd4e999 21180 xml-core_0.17.tar.xz
Checksums-Sha256:
 f4b953e75740239f4500174a3cb5234916b624d40c55c363b193b5a078b7ef42 1686 
xml-core_0.17.dsc
 2f21dbefa53aa54373214312edbf1c7f35041d6ac1d295bca50d3da9bd5007c3 21180 
xml-core_0.17.tar.xz
Files:
 da2a590f8a050173ed40e7768e673d9a 1686 text optional xml-core_0.17.dsc
 a0708d2df0b68af981851f7142b4ef21 21180 text optional xml-core_0.17.tar.xz

-BEGIN PGP SIGNATURE-

iQIvBAEBCgAZBQJYIJXuEhxtYXR0aWFAZGViaWFuLm9yZwAKCRAIFrnhjHYrrVJZ
D/0arNyOFGUkTRtLfu8TRdqzMhd7zqJYOLBvaeadq1cVCXWONr8PJc1z7YlojNXs
J5ZTMAHq+jFza5h6tuDRc/yc7Ayc2VyTwuo2/2vGa1mWDFiJZyZXABEH4bTUrauy
WPzb5YQn4kVyor8MBFW0p5gRr9ZZPqjpnXK+IRRAWg0K294OVk3xfiOnVRXpWOBw
uVs23ajJreevDrnjA8goQwxGrDrdYVNt0bLn04vLyigWmlNnFwgeMNhvfj/sAhR8
4qs2s4Ee7uJdj+TLC2l9HKARSjW7aS337WWnSsI3iYqUS0QMwSfsi/StWE6JRna1
Xhnszayi+NuubPr/J+Cro98wlv6KIiJl/dIflBl/AQPYuO2I9mwZH7KQkL/R8mty
FGjYRo9k5YjqczMumL/sMJVg/1GlLOroffXP8ns4XlQBuFD43Ya6eEWWkJnz0Oze
5qXkq2EGPH/Pin/7KP0VO1FX3B0zN3GLQtxESv7QDSHfXSOg84bEydibFuVOMguY
dOeCAZuDVHYWL2Qf0lHtVYIRtWQ7AzV/q8UytZAuYWJOIh+mrasJyBz9MYBG57/8
RNxODaIqKzsnnMdFEfT99C5LAPq7cqhiOnex2yhB5UZNbMUoYQxHMRYFm3ZG+EtC
iPkgIWdHbXso9YYjz59qjvjMLYdtQpBGG2Q1qQA6/AfNHw==
=kbDO
-END PGP 

Bug#842147: marked as done (Cannot install dia-common in stretch because of problem with update-xmlcatalog)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 15:30:45 +
with message-id 
and subject line Bug#841425: fixed in xml-core 0.17
has caused the Debian Bug report #841425,
regarding Cannot install dia-common in stretch because of problem with 
update-xmlcatalog
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.)


-- 
841425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dia-common
Version: 0.97.3+git20160930-1
Severity: important

Dear Maintainer,

I tried to install dia-common on stretch. This fails with the following
error message:

Setting up dia-common (0.97.3+git20160930-1) ...
Unknown option: sort
Usage:
update-xmlcatalog  --add --root --type  \
--id  --package 
update-xmlcatalog  --del --root --type  \
--id 

update-xmlcatalog  --add --package  --type  \
--id  --local 
update-xmlcatalog  --del --package  --type  \
--id 

update-xmlcatalog  --add --local  --type  \
--id  --file 
update-xmlcatalog  --del --local  --type  \
--id 

update-xmlcatalog --help

With:
--file= a local filename
--id= catalog entry idenitifier
--local  = a local XML catalog
--package  = a package XML catalog
--root  = the root XML catalog (= /etc/xml/catalog)
--type= catalog entry type (= public, system, uri)

Options:
--verbose = be verbose

dpkg: error processing package dia-common (--configure):
 subprocess installed post-installation script returned error exit status 1

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

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

Versions of packages dia-common depends on:
ii  python-gtk2  2.24.0-5.1
ii  xml-core 0.13+nmu2

Versions of packages dia-common recommends:
iu  dia  0.97.3+git20160930-1

dia-common suggests no packages.

-- no debconf information

Installation works fine after removing --sort from
/var/lib/dpkg/info/dia-common.postinst (I did not test the program
afterwards).

-- 
Benedikt Wildenhain, M.Sc., Wiss. Mitarbeiter - Hardwarenahe IT-Systeme
Hochschule Bochum - Bochum University of Applied Sciences
Campus Velbert/Heiligenhaus - http://www.hs-bochum.de/cvh/
Höseler Platz 2, Heiligenhaus, Raum 2.28, Tel +49 (0)2056 158744


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xml-core
Source-Version: 0.17

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated xml-core 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: Mon, 07 Nov 2016 14:53:35 +
Source: xml-core
Binary: xml-core
Architecture: source
Version: 0.17
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Mattia Rizzolo 
Description:
 xml-core   - XML infrastructure and XML catalog file support
Closes: 841425 843507
Changes:
 xml-core (0.17) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Helmut Grohne ]
   * Mark xml-core Multi-Arch: foreign.  Closes: #843507
 .
   [ Mattia Rizzolo ]
   * Bump generated dependency on xml-core to >= 0.14 for the sorting
 option.  Closes: #841425
   * d/rules: run dh_installxmlcatalogs after dh_installcatalogs,
 as the xml-core sequencer does.
Checksums-Sha1:
 a1969ac13c531743fa0a7ae71ddd62c8bedc2cfe 1686 xml-core_0.17.dsc
 

Processed: reassign 843532 to src:dnssec-trigger, retitle 828283 to OpenSSL 1.1.0 Support ...

[Debian Bug Tracking System]

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

> reassign 843532 src:dnssec-trigger
Bug #843532 [dnssec-trigger] dnssec-trigger: broken by OpenSSL 1.1.0
Bug reassigned from package 'dnssec-trigger' to 'src:dnssec-trigger'.
No longer marked as found in versions dnssec-trigger/0.13~svn685-6.
Ignoring request to alter fixed versions of bug #843532 to the same values 
previously set
> retitle 828283 OpenSSL 1.1.0 Support
Bug #828283 [src:dnssec-trigger] dnssec-trigger: FTBFS with openssl 1.1.0
Changed Bug title to 'OpenSSL 1.1.0 Support' from 'dnssec-trigger: FTBFS with 
openssl 1.1.0'.
> forcemerge 828283 843532
Bug #828283 [src:dnssec-trigger] OpenSSL 1.1.0 Support
Bug #843532 [src:dnssec-trigger] dnssec-trigger: broken by OpenSSL 1.1.0
Severity set to 'serious' from 'critical'
827061 was blocked by: 828478 828443 828486 828229 828578 828300 828469 828399 
828378 828381 828230 828501 828462 828279 828603 828616 828287 828383 828390 
828359 828601 828525 828366 835794 828414 828549 828282 835585 828356 828520 
828336 828503 828249 828532 828511 828465 828323 828463 828417 828328 828368 
828608 828384 828403 828266 828574 828593 828357 828370 828404 828484 828407 
828596 828527 828592 828597 828292 828610 828492 828587 828430 828349 828447 
828324 828493 828317 828421 828569 814600 828377 828487 828289 837960 828402 
828450 828375 828333 828436 828406 828555 828614 828353 828400 828374 828309 
828319 828452 828253 828393 828528 828515 828422 828479 828556 835789 828142 
828507 828584 828523 828395 828346 828347 828514 828457 828468 828238 828570 
828265 828286 828321 828490 828482 828534 828410 828611 828290 828285 828595 
828573 828314 828458 828276 828297 836419 828271 828513 828547 828545 828590 
828615 828419 828332 828599 828315 828303 835786 828460 828361 828429 828391 
828338 828322 828441 828577 828389 828284 828312 828331 828277 828341 828474 
828453 828268 829465 835790 828517 828509 828455 828538 822380 828568 828278 
828382 828531 828250 828082 809271 828294 828488 828581 828473 812166 828372 
828481 828281 828235 828586 828358 808669 828232 828127 828425 828365 828343 
828519 828521 828318 828567 828415 828440 828433 828299 828255 828448 828248 
828604 828274 828598 828585 828405 828497 828269 828327 828270 828325 828485 
828609 828464 828242 828561 828583 828240 828575 828367 828557 828231 828499 
828529 828344 835549 828444 828564 828431 828576 828275 828526 827068 828546 
828259 828480 828571 828234 828369 828302 828466 828461 828423 828330 828296 
828530 828489 828539 828424 828434 828411 828408 828418 828335 828267 828260 
828251 828392 828451 828239 828500 828470 828228 828504 828552 828329 828445 
828363 828362 828607 828307 828293 828562 828477 828602 828388 828446 828618 
828306 828288 835801 828559 835798 828252 828428 828533 828563 828246 828439 
828256 828334 828291 828435 828554 828139 828483 828508 828380 828605 828316 
828283 828456 828550 828560 828244 828543 828619 828495 828280 828261 828273 
828454 828394 828379 828516 828542 828310 828541 828437 828326 828506 828245 
828459 829452 828340 828313 835785 828301 841635 828580 828536 828620 828544 
828471 828320 828426 828553 827076 835796 828355 828505 828311 828438 828337 
828540 828308 828247 828512 828304 828524 828600 828566 828476 828510 835800 
828612 828496 828594 828582 828606 828537 828401 828551 828412 828502 828237 
835793 828432 828498 828385 828409 828491 828241 828350 828352 828565 828396 
828339 828572 828264 828522 828449 828472 828345 828494 835797 828386 828376 
835804 828272 828467 828254 828373 828535 828427 828257 828243 828305 828518 
835799 835811 828262 828258 828354 828398 828416 828579 828295 828342 828589 
828588 828420 828348 828442 828263 828387 828558 828364 828591 828360 828233 
828298 828351 828083 828397 828413 828548 828371 828617 828236
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 843532
Marked as found in versions dnssec-trigger/0.13~svn685-5.
Added tag(s) patch.
Merged 828283 843532
> thanks
Stopping processing here.

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

Bug#808485: marked as done (jython: Missing Export-Package field in the OSGi metadata)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 15:25:12 +
with message-id 
and subject line Bug#808485: fixed in jython 2.5.3-11
has caused the Debian Bug report #808485,
regarding jython: Missing Export-Package field in the OSGi metadata
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.)


-- 
808485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-pydev
Version: 3.9.2-4
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

...
[eclipse.buildScript]   Missing required plug-in org.python.pydev.jython_0.0.0.
[eclipse.buildScript] Bundle jnr.ffi:
[eclipse.buildScript]   Unsatisfied import package com.kenai.jffi_0.0.0.
[eclipse.buildScript] Bundle jnr.posix:
[eclipse.buildScript]   Unsatisfied import package sun.misc_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.constants_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.constants.platform_0.0.0.
[eclipse.buildScript]   Unsatisfied import package 
jnr.constants.platform.windows_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.ffi_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.ffi.annotations_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.ffi.byref_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.ffi.mapper_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.ffi.provider_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.ffi.types_0.0.0.
[eclipse.buildScript] Bundle org.python:
[eclipse.buildScript]   Unsatisfied import package com.kenai.jffi_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.constants_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.constants.platform_0.0.0.
[eclipse.buildScript]   Unsatisfied import package 
jnr.constants.platform.linux_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.posix_0.0.0.
[eclipse.buildScript]   Unsatisfied import package jnr.posix.util_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.antlr.runtime_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.antlr.runtime.tree_0.0.0.

BUILD FAILED
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
 The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91:
 The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
 The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/genericTargets.xml:111:
 Processing inclusion from feature org.python.pydev.feature: Bundle 
org.python.pydev.jython_3.9.2.dist failed to resolve.:
Missing required plug-in org.python_0.0.0.


Total time: 6 seconds
An error has occurred. See the log file
/eclipse-pydev-3.9.2/debian/.eclipse-build/build/home/workspace/.metadata/.log.
jh_compilefeatures: cd debian/.eclipse-build && 
/usr/lib/eclipse/buildscripts/pde-build -o 
/eclipse-pydev-3.9.2/debian/.eclipse-build/orbitdeps -a "-DjavacTarget=1.7 
-DjavacSource=1.7 -DbuildId=dist -DforceContextQualifier=dist"  -f 
org.python.pydev.feature returned exit code 13
debian/rules:22: recipe for target 'override_jh_compilefeatures-indep' failed
make[1]: *** [override_jh_compilefeatures-indep] Error 13
make[1]: Leaving directory '/eclipse-pydev-3.9.2'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/eclipse-pydev.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: jython
Source-Version: 2.5.3-11

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

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

[Michael Biebl]

Control: tags -1 + moreinfo

On Mon, 07 Nov 2016 16:10:51 +0100 Yuri D'Elia  wrote:

> This is an i386 kvm image running linux 3.4.
> Downgrading to 231-10 fixes the issue.
> 
> 
> -- Package-specific info:
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (900, 'unstable'), (800, 'experimental')
> Architecture: i386 (i686)
> 
> Kernel: Linux 3.4.112-kvm-i386-20161024

I suspect your kernel is too old and/or doesn't have all necessary
features enabled. Have you checked

Can you please try to reproduce the problem with a standard Debian kernel?

See /usr/share/doc/systemd/README.gz
It explicitly mentions 3.12 as minimum required version and all
necessary config options.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Fails to start dovecot/resolved with NAMESPACE spawning error

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #843537 [systemd] Fails to start dovecot/resolved with NAMESPACE spawning 
error
Added tag(s) moreinfo.

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

Processed (with 1 error): reopening 828283, forcibly merging 828283 843532

[Debian Bug Tracking System]

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

> reopen 828283
Bug #828283 {Done: Ondřej Surý } [src:dnssec-trigger] 
dnssec-trigger: FTBFS with openssl 1.1.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions dnssec-trigger/0.13~svn685-6.
> forcemerge 828283 843532
Bug #828283 [src:dnssec-trigger] dnssec-trigger: FTBFS with openssl 1.1.0
Unable to merge bugs because:
package of #843532 is 'dnssec-trigger' not 'src:dnssec-trigger'
Failed to forcibly merge 828283: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#843537: Fails to start dovecot/resolved with NAMESPACE spawning error

[Yuri D'Elia]

Package: systemd
Version: 232-1
Severity: serious

Upgrading systemd from 231-10 to either 232-1 or 232-2 breaks systemd-resolved
and dovecot on my system, with the following error when the units are started:

Nov  7 15:26:03 e systemd[18963]: systemd-resolved.service: Failed at step 
NAMESPACE spawning /bin/sh: Bad file descriptor
Nov  7 15:26:03 e systemd[1]: systemd-resolved.service: Control process exited, 
code=exited status=226
Nov  7 15:26:17 e systemd[1]: Stopping Dovecot IMAP/POP3 email server...
Nov  7 15:26:17 e systemd[19423]: dovecot.service: Failed at step NAMESPACE 
spawning /usr/bin/doveadm: Bad file descriptor
Nov  7 15:26:17 e systemd[1]: dovecot.service: Control process exited, 
code=exited status=226

On top of that, udevd.service also emits the following error:

Nov  7 15:26:33 e systemd[1]: systemd-udevd.service: Failed to set invocation 
ID on control group /system.slice/systemd-udevd.service, ignoring:  
Operation not supported

although the service is still started.

This is an i386 kvm image running linux 3.4.
Downgrading to 231-10 fixes the issue.


-- Package-specific info:

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

Kernel: Linux 3.4.112-kvm-i386-20161024
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 systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.10.95-5
ii  libaudit1   1:2.6.7-1
ii  libblkid1   2.28.2-1
ii  libc6   2.24-5
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-1
ii  libgcc1 1:6.2.0-11
ii  libgcrypt20 1.7.3-2
ii  libgpg-error0   1.24-1
ii  libidn111.33-1
ii  libip4tc0   1.6.0-4
ii  libkmod223-1
ii  liblzma55.2.2-1.2
ii  libmount1   2.28.2-1
ii  libpam0g1.1.8-3.3
ii  libseccomp2 2.3.1-2
ii  libselinux1 2.6-2
pn  libsystemd0 
ii  mount   2.28.2-1
ii  util-linux  2.28.2-1

Versions of packages systemd recommends:
ii  dbus1.10.12-1
pn  libpam-systemd  

Versions of packages systemd suggests:
ii  policykit-10.105-17
pn  systemd-container  
pn  systemd-ui 

Versions of packages systemd is related to:
pn  dracut   
pn  initramfs-tools  
pn  udev 

-- Configuration Files:
/etc/systemd/logind.conf changed [not included]
/etc/systemd/resolved.conf changed [not included]

Bug#841163: Upload of MySQL 5.7.16 security update to unstable

[Lars Tangvald]

Hi all,

We prepared a security upload for the Oracle October 2016 CPU, but we need 
someone with access to sponsor the upload to Debian unstable. Is anyone 
available to do this?
The source should be ready to go from 
https://anonscm.debian.org/cgit/pkg-mysql/mysql.git

--
Lars

Bug#841592: [debian-mysql] Bug#841592: mysql-5.7: FTBFS: Tests failures

[Lucas Nussbaum]

Hi,

On 07/11/16 at 12:39 +0100, Lars Tangvald wrote:
> Hi,
> 
> I can't reproduce this failure, with 5.7.15 or the 5.7.16 we've prepared for
> #841163
> I think maybe this is an unstable test, in which case we can disable it
> until it's resolved upstream.
> Could you retry the build and see if it happens again?

I don't think it's random: the rebuild is automatically retried when it
fails. However, maybe a change in another package fixed it. If you have
a full build log, maybe you could diff it with me to see if a build-dep
changed, which could explain the result?

I plan to do another archive rebuild soon (probably over next week-end).
I'll double-check at this point.

Lucas

Processed: retitle 808485 to jython: Missing Export-Package field in the OSGi metadata

[Debian Bug Tracking System]

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

> retitle 808485 jython: Missing Export-Package field in the OSGi metadata
Bug #808485 [jython] eclipse-pydev: FTBFS: Missing required plug-in 
org.python_0.0.0.
Changed Bug title to 'jython: Missing Export-Package field in the OSGi 
metadata' from 'eclipse-pydev: FTBFS: Missing required plug-in 
org.python_0.0.0.'.
> thanks
Stopping processing here.

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

Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process

[Tom Marble]

I can confirm I am hitting this exact same bug (same system
information).

--Tom

Processed: severity of 843510 is important

[Debian Bug Tracking System]

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

> severity 843510 important
Bug #843510 [src:linux] linux-image-4.8.0-rc8-amd64-unsigned: Task timeout when 
workstation is connected
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#843511: libqt5widgets5: Some Qt applications segfault on startup

[Dmitry Shachnev]

Hi Ralf,

On Mon, Nov 07, 2016 at 01:33:04PM +0100, Ralf Jung wrote:
> Hi Dmitry,
>
> > Emilio has scheduled a lxqt-plugin rebuild now, so I am closing this bug.
> >
> > I still hope to be able to refactor the Qt side of this so that platform
> > plugins do not need to link against the private static library, but this
> > is not a trivial issue.
> >
> > See discussions at [1] (LXQt specific) and [2] (Qt in general) for details.
>
> Great, thanks.
> However, with no additional dependency being added, this means Qt 5.7
> will move to testing before the new lxqt-qtplugin does, breaking every
> LXQt out there -- correct?

In theory that would be the case, but Lisandro has just asked the release
team to make sure Qt and binNMUs migrate together.

This should happen soon if nothing goes wrong.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Proposed NMU

[Debian Bug Tracking System]

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

> tags 828566 + patch
Bug #828566 [src:tcltls] tcltls: FTBFS with openssl 1.1.0
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#828566: Proposed NMU

[Sergei Golovan]

tags 828566 + patch
thanks

Hi, Muammar,

I'd like to offer a patch which ports tcltls to the new Openssl 1.1.
It's already forwarded upstream
(https://sourceforge.net/p/tls/bugs/66/) though I don't know when it
(or some other patch) will be accepted. The changes are mostly
straightforward, the patch retains compatibility with OpenSSL 1.0, and
the package passes regression tests.

If you don't mind, I could do NMU for this bugfix.

Cheers!
-- 
Sergei Golovan
diff -Nru tcltls-1.6.7+dfsg/debian/changelog tcltls-1.6.7+dfsg/debian/changelog
--- tcltls-1.6.7+dfsg/debian/changelog  2016-05-29 14:54:10.0 +0300
+++ tcltls-1.6.7+dfsg/debian/changelog  2016-11-07 16:40:21.0 +0300
@@ -1,3 +1,10 @@
+tcltls (1.6.7+dfsg-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Added a patch which fixes FTBFS with OpenSSL 1.1 (closes: #828566).
+
+ -- Sergei Golovan   Mon, 07 Nov 2016 16:40:21 +0300
+
 tcltls (1.6.7+dfsg-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru tcltls-1.6.7+dfsg/debian/patches/openssl1.1 
tcltls-1.6.7+dfsg/debian/patches/openssl1.1
--- tcltls-1.6.7+dfsg/debian/patches/openssl1.1 1970-01-01 03:00:00.0 
+0300
+++ tcltls-1.6.7+dfsg/debian/patches/openssl1.1 2016-11-06 23:48:18.0 
+0300
@@ -0,0 +1,410 @@
+Author: Sergei Golovan 
+Description: Patch ports the tcltls to the new OpenSSL 1.1 API.
+Last-Modified: Sun, 30 Oct 2016 23:08:28 +0300
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828566
+Bug-Upstream: https://sourceforge.net/p/tls/bugs/66/
+Forwarded: yes
+
+--- a/tls.c
 b/tls.c
+@@ -115,15 +115,29 @@
+ static DH *get_dh2048()
+ {
+ DH *dh=NULL;
++BIGNUM *p=NULL, *g=NULL;
+ 
+-if ((dh=DH_new()) == NULL) return(NULL);
++p=BN_bin2bn(dh2048_p,sizeof(dh2048_p),NULL);
++if (p == NULL) goto err;
+ 
+-dh->p=BN_bin2bn(dh2048_p,sizeof(dh2048_p),NULL);
+-dh->g=BN_bin2bn(dh2048_g,sizeof(dh2048_g),NULL);
++g=BN_bin2bn(dh2048_g,sizeof(dh2048_g),NULL);
++if (g == NULL) goto err;
+ 
+-if ((dh->p == NULL) || (dh->g == NULL))
+-  return(NULL);
++if ((dh=DH_new()) == NULL) goto err;
++
++#if OPENSSL_VERSION_NUMBER < 0x1010L
++dh->p=p;
++dh->g=g;
++#else
++if (!DH_set0_pqg(dh, p, NULL, g)) goto err;
++#endif
+ return(dh);
++
++err:
++if (p) BN_free(p);
++if (g) BN_free(g);
++if (dh) DH_free(dh);
++return(NULL);
+ }
+ #endif
+ 
+@@ -160,7 +174,10 @@
+ #define OPENSSL_THREAD_DEFINES
+ #include 
+ 
+-#ifdef OPENSSL_THREADS
++static Tcl_Mutex init_mx;
++static int initialized;
++
++#if defined(OPENSSL_THREADS) && OPENSSL_VERSION_NUMBER < 0x1010L
+ #include 
+ 
+ /*
+@@ -169,8 +186,6 @@
+  */
+ 
+ static Tcl_Mutex locks[CRYPTO_NUM_LOCKS];
+-static Tcl_Mutex init_mx;
+-static int initialized;
+ 
+ static void  CryptoThreadLockCallback (int mode, int n, const char 
*file, int line);
+ static unsigned long CryptoThreadIdCallback   (void);
+@@ -310,7 +325,7 @@
+ Tcl_Obj *cmdPtr, *result;
+ char *errStr, *string;
+ int length;
+-SSL   *ssl= (SSL*)X509_STORE_CTX_get_app_data(ctx);
++SSL   *ssl= (SSL*)X509_STORE_CTX_get_ex_data(ctx, 
SSL_get_ex_data_X509_STORE_CTX_idx());
+ X509  *cert   = X509_STORE_CTX_get_current_cert(ctx);
+ State *statePtr   = (State*)SSL_get_app_data(ssl);
+ int depth = X509_STORE_CTX_get_error_depth(ctx);
+@@ -554,14 +569,14 @@
+ }
+ switch ((enum protocol)index) {
+ case TLS_SSL2:
+-#if defined(NO_SSL2)
++#if defined(NO_SSL2) || OPENSSL_VERSION_NUMBER >= 0x1010L
+   Tcl_AppendResult(interp, "protocol not supported", NULL);
+   return TCL_ERROR;
+ #else
+   ctx = SSL_CTX_new(SSLv2_method()); break;
+ #endif
+ case TLS_SSL3:
+-#if defined(NO_SSL3)
++#if defined(NO_SSL3) || OPENSSL_VERSION_NUMBER >= 0x1010L
+   Tcl_AppendResult(interp, "protocol not supported", NULL);
+   return TCL_ERROR;
+ #else
+@@ -754,12 +769,12 @@
+ #ifndef OPENSSL_NO_TLSEXT
+ char *servername  = NULL; /* hostname for Server Name Indication */
+ #endif
+-#if defined(NO_SSL2)
++#if defined(NO_SSL2) || OPENSSL_VERSION_NUMBER >= 0x1010L
+ int ssl2 = 0;
+ #else
+ int ssl2 = 1;
+ #endif
+-#if defined(NO_SSL3)
++#if defined(NO_SSL3) || OPENSSL_VERSION_NUMBER >= 0x1010L
+ int ssl3 = 0;
+ #else
+ int ssl3 = 1;
+@@ -1069,13 +1084,13 @@
+ }
+ 
+ /* create SSL context */
+-#if defined(NO_SSL2)
++#if defined(NO_SSL2) || OPENSSL_VERSION_NUMBER >= 0x1010L
+ if (ENABLED(proto, TLS_PROTO_SSL2)) {
+   Tcl_AppendResult(interp, "protocol not supported", NULL);
+   return (SSL_CTX *)0;
+ }
+ #endif
+-#if defined(NO_SSL3)
++#if defined(NO_SSL3) || OPENSSL_VERSION_NUMBER >= 0x1010L
+ if (ENABLED(proto, TLS_PROTO_SSL3)) {
+   Tcl_AppendResult(interp, "protocol not supported", NULL);
+   return (SSL_CTX 

Bug#843532: dnssec-trigger: broken by OpenSSL 1.1.0

[Zack Weinberg]

Package: dnssec-trigger
Version: 0.13~svn685-6
Severity: critical
Justification: renders package unusable

On upgrading dnssec-trigger within unstable, the postinst fails with
errors from systemd:

Setting up dnssec-trigger (0.13~svn685-6) ...
Job for dnssec-triggerd.service failed because the control process exited with 
error code.
See "systemctl status dnssec-triggerd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dnssec-triggerd, action "start" failed.
● dnssec-triggerd.service - Reconfigure local DNSSEC resolver on connectivity 
changes
   Loaded: loaded (/lib/systemd/system/dnssec-triggerd.service; enabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2016-11-07 
08:25:41 EST; 3ms ago
  Process: 8425 ExecStopPost=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--cleanup (code=exited, status=1/FAILURE)
  Process: 8423 ExecStartPost=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--update (code=exited, status=1/FAILURE)
  Process: 8422 ExecStart=/usr/sbin/dnssec-triggerd -d (code=exited, 
status=1/FAILURE)
  Process: 8421 ExecStartPre=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--prepare (code=exited, status=0/SUCCESS)
 Main PID: 8422 (code=exited, status=1/FAILURE)

Nov 07 08:25:41 moxana systemd[1]: dnssec-triggerd.service: Unit entered fa…ate.
Nov 07 08:25:41 moxana systemd[1]: dnssec-triggerd.service: Failed with res…de'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package dnssec-trigger (--configure):
 subprocess installed post-installation script returned error exit status 1

The real error message is hiding in "journalctl -xe":

-- Unit dnssec-triggerd.service has begun starting up.
Nov 07 08:34:17 moxana dnssec-triggerd[20281]: Nov 07 08:34:17 
dnssec-triggerd[20281] error: could not set SSL_OP_NO_SSLv2 crypto 
error:
Nov 07 08:34:17 moxana dnssec-triggerd[20281]: Nov 07 08:34:17 
dnssec-triggerd[20281] error: cannot setup SSL context
Nov 07 08:34:17 moxana dnssec-triggerd[20281]: Nov 07 08:34:17 
dnssec-triggerd[20281] fatal error: could not init server
Nov 07 08:34:17 moxana systemd[1]: dnssec-triggerd.service: Main process 
exited, code=exited, status=1/FAILURE
Nov 07 08:34:17 moxana dnssec-trigger-script[20282]: Cannot connect to 
dnssec-trigger.
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]: chattr: Operation not 
supported while reading flags on /etc/resolv.conf
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]: Traceback (most recent 
call last):
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]:   File 
"/usr/lib/dnssec-trigger/dnssec-trigger-script", line 465, in 
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]: 
Application(sys.argv).run()
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]:   File 
"/usr/lib/dnssec-trigger/dnssec-trigger-script", line 364, in run
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]: self.method()
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]:   File 
"/usr/lib/dnssec-trigger/dnssec-trigger-script", line 398, in run_cleanup
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]: 
subprocess.check_call(["chattr", "-i", "/etc/resolv.conf"])
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]:   File 
"/usr/lib/python2.7/subprocess.py", line 186, in check_call
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]: raise 
CalledProcessError(retcode, cmd)
Nov 07 08:34:18 moxana dnssec-trigger-script[20284]: 
subprocess.CalledProcessError: Command '['chattr', '-i', '/etc/resolv.conf']' 
returned non-
Nov 07 08:34:18 moxana systemd[1]: Failed to start Reconfigure local DNSSEC 
resolver on connectivity changes.
-- Subject: Unit dnssec-triggerd.service has failed

I get the same SSL-related errors upon attempting to start dnssec-triggerd 
manually:

# dnssec-triggerd -d -v
Nov 07 08:37:21 dnssec-triggerd[20314] debug: event mini-event-0.13 uses 
not_obtainable method.
Nov 07 08:37:21 dnssec-triggerd[20314] error: could not set SSL_OP_NO_SSLv2 
crypto error::lib(0):func(0):reason(0)
Nov 07 08:37:21 dnssec-triggerd[20314] error: cannot setup SSL context
Nov 07 08:37:21 dnssec-triggerd[20314] fatal error: could not init server

The patch for bug #828283 appears to have been either incomplete or broken, and 
not to have been tested. >:-(

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

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

Versions of packages dnssec-trigger depends on:
ii  gir1.2-networkmanager-1.0  1.4.2-2
ii  init-system-helpers1.46
ii  libc6  2.24-5
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libglib2.0-0   2.50.1-1
ii  libgtk2.0-02.24.31-1
ii  libldns1  

Bug#831264: marked as done (rdkit: FTBFS: ! LaTeX Error: File `iftex.sty' not found.)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 13:35:31 +
with message-id 
and subject line Bug#831264: fixed in rdkit 201603.5-2
has caused the Debian Bug report #831264,
regarding rdkit: FTBFS: ! LaTeX Error: File `iftex.sty' not found.
to be marked as done.

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

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


-- 
831264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rdkit
Version: 201503-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/Docs/Book/_build/latex'
> pdflatex  'RDKit.tex'
> This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./RDKit.tex
> LaTeX2e <2016/03/31> patch level 1
> Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
> (./sphinxmanual.cls
> Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
> 
> ! LaTeX Error: File `iftex.sty' not found.
> 
> Type X to quit or  to proceed,
> or enter new name. (Default extension: sty)
> 
> Enter file name: 
> ! Emergency stop.
>  
>  
> l.5 ^^M
>
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on RDKit.log.
> make[3]: *** [RDKit.pdf] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/rdkit_201503-3_unstable_gcc5.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rdkit
Source-Version: 201603.5-2

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated rdkit 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: Mon, 07 Nov 2016 14:50:50 +0200
Source: rdkit
Binary: python-rdkit rdkit-doc rdkit-data librdkit1 librdkit-dev
Architecture: source amd64 all
Version: 201603.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Graham Inggs 
Description:
 librdkit-dev - Collection of cheminformatics and machine-learning software 
(deve
 librdkit1  - Collection of cheminformatics and machine-learning software (shar
 python-rdkit - Collection of cheminformatics and machine-learning software
 rdkit-data - Collection of cheminformatics and machine-learning software (data
 rdkit-doc  - Collection of cheminformatics and machine-learning software (docu
Closes: 831264
Changes:
 rdkit (201603.5-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/control (Build-Depends): Added pandoc and
 texlive-generic-extra. (Closes: #831264)
   * debian/rules (override_dh_auto_configure): Added
 -DRDK_OPTIMIZE_NATIVE=OFF to prevent FTBFS on ppc64el.
Checksums-Sha1:
 99aa49b658b2dc540428fe072ef03a7a534e8b1e 2470 rdkit_201603.5-2.dsc
 f6e3d7799644ad61d456bda99ab03c13ddbedd31 8052 rdkit_201603.5-2.debian.tar.xz
 bc578297a04afdea002a433d956af481949c2cae 233194 
librdkit-dev_201603.5-2_amd64.deb
 5cd48f040769ce4f625979e8200c65d3dedaf783 36109112 
librdkit1-dbgsym_201603.5-2_amd64.deb
 3e03c9051a1a11fc81c2dab5e6ae088b5a7dd3de 2087924 librdkit1_201603.5-2_amd64.deb
 0801c6de89cb24c1442c5eb0ce42b6cbf7edecf3 26885898 

Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process

[Stef Walter]

Package: docker.io
Version: 1.11.2~ds1-6
Severity: grave
Justification: renders package unusable

The docker package is unfortunately currently broken. It fails to run
containers and instead produces the following message:

rpc error: code = 2 desc = "oci runtime error: could not synchronise with 
container process: no subsystem for mount"

This can be reproduced by running something like:

docker run -ti busybox /bin/sh

Or any similar command.

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

Kernel: Linux 4.8.0-1-amd64 (SMP w/1 CPU core)
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 docker.io depends on:
ii  adduser  3.115
ii  containerd   0.2.1~ds1-3
ii  init-system-helpers  1.46
ii  iptables 1.6.0-4
ii  libapparmor1 2.10.95-5
ii  libc62.24-5
ii  libdevmapper1.02.1   2:1.02.133-1
ii  libsqlite3-0 3.15.1-1
ii  libsystemd0  232-2
ii  runc 0.1.1+dfsg1-1

Versions of packages docker.io recommends:
ii  ca-certificates  20161102
ii  cgroupfs-mount   1.3
ii  git  1:2.10.2-2
ii  xz-utils 5.2.2-1.2

Versions of packages docker.io suggests:
pn  aufs-tools   
pn  btrfs-progs  
ii  debootstrap  1.0.86
pn  docker-doc   
pn  rinse
pn  zfs-fuse | zfsutils  

-- no debconf information

Bug#830399: python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Stuart Prescott]

Adding python-pytest and python3-pytest to the build-depends does not 
seem to be enough -- the tests then fail for other reasons as follows:


=== FAILURES ===
 test_complete_on_empty_import _

args = (), kwds = {}
oldcwd = '/<>/.pybuild/pythonX.Y_2.7/build'
repo_root = '/<>/.pybuild/pythonX.Y_2.7/build'

@functools.wraps(func)
def wrapper(*args, **kwds):
try:
oldcwd = os.getcwd()
repo_root = os.path.dirname(test_dir)
os.chdir(os.path.join(repo_root, path))
>   return func(*args, **kwds)

test/helpers.py:36: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

@cwd_at('jedi')
def test_complete_on_empty_import():
assert Script("from datetime import").completions()[0].name == 'import'
# should just list the files in the directory
>   assert 10 < len(Script("from .", path='').completions()) < 30
E   assert 10 < 0
E+  where 0 = len([])
E+where [] = >()
E+  where > = .completions
E+where  = Script('from .', path='')

test/test_integration_import.py:21: AssertionError
 1 failed, 1213 passed, 17 skipped, 4 xfailed in 28.67 seconds =
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest test
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2



The tests fail for both python 2.7 and python 3.5.

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#843527: haskell-fail: FTBFS: haddock: No input file(s).

[Chris Lamb]

Source: haskell-fail
Version: 4.9.0.0-1
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,

haskell-fail fails to build from source in unstable/amd64:

  […]
  /usr/bin/haddock --version
  /usr/bin/ghc --numeric-version
  Running Haddock for fail-4.9.0.0...
  /usr/bin/haddock --ghc-version 
'--mathjax=file:///usr/share/javascript/mathjax/MathJax.js'
  creating dist-ghc/build
  creating dist-ghc/build/autogen
  Running hscolour for fail-4.9.0.0...
  creating dist-ghc/doc/html/fail
  creating dist-ghc/doc/html
  creating dist-ghc/doc
  creating dist-ghc/doc/html
  creating dist-ghc/doc/html/fail
  Preprocessing library fail-4.9.0.0...
  creating dist-ghc/doc/html/fail/src
  /usr/bin/HsColour -print-css -odist-ghc/doc/html/fail/src/hscolour.css
  /usr/bin/ghc --print-libdir
  Preprocessing library fail-4.9.0.0...
  creating dist-ghc/doc/html/fail
  /usr/bin/haddock 
'@dist-ghc/doc/html/fail/haddock-response16816927771714636915.txt' 
'--mathjax=file:///usr/share/javascript/mathjax/MathJax.js'
  haddock: No input file(s).
  Haddock failed (no modules?), refusing to create empty documentation package.
  /usr/share/cdbs/1/class/hlibrary.mk:173: recipe for target 
'build-haddock-stamp' failed
  make: *** [build-haddock-stamp] Error 1

  […]

The full build log is attached.


Regards,

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


haskell-fail.4.9.0.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#843528: hyperscan: FTBFS: boost/graph/graph_concepts.hpp:131:19: error: no matching function for call to 'degree(void*&, boost::reverse_graph<boost::adjacency_list<boost::listS, boost::listS, boos

[Chris Lamb]

Source: hyperscan
Version: 4.3.1-1
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,

hyperscan fails to build from source in unstable/amd64:

  […]

  /usr/bin/c++   -Dhs_shared_EXPORTS 
-I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/obj-x86_64-linux-gnu
 -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1 
-I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src
 -isystem 
/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/include
  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -mssse3 -march=core2 
-Wdate-time -D_FORTIFY_SOURCE=2  -DNDEBUG -std=c++11 -Wall -Wextra -Wshadow 
-Wswitch -Wreturn-type -Wcast-qual -Wno-deprecated -Wnon-virtual-dtor 
-fno-strict-aliasing -fabi-version=0 -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -fno-omit-frame-pointer -fvisibility=hidden -Wvla 
-Wpointer-arith -Wno-unused-const-variable -Wno-ignored-attributes 
-Wmissing-declarations -g -O2 -fPIC   -o 
CMakeFiles/hs_shared.dir/src/nfa/goughcompile.cpp.o -c 
/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src/nfa/goughcompile.cpp
  [ 30%] Building CXX object 
CMakeFiles/hs_shared.dir/src/nfa/goughcompile_accel.cpp.o
  /usr/bin/c++   -Dhs_shared_EXPORTS 
-I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/obj-x86_64-linux-gnu
 -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1 
-I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src
 -isystem 
/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/include
  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -mssse3 -march=core2 
-Wdate-time -D_FORTIFY_SOURCE=2  -DNDEBUG -std=c++11 -Wall -Wextra -Wshadow 
-Wswitch -Wreturn-type -Wcast-qual -Wno-deprecated -Wnon-virtual-dtor 
-fno-strict-aliasing -fabi-version=0 -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -fno-omit-frame-pointer -fvisibility=hidden -Wvla 
-Wpointer-arith -Wno-unused-const-variable -Wno-ignored-attributes 
-Wmissing-declarations -g -O2 -fPIC   -o 
CMakeFiles/hs_shared.dir/src/nfa/goughcompile_accel.cpp.o -c 
/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src/nfa/goughcompile_accel.cpp
  [ 30%] Building CXX object 
CMakeFiles/hs_shared.dir/src/nfa/goughcompile_reg.cpp.o
  /usr/bin/c++   -Dhs_shared_EXPORTS 
-I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/obj-x86_64-linux-gnu
 -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1 
-I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src
 -isystem 
/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/include
  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -mssse3 -march=core2 
-Wdate-time -D_FORTIFY_SOURCE=2  -DNDEBUG -std=c++11 -Wall -Wextra -Wshadow 
-Wswitch -Wreturn-type -Wcast-qual -Wno-deprecated -Wnon-virtual-dtor 
-fno-strict-aliasing -fabi-version=0 -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -fno-omit-frame-pointer -fvisibility=hidden -Wvla 
-Wpointer-arith -Wno-unused-const-variable -Wno-ignored-attributes 
-Wmissing-declarations -g -O2 -fPIC   -o 
CMakeFiles/hs_shared.dir/src/nfa/goughcompile_reg.cpp.o -c 
/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src/nfa/goughcompile_reg.cpp
  [ 30%] Building CXX object 
CMakeFiles/hs_shared.dir/src/nfa/mcclellancompile.cpp.o
  /usr/bin/c++   -Dhs_shared_EXPORTS 
-I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/obj-x86_64-linux-gnu
 -I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1 
-I/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/src
 -isystem 
/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1/include
  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161107132007.yj6Rtc2DyF.db.hyperscan/hyperscan-4.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -mssse3 -march=core2 
-Wdate-time -D_FORTIFY_SOURCE=2  -DNDEBUG -std=c++11 -Wall -Wextra -Wshadow 
-Wswitch -Wreturn-type -Wcast-qual -Wno-deprecated -Wnon-virtual-dtor 
-fno-strict-aliasing -fabi-version=0 -Wno-unused-local-typedefs 
-Wno-maybe-uninitialized -fno-omit-frame-pointer -fvisibility=hidden -Wvla 
-Wpointer-arith -Wno-unused-const-variable -Wno-ignored-attributes 
-Wmissing-declarations -g -O2 -fPIC   -o 

Bug#843529: node-dateformat: FTBFS: Error: Cannot find module 'underscore'

[Chris Lamb]

Source: node-dateformat
Version: 1.0.11-1
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,

node-dateformat fails to build from source in unstable/amd64:

  […]

 dh_auto_build
 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161107132446.quqSm7tjme.db.node-dateformat/node-dateformat-1.0.11'
  mocha -R spec
  module.js:327
  throw err;
  ^
  
  Error: Cannot find module 'underscore'
  at Function.Module._resolveFilename (module.js:325:15)
  at Function.Module._load (module.js:276:25)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at Object. 
(/home/lamby/temp/cdt.20161107132446.quqSm7tjme.db.node-dateformat/node-dateformat-1.0.11/test/test_formats.js:3:9)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load (module.js:343:32)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
  at Array.forEach (native)
  at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
  at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
  at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load (module.js:343:32)
  at Function.Module._load (module.js:300:12)
  at Function.Module.runMain (module.js:441:10)
  at startup (node.js:139:18)
  at node.js:974:3
  debian/rules:7: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161107132446.quqSm7tjme.db.node-dateformat/node-dateformat-1.0.11'
  debian/rules:3: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


node-dateformat.1.0.11-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#843354: marked as done (libbrial{, -groebner}-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/include/polybori/BlockDegLexOrder.h, ...)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 13:18:55 +
with message-id 
and subject line Bug#843354: fixed in brial 0.8.5-3
has caused the Debian Bug report #843354,
regarding libbrial{, -groebner}-dev: fails to upgrade from 'jessie' - trying to 
overwrite /usr/include/polybori/BlockDegLexOrder.h, ...
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.)


-- 
843354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbrial-dev,libbrial-groebner-dev
Version: 0.8.5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' 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 libbrial-dev.
  Preparing to unpack .../libbrial-dev_0.8.5-2_amd64.deb ...
  Unpacking libbrial-dev (0.8.5-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbrial-dev_0.8.5-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/polybori/BlockDegLexOrder.h', which is 
also in package libpolybori-dev 0.8.3-3+b2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Processing triggers for libc-bin (2.19-18+deb8u6) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libbrial-dev_0.8.5-2_amd64.deb

  Selecting previously unselected package libbrial-groebner-dev.
  Preparing to unpack .../libbrial-groebner-dev_0.8.5-2_amd64.deb ...
  Unpacking libbrial-groebner-dev (0.8.5-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbrial-groebner-dev_0.8.5-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/polybori/groebner/BitMask.h', which is 
also in package libpolybori-groebner-dev 0.8.3-3+b2
  Processing triggers for libc-bin (2.19-18+deb8u6) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libbrial-groebner-dev_0.8.5-2_amd64.deb


cheers,

Andreas


libpolybori-dev=0.8.3-3+b2_libbrial-dev=0.8.5-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: brial
Source-Version: 0.8.5-3

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated brial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Nov 2016 11:57:21 +
Source: brial
Binary: python-brial python-polybori libbrial-dev libbrial0 libbrial0-dbg 
libbrial-groebner-dev libbrial-groebner0 libbrial-groebner0-dbg
Architecture: source amd64 all
Version: 0.8.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Tobias Hansen 
Description:
 libbrial-dev - polynomials over Boolean Rings, core development files
 libbrial-groebner-dev - development files for libbrial-groebner
 libbrial-groebner0 - computer algebra routines of BRiAl
 libbrial-groebner0-dbg - debug symbols for libbrial-groebner0
 libbrial0  - polynomials over Boolean Rings, shared library
 libbrial0-dbg - debug symbols for libbrial0
 python-brial - polynomials over Boolean Rings, Python module
 python-polybori - transitional package
Closes: 843354
Changes:
 brial (0.8.5-3) unstable; urgency=medium
 .
   * Add Breaks and Replaces to old polybori for the dev packages.
 (Closes: #843354)
Checksums-Sha1:
 504af52152279614109cd950286790eb223da460 2539 brial_0.8.5-3.dsc
 30e516080dbc5bca99f573ce8f3a5831a3ad1a66 11604 brial_0.8.5-3.debian.tar.xz
 e215cef324e6c769adf3ff62ee1e18312f2d50ea 9247 
brial_0.8.5-3_20161107T130607z-14b39213.buildinfo
 0cfbc227fb674ddd9bd9e4bd7a4067899463da0f 97548 

Bug#831833: marked as done (bedtools groupby broken; will break users pipelines.)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 13:18:37 +
with message-id 
and subject line Bug#831833: fixed in bedtools 2.26.0+dfsg-3
has caused the Debian Bug report #831833,
regarding bedtools groupby broken; will break users pipelines.
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.)


-- 
831833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bedtools
Version: 2.26.0-1
Severity: serious
Tags: upstream

Hi all,

at work I was just bitten by upstream issue 418, reporting that `bedtools
groupby` is broken.

https://github.com/arq5x/bedtools2/issues/418

I am filing this bug to prevent migration to Squeeze.

Have a nice day,

-- 
Charles
--- End Message ---
--- Begin Message ---
Source: bedtools
Source-Version: 2.26.0+dfsg-3

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

Debian distribution maintenance software
pp.
Charles Plessy  (supplier of updated bedtools 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, 05 Nov 2016 21:48:09 +0900
Source: bedtools
Binary: bedtools bedtools-test
Architecture: source
Version: 2.26.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Charles Plessy 
Description:
 bedtools   - suite of utilities for comparing genomic features
 bedtools-test - test data for the bedtools package
Closes: 831833
Changes:
 bedtools (2.26.0+dfsg-3) unstable; urgency=medium
 .
   d6d3452 Sync with upstream repo at commit 6bf23c, closes: #831833.
Checksums-Sha1:
 4472b01419bd4fe181ab82540df71ed9c013d643 2115 bedtools_2.26.0+dfsg-3.dsc
 4b410659aa085ebd60e6f8bc9d37a0845d0cf3a2 51636 
bedtools_2.26.0+dfsg-3.debian.tar.xz
Checksums-Sha256:
 c64c137b24feb56d7c4733724f8c425a1271b907a14c72f4953cbf626f94427e 2115 
bedtools_2.26.0+dfsg-3.dsc
 7953013fcab73dc770dbe81b7615f6618b060b05913780c1a8c6a4f7643455ae 51636 
bedtools_2.26.0+dfsg-3.debian.tar.xz
Files:
 f0c31846c114bc05561a10f8572d800c 2115 science optional 
bedtools_2.26.0+dfsg-3.dsc
 df5973d57bee1e8944d13903a04f3bb6 51636 science optional 
bedtools_2.26.0+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJYIHwGAAoJEMW9bI8ildUCRoUP/RmbcnvPbDu1BmwONTU3M7k2
N/KQfm6oYRAF9+HgEyWmk84vA9ddKHB2w2Z7foI8NgoGwZ1Q+ckH6KJokUsQSmLc
EcGDzrCQSR7qjMyIx3V50Jdcfr6raKhBZ9wXYLGkhc210h8WFrGcj9heYhyY2sxb
wjY0VTXyamJafEP0bf5r/kEWmpPukOd3f36odjTK3Bi4t8ilzRw/PMqS/Ae5rScq
tfHIypD+sHvwsNeK6FOh43tPlkyMpTMPBP84+lAlWs0KQcN6X+Bo4tChxVwj8o0m
hItSPhPk3a04JXx8kZh0Buod6UIyRfzBaZsatOK9ng/AkrOfcXmiK+q18oSuBsva
yAn34G50QCldAJZGx7I55iEqyW00Zo/U+sSywNy/MRcSPqFPQCQEpLQzfa0rTkc+
xN8b9HFUgBLPbTB5maYipWsyWIVzWTMUx18TpjiJtbVihHjbYnIVluphT/byf82c
H/bEKCMtewWaRmyLOnPmTPB6iGxc8qNH7OqPPMOy1IZjQ7pblySP5R9DBU/58PHQ
nEYMgERjWiKGRjyb7MHNZz9n2kUXabFgd6ASrSuciqK/z23qUWXvbsWYGvKc7v/k
AKoImcn1A7Qxz88AGZpLaTcF0ao9VTDo7WFhwsn5qGkfwRck+KoBlVZCCfSLEgj3
/Dp8sGA2arFvGe+sfM/k
=Ictc
-END PGP SIGNATURE End Message ---

Processed: tagging 842927

[Debian Bug Tracking System]

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

> tags 842927 + pending
Bug #842927 [libboost-python1.62.0] libboost-python1.62.0 exports Python 2 
symbols for Python 3
Bug #842928 [libboost-python1.62.0] libboost-python1.62.0 exports Python 2 
symbols for Python 3
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#843136: drumgizmo FTBFS on mips and mipsel: error: undefined reference to `__atomic_load_8'

[Radovan Birdic]

Hi,

On 04/11/16 10:58, James Cowgill wrote:
> > +  #include 
> Typo? You want 

Yes, this is my fault. The name of the library is not properly specified.

> >#include 
> > +  std::atomic x;
> > +  std::atomic y;
> I don't think you should rely on these types being in the global namespace.

I modified test and removed uintptr_t type, because this type may not be 
defined in some library implementations.
More about that:
http://www.cplusplus.com/reference/cstdint/

Could you please take a look at new patch I attached? It includes a new test 
for checking is libatomic needed to link.

Regards,
Radovan--- drumgizmo-0.9.11.orig/configure.ac
+++ drumgizmo-0.9.11/configure.ac
@@ -473,9 +473,10 @@ dnl ==
 AC_MSG_CHECKING([for the need for linkage with libatomic])
 AC_LANG_PUSH([C++])
 AC_LINK_IFELSE([AC_LANG_SOURCE[
+  #include 
   #include 
   int main() {
-struct Test { int val; };
+struct Test { uintmax_t val; };
 std::atomic s;
 return s.is_lock_free()?1:0;
   }

Bug#822201: marked as done (ca-certificates-java: postinst and trigger should fail if no known jvm is found)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 13:03:49 +
with message-id <e1c3jax-0004ki...@fasolo.debian.org>
and subject line Bug#822201: fixed in ca-certificates-java 20161107
has caused the Debian Bug report #822201,
regarding ca-certificates-java: postinst and trigger should fail if no known 
jvm is found
to be marked as done.

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

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


-- 
822201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: ca-certificates-java
Source-Version: 20161107

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

A summary of

Bug#843482: marked as done (aubio: FTBFS on PowerPC variants: test_zeros fails)

[Debian Bug Tracking System]

Your message dated Mon, 07 Nov 2016 13:03:37 +
with message-id 
and subject line Bug#843482: fixed in aubio 0.4.3-2
has caused the Debian Bug report #843482,
regarding aubio: FTBFS on PowerPC variants: test_zeros fails
to be marked as done.

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

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


-- 
843482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aubio
Version: 0.4.1-2.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of aubio for ppc64el and the non-release architectures powerpc
and ppc64 all failed; see below for an excerpt from the ppc64el log at
https://buildd.debian.org/status/fetch.php?pkg=aubio=ppc64el=0.4.3-1=1478460825
Could you please take a look?

Thanks!

  ==
  FAIL: test_zeros (test_phasevoc.aubio_pvoc_test_case)
  check the resynthesis of zeros gives zeros
  --
  Traceback (most recent call last):
File "/«PKGBUILDDIR»/python/tests/test_phasevoc.py", line 49, in test_zeros
  assert_equal ( s.phas, 0.)
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 322, 
in assert_equal
  return assert_array_equal(actual, desired, err_msg, verbose)
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 813, 
in assert_array_equal
  verbose=verbose, header='Arrays are not equal')
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 739, 
in assert_array_compare
  raise AssertionError(msg)
  AssertionError: 
  Arrays are not equal
  
  (mismatch 34.6978557505%)
   x: array([ 0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
  0.  ,  0.  ,  0.  ,  0.  , -0.  ,  0.  ,...
   y: array(0.0)
  
  ==
  FAIL: test_zeros (test_fft.aubio_fft_test_case)
  check the transform of zeros is all zeros
  --
  Traceback (most recent call last):
File "/«PKGBUILDDIR»/python/tests/test_fft.py", line 36, in test_zeros
  assert_equal ( fftgrain.phas, 0 )
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 322, 
in assert_equal
  return assert_array_equal(actual, desired, err_msg, verbose)
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 813, 
in assert_array_equal
  verbose=verbose, header='Arrays are not equal')
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 739, 
in assert_array_compare
  raise AssertionError(msg)
  AssertionError: 
  Arrays are not equal
  
  (mismatch 31.5175097276%)
   x: array([ 0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
  0.  ,  0.  ,  0.  ,  0.  , -0.  ,  0.  ,...
   y: array(0)
  
  --
  Ran 745 tests in 12.995s
  
  FAILED (failures=2, skipped=4)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: aubio
Source-Version: 0.4.3-2

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

Debian distribution maintenance software
pp.
Paul Brossier  (supplier of updated aubio 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: Mon, 07 Nov 2016 13:18:01 +0100
Source: aubio
Binary: libaubio-dev libaubio5 aubio-tools libaubio-doc python-aubio 
python3-aubio
Architecture: source
Version: 0.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Paul Brossier 

Processed: Re: Bug#828308: downgrade severity, because the bug is not RC anymore

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #828308 [src:gdcm] missing include for 'X509_STORE_CTX cert_ctx'
Severity set to 'important' from 'serious'

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