Bug#844986: git repo link

[Paolo Greppi]

Until we find a better home for this, here is a git repo link:
https://gitlab.com/simevo/python-jsonref

Any help or suggestion are welcome !

Paolo



signature.asc
Description: OpenPGP digital signature

Bug#844858: oggvideotools: FTBFS: decoderTest.cpp:19:41: error: 'memset' was not declared in this scope

[Petter Reinholdtsen]

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

Thanks for noticing.  Look like the compiler changed the system header
in some way.  memset() is found in , according to its manual
page.

-- 
Happy hacking
Petter Reinholdtsen

Bug#844987: lvm2: issue discards by default

[Heinrich Schuchardt]

Package: lvm2
Version: 2.02.167-1
Severity: wishlist

Dear Maintainer,

many devices use SSDs for these it makes senses to forward discard
issued by the file system to the device.

I suggest that in /etc/lvm/lvm.conf we set
issue_discards = 1.

If the file system issues discards and the hardware supports it
this setting will result in the forwarding of the discards to
the drive. This is what the user expects.

If the file system does not issue discards or the hardware does not
support it, this setting will have no effect.

There is no benefit for the average user to set
issue_discards = 0.

Best regards

Heinrich Schuchardt

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

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

Versions of packages lvm2 depends on:
ii  dmeventd  2:1.02.136-1
ii  dmsetup   2:1.02.136-1
ii  init-system-helpers   1.46
ii  libblkid1 2.29-1
ii  libc6 2.24-5
ii  libdevmapper-event1.02.1  2:1.02.136-1
ii  libdevmapper1.02.12:1.02.136-1
ii  liblvm2app2.2 2.02.167-1
ii  libreadline5  5.2+dfsg-3+b1
ii  libudev1  232-3
ii  lsb-base  9.20161101

lvm2 recommends no packages.

Versions of packages lvm2 suggests:
pn  thin-provisioning-tools  

-- Configuration Files:
/etc/lvm/lvm.conf changed [not included]

-- no debconf information

Bug#844986: ITP: python-jsonref -- JSON Reference implementation for Python

[Paolo Greppi]

Package: wnpp
Severity: wishlist
Owner: Paolo Greppi 
X-Debbugs-Cc: paolo.gre...@libpf.com, debian-de...@lists.debian.org

* Package name: python-jsonref
  Version : 0.1
  Upstream Author : Chase Sterling 
* URL : https://github.com/gazpachoking/jsonref
* License : MIT
  Programming Lang: Python
  Description : JSON Reference implementation for Python

Python library for automatic dereferencing of JSON Reference object.

It lets you use a data structure with JSON reference objects, as if the
references had been replaced with the referent data. References are
evaluated
lazily. Nothing is dereferenced until it is used. Recursive references are
supported, and create recursive python data structures.


