Bug#837017: libvisio: FTBFS: Tests failures

[Rene Engelhard]

Hi,

On Thu, Sep 08, 2016 at 08:19:20AM +0200, Lucas Nussbaum wrote:
> Could you share your build log and diff it with me ?

Works even in cowbuilder for me.

http://zyklop.dyndns.org/~rene/libvisio_0.1.5-1.log

Regards,

Rene

Bug#835417: marked as done (opensurgsim: FTBFS with eigen3 3.3~beta2-1)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 05:22:21 +
with message-id 
and subject line Bug#835417: fixed in opensurgsim 0.6.0-6
has caused the Debian Bug report #835417,
regarding opensurgsim: FTBFS with eigen3 3.3~beta2-1
to be marked as done.

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

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


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

Source: opensurgsim
Version: 0.6.0-5
Severity: serious

After fixing the issue with GCC6 in #831096, opensurgsim still FTBFS 
with eigen3 3.3~beta2-1, however it builds fine with 3.3~beta1-2.
Bug #835411 has been filed against eigen3.  Part of the problem in 
eigen3 has already been fixed upstream, although it is not clear yet 
whether opensurgsim will require any changes.
--- End Message ---
--- Begin Message ---
Source: opensurgsim
Source-Version: 0.6.0-6

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated opensurgsim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 22:39:37 +0200
Source: opensurgsim
Binary: libopensurgsim libopensurgsim-dev opensurgsim-doc
Architecture: source amd64 all
Version: 0.6.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libopensurgsim - Free platform for surgical simulation - runtime
 libopensurgsim-dev - Free platform for surgical simulation - development
 opensurgsim-doc - Free platform for surgical simulation - documentation
Closes: 831096 835417
Changes:
 opensurgsim (0.6.0-6) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload
   * cme fix dpkg-control
   * Fix FTBFS with GCC 6 (thanks for the patch to Graham Inggs
 )
 Closes: #831096
 .
   [ Paul Novotny ]
   * Fix FTBFS with eigen3 3.3~beta2-1 (Closes: #835417)
Checksums-Sha1:
 60cb9db8a7f243c473a45a18802fc3807a9f10ea 2332 opensurgsim_0.6.0-6.dsc
 465b13132bcc2729f2c365960373334879018e42 14568 
opensurgsim_0.6.0-6.debian.tar.xz
 e3e8a45484288d6fec04c20dc84997179a4f500c 74186084 
libopensurgsim-dbgsym_0.6.0-6_amd64.deb
 347946566f20a2cbaa6654a0b857e3da858cb868 180320 
libopensurgsim-dev_0.6.0-6_amd64.deb
 e7ca39bacc83ede94e4efa7bf55895b3a0bae2b3 1433240 
libopensurgsim_0.6.0-6_amd64.deb
 ccc33f8d6f1e368414cacca2f06a8b60ef3e3dc2 2239864 
opensurgsim-doc_0.6.0-6_all.deb
Checksums-Sha256:
 f8b4d5788007d1f3c122b1fbfe2315e445c2d6468735af9646133de55d01e3d8 2332 
opensurgsim_0.6.0-6.dsc
 19853ca01a3393fc3364cbd8d9d9662a86caaeb4ba8f1cfe6fd1c2f208692acf 14568 
opensurgsim_0.6.0-6.debian.tar.xz
 7216e2ddbf1c2bda40c44fc4f4b9265df96e138908287fb696dfb12bc4dc7ebc 74186084 
libopensurgsim-dbgsym_0.6.0-6_amd64.deb
 f5543aa883d0e8d841ae2f96cccbda6b7f7090b612fc93661c80fcaaec79 180320 
libopensurgsim-dev_0.6.0-6_amd64.deb
 d850efc84f92e415418b7f2c763e0e446299c90e5d6c442fbb1cfeb9c5e5201a 1433240 
libopensurgsim_0.6.0-6_amd64.deb
 7b1d99e0414be3a467c62d0fdc7ded143d0e771a3e9b1ff2342cc9a6f974c3c7 2239864 
opensurgsim-doc_0.6.0-6_all.deb
Files:
 574c0a0345b8f467925cc1caa9e2f380 2332 science optional opensurgsim_0.6.0-6.dsc
 49a56da0ff3d884bb380dd3f047bb027 14568 science optional 
opensurgsim_0.6.0-6.debian.tar.xz
 bea8c4b1aa1c8d66433dce7dd9c599da 74186084 debug extra 
libopensurgsim-dbgsym_0.6.0-6_amd64.deb
 1787c2c0510df12a81de9ac1373caa74 180320 libdevel optional 
libopensurgsim-dev_0.6.0-6_amd64.deb
 3cdfadbc5fd752d29b09bd71993740a3 1433240 libs optional 
libopensurgsim_0.6.0-6_amd64.deb
 d448e8e32a4cad609e767f3ee16a38a4 2239864 doc optional 
opensurgsim-doc_0.6.0-6_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX0jXkAAoJEFeKBJTRxkbRh7UP/R2LQS7Sdkd7wlLyWun4w90I
lB5oEX94UdBp33CQeWYTrGGOfUy5iV4yqLNmy0H9J+E3snatSDqHkmgSyju51E97
gY/7pyoowis8S7HXIJoF2mJzrhqjIcs993PMHuZCrpoLV0lJUo166IEBqKWyVZ5h

Bug#831096: marked as done (opensurgsim: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 05:22:21 +
with message-id 
and subject line Bug#831096: fixed in opensurgsim 0.6.0-6
has caused the Debian Bug report #831096,
regarding opensurgsim: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: 
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.)


