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

[Xavier Grave]

I never got such error when using dsa, does the example is still running ?
Did you try :
netstat -ntap | grep LISTEN
In order to see what's is running and may collide with the bank example.

But if the example from the web page is running I think you have achieved a 
working polyorb package as far as I can see. Nice.

xavier

- Mail original -
De: "Svante Signell" 
À: "Xavier Grave" , 835...@bugs.debian.org
Cc: "Mattia Rizzolo" , debian-...@lists.debian.org
Envoyé: Mardi 6 Septembre 2016 16:31:50
Objet: Re: Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

On Tue, 2016-09-06 at 11:17 +0200, Xavier Grave wrote:
> You should also run the po_cos_naming, you can look at [1] in order to see how
> to "play" with dsa applications.
> 
> xavier
> [1] : http://wiki.ada-dk.org/a_dsa_tutorial
> 
The dsa exammple in that web page works!

The bank example almost works too:
(after changing 192.168.1.1:9099 to 127.0.0.1:9099)

./bank_server
...
Request : p

=> Print

   Customer : poor
   Password : 
   Balance  :  25

   Customer : middle
   Password : 
   Balance  :  250

   Customer : rich
   Password : 
   Balance  :  2500


Menu :

   Create
   Load
   Print
   Quit
   Save

Request : 

./bank_client
polyorb.utils.tcp_access_points: bind failed: [98] Address already in use

raised GNAT.SOCKETS.SOCKET_ERROR : [98] Address already in use

Bug#836927: assaultcube: FTBFS with GCC 6: error: 'float round(float)' conflicts with a previous declaration

[Andreas Beckmann]

Source: assaultcube
Version: 1.1.0.4+dfsg2-1.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

assaultcube FTBFS since the switch to GCC 6 (which defaults to -std=c++14) was 
made:

[...]
g++ -O3 -fomit-frame-pointer -g -Wall -fsigned-char -rdynamic -I. -Ibot 
-I../enet/include -I/usr/include `sdl-config --cflags` -idirafter ../include -o 
cube.h.gch.tmp cube.h
In file included from cube.h:8:0:
tools.h: In function 'float round(float)':
tools.h:58:34: error: 'float round(float)' conflicts with a previous declaration
 static inline float round(float x) { return floor(x + 0.5f); }
  ^
In file included from /usr/include/c++/6/math.h:36:0,
 from platform.h:9,
 from cube.h:7:
/usr/include/c++/6/cmath:1708:3: note: previous declaration 'constexpr float 
std::round(float)'
   round(float __x)
   ^
In file included from cube.h:53:0:
protos.h: In member function 'bool servercommandline::checkarg(const char*)':
protos.h:914:17: warning: this 'else' clause does not guard... 
[-Wmisleading-indentation]
 else if(ai > 0) maxdemos = ai; break;
 ^~~~
protos.h:914:48: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'else'
 else if(ai > 0) maxdemos = ai; break;
^
Makefile:138: recipe for target 'cube.h.gch' failed
make[1]: *** [cube.h.gch] Error 1


Andreas

Bug#836931: powder: FTBFS with GCC 6: error: narrowing conversion of ''\37777777611'' from 'char' to 'u8 {aka unsigned char}' inside { }

[Andreas Beckmann]

Source: powder
Version: 117-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source

Hi,

powder FTBFS since the gcc default was switched to gcc-6:


g++ -DLINUX -I ../../port/sdl `sdl-config --cflags` -c ../../glbdef.cpp -o 
../../glbdef.o -O3
../../glbdef.cpp:23:1: error: narrowing conversion of ''\3777607'' from 
'char' to 'u8 {aka unsigned char}' inside { } [-Wnarrowing]
 };
 ^
../../glbdef.cpp:23:1: error: narrowing conversion of ''\3777611'' from 
'char' to 'u8 {aka unsigned char}' inside { } [-Wnarrowing]
Makefile:54: recipe for target '../../glbdef.o' failed


(in case it does matter: this was observed on i386)


Andreas

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Sascha Steinbiss]

Hi Andreas,

> Back to the salmon issue:  When using the just uploaded rapmap and
> trying to prevent salmon's cmake from downloading it in a patch I'm now
> facing the next configure issue which seems that BOOST_INCLUDEDIR and
> BOOST_LIBRARYDIR are not found.  Any clue how to get the latest state
> of salmon Git build?

I’ll look at it.

Cheers
Sascha

> 
> Kind regards
> 
>  Andreas.
> 
> On Wed, Sep 07, 2016 at 10:31:17AM +0200, Andreas Tille wrote:
>> Hi,
>> 
>> thanks to Sascha's help I finalised rapmap, ITPed #836914 and uploaded.
>> 
>> Kind regards
>> 
>>   Andreas.
>> 
>> --
>> http://fam-tille.de
>> 
>> ___
>> Debian-med-packaging mailing list
>> debian-med-packag...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>> 
> 
> --
> http://fam-tille.de



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#836945: python-taurus: missing copyright file

[Andreas Beckmann]

Package: python-taurus
Version: 4.0.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package misses the
/usr/share/doc/python-taurus/copyright file.


Andreas


python-taurus_4.0.1+dfsg-1.log.gz
Description: application/gzip

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Sascha Steinbiss]

Hi Andreas,

> I'm now
> facing the next configure issue which seems that BOOST_INCLUDEDIR and
> BOOST_LIBRARYDIR are not found.  Any clue how to get the latest state
> of salmon Git build?

It was a missing build-dependency on libboost-timer-dev. I also added the 
necessary build-deps on libdivsufsort and libsparsehash, see git.

However, the build still fails with:

In file included from /build/salmon-0.7.1+ds1/include/UtilityFunctions.hpp:5:0,
 from /build/salmon-0.7.1+ds1/include/SBModel.hpp:7,
 from /build/salmon-0.7.1+ds1/src/SBModel.cpp:1:
/build/salmon-0.7.1+ds1/include/SalmonUtils.hpp:32:27: fatal error: 
RapMapUtils.hpp: No such file or directory

which suggests that salmon also uses parts of the previous embedded or 
downloaded RapMap source tree to build salmon, not just the binary.
I’m not familiar enough with RapMap’s intended use to decide whether we should 
introduce a rapmap-dev package given that it doesn’t seem to build a library. 
Any hints?

Cheers
Sascha

> 
> Kind regards
> 
>  Andreas.
> 
> On Wed, Sep 07, 2016 at 10:31:17AM +0200, Andreas Tille wrote:
>> Hi,
>> 
>> thanks to Sascha's help I finalised rapmap, ITPed #836914 and uploaded.
>> 
>> Kind regards
>> 
>>   Andreas.
>> 
>> --
>> http://fam-tille.de
>> 
>> ___
>> Debian-med-packaging mailing list
>> debian-med-packag...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>> 
> 
> --
> http://fam-tille.de



signature.asc
Description: Message signed with OpenPGP using GPGMail

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

[Xavier Grave]

No, I think you don't need more tests since you have found the conflict source 
as far as I understand.

I'm very short of time for the month - may be someone on debian-ada can test 
your patched package ? Can you provide an url to download it please ?

- Mail original -
De: "Svante Signell" 
À: "Xavier Grave" 
Cc: 835...@bugs.debian.org, "Mattia Rizzolo" , 
debian-...@lists.debian.org
Envoyé: Mercredi 7 Septembre 2016 13:00:33
Objet: Re: Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

Hi again,

seems like the conflicting application is qemu-system-x86_64 whichever port I
choose in examples/dsa/bank/polyorb.conf:
# cat polyorb.conf
[dsa]
name_service=corbaloc:iiop:1.2@127.0.0.1:9099/NameService/00024fF800
0
[iiop]
polyorb.protocols.iiop.default_port=5001

# cat namer/polyorb.conf
[iiop]
polyorb.protocols.iiop.default_port=9099

# netstat -ntap | grep LISTEN|less
8709/qemu-system-x8 
tcp0  0 0.0.0.0:50010.0.0.0:*   LISTEN

ps aux|grep 8709
root  8713  0.0  0.0  0 0 ?SAug24   0:00 [kvm-pit/8709]

In order to test properly I need to do that in an environment not running qemu,
like in a qemu linux guest. Unfortunately I cannot shut down all qemu instances
I have running on the box.

Do you want me to do that too? It will take a while.

On Wed, 2016-09-07 at 10:40 +0200, Xavier Grave wrote:
> I never got such error when using dsa, does the example is still running ?
> Did you try :
> netstat -ntap | grep LISTEN
> In order to see what's is running and may collide with the bank example.
> 
> But if the example from the web page is running I think you have achieved a
> working polyorb package as far as I can see. Nice.

Thanks!

Processed: your mail

[Debian Bug Tracking System]

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

> owner 836904 !
Bug #836904 [src:vsftpd] Depend eatmydata is unused and undesirable on 
productive systems
Owner recorded as Keng-Yu Lin .
>
End of message, stopping processing here.

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

Bug#836947: gnome-shell-extension-redshift: uninstallable in sid

[Andreas Beckmann]

Package: gnome-shell-extension-redshift
Version: 3.20.1-1
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

  The following packages have unmet dependencies:
   gnome-shell-extension-redshift : Depends: gnome-shell (< 3.21) but 3.21.91-2 
is to be installed


Cheers,

Andreas

Bug#836889: [Pkg-sugar-devel] Bug#836889: sugar: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Jonas Smedegaard]

Hi Chris,

Quoting Chris Lamb (2016-09-06 22:36:42)
> sugar fails to build from source in unstable/amd64:

>   /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
> resolved from binary package "stamp-autotools".  Stop.

I highly suspect that this was fixed in cdbs 0.145 released yesterday.

Nice if you could double-check if indeed this issue is closed.

 - Jonas

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

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


signature.asc
Description: signature

Bug#835035: marked as done (binutils-mingw-w64: FTBFS: Patches fail to apply)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 12:03:30 +
with message-id 
and subject line Bug#835035: fixed in binutils-mingw-w64 7
has caused the Debian Bug report #835035,
regarding binutils-mingw-w64: FTBFS: Patches fail to apply
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.)


-- 
835035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: binutils-mingw-w64
Version: 6.6
Severity: serious

>From my pbuilder build log:

...
# Revert gc-sections support for COFF and PE (#813144)
patch -d /build/binutils-mingw-w64-6.6/upstream -R -p1 <
debian/patches/coff-pe-gc-sections.patch
patching file bfd/coffcode.h
Hunk #2 succeeded at 5998 (offset 5 lines).
patching file bfd/coffgen.c
Unreversed patch detected!  Ignore -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file bfd/coffgen.c.rej
patching file bfd/libcoff-in.h
patching file bfd/libcoff.h
patching file ld/NEWS
Hunk #1 succeeded at 32 with fuzz 2 (offset 31 lines).
patching file ld/ld.texinfo
Hunk #1 succeeded at 1527 (offset 91 lines).
patching file ld/scripttempl/pe.sc
patching file ld/scripttempl/pep.sc
patching file ld/testsuite/lib/ld-lib.exp
Hunk #1 succeeded at 1690 (offset 80 lines).
debian/rules:27: recipe for target 'unpack-stamp' failed
make: *** [unpack-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: binutils-mingw-w64
Source-Version: 7

We believe that the bug you reported is fixed in the latest version of
binutils-mingw-w64, 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.
Stephen Kitt  (supplier of updated binutils-mingw-w64 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Sep 2016 13:53:50 +0200
Source: binutils-mingw-w64
Binary: binutils-mingw-w64 binutils-mingw-w64-i686 binutils-mingw-w64-x86-64
Architecture: source
Version: 7
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 binutils-mingw-w64 - Cross-binutils for Win32 and Win64 using MinGW-w64
 binutils-mingw-w64-i686 - Cross-binutils for Win32 (x86) using MinGW-w64
 binutils-mingw-w64-x86-64 - Cross-binutils for Win64 (x64) using MinGW-w64
Closes: 835035 836365
Changes:
 binutils-mingw-w64 (7) unstable; urgency=medium
 .
   * Adjust patches to build with binutils-mingw-w64 2.27 (Closes:
 #835035):
 - drop pr-16598-x64-import-libraries.patch, merged upstream;
 - drop coff-pe-gc-sections.patch, gcc 6 builds correctly with
   gc-sections;
 - disable the x86-64-mpx-inval-2 test which is currently broken;
 - stop disabling obsolete or fixed tests.
   * Update licensing information.
   * Clean up debian/control with cme.
   * Standards-Version 3.9.8, no change required.
   * Switch to debhelper compatibility level 9.
   * Enable all hardening options.
   * Fix a number of spelling mistakes.
   * Use quilt to apply the patches.
   * Disable some (broken) tests which activate when gcc-mingw-w64 is
 available.
   * Enable security flags by default: dynamicbase, nxcompat and
 high-entropy-va (the latter on x64); add linker flags to disable these
 (Closes: #836365).
Checksums-Sha1:
 f8d74d705c367c7b184b299b53793697fd704252 1831 binutils-mingw-w64_7.dsc
 e8781fc4adf3132918fbec9cec0f12eb2060bc7e 8676 binutils-mingw-w64_7.tar.xz
Checksums-Sha256:
 d253af17c9e324d0cb6917c10477aa8edccbce1c95c783bcd3b3088c5bba68fc 1831 
binutils-mingw-w64_7.dsc
 b051e1bc3f16b0efa7a8688aefd65943db0f8e27eeca31728c6c6dc06c4318a3 8676 
binutils-mingw-w64_7.tar.xz
Files:
 ac0660b26961d02b956d9b9ea14f850b 1831 devel extra binutils-mingw-w64_7.dsc
 b7011cb6a0303bee9684102f60aae641 8676 devel extra binutils-mingw-w64_7.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXz//sAAoJEIDTAvWIbYOcre0QAJ0kIaYP9mgiekIz9jntikDB

Bug#836948: getty-run: fails to remove: warning: getty-tty6: unable to open supervise/ok: file does not exist

[Andreas Beckmann]

Package: getty-run
Version: 2.1.2-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

  Removing getty-run (2.1.2-6) ...
  warning: getty-tty6: unable to open supervise/ok: file does not exist
  dpkg: error processing package getty-run (--remove):
   subprocess installed pre-removal script returned error exit status 1


cheers,

Andreas


getty-run_2.1.2-6.log.gz
Description: application/gzip

Bug#836930: mssstest: FTBFS with GCC 6: error: reference to 'rank' is ambiguous

[Andreas Beckmann]

Source: mssstest
Version: 3.0-4
Severity: serious
Justification: fails to build from source

Hi,

mssstest FTBFS since the default compiler was switched to gcc-6:

 debian/rules build
dh build
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
make -j1
make[1]: Entering directory '/build/mssstest-3.0'
g++ -g -O2 -fdebug-prefix-map=/build/mssstest-3.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -c neededroutines.cpp  -g -o neededroutines.o
neededroutines.cpp: In function 'float rankties(long unsigned int, float*, 
float*)':
neededroutines.cpp:172:3: error: reference to 'rank' is ambiguous
   rank(len, arr, intranks);
   ^~~~
neededroutines.cpp:138:6: note: candidates are: void rank(long unsigned int, 
float*, int*)
 void rank(unsigned long len, float arr[], int ranks[])
  ^~~~
In file included from /usr/include/c++/6/bits/move.h:57:0,
 from /usr/include/c++/6/bits/nested_exception.h:40,
 from /usr/include/c++/6/exception:171,
 from /usr/include/c++/6/ios:39,
 from /usr/include/c++/6/ostream:38,
 from /usr/include/c++/6/iostream:39,
 from neededroutines.h:1,
 from neededroutines.cpp:2:
/usr/include/c++/6/type_traits:1471:12: note: template 
struct std::rank
 struct rank
^~~~
makefile:10: recipe for target 'neededroutines.o' failed
make[1]: *** [neededroutines.o] Error 1
make[1]: Leaving directory '/build/mssstest-3.0'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2


Andreas

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Andreas Tille]

Hi,

thanks to Sascha's help I finalised rapmap, ITPed #836914 and uploaded.

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Bug#805962: witty: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

[Klaus Neuschwander]

Tags: patch

The changes Santiago Vila suggested do fix the FTBFS. However, it will
build all arch-dependent files (except the packages) anyway. Fixing that
would need further diving into the build system.

The attached patch makes the suggested changes. It applies against
3.3.5+dfsg-1 and 3.3.4+dfsg-6.
--- rules_original	2016-09-07 06:01:45.650884699 +0200
+++ rules	2016-09-07 05:39:22.320417413 +0200
@@ -242,28 +242,47 @@
 
 # Build architecture-independent files here.
 binary-indep: install
+	dh_testdir -i
+	dh_testroot -i
+	dh_installchangelogs -i Changelog
+	dh_installdocs -i
+	dh_installexamples -i
+	dh_install -i --sourcedir=debian/tmp/
+	dh_install -i --sourcedir=debian/tmp/
+	dh_installman -i
+	dh_lintian -i
+	dh_link -i
+	dh_strip -i --dbg-package=libwt-dbg
+	dh_compress -i -Xwt.doc -Xauth.doc -Xdbo.doc -XDoxyfile -X.html -X.C -X.h -X.txt -X.map -X.xml -X.js -X.csv -XWQApplication -X.qch -A
+	dh_makeshlibs -i -V
+	dh_shlibdeps -i -- -S$(CURDIR)/debian/tmp/usr/lib/
+	dh_fixperms -i
+	dh_installdeb -i
+	dh_gencontrol -i
+	dh_md5sums -i
+	dh_builddeb -i
 
 # Build architecture-dependent files here.
 binary-arch: install
-	dh_testdir
-	dh_testroot
-	dh_installchangelogs Changelog
-	dh_installdocs
-	dh_installexamples
-	dh_install --sourcedir=debian/tmp/
-	dh_install --sourcedir=debian/tmp/
-	dh_installman
-	dh_lintian
-	dh_link
-	dh_strip --dbg-package=libwt-dbg
-	dh_compress -Xwt.doc -Xauth.doc -Xdbo.doc -XDoxyfile -X.html -X.C -X.h -X.txt -X.map -X.xml -X.js -X.csv -XWQApplication -X.qch -A
-	dh_makeshlibs -V
+	dh_testdir -a
+	dh_testroot -a
+	dh_installchangelogs -a Changelog
+	dh_installdocs -a
+	dh_installexamples -a
+	dh_install -a --sourcedir=debian/tmp/
+	dh_install -a --sourcedir=debian/tmp/
+	dh_installman -a
+	dh_lintian -a
+	dh_link -a
+	dh_strip -a --dbg-package=libwt-dbg
+	dh_compress -a -Xwt.doc -Xauth.doc -Xdbo.doc -XDoxyfile -X.html -X.C -X.h -X.txt -X.map -X.xml -X.js -X.csv -XWQApplication -X.qch -A
+	dh_makeshlibs -a -V
 	dh_shlibdeps -a -- -S$(CURDIR)/debian/tmp/usr/lib/
-	dh_fixperms
-	dh_installdeb
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
+	dh_fixperms -a
+	dh_installdeb -a
+	dh_gencontrol -a
+	dh_md5sums -a
+	dh_builddeb -a
 
 binary: binary-indep binary-arch
 .PHONY: build clean binary-indep binary-arch binary install configure

Bug#834035: kdb5_util hangs forever

[Michael Welle]

Hello,

I've installed a test machine and everything looks good so far. Thank
you all who were involved in fixing this bug.

Regards
hmw

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Sascha Steinbiss]

Hi Andreas,

> thanks to Sascha's help I finalised rapmap, ITPed #836914 and uploaded.

You’re welcome. I was going to finish it yesterday but I since I couldn’t find 
a explicit copyright statement I raised 
https://github.com/COMBINE-lab/RapMap/issues/31. It looks like I could also 
have just used the lab as copyright holder, good to know. Maybe I was overly 
cautious as my current employer has quite strict rules who to use as copyright 
holder ;)

