Processed: found 835532 in 1.36-1, found 835535 in 1.36-1

[Debian Bug Tracking System]

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

> found 835532 1.36-1
Bug #835532 [postgrey] default config dir change from /etc/postgrey to 
/etc/postfix not handled
Marked as found in versions postgrey/1.36-1.
> found 835535 1.36-1
Bug #835535 [postgrey] fails to start after upgrade: default dbdir change not 
handled
Marked as found in versions postgrey/1.36-1.
> thanks
Stopping processing here.

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

Processed: fixed 821734 in 1.3.0-3

[Debian Bug Tracking System]

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

> fixed 821734 1.3.0-3
Bug #821734 {Done: Nicholas Breen } [libvotca-csg3] 
libvotca-csg3: fails to upgrade from 'jessie' - trying to overwrite 
/usr/share/man/man7/votca-csg.7.gz
Marked as fixed in versions votca-csg/1.3.0-3.
> thanks
Stopping processing here.

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

Processed: Fix the version tracking for this mate-common bug

[Debian Bug Tracking System]

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

> reassign 833001 mate-common
Bug #833001 {Done: John Paul Adrian Glaubitz } 
[src:caja-actions] caja-actions: FTBFS: ./autogen.sh: 80: shift: can't shift 
that many
Bug reassigned from package 'src:caja-actions' to 'mate-common'.
No longer marked as found in versions caja-actions/1.8.0+dfsg1-1.
No longer marked as fixed in versions mate-common/1.14.0-2.
> reassign 833076 mate-common
Bug #833076 {Done: John Paul Adrian Glaubitz } 
[src:mate-indicator-applet] mate-indicator-applet: FTBFS: ./autogen.sh: 80: 
shift: can't shift that many
Bug reassigned from package 'src:mate-indicator-applet' to 'mate-common'.
No longer marked as found in versions mate-indicator-applet/1.14.1-1.
No longer marked as fixed in versions mate-common/1.14.0-2.
> reassign 833842 mate-common
Bug #833842 {Done: John Paul Adrian Glaubitz } 
[src:mate-power-manager] mate-power-manager: FTBFS: ./autogen.sh: 80: shift: 
can't shift that many
Bug reassigned from package 'src:mate-power-manager' to 'mate-common'.
No longer marked as found in versions mate-power-manager/1.14.0-2.
No longer marked as fixed in versions mate-common/1.14.0-2.
> reassign 833881 mate-common
Bug #833881 {Done: John Paul Adrian Glaubitz } 
[src:caja-dropbox] caja-dropbox: FTBFS in sid: ./autogen.sh: 80: shift: can't 
shift that many
Bug reassigned from package 'src:caja-dropbox' to 'mate-common'.
No longer marked as found in versions caja-dropbox/1.14.0-1.
No longer marked as fixed in versions mate-common/1.14.0-2.
> reassign 834079 mate-common
Bug #834079 {Done: John Paul Adrian Glaubitz } 
[src:atril] atril: FTBFS: ./autogen.sh: 80: shift: can't shift that many
Bug reassigned from package 'src:atril' to 'mate-common'.
No longer marked as found in versions atril/1.14.1-2.
No longer marked as fixed in versions mate-common/1.14.0-2.
> reassign 834287 mate-common
Bug #834287 {Done: John Paul Adrian Glaubitz } 
[src:caja-extensions] caja-extensions: FTBFS: ./autogen.sh: 80: shift: can't 
shift that many
Bug reassigned from package 'src:caja-extensions' to 'mate-common'.
No longer marked as found in versions caja-extensions/1.14.0-1.
No longer marked as fixed in versions mate-common/1.14.0-2.
> merge 833001 833076 833842 833881 834079 834287
Bug #833001 {Done: John Paul Adrian Glaubitz } 
[mate-common] caja-actions: FTBFS: ./autogen.sh: 80: shift: can't shift that 
many
Bug #834287 {Done: John Paul Adrian Glaubitz } 
[mate-common] caja-extensions: FTBFS: ./autogen.sh: 80: shift: can't shift that 
many
Added tag(s) sid and stretch.
Bug #833881 {Done: John Paul Adrian Glaubitz } 
[mate-common] caja-dropbox: FTBFS in sid: ./autogen.sh: 80: shift: can't shift 
that many
Added tag(s) stretch and sid.
Bug #833842 {Done: John Paul Adrian Glaubitz } 
[mate-common] mate-power-manager: FTBFS: ./autogen.sh: 80: shift: can't shift 
that many
Added tag(s) stretch and sid.
Bug #833076 {Done: John Paul Adrian Glaubitz } 
[mate-common] mate-indicator-applet: FTBFS: ./autogen.sh: 80: shift: can't 
shift that many
Added tag(s) sid and stretch.
Bug #834079 {Done: John Paul Adrian Glaubitz } 
[mate-common] atril: FTBFS: ./autogen.sh: 80: shift: can't shift that many
Added tag(s) stretch and sid.
Merged 833001 833076 833842 833881 834079 834287
> found 833001 1.14.0-1
Bug #833001 {Done: John Paul Adrian Glaubitz } 
[mate-common] caja-actions: FTBFS: ./autogen.sh: 80: shift: can't shift that 
many
Bug #833076 {Done: John Paul Adrian Glaubitz } 
[mate-common] mate-indicator-applet: FTBFS: ./autogen.sh: 80: shift: can't 
shift that many
Bug #833842 {Done: John Paul Adrian Glaubitz } 
[mate-common] mate-power-manager: FTBFS: ./autogen.sh: 80: shift: can't shift 
that many
Bug #833881 {Done: John Paul Adrian Glaubitz } 
[mate-common] caja-dropbox: FTBFS in sid: ./autogen.sh: 80: shift: can't shift 
that many
Bug #834079 {Done: John Paul Adrian Glaubitz } 
[mate-common] atril: FTBFS: ./autogen.sh: 80: shift: can't shift that many
Bug #834287 {Done: John Paul Adrian Glaubitz } 
[mate-common] caja-extensions: FTBFS: ./autogen.sh: 80: shift: can't shift that 
many
Marked as found in versions mate-common/1.14.0-1 and reopened.
Marked as found in versions mate-common/1.14.0-1 and reopened.
Marked as found in versions mate-common/1.14.0-1 and reopened.
Marked as found in versions mate-common/1.14.0-1 and reopened.
Marked as found in versions mate-common/1.14.0-1 and reopened.
Marked as found in versions 

Processed: Fix the version tracking of #831182

[Debian Bug Tracking System]

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

> reassign 831182 qbs-dev
Bug #831182 {Done: Adam Majer } [src:qtcreator] qtcreator: 
FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or 
directory
Bug reassigned from package 'src:qtcreator' to 'qbs-dev'.
No longer marked as found in versions qtcreator/4.0.2-1.
No longer marked as fixed in versions qbs/1.5.2+dfsg-1.
> found 831182 1.5.1+dfsg-1
Bug #831182 {Done: Adam Majer } [qbs-dev] qtcreator: FTBFS 
with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory
Marked as found in versions qbs/1.5.1+dfsg-1 and reopened.
> fixed 831182 1.5.2+dfsg-1
Bug #831182 [qbs-dev] qtcreator: FTBFS with GCC 6: cstdlib:75:25: fatal error: 
stdlib.h: No such file or directory
Marked as fixed in versions qbs/1.5.2+dfsg-1.
> affects 831182 src:qtcreator
Bug #831182 [qbs-dev] qtcreator: FTBFS with GCC 6: cstdlib:75:25: fatal error: 
stdlib.h: No such file or directory
Added indication that 831182 affects src:qtcreator
> close 831182
Bug #831182 [qbs-dev] qtcreator: FTBFS with GCC 6: cstdlib:75:25: fatal error: 
stdlib.h: No such file or directory
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#815004: Engine is installed at wrong location

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 0.1.8-4
Bug #815004 {Done: Eric Dorland } [libengine-pkcs11-openssl] 
Engine is installed at wrong location
No longer marked as found in versions engine-pkcs11/0.1.8-4.

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

Bug#815004: Engine is installed at wrong location

[Julien Cristau]

Control: notfound -1 0.1.8-4

On Fri, Aug 26, 2016 at 13:39:13 +0200, Julien Cristau wrote:

> Control: found -1 0.1.8-4
> 
[...]
> This seems broken in stable as well:
> 
> $ openssl engine pkcs11
> 140063553324688:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
> the shared 
> library:dso_dlfcn.c:187:filename(/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpkcs11.so):
>  /usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpkcs11.so: cannot open 
> shared object file: No such file or directory
> 140063553324688:error:25070067:DSO support routines:DSO_load:could not load 
> the shared library:dso_lib.c:232:
> 140063553324688:error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
> found:eng_dyn.c:465:
> 140063553324688:error:2606A074:engine routines:ENGINE_by_id:no such 
> engine:eng_list.c:390:id=pkcs11
> 
> It would be nice to fix this in a jessie update.
> 
So after more poking, it seems that's not how engine_pkcs11 works in
jessie at all, and I need an openssl config file to get it loaded
instead.

Cheers,
Julien

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Yaroslav Halchenko]

Thank you Richard!

On August 26, 2016 7:40:50 PM EDT, Richard Hartmann 
 wrote:
>And uploaded.

Bug#835550: network-manager: FTBFS on mips* and powerpc - NetworkManager segfaults

[James Cowgill]

Source: network-manager
Version: 1.4.0-2
Severity: serious

Hi,

network-manager FTBFS on all mips arches and on powerpc with this error:

> make[9]: Leaving directory '/«PKGBUILDDIR»/src/settings/plugins/ibft/tests'
> LD_BIND_NOW=1 LD_PRELOAD=./../.libs/libnm-settings-plugin-ibft.so 
> ../../../../../src/NetworkManager --version >/dev/null
> /bin/bash: line 1: 10923 Segmentation fault  LD_BIND_NOW=1 
> LD_PRELOAD=./../.libs/libnm-settings-plugin-ibft.so 
> ../../../../../src/NetworkManager --version > /dev/null
> Makefile:1254: recipe for target 'check-local' failed
> make[8]: *** [check-local] Error 139
> make[8]: Leaving directory '/«PKGBUILDDIR»/src/settings/plugins/ibft/tests'
> Makefile:1048: recipe for target 'check-am' failed
> make[7]: *** [check-am] Error 2
> make[7]: Leaving directory '/«PKGBUILDDIR»/src/settings/plugins/ibft/tests'
> Makefile:698: recipe for target 'check-recursive' failed
> make[6]: *** [check-recursive] Error 1
> make[6]: Leaving directory '/«PKGBUILDDIR»/src/settings/plugins/ibft'
> Makefile:519: recipe for target 'check-recursive' failed
> make[5]: *** [check-recursive] Error 1
> make[5]: Leaving directory '/«PKGBUILDDIR»/src/settings/plugins'
> Makefile:2509: recipe for target 'check-recursive' failed
> make[4]: *** [check-recursive] Error 1
> make[4]: Leaving directory '/«PKGBUILDDIR»/src'
> Makefile:2658: recipe for target 'check' failed
> make[3]: *** [check] Error 2
> make[3]: Leaving directory '/«PKGBUILDDIR»/src'
> Makefile:655: recipe for target 'check-recursive' failed
> make[2]: *** [check-recursive] Error 1

I tried to build it on mips64el and simply trying to run 'NetworkManager
--version' prints out the correct version, then a load of garbage before
finally segfaulting.

I haven't done extensive testing, but this bug smells very similar to
bug #816059 in lua and is related to using version scripts on certain
architectures.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Richard Hartmann]

And uploaded.

Bug#835085: noweb: FTBFS: build-depends on iconc which didn't work and it was removed

[Santiago Vila]

On Fri, Aug 26, 2016 at 03:04:32PM -0400, Hubert Chathi wrote:
> On Mon, 22 Aug 2016 11:53:51 +0200 (CEST), Santiago Vila  
> said:
> 
> > This package does no longer build from source because the iconc
> > package does no longer exist (I'm not providing a build log, but this
> > is very easy to check).
> [...]
> > So, I believe the attached patch should fix the FTBFS bug (but I have
> > not actually tested it). Please give it a try.
> 
> Thanks.  The patch seems to work fine.  Can you sponsor an upload for
> me?  My key was removed from the keyring due to being weak, and I
> haven't managed to get a new one in.  The fixed packages are available
> at: https://debian.uhoreg.ca/unstable/ (In addition to the diff you
> provided, I also updated the upstream's homepage.)

I'll take a look, yes.

Bug#835514: marked as done (libprotobuf-java: junit and easymock dependencies should only be required for tests)

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 23:19:24 +
with message-id 
and subject line Bug#835514: fixed in protobuf 3.0.0-6
has caused the Debian Bug report #835514,
regarding libprotobuf-java: junit and easymock dependencies should only be 
required for tests
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.)


-- 
835514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libprotobuf-java
Version: 3.0.0-5
Severity: serious
Tags: patch

Hello,

thanks for fixing #835358 so quickly. Unfortunately there is another
issue with the pom.xml file now. java/core/pom.xml lists junit and
easymock artifacts as dependencies but libprotobuf-java does not
depend on these packages. This causes build failures like [1].

libprotobuf-java should either depend on the respective packages or
change the scope to test again as in earlier versions. I think the
latter solution is preferable because junit and easymock are only
needed for tests. If you take a look at version 2.6.1, you will see
that scope test was used before. [2] I don't know why they changed this
but it looks like an upstream bug to me.

I'm attaching a patch that resolves the issue and restores the old
behavior again.

Regards,

Markus

[1] https://bugs.debian.org/835430
[2] 
https://anonscm.debian.org/cgit/pkg-protobuf/pkg-protobuf.git/tree/java/pom.xml?h=debian/2.6.1-2
From: Markus Koschany 
Date: Thu, 25 Aug 2016 18:58:17 +0200
Subject: protobuf-java

---
 java/core/pom.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/java/core/pom.xml b/java/core/pom.xml
index 39d6781..20ed02a 100644
--- a/java/core/pom.xml
+++ b/java/core/pom.xml
@@ -22,14 +22,17 @@
 
   junit
   junit
+  test
 
 
   org.easymock
   easymock
+  test
 
 
   org.easymock
   easymockclassextension
+  test
 
   
 
--- End Message ---
--- Begin Message ---
Source: protobuf
Source-Version: 3.0.0-6

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

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

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated protobuf 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, 27 Aug 2016 09:02:16 +1000
Source: protobuf
Binary: libprotobuf10 libprotobuf-lite10 libprotobuf-dev libprotoc10 
libprotoc-dev protobuf-compiler python-protobuf libprotobuf-java
Architecture: source amd64 all
Version: 3.0.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian protobuf maintainers 

Changed-By: Dmitry Smirnov 
Description:
 libprotobuf-dev - protocol buffers C++ library (development files)
 libprotobuf-java - Java bindings for protocol buffers
 libprotobuf-lite10 - protocol buffers C++ library (lite version)
 libprotobuf10 - protocol buffers C++ library
 libprotoc-dev - protocol buffers compiler library (development files)
 libprotoc10 - protocol buffers compiler library
 protobuf-compiler - compiler for protocol buffer definition files
 python-protobuf - Python bindings for protocol buffers
Closes: 835514
Changes:
 protobuf (3.0.0-6) unstable; urgency=medium
 .
   * New "java-test-scope.patch" to set scope of "junit" and "easymock" to
 "test" (Closes: #835514).
 Thanks, Markus Koschany.
Checksums-Sha1:
 8ec920dac419ea1d6b4426f83ee189114a5dd538 2859 protobuf_3.0.0-6.dsc
 938350e7996f2ec58c3a26ab67c98715898b0519 20660 protobuf_3.0.0-6.debian.tar.xz
 e0a60be24505a6dfbb6b52620321afb77b4c426f 937680 
libprotobuf-dev_3.0.0-6_amd64.deb
 38a85fdc72a2669feb9054c5da3f89018bacbff9 643702 
libprotobuf-java_3.0.0-6_all.deb
 b71ba2670280d17c1e2629e230465ea37cd36c7e 713866 
libprotobuf-lite10-dbgsym_3.0.0-6_amd64.deb
 f3649f15b63bffbbb410f7cbdb3802398ac7eacf 12 
libprotobuf-lite10_3.0.0-6_amd64.deb
 ce5e5bbabff4d5e0b9eb95923cc4a6977bfb3b09 6433426 
libprotobuf10-dbgsym_3.0.0-6_amd64.deb
 63207112084f65df6de3716e839612f46c1043eb 

Processed: bug 835514 is forwarded to https://github.com/google/protobuf/issues/2019

[Debian Bug Tracking System]

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

> forwarded 835514 https://github.com/google/protobuf/issues/2019
Bug #835514 [libprotobuf-java] libprotobuf-java: junit and easymock 
dependencies should only be required for tests
Set Bug forwarded-to-address to 
'https://github.com/google/protobuf/issues/2019'.
> thanks
Stopping processing here.

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

Processed: Patch for the gcc-arm-none-eabi FTBFS

[Debian Bug Tracking System]

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

> tags 831142 +patch
Bug #831142 [src:gcc-arm-none-eabi] gcc-arm-none-eabi: FTBFS with GCC 6: 
cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)' 
redeclared inline with 'gnu_inline' attribute
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#831142: Patch for the gcc-arm-none-eabi FTBFS