-- 
831096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensurgsim
Version: 0.6.0-5
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):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> [  0%] Building CXX object 
> GoogleMock/CMakeFiles/gmock.dir/usr/src/gtest/src/gtest-all.cc.o
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/GoogleMock && /usr/bin/c++   
> -DBOOST_ALL_DYN_LINK -DGTEST_CREATE_SHARED_LIBRARY=1 
> -D_POSIX_C_SOURCE=200809L -Dgmock_EXPORTS -I/«PKGBUILDDIR» -isystem 
> /usr/include/eigen3 -isystem 
> /usr/lib/x86_64-linux-gnu/cmake/yaml-cpp/../../../../include 
> -I/usr/src/gmock/include -I/usr/src/gmock -I/usr/src/gtest/include 
> -I/usr/src/gtest  -g -O2 -fstack-protector-strong -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wall  -std=gnu++11 -fPIC   -g -O2 
> -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2  -Wall  -std=gnu++11 
> -Wall -Wshadow -DGTEST_HAS_PTHREAD=1 -fexceptions -Wextra 
> -Wno-unused-parameter -Wno-missing-field-initializers -o 
> CMakeFiles/gmock.dir/usr/src/gtest/src/gtest-all.cc.o -c 
> /usr/src/gtest/src/gtest-all.cc
> In file included from /usr/include/c++/6/ext/string_conversions.h:41:0,
>  from /usr/include/c++/6/bits/basic_string.h:5402,
>  from /usr/include/c++/6/string:52,
>  from /usr/include/c++/6/bits/locale_classes.h:40,
>  from /usr/include/c++/6/bits/ios_base.h:41,
>  from /usr/include/c++/6/ios:42,
>  from /usr/include/c++/6/ostream:38,
>  from /usr/include/gtest/gtest.h:55,
>  from /usr/src/gtest/src/gtest-all.cc:39:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** 
> [GoogleMock/CMakeFiles/gmock.dir/usr/src/gtest/src/gtest-all.cc.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/opensurgsim_0.6.0-5_unstable_gcc6.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: opensurgsim
Source-Version: 0.6.0-6

We believe that the bug you reported is fixed in the latest version of
opensurgsim, 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.
Andreas Tille  (supplier of updated opensurgsim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 22:39:37 +0200
Source: opensurgsim
Binary: libopensurgsim libopensurgsim-dev opensurgsim-doc
Architecture: source amd64 all
Version: 0.6.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libopensurgsim - Free platform for surgical simulation - runtime
 libopensurgsim-dev - 

Processed: severity of 830568 is normal, tagging 830568

[Debian Bug Tracking System]

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

> severity 830568 normal
Bug #830568 [src:python-asyncssh] python-asyncssh: accesses the internet during 
build
Severity set to 'normal' from 'serious'
> tags 830568 + wontfix
Bug #830568 [src:python-asyncssh] python-asyncssh: accesses the internet during 
build
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Bug#775541: tests of new packages

[Vincent McIntyre]

I found one further issue which is related to  #738063.

I wanted to limit the exports to supporting version 2 and 3.

I first set RPCMOUNTDOPTS="--manage-gids --no-nfs-version 4"
as explained in /etc/default/nfs-kernel-server.
But I found I also needed add the following to that file:

   RPCNFSDPRIORITY=0

 + # other options for nfsd
 + # To disable NFSv4 on the server, specify '--no-nfs-version 4' here also
 + RPCNFSDOPTS="--no-nfs-version 4"


I discovered this by reading the source of the new script
/usr/lib/systemd/scripts/nfs-utils_env.sh
which constructs the RPCNFSDARGS variable used in
the /lib/systemd/system/nfs-server.service file.

If you upload a new version of this package, could you add an
empty definition of RPCNFSDOPTS to /etc/default/nfs-kernel-server,
so people can find it?

Users of the init script would also benefit from this change.

Thanks
Vince

Bug#834087: Bug#832656: runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory

[Anders Kaseorg]

Control: tags -1 + moreinfo

On Thu, 28 Jul 2016, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package failed to install.
> […]
>   ln: failed to create symbolic link '/etc/service/bcron-sched': No such file 
> or directory
> […]
> Similar problems were seen in different *-run packages.

This is marked as affecting git-daemon-run, but I can’t figure out what 
problem is being reported.  ‘apt install git-daemon-run’ succeeds for me 
in a sid chroot.

However, there seems to be a suggestion that fixing the problem, whatever 
it is, requires switching the packaging to Debhelper, which is in progress 
(awaiting sponsorship): https://bugs.debian.org/834886.

Anders

Processed: Re: Bug#832656: runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #834087 [git-daemon-run] runit: breaks users of runit: ln: failed to create 
symbolic link '/etc/service/bcron-sched': No such file or directory
Added tag(s) moreinfo.

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

Bug#775541: tests of new packages

[Vincent McIntyre]

Thanks Andreas for those new packages.
I did some testing of the 1.2.8-9.2 packages on a clean jessie install.
They are pretty close but I found an issue with NFS exports in one case.

I used the attached check.sh script to show the state of various targets
as I changed things. The attached results.tar shows the output from it.
Between each major stage below, the system is rebooted.
Then I log in and run check.sh before doing anything else.
Throughout, /etc/network/interfaces contained:
  source /etc/network/interfaces.d/*
  auto lo
  iface lo inet loopback
  allow-hotplug eth0
  iface eth0 inet dhcp
and /etc/network/interfaces.d/ was empty.

step 1 - jessie system with nfs packages 1.2.8-9
 one fstab mount, no exports. no changes to /etc/default/nfs-*.
 The fstab mount works ok; it tries to mount it way too early
 but we invoke it with the 'bg' option so eventually it works.

step 2 - as above but with the _netdev option added to the fstab entry.
 System still tries to mount too early, before dhclient is done,
 but it works in the end.

step 3 - as above but export one filesystem.
 The fstab mount works, as above.
 Tried a few different ways to do the exports
   - wildcard host (step3.1)
 This works ok.
   - point the export at a single host (step3.2)
 This tries to start mountd to early, before it can resolve
 the hostname given in the exports file.
 As a result we end up with an empty export list:
 # showmount -e
 Export list for install:
 #
 Restarting the service once the system is fully booted works
 # systemctl restart nfs-kernel-server.service
 # showmount -e
 Export list for install:
 /data/INSTALL_1 mayhem.atnf.CSIRO.AU
 #
   - point the export at a netgroup (step3.3)
 This works, even though the netgroup cannot be resolved
 (there's no definition for it).
 # showmount -e
 Export list for install:
 /data/INSTALL_1 @all_hosts
 #

NB nfs-kernel-server starts before dhclient
Sep 08 17:04:46 install nfs-kernel-server[657]: Exporting directories for NFS 
kernel daemon
Sep 08 17:04:46 install kernel: NFSD: Using /var/lib/nfs/v4recovery as the 
NFSv4 state recovery directory
Sep 08 17:04:46 install kernel: NFSD: starting 90-second grace period (net 
818ba280)
...
Sep 08 17:04:46 install rpc.mountd[738]: Version 1.2.8 starting
Sep 08 17:04:46 install nfs-kernel-server[657]: Starting NFS kernel daemon: 
nfsd mountd.
Sep 08 17:04:46 install acpid[734]: starting up with netlink and the input layer
Sep 08 17:04:46 install acpid[734]: 1 rule loaded
Sep 08 17:04:46 install acpid[734]: waiting for events: event logging is off
...
Sep 08 17:04:49 install kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: None
Sep 08 17:04:49 install kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
becomes ready
Sep 08 17:04:50 install dhclient[532]: DHCPDISCOVER on eth0 to 255.255.255.255 
port 67 interval 6
...
Sep 08 17:04:56 install ifup[522]: Starting rpcbind (via systemctl): 
rpcbind.service.
Sep 08 17:04:56 install ifup[522]: Starting nfs-common (via systemctl): 
nfs-common.service.
Sep 08 17:04:56 install kernel: Key type dns_resolver registered
Sep 08 17:04:56 install kernel: NFS: Registering the id_resolver key type
Sep 08 17:04:56 install kernel: Key type id_resolver registered
Sep 08 17:04:56 install kernel: Key type id_legacy registered


step3.4 - install new nfs packages but don't reboot yet.
  I didn't analyse this step carefully

step 4 - jessie system with nfs packages 1.2.8-9.2
 one fstab mount, one exported directory.

 rpc.mountd fails to start because it wants rpcbind to be there,
 but rpcbind has not been started yet. showmount -e fails:
 # showmount -e
 clnt_create: RPC: Program not registered

step4.1 modify  /lib/systemd/system/nfs-mountd.service,
   - After=network.target local-fs.target
   + After=rpcbind.target network.target local-fs.target
run systemd daemon-reload
but don't reboot.
The exports are still not there
# showmount -e
clnt_create: RPC: Program not registered

re run exports, it fails
# exportfs -rav
exporting @all_hosts:/data/INSTALL_1
# showmount -e
clnt_create: RPC: Program not registered
#

step 5 - reboot after step4.1:

 usr-local.mount starts a little (1-2s) later. It starts
 just after ifup, but before dhclient has gotten an answer
 so it can't resolve the server hostname, but eventually
 the mount does work.

 Exports also work, in some cases:
 - wildcard case is OK (step5.1)
 # showmount -e
 Export list for install:
 

Bug#837013: marked as done (notmuch: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 01:34:29 +
with message-id 
and subject line Bug#837013: fixed in notmuch 0.22.2-1
has caused the Debian Bug report #837013,
regarding notmuch: FTBFS: Tests failures
to be marked as done.

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

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


-- 
837013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: notmuch
Version: 0.22.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 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):
> gpg: no valid OpenPGP data found.
> Added 2 new messages to the database.
>  missing prerequisites: database-v1.tar.xz - fetch with 'make 
> download-test-databases'
>  SKIP   all tests in T530-upgrade
>  BROKEN No ghosts should remain after deletion of second message
>   --- T590-thread-breakage.22.expected2016-09-06 22:45:08.15600 
> +
>   +++ T590-thread-breakage.22.output  2016-09-06 22:45:08.15600 
> +
>   @@ -1 +1 @@
>   -0
>   +1
> 
> Notmuch test suite complete.
> 772/778 tests passed.
> 1 broken test failed as expected.
> 5 tests failed.
> test/Makefile.local:64: recipe for target 'test' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/notmuch_0.22.1-3_unstable.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: notmuch
Source-Version: 0.22.2-1

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated notmuch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 19:09:53 -0300
Source: notmuch
Binary: notmuch libnotmuch4 libnotmuch-dev python-notmuch python3-notmuch 
ruby-notmuch notmuch-emacs notmuch-vim notmuch-mutt notmuch-dbg
Architecture: source
Version: 0.22.2-1
Distribution: unstable
Urgency: medium
Maintainer: Carl Worth 
Changed-By: David Bremner 
Description:
 libnotmuch-dev - thread-based email index, search and tagging (development)
 libnotmuch4 - thread-based email index, search and tagging (runtime)
 notmuch- thread-based email index, search and tagging
 notmuch-dbg - thread-based email index, search and tagging - debugging symbols
 notmuch-emacs - thread-based email index, search and tagging (emacs interface)
 notmuch-mutt - thread-based email index, search and tagging (Mutt interface)
 notmuch-vim - thread-based email index, search and tagging (vim interface)
 python-notmuch - python interface to the notmuch mail search and index library
 python3-notmuch - Python 3 interface to the notmuch mail search and index 
library
 ruby-notmuch - Ruby interface to the notmuch mail search and index library
Closes: 837013
Changes:
 notmuch (0.22.2-1) unstable; urgency=medium
 .
   * Fix test suite compatibility with GnuPG 2.1.15.  Bug fix: "FTBFS:
 Tests failures", thanks to Lucas Nussbaum (Closes: #837013).
Checksums-Sha1:
 34e38504cf884a97ab24b268a81ee76eb256f899 2788 notmuch_0.22.2-1.dsc
 f60825656b0d00a6a60f82a01ab687f5bb46e839 683796 notmuch_0.22.2.orig.tar.gz
 164db9d10dd4eeba901d8bb59da8c724a89e4f97 15296 notmuch_0.22.2-1.debian.tar.xz
Checksums-Sha256:
 f96a61dfacccdcc893ec0b2c12238cb96fb37ff394d0f203139ffed839dd5e59 2788 
notmuch_0.22.2-1.dsc
 6cd19c61634079981b2d8f4b7cb4eb953cba2a36272520603682d813d2bd7ed1 683796 
notmuch_0.22.2.orig.tar.gz
 0c6a3ec7c8c231b35599ebd0ac3ffc4069c9eefc6be41ed36aa3ad5f65f106c6 15296 

Bug#837123: ([anna] segfault in wheezy installer)

[Vincent McIntyre]

I just realised this went to the libc maintainers;
I was expecting it would go to the debian-installer team.

This might be an issue in the way libc6-udeb is being used
within debian-installer, rather than libc6-udeb itself.

I don't know how to figure out if that is the case;
if it is the case, please do reassign.

Kind regards
Vince

Bug#835736: marked as done (containerd: FTBFS: dh_auto_build: go install -v -p 1 github.com/docker/containerd github.com/docker/containerd/api/grpc/server github.com/docker/containerd/api/grpc/types g

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 00:48:36 +
with message-id 
and subject line Bug#835736: fixed in containerd 0.2.1~ds1-3
has caused the Debian Bug report #835736,
regarding containerd: FTBFS: dh_auto_build: go install -v -p 1 
github.com/docker/containerd github.com/docker/containerd/api/grpc/server 
github.com/docker/containerd/api/grpc/types 
github.com/docker/containerd/api/http/pprof 
github.com/docker/containerd/containerd 
github.com/docker/containerd/containerd-shim github.com/docker/containerd/ctr 
github.com/docker/containerd/osutils github.com/docker/containerd/runtime 
github.com/docker/containerd/specs github.com/docker/containerd/supervisor 
returned exit code 2
to be marked as done.

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

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


-- 
835736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: containerd
Version: 0.2.1~ds1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 github.com/docker/containerd 
> github.com/docker/containerd/api/grpc/server 
> github.com/docker/containerd/api/grpc/types 
> github.com/docker/containerd/api/http/pprof 
> github.com/docker/containerd/containerd 
> github.com/docker/containerd/containerd-shim github.com/docker/containerd/ctr 
> github.com/docker/containerd/osutils github.com/docker/containerd/runtime 
> github.com/docker/containerd/specs github.com/docker/containerd/supervisor
> github.com/docker/containerd
> github.com/golang/protobuf/proto
> golang.org/x/net/context
> golang.org/x/net/http2/hpack
> golang.org/x/net/lex/httplex
> golang.org/x/net/http2
> golang.org/x/net/internal/timeseries
> golang.org/x/net/trace
> google.golang.org/grpc/codes
> google.golang.org/grpc/credentials
> google.golang.org/grpc/grpclog
> google.golang.org/grpc/internal
> google.golang.org/grpc/metadata
> google.golang.org/grpc/naming
> google.golang.org/grpc/peer
> google.golang.org/grpc/transport
> google.golang.org/grpc
> github.com/docker/containerd/api/grpc/types
> # github.com/docker/containerd/api/grpc/types
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: cannot use 
> _API_CreateContainer_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1141: cannot use 
> _API_UpdateContainer_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1145: cannot use 
> _API_Signal_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1149: cannot use 
> _API_UpdateProcess_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1153: cannot use 
> _API_AddProcess_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1157: cannot use 
> _API_CreateCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1161: cannot use 
> _API_DeleteCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1165: cannot use 
> _API_ListCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, 

Bug#837123: [anna] segfault in wheezy installer

[Vincent McIntyre]

Package: libc6-udeb
Version: 2.13-38+deb7u10
Severity: grave
Justification: breaks installation entirely

The wheezy installer fails with anna reporting a segfault:

...
anna[5033]: DEBUG: retrieving libc6-udeb 2.13-38+deb7u10
anna[5033]: DEBUG: retrieving finish-install 2.41wheezy1
anna[5033]: DEBUG: Segmentation fault
anna[5033]: WARNING **: package retrieval failed
kernel: [   66.427372] wget[5382]: segfault a 0 ip 7176c922c0ca sp 
7ffc8ca83890 error 6 in libresolv-2.13.so[7f76c9222000+13000]

This occurs shortly after libc6-udev is downloaded,
according to the installer interactive display.

Background
--
I was trying to reinstall an older system with wheezy.
I was using the PXE install image available on 2016-09-08 UTC, at
ftp.au.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot

The mirror shows the last update timestamp as 2016-05-31.
debian-installer/amd64/boot-screens/f1.txt has the fairly useless
build date stamp 20130613+deb7u3+b2.

This installation method was working fine with earlier installer
versions. The breakage has been there some months I'd say.
I only became fully aware of it yesterday.

I don't think the mirror is out of date; I got the same result
with the netboot installer image downloaded from ftp.us.debian.org.


The log above was copied by eye from the console,
I was unable to install the openssh-client=udeb to copy the logs,
thanks to the segfault.

The core of the issue is probably screwed up libc6 versions,
see bugs 740068, 833432

Other package versions that may be of interest
 base-installer: 1.130
 cdebconf-udeb: 0.182
 di-utils: 1.92+deb7u1
 libc6-udeb: 2.13-38+deb7u10
 anna: 1.44+deb7u1

It's really unfortunate to have the oldstable installer break like this.
I hope it can be fixed, age notwithstanding.

Kind regards
Vince
-- 

Bug#835712: marked as done (torus-trooper: FTBFS: src/abagames/tt/shape.d:442:48: error: std.math.fabs called with argument types (int) matches both:)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 00:23:03 +
with message-id 
and subject line Bug#835712: fixed in torus-trooper 0.22.dfsg1-11
has caused the Debian Bug report #835712,
regarding torus-trooper: FTBFS: src/abagames/tt/shape.d:442:48: error: 
std.math.fabs called with argument types (int) matches both:
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.)


-- 
835712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: torus-trooper
Version: 0.22.dfsg1-10
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[2]: Entering directory '/<>'
> gdc -o torus-trooper import/SDL.d import/SDL_active.d import/SDL_audio.d 
> import/SDL_byteorder.d import/SDL_cdrom.d import/SDL_copying.d 
> import/SDL_endian.d import/SDL_error.d import/SDL_events.d 
> import/SDL_getenv.d import/SDL_joystick.d import/SDL_keyboard.d 
> import/SDL_keysym_.d import/SDL_mixer.d import/SDL_mouse.d import/SDL_mutex.d 
> import/SDL_quit.d import/SDL_rwops.d import/SDL_syswm.d import/SDL_thread.d 
> import/SDL_timer.d import/SDL_types.d import/SDL_version_.d 
> import/SDL_video.d import/bulletml.d import/opengl.d import/openglu.d 
> src/abagames/tt/barrage.d src/abagames/tt/boot.d 
> src/abagames/tt/bulletactor.d src/abagames/tt/bulletactorpool.d 
> src/abagames/tt/bulletimpl.d src/abagames/tt/bullettarget.d 
> src/abagames/tt/camera.d src/abagames/tt/enemy.d 
> src/abagames/tt/floatletter.d src/abagames/tt/gamemanager.d 
> src/abagames/tt/letter.d src/abagames/tt/particle.d 
> src/abagames/tt/prefmanager.d src/abagames/tt/replay.d 
> src/abagames/tt/screen.d src/abagames/tt/shape.d src/abagames/tt/ship.d 
> src/abagames/tt/shot.d src/abagames/tt/soundmanager.d 
> src/abagames/tt/stagemanager.d src/abagames/tt/title.d 
> src/abagames/tt/tunnel.d src/abagames/util/actor.d 
> src/abagames/util/bulletml/bullet.d 
> src/abagames/util/bulletml/bulletsmanager.d src/abagames/util/iterator.d 
> src/abagames/util/logger.d src/abagames/util/prefmanager.d 
> src/abagames/util/rand.d src/abagames/util/sdl/displaylist.d 
> src/abagames/util/sdl/gamemanager.d src/abagames/util/sdl/input.d 
> src/abagames/util/sdl/luminous.d src/abagames/util/sdl/mainloop.d 
> src/abagames/util/sdl/pad.d src/abagames/util/sdl/recordablepad.d 
> src/abagames/util/sdl/screen.d src/abagames/util/sdl/screen3d.d 
> src/abagames/util/sdl/sdlexception.d src/abagames/util/sdl/sound.d 
> src/abagames/util/sdl/texture.d src/abagames/util/tokenizer.d 
> src/abagames/util/vector.d -Iimport -Isrc -Wno-deprecated -frelease -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -lSDL 
> -lGL -lGLU -lSDL_mixer -lbulletml
> cc1d: warning: command line option '-Wformat=1' is valid for 
> C/C++/ObjC/ObjC++ but not for D
> cc1d: warning: command line option '-Wdate-time' is valid for 
> C/C++/Fortran/ObjC/ObjC++ but not for D
> src/abagames/tt/shape.d:442:48: error: std.math.fabs called with argument 
> types (int) matches both:
> /usr/lib/gcc/x86_64-linux-gnu/6/include/d/std/math.d:3419:6: 
> std.math.fabs(real x)
> and:
> /usr/lib/gcc/x86_64-linux-gnu/6/include/d/std/math.d:3425:7: 
> std.math.fabs(float x)
>  float y1 = -0.5 + (1.0 / divNum) * fabs(i - divNum / 2) * 2;
> ^
> Makefile:8: recipe for target 'torus-trooper' failed
> make[2]: *** [torus-trooper] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/torus-trooper_0.22.dfsg1-10_unstable.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: torus-trooper
Source-Version: 0.22.dfsg1-11

We believe that the bug you reported is fixed in the latest version of
torus-trooper, 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 

Processed: bug 834121 is forwarded to https://github.com/rsyslog/liblognorm/issues/217

[Debian Bug Tracking System]

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

> forwarded 834121 https://github.com/rsyslog/liblognorm/issues/217
Bug #834121 [src:liblognorm] FTBFS on various architectures, test suite times 
out
Set Bug forwarded-to-address to 
'https://github.com/rsyslog/liblognorm/issues/217'.
> thanks
Stopping processing here.

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

Bug#837121: gazebo: please restrict libkido-dev (build-)dependency to architectures where it is available.

[Peter Green]

Package: gazebo
Version: 7.3.0+dfsg-3
Severity: serious
Tags: patch

The most recent version of gazebo added a build-dependency on 
libkido-dev to the source package and added a binary on libkido-dev to 
libgazebo7-dev


No mention of this was made in the changelog and no other changes in the 
upload seem to be related but 
https://anonscm.debian.org/git/debian-science/packages/gazebo.git/commit/?id=80f9a218ccebb32258812afdf1cce6b50ab88126 
indicates this was to add support for a new feature.


libkido-dev is only available on a handful of architectures. As a result 
this new (build-)dependency is blocking the migration of the new version 
of the package (and hence the FTBFS fix) to testing.


The attatched patch restricts the (build-)dependencies on libkido-dev to 
the architectures where it is actually available (amd64, arm64, i386, 
ppc64el and alpha)
diff -Nru gazebo-7.3.0+dfsg/debian/changelog gazebo-7.3.0+dfsg/debian/changelog
--- gazebo-7.3.0+dfsg/debian/changelog  2016-08-31 17:57:53.0 +
+++ gazebo-7.3.0+dfsg/debian/changelog  2016-09-07 15:06:23.0 +
@@ -1,3 +1,10 @@
+gazebo (7.3.0+dfsg-3+rpi1) stretch-staging; urgency=medium
+
+  * Restrict (build-)dependency on libkido-dev to architectures where that 
package
+is actually available (amd64, arm64, i386, ppc64el and alpha). 
+
+ -- Peter Michael Green   Wed, 07 Sep 2016 15:06:23 
+
+
 gazebo (7.3.0+dfsg-3) unstable; urgency=medium
 
   [ Jochen Sprickerhof ]
diff -Nru gazebo-7.3.0+dfsg/debian/control gazebo-7.3.0+dfsg/debian/control
--- gazebo-7.3.0+dfsg/debian/control2016-08-30 22:54:59.0 +
+++ gazebo-7.3.0+dfsg/debian/control2016-09-07 15:06:07.0 +
@@ -45,7 +45,7 @@
libbullet-dev,
libsimbody-dev,
libsimbody-dev (<< 4.0.0),
-   libkido-dev,
+   libkido-dev [amd64 arm64 i386 powerpc alpha],
libgdal-dev,
ruby-ronn,
libgtest-dev
@@ -138,7 +138,7 @@
  libignition-math2-dev,
  libbullet-dev,
  libsimbody-dev,
- libkido-dev,
+ libkido-dev [amd64 arm64 i386 powerpc alpha],
  libgazebo7 (= ${binary:Version}),
  gazebo7-common (= ${source:Version}),
  gazebo7-plugin-base (= ${binary:Version}),

Bug#836537: marked as done (snd: FTBFS: snd-main.c:2162:24: error: macro "g_abort" passed 1 arguments, but takes just 0)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 23:31:58 +
with message-id 
and subject line Bug#836537: fixed in snd 16.8-1
has caused the Debian Bug report #836537,
regarding snd: FTBFS: snd-main.c:2162:24: error: macro "g_abort" passed 1 
arguments, but takes just 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.)


-- 
836537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snd
Version: 16.7-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,

snd fails to build from source in unstable/amd64:

  [..]

  make: [makefile-clean] Error 1 (ignored)
  rmdir --ignore-fail-on-non-empty debian/stamp-autotools
  rmdir: failed to remove 'debian/stamp-autotools': No such file or directory
  /usr/share/cdbs/1/class/autotools.mk:58: recipe for target 'makefile-clean' 
failed
  make: [makefile-clean] Error 1 (ignored)
  set -e;
  if test -e debian/autoreconf.before; then \
dh_autoreconf_clean ; \
  fi
  dh_clean 
  rm -f debian/stamp-autotools-files
  rm -f debian/copyright_newhints
  rm -f debian/cdbs-install-list debian/cdbs-package-list 
debian/stamp-copyright-check
  rm -rf "debian/upstream-cruft"
  rm -f debian/stamp-upstream-cruft
  rm -f snd.nox.1 snd.gtk-jack.1 snd.gtk-pulse.1
   debian/rules build
  CDBS WARNING:  copyright-check disabled - licensecheck is missing.
  test -x debian/rules
  mkdir -p "build"
  CDBS WARNING:DEB_COPYRIGHT_CHECK_IGNORE_REGEX is deprecated since 0.4.133
  mkdir -p debian/stamp-makefile-build debian/stamp-makefile-install
  mkdir -p debian/stamp-autotools
  
  Scanning upstream source for new/changed copyright notices...
  
  set -e; LC_ALL=C.UTF-8 licensecheck --check '.*' --recursive --copyright 
--deb-fmt --ignore 
'^(pix/.*\.png|debian/(changelog|copyright(|_hints|_newhints)))' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
  /bin/sh: 1: licensecheck: not found
  0 combinations of copyright and licensing found.
  No new copyright notices found - assuming no news is good news...
  touch debian/stamp-copyright-check
  touch debian/stamp-upstream-cruft
  set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
/usr/share/misc/config.guess ./config.guess;
  set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
/usr/share/misc/config.sub ./config.sub;
  dh_autoreconf 
  touch debian/stamp-autotools-files
  chmod a+x 
/home/lamby/temp/cdt.20160903204930.AgBYCHkK99.db.snd/snd-16.7/./configure
  mkdir -p build/gtk-jack
  cd build/gtk-jack && CFLAGS="-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160903204930.AgBYCHkK99.db.snd/snd-16.7=.
 -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160903204930.AgBYCHkK99.db.snd/snd-16.7=.
 -fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -DREPRODUCIBLE_BUILD=1" 
LDFLAGS="-Wl,-z,relro" 
/home/lamby/temp/cdt.20160903204930.AgBYCHkK99.db.snd/snd-16.7/./configure 
--build=x86_64-linux-gnu --prefix=/usr --includedir="\${prefix}/include" 
--mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
--sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/snd" 
--disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules 
--with-ladspa --with-gmp --prefix=/usr --with-gtk --with-alsa --with-jack
  configure: WARNING: unrecognized options: --disable-maintainer-mode, 
--disable-dependency-tracking, --disable-silent-rules
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking for gcc... gcc
  checking whether the C compiler works... yes
  checking for C compiler default output file name... a.out
  checking for suffix of executables... 
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether we are using the GNU C compiler... yes
  checking whether gcc accepts -g... yes
  checking for gcc option to accept ISO C89... none needed
  checking for a BSD-compatible install... /usr/bin/install -c
  checking how to run the C preprocessor... gcc -E
  checking for grep that handles long lines and -e... /bin/grep
  checking for egrep... /bin/grep -E
  checking for ANSI C header files... yes
  checking for sys/types.h... yes
  checking for sys/stat.h... yes
  

Bug#837077: FTBFS, dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so needed by debian/budgie-core/usr/bin/budgie-wm

[Jeremy Bicha]

On Thu, Sep 8, 2016 at 6:51 PM, foss.freedom  wrote:
> Jeremy, upstream have worked double quick here and has proposed a patch.  I
> am going to do some testing tomorrow.  Assuming all goes well then I will
> push an update request.

That should be fine. I don't think Debian is in such a hurry to finish
the mutter transition that we can't wait a bit longer to keep
budgie-desktop in testing now that a fix has been identified.

Jeremy

Bug#837117: libscrypt0: Library does not appear to be working

[Allan Wind]

Package: libscrypt0
Version: 1-2.2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

The use case of the -dev library, as documented in the README.txt, is:

#include 
#include 
#include 

#define PASSWORD "test"

int main() {
char mcf[SCRYPT_MCF_LEN + 1];
libscrypt_hash(mcf, PASSWORD, SCRYPT_N, SCRYPT_r, SCRYPT_p);
assert(libscrypt_check(mcf, PASSWORD) > 0);
return 0;
}

You compile the program with:

gcc -lm -lscrypt scrypt-test.c -o scrypt-test

and it fails with:

allan@vent:~/src/yaxto$ ./scrypt-test 
scrypt-test: scrypt-test.c:10: main: Assertion `libscrypt_check(mcf, "test") > 
0' failed.
Aborted

I grabbed the current version from github 
(f2b792386b287cc471b1eb030e4ddcbc96be5ad5),
and it works as expected:

allan@vent:~/src/yaxto$ LD_LIBRARY_PATH=~/src/libscrypt ./scrypt-test 
allan@vent:~/src/yaxto$ 

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

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

Versions of packages libscrypt0 depends on:
ii  libc6  2.19-18+deb8u4

libscrypt0 recommends no packages.

libscrypt0 suggests no packages.

-- debconf-show failed

-- 
Allan Wind
Yaxto - Runs My Business

Bug#837077: FTBFS, dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so needed by debian/budgie-core/usr/bin/budgie-wm

[foss.freedom]

Jeremy, upstream have worked double quick here and has proposed a patch.  I
am going to do some testing tomorrow.  Assuming all goes well then I will
push an update request.

On 8 Sep 2016 23:18, "Jeremy Bicha"  wrote:

> On Thu, Sep 8, 2016 at 4:01 PM, foss.freedom 
> wrote:
> > In summary - budgie-desktop upstream do not test against GNOME unstable
> and
> > wait until things have been officially published.
>
> David, does that mean that you are ok with budgie-desktop being
> temporarily removed from Debian's testing repository? budgie-desktop
> can be added back when it does build again. The removal won't affect
> budgie-desktop's inclusion in Ubuntu 16.10.
>
> Thanks,
> Jeremy Bicha
>

Bug#837100: [PKG-Openstack-devel] Bug#837100: python-hacking dependency versions are pinned by upstream, package doesn't work with Debian ones

[Víctor Cuadrado Juan]

On Thu, 8 Sep 2016 23:35:27 +0200 Thomas Goirand  wrote:
> According to James Page, we should look into the Ubuntu package of
> hacking and get patches there to fix the issues.

Why specifically the Ubuntu package, and not the Debian one?

Cheers,


-- 
Víctor Cuadrado Juan   m...@viccuad.me

PGP key ID: 4096R: 0xA2591E231E251F36
Key fingerprint: E3C5 114C 0C5B 4C49 BA03  0991 A259 1E23 1E25 1F36
My signed E-Mails are trustworthy.



signature.asc
Description: OpenPGP digital signature

Bug#837109: marked as done (hypre: -dev package library dependency not binNMU safe)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 22:28:19 +
with message-id 
and subject line Bug#837109: fixed in hypre 2.8.0b-4
has caused the Debian Bug report #837109,
regarding hypre: -dev package library dependency not binNMU safe
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.)


-- 
837109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hypre
Version: 2.8.0b-3
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so
Control: block 836917 by -1
Control: affects -1 src:freefem++ src:petsc src:aster src:petsc4py src:slepc 
src:deal.ii src:getdp src:slepc4py src:dolfin

Dear Maintainer,

The upload of openmpi (2.0.1-3) has triggered an uncoordinated
transition (#836917). Unfortunately the version constraint on the
library package from the -dev package is not binNMU safe causing it not
to be installable when the package version contains a binNMU version
(+bN), this prevents the rebuilds of freefem++ & petsc:

 freefem++ build-depends on:
 - libhypre-dev:amd64
 libhypre-dev depends on missing:
 - libhypre-2.8.0b:amd64 (< 2.8.0b-3+1~)

 petsc build-depends on:
 - libhypre-dev:amd64 (>= 2.4.0)
 libhypre-dev depends on missing:
 - libhypre-2.8.0b:amd64 (< 2.8.0b-3+1~)

The attached patch turn the -dev package into an arch:any package with a
(= ${binary:Version) version requirement for the library package which
ensures that the same version of the -dev & library packages are
installed and which supports +bN binary versions for binNMUs.

Please apply the patch in the next revision of hypre to unblock the
rebuilds of freefem++, petsc, and their reverse dependencies for the
ongoing openmpi transition.

Kind Regards,

Bas
diff -Nru hypre-2.8.0b/debian/control hypre-2.8.0b/debian/control
--- hypre-2.8.0b/debian/control	2016-02-29 13:08:46.0 +0100
+++ hypre-2.8.0b/debian/control	2016-09-08 21:29:20.0 +0200
@@ -32,12 +32,11 @@
  This package contains the shared libraries.
 
 Package: libhypre-dev
-Architecture: all
+Architecture: any
 Section: libdevel
 Depends:
  libblas-dev | libblas.so,
- libhypre-2.8.0b (>= ${source:Version}),
- libhypre-2.8.0b (<< ${source:Version}+1~),
+ libhypre-2.8.0b (= ${binary:Version}),
  liblapack-dev | liblapack.so,
  libsuperlu-dev,
  mpi-default-dev,
--- End Message ---
--- Begin Message ---
Source: hypre
Source-Version: 2.8.0b-4

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated hypre package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Sep 2016 20:36:58 +
Source: hypre
Binary: libhypre-2.8.0b libhypre-dev
Architecture: source
Version: 2.8.0b-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mattia Rizzolo 
Description:
 libhypre-2.8.0b - High Performance Matrix Preconditioners - Shared Library
 libhypre-dev - High Performance Matrix Preconditioners - Development Files
Closes: 837109
Changes:
 hypre (2.8.0b-4) unstable; urgency=medium
 .
   * Team upload.
   * Apply patch from Bas Couwenberg  to turn libhypre-dev
 into an arch:any package, to be able to specify a stricter version
 restriction against libhypre-2.8.0b.  Closes: #837109
   * Bump Standards-Version to 3.9.8, no changes needed.
Checksums-Sha1:
 ebc6be923091835fa2d5546f54d8f352365d9544 2123 hypre_2.8.0b-4.dsc
 3f10981164f05f1b1f86abf074e923104b9567b4 10456 hypre_2.8.0b-4.debian.tar.xz
Checksums-Sha256:
 8fe3eff5e9e9541fd29bed9141ebeab4f30663355e819b38d5275b86d05f6653 2123 
hypre_2.8.0b-4.dsc
 2826737ff2baf92e70e862043b02b067ca3dbd11dc02599589613d9415dd7582 10456 
hypre_2.8.0b-4.debian.tar.xz
Files:
 61f1120d8b0bc18a889e53ed52af3893 2123 math extra hypre_2.8.0b-4.dsc
 6bfb7a3471cb32b510b2f2bf09ce809e 10456 math extra 

Bug#837084: marked as done (font-manager: fails to install: font-manager.postinst: glib-compile-schemas: not found)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 22:21:44 +
with message-id 
and subject line Bug#837084: fixed in font-manager 0.7.2+0git410aa802-3
has caused the Debian Bug report #837084,
regarding font-manager: fails to install: font-manager.postinst: 
glib-compile-schemas: 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.)


-- 
837084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: font-manager
Version: 0.7.2+0git410aa802-2
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 font-manager.
  (Reading database ... 
(Reading database ... 14582 files and directories currently installed.)
  Preparing to unpack .../font-manager_0.7.2+0git410aa802-2_amd64.deb ...
  Unpacking font-manager (0.7.2+0git410aa802-2) ...
  Processing triggers for libglib2.0-0:amd64 (2.49.6-1) ...
  Processing triggers for libc-bin (2.24-2) ...
  Setting up font-manager (0.7.2+0git410aa802-2) ...
  /var/lib/dpkg/info/font-manager.postinst: 23: 
/var/lib/dpkg/info/font-manager.postinst: glib-compile-schemas: not found
  dpkg: error processing package font-manager (--configure):
   subprocess installed post-installation script returned error exit status 127
  Processing triggers for libc-bin (2.24-2) ...
  Errors were encountered while processing:
   font-manager


cheers,

Andreas


font-manager_0.7.2+0git410aa802-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: font-manager
Source-Version: 0.7.2+0git410aa802-3

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

Debian distribution maintenance software
pp.
Alessio Treglia  (supplier of updated font-manager package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Sep 2016 21:39:43 +0100
Source: font-manager
Binary: font-manager
Architecture: source amd64
Version: 0.7.2+0git410aa802-3
Distribution: unstable
Urgency: medium
Maintainer: Alessio Treglia 
Changed-By: Alessio Treglia 
Description:
 font-manager - font management application for the GNOME desktop
Closes: 837084
Changes:
 font-manager (0.7.2+0git410aa802-3) unstable; urgency=medium
 .
   * Get rid of manually created post{inst,rm} (Closes: #837084)
Checksums-Sha1:
 30d204cf1d7e76d6f42d8892b065b7df5bc3de51 2334 
font-manager_0.7.2+0git410aa802-3.dsc
 e1fb3fc9fd95e8543773a5cbc6f285a444e6b3b6 3704 
font-manager_0.7.2+0git410aa802-3.debian.tar.xz
 ae222c5494ae50b010844ccd8455343c70097b6b 1506856 
font-manager-dbgsym_0.7.2+0git410aa802-3_amd64.deb
 404050b58a798e3e049edf552ca9097258fb23e1 284972 
font-manager_0.7.2+0git410aa802-3_amd64.deb
Checksums-Sha256:
 997345664dcd998f271a63577d4684cfff59976135b44d2932bc04cb80bf59ef 2334 
font-manager_0.7.2+0git410aa802-3.dsc
 d842b57271b8c0b247c77cb36bf2502691ec863ca551f50c6f13714c8523bc42 3704 
font-manager_0.7.2+0git410aa802-3.debian.tar.xz
 2a12e69bd98b97eac99b9e2c392f6b802676061d5b6f8338043539c8ddc055e8 1506856 
font-manager-dbgsym_0.7.2+0git410aa802-3_amd64.deb
 cd4393d7cdebc104ec563787d7ea0d8db66914cf4170718b0add90386e784d21 284972 
font-manager_0.7.2+0git410aa802-3_amd64.deb
Files:
 90b952c5bb41ac6bab65622d077428a0 2334 graphics optional 
font-manager_0.7.2+0git410aa802-3.dsc
 cf21a89711f25e2916aaf17b99155be6 3704 graphics optional 
font-manager_0.7.2+0git410aa802-3.debian.tar.xz
 a088415a8048202d6b6f8b911ea636fd 1506856 debug extra 
font-manager-dbgsym_0.7.2+0git410aa802-3_amd64.deb
 3e10641b1938d8205b7a353dbb5ab8b1 284972 graphics optional 
font-manager_0.7.2+0git410aa802-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJX0dBlAAoJEOikiuUxHXZaJZYP/icv/d2HYzhJVWXaOHkhM184

Bug#837077: FTBFS, dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so needed by debian/budgie-core/usr/bin/budgie-wm

[Jeremy Bicha]

On Thu, Sep 8, 2016 at 4:01 PM, foss.freedom  wrote:
> In summary - budgie-desktop upstream do not test against GNOME unstable and
> wait until things have been officially published.

David, does that mean that you are ok with budgie-desktop being
temporarily removed from Debian's testing repository? budgie-desktop
can be added back when it does build again. The removal won't affect
budgie-desktop's inclusion in Ubuntu 16.10.

Thanks,
Jeremy Bicha

Processed: severity of 837067 is important

[Debian Bug Tracking System]

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

> severity 837067 important
Bug #837067 [src:libsecret] libsecret: FTBFS - /collection/delete-sync failure
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 710696 is important

[Debian Bug Tracking System]

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

> severity 710696 important
Bug #710696 [src:libsoup2.4] libsoup2.4 FTBFS too much often (failing tests)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#837100: [PKG-Openstack-devel] Bug#837100: python-hacking dependency versions are pinned by upstream, package doesn't work with Debian ones

[Thomas Goirand]

On 09/08/2016 09:57 PM, Ondrej Novy wrote:
> Sry, ignore my last email, I'm idiot :)
> 
> -- 
> Best regards
>  Ondřej Nový

Ondřej,

According to James Page, we should look into the Ubuntu package of
hacking and get patches there to fix the issues.

You're not an idiot btw... :P

Cheers,

Thomas Goirand (zigo)

Processed: tagging 837084

[Debian Bug Tracking System]

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

> tags 837084 + pending
Bug #837084 [font-manager] font-manager: fails to install: 
font-manager.postinst: glib-compile-schemas: not found
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#835209: missing decoder: text/html error on playing ogg or mp3 files

[Debian Bug Tracking System]

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

> block 834439 by 835209
Bug #834439 [clementine] clementine: depend on gstreamer1.0-plugins-bad
834439 was not blocked by any bugs.
834439 was not blocking any bugs.
Added blocking bug(s) of 834439: 835209
> thanks
Stopping processing here.

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

Bug#837110: linux: armhf: nic-modules: FTBFS: dwmac-socfpga module renamed to dwmac-altr-socfpga

[Vagrant Cascadian]

Package: linux
Version: 4.8~rc5-1~exp1
Severity: grave
Tags: patch
Justification: renders package unusable

It appears the dwmac-socfpga module was renamed to dwmac-altr-socfpga
in 4.8.x, in commit:

  commit fb3bbdb859891e6bc27fd1afb3a07319f82c2ee4
  Author: Tien Hock Loh 
  Date:   Thu Jul 7 20:23:30 2016 -0700

net: ethernet: Add TSE PCS support to dwmac-socfpga


I haven't tested if there are other module renames that would also
lead to a FTBFS.


diff --git a/debian/installer/armhf/modules/armhf-armmp/nic-modules 
b/debian/installer/armhf/modules/armhf-armmp/nic-modules
index e3d0df7..75a4eb9 100644
--- a/debian/installer/armhf/modules/armhf-armmp/nic-modules
+++ b/debian/installer/armhf/modules/armhf-armmp/nic-modules
@@ -5,7 +5,7 @@ smsc911x
 stmmac
 stmmac-platform
 dwmac-generic
-dwmac-socfpga
+dwmac-altr-socfpga
 dwmac-sunxi
 sun4i-emac
 xgmac


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#808312: Fix overwrite chemps2.1.gz

[Sebastian Wouters]

Hi Andreas,

The bug is hopefully fixed with
https://anonscm.debian.org/cgit/debichem/packages/chemps2.git/commit/?id=c787f951661b39221db198de19577b88ac1629e1

I'll ask Graham or Michael to upload.

Best wishes,
Sebastian

Processed: hypre: -dev package library dependency not binNMU safe

[Debian Bug Tracking System]

Processing control commands:

> block 836917 by -1
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 831164 811651 837030 812036 830440 837061 835680 837059 
837062 811907 837055 837058 825934 837012 817690
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 837109
> affects -1 src:freefem++ src:petsc src:aster src:petsc4py src:slepc 
> src:deal.ii src:getdp src:slepc4py src:dolfin
Bug #837109 [src:hypre] hypre: -dev package library dependency not binNMU safe
Added indication that 837109 affects src:freefem++, src:petsc, src:aster, 
src:petsc4py, src:slepc, src:deal.ii, src:getdp, src:slepc4py, and src:dolfin

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

Bug#837109: hypre: -dev package library dependency not binNMU safe

[Bas Couwenberg]

Source: hypre
Version: 2.8.0b-3
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so
Control: block 836917 by -1
Control: affects -1 src:freefem++ src:petsc src:aster src:petsc4py src:slepc 
src:deal.ii src:getdp src:slepc4py src:dolfin

Dear Maintainer,

The upload of openmpi (2.0.1-3) has triggered an uncoordinated
transition (#836917). Unfortunately the version constraint on the
library package from the -dev package is not binNMU safe causing it not
to be installable when the package version contains a binNMU version
(+bN), this prevents the rebuilds of freefem++ & petsc:

 freefem++ build-depends on:
 - libhypre-dev:amd64
 libhypre-dev depends on missing:
 - libhypre-2.8.0b:amd64 (< 2.8.0b-3+1~)

 petsc build-depends on:
 - libhypre-dev:amd64 (>= 2.4.0)
 libhypre-dev depends on missing:
 - libhypre-2.8.0b:amd64 (< 2.8.0b-3+1~)

The attached patch turn the -dev package into an arch:any package with a
(= ${binary:Version) version requirement for the library package which
ensures that the same version of the -dev & library packages are
installed and which supports +bN binary versions for binNMUs.

Please apply the patch in the next revision of hypre to unblock the
rebuilds of freefem++, petsc, and their reverse dependencies for the
ongoing openmpi transition.

Kind Regards,

Bas
diff -Nru hypre-2.8.0b/debian/control hypre-2.8.0b/debian/control
--- hypre-2.8.0b/debian/control	2016-02-29 13:08:46.0 +0100
+++ hypre-2.8.0b/debian/control	2016-09-08 21:29:20.0 +0200
@@ -32,12 +32,11 @@
  This package contains the shared libraries.
 
 Package: libhypre-dev
-Architecture: all
+Architecture: any
 Section: libdevel
 Depends:
  libblas-dev | libblas.so,
- libhypre-2.8.0b (>= ${source:Version}),
- libhypre-2.8.0b (<< ${source:Version}+1~),
+ libhypre-2.8.0b (= ${binary:Version}),
  liblapack-dev | liblapack.so,
  libsuperlu-dev,
  mpi-default-dev,

Bug#837077: FTBFS, dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so needed by debian/budgie-core/usr/bin/budgie-wm

[foss.freedom]

Michael - have raised this issue upstream


 - https://github.com/solus-project/budgie-desktop/issues/564

In summary - budgie-desktop upstream do not test against GNOME unstable and
wait until things have been officially published.

On 8 September 2016 at 15:15, Michael Biebl  wrote:

> Source: budgie-desktop
> Version: 10.2.6-1
> Severity: serious
>
> Hi,
>
> after the recent upgrade of mutter to 3.21.x, budgie-desktop fails to
> build from source:
>
> dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so
> needed by debian/budgie-core/usr/bin/budgie-wm (ELF format:
> 'elf64-x86-64'; RPATH: '')
> dpkg-shlibdeps: warning: couldn't find library libmutter-cogl.so needed by
> debian/budgie-core/usr/bin/budgie-wm (ELF format: 'elf64-x86-64'; RPATH:
> '')
>
> The complete build log is available at
> https://buildd.debian.org/status/package.php?p=budgie-desktop
>
>
> Regards,
> Michael
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200,
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>

Bug#834830: marked as done (open-iscsi-udeb: initramfs is not regenerated at end of installation, leaving GenerateName= in initiatorname.iscsi)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 19:47:42 +
with message-id 
and subject line Bug#834830: fixed in open-iscsi 2.0.873+git0.3b4b4500-8+deb8u2
has caused the Debian Bug report #834830,
regarding open-iscsi-udeb: initramfs is not regenerated at end of installation, 
leaving GenerateName= in initiatorname.iscsi
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.)


-- 
834830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-iscsi-udeb
Version: 2.0.873+git0.3b4b4500-8
Severity: serious
Justification: installs with iSCSI rootfs unbootable by default
Tags: confirmed jessie

This was reported on debian-user, and I've been able to reproduce
that in a local test environment in a VM.

https://lists.debian.org/debian-user/2016/08/msg00689.html

In a default install, the initramfs contains an initiatorname.iscsi
with the contents GenerateName=yes, instead of an actually generated
name.

This is due to the fact that the d-i variant of initiatorname.iscsi
(that does contain a valid name) is only copied to the system at the
very end, and the initramfs is not regenerated.

This does not affect Stretch/sid, as we generate an initiator name
in postinst now.

Regards,
Christian
--- End Message ---
--- Begin Message ---
Source: open-iscsi
Source-Version: 2.0.873+git0.3b4b4500-8+deb8u2

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

Debian distribution maintenance software
pp.
Christian Seiler  (supplier of updated open-iscsi 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, 20 Aug 2016 11:14:44 +0200
Source: open-iscsi
Binary: open-iscsi open-iscsi-udeb
Architecture: source amd64
Version: 2.0.873+git0.3b4b4500-8+deb8u2
Distribution: jessie
Urgency: medium
Maintainer: Debian iSCSI Maintainers 

Changed-By: Christian Seiler 
Description:
 open-iscsi - High performance, transport independent iSCSI implementation
 open-iscsi-udeb - Configure iSCSI (udeb)
Closes: 833917 834830
Changes:
 open-iscsi (2.0.873+git0.3b4b4500-8+deb8u2) jessie; urgency=medium
 .
   * [6d8d26d] init script: wait a bit after iSCSI devices have appeared.
 This works around a race condition in which dependent devices can
 appear only after the initial udev settle has returned.
 (Closes: #833917)
   * [8a8a870] open-iscsi-udeb: update initramfs after copying
 configuration to target system. (Closes: #834830)
Checksums-Sha1:
 8e9e9bbe0878e99458045760f864aa20b5e959ed 2367 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2.dsc
 74d311270d9cc305cb0e9602b882726ef95b0708 17220 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2.debian.tar.xz
 c7650ff3acd723a3383d552a67db85700d4f852a 295986 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2_amd64.deb
 12c791563e3e04bf0331a18c76eee961e8b468b7 255092 
open-iscsi-udeb_2.0.873+git0.3b4b4500-8+deb8u2_amd64.udeb
Checksums-Sha256:
 d98716f2f2206651498e7cd4268e3e248fb244ac7dc5e7d0cbd0703416e9f07b 2367 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2.dsc
 21a469e437534210bfcf4f7106984553632d1ee640afd339eb69996ca24da0f0 17220 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2.debian.tar.xz
 df315c8cbe14d62da704eb44b01bde9d2eb285907ff5ddb2dac17f4e46fb7f42 295986 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2_amd64.deb
 e9f12b25ac3187d601297050bda163d4f24b58ad76efef9d2b7c4b0c19a816b8 255092 
open-iscsi-udeb_2.0.873+git0.3b4b4500-8+deb8u2_amd64.udeb
Files:
 e62cd003cb6ff624fcc1de4a6f5c45bc 2367 net optional 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2.dsc
 57e872381c0b6c1ea155195b4b7ca8f1 17220 net optional 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2.debian.tar.xz
 63643774beb0ad624cec981808109acd 295986 net optional 
open-iscsi_2.0.873+git0.3b4b4500-8+deb8u2_amd64.deb
 082c7258d919dbc7b2b3d02ab9746431 255092 debian-installer optional 
open-iscsi-udeb_2.0.873+git0.3b4b4500-8+deb8u2_amd64.udeb

-BEGIN PGP SIGNATURE-

Bug#836714: marked as done (charybdis: CVE-2016-7143: certificate fingerprint spoofing through crafted SASL messages)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 19:47:08 +
with message-id 
and subject line Bug#836714: fixed in charybdis 3.4.2-5+deb8u2
has caused the Debian Bug report #836714,
regarding charybdis: CVE-2016-7143: certificate fingerprint spoofing through 
crafted SASL messages
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.)


-- 
836714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: inspircd
Version: 2.0.5-1+deb7u2
Severity: critical
Tags: security

inspircd published 2.0.23 that fixes an issue with SASL
authentication. The details are here:

http://www.inspircd.org/2016/09/03/v2023-released.html

All versions are affected.

Upstream hasn't requested a CVE yet. I will contact oss-security to
make sure that happens.

It seems to also affect Charybdis, which fixed the issue in the
upcoming 3.5.3 release:

https://github.com/charybdis-ircd/charybdis/commit/818a3fda944b26d4814132cee14cfda4ea4aa824

I will take care of the 3.5.3 upload or backporting those patches to
3.5.2 and 3.4 (if relevant) as soon as I can.

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

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: charybdis
Source-Version: 3.4.2-5+deb8u2

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated charybdis 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, 05 Sep 2016 19:41:12 -0400
Source: charybdis
Binary: charybdis charybdis-dbg
Architecture: source amd64
Version: 3.4.2-5+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 charybdis  - fast, scalable irc server
 charybdis-dbg - fast, scalable irc server
Closes: 836714
Changes:
 charybdis (3.4.2-5+deb8u2) jessie-security; urgency=high
 .
   * add fix for CVE-2016-7143, backported from upstream (Closes: #836714)
Checksums-Sha1:
 e91fc06bda53191cb81048d6d90fa9e6734bfb34 2087 charybdis_3.4.2-5+deb8u2.dsc
 bb7a87f876a1c9870acf4a9676ad37e2b0c6ce6d 1941172 charybdis_3.4.2.orig.tar.gz
 c0e65d5f43b3674cd6dde3efafc4874c6904614a 23356 
charybdis_3.4.2-5+deb8u2.debian.tar.xz
 ce724f2d9bd08a81275f1f85eb51fc46d5488540 578934 
charybdis_3.4.2-5+deb8u2_amd64.deb
 836f11801908ad411849778566cdbded56776dda 1518646 
charybdis-dbg_3.4.2-5+deb8u2_amd64.deb
Checksums-Sha256:
 d2fe499fea40c1ce8e3ef9e38bf69a66c33a47697ccda761867034f211dc0965 2087 
charybdis_3.4.2-5+deb8u2.dsc
 cbc20aca5022758b9039a34237a1d7a0f99b48ec5c3ef8e7a04d49f3bc264789 1941172 
charybdis_3.4.2.orig.tar.gz
 93c57b942db77a4612eaef1e3d826918228ae39ecaed8856f36d13a975d248f1 23356 
charybdis_3.4.2-5+deb8u2.debian.tar.xz
 c768e732621584ceca861de49470286299f83a039f3b5d80704d2e937c91a9e6 578934 
charybdis_3.4.2-5+deb8u2_amd64.deb
 9d10a0718ab0ca3e446a8d572a37877e94e7575a801b3f9f7151c64839b0bf24 1518646 
charybdis-dbg_3.4.2-5+deb8u2_amd64.deb
Files:
 7f9e129da6b6ee06858af78741847c29 2087 net optional charybdis_3.4.2-5+deb8u2.dsc
 6fd12f8c9ac99b8f6215488a47b37319 1941172 net optional 
charybdis_3.4.2.orig.tar.gz
 f16074c8dc6e7814e34ab5f93cee39d9 23356 net optional 
charybdis_3.4.2-5+deb8u2.debian.tar.xz
 7c90d2d9751885e982c6821297bd996d 578934 net optional 
charybdis_3.4.2-5+deb8u2_amd64.deb
 2c6df8c459ef467ed5e4e4d8e95459eb 1518646 debug extra 
charybdis-dbg_3.4.2-5+deb8u2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXzsiaAAoJEHkhUlJ7dZIerngQALASA6H9/WGlgyJyymNg6G2V
Cle/AyPx7D9ng8FQE51my293fDyOYLgraSYqZQj7CNimUAcT3pRj4+oHRxr4+yYH

Bug#828120: marked as done (view3dscene: FTBFS: convert: Non-conforming drawing primitive definition (push))

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 19:34:41 +
with message-id 
and subject line Bug#828120: fixed in view3dscene 3.15.0-6
has caused the Debian Bug report #828120,
regarding view3dscene: FTBFS: convert: Non-conforming drawing primitive 
definition (push)
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.)


-- 
828120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: view3dscene
Version: 3.15.0-5
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,

view3dscene fails to build from source in unstable/amd64:

  [..]

  tovrmlx3d: VRML/X3D warning: External prototype "SuperShape" cannot be 
loaded, so cannot instantiate nodes using it
  tovrmlx3d: VRML/X3D warning: Node "SuperShape" is not allowed in the field 
"geometry" of the node "Shape"
  tovrmlx3d: VRML/X3D warning: Cannot load external prototype from URL 
"file:///home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/white_dune-0.29beta871/logo/SuperShapePROTO.wrl":
 Unable to open file 
"/home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/white_dune-0.29beta871/logo/SuperShapePROTO.wrl"
  tovrmlx3d: VRML/X3D warning: Cannot load external prototype from URL 
"http://129.69.35.12/dune/docs/scriptedNodes/SuperShapePROTO.wrl": Downloading 
from "http" is not enabled
  tovrmlx3d: VRML/X3D warning: Cannot load external prototype from URL 
"file:///home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/white_dune-0.29beta871/logo/SuperExtrusionPROTO.wrl":
 Unable to open file 
"/home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/white_dune-0.29beta871/logo/SuperExtrusionPROTO.wrl"
  tovrmlx3d: VRML/X3D warning: Cannot load external prototype from URL 
"http://129.69.35.12/dune/docs/scriptedNodes/SuperExtrusionPROTO.wrl": 
Downloading from "http" is not enabled
  tovrmlx3d: VRML/X3D warning: Cannot load external prototype from URL 
"file:///home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/docs/typical_vrml_examples/LdrawDatExportPROTO.wrl":
 Unable to open file 
"/home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/docs/typical_vrml_examples/LdrawDatExportPROTO.wrl"
  tovrmlx3d: VRML/X3D warning: External prototype "SuperShape" cannot be 
loaded, so cannot instantiate nodes using it
  tovrmlx3d: VRML/X3D warning: Node "SuperShape" is not allowed in the field 
"geometry" of the node "Shape"
  tovrmlx3d: VRML/X3D warning: External prototype "SuperExtrusion" cannot be 
loaded, so cannot instantiate nodes using it
  tovrmlx3d: VRML/X3D warning: Node "SuperExtrusion" is not allowed in the 
field "geometry" of the node "Shape"
  tovrmlx3d: VRML/X3D warning: External prototype "SuperShape" cannot be 
loaded, so cannot instantiate nodes using it
  tovrmlx3d: VRML/X3D warning: Node "SuperShape" is not allowed in the field 
"geometry" of the node "Shape"
  tovrmlx3d: VRML/X3D warning: External prototype "SuperShape" cannot be 
loaded, so cannot instantiate nodes using it
  tovrmlx3d: VRML/X3D warning: Node "SuperShape" is not allowed in the field 
"geometry" of the node "Shape"
  tovrmlx3d: VRML/X3D warning: Cannot load external prototype from URL 
"file:///home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/white_dune-0.29beta871/logo/SuperShapePROTO.wrl":
 Unable to open file 
"/home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/white_dune-0.29beta871/logo/SuperShapePROTO.wrl"
  tovrmlx3d: VRML/X3D warning: Cannot load external prototype from URL 
"http://129.69.35.12/dune/docs/scriptedNodes/SuperShapePROTO.wrl": Downloading 
from "http" is not enabled
  tovrmlx3d: VRML/X3D warning: Cannot load external prototype from URL 
"file:///home/lamby/temp/cdt.20160625083313.Fnu3foubd1.view3dscene/view3dscene-3.15.0/debian/tmp/whitedune/whitedune-docs/white_dune-0.29beta871/logo/SuperExtrusionPROTO.wrl":
 Unable to open file 

Processed: your mail

[Debian Bug Tracking System]

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

> tags 835489 + pending
Bug #835489 [pyqso] Fails to start
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#837100: python-hacking dependency versions are pinned by upstream, package doesn't work with Debian ones

[Víctor Cuadrado Juan]

Package: python-hacking
Version: 0.10.2-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Upstream for python-hacking hardpins the dependecies: [1]
> Hacking pins its dependencies, as a new release of some dependency
> can break hacking based gating jobs. This is because new versions of
> dependencies can introduce new rules, or make existing rules stricter.

Currently we have python-hacking 0.10.2, which depends on: [2]
pbr (>=0.11,<2.0)
pep8 (==1.5.7)
pyflakes (==0.8.1)
flake8 (==2.2.4)
mccabe (==0.2.1)
six (>=1.7.0)

Even the newly released upstream version, 0.11.0, depends on: [3]
flake8 (>=2.5.4,<2.6.0)
mccabe (==0.2.1)
pbr (>=1.6)
pep8 (==1.5.7)
pyflakes (==0.8.1)
six (>=1.9.0)

Neither can be satisfaced on Testing nor Unstable (eg: we have
flake8 3.0.4 already), and this renders the package unusable. See
for example the following traceback from flake8:

Traceback (most recent call last):
  File "/usr/bin/flake8", line 9, in 
load_entry_point('flake8==3.0.4', 'console_scripts', 'flake8')()
  File "/usr/lib/python3/dist-packages/flake8/main/cli.py", line 16, in
main
app.run(argv)
  File "/usr/lib/python3/dist-packages/flake8/main/application.py", line
316, in run
self._run(argv)
  File "/usr/lib/python3/dist-packages/flake8/main/application.py", line
300, in _run
self.run_checks()
  File "/usr/lib/python3/dist-packages/flake8/main/application.py", line
238, in run_checks
self.file_checker_manager.run()
  File "/usr/lib/python3/dist-packages/flake8/checker.py", line 343, in run
self.run_serial()
  File "/usr/lib/python3/dist-packages/flake8/checker.py", line 327, in
run_serial
checker.run_checks(self.results_queue, self.statistics_queue)
  File "/usr/lib/python3/dist-packages/flake8/checker.py", line 568, in
run_checks
self.process_tokens()
  File "/usr/lib/python3/dist-packages/flake8/checker.py", line 552, in
process_tokens
self.handle_newline(token_type)
  File "/usr/lib/python3/dist-packages/flake8/checker.py", line 595, in
handle_newline
self.run_logical_checks()
  File "/usr/lib/python3/dist-packages/flake8/checker.py", line 503, in
run_logical_checks
results = self.run_check(plugin, logical_line=logical_line) or ()
  File "/usr/lib/python3/dist-packages/flake8/checker.py", line 455, in
run_check
exception=ae,
flake8.exceptions.PluginRequestedUnknownParameters: "hacking.core"
requested unknown parameters causing 'FileProcessor' object has no attribute
'physical_line'

We either need to fix this, or remove the package.

Cheers,


[1]: https://github.com/openstack-dev/hacking
[2]: https://pypi.python.org/pypi/hacking/0.10.2
[3]: https://pypi.python.org/pypi/hacking/0.11.0



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

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

Versions of packages python-hacking depends on:
ii  pep8   1.7.0-4
ii  pyflakes   1.2.3-1
ii  python-flake8  3.0.4+dfsg1-1
ii  python-mccabe  0.5.2-2
ii  python-pbr 1.8.0-4.1
ii  python-six 1.10.0-3
pn  python:any 

python-hacking recommends no packages.

python-hacking suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJX0bg9AAoJECI/Fcparw549x8IAMJXAs8GzVspdkN15JiyD8sz
F9Mhhwy6YTyaOwqDcxLxEoocAudhBFQ5YT8qpyz6itqFp5zU0Z+8FnCzZggTkat5
irXdNz7LRMtDzJW0Yx6uGS338/hE2eRLxKyHWvLMlPhwC2SHwuMqagk5GWFZYHz8
iBp7rbSsW65wz5rMYURLyBKc6P6TCxfCK/0Uq3FMPCsPgGy7t8XYXshBco3b+okM
PcPRIDJ92+TJI9OBmwqdVKGUTR2N8vSZT4luxJHsc1U+frzVGElACw75MGbDNbsh
MiNHldGsGi15SkviKbkvzt7gM/cSpzfnvmATj3CvNksXImyMdhENWxOiSNTPErI=
=JGym
-END PGP SIGNATURE-

Bug#833501: found in 53.0.2785.92-2

[Jan Gerber]

On Tue, 6 Sep 2016 17:38:18 -0400 Gedalya  wrote:
> now that we're back with gcc 6, same crashes occur with facebook, google maps 
> and other sites.
> 
> This got it working for me
> 
> --- rules.orig2016-09-06 15:44:51.692191414 -0400
> +++ rules2016-09-06 15:47:29.097229998 -0400
> @@ -16,6 +16,10 @@
>  export CFLAGS+=-fuse-ld=gold
>  export CXXFLAGS+=-fuse-ld=gold
>  
> +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68853
> +export CFLAGS+=-fno-delete-null-pointer-checks
> +export CXXFLAGS+=-fno-delete-null-pointer-checks
> +
>  # treat all warnings as errors
>  defines=werror=

can confirm that recompiling chromium with that patch fixes the issue for me.
without it, chromium crashes all the time.

Processed: affects 837062

[Debian Bug Tracking System]

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

> affects 837062 src:aster src:cp2k src:elpa src:espresso src:freefem++ 
> src:mumps src:nwchem src:petsc
Bug #837062 [src:scalapack] scalapack: FTBFS due to test failures
Added indication that 837062 affects src:aster, src:cp2k, src:elpa, 
src:espresso, src:freefem++, src:mumps, src:nwchem, and src:petsc
> thanks
Stopping processing here.

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

Processed: affects 830440

[Debian Bug Tracking System]

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

> affects 830440 src:adios src:paraview
Bug #830440 [src:mpi4py] mpi4py: FTBFS: ld: cannot find -llmpe
Added indication that 830440 affects src:adios and src:paraview
> thanks
Stopping processing here.

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

Processed: affects 830440

[Debian Bug Tracking System]

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

> affects 830440 src:vtk6
Bug #830440 [src:mpi4py] mpi4py: FTBFS: ld: cannot find -llmpe
Added indication that 830440 affects src:vtk6
> thanks
Stopping processing here.

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

Processed: block 836917 with 830440

[Debian Bug Tracking System]

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

> block 836917 with 830440
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 837061 837012 811651 837055 837062 825934 831164 812036 
817690 811907 837058 835680 837059 837030
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 830440
> thanks
Stopping processing here.

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

Bug#837091: firefox-esr: EME DRM extention present and enabled

[Tjeerd Pinkert]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: firefox-esr
Version: 45.3.0esr-1~deb8u1
Severity: serious
Tags: security upstream
Justification: Policy 2.2.1 must comply with the DFSG

Dear Maintainer,

after reading up a bit (late(ly)) on the W3C EME proposed standard for
embedding of DRM managed content in web pages, I decided to have a
look if it is present in the firefox browser. about:config shows the
following:

media.eme.apiVisible;true
media.eme.enabled;true

I think the presence of code that requires closed source components to
function, might violate the DFSG for the main section? On the other
hand, no package relation is available in the non-free section as far
as I see that is actively depended on. If a decision has been taken on
this already, then please close.

I have not found this in the system for the firefox-esr package, I did
find bug 748342 (iceweasel), and the upstream bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1011459
and a discussion at:
http://forums.debian.net/viewtopic.php?f=20=114687

First of all I disabled the function by setting the above values to:
false.

It would be better to have support for EME removed altogether to be free
of any possible legal issues arising from DRM enabled software.

Yours,


Tjeerd Pinkert


P.S. yes I know, having flash installed as a plugin is as bad as
having EME enabled... Trying to block as much as possible though...


- -- Package-specific info:

- -- Extensions information
Name: Adblock Plus
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{d1
0d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Package: xul-ext-adblock-plus
Status: enabled

Name: Cookie Monster
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{45
d8ff86-d909-11db-9705-005056c8}
Package: xul-ext-cookie-monster
Status: enabled

Name: Default theme
Location:
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198
ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: DOM Inspector
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ins
pec...@mozilla.org
Package: xul-ext-dom-inspector
Status: enabled

Name: Element Hiding Helper for Adblock Plus
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ele
mhidehel...@adblockplus.org
Package: xul-ext-adblock-plus-element-hiding-helper
Status: enabled

Name: English (GB) Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack-en-GB@firefox-esr.mozil
la.org.xpi
Package: firefox-esr-l10n-en-gb
Status: enabled

Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: Flashblock
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{3d
7eb24f-2740-49df-8937-200b1cc08f8a}
Package: xul-ext-flashblock
Status: enabled

Name: FlashGot
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{19
503e42-ca3c-4c27-b1e2-9cdb2170ee34}
Package: xul-ext-flashgot
Status: enabled

Name: Lightbeam
Location: ${PROFILE_EXTENSIONS}/jid1-f9uj2thwoam...@jetpack.xpi
Status: enabled

Name: Nederlands (NL) Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack-nl@firefox-esr.mozilla.
org.xpi
Package: firefox-esr-l10n-nl
Status: enabled

Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.x
pi
Status: enabled

- -- Plugins information
Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: disabled

Name: iTunes Application Detector
Location: /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
Package: rhythmbox-plugins
Status: disabled

Name: Shockwave Flash (11.2.202.632)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled


- -- Addons package information
ii  firefox-esr45.3.0esr-1~ amd64Mozilla Firefox web
browser - Ext
ii  firefox-esr-l1 45.3.0esr-1~ all  English (United Kingdom)
language
ii  firefox-esr-l1 45.3.0esr-1~ all  Dutch language package
for Firefo
ii  gnome-shell3.14.4-1~deb amd64graphical shell for the
GNOME des
ii  rhythmbox-plug 3.1-1amd64plugins for rhythmbox
music playe
ii  xul-ext-adbloc 2.6.6+dfsg-1 all  advertisement blocking
extension
ii  xul-ext-adbloc 1.3-1all  companion for Adblock
Plus to cre
ii  xul-ext-cookie 1.2.0-1  all  manage cookies in a
whitelist-bas
ii  xul-ext-dom-in 1:2.0.14-1   all  tool for inspecting the
DOM of we
ii  xul-ext-flashb 1.5.18-1 all  Mozilla extension to
block Adobe
ii  xul-ext-flashg 1.5.6.7+dfsg all  Extension to handle
downloads wit

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: 

Bug#836706: closing 836706

[Salvatore Bonaccorso]

close 836706 2.0.17-1+deb8u2
thanks

Processed: closing 836706

[Debian Bug Tracking System]

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

> close 836706 2.0.17-1+deb8u2
Bug #836706 [src:inspircd] inspircd: CVE-2016-7142: certificate fingerprint 
spoofing through crafted SASL messages
The source 'inspircd' and version '2.0.17-1+deb8u2' do not appear to match any 
binary packages
Marked as fixed in versions inspircd/2.0.17-1+deb8u2.
Bug #836706 [src:inspircd] inspircd: CVE-2016-7142: certificate fingerprint 
spoofing through crafted SASL messages
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: [bts-link] source package unknown-horizons

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package unknown-horizons
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #797998 (http://bugs.debian.org/797998)
> # Bug title: unknown-horizons: Crash shortly after start of single player game
> #  * https://github.com/unknown-horizons/unknown-horizons/issues/2295
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 797998 + fixed-upstream
Bug #797998 [unknown-horizons] unknown-horizons: Crash shortly after start of 
single player game
Added tag(s) fixed-upstream.
> usertags 797998 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#837090: wordpress: CVE-2016-6896 CVE-2016-6897

[Salvatore Bonaccorso]

Source: wordpress
Version: 4.5.3+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerabilities were published for wordpress.

CVE-2016-6896[0] and CVE-2016-6897[1]. It was reported that they at
least affect 4.5.3, no earlier version were so far checked, since no
full details to fixes given. There are more information in [2].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-6896
[1] https://security-tracker.debian.org/tracker/CVE-2016-6897
[2] 
https://sumofpwn.nl/advisory/2016/path_traversal_vulnerability_in_wordpress_core_ajax_handlers.html
[3] http://seclists.org/oss-sec/2016/q3/341

Could you please have a look at those, and please adjust the affected
versions in the BTS as needed.

Regards,
Salvatore

Processed: [bts-link] source package ola

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package ola
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #836383 (http://bugs.debian.org/836383)
> # Bug title: FTBFS on mips*
> #  * https://github.com/OpenLightingProject/ola/pull/1116
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 836383 + fixed-upstream
Bug #836383 [ola] FTBFS on mips*
Added tag(s) fixed-upstream.
> usertags 836383 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#837030: marked as done (gdk-pixbuf: FTBFS on most architectures due to test failures)

[Samuel Thibault]

Unfortunately it now fails due to missing gtk-doc build-dependency.

Samuel

Processed: [bts-link] source package ruby-aruba

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package ruby-aruba
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #836735 (http://bugs.debian.org/836735)
> # Bug title: ruby-aruba: uninitialized constant Aruba::CommandMonitor::Utils
> #  * https://github.com/cucumber/aruba/issues/346
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 836735 + fixed-upstream
Bug #836735 [ruby-aruba] ruby-aruba: uninitialized constant 
Aruba::CommandMonitor::Utils
Added tag(s) fixed-upstream.
> usertags 836735 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#837030: marked as done (gdk-pixbuf: FTBFS on most architectures due to test failures)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 17:25:40 +
with message-id 
and subject line Bug#837030: fixed in gdk-pixbuf 2.35.4-3
has caused the Debian Bug report #837030,
regarding gdk-pixbuf: FTBFS on most architectures due to test failures
to be marked as done.

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

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


-- 
837030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdk-pixbuf
Version: 2.35.4-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:wxwidgets3.0 src:grass src:qgis

Dear Maintainer,

gdk-pixbuf (2.35.4-1) FTBFS on pretty much all architectures due to test
failures:

 ERROR: pixbuf-composite
 ===
 
 **
 
GLib:ERROR:/build/glib2.0-E8y2Xu/glib2.0-2.49.6/./glib/gtestutils.c:3361:g_test_build_filename_va:
 assertion failed (num_path_segments < G_N_ELEMENTS (pathv)): (16 < 16)
 Aborted
 # random seed: R02Sc22c9ad260066d3d905a7b2bba549525
 1..2
 # Start of pixbuf tests
 ok 1 /pixbuf/composite1
 PASS: pixbuf-composite 1 /pixbuf/composite1
 # 
GLib:ERROR:/build/glib2.0-E8y2Xu/glib2.0-2.49.6/./glib/gtestutils.c:3361:g_test_build_filename_va:
 # assertion failed (num_path_segments < G_N_ELEMENTS (pathv)): (16 < 16)
 ERROR: pixbuf-composite - too few tests run (expected 2, got 1)
 ERROR: pixbuf-composite - exited with status 134 (terminated by signal 6?)

This subsequently causes uninstallable build dependencies of its reverse
dependencies.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: gdk-pixbuf
Source-Version: 2.35.4-3

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated gdk-pixbuf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 18:59:21 +0200
Source: gdk-pixbuf
Binary: libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev 
libgdk-pixbuf2.0-doc libgdk-pixbuf2.0-0-udeb gir1.2-gdkpixbuf-2.0
Architecture: source
Version: 2.35.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 gir1.2-gdkpixbuf-2.0 - GDK Pixbuf library - GObject-Introspection
 libgdk-pixbuf2.0-0 - GDK Pixbuf library
 libgdk-pixbuf2.0-0-udeb - GDK Pixbuf library - minimal runtime (udeb)
 libgdk-pixbuf2.0-common - GDK Pixbuf library - data files
 libgdk-pixbuf2.0-dev - GDK Pixbuf library (development files)
 libgdk-pixbuf2.0-doc - GDK Pixbuf library (documentation)
Closes: 837030
Changes:
 gdk-pixbuf (2.35.4-3) unstable; urgency=medium
 .
   * Make sure to NULL terminate the arguments passed to g_test_get_filename().
 Otherwise the /pixbuf/composite2 test will segfault. (Closes: #837030)
   * Make test-suite failures fatal again.
Checksums-Sha1:
 043bc42c4c2f7d4962341c1b9f36b0749f83fef4 2844 gdk-pixbuf_2.35.4-3.dsc
 c2c0ce4f0cadc486b170b773e21de5aad97eecb1 13520 
gdk-pixbuf_2.35.4-3.debian.tar.xz
Checksums-Sha256:
 5afcfd2b135d67575093884ecf40c2a270e32bbb49d631a4cea3689b3a1f5dd3 2844 
gdk-pixbuf_2.35.4-3.dsc
 170a0ceaa524919adb467df2d6fc54c0ed62d80a7f432936f0b22bdcd4e7813e 13520 
gdk-pixbuf_2.35.4-3.debian.tar.xz
Files:
 bb3829e4fe6d8e6312d98db1e7fa8c82 2844 libs optional gdk-pixbuf_2.35.4-3.dsc
 2ad59567e8e5d6b7b9173400aa429490 13520 libs optional 
gdk-pixbuf_2.35.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCAAYBQJX0ZmyERxiaWVibEBkZWJpYW4ub3JnAAoJEGrh3w1gjyLcCTkQ
AI0mryJVcUDaLs+TcBDfaHr9y2OaO+kmLc9V0CzF5qzE4BLpVWvJfTw57Ph6Xg+L
6HT9qQMVlAGJ8x0Jv0PUmUu/ocYssjcy1/FDEYPpLWgd1U2faLJfUowsZJC5lXwC
uLPI17CqQKwk+pntYiRRY87h1kiHiTDCwR7xIkrKwl1NNtcGj4XT3tFyXwUC3B23
QwN5pLcqKpYh2KE7kJe2FUuxV4U+TKlw/JDJbZ6uUG4T60WyUosNCuwiD0tgGBOl
+X0iKGHtxgGCk1lEEcHfUVvJ2clpGJGIpPUuIGk1Blrmrfm8iyWZa3ZirNriLhRv
1BLQ4wZMIc2tovF4tks638bgjh1R8NJBfdLmHm1MgeznFLp0myVDIBuLZVzx68QK

Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

[Mattia Rizzolo]

On Thu, Sep 08, 2016 at 07:18:08PM +0200, Svante Signell wrote:
> On Wed, 2016-09-07 at 14:14 +0200, Xavier Grave wrote:
> > No, I think you don't need more tests since you have found the
> > conflict source as far as I understand.
> > 
> > I'm very short of time for the month - may be someone on debian-ada
> > can test your patched package ? Can you provide an url to download it
> > please ?
> 
> I don't have a natural url place to put the changes, sorry. The patches
> were attached to my first posting in this thread and time is running
> out until the package is removed. The patches are also available in bug
> #835966.

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=835966;msg=13;filename=examples_corba_echo_echo-impl.adb.patch
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=835966;msg=13;filename=debian_patches_series.patch
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=835966;msg=13;filename=src_csupport.c.patch
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=835966;msg=13;filename=hardening.patch
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=835966;msg=13;filename=debian_rules.patch
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=835966;msg=13;filename=debian_control.patch

if you want to wget them you need to quote the URLs (as due to the ; the
shell would think it a series of command chained).

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

[Svante Signell]

On Wed, 2016-09-07 at 14:14 +0200, Xavier Grave wrote:
> No, I think you don't need more tests since you have found the
> conflict source as far as I understand.
> 
> I'm very short of time for the month - may be someone on debian-ada
> can test your patched package ? Can you provide an url to download it
> please ?

I don't have a natural url place to put the changes, sorry. The patches
were attached to my first posting in this thread and time is running
out until the package is removed. The patches are also available in bug
#835966.

HTH

Bug#837086: tea: FTBFS on the arch:all buildd (dpkg-buildpackage -A)

[Andreas Beckmann]

Source: tea
Version: 42.0.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

tea FTBFS while building only arch-indep packages (as with
dpkg-buildpackage -A, such as done on the arch:all buildds):

https://buildd.debian.org/status/fetch.php?pkg=tea=all=42.0.0-2=1473268741

   debian/rules override_dh_install
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_install
cp icons/tea-icon-v3-02.png 
/«PKGBUILDDIR»/debian/tea/usr/share/icons/hicolor/128x128/apps/tea.png
cp: cannot create regular file 
'/«PKGBUILDDIR»/debian/tea/usr/share/icons/hicolor/128x128/apps/tea.png': No 
such file or directory
debian/rules:17: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1


Andreas

Bug#837084: font-manager: fails to install: font-manager.postinst: glib-compile-schemas: not found

[Alessio Treglia]

Ciao Andreas,

Thanks for reporting this.

I'll do some work on it as soon as possible.

Cheers.

-- 
Alessio Treglia  | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer|  quadris...@ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A

Bug#834158: marked as done (lvtk: FTBFS: boost/system/error_code.hpp:221: undefined reference to `boost::system::generic_category()')

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 16:30:53 +
with message-id 
and subject line Bug#834158: fixed in lvtk 1.2.0~dfsg0-2
has caused the Debian Bug report #834158,
regarding lvtk: FTBFS: boost/system/error_code.hpp:221: undefined reference to 
`boost::system::generic_category()'
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.)


-- 
834158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lvtk
Version: 1.2.0~dfsg0-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,

lvtk fails to build from source in unstable/amd64:

  [..]

  Setting up libharfbuzz-dev:amd64 (1.2.7-1+b1) ...
  Setting up fontconfig (2.11.0-6.5) ...
  Regenerating fonts cache... done.
  Setting up libcups2:amd64 (2.1.4-4) ...
  Setting up libfontconfig1-dev:amd64 (2.11.0-6.5) ...
  Setting up libsm-dev:amd64 (2:1.2.2-1+b1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxfixes3:amd64 (1:5.0.2-1) ...
  Setting up libatkmm-1.6-dev:amd64 (2.24.2-1) ...
  Setting up x11proto-fixes-dev (1:5.0-2) ...
  Setting up libgdk-pixbuf2.0-0:amd64 (2.34.0-1) ...
  Setting up libxcb-shm0-dev:amd64 (1.11.1-1.1) ...
  Setting up libgd3:amd64 (2.2.3-3+b1) ...
  Setting up gir1.2-gdkpixbuf-2.0:amd64 (2.34.0-1) ...
  Setting up libxrender-dev:amd64 (1:0.9.9-2) ...
  Setting up libxmu6:amd64 (2:1.1.2-2) ...
  Setting up libxcb-render0-dev:amd64 (1.11.1-1.1) ...
  Setting up x11proto-damage-dev (1:1.2.1-2) ...
  Setting up libxft-dev (2.3.2-1) ...
  Setting up gtk-update-icon-cache (3.20.7-1) ...
  Setting up libgdk-pixbuf2.0-dev (2.34.0-1) ...
  Setting up libxcursor1:amd64 (1:1.1.14-1+b1) ...
  Setting up libxext-dev:amd64 (2:1.3.3-1) ...
  Setting up libpango-1.0-0:amd64 (1.40.1-1) ...
  Setting up libxfixes-dev:amd64 (1:5.0.2-1) ...
  Setting up x11proto-composite-dev (1:0.4.2-2) ...
  Setting up libxrandr2:amd64 (2:1.5.0-1) ...
  Setting up libxi6:amd64 (2:1.7.6-1) ...
  Setting up libxaw7:amd64 (2:1.0.13-1) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up libcairomm-1.0-1v5:amd64 (1.12.0-1+b1) ...
  Setting up libxinerama1:amd64 (2:1.1.3-1+b1) ...
  Setting up libxcursor-dev:amd64 (1:1.1.14-1+b1) ...
  Setting up libxdamage1:amd64 (1:1.1.4-2+b1) ...
  Setting up libxrandr-dev:amd64 (2:1.5.0-1) ...
  Setting up libxcomposite-dev (1:0.4.4-1) ...
  Setting up libcairo-script-interpreter2:amd64 (1.14.6-1+b1) ...
  Setting up libcairo-gobject2:amd64 (1.14.6-1+b1) ...
  Setting up libxdamage-dev:amd64 (1:1.1.4-2+b1) ...
  Setting up libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Setting up libxinerama-dev:amd64 (2:1.1.3-1+b1) ...
  Setting up libxi-dev (2:1.7.6-1) ...
  Setting up libcairo2-dev (1.14.6-1+b1) ...
  Setting up gir1.2-freedesktop:amd64 (1.48.0-3) ...
  Setting up libcairomm-1.0-dev:amd64 (1.12.0-1+b1) ...
  Setting up libpangoxft-1.0-0:amd64 (1.40.1-1) ...
  Setting up libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Setting up libpangomm-1.4-1v5:amd64 (2.40.0-1) ...
  Setting up gir1.2-pango-1.0:amd64 (1.40.1-1) ...
  Setting up libpango1.0-dev (1.40.1-1) ...
  Setting up libpangomm-1.4-dev:amd64 (2.40.0-1) ...
  Setting up libgvc6 (2.38.0-14) ...
  Setting up librsvg2-2:amd64 (2.40.16-1) ...
  Setting up librsvg2-common:amd64 (2.40.16-1) ...
  Setting up graphviz (2.38.0-14) ...
  Setting up gnome-icon-theme (3.12.0-2) ...
  update-alternatives: using 
/usr/share/icons/gnome/scalable/places/debian-swirl.svg to provide 
/usr/share/icons/gnome/scalable/places/start-here.svg (start-here.svg) in auto 
mode
  Setting up libgtk2.0-0:amd64 (2.24.30-4) ...
  Setting up libgtkmm-2.4-1v5:amd64 (1:2.24.4-2+b1) ...
  Setting up gir1.2-gtk-2.0 (2.24.30-4) ...
  Setting up libgtk2.0-dev (2.24.30-4) ...
  Setting up libgtkmm-2.4-dev:amd64 (1:2.24.4-2+b1) ...
  Setting up lvtk-build-deps (1.2.0~dfsg0-1) ...
  Processing triggers for libc-bin (2.23-4) ...
  Processing triggers for systemd (231-1) ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.34.0-1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=e0a5e1332085
  

Bug#836335: marked as done (lldb dependency cannot be satisfied on all archs)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 16:30:39 +
with message-id 
and subject line Bug#836335: fixed in llvm-toolchain-3.8 1:3.8.1-12
has caused the Debian Bug report #836335,
regarding lldb dependency cannot be satisfied on all archs
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.)


-- 
836335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rustc
Version: 1.10.0+dfsg1-3
Severity: serious
Tags: sid stretch

excuses:
32 days old (needed 5 days)
rust-lldb/arm64 unsatisfiable Depends: lldb
Valid candidate

the package doesn't migrate, you should only depend on lldb on architectures
where it exists.
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-3.8
Source-Version: 1:3.8.1-12

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-3.8 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 10:39:51 +0200
Source: llvm-toolchain-3.8
Binary: clang-3.8 clang-format-3.8 clang-tidy-3.8 clang-3.8-doc libclang1-3.8 
libclang1-3.8-dbg libclang-3.8-dev libclang-common-3.8-dev libfuzzer-3.8-dev 
python-clang-3.8 clang-3.8-examples libllvm3.8 libllvm3.8-dbg llvm-3.8 
llvm-3.8-runtime llvm-3.8-dev llvm-3.8-tools libllvm-3.8-ocaml-dev llvm-3.8-doc 
llvm-3.8-examples lldb-3.8 liblldb-3.8 liblldb-3.8-dbg python-lldb-3.8 
liblldb-3.8-dev lldb-3.8-dev
Architecture: source amd64 all
Version: 1:3.8.1-12
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-3.8  - C, C++ and Objective-C compiler (LLVM based)
 clang-3.8-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-3.8-examples - Clang examples
 clang-format-3.8 - Tool to format C/C++/Obj-C code
 clang-tidy-3.8 - clang-based C++ linter tool
 libclang-3.8-dev - clang library - Development package
 libclang-common-3.8-dev - clang library - Common development package
 libclang1-3.8 - C interface to the clang library
 libclang1-3.8-dbg - clang library
 libfuzzer-3.8-dev - Library for coverage-guided fuzz testing
 liblldb-3.8 - Next generation, high-performance debugger, library
 liblldb-3.8-dbg - Next generation, high-performance debugger, debugging 
libraries
 liblldb-3.8-dev - Next generation, high-performance debugger - Header files
 libllvm-3.8-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm3.8 - Modular compiler and toolchain technologies, runtime library
 libllvm3.8-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lldb-3.8   - Next generation, high-performance debugger
 lldb-3.8-dev - transitional dummy package to liblldb-3.8-dev
 llvm-3.8   - Modular compiler and toolchain technologies
 llvm-3.8-dev - Modular compiler and toolchain technologies, libraries and 
header
 llvm-3.8-doc - Modular compiler and toolchain technologies, documentation
 llvm-3.8-examples - Modular compiler and toolchain technologies, examples
 llvm-3.8-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-3.8-tools - Modular compiler and toolchain technologies, tools
 python-clang-3.8 - Clang Python Bindings
 python-lldb-3.8 - Next generation, high-performance debugger, python lib
Closes: 836335 836591
Changes:
 llvm-toolchain-3.8 (1:3.8.1-12) unstable; urgency=medium
 .
   * Fix a ftbfs on lldb on arm64 (Closes: #836591) (Closes: #836335)
 Once more, thanks to Ximin Luo for investigating
Checksums-Sha1:
 45da1d811ec0be6e106c6c2b3dd4401ecb5e568b 6028 llvm-toolchain-3.8_3.8.1-12.dsc
 434843c28e116f5a3151b43e638a6ea23495f2fb 62284 
llvm-toolchain-3.8_3.8.1-12.debian.tar.xz
 b9d48d09dd99fd47c933fe0d8f4beb9bcbf48250 131653682 
clang-3.8-dbgsym_3.8.1-12_amd64.deb
 84b87c852a03a4775f7e6ff3c2e31a902ce08734 580258 

Bug#836636: marked as done (libprelude: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 16:26:24 +
with message-id 
and subject line Bug#836636: fixed in libprelude 1.0.0-11.8
has caused the Debian Bug report #836636,
regarding libprelude: please drop the build dependency on hardening-wrapper
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.)


-- 
836636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libprelude
Version: 1.0.0-11.7
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: libprelude
Source-Version: 1.0.0-11.8

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libprelude package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Sep 2016 17:33:46 +0200
Source: libprelude
Binary: libprelude-dev libprelude2 libprelude2-dbg libprelude-perl 
python-prelude
Architecture: source
Version: 1.0.0-11.8
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier 
Changed-By: gregor herrmann 
Closes: 836636
Description: 
 libprelude-dev - Security Information Management System [ Development files ]
 libprelude-perl - Security Information Management System [ Base library ]
 libprelude2 - Security Information Management System [ Base library ]
 libprelude2-dbg - Security Information Management System [ Debug symbols ]
 python-prelude - Security Information Management System [ Base library ]
Changes:
 libprelude (1.0.0-11.8) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "please drop the build dependency on hardening-wrapper", which causes
 the package to FTBFS:
 drop hardening-wrapper from debian/control and related variables from
 debian/rules.
 (Closes: #836636)
   * Bring back some hardening via dpkg-buildflags and DEB_BUILD_MAINT_OPTIONS
 in debian/rules.
Checksums-Sha1: 
 617064ab3233ceebfd709dce92454aade4fc7915 2213 libprelude_1.0.0-11.8.dsc
 b3e317fb82ce891885aae222324d26017bc5df04 15408 
libprelude_1.0.0-11.8.debian.tar.xz
Checksums-Sha256: 
 7e98515491dee3f7886454ec8fa252e1e0d47d74b294faeb9413ff2526a88297 2213 
libprelude_1.0.0-11.8.dsc
 38fee666cd0f2f1df58fd49d61f6ff397f48c909833ad05e82ce0d4d04873242 15408 
libprelude_1.0.0-11.8.debian.tar.xz
Files: 
 b3fe2e21227ab554b91ac9b5b6bbee17 2213 libs extra libprelude_1.0.0-11.8.dsc
 590500341e7cddfa512c8a9c555691e3 15408 libs extra 
libprelude_1.0.0-11.8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJXzuJ7XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGQd8QAKpIMRnLUikZEe55eeKVr7PZ
E2aub3QPKrXGut6/raSKyUOQmlC9Xv23d5dCa3IB9JY+v/NVG40D+gD3QrQg4JI1
pOSYNOzNM/UhycJzrpxMrqqyvWP68zLM9e687CQxGyZUxmB1SD4rrQS4ZsqLAPJI
eEIuu6Tozx9LeqRl/rzeL9nA5mKc7JSe78QoOMVVOf0u8Efiz0//QrWfrpMjJJUD
dk2l7iVtOurfCbaLwjdIN9OLcqYeEbDC/YMW/gx1np9Rc8e3B0x6ca7kqtXKOpny
gn/dMOhyynM3pY32Qej5zBsJyjmyWgO2/ZIaJejuEbNsKr6QJ6qxZz19srj6EJ+F
q5gAL2GLhGqfiit3iePI00Z9ukM9nsC0jr2TL/F90r0B11qM6PZUjDmNmWp/t5RV
NfUMdx5YnRjOuCNQyW7CmeC+Gp/m9mOtzVVQcHD3ZkE7dIA8M8B8w7WkfMNMtv72
9gX6QOVVvAc0bY8PpBM52m2gLpHXUwdMeRPzf8mZmxq3mumyZ9SMbHW1XqNVGhtK
vil/AXjibORLz+id+3bL1V8oRydpDrPVV8vKUyH/VXkKIbmi/UNXon0eQSjVjBJ5

Bug#837085: neurodebian-archive-keyring: fails to install: Error: gnupg, gnupg2 and gnupg1 do not seem to be installed,

[Andreas Beckmann]

Package: neurodebian-archive-keyring
Version: 0.37.4
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 neurodebian-archive-keyring.
  (Reading database ... 
(Reading database ... 6247 files and directories currently installed.)
  Preparing to unpack .../neurodebian-archive-keyring_0.37.4_all.deb ...
  Unpacking neurodebian-archive-keyring (0.37.4) ...
  Setting up neurodebian-archive-keyring (0.37.4) ...
  Warning: The postinst maintainerscript of the package 
neurodebian-archive-keyring
  Warning: seems to use apt-key (provided by apt) without depending on gnupg or 
gnupg2.
  Warning: This will BREAK in the future and should be fixed by the package 
maintainer(s).
  Note: Check first if apt-key functionality is needed at all - it probably 
isn't!
  Error: gnupg, gnupg2 and gnupg1 do not seem to be installed,
  Error: but apt-key requires gnupg, gnupg2 or gnupg1 for this operation.
  
  dpkg: error processing package neurodebian-archive-keyring (--configure):
   subprocess installed post-installation script returned error exit status 255
  Errors were encountered while processing:
   neurodebian-archive-keyring


cheers,

Andreas


neurodebian-archive-keyring_0.37.4.log.gz
Description: application/gzip

Bug#831797: marked as done (gearhead: FTBFS with -fdebug-prefix-map)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 16:22:43 +
with message-id 
and subject line Bug#831797: fixed in gearhead 1.302-2
has caused the Debian Bug report #831797,
regarding gearhead: FTBFS with -fdebug-prefix-map
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.)


-- 
831797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gearhead
Version: 1.302-1
Severity: important
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear maintainer, your package FTBFS when dpkg enables the build flag
-fdebug-prefix-map from the reproducible/fixdebugpath feature area:

dpkg-buildpackage: info: source package gearhead
dpkg-buildpackage: info: source version 1.302-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Kari Pahula 
 dpkg-source --before-build gearhead-1.302
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-arch-stamp build-arch-console-stamp build-arch-sdl-stamp 
build-indep-stamp
rm -rf debian/build
dh_clean
 debian/rules build
dh_testdir
mkdir -p debian/build/console
cp *.pas *.pp *.inc debian/build/console
dh_testdir
cd debian/build/console; fpc -g -O2 -fdebug-prefix-map=/build/gearhead-1.302=. 
-g -XD gharena
Error: Illegal parameter: -fdebug-prefix-map=/build/gearhead-1.302=.
Error: /usr/bin/ppcx64 returned an error exitcode
debian/rules:38: recipe for target 'build-arch-console-stamp' failed
make: *** [build-arch-console-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Please note that the intention is to enable this build flag RSN
https://lists.debian.org/msgid-search/20160718085659.gi7...@chase.mapreri.org


A quick workaround would be to disable the reproducible/fixdebugpath
buildflags with
export DEB_BUILD_MAINT_OPTIONS=reproducible=-fixdebugpath

The real problem here is that you are passing CFLAGS to fpc, and CFLAGS
are definitely not meant to be passed to fpc.  If I were you I'd revise
such choice (I also suppose that's the reason you disabled the hardening
buildflags, also those enabled by default (which I consider a pretty bad
thing)?).  I can't really figre what you'd gain, what CFLAGS contains
in your case is only '-g -O2', and apparently the build system is
alraedy putting -g; you can probably live by either adding -O2 yourself
in d/rules or leaving it to whatever default fpc has.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gearhead
Source-Version: 1.302-2

We believe that the bug you reported is fixed in the latest version of
gearhead, 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.
Kari Pahula  (supplier of updated gearhead package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 18:36:45 +0300
Source: gearhead
Binary: gearhead gearhead-sdl gearhead-data
Architecture: source all amd64
Version: 1.302-2
Distribution: unstable
Urgency: medium
Maintainer: Kari Pahula 
Changed-By: Kari Pahula 
Description:
 gearhead   - roguelike mecha role playing game, console version
 gearhead-data - data files for gearhead
 gearhead-sdl - roguelike mecha role playing game, SDL version
Closes: 831797
Changes:
 gearhead (1.302-2) unstable; urgency=medium
 .
   * Stop using CFLAGS as a compile flag variable, fpc's not a C compiler.
 (Closes: #831797)
Checksums-Sha1:
 d71c6a3501887a8ab4c0bae21c1203a84c6ceba0 1892 gearhead_1.302-2.dsc
 

Bug#837084: font-manager: fails to install: font-manager.postinst: glib-compile-schemas: not found

[Andreas Beckmann]

Package: font-manager
Version: 0.7.2+0git410aa802-2
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 font-manager.
  (Reading database ... 
(Reading database ... 14582 files and directories currently installed.)
  Preparing to unpack .../font-manager_0.7.2+0git410aa802-2_amd64.deb ...
  Unpacking font-manager (0.7.2+0git410aa802-2) ...
  Processing triggers for libglib2.0-0:amd64 (2.49.6-1) ...
  Processing triggers for libc-bin (2.24-2) ...
  Setting up font-manager (0.7.2+0git410aa802-2) ...
  /var/lib/dpkg/info/font-manager.postinst: 23: 
/var/lib/dpkg/info/font-manager.postinst: glib-compile-schemas: not found
  dpkg: error processing package font-manager (--configure):
   subprocess installed post-installation script returned error exit status 127
  Processing triggers for libc-bin (2.24-2) ...
  Errors were encountered while processing:
   font-manager


cheers,

Andreas


font-manager_0.7.2+0git410aa802-2.log.gz
Description: application/gzip

Bug#836426: Caused by libgtk-3-0 3.21

[Josh Triplett]

On Thu, Sep 08, 2016 at 01:48:01PM +0200, Michael Biebl wrote:
> Am 08.09.2016 um 03:23 schrieb Josh Triplett:
> > It seems appropriate for an issue that causes window contents to fail to
> > render, making gnome-boxes unusable with that version of GTK+.  
> 
> The emacs warnings don't look critical and are most likely something
> which needs to be addressed in emacs.

I don't know the associated impact of those; if they're *just* a warning
with no other impact, then perhaps.

> As for gnome-boxes, can you reproduce the problem with 3.21.3 from
> unstable? I just tested a local installation of debian 8.5 and that
> worked fine. I don't have  windows ISO to test whether that is
> reproducible with that setup.

I'll test gnome-boxes 3.21.3 next week.

However, it seems like a compatibility issue if upgrading to a new
libgtk-3-0 with the same SONAME breaks applications that worked with a
previous version.  Other than rare circumstances like "application doing
something always clearly documented as broken and old versions let them
get away with it", which might *occasionally* be justifiable if it
doesn't cause significant breakage in practice, generally that kind of
compatibility issue seems like a bug in the library, not the
application.

> I think it would be best if you file this issue upstream at the
> gnome-boxes bug tracker
> https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-boxes

Before reporting it there, I'd need to confirm that 1) the bug still
appears with gnome-boxes 3.21.3 and 2) the bug actually lies in
gnome-boxes rather than in libgtk-3-0.

Processed: Re: Bug#837065: gdal-bin: ogr2ogr Segmentation fault

[Debian Bug Tracking System]

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

> tags 837065 - moreinfo
Bug #837065 [gdal-bin] gdal-bin: ogr2ogr Segmentation fault
Removed tag(s) moreinfo.
> fixed 837065 gdal/2.1.1+dfsg-2
Bug #837065 [gdal-bin] gdal-bin: ogr2ogr Segmentation fault
Marked as fixed in versions gdal/2.1.1+dfsg-2.
> thanks
Stopping processing here.

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

Bug#837065: marked as done (gdal-bin: ogr2ogr Segmentation fault)

[Debian Bug Tracking System]

Your message dated Thu, 8 Sep 2016 17:27:41 +0200
with message-id 
and subject line Re: Bug#837065: gdal-bin: ogr2ogr Segmentation fault
has caused the Debian Bug report #837065,
regarding gdal-bin: ogr2ogr Segmentation fault
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.)


-- 
837065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdal-bin
Version: 2.1.1+dfsg-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

On an up-to-date Debian testing system, the following command, which normally 
just works,
now gives a seg fault:
  ogr2ogr -t_srs EPSG:3857 -f "SQLite" -dsco SPATIALITE=YES \
 file.sqlite points.xml

I think I noted a very recent update of spatialite in testing, so this might be 
related to that?

Andy.

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

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

Versions of packages gdal-bin depends on:
ii  libc6   2.23-5
ii  libgcc1 1:6.1.1-11
ii  libgdal20 [gdal-abi-2-1-1]  2.1.1+dfsg-1+b1
ii  libstdc++6  6.1.1-11

gdal-bin recommends no packages.

Versions of packages gdal-bin suggests:
ii  python-gdal  2.1.1+dfsg-1+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
tags 837065 - moreinfo
fixed 837065 gdal/2.1.1+dfsg-2
thanks

Hi Andy,

On 09/08/2016 05:15 PM, Andy G Wood wrote:
> On Thursday, 8 September 2016 15:24:46 BST Sebastiaan Couwenberg wrote:
>> On 09/08/2016 03:07 PM, Andy G Wood wrote:
 Please provide a list of the package versions you have installed for the
 libdal20 dependencies (apt-cache show libgdal20 | grep Depends).
> 
> libogdi3.2 3.2.0+ds-1+b1
> libproj12 4.9.3-1
> libspatialite7:amd64 4.3.0a-5+b1

The above packages were rebuilt for the proj transition, but your gdal
version is still from before the rebuild as part of that transition.

If you cannot wait 5 days for the gdal version in unstable to migrate to
testing, you can temporarily add the sources for unstable and upgrade to
the gdal version there (and subsequently remove the unstable sources).

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1--- End Message ---

Bug#837079: shadow: src:shadow FTBFS due to conflicting hardening-wrapper

[Johannes Schauer]

Source: shadow
Version: 1:4.2-3.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

here part of my build log:

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-shadow-dummy : Depends: hardening-wrapper but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed


Dose3 gives a better explanation:

  package: shadow
  version: 1:4.2-3.1
  architecture: any
  type: src
  status: broken
  reasons:
   -
conflict:
 pkg1:
  package: binutils
  version: 2.27-8
  architecture: amd64
  unsat-conflict: hardening-wrapper:amd64 (< 2.8+nmu3)
 pkg2:
  package: hardening-wrapper
  version: 2.8+nmu2
  architecture: amd64
 depchain1:
  -
   depchain:
-
 package: shadow
 version: 1:4.2-3.1
 architecture: any
 type: src
 depends: hardening-wrapper:amd64
-
 package: hardening-wrapper
 version: 2.8+nmu2
 architecture: amd64
 depends: binutils:amd64 (>= 2.25.90)
 depchain2:
  -
   depchain:
-
 package: shadow
 version: 1:4.2-3.1
 architecture: any
 type: src
 depends: hardening-wrapper:amd64

So the problem is that binutils conflicts with hardening-wrapper and indeed:

Package: binutils
Version: 2.27-8
Breaks: [...], hardening-wrapper (<< 2.8+nmu3)

I don't know what the proper solution for this is but #836653 indicates
that you might want to drop the build-dependency on hardening-wrapper
completely.

Thanks!

cheers, josch

Bug#837065: gdal-bin: ogr2ogr Segmentation fault

[Andy G Wood]

On Thursday, 8 September 2016 15:24:46 BST Sebastiaan Couwenberg wrote:
> On 09/08/2016 03:07 PM, Andy G Wood wrote:
> >> Please provide a list of the package versions you have installed for the
> >> libdal20 dependencies (apt-cache show libgdal20 | grep Depends).
> > 
> > $ apt-cache show libgdal20 | grep Depends
> 
> Those are only the libgdal20 dependencies, not their installed versions.

Sorry I missed that bit.  Slight delay to "bash" the answer, which is:
libarmadillo6 1:6.700.6+dfsg-1
libc6:amd64 2.23-5
libcrypto++6 5.6.3-7
libcurl3-gnutls:amd64 7.50.1-1
libdap23:amd64 3.18.0-2
libdapclient6v5:amd64 3.18.0-2
libdapserver7v5:amd64 3.18.0-2
libepsilon1:amd64 0.9.2+dfsg-2
libexpat1:amd64 2.2.0-1
libfreexl1:amd64 1.0.2-2
libgcc1:amd64 1:6.1.1-11
libgeos-c1v5 3.5.0-4
libgeotiff2:amd64 1.4.2-2+b1
libgif7:amd64 5.1.4-0.3
libhdf4-0-alt 4.2.12-1
libhdf5-10:amd64 1.8.16+docs-8
libjpeg62-turbo:amd64 1:1.5.0-1
libjson-c3:amd64 0.12.1-1
libkmlbase1:amd64 1.3.0-3
libkmldom1:amd64 1.3.0-3
libkmlengine1:amd64 1.3.0-3
libkmlregionator1:amd64 1.3.0-3
libkmlxsd1:amd64 1.3.0-3
liblzma5:amd64 5.1.1alpha+20120614-2.1
libnetcdf11 1:4.4.1-2
libodbc1:amd64 2.3.1-4.1
libogdi3.2 3.2.0+ds-1+b1
libopenjp2-7:amd64 2.1.1-1
libpcre3:amd64 2:8.39-2
libpng16-16:amd64 1.6.24-2
libpoppler61:amd64 0.44.0-3
libpq5:amd64 9.6~rc1-1
libproj12 4.9.3-1
libqhull7:amd64 2015.2-1
libspatialite7:amd64 4.3.0a-5+b1
libstdc++6:amd64 6.1.1-11
libsz2:amd64 0.3.2-1
libtiff5:amd64 4.0.6-2
libwebp6:amd64 0.5.1-2
libxerces-c3.1:amd64 3.1.3+debian-2.1+b1
libxml2:amd64 2.9.4+dfsg1-1+b1
odbcinst1debian2:amd64 2.3.1-4.1
zlib1g:amd64 1:1.2.8.dfsg-2+b1

Andy.

Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

[Sebastiaan Couwenberg]

On 09/08/2016 05:03 PM, Samuel Thibault wrote:
> Michael Biebl, on Thu 08 Sep 2016 16:51:24 +0200, wrote:
>> Am 08.09.2016 um 14:59 schrieb Sebastiaan Couwenberg:
>>> On 09/08/2016 04:05 AM, Michael Biebl wrote:
 We've already seen the issue and forwarded to upstream.
>>>
>>> Due to the large number of affected packages that cannot be built until
>>> gdk-pixbuf is fixed, please consider disabling the test until upstream
>>> can provide a fix.
>>
>> Sure, made the test-suite non-fatal in 2.35.4-2.
>>
>> Let's keep this bug open and at RC though. Otherwise this would kind of
>> defeat the purpose of the test-suite.
> 
> I believe he meant only disabling that precise test, and not ignoring
> the whole testsuite.

Yes, but to change in -2 gets us the same result. gdk-pixbuf should no
longer FTBFS everywhere allowing the rdeps to be built again.

Thanks for not waiting for the upstream fix before unblocking the rdeps
with a new gdk-pixbuf upload.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#837067: libsecret: FTBFS too much often (failing tests)

[Michael Biebl]

Control: retitle -1 libsecret: FTBFS - /collection/delete-sync failure

Am 08.09.2016 um 14:40 schrieb Santiago Vila:
> Package: src:libsecret
> Version: 0.18.5-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 autoreconf,gir,gnome
>dh_testdir -i
>dh_update_autotools_config -i
>dh_autoreconf -i
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build'.
> libtoolize: copying file 'build/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build/m4'.
> libtoolize: copying file 'build/m4/libtool.m4'
> libtoolize: copying file 'build/m4/ltoptions.m4'
> libtoolize: copying file 'build/m4/ltsugar.m4'
> libtoolize: copying file 'build/m4/ltversion.m4'
> libtoolize: copying file 'build/m4/lt~obsolete.m4'
> 
> [... snipped ...]
> 

You snipped the interesting part. The failing test is
/collection/delete-sync, which is known to behave erratically.
See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821347#64

Looks like a timing issue.


-- 
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: Bug#837067: libsecret: FTBFS too much often (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libsecret: FTBFS - /collection/delete-sync failure
Bug #837067 [src:libsecret] libsecret: FTBFS too much often (failing tests)
Changed Bug title to 'libsecret: FTBFS - /collection/delete-sync failure' from 
'libsecret: FTBFS too much often (failing tests)'.

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

Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

[Samuel Thibault]

Hello,

Michael Biebl, on Thu 08 Sep 2016 16:51:24 +0200, wrote:
> Am 08.09.2016 um 14:59 schrieb Sebastiaan Couwenberg:
> > On 09/08/2016 04:05 AM, Michael Biebl wrote:
> >> We've already seen the issue and forwarded to upstream.
> > 
> > Due to the large number of affected packages that cannot be built until
> > gdk-pixbuf is fixed, please consider disabling the test until upstream
> > can provide a fix.
> 
> Sure, made the test-suite non-fatal in 2.35.4-2.
> 
> Let's keep this bug open and at RC though. Otherwise this would kind of
> defeat the purpose of the test-suite.

I believe he meant only disabling that precise test, and not ignoring
the whole testsuite.

Samuel

Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

[Michael Biebl]

Am 08.09.2016 um 14:59 schrieb Sebastiaan Couwenberg:
> On 09/08/2016 04:05 AM, Michael Biebl wrote:
>> We've already seen the issue and forwarded to upstream.
> 
> Due to the large number of affected packages that cannot be built until
> gdk-pixbuf is fixed, please consider disabling the test until upstream
> can provide a fix.
> 

Sure, made the test-suite non-fatal in 2.35.4-2.

Let's keep this bug open and at RC though. Otherwise this would kind of
defeat the purpose of the test-suite.

We ship a symbols file in gdk-pixbuf, so packages should usually not
pick up a tight dependency on the new version.

Michael


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

[Debian Bug Tracking System]

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

> tags 835754 + patch upstream fixed-upstream
Bug #835754 [src:z3] z3: FTBFS: util/debug.cpp:79:38: error: cannot convert 
'std::basic_istream' to 'bool' in initialization
Added tag(s) fixed-upstream, patch, and upstream.
> thanks
Stopping processing here.

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

Bug#837077: FTBFS, dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so needed by debian/budgie-core/usr/bin/budgie-wm

[Michael Biebl]

Source: budgie-desktop
Version: 10.2.6-1
Severity: serious

Hi,

after the recent upgrade of mutter to 3.21.x, budgie-desktop fails to
build from source:

dpkg-shlibdeps: error: couldn't find library libmutter-clutter-1.0.so needed by 
debian/budgie-core/usr/bin/budgie-wm (ELF format: 'elf64-x86-64'; RPATH: '')
dpkg-shlibdeps: warning: couldn't find library libmutter-cogl.so needed by 
debian/budgie-core/usr/bin/budgie-wm (ELF format: 'elf64-x86-64'; RPATH: '')

The complete build log is available at
https://buildd.debian.org/status/package.php?p=budgie-desktop


Regards,
Michael


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

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

Bug#835754: z3: FTBFS: util/debug.cpp:79:38: error: cannot convert 'std::basic_istream' to 'bool' in initialization

[Fabian Wolff]

Control: tags = patch fixed-upstream

Hi,

the issue here is that GCC 6 defaults to -std=gnu++14. Since C++11,
std::basic_ios no longer provides an implicit void* operator but only
an explicit bool operator. Therefore, the problem can be fixed with
this patch:

--- a/src/util/debug.cpp
+++ b/src/util/debug.cpp
@@ -76,7 +76,7 @@
 for (;;) {
 std::cerr << "(C)ontinue, (A)bort, (S)top, (T)hrow exception, Invoke 
(G)DB\n";
 char result;
-bool ok = (std::cin >> result);
+bool ok = bool(std::cin >> result);
 if (!ok) exit(ERR_INTERNAL_FATAL); // happens if std::cin is eof or 
unattached.
 switch(result) {
 case 'C':

Reference: http://en.cppreference.com/w/cpp/io/basic_ios/operator_bool

This was fixed in the upstream repository by this commit:

  https://github.com/Z3Prover/z3/commit/f02d273ee39ae047222e362c37213d29135dc661

Kind regards,
Fabian


signature.asc
Description: PGP signature

Bug#837065: gdal-bin: ogr2ogr Segmentation fault

[Sebastiaan Couwenberg]

On 09/08/2016 03:07 PM, Andy G Wood wrote:
>> Please provide a list of the package versions you have installed for the
>> libdal20 dependencies (apt-cache show libgdal20 | grep Depends).
>  
> $ apt-cache show libgdal20 | grep Depends

Those are only the libgdal20 dependencies, not their installed versions.

Now you need to do `dpkg -l | grep ` for the various packages.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#835741: marked as done (prometheus: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 13:20:21 +
with message-id 
and subject line Bug#835741: fixed in prometheus 1.1.1+ds-1
has caused the Debian Bug report #835741,
regarding prometheus: FTBFS: Tests failures
to be marked as done.

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

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


-- 
835741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus
Version: 1.0.1+ds-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> === RUN   TestRespondSuccess
> --- PASS: TestRespondSuccess (0.00s)
> === RUN   TestRespondError
> --- PASS: TestRespondError (0.00s)
> === RUN   TestParseTime
> --- PASS: TestParseTime (0.00s)
> === RUN   TestParseDuration
> --- PASS: TestParseDuration (0.00s)
> === RUN   TestOptionsMethod
> --- PASS: TestOptionsMethod (0.00s)
> PASS
> okgithub.com/prometheus/prometheus/web/api/v1 0.027s
> ? github.com/prometheus/prometheus/web/ui [no test files]
> dh_auto_test: go test -v -p 1 github.com/prometheus/prometheus/cmd/prometheus 
> github.com/prometheus/prometheus/cmd/promtool 
> github.com/prometheus/prometheus/config 
> github.com/prometheus/prometheus/notifier 
> github.com/prometheus/prometheus/promql 
> github.com/prometheus/prometheus/retrieval 
> github.com/prometheus/prometheus/retrieval/discovery 
> github.com/prometheus/prometheus/retrieval/discovery/consul 
> github.com/prometheus/prometheus/retrieval/discovery/dns 
> github.com/prometheus/prometheus/retrieval/discovery/kubernetes 
> github.com/prometheus/prometheus/retrieval/discovery/marathon 
> github.com/prometheus/prometheus/rules 
> github.com/prometheus/prometheus/storage 
> github.com/prometheus/prometheus/storage/local 
> github.com/prometheus/prometheus/storage/local/codable 
> github.com/prometheus/prometheus/storage/local/index 
> github.com/prometheus/prometheus/storage/local/storagetool 
> github.com/prometheus/prometheus/storage/metric 
> github.com/prometheus/prometheus/storage/remote 
> github.com/prometheus/prometheus/storage/remote/graphite 
> github.com/prometheus/prometheus/storage/remote/influxdb 
> github.com/prometheus/prometheus/storage/remote/opentsdb 
> github.com/prometheus/prometheus/template 
> github.com/prometheus/prometheus/util/cli 
> github.com/prometheus/prometheus/util/flock 
> github.com/prometheus/prometheus/util/httputil 
> github.com/prometheus/prometheus/util/stats 
> github.com/prometheus/prometheus/util/strutil 
> github.com/prometheus/prometheus/util/testutil 
> github.com/prometheus/prometheus/util/treecache 
> github.com/prometheus/prometheus/vendor/github.com/influxdb/influxdb/client 
> github.com/prometheus/prometheus/vendor/github.com/influxdb/influxdb/tsdb 
> github.com/prometheus/prometheus/web 
> github.com/prometheus/prometheus/web/api/v1 
> github.com/prometheus/prometheus/web/ui returned exit code 1
>   cd /<>/prometheus-1.0.1+ds
> debian/rules:67: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/prometheus_1.0.1+ds-1_unstable.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: prometheus
Source-Version: 1.1.1+ds-1

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

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

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated prometheus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 

Bug#837065: gdal-bin: ogr2ogr Segmentation fault

[Andy G Wood]

Hi Bas,

> spatialite, gdal and many other packages were recently rebuilt for the
> transition to proj 4.9.3. Ensure you've upgraded all package

$ sudo apt-get update; sudo apt-get dist-upgrade
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

> gdal 2.1.1+dfsg-1+b1 has not been rebuilt with the proj 4.9.3, you need
> at least +b2 for that. It has most likely not migrated because new gdal
> revisions were uploaded to unstable to deal with the libmysqlclient-dev
> changes, and haven't aged sufficiently to migrate to testing.

As of today (Thu  8 Sep 13:53:11 BST 2016)
gdal 2.1.1+dfsg-4 in unstable is "Too young, only 0 of 5 days old"

> Please provide a list of the package versions you have installed for the
> libdal20 dependencies (apt-cache show libgdal20 | grep Depends).
 
$ apt-cache show libgdal20 | grep Depends
Depends: libarmadillo6, libc6 (>= 2.15), libcrypto++6, libcurl3-gnutls (>= 
7.16.2), libdap23, libdapclient6v5, libdapserver7v5, libepsilon1 (>= 0.8.1), 
libexpat1 (>= 2.0.1), libfreexl1 (>= 0.0.2~beta20110817), libgcc1 (>= 1:3.0), 
libgeos-c1v5 (>= 3.4.2), libgeotiff2 (>= 1.4.1), libgif7 (>= 5.1), libhdf4-0-
alt (>= 4.2r4), libhdf5-10, libjpeg62-turbo (>= 1.3.1), libjson-c3 (>= 0.11), 
libkmlbase1 (>= 1.3.0~r864), libkmldom1 (>= 1.3.0~rc2), libkmlengine1 (>= 
1.3.0~r864), libkmlregionator1 (>= 1.3.0~r864), libkmlxsd1 (>= 1.3.0~r864), 
liblzma5 (>= 5.1.1alpha+20110809), libnetcdf11 (>= 4.0.1), libodbc1 (>= 
2.3.1), libogdi3.2 (>= 3.2.0~beta2), libopenjp2-7 (>= 2.0.0), libpcre3, 
libpng16-16 (>= 1.6.2-1), libpoppler61 (>= 0.44.0), libpq5, libproj12 (>= 
4.8.0), libqhull7, libspatialite7 (>= 4.2.0), libstdc++6 (>= 5.2), libsz2, 
libtiff5 (>= 4.0.3), libwebp6 (>= 0.5.1), libxerces-c3.1, libxml2 (>= 2.7.4), 
odbcinst1debian2 (>= 2.3.1), zlib1g (>= 1:1.2.0)
Depends: libarmadillo6, libc6 (>= 2.15), libcrypto++6, libcurl3-gnutls (>= 
7.16.2), libdap17v5, libdapclient6v5, libdapserver7v5, libepsilon1 (>= 0.8.1), 
libexpat1 (>= 2.0.1), libfreexl1 (>= 0.0.2~beta20110817), libgcc1 (>= 1:4.0), 
libgeos-c1v5 (>= 3.4.2), libgeotiff2 (>= 1.4.1), libgif7 (>= 5.1), libhdf4-0-
alt (>= 4.2r4), libhdf5-10, libjpeg62-turbo (>= 1.3.1), libjson-c3 (>= 0.11), 
libkmlbase1 (>= 1.3.0~r864), libkmldom1 (>= 1.3.0~rc2), libkmlengine1 (>= 
1.3.0~r864), libkmlregionator1 (>= 1.3.0~r864), libkmlxsd1 (>= 1.3.0~r864), 
liblzma5 (>= 5.1.1alpha+20110809), libmysqlclient18, libnetcdf11 (>= 4.0.1), 
libodbc1 (>= 2.3.1), libogdi3.2 (>= 3.2.0~beta2), libopenjp2-7 (>= 2.0.0), 
libpcre3, libpng16-16 (>= 1.6.2-1), libpoppler61 (>= 0.44.0), libpq5, libproj9 
(>= 4.8.0), libqhull7, libspatialite7 (>= 4.2.0), libstdc++6 (>= 5.2), libsz2, 
libtiff5 (>= 4.0.3), libwebp6 (>= 0.5.1), libxerces-c3.1, libxml2 (>= 2.7.4), 
odbcinst1debian2 (>= 2.3.1), zlib1g (>= 1:1.2.0)

Andy.

Processed: Pending fixes for bugs in the prometheus package

[Debian Bug Tracking System]

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

> tag 835741 + pending
Bug #835741 [src:prometheus] prometheus: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#835741: Pending fixes for bugs in the prometheus package

[pkg-go-maintainers]

tag 835741 + pending
thanks

Some bugs in the prometheus package are closed in revision
62c8ee1afbd21e662ee5c5ae673455b77e3a575f in branch 'debian/sid' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/prometheus.git/commit/?id=62c8ee1

Commit message:

Backport fix that closes: #835741.

Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

[Sebastiaan Couwenberg]

On 09/08/2016 04:05 AM, Michael Biebl wrote:
> We've already seen the issue and forwarded to upstream.

Due to the large number of affected packages that cannot be built until
gdk-pixbuf is fixed, please consider disabling the test until upstream
can provide a fix.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Processed: affects 837030

[Debian Bug Tracking System]

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

> affects 837030 src:ns3 src:paraview src:vtk6
Bug #837030 [src:gdk-pixbuf] gdk-pixbuf: FTBFS on most architectures due to 
test failures
Added indication that 837030 affects src:ns3, src:paraview, and src:vtk6
> thanks
Stopping processing here.

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

Bug#837065: gdal-bin: ogr2ogr Segmentation fault

[Sebastiaan Couwenberg]

Control: tags -1 moreinfo

Hi Andi,

On 09/08/2016 02:26 PM, Andy Wood wrote:
> On an up-to-date Debian testing system, the following command, which normally 
> just works,
> now gives a seg fault:
>   ogr2ogr -t_srs EPSG:3857 -f "SQLite" -dsco SPATIALITE=YES \
>  file.sqlite points.xml
> 
> I think I noted a very recent update of spatialite in testing, so this might 
> be related to that?

spatialite, gdal and many other packages were recently rebuilt for the
transition to proj 4.9.3. Ensure you've upgraded all packages.

gdal 2.1.1+dfsg-1+b1 has not been rebuilt with the proj 4.9.3, you need
at least +b2 for that. It has most likely not migrated because new gdal
revisions were uploaded to unstable to deal with the libmysqlclient-dev
changes, and haven't aged sufficiently to migrate to testing.

Please provide a list of the package versions you have installed for the
libdal20 dependencies (apt-cache show libgdal20 | grep Depends).

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#837065: gdal-bin: ogr2ogr Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #837065 [gdal-bin] gdal-bin: ogr2ogr Segmentation fault
Added tag(s) moreinfo.

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

Processed: affects 837030

[Debian Bug Tracking System]

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

> affects 837030 src:hyphy src:gtk+2.0 src:octave-mpi
Bug #837030 [src:gdk-pixbuf] gdk-pixbuf: FTBFS on most architectures due to 
test failures
Added indication that 837030 affects src:hyphy, src:gtk+2.0, and src:octave-mpi
> thanks
Stopping processing here.

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

Processed: affects 837030

[Debian Bug Tracking System]

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

> affects 837030 src:java-atk-wrapper src:openjdk-8
Bug #837030 [src:gdk-pixbuf] gdk-pixbuf: FTBFS on most architectures due to 
test failures
Added indication that 837030 affects src:java-atk-wrapper and src:openjdk-8
> thanks
Stopping processing here.

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

Bug#837065: gdal-bin: ogr2ogr Segmentation fault

[Andy Wood]

Package: gdal-bin
Version: 2.1.1+dfsg-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

On an up-to-date Debian testing system, the following command, which normally 
just works,
now gives a seg fault:
  ogr2ogr -t_srs EPSG:3857 -f "SQLite" -dsco SPATIALITE=YES \
 file.sqlite points.xml

I think I noted a very recent update of spatialite in testing, so this might be 
related to that?

Andy.

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

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

Versions of packages gdal-bin depends on:
ii  libc6   2.23-5
ii  libgcc1 1:6.1.1-11
ii  libgdal20 [gdal-abi-2-1-1]  2.1.1+dfsg-1+b1
ii  libstdc++6  6.1.1-11

gdal-bin recommends no packages.

Versions of packages gdal-bin suggests:
ii  python-gdal  2.1.1+dfsg-1+b1

-- no debconf information

Processed: block 836917 with 837030, affects 837030

[Debian Bug Tracking System]

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

> block 836917 with 837030
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 817690 825934 835680 811651 837055 837059 811907 837058 
837061 831164 837062 837012 812036
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 837030
> affects 837030 src:gmsh
Bug #837030 [src:gdk-pixbuf] gdk-pixbuf: FTBFS on most architectures due to 
test failures
Added indication that 837030 affects src:gmsh
> thanks
Stopping processing here.

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

Processed: Re: Bug#835737: gcr: FTBFS: Tests failures

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771052
Bug #835737 [src:gcr] gcr: FTBFS: Tests failures
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771052'.

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

Bug#835737: gcr: FTBFS: Tests failures

[Michael Biebl]

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771052

Am 28.08.2016 um 11:33 schrieb Lucas Nussbaum:
> Source: gcr
> Version: 3.20.0-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160828 qa-ftbfs
> Justification: FTBFS on amd64

Thanks for your bug report, Lucas.

I've forwarded the issue to upstream. It seems caused by the gnupg 2.1 switch.

Regards,
Michael 


-- 
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: scalapack: FTBFS due to test failures

[Debian Bug Tracking System]

Processing control commands:

> block 836917 by -1
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 837055 825934 837061 817690 835680 811651 831164 837012 
837059 811907 837058 812036
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 837062

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

Processed: gromacs: FTBFS due to test failures

[Debian Bug Tracking System]

Processing control commands:

> block 836917 by -1
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 831164 837012 812036 835680 837055 811651 811907 817690 
837058 825934 837059
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 837061

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

Bug#837059: abyss: FTBFS (error: cannot convert 'std::ifstream {aka std::basic_ifstream}' to 'bool' in return)

[Bas Couwenberg]

Source: abyss
Version: 1.9.0-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 836917 by -1

Dear Maintainer,

The upload of openmpi (2.0.1-3) has triggered an uncoordinated
transition (#836917). Unfortunately your package FTBFS:

 g++ -DHAVE_CONFIG_H -I. -I..  -I.. -I/build/abyss-1.9.0  
-isystem/usr/lib/openmpi/include   -Wdate-time -D_FORTIFY_SOURCE=2 
-isystem/build/abyss-1.9.0/boost_1_56_0 -Wall -Wextra -g -O2 
-fdebug-prefix-map=/build/abyss-1.9.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o abyss_db_csv-db-csv.o `test -f 'db-csv.cc' || 
echo './'`db-csv.cc
 db-csv.cc: In function 'bool existFile(const char*)':
 db-csv.cc:23:9: error: cannot convert 'std::ifstream {aka 
std::basic_ifstream}' to 'bool' in return
   return file;
  ^~~~

The full buildlog is attached.

Kind Regards,

Bas
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: Unmet build dependencies: libboost-graph-dev 
libsparsehash-dev libtext-multimarkdown-perl libgtest-dev
W: Unmet build-dependency in source
dpkg-buildpackage: source package abyss
dpkg-buildpackage: source version 1.9.0-2
dpkg-buildpackage: source distribution UNRELEASED
dpkg-buildpackage: source changed by Andreas Tille 
 dpkg-source --before-build abyss-1.9.0
 fakeroot debian/rules clean
dh  clean --with autoreconf
   dh_testdir
   dh_auto_clean
   dh_autoreconf_clean
   dh_clean
 dpkg-source -b abyss-1.9.0
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building abyss using existing ./abyss_1.9.0.orig.tar.gz
dpkg-source: info: building abyss in abyss_1.9.0-2.debian.tar.xz
dpkg-source: info: building abyss in abyss_1.9.0-2.dsc
 dpkg-genchanges -S >../abyss_1.9.0-2_source.changes
dpkg-genchanges: not including original source code in upload
 dpkg-source --after-build abyss-1.9.0
dpkg-buildpackage: binary and diff upload (original source NOT included)
 -> Copying COW directory
  forking: rm -rf /var/cache/pbuilder/build/cow.12652 
  forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow 
/var/cache/pbuilder/build/cow.12652 
I: removed stale ilistfile /var/cache/pbuilder/build/cow.12652/.ilist
  forking: chroot /var/cache/pbuilder/build/cow.12652 cowdancer-ilistcreate 
/.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ' 
 -> Invoking pbuilder
  forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.12652 --buildresult /var/cache/pbuilder/result/ 
--debbuildopts  --no-targz --internal-chrootexec chroot 
/var/cache/pbuilder/build/cow.12652 cow-shell 
/home/bas/tmp/debian/abyss_1.9.0-2.dsc 
I: Running in no-targz mode
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Wed Sep  7 20:43:54 CEST 2016
I: pbuilder-time-stamp: 1473273834
I: copying local configuration
I: mounting /proc filesystem
I: mounting /sys filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
W: no hooks of type H found -- ignoring
I: Obtaining the cached apt archive contents
I: Installing the build-deps
W: no hooks of type D found -- ignoring
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), dh-autoreconf, libboost-graph-dev, libopenmpi-dev, 
libsparsehash-dev, libtext-multimarkdown-perl, libgtest-dev, libsqlite3-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 13373 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on debhelper (>= 9); however:
  Package debhelper is not installed.
 pbuilder-satisfydepends-dummy depends on dh-autoreconf; however:
  Package dh-autoreconf is not installed.
 pbuilder-satisfydepends-dummy depends on libboost-graph-dev; however:
  Package libboost-graph-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libopenmpi-dev; however:
  Package libopenmpi-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libsparsehash-dev; however:
  Package libsparsehash-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libtext-multimarkdown-perl; however:

Processed: abyss: FTBFS (error: cannot convert 'std::ifstream {aka std::basic_ifstream}' to 'bool' in return)

[Debian Bug Tracking System]

Processing control commands:

> block 836917 by -1
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 837012 811907 831164 817690 835680 825934 812036 837055 
811651 837058
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 837059

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

Processed: p4est: FTBFS due to test failures

[Debian Bug Tracking System]

Processing control commands:

> block 836917 by -1
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 837055 811907 817690 812036 811651 825934 835680 831164
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 837058

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

Processed: block 836917 with 837012

[Debian Bug Tracking System]

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

> block 836917 with 837012
Bug #836917 [release.debian.org] transition: openmpi
836917 was blocked by: 835680 837058 831164 825934 811651 811907 812036 817690 
837055
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 837012
> thanks
Stopping processing here.

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

Processed: Re: Bug#835098: gcr: FTBFS: Missing build-depends on gnupg

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #835098 [src:gcr] gcr: FTBFS: Missing build-depends on gnupg
Added tag(s) pending.

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

Bug#835098: gcr: FTBFS: Missing build-depends on gnupg

[Michael Biebl]

Control: tags -1 + pending

Am 22.08.2016 um 18:23 schrieb Michael Biebl:
> Am 22.08.2016 um 15:04 schrieb Santiago Vila:
>>
>> To reproduce, please try to build the package on a chroot not having
>> gnupg installed (neither gnupg1 or gnupg).
>>
>> The attached patch (untested) might fix this bug.
> 
> It seems to be required to run the test-suite only.
> So it would make sense to mark the build depedency with 
> (requires a bump of dpkg-dev and debhelper as well).

I've added that particular change to SVN so it will be part of the next
upload.

The test-suite will still fail though.
The switch of /usr/bin/gnupg to gnupg 2.1 broke parts of the test suite,
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835737

-- 
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#836426: Caused by libgtk-3-0 3.21

[Michael Biebl]

Am 08.09.2016 um 03:23 schrieb Josh Triplett:

> It seems appropriate for an issue that causes window contents to fail to
> render, making gnome-boxes unusable with that version of GTK+.  

The emacs warnings don't look critical and are most likely something
which needs to be addressed in emacs.

As for gnome-boxes, can you reproduce the problem with 3.21.3 from
unstable? I just tested a local installation of debian 8.5 and that
worked fine. I don't have  windows ISO to test whether that is
reproducible with that setup.

I think it would be best if you file this issue upstream at the
gnome-boxes bug tracker
https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-boxes

-- 
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#837055: fftw: FTBFS due to bfnnconv.pl failing to execute m-ascii.pl (. removed from @INC in perl)

[Bas Couwenberg]

Source: fftw
Version: 2.1.5-4
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so
Control: block 836917 by -1

Dear Maintainer,

The upload of openmpi (2.0.1-3) has triggered an uncoordinated
transition (#836917). Unfortunately your package FTBFS due to the recent
change in perl:

 https://lists.debian.org/debian-devel-announce/2016/08/msg00013.html

The attached patch adds . back to @INC if it's not present, to fix the
bfnnconv.pl failure to execute m-ascii.pl.

Kind Regards,

Bas
diff -Nru fftw-2.1.5/debian/patches/perl-dot-in-INC.patch fftw-2.1.5/debian/patches/perl-dot-in-INC.patch
--- fftw-2.1.5/debian/patches/perl-dot-in-INC.patch	1970-01-01 01:00:00.0 +0100
+++ fftw-2.1.5/debian/patches/perl-dot-in-INC.patch	2016-09-08 13:11:40.0 +0200
@@ -0,0 +1,19 @@
+Description: Add . to @INC if removed for CVE-2016-1238.
+ bfnnconv.pl fails to execute m-ascii.pl otherwise.
+ See also: https://lists.debian.org/debian-devel-announce/2016/08/msg00013.html
+Author: Bas Couwenberg 
+
+--- a/FAQ/bfnnconv.pl
 b/FAQ/bfnnconv.pl
+@@ -21,6 +21,11 @@
+ # by the GPL.  However, I would appreciate it if you credited me if
+ # appropriate in any documents you format using BFNN.)
+ 
++# Add . to @INC if removed for CVE-2016-1238
++BEGIN {
++push @INC, "." if(!grep /^\.$/, @INC);
++}
++
+ @outputs=('ascii','info','html');
+ 
+ while ($ARGV[0] =~ m/^\-/) {
diff -Nru fftw-2.1.5/debian/patches/series fftw-2.1.5/debian/patches/series
--- fftw-2.1.5/debian/patches/series	2016-07-11 08:55:51.0 +0200
+++ fftw-2.1.5/debian/patches/series	2016-09-08 13:08:54.0 +0200
@@ -4,3 +4,4 @@
 05_ac_define_syntax.diff
 info-syntax
 fix-texi2html-perl522.patch
+perl-dot-in-INC.patch