Cheers
Sascha


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#835708: Fwd: Bug#835708: [NMU] Re: Bug#835708: plplot: FTBFS: Tests failures [origin: a...@debian.org]

[Axel Beckert]

Dear Debian OCaml Maintainers,

do you by chance know any nicer solution for fixing plplot's FTBFS
than by dropping /usr/lib/ocaml/plcairo/ which is suddenly no more
build since somewhen between 8nd (last NMU) and 28th of August 2016
(bug report about FTBFS)?

If so I'd cancel or reschedule that NMU and do a new, less sacrificing
one.

(I tried to figure out any potentially causing packages using
which-pkg-broke, but as of now it only supports binary packages, so I
tried it with libplplot-ocaml and libplplot-dev, but that gave no
enlightning results.)

- Forwarded message from Axel Beckert  -
Date: Wed, 7 Sep 2016 02:01:06 +0200
From: Axel Beckert 
To: 835...@bugs.debian.org
Cc: Lucas Nussbaum , Ole Streicher 
Subject: Bug#835708: [NMU] Re: Bug#835708: plplot: FTBFS: Tests failures
Reply-To: Axel Beckert , 835...@bugs.debian.org

Dear Andrew,

Axel Beckert wrote:
> make[1]: Leaving directory 
> '/build/plplot-5.10.0+dfsg2/debian/build_tmp/bindings/qt_gui/pyqt4'
> touch install-python2.7
> touch install-python
> dh_movefiles -a --no-package=libplplot12 --no-package=libplplot-dev \
>  --no-package=python-plplot --no-package=python-plplot-qt   \
>  --no-package=libplplot-java --no-package=libplplot-ada1 \
>  --no-package=libplplot-ocaml --no-package=libplplot-lua \
>  --no-package=libplplot-d --no-package=libplplot-ada1-dev
> dh_movefiles --package=python-plplot-qt
> dh_movefiles --package=python-plplot
> dh_movefiles --package=libplplot-java
> dh_movefiles --package=libplplot-ocaml
> dh_movefiles: debian/tmp/usr/lib/ocaml/plcairo/META not found (supposed to 
> put it in libplplot-ocaml)
> debian/rules:147: recipe for target 'install-arch' failed
> make: *** [install-arch] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
> 
> So it seems as if the issue is somewhere in the ocaml bindings.

It seems as if the files for /usr/lib/ocaml/plcairo/ are no more built
for a reason unknown to me and independent of plplot. The remaining
libraries to be put into the libplplot-ocaml are still build.

Since /usr/lib/ocaml/plcairo/ seems to be only one part of the
libplplot-ocaml package and the remaining part looks functioning
without it, I decided to sacrifice that half of libplplot-ocaml to fix
the FTBFS and hence save all reverse dependencies from being removed
from testing. (libplplot-ocaml seems to have no reverse dependencies
not built from the plplot source package.)

After this mail, I'll upload an according fix as NMU to DELAYED/2.
Full source debdiff and libplplot-ocaml binary debdiff following. Feel
free to tell me to fast-forward or delay the upload a little bit more.