[Adrian Bunk]

tags 831142 +patch
thanks

Attached is the fix from upstream 4.9.4 for the gcc-arm-none-eabi FTBFS.

cu
Adrian

-- 

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

>From 8c3fa311caa86f61b4e28d1563d1110b44340fb2 Mon Sep 17 00:00:00 2001
From: edlinger 
Date: Thu, 25 Feb 2016 15:36:41 +
Subject: 2016-02-25  Bernd Edlinger  

Backported from mainline
2016-02-19  Jakub Jelinek  
Bernd Edlinger  

* Make-lang.in: Invoke gperf with -L C++.
* cfns.gperf: Remove prototypes for hash and libc_name_p
inlines.
* cfns.h: Regenerated.
* except.c (nothrow_libfn_p): Adjust.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-4_9-branch@233721 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/cp/Make-lang.in b/gcc/cp/Make-lang.in
index bd1c1d7..a0ea0d4 100644
--- a/src/gcc/cp/Make-lang.in
+++ b/src/gcc/cp/Make-lang.in
@@ -111,7 +111,7 @@ else
 # deleting the $(srcdir)/cp/cfns.h file.
 $(srcdir)/cp/cfns.h:
 endif
-	gperf -o -C -E -k '1-6,$$' -j1 -D -N 'libc_name_p' -L ANSI-C \
+	gperf -o -C -E -k '1-6,$$' -j1 -D -N 'libc_name_p' -L C++ \
 		$(srcdir)/cp/cfns.gperf --output-file $(srcdir)/cp/cfns.h
 
 #
diff --git a/gcc/cp/cfns.gperf b/gcc/cp/cfns.gperf
index 05ca753..d9b16b8 100644
--- a/src/gcc/cp/cfns.gperf
+++ b/src/gcc/cp/cfns.gperf
@@ -1,3 +1,5 @@
+%language=C++
+%define class-name libc_name
 %{
 /* Copyright (C) 2000-2014 Free Software Foundation, Inc.
 
@@ -16,14 +18,6 @@ for more details.
 You should have received a copy of the GNU General Public License
 along with GCC; see the file COPYING3.  If not see
 .  */
-#ifdef __GNUC__
-__inline
-#endif
-static unsigned int hash (const char *, unsigned int);
-#ifdef __GNUC__
-__inline
-#endif
-const char * libc_name_p (const char *, unsigned int);
 %}
 %%
 # The standard C library functions, for feeding to gperf; the result is used
diff --git a/gcc/cp/cfns.h b/gcc/cp/cfns.h
index c845ddf..65801d1 100644
--- a/src/gcc/cp/cfns.h
+++ b/src/gcc/cp/cfns.h
@@ -1,5 +1,5 @@
-/* ANSI-C code produced by gperf version 3.0.3 */
-/* Command-line: gperf -o -C -E -k '1-6,$' -j1 -D -N libc_name_p -L ANSI-C cfns.gperf  */
+/* C++ code produced by gperf version 3.0.4 */
+/* Command-line: gperf -o -C -E -k '1-6,$' -j1 -D -N libc_name_p -L C++ --output-file cfns.h cfns.gperf  */
 
 #if !((' ' == 32) && ('!' == 33) && ('"' == 34) && ('#' == 35) \
   && ('%' == 37) && ('&' == 38) && ('\'' == 39) && ('(' == 40) \
@@ -28,7 +28,7 @@
 #error "gperf generated tables don't work with this execution character set. Please report a bug to ."
 #endif
 
-#line 1 "cfns.gperf"
+#line 3 "cfns.gperf"
 
 /* Copyright (C) 2000-2014 Free Software Foundation, Inc.
 
@@ -47,25 +47,18 @@ for more details.
 You should have received a copy of the GNU General Public License
 along with GCC; see the file COPYING3.  If not see
 .  */
-#ifdef __GNUC__
-__inline
-#endif
-static unsigned int hash (const char *, unsigned int);
-#ifdef __GNUC__
-__inline
-#endif
-const char * libc_name_p (const char *, unsigned int);
 /* maximum key range = 391, duplicates = 0 */
 