the interest in this is that it is required by python-ramlfications (see
ITP https://bugs.debian.org/843882) which in turn is a build-dependency
for buildbox 0.9.1

Ciao, Paolo



signature.asc
Description: OpenPGP digital signature

Bug#844749: live-build: Jessie image with backported kernel (linux-image-4.7.0-0.bpo.1-amd64) doesn't boot

[intrigeri]

Igor Starkov:
>[2.974235] FAT-fs (sda1): IO charset ascii not found
>mount: mounting /dev/sda1 on /live/medium failed: Invalid argument
>     skipped similar lines 
>[   63.554664] FAT-fs (sda1): IO charset ascii not found
>mount: mounting /dev/sda1 on /live/medium failed: Invalid argument

Try adding a "nls_ascii" line (without quotes) in
/etc/initramfs-tools/modules.

Bug#844786: ITP: snap -- The open telemetry framework

[Geert Stappers]

On Fri, Nov 18, 2016 at 10:40:41PM -0500, matt jones wrote:
> 
> * Package name: snap

That will conflict with 'snap' https://packages.qa.debian.org/s/snap.html

And while solving the package name collision,
try to avoid collisions of filenames of executables and configuration files.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#844982: tntdb: FTBFS: g++: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: tntdb
Version: 1.3-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/src/mysql'
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o bindutils.lo 
> bindutils.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o bindvalues.lo 
> bindvalues.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o boundrow.lo 
> boundrow.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o boundvalue.lo 
> boundvalue.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o connection.lo 
> connection.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> connectionmanager.lo connectionmanager.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o cursor.lo 
> cursor.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o error.lo 
> error.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-long-long -Wall -pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o resultrow.lo 
> resultrow.cpp
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src -I../../include -I../../include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIF

Bug#844976: clisp: FTBFS: Cannot map memory to address 0x8020875b2000 .

[Lucas Nussbaum]

Source: clisp
Version: 1:2.49-10
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Note that this build machine has 256 GB of RAM, so there's something
strange going on.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/debian/build/po'
> installing en.gmo as ../locale/en/LC_MESSAGES/clisp.mo
> installing clisplow_en.gmo as ../locale/en/LC_MESSAGES/clisplow.mo
> installing da.gmo as ../locale/da/LC_MESSAGES/clisp.mo
> installing clisplow_da.gmo as ../locale/da/LC_MESSAGES/clisplow.mo
> installing de.gmo as ../locale/de/LC_MESSAGES/clisp.mo
> installing clisplow_de.gmo as ../locale/de/LC_MESSAGES/clisplow.mo
> installing fr.gmo as ../locale/fr/LC_MESSAGES/clisp.mo
> installing clisplow_fr.gmo as ../locale/fr/LC_MESSAGES/clisplow.mo
> installing es.gmo as ../locale/es/LC_MESSAGES/clisp.mo
> installing clisplow_es.gmo as ../locale/es/LC_MESSAGES/clisplow.mo
> installing nl.gmo as ../locale/nl/LC_MESSAGES/clisp.mo
> installing clisplow_nl.gmo as ../locale/nl/LC_MESSAGES/clisplow.mo
> installing ru.gmo as ../locale/ru/LC_MESSAGES/clisp.mo
> installing clisplow_ru.gmo as ../locale/ru/LC_MESSAGES/clisplow.mo
> make[2]: Leaving directory '/<>/debian/build/po'
> rm -rf data
> mkdir data
> cd data && ln -s /<>/utils/unicode/UnicodeDataFull.txt .
> cd data && ln -s /<>/doc/Symbol-Table.text .
> gcc -falign-functions=4 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit 
> -Wreturn-type -Wmissing-declarations -O -DENABLE_UNICODE -DDYNAMIC_FFI 
> -DDYNAMIC_MODULES -I.  -Wl,--export-dynamic spvw.o spvwtabf.o spvwtabs.o 
> spvwtabo.o eval.o control.o encoding.o pathname.o stream.o socket.o io.o 
> funarg.o array.o hashtabl.o list.o package.o record.o weak.o sequence.o 
> charstrg.o debug.o error.o misc.o time.o predtype.o symbol.o lisparit.o 
> i18n.o foreign.o unixaux.o built.o modules.o -lreadline -lncurses -ldl 
> -lavcall -lcallback  -lsigsegv libgnu_cl.a -o lisp.run
> ./lisp.run -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp 
> /<>/src/ -x '(and (load "/<>/src/init.lisp") 
> (sys::%saveinitmem) (ext::exit)) (ext::exit t)'
>   i i i i i i i   ooooo   o   o
>   I I I I I I I  8 8   8   8 8 o  88
>   I  \ `+' /  I  8 8   8 888
>\  `-+-'  /   8 8   8  o   8
> `-__|__-'8 8   8   8  8
> |8 o   8   8 o 8  8
>   --+--   o8oo  ooo8ooo   o   8
> 
> Welcome to GNU CLISP 2.49 (2010-07-07) <http://clisp.cons.org/>
> 
> Copyright (c) Bruno Haible, Michael Stoll 1992, 1993
> Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
> Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
> Copyright (c) Bruno Haible, Sam Steingold 1999-2000
> Copyright (c) Sam Steingold, Bruno Haible 2001-2010
> 
> Type :h and hit Enter for context help.
> 
> ;; Loading file /<>/src/defseq.lisp ...
> ;; Loaded file /<>/src/defseq.lisp
> ;; Loading file /<>/src/backquote.lisp ...
> ;; Loaded file /<>/src/backquote.lisp
> ;; Loading file /<>/src/defmacro.lisp ...
> ;; Loaded file /<>/src/defmacro.lisp
> ;; Loading file /<>/src/macros1.lisp ...
> ;; Loaded file /<>/src/macros1.lisp
> ;; Loading file /<>/src/macros2.lisp ...
> ;; Loaded file /<>/src/macros2.lisp
> ;; Loading file /<>/src/defs1.lisp ...
> ;; Loaded file /<>/src/defs1.lisp
> ;; Loading file /<>/src/lambdalist.lisp ...
> ;; Loaded file /<>/src/lambdalist.lisp
> ;; Loading file /<>/src/places.lisp ...
> ;; Loaded file /<>/src/places.lisp
> ;; Loading file /<>/src/floatprint.lisp ...
> ;; Loaded file /<>/src/floatprint.lisp
> ;; Loading file /<>/src/defpackage.lisp ...
> ;; Loaded file /<>/src/defpackage.lisp
> ;; Loading file /<>/src/type.lisp ...
> ;;  Loading file /<>/src/subtypep.lisp ...
> ;;  Loaded file /<>/src/subtypep.lisp
> ;; Loaded file /<>/src/type.lisp
> ;; Loading file /<>/src/clos-package.lisp ...
> ;; Loaded file /<>/src/clos-package.lisp
> ;; Loading file /<>/src/clos-macros.lisp ...
> ;; Loaded file /<>/src/clos-macros.lisp
> ;; Loading file /<>/src/clos-class0.lisp ...
> ;; Loaded file /<>/src/clos-class0.lisp
> ;; Loading file /<>/src/clos-metaobject1.lisp ...
> ;; Loaded file /<>/src/clos-metaobject1.lisp
> ;; Loading file /<>/

Bug#844971: monkeysphere: FTBFS: dh_auto_test: make -j1 test returned exit code 2

[Lucas Nussbaum]

Source: monkeysphere
Version: 0.40-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> MONKEYSPHERE_TEST_NO_EXAMINE=true ./tests/keytrans
> ##
> ### generating openpgp key...
> gpg: keybox '/<>/tests/tmp/ms.srQ/pubring.kbx' created
> gpg: /<>/tests/tmp/ms.srQ/trustdb.gpg: trustdb created
> gpg: key 06D32D10E73335B8 marked as ultimately trusted
> gpg: directory '/<>/tests/tmp/ms.srQ/openpgp-revocs.d' created
> gpg: revocation certificate stored as 
> '/<>/tests/tmp/ms.srQ/openpgp-revocs.d/1C654EABB629ED23F97F144F06D32D10E73335B8.rev'
> gpg: done
> ##
> ### retrieving key timestamp...
> gpg: checking the trustdb
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
> ##
> ### exporting key to ssh file...
> ##
> ### reconvert key, and compare to key in gpg keyring...
> --- /dev/fd/632016-11-18 23:34:57.27600 +
> +++ /dev/fd/622016-11-18 23:34:57.27600 +
> @@ -11,11 +11,10 @@
>   keyid: 06D32D10E73335B8
>  # off=475 ctb=b4 tag=13 hlen=2 plen=8
>  :user ID packet: "testtest"
> -# off=485 ctb=88 tag=2 hlen=2 plen=208
> +# off=485 ctb=88 tag=2 hlen=2 plen=185
>  :signature packet: algo 1, keyid 06D32D10E73335B8
>   version 4, created 1479512096, md5len 0, sigclass 0x13
> - digest algo 8, begin of digest f3 0b
> - hashed subpkt 33 len 21 (issuer fpr v4 
> 1C654EABB629ED23F97F144F06D32D10E73335B8)
> + digest algo 8, begin of digest 14 ff
>   hashed subpkt 2 len 4 (sig created 2016-11-18)
>   hashed subpkt 27 len 1 (key flags: 03)
>   hashed subpkt 11 len 5 (pref-sym-algos: 9 8 7 3 2)
> @@ -24,4 +23,4 @@
>   hashed subpkt 30 len 1 (features: 01)
>   hashed subpkt 23 len 1 (keyserver preferences: 80)
>   subpkt 16 len 8 (issuer key ID 06D32D10E73335B8)
> - data: [1022 bits]
> + data: [1024 bits]
> FAILED!
> ### removing temp dir...
> Makefile:116: recipe for target 'test-keytrans' failed
> make[1]: *** [test-keytrans] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: make -j1 test returned exit code 2

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/monkeysphere_0.40-2_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#844979: ratt: FTBFS: dh_auto_build: go install -v -p 1 github.com/debian/ratt returned exit code 2

[Lucas Nussbaum]

Source: ratt
Version: 0.0~git20150816.0.b060319-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 github.com/debian/ratt
> golang.org/x/crypto/openpgp/errors
> golang.org/x/crypto/openpgp/armor
> golang.org/x/crypto/cast5
> golang.org/x/crypto/openpgp/elgamal
> golang.org/x/crypto/openpgp/s2k
> golang.org/x/crypto/openpgp/packet
> golang.org/x/crypto/openpgp
> golang.org/x/crypto/openpgp/clearsign
> pault.ag/go/debian/version
> pault.ag/go/debian/dependency
> pault.ag/go/debian/internal
> pault.ag/go/debian/transput
> pault.ag/go/topsort
> pault.ag/go/debian/control
> github.com/debian/ratt
> # github.com/debian/ratt
> src/github.com/debian/ratt/ratt.go:117: undefined: control.ParseParagraph
> dh_auto_build: go install -v -p 1 github.com/debian/ratt returned exit code 2
> debian/rules:4: recipe for target 'build' failed
> make: *** [build] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/ratt_0.0~git20150816.0.b060319-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#844967: picviz: FTBFS: cmake_minimum_required(VERSION 3.7)

[Lucas Nussbaum]

Source: picviz
Version: 0.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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_testdir
> # Add here commands to configure the package.
> [ -d build ] || mkdir build
> cd build && cmake -DCMAKE_SKIP_RPATH:BOOL=ON \
>   -DLIB_INSTALL_DIR=/usr/lib \
>   -DMOD_INSTALL_DIR=/usr/lib/picviz \
>   -DCMAKE_INSTALL_PREFIX=/usr \
>   ..
> -- The C compiler identification is GNU 6.2.0
> -- The CXX compiler identification is GNU 6.2.0
> -- 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
> CMake Warning (dev) at CMakeLists.txt:18 (add_definitions):
>   Policy CMP0005 is not set: Preprocessor definition values are now escaped
>   automatically.  Run "cmake --help-policy CMP0005" for policy details.  Use
>   the cmake_policy command to set the policy and suppress this warning.
> This warning is for project developers.  Use -Wno-dev to suppress it.
> 
> CMake Warning (dev) at CMakeLists.txt:19 (add_definitions):
>   Policy CMP0005 is not set: Preprocessor definition values are now escaped
>   automatically.  Run "cmake --help-policy CMP0005" for policy details.  Use
>   the cmake_policy command to set the policy and suppress this warning.
> This warning is for project developers.  Use -Wno-dev to suppress it.
> 
> -- WARNING: you are using the obsolete 'PKGCONFIG' macro, use FindPkgConfig
> -- PKGCONFIG() indicates that plplotd is not installed (install the package 
> which contains plplotd.pc if you want to support this feature)
> -- WARNING: you are using the obsolete 'PKGCONFIG' macro, use FindPkgConfig
> -- Found PCRE: /usr/include  
> -- Could NOT find EVENT (missing:  EVENT_EVENT_LIBRARY) 
> -- checking for module 'cairo-png'
> --   found cairo-png, version 1.14.6
> CMake Warning (dev) at src/libpicviz/CMakeLists.txt:25 (add_library):
>   Policy CMP0002 is not set: Logical target names must be globally unique.
>   Run "cmake --help-policy CMP0002" for policy details.  Use the cmake_policy
>   command to set the policy and suppress this warning.
> This warning is for project developers.  Use -Wno-dev to suppress it.
> 
> CMake Error at src/libpicviz/CMakeLists.txt:31 (install):
>   install TARGETS given no ARCHIVE DESTINATION for static library target
>   "picviz".
> 
> 
> CMake Warning (dev) in CMakeLists.txt:
>   No cmake_minimum_required command is present.  A line of code such as
> 
> cmake_minimum_required(VERSION 3.7)
> 
>   should be added at the top of the file.  The version specified may be lower
>   if you wish to support older CMake versions for this project.  For more
>   information run "cmake --help-policy CMP".
> This warning is for project developers.  Use -Wno-dev to suppress it.
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/build/CMakeFiles/CMakeOutput.log".
> debian/rules:18: recipe for target 'configure-stamp' failed
> make: *** [configure-stamp] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/picviz_0.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#844959: android-platform-tools-base: FTBFS: org.codehaus.groovy.runtime.typehandling.GroovyCastException

[Lucas Nussbaum]

Source: android-platform-tools-base
Version: 2.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> dh_auto_build -- -x test --settings-file debian/settings.gradle assemble
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian --parallel --max-workers=64 -x test --settings-file 
> debian/settings.gradle assemble
> Initialized native services in: /<>/.gradle/native
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
>   Loading the Maven rules...
> Compiling settings file '/<>/debian/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/debian/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file 
> '/<>/debian/settings.gradle'.
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'debian', project ':base', project 
> ':base:annotations', project ':base:archquery', project ':base:asset-studio', 
> project ':base:builder', project ':base:builder-model', project 
> ':base:builder-test-api', project ':base:common', project ':base:ddmlib', 
> project ':base:draw9patch', project ':base:dvlib', project 
> ':base:google-services', project ':base:gradle', project ':base:gradle-api', 
> project ':base:gradle-core', project ':base:jack', project 
> ':base:layoutlib-api', project ':base:lint', project ':base:lint-api', 
> project ':base:lint-checks', project ':base:manifest-merger', project 
> ':base:repository', project ':base:screenshot2', project ':base:sdk-common', 
> project ':base:sdklib', project ':base:testutils', project 
> ':base:transform-api', project ':base:jack:jack-api', project 
> ':base:jack:jill-api']
>   Keep-alive timer started
>   Adding Debian repository to project 'debian'
>   Adding Debian repository to project 'base'
>   Adding Debian repository to project 'annotations'
>   Adding Debian repository to project 'archquery'
>   Adding Debian repository to project 'asset-studio'
>   Adding Debian repository to project 'builder'
>   Adding Debian repository to project 'builder-model'
>   Adding Debian repository to project 'builder-test-api'
>   Adding Debian repository to project 'common'
>   Adding Debian repository to project 'ddmlib'
>   Adding Debian repository to project 'draw9patch'
>   Adding Debian repository to project 'dvlib'
>   Adding Debian repository to project 'google-services'
>   Adding Debian repository to project 'gradle'
>   Adding Debian repository to project 'gradle-api'
>   Adding Debian repository to project 'gradle-core'
>   Adding Debian repository to project 'jack'
>   Adding Debian repository to project 'layoutlib-api'
>   Adding Debian repository to project 'lint'
>   Adding Debian repository to project 'lint-api'
>   Adding Debian repository to project 'lint-checks'
>   Adding Debian repository to project 'manifest-merger'
>   Adding Debian repository to project 'repository'
>   Adding Debian repository to project 'screenshot2'
>   Adding Debian repository to project 'sdk-common'
>   Adding Debian repository to project 'sdklib'
>   Adding Debian repository to project 'testutils'
>   Adding Debian repository to project 'transform-api'
>   Adding Debian repository to project 'jack-api'
>   Adding Debian repository to project 'jill-api'
> Parallel execution is an incubating feature.
> Evaluating root project 'debian' using build file 
> '/<>/build.gradle'.
> Compiling build file '/<>/build.gradle' using 
> SubsetScriptTransformer.
> Compiling build file '/<>/build.gradle' using 
> BuildScriptTransformer.
> Compiling script '/<>/debian/version.gradle' using 
> SubsetScriptTransformer.
> Compiling script '/<>/debian/version.gradle' using 
> BuildScriptTransformer.
> Compiling script '/<>/debian/generatePom.gradle' using 
> SubsetScriptTransformer.
> Compiling script '/<>/debian/generatePom.gradle' using 
> BuildScriptTransformer.
> Compiling script '/<>/debian/generateClasspath.gradl

Bug#844961: golang-google-cloud: FTBFS: dh_auto_build: go install -v -p 1 google.golang.org/cloud google.golang.org/cloud/bigquery google.golang.org/cloud/bigtable google.golang.org/cloud/bigtable/btt

[Lucas Nussbaum]

Source: golang-google-cloud
Version: 0.0~git20160615-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 google.golang.org/cloud 
> google.golang.org/cloud/bigquery google.golang.org/cloud/bigtable 
> google.golang.org/cloud/bigtable/bttest 
> google.golang.org/cloud/bigtable/cmd/cbt 
> google.golang.org/cloud/bigtable/cmd/loadtest 
> google.golang.org/cloud/bigtable/internal/cbtrc 
> google.golang.org/cloud/bigtable/internal/cluster_data_proto 
> google.golang.org/cloud/bigtable/internal/cluster_service_proto 
> google.golang.org/cloud/bigtable/internal/data_proto 
> google.golang.org/cloud/bigtable/internal/rpc_status_proto 
> google.golang.org/cloud/bigtable/internal/service_proto 
> google.golang.org/cloud/bigtable/internal/table_data_proto 
> google.golang.org/cloud/bigtable/internal/table_service_proto 
> google.golang.org/cloud/compute/metadata google.golang.org/cloud/container 
> google.golang.org/cloud/datastore 
> google.golang.org/cloud/datastore/internal/proto 
> google.golang.org/cloud/datastore/internal/type_proto 
> google.golang.org/cloud/examples/bigquery/concat_table 
> google.golang.org/cloud/examples/bigquery/load 
> google.golang.org/cloud/examples/bigquery/query 
> google.golang.org/cloud/examples/bigquery/read 
> google.golang.org/cloud/examples/bigtable/bigtable-hello 
> google.golang.org/cloud/examples/bigtable/search 
> google.golang.org/cloud/examples/pubsub/cmdline 
> google.golang.org/cloud/examples/pubsub/consumer 
> google.golang.org/cloud/examples/storage/appengine 
> google.golang.org/cloud/examples/storage/appenginevm 
> google.golang.org/cloud/internal google.golang.org/cloud/internal/opts 
> google.golang.org/cloud/internal/testutil 
> google.golang.org/cloud/internal/transport google.golang.org/cloud/logging 
> google.golang.org/cloud/logging/apiv2/config 
> google.golang.org/cloud/logging/apiv2/logging 
> google.golang.org/cloud/logging/apiv2/metrics google.golang.org/cloud/pubsub 
> google.golang.org/cloud/storage
> src/google.golang.org/cloud/internal/transport/dial.go:24:2: cannot find 
> package "golang.org/x/oauth2/google" in any of:
>   /usr/lib/go-1.7/src/golang.org/x/oauth2/google (from $GOROOT)
>   /<>/obj-x86_64-linux-gnu/src/golang.org/x/oauth2/google 
> (from $GOPATH)
> dh_auto_build: go install -v -p 1 google.golang.org/cloud 
> google.golang.org/cloud/bigquery google.golang.org/cloud/bigtable 
> google.golang.org/cloud/bigtable/bttest 
> google.golang.org/cloud/bigtable/cmd/cbt 
> google.golang.org/cloud/bigtable/cmd/loadtest 
> google.golang.org/cloud/bigtable/internal/cbtrc 
> google.golang.org/cloud/bigtable/internal/cluster_data_proto 
> google.golang.org/cloud/bigtable/internal/cluster_service_proto 
> google.golang.org/cloud/bigtable/internal/data_proto 
> google.golang.org/cloud/bigtable/internal/rpc_status_proto 
> google.golang.org/cloud/bigtable/internal/service_proto 
> google.golang.org/cloud/bigtable/internal/table_data_proto 
> google.golang.org/cloud/bigtable/internal/table_service_proto 
> google.golang.org/cloud/compute/metadata google.golang.org/cloud/container 
> google.golang.org/cloud/datastore 
> google.golang.org/cloud/datastore/internal/proto 
> google.golang.org/cloud/datastore/internal/type_proto 
> google.golang.org/cloud/examples/bigquery/concat_table 
> google.golang.org/cloud/examples/bigquery/load 
> google.golang.org/cloud/examples/bigquery/query 
> google.golang.org/cloud/examples/bigquery/read 
> google.golang.org/cloud/examples/bigtable/bigtable-hello 
> google.golang.org/cloud/examples/bigtable/search 
> google.golang.org/cloud/examples/pubsub/cmdline 
> google.golang.org/cloud/examples/pubsub/consumer 
> google.golang.org/cloud/examples/storage/appengine 
> google.golang.org/cloud/examples/storage/appenginevm 
> google.golang.org/cloud/internal google.golang.org/cloud/internal/opts 
> google.golang.org/cloud/internal/testutil 
> google.golang.org/cloud/internal/transport google.golang.org/cloud/logging 
> google.golang.org/cloud/logging/apiv2/config 
> google.golang.org/cloud/logging/apiv2/logging 
> google.golang.org/cloud/logging/apiv2/metrics google.golang.org/cloud/pubsub 
> google.golang.org/cloud/storage returned exit code 1
> debian/rules:6: recipe for target 'build' failed

Bug#844983: zygrib: FTBFS: dpkg-buildpackage: error: dpkg-source -b zygrib-7.0.0 gave error exit status 2

[Lucas Nussbaum]

Source: zygrib
Version: 7.0.0-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>/src'
> rm -f objs/moc_PositionEditorWidget.cpp objs/moc_ColorEditorWidget.cpp 
> objs/moc_LineEditorWidget.cpp objs/moc_TextStyleEditorWidget.cpp 
> objs/moc_AngleConverterWidget.cpp objs/moc_AngleConverterDialog.cpp 
> objs/moc_CurveDrawer.cpp objs/moc_BoardPanel.cpp 
> objs/moc_ColorScaleWidget.cpp objs/moc_DataQString.cpp 
> objs/moc_DateChooser.cpp objs/moc_DialogBoxColumn.cpp 
> objs/moc_DialogFonts.cpp objs/moc_DialogGraphicsParams.cpp 
> objs/moc_DialogLoadGRIB.cpp objs/moc_DialogLoadIAC.cpp 
> objs/moc_DialogLoadMBLUE.cpp objs/moc_DialogProxy.cpp 
> objs/moc_DialogSelectMetar.cpp objs/moc_DialogServerStatus.cpp 
> objs/moc_DialogUnits.cpp objs/moc_FileLoaderGRIB.cpp 
> objs/moc_FileLoaderIAC.cpp objs/moc_FileLoaderMBLUE.cpp 
> objs/moc_GribAnimator.cpp objs/moc_ImageWriter.cpp 
> objs/moc_LongTaskProgress.cpp objs/moc_Metar.cpp objs/moc_MeteoTable.cpp 
> objs/moc_MeteoTableWidget.cpp objs/moc_MeteotableOptionsDialog.cpp 
> objs/moc_MainWindow.cpp objs/moc_MapDrawer.cpp objs/moc_MenuBar.cpp 
> objs/moc_POI.cpp objs/moc_POI_Editor.cpp objs/moc_PositionEditor.cpp 
> objs/moc_Projection.cpp objs/moc_SkewT.cpp objs/moc_Terrain.cpp 
> objs/moc_Util.cpp
> rm -f GUI/ui_PositionEditorWidget.h GUI/ui_PoiEditorDialog.h 
> GUI/ui_ColorEditorWidget.h GUI/ui_LineEditorWidget.h 
> GUI/ui_TextStyleEditorWidget.h GUI/ui_GraphicsParamsDialog.h 
> GUI/ui_MeteotableOptionsDialog.h GUI/ui_AngleConverterWidget.h
> rm -f objs/PositionEditorWidget.o objs/ColorEditorWidget.o 
> objs/LineEditorWidget.o objs/TextStyleEditorWidget.o 
> objs/AngleConverterWidget.o objs/AngleConverterDialog.o objs/BoatSpeed.o 
> objs/CurveDrawer.o objs/CustomQwtClasses.o objs/Astro.o objs/MbzFile.o 
> objs/MblueRecord.o objs/MblueReader.o objs/MbluePlot.o objs/BoardPanel.o 
> objs/ColorScale.o objs/ColorScaleWidget.o objs/DataColors.o 
> objs/DataQString.o objs/DataMeteoAbstract.o objs/DataPointInfo.o 
> objs/DateChooser.o objs/DialogBoxColumn.o objs/DialogFonts.o 
> objs/DialogGraphicsParams.o objs/DialogLoadGRIB.o objs/DialogLoadIAC.o 
> objs/DialogLoadMBLUE.o objs/DialogProxy.o objs/DialogSelectMetar.o 
> objs/DialogServerStatus.o objs/DialogUnits.o objs/FileLoaderGRIB.o 
> objs/FileLoaderIAC.o objs/FileLoaderMBLUE.o objs/Font.o objs/GriddedPlotter.o 
> objs/GriddedReader.o objs/GriddedRecord.o objs/GshhsRangsReader.o 
> objs/GshhsReader.o objs/GribAnimator.o objs/GribPlot.o objs/GisReader.o 
> objs/GribReader.o objs/GribRecord.o objs/IacPlot.o objs/IacReader.o 
> objs/IacReaderUtil.o objs/ImageWriter.o objs/IrregularGridded.o 
> objs/IsoLine.o objs/LongTaskProgress.o objs/LonLatGrid.o objs/main.o 
> objs/MainWindow.o objs/MapDrawer.o objs/MenuBar.o objs/Metar.o 
> objs/MeteoTable.o objs/MeteoTableWidget.o objs/MeteotableOptionsDialog.o 
> objs/Orthodromie.o objs/POI.o objs/POI_Editor.o objs/PositionEditor.o 
> objs/Projection.o objs/Projection_libproj.o objs/Settings.o objs/SkewT.o 
> objs/SkewTWindow.o objs/Terrain.o objs/Therm.o objs/Util.o objs/zuFile.o 
> objs/moc_PositionEditorWidget.o objs/moc_ColorEditorWidget.o 
> objs/moc_LineEditorWidget.o objs/moc_TextStyleEditorWidget.o 
> objs/moc_AngleConverterWidget.o objs/moc_AngleConverterDialog.o 
> objs/moc_CurveDrawer.o objs/moc_BoardPanel.o objs/moc_ColorScaleWidget.o 
> objs/moc_DataQString.o objs/moc_DateChooser.o objs/moc_DialogBoxColumn.o 
> objs/moc_DialogFonts.o objs/moc_DialogGraphicsParams.o 
> objs/moc_DialogLoadGRIB.o objs/moc_DialogLoadIAC.o objs/moc_DialogLoadMBLUE.o 
> objs/moc_DialogProxy.o objs/moc_DialogSelectMetar.o 
> objs/moc_DialogServerStatus.o objs/moc_DialogUnits.o 
> objs/moc_FileLoaderGRIB.o objs/moc_FileLoaderIAC.o objs/moc_FileLoaderMBLUE.o 
> objs/moc_GribAnimator.o objs/moc_ImageWriter.o objs/moc_LongTaskProgress.o 
> objs/moc_Metar.o objs/moc_MeteoTable.o objs/moc_MeteoTableWidget.o 
> objs/moc_MeteotableOptionsDialog.o objs/moc_MainWindow.o objs/moc_MapDrawer.o 
> objs/moc_MenuBar.o objs/moc_POI.o objs/moc_POI_Editor.o 
> objs/moc_PositionEditor.o objs/moc_Projection.o objs/moc_SkewT.o 
> objs/moc_Terrain.o objs/moc_Util.o
> rm -f *~ core *.core
> make[3]: Leaving directory '/<>/src'
> make[2]: Leaving directory '/<>'
> rm -rf  src/objs/* src/zyGrib src/Makefile src/qwt-6.0.1
> make[1]: Leaving directory '/<>'
>dh_clean
>   rm -f debian/debhelper-build-stamp
>   rm -f debian/zygrib.substvars
>   rm -f debian/zygrib.*.debhelper
>   rm -rf debian/zygrib/
>   rm -f debian/zygri

Bug#844985: ITP: fonts-churchslavonic -- This package provides OpenType and TrueType fonts for Church Slavonic (cu)

[Aleksandr Andreev]

Package: wnpp
Severity: wishlist
Owner: Aleksandr Andreev 

* Package name: fonts-churchslavonic
  Version : 1.0.0
  Upstream Author : Aleksandr Andreev 
* URL : http://sci.ponomar.net/
* License : SIL Open Font License 1.1
  Programming Lang: N/A
  Description : Fonts for Church Slavonic language

This package provides OpenType and TrueType fonts for the Church Slavonic (cu)
language. Fonts use OpenType and SIL Graphite features and Unicode encoding.

A sponsor is needed.

Bug#836826: FTBFS: cp: cannot stat '/usr/src/gtest/src': No such file or directory

[Lucas Nussbaum]

severity -1 serious
thanks

Hi,

On 06/09/16 at 11:40 +0200, Goswin von Brederlow wrote:
> it looks like protobuf is missing a Build-Depends on libgtest-dev:

This FTBFS bug should have been filed as severity:serious.

Lucas

Bug#844832: yade: FTBFS: build-dependency not installable: libvtk6-dev

[Anton Gladky]

Hi Lucas,

thanks for the bugreport. But in this case there is nothing to do
with vtk6, but with its dependencies, which can not be satisfied,

Short research indicated the problem with the package pycparser.
It has in dependencies python-ply-lex-3.5 and python-ply-yacc-3.5 and
they are not available.

[1] https://packages.debian.org/unstable/python-pycparser

Best regards

Anton


2016-11-19 7:28 GMT+01:00 Lucas Nussbaum <lu...@debian.org>:
> Source: yade
> Version: 2016.06a-5
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161118 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):
>> +--+
>> | Install package build dependencies 
>>   |
>> +--+
>>
>>
>> Setup apt archive
>> -
>>
>> Merged Build-Depends: cmake, debhelper (>= 9), freeglut3-dev, help2man, 
>> ipython (>= 5), libboost-all-dev, libbz2-dev, libcgal-dev, libeigen3-dev (>= 
>> 3.2.1-2), libgl1-mesa-dev, libgts-dev, libloki-dev, libmetis-dev, 
>> libopenblas-dev, libqglviewer-dev-qt5, libsuitesparse-dev, libvtk6-dev, 
>> libxi-dev, libxmu-dev, pyqt5-dev-tools, python-all-dev, python-gts, 
>> python-imaging, python-matplotlib, python-minieigen, python-numpy, 
>> python-sip, python-pyqt5, python-tk, python-xlib, zlib1g-dev, dvipng, 
>> graphviz, libjs-jquery, lmodern, python-bibtex, python-sphinx, 
>> texlive-fonts-recommended, texlive-generic-extra, texlive-latex-extra, 
>> texlive-latex-recommended, texlive-pictures, texlive-xetex, tipa
>> Filtered Build-Depends: cmake, debhelper (>= 9), freeglut3-dev, help2man, 
>> ipython (>= 5), libboost-all-dev, libbz2-dev, libcgal-dev, libeigen3-dev (>= 
>> 3.2.1-2), libgl1-mesa-dev, libgts-dev, libloki-dev, libmetis-dev, 
>> libopenblas-dev, libqglviewer-dev-qt5, libsuitesparse-dev, libvtk6-dev, 
>> libxi-dev, libxmu-dev, pyqt5-dev-tools, python-all-dev, python-gts, 
>> python-imaging, python-matplotlib, python-minieigen, python-numpy, 
>> python-sip, python-pyqt5, python-tk, python-xlib, zlib1g-dev, dvipng, 
>> graphviz, libjs-jquery, lmodern, python-bibtex, python-sphinx, 
>> texlive-fonts-recommended, texlive-generic-extra, texlive-latex-extra, 
>> texlive-latex-recommended, texlive-pictures, texlive-xetex, tipa
>> dpkg-deb: building package 'sbuild-build-depends-yade-dummy' in 
>> '/<>/resolver-dm1LPf/apt_archive/sbuild-build-depends-yade-dummy.deb'.
>> dpkg-scanpackages: warning: Packages in archive but missing from override 
>> file:
>> dpkg-scanpackages: warning:   sbuild-build-depends-yade-dummy
>> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
>> Ign:1 copy:/<>/resolver-dm1LPf/apt_archive ./ InRelease
>> Get:2 copy:/<>/resolver-dm1LPf/apt_archive ./ Release [963 B]
>> Ign:3 copy:/<>/resolver-dm1LPf/apt_archive ./ Release.gpg
>> Get:4 copy:/<>/resolver-dm1LPf/apt_archive ./ Sources [645 B]
>> Get:5 copy:/<>/resolver-dm1LPf/apt_archive ./ Packages [707 B]
>> Fetched 2315 B in 0s (0 B/s)
>> Reading package lists...
>> W: No sandbox user '_apt' on the system, can not drop privileges
>> Reading package lists...
>>
>> Install yade build dependencies (apt-based resolver)
>> 
>>
>> Installing build dependencies
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>> The following packages have unmet dependencies:
>>  sbuild-build-depends-yade-dummy : Depends: libvtk6-dev but it is not going 
>> to be installed
>> E: Unable to correct problems, you have held broken packages.
>> apt-get failed.
>
> The full build log is available from:
>http://aws-logs.debian.net/2016/11/18/yade_2016.06a-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.
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#844981: ruby-mysql: FTBFS: cat: mkmf.log: No such file or directory

[Lucas Nussbaum]

Source: ruby-mysql
Version: 2.9.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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
> dh binary --buildsystem=ruby --with ruby
> dh: Compatibility levels before 9 are deprecated (level 7 in use)
>dh_testroot -O--buildsystem=ruby
>dh_prep -O--buildsystem=ruby
>dh_auto_install -O--buildsystem=ruby
> dh_auto_install: Compatibility levels before 9 are deprecated (level 7 in use)
>   dh_ruby --install /<>/debian/ruby-mysql
>dh_ruby --install
> 
> ┌──┐
> │ Install files   
>  │
> └──┘
> 
> install -d /<>/debian/ruby-mysql/usr/lib/ruby/vendor_ruby
> install -D -m644 /<>/lib/mysql/version.rb 
> /<>/debian/ruby-mysql/usr/lib/ruby/vendor_ruby/mysql/version.rb
> install -D -m644 /<>/lib/mysql.rb 
> /<>/debian/ruby-mysql/usr/lib/ruby/vendor_ruby/mysql.rb
> 
> ┌──┐
> │ Build native extensions for ruby2.3 
>  │
> └──┘
> 
> /usr/bin/ruby2.3 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
> /<> debian/ruby-mysql
> current directory: /<>/ext/mysql_api
> /usr/bin/ruby2.3 -r ./siteconf20161118-86628-r8c656.rb extconf.rb
> checking for mysql_ssl_set()... *** extconf.rb failed ***
> Could not create Makefile due to some reason, probably lack of necessary
> libraries and/or headers.  Check the mkmf.log file for more details.  You may
> need configuration options.
> 
> Provided configuration options:
>   --with-opt-dir
>   --without-opt-dir
>   --with-opt-include
>   --without-opt-include=${opt-dir}/include
>   --with-opt-lib
>   --without-opt-lib=${opt-dir}/lib
>   --with-make-prog
>   --without-make-prog
>   --srcdir=.
>   --curdir
>   --ruby=/usr/bin/$(RUBY_BASE_NAME)2.3
>   --with-mysql-config
>   --without-mysql-config
> /usr/lib/ruby/2.3.0/mkmf.rb:456:in `try_do': The compiler failed to generate 
> an executable file. (RuntimeError)
> You have to install development tools first.
>   from /usr/lib/ruby/2.3.0/mkmf.rb:541:in `try_link0'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:556:in `try_link'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:765:in `try_func'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:1051:in `block in have_func'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:942:in `block in checking_for'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:350:in `block (2 levels) in postpone'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:320:in `open'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:350:in `block in postpone'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:320:in `open'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:346:in `postpone'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:941:in `checking_for'
>   from /usr/lib/ruby/2.3.0/mkmf.rb:1050:in `have_func'
>   from extconf.rb:45:in `'
> ~ ↓ mkmf.log ~
> cat: mkmf.log: No such file or directory
> /usr/lib/ruby/2.3.0/rubygems/ext/builder.rb:92:in `run': extconf failed, exit 
> code 1 (Gem::InstallError)
>   from /usr/lib/ruby/2.3.0/rubygems/ext/ext_conf_builder.rb:48:in `block 
> in build'
>   from /usr/lib/ruby/2.3.0/tempfile.rb:295:in `open'
>   from /usr/lib/ruby/2.3.0/rubygems/ext/ext_conf_builder.rb:31:in `build'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:76:in 
> `block in build_and_install'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:70:in 
> `chdir'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:70:in 
> `build_and_install'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:108:in 
> `block in build_all_extensions'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:105:in 
> `each'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:105:in 
> `build_all_extensions'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb:121:in 
> `'
> ~ ↑ mkmf.log ~
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:56:in `run': /usr/bin/ruby2.3 
> /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /<> 
> debian/ruby-mysql (Gem2Deb::Comma

Bug#844970: ganeti: FTBFS: Makefile:4386: Makefile.ghc: No such file or directory

[Lucas Nussbaum]

Source: ganeti
Version: 2.15.2-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> Makefile:4386: Makefile.ghc: No such file or directory
> mkdir -p apps
> rm -f apps/htools.hs
> ln -s ../src/htools.hs apps/htools.hs
> touch apps/htools.hs.stamp
> mkdir -p apps
> rm -f apps/hpc-htools.hs
> ln -s ../test/hs/hpc-htools.hs apps/hpc-htools.hs
> touch apps/hpc-htools.hs.stamp
> mkdir -p apps
> rm -f apps/hpc-mon-collector.hs
> ln -s ../test/hs/hpc-mon-collector.hs apps/hpc-mon-collector.hs
> touch apps/hpc-mon-collector.hs.stamp
> mkdir -p apps
> rm -f apps/ganeti-kvmd.hs
> ln -s ../src/ganeti-kvmd.hs apps/ganeti-kvmd.hs
> touch apps/ganeti-kvmd.hs.stamp
> mkdir -p apps
> rm -f apps/ganeti-wconfd.hs
> ln -s ../src/ganeti-wconfd.hs apps/ganeti-wconfd.hs
> touch apps/ganeti-wconfd.hs.stamp
> mkdir -p apps
> rm -f apps/hconfd.hs
> ln -s ../src/hconfd.hs apps/hconfd.hs
> touch apps/hconfd.hs.stamp
> mkdir -p apps
> rm -f apps/hluxid.hs
> ln -s ../src/hluxid.hs apps/hluxid.hs
> touch apps/hluxid.hs.stamp
> mkdir -p apps
> rm -f apps/hs2py.hs
> ln -s ../src/hs2py.hs apps/hs2py.hs
> touch apps/hs2py.hs.stamp
> mkdir -p apps
> rm -f apps/rpc-test.hs
> ln -s ../src/rpc-test.hs apps/rpc-test.hs
> touch apps/rpc-test.hs.stamp
> mkdir -p apps
> rm -f apps/ganeti-mond.hs
> ln -s ../src/ganeti-mond.hs apps/ganeti-mond.hs
> touch apps/ganeti-mond.hs.stamp
> mkdir -p apps
> rm -f apps/ganeti-metad.hs
> ln -s ../src/ganeti-metad.hs apps/ganeti-metad.hs
> touch apps/ganeti-metad.hs.stamp
> for p in src/htools test/hs/hpc-htools test/hs/hpc-mon-collector 
> src/ganeti-kvmd src/ganeti-wconfd src/hconfd src/hluxid src/hs2py 
> src/rpc-test src/ganeti-mond src/ganeti-metad ; do \
>   echo   >> ganeti.cabal; \
>   echo "executable `basename $p`"   >> ganeti.cabal; \
>   echo "  hs-source-dirs: apps"  >> ganeti.cabal; \
>   echo "  main-is: `basename $p`.hs">> ganeti.cabal; \
>   echo "  default-language: Haskell2010" >> ganeti.cabal; \
>   echo "  build-depends:">> ganeti.cabal; \
>   echo "  base"  >> ganeti.cabal; \
>   echo ", ganeti">> ganeti.cabal; \
>   if [ $p == test/hs/htest ]; then \
> echo ", hslogger"  >> ganeti.cabal; \
> echo ", test-framework">> ganeti.cabal; \
>   elif [ $p == src/rpc-test ]; then \
> echo ", json"  >> ganeti.cabal; \
>   fi \
> done
> touch empty-cabal-config
> /usr/bin/cabal --config-file=empty-cabal-config configure --user \
>   -f`test no == yes && echo "htest" || echo "-htest"` \
>   -f`test True == True && echo "mond" || echo "-mond"` \
>   -f`test True == True && echo "metad" || echo "-metad"`
> Warning: No remote package servers have been specified. Usually you would have
> one specified in the config file.
> Resolving dependencies...
> Warning: solver failed to find a solution:
> Could not resolve dependencies:
> trying: ganeti-2.15 (user goal)
> next goal: MonadCatchIO-transformers (dependency of ganeti-2.15)
> Dependency tree exhaustively searched.
> Trying configure anyway.
> cabal: unable to decommit memory: Invalid argument
> cabal: unable to decommit memory: Invalid argument
> cabal: unable to decommit memory: Invalid argument
> cabal: unable to decommit memory: Invalid argument
> Configuring ganeti-2.15...
> cabal: Encountered missing dependencies:
> MonadCatchIO-transformers >=0.3.0.0 && <0.4
> cabal: unable to decommit memory: Invalid argument
> cabal: unable to decommit memory: Invalid argument
> cabal: unable to decommit memory: Invalid argument
> Makefile:4394: recipe for target 'cabal_macros.h' failed
> make[2]: *** [cabal_macros.h] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/ganeti_2.15.2-6_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#844968: git-annex: FTBFS: cabal: unable to decommit memory: Invalid argument

[Lucas Nussbaum]

Source: git-annex
Version: 6.20161012-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Note that this build machine has 256GB of RAM. Maybe there's something
strange going on with machines with a lot of RAM?

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> if [ "debian/cabal-wrapper" = ./Setup ]; then ghc --make Setup; fi
> if [ "debian/cabal-wrapper" = stack ]; then \
>   debian/cabal-wrapper build -j1; \
> else \
>   debian/cabal-wrapper configure --ghc-options="-optl-Wl,-z,relro -optc-g 
> -optc-O2 -optc-fdebug-prefix-map=/<>=. 
> -optc-fstack-protector-strong -optc-Wformat -optc-Werror=format-security 
> -optc-Wp,-Wdate-time -optc-Wp,-D_FORTIFY_SOURCE=2"; \
> fi
> Config file path source is default config file.
> Config file /tmp/tmp.XSW1xAw2K6/.cabal/config not found.
> Writing default configuration to /tmp/tmp.XSW1xAw2K6/.cabal/config
> Warning: The package list for 'hackage.haskell.org' does not exist. Run 'cabal
> update' to download it.
> Resolving dependencies...
> cabal: unable to decommit memory: Invalid argument
> Warning: solver failed to find a solution:
> Could not resolve dependencies:
> trying: git-annex-6.20161012 (user goal)
> next goal: persistent-template (dependency of git-annex-6.20161012)
> rejecting: persistent-template-2.5.1.6/installed-FlO... (conflict:
> persistent-template => persistent==2.6/installed-2DW..., git-annex =>
> persistent(<2.5))
> Dependency tree exhaustively searched.
> Trying configure anyway.
> [ 1 of 34] Compiling Utility.FileSize ( Utility/FileSize.hs, 
> dist/setup/Utility/FileSize.o )
> cabal: unable to decommit memory: Invalid argument
> cabal: unable to decommit memory: Invalid argument
> [ 2 of 34] Compiling Utility.Applicative ( Utility/Applicative.hs, 
> dist/setup/Utility/Applicative.o )
> [ 3 of 34] Compiling Utility.PosixFiles ( Utility/PosixFiles.hs, 
> dist/setup/Utility/PosixFiles.o )
> [ 4 of 34] Compiling Utility.SystemDirectory ( Utility/SystemDirectory.hs, 
> dist/setup/Utility/SystemDirectory.o )
> [ 5 of 34] Compiling Utility.Env  ( Utility/Env.hs, 
> dist/setup/Utility/Env.o )
> [ 6 of 34] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs, 
> dist/setup/Utility/PartialPrelude.o )
> [ 7 of 34] Compiling Utility.Process.Shim ( Utility/Process/Shim.hs, 
> dist/setup/Utility/Process/Shim.o )
> [ 8 of 34] Compiling Utility.Data ( Utility/Data.hs, 
> dist/setup/Utility/Data.o )
> [ 9 of 34] Compiling Utility.Exception ( Utility/Exception.hs, 
> dist/setup/Utility/Exception.o )
> [10 of 34] Compiling Build.Mans   ( Build/Mans.hs, 
> dist/setup/Build/Mans.o )
> [11 of 34] Compiling Utility.FileSystemEncoding ( 
> Utility/FileSystemEncoding.hs, dist/setup/Utility/FileSystemEncoding.o )
> [12 of 34] Compiling Utility.Tmp  ( Utility/Tmp.hs, 
> dist/setup/Utility/Tmp.o )
> [13 of 34] Compiling Utility.UserInfo ( Utility/UserInfo.hs, 
> dist/setup/Utility/UserInfo.o )
> [14 of 34] Compiling Utility.OSX  ( Utility/OSX.hs, 
> dist/setup/Utility/OSX.o )
> [15 of 34] Compiling Utility.Monad( Utility/Monad.hs, 
> dist/setup/Utility/Monad.o )
> [16 of 34] Compiling Utility.Misc ( Utility/Misc.hs, 
> dist/setup/Utility/Misc.o )
> [17 of 34] Compiling Utility.Process  ( Utility/Process.hs, 
> dist/setup/Utility/Process.o )
> [18 of 34] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, 
> dist/setup/Utility/SafeCommand.o )
> [19 of 34] Compiling Utility.Network  ( Utility/Network.hs, 
> dist/setup/Utility/Network.o )
> [20 of 34] Compiling Utility.FreeDesktop ( Utility/FreeDesktop.hs, 
> dist/setup/Utility/FreeDesktop.o )
> [21 of 34] Compiling Assistant.Install.AutoStart ( 
> Assistant/Install/AutoStart.hs, dist/setup/Assistant/Install/AutoStart.o )
> [22 of 34] Compiling Utility.ExternalSHA ( Utility/ExternalSHA.hs, 
> dist/setup/Utility/ExternalSHA.o )
> [23 of 34] Compiling Utility.Directory ( Utility/Directory.hs, 
> dist/setup/Utility/Directory.o )
> [24 of 34] Compiling Build.Version( Build/Version.hs, 
> dist/setup/Build/Version.o )
> [25 of 34] Compiling Utility.Path ( Utility/Path.hs, 
> dist/setup/Utility/Path.o )
> [26 of 34] Compiling Build.TestConfig ( Build/TestConfig.hs, 
> dist/setup/Build/TestConfig.o )
> [27 of 34] Compiling Common   ( Common.hs, dist/setup/Common.o )
> [28 of 34] Compiling Utility.DottedVersion ( Utility/DottedVersion.hs, 
> dist/setup/Utility/DottedVersion.o )
> [29 of 34] Compiling Git.Version  ( Git/Version.hs, 
> dist/setup/Git/Version.o )
> [30 of 34] Co