diff -Nru plplot-5.10.0+dfsg2/debian/changelog 
plplot-5.10.0+dfsg2/debian/changelog
--- plplot-5.10.0+dfsg2/debian/changelog2016-08-03 21:18:45.0 
+0200
+++ plplot-5.10.0+dfsg2/debian/changelog2016-09-07 01:29:02.0 
+0200
@@ -1,3 +1,11 @@
+plplot (5.10.0+dfsg2-0.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable installation of /usr/lib/ocaml/plcairo/ as it seems to no more
+be built. (Fixes FTBFS and hence closes: #835708)
+
+ -- Axel Beckert   Wed, 07 Sep 2016 01:29:02 +0200
+
 plplot (5.10.0+dfsg2-0.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru plplot-5.10.0+dfsg2/debian/libplplot-ocaml.files 
plplot-5.10.0+dfsg2/debian/libplplot-ocaml.files
--- plplot-5.10.0+dfsg2/debian/libplplot-ocaml.files2015-10-06 
23:58:30.0 +0200
+++ plplot-5.10.0+dfsg2/debian/libplplot-ocaml.files2016-09-07 
01:17:17.0 +0200
@@ -3,8 +3,8 @@
 usr/lib/ocaml/plplot/*.a
 usr/lib/ocaml/plplot/*.cm*
 usr/lib/ocaml/plplot/*.ml*
-usr/lib/ocaml/plcairo/META
-usr/lib/ocaml/plcairo/*.a
-usr/lib/ocaml/plcairo/*.cm*
-usr/lib/ocaml/plcairo/*.ml*
+#usr/lib/ocaml/plcairo/META
+#usr/lib/ocaml/plcairo/*.a
+#usr/lib/ocaml/plcairo/*.cm*
+#usr/lib/ocaml/plcairo/*.ml*
 usr/share/doc/libplplot-ocaml

[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/META
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/libplcairo_stubs.a
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.a
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.cma
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.cmi
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.cmxa
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.mli
-rw-r--r--  root/root   /usr/lib/ocaml/stublibs/dllplcairo_stubs.so

Control files: lines which differ (wdiff format)

Depends: libplplot12 (>= 5.10.0+dfsg2), ocaml-base-nox-4.02.3, libc6 (>= 
[-2.14), libcairo2 (>= 1.2.4)-] {+2.14)+}
Installed-Size: 

Bug#836888: marked as done (erlang-redis-client: FTBFS: Uncaught error in rebar_core)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 09:50:04 +
with message-id 
and subject line Bug#836888: fixed in erlang-redis-client 1.0.8-3
has caused the Debian Bug report #836888,
regarding erlang-redis-client: FTBFS: Uncaught error in rebar_core
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.)


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

Dear Maintainer,

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

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  erlang-redis-client
   Version:  1.0.8-2
   Build architecture:   amd64
   Date: Tue, 06 Sep 2016 21:27:54 +0100
   Hostname: ebd2af7d97c3
   Uname:Linux ebd2af7d97c3 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'erlang-redis-client-build-deps' in 
'../erlang-redis-client-build-deps_1.0.8-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package erlang-redis-client-build-deps.
  (Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack erlang-redis-client-build-deps_1.0.8-2_all.deb ...
  Unpacking erlang-redis-client-build-deps (1.0.8-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools rebar
  Suggested packages:
erlang erlang-manpages erlang-doc
  Recommended packages:
libsctp1 erlang-crypto mercurial
  The following NEW packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools rebar
  0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 9653 kB of archives.
  After this operation, 22.0 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 erlang-base amd64 
1:19.0.5+dfsg-3 [7073 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 erlang-dev amd64 
1:19.0.5+dfsg-3 [359 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 erlang-mnesia amd64 
1:19.0.5+dfsg-3 [747 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 erlang-runtime-tools 
amd64 1:19.0.5+dfsg-3 [205 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 erlang-tools amd64 
1:19.0.5+dfsg-3 [521 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 erlang-syntax-tools 
amd64 1:19.0.5+dfsg-3 [373 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 rebar amd64 2.6.2-2 
[203 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 dh-rebar all 0.0.4 
[7298 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 erlang-eunit amd64 
1:19.0.5+dfsg-3 [164 kB]
  Fetched 9653 kB in 0s (95.1 MB/s)
  Selecting previously unselected package erlang-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%

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

[Svante Signell]

Hi again,

seems like the conflicting application is qemu-system-x86_64 whichever port I
choose in examples/dsa/bank/polyorb.conf:
# cat polyorb.conf
[dsa]
name_service=corbaloc:iiop:1.2@127.0.0.1:9099/NameService/00024fF800
0
[iiop]
polyorb.protocols.iiop.default_port=5001

# cat namer/polyorb.conf
[iiop]
polyorb.protocols.iiop.default_port=9099

# netstat -ntap | grep LISTEN|less
8709/qemu-system-x8 
tcp0  0 0.0.0.0:50010.0.0.0:*   LISTEN

ps aux|grep 8709
root  8713  0.0  0.0  0 0 ?SAug24   0:00 [kvm-pit/8709]

In order to test properly I need to do that in an environment not running qemu,
like in a qemu linux guest. Unfortunately I cannot shut down all qemu instances
I have running on the box.

Do you want me to do that too? It will take a while.

On Wed, 2016-09-07 at 10:40 +0200, Xavier Grave wrote:
> I never got such error when using dsa, does the example is still running ?
> Did you try :
> netstat -ntap | grep LISTEN
> In order to see what's is running and may collide with the bank example.
> 
> But if the example from the web page is running I think you have achieved a
> working polyorb package as far as I can see. Nice.

Thanks!

Bug#836933: fdk-aac: FTBFS with GCC 6: error: narrowing conversion of '2975553344u' from 'unsigned int' to 'LONG {aka long int}' inside { }

[Andreas Beckmann]

Source: fdk-aac
Version: 0.1.3+20140816-2
Severity: serious
Tags: sid stretch
Justification: fails to build from source

Hi,

fdk-aac FTBFS since the default compiler was switched to gcc-6:

libtool: compile:  g++ -DPACKAGE_NAME=\"fdk-aac\" -DPACKAGE_TARNAME=\"fdk-aac\" 
-DPACKAGE_VERSION=\"0.1.3\" "-DPACKAGE_STRING=\"fdk-aac 0.1.3\"" 
-DPACKAGE_BUGREPORT=\"http://sourceforge.net/projects/opencore-amr/\;
 -DPACKAGE_URL=\"\" -DPACKAGE=\"fdk-aac\" -DVERSION=\"0.1.3\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -
DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. 
-I./libAACdec/include -I./libAACenc/include -I./libSBRdec/include 
-I./libSBRenc/include -I./libMpegTPDec/include -I./libMpegTPEnc/inclu
de -I./libSYS/include -I./libFDK/include -I./libPCMutils/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -fno-exceptions -fno-rtti -g -O2 
-fdebug-prefix-map=/build/fdk-aac-0.1.3+20140816=. -fstack-protector-strong 
-Wformat
 -Werror=format-security -c libAACenc/src/adj_thr.cpp  -fPIC -DPIC -o 
libAACenc/src/.libs/adj_thr.o
libAACenc/src/adj_thr.cpp:196:1: error: narrowing conversion of '2975553344u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
 };
 ^
libAACenc/src/adj_thr.cpp:196:1: error: narrowing conversion of '3204251762u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
libAACenc/src/adj_thr.cpp:210:1: error: narrowing conversion of '3274620506u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
 };
 ^
libAACenc/src/adj_thr.cpp:210:1: error: narrowing conversion of '3415357995u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
libAACenc/src/adj_thr.cpp:224:1: error: narrowing conversion of '3833172413u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
 };
 ^
libAACenc/src/adj_thr.cpp:224:1: error: narrowing conversion of '4261981948u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
libAACenc/src/adj_thr.cpp:224:1: error: narrowing conversion of '4272977064u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
libAACenc/src/adj_thr.cpp:224:1: error: narrowing conversion of '3415357995u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
libAACenc/src/adj_thr.cpp:224:1: error: narrowing conversion of '3498920878u' 
from 'unsigned int' to 'LONG {aka long int}' inside { } [-Wnarrowing]
Makefile:1264: recipe for target 'libAACenc/src/adj_thr.lo' failed
make[1]: *** [libAACenc/src/adj_thr.lo] Error 1


In case it does matter: this was observed on i386.


Andreas

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

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 11:18:59 +
with message-id 
and subject line Bug#834668: fixed in django-taggit 0.21.2-1
has caused the Debian Bug report #834668,
regarding django-taggit: FTBFS in testing (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.)


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


[...]
 debian/rules build-indep
dh build-indep --fail-missing --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--fail-missing -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--fail-missing -O--buildsystem=pybuild
   dh_auto_configure -i -O--fail-missing -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--fail-missing -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

Name:


>/tests/tests.py", line 156, in test_add_tag
self.assert_tags_equal(self.food_model.tags.all(), ['green'])
  File "/<>/tests/tests.py", line 45, in assert_tags_equal
self.assertEqual(got, tags)
AssertionError: Lists differ: [] != [u'green']

Second list contains 1 additional elements.
First extra element 0:
u'green'

- []
+ [u'green']

==
FAIL: test_prefetch_related (tests.tests.TaggableManagerDirectCustomPKTestCase)
--
Traceback (most recent call last):
  File "/<>/tests/tests.py", line 654, in test_prefetch_related
'apple': set(['1', '2'])
AssertionError: {u'orange': set([]), u'apple': set([])} != {u'orange': 
set([u'2', u'4']), u'apple': set([u'1', u'2'])}
- {u'apple': set([]), u'orange': set([])}
+ {u'apple': set([u'1', u'2']), u'orange': set([u'2', u'4'])}
? ++++


--
Ran 222 tests in 1.410s

FAILED (failures=7, skipped=1)
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
Destroying test database for alias 'default'...
debian/rules:8: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] 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: django-taggit
Source-Version: 0.21.2-1

We believe that the bug you reported is fixed in the latest version of
django-taggit, 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.
Michal Čihař  (supplier of updated django-taggit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Sep 2016 13:05:54 +0200
Source: django-taggit
Binary: python-django-taggit python3-django-taggit
Architecture: source all
Version: 0.21.2-1
Distribution: unstable
Urgency: medium
Maintainer: Michal Čihař 
Changed-By: Michal Čihař 
Description:
 python-django-taggit - simple tagging for Django (Python 2)

Bug#836938: exult: FTBFS with GCC 6: error: narrowing conversion of '255' from 'int' to 'char' inside { }

[Andreas Beckmann]

Source: exult
Version: 1.2-16.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

exult FTBFS since the default compiler was switched to gcc-6 with lots
of these errors:

exulticon.h:271:2: error: narrowing conversion of '255' from 'int' to 'char' 
inside { } [-Wnarrowing]


Andreas


exult_1.2-16.1.log.gz
Description: application/gzip

Bug#837040: RFS: btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: grave

Dear mentors,

I am looking for a sponsor for an urgent NMU of "btrfs-progs".  Upstream has 
marked this as an "urgent fix" < 
https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs-4.7.2_.28Sep_2016.29
 >

Sept 5th I filed bug #836778 notifying the maintainer of the issue.

Package name: btrfs-progs
Version : 4.7.1-1~bpo8+1
Section : admin

It builds these binary packages:

btrfs-progs - Checksumming Copy on Write Filesystem utilities
btrfs-progs-dbg - Checksumming Copy on Write Filesystem utilities (debug)
btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) (udeb)
btrfs-tools - transitional dummy package
btrfs-tools-dbg - transitional dummy package

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

  https://mentors.debian.net/package/btrfs-progs

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.7.1-1~bpo8+1.dsc

It is also available here:

  https://github.com/sten0/btrfs-progs.git

Changes since the last upload:

   * Non-maintainer upload.
   * New upstream release. (Closes #836778)

Regards,
Nicholas


signature.asc
Description: Digital signature

Bug#837040: RFS: btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]

[Adam Borowski]

On Thu, Sep 08, 2016 at 12:57:32AM -0400, Nicholas D Steeves wrote:
> Package: sponsorship-requests
> Severity: grave
> 
> I am looking for a sponsor for an urgent NMU of "btrfs-progs".  Upstream
> has marked this as an "urgent fix" <
> https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs-4.7.2_.28Sep_2016.29

> Package name: btrfs-progs
> Version : 4.7.1-1~bpo8+1

Except, you see, it's 4.7 and 4.7.1 which are the buggy versions, 4.6.1 is
unaffected.  So you demand, with a grave severity, to overwrite a known-good
version with one with a data loss bug.

-- 
Second "wet cat laying down on a powered on box-less SoC on the desk" close
shave in a week.  Protect your ARMs, folks!

Bug#837040: RFS: btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]

[Nicholas D Steeves]

On Thu, Sep 08, 2016 at 07:11:31AM +0200, Adam Borowski wrote:
> On Thu, Sep 08, 2016 at 12:57:32AM -0400, Nicholas D Steeves wrote:
> > Package: sponsorship-requests
> > Severity: grave
> > 
> > I am looking for a sponsor for an urgent NMU of "btrfs-progs".  Upstream
> > has marked this as an "urgent fix" <
> > https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs-4.7.2_.28Sep_2016.29
> 
> > Package name: btrfs-progs
> > Version : 4.7.1-1~bpo8+1
> 
> Except, you see, it's 4.7 and 4.7.1 which are the buggy versions, 4.6.1 is
> unaffected.  So you demand, with a grave severity, to overwrite a known-good
> version with one with a data loss bug.
> 
> -- 
> Second "wet cat laying down on a powered on box-less SoC on the desk" close
> shave in a week.  Protect your ARMs, folks!

I hit "r" instead of "g", so my last reply didn't make it to the bug-tracker.  
This is an error in my bug submission, and I am embarassed I made that mistake 
(too late here, I'm going to sleep).  It should read:

Package name: btrfs-progs
Version : 4.7.2-0.1

5 Sept (I think, it might have been earlier) I asked Gianfranco to cancel my 
bpo in the deferred queue because of this issue.

Thank you,
Nicholas


signature.asc
Description: Digital signature

Bug#837040: RFS: btrfs-progs/4.7.2-0.1 [RC NMU]

[Nicholas D Steeves]

Control: retitle -1 'RFS: btrfs-progs/4.7.2-0.1 [RC NMU]'

Was almost asleep and then realised this; here is the correct link:
 dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.7.2-0.1.dsc

Humble regards,
Nicholas


signature.asc
Description: Digital signature

Processed: Re: Bug#837040: RFS: btrfs-progs/4.7.2-0.1 [RC NMU]

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 'RFS: btrfs-progs/4.7.2-0.1 [RC NMU]'
Bug #837040 [sponsorship-requests] RFS: btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]
Changed Bug title to ''RFS: btrfs-progs/4.7.2-0.1 [RC NMU]'' from 'RFS: 
btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]'.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 14:00:11 +
with message-id 
and subject line Bug#811635: fixed in libfolia 1.3.1-1
has caused the Debian Bug report #811635,
regarding FTBFS with GCC 6: cannot convert x to y
to be marked as done.

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

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


-- 
811635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfolia
Version: 0.10-4.2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -I/usr/include/libxml2 -I/usr/include -fopenmp 
> -c document.cxx  -fPIC -DPIC -o .libs/document.o
> document.cxx: In member function 'bool folia::Document::save(std::ostream&, 
> const string&, bool)':
> document.cxx:250:12: error: cannot convert 'std::ostream {aka 
> std::basic_ostream}' to 'bool' in return
>  return os;
> ^~
> 
> Makefile:424: recipe for target 'document.lo' failed
> make[3]: *** [document.lo] Error 1
> make[3]: Leaving directory '/<>/src'
> Makefile:375: recipe for target 'all-recursive' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: libfolia
Source-Version: 1.3.1-1

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

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

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

Debian distribution maintenance software
pp.
Maarten van Gompel  (supplier of updated libfolia package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 30 Jul 2016 17:17:00 +0200
Source: libfolia
Binary: libfolia-dev libfolia4
Architecture: source amd64
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Maarten van Gompel 
Description:
 libfolia-dev - implementation of the FoLiA document format
 libfolia4  - implementation of the FoLiA document format
Closes: 734025 811635
Changes:
 libfolia (1.3.1-1) unstable; urgency=medium
 .
   * New upstream (Missed: v1.0, v1.2)
   * Updated descriptions
   * Website update
   * debian/watch update (now pointing to github)
   * Library version is now libfolia4 (so.4) instead of libfolia3 (so.3)
   * Compilation on GCC6 should be fixed with new upstream (Closes: #811635)
   * debian/rules, debian/control: add autoreconf in order to fix FTBFS
on ppc64el. Thanks Logan Rosen for the patch. (Closes: #734025)
   * debian/watch: point to 'make dist' tarball rather than
 bare sources
   * Applied cme fix dpkg
   * debian/copyright: fixed dep5-copyright-license-name-not-unique
   * Removed Joost van Baal-Ilić as uploader
Checksums-Sha1:
 87167db9ee49de05c630f16b5dfd283170025ee0 2113 libfolia_1.3.1-1.dsc
 c51d72151282973ecc34d4b8d5915aca8484ba94 479577 libfolia_1.3.1.orig.tar.gz
 7927cca51ef3b2abf833a0f8d835594458c5756f 3956 libfolia_1.3.1-1.debian.tar.xz
 09a6fe7c8aba8e8110804f1363578c4e3dd49279 36872 libfolia-dev_1.3.1-1_amd64.deb
 fd3984316755e3162a3d5706e8eaa39e62e0501b 1726722 
libfolia4-dbgsym_1.3.1-1_amd64.deb
 b0541e409985cc846bb29f4f182d68a7afc5c507 346804 libfolia4_1.3.1-1_amd64.deb
Checksums-Sha256:
 bec79e2d3b1822b199673c760dff7f399b5f872c284fef9257e2805c5e20a027 2113 
libfolia_1.3.1-1.dsc
 b2b9040b29cbef4910a0891b5080ea4e07af06cedeb70c42b90305b38ba4e854 479577 
libfolia_1.3.1.orig.tar.gz
 a6213871d4219fd28ab48753bf6564193cf62e6424ef1794eeca118b36201e5a 3956 
libfolia_1.3.1-1.debian.tar.xz
 

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Sascha Steinbiss]

Hi Andreas,

>> However, the build still fails with:
>> 
>> In file included from 
>> /build/salmon-0.7.1+ds1/include/UtilityFunctions.hpp:5:0,
>>from /build/salmon-0.7.1+ds1/include/SBModel.hpp:7,
>>from /build/salmon-0.7.1+ds1/src/SBModel.cpp:1:
>> /build/salmon-0.7.1+ds1/include/SalmonUtils.hpp:32:27: fatal error: 
>> RapMapUtils.hpp: No such file or directory
>> 
>> which suggests that salmon also uses parts of the previous embedded or 
>> downloaded RapMap source tree to build salmon, not just the binary.
>> I’m not familiar enough with RapMap’s intended use to decide whether we 
>> should introduce a rapmap-dev package given that it doesn’t seem to build a 
>> library. Any hints?
> 
> Possible quick-n-dirty, solution: Just add a code copy of
> RapMapUtils.hpp either as quilt patch or in debian/rapmap and copy over
> in build process.

Sure, that’s always an option.

> This might help us whether the new version would
> really fix the original build issue of #835720.

Looking at the error message, the original build issue looks like something I 
had to fix in RapMap as well, as there was a mismatch between the version of 
spdlog whose API salmon and RapMap were using and the one packaged in Debian. 
So I guess this will be fixed if we include Debian’s patched copy of the 
required RapMap code or — if not -- I know how to fix it.

> Proper solution is probably to contact upstream (I think its the same
> for rapmap and salmon) how to sensibly solve this issue.

I’d rather get it to work for now and will try including the smallest necessary 
set of code needed to build salmon. It is definitely more than one file; 
currently I’m using trial and error to arrive at a minimal set. I have also 
opened https://github.com/COMBINE-lab/salmon/issues/87, let’s see what they say.

Cheers
Sascha



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Andreas Tille]

On Wed, Sep 07, 2016 at 03:24:44PM +0100, Sascha Steinbiss wrote:
> 
> I’d rather get it to work for now and will try including the smallest 
> necessary set of code needed to build salmon. It is definitely more than one 
> file; currently I’m using trial and error to arrive at a minimal set. I have 
> also opened https://github.com/COMBINE-lab/salmon/issues/87, let’s see what 
> they say.

I guess you might be able to get the full set when checking my rapmap related 
quilt patch which contains a list.

Kind regards

   Andreas.


-- 
http://fam-tille.de

Bug#836953: asterisk: B-D libfreeradius-client-dev is gone

[Andreas Beckmann]

Source: asterisk
Version: 1:13.9.1~dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

the Build-Depends: libfreeradius-client-dev is no longer satisfiable
since freeradius-client has been removed from unstable.

The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Depends: libfreeradius-client-dev which is a 
virtual package and is not provided by any available package
 or
  libradiusclient-ng-dev which is a 
virtual package and is not provided by any available package

Unable to resolve dependencies!  Giving up...


Andreas

Processed: found 687463 in 2:2.0.5-1.1, found 793486 in 5.7.7-2.1

[Debian Bug Tracking System]

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

> found 687463 2:2.0.5-1.1
Bug #687463 [ocsinventory-agent] ocsinventory-agent: fails to purge - command 
ucf in postrm not found
Marked as found in versions ocsinventory-agent/2:2.0.5-1.1.
> found 793486 5.7.7-2.1
Bug #793486 [interchange-cat-standard] interchange-cat-standard: fails to 
install in sid: post-installation script returned error exit status 10
Marked as found in versions interchange/5.7.7-2.1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#836962: Uninstallable in testing when default-libmysqlclient-dev is installed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #836962 [libgdal-dev] Uninstallable in testing when 
default-libmysqlclient-dev is installed
Added tag(s) pending.

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

Bug#836961: r8168-dkms: Compilation error with linux-image-4.7.0-1-amd64

[Henry Precheur]

Package: r8168-dkms
Version: 8.042.00-1
Severity: serious
Tags: upstream
Justification: fails to build from source

Hi,

I tried to build r8168-dkms with the latest kernel image, and I get the
following errors:

/var/lib/dkms/r8168/8.042.00/build/r8168_n.c: In function 
‘rtl8168_init_one’:
/var/lib/dkms/r8168/8.042.00/build/r8168_n.c:22799:28: error: ‘struct 
net_device’ has no member named ‘gso_min_segs’
 dev->gso_min_segs = NIC_MIN_PHYS_BUF_COUNT;
^
/var/lib/dkms/r8168/8.042.00/build/r8168_n.c:22807:28: error: ‘struct 
net_device’ has no member named ‘gso_min_segs’
 dev->gso_min_segs = NIC_MIN_PHYS_BUF_COUNT;
^
/var/lib/dkms/r8168/8.042.00/build/r8168_n.c: In function 
‘rtl8168_start_xmit’:
/var/lib/dkms/r8168/8.042.00/build/r8168_n.c:24969:12: error: ‘struct 
net_device’ has no member named ‘trans_start’
 dev->trans_start = jiffies;
^
It looks like Arch Linux already has a patch for this:

  https://aur.archlinux.org/packages/r8168-dkms/

  https://gist.github.com/ozmartian/698c99ac7b9f4a5e5194f0591cd11ab0

Thank-you for your work, Cheers,

PS: I'm running kernel 4.6.0-1 to report the bug, but it happens with
linux-image-4.7.0-1-amd64, 4.6 is fine.

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

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

Versions of packages r8168-dkms depends on:
ii  dkms  2.2.1.0+git20160527-1

r8168-dkms recommends no packages.

r8168-dkms suggests no packages.

-- no debconf information

Bug#836962: Uninstallable in testing when default-libmysqlclient-dev is installed

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Enrico,

Thanks for reporting this issue.

I'm very disappointed that the introduction of the
default-libmysqlclient-dev packages now immediately results in RC bugs.

For now I've changed the dependency to default-libmysqlclient-dev, but
I'm considering dropping MySQL/MariaDB support because of my
disappointment in its maintainers.

Kind Regards,

Bas

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

Bug#796298: tcplay: FTBFS: CMake Error at CMakeLists.txt:30 (message): Could not find the devmapper library

[GCS]

Hi Michael,

On Wed, Sep 7, 2016 at 12:36 AM, Michael Prokop  wrote:
> * László Böszörményi [Wed Aug 26, 2015 at 07:28:02AM +0200]:
>> On Fri, Aug 21, 2015 at 10:10 AM, Chris Lamb  wrote:
>> > From a cursory glance, devmapper.pc specifies Requires.Private librt,
>> > which doesn't have a  librt.pc (which is likely correct as it's meant to
>> > be linked statically? I'll leave it to you).
>
>>  You are right in the sense that without 'Requires.private:' the
>> devmapper library is found correctly. On the other hand I don't think
>> static linking is mandatory as libdevmapper.so.* exists and is under
>> /lib (no need to have /usr mounted, can be used in emergency shells as
>> well). Can be a cmake issue? Will investigate further.
>
> Any news here, László? I'm asking because this is an RC bug and
> therefore preventing tcplay to enter Debian/stretch.
 Last checked by me in May and couldn't make it compile as far as I
can remember.

> This issue was also reported towards upstream:
>   https://github.com/bwalex/tc-play/issues/50
 This is a very different one.

> I was trying to reproduce it, though couldn't:
>
> | -- Checking for module 'devmapper'
> | --   Found devmapper, version 1.02.133
>
> Instead if fails with:
[...]
> when compiling against current Debian/unstable. It looks like that's
> an issue of static vs dynamic library linking. When replacing:
>
>   set (CFLAGS_COMMON "-std=c99 -fPIE ${CFLAGS_LINUX} ${CFLAGS_WARN} 
> ${CFLAGS_VER}")
>
> in CMakeLists.txt with (so adding the '-fPIC' option there):
>
>   set (CFLAGS_COMMON "-std=c99 -fPIE -fPIC ${CFLAGS_LINUX} ${CFLAGS_WARN} 
> ${CFLAGS_VER}")
>
> it indeed compiles for me.
 Indeed, this fixes the current issue.

> Can you please take care of an according fixed package upload?
 Sure, it's in its way.

Thanks for the heads-up,
Laszlo/GCS

Bug#836962: Uninstallable in testing when default-libmysqlclient-dev is installed

[Enrico Zini]

Package: libgdal-dev
Version: 2.1.1+dfsg-1+b1
Severity: serious

Hello,

now that default-libmysqlclient-dev is in testing and it depends on
libmariadbclient-dev-compat, libgdal-dev is not installable anymore:

  apt-get install libgdal-dev
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   libgdal-dev : Depends: libmysqlclient-dev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

It's probably enough to have libgdal-dev depend on
default-libmysqlclient-dev instead of libmysqlclient-dev, as per
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html


Thanks,

Enrico

-- 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=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgdal-dev depends on:
ii  libc6-dev  2.23-5
ii  libcurl4-gnutls-dev [libcurl-ssl-dev]  7.50.1-1
pn  libdap-dev 
pn  libgdal1h  
ii  libgeos-dev3.5.0-4
pn  libgif-dev 
ii  libhdf4-alt-dev4.2.12-1
ii  libhdf5-dev1.8.16+docs-8
ii  libjasper-dev  1.900.1-debian1-2.4+deb8u1
ii  libjpeg-dev1:1.5.0-1
ii  libjpeg62-turbo-dev [libjpeg-dev]  1:1.5.0-1
ii  libltdl-dev2.4.6-2
pn  libmysqlclient-dev 
ii  libnetcdf-dev  1:4.4.1-2
ii  libpng-dev 1.6.24-2
ii  libpq-dev  9.6~rc1-1
pn  libspatialite-dev  
ii  libsqlite3-dev 3.14.1-1
pn  libwebp-dev
pn  libxerces-c-dev
ii  unixodbc-dev   2.3.1-4.1

libgdal-dev recommends no packages.

Versions of packages libgdal-dev suggests:
pn  libgdal-doc  

Processed: block 836913 with 836208

[Debian Bug Tracking System]

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

> block 836913 with 836208
Bug #836913 [mesa] mesa: Please build with llvm-3.9
836913 was blocked by: 836960
836913 was not blocking any bugs.
Added blocking bug(s) of 836913: 836208
> thanks
Stopping processing here.

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

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Andreas Tille]

Hi Sascha,

On Wed, Sep 07, 2016 at 02:21:14PM +0100, Sascha Steinbiss wrote:
> 
> It was a missing build-dependency on libboost-timer-dev. I also added the 
> necessary build-deps on libdivsufsort and libsparsehash, see git.

Thanks for fixing.
 
> However, the build still fails with:
> 
> In file included from 
> /build/salmon-0.7.1+ds1/include/UtilityFunctions.hpp:5:0,
>  from /build/salmon-0.7.1+ds1/include/SBModel.hpp:7,
>  from /build/salmon-0.7.1+ds1/src/SBModel.cpp:1:
> /build/salmon-0.7.1+ds1/include/SalmonUtils.hpp:32:27: fatal error: 
> RapMapUtils.hpp: No such file or directory
> 
> which suggests that salmon also uses parts of the previous embedded or 
> downloaded RapMap source tree to build salmon, not just the binary.
> I’m not familiar enough with RapMap’s intended use to decide whether we 
> should introduce a rapmap-dev package given that it doesn’t seem to build a 
> library. Any hints?

Possible quick-n-dirty, solution: Just add a code copy of
RapMapUtils.hpp either as quilt patch or in debian/rapmap and copy over
in build process.  This might help us whether the new version would
really fix the original build issue of #835720.

Proper solution is probably to contact upstream (I think its the same
for rapmap and salmon) how to sensibly solve this issue.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#836669: caja: Crashes due to theme errors

[G. Heine]

Package: caja
Version: 1.14.2-1
Followup-For: Bug #836669

Dear Maintainer,

I encounter the same problem. Caja doesn't start at all.
The problem arose after the first restart after having upgraded several
packages (see below).

Syslog tells:

caja[3214]: Theme parsing error: mate-applications.css:415:16: not a number
caja[3214]: Theme parsing error: mate-applications.css:415:16: Expected a
string.
caja[3214]: Theme parsing error: other-applications.css:146:13: not a number
caja[3214]: Theme parsing error: other-applications.css:146:13: Expected a
string.
kernel: [   62.004994] caja[2880]: segfault at 7ffdaec61ea8 ip 7f2cf7bec7b6
sp 7ffdaec61ea0 error 6 in libc-2.23.so[7f2cf7bb2000+197000]

The first four lines also appear with mate-menu, mate-system-log or soffice.bin
instead of caja.

Other parts of MATE also segfault:
mate-power-mana[2918]: segfault at 7ffd39a51ff8 ip 7f8b81dfe7b6 sp
7ffd39a51ff0 error 6 in libc-2.23.so[7f8b81dc4000+197000]

Syslog also contains loads of error messages containing
"gtk_widget_size_allocate(): attempt to underallocate..." from wnck-applet and
synaptic which did not appear before yesterday's upgrade.
So it might be that the problem with caja is just a symptom of a defect in some
other package (but I am a layman with respect to programming).

Yesterday's changes on my system:

Commit Log for Tue Sep  6 12:24:16 2016

Die folgenden Pakete wurden aktualisiert:
gir1.2-gtk-3.0 (3.20.9-1) to 3.21.5-3
glib-networking (2.48.2-1) to 2.49.90-1
glib-networking-common (2.48.2-1) to 2.49.90-1
glib-networking-services (2.48.2-1) to 2.49.90-1
gnome-mahjongg (1:3.20.0-2) to 1:3.21.90-1
gnome-sudoku (1:3.20.4-1) to 1:3.21.90-1
gsettings-desktop-schemas (3.20.0-3) to 3.21.4-2
gtk-update-icon-cache (3.20.9-1) to 3.21.5-3
libgail-3-0 (3.20.9-1) to 3.21.5-3
libglib2.0-0 (2.48.1-3) to 2.49.6-1
libglib2.0-0:i386 (2.48.1-3) to 2.49.6-1
libglib2.0-bin (2.48.1-3) to 2.49.6-1
libglib2.0-data (2.48.1-3) to 2.49.6-1
libgtk-3-0 (3.20.9-1) to 3.21.5-3
libgtk-3-bin (3.20.9-1) to 3.21.5-3
libgtk-3-common (3.20.9-1) to 3.21.5-3
libjs-underscore (1.7.0~dfsg-1) to 1.8.3~dfsg-1
libnautilus-extension1a (3.20.1-3) to 3.20.3-1
python-imaging (3.3.0-1) to 3.3.1-1
python-pil (3.3.0-1) to 3.3.1-1
python3-pil (3.3.0-1) to 3.3.1-1
quadrapassel (1:3.20.0-2) to 1:3.21.90-1
sparky-desktop (20160811) to 20160905
swell-foop (1:3.20.0-2) to 1:3.21.91-1

Die folgenden Pakete wurden installiert:
libblkid1:i386 (2.28.1-1)
libmount1:i386 (2.28.1-1)

Updating further packages today didn't solve the problem.

Regards
G. Heine



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

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

Versions of packages caja depends on:
ii  caja-common   1.14.2-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.29.91-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-5
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.2-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.21.5-3
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.49.6-1
ii  libglib2.0-data   2.49.6-1
ii  libgtk-3-03.21.5-3
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.6-1

Versions of packages caja recommends:
ii  gvfs-backends  1.29.91-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
pn  gstreamer1.0-tools  
pn  meld

-- no debconf information

Bug#825320: gcc-doc-defaults: FTBFS in sid: error in 'Version' field string '5:': nothing after colon in version number

[Dmitry Eremin-Solenikov]

Package: gcc-doc
Followup-For: Bug #825320

The error with gnat-doc package version was most probably caused by the
missinchronization of gcc-doc-defaults rebuild vs. gnat defaults
changes. The attached patch should adds support for new GCC/GNAT/etc
packages defaulting to 6.x branch.

-- 
With best wishes
Dmitry


-- 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 gcc-doc depends on:
ii  gcc-6-doc  6.1.0-1

gcc-doc recommends no packages.

gcc-doc suggests no packages.

-- no debconf information
diff -Napur gcc-doc-defaults-14/debian/changelog gcc-doc-defaults-15/debian/changelog
--- gcc-doc-defaults-14/debian/changelog	2015-05-05 23:43:02.0 +0300
+++ gcc-doc-defaults-15/debian/changelog	2016-09-08 00:06:02.187292450 +0300
@@ -1,3 +1,9 @@
+gcc-doc-defaults (5:15) unstable; urgency=medium
+
+  * Updated to 6.1 versions. (Closes: #794778, #833505, #825320)
+
+ -- Dmitry Eremin-Solenikov   Wed, 07 Sep 2016 23:48:17 +0300
+
 gcc-doc-defaults (5:14) unstable; urgency=medium
 
   * Updated gcc/doc/ with upstream 4.9.1.
diff -Napur gcc-doc-defaults-14/debian/control gcc-doc-defaults-15/debian/control
--- gcc-doc-defaults-14/debian/control	2015-05-05 23:43:47.0 +0300
+++ gcc-doc-defaults-15/debian/control	2016-09-07 23:52:23.662784731 +0300
@@ -16,7 +16,7 @@ Vcs-Git: git://anonscm.debian.org/users/
 
 Package: gcc-doc
 Architecture: any
-Depends: gcc-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gcc-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Replaces: gcc (<< 4:4.1.1-7), g++ (<< 4:4.1.1-7)
 Breaks: gcc (<< 4:4.1.1-7), g++ (<< 4:4.1.1-7)
 Description: documentation for the GNU compilers (gcc, gobjc, g++)
@@ -27,7 +27,7 @@ Description: documentation for the GNU c
 
 Package: cpp-doc
 Architecture: any
-Depends: cpp-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: cpp-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Replaces: cpp (<< 4:4.1.1-7)
 Breaks: cpp (<< 4:4.1.1-7)
 Description: documentation for the GNU C preprocessor (cpp)
@@ -38,7 +38,7 @@ Description: documentation for the GNU C
 
 Package: gfortran-doc
 Architecture: any
-Depends: gfortran-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gfortran-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Replaces: gfortran (<< 4:4.1.1-7)
 Breaks: gfortran (<< 4:4.1.1-7)
 Description: documentation for the GNU Fortran Compiler (gfortran)
@@ -49,7 +49,7 @@ Description: documentation for the GNU F
 
 Package: gnat-doc
 Architecture: any
-Depends: gnat-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gnat-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Description: documentation for the GNU Ada Compiler (gnat)
  This is the dependency package that should install documentation
  for Debian default version of GNU Ada compiler.
@@ -58,7 +58,7 @@ Description: documentation for the GNU A
 
 Package: gcj-doc
 Architecture: any
-Depends: gcj-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gcj-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Replaces: gcj (<< 4:4.3.1-2)
 Breaks: gcj (<< 4:4.3.1-2)
 Description: documentation for the GNU Java tools (gcj, gij)
@@ -69,7 +69,7 @@ Description: documentation for the GNU J
 
 Package: gccgo-doc
 Architecture: amd64 arm64 armel armhf i386 ia64 mips mips64 mips64el mipsel powerpc ppc64 ppc64el s390 s390x x32
-Depends: gccgo-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gccgo-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Description: documentation for the GNU Go compiler (gccgo)
  This is the dependency package that should install documentation
  for Debian default version of GNU Go compiler.
diff -Napur gcc-doc-defaults-14/debian/rules gcc-doc-defaults-15/debian/rules
--- gcc-doc-defaults-14/debian/rules	2015-05-05 23:26:21.0 +0300
+++ gcc-doc-defaults-15/debian/rules	2016-09-07 23:52:07.337702255 +0300
@@ -12,6 +12,7 @@ DOC_VER_4.7 := 4.7.4-1~
 DOC_VER_4.8 := 4.8.4-1~
 DOC_VER_4.9 := 4.9.2-1~
 DOC_VER_5   := 5.1.0-1~
+DOC_VER_6   := 6.1.0-1~
 
 # The version for binary packages: gcc-doc-base, gcc-doc, etc.
 # Automatic set debian revision, adapted from gcc-defaults' rules.
@@ -27,15 +28,18 @@ DEBIAN_EPOCH := $(shell echo $(VDEF) | a
 #PKG_VER_4.8 := 4.8.4-1
 #PKG_VER_4.9 := 4.9.2-1
 #PKG_VER_5   := 5.1.0-1
+#PKG_VER_6   := 6.1.0-1
 
-PKG_VER_4.4 := 4.4.7-$(shell expr $(VMAJOR) - 4)
-PKG_VER_4.6 := 4.6.4-$(shell expr $(VMAJOR) - 5)
-PKG_VER_4.7 := 4.7.4-$(shell expr $(VMAJOR) - 9)
-PKG_VER_4.8 := 4.8.4-$(shell expr $(VMAJOR) - 13)
-PKG_VER_4.9 := 4.9.2-$(shell expr $(VMAJOR) - 13)
-PKG_VER_5   := 5.1.0-$(shell expr $(VMAJOR) - 13)
+PKG_VER_4.4 := 4.4.7-$(shell expr $(VMAJOR) - 5)
+PKG_VER_4.6 := 4.6.4-$(shell expr $(VMAJOR) - 6)
+PKG_VER_4.7 := 4.7.4-$(shell expr $(VMAJOR) - 10)
+PKG_VER_4.8 := 4.8.4-$(shell expr $(VMAJOR) - 

Bug#808312: chemps2: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/chemps2.1.gz

[Andreas Beckmann]

Followup-For: Bug #808312

Hi,

the fix seems to have disappeared, as can be seen in upgrades from
jessie-backports to stretch failing:

  Preparing to unpack .../chemps2_1.8-1_amd64.deb ...
  Unpacking chemps2 (1.8-1) over (1.6-1~bpo80+1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/chemps2_1.8-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/chemps2.1.gz', which is also in 
package libchemps2-1 1.6-1~bpo80+1


Andreas


chemps2_1.8-1.log.gz
Description: application/gzip

Bug#836968: marked as done (erlang-p1-oauth2: FTBFS: Missing Build-Depends on erlang-crypto)

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 23:54:00 +0200
with message-id 
and subject line Re: FTBFS: Missing Build-Depends on erlang-crypto
has caused the Debian Bug report #836968,
regarding erlang-p1-oauth2: FTBFS: Missing Build-Depends on erlang-crypto
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.)


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

Dear Maintainer,

erlang-p1-oauth2 fails to build from source in unstable/amd64 due to
missing Build-Depends on  erlang-crypto:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  erlang-p1-oauth2
   Version:  0.6.1-1
   Build architecture:   amd64
   Date: Wed, 07 Sep 2016 17:38:25 +0100
   Hostname: e2d200a4c95d
   Uname:Linux e2d200a4c95d 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'erlang-p1-oauth2-build-deps' in 
'../erlang-p1-oauth2-build-deps_0.6.1-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package erlang-p1-oauth2-build-deps.
  (Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack erlang-p1-oauth2-build-deps_0.6.1-1_all.deb ...
  Unpacking erlang-p1-oauth2-build-deps (0.6.1-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-meck erlang-mnesia
erlang-proper erlang-proper-dev erlang-runtime-tools erlang-syntax-tools
erlang-tools rebar
  Suggested packages:
erlang erlang-manpages erlang-doc
  Recommended packages:
libsctp1 erlang-crypto mercurial
  The following NEW packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-meck erlang-mnesia
erlang-proper erlang-proper-dev erlang-runtime-tools erlang-syntax-tools
erlang-tools rebar
  0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 9987 kB of archives.
  After this operation, 22.6 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 erlang-base amd64 
1:19.0.5+dfsg-3 [7073 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 erlang-dev amd64 
1:19.0.5+dfsg-3 [359 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 erlang-mnesia amd64 
1:19.0.5+dfsg-3 [747 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 erlang-runtime-tools 
amd64 1:19.0.5+dfsg-3 [205 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 erlang-tools amd64 
1:19.0.5+dfsg-3 [521 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 erlang-syntax-tools 
amd64 1:19.0.5+dfsg-3 [373 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 rebar amd64 2.6.2-2 
[203 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 dh-rebar all 0.0.4 
[7298 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 erlang-eunit amd64 
1:19.0.5+dfsg-3 [164 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 erlang-proper amd64 
1.1+gitfa58f82bdc+dfsg-1 [269 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 erlang-proper-dev 
amd64 1.1+gitfa58f82bdc+dfsg-1 [4958 B]
  Get:12 http://httpredir.debian.org/debian 

Bug#836509: marked as done (glance: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 22:20:39 +0200
with message-id <0ab76b03-ea25-d971-437a-d6e9c49dc...@debian.org>
and subject line Re: [PKG-Openstack-devel] Bug#836509: glance: FTBFS in testing 
(failing tests)
has caused the Debian Bug report #836509,
regarding glance: FTBFS in testing (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.)


-- 
836509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glance
Version: 2:12.0.0-4
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
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,sphinxdoc,systemd
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions

[... snipped ...]

glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_non_integer_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_non_integer_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_asc
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_asc
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_bad_value
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_bad_value
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_key_id
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_key_id
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_strip_params_from_filters
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_strip_params_from_filters
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_filter_and_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_filter_and_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_many_filter
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_many_filter
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_zero_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_zero_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create_ensure_expires_at_is_not_returned
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create_ensure_expires_at_is_not_returned
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get_ensure_expires_at_not_returned
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get_ensure_expires_at_not_returned
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_carries_query_parameters
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_carries_query_parameters
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_next_marker
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_next_marker
 ... ok

==
FAIL: glance.tests.unit.common.test_utils.TestUtils.test_validate_key_cert_key

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Sascha Steinbiss]

Hi Andreas,

>> I’d rather get it to work for now and will try including the smallest 
>> necessary set of code needed to build salmon. It is definitely more than one 
>> file; currently I’m using trial and error to arrive at a minimal set. I have 
>> also opened https://github.com/COMBINE-lab/salmon/issues/87, let’s see what 
>> they say.
> 
> I guess you might be able to get the full set when checking my rapmap related 
> quilt patch which contains a list.

True. BTW it builds now with some RapMap code added back in (see git) but one 
of the unit tests fails ATM — I’ll take a look tomorrow.

Good night
Sascha


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

[Andreas Beckmann]

Package: golang-doc
Version: 2:1.7~1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

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

  Preparing to unpack .../golang-go_2%3a1.7~1_i386.deb ...
  dpkg-maintscript-helper: error: directory '/usr/lib/go' contains files not 
owned by package golang-go:i386, cannot switch to symlink
  dpkg: error processing archive 
/var/cache/apt/archives/golang-go_2%3a1.7~1_i386.deb (--unpack):
   subprocess new pre-installation script returned error exit status 1


cheers,

Andreas


golang-doc_2:1.7~1.log.gz
Description: application/gzip

Processed: unarchiving 823574, found 823574 in 2.2.0-2~bpo80+1

[Debian Bug Tracking System]

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

> unarchive 823574
Bug #823574 {Done: Ondřej Surý } [knot] knot: fails to 
upgrade from 'jessie': Error: syntax error (file 
'/var/backups/knot/20160503-122201/knot.conf', line 6)
Unarchived Bug 823574
> found 823574 2.2.0-2~bpo80+1
Bug #823574 {Done: Ondřej Surý } [knot] knot: fails to 
upgrade from 'jessie': Error: syntax error (file 
'/var/backups/knot/20160503-122201/knot.conf', line 6)
Marked as found in versions knot/2.2.0-2~bpo80+1.
> thanks
Stopping processing here.

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

Bug#836989: fontforge-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/mime/packages/fontforge.xml

[Andreas Beckmann]

Package: fontforge-common
Version: 1:20160404~dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + fontforge

Hi,

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

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

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

  Preparing to unpack .../0-fontforge-common_1%3a20160404~dfsg-3_all.deb ...
  Unpacking fontforge-common (1:20160404~dfsg-3) over (20120731.b-7.2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-UtugTa/0-fontforge-common_1%3a20160404~dfsg-3_all.deb 
(--unpack):
   trying to overwrite '/usr/share/mime/packages/fontforge.xml', which is also 
in package fontforge 20120731.b-7.2
  Preparing to unpack .../1-fontforge_1%3a20160404~dfsg-3_amd64.deb ...
  Unpacking fontforge (1:20160404~dfsg-3) over (20120731.b-7.2) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-UtugTa/0-fontforge-common_1%3a20160404~dfsg-3_all.deb
 

cheers,

Andreas


fontforge_1:20160404~dfsg-3.log.gz
Description: application/gzip

Processed: fontforge-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/mime/packages/fontforge.xml

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + fontforge
Bug #836989 [fontforge-common] fontforge-common: fails to upgrade from 'sid' - 
trying to overwrite /usr/share/mime/packages/fontforge.xml
Added indication that 836989 affects fontforge

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

Bug#802021: audacity: non-free files

[James Cowgill]

Hi,

On 07/09/16 20:26, Herbert Fortes wrote:
>>
>> Files in "lib-src/libnyquist/nyquist/xlisp" have the following in the
> header:
>>
>> Copyright (c) 1985, by David Michael Betz
>> All Rights Reserved
>> Permission is granted for unrestricted non-commercial use
>>
> 
> I tried to send an email to David Michael Betz
> but the email returns. I tried to email address:

There seems to be a more recent version of xlisp on this site:
http://www.xlisp.org/

It has another email address (which I've CCed). Hopefully it works!

Maybe part of the solution to this bug is to update audacity's copy of
xlisp to this new version which seems to be under the BSD 3-clause license?

(of course there are some other non-free files to look at as well)

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + science-geography
Bug #836993 [qgis] qgis: fails to upgrade from 'jessie': dpkg-divert: error: 
rename involves overwriting `/usr/bin/qgis'
Added indication that 836993 affects science-geography

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

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

[Paul Novotny]

On Tue, Sep 6, 2016 at 4:06 PM, Andreas Tille  wrote:

[Paul, I wonder whether you realised the problems with opensurgsim]


Thanks for the heads up. Graham's GCC6 patch works for me. I'll get it 
applied upstream.



Hi Graham,

On Thu, Aug 25, 2016 at 02:37:53PM +0200, Graham Inggs wrote:

 Hi Maintainer

 The attached patch fixes the FTBFS with GCC 6.
 I'll open a separate bug for the eigen3 issue and mark it as being 
blocked

 by #835411.


I checked building opensurgsim and while I have not realised any
problems directly hinting to eigen3 I've got:

...
 2 FAILED TESTS

  Start 12: SurgSimPhysicsTest
12/12 Test #12: SurgSimPhysicsTest ...   Passed0.64 
sec


92% tests passed, 1 tests failed out of 12

Total Test time (real) =   8.99 sec

The following tests FAILED:
 11 - SurgSimMathTest (Failed)
Errors while running CTest
Makefile:130: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory 
'/build/opensurgsim-0.6.0/obj-x86_64-linux-gnu'


I am building now to see if I can reproduce this. SurgSimMathTest 
failure might be related to Eigen, but I'll let you know what I find.


-Paul

Bug#836508: marked as done (barbican: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 22:17:48 +0200
with message-id <9a014c87-b5c1-62d6-d3c2-eb870a0db...@debian.org>
and subject line Re: Bug#836508: barbican: FTBFS in testing (failing tests)
has caused the Debian Bug report #836508,
regarding barbican: FTBFS in testing (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.)


-- 
836508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:barbican
Version: 1:2.0.0-5
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
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,systemd,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_large_statuses_clipped
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_large_statuses_clipped
 ... ok
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_no_follow_on_needed
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_no_follow_on_needed
 ... ok
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_retrieve_entity
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_retrieve_entity
 ... ok

==
FAIL: 
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_no_file_storage
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_no_file_storage
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 166, in 
test_gen_cert_no_file_storage
self.verify_sig(cert_enc)
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 157, in verify_sig
crypto.verify(self.ca.cert, sig[1:], der[0], 'sha256')
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2605, in 
verify
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


==
FAIL: 
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_with_file_storage
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_with_file_storage
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 182, in 
test_gen_cert_with_file_storage
self.verify_sig(cert_enc)
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 157, in verify_sig
crypto.verify(self.ca.cert, sig[1:], der[0], 'sha256')
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2605, in 
verify
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


--
Ran 1216 tests in 80.278s

FAILED (failures=2, skipped=4)
debian/rules:20: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2

Processed: libcamitk4: fails to upgrade from 'jessie' - trying to overwrite /usr/bin/camitk-config

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + med-imaging-dev med-imaging
Bug #836990 [libcamitk4] libcamitk4: fails to upgrade from 'jessie' - trying to 
overwrite /usr/bin/camitk-config
Added indication that 836990 affects med-imaging-dev and med-imaging

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

Processed: Re: Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #836993 [qgis] qgis: fails to upgrade from 'jessie': dpkg-divert: error: 
rename involves overwriting `/usr/bin/qgis'
Added tag(s) pending.

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

Processed: unarchiving 808312, found 808312 in 1.8-1

[Debian Bug Tracking System]

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

> unarchive 808312
Bug #808312 {Done: Sebastian Wouters } [chemps2] 
chemps2: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/man/man1/chemps2.1.gz
Unarchived Bug 808312
> found 808312 1.8-1
Bug #808312 {Done: Sebastian Wouters } [chemps2] 
chemps2: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/man/man1/chemps2.1.gz
Marked as found in versions chemps2/1.8-1 and reopened.
> thanks
Stopping processing here.

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

Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Andreas,

Thanks for your work on piuparts.

I've moved the diversion removal to postinst per your suggestion, thanks!

A new upload to unstable will follow shortly.

Kind Regards,

Bas

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

Bug#836508: barbican: FTBFS in testing (failing tests)

[Santiago Vila]

On Wed, 7 Sep 2016, Thomas Goirand wrote:

> Santiago,
> 
> Please don't play BTS pingpong. This bug shall stay closed. The issue
> was in pyopenssl, and never in Barbican.
> 
> We don't increase version numbers just to avoid bugs. It has never been
> done, and will never be done. Otherwise, we'd be doing this for every
> single bug sent to the BTS, multiplied by the number of reverse
> dependencies.

That's a straw man argument, at least for two reasons:

* Not every bug sent to the BTS is a bug which make other packages to FTBFS.
* We sometimes increase version numbers to avoid FTBFS bugs.

Therefore, asking for a version increase was not as unreasonable as
you paint it.

If you consider that this is not necessary in this particular case,
so be it, but please don't use fallacious arguments.

Thanks.

Bug#836970: marked as done (erlang-p1-sqlite3: FTBFS: Missing Build-Depends on erlang-crypto)

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 23:54:00 +0200
with message-id 
and subject line Re: FTBFS: Missing Build-Depends on erlang-crypto
has caused the Debian Bug report #836970,
regarding erlang-p1-sqlite3: FTBFS: Missing Build-Depends on erlang-crypto
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.)


-- 
836970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-p1-sqlite3
Version: 1.1.5~dfsg0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Tags: patch
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

erlang-p1-sqlite3 fails to build from source in unstable/amd64 due to
missing Build-Depends on erlang-crypto:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  erlang-p1-sqlite3
   Version:  1.1.5~dfsg0-1
   Build architecture:   amd64
   Date: Wed, 07 Sep 2016 17:38:40 +0100
   Hostname: 2119ab903179
   Uname:Linux 2119ab903179 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'erlang-p1-sqlite3-build-deps' in 
'../erlang-p1-sqlite3-build-deps_1.1.5~dfsg0-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package erlang-p1-sqlite3-build-deps.
  (Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack erlang-p1-sqlite3-build-deps_1.1.5~dfsg0-1_all.deb ...
  Unpacking erlang-p1-sqlite3-build-deps (1.1.5~dfsg0-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools libsqlite3-dev rebar
  Suggested packages:
erlang erlang-manpages erlang-doc sqlite3-doc
  Recommended packages:
libsctp1 erlang-crypto mercurial
  The following NEW packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools libsqlite3-dev rebar
  0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 10.3 MB of archives.
  After this operation, 24.1 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 erlang-base amd64 
1:19.0.5+dfsg-3 [7073 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 erlang-dev amd64 
1:19.0.5+dfsg-3 [359 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 erlang-mnesia amd64 
1:19.0.5+dfsg-3 [747 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 erlang-runtime-tools 
amd64 1:19.0.5+dfsg-3 [205 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 erlang-tools amd64 
1:19.0.5+dfsg-3 [521 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 erlang-syntax-tools 
amd64 1:19.0.5+dfsg-3 [373 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 rebar amd64 2.6.2-2 
[203 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 dh-rebar all 0.0.4 
[7298 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 erlang-eunit amd64 
1:19.0.5+dfsg-3 [164 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libsqlite3-dev amd64 
3.14.1-1 [689 kB]
  Fetched 10.3 MB in 0s (61.3 MB/s)
  Selecting previously unselected package erlang-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%

Bug#836969: marked as done (erlang-p1-xmlrpc: FTBFS: Missing Build-Depends on erlang-crypto)

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 23:54:00 +0200
with message-id 
and subject line Re: FTBFS: Missing Build-Depends on erlang-crypto
has caused the Debian Bug report #836969,
regarding erlang-p1-xmlrpc: FTBFS: Missing Build-Depends on erlang-crypto
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.)


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

Dear Maintainer,

erlang-p1-xmlrpc fails to build from source in unstable/amd64 due to
missing Build-Depends on erlang-crypto:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  erlang-p1-xmlrpc
   Version:  1.15.1-2
   Build architecture:   amd64
   Date: Wed, 07 Sep 2016 17:38:54 +0100
   Hostname: eba892046709
   Uname:Linux eba892046709 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'erlang-p1-xmlrpc-build-deps' in 
'../erlang-p1-xmlrpc-build-deps_1.15.1-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package erlang-p1-xmlrpc-build-deps.
  (Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack erlang-p1-xmlrpc-build-deps_1.15.1-2_all.deb ...
  Unpacking erlang-p1-xmlrpc-build-deps (1.15.1-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools erlang-xmerl rebar
  Suggested packages:
erlang erlang-manpages erlang-doc
  Recommended packages:
libsctp1 erlang-crypto mercurial
  The following NEW packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools erlang-xmerl rebar
  0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 10.6 MB of archives.
  After this operation, 23.7 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 erlang-base amd64 
1:19.0.5+dfsg-3 [7073 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 erlang-dev amd64 
1:19.0.5+dfsg-3 [359 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 erlang-mnesia amd64 
1:19.0.5+dfsg-3 [747 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 erlang-runtime-tools 
amd64 1:19.0.5+dfsg-3 [205 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 erlang-tools amd64 
1:19.0.5+dfsg-3 [521 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 erlang-syntax-tools 
amd64 1:19.0.5+dfsg-3 [373 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 rebar amd64 2.6.2-2 
[203 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 dh-rebar all 0.0.4 
[7298 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 erlang-eunit amd64 
1:19.0.5+dfsg-3 [164 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 erlang-xmerl amd64 
1:19.0.5+dfsg-3 [985 kB]
  Fetched 10.6 MB in 0s (64.0 MB/s)
  Selecting previously unselected package erlang-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading 

Bug#836995: texlive-base: fails to upgrade wheezy -> jessie -> stretch

[Andreas Beckmann]

Package: texlive-base
Version: 2016.20160819-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + tex4ht

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy' to 'jessie' to 'stretch'.
It installed fine in 'wheezy', and upgraded to 'jessie' successfully,
but then the upgrade to 'stretch' failed.

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

  Selecting previously unselected package texlive-base.
  Preparing to unpack .../texlive-base_2016.20160819-2_all.deb ...
  Unpacking texlive-base (2016.20160819-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-base_2016.20160819-2_all.deb (--unpack):
   trying to overwrite '/usr/share/texlive/tlpkg/TeXLive/TLConfFile.pm', which 
is also in package texlive-common 2012.20120611-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


Please add appropriate Breaks+Replaces against texlive-common/wheezy
which may have survived some wheezy->jessie upgrades.


cheers,

Andreas


tex4ht_20160814-1.log.gz
Description: application/gzip

Processed: fixed 836970 in 1.1.5~dfsg0-2

[Debian Bug Tracking System]

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

> fixed 836970 1.1.5~dfsg0-2
Bug #836970 {Done: Philipp Huebner } 
[src:erlang-p1-sqlite3] erlang-p1-sqlite3: FTBFS: Missing Build-Depends on 
erlang-crypto
Marked as fixed in versions erlang-p1-sqlite3/1.1.5~dfsg0-2.
> thanks
Stopping processing here.

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

Processed: fixed 836969 in 1.15.1-3

[Debian Bug Tracking System]

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

> fixed 836969 1.15.1-3
Bug #836969 {Done: Philipp Huebner } 
[src:erlang-p1-xmlrpc] erlang-p1-xmlrpc: FTBFS: Missing Build-Depends on 
erlang-crypto
Marked as fixed in versions erlang-p1-xmlrpc/1.15.1-3.
> thanks
Stopping processing here.

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

Bug#823574: knot: fails to upgrade from 'jessie': Error: syntax error (file '/var/backups/knot/20160503-122201/knot.conf', line 6)

[Andreas Beckmann]

Followup-For: Bug #823574

Please update the package in jessie-backports to a fixed version.

Thanks


Andreas

Bug#836962: Uninstallable in testing when default-libmysqlclient-dev is installed

[Enrico Zini]

On Wed, Sep 07, 2016 at 06:09:16PM +0200, Sebastiaan Couwenberg wrote:

> I'm very disappointed that the introduction of the
> default-libmysqlclient-dev packages now immediately results in RC bugs.
> 
> For now I've changed the dependency to default-libmysqlclient-dev, but
> I'm considering dropping MySQL/MariaDB support because of my
> disappointment in its maintainers.

Hi, thanks for dealing with this so quickly.

Note that it might have been a misjudgement of mine to set severity of
this bug to serious, rather than a fault of the mysql/mariadb
mainatainers.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


signature.asc
Description: PGP signature

Bug#837005: mate-applets: FTBFS: ./cpufreq/src/cpufreq-monitor-libcpufreq.c:118: undefined reference to `cpupower_is_cpu_online'

[Lucas Nussbaum]

Source: mate-applets
Version: 1.14.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security  -fPIE -pie -Wl,-z,relro -Wl,-z,now -o 
> mate-cpufreq-applet cpufreq-applet.o cpufreq-utils.o cpufreq-prefs.o 
> cpufreq-selector.o cpufreq-popup.o cpufreq-monitor.o 
> cpufreq-monitor-factory.o cpufreq-monitor-procfs.o cpufreq-monitor-sysfs.o 
> cpufreq-monitor-libcpufreq.o cpufreq-monitor-cpuinfo.o -lmate-panel-applet-4 
> -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject 
> -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lmate-desktop-2 
> -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject 
> -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 
> -lstartup-notification-1 -lcpufreq -ldbus-glib-1 -ldbus-1 -lgobject-2.0 
> -lglib-2.0 
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIE -pie -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -o mate-cpufreq-applet cpufreq-applet.o 
> cpufreq-utils.o cpufreq-prefs.o cpufreq-selector.o cpufreq-popup.o 
> cpufreq-monitor.o cpufreq-monitor-factory.o cpufreq-monitor-procfs.o 
> cpufreq-monitor-sysfs.o cpufreq-monitor-libcpufreq.o 
> cpufreq-monitor-cpuinfo.o  -lmate-panel-applet-4 -lmate-desktop-2 -lgtk-3 
> -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo 
> -lgdk_pixbuf-2.0 -lgio-2.0 -lstartup-notification-1 -lcpufreq -ldbus-glib-1 
> -ldbus-1 -lgobject-2.0 -lglib-2.0
> cpufreq-monitor-libcpufreq.o: In function `cpufreq_monitor_libcpufreq_run':
> ./cpufreq/src/cpufreq-monitor-libcpufreq.c:118: undefined reference to 
> `cpupower_is_cpu_online'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/mate-applets_1.14.1-1_unstable.log

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

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

Bug#837006: gnome-python-desktop: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Lucas Nussbaum]

Source: gnome-python-desktop
Version: 2.32.0+dfsg-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "debian/build"
> CDBS WARNING:DEB_DH_BUILDDEB_ARGS is deprecated since 0.4.85
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> dh_autoreconf 
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> configure.ac:66: installing './compile'
> configure.ac:41: installing './missing'
> braseroburn/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> braseroburn/Makefile.am: installing './depcomp'
> braseromedia/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> evince/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' 
> (or '*_CPPFLAGS')
> evolution/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gnomeapplet/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gnomedesktop/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gnomekeyring/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gnomeprint/Makefile.am:2: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gtksourceview/Makefile.am:3: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gtop/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or 
> '*_CPPFLAGS')
> mediaprofiles/Makefile.am:3: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> metacity/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' 
> (or '*_CPPFLAGS')
> nautilusburn/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> rsvg/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or 
> '*_CPPFLAGS')
> tests/Makefile.am:3: warning: shell echo $$PYTHONPATH: non-POSIX variable name
> tests/Makefile.am:3: (probably a GNU make extension)
> wnck/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or 
> '*_CPPFLAGS')
> touch debian/stamp-autotools-files
> /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
> resolved from binary package "stamp-autotools".  Stop.
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> 
> Build finished at 2016-09-06T22:49:54Z

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gnome-python-desktop_2.32.0+dfsg-3_unstable.log

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

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

Bug#837010: gnustep-base: FTBFS: Tests failures

[Lucas Nussbaum]

Source: gnustep-base
Version: 1.24.9-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> 
> Testing NSXMLParser.m...
> Running base/headers/NSXMLParser.m...
> Passed test: NSXMLParser.m:9 ... include of Foundation/NSXMLParser.h works
> Completed file:  NSXMLParser.m
> 
> Testing NSZone.m...
> Running base/headers/NSZone.m...
> Passed test: NSZone.m:9 ... include of Foundation/NSZone.h works
> Completed file:  NSZone.m
> 
> Testing Unicode.m...
> Running base/headers/Unicode.m...
> Passed test: Unicode.m:9 ... include of GNUstepBase/Unicode.h works
> Completed file:  Unicode.m
> debian/rules:166: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gnustep-base_1.24.9-3_unstable.log

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

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

Bug#837007: xfce4-radio-plugin: FTBFS: videodev2.h:2105:20: error: field 'timestamp' has incomplete type

[Lucas Nussbaum]

Source: xfce4-radio-plugin
Version: 0.5.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -pthread 
> -I/usr/include/xfce4/libxfce4panel-1.0 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/freetype2 -I/usr/include/xfce4 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/xfce4 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/freetype2 -I/usr/include/xfce4 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -std=c99 -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o xfce4_radio_plugin-v4l2.o `test -f 'v4l2.c' || 
> echo './'`v4l2.c
> In file included from v4l2.c:25:0:
> /usr/include/linux/videodev2.h:2105:20: error: field 'timestamp' has 
> incomplete type
>   struct timespec   timestamp;
> ^
> Makefile:501: recipe for target 'xfce4_radio_plugin-v4l2.o' failed
> make[3]: *** [xfce4_radio_plugin-v4l2.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/xfce4-radio-plugin_0.5.1-3_unstable.log

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

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

Bug#837025: pyasn1: FTBFS: debian/rules:16: *** target file 'debian/python-module-stampdir/pypy-pyasn1' has both : and :: entries. Stop.

[Lucas Nussbaum]

Source: pyasn1
Version: 0.1.9-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> py3versions: no X-Python3-Version in control file, using supported versions
> debian/rules:16: *** target file 'debian/python-module-stampdir/pypy-pyasn1' 
> has both : and :: entries.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> 
> Build finished at 2016-09-06T23:08:12Z

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/pyasn1_0.1.9-1_unstable.log

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

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

Bug#837028: gauche-gtk: FTBFS: pango-font.c:249:44: error: 'desc' undeclared (first use in this function)

[Lucas Nussbaum]

Source: gauche-gtk
Version: 0.6~pre1+git20121223-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -g -O2 
> -fdebug-prefix-map=/<>/gauche-gtk-0.6~pre1+git20121223=. 
> -fstack-protector-strong -Wformat -Werror=format-security -I. `gauche-config 
> -I` `gauche-config --so-cflags` `pkg-config --cflags gtk+-2.0` -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o pango-font.o pango-font.c
> pango-font.c: In function 'pango_font_pango_font_description_to_string':
> pango-font.c:249:44: error: 'desc' undeclared (first use in this function)
>  char *s = pango_font_description_to_string(desc);
> ^~~~
> pango-font.c:249:44: note: each undeclared identifier is reported only once 
> for each function it appears in
> pango-font.c: In function 'pango_font_pango_font_description_to_filename':
> pango-font.c:267:46: error: 'desc' undeclared (first use in this function)
>  char *s = pango_font_description_to_filename(desc);
>   ^~~~
> : recipe for target 'pango-font.o' failed
> make[2]: *** [pango-font.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gauche-gtk_0.6~pre1+git20121223-1_unstable.log

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

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

Processed: affects 832077

[Debian Bug Tracking System]

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

> affects 832077 vim-gtk3
Bug #832077 [libgtk-3-0] Gtk-WARNING **: EmacsFixed 0x95c12e8 is drawn without 
a current allocation. This should not happen.
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
Added indication that 832077 affects vim-gtk3
Added indication that 836426 affects vim-gtk3
> thanks
Stopping processing here.

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

Bug#837027: csh: FTBFS: proc.c:84:16: error: storage size of 'w' isn't known

[Lucas Nussbaum]

Source: csh
Version: 20110502-2.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
> -DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c proc.c
> proc.c: In function 'pchild':
> proc.c:84:16: error: storage size of 'w' isn't known
>  union wait w;
> ^
> *** Error code 1
> 
> Stop.
> bmake[2]: stopped in /<>
> dh_auto_build: bmake returned exit code 1
> debian/rules:10: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/csh_20110502-2.1_unstable.log

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

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

Processed: Re: Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Debian Bug Tracking System]

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

> severity 834744 serious
Bug #834744 [src:xmlgraphics-commons] xmlgraphics-commons: FTBFS (missing 
build-depends on gnupg)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#835489: Fails to start

[Dmitry Eremin-Solenikov]

Package: pyqso
Followup-For: Bug #835489

Please consider the attached patch that fixed all the issues of PyQSO vs
Python3. I have uploaded the corresponding package to
mentors.debian.net (https://mentors.debian.net/package/pyqso). Thanks in 
advance.

-- 
With best wishes
Dmitry

-- 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.21.5-3
ii  libjs-jquery 1.12.4-1
ii  libjs-underscore 1.8.3~dfsg-1
ii  python-libhamlib23.0.1-1
ii  python3-gi-cairo 3.20.1-1
ii  python3-matplotlib   1.5.2~rc2-1
ii  python3-mpltoolkits.basemap  1.0.7+dfsg-4
ii  python3-numpy1:1.11.1~rc1-1
pn  python3:any  

pyqso recommends no packages.

pyqso suggests no packages.

-- no debconf information
diff -Napur pyqso-0.3-old/debian/changelog pyqso-0.3/debian/changelog
--- pyqso-0.3-old/debian/changelog	2016-07-08 04:55:53.0 +0300
+++ pyqso-0.3/debian/changelog	2016-09-08 01:01:19.026455214 +0300
@@ -1,3 +1,14 @@
+pyqso (0.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild with Python3 (Closes: #835489).
+  * Change packages in dependencies to rerefence Python3 packages.
+  * Move python(3)-libhamlib2 to Recomends, as the Python3 version of package
+is not yet available in Debian.
+  * Bump standards version to 3.9.8 (No changes needed).
+
+ -- Dmitry Eremin-Solenikov   Thu, 08 Sep 2016 01:00:46 +0300
+
 pyqso (0.3-1) unstable; urgency=medium
 
   * Imported Upstream version 0.3.
diff -Napur pyqso-0.3-old/debian/control pyqso-0.3/debian/control
--- pyqso-0.3-old/debian/control	2016-07-08 04:51:02.0 +0300
+++ pyqso-0.3/debian/control	2016-09-08 01:01:46.095566806 +0300
@@ -5,10 +5,10 @@ Section: hamradio
 Priority: optional
 Build-Depends: debhelper (>= 9),
dh-python,
-   python-all,
+   python3-all,
python-setuptools,
python-sphinx
-Standards-Version: 3.9.6
+Standards-Version: 3.9.8
 Vcs-Browser: http://anonscm.debian.org/cgit/pkg-hamradio/pyqso.git
 Vcs-Git: http://anonscm.debian.org/git/pkg-hamradio/pyqso.git
 Homepage: http://christianjacobs.uk/pyqso
@@ -16,15 +16,15 @@ Homepage: http://christianjacobs.uk/pyqs
 Package: pyqso
 Architecture: all
 Depends: ${misc:Depends},
- ${python:Depends},
- python-libhamlib2,
+ ${python3:Depends},
  gir1.2-gtk-3.0,
- python-gi-cairo,
- python-mpltoolkits.basemap,
- python-numpy,
- python-matplotlib,
+ python3-gi-cairo,
+ python3-mpltoolkits.basemap,
+ python3-numpy,
+ python3-matplotlib,
  libjs-jquery,
  libjs-underscore
+Recommends: python3-libhamlib2,
 Description: logging tool for amateur radio operators
  PyQSO is a logging tool for amateur radio operators. It provides a simple
  graphical interface through which users can manage information about the
diff -Napur pyqso-0.3-old/debian/rules pyqso-0.3/debian/rules
--- pyqso-0.3-old/debian/rules	2016-07-08 04:51:02.0 +0300
+++ pyqso-0.3/debian/rules	2016-09-08 00:38:38.589181137 +0300
@@ -2,7 +2,7 @@
 export PYBUILD_NAME=pyqso
 
 %:
-	dh $@ --with python2 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_auto_build:
 	PYTHONPATH=. http_proxy='localhost' sphinx-build -N -bhtml docs/source/ build/html  # HTML generator

Bug#837026: tcsh: FTBFS: sh.proc.c:155:16: error: storage size of 'w' isn't known

[Lucas Nussbaum]

Source: tcsh
Version: 6.18.01-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -I. -I. 
> -D_PATH_TCSHELL='"/usr/bin/tcsh"'  -Wdate-time -D_FORTIFY_SOURCE=2  sh.proc.c
> In file included from /usr/include/signal.h:28:0,
>  from sh.h:39,
>  from sh.proc.c:33:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> sh.proc.c: In function 'pchild':
> sh.proc.c:155:16: error: storage size of 'w' isn't known
>  union wait w;
> ^
> Makefile:465: recipe for target 'sh.proc.o' failed
> make[2]: *** [sh.proc.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/tcsh_6.18.01-5_unstable.log

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

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

Bug#837018: gupnp-igd: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Lucas Nussbaum]

Source: gupnp-igd
Version: 0.2.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
> enable.
> test -x debian/rules
> mkdir -p "debian/build"
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
> --copyright --deb-fmt --ignore 
> '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> /bin/sh: 1: /usr/bin/licensecheck: not found
> 0 combinations of copyright and licensing found.
> diff: debian/copyright_hints: No such file or directory
> No new copyright notices found - assuming no news is good news...
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> dh_autoreconf 
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> configure.ac:8: installing './compile'
> configure.ac:3: installing './missing'
> libgupnp-igd/Makefile.am: installing './depcomp'
> touch debian/stamp-autotools-files
> /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
> resolved from binary package "stamp-autotools".  Stop.
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> 
> Build finished at 2016-09-06T22:51:00Z

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gupnp-igd_0.2.4-1_unstable.log

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

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

Bug#837023: gridengine: FTBFS: ../sh.proc.c:153:16: error: storage size of ‘w’ isn’t known

[Lucas Nussbaum]

Source: gridengine
Version: 8.1.9+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> cc -c -O2 -Wstrict-prototypes -DLINUX -DLINUXAMD64 -DLINUXAMD64 -D_GNU_SOURCE 
> -DGETHOSTBYNAME_R6 -DGETHOSTBYADDR_R8 -DTARGET_64BIT -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/gridengine-8.1.9+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -DSGE_PQS_API 
> -DSPOOLING_dynamic -DSECURE -DHAVE_HWLOC=1 -DCOMPILE_DC 
> -D__SGE_COMPILE_WITH_GETTEXT__ -D__SGE_NO_USERMAPPING__ -U_GNU_SOURCE 
> -Wno-error -DPROG_NAME='"qtcsh"' -DLINUXAMD64 -I. -I.. 
> -D_PATH_TCSHELL='"/usr/local/bin/tcsh"'  -Wdate-time -D_FORTIFY_SOURCE=2  
> -I../../../libs/gdi -I../../../libs/gdi ../sh.proc.c
> In file included from /usr/include/signal.h:28:0,
>  from ../sh.h:39,
>  from ../sh.proc.c:33:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> ../sh.proc.c: In function ‘pchild’:
> ../sh.proc.c:153:16: error: storage size of ‘w’ isn’t known
>  union wait w;
> ^
> Makefile:381: recipe for target 'sh.proc.o' failed
> make[2]: *** [sh.proc.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gridengine_8.1.9+dfsg-1_unstable.log

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

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

Bug#837021: openjfx: FTBFS: PosixPlatform.cpp:235:10: error: 'wait' was not declared in this scope

[Lucas Nussbaum]

Source: openjfx
Version: 8u102-b14-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -Xlinker -s -static-libstdc++ -Wl,-O1 -shared -o libDumpRenderTreeJava.so 
> Release/obj/GCController.o Release/obj/TestRunner.o Release/obj/WorkQueue.o 
> Release/obj/DumpRenderTree.o Release/obj/GCControllerJava.o 
> Release/obj/JavaEnv.o Release/obj/TestRunnerJava.o 
> Release/obj/WorkQueueItemJava.o Release/obj/EventSender.o  
> -L../../Release/lib -lpthread -ljfxwebkit  
> mv -f libDumpRenderTreeJava.so ../../Release/lib/ 
> make[3]: Leaving directory 
> '/<>/modules/web/build/linux/Tools/DumpRenderTree'
> make[2]: Leaving directory '/<>/modules/web/build/linux/Release'
> 
> 
>  WebKit is now built (1h:03m:38s). 
>  To run FXLauncher with this newly-built code, use the
>  "Tools/Scripts/run-launcher" script.
> 
> :web:compileNativeLinux (Thread[main,5,main]) completed. Took 1 hrs 3 mins 
> 38.269 secs.
> :web:compileGeneratedLinux (Thread[main,5,main]) started.
> :web:compileGeneratedLinux
> Executing task ':web:compileGeneratedLinux' (up-to-date check took 0.075 
> secs) due to:
>   No history is available.
> All input files are considered out-of-date for incremental task 
> ':web:compileGeneratedLinux'.
> Compiling with Java command line compiler 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac'.
> Starting process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''. 
> Working directory: /<>/modules/web Command: 
> /usr/lib/jvm/java-8-openjdk-amd64/bin/javac 
> @/<>/modules/web/build/tmp/compileGeneratedLinux/java-compiler-args.txt
> Successfully started process 'command 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> :web:compileGeneratedLinux (Thread[main,5,main]) completed. Took 3.056 secs.
> :web:compileGenerated (Thread[main,5,main]) started.
> :web:compileGenerated
> Skipping task ':web:compileGenerated' as it has no actions.
> :web:compileGenerated (Thread[main,5,main]) completed. Took 0.0 secs.
> :web:drtJar (Thread[main,5,main]) started.
> :web:drtJar
> Executing task ':web:drtJar' (up-to-date check took 0.007 secs) due to:
>   No history is available.
> :web:drtJar (Thread[main,5,main]) completed. Took 0.028 secs.
> :web:jar (Thread[main,5,main]) started.
> :web:jar
> Executing task ':web:jar' (up-to-date check took 0.02 secs) due to:
>   No history is available.
> :web:jar (Thread[main,5,main]) completed. Took 0.166 secs.
> :builders:compileJava (Thread[main,5,main]) started.
> :builders:compileJava
> Executing task ':builders:compileJava' (up-to-date check took 0.046 secs) due 
> to:
>   No history is available.
> All input files are considered out-of-date for incremental task 
> ':builders:compileJava'.
> Compiling with Java command line compiler 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac'.
> Starting process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''. 
> Working directory: /<>/modules/builders Command: 
> /usr/lib/jvm/java-8-openjdk-amd64/bin/javac 
> @/<>/modules/builders/build/tmp/compileJava/java-compiler-args.txt
> Successfully started process 'command 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''
> Note: 
> /<>/modules/builders/src/main/java/javafx/scene/web/WebViewBuilder.java
>  uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> :builders:compileJava (Thread[main,5,main]) completed. Took 3.794 secs.
> :builders:processResources (Thread[main,5,main]) started.
> :builders:processResources
> file or directory '/<>/modules/builders/src/main/resources', not 
> found
> Skipping task ':builders:processResources' as it has no source files.
> :builders:processResources UP-TO-DATE
> :builders:processResources (Thread[main,5,main]) completed. Took 0.001 secs.
> :builders:classes (Thread[main,5,main]) started.
> :builders:classes
> Skipping task ':builders:classes' as it has no actions.
> :builders:classes (Thread[main,5,main]) completed. Took 0.0 secs.
> :builders:jar (Thread[main,5,main]) started.
> :builders:jar
> Executing task ':builders:jar' (up-to-date check took 0.003 secs) due to:
>   No history is available.
> :builders:jar (Thread[main,5,main]) completed. Took 0.053 secs.
> :builders:assemble (Thread[main,5,main]) started.
> :builders:assemble
> Skipping task ':builders:assemble' as it has no actions.
> :builders:assemble (Thread[main,5,main]) completed. Took 0.0 secs.
> :controls:assemble (Thread[main,5,main]) started.
> :controls:assemble
> Skipping task 

Bug#837016: singular: FTBFS: aminclude.am:35: error: DX_COND_doc does not appear in AM_CONDITIONAL

[Lucas Nussbaum]

Source: singular
Version: 4.0.3-p1+ds-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with autoreconf --parallel
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '../build-aux'.
> libtoolize: copying file '../build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, '../m4'.
> libtoolize: copying file '../m4/libtool.m4'
> libtoolize: copying file '../m4/ltoptions.m4'
> libtoolize: copying file '../m4/ltsugar.m4'
> libtoolize: copying file '../m4/ltversion.m4'
> libtoolize: copying file '../m4/lt~obsolete.m4'
> configure.ac:11: installing '../build-aux/ar-lib'
> configure.ac:11: installing '../build-aux/compile'
> configure.ac:41: installing '../build-aux/config.guess'
> configure.ac:41: installing '../build-aux/config.sub'
> configure.ac:9: installing '../build-aux/install-sh'
> configure.ac:9: installing '../build-aux/missing'
> Makefile.am: installing '../build-aux/depcomp'
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '../build-aux'.
> libtoolize: copying file '../build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, '../m4'.
> libtoolize: copying file '../m4/libtool.m4'
> libtoolize: copying file '../m4/ltoptions.m4'
> libtoolize: copying file '../m4/ltsugar.m4'
> libtoolize: copying file '../m4/ltversion.m4'
> libtoolize: copying file '../m4/lt~obsolete.m4'
> configure.ac:15: installing '../build-aux/compile'
> configure.ac:21: installing '../build-aux/missing'
> Makefile.am:93: warning: EXTRA_DIST multiply defined in condition TRUE ...
> Makefile.am:28: ... 'EXTRA_DIST' previously defined here
> Makefile.am: installing '../build-aux/depcomp'
> parallel-tests: installing '../build-aux/test-driver'
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '../build-aux'.
> libtoolize: copying file '../build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, '../m4'.
> libtoolize: copying file '../m4/libtool.m4'
> libtoolize: copying file '../m4/ltoptions.m4'
> libtoolize: copying file '../m4/ltsugar.m4'
> libtoolize: copying file '../m4/ltversion.m4'
> libtoolize: copying file '../m4/lt~obsolete.m4'
> configure.ac:23: installing '../build-aux/compile'
> configure.ac:21: installing '../build-aux/missing'
> aminclude.am:35: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:41: error: DX_COND_html does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:51: error: DX_COND_chm does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:55: error: DX_COND_chi does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:67: error: DX_COND_man does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:77: error: DX_COND_rtf does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:87: error: DX_COND_xml does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:97: error: DX_COND_ps does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:126: error: DX_COND_pdf does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:155: error: DX_COND_latex does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> Makefile.am: installing '../build-aux/depcomp'
> configure.ac: installing '../build-aux/ylwrap'
> autoreconf: automake failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> debian/rules:14: recipe for target 'build' failed
> make: *** [build] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/singular_4.0.3-p1+ds-3_unstable.log

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

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

Bug#837015: linux-tools: FTBFS: util/event.c:448:2: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations]

[Lucas Nussbaum]

Source: linux-tools
Version: 4.4.6-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>   gcc 
> -Wp,-MD,/<>/debian/build/tools/perf/out/util/.event.o.d,-MT,/<>/debian/build/tools/perf/out/util/event.o
>  -g -O2 -fdebug-prefix-map=/<>/debian/build/tools/perf=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/<>/tools/perf 
> -I/<>/debian/build/tools/perf -isystem 
> /<>/debian/build/include -Wno-error -DHAVE_ARCH_X86_64_SUPPORT 
> -DHAVE_PERF_REGS_SUPPORT -DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -Werror -O6 
> -fno-omit-frame-pointer -ggdb3 -funwind-tables -Wall -Wextra -std=gnu99 
> -fstack-protector-all -D_FORTIFY_SOURCE=2 
> -I/<>/tools/perf/util/include 
> -I/<>/tools/perf/arch/x86/include 
> -I/<>/tools/include/ -I/<>/arch/x86/include/uapi 
> -I/<>/arch/x86/include -I/<>/include/uapi 
> -I/<>/include 
> -I/<>/debian/build/tools/perf/out//util 
> -I/<>/debian/build/tools/perf/out/ 
> -I/<>/tools/perf/util -I/<>/tools/perf 
> -I/<>/tools/lib/ -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_GNU_SOURCE -DHAVE_SYNC_COMPARE_AND_SWAP_SUPPORT 
> -DHAVE_PTHREAD_ATTR_SETAFFINITY_NP -DHAVE_LIBELF_SUPPORT 
> -DHAVE_LIBELF_MMAP_SUPPORT -DHAVE_ELF_GETPHDRNUM_SUPPORT -DHAVE_DWARF_SUPPORT 
>  -DHAVE_LIBBPF_SUPPORT -DHAVE_DWARF_UNWIND_SUPPORT -DNO_LIBUNWIND_DEBUG_FRAME 
> -DHAVE_LIBUNWIND_SUPPORT  -DHAVE_LIBAUDIT_SUPPORT -I/usr/include/slang 
> -DHAVE_SLANG_SUPPORT -DHAVE_TIMERFD_SUPPORT -DHAVE_CPLUS_DEMANGLE_SUPPORT 
> -DHAVE_ZLIB_SUPPORT -DHAVE_BACKTRACE_SUPPORT -DHAVE_LIBNUMA_SUPPORT 
> -DHAVE_KVM_STAT_SUPPORT -DHAVE_PERF_READ_VDSO32 -DHAVE_PERF_READ_VDSOX32 
> -DHAVE_AUXTRACE_SUPPORT -I/<>/debian/build/tools/perf/out/ 
> -D"BUILD_STR(s)=#s"   -c -o 
> /<>/debian/build/tools/perf/out/util/event.o util/event.c
> util/event.c: In function '__event__synthesize_thread':
> util/event.c:448:2: error: 'readdir_r' is deprecated 
> [-Werror=deprecated-declarations]
>   while (!readdir_r(tasks, , ) && next) {
>   ^
> In file included from /usr/include/features.h:364:0,
>  from /usr/include/stdint.h:25,
>  from /usr/lib/gcc/x86_64-linux-gnu/6/include/stdint.h:9,
>  from /<>/tools/include/linux/types.h:6,
>  from util/event.c:1:
> /usr/include/dirent.h:189:12: note: declared here
>  extern int __REDIRECT (readdir_r,
> ^
> util/event.c: In function 'perf_event__synthesize_threads':
> util/event.c:586:2: error: 'readdir_r' is deprecated 
> [-Werror=deprecated-declarations]
>   while (!readdir_r(proc, , ) && next) {
>   ^
> In file included from /usr/include/features.h:364:0,
>  from /usr/include/stdint.h:25,
>  from /usr/lib/gcc/x86_64-linux-gnu/6/include/stdint.h:9,
>  from /<>/tools/include/linux/types.h:6,
>  from util/event.c:1:
> /usr/include/dirent.h:189:12: note: declared here
>  extern int __REDIRECT (readdir_r,
> ^
> cc1: all warnings being treated as errors
> mv: cannot stat 
> '/<>/debian/build/tools/perf/out/util/.event.o.tmp': No such 
> file or directory
> /<>/tools/build/Makefile.build:77: recipe for target 
> '/<>/debian/build/tools/perf/out/util/event.o' failed
> make[8]: *** [/<>/debian/build/tools/perf/out/util/event.o] 
> Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/linux-tools_4.4.6-1_unstable.log

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

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

Bug#837024: gamin: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Lucas Nussbaum]

Source: gamin
Version: 0.1.10-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
> enable.
> test -x debian/rules
> mkdir -p "debian/build"
> CDBS WARNING:DEB_DH_BUILDDEB_ARGS is deprecated since 0.4.85
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
> --copyright --deb-fmt --ignore 
> '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> /bin/sh: 1: /usr/bin/licensecheck: not found
> 0 combinations of copyright and licensing found.
> diff: debian/copyright_hints: No such file or directory
> No new copyright notices found - assuming no news is good news...
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> dh_autoreconf 
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> automake: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:28: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms 
> are deprecated.  For more info, see:
> configure.in:28: 
> http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
> configure.in:30: installing './compile'
> configure.in:28: installing './missing'
> automake: warning: autoconf input should be named 

Bug#837022: wagon2: FTBFS: dh_auto_test failed

[Lucas Nussbaum]

Source: wagon2
Version: 2.10-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p /<>/wagon-providers/wagon-scm/target/test-classes/
> svnadmin create 
> /<>/wagon-providers/wagon-scm/target/test-classes/test-repo-svn
> dh_auto_build
>   /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 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> 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...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-provider-api:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-file:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-ftp:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http:jar:2.10
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-surefire-plugin @ line 143, column 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 143, column 
> 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http-shared:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http-lightweight:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 59, column 
> 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-providers:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-provider-test:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-tck-http:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-tcks:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> 

Bug#837019: zvbi: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: zvbi
Version: 0.2.35-11
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/test'
> PASS: ctest
> PASS: cpptest
> PASS: ctest-c89
> PASS: ctest-gnu89
> PASS: ctest-c94
> PASS: ctest-c99
> PASS: ctest-gnu99
> PASS: cpptest-cxx98
> PASS: cpptest-gnuxx98
> PASS: exoptest
> PASS: test-dvb_demux
> PASS: test-dvb_mux
> PASS: test-hamm
> PASS: test-packet-830
> ../test-driver: line 107: 20549 Aborted "$@" > $log_file 2>&1
> FAIL: test-pdc
> PASS: test-raw_decoder
> PASS: test-unicode
> PASS: test-vps
> ==
>zvbi 0.2.35: test/test-suite.log
> ==
> 
> # TOTAL: 18
> # PASS:  17
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test-pdc
> ==
> 
> test-pdc: test-pdc.cc:1078: void test_pil_to_time(): Assertion `ztime 
> ("20010215T19") == vbi_pil_to_time (VBI_PIL (2, 15, 20, 0), t1, 
> "Europe/Paris")' failed.
> FAIL test-pdc (exit status: 134)
> 
> 
> Testsuite summary for zvbi 0.2.35
> 
> # TOTAL: 18
> # PASS:  17
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See test/test-suite.log
> 
> Makefile:1466: recipe for target 'test-suite.log' failed
> make[4]: *** [test-suite.log] Error 1
> make[4]: Leaving directory '/<>/test'
> Makefile:1572: recipe for target 'check-TESTS' failed
> make[3]: *** [check-TESTS] Error 2
> make[3]: Leaving directory '/<>/test'
> Makefile:1764: recipe for target 'check-am' failed
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory '/<>/test'
> Makefile:510: recipe for target 'check-recursive' failed
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/zvbi_0.2.35-11_unstable.log

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

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

Bug#837009: cheetah: FTBFS: debian/rules:20: *** no python implementation resolved from flavor "python$buildver". Stop.

[Lucas Nussbaum]

Source: cheetah
Version: 2.4.4-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs -A 
> mkdir -p "."
> mkdir -p debian/python-module-stampdir
> set -e; cd . && python2 setup.py build 
> --build-base="/<>/./build";
> running build
> running build_py
> running build_ext
> running build_scripts
> touch debian/python-module-stampdir/python-cheetah
> Adding cdbs dependencies to debian/python-cheetah.substvars
> dh_installdirs -ppython-cheetah \
>   
> set -e; cd . && python2 setup.py install 
> --root="/<>/debian/python-cheetah/" --install-layout=deb 
> --no-compile -O0 --single-version-externally-managed;
> running install
> running build
> running build_py
> running build_ext
> running build_scripts
> running install_lib
> creating /<>/debian/python-cheetah/usr
> creating /<>/debian/python-cheetah/usr/lib
> creating /<>/debian/python-cheetah/usr/lib/python2.7
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/SiteHierarchy.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/RecursiveNull.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/CGITemplate.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/__init__.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/MondoReport.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Template.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ImportManager.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/FileUtils.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/SettingsManager.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/DummyTransaction.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ImportHooks.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/DirectiveAnalyzer.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/SourceReader.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/Version.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/NameMapper.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/Parser.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/CacheStore.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ErrorCatchers.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/WebInputMixin.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/Indenter.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/Misc.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/statprof.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/__init__.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/htmlEncode.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/htmlDecode.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> 

Bug#837020: liblightify: FTBFS: doxygen-include.am:47: error: DX_COND_doc does not appear in AM_CONDITIONAL

[Lucas Nussbaum]

Source: liblightify
Version: 0~git20160607-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build  --with autoreconf
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
> aclocal: warning: couldn't open directory 'm4': No such file or directory
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
> libtoolize: copying file 'build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> configure.ac:24: installing 'build-aux/compile'
> configure.ac:86: installing 'build-aux/config.guess'
> configure.ac:86: installing 'build-aux/config.sub'
> configure.ac:11: installing 'build-aux/install-sh'
> configure.ac:11: installing 'build-aux/missing'
> configure.ac:9: installing 'build-aux/tap-driver.sh'
> doxygen-include.am:47: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:53: error: DX_COND_html does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:63: error: DX_COND_chm does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:67: error: DX_COND_chi does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:79: error: DX_COND_man does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:89: error: DX_COND_rtf does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:99: error: DX_COND_xml does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:109: error: DX_COND_ps does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:138: error: DX_COND_pdf does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:167: error: DX_COND_latex does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> Makefile.am:4: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am:18: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am: installing 'build-aux/depcomp'
> parallel-tests: installing 'build-aux/test-driver'
> autoreconf: automake failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> debian/rules:4: recipe for target 'build' failed
> make: *** [build] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/liblightify_0~git20160607-1_unstable.log

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

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

Bug#837017: libvisio: FTBFS: Tests failures

[Lucas Nussbaum]

Source: libvisio
Version: 0.1.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[6]: *** [test-suite.log] Error 1
> make[6]: Leaving directory '/<>/src/test'
> Makefile:892: recipe for target 'check-TESTS' failed
> make[5]: *** [check-TESTS] Error 2
> make[5]: Leaving directory '/<>/src/test'
> Makefile:965: recipe for target 'check-am' failed
> make[4]: *** [check-am] Error 2
> make[4]: Leaving directory '/<>/src/test'
> Makefile:394: recipe for target 'check-recursive' failed
> make[3]: *** [check-recursive] Error 1
> make[3]: Leaving directory '/<>/src'
> Makefile:501: recipe for target 'check-recursive' failed
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory '/<>'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> debian/rules:14: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/libvisio_0.1.5-1_unstable.log

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

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

Bug#837011: ltrace: FTBFS: proc.c:245:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations]

[Lucas Nussbaum]

Source: ltrace
Version: 0.7.3-5.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../..  -I../../sysdeps/linux-gnu/x86  -I../../sysdeps/linux-gnu   
> -I../../sysdeps -I../..  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wsign-compare -Wfloat-equal -Wformat-security -Werror -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o proc.lo proc.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. 
> -I../../sysdeps/linux-gnu/x86 -I../../sysdeps/linux-gnu -I../../sysdeps 
> -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -Wfloat-equal 
> -Wformat-security -Werror -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c proc.c  -fPIC 
> -DPIC -o .libs/proc.o
> proc.c: In function 'process_tasks':
> proc.c:245:3: error: 'readdir_r' is deprecated 
> [-Werror=deprecated-declarations]
>if (readdir_r(d, , ) != 0) {
>^~
> In file included from proc.c:31:0:
> /usr/include/dirent.h:183:12: note: declared here
>  extern int readdir_r (DIR *__restrict __dirp,
> ^
> cc1: all warnings being treated as errors
> Makefile:366: recipe for target 'proc.lo' failed
> make[5]: *** [proc.lo] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/ltrace_0.7.3-5.1_unstable.log

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

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

Bug#837013: notmuch: FTBFS: Tests failures

[Lucas Nussbaum]

Source: notmuch
Version: 0.22.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gpg: no valid OpenPGP data found.
> Added 2 new messages to the database.
>  missing prerequisites: database-v1.tar.xz - fetch with 'make 
> download-test-databases'
>  SKIP   all tests in T530-upgrade
>  BROKEN No ghosts should remain after deletion of second message
>   --- T590-thread-breakage.22.expected2016-09-06 22:45:08.15600 
> +
>   +++ T590-thread-breakage.22.output  2016-09-06 22:45:08.15600 
> +
>   @@ -1 +1 @@
>   -0
>   +1
> 
> Notmuch test suite complete.
> 772/778 tests passed.
> 1 broken test failed as expected.
> 5 tests failed.
> test/Makefile.local:64: recipe for target 'test' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/notmuch_0.22.1-3_unstable.log

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

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

Bug#837012: tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'

[Lucas Nussbaum]

Source: tachyon
Version: 0.99~b6+dsx-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wno-unused-result 
> -I/usr/include/libdrm -I/usr/include/libdrm -g -O3 
> -fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
> -ffast-math -fomit-frame-pointer   -o tachyon-ogl tachyon_ogl-main.o 
> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o 
> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o 
> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o ../src/libtachyon.la -lm -lGL 
>  -lGL 
> libtool: link: gcc -Wno-unused-result -I/usr/include/libdrm 
> -I/usr/include/libdrm -g -O3 
> "-fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=." -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
> -ffast-math -fomit-frame-pointer -o .libs/tachyon-ogl tachyon_ogl-main.o 
> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o 
> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o 
> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o  ../src/.libs/libtachyon.so 
> -lm -lGL
> /usr/bin/ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'
> //usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO missing 
> from command line
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/tachyon_0.99~b6+dsx-5_unstable.log

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

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

Bug#837014: mono: FTBFS: build/profiles/basic.make:93: recipe for target 'build/deps/basic-profile-check.exe' failed

[Lucas Nussbaum]

Source: mono
Version: 4.2.1.102+dfsg2-8
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/mono-4.2.1.102+dfsg2/runtime'
> d=`cd ../support && pwd`; \
> sed 
> 's,target="/usr/lib/libMonoPosixHelper.so",target="'$d'/libMonoPosixHelper.la",'
>  ../data/config > etc/mono/configt
> if test -z ""; then :; else \
>   sed 's,target="libgdiplus.so",target="",' etc/mono/configt > 
> etc/mono/configtt; \
>   mv -f etc/mono/configtt etc/mono/configt; fi
> mv -f etc/mono/configt etc/mono/config
> /bin/bash ../mkinstalldirs _tmpinst/bin
> mkdir -p -- _tmpinst/bin
> cp mono-wrapper _tmpinst/bin/mono
> echo '#! /bin/sh' > _tmpinst/bin/ilasm ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/ilasm/ilasm.exe"'" "$@"' >> 
> _tmpinst/bin/ilasm ; \
> chmod +x _tmpinst/bin/ilasm
> echo '#! /bin/sh' > _tmpinst/bin/mcs ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/build/mcs.exe"'" "$@"' 
> >> _tmpinst/bin/mcs ; \
> chmod +x _tmpinst/bin/mcs
> echo '#! /bin/sh' > _tmpinst/bin/dmcs ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/build/mcs.exe -sdk:4"'" 
> "$@"' >> _tmpinst/bin/dmcs ; \
> chmod +x _tmpinst/bin/dmcs
> echo '#! /bin/sh' > _tmpinst/bin/al2 ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/net_2_0/al.exe"'" "$@"' 
> >> _tmpinst/bin/al2 ; \
> chmod +x _tmpinst/bin/al2
> echo '#! /bin/sh' > _tmpinst/bin/al ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/net_4_5/al.exe"'" "$@"' 
> >> _tmpinst/bin/al ; \
> chmod +x _tmpinst/bin/al
> if test -w /<>/mono-4.2.1.102+dfsg2/mcs; then :; else chmod -R +w 
> /<>/mono-4.2.1.102+dfsg2/mcs; fi
> cd /<>/mono-4.2.1.102+dfsg2/mcs && /usr/bin/make 
> --no-print-directory -s NO_DIR_CHECK=1 PROFILES='binary_reference_assemblies 
> net_4_5 xbuild_12 xbuild_14' CC='gcc' all-profiles
> mkdir -p -- build/deps
> build/profiles/basic.make:93: recipe for target 
> 'build/deps/basic-profile-check.exe' failed
> make[7]: *** [build/deps/basic-profile-check.exe] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/mono_4.2.1.102+dfsg2-8_unstable.log

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

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

Bug#837017: libvisio: FTBFS: Tests failures

[Rene Engelhard]

tag 837017 + moreinfo
tag 837017 + unreproducible
thanks

Hi,

On Thu, Sep 08, 2016 at 12:16:24AM +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > make[6]: *** [test-suite.log] Error 1
> > make[6]: Leaving directory '/<>/src/test'
> > Makefile:892: recipe for target 'check-TESTS' failed
> > make[5]: *** [check-TESTS] Error 2
> > make[5]: Leaving directory '/<>/src/test'
> > Makefile:965: recipe for target 'check-am' failed
> > make[4]: *** [check-am] Error 2
> > make[4]: Leaving directory '/<>/src/test'
> > Makefile:394: recipe for target 'check-recursive' failed
> > make[3]: *** [check-recursive] Error 1
> > make[3]: Leaving directory '/<>/src'
> > Makefile:501: recipe for target 'check-recursive' failed
> > make[2]: *** [check-recursive] Error 1
> > make[2]: Leaving directory '/<>'
> > dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> > debian/rules:14: recipe for target 'override_dh_auto_test' failed

Nope.

> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2016/09/06/libvisio_0.1.5-1_unstable.log

404

And a apt-get -b source libvisio works fine here.

Regards,

Rene

Processed: Re: Bug#837017: libvisio: FTBFS: Tests failures

[Debian Bug Tracking System]

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

> tag 837017 + moreinfo
Bug #837017 [src:libvisio] libvisio: FTBFS: Tests failures
Added tag(s) moreinfo.
> tag 837017 + unreproducible
Bug #837017 [src:libvisio] libvisio: FTBFS: Tests failures
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#837000: kerberos-configs: FTBFS: Undefined subroutine ::read_config called at ./genblob line 9.

[Sam Hartman]

> "Lucas" == Lucas Nussbaum  writes:

Lucas> Hi,

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

Lucas> Relevant part (hopefully):
>> fakeroot debian/rules binary ./genblob >tmp & tmp config-blob
>> Undefined subroutine ::read_config called at ./genblob line
>> 9.  debian/rules:17: recipe for target 'config-blob' failed make:
>> *** [config-blob] Error 2

Lucas> The full build log is available from:
Lucas> 
http://people.debian.org/~lucas/logs/2016/09/06/kerberos-configs_2.3_unstable.log

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

Lucas> About the archive rebuild: The rebuild was done on EC2 VM
Lucas> instances from Amazon Web Services, using a clean, minimal
Lucas> and up-to-date chroot. Every failed build was retried once to
Lucas> eliminate random failures.

Looks like a . removed from cwd bug in perl.
Kerberos-configs is a bit over-due for some love anyway.
The fix is easy, but I'll go fold in a bunch of other bugs while I get
to it.


--Sam

Bug#817374: marked as done (bbmail: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 16:22:48 +
with message-id 
and subject line Bug#817374: fixed in bbmail 0.8.3-7
has caused the Debian Bug report #817374,
regarding bbmail: Removal of debhelper compat 4
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.)


-- 
817374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bbmail
Severity: important
Usertags: compat-4-removal

Hi,

The package bbmail uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: bbmail
Source-Version: 0.8.3-7

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

Debian distribution maintenance software
pp.
Kevin Coyner  (supplier of updated bbmail package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Sep 2016 10:42:21 -0400
Source: bbmail
Binary: bbmail
Architecture: source amd64
Version: 0.8.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Kevin Coyner 
Description:
 bbmail - Mail notifier for Blackbox/Fluxbox
Closes: 697539 697713 817374
Changes:
 bbmail (0.8.3-7) unstable; urgency=medium
 .
   * Orphaning this package.
   * debian/compat: Bumped to version 9. (Closes: Bug#817374)
   * debian/control:
 + Bumped debhelper to version 9.
 + Maintainer set to Debian QA Group .
 + Spelling correction to the word and. (Closes: Bug#697539)
 + Spelling correction - add the word is. (Closes: Bug#697713)
   * debian/changelog: Changed the word March to Mar.
Checksums-Sha1:
 37c1812506a5bc09a11cd0445850adde95689f71 1287 bbmail_0.8.3-7.dsc
 306150de4dd3590c3ad76012989dfd8911a44c23 27996 bbmail_0.8.3-7.diff.gz
 175ba7c394585f41dd2efe566e56a147613b58e6 54008 bbmail_0.8.3-7_amd64.deb
Checksums-Sha256:
 62b60bd79d4072fc81770f6fb9d4132ea9d826b0a0946fd9d37a22e03060c214 1287 
bbmail_0.8.3-7.dsc
 05636631b46a7e0c3a929f59ccefeffb89d375e30098d0cf6feebed948c1c808 27996 
bbmail_0.8.3-7.diff.gz
 e6cdc0939ad7b353cd8c98e377fe1810fca082448780f7d0a5e0ea9fa489dac9 54008 
bbmail_0.8.3-7_amd64.deb
Files:
 edd8af3303b778f4ff3349ea96c0a10c 1287 mail optional bbmail_0.8.3-7.dsc
 e5e6f721d0460a374d85de1d42629139 27996 mail optional bbmail_0.8.3-7.diff.gz
 de3b77008dbb103448404da482d55f9d 54008 mail optional bbmail_0.8.3-7_amd64.deb

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJX0CeVAAoJEOuzGmLIXY9xTlcH/jp6/jthMMXdf0xmE5296YuR
0MFIBSb6hZhjz6R+Nv+z/lC39MNTx+7xT4Llyg4ohb3jVhRjywjmhaWWTCNzYDE9
uU3Y8Ng6J4AJylK1TsnFBtXJC9KN8LJE2df8eeGYjwkwM/plELA1thYwOud+RhPh
ILvAqELP1sgJqwHGccaOb1JFafPzuJtJC3y/Ka5YQimAr4lcPWkBXOmmieLMLZM0
cwVwHQ039N9XZPsaalkyaP7Rdnyk37lW4Jp4CrDx1N6vjaHZ0y3TJOn0+x4sArTk
VoKGXm0eaHUWD+rX8gwSproi7eiYeOL7WbCJQQUBbvDXeSBIPCUeJVO/tq3OH4s=
=JXMZ
-END PGP SIGNATURE End Message ---

Processed: Caused by libgtk-3-0 3.21

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgtk-3-0 3.21.5-3
Bug #836426 [gnome-boxes] Graphics rendering (with QXL graphics) doesn't update
Bug reassigned from package 'gnome-boxes' to 'libgtk-3-0'.
No longer marked as found in versions gnome-boxes/3.20.2-2.
Ignoring request to alter fixed versions of bug #836426 to the same values 
previously set
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
Marked as found in versions gtk+3.0/3.21.5-3.
> affects -1 gnome-boxes
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
Added indication that 836426 affects gnome-boxes
> severity -1 serious
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
Severity set to 'serious' from 'important'
> forcemerge -1 832077
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
Marked as found in versions gtk+3.0/3.21.5-1.
Bug #832077 [libgtk-3-0] Gtk-WARNING **: EmacsFixed 0x95c12e8 is drawn without 
a current allocation. This should not happen.
Severity set to 'serious' from 'normal'
Added indication that 832077 affects gnome-boxes
Marked as found in versions gtk+3.0/3.21.5-3.
Merged 832077 836426
> affects 832077 emacs24
Bug #832077 [libgtk-3-0] Gtk-WARNING **: EmacsFixed 0x95c12e8 is drawn without 
a current allocation. This should not happen.
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
Added indication that 832077 affects emacs24
Added indication that 836426 affects emacs24

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

Bug#796298: marked as done (tcplay: FTBFS: CMake Error at CMakeLists.txt:30 (message): Could not find the devmapper library)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 16:35:43 +
with message-id 
and subject line Bug#796298: fixed in tcplay 1.1-3
has caused the Debian Bug report #796298,
regarding tcplay: FTBFS: CMake Error at CMakeLists.txt:30 (message): Could not 
find the devmapper library
to be marked as done.

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

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


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

Dear Maintainer,

tcplay fails to build from source on unstable/amd64:

  [..]

  -- Found PkgConfig: /usr/bin/pkg-config (found version "0.28") 
  -- checking for module 'devmapper'
  --   package 'devmapper' not found
  -- checking for module 'uuid'
  --   found uuid, version 2.26.0
  CMake Error at CMakeLists.txt:30 (message):
Could not find the devmapper library
  
  
  -- Configuring incomplete, errors occurred!
  See also
  
"/home/lamby/temp/cdt.20150821090745.LsaNbqC5Fn/tcplay-1.1/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr
  -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None returned exit code
  1
  debian/rules:39: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

>From a cursory glance, devmapper.pc specifies Requires.Private librt,
which doesn't have a  librt.pc (which is likely correct as it's meant to
be linked statically? I'll leave it to you).

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
 dpkg-buildpackage -rfakeroot -D -us -uc -b
dpkg-buildpackage: source package tcplay
dpkg-buildpackage: source version 1.1-2
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Laszlo Boszormenyi (GCS) 
 dpkg-source --before-build tcplay-1.1
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
   dh_clean
 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None
-- The C compiler identification is GNU 5.2.1
-- The CXX compiler identification is GNU 5.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.28") 
-- checking for module 'devmapper'
--   package 'devmapper' not found
-- checking for module 'uuid'
--   found uuid, version 2.26.0
CMake Error at CMakeLists.txt:30 (message):
  Could not find the devmapper library


-- Configuring incomplete, errors occurred!
See also 
"/home/lamby/temp/cdt.20150821090745.LsaNbqC5Fn/tcplay-1.1/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None returned exit code 1
debian/rules:39: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: tcplay
Source-Version: 1.1-3

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated tcplay 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: 

Bug#836889: marked as done (sugar: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 18:17:55 +0100
with message-id 
<1473268675.853995.718652833.7f39d...@webmail.messagingengine.com>
and subject line Re: [Pkg-sugar-devel] Bug#836889: sugar: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools". Stop.
has caused the Debian Bug report #836889,
regarding sugar: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python 
implementation resolved from binary package "stamp-autotools".  Stop.
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.)


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

Dear Maintainer,

sugar fails to build from source in unstable/amd64:

  [..]

  Setting up python-empy (3.3.2-1) ...
  Setting up libatk1.0-0:amd64 (2.21.90-2) ...
  Setting up x11proto-randr-dev (1.5.0-1) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Processing triggers for systemd (231-5) ...
  Setting up libpython2.7:amd64 (2.7.12-3) ...
  Setting up openssl (1.0.2h-1) ...
  Setting up libdconf1:amd64 (0.26.0-1) ...
  Setting up libfile-listing-perl (6.04-1) ...
  Setting up libexpat1-dev:amd64 (2.2.0-1) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up shared-mime-info (1.6-1) ...
  Setting up libxkbcommon0:amd64 (0.6.1-1) ...
  Setting up libhttp-message-perl (6.11-1) ...
  Setting up libpcrecpp0v5:amd64 (2:8.39-2) ...
  Setting up libpcre32-3:amd64 (2:8.39-2) ...
  Setting up libnet-http-perl (6.09-1) ...
  Setting up libpython2.7-dev:amd64 (2.7.12-3) ...
  Setting up icu-devtools (57.1-3) ...
  Setting up libdrm-radeon1:amd64 (2.4.70-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-2) ...
  Setting up libcolord2:amd64 (1.3.2-1) ...
  Setting up libthai-data (0.1.25-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.70-1) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up ca-certificates (20160104) ...
  Setting up hicolor-icon-theme (0.15-1) ...
  Setting up libglib2.0-bin (2.49.6-1) ...
  Setting up python2.7-dev (2.7.12-3) ...
  Setting up libgraphite2-dev (1.3.8-1) ...
  Setting up wayland-protocols (1.7-1) ...
  Setting up dh-buildinfo (0.11+nmu1) ...
  Setting up libwww-robotrules-perl (6.01-1) ...
  Setting up libwayland-cursor0:amd64 (1.11.0-2) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.10-1) ...
  Setting up liblzo2-2:amd64 (2.08-1.2) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libhttp-negotiate-perl (6.00-2) ...
  Setting up libepoxy-dev:amd64 (1.3.1-1) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libpython-dev:amd64 (2.7.11-2) ...
  Setting up gconf2-common (3.2.6-3) ...
  
  Creating config file /etc/gconf/2/path with new version
  Setting up libdbus-1-dev:amd64 (1.10.10-1) ...
  Setting up libpcre3-dev:amd64 (2:8.39-2) ...
  Setting up gir1.2-atk-1.0 (2.21.90-2) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up libxkbcommon-dev (0.6.1-1) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libdrm-amdgpu1:amd64 (2.4.70-1) ...
  Setting up libhttp-cookies-perl (6.01-1) ...
  Setting up libxshmfence-dev:amd64 (1.2-1) ...
  Setting up dconf-service (0.26.0-1) ...
  Setting up libdbus-glib-1-2:amd64 (0.106-1) ...
  Setting up python-dev (2.7.11-2) ...
  Setting up liblapack3 (3.6.1-2) ...
  update-alternatives: using /usr/lib/lapack/liblapack.so.3 to provide 
/usr/lib/liblapack.so.3 (liblapack.so.3) in auto mode
  Setting up libgconf-2-4:amd64 (3.2.6-3) ...
  Setting up libgbm1:amd64 (11.2.2-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libxau-dev:amd64 (1:1.0.8-1) ...
  Setting up libthai0:amd64 (0.1.25-1) ...
  Setting up libicu-dev (57.1-3) ...
  Setting up libglib2.0-dev (2.49.6-1) ...
  Setting up python-numpy (1:1.11.1~rc1-1) ...
  Setting up python-gobject-2-dev (2.28.6-13) ...
  Setting up gconf-service (3.2.6-3) ...
  Setting up 

Bug#836889: [Pkg-sugar-devel] Bug#836889: sugar: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Chris Lamb]

> I highly suspect that this was fixed in cdbs 0.145 released yesterday.
> 
> Nice if you could double-check if indeed this issue is closed.

Building now… builds!  Closing in BCC.


Regards,

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