-#ifdef __GNUC__
-__inline
-#else
-#ifdef __cplusplus
-inline
-#endif
-#endif
-static unsigned int
-hash (register const char *str, register unsigned int len)
+class libc_name
+{
+private:
+  static inline unsigned int hash (const char *str, unsigned int len);
+public:
+  static const char *libc_name_p (const char *str, unsigned int len);
+};
+
+inline unsigned int
+libc_name::hash (register const char *str, register unsigned int len)
 {
   static const unsigned short asso_values[] =
 {
@@ -122,14 +115,8 @@ hash (register const char *str, register unsigned int len)
   return hval + asso_values[(unsigned char)str[len - 1]];
 }
 
-#ifdef __GNUC__
-__inline
-#ifdef __GNUC_STDC_INLINE__
-__attribute__ ((__gnu_inline__))
-#endif
-#endif
 const char *
-libc_name_p (register const char *str, register unsigned int len)
+libc_name::libc_name_p (register const char *str, register unsigned int len)
 {
   enum
 {
diff --git a/gcc/cp/except.c b/gcc/cp/except.c
index 221971a..32340f5 100644
--- a/src/gcc/cp/except.c
+++ b/src/gcc/cp/except.c
@@ -1030,7 +1030,8 @@ nothrow_libfn_p (const_tree fn)
  unless the system headers are playing rename tricks, and if
  they are, we don't want to be confused by them.  */
   id = DECL_NAME (fn);
-  return !!libc_name_p (IDENTIFIER_POINTER (id), IDENTIFIER_LENGTH (id));
+  return !!libc_name::libc_name_p (IDENTIFIER_POINTER (id),
+   IDENTIFIER_LENGTH (id));
 }
 
 /* Returns nonzero if an exception of type FROM will be caught by a
-- 
2.9.3

Processed: your mail

[Debian Bug Tracking System]

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

> block 832410 by 835546
Bug #832410 [python-clang-4.0,python-lldb-4.0] python-clang-4.0, 
python-lldb-4.0: missing Breaks+Replaces against the corresponding python-*-3.9 
packages
832410 was not blocked by any bugs.
832410 was not blocking any bugs.
Added blocking bug(s) of 832410: 835546
> thanks
Stopping processing here.

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

Bug#829173: swiginac: FTBFS

[peter green]

Apparently ginac requires C++11 now, which you need to manually enable with GCC 
5.
gcc-6 is now the default and has C++11 enabled by default, so this is no 
longer an issue.


Unfortunately the packege now fails to build for a different reason. 
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/swiginac_1.5.1.1-2.rbuild.log


x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-oH9M6v/python2.7-2.7.12=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c swiginac_wrap.cpp -o 
build/temp.linux-x86_64-2.7/swiginac_wrap.o
cc1plus: warning: command line option '-Wstrict-prototypes' is valid for C/ObjC 
but not for C++
swiginac_wrap.cpp: In function 'GiNaC::ex GiNaC_basic_normal__SWIG_2(const 
GiNaC::basic*, int)':
swiginac_wrap.cpp:5625:41: error: no matching function for call to 
'GiNaC::ex::normal(int&)'
 return self->eval().normal(level);
 ^
In file included from /usr/include/ginac/ginac.h:30:0,
 from swiginac_wrap.cpp:3305:
/usr/include/ginac/ex.h:186:5: note: candidate: GiNaC::ex GiNaC::ex::normal() 
const
  ex normal() const;
 ^~
/usr/include/ginac/ex.h:186:5: note:   candidate expects 0 arguments, 1 provided

Processed: your mail

[Debian Bug Tracking System]

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

> tag 811323 + pending
Bug #811323 [src:mugshot] mugshot: FTBFS: ImportError: No module named 'gi'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 820186

[Debian Bug Tracking System]

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

> tags 820186 + pending
Bug #820186 [src:kdevelop-python] kdevelop-python: build-depends on 
python3.4-dev which is going away
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#835514: libprotobuf-java: junit and easymock dependencies should only be required for tests

[Sebastiaan Couwenberg]

I've tested the libprotobuf-java reverse dependencies and unfortunately 
most are using maven and are affected by this issue, I've marked those 
packages accordingly.


Kind Regards,

Bas

Processed: Additional affected packages

[Debian Bug Tracking System]

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

> affects 835514 src:bookkeeper src:projectreactor src:netty-3.9
Bug #835514 [libprotobuf-java] libprotobuf-java: junit and easymock 
dependencies should only be required for tests
Added indication that 835514 affects src:bookkeeper, src:projectreactor, and 
src:netty-3.9
> affects 835514 src:netty src:libspring-java
Bug #835514 [libprotobuf-java] libprotobuf-java: junit and easymock 
dependencies should only be required for tests
Added indication that 835514 affects src:netty and src:libspring-java
> thanks
Stopping processing here.

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

Processed: Debian bugs: #834979m #835540

[Debian Bug Tracking System]

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

> found 835540 log4cpp/1.1.1-1
Bug #835540 [src:log4cpp] Missing dependencies at linktime
Marked as found in versions log4cpp/1.1.1-1.
> severity 834979 important
Bug #834979 [src:bitz-server] bitz-server: FTBFS in testing (linking error)
Severity set to 'important' from 'serious'
> block 834979 by 835540 
Bug #834979 [src:bitz-server] bitz-server: FTBFS in testing (linking error)
834979 was not blocked by any bugs.
834979 was not blocking any bugs.
Added blocking bug(s) of 834979: 835540
> --
Stopping processing here.

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

Processed: found 822787 in 0.99.22.4-1

[Debian Bug Tracking System]

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

> found 822787 0.99.22.4-1
Bug #822787 [src:quagga] quagga: CVE-2016-4049: Missing size check in 
bgp_dump_routes_func in bgpd/bgp_dump.c allowing DoS
Marked as found in versions quagga/0.99.22.4-1.
> thanks
Stopping processing here.

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

Bug#835540: Missing dependencies at linktime

[Jörg Frings-Fürst]

Source: log4cpp
Version: Missing Dependencies
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

at link time log4cpp produce this errors:


libtool: link: g++ -g -O2 -fdebug-prefix-map=/build/bitz-server-1.0.0=. -fPIE
- -fstack-protector-strong -Wformat -Werror=format-security -fPIE -pie -Wl,-z
- -Wl,relro -Wl,-z -Wl,now -o .libs/bitz-server main.o bitz-server.o
bitz/exception.o bitz/manager_exception.o bitz/config.o bitz/logger.o
bitz/util.o bitz/manager.o bitz/worker.o bitz/request_handler.o
bitz/options_request_handler.o bitz/reqmod_request_handler.o
bitz/respmod_request_handler.o bitz/modifier.o -Wl,--export-dynamic  -ldl
../lib/icap/.libs/libicap.so -lconfig++ -llog4cpp -lnsl /usr/lib/x86_64-linux-
gnu/libpsocksxx.so
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/liblog4cpp.so:
undefined reference to `pthread_key_create'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/liblog4cpp.so:
undefined reference to `pthread_getspecific'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/liblog4cpp.so:
undefined reference to `pthread_key_delete'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/liblog4cpp.so:
undefined reference to `pthread_setspecific'
collect2: error: ld returned 1 exit status


This looks like missing dependencies from log4cpp.

CU
Jörg



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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXwJeyAAoJEAn4nzyModJdz2gQAIyx2uSvUofq66c5YT49UDv7
O0UX0D5eSA+DfiDYq6PDwBM1F7lsRaiwoQdFosN1K+nNS5Hf3ujz4gaSx9q1bXcy
zmuD3ZvZxA0IL1b1736bKtFGeEyOxldkm22F3aqt9u3w/NIMPFm4zzfO4KgstREE
r0w3EjpD+Ao+I0j0lR/8uSQ7vOhxEuA8so8dBitjulBwPbYnuGL+T8sudX0SUI/C
T5Fl2BFkNnIHwPn5wG1i/9WRG1ObqDQq9MFJ4DmraUc5JfLKmGwNeQg9ZZMEeSWh
52Omv/k8Phq1Mxdhab9bSDK1Jmuj4JtJyD2Z3woRkjqjr//X6biyzSIDRzm5Mfg4
LtxFzFK1zLqZxtQBuWt7NxtYuhZxv3recOSZbepDW7y+10IICvoPUWfeFTs4+OSu
f3QzD0S1uAgLVumGjYAIOJ2x72GlopuYaoM2NjTDxntaQu7YpcZdKXoHMEdbHxYy
Nq8FSAfgiGp1ng+OQw7J2tyAKNVwWpjyC4twWql3TBgbMhrLe1ZtIiNHkDyLK/RI
diCmP2Yz0ZPX2EU5dP5M9TxNfem+tQrqUtOViteEajy5vj5i8/J62zAV72+LSI5Y
PyqgotgwkxRw0hN2b9WreHYu6rUmDMt9O9XjVSwPc1JUwJh+bzPbIqoEb+/xxcmm
HnpgZElB/ZHvwPJwlvdm
=YS19
-END PGP SIGNATURE-

Bug#824226: Info received (openjdk-8-jre: ATK bridge causes segfault when loading JR)

[Samuel Thibault]

Hello,

Peter Keel, on Fri 26 Aug 2016 12:32:12 +0200, wrote:
> Downgraded to these: 
> 
> libatk-bridge2.0-0_2.14.0-2_amd64.deb
> libatk-wrapper-java_0.30.5-1_all.deb
> libatk-wrapper-java-jni_0.30.5-1_amd64.deb

Well, these are very old, and have other issues.  The java wrapping
has been quite revamped since then, so it's not useful to debug with
those.  Please instead keep the latest versions of libatk-wrapper-java
(0.33.3-8), and to avoid the issue, comment the following line in
java-8-openjdk/accessibility.properties:

assistive_technologies=org.GNOME.Accessibility.AtkWrapper

> Now Java works again. 

Which java application? The java applications that I test do work
fine.  Please be specific, otherwise we can't reproduce bugs and fix
them.  For now, in my list of applications I haven't looked after yet is
MediaThekView, from bug #787955 .

> Either way, the accessibility-team is responsible. 

But it can't do much without precise feedback as to how to reproduce
bugs.

Samuel

Processed: tagging 833950, retitle 833950 to libportaudio2: brltty-espeak stops working with libasound2 1.1.2-1

[Debian Bug Tracking System]

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

> tags 833950 - pending
Bug #833950 [portaudio19] libasound2: brltty-espeak stops working with 1.1.2-1
Removed tag(s) pending.
> retitle 833950 libportaudio2: brltty-espeak stops working with libasound2 
> 1.1.2-1
Bug #833950 [portaudio19] libasound2: brltty-espeak stops working with 1.1.2-1
Changed Bug title to 'libportaudio2: brltty-espeak stops working with 
libasound2 1.1.2-1' from 'libasound2: brltty-espeak stops working with 1.1.2-1'.
> thanks
Stopping processing here.

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

Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Samuel Thibault]

Control: reassign -1 portaudio19

Hello,

Chris Brannon, on Thu 18 Aug 2016 11:32:40 -0700, wrote:
> I'm almost certain that the problem lies with portaudio, rather than
> libasound.  It's described in my message to the portaudio list, found
> here:
> 
> https://lists.columbia.edu/pipermail/portaudio/2016-August/000599.html

And the discussion shows that the issue really does seem to lie in
there. portaudio maintainers, could you include the upstream patch from

https://lists.columbia.edu/pipermail/portaudio/2016-August/000623.html

?

Without it, blind users using a screen reader have their screen reader
hang every few minutes, making the system basically unusable.

Thanks,
Samuel

Bug#835085: noweb: FTBFS: build-depends on iconc which didn't work and it was removed

[Hubert Chathi]

On Mon, 22 Aug 2016 11:53:51 +0200 (CEST), Santiago Vila  said:

> This package does no longer build from source because the iconc
> package does no longer exist (I'm not providing a build log, but this
> is very easy to check).
[...]
> So, I believe the attached patch should fix the FTBFS bug (but I have
> not actually tested it). Please give it a try.

Thanks.  The patch seems to work fine.  Can you sponsor an upload for
me?  My key was removed from the keyring due to being weak, and I
haven't managed to get a new one in.  The fixed packages are available
at: https://debian.uhoreg.ca/unstable/ (In addition to the diff you
provided, I also updated the upstream's homepage.)

Thanks again.

-- 
Hubert Chathi  -- Jabber: hub...@uhoreg.ca
PGP/GnuPG key: 4096R/113A1368 https://www.uhoreg.ca/
Fingerprint: F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Processed: Re: Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 portaudio19
Bug #833950 [libasound2] libasound2: brltty-espeak stops working with 1.1.2-1
Bug reassigned from package 'libasound2' to 'portaudio19'.
No longer marked as found in versions alsa-lib/1.1.2-1.
Ignoring request to alter fixed versions of bug #833950 to the same values 
previously set

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

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Richard Hartmann]

I will package that soon(tm), maybe tonight. Sorry for missing that.

Richard

Sent by mobile; excuse my brevity.

Bug#832841: yasat: FTBFS: Tests failures

[Adrian Bunk]

On Fri, Jul 29, 2016 at 10:53:35AM +0200, LABBE Corentin wrote:
> Hello

Hi Corentin,

> The major problem seems the absence of home directory and not dying if 
> TEMPYASATDIR does not exists.
> I will try to solve it by a fallback to /tmp/

can you upload a fix for this RC bug in your package?

> Strange that it fails only on amd64 in that case.

I'd guess your (binary-all) package is confirmed to FTBFS when trying to 
build it on amd64 without home directory.

I don't see any indication that this is confirmed to work on other 
platforms, this simply looks untested (and likely broken on all 
platforms).

> Regards

Thanks
Adrian

-- 

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

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Yaroslav Halchenko]

On Fri, 26 Aug 2016, Richard Hartmann wrote:

>Jftr, if I can help with a new package or build, do let me know.

well -- there was also a new release of annex since last version in sid

6.20160808

FWIW I just verified that snapshot past it (current master) builds  fine
on stretch

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#834677: marked as done (refcard: FTBFS in testing (xelatex compilation failed))

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 18:49:17 +
with message-id 
and subject line Bug#834677: fixed in refcard 9.0.2
has caused the Debian Bug report #834677,
regarding refcard: FTBFS in testing (xelatex compilation failed)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
USE_DBLATEX=1 LC_ALL=en_US.utf8 /usr/bin/make -C . CFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CXXFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
make[1]: Entering directory '/<>'
cp -f entries.dbk entries-en.dbk
po4a-translate --format docbook --keep 0 -m entries.dbk -p po4a/bg.po -l 
entries-bg.dbk
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = "en_US.utf8",
LANG = (unset)

[... snipped ...]

refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Extra }, or forgotten $.
refcard-ja.dbk.tex:132: leading text: }&
refcard-ja.dbk.tex:132: Missing } inserted.
refcard-ja.dbk.tex:132: leading text: }&
Unexpected error occured
Error: xelatex compilation failed
Makefile:76: recipe for target 'refcard-ja-a4.s.pdf' failed
make[1]: *** [refcard-ja-a4.s.pdf] Error 1
rm refcard-pt.dbk refcard-bg-a4.fo refcard-pt-a4.s.pdf refcard-ml-a4.s.pdf 
refcard-ml.dbk refcard-pt-a4.t.pdf refcard-pt-a4.fo refcard-ja.dbk 
refcard-en-a4.t.pdf refcard-ml-a4.t.pdf refcard-en-a4.s.pdf refcard-bg-a4.s.pdf 
refcard-en.dbk refcard-bg.dbk refcard-ml-a4.fo refcard-en-a4.fo 
refcard-bg-a4.t.pdf refcard-ja-a4.fo
make[1]: Leaving directory '/<>'
/usr/share/cdbs/1/class/makefile.mk:77: recipe for target 
'debian/stamp-makefile-build' failed
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.
--- End Message ---
--- Begin Message ---
Source: refcard
Source-Version: 9.0.2

We believe that the bug you reported is fixed in the latest version of

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Richard Hartmann]

Jftr, if I can help with a new package or build, do let me know.

Richard

Sent by mobile; excuse my brevity.

Bug#811986: qwtplot3d: FTBFS with GCC 6: symbol changes

[Adrian Bunk]

On Wed, Jul 20, 2016 at 05:24:06PM -0400, Scott Kitterman wrote:
> On Tuesday, January 19, 2016 08:13:48 PM you wrote:
> > Package: qwtplot3d
> > Version: 0.2.7+svn191-9
> > Severity: important
> > User: debian-...@lists.debian.org
> > Usertags: ftbfs-gcc-6 gcc-6-symbols
> > 
> > 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
> > 
> > ...
> > 
> > > dpkg-gensymbols: warning: some symbols or patterns disappeared in the
> > > symbols file: see diff output below dpkg-gensymbols: warning:
> > > debian/libqwtplot3d-qt4-0v5/DEBIAN/symbols doesn't match completely
> > > debian/libqwtplot3d-qt4-0v5.symbols ---
> > > debian/libqwtplot3d-qt4-0v5.symbols
> > > (libqwtplot3d-qt4-0v5_0.2.7+svn191-9_amd64) +++
> > > dpkg-gensymbolsFodDeO 2016-01-19 23:39:20.896195539 +
> ...
> 
> This is trivially fixable once GCC-6 is default, so removal from testing now 
> makes no sense.

Hi Scott,

can you upload a fix now that gcc 6 is the default?

> No idea how failing to build with a non-default compiler is 
> RC in any case.

It was made RC in preparation of changing the default compiler.

> Scott K

Thanks
Adrian

-- 

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

Processed: block 835170 with 835514

[Debian Bug Tracking System]

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

> block 835170 with 835514
Bug #835170 [release.debian.org] transition: protobuf
835170 was blocked by: 835425 835433 835427 835266 835430 822380 835290 835429 
835435 835302 809290 811917
835170 was not blocking any bugs.
Added blocking bug(s) of 835170: 835514
> thanks
Stopping processing here.

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

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Yaroslav Halchenko]

On Fri, 26 Aug 2016, Yaroslav Halchenko wrote:
> > Note 2: There is at least another package which broke after new git entered 
> > testing.
> > It's git-build-recipe, Bug #835526. Maybe there is a common reason for
> > both packages to fail.

> FWIW -- #835526 is probably unrelated to this issue.  We (and git-annex
> author) were aware of "merge of unrelated branches" change in behavior
> in git awhile back and both annex and datalad were read for it ;)

just to insult myself even more:  we still do have some tests failing
(in the datalad new codebase, so unrelated to this FTBFS) due to "merge
unrelated histories"... heh... so thanks again for alarming me about
new git version ;)

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#835514: libprotobuf-java: junit and easymock dependencies should only be required for tests

[Sebastiaan Couwenberg]

On Fri, 26 Aug 2016 14:36:00 +0200 Markus Koschany wrote:

thanks for fixing #835358 so quickly. Unfortunately there is another
issue with the pom.xml file now. java/core/pom.xml lists junit and
easymock artifacts as dependencies but libprotobuf-java does not
depend on these packages. This causes build failures like [1].

libprotobuf-java should either depend on the respective packages or
change the scope to test again as in earlier versions. I think the
latter solution is preferable because junit and easymock are only
needed for tests. If you take a look at version 2.6.1, you will see
that scope test was used before. [2] I don't know why they changed this
but it looks like an upstream bug to me.

I'm attaching a patch that resolves the issue and restores the old
behavior again.


I agree with Markus' assessment that restoring the test scope is 
preferable. It looks like the restructuring in [0] was overly ambitious 
in removing both the version and scope properties.


[0] 
https://github.com/google/protobuf/commit/49efe9d7db877022e76375df2d4daadab98619b6


Kind Regards,

Bas

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

Processed: affects 835514

[Debian Bug Tracking System]

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

> affects 835514 src:libphonenumber src:osmosis
Bug #835514 [libprotobuf-java] libprotobuf-java: junit and easymock 
dependencies should only be required for tests
Added indication that 835514 affects src:libphonenumber and src:osmosis
> thanks
Stopping processing here.

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

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Yaroslav Halchenko]

On Fri, 26 Aug 2016, Yaroslav Halchenko wrote:
> > > Thank you Santiago for the report!  I believe it is due to outdated
> > > git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
> > > I will request gb for it -- could have been a spurious/toolchain issue.
> > > CCing git-annex Debian maintainer

> > Note: If you rely on a specific feature of a package which has not
> > reached testing yet, consider using a versioned build-depends.

> > The script which migrates packages to testing (britney) does not take
> > build-depends in account yet, but at least in this case I would
> > get an error like "build-dependencies not meat, can't build package"
> > which is usually better than a FTBFS.

> > Note 2: There is at least another package which broke after new git entered 
> > testing.
> > It's git-build-recipe, Bug #835526. Maybe there is a common reason for
> > both packages to fail.

> FWIW -- #835526 is probably unrelated to this issue.  We (and git-annex
> author) were aware of "merge of unrelated branches" change in behavior
> in git awhile back and both annex and datalad were read for it ;)

ok -- confirming. also confirming that I have misdiagnosed the problem of
failing datalad unittests -- it has nothing to do with annex
compatibility, it happened due to change of the output from git in case
of absent changes to the worktree:

$> git --version   
git version 2.9.3
$> git status   
On branch annex/direct/master
nothing to commit, working tree clean

$> /usr/lib/git-annex.linux/git --version
git version 2.8.1
$> /usr/lib/git-annex.linux/git status   
On branch annex/direct/master
nothing to commit, working directory clean


so instead of 'working directory' now it reports 'working tree' and our test
was too rigid.  It will be fixed in the next datalad release (after I address
one more issue which came about seems with new git).  For now datalad should be
pruned away from testing ;)

Thanks and cheers!
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Processed: Re: Bug#835532: default config directory is /etc/postfix, not /etc/postgrey

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #835532 [postgrey] default config directory is /etc/postfix, not 
/etc/postgrey
Severity set to 'serious' from 'important'
> retitle -1 default config dir change from /etc/postgrey to /etc/postfix not 
> handled
Bug #835532 [postgrey] default config directory is /etc/postfix, not 
/etc/postgrey
Changed Bug title to 'default config dir change from /etc/postgrey to 
/etc/postfix not handled' from 'default config directory is /etc/postfix, not 
/etc/postgrey'.

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

Bug#751121: Please fix "FIXME" statements in copyright file

[Jonas Smedegaard]

Quoting Luca Falavigna (2014-06-10 16:40:39)
> Your debian/copyright file contains lots of FIXMEs.

Status update: Most FIXMEs have been addressed now, through analysis of 
the history of those files (documented as comments for each file in 
debian/copyright).


Remaining are 2 FIXMEs.

One is this:

> For example there is an entry for
>   distrib/initscripts/rc.atalk.suse.tmpl
> but this file does not exist. The corresponding file
>   distrib/initscripts/rc.atalk.suse-sysv.tmpl
> contains just the line:
>  Copyright (c) 1996-2001 SuSE GmbH Nuernberg, Germany.  All rights reserved.
> How do you know that Debian is allowed to distribute it?

...which is dropped in later upstream releases, so will go away when we 
upgrade.

Last remaining issue is this: etc/afpd/fce_api.c

That one I have now passed upstream: 
https://github.com/Netatalk/Netatalk/issues/74


 - Jonas

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

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


signature.asc
Description: signature

Processed: bug 751121 is forwarded to https://github.com/Netatalk/Netatalk/issues/74

[Debian Bug Tracking System]

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

> forwarded 751121 https://github.com/Netatalk/Netatalk/issues/74
Bug #751121 [src:netatalk] Please fix "FIXME" statements in copyright file
Set Bug forwarded-to-address to 
'https://github.com/Netatalk/Netatalk/issues/74'.
> thanks
Stopping processing here.

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

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Yaroslav Halchenko]

On Fri, 26 Aug 2016, Santiago Vila wrote:

> On Fri, Aug 26, 2016 at 12:22:20PM -0400, Yaroslav Halchenko wrote:
> > Thank you Santiago for the report!  I believe it is due to outdated
> > git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
> > I will request gb for it -- could have been a spurious/toolchain issue.
> > CCing git-annex Debian maintainer

> Note: If you rely on a specific feature of a package which has not
> reached testing yet, consider using a versioned build-depends.

> The script which migrates packages to testing (britney) does not take
> build-depends in account yet, but at least in this case I would
> get an error like "build-dependencies not meat, can't build package"
> which is usually better than a FTBFS.

> Note 2: There is at least another package which broke after new git entered 
> testing.
> It's git-build-recipe, Bug #835526. Maybe there is a common reason for
> both packages to fail.

FWIW -- #835526 is probably unrelated to this issue.  We (and git-annex
author) were aware of "merge of unrelated branches" change in behavior
in git awhile back and both annex and datalad were read for it ;)

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#834999: marked as done (YAML::XS generates broken multiline strings)

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 18:04:04 +
with message-id 
and subject line Bug#834999: fixed in libyaml-libyaml-perl 0.63-1
has caused the Debian Bug report #834999,
regarding YAML::XS generates broken multiline strings
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.)


-- 
834999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libyaml-libyaml-perl
Version: 0.41-6+b1
Severity: grave

YAML::XS adds an extra \n at the end of each line.
The YAML module cannot read the generated files.

Test case attached.

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

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

Versions of packages libyaml-libyaml-perl depends on:
ii  libc6   2.23-4
ii  perl5.22.2-3
ii  perl-base [perlapi-5.22.1]  5.22.2-3

libyaml-libyaml-perl recommends no packages.

libyaml-libyaml-perl suggests no packages.

-- no debconf information

-- 
ciao,
Marco
#!/usr/bin/perl

use v5.22;
use warnings;
use strict;

use File::Slurp;
use YAML::XS;

$_ = qq[line1
line2

line3
end
];

my $yaml = Dump($_);
print $yaml;
write_file('testyaml-data', $yaml);

#!/usr/bin/perl

use v5.22;
use warnings;
use strict;

use File::Slurp;
use YAML;

my $yaml = read_file('testyaml-data');
print $yaml;
print Load($yaml);



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libyaml-libyaml-perl
Source-Version: 0.63-1

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libyaml-libyaml-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Aug 2016 19:46:11 +0200
Source: libyaml-libyaml-perl
Binary: libyaml-libyaml-perl
Architecture: source
Version: 0.63-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 834999
Description: 
 libyaml-libyaml-perl - Perl interface to libyaml, a YAML implementation
Changes:
 libyaml-libyaml-perl (0.63-1) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * New upstream releases 0.43, 0.44, 0.45.
   * Update copyright years. Drop information about removed files.
   * Install new CONTRIBUTING file.
   * Add debian/upstream/metadata.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * Imported upstream version 0.52.
   * Mark package as autopkgtest-able.
 .
   * Import upstream version 0.60.
   * Drop a bunch of patches which all have been applied upstream.
   * Update years of upstream and packaging copyright.
 .
   * Import upstream version 0.62
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Jonathan Yu from Uploaders. Thanks for your work!
   * Remove Ryan Niebur from Uploaders. Thanks for your work!
 .
   * Import upstream version 0.63
   * Set bindnow linker flag in debian/rules.
   * Declare compliance with Debian Policy 3.9.8.
   * Add lintian override for embedded libyaml.
 .
   * One of those upstream releases since 0.41 also closes: #834999
 according to the test cases Marco d'Itri provided in the bug report.
Checksums-Sha1: 
 5f80e49b19a7c21d3613e371fdfea3f1946a37d3 2256 libyaml-libyaml-perl_0.63-1.dsc
 dbccd6b04ec8d9add97212e4ee2364c1e718187c 143075 
libyaml-libyaml-perl_0.63.orig.tar.gz
 a79b1edd75409ca9ffc5ae8b0ada64a1f66ec682 5424 
libyaml-libyaml-perl_0.63-1.debian.tar.xz
Checksums-Sha256: 
 

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Yaroslav Halchenko]

On Fri, 26 Aug 2016, Santiago Vila wrote:

> On Fri, Aug 26, 2016 at 12:22:20PM -0400, Yaroslav Halchenko wrote:
> > Thank you Santiago for the report!  I believe it is due to outdated
> > git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
> > I will request gb for it -- could have been a spurious/toolchain issue.
> > CCing git-annex Debian maintainer

> Note: If you rely on a specific feature of a package which has not
> reached testing yet, consider using a versioned build-depends.

yeah yeah... we have it all versioned ;)

Build-Depends:
 git-annex (>= 6.20160425) | git-annex-standalone (>= 6.20160425),
Depends:
 git-annex (>= 6.20160425) | git-annex-standalone (>= 6.20160425),

and I have checked -- backport build for stretch did install annex 6.20160511-1
and build passed. So ...

> Note 2: There is at least another package which broke after new git entered 
> testing.
> It's git-build-recipe, Bug #835526. Maybe there is a common reason for
> both packages to fail.

it might indeed be a git issue OR may be annex 6.20160511-1 incompatibility
with it ... indeed -- if I switch from git-annex-standalone build (built
and using older git as in stretch in july (2.8.1)), tests do fail for me
locally!

I will check a git-annex snapshot now, and report back...

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#835536: request-tracker4: FTBFS with gnupg 2.1

[Dominic Hargreaves]

Source: request-tracker4
Version: 4.2.12-6
Severity: serious
Justification: FTBFS

Now that libgnupg-interface-perl has been fixed to use gpg1 (
see #834281) request-tracker4 still FTBFS because it configures
GnuPG::Interface to use 'gpg' as the binary anyway. 

I intend to patch out this functionality so that request-tracker4
can work without hardcoding the path to gpg (which will avoid the
need to fiddle with this setting for backports).

Dominic.

Bug#835535: fails to start after upgrade: default dbdir change not handled

[Sébastien Villemot]

Package: postgrey
Version: 1.36-2
Severity: serious

Dear Maintainer,

After upgrade to 1.36-2, postgrey fails to start with the following message:

 FATAL: ERROR: can't open lock file: /var/spool/postfix/postgrey/postgrey.lock

This is because the default database directory was changed from
/var/lib/postgrey to /var/spool/postfix/postgrey, but the upgrade is not
properly handled by the maintainer scripts.

Please either revert the change or adapt the maintainer scripts.

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature

Bug#834999: embedded libyaml (was: Bug#834999: YAML::XS generates broken multiline strings)

[gregor herrmann]

On Fri, 26 Aug 2016 09:26:22 +0300, Niko Tyni wrote:

> > The problem is that we have a lintian ftp-master autoreject problem:
> > E: libyaml-libyaml-perl: embedded-library 
> > usr/lib/perl5/auto/YAML/XS/LibYAML/LibYAML.so: libyaml
> 
> Making it possible to use a system libyaml is discussed in
>  https://github.com/ingydotnet/yaml-libyaml-pm/issues/49
> and convincing upstream would be much better than doing so against their
> wish, particularly as this would create a functionality difference.

Right.
 
> The embedded libyaml is not a regression (see #664224) and not a release
> critical issue as far as I am aware. The lintian tag is overriddable.
> So I suggest we override the lintian error in order to fix this RC bug.

Ok, done.

Thanks for your help!


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones


signature.asc
Description: Digital Signature

Bug#835526: git-build-recipe: FTBFS in testing (broken by new git)

[Colin Watson]

On Fri, Aug 26, 2016 at 03:53:03PM +, Santiago Vila wrote:
> ERROR: 
> gitbuildrecipe.tests.test_recipe.BuildTreeTests.test_build_tree_merge_unrelated
[...]
> This used to build ok, so this failure seems related to git 2.9.3,
> which is in testing since a few days.

Thanks for your report.  I've proposed
https://code.launchpad.net/~cjwatson/git-build-recipe/+git/git-build-recipe/+merge/304105
to fix this.

-- 
Colin Watson   [cjwat...@ubuntu.com]

Bug#834281: FTBFS with gnupg2

[intrigeri]

Hi,

gregor herrmann:
> It seems we have (had) 3 packages where tests fails with gnupg2:

> #834522 libgnupg-perl
> #835075 libmail-gnupg-perl
> #834281 libgnupg-interface-perl

> The third one was fixed by intri by making it use gnupg1. Should we
> do the same for the two other bugs?

I'm in favour of doing the same for GnuPG bindings that have important
enough reverse dependencies, when there's a chance that the library is
updated to support modern GnuPG one of these days.

FWIW, I'll probably have GnuPG::Interface work with GnuPG v2.x sooner
or later, but I am not using any of the other libraries.

Cheers,
-- 
intrigeri

Processed: bug 835075 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=117239

[Debian Bug Tracking System]

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

> forwarded 835075 https://rt.cpan.org/Ticket/Display.html?id=117239
Bug #835075 [src:libmail-gnupg-perl] libmail-gnupg-perl: FTBFS: Failed 1/10 
test programs. 0/4 subtests failed.
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=117239'.
> thanks
Stopping processing here.

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

Bug#834281: FTBFS with gnupg2

[gregor herrmann]

It seems we have (had) 3 packages where tests fails with gnupg2:

#834522 libgnupg-perl
#835075 libmail-gnupg-perl
#834281 libgnupg-interface-perl

The third one was fixed by intri by making it use gnupg1. Should we
do the same for the two other bugs?


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Beatles


signature.asc
Description: Digital Signature

Processed: Bug#835413: pygobject: wrong enum to hash conversion on 64-bit big endian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #835413 [pygobject] pygobject: wrong enum to hash conversion on 64-bit big 
endian
Added tag(s) patch.

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

Bug#835413: pygobject: wrong enum to hash conversion on 64-bit big endian

[Aurelien Jarno]

control: tag -1 + patch

On 2016-08-25 14:16, Aurelien Jarno wrote:
> On 2016-08-25 09:15, Aurelien Jarno wrote:
> > I have tried to debug the issue, and I came to the same conclusion. The
> > problem happens in the test-py-lookup.py test when creating a schema
> > with Secret.Schema.new. The schema is defined in python using a
> > dictionary which is then transformed by gobject-introspection into a
> > to a GHashTable in order to call secret_schema_newv. This hash table
> > maps strings to enum (ie a 32-bit value).
> > 
> > In practice the hash table stores two gpointers, so the 32-bit value
> > has to be converted first to a pointer using GINT_TO_POINTER and when
> > read again converted with GPOINTER_TO_INT. The latter is correctly done
> > in libsecret, but the former doesn't seems to be done in
> > gobject-introspection. Therefore on a 64-bit little endian system, the
> > lower 32 bits are stored correctly, but the high 32 bits are left
> > unchanged as garbage. It's not a problem as GPOINTER_TO_INT just remove
> > this garbage. On a 64-bit big endian system, the value is stored on the
> > higher 32-bits, and the lower 32 bits are left unchanged as garbage.
> > Therefore GPOINTER_TO_INT just trash the value, just leaving the
> > garbage.
> > 
> > By changing the conversion in secret_schema_newv from
> >   type = GPOINTER_TO_INT (value);
> > to
> >   type = (gint)(((unsigned long) value) >> 32);
> > the testsuite is able to pass.
> > 
> > Of course this is not an acceptable patch and now we have to find where
> > in the whole gobject-introspection chain where to add the missing
> > GINT_TO_POINTER conversion.
> 
> The problem is actually in pygobject. enums are represented with a
> GI_TYPE_TAG_INTERFACE type, which corresponds to an "extended
> interface object". They are treated by _pygi_arg_to_hash_pointer (in
> gi/pygi-argument.c) as a pointer instead of a 32-bit value. The correct
> way to do that is to pass a GITypeInfo to the function so that it's
> possible to query the subtype of the GI_TYPE_TAG_INTERFACE type.
> 
> I am therefore cloning this bug and reassigning the clone to pygobject.
> I don't simply reassigning it as the /collection/delete-sync test is
> also failing, though it seems to not be fully reproducible and seems to
> also happen on other architectures (mipsel for example).
> 
> I have a dirty patch that works, I'll work on cleaning it so that it can
> be applied. It might take a few days.

Please find a patch attached. It fixes the test-py-lookup.py test in
libsecret so that it doesn't hang nor fail.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
From 8dde1d4951b71181193ab5278334eff1d6f998cb Mon Sep 17 00:00:00 2001
From: Aurelien Jarno 
Date: Fri, 26 Aug 2016 12:43:51 +0200
Subject: [PATCH] Fix list/hashtable enum <-> hash conversion on 64-bit big
 endian

glist and ghashtable objects both store pointers. Complex objects are
stored as pointers to the objects, but simpler objects like an integer
value are stored directly as a pointer, using for example the
GINT_TO_POINTER and GPOINTER_TO_INT macros.

This is done in pygobject with the _pygi_hash_pointer_to_arg and
_pygi_arg_to_hash_pointer functions. These functions handle the various
type of objects. However they consider that an enum, represented with the
GI_TYPE_TAG_INTERFACE type (extended interface object), are always a
pointer. This is wrong as it is often a 32-bit value. Therefore on 64-bit
big endian machines, the value is handle with the 2 32-bit parts swapped.

This patches fixes that by changing the second argument of both functions
from GITypeTag to GITypeInfo. This way the interface can be determined,
and the underlying storage type can also be determined. This currently
only handles enum and flags, leaving other types as pointers.
---
 gi/pygi-argument.c  | 32 
 gi/pygi-argument.h  |  4 ++--
 gi/pygi-hashtable.c |  8 
 gi/pygi-list.c  |  8 
 4 files changed, 38 insertions(+), 14 deletions(-)

diff --git a/gi/pygi-argument.c b/gi/pygi-argument.c
index e9bfe3b..db82be5 100644
--- a/gi/pygi-argument.c
+++ b/gi/pygi-argument.c
@@ -85,10 +85,32 @@ pygi_argument_to_gssize (GIArgument *arg_in,
 }
 }
 
+static GITypeTag
+_pygi_get_storage_type (GITypeInfo *type_info)
+{
+GITypeTag type_tag = g_type_info_get_tag (type_info);
+
+if (type_tag == GI_TYPE_TAG_INTERFACE) {
+GIBaseInfo *interface = g_type_info_get_interface (type_info);
+switch (g_base_info_get_type (interface)) {
+case GI_INFO_TYPE_ENUM:
+case GI_INFO_TYPE_FLAGS:
+type_tag = g_enum_info_get_storage_type ((GIEnumInfo *)interface);
+break;
+default:
+/* FIXME: we might have something to do for other types */
+break;
+}
+}
+return type_tag;
+}
+
 void
 

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Santiago Vila]