Bug#844980: undertaker: FTBFS: fixdep: error opening depfile: scripts/kconfig/.zconf.tab.o.d: No such file or directory

[Lucas Nussbaum]

Source: undertaker
Version: 1.6.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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]: Entering directory '/<>'
> make -f scripts/Makefile.build obj=scripts/basic
>   gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c  
> make -f scripts/Makefile.build obj=scripts/kconfig scripts/kconfig/conf
> make -f scripts/Makefile.build obj=scripts/kconfig scripts/kconfig/conf
>   gcc -Wp,-MD,scripts/kconfig/.conf.o.d -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer   -DCURSES_LOC="" -DLOCALE   -c -o 
> scripts/kconfig/conf.o scripts/kconfig/conf.c
> make[4]: Leaving directory '/<>/tailor'
>   gcc -Wp,-MD,scripts/kconfig/.conf.o.d -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer   -DCURSES_LOC="" -DLOCALE   -c -o 
> scripts/kconfig/conf.o scripts/kconfig/conf.c
>   gcc -Wp,-MD,scripts/kconfig/.dumpconf.o.d -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer   -DCURSES_LOC="" -DLOCALE   -c -o 
> scripts/kconfig/dumpconf.o scripts/kconfig/dumpconf.c
>   cat scripts/kconfig/lex.zconf.c_shipped > scripts/kconfig/lex.zconf.c
>   cat scripts/kconfig/zconf.tab.c_shipped > scripts/kconfig/zconf.tab.c
>   cat scripts/kconfig/zconf.hash.c_shipped > scripts/kconfig/zconf.hash.c
>   gcc -Wp,-MD,scripts/kconfig/.dumpconf.o.d -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer   -DCURSES_LOC="" -DLOCALE   -c -o 
> scripts/kconfig/dumpconf.o scripts/kconfig/dumpconf.c
>   gcc -Wp,-MD,scripts/kconfig/.zconf.tab.o.d -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer   -DCURSES_LOC="" -DLOCALE  -Iscripts/kconfig 
> -c -o scripts/kconfig/zconf.tab.o scripts/kconfig/zconf.tab.c
>   gcc -Wp,-MD,scripts/kconfig/.zconf.tab.o.d -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer   -DCURSES_LOC="" -DLOCALE  -Iscripts/kconfig 
> -c -o scripts/kconfig/zconf.tab.o scripts/kconfig/zconf.tab.c
> g++ -Wextra -O2 -std=gnu++11 -I../scripts/kconfig -I../picosat  -c -o bool.o 
> bool.cpp
>   gcc  -o scripts/kconfig/conf scripts/kconfig/conf.o 
> scripts/kconfig/zconf.tab.o  
> fixdep: error opening depfile: scripts/kconfig/.zconf.tab.o.d: No such file 
> or directory
> scripts/Makefile.host:134: recipe for target 'scripts/kconfig/zconf.tab.o' 
> failed
> make[7]: *** [scripts/kconfig/zconf.tab.o] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/undertaker_1.6.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#844974: falcon: FTBFS: error: Could not find suitable distribution for Requirement.parse('keepalive>=0.5')

[Lucas Nussbaum]

Source: falcon
Version: 1.8.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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[5]: Entering directory '/<>/DEXTRACTOR'
> rsync -av dexta undexta /<>/inst/bin
> sending incremental file list
> dexta
> undexta
> 
> sent 133,708 bytes  received 54 bytes  267,524.00 bytes/sec
> total size is 133,512  speedup is 1.00
> make[5]: Leaving directory '/<>/DEXTRACTOR'
> cd /<>/pypeFLOW; python setup.py install --prefix 
> /<>/inst
> running install
> running bdist_egg
> running egg_info
> creating pypeflow.egg-info
> writing requirements to pypeflow.egg-info/requires.txt
> writing pypeflow.egg-info/PKG-INFO
> writing top-level names to pypeflow.egg-info/top_level.txt
> writing dependency_links to pypeflow.egg-info/dependency_links.txt
> writing entry points to pypeflow.egg-info/entry_points.txt
> writing manifest file 'pypeflow.egg-info/SOURCES.txt'
> reading manifest file 'pypeflow.egg-info/SOURCES.txt'
> writing manifest file 'pypeflow.egg-info/SOURCES.txt'
> installing library code to build/bdist.linux-x86_64/egg
> running install_lib
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> creating build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/common.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/task.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/data.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/controller.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/do_task.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/pwatcher_bridge.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/__init__.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/util.py -> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/simple_pwatcher_bridge.py -> 
> build/lib.linux-x86_64-2.7/pypeflow
> copying ./pypeflow/do_support.py -> build/lib.linux-x86_64-2.7/pypeflow
> creating build/lib.linux-x86_64-2.7/pwatcher
> copying ./pwatcher/fs_based.py -> build/lib.linux-x86_64-2.7/pwatcher
> copying ./pwatcher/network_based.py -> build/lib.linux-x86_64-2.7/pwatcher
> copying ./pwatcher/__init__.py -> build/lib.linux-x86_64-2.7/pwatcher
> copying ./pwatcher/blocking.py -> build/lib.linux-x86_64-2.7/pwatcher
> creating build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/pwatcher.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/query_server.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/network_heartbeat.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/__init__.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/pypeflow_example.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/fs_heartbeat.py -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> copying ./pwatcher/mains/job_start.sh -> 
> build/lib.linux-x86_64-2.7/pwatcher/mains
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/egg
> creating build/bdist.linux-x86_64/egg/pwatcher
> copying build/lib.linux-x86_64-2.7/pwatcher/fs_based.py -> 
> build/bdist.linux-x86_64/egg/pwatcher
> creating build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/pwatcher.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/query_server.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/network_heartbeat.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/job_start.sh -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/__init__.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/pypeflow_example.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/mains/fs_heartbeat.py -> 
> build/bdist.linux-x86_64/egg/pwatcher/mains
> copying build/lib.linux-x86_64-2.7/pwatcher/network_based.py -> 
> build/bdist.linux-x86_64/egg/pwatcher
> copying build/lib.linux-x86_64-2.7/pwatcher/__init__.py -> 
> build/bdist.linux-x86_64/egg/pwatcher
> copying build/lib.linux-x86_64-2.7/pwatcher/blocking.py -> 
> build/bdist.linux-x86_64/egg/pwatcher
> creating build/bdist.linux-x86_64/egg/pypeflow
>

