Bug#782904: python-debian test failures with gnupg-2.1.3

[Stuart Prescott]

Control: tags -1 + patch

> The test suite failures reported in this bug still exist with gpgv 2.1.14-3
> from experimental.

The root of the problem is that the new gpgv spits out a lot more information 
on status-fd than it used to and the test suite is strict in not wanting to 
see extra fields (to make sure one of them is not something like BADSIG).

For reference, with gpgv 2.1.14-3 from experimental:

$ gpgv --status-fd 1 --keyring /usr/share/keyrings/debian-keyring.gpg 
../python-debian_0.1.28_source.changes
[GNUPG:] PROGRESS need_entropy X 30 120
[GNUPG:] PROGRESS need_entropy X 120 120
[ ... 8< ... snipped a further 108 lines of the PROGRESS ...  8< ... ]
[GNUPG:] NEWSIG
gpgv: Signature made Tue Jun 14 14:54:20 2016 UTC using RSA key ID 
[GNUPG:] KEY_CONSIDERED 90E2D2C1AD146A1B7EBB891DBBC17EBB1396F2F7 0
[GNUPG:] SIG_ID 9GygF08Hh2I/7oKF/hsxVULBUhU 2016-06-14 1465916060
[GNUPG:] KEY_CONSIDERED 90E2D2C1AD146A1B7EBB891DBBC17EBB1396F2F7 0
[GNUPG:] GOODSIG BBC17EBB1396F2F7 Stuart Prescott 
gpgv: Good signature from "Stuart Prescott "
gpgv: aka "Stuart Prescott "
gpgv: aka "Stuart Prescott "
[GNUPG:] VALIDSIG 90E2D2C1AD146A1B7EBB891DBBC17EBB1396F2F7 2016-06-14 
1465916060 0 4 0 1 8 01 90E2D2C1AD146A1B7EBB891DBBC17EBB1396F2F7

So gpgv now includes PROGRESS, NEWSIG and KEY_CONSIDERED output. None of these 
keys conveys any additional information with the GOODSIG and VALIDSIG keys 
remaining unchanged.

The attached patch just filters these three headers out from the gpgv output 
and calm is restored.

python-debian and gnupg maintainers -- any comments here?


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7>From 36a1bc85438ac8638b91155a79b5fedc5898320f Mon Sep 17 00:00:00 2001
From: Stuart Prescott 
Date: Sat, 6 Aug 2016 16:30:07 +1000
Subject: [PATCH 1/2] Filter unwanted gpgv headers in signature check

gnupg 2 includes extra informational headers on status-fd when checking
the signature using gpgv, which causes the test suite to fail. The new
headers aren't actually interesting for the final result so they can be
filtered from the results exposed to the caller.

(Closes: #782904)
---
 lib/debian/deb822.py | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/lib/debian/deb822.py b/lib/debian/deb822.py
index c1dcb17..cfb76c1 100644
--- a/lib/debian/deb822.py
+++ b/lib/debian/deb822.py
@@ -806,6 +806,13 @@ class GpgInfo(dict):
 else:
 value = l[s+1:].split(' ')
 
+# Skip headers in the gpgv output that are not interesting
+# note NEWSI is actually NEWSIG but the above parsing loses the 'G'
+# if no keyid is included in the message. See
+# /usr/share/doc/gnupg/DETAILS.gz
+if key in ('NEWSI', 'NEWSIG', 'KEY_CONSIDERED', 'PROGRESS'):
+continue
+
 n[key] = value
 return n 
 
-- 
2.1.4

Processed: Re: Bug#782904: python-debian test failures with gnupg-2.1.3

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #782904 [python-debian] python-debian test failures with gnupg-2.1.3
Added tag(s) patch.

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

Bug#831088: marked as done (urweb: FTBFS with GCC 6: memmem.c:77:17: error: this 'if' clause does not guard... [-Werror=misleading-indentation])

[Debian Bug Tracking System]

Your message dated Sat, 06 Aug 2016 04:39:27 +
with message-id 
and subject line Bug#831088: fixed in urweb 20160805+dfsg-1
has caused the Debian Bug report #831088,
regarding urweb: FTBFS with GCC 6: memmem.c:77:17: error: this 'if' clause does 
not guard... [-Werror=misleading-indentation]
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.)


-- 
831088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: urweb
Version: 20160515+dfsg-1
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):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../../include/urweb  -I./../../include/urweb -I/usr/include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wimplicit -Wall -Werror -Wno-deprecated-declarations 
> -pthread -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c 
> -o memmem.lo memmem.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../include/urweb 
> -I./../../include/urweb -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wimplicit -Wall -Werror -Wno-deprecated-declarations -pthread -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c memmem.c  -fPIC 
> -DPIC -o .libs/memmem.o
> memmem.c: In function 'memmem':
> memmem.c:77:17: error: this 'if' clause does not guard... 
> [-Werror=misleading-indentation]
>  if (*sp == *pp)
>  ^~
> memmem.c:81:25: note: ...this statement, but the latter is misleadingly 
> indented as if it is guarded by the 'if'
>  sp++;
>  ^~
> memmem.c:73:14: error: nonnull argument 'b1' compared to NULL 
> [-Werror=nonnull-compare]
>  if(!(b1 && b2 && len1 && len2))
>   ^~
> memmem.c:73:17: error: nonnull argument 'b2' compared to NULL 
> [-Werror=nonnull-compare]
>  if(!(b1 && b2 && len1 && len2))
>  ^~
> cc1: all warnings being treated as errors
> make[2]: *** [memmem.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/urweb_20160515+dfsg-1_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: urweb
Source-Version: 20160805+dfsg-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 05 Aug 2016 21:48:47 -0400
Source: urweb
Binary: urweb liburweb0 liburweb-cgi0 liburweb-fastcgi0 liburweb-http0 
liburweb-static0 urweb-doc urweb-mode
Architecture: source amd64 all
Version: 20160805+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Barenblat 
Changed-By: Benjamin Barenblat 
Description:
 liburweb-cgi0 - urweb CGI backend
 liburweb-fastcgi0 - urweb FastCGI backend
 liburweb-http0 - urweb standalone backend
 liburweb-static0 - urweb static backend
 liburweb0  - urweb runtime system
 urweb  - purely functional language for web programming
 urweb-do

Bug#811622: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Sat, 06 Aug 2016 04:20:06 +
with message-id 
and subject line Bug#811622: fixed in crtmpserver 1.0~dfsg-5.2
has caused the Debian Bug report #811622,
regarding FTBFS with GCC 6: cannot convert x to y
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.)