On Fri, Aug 26, 2016 at 12:22:20PM -0400, Yaroslav Halchenko wrote:
> Thank you Santiago for the report!  I believe it is due to outdated
> git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
> I will request gb for it -- could have been a spurious/toolchain issue.
> CCing git-annex Debian maintainer

Note: If you rely on a specific feature of a package which has not
reached testing yet, consider using a versioned build-depends.

The script which migrates packages to testing (britney) does not take
build-depends in account yet, but at least in this case I would
get an error like "build-dependencies not meat, can't build package"
which is usually better than a FTBFS.

Note 2: There is at least another package which broke after new git entered 
testing.
It's git-build-recipe, Bug #835526. Maybe there is a common reason for
both packages to fail.

Thanks.

Bug#835531: theano: FTBFS on amd64 (fail of test_csr_correct_output_faster_than_scipy)

[Daniel Stender]

Source: theano
Version: 0.8.2-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Current theano now fails also on amd64:


FAIL: test_csr_correct_output_faster_than_scipy 
(theano.sparse.tests.test_basic.test_structureddot)
--
Traceback (most recent call last):
  File "/build-1st/theano-0.8.2/theano/sparse/tests/test_basic.py", line 1218, 
in test_csr_correct_output_faster_than_scipy
scipy_time, overhead_rtol, overhead_tol))
AssertionError: (0.016754150390625, 0.015386821746826172, 0.012169837951660156, 
1.1, 0.002)

--
Ran 2995 tests in 17686.047s

FAILED (SKIP=113, failures=1)


DS

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

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

Bug#834679: marked as done (surefire: FTBFS in testing (1 required artifact is missing))

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 16:37:06 +
with message-id 
and subject line Bug#834679: fixed in surefire 2.17-3
has caused the Debian Bug report #834679,
regarding surefire: FTBFS in testing (1 required artifact is missing)
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.)


-- 
834679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:surefire
Version: 2.17-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
cd . && /usr/lib/jvm/default-java/bin/java -classpath 
/usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/maven-core.jar:/usr/share/java/maven-model.jar:/usr/share/java/maven-plugin-api.jar:/usr/share/java/maven-project.jar:/usr/share/java/plexus-utils.jar:/usr/share/java/plexus-container-default-alpha.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dpackage=surefire 
-Dversion=2.17 -buildfile debian/build.xml package 
Buildfile: /<>/debian/build.xml

package:
[mkdir] Created dir: 
/<>/surefire-grouper/target/generated-sources
   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 
/<>/surefire-grouper/src/main/javacc/category-expression.jj . . .
   [javacc] File "TokenMgrError.java" does not exist.  Will create one.

[... snipped ...]

 [java] 1) org.apache.commons:commons-lang3:jar:3.x
 [java] 
 [java]   Try downloading the file manually from the project website.
 [java] 
 [java]   Then, install it using the command: 
 [java]   mvn install:install-file -DgroupId=org.apache.commons 
-DartifactId=commons-lang3 -Dversion=3.x -Dpackaging=jar -Dfile=/path/to/file
 [java] 
 [java]   Alternatively, if you host your own repository you can deploy the 
file there: 
 [java]   mvn deploy:deploy-file -DgroupId=org.apache.commons 
-DartifactId=commons-lang3 -Dversion=3.x -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]
 [java] 
 [java]   Path to dependency: 
 [java] 1) 
org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.17
 [java] 2) org.apache.maven.surefire:maven-surefire-common:jar:debian
 [java] 3) org.apache.commons:commons-lang3:jar:3.x
 [java] 
 [java] --
 [java] 1 required artifact is missing.
 [java] 
 [java] for artifact: 
 [java]   org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.17
 [java] 
 [java] from the specified remote repositories:
 [java]   central (https://repo1.maven.org/maven2)
 [java] 
 [java] 
 [java] at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:361)
 [java] at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304)
 [java] at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1499)
 [java] at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
 [java] at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
 [java] ... 9 more
 [java] [INFO] 

 [java] [INFO] Total time: 1 second
 [java] [INFO] Finished at: Tue Aug 16 17:42:30 CEST 2016
 [java] [INFO] Final Memory: 5M/13M
 [java] [INFO] 


BUILD FAILED
/<>/debian/build.xml:111: The following error occurred while 
executing this line:
/<>/debian/build.xml:34: The following error occurred while 
executing this line:
/usr/share/maven-ant-helper/maven-build.xml:325: The following error occurred 
while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:320: The following error occurred 
while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:297: Java returned: 1

Total time: 48 seconds
/usr/share/cdbs/1/class/ant.mk:39: recipe for target 

Bug#830060: marked as done (Could not find 'appraisal')

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 16:36:21 +
with message-id 
and subject line Bug#830060: fixed in ruby-appraisal 0.5.1-2
has caused the Debian Bug report #830060,
regarding Could not find 'appraisal'
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.)


-- 
830060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-appraisal
Version: 0.5.1-1
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

irb(main):001:0> gem "appraisal"
Gem::LoadError: Could not find 'appraisal' (>= 0) among 117 total gem(s)
[...]

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