Bug#844975: courier: FTBFS: dh_install: missing files, aborting

[Lucas Nussbaum]

Source: courier
Version: 0.76.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> make[3]: Nothing to be done for 'install-perms-local'.
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> cd /<>/courier && ./perms.sh > 
> /<>/debian/tmp/install-perms-list.dat
> install -m 644 debian/init-d-script-courier 
> /<>/debian/tmp/usr/lib/courier/
> for man1 in addcr courier-config; do \
> pod2man --center='Debian GNU/Linux Documentation' --release='Debian 
> GNU/Linux '`cat /etc/debian_version` --section=1 debian/${man1}.pod > 
> /<>/debian/tmp/usr/share/man/man1/${man1}.1; \
> done
> for man8 in sharedindexinstall sharedindexsplit webgpg webmaild; do \
> pod2man --center='Debian GNU/Linux Documentation' --release='Debian 
> GNU/Linux '`cat /etc/debian_version` --section=8 debian/${man8}.pod > 
> /<>/debian/tmp/usr/share/man/man8/${man8}.8; \
> done
> rm -f 
> /<>/debian/tmp/usr/lib/courier/sqwebmail/html/en-us/ISPELLDICT
> rm -f /<>/debian/tmp/usr/lib/courier/perlfilter-example.pl
> rm -f /<>/debian/tmp/etc/courier/quotawarnmsg.example
> perl -i -pe 's%^#!\s?perl%#!/usr/bin/perl%' 
> /<>/debian/tmp/usr/share/courier/webadmin/*.pl
> rm -f /<>/debian/tmp/usr/sbin/showmodules
> for f in /<>/debian/tmp/etc/courier/*.dist; do \
>   mv ${f} ${f%.dist}; \
> done
> rm /<>/debian/tmp/etc/courier/*.authpam
> install -d -m 755 /<>/debian/tmp/etc/pam.d
> install -m 644 debian/common-session.pam 
> /<>/debian/tmp/etc/pam.d/esmtp
> install -m 644 debian/common-session.pam 
> /<>/debian/tmp/etc/pam.d/imap
> install -m 644 debian/common-session.pam 
> /<>/debian/tmp/etc/pam.d/pop3
> install -m 644 debian/common-password.pam 
> /<>/debian/tmp/etc/pam.d/webmail
> install -m 644 debian/common-password.pam 
> /<>/debian/tmp/etc/pam.d/calendar
> chmod 644 /<>/debian/tmp/usr/lib/courier/faxmail/init
> rm -f \
>   /<>/debian/tmp/etc/courier/maildrop \
>   /<>/debian/tmp/usr/bin/mailbot \
>   /<>/debian/tmp/usr/bin/maildrop \
>   /<>/debian/tmp/usr/bin/makemime \
>   /<>/debian/tmp/usr/bin/reformail \
>   /<>/debian/tmp/usr/bin/reformime \
>   /<>/debian/tmp/usr/share/man/man1/mailbot.1 \
>   /<>/debian/tmp/usr/share/man/man1/maildrop.1 \
>   /<>/debian/tmp/usr/share/man/man1/makemime.1 \
>   /<>/debian/tmp/usr/share/man/man1/reformail.1 \
>   /<>/debian/tmp/usr/share/man/man1/reformime.1 \
>   /<>/debian/tmp/usr/share/man/man7/maildropex.7 \
>   /<>/debian/tmp/usr/share/man/man7/maildropfilter.7 \
>   /<>/debian/tmp/usr/share/man/man7/maildropgdbm.7
> dh_install --list-missing
>   install -d debian/courier-base//usr/bin
>   cp --reflink=auto -a debian/tmp/usr/bin/courier-config 
> debian/courier-base//usr/bin/
>   cp --reflink=auto -a 
> ./debian/tmp/dh-exec.w3GWHmPn/usr/bin/deliverquota.courier 
> debian/courier-base/usr/bin//
>   cp --reflink=auto -a debian/tmp/usr/bin/maildiracl 
> debian/courier-base//usr/bin/
>   cp --reflink=auto -a debian/tmp/usr/bin/maildirkw 
> debian/courier-base//usr/bin/
>   cp --reflink=auto -a 
> ./debian/tmp/dh-exec.w3GWHmPn/usr/bin/maildirmake.courier 
> debian/courier-base/usr/bin//
>   cp --reflink=auto -a 
> ./debian/tmp/dh-exec.w3GWHmPn/usr/bin/makedat.courier 
> debian/courier-base/usr/bin//
>   cp --reflink=auto -a debian/tmp/usr/bin/testmxlookup 
> debian/courier-base//usr/bin/
>   install -d debian/courier-base//usr/lib/courier/courier
>   cp --reflink=auto -a debian/tmp/usr/lib/courier/courier/makedatprog 
> debian/courier-base//usr/lib/courier/courier/
>   cp --reflink=auto -a debian/tmp/usr/lib/courier/makedat 
> debian/courier-base//usr/lib/courier/
>   cp --reflink=auto -a debian/tmp/usr/lib/courier/perlfilter-ratelimit.pl 
> debian/courier-base//usr/lib/courier/
>   cp --reflink=auto -a debian/tmp/usr/lib/courier/makeimapaccess 
> debian/courier-base//usr/lib/courier/
>   install -d debian/courier-base//usr/sbin
>   cp --reflink=auto -a debian/tmp/usr/sbin/couriertcpd 
> debian/courier-base//usr/sbin/
>   cp --reflink=auto -a debian/tmp/usr/sbin/makeimapaccess 
> debian/courier-base//usr/sbin/
>   cp --reflink=auto -a debian/tmp/usr/sbin/sharedindexinstall 
> debian/courier-base//usr/sbin/
>   cp --reflink=auto -a debian/tmp/usr/sbin/sharedindexs

Bug#844965: gfal2: FTBFS: dh_install: missing files, aborting

[Lucas Nussbaum]

Source: gfal2
Version: 2.12.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 debian/gfal2-doc/usr/share/doc/gfal2-doc
> mv debian/tmp/usr/share/doc/gfal2/examples \
>debian/tmp/usr/share/doc/gfal2/html \
>debian/gfal2-doc/usr/share/doc/gfal2-doc
> rm -rf debian/tmp/usr/share/doc
> # Replace with a script for multi-arch
> printf '#!/bin/sh\necho ' > debian/tmp/usr/bin/gfal2_version.sh
> LD_LIBRARY_PATH=/<>/debian/tmp/usr/lib/x86_64-linux-gnu:${LD_LIBRARY_PATH}
>  \
>debian/tmp/usr/bin/gfal2_version >> \
>debian/tmp/usr/bin/gfal2_version.sh
> mv debian/tmp/usr/bin/gfal2_version.sh \
>debian/tmp/usr/bin/gfal2_version
> dh_install --fail-missing
> dh_install: Compatibility levels before 9 are deprecated (level 8 in use)
> dh_install: usr/lib/libgtest.a exists in debian/tmp but is not installed to 
> anywhere
> dh_install: usr/lib/libgtest_main.a exists in debian/tmp but is not installed 
> to anywhere
> dh_install: usr/include/gtest/gtest-death-test.h exists in debian/tmp but is 
> not installed to anywhere
> dh_install: usr/include/gtest/gtest.h exists in debian/tmp but is not 
> installed to anywhere
> dh_install: usr/include/gtest/gtest-param-test.h exists in debian/tmp but is 
> not installed to anywhere
> dh_install: usr/include/gtest/gtest-printers.h exists in debian/tmp but is 
> not installed to anywhere
> dh_install: usr/include/gtest/gtest_prod.h exists in debian/tmp but is not 
> installed to anywhere
> dh_install: usr/include/gtest/gtest-message.h exists in debian/tmp but is not 
> installed to anywhere
> dh_install: usr/include/gtest/gtest-param-test.h.pump exists in debian/tmp 
> but is not installed to anywhere
> dh_install: usr/include/gtest/gtest_pred_impl.h exists in debian/tmp but is 
> not installed to anywhere
> dh_install: usr/include/gtest/gtest-spi.h exists in debian/tmp but is not 
> installed to anywhere
> dh_install: usr/include/gtest/gtest-typed-test.h exists in debian/tmp but is 
> not installed to anywhere
> dh_install: usr/include/gtest/gtest-test-part.h exists in debian/tmp but is 
> not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-tuple.h.pump exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-type-util.h exists in debian/tmp 
> but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-param-util-generated.h exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-param-util.h exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-internal.h exists in debian/tmp 
> but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-linked_ptr.h exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-port.h exists in debian/tmp but 
> is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-tuple.h exists in debian/tmp but 
> is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-death-test-internal.h exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-param-util-generated.h.pump 
> exists in debian/tmp but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-filepath.h exists in debian/tmp 
> but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-type-util.h.pump exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-port-arch.h exists in debian/tmp 
> but is not installed to anywhere
> dh_install: usr/include/gtest/internal/gtest-string.h exists in debian/tmp 
> but is not installed to anywhere
> dh_install: usr/include/gtest/internal/custom/gtest.h exists in debian/tmp 
> but is not installed to anywhere
> dh_install: usr/include/gtest/internal/custom/gtest-printers.h exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/include/gtest/internal/custom/gtest-port.h exists in 
> debian/tmp but is not installed to anywhere
> dh_install: missing files, aborting
> debian/rules:26: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/gfal2_2.12.2-2_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#844972: photofloat: FTBFS: Exception in thread "main" java.lang.reflect.InvocationTargetException

[Lucas Nussbaum]

Source: photofloat
Version: 0~20120917+dfsg-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/photofloat-0~20120917+dfsg/web'
> Compiling javascript js/000-jquery-1.7.2.js
> Exception in thread "main" java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at com.yahoo.platform.yui.compressor.Bootstrap.main(Bootstrap.java:21)
> Caused by: java.util.MissingResourceException: Can't find bundle for base 
> name org.mozilla.javascript.resources.Messages, locale en_US
>   at 
> java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1564)
>   at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1387)
>   at java.util.ResourceBundle.getBundle(ResourceBundle.java:845)
>   at 
> org.mozilla.javascript.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:3608)
>   at 
> org.mozilla.javascript.ScriptRuntime.getMessage(ScriptRuntime.java:3592)
>   at 
> org.mozilla.javascript.ScriptRuntime.getMessage0(ScriptRuntime.java:3540)
>   at org.mozilla.javascript.Parser.addError(Parser.java:145)
>   at org.mozilla.javascript.Parser.reportError(Parser.java:160)
>   at org.mozilla.javascript.Parser.memberExprTail(Parser.java:2039)
>   at org.mozilla.javascript.Parser.memberExpr(Parser.java:1977)
>   at org.mozilla.javascript.Parser.unaryExpr(Parser.java:1832)
>   at org.mozilla.javascript.Parser.mulExpr(Parser.java:1761)
>   at org.mozilla.javascript.Parser.addExpr(Parser.java:1742)
>   at org.mozilla.javascript.Parser.shiftExpr(Parser.java:1722)
>   at org.mozilla.javascript.Parser.relExpr(Parser.java:1696)
>   at org.mozilla.javascript.Parser.eqExpr(Parser.java:1652)
>   at org.mozilla.javascript.Parser.bitAndExpr(Parser.java:1641)
>   at org.mozilla.javascript.Parser.bitXorExpr(Parser.java:1630)
>   at org.mozilla.javascript.Parser.bitOrExpr(Parser.java:1619)
>   at org.mozilla.javascript.Parser.andExpr(Parser.java:1607)
>   at org.mozilla.javascript.Parser.orExpr(Parser.java:1595)
>   at org.mozilla.javascript.Parser.condExpr(Parser.java:1578)
>   at org.mozilla.javascript.Parser.assignExpr(Parser.java:1563)
>   at org.mozilla.javascript.Parser.expr(Parser.java:1542)
>   at org.mozilla.javascript.Parser.statementHelper(Parser.java:1221)
>   at org.mozilla.javascript.Parser.statement(Parser.java:726)
>   at org.mozilla.javascript.Parser.parseFunctionBody(Parser.java:482)
>   at org.mozilla.javascript.Parser.function(Parser.java:611)
>   at org.mozilla.javascript.Parser.primaryExpr(Parser.java:2255)
>   at org.mozilla.javascript.Parser.memberExpr(Parser.java:1974)
>   at org.mozilla.javascript.Parser.unaryExpr(Parser.java:1832)
>   at org.mozilla.javascript.Parser.mulExpr(Parser.java:1761)
>   at org.mozilla.javascript.Parser.addExpr(Parser.java:1742)
>   at org.mozilla.javascript.Parser.shiftExpr(Parser.java:1722)
>   at org.mozilla.javascript.Parser.relExpr(Parser.java:1696)
>   at org.mozilla.javascript.Parser.eqExpr(Parser.java:1652)
>   at org.mozilla.javascript.Parser.bitAndExpr(Parser.java:1641)
>   at org.mozilla.javascript.Parser.bitXorExpr(Parser.java:1630)
>   at org.mozilla.javascript.Parser.bitOrExpr(Parser.java:1619)
>   at org.mozilla.javascript.Parser.andExpr(Parser.java:1607)
>   at org.mozilla.javascript.Parser.orExpr(Parser.java:1595)
>   at org.mozilla.javascript.Parser.condExpr(Parser.java:1578)
>   at org.mozilla.javascript.Parser.assignExpr(Parser.java:1563)
>   at org.mozilla.javascript.Parser.assignExpr(Parser.java:1569)
>   at org.mozilla.javascript.Parser.expr(Parser.java:1542)
>   at org.mozilla.javascript.Parser.statementHelper(Parser.java:1221)
>   at org.mozilla.javascript.Parser.statement(Parser.java:726)
>   at org.mozilla.javascript.Parser.parseFunctionBody(Parser.java:482)
>   at org.mozilla.javascript.Parser.function(Parser.java:611)
>   at org.mozilla.javascript.Parser.primaryExpr(Parser.java:2255)
>   at org.mozilla.javascript.Parser.memberExpr(Parser.java:1974)
>   at org.mozilla.javascript.Parser.unaryExpr(Parser.java:1832)
>   at org.mozilla.javascript.Parser.mulE

Bug#844963: gnome-shell-extension-dashtodock: FTBFS: make[1]: git: Command not found

[Lucas Nussbaum]

Source: gnome-shell-extension-dashtodock
Version: 55-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> make[1]: git: Command not found
> rm -fR ./_build
> mkdir -p _build
> cp extension.js stylesheet.css metadata.json COPYING README.md convenience.js 
> dash.js docking.js appIcons.js intellihide.js prefs.js theming.js Settings.ui 
> _build
> mkdir -p _build/media
> cd media ; cp logo.svg ../_build/media/
> mkdir -p _build/schemas
> cp schemas/*.xml _build/schemas/
> cp schemas/gschemas.compiled _build/schemas/
> mkdir -p _build/locale
> for l in po/cs.mo po/hu.mo po/zh_CN.mo po/de.mo po/pt.mo po/ja.mo po/ar.mo 
> po/pl.mo po/it.mo po/ru.mo po/nl.mo po/s...@latin.mo po/sk.mo po/tr.mo 
> po/sr.mo po/es.mo po/sv.mo po/fr.mo po/pt_BR.mo ; do \
>   lf=_build/locale/`basename $l .mo`; \
>   mkdir -p $lf; \
>   mkdir -p $lf/LC_MESSAGES; \
>   cp $l $lf/LC_MESSAGES/dashtodock.mo; \
> done;
> sed -i 's/"version": -1/"version": ""/'  _build/metadata.json;
> rm -rf ~/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com
> mkdir -p ~/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com
> mkdir: cannot create directory '/sbuild-nonexistent': Permission denied
> Makefile:53: recipe for target 'install-local' failed
> make[1]: *** [install-local] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/gnome-shell-extension-dashtodock_55-2_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#844966: ovirt-guest-agent: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: ovirt-guest-agent
Version: 1.0.12.2.dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> /usr/bin/pep8 --exclude="ovirt-guest-agent/setup.py" --filename 
> '*.py,*.py.in' \
>   ovirt-guest-agent/CredServer.py ovirt-guest-agent/GuestAgentLinux2.py 
> ovirt-guest-agent/GuestAgentWin32.py ovirt-guest-agent/LockActiveSession.py 
> ovirt-guest-agent/OVirtAgentLogic.py ovirt-guest-agent/OVirtGuestService.py 
> ovirt-guest-agent/VirtIoChannel.py ovirt-guest-agent/WinFile.py 
> ovirt-guest-agent/ovirt-guest-agent.py ovirt-guest-agent/version.py 
> ovirt-guest-agent/hooks.py tests/*.py
> ovirt-guest-agent/CredServer.py:296:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> ovirt-guest-agent/GuestAgentLinux2.py:39:1: E305 expected 2 blank lines after 
> class or function definition, found 0
> ovirt-guest-agent/GuestAgentLinux2.py:514:1: E305 expected 2 blank lines 
> after class or function definition, found 1
> ovirt-guest-agent/GuestAgentWin32.py:745:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> ovirt-guest-agent/LockActiveSession.py:155:1: E305 expected 2 blank lines 
> after class or function definition, found 1
> ovirt-guest-agent/VirtIoChannel.py:35:1: E305 expected 2 blank lines after 
> class or function definition, found 0
> ovirt-guest-agent/VirtIoChannel.py:231:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> ovirt-guest-agent/ovirt-guest-agent.py:118:1: E305 expected 2 blank lines 
> after class or function definition, found 1
> Makefile:904: recipe for target 'check-local' failed
> make[3]: *** [check-local] Error 1
> make[3]: Leaving directory '/<>'
> Makefile:770: recipe for target 'check-am' failed
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory '/<>'
> Makefile:482: 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://aws-logs.debian.net/2016/11/18/ovirt-guest-agent_1.0.12.2.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#844960: byobu: FTBFS: python syntax error

[Lucas Nussbaum]

Source: byobu
Version: 5.87-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> # Check python syntax
> pep8 --verbose --repeat --ignore W191,E501 usr/lib/byobu/include/config.py 
> usr/lib/byobu/include/select-session.py
> checking usr/lib/byobu/include/config.py
> checking usr/lib/byobu/include/select-session.py
> usr/lib/byobu/include/select-session.py:106:1: E305 expected 2 blank lines 
> after class or function definition, found 1
> debian/rules:6: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/byobu_5.87-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#844957: dballe: FTBFS: g++: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: dballe
Version: 7.19-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>/dballe'
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
>  -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I..  -I/usr/include/postgresql  
> -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -I/usr/include/lua5.1  -Werror   -g 
> -O2 -Wall -c -o libdballe_la-file.lo `test -f 'file.cc' || echo './'`file.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. 
> -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I.. -I/usr/include/postgresql 
> -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -I/usr/include/lua5.1 -Werror -g -O2 
> -Wall -c file.cc  -fPIC -DPIC -o .libs/libdballe_la-file.o
> g++: error: .specs: No such file or directory
> Makefile:1708: recipe for target 'libdballe_la-file.lo' failed
> make[4]: *** [libdballe_la-file.lo] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/dballe_7.19-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#844964: botch: FTBFS: tests failures

[Lucas Nussbaum]

Source: botch
Version: 0.20-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> # FIXME: add more tests
> #./tests.py
> #OCAMLPATH=/<>/dose/_build ocamlbuild -classic-display 
> -use-ocamlfind -cflags "-w +a-4-9-24" tests.native
> #./tests.native
> pyflakes3 tools/*.py
> # E402 is triggered by the sys.path.append() statement in front of import of 
> utils
> # see https://github.com/PyCQA/pep8/issues/264
> pep8 --ignore=E402 tools/*.py
> tools/add-arch.py:29:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/apply-ma-diff.py:53:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/build-order-from-zero.py:55:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> tools/build-order-from-zero.py:214:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> tools/buildgraph2packages.py:42:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/calcportsmetric.py:52:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/check-ma-same-versions.py:45:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> tools/checkfas.py:27:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/convert-arch.py:30:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/dose2html.py:507:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/fasofstats.py:24:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/filter-src-builds-for.py:20:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> tools/fix-cross-problems.py:69:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/graph-ancestors.py:26:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/graph-descendants.py:26:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/graph-difference.py:149:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/graph-neighborhood.py:39:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/graph-shortest-path.py:34:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/graph-sinks.py:24:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/graph-sources.py:24:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/graph-tred.py:20:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/graphml2dot.py:41:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/latest-version.py:26:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/ma-diff.py:63:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/multiarch-interpreter-problem.py:160:1: E305 expected 2 blank lines 
> after class or function definition, found 1
> tools/packages-diff.py:75:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/packages-difference.py:38:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/packages-intersection.py:29:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> tools/packages-union.py:29:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/profile-build-fvs.py:30:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> tools/remove-virtual-disjunctions.py:131:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> tools/stat-html.py:78:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/stat-html.py:665:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/util.py:327:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/util.py:349:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> tools/wanna-build-sortblockers.py:57:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> Makefile:311: recipe for target 'test-python' failed
> make[2]: *** [test-python] Error 1

The full build log is available from:
   http://aws-logs.

Bug#844958: fonts-okolaks: FTBFS: Could not open screen.

[Lucas Nussbaum]

Source: fonts-okolaks
Version: 0.5-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> cp -p okolaks_g.sfd Okolaks.sfd
> fontforge sfd2condensed.ff Okolaks.sfd
> Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
>  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>  with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
>  Based on sources from 20161112-ML-D.
>  Based on source from git with hash: 
> Cannot find your hotkey definition file!
> no xdefs_filename!
> TESTING: getPixmapDir:/usr/share/fontforge/pixmaps
> TESTING: getShareDir:/usr/share/fontforge
> TESTING: GResourceProgramDir:/usr/bin
> trying default theme:/usr/share/fontforge/pixmaps/resources
> Could not open screen.
> debian/rules:9: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/fonts-okolaks_0.5-6_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#844954: libgtk-3-0: segfault when connecting from old X

[Adam Borowski]

Package: libgtk-3-0
Version: 3.22.3-2
Severity: important

Any attempts to run a GTK3 program when connected remotely from old X make
the program segfault on start.  Anything GTK2, xlogo, etc, do work as
normal.  The segfault doesn't seem to be arch-dependant, reproduced it on
amd64 and armhf.

I've tried a bunch of programs, all crash.  Attached backtrace is from 'eom'.


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

Kernel: Linux 4.8.8+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme  3.22.0-1
ii  hicolor-icon-theme  0.15-1
ii  libatk-bridge2.0-0  2.22.0-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-5
ii  libcairo-gobject2   1.14.6-1.1
ii  libcairo2   1.14.6-1.1
ii  libcolord2  1.3.3-2
ii  libcups22.2.1-2
ii  libepoxy0   1.3.1-1
ii  libfontconfig1  2.11.0-6.7
ii  libfreetype62.6.3-3+b1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.2-1
ii  libgtk-3-common 3.22.3-2
ii  libjson-glib-1.0-0  1.2.2-1
ii  libpango-1.0-0  1.40.3-3
ii  libpangocairo-1.0-0 1.40.3-3
ii  libpangoft2-1.0-0   1.40.3-3
ii  librest-0.7-0   0.8.0-2
ii  libsoup2.4-12.56.0-1
ii  libwayland-client0  1.11.0-2
ii  libwayland-cursor0  1.11.0-2
ii  libwayland-egl1-mesa [libwayland-egl1]  12.0.4-2
ii  libx11-62:1.6.3-1
ii  libxcomposite1  1:0.4.4-1
ii  libxcursor1 1:1.1.14-1+b1
ii  libxdamage1 1:1.1.4-2+b1
ii  libxext62:1.3.3-1
ii  libxfixes3  1:5.0.2-1
ii  libxi6  2:1.7.6-1.1
ii  libxinerama12:1.1.3-1+b1
ii  libxkbcommon0   0.6.1-1
ii  libxml2 2.9.4+dfsg1-2.1
ii  libxrandr2  2:1.5.0-1
ii  shared-mime-info1.7-1

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.22.3-2

Versions of packages libgtk-3-0 suggests:
pn  gvfs 
ii  librsvg2-common  2.40.16-1

-- no debconf information
GNU gdb (Debian 7.11.1-2+b1) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from eom...Reading symbols from 
/usr/lib/debug/.build-id/95/865258ef7f9a9be0cfe314b2fbcf6d317b3027.debug...done.
done.
(gdb) run
Starting program: /usr/bin/eom 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
XIFreeDeviceInfo (info=info@entry=0x0) at ../../src/XIQueryDevice.c:118
(gdb) bt full
#0  0x71f735dc in XIFreeDeviceInfo (info=info@entry=0x0)
at ../../src/XIQueryDevice.c:118
ptr = 0x0
#1  0x769d9d1a in gdk_x11_device_manager_xi2_constructed 
(object=0x557da0a0 [GdkX11DeviceManagerXI2]) at 
././gdk/x11/gdkdevicemanager-xi2.c:727
device_manager = 0x557da0a0 [GdkX11DeviceManagerXI2]
display = 0x558050e0 [GdkX11Display]
screen = 
masters = 0x558534c0
slaves = 0x55853520
xdisplay = 
info = 0x0
dev = 
ndevices = -1
i = 
event_mask = 
  {deviceid = 4, mask_len = 0, mask = 0x7fffdc80 "\030"}
mask = "\000"
__func__ = "gdk_x11_device_manager_xi2_constructed"
#2  0x73bca777 in g_object_new_internal 
(class=class@entry=0x55857710, params=params@entry=0x7fffddc0, 

Bug#844951: salt-formula-cinder: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-cinder
Version: 2016.4.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of cinder.ceph_single failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-cinder_2016.4.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#844952: courier-authlib: FTBFS: configure: error: --with-mailuser.

[Lucas Nussbaum]

Source: courier-authlib
Version: 0.66.4-7
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> checking for crypt in -lcrypt... no
> checking for crypt... no
> checking for crypt() prototype... 0
> checking for mail userid... ./configure: line 421: test: use: integer 
> expression expected
> ./configure: line 424: $4: Bad file descriptor
> configure: error: --with-mailuser.
> ./configure: line 310: return: use: numeric argument required
> ./configure: line 320: exit: use: numeric argument required
>   "tail -v -n +0 config.log"

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/courier-authlib_0.66.4-7_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#844950: libdatetime-format-duration-perl: FTBFS: Tests failures

[Lucas Nussbaum]

Source: libdatetime-format-duration-perl
Version: 1.03a-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> t/5_fmt_no_normalise.t (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: No plan found in TAP output
> t/6_parse.t(Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: No plan found in TAP output
> t/7_misc.t (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 7 tests but ran 0.
> t/8_negatives.t(Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: No plan found in TAP output
> Files=9, Tests=2,  1 wallclock secs ( 0.04 usr  0.01 sys +  1.06 cusr  0.07 
> csys =  1.18 CPU)
> Result: FAIL
> Failed 8/9 test programs. 1/2 subtests failed.
> Makefile:817: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libdatetime-format-duration-perl_1.03a-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#844953: mongo-cxx-driver-legacy: FTBFS: Tests failures

[Lucas Nussbaum]

Source: mongo-cxx-driver-legacy
Version: 1.1.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> [   OK ] BSONValidateFast.ErrorBeforeId (0 ms)
> [ RUN  ] BSONValidateFast.ErrorNoId
> [   OK ] BSONValidateFast.ErrorNoId (0 ms)
> [ RUN  ] BSONValidateFast.ErrorIsInId
> [   OK ] BSONValidateFast.ErrorIsInId (0 ms)
> [ RUN  ] BSONValidateFast.NonTopLevelId
> [   OK ] BSONValidateFast.NonTopLevelId (0 ms)
> [ RUN  ] BSONValidateFast.StringHasSomething
> [   OK ] BSONValidateFast.StringHasSomething (0 ms)
> [--] 12 tests from BSONValidateFast (0 ms total)
> 
> [--] Global test environment tear-down
> [==] 16 tests from 2 test cases ran. (768 ms total)
> [  PASSED  ] 16 tests.
> scons: building terminated because of errors.
> debian/rules:40: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/mongo-cxx-driver-legacy_1.1.2-2_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#844944: python-acme: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Lucas Nussbaum]

Source: python-acme
Version: 0.9.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/jws.py -> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/util_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/fields.py -> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/fields_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/dns_resolver.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/messages_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/errors.py -> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/challenges_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/jws_test.py -> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/crypto_util.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/dns_resolver_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/crypto_util_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/util.py -> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/standalone_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/messages.py -> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/challenges.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/client_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/standalone.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/client.py -> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/test_util.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> copying acme/errors_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme
> creating /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/jwk.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/jws.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/util_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/json_util_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/interfaces.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/errors.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/interfaces_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/b64.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/jwa.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/json_util.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/jws_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/util.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/b64_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/jwk_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/errors_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> copying acme/jose/jwa_test.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/jose
> running egg_info
> writing requirements to acme.egg-info/requires.txt
> writing acme.egg-info/PKG-INFO
> writing top-level names to acme.egg-info/top_level.txt
> writing dependency_links to acme.egg-info/dependency_links.txt
> writing entry points to acme.egg-info/entry_points.txt
> reading manifest file 'acme.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'acme.egg-info/SOURCES.txt'
> creating /<>/.pybuild/pythonX.Y_2.7/build/acme/testdata
> copying acme/testdata/README -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/testdata
> copying acme/testdata/cert-100sans.pem -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/testdata
> copying acme/testdata/cert-idnsans.pem -> 
> /<>/.pybuild/pythonX.Y_2.7/build/acme/testdata
> copying acme/testdata/cert-san.pem -> 
> /<>/.pybuild

Bug#844946: cloud-init: FTBFS: Tests failures

[Lucas Nussbaum]

Source: cloud-init
Version: 0.7.8-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> Running:  pep8 cloudinit/ tests/ tools/
> cloudinit/safeyaml.py:26:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> cloudinit/util.py:2029:9: E741 ambiguous variable name 'l'
> cloudinit/sources/DataSourceAltCloud.py:279:1: E305 expected 2 blank lines 
> after class or function definition, found 1
> cloudinit/sources/DataSourceBigstep.py:50:1: E305 expected 2 blank lines 
> after class or function definition, found 1
> cloudinit/sources/DataSourceEc2.py:204:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> cloudinit/sources/DataSourceGCE.py:160:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> cloudinit/config/cc_ca_certs.py:54:34: E741 ambiguous variable name 'l'
> cloudinit/config/cc_growpart.py:300:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> cloudinit/config/cc_resizefs.py:49:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> cloudinit/handlers/upstart_job.py:119:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> tools/hacking.py:159:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> Makefile:39: recipe for target 'pep8' failed
> make[2]: *** [pep8] Error 1
> make[2]: Leaving directory '/<>'
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/cloud-init_0.7.8-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#844945: salt-formula-keystone: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-keystone
Version: 2016.4.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of keystone.cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-keystone_2016.4.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#844949: salt-formula-neutron: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-neutron
Version: 2016.4.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of neutron.control_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-neutron_2016.4.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#844948: salt-formula-heat: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-heat
Version: 2016.4.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of heat.server_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-heat_2016.4.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#844947: salt-formula-glance: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-glance
Version: 2016.4.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of glance.cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-glance_2016.4.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#844933: bitcoin: FTBFS: Tests failures

[Lucas Nussbaum]

Source: bitcoin
Version: 0.13.1-0.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> QWARN  : PaymentServerTests::paymentServerTests() qt.network.ssl: QSslSocket: 
> cannot call unresolved function CRYPTO_set_locking_callback
> QWARN  : PaymentServerTests::paymentServerTests() qt.network.ssl: QSslSocket: 
> cannot call unresolved function SSL_library_init
> QWARN  : PaymentServerTests::paymentServerTests() qt.network.ssl: QSslSocket: 
> cannot call unresolved function SSLv23_client_method
> QWARN  : PaymentServerTests::paymentServerTests() qt.network.ssl: QSslSocket: 
> cannot call unresolved function sk_num
> 
> = Received signal, dumping stack ==
> = End of stack trace ==
> QFATAL : PaymentServerTests::paymentServerTests() Received signal 11
>  Function time: 49ms Total time: 49ms
> FAIL!  : PaymentServerTests::paymentServerTests() Received a fatal error.
>Loc: [Unknown file(0)]
> Totals: 1 passed, 1 failed, 0 skipped, 0 blacklisted, 51ms
> * Finished testing of PaymentServerTests *
> FAIL qt/test/test_bitcoin-qt (exit status: 134)
> 
> debian/rules:50: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/bitcoin_0.13.1-0.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#844930: teem: FTBFS: Tests failures

[Lucas Nussbaum]

Source: teem
Version: 1.12.0~20160122-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> 34/37 Test #23: probePolynomial ..   Passed1.62 sec
> 35/37 Test #34: probeSS_cos10    Passed2.18 sec
> 36/37 Test #24: probeMulti ...   Passed2.40 sec
> 37/37 Test #28: kernall ..   Passed4.68 sec
> 
> 89% tests passed, 4 tests failed out of 37
> 
> Total Test time (real) =   4.72 sec
> 
> The following tests FAILED:
>31 - probeSS_cos01 (Failed)
>35 - probeSS_ctmr02 (Failed)
>36 - probeSS_ctmr04 (Failed)
>37 - probeSS_ctmr10 (Failed)
> Errors while running CTest
> Makefile:130: recipe for target 'test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/teem_1.12.0~20160122-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#844939: git-remote-hg: FTBFS: Tests failures

[Lucas Nussbaum]

Source: git-remote-hg
Version: 0.3-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> # 
> # echo feature > expected &&
> # hg -R hgrepo log --template="{branch}
> # " -r tip > actual &&
> # test_cmp expected actual
> # 
> ok 32 - cloning a removed file works
> ok 33 - cloning a file replaced with a directory
> ok 34 - clone replace directory with a file
> # still have 1 known breakage(s)
> # failed 9 among remaining 33 test(s)
> 1..34
> Makefile:14: recipe for target 'main.t' failed
> make[2]: *** [main.t] Error 1
> make[2]: Leaving directory '/<>/test'
> Makefile:11: recipe for target 'test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/git-remote-hg_0.3-2_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#844936: python-keystonemiddleware: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-keystonemiddleware
Version: 4.9.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File 
> "keystonemiddleware/tests/unit/auth_token/test_auth_token_middleware.py", 
> line 1344, in test_request_no_token_dummy
> [self.examples.SIGNED_TOKEN_SCOPED_HASH])
>   File "keystonemiddleware/auth_token/__init__.py", line 716, in 
> _validate_offline
> verified = self._cms_verify(token_data, inform)
>   File "keystonemiddleware/auth_token/__init__.py", line 768, in _cms_verify
> return verify()
>   File "keystonemiddleware/auth_token/__init__.py", line 765, in verify
> raise ksm_exceptions.InvalidToken(msg)
> keystonemiddleware.auth_token._exceptions.InvalidToken: Token authorization 
> failed
> 
> 
> --
> Ran 347 tests in 13.720s
> 
> FAILED (failures=2, skipped=3)
> debian/rules:26: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/python-keystonemiddleware_4.9.0-2_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#844932: git-buildpackage: FTBFS: Tests failures

[Lucas Nussbaum]

Source: git-buildpackage
Version: 0.8.6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> ./gbp/scripts/import_orig.py:650:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> ./gbp/scripts/import_dscs.py:176:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> ./gbp/scripts/config.py:139:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./gbp/scripts/clone.py:149:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./gbp/scripts/create_remote_repo.py:365:1: E305 expected 2 blank lines after 
> class or function definition, found 1
> ./gbp/scripts/buildpackage.py:798:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> ./gbp/scripts/pull.py:174:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./gbp/scripts/import_dsc.py:435:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./gbp/scripts/dch.py:572:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./gbp/scripts/pq.py:487:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./gbp/scripts/supercommand.py:149:1: E305 expected 2 blank lines after class 
> or function definition, found 1
> ./gbp/deb/format.py:116:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> Makefile:12: recipe for target 'syntax-check' failed
> make[2]: *** [syntax-check] Error 1
> make[2]: Leaving directory '/<>'
> debian/rules:21: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/git-buildpackage_0.8.6_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#844929: apparmor: FTBFS: Tests failures

[Lucas Nussbaum]

Source: apparmor
Version: 2.10.95-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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]: *** [check-TESTS] Error 2
> make[6]: Leaving directory 
> '/<>/libraries/libapparmor.python2.7/swig/python/test'
> Makefile:720: recipe for target 'check-am' failed
> make[5]: *** [check-am] Error 2
> make[5]: Leaving directory 
> '/<>/libraries/libapparmor.python2.7/swig/python/test'
> Makefile:378: recipe for target 'check-recursive' failed
> make[4]: *** [check-recursive] Error 1
> make[4]: Leaving directory 
> '/<>/libraries/libapparmor.python2.7/swig/python'
> Makefile:375: recipe for target 'check-recursive' failed
> make[3]: *** [check-recursive] Error 1
> make[3]: Leaving directory 
> '/<>/libraries/libapparmor.python2.7/swig'
> Makefile:407: recipe for target 'check-recursive' failed
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory '/<>/libraries/libapparmor.python2.7'
> dh_auto_test: make -j1 check VERBOSE=1 PYTHON=/usr/bin/python2.7 returned 
> exit code 2
> debian/rules:58: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/apparmor_2.10.95-6_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#844931: python-dugong: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13

[Lucas Nussbaum]

Source: python-dugong
Version: 3.7+dfsg-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>/python-dugong-3.7+dfsg'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/python-dugong-3.7+dfsg/.pybuild/pythonX.Y_3.5/build/dugong
> copying ./dugong/__init__.py -> 
> /<>/python-dugong-3.7+dfsg/.pybuild/pythonX.Y_3.5/build/dugong
> # Build docs
> python3 setup.py build_sphinx
> running build_sphinx
> creating /<>/python-dugong-3.7+dfsg/doc/doctrees
> creating /<>/python-dugong-3.7+dfsg/doc/html
> Running Sphinx v1.4.8
> loading pickled environment... not yet created
> loading intersphinx inventory from ../debian/python.inv...
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 7 source files that are out of date
> updating environment: 7 added, 0 changed, 0 removed
> reading sources... [ 14%] api
> reading sources... [ 28%] coroutines
> reading sources... [ 42%] index
> reading sources... [ 57%] intro
> reading sources... [ 71%] issues
> reading sources... [ 85%] tutorial
> reading sources... [100%] whatsnew
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 14%] api
> writing output... [ 28%] coroutines
> writing output... [ 42%] index
> writing output... [ 57%] intro
> writing output... [ 71%] issues
> writing output... [ 85%] tutorial
> writing output... [100%] whatsnew
> 
> /<>/python-dugong-3.7+dfsg/rst/api.rst:35: WARNING: py:obj 
> reference target not found: ssl.SSLSocket
> generating indices... genindex
> writing additional pages... search
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en) ... done
> dumping object inventory... done
> build succeeded, 1 warning.
> make[1]: Leaving directory '/<>/python-dugong-3.7+dfsg'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd 
> /<>/python-dugong-3.7+dfsg/.pybuild/pythonX.Y_3.5/build; python3.5 
> -m pytest --installed "/<>/python-dugong-3.7+dfsg/test/"
> = test session starts 
> ==
> platform linux -- Python 3.5.2+, pytest-3.0.3, py-1.4.31, pluggy-0.4.0 -- 
> /usr/bin/python3.5
> cachedir: ../../../test/.cache
> rootdir: /<>/python-dugong-3.7+dfsg/test, inifile: pytest.ini
> plugins: catchlog-1.2.2
> collecting ... collected 118 items
> 
> ../../../test/test_aio.py::test_aio_future PASSED
> ../../../test/test_dugong.py::test_connect_ssl SKIPPED
> ../../../test/test_dugong.py::test_invalid_ssl SKIPPED
> ../../../test/test_dugong.py::test_dns_one PASSED
> ../../../test/test_dugong.py::test_dns_two PASSED
> ../../../test/test_dugong.py::test_http_proxy[plain-None] PASSED
> ../../../test/test_dugong.py::test_http_proxy[plain-8080] PASSED
> ../../../test/test_dugong.py::test_connect_proxy[plain-None] PASSED
> ../../../test/test_dugong.py::test_connect_proxy[plain-8080] PASSED
> ../../../test/test_dugong.py::test_get_pipeline[plain] PASSED
> ../../../test/test_dugong.py::test_ssl_info[plain] PASSED
> ../../../test/test_dugong.py::test_blocking_send[plain] PASSED
> ../../../test/test_dugong.py::test_blocking_read[plain] PASSED
> ../../../test/test_dugong.py::test_discard[plain] PASSED
> ../../../test/test_dugong.py::test_discard_chunked[plain] PASSED
> ../../../test/test_dugong.py::test_read_text[plain] PASSED
> ../../../test/test_dugong.py::test_read_text2[plain] PASSED
> ../../../test/test_dugong.py::test_read_text3[plain] PASSED
> ../../../test/test_dugong.py::test_read_identity[plain] PASSED
> ../../../test/test_dugong.py::test_conn_close_1[plain] PASSED
> ../../../test/test_dugong.py::test_conn_close_2[plain] PASSED
> ../../../test/test_dugong.py::test_conn_close_3[plain] PASSED
> ../../../test/test_dugong.py::test_conn_close_4[plain] PASSED
> ../../../test/test_dugong.py::test_conn_close_5[plain] PASSED
> ../../../test/test_dugong.py::test_exhaust_buffer[plain] PASSED
> ../../../test/test_dugong.py::test_full_buffer[plain] PASSED
> ../../../test/test_dugong.py::test_readinto_identity[plain] PASSED
> ../../../test/test_dugong.py::test_read_chunked[plain] PASSED
> ../../../test/test_dugong.py::test_read_chunked2[plain] PASSED
> ../../../test/test_dugong.py::test_readinto_chunked[plain] PASSED
> ../../../test/test_dugong.py::test_d

Bug#844937: owncloud-client: FTBFS: Tests failures

[Lucas Nussbaum]

Source: owncloud-client
Version: 2.2.4+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>Loc: 
> [/<>/owncloud-client-2.2.4+dfsg/test/testexcludedfiles.cpp(41)]
> PASS   : TestExcludedFiles::cleanupTestCase()
> Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 0ms
> * Finished testing of TestExcludedFiles *
> 
>   Start 36: FolderManTest
> 36/36 Test #36: FolderManTest    Passed0.03 sec
> 
> 97% tests passed, 1 tests failed out of 36
> 
> Total Test time (real) =  12.75 sec
> 
> The following tests FAILED:
>35 - ExcludedFilesTest (Failed)
> Errors while running CTest
> Makefile:152: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/owncloud-client_2.2.4+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#844942: plastimatch: FTBFS: Tests failures

[Lucas Nussbaum]

Source: plastimatch
Version: 1.6.3+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> Start 357: plm-sift-a-check-1
> Start 358: plm-sift-a-check-2
> 425/426 Test #357: plm-sift-a-check-1    Passed0.02 
> sec
> 426/426 Test #358: plm-sift-a-check-2    Passed0.02 
> sec
> 
> 99% tests passed, 4 tests failed out of 426
> 
> Total Test time (real) =   9.85 sec
> 
> The following tests FAILED:
>   421 - vf-invert-trans-1 (Failed)
>   422 - vf-invert-trans-1-stats (Failed)
>   423 - vf-invert-trans-1-check (Failed)
>   426 - wed-c (Failed)
> Errors while running CTest
> Makefile:152: recipe for target 'test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/plastimatch_1.6.3+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#844943: python-bleach: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-bleach
Version: 1.4.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
> loadTestsFromName
> addr.filename, addr.module)
>   File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
> importFromPath
> return self.importFromDir(dir_path, fqname)
>   File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
> importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
>   File "/<>/bleach/__init__.py", line 8, in 
> from html5lib.sanitizer import HTMLSanitizer
> ImportError: No module named sanitizer
> 
> --
> Ran 1 test in 0.018s
> 
> FAILED (errors=1)
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/python-bleach_1.4.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.

Bug#844940: telepathy-logger: FTBFS: configure: error: Your intltool is too old. You need intltool 0.35.0 or later.

[Lucas Nussbaum]

Source: telepathy-logger
Version: 0.8.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> checking for GLIB - version >= 2.0.0... yes (version 2.50.2)
> checking for X... no
> checking whether NLS is requested... yes
> ./configure: line 14069: intltool-update: command not found
> checking for intltool >= 0.35.0...  found
> configure: error: Your intltool is too old.  You need intltool 0.35.0 or 
> later.
>   "tail -v -n +0 config.log"

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/telepathy-logger_0.8.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.

Bug#844928: python-keystoneclient: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-keystoneclient
Version: 1:3.2.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 414, in 
> match
> reraise(*matchee)
>   File "/usr/lib/python2.7/dist-packages/testtools/matchers/_exception.py", 
> line 101, in match
> result = matchee()
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 969, in 
> __call__
> return self._callable_object(*self._args, **self._kwargs)
>   File "keystoneclient/common/cms.py", line 199, in cms_verify
> raise subprocess.CalledProcessError(retcode, 'openssl', output=err)
> subprocess.CalledProcessError: Command 'openssl' returned non-zero exit 
> status 1
> 
> 
> --
> Ran 1626 tests in 7.564s
> 
> FAILED (failures=2, skipped=1)
> debian/rules:36: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/python-keystoneclient_3.2.0-2_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#844938: node-inline-source-map: FTBFS: Tests failures

[Lucas Nussbaum]

Source: node-inline-source-map
Version: 0.6.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> pass: 0
> ok: false
> count: 1
> fail: 1
>   command: /usr/bin/nodejs
>   exitCode: 1
>   timeout: 3
>   arguments:
> - test/source-content.js
>   file: test/source-content.js
>   ...
> 
> 1..2
> # failed 2 of 2 tests
> # time=402.429ms
> debian/rules:11: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/node-inline-source-map_0.6.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#844934: obsub: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2855: ordinal not in range(128)

[Lucas Nussbaum]

Source: obsub
Version: 0.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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
> dh clean --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/pythonX.Y_2.7/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:184: python3.5 setup.py clean 
> Traceback (most recent call last):
>   File "setup.py", line 10, in 
> long_description = open('README.rst').read()
>   File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2855: 
> ordinal not in range(128)
> E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
> python3.5 setup.py clean 
> dh_auto_clean: pybuild --clean --test-nose -i python{version} -p 3.5 returned 
> exit code 13
> debian/rules:6: recipe for target 'clean' failed
> make: *** [clean] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/obsub_0.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.

Bug#844941: mediatomb: FTBFS: configure: error: unable to configure mysql support

[Lucas Nussbaum]

Source: mediatomb
Version: 0.12.1-47-g7ab7616-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> checking mysql cflags... -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer
> checking mysql libs... -L/usr/lib/x86_64-linux-gnu -lmysqlclient -lpthread 
> -lz -lm -lrt -latomic -ldl
> checking mysql.h usability... no
> checking mysql.h presence... no
> checking for mysql.h... no
> configure: error: unable to configure mysql support
>   "tail -v -n +0 config.log"

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/mediatomb_0.12.1-47-g7ab7616-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#844927: yafc: FTBFS: src/syshdr.h:164:9: error: unknown type name 'CPPFunction'

[Lucas Nussbaum]

Source: yafc
Version: 1.3.7-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 -DLOCALEDIR=\"/usr/share/locale\" -DSYSCONFDIR=\"/etc\" -DHAVE_CONFIG_H 
> -I.-I/usr/include/editline -I./src -I./src/ftp -I./src/libmhe -isystem 
> /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o src/main.o src/main.c
> In file included from src/main.c:13:0:
> src/syshdr.h:164:9: error: unknown type name 'CPPFunction'
>  typedef CPPFunction rl_completion_func_t;
>  ^~~
> src/syshdr.h:164:21: error: conflicting types for 'rl_completion_func_t'
>  typedef CPPFunction rl_completion_func_t;
>  ^~~~
> In file included from src/syshdr.h:159:0,
>  from src/main.c:13:
> /usr/include/editline/readline.h:43:16: note: previous declaration of 
> 'rl_completion_func_t' was here
>  typedef char **rl_completion_func_t(const char *, int, int);
> ^~~~
> Makefile:828: recipe for target 'src/main.o' failed
> make[3]: *** [src/main.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/yafc_1.3.7-2_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#844924: pygobject: FTBFS: Tests failures

[Lucas Nussbaum]

Source: pygobject
Version: 3.22.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> if 'generic-c-marshaller' in GObject.features:
> ^
> pygtkcompat/pygtkcompat.py:102:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> _unset = object()
> ^
> Makefile:1202: recipe for target 'check-local' failed
> make[4]: *** [check-local] Error 1
> make[4]: Leaving directory '/<>/build-2.7'
> Makefile:969: recipe for target 'check-am' failed
> make[3]: *** [check-am] Error 2
> make[3]: Leaving directory '/<>/build-2.7'
> Makefile:679: recipe for target 'check-recursive' failed
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory '/<>/build-2.7'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> debian/rules:35: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/pygobject_3.22.0-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#844926: salt-formula-nova: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-nova
Version: 2016.4.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of nova.compute_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-nova_2016.4.2-2_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#844917: golang-github-tideland-golib: FTBFS: Tests failures

[Lucas Nussbaum]

Source: golang-github-tideland-golib
Version: 4.12.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> version_test.go:180: test #4: "v3.2.1" < "v1.2.3"
> version_test.go:180: test #5: "v1.2.3-alpha" < "v1.2.3"
> version_test.go:180: test #6: "v1.2.3-alpha.1" < "v1.2.3-alpha"
> version_test.go:180: test #7: "v1.2.3-alpha.1" < "v1.2.3-alpha.2"
> version_test.go:180: test #8: "v1.2.3-alpha.4711" < "v1.2.3-alpha.471"
> version_test.go:180: test #9: "v1.2.3-alpha.48" < "v1.2.3-alpha.4711"
> version_test.go:180: test #10: "v1.2.3+alpha.1" < "v1.2.3+alpha.2"
> version_test.go:180: test #11: "v1.2.3+alpha.2" < "v1.2.3+alpha.1"
> version_test.go:180: test #12: "v1.2.3-alpha+alpha.2" < "v1.2.3-alpha+alpha.1"
> version_test.go:180: test #13: "v1.2.3-alpha.48+alpha.2" < 
> "v1.2.3-alpha.4711+alpha.1"
> version_test.go:180: test #14: "v1.2.3-alpha.2" < "v1.2.3-alpha.1b"
> --- PASS: TestLess (0.00s)
> PASS
> okgithub.com/tideland/golib/version   0.003s
> dh_auto_test: go test -v -p 1 -short github.com/tideland/golib/audit 
> github.com/tideland/golib/cache github.com/tideland/golib/collections 
> github.com/tideland/golib/errors github.com/tideland/golib/etc 
> github.com/tideland/golib/feed/atom github.com/tideland/golib/feed/rss 
> github.com/tideland/golib/feed/utils github.com/tideland/golib/identifier 
> github.com/tideland/golib/logger github.com/tideland/golib/loop 
> github.com/tideland/golib/mapreduce github.com/tideland/golib/monitoring 
> github.com/tideland/golib/numerics github.com/tideland/golib/redis 
> github.com/tideland/golib/scene github.com/tideland/golib/scroller 
> github.com/tideland/golib/sml github.com/tideland/golib/sort 
> github.com/tideland/golib/stringex github.com/tideland/golib/timex 
> github.com/tideland/golib/version returned exit code 1
> debian/rules:7: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/golang-github-tideland-golib_4.12.0-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#844911: libmime-lite-html-perl: FTBFS: Tests failures

[Lucas Nussbaum]

Source: libmime-lite-html-perl
Version: 1.24-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 '/<>'
> cp HTML.pm blib/lib/MIME/Lite/HTML.pm
> Manifying 1 pod document
> make[1]: Leaving directory '/<>'
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> # recreate ref files
> # ignore non-zero exit code that occurs since no tests are run
> perl -Iblib/lib t/20create_image_part.t 1
> 1..4
> Create /var/tmp/mime-lite-html-tests/ref/img/fleur.eml.cid
> Create /var/tmp/mime-lite-html-tests/ref/img/sommaire.eml.cid
> Create /var/tmp/mime-lite-html-tests/ref/img/fleur.eml.location
> Create /var/tmp/mime-lite-html-tests/ref/img/sommaire.eml.location
> # No tests run!
> debian/rules:4: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libmime-lite-html-perl_1.24-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#844908: rpmlint: FTBFS: Tests failures

[Lucas Nussbaum]

Source: rpmlint
Version: 1.9-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> ./FilesCheck.py:1003:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> ./Config.py:84:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> ./Config.py:98:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> ./Config.py:112:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> ./Config.py:133:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> ./Config.py:143:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> ./AbstractCheck.py:108:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> ./test/test.Pkg.py:33:1: E305 expected 2 blank lines after class or function 
> definition, found 1
> ./test/test.SpecCheck.py:34:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./test/test.SpecCheck2.py:20:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./test/test.SpecCheck3.py:20:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> ./test/test.PamCheck.py:25:1: E305 expected 2 blank lines after class or 
> function definition, found 1
> Makefile:60: recipe for target 'check' failed
> make[2]: *** [check] Error 1
> make[2]: Leaving directory '/<>'
> debian/rules:18: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/rpmlint_1.9-4_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#844923: hg-git: FTBFS: Tests failures

[Lucas Nussbaum]

Source: hg-git
Version: 0.8.5-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> -  +++ b/d/gamma  Mon Jan 01 00:00:13 2007 +
> -  @@ -1,1 +1,2 @@
> -   gamma
> -  +gamma 2
>
>  
>  incoming -r
> 
> Warning: test-incoming.t output changed
> ~.warning: Tested with unexpected mercurial lib: 
> /usr/lib/python2.7/dist-packages/mercurial
>  (expected /usr/bin/mercurial)
> 
> Skipped test-encoding.t: blacklisted
> Warned test-incoming.t: output changed
> # Ran 36 tests, 1 skipped, 1 warned, 0 failed.
> Makefile:13: recipe for target 'tests' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/hg-git_0.8.5-4_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#844912: rdflib: FTBFS: Tests failures

[Lucas Nussbaum]

Source: rdflib
Version: 4.1.2-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> dc:identifier  ;
> dc:issued "2009-06-19"^^xsd:dateTime ;
> dc:type <http://purl.oreilly.com/product-types/BOOK> .
> -
> 
> 
> - >> end captured stdout << --
> 
> --
> Ran 2247 tests in 45.069s
> 
> FAILED (SKIP=78, failures=1)
> Running nose with: --exclude=test_conneg --attr= test rdflib --where=./
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: 
> python2.7 run_tests.py  --exclude=test_conneg
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
> exit code 13
> debian/rules:40: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/rdflib_4.1.2-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#844918: libncursesada: FTBFS: configure: error: No usable Ada compiler found

[Lucas Nussbaum]

Source: libncursesada
Version: 6.0.20150808-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> checking for working mkstemp... yes
> checking for gnatmake... yes
> checking for gnat version... 6.2.0
> checking for m4... yes
> checking if GNAT works... no
> configure: error: No usable Ada compiler found
>   "tail -v -n +0 config.log"

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libncursesada_6.0.20150808-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#844916: salt-formula-horizon: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-horizon
Version: 2016.4.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of horizon.cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-horizon_2016.4.2-2_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#844925: ruby-sidekiq-cron: FTBFS: ERROR: Test "ruby2.3" failed: ArgumentError: argument out of range

[Lucas Nussbaum]

Source: ruby-sidekiq-cron
Version: 0.4.2-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> ArgumentError: argument out of range
> /<>/test/unit/poller_test.rb:83:in `initialize'
> /<>/test/unit/poller_test.rb:83:in `new'
> /<>/test/unit/poller_test.rb:83:in `block (2 levels) in  (required)>'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:799:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:322:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:335:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:135:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:62:in `block in autorun'
> 
> 83 runs, 155 assertions, 0 failures, 4 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -I"lib:test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/unit/job_test.rb" 
> "test/unit/poller_test.rb" "test/unit/web_extesion_test.rb" ]
> 
> Tasks: TOP => test
> (See full trace by running task with --trace)
> + cleanup
> + kill -9 114156
> rake aborted!
> Command failed with status (1): [./debian/start-redis-server.sh ruby2.3 -S 
> ...]
> /<>/debian/ruby-tests.rake:5:in `block in '
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/ruby-sidekiq-cron_0.4.2-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#844913: node-isexe: FTBFS: Tests failures

[Lucas Nussbaum]

Source: node-isexe
Version: 1.1.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> module.js:327
> throw err;
> ^
> 
> Error: Cannot find module 'nyc/bin/nyc.js'
> at Function.Module._resolveFilename (module.js:325:15)
> at Function.require.resolve (internal/module.js:16:19)
> at getNycBin (/usr/lib/nodejs/tap/bin/run.js:10:21)
> at respawnWithCoverage (/usr/lib/nodejs/tap/bin/run.js:409:15)
> at main (/usr/lib/nodejs/tap/bin/run.js:119:5)
> at Object. (/usr/lib/nodejs/tap/bin/run.js:52:1)
> at Module._compile (module.js:409:26)
> at Object.Module._extensions..js (module.js:416:10)
> at Module.load (module.js:343:32)
> at Function.Module._load (module.js:300:12)
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/node-isexe_1.1.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.

Bug#844919: pytest: FTBFS: Tests failures

[Lucas Nussbaum]

Source: pytest
Version: 3.0.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py:23: in 
> from twisted.trial import itrial, util
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> """
> 
> from __future__ import division, absolute_import
> 
> >   import zope.interface as zi
> E   AttributeError: 'module' object has no attribute 'interface'
> 
> /usr/lib/python2.7/dist-packages/twisted/trial/itrial.py:12: AttributeError
> === 3 failed, 1640 passed, 26 skipped, 13 xfailed, 4 error in 71.75 seconds 
> 
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: cd 
> debian/tmp/test-working-directory && python2.7 -m pytest --lsof -rfsxX 
> --ignore=/<>/testing/freeze 
> --ignore=/<>/testing/test_entry_points.py 
> --ignore=/<>/testing/test_pdb.py /<>/testing
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 
> --system=custom --test-args=cd debian/tmp/test-working-directory && 
> {interpreter} -m pytest --lsof -rfsxX --ignore={dir}/testing/freeze 
> --ignore={dir}/testing/test_entry_points.py 
> --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> debian/rules:25: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/pytest_3.0.3-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#844922: node-string-decoder: FTBFS: Tests failures

[Lucas Nussbaum]

Source: node-string-decoder
Version: 0.10.25-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> plan:
>   start: 1
>   end: 0
>   skipAll: true
> failures:
>   - tapError: 'Plan of 1..0, but test points encountered'
>   command: /usr/bin/nodejs
>   arguments:
> - test/simple/test-string-decoder-end.js
>   file: test/simple/test-string-decoder-end.js
>   ...
> 
> 1..1
> # failed 1 of 1 tests
> # time=158.079ms
> debian/rules:11: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/node-string-decoder_0.10.25-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#844909: python-trollius: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-trollius
Version: 2.1~b1-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> data = self.loop.run_until_complete(f)
>   File "/<>/trollius/base_events.py", line 350, in 
> run_until_complete
> return future.result()
>   File "/<>/trollius/futures.py", line 285, in result
> compat.reraise(type(self._exception), self._exception, exc_tb)
>   File "/<>/trollius/tasks.py", line 259, in _step
> result = coro.send(value)
>   File "/<>/trollius/streams.py", line 464, in read
> raise self._exception
> socket.error: [Errno 0] Error
> 
> --
> Ran 905 tests in 9.564s
> 
> FAILED (errors=2, skipped=1)
> debian/rules:24: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/python-trollius_2.1~b1-4_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#844914: rsyslog: FTBFS: Tests failures

[Lucas Nussbaum]

Source: rsyslog
Version: 8.23.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> 
> 
> 
> Test: ./omjournal-basic-no-template.sh
> 
> journalctl command missing, skipping test
> SKIP omjournal-basic-no-template.sh (exit status: 77)
> 
> SKIP: sndrcv_relp_dflt_pt.sh
> 
> 
> ===
> need to be root to run this test - skipping
> SKIP sndrcv_relp_dflt_pt.sh (exit status: 77)
> 
> debian/rules:66: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/rsyslog_8.23.0-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#844910: devscripts: FTBFS: Tests failures

[Lucas Nussbaum]

Source: devscripts
Version: 2.16.8
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> test_dscextractChangelog
> test_debchange
> test_list_unreleased
> test_debuild2
> ASSERT:standard output of debuild --no-conf --no-lintian 
> --preserve-envvar=PATH --preserve-envvar=PERL5LIB 
> --preserve-envvar=DEBFULLNAME --preserve-envvar=DEBEMAIL 
> --preserve-envvar=GNUPGHOME -k'uscan test key (no secret) <n...@debian.org>' 
> matches /<>/test/package_lifecycle/debuild.txt\n expected:<0> 
> but was:<1>
> 20d19
> <  dpkg-genbuildinfo
> test_debdiff
> 
> Ran 8 tests.
> 
> FAILED (failures=2)
> Makefile:16: recipe for target 'test_package_lifecycle.test' failed
> make[2]: *** [test_package_lifecycle.test] Error 1
> make[2]: Leaving directory '/<>/test'
> Makefile:50: recipe for target 'test_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/devscripts_2.16.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#844921: python-django-compressor: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-django-compressor
Version: 2.0-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> omit_optional_tags=False, use_trailing_solidus=True,
>   File "/usr/lib/python2.7/dist-packages/html5lib/serializer.py", line 78, in 
> serialize
> return s.render(walker(input), encoding)
>   File "/usr/lib/python2.7/dist-packages/html5lib/serializer.py", line 323, 
> in render
> return "".join(list(self.serialize(treewalker)))
>   File "/usr/lib/python2.7/dist-packages/html5lib/serializer.py", line 263, 
> in serialize
> raise ValueError("quote_attr_values must be one of: "
> ValueError: quote_attr_values must be one of: 'always', 'spec', or 'legacy'
> 
> --
> Ran 304 tests in 1.635s
> 
> FAILED (errors=22, skipped=10)
> Creating test database for alias 'default'...
> Destroying test database for alias 'default'...
> debian/rules:15: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/python-django-compressor_2.0-4_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#844915: notmuch: FTBFS: Tests failures

[Lucas Nussbaum]

Source: notmuch
Version: 0.23.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>"id": 3
>}
>  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-11-18 23:19:14.65600 
> +
>   +++ T590-thread-breakage.22.output  2016-11-18 23:19:14.65600 
> +
>   @@ -1 +1 @@
>   -0
>   +1
> 
> Notmuch test suite complete.
> 808/814 tests passed.
> 2 broken tests failed as expected.
> 4 tests failed.
> test/Makefile.local:64: recipe for target 'test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/notmuch_0.23.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#844920: salt-formula-kubernetes: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-kubernetes
Version: 2016.8.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of kubernetes.master_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-kubernetes_2016.8.3-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#844901: openssh: FTBFS: configure: error: libedit not found

[Lucas Nussbaum]

Source: openssh
Version: 1:7.3p1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> checking for /proc/pid/fd directory... yes
> checking for libwrap... yes
> checking for pkg-config... /usr/bin/pkg-config
> checking if /usr/bin/pkg-config knows about libedit... yes
> checking for el_init in -ledit... no
> configure: error: libedit not found
>   "tail -v -n +0 config.log"

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/openssh_7.3p1-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#844903: lintian: FTBFS: Tests failures

[Lucas Nussbaum]

Source: lintian
Version: 2.5.49
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   [tests]
> binaries-missing-lfs: architecture mismatch
> changelog-file-strange-date: Missing Depends: dpkg (<< 1.18.2)
> debhelper-compat: Missing Depends: debhelper (<< 9.20151101~)
> debhelper-compat-empty: Missing Depends: debhelper (<< 9.20151101~)
> runtests-arch-i386: architecture mismatch
> shared-libs-non-pic-i386: architecture mismatch
> 
> Failed tests (6)
> tests::binaries-general
> tests::binaries-hardening
> tests::deb-format-udeb-compression
> tests::version-substvars-general
> tests::legacy-binary
> tests::legacy-libbaz
> debian/rules:48: recipe for target 'runtests' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/lintian_2.5.49_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#844907: python-tornado: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-tornado
Version: 4.4.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> 
> --
> Ran 1463 tests in 10.780s
> 
> FAILED (failures=1, errors=7, skipped=57)
> Some tests were skipped because: PEP 380 (yield from) not available,
> PEP 492 (async/await) not available, Prevent internet access during
> build, asyncio module not present, curl client accepts invalid
> headers, localhost does not resolve to ipv6, needs fix, non-windows
> platform, pycares module not present, timing tests unreliable on
> travis, tornado.speedups module not present
> [E 161118 23:29:11 testing:735] FAIL
> [E 161118 23:29:11 runtests:182] logged 17 warnings and 2 errors
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: 
> python2.7 ./tornado/test/runtests.py --verbose
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> debian/rules:14: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/python-tornado_4.4.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.

Bug#844905: node-nan: FTBFS: Tests failures

[Lucas Nussbaum]

Source: node-nan
Version: 2.4.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> # Subtest: wrappedobjectfactory
> 1..4
> ok 1 - type is function
> ok 2 - type is number
> ok 3 - should be equal
> ok 4 - should be equal
> ok 1 - wrappedobjectfactory # time=12.252ms
> 
> 1..1
> # time=38.425ms
> ok 37 - test/js/wrappedobjectfactory-test.js # time=143.746ms
> 
> 1..37
> # failed 1 of 37 tests
> # time=7671.036ms
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/node-nan_2.4.0-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#844902: nuitka: FTBFS: Tests failures

[Lucas Nussbaum]

Source: nuitka
Version: 0.5.23+ds-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> Run './tests/packages/run_all.py search' in '/<>/nuitka-0.5.23+ds'.
> Using concrete python 2.7.12 on x86_64
> Consider output of recursively compiled program: sub_package
> Comparing output of 'sub_package/kitty' using 'python2.7' with flags silent, 
> expect_success, remove_output, module_mode, two_step_execution, 
> ignore_warnings ...
> Running the optimizations tests with options '--debug' with python2.7:
> Run './tests/optimizations/run_all.py search' in 
> '/<>/nuitka-0.5.23+ds'.
> Warning, no 'lxml' module installed, cannot do XML based tests.
> Running the standalone tests with options '--debug' with python2.7:
> Run './tests/standalone/run_all.py search' in 
> '/<>/nuitka-0.5.23+ds'.
> Using concrete python 2.7.12 on x86_64
> Consider output of recursively compiled program: CtypesUsing.py
> Comparing output of 'CtypesUsing.py' using 'python2.7' with flags silent, 
> expect_success, standalone, remove_output, plugin_disable:pylint-warnings, 
> no_site ...
> Should not access '/lib/x86_64-linux-gnu/libutil.so.1'.
> Should not access '/lib/x86_64-linux-gnu/libz.so.1'.
> Should not access '/usr/lib/x86_64-linux-gnu/libffi.so.6'.
> debian/rules:16: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/nuitka_0.5.23+ds-1_unstable.log

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

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

Bug#844904: salt-formula-ceilometer: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-ceilometer
Version: 2016.4.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of ceilometer.agent_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-ceilometer_2016.4.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#844906: salt-formula-swift: FTBFS: Tests failures

[Lucas Nussbaum]

Source: salt-formula-swift
Version: 2016.8.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 
> 
> import salt.crypt
>   File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
> import salt.utils.rsax931
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 
> 
> libcrypto = _init_libcrypto()
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config
> [ERROR] Execution of swift.proxy_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/salt-formula-swift_2016.8.3-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#844900: sra-sdk: FTBFS: libncbi-vdb.so: undefined reference to `mbedtls_x509_crt_parse_file'

[Lucas Nussbaum]

Source: sra-sdk
Version: 2.7.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 -static-libstdc++ -static-libgcc -o 
> /<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/bin/rcexplain.2.7.0
>  -DNDEBUG -m64 -specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro 
> -Wl,-z,now rcexplain.o 
> -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/lib 
> -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/ilib 
> -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu 
> -L/usr/lib/x86_64-linux-gnu -lkapp -ltk-version -lncbi-vdb -Wl,-Bdynamic -ldl 
> -lpthread -Wl,-Bdynamic -lm -lz -lbz2 -lsz
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
> preloaded (cannot open shared object file): ignored.
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_x509_crt_parse_file'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ctr_drbg_seed'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_init'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_strerror'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_set_hostname'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_config_init'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_handshake'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_conf_ca_chain'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_entropy_init'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_x509_crt_init'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ctr_drbg_init'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_free'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_config_free'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_close_notify'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_setup'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_config_defaults'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_conf_authmode'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ctr_drbg_random'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_x509_crt_parse'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ctr_drbg_free'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_set_bio'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_get_verify_result'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_entropy_free'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_read'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_x509_crt_free'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_entropy_func'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_conf_rng'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_ssl_write'
> /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to 
> `mbedtls_x509_crt_verify_info'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/sra-sdk_2.7.0-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#844897: libprelude: FTBFS: PreludeEasy.cxx:2452:75: error: 'SWIG_From_long_SS_long' was not declared in this scope

[Lucas Nussbaum]

Source: libprelude
Version: 1.0.0-11.8
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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++ -c  -I../.. -I../../src/include -I../../src/include 
> -I../../src/libprelude-error -I../../bindings/c++/include -I../../libmissing 
> -I../../libmissing -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
> -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -O2 -g   -DVERSION=\"\" -DXS_VERSION=\"\" -fPIC 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.24/CORE"   PreludeEasy.cxx
> In file included from PreludeEasy.cxx:1643:0:
> ../../config.h:1566:0: warning: "VERSION" redefined
>  #define VERSION "1.0.0"
>  
> :0:0: note: this is the location of the previous definition
> PreludeEasy.cxx: In function 'int IDMEFValue_to_SWIG(const 
> Prelude::IDMEFValue&, SV**)':
> PreludeEasy.cxx:2452:75: error: 'SWIG_From_long_SS_long' was not declared in 
> this scope
>  *ret = SWIG_From_long_SS_long(idmef_value_get_int64(value));
>^
> Makefile:344: recipe for target 'PreludeEasy.o' failed
> make[6]: *** [PreludeEasy.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/libprelude_1.0.0-11.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#844898: cross-toolchain-base-ports: FTBFS: gcc: error: unrecognized command line option '-mno-space-regs'; did you mean '-fno-make-deps'?

[Lucas Nussbaum]

Source: cross-toolchain-base-ports
Version: 6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> powerpc-linux-gnu-gcc-6 -m64 argz-extract.c -c -std=gnu11 -fgnu89-inline  -O2 
> -Wall -Werror -Wundef -Wwrite-strings -fmerge-all-constants -frounding-math 
> -g -pipe -Wstrict-prototypes -Wold-style-definition -mlong-double-128
> -ftls-model=initial-exec-isystem 
> /<>/glibc-2.24/debian/include  -I../include 
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64/string  
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64  
> -I../sysdeps/unix/sysv/linux/powerpc/powerpc64/fpu  
> -I../sysdeps/unix/sysv/linux/powerpc/powerpc64  
> -I../sysdeps/unix/sysv/linux/wordsize-64  
> -I../sysdeps/unix/sysv/linux/powerpc  -I../sysdeps/powerpc/nptl  
> -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux  
> -I../sysdeps/nptl  -I../sysdeps/pthread  -I../sysdeps/gnu  
> -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  -I../sysdeps/unix/powerpc  
> -I../sysdeps/unix  -I../sysdeps/posix  
> -I../sysdeps/powerpc/powerpc64/fpu/multiarch  
> -I../sysdeps/powerpc/powerpc64/fpu  -I../sysdeps/powerpc/powerpc64/multiarch  
> -I../sysdeps/powerpc/powerpc64  -I../sysdeps/wordsize-64  
> -I../sysdeps/powerpc/fpu  -I../sysdeps/powerpc  
> -I../sysdeps/ieee754/ldbl-128ibm  -I../sysdeps/ieee754/ldbl-opt  
> -I../sysdeps/ieee754/dbl-64  -I../sysdeps/ieee754/flt-32  
> -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. -I../libio -I. -nostdinc 
> -isystem 
> /<>/debian/tmp.powerpc/usr/bin/../lib/gcc-cross/powerpc-linux-gnu/6/include
>  -isystem 
> /<>/debian/tmp.powerpc/usr/bin/../lib/gcc-cross/powerpc-linux-gnu/6/include-fixed
>  -isystem /<>/glibc-2.24/debian/include  -D_LIBC_REENTRANT 
> -include /<>/glibc-2.24/build-tree/powerpc-ppc64/libc-modules.h 
> -DMODULE_NAME=libc -include ../include/libc-symbols.h   -o 
> /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-extract.o 
> -MD -MP -MF 
> /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-extract.o.dt 
> -MT /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-extract.o
> powerpc-linux-gnu-gcc-6 -m64 argz-insert.c -c -std=gnu11 -fgnu89-inline  -O2 
> -Wall -Werror -Wundef -Wwrite-strings -fmerge-all-constants -frounding-math 
> -g -pipe -Wstrict-prototypes -Wold-style-definition -mlong-double-128
> -ftls-model=initial-exec-isystem 
> /<>/glibc-2.24/debian/include  -I../include 
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64/string  
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64  
> -I../sysdeps/unix/sysv/linux/powerpc/powerpc64/fpu  
> -I../sysdeps/unix/sysv/linux/powerpc/powerpc64  
> -I../sysdeps/unix/sysv/linux/wordsize-64  
> -I../sysdeps/unix/sysv/linux/powerpc  -I../sysdeps/powerpc/nptl  
> -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux  
> -I../sysdeps/nptl  -I../sysdeps/pthread  -I../sysdeps/gnu  
> -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  -I../sysdeps/unix/powerpc  
> -I../sysdeps/unix  -I../sysdeps/posix  
> -I../sysdeps/powerpc/powerpc64/fpu/multiarch  
> -I../sysdeps/powerpc/powerpc64/fpu  -I../sysdeps/powerpc/powerpc64/multiarch  
> -I../sysdeps/powerpc/powerpc64  -I../sysdeps/wordsize-64  
> -I../sysdeps/powerpc/fpu  -I../sysdeps/powerpc  
> -I../sysdeps/ieee754/ldbl-128ibm  -I../sysdeps/ieee754/ldbl-opt  
> -I../sysdeps/ieee754/dbl-64  -I../sysdeps/ieee754/flt-32  
> -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. -I../libio -I. -nostdinc 
> -isystem 
> /<>/debian/tmp.powerpc/usr/bin/../lib/gcc-cross/powerpc-linux-gnu/6/include
>  -isystem 
> /<>/debian/tmp.powerpc/usr/bin/../lib/gcc-cross/powerpc-linux-gnu/6/include-fixed
>  -isystem /<>/glibc-2.24/debian/include  -D_LIBC_REENTRANT 
> -include /<>/glibc-2.24/build-tree/powerpc-ppc64/libc-modules.h 
> -DMODULE_NAME=libc -include ../include/libc-symbols.h   -o 
> /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-insert.o -MD 
> -MP -MF 
> /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-insert.o.dt 
> -MT /<>/glibc-2.24/build-tree/powerpc-ppc64/string/argz-insert.o
> powerpc-linux-gnu-gcc-6 -m64 argz-stringify.c -c -std=gnu11 -fgnu89-inline  
> -O2 -Wall -Werror -Wundef -Wwrite-strings -fmerge-all-constants 
> -frounding-math -g -pipe -Wstrict-prototypes -Wold-style-definition 
> -mlong-double-128-ftls-model=initial-exec-isystem 
> /<>/glibc-2.24/debian/include  -I../include 
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64/string  
> -I/<>/glibc-2.24/build-tree/powerpc-ppc64  
> -I../sysdeps/unix/sysv/linux/powerpc/powe

Bug#844899: gmysqlcc: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: gmysqlcc
Version: 0.3.0-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -pthread -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/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -pthread -I/usr/include/gtksourceview-2.0 
> -I/usr/include/libxml2 -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/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer   -Wall  -ggdb -MT gmlc_gui_helpers.o 
> -MD -MP -MF .deps/gmlc_gui_helpers.Tpo -c -o gmlc_gui_helpers.o 
> gmlc_gui_helpers.c
> x86_64-linux-gnu-gcc: error: .specs: No such file or directory
> Makefile:450: recipe for target 'gmlc_gui_helpers.o' failed
> make[3]: *** [gmlc_gui_helpers.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/gmysqlcc_0.3.0-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#844895: libapache-mod-musicindex: FTBFS: x86_64-linux-gnu-gcc: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: libapache-mod-musicindex
Version: 1.4.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 x86_64-linux-gnu-gcc 
> -DHAVE_CONFIG_H -I. -I../../src -I.. -I/usr/include/apache2 
> -I/usr/include/apr-1.0 -I/usr/include/mysql -DLINUX -D_REENTRANT 
> -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic 
> -fstrict-aliasing -pipe -g -O2 -fdebug-prefix-map=/build/apache2-2.4.23=. 
> -fstack-protector-strong -Wformat -Werror=format-security   -pthread 
> -I/usr/include  -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -MT mod_musicindex_la-mod_musicindex.lo -MD -MP -MF 
> .deps/mod_musicindex_la-mod_musicindex.Tpo -c -o 
> mod_musicindex_la-mod_musicindex.lo `test -f 'mod_musicindex.c' || echo 
> '../../src/'`mod_musicindex.c
> libtool: compile:  x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../src -I.. 
> -I/usr/include/apache2 -I/usr/include/apr-1.0 -I/usr/include/mysql -DLINUX 
> -D_REENTRANT -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic 
> -fstrict-aliasing -pipe -g -O2 -fdebug-prefix-map=/build/apache2-2.4.23=. 
> -fstack-protector-strong -Wformat -Werror=format-security -pthread 
> -I/usr/include -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -MT mod_musicindex_la-mod_musicindex.lo -MD -MP -MF 
> .deps/mod_musicindex_la-mod_musicindex.Tpo -c ../../src/mod_musicindex.c  
> -fPIC -DPIC -o .libs/mod_musicindex_la-mod_musicindex.o
> x86_64-linux-gnu-gcc: error: .specs: No such file or directory
> Makefile:462: recipe for target 'mod_musicindex_la-mod_musicindex.lo' failed
> make[3]: *** [mod_musicindex_la-mod_musicindex.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libapache-mod-musicindex_1.4.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#844893: lizardfs: FTBFS: ./build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create'

[Lucas Nussbaum]

Source: lizardfs
Version: 3.10.4+dfsg-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /usr/bin/cc  -g -O2 -fdebug-prefix-map=/<>/lizardfs-3.10.4+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  
> CMakeFiles/cmTC_f5a21.dir/CheckSymbolExists.c.o  -o cmTC_f5a21 -rdynamic 
> CMakeFiles/cmTC_f5a21.dir/CheckSymbolExists.c.o: In function `main':
> ./build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to 
> `pthread_create'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/lizardfs_3.10.4+dfsg-2_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#844892: mapserver: FTBFS: ld: final link failed: Nonrepresentable section on output

[Lucas Nussbaum]

Source: mapserver
Version: 7.0.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /usr/bin/ld: CMakeFiles/mapserver.dir/kerneldensity.c.o: relocation 
> R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared 
> object; recompile with -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/mapserver_7.0.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.

Bug#844894: redland: FTBFS: gcc: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: redland
Version: 1.0.17-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2  
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/raptor2 -I/usr/include/rasqal 
> -I/usr/include/raptor2  
> -DREDLAND_MODULE_PATH="\""/usr/local/lib/redland:/usr/lib/x86_64-linux-gnu/redland"\""
>  -DLIBRDF_INTERNAL=1 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> librdf_storage_mysql_la-rdf_storage_mysql.lo `test -f 'rdf_storage_mysql.c' 
> || echo './'`rdf_storage_mysql.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/raptor2 -I/usr/include/rasqal 
> -I/usr/include/raptor2 
> -DREDLAND_MODULE_PATH=\"/usr/local/lib/redland:/usr/lib/x86_64-linux-gnu/redland\"
>  -DLIBRDF_INTERNAL=1 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> rdf_storage_mysql.c  -fPIC -DPIC -o 
> .libs/librdf_storage_mysql_la-rdf_storage_mysql.o
> gcc: error: .specs: No such file or directory
> Makefile:1150: recipe for target 
> 'librdf_storage_mysql_la-rdf_storage_mysql.lo' failed
> make[4]: *** [librdf_storage_mysql_la-rdf_storage_mysql.lo] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/redland_1.0.17-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#844896: gazebo: FTBFS: gtest.cc:1898:10: error: type 'const class testing::internal::scoped_ptr' argument given to 'delete', expected pointer

[Lucas Nussbaum]

Source: gazebo
Version: 7.3.1+dfsg-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /usr/bin/c++  -fPIC -g -O2 
> -fdebug-prefix-map=/<>/gazebo-7.3.1+dfsg=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -Wextra -Wno-long-long -Wno-unused-value -Wno-unused-value -Wno-unused-value 
> -Wno-unused-value -Wfloat-equal -Wshadow -Winit-self -Wswitch-default 
> -Wmissing-include-dirs -pedantic -fvisibility=hidden 
> -fvisibility-inlines-hidden -std=c++11 -DBUILDING_DLL_GIMPACT -mfpmath=sse 
> -msse -msse2 -msse3 -mssse3 -DSSE -Wl,-z,relro -shared 
> -Wl,-soname,libgazebo_gimpact.so.7 -o libgazebo_gimpact.so.7.3.1 
> CMakeFiles/gazebo_gimpact.dir/src/gim_tri_tri_overlap.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_math.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gimpact.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_trimesh_trimesh_collision.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_trimesh_sphere_collision.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_trimesh.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_trimesh_capsule_collision.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_memory.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_contact.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_boxpruning.cpp.o 
> CMakeFiles/gazebo_gimpact.dir/src/gim_trimesh_ray_collision.cpp.o 
> cd /<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu/deps/opende/GIMPACT 
> && /usr/bin/cmake -E cmake_symlink_library libgazebo_gimpact.so.7.3.1 
> libgazebo_gimpact.so.7 libgazebo_gimpact.so
> make[3]: Leaving directory 
> '/<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu'
> [ 10%] Built target gazebo_gimpact
> In file included from 
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest-all.cc:42:0:
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest.cc: In destructor 
> 'virtual testing::Test::~Test()':
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest.cc:1898:10: error: type 
> 'const class 
> testing::internal::scoped_ptr' argument 
> given to 'delete', expected pointer
>delete gtest_flag_saver_;
>   ^
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest.cc: At global scope:
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest.cc:2178:1: error: 
> prototype for 'testing::TestInfo::TestInfo(const string&, const string&, 
> const char*, const char*, testing::internal::TypeId, 
> testing::internal::TestFactoryBase*)' does not match any in class 
> 'testing::TestInfo'
>  TestInfo::TestInfo(const std::string& a_test_case_name,
>  ^~~~
> In file included from /usr/include/gtest/internal/gtest-internal.h:40:0,
>  from /usr/include/gtest/gtest.h:58,
>  from 
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest-all.cc:39:
> /usr/include/gtest/gtest.h:772:3: error: candidates are: 
> testing::TestInfo::TestInfo(const testing::TestInfo&)
>GTEST_DISALLOW_COPY_AND_ASSIGN_(TestInfo);
>^
> In file included from 
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest-all.cc:39:0:
> /usr/include/gtest/gtest.h:728:3: error: 
> testing::TestInfo::TestInfo(const string&, const string&, const char*, const 
> char*, testing::internal::CodeLocation, testing::internal::TypeId, 
> testing::internal::TestFactoryBase*)
>TestInfo(const std::string& test_case_name,
>^~~~
> In file included from 
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest-all.cc:42:0:
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest.cc: In function 
> 'testing::TestInfo* testing::internal::MakeAndRegisterTestInfo(const char*, 
> const char*, const char*, const char*, testing::internal::TypeId, 
> testing::internal::SetUpTestCaseFunc, 
> testing::internal::TearDownTestCaseFunc, 
> testing::internal::TestFactoryBase*)':
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest.cc:2228:45: error: no 
> matching function for call to 'testing::TestInfo::TestInfo(const char*&, 
> const char*&, const char*&, const char*&, const void*&, 
> testing::internal::TestFactoryBase*&)'
> fixture_class_id, factory);
>  ^
> In file included from /usr/include/gtest/internal/gtest-internal.h:40:0,
>  from /usr/include/gtest/gtest.h:58,
>  from 
> /<>/gazebo-7.3.1+dfsg/test/gtest/src/gtest-all.cc:39:
> /usr/include/gtest/gtest.h:772:3: note: candidate: 
> testing::TestInfo::TestInfo(const testing::TestInfo&)
>GTEST_DISALLOW_COPY_AND_ASSIGN_(TestInfo);
>^

Bug#844877: voms: FTBFS: sslutils.c:263:33: error: dereferencing pointer to incomplete type 'X509_NAME {aka struct X509_name_st}'

[Lucas Nussbaum]

Source: voms
Version: 2.0.14-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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../../src/autogen   -Wdate-time -D_FORTIFY_SOURCE=2  -I ../../src/include 
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -MT libssl_utils_nog_la-sslutils.lo -MD -MP 
> -MF .deps/libssl_utils_nog_la-sslutils.Tpo -c -o 
> libssl_utils_nog_la-sslutils.lo `test -f 'sslutils.c' || echo './'`sslutils.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src/autogen -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I ../../src/include -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -MT libssl_utils_nog_la-sslutils.lo -MD -MP -MF 
> .deps/libssl_utils_nog_la-sslutils.Tpo -c sslutils.c  -fPIC -DPIC -o 
> .libs/libssl_utils_nog_la-sslutils.o
> In file included from /usr/include/inttypes.h:25:0,
>  from /usr/include/openssl/e_os2.h:249,
>  from /usr/include/openssl/x509.h:19,
>  from ../../src/include/myproxycertinfo.h:29,
>  from sslutils.c:36:
> /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"
>^~~
> sslutils.c: In function 'X509_NAME_cmp_no_set':
> sslutils.c:263:33: error: dereferencing pointer to incomplete type 'X509_NAME 
> {aka struct X509_name_st}'
>  if (sk_X509_NAME_ENTRY_num(a->entries) !=
>  ^~
> sslutils.c:274:15: error: dereferencing pointer to incomplete type 
> 'X509_NAME_ENTRY {aka struct X509_name_entry_st}'
>  j = na->value->length-nb->value->length;
>^~
> sslutils.c: In function 'ERR_load_prxyerr_strings':
> sslutils.c:517:9: warning: implicit declaration of function 'RAND_egd' 
> [-Wimplicit-function-declaration]
>  RAND_egd(egd_path);
>  ^~~~
> sslutils.c: In function 'proxy_genreq':
> sslutils.c:718:18: error: dereferencing pointer to incomplete type 'EVP_PKEY 
> {aka struct evp_pkey_st}'
>  if (upkey->type != EVP_PKEY_RSA)
>   ^~
> sslutils.c:743:5: warning: 'RSA_generate_key' is deprecated 
> [-Wdeprecated-declarations]
>  if ((rsa = RSA_generate_key(rbits,
>  ^~
> In file included from /usr/include/openssl/rsa.h:13:0,
>  from /usr/include/openssl/x509.h:31,
>  from ../../src/include/myproxycertinfo.h:29,
>  from sslutils.c:36:
> /usr/include/openssl/rsa.h:193:1: note: declared here
>  DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void
>  ^
> In file included from /usr/include/openssl/x509.h:23:0,
>  from ../../src/include/myproxycertinfo.h:29,
>  from sslutils.c:36:
> sslutils.c:804:41: error: dereferencing pointer to incomplete type 'X509_REQ 
> {aka struct X509_req_st}'
>  EVP_MD* md = EVP_get_digestbyobj(req->sig_alg->algorithm);
>  ^
> sslutils.c:808:36: error: dereferencing pointer to incomplete type 'X509 {aka 
> struct x509_st}'
>   md = EVP_get_digestbyobj(ucert->sig_alg->algorithm);
> ^
> sslutils.c:812:24: warning: assignment discards 'const' qualifier from 
> pointer target type [-Wdiscarded-qualifiers]
>  if (md == NULL) md = EVP_sha1();
> ^
> sslutils.c: In function 'proxy_sign':
> sslutils.c:920:36: warning: assignment discards 'const' qualifier from 
> pointer target type [-Wdiscarded-qualifiers]
>  if (sig_algo == NULL) sig_algo = EVP_sha1();
> ^
> sslutils.c:927:19: warning: assignment discards 'const' qualifier from 
> pointer target type [-Wdiscarded-qualifiers]
>cn_sig_algo = EVP_sha1();
>^
> sslutils.c:957:9: warning: passing argument 1 of 'free' discards 'const' 
> qualifier from pointer target type [-Wdiscarded-qualifiers]
> free(newserial);
>  ^
> In file included from /usr/include/openssl/crypto.h:19:0,
>  from /usr/include/openssl/buffer.h:15,
>  from /usr/include/openssl/x509.h:22,
>  from ../../src/include/myproxycertinfo.h:29,
>  from sslutils.c:36:
> /usr/include/stdlib.h:444:13: note: expected 'void *' but argument 

Bug#844888: haproxy: FTBFS: include/types/compression.h:32:18: fatal error: zlib.h: No such file or directory

[Lucas Nussbaum]

Source: haproxy
Version: 1.6.9-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 -Iinclude -Iebtree -Wall -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -DCONFIG_HAP_LINUX_SPLICE -DTPROXY 
> -DCONFIG_HAP_LINUX_TPROXY -DCONFIG_HAP_CRYPT -DUSE_ZLIB  -DENABLE_POLL 
> -DENABLE_EPOLL -DUSE_CPU_AFFINITY -DASSUME_SPLICE_WORKS -DUSE_ACCEPT4 
> -DNETFILTER -DUSE_GETSOCKNAME -DCONFIG_REGPARM=3 -DUSE_OPENSSL  
> -DUSE_SYSCALL_FUTEX -DUSE_LUA -I/usr/include/lua5.3 -DUSE_PCRE  
> -DCONFIG_HAP_NS  -DCONFIG_HAPROXY_VERSION=\"1.6.9-2\" 
> -DCONFIG_HAPROXY_DATE=\"2016/11/18\" \
>   -DBUILD_TARGET='"linux2628"' \
>   -DBUILD_ARCH='""' \
>   -DBUILD_CPU='"generic"' \
>   -DBUILD_CC='"gcc"' \
>   -DBUILD_CFLAGS='"-g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2"' \
>   -DBUILD_OPTIONS='"USE_ZLIB=1 USE_REGPARM=1 USE_OPENSSL=1 USE_LUA=1 
> USE_PCRE=1 USE_NS=1"' \
>-c -o src/haproxy.o src/haproxy.c
> In file included from include/types/stream.h:35:0,
>  from include/proto/log.h:33,
>  from include/common/cfgparse.h:29,
>  from src/haproxy.c:63:
> include/types/compression.h:32:18: fatal error: zlib.h: No such file or 
> directory
>  #include 
>   ^
> compilation terminated.
> Makefile:789: recipe for target 'src/haproxy.o' failed
> make[2]: *** [src/haproxy.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/haproxy_1.6.9-2_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#844889: orafce: FTBFS: libpq-be.h:25:25: fatal error: openssl/ssl.h: No such file or directory

[Lucas Nussbaum]

Source: orafce
Version: 3.3.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
> -Wendif-labels -Wmissing-format-attribute -Wformat-security 
> -fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -g -O2 
> -fdebug-prefix-map=/build/postgresql-9.6-9ZCru8/postgresql-9.6-9.6.1=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -I/usr/include/mit-krb5 -fPIC -pie -fno-omit-frame-pointer -fpic -I. -I./ 
> -I/usr/include/postgresql/9.6/server -I/usr/include/postgresql/internal 
> -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2  
> -I/usr/include/tcl8.6  -c -o putline.o putline.c
> In file included from /usr/include/postgresql/9.6/server/libpq/libpq.h:21:0,
>  from putline.c:12:
> /usr/include/postgresql/9.6/server/libpq/libpq-be.h:25:25: fatal error: 
> openssl/ssl.h: No such file or directory
>  #include 
>  ^
> compilation terminated.
> : recipe for target 'putline.o' failed
> make[2]: *** [putline.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/orafce_3.3.1-2_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#844890: libvcflib: FTBFS: ld: final link failed: Nonrepresentable section on output

[Lucas Nussbaum]

Source: libvcflib
Version: 1.0.0~rc1+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /usr/bin/ld: src/split.o: relocation R_X86_64_32 against 
> `.rodata._Z8tokenizeISt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS6_EEEvRKS6_RT_SA_b.str1.8'
>  can not be used when making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/libvcflib_1.0.0~rc1+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#844882: ocserv: FTBFS: ./ocserv-args.h:1:1: error: unterminated comment

[Lucas Nussbaum]

Source: ocserv
Version: 0.11.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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.. -I./../gl/ -I./../gl/ -I./ -I./../ -I./../  
> -I/usr/include/p11-kit-1 -I./common -I./common   -I/usr/include/liboath 
> -isystem /usr/include/mit-krb5  -I/usr/include/p11-kit-1  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -Wno-strict-aliasing -c -o sup-config/radius.o sup-config/radius.c
> In file included from sup-config/file.c:29:0:
> ./ocserv-args.h:1:1: error: unterminated comment
>  /*   -*- buffer-read-only: t -*- vi: set ro:
>  ^
> worker-vpn.c: In function 'send_stats_to_secmod':
> worker-vpn.c:451:4: warning: ignoring return value of 'read', declared with 
> attribute warn_unused_result [-Wunused-result]
> read(sd, buf, sizeof(buf));
> ^~
> Makefile:1392: recipe for target 'sup-config/file.o' failed
> make[6]: *** [sup-config/file.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/ocserv_0.11.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#844891: urweb: FTBFS: ld: final link failed: Nonrepresentable section on output

[Lucas Nussbaum]

Source: urweb
Version: 20161022+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /usr/bin/ld: 
> /<>/urweb-20161022+dfsg/src/c/.libs/liburweb.a(queue.o): relocation 
> R_X86_64_32 against `.bss' can not be used when making a shared object; 
> recompile with -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/urweb_20161022+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#844873: mclibs: FTBFS: ld: final link failed: Nonrepresentable section on output

[Lucas Nussbaum]

Source: mclibs
Version: 20061220+dfsg3-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libkernlib.a(gshowf.o):
>  relocation R_X86_64_32S against `.rodata.str1.8' can not be used when making 
> a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/mclibs_20061220+dfsg3-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.