-- 
811622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: crtmpserver
Version: 1.0~dfsg-5.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [ 25%] Building CXX object 
> thelib/CMakeFiles/thelib.dir/src/protocols/rtmp/basertmpprotocol.cpp.o
> cd "/<>/obj-x86_64-linux-gnu/thelib" && /usr/bin/c++   
> -DCreateRTCPPacket=CreateRTCPPacket_mystyle_only_once 
> -DFeedDataAudioMPEG4Generic=FeedDataAudioMPEG4Generic_one_by_one -DHAS_LUA 
> -DHAS_MEDIA_FLV -DHAS_MEDIA_MP3 -DHAS_MEDIA_MP4 -DHAS_PROTOCOL_CLI 
> -DHAS_PROTOCOL_HLS -DHAS_PROTOCOL_HTTP -DHAS_PROTOCOL_LIVEFLV 
> -DHAS_PROTOCOL_RTMP -DHAS_PROTOCOL_RTP -DHAS_PROTOCOL_TS -DHAS_PROTOCOL_VAR 
> -DHandleTSVideoData=HandleVideoData_version3 -DLINUX 
> -DLITTLE_ENDIAN_BYTE_ALIGNED -DNET_EPOLL -D_FILE_OFFSET_BITS=64 
> -D__USE_FILE_OFFSET64 -Dthelib_EXPORTS -I/usr/include/lua5.1 
> -I"/<>/common/include" -I"/<>/thelib/include"  
> -Wdate-time -D_FORTIFY_SOURCE=2 -g  -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -fPIC -O3 -fno-strict-aliasing -fPIC   
> -I/<>/obj-x86_64-linux-gnu/precompiled.gch/Release.c++ -include 
> common -Winvalid-pch -o 
> CMakeFiles/thelib.dir/src/protocols/rtmp/basertmpprotocol.cpp.o -c 
> "/<>/thelib/src/p
> rotocols/rtmp/basertmpprotocol.cpp"
> In file included from 
> /<>/thelib/include/streaming/baseinfilestream.h:25:0,
>  from 
> /<>/thelib/include/protocols/rtmp/streaming/infilertmpstream.h:25,
>  from 
> /<>/thelib/src/protocols/rtmp/basertmpprotocol.cpp:31:
> /<>/thelib/include/mediaformats/mediaframe.h:40:17: warning: 
> invalid suffix on literal; C++11 requires a space between literal and string 
> macro [-Wliteral-suffix]
>return format("s: %"PRIx64"; l: %"PRIx64"; t: %hhu; dt: %.2f; kf: %hhu; 
> at: %.2f; bh: %hhu",
>  ^
> 
> /<>/thelib/include/mediaformats/mediaframe.h:40:29: warning: 
> invalid suffix on literal; C++11 requires a space between literal and string 
> macro [-Wliteral-suffix]
>return format("s: %"PRIx64"; l: %"PRIx64"; t: %hhu; dt: %.2f; kf: %hhu; 
> at: %.2f; bh: %hhu",
>  ^
> 
> /<>/thelib/src/protocols/rtmp/basertmpprotocol.cpp:225:9: 
> warning: invalid suffix on literal; C++11 requires a space between literal 
> and string macro [-Wliteral-suffix]
>FATAL("Invalid channel id in reset message: %"PRIu32, channelId);
>  ^
> 
> /<>/thelib/src/protocols/rtmp/basertmpprotocol.cpp:467:9: 
> warning: invalid suffix on literal; C++11 requires a space between literal 
> and string macro [-Wliteral-suffix]
>FATAL("Try to play a stream over a non neutral stream: id: %u; type: 
> %"PRIu64,
>  ^
> 
> /<>/thelib/src/protocols/rtmp/basertmpprotocol.cpp:722:13: 
> warning: invalid suffix on literal; C++11 requires a space between literal 
> and string macro [-Wliteral-suffix]
>FATAL("The server doesn't support stream ids bigger than %"PRIu32,
>  ^
> 
> /<>/thelib/src/protocols/rtmp/basertmpprotocol.cpp:754:13: 
> warning: invalid suffix on literal; C++11 requires a space between literal 
> and string macro [-Wliteral-suffix]
>FATAL("The server doesn't support stream ids bigger than %"PRIu32,
>  ^
> 
> /<>/thelib/src/protocols/rtmp/basertmpprotocol.cpp: In member 
> function 'BaseStream* BaseRTMPProtocol::GetRTMPStream(uint32_t)':
> /<>/thelib/src/protocols/rtmp/basertmpprotocol.cpp:345:10: 
> error: cannot convert 'bool' to 'BaseStream*' in return
>return false;
>   ^
> 
> thelib/CMakeFiles/thelib.dir/build.make:1025: recipe for target 
> 'thelib/CMakeFiles/thelib.dir/src/protocols/rtmp/basertmpprotocol.cpp.o' 
> failed
> make[3]: *** 
> [thelib/CMakeFiles/thelib.dir/src/protocols/rtmp/basertmpprotocol.cpp.o] 
> Error 1
> make[3]: Leaving director

Processed: Re: Bug#782904: python-debian test failures with gnupg-2.1.3

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #782904 [python-debian] python-debian test failures with gnupg-2.1.3
Severity set to 'serious' from 'normal'

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

Bug#810526: marked as done (php5-pimple: fails to install: php5-pimple.postinst: php5enmod: not found)

[Debian Bug Tracking System]

Your message dated Sat, 06 Aug 2016 13:26:42 +1000
with message-id <1713398.yne3dS08z6@deblab>
and subject line Done: php5-pimple: fails to install: php5-pimple.postinst: 
php5enmod: not found
has caused the Debian Bug report #810526,
regarding php5-pimple: fails to install: php5-pimple.postinst: php5enmod: 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.)


-- 
810526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-pimple
Version: 3.0.2-1
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 php5-pimple.
  (Reading database ... 
(Reading database ... 7562 files and directories currently installed.)
  Preparing to unpack .../php5-pimple_3.0.2-1_amd64.deb ...
  Unpacking php5-pimple (3.0.2-1) ...
  Setting up php5-pimple (3.0.2-1) ...
  /var/lib/dpkg/info/php5-pimple.postinst: 11: 
/var/lib/dpkg/info/php5-pimple.postinst: php5enmod: not found
  dpkg: error processing package php5-pimple (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   php5-pimple


cheers,

Andreas


php5-pimple_3.0.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Package: php-pimple
Version: 3.0.2-2

"php5-pimple" is not provided any more.
3.0.2-2 no longer builds PHP-7 incompatible C extension.

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

-- 
Cheers,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

Good luck happens when preparedness meets opportunity.



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

Bug#806045: heimdal: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Brian May]

Santiago Vila  writes:

> Hope this helps.

Hopefully the fix I just applied to git is correct and will solve this.

Not going to upload however, as I can't build due to some of the tests
failing (I think this is an unrelated issue).
-- 
Brian May 

Bug#833538: marked as done (ncbi-blast+: FTBFS on s390x and sparc64: run_with_lock crashes)

[Debian Bug Tracking System]

Your message dated Sat, 06 Aug 2016 01:21:56 +
with message-id 
and subject line Bug#833538: fixed in ncbi-blast+ 2.4.0-3
has caused the Debian Bug report #833538,
regarding ncbi-blast+: FTBFS on s390x and sparc64: run_with_lock crashes
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.)


-- 
833538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncbi-blast+
Version: 2.4.0-2
Severity: serious
Justification: fails to build from source

The s390x and sparc64 builds of BLAST+ 2.4.0 have been failing:

  make[2]: Entering directory '/.../ncbi-blast+-2.4.0/c++/BUILD/build/corelib'
  /.../ncbi-blast+-2.4.0/c++/src/build-system/Makefile.meta_l:260: recipe for 
target 'sources.usr.locked' failed
  make[2]: *** [sources.usr.locked] Segmentation fault
  make[2]: Leaving directory '/.../ncbi-blast+-2.4.0/c++/BUILD/build/corelib'

The problem turned out to be that the build system, as patched by
Debian, winds up linking an optional helper tool named run_with_lock
with -pie but not compiling it with -fPIE.  On most platforms, this
inconsistency results in a linker error, and the build system proceeds
to fall back on a shell script.  However, on these two architectures,
the linker nominally succeeds but produces an executable that
immediately segfaults.

It should be possible to address the problem by supplying hardened
CFLAGS and LDFLAGS to configure as {C,LD}FLAGS_FOR_BUILD respectively;
we will then also want to add run_with_lock to the blacklist in
override_dh_install-arch.  I'll take care of these changes when I get
a chance, but am looking at a busy weekend.
--- End Message ---
--- Begin Message ---
Source: ncbi-blast+
Source-Version: 2.4.0-3

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

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

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated ncbi-blast+ package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 05 Aug 2016 19:47:24 -0400
Source: ncbi-blast+
Binary: ncbi-blast+ ncbi-blast+-legacy
Architecture: source amd64 all
Version: 2.4.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Aaron M. Ucko 
Description:
 ncbi-blast+ - next generation suite of BLAST sequence search tools
 ncbi-blast+-legacy - NCBI Blast legacy call script
Closes: 833538 833539 833541
Changes:
 ncbi-blast+ (2.4.0-3) unstable; urgency=medium
 .
   * debian/rules:
 - Properly build (but don't install) run_with_lock. (Closes: #833538.)
 - Comment out nostrip check, which yielded a useless dbgsym package.
   * Reinstate and refresh the hurd_fixes patch, which mostly still applies.
 (Closes: #833539.)
   * Add a new support_x32 patch to avoid picking up wrong inline assembly.
 (Closes: #833541.)
Checksums-Sha1:
 98f9cf6113280fccfba6938d14f54c309f60ad6f 2226 ncbi-blast+_2.4.0-3.dsc
 3b9ee3fd18c8811f0d1223fd0c3ae48d28cc8639 28444 
ncbi-blast+_2.4.0-3.debian.tar.xz
 b5e3de08761a3658820221a9cd53455eb873cd5c 149066700 
ncbi-blast+-dbgsym_2.4.0-3_amd64.deb
 59cfa5b8bc5ffee2813b3b919e849f03daf87784 8812 
ncbi-blast+-legacy_2.4.0-3_all.deb
 9ef73e94184dba3d974fd94a3608c5120ad4a1e2 9114490 ncbi-blast+_2.4.0-3_amd64.deb
Checksums-Sha256:
 70c529548b513828734ddee5f5279b297638e97f3b8b3e25df9fe36a1e8cc3ba 2226 
ncbi-blast+_2.4.0-3.dsc
 944f52bcae0ca3184fd47697f5777b1bd7214791be12f695264dfe70948c6083 28444 
ncbi-blast+_2.4.0-3.debian.tar.xz
 26e7fee7590802f7587664fe0ec7da2d908dc5ce72357f3fff4856ed2499df1f 149066700 
ncbi-blast+-dbgsym_2.4.0-3_amd64.deb
 1205164bd82304a1f748f2b04518baa3bab9f070e95b70656938a1ad73fd7415 8812 
ncbi-blast+-legacy_2.4.0-3_all.deb
 3c2f9f583cde39fff995d1a1956b9a094ed20a5982a0b4e8d0798c4fd2996f5e 9114490 
ncbi-blast+_2.4.0-3_amd64.deb
Files:
 253071fef2f63f2533b36376f0a94fbb 2226 science optional ncbi-blast+_2.4.0-3.dsc
 a9eb2595e56eae0a7ed03fdfaca103d7 28444 science optional 
ncbi-blast+_2.4.0-3.debian.tar.xz
 ed45f11cefa4cf94b6f46d25bbeb7f38 149066700 debug extra 
ncbi-blast+-dbgsy

Processed: pinot: patch to fix FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags 812165 + patch
Bug #812165 [pinot] pinot: FTBFS with GCC 6: cannot convert
Added tag(s) patch.

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

Bug#812165: pinot: patch to fix FTBFS

[Olly Betts]

Control: tags 812165 + patch

While checking rdeps of xapian-core in preparation for the upcoming
transition to xapian-core 1.4.0, I hit the current FTBFS of pinot with
GCC6.  The attached patch fixes that FTBFS.

However, the resulting build segfaults when the pinot binary is run.
A brief investigation suggests it's some sort of symbol mangling issue
as this log entry appears:

$ more ~/.pinot/pinot.log
FilterFactory::loadFilters: /usr/lib/pinot/filters/libexternalfilter.so: 
undefined symbol: _Z16get_filter_typesRSt3setISsSt4lessISsESaISsEE

I'm not an active user of pinot, so didn't have a .pinot before trying
to fix this FTBFS.

Incidentally, I notice there's also a newer release of pinot: 1.08.  The
current watch file isn't showing this, I suspect due to google code
going read-only.

Cheers,
Olly
diff -Nru pinot-1.05/debian/changelog pinot-1.05/debian/changelog
--- pinot-1.05/debian/changelog	2015-09-07 17:59:39.0 +1200
+++ pinot-1.05/debian/changelog	2016-08-06 12:13:24.0 +1200
@@ -1,3 +1,11 @@
+pinot (1.05-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix to build with GCC6, new patch: fix-ftbfs-with-gcc6.patch
+(Closes: #812165)
+
+ -- Olly Betts   Sat, 06 Aug 2016 12:12:06 +1200
+
 pinot (1.05-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru pinot-1.05/debian/patches/fix-ftbfs-with-gcc6.patch pinot-1.05/debian/patches/fix-ftbfs-with-gcc6.patch
--- pinot-1.05/debian/patches/fix-ftbfs-with-gcc6.patch	1970-01-01 12:00:00.0 +1200
+++ pinot-1.05/debian/patches/fix-ftbfs-with-gcc6.patch	2016-08-06 12:02:50.0 +1200
@@ -0,0 +1,17 @@
+Description: Fix to build with GCC6
+Author: Olly Betts 
+Bug-Debian: https://bugs.debian.org/812165
+Forwarded: no
+Last-Update: 2016-08-06
+
+--- pinot-1.05.orig/IndexSearch/ModuleFactory.cpp
 pinot-1.05/IndexSearch/ModuleFactory.cpp
+@@ -132,7 +132,7 @@ IndexInterface *ModuleFactory::getLibrar
+ 		(typeIter->second.m_canIndex == false))
+ 	{
+ 		// We don't know about this type, or doesn't support indexes
+-		return false;
++		return NULL;
+ 	}
+ 
+ 	void *pHandle = typeIter->second.m_pHandle;
diff -Nru pinot-1.05/debian/patches/series pinot-1.05/debian/patches/series
--- pinot-1.05/debian/patches/series	2012-06-23 15:36:32.0 +1200
+++ pinot-1.05/debian/patches/series	2016-08-06 12:02:22.0 +1200
@@ -1 +1,2 @@
 boost1.48.patch
+fix-ftbfs-with-gcc6.patch


signature.asc
Description: PGP signature

Bug#831957: marked as done (adzapper: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 23:57:13 +
with message-id 
and subject line Bug#831957: fixed in adzapper 20090301.dfsg.2-1
has caused the Debian Bug report #831957,
regarding adzapper: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: 
binary build with no binary artifacts found; cannot distribute
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.)


-- 
831957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adzapper
Version: 20090301.dfsg.1-0.2
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> dh_testdir
> dh_testroot
> dh_clean -k
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs
> # Add here commands to install the package into debian/adzapper.
> install -m 755 scripts/squid_redirect debian/adzapper/usr/bin/adzapper
> install -m 755 debian/adzapper.wrapper debian/adzapper/usr/bin
> install -m 755 debian/adzapper2konq debian/adzapper/usr/bin
> install -m 755 debian/adzapper2ab debian/adzapper/usr/bin
> install -m 644 debian/adzapper.conf debian/adzapper/etc/
>  dpkg-genchanges --build=all >../adzapper_20090301.dfsg.1-0.2_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/adzapper_20090301.dfsg.1-0.2_unstable_archallonly.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: adzapper
Source-Version: 20090301.dfsg.2-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Aug 2016 00:27:06 +0200
Source: adzapper
Binary: adzapper
Architecture: source
Version: 20090301.dfsg.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 adzapper   - proxy advertisement zapper add-on
Closes: 831957
Changes:
 adzapper (20090301.dfsg.2-1) unstable; urgency=medium
 .
   * QA upload.
   * Package is orphaned (Bug #722717). Set maintainer to "Debian QA Group".
   * Repackage source tarball again. Old tarball had modified files
 and a populated debian directory.
   * Package is "Arch: all". Move things from binary-arch to binary-indep.
 Package should now build with "dpkg-buildpackag

Bug#828653: Fix committed to Git

[Brian May]

Thomas Goirand  writes:

> I have sent a (one liner) fix to the Git. Can you please review it, and
> allow me to upload it (or upload it yourself)?

Please go ahead and upload.

Thanks
-- 
Brian May 

Bug#831813: marked as done (nullmailer leaks sensitive data through debconf)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 22:37:29 +
with message-id 
and subject line Bug#831813: fixed in nullmailer 1:1.13-1.2
has caused the Debian Bug report #831813,
regarding nullmailer leaks sensitive data through debconf
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.)


-- 
831813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nullmailer
Version: 1:1.13-1
Severity: grave

The nullmailer package keeps sensitive information like users and passwords to
the mail accounts on the remote SMTP servers in the '/etc/nullmailer/remotes'
file, which is secured by 600 permissions and owned by mail:mail. However,
after running command:

  dpkg-reconfigure -f noninteractive nullmailer

contents of this file are stored in the debconf database as cleartext in the
'nullmailer/relayhost' database key and can be read by any user using the
command:

  debconf-get-selections | grep nullmailer

The 'dpkg-reconfigure' command cannot be executed directly by unprivileged
users. However, the debconf database reads the contents of the
'/etc/nullmailer/remotes' file and includes its contents in the database on
package installation.

This behaviour occurs again on package reinstallation - the debconf database
is automatically updated with the contents of the '/etc/nullmailer/remotes'
file. Therefore the sensitive information might show up in the
'debconf-get-selections' output after an automatic package upgrade or package
reinstallation.

Regards,
Maciej


pgp53hDPWd09g.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: nullmailer
Source-Version: 1:1.13-1.2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 31 Jul 2016 20:57:13 +
Source: nullmailer
Binary: nullmailer
Architecture: source
Version: 1:1.13-1.2
Distribution: unstable
Urgency: medium
Maintainer: Nick Leverton 
Changed-By: Christian Hofstaedtler 
Description:
 nullmailer - simple relay-only mail transport agent
Closes: 831813
Changes:
 nullmailer (1:1.13-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Do not keep relayhost data in debconf database longer than
 strictly needed. (Closes: #831813)
Checksums-Sha1:
 1ec52cc832332074394e1b6fb5d73a966571166a 1804 nullmailer_1.13-1.2.dsc
 4a777ec343bb0745361ab9a527c111c22c8075bd 30760 
nullmailer_1.13-1.2.debian.tar.xz
Checksums-Sha256:
 7b3d9732f4f930242686059e97236c42cf2703332313241168cb6f80859df189 1804 
nullmailer_1.13-1.2.dsc
 48c15f5df55069a12a5318eab3a8ca7d50d34ca6769c153f436e359f9f16a1a1 30760 
nullmailer_1.13-1.2.debian.tar.xz
Files:
 07ffbbe682603e0098dfdc94ed94439d 1804 mail extra nullmailer_1.13-1.2.dsc
 57ba3876663778c19a4b572e31be64c9 30760 mail extra 
nullmailer_1.13-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXnmhPAAoJEFwT1tuTBS4DbKUQAKZVDXbSWeIvE90oqvYm2rHx
LzWMXVet2D0pIraSJ8lvnDLcwYjStzbngMVEIwsqCTeQ8uxe0CWSZ/bHmhGFFAf0
Yo77OLlPbeb6WWSvN6ak3EU4YzMQgtwWKL8phgJVvSe/2cQVxh1//t1gd0vijGy/
Q20xXFjXEb1uu7wJx23W7olNjWqqzhCkCOsQ6MfT2l68DED/wcSTvX+JWxti6761
hAZRI78AnkN68AuJhQTwXKFAmJ3B/a5CWzXa7b17wjysj9iVw5XmH++CppRnknyk
1XUKBqjNU37XUEwJYgSNesXvBXtLF6Uan59IN/bg+RY7GtmI3t16N/8oixHFBlNn
kJZjGAErzyFwwZH37LdzW4cQ0I02NtwNQiToh3JD0PCr1wCx5uC/N3gtWDIpM4QV
BxmTRAUl36sVQfPoglGxGh6oRZalZUrkfeiOnbLNK6cKVUh66Y1aHeHGT62kYu05
MGF6F7/ksx4DSc7a+BE14RtsCYBD8DJJbQUNjUXGsyLg4Kl+lNhAbhEbzKCevOq3
D9mu3yT5VyYstetou63Q7yChxynZlhtW2ZymRG9PW98jwF3Z2oI4mGB2oDQUccpB
79JN3Lu5QPQCRrtuanbVjSBcpvRidp+ZpDgM4J6k04/e7fiTbY6QVIRiKnRWaLSV
/FHJtqQu2wOWDYtmBRL4
=+I+Z
-END PGP SIGNATURE End Message ---

Bug#831151: marked as done (nanopolish: FTBFS with GCC 6: src/common/nanopolish_variant.cpp:27:79: error: no matching function for call to 'max(int, __gnu_cxx::__enable_if::__type)')

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 22:37:16 +
with message-id 
and subject line Bug#831151: fixed in nanopolish 0.4.0-2
has caused the Debian Bug report #831151,
regarding nanopolish: FTBFS with GCC 6: 
src/common/nanopolish_variant.cpp:27:79: error: no matching function for call 
to 'max(int, __gnu_cxx::__enable_if::__type)'
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.)


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

Hi,

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

Relevant part (hopefully):
> g++ -o src/common/nanopolish_variant.o -c -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -g -O3 -std=c++11 -fopenmp -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/hdf5/serial   -I./fast5 -I./src 
> -I./src/hmm -I./src/thirdparty -I./src/common -I./src/alignment -fPIC 
> src/common/nanopolish_variant.cpp
> src/common/nanopolish_variant.cpp: In function 'std::vector 
> extract_variants(const string&, const string&)':
> src/common/nanopolish_variant.cpp:27:79: error: no matching function for call 
> to 'max(int, __gnu_cxx::__enable_if::__type)'
>  par.band_width = std::max(20, abs(reference.size() - haplotype.size()) * 
> 2);
>   
>  ^
> In file included from /usr/include/c++/6/algorithm:61:0,
>  from src/common/nanopolish_variant.cpp:8:
> /usr/include/c++/6/bits/stl_algobase.h:219:5: note: candidate: template _Tp> const _Tp& std::max(const _Tp&, const _Tp&)
>  max(const _Tp& __a, const _Tp& __b)
>  ^~~
> /usr/include/c++/6/bits/stl_algobase.h:219:5: note:   template argument 
> deduction/substitution failed:
> src/common/nanopolish_variant.cpp:27:79: note:   deduced conflicting types 
> for parameter 'const _Tp' ('int' and '__gnu_cxx::__enable_if double>::__type {aka double}')
>  par.band_width = std::max(20, abs(reference.size() - haplotype.size()) * 
> 2);
>   
>  ^
> In file included from /usr/include/c++/6/algorithm:61:0,
>  from src/common/nanopolish_variant.cpp:8:
> /usr/include/c++/6/bits/stl_algobase.h:265:5: note: candidate: template _Tp, class _Compare> const _Tp& std::max(const _Tp&, const _Tp&, _Compare)
>  max(const _Tp& __a, const _Tp& __b, _Compare __comp)
>  ^~~
> /usr/include/c++/6/bits/stl_algobase.h:265:5: note:   template argument 
> deduction/substitution failed:
> src/common/nanopolish_variant.cpp:27:79: note:   deduced conflicting types 
> for parameter 'const _Tp' ('int' and '__gnu_cxx::__enable_if double>::__type {aka double}')
>  par.band_width = std::max(20, abs(reference.size() - haplotype.size()) * 
> 2);
>   
>  ^
> In file included from /usr/include/c++/6/algorithm:62:0,
>  from src/common/nanopolish_variant.cpp:8:
> /usr/include/c++/6/bits/stl_algo.h:3459:5: note: candidate: template _Tp> _Tp std::max(std::initializer_list<_Tp>)
>  max(initializer_list<_Tp> __l)
>  ^~~
> /usr/include/c++/6/bits/stl_algo.h:3459:5: note:   template argument 
> deduction/substitution failed:
> src/common/nanopolish_variant.cpp:27:79: note:   mismatched types 
> 'std::initializer_list<_Tp>' and 'int'
>  par.band_width = std::max(20, abs(reference.size() - haplotype.size()) * 
> 2);
>   
>  ^
> In file included from /usr/include/c++/6/algorithm:62:0,
>  from src/common/nanopolish_variant.cpp:8:
> /usr/include/c++/6/bits/stl_algo.h:3465:5: note: candidate: template _Tp, class _Compare> _Tp std::max(std::initializer_list<_Tp>, _Compare)
>  max(initializer_list<_Tp> __l, _Compare __comp)
>  ^~~
> /usr/include/c++/6/bits/stl_algo.h:3465:5: note:   template argument 
> deduction/substitution failed:
> src/common/nanopolish_variant.cpp:27:79: note:   mismatched types 
> 'std::initializer_list<_Tp>' and 'int'
>  par.band_width = std::

Bug#821656: Bumping severity of PHP 7.0 transition bugs to serious

[Petter Reinholdtsen]

Hi.

Any news on migrating shaarli to PHP7?  This package is used by the FreedomBox,
and it would be a shame to have to drop shaarli support because the package
did not make it into testing / Stretch.

-- 
Happy hacking
Petter Reinholdtsen

Bug#831529: libavcodec57: broken option parsing with LANGs with decimal mark different from .

[Mark Thompson]

This is now fixed with the same patch from Carl in ffmpeg master 

 and the 3.1 release branch 
.
  3.1.2 should be released soon.

Thank you for the report, and apologies for the breakage.

- Mark

PS:  It is probably worth noting that there may be other issues (though less 
fatal than this one) when lav* is used with a non-C locale, due to use of 
strtod() and related locale-dependent functions.  Making use of different 
properties of a non-C locale (such as a non-'.' decimal_point in LC_NUMERIC) 
should probably be considered an unsupported configuration with ffmpeg (the 
utility) at least, and there may be steps taken in future to make the behaviour 
more consistent.

Bug#812275: bitcoin: FTBFS with GCC 6: test suite failures

[Anthony Towns]

Source: bitcoin
Followup-For: Bug #812275

> This package fails to build with GCC 6.

FWIW, this bug seems to be fixed upstream somewhere between 0.12.1 and
0.13.0rc2. I ran a git bisect, and the commit that fixes the issue seems
to be:

https://github.com/bitcoin/bitcoin/commit/89f71c68c0fecf63059f6055ebdd25f1eba4c982

Cheers,
aj

Processed: Merge bugs

[Debian Bug Tracking System]

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

> forcemerge 833524 833542
Bug #833524 [chromium] chromium: Aw Snap! after update to new in sid / even 
when purged and installed as clean
Bug #833542 [chromium] chromium: Crashes all the time after last update
Severity set to 'normal' from 'grave'
Added tag(s) upstream.
Merged 833524 833542
> severity 833524 important
Bug #833524 [chromium] chromium: Aw Snap! after update to new in sid / even 
when purged and installed as clean
Bug #833542 [chromium] chromium: Crashes all the time after last update
Severity set to 'important' from 'normal'
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Bug#831922: libjs-swfupload: FTBFS with dpkg-buildpackage -A: dh_install: missing files, aborting

[Santiago Vila]

On Fri, Aug 05, 2016 at 10:43:43PM +0200, Christian Welzel wrote:
> Am 23.07.2016 um 12:26 schrieb Santiago Vila:
> 
> > The "build-indep" target is missing.
> 
> I prepared a new version of the package with new upstream.
> I cannot upload myself, so please take a look into
> https://mentors.debian.net/debian/pool/main/libj/libjs-swfupload/libjs-swfupload_2.2.0.1+ds2-1.dsc
> and upload for me, if all is good.

If this is a new upstream, why is this still 2.2.0.1?

Thanks.

Processed: tagging 831082

[Debian Bug Tracking System]

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

> tags 831082 + pending
Bug #831082 [src:clanlib] clanlib: FTBFS with GCC 6: 
IOData/Generic/datafile_inputprovider.h:147:48: error: no matching function for 
call to 'make_pair(int&, int&)'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#800767: marked as done (biomaj: depends on obsolete libcommons-net2-java library)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 20:56:49 +
with message-id 

and subject line Close bug #800767
has caused the Debian Bug report #800767,
regarding biomaj: depends on obsolete libcommons-net2-java library
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.)


-- 
800767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: biomaj
Severity: important
User: pkg-java-maintain...@lists.alioth.debian.org
Usertags: oldlibs libcommons-net2-java

Hi,

biomaj build-depends or depends on libcommons-net2-java, which is
obsolete and was replaced by libcommons-net-java (>= 3). biomaj
should be ported to the new version of libcommons-net-java, so that
we can remove the old, unmaintained one.

Please try to do this before the Stretch release as we are going to
try to remove libcommons-net2-java this cycle.

We will bump this issue to serious when the list of rdeps is small
and we are getting ready to remove libcommons-net2-java completely.

If you have any questions don't hesitate to ask.

Regards,

Markus
--- End Message ---
--- Begin Message ---
package biomaj
fixed in 1.2.3-7

Team upload fixed in 1.2.3-7, issue still opened, don't know why
--- End Message ---

Bug#831922: libjs-swfupload: FTBFS with dpkg-buildpackage -A: dh_install: missing files, aborting

[Christian Welzel]

Am 23.07.2016 um 12:26 schrieb Santiago Vila:


The "build-indep" target is missing.


I prepared a new version of the package with new upstream.
I cannot upload myself, so please take a look into
https://mentors.debian.net/debian/pool/main/libj/libjs-swfupload/libjs-swfupload_2.2.0.1+ds2-1.dsc
and upload for me, if all is good.


--
 MfG, Christian Welzel

  GPG-Key: pub 4096R/5117E119 2011-09-19
  Fingerprint: 3688 337C 0D3E 3725 94EC  E401 8D52 CDE9 5117 E119

Processed: Re: [Letsencrypt-devel] Bug#833494: acmetool: Does not correctly respond to changes in an ACME server's preferred agreement

[Debian Bug Tracking System]

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

> forwarded 833494 https://github.com/hlandau/acme/issues/191
Bug #833494 [acmetool] acmetool: Does not correctly respond to changes in an 
ACME server's preferred agreement
Set Bug forwarded-to-address to 'https://github.com/hlandau/acme/issues/191'.
>
End of message, stopping processing here.

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

Processed: Re: [Letsencrypt-devel] Bug#833494: acmetool: Does not correctly respond to changes in an ACME server's preferred agreement

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #833494 [acmetool] acmetool: Does not correctly respond to changes in an 
ACME server's preferred agreement
Severity set to 'serious' from 'important'
> tag -1 fixed-upstream
Bug #833494 [acmetool] acmetool: Does not correctly respond to changes in an 
ACME server's preferred agreement
Ignoring request to alter tags of bug #833494 to the same tags previously set

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

Bug#831110: marked as done (trinityrnaseq: FTBFS with GCC 6: ./aligns/KmerAlignCore.cc:6:34: fatal error: aligns/KmerAlignCore.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 19:52:28 +
with message-id 
and subject line Bug#831110: fixed in trinityrnaseq 2.2.0+dfsg-2
has caused the Debian Bug report #831110,
regarding trinityrnaseq: FTBFS with GCC 6: ./aligns/KmerAlignCore.cc:6:34: 
fatal error: aligns/KmerAlignCore.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.)


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

Hi,

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

Relevant part (hopefully):
> g++  -W -Wall -Wno-unused -Wno-deprecated -ansi -pedantic -Wno-long-long 
> -fno-nonansi-builtins -Wctor-dtor-privacy -Wsign-promo -Woverloaded-virtual 
> -Wendif-labels  -O3  -ggdb3 -DMAKE_DATE='"Mon May 23 18:46:45 UTC 2016"' 
> -DMAKE_OS_RELEASE='"3.16.0-4-amd64"' -DMAKE_RELEASE='"3.0"' -DNEW_MAKEFILE 
> -imacros system/BigFileDefines.h -pthread  -ftemplate-depth-30 
> -fno-strict-aliasing -mieee-fp   -fopenmp  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c ./aligns/KmerAlignCore.cc -o 
> obj/aligns/KmerAlignCore.o
> ./aligns/KmerAlignCore.cc:6:34: fatal error: aligns/KmerAlignCore.h: No such 
> file or directory
>  #include "aligns/KmerAlignCore.h"
>   ^
> compilation terminated.
> make[2]: *** [aligns/KmerAlignCore.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/trinityrnaseq_2.2.0+dfsg-1_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: trinityrnaseq
Source-Version: 2.2.0+dfsg-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 05 Aug 2016 19:21:49 +
Source: trinityrnaseq
Binary: trinityrnaseq trinityrnaseq-examples
Architecture: source amd64 all
Version: 2.2.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sascha Steinbiss 
Description:
 trinityrnaseq - RNA-Seq De novo Assembly
 trinityrnaseq-examples - RNA-Seq De novo Assembly common example and testing 
files
Closes: 831110
Changes:
 trinityrnaseq (2.2.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix build on GCC 6 (Closes: #831110)
Checksums-Sha1:
 6f8d69dbf5bc729648bb0a709f1830d3f6059cef 2274 trinityrnaseq_2.2.0+dfsg-2.dsc
 900570cb812d2eedda65d63d08c5a2ddd852af62 17148 
trinityrnaseq_2.2.0+dfsg-2.debian.tar.xz
 772a67a71cac7132d4cd77d804fb5dddfb020b1d 16373904 
trinityrnaseq-dbgsym_2.2.0+dfsg-2_amd64.deb
 9281e00cad49a6c670c5a0e60beff107f8fe6539 154106502 
trinityrnaseq-examples_2.2.0+dfsg-2_all.deb
 ae878f7d19c0dcf7de4b623ac3f0cd999d1baadf 1711330 
trinityrnaseq_2.2.0+dfsg-2_amd64.deb
Checksums-Sha256:
 90498e496dec8eef0a9736ab1fda0fcc617c9a3e807e7a4dcb87beef0b086d08 2274 
trinityrnaseq_2.2.0+dfsg-2.dsc
 a0e7affc1f0e2a44e44fd6c336732dff8da5d73de2fd7107da7b26e1032692d7 17148 
trinityrnaseq_2.2.0+dfsg-2.debian.tar.xz
 ddcf7c2ea797624a279afd6e07c84c3bdee1af40d783dc581427bfdae122c577 16373904 
trinityrnaseq-dbgsym_2.2.0+dfsg-2_amd64.deb
 5a501b415f2773d386366e903ccdab6fbb

Bug#833542: chromium: Crashes all the time after last update

[Salvo Tomaselli]

Package: chromium
Version: 52.0.2743.116-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
after the last update, I am getting the "aw snap!" page all
the time.

I see on the changelog that security fixes were made, but
at the moment it became rather unusable for me.

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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.20.0-1
ii  libavcodec57 7:3.1.1-4
ii  libavformat577:3.1.1-4
ii  libavutil55  7:3.1.1-4
ii  libc62.23-4
ii  libcairo21.14.6-1+b1
ii  libcups2 2.1.4-4
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.1.1-11
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-2
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk-3-0   3.20.7-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libjpeg62-turbo  1:1.5.0-1
ii  libnettle6   3.2-1
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.25-1
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpci3  1:3.3.1-1.1
ii  libpulse09.0-1.1
ii  libspeechd2  0.8.4-2
ii  libstdc++6   6.1.1-11
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.4+dfsg1-1+b1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-4
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
pn  fonts-liberation  

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#833538: ncbi-blast+: FTBFS on s390x and sparc64: run_with_lock crashes

[Aaron M. Ucko]

Source: ncbi-blast+
Version: 2.4.0-2
Severity: serious
Justification: fails to build from source

The s390x and sparc64 builds of BLAST+ 2.4.0 have been failing:

  make[2]: Entering directory '/.../ncbi-blast+-2.4.0/c++/BUILD/build/corelib'
  /.../ncbi-blast+-2.4.0/c++/src/build-system/Makefile.meta_l:260: recipe for 
target 'sources.usr.locked' failed
  make[2]: *** [sources.usr.locked] Segmentation fault
  make[2]: Leaving directory '/.../ncbi-blast+-2.4.0/c++/BUILD/build/corelib'

The problem turned out to be that the build system, as patched by
Debian, winds up linking an optional helper tool named run_with_lock
with -pie but not compiling it with -fPIE.  On most platforms, this
inconsistency results in a linker error, and the build system proceeds
to fall back on a shell script.  However, on these two architectures,
the linker nominally succeeds but produces an executable that
immediately segfaults.

It should be possible to address the problem by supplying hardened
CFLAGS and LDFLAGS to configure as {C,LD}FLAGS_FOR_BUILD respectively;
we will then also want to add run_with_lock to the blacklist in
override_dh_install-arch.  I'll take care of these changes when I get
a chance, but am looking at a busy weekend.

Bug#822003: marked as done (mrxvt: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 17:50:51 +
with message-id 
and subject line Bug#822003: fixed in mrxvt 0.5.4-2
has caused the Debian Bug report #822003,
regarding mrxvt: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
822003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mrxvt
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package mrxvt builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that mrxvt builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to mrxvt at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, mrxvt will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: mrxvt
Source-Version: 0.5.4-2

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

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

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated mrxvt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 05 Aug 2016 18:39:04 +0200
Source: mrxvt
Binary: mrxvt-common mrxvt mrxvt-mini mrxvt-cjk
Architecture: source
Version: 0.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 mrxvt  - lightweight multi-tabbed X terminal emulator - complete version
 mrxvt-cjk  - lightweight multi-tabbed X terminal emulator - CJK version
 mrxvt-common - lightweight multi-tabbed X terminal emulator - common files
 mrxvt-mini - lightweight multi-tabbed X terminal emulator - minimalistic versi
Closes: 664313 822003
Changes:
 mrxvt (0.5.4-2) unstable; urgency=medium
 .
   * QA upload.
   * Package is orphaned (Bug #698983). Set maintainer to "Debian QA Group".
   * Switch to "3.0 (quilt)" source format. Closes: #664313.
   * Add build-arch and build-indep targets. Closes: #822003.
   * Remove generated file "compile" in clean target.
   * Enable hardening by using dpkg-buildflags.
   * Drop unnecessary debian/rules stuff.
   * Raise debhelper compat level to 9.
   * Standards-Version: 3.9.8.
Checksums-Sha1:
 2964ad8e59a6bd1d856e7c3ab333fbff267584d2 1628 mrxvt_0.5.4-2.dsc
 b3fd9ddbb482fc5fa69cd0b5c759543570ddcea0 10764 mrxvt_0.5.4-2.debian.tar.xz
Checksums-Sha256:
 40ac3ccf56f632a33bbcef42bef77fb068df29c88dbd321bd31428d11e538741 1628 
mrxvt_0.5.4-2.dsc
 6e6c07c7e664f75b2940310ed26123f685037577afa7ca7b579f485de13317bb 10764 
mrxvt_0.5.4-2.debian.tar.xz
Files:
 fd9c9562aa0d5fc9b521fc7db7d0cf5d 1628 x11 optional mrxvt_0.5.4-2.dsc
 9958739af64c41fd135edc2f80ae0ac1 10764 x11 optional mrxvt_0.5.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXpME/AAoJEEHOfwufG4syrSYH/0hsLhV4CtPqHUOvrGLfeh+F
uh2yd+JXaXk2jL3ty/FnVaJlRFxeaffGUhpHg7A39rGDmp7y0Ahf2uiqnBi8ECVV
SXD7oLa3JV5znvslCAQrIVzyv3/0AtC+FpOLwGlDASjVxTGsZrW2nJbz0R37ClqO
nn7qnAUoPRJQcxvBZTdI0zH1ijTmpOhSOfJXMyyj0DdIQjMEMdV0MJ8EaNaD57oh
7WXUYmqRsHM4TLULsoJE/FXs9s7B8O93Z2UtD+OzS7oH4FGKUUhP5px4nL1qKKxm
ssiG2cWbWfsByC+mgtQvRBay2RVzQA74gUyD8F5Xzqj+QVY8z6cfcM2xZuVPPoU=
=gHMF
-END PGP SIGNATURE End Message ---

Bug#831184: mumble: FTBFS with GCC 6, seems Ice related

[Chris Knadle]

Jose Gutierrez de la Concha:
> On Thu, Aug 4, 2016 at 7:03 PM, Chris Knadle 
> wrote:

[...]
> Can you try to put /usr/lib/x86_64-linux-gnu/c++11 before
> /usr/lib/x86_64-linux-gnu
> otherwise linker will pick the C++98 libs

Mmm... okay that information helps.  Though... unfortunately this isn't
simple to do.

I don't know what's adding -L/usr/lib/x86_64-linux-gnu at the moment, as
this doesn't appear anywhere in the source package.  It's probably being
added by debhelper or qmake.  Either way it's going to take some
investigation to figure out what's doing it and to change what it's doing.

Thanks

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#802409: marked as done (nipype: FTBFS: ImportError: cannot import name mpl)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 16:43:53 +
with message-id 
and subject line Bug#802409: fixed in nipype 0.12.1+git4-gbc3a0b5-1
has caused the Debian Bug report #802409,
regarding nipype: FTBFS: ImportError: cannot import name mpl
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.)


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

Dear Maintainer,

The package fails to build:

SpaceTimeRealigner
Trim
Similarity
WARNING: Empty - nipype.interfaces.nitime
Traceback (most recent call last):
  File "../tools/build_interface_docs.py", line 54, in 
docwriter.write_api_docs(outdir)
  File "/nipype-0.11.0/tools/interfacedocgen.py", line 467, in write_api_docs
self.write_modules_api(modules,outdir)
  File "/nipype-0.11.0/tools/interfacedocgen.py", line 434, in write_modules_api
api_str = self.generate_api_doc(m)
  File "/nipype-0.11.0/tools/interfacedocgen.py", line 288, in generate_api_doc
__import__(uri)
  File "/nipype-0.11.0/nipype/interfaces/nitime/__init__.py", line 4, in 

from .analysis import (CoherenceAnalyzerInputSpec, 
CoherenceAnalyzerOutputSpec,
  File "/nipype-0.11.0/nipype/interfaces/nitime/analysis.py", line 31, in 

import nitime.viz as viz
  File "/usr/lib/python2.7/dist-packages/nitime/viz.py", line 19, in 
from matplotlib import mpl
ImportError: cannot import name mpl
Makefile:37: recipe for target 'api' failed
make[1]: *** [api] Error 1

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: nipype
Source-Version: 0.12.1+git4-gbc3a0b5-1

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated nipype 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, 04 Aug 2016 22:07:30 -0400
Source: nipype
Binary: python-nipype python-nipype-doc
Architecture: source all
Version: 0.12.1+git4-gbc3a0b5-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Description:
 python-nipype - Neuroimaging data analysis pipelines in Python
 python-nipype-doc - Neuroimaging data analysis pipelines in Python -- 
documentation
Closes: 802409
Changes:
 nipype (0.12.1+git4-gbc3a0b5-1) unstable; urgency=medium
 .
   * New upstream snapshot from 0.12.0-53-g356319b -- there were a number of
 fixes after release, without visible major new features introduced),
 thus snapshot was chosen
   * debian/control
 - python-{funcsigs,future,mock,prov,psutil} added to
   {Build-,}Depends/Recommends
 - boosted policy to 3.9.8
   * debian/patches
 - refreshed
 - deb_robust_apidocgen added to guarantee robust doc generations even
   externals puke on import for some reason (like nitime atm)
   (Closes: #802409)
   * debian/rules
 - adjusted to find installed nipype under any -packages
Checksums-Sha1:
 8df3df029feed1325128c9861a7d057fb8c7c1d4 2558 nipype_0.12.1+git4-gbc3a0b5-1.dsc
 26a5fd10dc00747c87a5f6a16578ef1aa4b3a844 3083319 
nipype_0.12.1+git4-gbc3a0b5.orig.tar.gz
 013a9705a98ffe922ea41fd13e5edbc85e4906e2 10856 
nipype_0.12.1+git4-gbc3a0b5-1.debian.tar.xz
 e37b2f153c5e1fd4ea2cd9c4ded43abe1647ac9d 12864792 
python-nipype-doc_0.12.1+git4-gbc3a0b5-1_all.deb
 4ca43baf3e229554c5f1d6b52cb690e21fc7bf6d 1525426 
python-nipype_0.12.1+git4-gbc3a0b5-1_all.deb
Checksums-Sha256:
 9b7499ef357989bfb2caf6399a2d6192a047eac990e38209f328a84a3fb65c20 2558 
nipype_0.12.1+git4-gbc3a0b5-1.dsc
 9028d425184a24df813002dbf237ab0ed2528b128adb92c8e5f9945b7e1651bc 3083319 

Bug#830441: marked as done (libkf5grantleetheme: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 16:37:22 +
with message-id 
and subject line Bug#830441: fixed in libkf5grantleetheme 16.04.3-1
has caused the Debian Bug report #830441,
regarding libkf5grantleetheme: FTBFS: dh_install: missing files, aborting
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.)


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/KF5GrantleeTheme/KF5GrantleeThemeConfig.cmake
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/KF5GrantleeTheme/KF5GrantleeThemeConfigVersion.cmake
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/KF5GrantleeTheme/KF5GrantleeThemeTargets.cmake
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/KF5GrantleeTheme/KF5GrantleeThemeTargets-debian.cmake
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/grantleetheme_version.h
> -- Installing: /«PKGBUILDDIR»/debian/tmp/etc/xdg/grantleetheme.categories
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5GrantleeTheme.so.5.2.2
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5GrantleeTheme.so.5
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5GrantleeTheme.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/GrantleeTheme/grantleethememanager.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/GrantleeTheme/grantleetheme.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/grantleetheme/grantleethememanager.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/grantleetheme/grantleetheme.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/grantleetheme/grantleetheme_export.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/grantleetheme/GrantleeThemeManager
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/grantleetheme/GrantleeTheme
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/mkspecs/modules/qt_GrantleeTheme.pri
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/grantlee/5.1/kde_grantlee_plugin.so
> make[2]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> dh_install  
> dh_install: Cannot find (any matches for) 
> "usr/lib/*/grantlee/5.0/kde_grantlee_plugin.so" (tried in "." and 
> "debian/tmp")
> dh_install: libkf5grantleetheme-plugins missing files: 
> usr/lib/*/grantlee/5.0/kde_grantlee_plugin.so
> dh_install: missing files, aborting
> make[1]: *** [pre_install_dh_install] Error 255

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/libkf5grantleetheme_16.04.2-1_unstable_reb.normal.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: libkf5grantleetheme
Source-Version: 16.04.3-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated libkf5grantleetheme 
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

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

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 16:23:35 +
with message-id 
and subject line Bug#806604: fixed in aubio 0.4.1-2.2
has caused the Debian Bug report #806604,
regarding aubio: FTBFS when built with dpkg-buildpackage -A (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.)


-- 
806604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aubio
Version: 0.4.1-2
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_testdir -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./waf --nocache configure --verbose --prefix=/usr --destdir=debian/tmp 
--enable-fftw3f
Setting top to   : /<> 
Setting out to   : /<>/build 
Checking for 'gcc' (c compiler)  : /usr/bin/gcc 
Checking for header stdlib.h : 16:36:18 runner ['/usr/bin/gcc', 
'-D_FORTIFY_SOURCE=2', '-g', '-O2', '-fstack-protector-strong', '-Wformat', 
'-Werror=format-security', '-g', '-Wall', '-Wextra', '-fPIC', '../test.c', 
'-c', '-o', 'test.c.1.o']
16:36:18 runner ['/usr/bin/gcc', '-Wl,-z,relro', 'test.c.1.o', '-o', 
'/<>/build/.conf_check_ecfddc2ce29c573b1079b107c2434884/testbuild/testprog',
 '-Wl,-Bstatic', '-Wl,-Bdynamic']
yes 

[... snipped ...]

yes 
Checking for program pkg-config  : /usr/bin/pkg-config 
Checking for 'fftw3f' >= 3.0.0   : 16:36:19 runner 
['/usr/bin/pkg-config', '--atleast-version=3.0.0', 'fftw3f']
16:36:19 runner ['/usr/bin/pkg-config', '--cflags', '--libs', 'fftw3f']
yes 
Checking for FFT implementation  : fftw3f 
Checking for 'sndfile' >= 1.0.4  : 16:36:19 runner 
['/usr/bin/pkg-config', '--atleast-version=1.0.4', 'sndfile']
16:36:19 runner ['/usr/bin/pkg-config', '--cflags', '--libs', 'sndfile']
yes 
Checking for 'samplerate' >= 0.0.15  : 16:36:19 runner 
['/usr/bin/pkg-config', '--atleast-version=0.0.15', 'samplerate']
16:36:19 runner ['/usr/bin/pkg-config', '--cflags', '--libs', 'samplerate']
yes 
Checking for 'jack'  : 16:36:19 runner 
['/usr/bin/pkg-config', '--cflags', '--libs', 'jack']
yes 
Checking for 'libavcodec' >= 54.35.0 : 16:36:19 runner 
['/usr/bin/pkg-config', '--atleast-version=54.35.0', 'libavcodec']
16:36:19 runner ['/usr/bin/pkg-config', '--cflags', '--libs', 'libavcodec']
yes 
Checking for 'libavformat' >= 52.3.0 : 16:36:19 runner 
['/usr/bin/pkg-config', '--atleast-version=52.3.0', 'libavformat']
16:36:19 runner ['/usr/bin/pkg-config', '--cflags', '--libs', 'libavformat']
yes 
Checking for 'libavutil' >= 52.3.0   : 16:36:19 runner 
['/usr/bin/pkg-config', '--atleast-version=52.3.0', 'libavutil']
16:36:19 runner ['/usr/bin/pkg-config', '--cflags', '--libs', 'libavutil']
yes 
Checking for 'libavresample' >= 1.0.1: 16:36:19 runner 
['/usr/bin/pkg-config', '--atleast-version=1.0.1', 'libavresample']
16:36:19 runner ['/usr/bin/pkg-config', '--cflags', '--libs', 'libavresample']
yes 
Checking for all libav libraries : yes 
Checking for program txt2man : /usr/bin/txt2man 
Checking for program doxygen : /usr/bin/doxygen 
'configure' finished successfully (0.492s)
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
ln -sf /usr/share/javascript/jquery/jquery.js doc/web/html/jquery.js
ln: failed to create symbolic link 'doc/web/html/jquery.js': No such file or 
directory
debian/rules:39: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/<>'
debian/rules:20: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once t

Processed: tagging 831591

[Debian Bug Tracking System]

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

> tags 831591 + moreinfo
Bug #831591 [ffmpeg] ffmpeg: kodi crash
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#833515: alter-sequence-alignment: FTBFS: failed to create task or type foreach

[Emmanuel Bourg]

Le 5/08/2016 à 16:14, Andreas Tille a écrit :

> since I do not have the slightest idea why the package which has built
> once does not build any more I'd like to forward this bug to ask for
> your kind help.

Hi Andreas,

This is a regression caused by my latest update to ant-contrib. Sorry
about that, I'll fix it.

Emmanuel Bourg

Bug#833515: alter-sequence-alignment: FTBFS: failed to create task or type foreach

[Andreas Tille]

Hi Java team,

since I do not have the slightest idea why the package which has built
once does not build any more I'd like to forward this bug to ask for
your kind help.

Kind regards

   Andreas.

On Fri, Aug 05, 2016 at 12:46:20PM +0200, Chris Lamb wrote:
> Source: alter-sequence-alignment
> Version: 1.3.3+dfsg-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,
> 
> alter-sequence-alignment fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to 
> provide /usr/bin/jstack (jstack) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript 
> to provide /usr/bin/jrunscript (jrunscript) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc to 
> provide /usr/bin/javadoc (javadoc) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to 
> provide /usr/bin/jhat (jhat) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to 
> provide /usr/bin/javap (javap) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to 
> provide /usr/bin/jar (jar) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to 
> provide /usr/bin/xjc (xjc) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen 
> to provide /usr/bin/schemagen (schemagen) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to 
> provide /usr/bin/jps (jps) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck 
> to provide /usr/bin/extcheck (extcheck) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to 
> provide /usr/bin/jmap (jmap) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstatd to 
> provide /usr/bin/jstatd (jstatd) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdb to 
> provide /usr/bin/jdb (jdb) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/serialver 
> to provide /usr/bin/serialver (serialver) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsgen to 
> provide /usr/bin/wsgen (wsgen) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jcmd to 
> provide /usr/bin/jcmd (jcmd) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jarsigner 
> to provide /usr/bin/jarsigner (jarsigner) in auto mode
>   Setting up openjdk-8-jre:amd64 (8u102-b14.1-1) ...
>   update-alternatives: using 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
> /usr/bin/policytool (policytool) in auto mode
>   Setting up ant (1.9.7-3) ...
>   Setting up javacc (5.0-5) ...
>   Setting up default-jre-headless (2:1.8-57) ...
>   Setting up default-jdk-headless (2:1.8-57) ...
>   Setting up openjdk-8-jdk:amd64 (8u102-b14.1-1) ...
>   update-alternatives: using 
> /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer to provide 
> /usr/bin/appletviewer (appletviewer) in auto mode
>   update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole 
> to provide /usr/bin/jconsole (jconsole) in auto mode
>   Setting up default-jre (2:1.8-57) ...
>   Setting up ant-contrib (1.0~b3+svn177-8) ...
>   Setting up default-jdk (2:1.8-57) ...
>   Setting up alter-sequence-alignment-build-deps (1.3.3+dfsg-1) ...
>   Processing triggers for libc-bin (2.23-4) ...
>   Processing triggers for systemd (231-1) ...
>   Processing triggers for ca-certificates (20160104) ...
>   Updating certificates in /etc/ssl/certs...
>   173 added, 0 removed; done.
>   Running hooks in /etc/ca-certificates/update.d...
>   
>   Adding debian:ACCVRAIZ1.pem
>   Adding debian:ACEDICOM_Root.pem
>   Adding debian:AC_Raíz_Certicámara_S.A..pem
>   Adding debian:Actalis_Authentication_Root_CA.pem
>   Adding debian:AddTrust_External_Root.pem
>   Adding debian:AddTrust_Low-Value_Services_Root.pem
>   Adding debian:AddTrust_Public_Services_Root.pem
>   Adding debian:AddTrust_Qualified_Certificates_Root.pem
>   Adding debian:AffirmTrust_Commercial.pem
>   Adding debian:AffirmTrust_Networking.pem
>   Adding debian:AffirmTrust_Premium.pem
>   Adding debian:AffirmTrust_Premium_ECC.pem
>   Adding debian:ApplicationCA_-_Japanese_Government.pem
>   Adding debian:Atos_TrustedRoot_2011.pem
>   Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
>   Adding debian:Baltimore_CyberTrust_Root.pem
>   Adding debian:Buypass_Class_2_CA_1.pem
>   Adding debian:Buypass_Class_2_Root_CA.pem
>   Adding debian:Buypass_Class_3_Root_CA.pem
>   Adding debian:CA_Disig.pem
>   Adding debian:CA_Disig_Root_R1.pem
>   Add

Processed: forcemerge

[Debian Bug Tracking System]

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

> forcemerge 814480 825242 825920
Bug #814480 [imagemagick] imagemagick: cannot upgrade: 
/usr/share/doc/imagemagick contains files not owned by package imagemagick:all
Bug #825242 [imagemagick] [imagemagick] Incorrect owner inside the package 
render imagemagick and imagemagick-6.q16 broken after upgrading to 
8:6.9.2.10+dfsg-2
Severity set to 'grave' from 'critical'
Added tag(s) pending.
Bug #825920 [imagemagick] errors upon install
Severity set to 'grave' from 'normal'
Added tag(s) pending.
Merged 814480 825242 825920
>
End of message, stopping processing here.

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

Bug#833530: gnome-packagekit: Missing Build-Depends on sp

[Chris Lamb]

Source: gnome-packagekit
Version: 3.18.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Tags: patch

Dear Maintainer,

gnome-packagekit fails to build from source in unstable/amd64 due to
missing Build-Depends on sp (for nsgmls):

  [..]

  /usr/share/docbook-utils/backends/man: 10: 
/usr/share/docbook-utils/backends/man: nsgmls: not 
found/usr/share/docbook-utils/backends/man: 10: 
/usr/share/docbook-utils/backends/man: 
  nsgmls: not found
  /usr/share/docbook-utils/backends/man: 10: 
/usr/share/docbook-utils/backends/man: nsgmls: not found
  /usr/share/docbook-utils/backends/man: 10: 
/usr/share/docbook-utils/backends/man: nsgmls: not found
   /bin/mkdir -p 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/debian/tmp/usr/share/man/man1'
   /usr/bin/install -c -m 644 ./gpk-application.1 ./gpk-log.1 ./gpk-prefs.1 
./gpk-update-viewer.1 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/debian/tmp/usr/share/man/man1'
  /usr/bin/install: cannot stat './gpk-application.1': No such file or directory
  /usr/bin/install: cannot stat './gpk-log.1': No such file or directory
  /usr/bin/install: cannot stat './gpk-prefs.1': No such file or directory
  /usr/bin/install: cannot stat './gpk-update-viewer.1': No such file or 
directory
  Makefile:389: recipe for target 'install-man1' failed
  make[4]: *** [install-man1] Error 1
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/man'
  Makefile:481: recipe for target 'install-am' failed
  make[3]: *** [install-am] Error 2
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/man'
  Makefile:481: recipe for target 'install-recursive' failed
  make[2]: *** [install-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0'
  dh_auto_install: make -j9 install 
DESTDIR=/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0/debian/tmp
 AM_UPDATE_INFO_DIR=no returned exit code 2
  debian/rules:17: recipe for target 'override_dh_auto_install' failed
  make[1]: *** [override_dh_auto_install] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160805144704.JVeIEKvLyU.gnome-packagekit/gnome-packagekit-3.18.0'
  debian/rules:11: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


gnome-packagekit.3.18.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: limit source to imagemagick, tagging 832783

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 832783 + pending
Bug #832783 [imagemagick] Fix an out of bound in generic decoder
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#833351: marked as done (python-tornado: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 13:50:36 +
with message-id 
and subject line Bug#833351: fixed in python-tornado 4.4.1-2
has caused the Debian Bug report #833351,
regarding python-tornado: accesses the internet during build
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.)


-- 
833351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tornado
Version: 4.4.1-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst python-tornado builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

00:00:21.707841 IP d29dd38a7d1e.9 > router.asus.com.domain: 40327+ A? 
docs.python.org. (33)
00:00:21.707887 IP d29dd38a7d1e.9 > router.asus.com.domain: 61201+ ? 
docs.python.org. (33)

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


python-tornado.4.4.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-tornado
Source-Version: 4.4.1-2

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

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

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-tornado package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 05 Aug 2016 15:20:50 +0200
Source: python-tornado
Binary: python-tornado python3-tornado python-tornado-doc
Architecture: source
Version: 4.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-tornado - scalable, non-blocking web server and tools
 python-tornado-doc - scalable, non-blocking web server and tools - 
documentation
 python3-tornado - scalable, non-blocking web server and tools - Python 3 
package
Closes: 833351
Changes:
 python-tornado (4.4.1-2) unstable; urgency=medium
 .
   * Prevent internet access during build (Closes: #833351)
 - Use local objects.inv for intersphinx mapping
 - Skip domain resolving tests
Checksums-Sha1:
 3d02a5d07edef63c788727329e70daa8f5a8b068 2838 python-tornado_4.4.1-2.dsc
 5204fff109d0398d55213e31125d58bb1e99fb26 9728 
python-tornado_4.4.1-2.debian.tar.xz
Checksums-Sha256:
 b4fe24ef1a3654d4128c7c937d18bb38ca3ec16796708acf67341c61673b6b69 2838 
python-tornado_4.4.1-2.dsc
 367b72a12543175ad7850f07980bdfdb5922114eecdf444a960887ffbc127e64 9728 
python-tornado_4.4.1-2.debian.tar.xz
Files:
 1437e3034015f609d25258cef297f8d9 2838 web optional python-tornado_4.4.1-2.dsc
 1297e9742974795f3d0fcee8bc030961 9728 web optional 
python-tornado_4.4.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXpJWmAAoJEDVzElWdHgZLofYP/1gENoWsinebfQg0Wz4JhkSn
NeQr082tgGm8/9NRB2riwr5Gx2YJ+pMKexTS0N640p0FTUHXcON5QWfT3TOq8UkS
gOKresnZSFgxkXZLgfQDW8MRSITc0V4Hg51RX/nRDkE8C9bm25rhq2Y1Jp5xVd3P
gP2a0WJYvrfNLrTJP1YmWxLwO+cOaj+uXsvUtfv8KCTOiDJqgPnUw1wzDoMOPk7S
hYQCIr0mDRHvgOx5RH4xA2cwBCfhc1E5U9zqJ8xbg0aWlVFdx2OJU5dxU5bTEQfd
6M7dUQ6Y8jt/BHno2BiJ0Li+E/4K5HscE6ZSYT9kNBNwhmizJvwU5IqnffPtvqSq
Lwpr+EWRDjnySd46JSkN81chr/4Mfjycs6Gp+v9jy9psqvENKw0CirpLdGcCX5dl
bILyuVp+/oa4Z53oWR6g2kkYtRE2lYeWwjEQq2HReJPD+b02Gdg+SFh/lWWJZk0J
WxoHk1xA+T70uEjw+PW9FTBmp5fTZgNniQPgS6w3UdH7VIwpBTtAp87wqlQfSwRr
wV2WHukWmwO//2fPMSWSTU7E0H0sB90lMQbRGPEFP4nUz9sfCpkmZniEgmzQf7Bn
HhCb/ZYY+ZDIqAym9tlr/i1MsmzxZvedh6rRRb5RJj18YYuZenDmzVznjXoXU6Fu
KotvKqIEHgjagq9aP0Lj
=mGv8
-END PGP SIGNATURE End Message ---

Bug#830902: openBVE doesn't start

[Florin Iucha]

I am observing the same behavior. I am running Debian "Stretch".

Bug#833465: [pkg-gnupg-maint] Help with libgpgme-related package

[Daniel Kahn Gillmor]

On Thu 2016-08-04 18:40:52 -0400, Santiago Vila wrote:

> I finally did this:
>
> https://anonscm.debian.org/cgit/collab-maint/fwknop.git/commit/?id=b9d788bb5e58613e1c1400a684041d493b043510
> https://anonscm.debian.org/cgit/collab-maint/fwknop.git/commit/?id=48d2be65049e1fd03b0ea41a9e668edf2ca766c7
>
> because this is just a workaround.
>
> If time allows, will try to contact upstream about this oddity.

fwiw, fwknop actually only uses this value by passing it to
gpgme_set_engine_info() if the user hasn't explicitly asked for a
non-default value:

 https://sources.debian.net/src/fwknop/2.6.0-4/lib/gpgme_funcs.c/?hl=67#L63

But gpgme clearly automatically selects the preferred value if it is
passed NULL here:

 https://sources.debian.net/src/gpgme1.0/1.6.0-3/src/engine.c/?hl=368#L351

So the right upstream fix would be to strip out any hardcoded defaults
in fwknop, remove the configure.ac variable, and pass NULL to
gpgme_set_version_info() unless the user explicitly specifies otherwise.

hth,

--dkg


signature.asc
Description: PGP signature

Bug#833528: multipath-tools: Multipathd reports failed paths as active, but with increased error count.

[Panos Gotsis]

Package: multipath-tools
Version: 0.5.0-6+deb8u2
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

We have our nodes installed with the latest patched jessie. The OS version 
comes with
multipath-tools-0.5.0-6+deb8u2. The system uses iscsi to connect to a SAN 
storage (Netapp).

The multipathd daemon starts properly and assembles the multipath devices for 
the iscsi LUNs.
However, when testing how it handles failures, we are seeing that for LUNs that 
we have set
offline or delete completely on our storage system, the output of multipath -l 
or, even
better, dmsetup status, is not showing these paths as failed, but as active, 
and it only
increments the fail_count counter.

This is an example output from one of our systems, where one out of the three 
LUNs has
been disabled through the storage management.


# dmsetup status --target multipath
3600a0980383036522d5d48687465724c: 0 10485760 multipath 2 0 0 0 1 1 A 0 2 0 
8:32 A 0 8:80 A 0 
3600a0980383036522d5d48687465724a: 0 10485760 multipath 2 0 0 0 1 1 A 0 2 0 
8:16 A 1 8:64 A 1 
3600a0980383036522d5d486874657252: 0 10485760 multipath 2 0 0 0 1 1 A 0 2 0 
8:48 A 0 8:96 A 0 

The device with dm name 3600a0980383036522d5d48687465724a should be reported as 
failed. Running
the multipath daemon in forground mode and with increased verbosity, we are 
seeing the following
messages.

Aug 04 17:35:46 | sdg: get_state
Aug 04 17:35:46 | 8:96: tur checker starting up
Aug 04 17:35:46 | 8:96: tur checker finished, state down
Aug 04 17:35:46 | sdg: state = down
Aug 04 17:35:46 | sdg: checker msg is "tur checker reports path is down"
Aug 04 17:35:46 | 3600a0980383036522d5d48687465724a: disassemble map [1 
retain_attached_hw_handler 0 1 1 round-robin 0 2 1 8:16 1 8:64 1 ]
Aug 04 17:35:46 | 3600a0980383036522d5d48687465724a: disassemble status [2 0 0 
0 1 1 A 0 2 0 8:16 A 1 8:64 A 1 ]
Aug 04 17:35:46 | 3600a0980383036522d5d48687465724a: sdg - tur checker reports 
path is down
Aug 04 17:35:46 | sdg: mask = 0x8
Aug 04 17:35:46 | sdg: path state = running

It seems weird that the path state is set as running, when the tur checker 
marks the path as down.
Maybe I am missing the semantics of these messages, but in any case the output 
of the dmsetup status
is wrong.

We got the sources from stretch and built package version 0.6.1-3 for jessie. 
After installing the
packages and rebooting, we run the same test. We got the following output.


# dmsetup status --target multipath
3600a0980383036522d5d48687465724c: 0 10485760 multipath 2 0 1 0 1 1 A 0 2 0 
8:32 A 0 8:80 A 0 
3600a0980383036522d5d48687465724a: 0 10485760 multipath 2 0 1 0 1 1 E 0 2 0 
8:16 F 1 8:64 F 1 
3600a0980383036522d5d486874657252: 0 10485760 multipath 2 0 1 0 1 1 A 0 2 0 
8:48 A 0 8:96 A 0 

Which is what we would expect.

I am unsure whether the issue is apparent only on iscsi LUNs or if it is 
affecting FC LUNs as
well. For good measure, we tweaked the timeouts of the iscsi daemon to much 
lower values so
that the possibility of some queued command not being processed promptly is 
ruled out. With
the upgrade though, the output of the status command is as it should be.

We are unsure about which is the exact patch on multipath-tools that fixed it 
upstream.

The 0.6.1-3 package was built as is on jessie, without changes to the control 
file, as the
package dependencies are already covered. However, the -k command line option 
is not
working. This is not a major problem, as the commands get properly processed 
anyway, but we
are also unsure whether it has any bugs.


-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
user_friendly_names no
max_fds 8192
flush_on_last_del   yes
}
blacklist {
  devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
  devnode "^sda[0-9]*$"
  devnode "^hd[a-z][0-9]*"
  devnode "^cciss.c[0-9]d[0-9].*"
}
devices {
device {
vendor  "NETAPP"
product "LUN"
path_checkertur
path_grouping_policygroup_by_prio
path_selector   "round-robin 0"
features"1 queue_if_no_path"
prioontap
hardware_handler"0"
failbackimmediate
rr_weight   uniform
rr_min_io   128
getuid_callout  "/lib/udev/scsi_id -g -u -d /dev/%n"
}
}


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/40 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 multipath-tools depends on:
ii  initscripts 2.88dsf-59
ii  kpartx  0.5.0-6+deb8u2
ii  libaio1 0.3.110-1
ii  libc6   2.19-18+deb8u4
ii  libdevmapper

Bug#828646: django-countries: Fix for Django 1.10 FTBFS available in git

[Thomas Goirand]

Hi Michael,

I have committed in Git a quick fix for #828646. Can I upload it?

Cheers,

Thomas Goirand (zigo)

Processed: reassign 833517 to docbook-utils

[Debian Bug Tracking System]

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

> reassign 833517 docbook-utils 0.6.14-3.2
Bug #833517 [src:colorhug-client] colorhug-client: FTBFS: /usr/bin/install: 
cannot stat './colorhug-backlight.1': No such file or directory
Bug reassigned from package 'src:colorhug-client' to 'docbook-utils'.
No longer marked as found in versions colorhug-client/0.2.8-2.
Ignoring request to alter fixed versions of bug #833517 to the same values 
previously set
Bug #833517 [docbook-utils] colorhug-client: FTBFS: /usr/bin/install: cannot 
stat './colorhug-backlight.1': No such file or directory
Marked as found in versions docbook-utils/0.6.14-3.2.
> thanks
Stopping processing here.

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

Processed (with 3 errors): forcibly merging 833496 833517, affects 833496, severity of 833496 is serious

[Debian Bug Tracking System]

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

> forcemerge 833496 833517
Bug #833496 [docbook-utils] Prevents gbp from building after change to onsglms
Unable to merge bugs because:
package of #833517 is 'src:colorhug-client' not 'docbook-utils'
Failed to forcibly merge 833496: Did not alter merged bugs.

> affects 833496 colorhug-client
Failed to mark 833496 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/833496 -- Unable to lock 
/org/bugs.debian.org/spool/lock/833496 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> severity 833496 serious
Failed to set severity of Bug 833496 to serious: failed to get lock on 
/org/bugs.debian.org/spool/lock/833496 -- Unable to lock 
/org/bugs.debian.org/spool/lock/833496 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/833496 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Bug#833517: colorhug-client: FTBFS: /usr/bin/install: cannot stat './colorhug-backlight.1': No such file or directory

[Michal Čihař]

Hi

Dne 5.8.2016 v 13:42 Chris Lamb napsal(a):
> Source: colorhug-client
> Version: 0.2.8-2
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> colorhug-client fails to build from source in unstable/amd64:
> Regards,

Seems to be bug in docbook-utils (introduced in 0.6.14-3.2) package:

$ docbook2man man/colorhug-backlight.sgml
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on:
/home/nijel/work/debian/colorhug-client/man/colorhug-backlight.sgml
/usr/share/docbook-utils/backends/man: 10:
/usr/share/docbook-utils/backends/man: nsgmls: not found
Done.

This is already known as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833496

Also it doesn't properly report such error, what makes the build failure
cause less obvious. I've just reported that as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833522

-- 
Michal Čihař | http://cihar.com/ | https://weblate.org/



signature.asc
Description: OpenPGP digital signature

Bug#833517: colorhug-client: FTBFS: /usr/bin/install: cannot stat './colorhug-backlight.1': No such file or directory

[Chris Lamb]

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

Dear Maintainer,

colorhug-client fails to build from source in unstable/amd64:

  [..]

  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160805123718.gcspYbTKOm.colorhug-client/colorhug-client-0.2.8/src'
  make  check-am
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160805123718.gcspYbTKOm.colorhug-client/colorhug-client-0.2.8/src'
  make  ch-self-test
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160805123718.gcspYbTKOm.colorhug-client/colorhug-client-0.2.8/src'
  gcc -DHAVE_CONFIG_H -I. -I..  -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gusb-1 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libusb-1.0 -pthread -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gusb-1 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libusb-1.0 -pthread -I/usr/include/colord-1 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/colord-1/colorhug -I/usr/include/gusb-1 
-I/usr/include/libusb-1.0 -I/usr/include/colord-1 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/colord-1 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_REENTRANT -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DCD_DISABLE_DEPRECATED 
-DTESTDATADIR=\""../data/tests"\" -DG_LOG_DOMAIN=\"ChClient\" 
-DG_USB_API_IS_SUBJECT_TO_CHANGE -DLOCALEDIR=\""/usr/share/locale"\" 
-Wdate-time -D_FORTIFY_SOURCE=2 -DEGG_TEST  -Wall -Wcast-align 
-Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align 
-Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security 
-Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body 
-Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized 
-Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing 
-Winline -Wmissing-parameter-type -Woverride-init -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160805123718.gcspYbTKOm.colorhug-client/colorhug-client-0.2.8=.
 -fstack-protector-strong -Wformat -Werror=format-security -c -o 
ch_self_test-ch-self-test.o `test -f 'ch-self-test.c' || echo 
'./'`ch-self-test.c
  gcc -DHAVE_CONFIG_H -I. -I..  -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gusb-1 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libusb-1.0 -pthread -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gusb-1 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/in

Bug#811957: marked as done (ecere-sdk: FTBFS with GCC 6: error: expected)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 11:37:38 +
with message-id 
and subject line Bug#811957: fixed in ecere-sdk 0.44.15-1
has caused the Debian Bug report #811957,
regarding ecere-sdk: FTBFS with GCC 6: error: expected
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.)


-- 
811957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ecere-sdk
Version: 0.44.14-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

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

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> Building 2nd stage ecere...
> make[2]: Entering directory '/<>/ecere'
> obj/release.linux/Archive.c:327:93: error: expected ')' before '__leaf__'
>   extern unsigned int gnu_dev_major(unsigned long long int __dev) 
> __attribute__((__nothrow__ __leaf__)) __attribute__((__const__));
>   
>^~~~
> 
> obj/release.linux/Archive.c:327:102: error: expected ',' or ';' before ')' 
> token
>   extern unsigned int gnu_dev_major(unsigned long long int __dev) 
> __attribute__((__nothrow__ __leaf__)) __attribute__((__const__));
>   
> ^
> 
> obj/release.linux/Archive.c:329:93: error: expected ')' before '__leaf__'
>   extern unsigned int gnu_dev_minor(unsigned long long int __dev) 
> __attribute__((__nothrow__ __leaf__)) __attribute__((__const__));
>   
>^~~~
> 
> obj/release.linux/Archive.c:329:102: error: expected ',' or ';' before ')' 
> token
>   extern unsigned int gnu_dev_minor(unsigned long long int __dev) 
> __attribute__((__nothrow__ __leaf__)) __attribute__((__const__));
>   
> ^
> 
> obj/release.linux/Archive.c:331:119: error: expected ')' before '__leaf__'
>   extern unsigned long long int gnu_dev_makedev(unsigned int __major, 
> unsigned int __minor) __attribute__((__nothrow__ __leaf__)) 
> __attribute__((__const__));
>   
>  ^~~~
> 
> obj/release.linux/Archive.c:331:128: error: expected ',' or ';' before ')' 
> token
>   extern unsigned long long int gnu_dev_makedev(unsigned int __major, 
> unsigned int __minor) __attribute__((__nothrow__ __leaf__)) 
> __attribute__((__const__));
>   
>   ^
> 
> Makefile:1440: recipe for target 'obj/release.linux/Archive.o' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: ecere-sdk
Source-Version: 0.44.15-1

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

Debian distribution maintenance software
pp.
Jerome St-Louis  (supplier of updated ecere-sdk 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, 4 Aug 2016 14:00:00 -0400
Source: ecere-sdk
Binary: ecere-sdk ecere-dev libecere0 libecerecom0 libecc0 libeda0 
libedasqlite0 libecereaudio0 ecere-samples ecere-extras
Architecture: source
Version: 0.44.15-1
Distribution: unstable
Urgency: low
Maintainer: Jerome St-Louis 
Changed-By: Jerome St-Louis 
Description:
 ecere-dev  - Ecere SDK Development Tools
 ecere-extras - Extras for the Ecere SDK

Bug#828653: Fix committed to Git

[Thomas Goirand]

Hi Brian,

I have sent a (one liner) fix to the Git. Can you please review it, and
allow me to upload it (or upload it yourself)?

Cheers,

Thomas Goirand (zigo)

Bug#830426: marked as done (kcalutils: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 10:58:14 +
with message-id 
and subject line Bug#830426: fixed in kcalutils 16.04.3-1
has caused the Debian Bug report #830426,
regarding kcalutils: FTBFS: dh_install: missing files, aborting
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.)


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/KF5CalendarUtils/KF5CalendarUtilsConfig.cmake
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/KF5CalendarUtils/KF5CalendarUtilsConfigVersion.cmake
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/KF5CalendarUtils/KF5CalendarUtilsTargets.cmake
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/KF5CalendarUtils/KF5CalendarUtilsTargets-debian.cmake
> -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/kcalutils_version.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5CalendarUtils.so.5.2.2
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5CalendarUtils.so.5
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5CalendarUtils.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/HTMLExportSettings
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/kcalutils_export.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/htmlexportsettings.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/dndfactory.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/htmlexport.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/icaldrag.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/incidenceformatter.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/recurrenceactions.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/scheduler.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/stringify.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/kcalutils/vcaldrag.h
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/KCalUtils/DndFactory
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/KCalUtils/HtmlExport
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/KCalUtils/ICalDrag
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/KCalUtils/IncidenceFormatter
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/KCalUtils/RecurrenceActions
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/KCalUtils/Scheduler
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/KCalUtils/Stringify
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/include/KF5/KCalUtils/KCalUtils/VCalDrag
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/mkspecs/modules/qt_KCalUtils.pri
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/grantlee/5.1/kcalendar_grantlee_plugin.so
> -- Set runtime path of 
> "/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/grantlee/5.1/kcalendar_grantlee_plugin.so"
>  to ""
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/share/kcalendar/templates/default/event.html
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/share/kcalendar/templates/default/freebusy.html
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/share/kcalendar/templates/default/incidence_header.html
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/share/kcalendar/templates/default/journal.html
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/share/kcalendar/templates/default/template_base.html
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/

Bug#828655: Can I upload the Django 1.10 fix for django-recurrence (see: #828655)

[Thomas Goirand]

Hi,

I have applied upstream fix available at:
https://github.com/django-recurrence/django-recurrence/commit/0d1bcfd107979a05f76eef93be806eedf017de5f

This is already pushed to the git of the DPMT. Can I upload what's in
the DPMT git now?

Cheers,

Thomas Goirand (zigo)

Bug#833515: alter-sequence-alignment: FTBFS: failed to create task or type foreach

[Chris Lamb]

Source: alter-sequence-alignment
Version: 1.3.3+dfsg-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,

alter-sequence-alignment fails to build from source in unstable/amd64:

  [..]

  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript 
to provide /usr/bin/jrunscript (jrunscript) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to 
provide /usr/bin/jhat (jhat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to 
provide /usr/bin/javap (javap) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to 
provide /usr/bin/jar (jar) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to 
provide /usr/bin/xjc (xjc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen to 
provide /usr/bin/schemagen (schemagen) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to 
provide /usr/bin/jps (jps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck to 
provide /usr/bin/extcheck (extcheck) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to 
provide /usr/bin/jmap (jmap) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstatd to 
provide /usr/bin/jstatd (jstatd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdb to 
provide /usr/bin/jdb (jdb) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/serialver to 
provide /usr/bin/serialver (serialver) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsgen to 
provide /usr/bin/wsgen (wsgen) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jcmd to 
provide /usr/bin/jcmd (jcmd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jarsigner to 
provide /usr/bin/jarsigner (jarsigner) in auto mode
  Setting up openjdk-8-jre:amd64 (8u102-b14.1-1) ...
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
/usr/bin/policytool (policytool) in auto mode
  Setting up ant (1.9.7-3) ...
  Setting up javacc (5.0-5) ...
  Setting up default-jre-headless (2:1.8-57) ...
  Setting up default-jdk-headless (2:1.8-57) ...
  Setting up openjdk-8-jdk:amd64 (8u102-b14.1-1) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer 
to provide /usr/bin/appletviewer (appletviewer) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to 
provide /usr/bin/jconsole (jconsole) in auto mode
  Setting up default-jre (2:1.8-57) ...
  Setting up ant-contrib (1.0~b3+svn177-8) ...
  Setting up default-jdk (2:1.8-57) ...
  Setting up alter-sequence-alignment-build-deps (1.3.3+dfsg-1) ...
  Processing triggers for libc-bin (2.23-4) ...
  Processing triggers for systemd (231-1) ...
  Processing triggers for ca-certificates (20160104) ...
  Updating certificates in /etc/ssl/certs...
  173 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  
  Adding debian:ACCVRAIZ1.pem
  Adding debian:ACEDICOM_Root.pem
  Adding debian:AC_Raíz_Certicámara_S.A..pem
  Adding debian:Actalis_Authentication_Root_CA.pem
  Adding debian:AddTrust_External_Root.pem
  Adding debian:AddTrust_Low-Value_Services_Root.pem
  Adding debian:AddTrust_Public_Services_Root.pem
  Adding debian:AddTrust_Qualified_Certificates_Root.pem
  Adding debian:AffirmTrust_Commercial.pem
  Adding debian:AffirmTrust_Networking.pem
  Adding debian:AffirmTrust_Premium.pem
  Adding debian:AffirmTrust_Premium_ECC.pem
  Adding debian:ApplicationCA_-_Japanese_Government.pem
  Adding debian:Atos_TrustedRoot_2011.pem
  Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
  Adding debian:Baltimore_CyberTrust_Root.pem
  Adding debian:Buypass_Class_2_CA_1.pem
  Adding debian:Buypass_Class_2_Root_CA.pem
  Adding debian:Buypass_Class_3_Root_CA.pem
  Adding debian:CA_Disig.pem
  Adding debian:CA_Disig_Root_R1.pem
  Adding debian:CA_Disig_Root_R2.pem
  Adding debian:CA_WoSign_ECC_Root.pem
  Adding debian:CFCA_EV_ROOT.pem
  Adding debian:CNNIC_ROOT.pem
  Adding debian:COMODO_Certification_Authority.pem
  Adding debian:COMODO_ECC_Certification_Authority.pem
  Adding debian:COMODO_RSA_Certification_Authority.pem
  Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
  Adding debian:Camerfirma_Global_Chambersign_Root.pem
  Adding debian:Certification_Authority_of_WoS

Bug#831184: mumble: FTBFS with GCC 6, seems Ice related

[Jose Gutierrez de la Concha]

On Thu, Aug 4, 2016 at 7:03 PM, Chris Knadle 
wrote:

>
>
> Jose Gutierrez de la Concha:
> > Hi,
> >
> > When building an Ice application with C++11/C++14 enabled you need to
> link
> > with libraries with ++11 suffix -lIce++11 instead of -lIce.
> >
> > libzeroc-ice3.6 provide C++98 libraries and C++11 libraries with ++11
> > suffix and the APIs are slightly different.
>
> I tried this (patch is attached), but this results in an error message
> that the linker is unable to find -lIce++11:
>
>
You are right, I was confused with our master branch (3.7) where we get rid
of c++11 subdir

> -
>
> g++ -c -include release/murmurd -m64 -pipe -g -O2
> -fdebug-prefix-map=/build/mumble-1.2.16/src/murmur=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wfatal-errors
> -fvisibility=hidden -g -std=c++11 -O2 -Wall -W -D_REENTRANT
> -DNO_UPDATE_CHECK -DPLUGIN_PATH=/usr/lib/mumble
> -DMUMBLE_VERSION=1.2.16-1 -DHAVE_LIMITS_H -DHAVE_ENDIAN_H
> -DRESTRICT=__restrict__ -D_FORTIFY_SOURCE=2
> -DMUMBLE_VERSION_STRING=1.2.16 -DMURMUR -DUSE_DBUS -DUSE_ICE
> -DUSE_BONJOUR -D_REENTRANT -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_XML_LIB
> -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml
> -I/usr/include/qt4/QtSql -I/usr/include/qt4 -I/usr/include/qt4/QtDBus
> -I../../src -I. -I/usr/include/speech-dispatcher -I../bonjour -Irelease
> -I/usr/include/avahi-compat-libdns_sd -o release/moc_BonjourServer.o
> release/moc_BonjourServer.cpp
>
> g++ -m64 -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -Wl,-O1 -o
> ../../release/murmurd release/ACL.o release/Group.o release/Channel.o
> release/Connection.o release/User.o release/Timer.o release/CryptState.o
> release/OSInfo.o release/Net.o release/SSL.o release/Version.o
> release/main.o release/Server.o release/ServerUser.o release/ServerDB.o
> release/Register.o release/Cert.o release/Messages.o release/Meta.o
> release/RPC.o release/UnixMurmur.o release/DBus.o release/MurmurIce.o
> release/BonjourServiceRegister.o release/BonjourServer.o
> release/Mumble.pb.o release/Murmur.o release/moc_ACL.o
> release/moc_Channel.o release/moc_Connection.o release/moc_Server.o
> release/moc_ServerUser.o release/moc_Meta.o release/moc_UnixMurmur.o
> release/moc_DBus.o release/moc_MurmurIce.o
> release/moc_BonjourServiceRegister.o release/moc_BonjourServer.o
> -L../../release -L/usr/lib/x86_64-linux-gnu -lprotobuf -lcap -lIce++11
> -lIceUtil -lQtDBus -lssl -lcrypto -ldns_sd -lavahi-common -lavahi-client
> -lpthread -lQtSql -lQtXml -lQtNetwork -lQtCore

/usr/bin/ld: cannot find -lIce++11
>
> collect2: error: ld returned 1 exit status
>
> Makefile.Release:183: recipe for target '../../release/murmurd' failed
>
> make[4]: *** [../../release/murmurd] Error 1
>
> -
>
> I had a quick look at the documentation for using Ice 3.6 concerning C++
> and at the moment it doesn't mention using -lIce++11:
>
>
> https://doc.zeroc.com/display/Ice36/Using+the+Linux+Binary+Distributions#
> UsingtheLinuxBinaryDistributions-C++
>
> instead it's suggested to use -L/usr/lib/c++11 for 32-bit and
> -L/usr/lib64/c++11 for 64-bit.  The Debian package seems to have this
> directory in /usr/lib/x86_64-linux-gnu/c++11.  I tried adding that but
> that doesn't seem to help (and I suspect this is redundant as
> -L/usr/lib/x86_64-linux-gnu is included):
>
> -
>
> g++ -c -include release/murmurd -m64 -pipe -g -O2
> -fdebug-prefix-map=/build/mumble-1.2.16/src/murmur=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wfatal-errors
> -fvisibility=hidden -g -std=c++11 -O2 -Wall -W -D_REENTRANT
> -DNO_UPDATE_CHECK -DPLUGIN_PATH=/usr/lib/mumble
> -DMUMBLE_VERSION=1.2.16-1 -DHAVE_LIMITS_H -DHAVE_ENDIAN_H
> -DRESTRICT=__restrict__ -D_FORTIFY_SOURCE=2
> -DMUMBLE_VERSION_STRING=1.2.16 -DMURMUR -DUSE_DBUS -DUSE_ICE
> -DUSE_BONJOUR -D_REENTRANT -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_XML_LIB
> -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml
> -I/usr/include/qt4/QtSql -I/usr/include/qt4 -I/usr/include/qt4/QtDBus
> -I../../src -I. -I/usr/include/speech-dispatcher -I../bonjour -Irelease
> -I/usr/include/avahi-compat-libdns_sd -o release/moc_BonjourServer.o
> release/moc_BonjourServer.cpp
>
> g++ -m64 -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -Wl,-O1 -o
> ../../release/murmurd release/ACL.o release/Group.o release/Channel.o
> release/Connection.o release/User.o release/Timer.o release/CryptState.o
> release/OSInfo.o release/Net.o release/SSL.o release/Version.o
> release/main.o release/Server.o release/ServerUser.o release/ServerDB.o
> release/Register.o release/Cert.o release/Messages.o release/Meta.o
> release/RPC.o release/UnixMu

Bug#833513: Core needs update to cope with PPX-style syntax extensions

[Stéphane Glondu]

Package: src:janest-core-kernel
Version: 113.00.00-3
Severity: serious

Hello,

(Jane Street's) Core packages need update to cope with PPX-style syntax
extensions. But to package the current version of Core, many new
packages are needed. Here is a list (redacted from what is installed by
"opam install core_kernel"):

>   - install re1.6.1 [required by 
> ppx_expect]
>   - install variantslib   113.33.03 [required by 
> core_kernel]
>   - install typerep   113.33.03 [required by 
> core_kernel]
>   - install sexplib   113.33.03 [required by 
> core_kernel]
>   - install ppx_core  113.33.03 [required by 
> ppx_bench, ppx_assert, ppx_expect]
>   - install fieldslib 113.33.03 [required by 
> core_kernel]
>   - install bin_prot  113.33.03 [required by 
> core_kernel]
>   - install ppx_deriving  4.0   [required by 
> ppx_type_conv]
>   - install ppx_optcomp   113.33.03 [required by 
> ppx_driver]
>   - install ppx_driver113.33.03 [required by 
> core_kernel]
>   - install ppx_type_conv 113.33.03 [required by 
> ppx_assert]
>   - install ppx_pipebang  113.33.03 [required by ppx_jane]
>   - install ppx_let   113.33.03 [required by ppx_jane]
>   - install ppx_inline_test   113.33.03 [required by 
> core_kernel]
>   - install ppx_here  113.33.03 [required by 
> ppx_assert, ppx_jane]
>   - install ppx_variants_conv 113.33.03 [required by 
> ppx_expect, ppx_jane]
>   - install ppx_typerep_conv  113.33.03 [required by ppx_jane]
>   - install ppx_sexp_conv 113.33.03 [required by 
> ppx_expect, ppx_assert, ppx_jane]
>   - install ppx_fields_conv   113.33.03 [required by 
> ppx_expect, ppx_jane]
>   - install ppx_enumerate 113.33.03 [required by ppx_jane]
>   - install ppx_compare   113.33.03 [required by 
> ppx_expect, ppx_assert, ppx_jane]
>   - install ppx_bin_prot  113.33.03 [required by ppx_jane]
>   - install ppx_bench 113.33.03 [required by 
> core_kernel]
>   - install ppx_fail  113.33.03 [required by ppx_jane]
>   - install ppx_sexp_value113.33.03 [required by ppx_jane]
>   - install ppx_sexp_message  113.33.03 [required by ppx_jane]
>   - install ppx_custom_printf 113.33.03 [required by 
> ppx_expect, ppx_jane]
>   - install ppx_assert113.33.03 [required by 
> core_kernel]
>   - install ppx_expect113.33.03 [required by 
> core_kernel]
>   - install ppx_jane  113.33.03 [required by 
> core_kernel]
>   - install core_kernel   113.33.03 

Some of these packages are already in unstable as part of my effort to
update ocaml-ipaddr. And versions 113.33.03 of variantslib, fieldslib
and sexplib (named sexplib310 in Debian) are already in experimental.

Uploading them to unstable will break the Core stack (starting with
janest-core-kernel) currently in unstable/testing and the Ocsigen stack.
I intend to do that as soon as everything needed for ocaml-ipaddr (and
the Ocsigen stack) is ready.

I am submitting this RC bug now to keep janest-core-kernel out of testing.


Cheers,

-- 
Stéphane

Bug#831138: marked as done (snap-aligner: FTBFS with GCC 6: tuple:851:29: error: expected primary-expression before '.' token)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 10:05:59 +
with message-id 
and subject line Bug#831138: fixed in snap-aligner 0.18~1.0~beta.18+dfsg1-4
has caused the Debian Bug report #831138,
regarding snap-aligner: FTBFS with GCC 6: tuple:851:29: error: expected 
primary-expression before '.' token
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.)


-- 
831138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snap-aligner
Version: 0.18~1.0~beta.18+dfsg1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

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

Relevant part (hopefully):
> g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -MMD 
> -ISNAPLib -Wdate-time -D_FORTIFY_SOURCE=2  -c -o SNAPLib/FASTQ.o 
> SNAPLib/FASTQ.cpp
> In file included from /usr/include/c++/6/bits/stl_map.h:63:0,
>  from /usr/include/c++/6/map:61,
>  from SNAPLib/Util.h:3,
>  from SNAPLib/VariableSizeVector.h:3,
>  from SNAPLib/VariableSizeMap.h:5,
>  from SNAPLib/DataReader.h:26,
>  from SNAPLib/Read.h:30,
>  from SNAPLib/FASTQ.h:31,
>  from SNAPLib/FASTQ.cpp:29:
> /usr/include/c++/6/tuple:851:29: error: expected primary-expression before 
> '.' token
>noexcept(noexcept(__in._M_swap(__in)))
>  ^
> /usr/include/c++/6/tuple: In constructor 'constexpr std::tuple< 
>  >::tuple(const std::tuple<_Args1 ...>&)':
> /usr/include/c++/6/tuple:671:76: error: expected primary-expression before 
> ')' token
>  : _Inherited(static_cast&>(__in))
> ^
> /usr/include/c++/6/tuple: In constructor 'constexpr std::tuple< 
>  >::tuple(const std::tuple<_Args1 ...>&)':
> /usr/include/c++/6/tuple:683:76: error: expected primary-expression before 
> ')' token
>  : _Inherited(static_cast&>(__in))
> ^
> /usr/include/c++/6/tuple: In constructor 'constexpr std::tuple< 
>  >::tuple(std::tuple<_Args1 ...>&&)':
> /usr/include/c++/6/tuple:695:71: error: expected primary-expression before 
> ')' token
>  : _Inherited(static_cast<_Tuple_impl<0, _UElements...>&&>(__in)) { }
>^
> /usr/include/c++/6/tuple: In constructor 'constexpr std::tuple< 
>  >::tuple(std::tuple<_Args1 ...>&&)':
> /usr/include/c++/6/tuple:706:71: error: expected primary-expression before 
> ')' token
>  : _Inherited(static_cast<_Tuple_impl<0, _UElements...>&&>(__in)) { }
>^
> /usr/include/c++/6/tuple: In constructor 'std::tuple< 
>  >::tuple(std::allocator_arg_t, const _Alloc&, const 
> std::tuple<  >&)':
> /usr/include/c++/6/tuple:760:62: error: expected primary-expression before 
> ')' token
>   : _Inherited(__tag, __a, static_cast(__in)) { }
>   ^
> /usr/include/c++/6/tuple: In constructor 'std::tuple< 
>  >::tuple(std::allocator_arg_t, const _Alloc&, 
> std::tuple<  >&&)':
> /usr/include/c++/6/tuple:764:57: error: expected primary-expression before 
> ')' token
>   : _Inherited(__tag, __a, static_cast<_Inherited&&>(__in)) { }
>  ^
> /usr/include/c++/6/tuple: In constructor 'std::tuple< 
>  >::tuple(std::allocator_arg_t, const _Alloc&, const 
> std::tuple<_Args2 ...>&)':
> /usr/include/c++/6/tuple:775:69: error: expected primary-expression before 
> ')' token
>static_cast&>(__in))
>  ^
> /usr/include/c++/6/tuple: In constructor 'std::tuple< 
>  >::tuple(std::allocator_arg_t, const _Alloc&, const 
> std::tuple<_Args2 ...>&)':
> /usr/include/c++/6/tuple:787:69: error: expected primary-expression before 
> ')' token
>static_cast&>(__in))
>  ^
> /usr/include/c++/6/tuple: In construct

Bug#824944: marked as done (lua-discount: FTBFS: Failed tests: ------------- 1) test_toc)

[Debian Bug Tracking System]

Your message dated Fri, 05 Aug 2016 10:02:19 +
with message-id 
and subject line Bug#824944: fixed in lua-discount 2.1.8-2
has caused the Debian Bug report #824944,
regarding lua-discount: FTBFS: Failed tests:   -   1) test_toc
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.)


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

Dear Maintainer,

lua-discount fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'lua-discount-build-deps' in 
'../lua-discount-build-deps_1.2.10.1-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package lua-discount-build-deps.
  (Reading database ... 23082 files and directories currently installed.)
  Preparing to unpack lua-discount-build-deps_1.2.10.1-2_all.deb ...
  Unpacking lua-discount-build-deps (1.2.10.1-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dctrl-tools dh-lua libfile-find-rule-perl liblua5.1-0 liblua5.1-0-dev
liblua5.2-0 liblua5.2-dev liblua5.3-0 liblua5.3-dev libmarkdown2
libmarkdown2-dev libnumber-compare-perl libreadline-dev libreadline6-dev
libtext-glob-perl libtinfo-dev libtool-bin lua-unit lua5.1 lua5.2 lua5.3
pkg-config
  Suggested packages:
debtags readline-doc
  The following NEW packages will be installed:
dctrl-tools dh-lua libfile-find-rule-perl liblua5.1-0 liblua5.1-0-dev
liblua5.2-0 liblua5.2-dev liblua5.3-0 liblua5.3-dev libmarkdown2
libmarkdown2-dev libnumber-compare-perl libreadline-dev libreadline6-dev
libtext-glob-perl libtinfo-dev libtool-bin lua-unit lua5.1 lua5.2 lua5.3
pkg-config
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 1732 kB of archives.
  After this operation, 7969 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 dctrl-tools amd64 
2.24-2 [101 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libtool-bin amd64 
2.4.6-0.1 [86.4 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 pkg-config amd64 
0.29-4 [62.5 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 liblua5.3-0 amd64 
5.3.1-1 [117 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libtinfo-dev amd64 
6.0+20160319-1 [77.6 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libreadline6-dev 
amd64 6.3-8+b4 [123 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libreadline-dev amd64 
6.3-8+b4 [956 B]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 liblua5.3-dev amd64 
5.3.1-1 [141 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 lua5.3 amd64 5.3.1-1 
[103 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 liblua5.2-0 amd64 
5.2.4-1 [108 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 liblua5.2-dev amd64 
5.2.4-1 [128 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 lua5.2 amd64 5.2.4-1 
[95.2 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 liblua5.1-0 amd64 
5.1.5-8 [107 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 liblua5.1-0-dev 
amd64 5.1.5-8 [130 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 lua5.1 amd64 5.1.5-8 
[96.1 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 
libnumber-compare-perl all 0.03-1 [7642 B]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 libtext-glob-perl 
all 0.09-2 [8728 B]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 
libfile-find-rule-perl all 0.34-1 [30.6 kB]
  Get:19 http://httpredir.debian.org/debian sid/main amd64 dh-lua all 23 [30.8 
kB]
  Get:20 http://httpredir.debian.org/debian sid/main amd64 libmarkdown2 amd64 
2.2.0-1 [34.5 kB]
  Get:21 http://httpredir.debian.org/debian sid/main amd64 libmarkdown2-dev 
amd64 2.2.0-1 [22.0 kB]
  Get

Processed: Re: Bug#832873: ghostscript: FTBFS: sjpx_openjpeg.c:605: undefined reference to `opj_image_destroy'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #832873 [src:ghostscript] ghostscript: FTBFS: sjpx_openjpeg.c:605: 
undefined reference to `opj_image_destroy'
Added tag(s) patch.

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

Bug#832873: ghostscript: FTBFS: sjpx_openjpeg.c:605: undefined reference to `opj_image_destroy'

[Didier 'OdyX' Raboud]

Control: tags -1 +patch

Le vendredi, 29 juillet 2016, 08.48:47 h CEST Lucas Nussbaum a écrit :
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > ./base/sjpx_openjpeg.c:249: undefined
> > reference to `opj_decode' /usr/bin/ld: ./sobin/libgs.so.9.19: hidden
> > symbol `opj_setup_decoder' isn't defined /usr/bin/ld: final link failed:

I've now spent quite some time investigating this and finally found the
problem: libopenjp2-7-dev (>= 2.1.1) has changed it's
/usr/include/openjpeg-2.1/openjpeg.h
to include the following lines:

#if defined(OPJ_STATIC) || !defined(_WIN32)
/* http://gcc.gnu.org/wiki/Visibility */
#   if __GNUC__ >= 4
#   if defined(OPJ_STATIC) /* static library uses "hidden" */
#   define OPJ_API__attribute__ ((visibility 
("hidden")))
#   else
#   define OPJ_API__attribute__ ((visibility 
("default")))
#   endif

This makes all API symbols hidden if '-DOPJ_STATIC' is passed to GCC; as
it happens to be passed in base/lib.mak :

$(GLOBJ)sjpx_openjpeg.$(OBJ) : $(GLSRC)sjpx_openjpeg.c $(AK) \
 $(memory__h) $(gserror_h) $(gserrors_h) \
 $(gdebug_h) $(strimpl_h) $(sjpx_openjpeg_h) $(LIB_MAK) $(MAKEDIRS)
   $(GLJPXOPJCC) $(GLO_)sjpx_openjpeg.$(OBJ) \
   $(C_) -DOPJ_STATIC $(GLSRC)sjpx_openjpeg.c

Patching this -DOPJ_STATIC out fixes the FTBFS; patch attached.

Cheers,
-- 
OdyXDescrtiption: Don't pass -DOPJ_STATIC when compiling the OpenJPEG code, as it
 makes the symbols hidden when including /usr/include/openjpeg-2.1/openjpeg.h
 .
 Fixes a FTBFS against libopenjp2-7 (>= 2.1.1)
Author: Didier Raboud 
Origin: vendor
Bug-Debian: https://bugs.debian.org/832873

--- a/base/lib.mak
+++ b/base/lib.mak
@@ -1830,11 +1830,11 @@
 
 $(GLOBJ)sjpx_openjpeg.$(OBJ) : $(GLSRC)sjpx_openjpeg.c $(AK) \
  $(memory__h) $(gserror_h) $(gserrors_h) \
  $(gdebug_h) $(strimpl_h) $(sjpx_openjpeg_h) $(LIB_MAK) $(MAKEDIRS)
 	$(GLJPXOPJCC) $(GLO_)sjpx_openjpeg.$(OBJ) \
-		$(C_) -DOPJ_STATIC $(GLSRC)sjpx_openjpeg.c
+		$(C_) $(GLSRC)sjpx_openjpeg.c
 
 #  Pixel-difference filters  #
 # The Predictor facility of the LZW and Flate filters uses these.
 
 pdiff_=$(GLOBJ)spdiff.$(OBJ)


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

Bug#828669: Fixed #828669 in Git: can I upload?

[Thomas Goirand]

Hi Brian,

I've fixed #828669 by applying a patch from a contributor of django-mptt
which was available in github. I pushed all of that (including upgrading
to 0.8.5, the latest upstream release) to the DPMT git. Are you giving
me the greenlight for upload?

Cheers,

Thomas Goirand (zigo)

Processed: your mail

[Debian Bug Tracking System]

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

> severity 827215 important
Bug #827215 [android-sdk] android-sdk: llvm-rs-cc is missing
Severity set to 'important' from 'grave'
> # Not grave anymore after addition of the stub, it'll good enough for now.
>
End of message, stopping processing here.

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

Bug#833394: wmweather: URL of data source has changed

[Cristian Ionescu-Idbohrn]

On Fri, 5 Aug 2016, Matthieu Weber wrote:
> On Thu 04.08.2016 at 10:20:17PM +0200, Cristian Ionescu-Idbohrn wrote:
> > On Wed, 3 Aug 2016, Matthieu Weber wrote:
> > >
> > > The URL of the source of the data used by wmweather has changed,
> > > causing the software to exit immediately upon start.
> > >
> > > The fix is trivial, and a patch is included.
> >
> > Yeah, I thought of that too.  And tested (from strace):
> >
> > GET /pub/data/observations/metar/decoded/YBRM.TXT HTTP/1.1\r\nHost:
> > tgftp.nws.noaa.gov\r\nUser-Agent: wmweather 2.4.5\r\nAccept:
> > */*\r\n\r\n
>
> Remove the "/pub" in the beginning of the path, it shouldn't be there.
>
> This url works:
> http://tgftp.nws.noaa.gov/data/observations/metar/decoded/YBRM.TXT
>
> This one does not:
> http://tgftp.nws.noaa.gov/pub/data/observations/metar/decoded/YBRM.TXT

Yes, that does the trick ;)


Cheers,

-- 
Cristian

debian-bugs-rc@lists.debian.org

[Debian Bug Tracking System]

Your message dated Fri, 5 Aug 2016 10:24:00 +0200
with message-id <0bc140f9-455d-811b-f076-d68ed17b7...@debian.org>
and subject line Re: avogadro: FTBFS in experimental: undefined reference to 
`OpenBabel::OBMol::OBMol(OpenBabel::OBMol const&)'
has caused the Debian Bug report #803657,
regarding avogadro: FTBFS in experimental: undefined reference to 
`OpenBabel::OBMol::OBMol(OpenBabel::OBMol const&)'
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.)


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

avogadro compiles fine in experimental, but fails to link:

[100%] Linking CXX shared module ../../../lib/Avogadro.so
cd /tmp/buildd/avogadro-1.1.1/obj-x86_64-linux-gnu/libavogadro/src/python && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/python-module.dir/link.txt 
--verbose=1
/usr/bin/c++  -fPIC -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security  -fvisibility=hidden 
-fvisibility-inlines-hidden -fpermissive -Wl,--enable-new-dtags 
-Wl,--enable-new-dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc  -fPIC 
-Wl,-z,relro -Wl,-z,defs -Wl,--as-needed -shared -Wl,-soname,Avogadro.so -o 
../../../lib/Avogadro.so CMakeFiles/python-module.dir/eigen.cpp.o 
CMakeFiles/python-module.dir/camera.cpp.o 
CMakeFiles/python-module.dir/residue.cpp.o 
CMakeFiles/python-module.dir/primitivelist.cpp.o 
CMakeFiles/python-module.dir/mesh.cpp.o 
CMakeFiles/python-module.dir/periodictableview.cpp.o 
CMakeFiles/python-module.dir/molecule.cpp.o 
CMakeFiles/python-module.dir/primitive.cpp.o 
CMakeFiles/python-module.dir/fragment.cpp.o 
CMakeFiles/python-module.dir/engine.cpp.o 
CMakeFiles/python-module.dir/atom.cpp.o 
CMakeFiles/python-module.dir/painter.cpp.o 
CMakeFiles/python-module.dir/qlist.cpp.o 
CMakeFiles/python-module.dir/swig.cpp.o CMakeFiles/python-mo
 dule.dir/toolgroup.cpp.o CMakeFiles/python-module.dir/qstring.cpp.o 
CMakeFiles/python-module.dir/sip.cpp.o 
CMakeFiles/python-module.dir/moleculefile.cpp.o 
CMakeFiles/python-module.dir/std_vector.cpp.o 
CMakeFiles/python-module.dir/moleculelist.cpp.o 
CMakeFiles/python-module.dir/elementtranslator.cpp.o 
CMakeFiles/python-module.dir/plugin.cpp.o 
CMakeFiles/python-module.dir/meshgenerator.cpp.o 
CMakeFiles/python-module.dir/color.cpp.o 
CMakeFiles/python-module.dir/glwidget.cpp.o 
CMakeFiles/python-module.dir/neighborlist.cpp.o 
CMakeFiles/python-module.dir/cube.cpp.o 
CMakeFiles/python-module.dir/painterdevice.cpp.o 
CMakeFiles/python-module.dir/bond.cpp.o 
CMakeFiles/python-module.dir/pluginmanager.cpp.o 
CMakeFiles/python-module.dir/animation.cpp.o 
CMakeFiles/python-module.dir/navigate.cpp.o 
CMakeFiles/python-module.dir/extension.cpp.o 
CMakeFiles/python-module.dir/main.cpp.o CMakeFiles/python-module.dir/tool.cpp.o 
-lstdc++ ../../../lib/libavogadro.so.1.1.1 -lQtOpenGL -lQtGui -lQtCore -lpython
 2.7 -lboost_python 
-Wl,-rpath,/tmp/buildd/avogadro-1.1.1/obj-x86_64-linux-gnu/lib: 
CMakeFiles/python-module.dir/swig.cpp.o: In function 
`Molecule_OBMol(Avogadro::Molecule&)':
/tmp/buildd/avogadro-1.1.1/libavogadro/src/python/swig.cpp:554: undefined 
reference to `OpenBabel::OBMol::OBMol(OpenBabel::OBMol const&)'
/tmp/buildd/avogadro-1.1.1/libavogadro/src/python/swig.cpp:554: undefined 
reference to `OpenBabel::OBMol::~OBMol()'
/tmp/buildd/avogadro-1.1.1/libavogadro/src/python/swig.cpp:554: undefined 
reference to `OpenBabel::OBMol::~OBMol()'
collect2: error: ld returned 1 exit status
libavogadro/src/python/CMakeFiles/python-module.dir/build.make:993: recipe for 
target 'lib/Avogadro.so' failed
make[3]: *** [lib/Avogadro.so] Error 1
make[3]: Leaving directory '/tmp/buildd/avogadro-1.1.1/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:3089: recipe for target 
'libavogadro/src/python/CMakeFiles/python-module.dir/all' failed
make[2]: *** [libavogadro/src/python/CMakeFiles/python-module.dir/all] Error 2
make[2]: Leaving directory '/tmp/buildd/avogadro-1.1.1/obj-x86_64-linux-gnu'
Makefile:152: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/tmp/buildd/avogadro-1.1.1/obj-x86_64-linux-gnu'
dh_auto_build: make -j16 returned exit code 2
debian/rules:20: recipe for target 'build' failed


Andreas
--- End Message ---
--- Begin Message ---
Version: 1.1.1-1~exp3.1

the 1.1.1-1~exp3.1 NMU successfully built.--- End Message ---

Bug#833503: autopkgtest: accesses the internet during build

[Chris Lamb]

Source: autopkgtest
Version: 4.0.3
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst autopkgtest builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

The culprit seems to be:

 testbed.satisfy_dependencies_string('git, ca-certificates', 'install git for 
--git-source')

in runner/autopkgtest.

  2016-08-05 08:57:30.904700 IP 172.16.42.255.39212 > 10.0.1.1.domain: 1138+ 
SRV? _http._tcp.httpredir.debian.org. (49)
  2016-08-05 08:57:30.906362 IP 10.0.1.1.domain > 172.16.42.255.39212: 1138 
NXDomain* 0/0/0 (49)
  2016-08-05 08:57:30.906785 IP 172.16.42.255.41134 > 
httpredir.debian.org.http: Flags [S], seq 1490473331, win 29200, options [mss 
1460,sackOK,TS val 105543481 ecr 0,nop,wscale 7], length 0
  2016-08-05 08:57:30.906856 IP httpredir.debian.org.http > 
172.16.42.255.41134: Flags [S.], seq 875435214, ack 1490473332, win 28960, 
options [mss 1460,sackOK,TS val 105543481 ecr 105543481,nop,wscale 7], length 0
  2016-08-05 08:57:30.906868 IP 172.16.42.255.41134 > 
httpredir.debian.org.http: Flags [.], ack 1, win 229, options [nop,nop,TS val 
105543481 ecr 105543481], length 0
  2016-08-05 08:57:30.906960 IP 172.16.42.255.41134 > 
httpredir.debian.org.http: Flags [P.], seq 1:158, ack 1, win 229, options 
[nop,nop,TS val 105543481 ecr 105543481], length 157: HTTP: GET 
/debian/pool/main/c/ca-certificates/ca-certificates_20160104_all.deb HTTP/1.1
  2016-08-05 08:57:30.906988 IP httpredir.debian.org.http > 
172.16.42.255.41134: Flags [.], ack 158, win 235, options [nop,nop,TS val 
105543481 ecr 105543481], length 0
  2016-08-05 08:57:30.907110 IP httpredir.debian.org.http > 
172.16.42.255.41134: Flags [.], seq 1:7241, ack 158, win 235, options 
[nop,nop,TS val 105543481 ecr 105543481], length 7240: HTTP: HTTP/1.1 200 OK
  2016-08-05 08:57:30.907134 IP 172.16.42.255.41134 > 
httpredir.debian.org.http: Flags [.], ack 7241, win 342, options [nop,nop,TS 
val 105543481 ecr 105543481], length 0
  2016-08-05 08:57:30.907197 IP httpredir.debian.org.http > 
172.16.42.255.41134: Flags [.], seq 7241:14481, ack 158, win 235, options 
[nop,nop,TS val 105543481 ecr 105543481], length 7240: HTTP

  [..]

The full build log (including tcpdump output) is attached.


Regards,

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


autopkgtest.4.0.3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#811957: RFS: ecere-sdk/0.44.15-1 -- Please sponsor this new release of the Ecere SDK; Closes #811957; Closes #826352

[Jérôme St-Louis]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the 0.44.15-1 release of my package 
"ecere-sdk".


This closes 2 bugs including a serious one (FTBFS with GCC 6 which had 
it removed from 'testing').


Closes #811957 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811957)
Closes #826352 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826352)

* Package name: ecere-sdk
   Version : 0.44.15-1
   Upstream Author : Ecere Corporation 
* URL : http://ecere.org
* License : BSD-3 clauses
  Section : Development

It builds those binary packages:

ecere-dev - Ecere SDK Development Tools
ecere-extras - Extras for the Ecere SDK
ecere-samples - Project samples for the Ecere SDK
ecere-sdk - Ecere cross-platform SDK
libecc0 - eC Compiler Library
libecere0 - Ecere Runtime Library
libecereaudio0 - Ecere Audio
libecerecom0 - eC Core Runtime Library
libeda0 - Ecere Data Access
libedasqlite0 - EDA SQLite Driver

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

http://mentors.debian.net/package/ecere-sdk


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


  dget -x 
https://mentors.debian.net/debian/pool/main/e/ecere-sdk/ecere-sdk_0.44.15-1.dsc 



  More information about the Ecere SDK can be obtained from 
http://ecere.org



See Ecere SDK 0.44.15 release notes @ 
https://github.com/ecere/ecere-sdk/releases


New features include among others:
- Web support through Emscripten
- OpenGL Support
- Introduction of the ECON data inter-change format ( 
http://ec-lang.org/econ/ )

- IDE Customization (fonts & color schemes)


  Changes since the last upload:

ecere-sdk (0.44.15-1) unstable; urgency=low

  * Packaged Ecere SDK 0.44.15 (Closes: #811957 #826352)
  * Changes:
  * Fixed building with GCC 6 (Compiler was generating bad 
__attribute__

specifiers with spaces rather than commas)
  * Renamed IDE binary to less generic name (ide ==> ecere-ide)
  * Web Support through Emscripten and WebGL
  * 3D Graphics Improvements (OpenGL)
 - Support for Shaders
   (WebGL, Core/Compatibility profiles, OpenGL ES 2)
 - Phong Shading Using Shaders
 - Environment Mapping and Cube Maps
(Support for Reflection and Refraction)
 - Normals Mapping Support
 - Fixed and improved lighting
 - Computed Normals Weighting for smoother surfaces
 - Optimizations
  * Font Outline Support
  * Fixed text extent computation to account for overhang of italic 
fonts

  * ECON Support (ECON is a JSON superset, dropping quotes, supporting
hexadecimal, multi-line strings, comments, derived classes, and
mapping directly to eC instantiations -- http://ec-lang.org/econ/ )
  * ECON based IDE configuration (split options, recent files/projects
and compilers individually stored in separate files,
all in ~/.ecereIDE/)
  * ECON based Documentor
 (Documentation data can now be text-diffed with git etc.)
  * ECON based Color Scheme and Font Selection in Global Settings
  * Sortable Containers
  * Distributed Objects Fixes & Improvements
  * (Windows) Fixes for TDM-GCC 5
  * Android: Fixes to run on newer versions
  * X: Fixed NumPad key definitions
  * Build system Fixes & Improvements
  * Other Fixes & Improvements

 -- Jerome St-Louis   Thu, 4 Aug 2016 14:00:00 -0400


Best Regards,

 Jerome St-Louis

Bug#833493: cufflinks: FTBFS with gcc-6

[Gianfranco Costamagna]

Hi,

>The problem is, if the package does not build I can't upload it with the
>version ignorant boost.  The only thing I can do is commiting the change
>to Git which I did right now.


thanks!
>Anybody else reading here?

actually the issue is lemon library, an embedded code copy.
I found the original library
https://lemon.cs.elte.hu/trac/lemon/wiki/Downloads
seems that the embedded code copy is around version 0.7 while now they are at 
1.3.1
I would suggest you to package it and use it, because that particular code 
block seems to have
been changed, even if it is not trivial to extract a patch
(and would be also useless, because embedded code copies breaks too often and 
always because of
toolchain changes, because it is difficult to track them, and they don't get 
upstream fixes)

G.

Bug#833430: creduce doesn't pass the files to reduce to the test script

[Niko Tyni]

On Thu, Aug 04, 2016 at 11:26:58AM +0200, Matthias Klose wrote:
> Package: creduce
> Version: 2.5.0-1
> Severity: serious
> Tags: sid stretch
> 
> creduce doesn't pass the files to reduce to the test script. This used to 
> work ...
> 
> $ creduce --debug ./cr2.sh foo.c

> sanity check... tmpdir = /tmp/creduce-eButm5
> usage: /home/packages/tmp/cr2.sh 

Looks like commit creduce-2.4.0-7-g0bfd954
 
https://github.com/csmith-project/creduce/commit/0bfd95402e126293bb4f7df1435770f66da98bb1
changed the sanity check to run the "interestingness test" without
arguments, so your "exit 1" in cr2.sh usage() now makes it fail.

 +The interestingness test should not expect any command line arguments. 

Hope this helps,
-- 
Niko Tyni   nt...@debian.org

Bug#833487: systemd: Replaces file in systemd-container 230-1

[Michael Biebl]

Control: tags -1 + confirmed

Am 05.08.2016 um 04:33 schrieb Matthias Urlichs:
> Package: systemd
> Version: 230-1
> Severity: serious
> Justification: Missing Replaces:
> 
> Unpacking systemd (231-1) over (230-1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/systemd_231-1_amd64.deb (--unpack):
>  trying to overwrite '/lib/systemd/system/org.freedesktop.import1.busname', 
> which is also in package systemd-container 230-1

That's a result of
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=fa607af7b4c57e95675c533b26bc7ecab001e836

I think this rule should be re-added, as those clean-up rules are not
obsolete. Upstream still ships busname units.

If we decide though to keep the busname units,

/lib/systemd/system/org.freedesktop.import1.busname
/lib/systemd/system/org.freedesktop.machine1.busname

should be added to systemd-container.install instead, afaics.




-- 
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#833487: systemd: Replaces file in systemd-container 230-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #833487 [systemd] systemd: Replaces file in systemd-container 230-1
Added tag(s) confirmed.

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

Bug#833497: FTBFS: ImportError: No module named pyld

[Logan Rosen]

Package: python-activipy
Version: 0.1-4
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

python-activipy currently fails to build from source due to a lack of a
build dependency on python-pyld and python3-pyld. They are required for the
tests to run properly. [1]

In Ubuntu, the attached patch was applied to achieve the following:

  * Build-depend on python(3)-pyld to fix FTBFS.

Thanks for considering the patch.

Logan Rosen

[1] 
https://launchpadlibrarian.net/276329651/buildlog_ubuntu-yakkety-amd64.python-activipy_0.1-4_BUILDING.txt.gz

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-activipy-0.1/debian/control python-activipy-0.1/debian/control
--- python-activipy-0.1/debian/control	2016-07-31 16:33:34.0 -0400
+++ python-activipy-0.1/debian/control	2016-08-05 02:45:42.0 -0400
@@ -13,7 +13,9 @@
python3-pytest,
dh-python,
docbook-xsl,
-   xsltproc
+   xsltproc,
+   python-pyld,
+   python3-pyld
 Homepage: https://github.com/w3c-social/activipy
 Standards-Version: 3.9.8
 Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/python-activipy.git

Bug#833493: cufflinks: FTBFS with gcc-6

[Andreas Tille]

Hi Gianfranco,

On Fri, Aug 05, 2016 at 06:37:44AM +, Gianfranco Costamagna wrote:
> source: cufflinks
> version: 2.2.1-2
> severity: serious
> 
> Hi Andreas, as said in private emails, the package FTBFS with the new 
> toolchain, but what you didn't
> notice, is that the failure is not boost related, but gcc-6 (the default 
> since yesterday) instead.

May be it was to late yesterday. :-)

The problem is, if the package does not build I can't upload it with the
version ignorant boost.  The only thing I can do is commiting the change
to Git which I did right now.

> In file included from ./lemon/bits/base_extender.h:23:0,
> from ./lemon/list_graph.h:26,
> from ./lemon/dfs.h:26,
> from ./lemon/topology.h:22,
> from assemble.cpp:19:
> ./lemon/error.h: In member function 'lemon::ExceptionMember<_Type>& 
> lemon::ExceptionMember<_Type>::operator=(const 
> lemon::ExceptionMember<_Type>&)':
> ./lemon/error.h:70:27: error: return-statement with no value, in function 
> returning 'lemon::ExceptionMember<_Type>&' [-fpermissive]
> if (ptr.get() == 0) return;
> ^~
> ./lemon/error.h:72:21: error: return-statement with no value, in function 
> returning 'lemon::ExceptionMember<_Type>&' [-fpermissive]
> if (!copy.valid()) return;
> ^~
> 
> seems that you are returning nothing, in a method created to return an 
> ExceptionMember& pointer
> ExceptionMember& operator=(const ExceptionMember& copy) {
> 
> 
> I don't have a patch, sorry!

Anybody else reading here?
 
Kind regards

  Andreas.

-- 
http://fam-tille.de