We believe that the bug you reported is fixed in the latest version of
ruby-appraisal, 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.
Andrew Lee (李健秋)  (supplier of updated 
ruby-appraisal 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, 26 Aug 2016 15:35:13 +0800
Source: ruby-appraisal
Binary: ruby-appraisal
Architecture: source
Version: 0.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Andrew Lee (李健秋) 
Description:
 ruby-appraisal - Find out what your Ruby gems are worth
Closes: 830060
Changes:
 ruby-appraisal (0.5.1-2) unstable; urgency=medium
 .
   [ Sebastien Badia ]
   * Team upload
   * d/compat: Bump compat version to 9 and wrap file
   * d/control: Update Vcs-* fields (use cgit and https)
   * Bump Standards-Versions to 3.9.7 (no changes)
   * Update debian packaging
 .
   [ Cédric Boutillier ]
   * Use https:// in Vcs-* fields
   * Use https:// in Vcs-* fields
   * Run wrap-and-sort on packaging files
 .
   [ Andrew Lee (李健秋) ]
   * New upload to support current Ruby version. (Closes: #830060)
   * Bump standard version to 3.9.8.
Checksums-Sha1:
 1d195de41fde9807b6efd269928e0c3f1969e509 2106 ruby-appraisal_0.5.1-2.dsc
 f0243108db2fb162d2ae14194147a9169643e25f 2632 
ruby-appraisal_0.5.1-2.debian.tar.xz
Checksums-Sha256:
 02a69867a128a88da9371afedebc0b8b90de6fe4c6342d03a3fda7a206afebc9 2106 
ruby-appraisal_0.5.1-2.dsc
 96061e1182bb08f2359f43c2724ccf70c6b3fc1ba096b3ec2d1de1a6baf2c96d 2632 
ruby-appraisal_0.5.1-2.debian.tar.xz
Files:
 8214e1d5733686bf8affc1be27f30747 2106 ruby optional ruby-appraisal_0.5.1-2.dsc
 2b947ea9098a34867488dbf465eb8b9e 2632 ruby optional 
ruby-appraisal_0.5.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXwE+EAAoJEOfL4VKsF/lzEXgP/2sCzQB+Mj1f7hL3f2rFlBvk
znpy5VPMW4JdRX4XESIdgEzqoLIBI6Lv7nsvMI3vu1sENY55fjDFcerewHw3tFJL
lnAgLwZcuKcypJgaLN/IcTAcmwwT9jx5c6z5i+QKeXoQ/825yb+IMuJbVNob3SMZ
lj9rl6irLT3aLAoaviY7ZtDPvbHmsLHAB4bN8DlHxqVfd28H7opdT8BZ9hrfM3MZ
273mx61x+NyzU//Md0vobp6gud/cyl1Buw1if8sdxPgs7HKX+Br3A4leWd5y0R7T
IUsAzEyK4ITLK7qbnCxDHrmtVzh2cfxnRBAE6+xndIoZxzE7c1UvZCa+JoGxn6wx
fI+8GLxxb09BPWTfpfXCJA1XqUhojOeNPD4UVCvQcomQWh4bJ2T92kD7IqFVAWjD
irCNnOKMcjEyREz85id/0aN1eO72DwpR4DS6Xm0B9d+1xDw7Cn+QJ/aIy9NYrhF4
V5fsLvQCIVjliZtg+Uf9jZGQJ/sl0TE/6EHFhqKIuEVlnWnnn9NdlAXDHwgToeEl
rq/UyWydZWo95QRCeCrtYQqNA0+s2hdqUV5hiIvlFH1piKdCxlvc7F/py4uCCZqY
WpDVt+OrwzHmU8cxWoLF1xA1pI1SPXEkCpJtEi/8NGx16vMG66zc1zGJX5DWEJCp
dwkNwuLFmTJ8UpJdzJCg
=URhv
-END PGP SIGNATURE End Message ---

Bug#831965: Asciidoc: patch integrated

[Joseph Herlant]

Control: tags -1 + pending

Hi Lucas, Santiago,

Sorry I just noticed this bug.
Thanks Santiago, I tested and added your patch to the git repository.
As I don't have upload rights in Debian, Alexander Wirt will have a
look when he has some time.
There are a lot of changes since the last release in 2014, so it might
take some time to be pushed.

Thanks for your help,
Joseph

Processed: Asciidoc: patch integrated

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #831965 [src:asciidoc] asciidoc: FTBFS with dpkg-buildpackage -A: 
doc/testasciidoc.1: No such file or directory at /usr/bin/dh_installman line 
131.
Added tag(s) pending.

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

Bug#834913: marked as done (libslf4j-java: FTBFS too much often (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 16:29:38 +
with message-id 
and subject line Bug#834913: fixed in libslf4j-java 1.7.21-2
has caused the Debian Bug report #834913,
regarding libslf4j-java: FTBFS too much often (failing tests)
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.)


-- 
834913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libslf4j-java
Version: 1.7.21-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibslf4j-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 

[... snipped ...]

at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)


Results :

Failed tests: 
  
SimpleLoggerMultithreadedInitializationTest>MultithreadedInitializationTest.multiThreadedInitialization:46
 388 < 0+16

Tests run: 17, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] SLF4J .. SUCCESS [  0.694 s]
[INFO] SLF4J API Module ... SUCCESS [  5.988 s]
[INFO] SLF4J Simple Binding ... FAILURE [  1.166 s]
[INFO] SLF4J NOP Binding .. SKIPPED
[INFO] SLF4J JDK14 Binding  SKIPPED
[INFO] SLF4J LOG4J-12 Binding . SKIPPED
[INFO] SLF4J JCL Binding .. SKIPPED
[INFO] JCL 1.1.1 implemented over SLF4J ... SKIPPED
[INFO] Log4j Implemented Over SLF4J ... SKIPPED
[INFO] JUL to SLF4J bridge  SKIPPED
[INFO] SLF4J Migrator . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 8.642 s
[INFO] Finished at: 2016-08-18T23:48:34+02:00
[INFO] Final Memory: 12M/35M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project slf4j-simple: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/slf4j-simple/target/surefire-reports 
for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible 

Bug#834833: marked as done (javassist: FTBFS too much often (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 16:21:51 +
with message-id 
and subject line Bug#834833: fixed in javassist 1:3.20.0-2
has caused the Debian Bug report #834833,
regarding javassist: FTBFS too much often (failing tests)
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.)


-- 
834833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: javassist
Version: 3.20.0-1
Severity: serious

Dear maintainer:

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

A diff between a successful build and a failed build shows this:

--
Tests run: 376, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 20.789 sec 
<<< FAILURE! - in javassist.JvstTest
testJIRA150(javassist.JvstTest4)  Time elapsed: 0.711 sec  <<< FAILURE!
junit.framework.AssertionFailedError: 326 < 3 * 79
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at javassist.JvstTest4.testJIRA150(JvstTest4.java:666)


Results :

Failed tests: 
  javassist.JvstTest4#testJIRA150 AssertionFailedError 326 < 3 * 79

Tests run: 376, Failures: 1, Errors: 0, Skipped: 0
--

So apparently there are some tests based on performance.

If that's the case, such tests must be disabled, as it's not written
anywhere that the performance of any given autobuilder will remain
constant during the package build.

Thanks.
--- End Message ---
--- Begin Message ---
Source: javassist
Source-Version: 1:3.20.0-2

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated javassist 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, 26 Aug 2016 15:51:01 +0200
Source: javassist
Binary: libjavassist-java libjavassist-java-doc
Architecture: source
Version: 1:3.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libjavassist-java - library for editing bytecodes in Java
 libjavassist-java-doc - library for editing bytecodes in Java -- documentation
Closes: 834833
Changes:
 javassist (1:3.20.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Add disable-JIRA150-test.patch.
 Disable JIRA150 test that takes the performance of the host system into
 account. This may lead to random build failures. (Closes: #834833)
Checksums-Sha1:
 30e954e8dd5b71d9a1bfd17b7e6c06d4902763b8 2296 javassist_3.20.0-2.dsc
 27007f87e4fbe9b231cf6448087a4e7a31440d45 4992 javassist_3.20.0-2.debian.tar.xz
Checksums-Sha256:
 651127c58490a76280cde2ddb66d9ff04b9632d72060f21b00bab95fa486f0bb 2296 
javassist_3.20.0-2.dsc
 65a023a9e2d015c45c12d0c1adfbf59ca95072a8ca799dfac391211b5270 4992 
javassist_3.20.0-2.debian.tar.xz
Files:
 073c33dc82fc5a5119abff730e105880 2296 java optional javassist_3.20.0-2.dsc
 d3fb5a746cb926aad53b5dd3a1b1aa6c 4992 java optional 
javassist_3.20.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXwEptXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1Hk6NMQAIcL4WouO0qHpReW1OagtU8u
x2vTF9prpH6A7d2nqJlBKNZxufpGVQt9Ku86CIHItbO9hAYyRJjP+5n0eqDgUFgF
dNhyGqmnMT7r4QWMwt8gQLX0gEPVMcAtuOVaCoUm2dmqfHn0KJrWlEK6hghVcxvv
ct7sLQCtaiYiSAhMT3EWBtW2klU7oJ6ax6728nqGTBoQj72aycpwsry4PesKacXJ
2/LkIuRO4+0UUpVnrHil7F/9LAXLWRMcEjHv9fdkwUS9CLPaANmLbF/wgY7yy4x1
WWymLzH5WcHg7TAmwtyCsidPHOOxPJVo89j2JEyUjvkBYeaSJdfT3b70CP05MMdt
D1omRPmAfSqiFbEI+7uJKdQ1mU5/pmfQeBzGjzb2wn9TCbHwB1hrwRAvNwb1K/t0

Bug#834890: marked as done (commons-math: FTBFS with probability > 0 in a deliberate way)

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 16:20:36 +
with message-id 
and subject line Bug#834890: fixed in commons-math 2.2-6
has caused the Debian Bug report #834890,
regarding commons-math: FTBFS with probability > 0 in a deliberate way
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.)


-- 
834890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:commons-math
Version: 2.2-5
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
/usr/share/maven-debian-helper/copy-repo.sh /<>/debian
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibcommons-math-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo 
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to check 
if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \

[... snipped ...]

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
org.apache.commons.math.genetics.BinaryChromosomeTest
Running org.apache.commons.math.genetics.TournamentSelectionTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in 
org.apache.commons.math.genetics.TournamentSelectionTest
Running org.apache.commons.math.genetics.RandomKeyMutationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in 
org.apache.commons.math.genetics.RandomKeyMutationTest
Running org.apache.commons.math.genetics.OnePointCrossoverTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in 
org.apache.commons.math.genetics.OnePointCrossoverTest
Running org.apache.commons.math.genetics.GeneticAlgorithmTestBinary
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec - in 
org.apache.commons.math.genetics.GeneticAlgorithmTestBinary
Running org.apache.commons.math.geometry.Vector3DTest
Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec - in 
org.apache.commons.math.geometry.Vector3DTest
Running org.apache.commons.math.geometry.Vector3DFormatTest
Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec - in 
org.apache.commons.math.geometry.Vector3DFormatTest
Running org.apache.commons.math.geometry.RotationOrderTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in 
org.apache.commons.math.geometry.RotationOrderTest
Running org.apache.commons.math.geometry.RotationTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.145 sec - in 
org.apache.commons.math.geometry.RotationTest
Running org.apache.commons.math.geometry.FrenchVector3DFormatTest
Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec - in 
org.apache.commons.math.geometry.FrenchVector3DFormatTest

Results :

Failed tests: 
  GammaDistributionTest>ContinuousDistributionAbstractTest.testSampling:275 
Chisquare test failed p-value = 7.68153812779615E-4 chisquare statistic = 
16.8239998. 
value   expectedobserved
1   250 230
2   250 296
3   250 211
4   250 263
This test can fail randomly due to sampling error with probability 0.001.

Tests run: 2461, Failures: 1, Errors: 0, Skipped: 2

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 35.898 s
[INFO] Finished at: 2016-08-20T08:57:22+02:00
[INFO] Final Memory: 7M/17M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project commons-math: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/target/surefire-reports for the 
individual test results.
[ERROR] -> [Help 1]

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Yaroslav Halchenko]

Thank you Santiago for the report!  I believe it is due to outdated
git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
I will request gb for it -- could have been a spurious/toolchain issue.
CCing git-annex Debian maintainer

Cheers!

On Fri, 26 Aug 2016, Santiago Vila wrote:

> Package: src:datalad
> Version: 0.2.3-1
> Severity: serious

> Dear maintainer:

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

> 
> [...]
>  debian/rules build-indep
> dh build-indep --with python2 --buildsystem=pybuild
>dh_testdir -i -O--buildsystem=pybuild
>dh_update_autotools_config -i -O--buildsystem=pybuild
>dh_auto_configure -i -O--buildsystem=pybuild
>   pybuild --configure --test-nose -i python{version} -p 2.7
> I: pybuild base:184: python2.7 setup.py config 
> running config
>dh_auto_build -i -O--buildsystem=pybuild
>   pybuild --build --test-nose -i python{version} -p 2.7
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py

> [... snipped ...]



> ==
> FAIL: datalad.support.tests.test_annexrepo.test_AnnexRepo_add_to_git
> --
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", line 
> 697, in newfunc
> t(*(arg + (uri,)), **kw)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", line 
> 507, in newfunc
> return t(*(arg + (filename,)), **kw)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_annexrepo.py",
>  line 661, in test_AnnexRepo_add_to_git
> ok_clean_git_annex_proxy(repo.path)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", line 
> 157, in ok_clean_git_annex_proxy
> assert_in("nothing to commit, working directory clean", out[0], 
> "git-status output via proxy not plausible: %s" % out[0])
> AssertionError: git-status output via proxy not plausible: On branch 
> annex/direct/master
> nothing to commit, working tree clean


> ==
> FAIL: datalad.support.tests.test_annexrepo.test_AnnexRepo_annex_proxy
> --
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", line 
> 818, in newfunc
> reraise(*exc_info)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", line 
> 794, in newfunc
> func(*args, **kwargs)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", line 
> 697, in newfunc
> t(*(arg + (uri,)), **kw)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", line 
> 507, in newfunc
> return t(*(arg + (filename,)), **kw)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_annexrepo.py",
>  line 125, in test_AnnexRepo_annex_proxy
> ok_clean_git_annex_proxy(path=annex_path)
>   File 
> "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", line 
> 157, in ok_clean_git_annex_proxy
> assert_in("nothing to commit, working directory clean", out[0], 
> "git-status output via proxy not plausible: %s" % out[0])
> AssertionError: git-status output via proxy not plausible: On branch 
> annex/direct/master
> nothing to commit, working tree clean


> --
> Ran 399 tests in 103.178s

> FAILED (SKIP=41, errors=3, failures=3)
> E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose -s -v datalad
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 
> --test-nose returned exit code 13
> debian/rules:27: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 25
> make[1]: Leaving directory '/<>'
> debian/rules:19: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> 

> This used to build ok, so this failure seems related to git 2.9.3,
> which is in testing since a few days.

> Thanks.


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   

Bug#835525: datalad: FTBFS in testing (broken by new git)

[Santiago Vila]

Package: src:datalad
Version: 0.2.3-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure --test-nose -i python{version} -p 2.7
I: pybuild base:184: python2.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
pybuild --build --test-nose -i python{version} -p 2.7
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]



==
FAIL: datalad.support.tests.test_annexrepo.test_AnnexRepo_add_to_git
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 697, in newfunc
t(*(arg + (uri,)), **kw)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 507, in newfunc
return t(*(arg + (filename,)), **kw)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_annexrepo.py",
 line 661, in test_AnnexRepo_add_to_git
ok_clean_git_annex_proxy(repo.path)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 157, in ok_clean_git_annex_proxy
assert_in("nothing to commit, working directory clean", out[0], "git-status 
output via proxy not plausible: %s" % out[0])
AssertionError: git-status output via proxy not plausible: On branch 
annex/direct/master
nothing to commit, working tree clean


==
FAIL: datalad.support.tests.test_annexrepo.test_AnnexRepo_annex_proxy
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 818, in newfunc
reraise(*exc_info)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 794, in newfunc
func(*args, **kwargs)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 697, in newfunc
t(*(arg + (uri,)), **kw)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 507, in newfunc
return t(*(arg + (filename,)), **kw)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_annexrepo.py",
 line 125, in test_AnnexRepo_annex_proxy
ok_clean_git_annex_proxy(path=annex_path)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 157, in ok_clean_git_annex_proxy
assert_in("nothing to commit, working directory clean", out[0], "git-status 
output via proxy not plausible: %s" % out[0])
AssertionError: git-status output via proxy not plausible: On branch 
annex/direct/master
nothing to commit, working tree clean


--
Ran 399 tests in 103.178s

FAILED (SKIP=41, errors=3, failures=3)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose -s -v datalad
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --test-nose 
returned exit code 13
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:19: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This used to build ok, so this failure seems related to git 2.9.3,
which is in testing since a few days.

Thanks.

Bug#835526: git-build-recipe: FTBFS in testing (broken by new git)

[Santiago Vila]

Package: src:git-build-recipe
Version: 0.3.2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/deb_util.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/recipe.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/main.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/deb_version.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
copying gitbuildrecipe/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe
creating /<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
copying gitbuildrecipe/tests/test_deb_version.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
copying gitbuildrecipe/tests/test_recipe.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
copying gitbuildrecipe/tests/test_blackbox.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
copying gitbuildrecipe/tests/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
LC_ALL=C.UTF-8 dh_auto_test
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_3.5/build; 
python3.5 -m nose 
E.
==
ERROR: 
gitbuildrecipe.tests.test_recipe.BuildTreeTests.test_build_tree_merge_unrelated
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
348, in merge_branch
child_branch.commit)
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
637, in git_call
**kwargs)
  File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
**kwargs).stdout
  File "/usr/lib/python3.5/subprocess.py", line 708, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', '-C', 'target', 'merge', 
'--commit', '-m', 'Merge HEAD', 'cffd324cab4213c080815e51045e11e544b4791a']' 
returned non-zero exit status 128

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/tests/test_recipe.py",
 line 620, in test_build_tree_merge_unrelated
build_tree(base_branch, "target")
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
464, in build_tree
_build_inner_tree(base_branch, target_path)
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
388, in _build_inner_tree
instruction.apply(target_path)
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
520, in apply
merge_branch(self.recipe_branch, target_path)
  File 
"/<>/.pybuild/pythonX.Y_3.5/build/gitbuildrecipe/recipe.py", line 
350, in merge_branch
raise MergeFailed(e.output)
gitbuildrecipe.recipe.MergeFailed: git merge failed:
fatal: refusing to merge unrelated histories

 >> begin captured logging << 
root: INFO: Building tree.
root: INFO: Retrieving 'source1' to put at 'target'.
root: INFO: Merging 'source2' in to 'target'.
- >> end captured logging << -

--
Ran 158 tests in 18.388s

FAILED (errors=1)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_3.5/build; python3.5 -m nose 
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 returned 
exit code 13
debian/rules:6: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:3: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This used to build ok, so this failure seems related to git 2.9.3,
which is in testing since a few days.

Thanks.

Processed: Re: mina2: FTBFS too much often (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #834682 [src:mina2] mina2: FTBFS too much often (failing tests)
Severity set to 'normal' from 'serious'
> tags -1 unreproducible
Bug #834682 [src:mina2] mina2: FTBFS too much often (failing tests)
Added tag(s) unreproducible.

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

Bug#834682: mina2: FTBFS too much often (failing tests)

[Markus Koschany]

Control: severity -1 normal
Control: tags -1 unreproducible

On Wed, 17 Aug 2016 23:50:03 + Santiago Vila  wrote:
> Package: src:mina2
> Version: 2.0.13-1
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
> 
[...]
> 
> Tests in error: 
>   NioFileRegionTest.testSendLargeFile ?? IO Broken pipe
> 
> Tests run: 201, Failures: 0, Errors: 1, Skipped: 5


I have rebuilt mina2 ten times in a row now but I can't reproduce the
failing test or the build failure in general. It appears this issue is
not random and does not affect the majority of our users. In my opinion
it is not release critical hence I'm going to lower the severity unless
there is a compelling reason to do otherwise.

Since we have seen similar bug reports against packages with enabled
test suites in the past, I suggest to following:

If the tests fail randomly, the test(s) or the whole test suite should
be disabled or the tests changed because otherwise they cause more
maintenance work. The reasoning for enabling the test suite is that
regressions should be quickly detected but if the test results are
random we won't benefit from them.

The test suite is not the only way to spot regressions in a
distribution. Most of the time we are aware of build failures and
receive respective reports and if there is an important behavioral
change users will notice it.

On the other hand if we can choose between enabling or disabling a test
suite I'm all for enabling it because when the results are reliable,
they are a helpful mechanism to spot errors. So there is a trade-off
between the usefulness of the tests and the cost of triaging this kind
of bug reports and causing build failures.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#835514: libprotobuf-java: junit and easymock dependencies should only be required for tests

[Markus Koschany]

Package: libprotobuf-java
Version: 3.0.0-5
Severity: serious
Tags: patch

Hello,

thanks for fixing #835358 so quickly. Unfortunately there is another
issue with the pom.xml file now. java/core/pom.xml lists junit and
easymock artifacts as dependencies but libprotobuf-java does not
depend on these packages. This causes build failures like [1].

libprotobuf-java should either depend on the respective packages or
change the scope to test again as in earlier versions. I think the
latter solution is preferable because junit and easymock are only
needed for tests. If you take a look at version 2.6.1, you will see
that scope test was used before. [2] I don't know why they changed this
but it looks like an upstream bug to me.

I'm attaching a patch that resolves the issue and restores the old
behavior again.

Regards,

Markus

[1] https://bugs.debian.org/835430
[2] 
https://anonscm.debian.org/cgit/pkg-protobuf/pkg-protobuf.git/tree/java/pom.xml?h=debian/2.6.1-2
From: Markus Koschany 
Date: Thu, 25 Aug 2016 18:58:17 +0200
Subject: protobuf-java

---
 java/core/pom.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/java/core/pom.xml b/java/core/pom.xml
index 39d6781..20ed02a 100644
--- a/java/core/pom.xml
+++ b/java/core/pom.xml
@@ -22,14 +22,17 @@
 
   junit
   junit
+  test
 
 
   org.easymock
   easymock
+  test
 
 
   org.easymock
   easymockclassextension
+  test
 
   
 

Bug#834668: django-taggit: FTBFS in testing (failing tests)

[Michal Čihař]

Hi

Santiago Vila píše v St 17. 08. 2016 v 22:20 +:
> Package: src:django-taggit
> Version: 0.20.2-1
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

Most of the failures are fixed in latest upstream release, however one
of the failures is caused by bug in Django (https://code.djangoproject.
com/ticket/26983), so that can't be fixed until Django 1.10.1 is
available.


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


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

Bug#834241: marked as done (open-iscsi-udeb: uninstallable, depends on libmount1-udeb)

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 12:03:59 +
with message-id 
and subject line Bug#834241: fixed in open-iscsi 2.0.873+git1.4c1f2d90-2
has caused the Debian Bug report #834241,
regarding open-iscsi-udeb: uninstallable, depends on libmount1-udeb
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.)


-- 
834241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-iscsi-udeb
Version: 2.0.873+git1.4c1f2d90-1
Severity: serious
Justification: uninstallable

Hi,

partman-iscsi and open-iscsi-udeb are no longer installable since the
latter now depends on libmount1-udeb, which was dropped in 2014 (see
https://bugs.debian.org/723168).

(debian-boot@ x-d-cc'd, please keep it in the loop.)


KiBi.
--- End Message ---
--- Begin Message ---
Source: open-iscsi
Source-Version: 2.0.873+git1.4c1f2d90-2

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

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

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

Debian distribution maintenance software
pp.
Christian Seiler  (supplier of updated open-iscsi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Aug 2016 08:31:02 +0200
Source: open-iscsi
Binary: open-iscsi iscsiuio open-iscsi-udeb
Architecture: source
Version: 2.0.873+git1.4c1f2d90-2
Distribution: unstable
Urgency: medium
Maintainer: Debian iSCSI Maintainers 

Changed-By: Christian Seiler 
Description:
 iscsiuio   - iSCSI offloading daemon for QLogic devices
 open-iscsi - iSCSI initiator tools
 open-iscsi-udeb - Configure iSCSI (udeb)
Closes: 834241
Changes:
 open-iscsi (2.0.873+git1.4c1f2d90-2) unstable; urgency=medium
 .
   * [5a7879c] remove debian/source/local-options
   * [f5d5cbb] Temporarily build udeb without libmount (Closes: #834241)
   * [520129b] open-iscsi-udeb: update initramfs after copying
 configuration to target system
Checksums-Sha1:
 e991f504d946e0c7b2434bc59e8c9c3b8c7b4893 2524 
open-iscsi_2.0.873+git1.4c1f2d90-2.dsc
 a8158fc68c2178c52bc72bae675c0184e9163883 62152 
open-iscsi_2.0.873+git1.4c1f2d90-2.debian.tar.xz
Checksums-Sha256:
 ba742e977056c40b9f6ed3adc173331226bf18412c8199ee660147025ff3b5ac 2524 
open-iscsi_2.0.873+git1.4c1f2d90-2.dsc
 781828ba219189fc1f15d755c4ff07b535626c8c146fdb0432dcf12c624f4968 62152 
open-iscsi_2.0.873+git1.4c1f2d90-2.debian.tar.xz
Files:
 521edf29f3f580b774992287132338ec 2524 net optional 
open-iscsi_2.0.873+git1.4c1f2d90-2.dsc
 ee48c557c682eb32a3748edcedff55d5 62152 net optional 
open-iscsi_2.0.873+git1.4c1f2d90-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXwC7aAAoJEGMjNFnNz6AYvzAQAMbTVNO66Wk795wQjGxchI32
BnolgxYHajFCrFI3MIuaVYRp9PqpZxkU+qxu58Q6hyCzScsgPuhyXdXBdflnAN3y
cU1/spp1bOOTpmN54KwZOztjnszWKo+qgv+ST/f3Edx9XV1k2J75MPhFqooVbp5+
5qUtAYhyMLDVPB7ZrGsHVrKAuhak+kHB3tcIM6I15hq3Cxlqo7VHqZcgVBWzkVPp
HMPfVf06AiwHm8nOBjQuJboP4lLqXmAFfrVu+Oo5XsfevaXW4uUcKHYNjWZQu4IK
nsMzM0h07FcsX7pOOwFn17/VuLBPIKP1+30Z0iWtp7hJFpm+zlatIDZNA37HWUHl
KJ/cbb9slxzuwqivGKrkW5MunWpOsLGKaGryunYG1d9tDmsqRVOAh9lfHrwRmESL
jH6IFA3K2FHd6vFptpqz0ULANBLpmEiQcFMOJPBYtQ6IodGFK7VhtqAfpKMzqDW4
7kF5Y61FKjOjHzdN1QkCmU/SOp/fHGOj2xGPQczSVGiXp8EOZJ4/GXSkdoZYQeEb
e/YvXibVniUryb5nl6CDFnZkiAZDwr4V3Zoo+Q6ovzdKhKBPj9mHZKS22VtzJlLV
rbfHn8B9voOTE6vst1BI45iFkyR5Ee4IuF4fmBse9UCf30En4XfPB+Ygb5IZJb/q
jS+VKwQB4xdhTyluLnQv
=UISY
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#834241: open-iscsi-udeb: uninstallable, depends on libmount1-udeb

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #834241 [open-iscsi-udeb] open-iscsi-udeb: uninstallable, depends on 
libmount1-udeb
Added tag(s) pending.

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

Bug#834241: open-iscsi-udeb: uninstallable, depends on libmount1-udeb

[Christian Seiler]

Control: tags -1 + pending

On 08/13/2016 10:22 PM, Cyril Brulebois wrote:
> Christian Seiler  (2016-08-13):
>> So I'd probably want to do the following:
>>
>>  Step 1: build open-iscsi twice, once with libmount patched
>>  out (closing this bug)
>>  Step 2: file bugs against util-linux and libselinux to
>>  have them build udebs (I can provide patches)
>>  Step 3: make open-iscsi-udeb depend on libmount1-udeb again
>>
>> Is that agreeable?
> 
> I can't comment on the libmount/libselinux bits, but looking at it from
> a debian-boot@ point of view, that looks rather sane, thanks.

Since I didn't hear anything back from either libselinux or
util-linux maintainers, I assume they're in agreement. I'm hence
proceeding with this plan. I've opened bugs against util-linux
and libselinux for the udebs:

libselinux: https://bugs.debian.org/835503
util-linux: https://bugs.debian.org/835504

And I have committed a workaround for open-iscsi to git
packaging that disables libmount temporarily for the udeb packages,
which I'll upload soon:

https://anonscm.debian.org/cgit/pkg-iscsi/open-iscsi.git/commit/?id=f5d5cbb8fa2772dcd7db0be2a7ebc72a108fbd96

(I've tested both variants of the binaries on a regular system.)

Regards,
Christian

Bug#815004: Engine is installed at wrong location

[Julien Cristau]

Control: found -1 0.1.8-4

On Wed, Feb 17, 2016 at 12:02:54 +0100, Wouter Verhelst wrote:

> Package: libengine-pkcs11-openssl
> Version: 0.2.1-1
> Severity: grave
> Justification: makes the package in question unusable
> 
> Hi,
> 
> After installing libengine-pkcs11-openssl, the following happens:
> 
> wouter@gangtai:~$ openssl engine pkcs11 -t
> 139772252497552:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
> the shared 
> library:dso_dlfcn.c:187:filename(/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libpkcs11.so):
>  /usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libpkcs11.so: cannot open 
> shared object file: No such file or directory
> 139772252497552:error:25070067:DSO support routines:DSO_load:could not load 
> the shared library:dso_lib.c:232:
> 139772252497552:error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
> found:eng_dyn.c:465:
> 139772252497552:error:2606A074:engine routines:ENGINE_by_id:no such 
> engine:eng_list.c:390:id=pkcs11
> 
> This is because libengine-pkcs11-openssl writes its engine files to
> /usr/lib/ssl/engines rather than the location where current OpenSSL
> looks for engines.
> 
This seems broken in stable as well:

$ openssl engine pkcs11
140063553324688:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared 
library:dso_dlfcn.c:187:filename(/usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpkcs11.so):
 /usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpkcs11.so: cannot open 
shared object file: No such file or directory
140063553324688:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:232:
140063553324688:error:260B6084:engine routines:DYNAMIC_LOAD:dso not 
found:eng_dyn.c:465:
140063553324688:error:2606A074:engine routines:ENGINE_by_id:no such 
engine:eng_list.c:390:id=pkcs11

It would be nice to fix this in a jessie update.

Cheers,
Julien

Processed: Re: Bug#815004: Engine is installed at wrong location

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.1.8-4
Bug #815004 {Done: Eric Dorland } [libengine-pkcs11-openssl] 
Engine is installed at wrong location
Marked as found in versions engine-pkcs11/0.1.8-4.

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

Processed: unarchiving 815004

[Debian Bug Tracking System]

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

> unarchive 815004
Bug #815004 {Done: Eric Dorland } [libengine-pkcs11-openssl] 
Engine is installed at wrong location
Unarchived Bug 815004
> thanks
Stopping processing here.

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

Bug#824226: Info received (openjdk-8-jre: ATK bridge causes segfault when loading JR)

[Peter Keel]

Addendum: 

Downgraded to these: 

libatk-bridge2.0-0_2.14.0-2_amd64.deb
libatk-wrapper-java_0.30.5-1_all.deb
libatk-wrapper-java-jni_0.30.5-1_amd64.deb

and installed that (incidentally, there's no debug library for
the 2.20.1-3 version that would really need one):
libatk-bridge2.0-0-dbg_2.14.0-2_amd64.deb

Now Java works again. 

So the (GRAVE!) bug is most probably either here
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=libatk-bridge2.0-0
or here:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=libatk-wrapper-java
Either way, the accessibility-team is responsible. 

Cheers
Seegras
-- 
"Those who give up essential liberties for temporary safety deserve 
neither liberty nor safety." -- Benjamin Franklin
"It's also true that those who would give up privacy for security are 
likely to end up with neither." -- Bruce Schneier

Bug#835433: marked as done (ola: FTBFS with protobuf 3.0.0 (multiple issues))

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 10:29:22 +
with message-id 
and subject line Bug#835433: fixed in ola 0.10.2-2
has caused the Debian Bug report #835433,
regarding ola: FTBFS with protobuf 3.0.0 (multiple issues)
to be marked as done.

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

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


-- 
835433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ola
Version: 0.10.2-1
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so
Control: block 835170 by -1

Dear Maintainer,

The recent upload of protobuf 3.0.0 to unstable has started an
uncoordinated transition (#835170). Unfortunately your package FTBFS,
initially because python-numpy is not among the build dependencies, and
secondly because -Werror causes a build failure due to the
unused-parameter warning.

The attached patch fixes the build failures by adding python-numpy to
the build dependencies, and adds -Wno-error=unused-parameter to
CPPFLAGS. Please apply these changes in the next upload.

Kind Regards,

Bas
diff -Nru ola-0.10.2/debian/control ola-0.10.2/debian/control
--- ola-0.10.2/debian/control	2016-05-21 23:27:00.0 +0200
+++ ola-0.10.2/debian/control	2016-08-25 18:10:20.0 +0200
@@ -2,7 +2,7 @@
 Priority: extra
 Maintainer: Wouter Verhelst 
 Uploaders: RenZO 
-Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf, bash-completion, libcppunit-dev, bison, flex, pkg-config, uuid-dev, python, python-protobuf, libprotobuf-dev, protobuf-compiler, libprotoc-dev, libusb-1.0-0-dev, libftdi-dev, liblo-dev, libmicrohttpd-dev (>= 0.9.44+dfsg-1), libclosure-compiler-java, libncurses5-dev
+Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf, bash-completion, libcppunit-dev, bison, flex, pkg-config, uuid-dev, python, python-numpy, python-protobuf, libprotobuf-dev, protobuf-compiler, libprotoc-dev, libusb-1.0-0-dev, libftdi-dev, liblo-dev, libmicrohttpd-dev (>= 0.9.44+dfsg-1), libclosure-compiler-java, libncurses5-dev
 Standards-Version: 3.9.5
 Section: libs
 Vcs-Git: https://github.com/yoe/ola
diff -Nru ola-0.10.2/debian/rules ola-0.10.2/debian/rules
--- ola-0.10.2/debian/rules	2016-05-21 23:27:00.0 +0200
+++ ola-0.10.2/debian/rules	2016-08-25 18:15:54.0 +0200
@@ -10,6 +10,8 @@
 #export DH_VERBOSE=1
 export VERBOSE=1
 
+CPPFLAGS += -Wno-error=unused-parameter
+
 %:
 	dh $@ --parallel --with autotools_dev,autoreconf,bash_completion,python2
 
--- End Message ---
--- Begin Message ---
Source: ola
Source-Version: 0.10.2-2

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

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

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated ola 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, 26 Aug 2016 10:43:06 +0200
Source: ola
Binary: libola-dev ola-python ola-rdm-tests ola libola1
Architecture: source amd64 all
Version: 0.10.2-2
Distribution: unstable
Urgency: medium
Maintainer: Wouter Verhelst 
Changed-By: Wouter Verhelst 
Description:
 libola-dev - Open Lighting Architecture - development libraries
 libola1- Open Lighting Architecture - shared libraries
 ola- Open Lighting Architecture
 ola-python - Open Lighting Architecture - Python Classes
 ola-rdm-tests - Open Lighting Architecture - RDM Responder Tests
Closes: 835433
Changes:
 ola (0.10.2-2) unstable; urgency=medium
 .
   * debian/control: add python-numpy to build-depends, add
 -Wno-error=unused-parameter. Closes: #835433.
Checksums-Sha1:
 befde73f833e04b3f3e78447022d5e9ddf43fae7 2296 ola_0.10.2-2.dsc
 cfcde5027b189b40bdd4323bfde06c23712d613b 21140 ola_0.10.2-2.debian.tar.xz
 79e53dcc5f6ccd402e54229ec19f03c11ddc24f7 3141642 libola-dev_0.10.2-2_amd64.deb
 2dce5a55ad75dd36b720b50da96fd63a35a69617 765178 
libola1-dbgsym_0.10.2-2_amd64.deb
 e79ad0fa10a3d4aeb3f5f233c1cd3adc195185b0 2107814 libola1_0.10.2-2_amd64.deb
 

Bug#832479: marked as done (ValueError: Namespace Poppler not available)

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 10:27:11 +
with message-id 
and subject line Bug#832479: fixed in mat 0.6.1-3
has caused the Debian Bug report #832479,
regarding ValueError: Namespace Poppler not available
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.)


-- 
832479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mat
Version: 0.6.1-2
Severity: important

Dear Maintainer,
I just installed mat, and doing a simple

$ mat -c image.jpg

gives this error:

Traceback (most recent call last):
  File "/usr/bin/mat", line 10, in 
from libmat import mat
  File "/usr/lib/python2.7/dist-packages/libmat/mat.py", line 22, in 
import strippers  # this is loaded here because we need LOGGING_LEVEL
  File "/usr/lib/python2.7/dist-packages/libmat/strippers.py", line 9, in

import office
  File "/usr/lib/python2.7/dist-packages/libmat/office.py", line 15, in

gi.require_version('Poppler', '0.18')
  File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 102, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Poppler not available


However after manual installation of gir1.2-poppler-0.18 the problem is solved.

Maybe the mat package must ensure that the gir1.2-poppler-0.18 package is 
installed,
or install it otherwise.

Kind regards,
Mark



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

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

Versions of packages mat depends on:
ii  python-gi   3.20.1-1
ii  python-mutagen  1.33.2-1
ii  python-pdfrw0.2-2
pn  python:any  

Versions of packages mat recommends:
ii  gir1.2-gdkpixbuf-2.02.34.0-1
ii  gir1.2-glib-2.0 1.48.0-3
ii  gir1.2-gtk-3.0  3.20.6-2
pn  gir1.2-nautilus-3.0 
pn  gir1.2-poppler-0.18 
ii  libimage-exiftool-perl  10.20-1
ii  python-gi-cairo 3.20.1-1
pn  python-nautilus 

mat suggests no packages.

-- no debconf information

-- 
. ''`.  | GPG Public Key  : 0xCD542422 - Download it from http://is.gd/fOa7Vm
: :'  : | GPG Fingerprint : 0823 A40D F31B 67A8 5621 AD32 E293 A2EB CD54 2422
`. `'`  | Powered by Debian GNU/Linux, http://www.debian.org
  `-| Try not. Do, or do not. There is no try. - Master Yoda, TESB.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mat
Source-Version: 0.6.1-3

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

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated mat 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, 26 Aug 2016 08:40:53 +
Source: mat
Binary: mat
Architecture: source
Version: 0.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: intrigeri 
Closes: 826101 832479
Description: 
 mat- Metadata anonymisation toolkit
Changes:
 mat (0.6.1-3) unstable; urgency=medium
 .
   * Update documentation of recommended packages in README.Debian.
   * debian/copyright: use HTTPS URL.
   * Promote gir1.2-poppler-0.18 to Depends: even though it is supposed
 to be an optional dependency, needed only for PDF support, MAT crashes
 if it not installed. (Closes: #832479)
   * New patch: disable PDF support. (Closes: #826101)
Checksums-Sha1: 
 c65782f83d38cb5ef20f9fe26d3d80ee51af7e9d 2077 mat_0.6.1-3.dsc
 21b1ed34fb7c17673466e8542e0ac564d49093e9 13648 mat_0.6.1-3.debian.tar.xz
Checksums-Sha256: 
 aa4d2740c5b7bc36b72f0dd3b67bd7b522e11aa337f44f1e5d5465f9c29d667c 2077 
mat_0.6.1-3.dsc
 0c87284cb0dfd420d97e76e9c3b29d0a1e5df23e651b6f1de911e06243b3baac 13648 

Processed: Merge

[Debian Bug Tracking System]

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

> merge 835341 835477
Bug #835341 [mutt] mutt 1.6.2-3 has wrong dependencies
Bug #835477 [mutt] depends on libnotmuch3, not available in unstable
Added tag(s) pending.
Merged 835341 835477
> thanks
Stopping processing here.

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

Bug#812676: maven-scm: FTBFS - test fails with Unparseable date exception

[Santiago Vila]

On Mon, 25 Jan 2016, Michael Tautschnig wrote:

> java.text.ParseException: Unparseable date: "Wed Oct  4 15:42:47 2006"

This happened to me today while checking for "dpkg-buildpackage -A" bugs.
I attach my build log.

> The full build log is attached; please do let me know if the problem is
> unreproducible, in which case I shall try to investigate further.

The problem seems to be random. I guess that if you try to build many
times, a small fraction of the times will fail with the same error.

I would say there is a real problem here, so if you have time and
motivation, go ahead and investigate.

We want package builds to always succeed, not just "most of the time",
so bugs that only happen in a random way are also bugs.

Thanks.

maven-scm_1.3-7_amd64-20160826T002925Z.gz
Description: application/gzip

Bug#835489: Fails to start

[Dmitry Eremin-Solenikov]

Package: pyqso
Version: 0.3-1
Severity: grave

pyqso fails to start with the following console log.

/usr/bin/pyqso:20: PyGIWarning: Gtk was imported without specifying a version 
first. Use gi.require_version('Gtk', '3.0') before import to ensure that the 
right version gets loaded.
  from gi.repository import Gtk, GdkPixbuf
Traceback (most recent call last):
  File "/usr/bin/pyqso", line 22, in 
import configparser
ImportError: No module named configparser

After installing manually python-configparser, pyqso fails to find
unittest.mock module:

/usr/bin/pyqso:20: PyGIWarning: Gtk was imported without specifying a version 
first. Use gi.require_version('Gtk', '3.0') before import to ensure that the 
right version gets loaded.
  from gi.repository import Gtk, GdkPixbuf
INFO:root:PyQSO version 0.3
/usr/lib/python2.7/dist-packages/pyqso/logbook.py:20: PyGIWarning: PangoCairo 
was imported without specifying a version first. Use 
gi.require_version('PangoCairo', '1.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gtk, Pango, PangoCairo
/usr/lib/python2.7/dist-packages/matplotlib/font_manager.py:273: UserWarning: 
Matplotlib is building the font cache using fc-list. This may take a moment.
  warnings.warn('Matplotlib is building the font cache using fc-list. This may 
take a moment.')
Traceback (most recent call last):
  File "/usr/bin/pyqso", line 38, in 
from pyqso.logbook import *
  File "/usr/lib/python2.7/dist-packages/pyqso/logbook.py", line 38, in 
from pyqso.log import *
  File "/usr/lib/python2.7/dist-packages/pyqso/log.py", line 26, in 
from pyqso.record_dialog import *
  File "/usr/lib/python2.7/dist-packages/pyqso/record_dialog.py", line 34, in 

from pyqso.callsign_lookup import *
  File "/usr/lib/python2.7/dist-packages/pyqso/callsign_lookup.py", line 22, in 

import unittest.mock
ImportError: No module named mock

The module unittest.mock is provided only by Python 3.x. However manually 
starting pyqso with python3 also fails:

$ python3 /usr/bin/pyqso
/usr/bin/pyqso:20: PyGIWarning: Gtk was imported without specifying a version 
first. Use gi.require_version('Gtk', '3.0') before import to ensure that the 
right version gets loaded.
  from gi.repository import Gtk, GdkPixbuf
INFO:root:PyQSO version 0.3
Traceback (most recent call last):
  File "/usr/bin/pyqso", line 37, in 
from pyqso.adif import *
ImportError: No module named 'pyqso'


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

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

Versions of packages pyqso depends on:
ii  gir1.2-gtk-3.0  3.20.9-1
ii  libjs-jquery1.12.4-1
ii  libjs-underscore1.7.0~dfsg-1
ii  python-gi-cairo 3.20.1-1
ii  python-libhamlib2   3.0.1-1
ii  python-matplotlib   1.5.2~rc2-1
ii  python-mpltoolkits.basemap  1.0.7+dfsg-4
ii  python-numpy1:1.11.1~rc1-1
pn  python:any  

pyqso recommends no packages.

pyqso suggests no packages.

-- no debconf information

Bug#833411: pam-python: accesses the internet during build

[Chris Lamb]

Hi Petter,

Your patch works for me.

> Is there a recipe for how to easily test this?

Not really. I use containers and tcpdump -i eth0 with some extra filters, but
you might have some luck with (a recent version of) nsntrace.


Regards,

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

Bug#831591: ffmpeg: kodi crash

[Bálint Réczey]

Hi Carl,

2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos :
> Hi!
>
> First, please understand that so far, no ABI breakage between
> FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of
> non-public api (that we decided to work-around for 3.1.1).

OK, then assume that Kodi uses non-public API and the rebuild made kodi
use the latest ABI.
Can I somehow find easily the places where the non-public API is used?


>
> Am I correct that no backtrace was provided for this issue?

Yes, AFAIK.

Cheers,
Balint

> But even with a backtrace, I fear a bisect may be necessary.
>
> Sorry, Carl Eugen

Bug#835477: depends on libnotmuch3, not available in unstable

[Wouter Verhelst]

Package: mutt
Version: 1.6.2-3
Severity: serious

Hi,

My system wants to update mutt to 1.6.2-3, but that depends on
libnotmuch3, whereas in unstable, that should now be libnotmuch4
instead.

As such, it tries to install libnotmuch3 from jessie, which wants to
pull in libxapian22 (conflicting with libxapian22v5), resulting in
things not going so well.

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

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

Versions of packages mutt is related to:
ii  mutt  1.6.2-2

Processed: severity

[Debian Bug Tracking System]

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

> severity 818380 normal
Bug #818380 [clang-3.7] clang-3.7: __builtin_return_address() segfaults on s390x
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#835419: openvdb: FTBFS (32-bit): TestMultiResGrid.cc uses UL for size_t constants

[Mathieu Malaterre]

Control: tags -1 pending

On Thu, Aug 25, 2016 at 4:06 PM, Aaron M. Ucko  wrote:
> Source: openvdb
> Version: 3.2.0-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Builds of openvdb for 32-bit architectures such as i386 have been
> failing because TestMultiResGrid.cc uses the UL suffix for would-be
> size_t constants, yielding two errors and several warnings that I'd
> recommend addressing while you're at it:
>
> https://buildd.debian.org/status/fetch.php?pkg=openvdb=i386=3.2.0-1=1472106513
>
> On these architectures, size_t is formally unsigned int rather than
> unsigned long.  Although both types are de facto equivalent, the
> compiler insists on treating them as distinct.  I'm not aware of a
> UINT*_C-style macro for size_t, but these values are small enough that
> leaving them unsuffixed and casting to size_t should suffice.
>
> Could you please take a look?

Yay, this is 801802 again ... The worst part is that upstream did
integrate something similar and I thought I could simply removed this
old patch, but looks like some other new part have been added with
this very same bug.

sigh
-M

Bug#833411: pam-python: accesses the internet during build

[Petter Reinholdtsen]

Control: tags -1 + patch

[Chris Lamb]
> This appears to be caused by (at least) Sphinx's intersphinx mapping 
> extension.
> Please see #830186 for more information, including suggestions on how to fix 
> it.

Here is a patch I believe should fix the problem.  Not quite sure how to verify 
it.
Is there a recipe for how to easily test this?

-- 
Happy hacking
Petter Reinholdtsen
diff -Nru pam-python-1.0.4/debian/control pam-python-1.0.4/debian/control
--- pam-python-1.0.4/debian/control	2014-05-29 19:26:48.0 +
+++ pam-python-1.0.4/debian/control	2016-08-26 07:03:46.0 +
@@ -3,6 +3,7 @@
 Priority: extra
 Maintainer: Russell Stuart 
 Build-Depends: debhelper (>= 7), python-all-dev (>= 2.2), python-sphinx,
+  python-doc,
   libpam0g-dev | libpam-dev
 Standards-Version: 3.9.5
 Homepage:  http://pam-python.sourceforge.net/
diff -Nru pam-python-1.0.4/debian/patches/intersphinx-localmapping.diff pam-python-1.0.4/debian/patches/intersphinx-localmapping.diff
--- pam-python-1.0.4/debian/patches/intersphinx-localmapping.diff	1970-01-01 00:00:00.0 +
+++ pam-python-1.0.4/debian/patches/intersphinx-localmapping.diff	2016-08-26 07:03:46.0 +
@@ -0,0 +1,21 @@
+Description: Do not require Internet access during building.
+ intersphinx want to fetch some mapping data, and was set up to use
+ the Internet to find it.  Use a local file from python-doc instead to
+ avoid violating Debian policy 4.9.
+Author: Petter Reinholdtsen 
+Bug-Debian: https://bugs.debian.org/830186
+Bug-Debian: https://bugs.debian.org/833411
+Forwarded: no
+Reviewed-By: Petter Reinholdtsen 
+Last-Update: 2016-08-26
+
+--- pam-python-1.0.4.orig/doc/conf.py
 pam-python-1.0.4/doc/conf.py
+@@ -4,4 +4,6 @@ copyright = u'2010,2014, Russell Stuart'
+ version = '1.0.4'
+ release = '1.0.4'
+ extensions = ['sphinx.ext.intersphinx']
+-intersphinx_mapping = {'python': ('http://docs.python.org/2.7', None)}
++intersphinx_mapping = {
++  'python': ('/usr/share/doc/python-doc/html', None)
++}
diff -Nru pam-python-1.0.4/debian/patches/series pam-python-1.0.4/debian/patches/series
--- pam-python-1.0.4/debian/patches/series	1970-01-01 00:00:00.0 +
+++ pam-python-1.0.4/debian/patches/series	2016-08-26 07:03:46.0 +
@@ -0,0 +1 @@
+intersphinx-localmapping.diff

Processed: Re: Bug#835419: openvdb: FTBFS (32-bit): TestMultiResGrid.cc uses UL for size_t constants

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #835419 [src:openvdb] openvdb: FTBFS (32-bit): TestMultiResGrid.cc uses UL 
for size_t constants
Added tag(s) pending.

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

Processed: Re: pam-python: accesses the internet during build

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #833411 [src:pam-python] pam-python: accesses the internet during build
Added tag(s) patch.

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

Bug#834301: marked as done (ruby-fog-rackspace and ruby-fog: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 07:18:34 +
with message-id 
and subject line Bug#834301: fixed in ruby-fog-rackspace 0.1.1-2
has caused the Debian Bug report #834301,
regarding ruby-fog-rackspace and ruby-fog: error when trying to install together
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.)


-- 
834301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-fog,ruby-fog-rackspace
Version: ruby-fog/1.37.0-1
Version: ruby-fog-rackspace/0.1.1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-08-14
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:



Extracting templates from packages: 46%
Extracting templates from packages: 92%
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package libyaml-0-2:amd64.
(Reading database ... 10961 files and directories currently installed.)
Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
Selecting previously unselected package gcc-6-base:amd64.
Preparing to unpack .../gcc-6-base_6.1.1-11_amd64.deb ...
Unpacking gcc-6-base:amd64 (6.1.1-11) ...
Setting up gcc-6-base:amd64 (6.1.1-11) ...
(Reading database ... 10975 files and directories currently installed.)
Preparing to unpack .../libstdc++6_6.1.1-11_amd64.deb ...
Unpacking libstdc++6:amd64 (6.1.1-11) over (4.8.2-19) ...
Processing triggers for libc-bin (2.23-4) ...
Setting up libstdc++6:amd64 (6.1.1-11) ...
Processing triggers for libc-bin (2.23-4) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10989 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2h-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2h-1) ...
Selecting previously unselected package libgcrypt20:amd64.
Preparing to unpack .../libgcrypt20_1.7.2-2_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.7.2-2) ...
Selecting previously unselected package libicu57:amd64.
Preparing to unpack .../libicu57_57.1-2_amd64.deb ...
Unpacking libicu57:amd64 (57.1-2) ...
Selecting previously unselected package libxml2:amd64.
Preparing to unpack .../libxml2_2.9.4+dfsg1-1+b1_amd64.deb ...
Unpacking libxml2:amd64 (2.9.4+dfsg1-1+b1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.2h-1_amd64.deb ...
Unpacking openssl (1.0.2h-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20160104_all.deb ...
Unpacking ca-certificates (20160104) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.1+dfsg-1_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.1+dfsg-1) ...
Selecting previously unselected package libxslt1.1:amd64.
Preparing to unpack .../libxslt1.1_1.1.28-4_amd64.deb ...
Unpacking libxslt1.1:amd64 (1.1.28-4) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.10_all.deb ...
Unpacking rubygems-integration (1.10) ...
Selecting previously unselected package ruby-did-you-mean.
Preparing to unpack .../ruby-did-you-mean_1.0.0-2_all.deb ...
Unpacking ruby-did-you-mean (1.0.0-2) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.9.0-1_all.deb ...
Unpacking ruby-minitest (5.9.0-1) ...
Selecting previously unselected package ruby-net-telnet.
Preparing to unpack .../ruby-net-telnet_0.1.1-2_all.deb ...
Unpacking ruby-net-telnet (0.1.1-2) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.3.0-1_all.deb ...
Unpacking ruby-power-assert (0.3.0-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.7-2_all.deb ...
Unpacking ruby-test-unit (3.1.7-2) ...
Selecting previously unselected package libruby2.3:amd64.
Preparing to unpack .../libruby2.3_2.3.1-5_amd64.deb ...
Unpacking libruby2.3:amd64 (2.3.1-5) ...
Selecting previously unselected package ruby2.3.
Preparing to unpack .../ruby2.3_2.3.1-5_amd64.deb ...
Unpacking ruby2.3 (2.3.1-5) ...
Selecting previously unselected package ruby.
Preparing to unpack 

Bug#824740: marked as done (telepathy-ring: FTBFS: cp: cannot stat './AUTHORS--no-act': No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 08:44:59 +0200
with message-id <851a5456-7e8f-d3f5-b6d3-9caf4fb00...@adrianheine.de>
and subject line 
has caused the Debian Bug report #824740,
regarding telepathy-ring: FTBFS: cp: cannot stat './AUTHORS--no-act': 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.)


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

Dear Maintainer,

telepathy-ring fails to build from source in unstable/amd64:

  [..]

  # source='ring-conference-channel.c' object='ring-conference-channel.lo' 
libtool=yes 
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I.. -I../tests -I..  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c -o ring-conference-channel.lo 
ring-conference-channel.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../tests -I.. 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -c ring-conference-channel.c -o 
ring-conference-channel.o
  ring-conference-channel.c: In function 'ring_mergeable_conference_merge':
  ring-conference-channel.c:208:5: warning: 'tp_errors_quark' is deprecated: 
Use 'TP_ERROR' instead [-Wdeprecated-declarations]
   error = g_error_new(TP_ERRORS, TP_ERROR_INVALID_ARGUMENT,
   ^
  In file included from /usr/include/telepathy-1.0/telepathy-glib/handle.h:31:0,
   from 
/usr/include/telepathy-1.0/telepathy-glib/handle-repo.h:36,
   from 
/usr/include/telepathy-1.0/telepathy-glib/group-mixin.h:31,
   from ring-media-channel.h:26,
   from ring-conference-channel.h:35,
   from ring-conference-channel.c:40:
  /usr/include/telepathy-1.0/telepathy-glib/errors.h:39:8: note: declared here
   GQuark tp_errors_quark (void);
  ^
  ring-conference-channel.c: In function 
'ring_conference_channel_remove_member_with_reason':
  ring-conference-channel.c:630:5: warning: 'tp_errors_quark' is deprecated: 
Use 'TP_ERROR' instead [-Wdeprecated-declarations]
   g_set_error(error, TP_ERRORS, TP_ERROR_PERMISSION_DENIED,
   ^
  In file included from /usr/include/telepathy-1.0/telepathy-glib/handle.h:31:0,
   from 
/usr/include/telepathy-1.0/telepathy-glib/handle-repo.h:36,
   from 
/usr/include/telepathy-1.0/telepathy-glib/group-mixin.h:31,
   from ring-media-channel.h:26,
   from ring-conference-channel.h:35,
   from ring-conference-channel.c:40:
  /usr/include/telepathy-1.0/telepathy-glib/errors.h:39:8: note: declared here
   GQuark tp_errors_quark (void);
  ^
  ring-conference-channel.c: In function 'ring_conference_channel_join':
  ring-conference-channel.c:921:5: warning: 'tp_errors_quark' is deprecated: 
Use 'TP_ERROR' instead [-Wdeprecated-declarations]
   g_set_error(error, TP_ERRORS, TP_ERROR_INVALID_ARGUMENT,
   ^
  In file included from /usr/include/telepathy-1.0/telepathy-glib/handle.h:31:0,
   from 
/usr/include/telepathy-1.0/telepathy-glib/handle-repo.h:36,
   from 
/usr/include/telepathy-1.0/telepathy-glib/group-mixin.h:31,
   from ring-media-channel.h:26,
   from ring-conference-channel.h:35,
   from ring-conference-channel.c:40:
  /usr/include/telepathy-1.0/telepathy-glib/errors.h:39:8: note: declared here
   GQuark tp_errors_quark (void);

Bug#665616: marked as done (telepathy-ring: Including individual glib headers no longer supported)

[Debian Bug Tracking System]

Your message dated Fri, 26 Aug 2016 08:44:59 +0200
with message-id <851a5456-7e8f-d3f5-b6d3-9caf4fb00...@adrianheine.de>
and subject line 
has caused the Debian Bug report #665616,
regarding telepathy-ring: Including individual glib headers no longer supported
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.)


-- 
665616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-ring
Version: 2.1.0-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: glib-single-include

Hi,


including invidiual glib headers has been deprecated for several years.

Starting with glib 2.32 it is now mandatory to include glib.h instead
of individual headers [1], or the compiler will generate an error.

With the notable exception of:
 glib/gi18n.h
 glib/gi18n-lib.h
 glib/gprintf.h
 glib/gstdio.h
Those header files are still meant to be included separately.


Development releases of 2.32 (2.31.x) are available in experimental.
During a test-rebuild telepathy-ring failed to build with the new glib [2].

Please update telepathy-ring at your earliest convenience, so once we move
the glib version from experimental to unstable, your package will remain
buildable.

Usually, simply replacing #include  with #include 
is all that is needed (while keeping the above list of exceptions in
mind)
You can use the glib version from experimental to test if your package
builds correctly.


A simple shell script [3] has been written, that can help you
generate a patch which should fix the includes in most cases.
It's most likely not bug free and very limited, so please check the
resulting patch carefully.


Thanks!

Michael,
on behalf of the Debian GNOME team.

[1] 
http://git.gnome.org/browse/glib/commit/?id=7455dd370eb37ce3b0b409ff6120501f37b50569
[2] 
http://people.debian.org/~biebl/glib-single-include/telepathy-ring_2.1.0-1.log
[3] http://people.debian.org/~biebl/fix-glib-includes.sh



--- End Message ---
--- Begin Message ---
Version: 2.1.0-1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Aug 2016 23:31:37 +0200
Source: telepathy-ring
Binary: telepathy-ring
Architecture: source
Version: 2.1.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Telepathy maintainers 

Changed-By: Adrian Heine 
Description:
 telepathy-ring - GSM and 3G UMTS Telepathy connection manager
Closes: 620544 665616 791370 824740
Changes:
 telepathy-ring (2.1.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Jonny Lamb ]
   * Remove myself from Uploaders.
 .
   [ Hideki Yamane ]
   * debian/control
 - set it as "Architecture: linux-any" since ofono requires udev and the
   BlueZ stack (Closes: #620544).
 .
   [ Adrian Heine ]
   * Drop manual dbg package (Closes: #824740).
   * Import patch by Michael Biebl for including glib.h instead of individual
 headers (Closes: #665616).
   * build-depend on autotools-dev so that CDBS regenerates config.guess
 and config.sub (Closes: #791370).
Checksums-Sha1:
 5538881cde31c58e40f10c2c584c02288a58ec3d 2082 telepathy-ring_2.1.0-1.1.dsc
 505d8f6b41ab801c5a2f28092b96c9eac12b1cac 3216 telepathy-ring_2.1.0-1.1.diff.gz
Checksums-Sha256:
 cc2064d289242e656b758fc17b95a1810b4ae704bb8a8782abe1a6233ff4a8fa 2082 
telepathy-ring_2.1.0-1.1.dsc
 71c0448c1595864b6889a654ba2e7ccc427f779b0c82b270d81396dfc1cb5f63 3216 
telepathy-ring_2.1.0-1.1.diff.gz
Files:
 c8dc748957c4a669a992b5f9339dbd55 2082 net optional telepathy-ring_2.1.0-1.1.dsc
 4f607a0d8395e1cfc8dd169e4fe27b39 3216 net optional 
telepathy-ring_2.1.0-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJXurctAAoJEDEWul6f+mmjgAAQAJRjbnHT0SQ8b7EyBQFHTRJz
7JyfdhROFWIP0MZ6cFlIRgFxuS2ssywsH6lOa1HaBZnZoZcncuNvGV6PIui5+3Cm
3QQsyIexalcq5Y3rx5xOmjTWItVq41lGQhnzwBW37gaGKdBfQHpi0+MQPOkD7o8y
uePwOiTt0cUCMwd6Xqyq0r9RaWaeFlKmZwfOwllXbw3o1My4R6DFV1DScTc0gaE5
Vyk0JIyuqNi1+jKvZVYPk0BFxdjU6fglHLEs2iWc4OLOfd189IrqNh5s6bAnAHtO
NQ5z37whJT1ph2GH/9JzSI8Ei6KNZpJi+nmlyeCnCQbjV6byfS2hCTMzBRUIUNf3
OP4sPPXPMdx6vhgZFExdVUAQYNcGTZUv60wn62gcRg/q4l836PYR5HSVZfT5lWXc
Gka84DSEFJU1GEqTH1KtQIfkYju9yafwuQAsP7XvjvGUQgilFYMsZMt1clac5cDR
H4/qUnARixHkDAwjVZEWHwDXQU42gHFU9d35g/jW4NDM4DOKgMfu5b17uZDQFNWF
KMiUG4gaqqbFB0Ww2gYQm0B2xQ3qzeNgdIuvYGG0dynmwOzqyQjoUXoHmMPstteq
HSapmapULO9O6zkcxRHsBf9g06T+HQmcE+sCCY4r2XwLNw6R5+w4GveOJkMB+W/T
Ex3HHdtevbtwnscJOo9t
=KKK0
-END PGP SIGNATURE-
--- End Message ---

Processed: reassign to ruby-fog-rackspace

[Debian Bug Tracking System]

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

> reassign 834301 ruby-fog-rackspace
Bug #834301 [ruby-fog,ruby-fog-rackspace] ruby-fog-rackspace and ruby-fog: 
error when trying to install together
Bug reassigned from package 'ruby-fog,ruby-fog-rackspace' to 
'ruby-fog-rackspace'.
Ignoring request to alter found versions of bug #834301 to the same values 
previously set
Ignoring request to alter fixed versions of bug #834301 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#826300: [Pkg-pascal-devel] Bug#826300: Share knowledge on fpc and powerpc issue

[Graham Inggs]

On 18 August 2016 at 20:50, Paul Gevers  wrote:
> @Graham, I suggest you also get this done in Ubuntu soon, such that the
> next release has the latest fpc from Debian again.

Steve Langasek starting working through LP: #1562480 [1] and removing
powerpc binaries.
He found a false positive; 'laby' and a some packages not listed on
that bug that got their powerpc binaries copied from xenial; e.g.
'ztex-bmp' and 'winff'.  I'll add the missing packages to that bug.

BTW, I found that lazarus 1.6+dfsg-4 is FTBFS on amd64, arm64 and i386
in Ubuntu [2].
I tried rebuilding now, but they failed again.  1.6+dfsg-3 had built previously.
Tail of the build log:

Using buildid for compat level >= 9
dpkg-gencontrol: warning: Built-Using field of package
lazarus-ide-1.6: unknown substitution variable ${bu:version}
dpkg-gencontrol: warning: can't parse dependency fpc (= )
dpkg-gencontrol: error: error occurred while parsing Built-Using field: fpc (= )
Error: parsed ddeb section or priority is empty
debian/rules:401: recipe for target 'binary-arch' failed


[1] https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480
[2] https://launchpad.net/ubuntu/+source/lazarus/1.6+dfsg-4

Bug#834999: YAML::XS generates broken multiline strings

[Niko Tyni]

On Fri, Aug 26, 2016 at 12:10:29AM +0200, gregor herrmann wrote:
> On Sun, 21 Aug 2016 13:18:33 +0200, Marco d'Itri wrote:
> 
> > YAML::XS adds an extra \n at the end of each line.
> > The YAML module cannot read the generated files.
> > Test case attached.
> 
> This seems to be fixed in newer versions which we have in git.
> 
> The problem is that we have a lintian ftp-master autoreject problem:
> E: libyaml-libyaml-perl: embedded-library 
> usr/lib/perl5/auto/YAML/XS/LibYAML/LibYAML.so: libyaml
> 
> I've already created a branch gregoa/use-system-yaml which uses the
> system libyaml; no big deal, except that the tests fail because the
> embedded libyaml in libyaml-libyaml-perl is patched :/
> 
> Some time ago I updated the patch so that the tests pass; which
> always feels a bit cheap but according the the notes that past me
> added to the patch headers, the changes are related to changes in the
> embedded stuff and go back to original test code in the distribution.

Making it possible to use a system libyaml is discussed in
 https://github.com/ingydotnet/yaml-libyaml-pm/issues/49
and convincing upstream would be much better than doing so against their
wish, particularly as this would create a functionality difference.

The embedded libyaml is not a regression (see #664224) and not a release
critical issue as far as I am aware. The lintian tag is overriddable.

So I suggest we override the lintian error in order to fix this RC bug.
-- 
Niko Tyni   nt...@debian.org