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#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#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#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#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#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#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#844784: ITP: d3-format -- Formatting numbers for human consumption

[Ximin Luo]

Package: wnpp
Severity: wishlist
Owner: Ximin Luo 

* Package name: d3-format
  Version : 1.0.2
  Upstream Author : 2010-2015 Mike Bostock 
* URL : https://github.com/d3/d3-format
* License : BSD
  Programming Lang: JS
  Description : Formatting numbers for human consumption

Sometimes JavaScript doesn’t display numbers the way you expect. For example,
printing tenths with a naive simple loop might give you 0, 0.1, 0.2,
0.30004, 0.4, 0.5, 0.6001, 0.7001, 0.8,
0.9 - welcome to binary floating point!

Yet rounding error is not the only reason to customize number formatting. A
table of numbers should be formatted consistently for comparison; above, 0.0
would be better than 0. Large numbers should have grouped digits (e.g.,
42,000) or be in scientific or metric notation (4.2e+4, 42k). Currencies
should have fixed precision ($3.50). Reported numerical results should be
rounded to significant digits (4021 becomes 4000). Number formats should
appropriate to the reader’s locale (42.000,00 or 42,000.00). The list goes on.

Formatting numbers for human consumption is the purpose of d3-format, which is
modeled after Python 3’s format specification mini-language (PEP 3101).

Bug#805116: ITP: wifi-switcher

[Paul Wise]

On Sat, Nov 19, 2016 at 10:18 AM, Oleg SHALAEV wrote:

> but I can not do it because I am not a Debian Developer.
> Is it possible to submit the program to a Debian Developer,
> or I have to register as a  a Debian Developer myself?

Please read this page:

https://mentors.debian.net/intro-maintainers

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#844785: systemd prevents polkit from working properly

[Raphaël Halimi]

Sorry, I forgot to mention that I use sysv init.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#844790: ftp.debian.org has broken HTTPS

[Luke]

Package: ftp.debian.org,security.debian.org
Severity: minor

When navigating to https://ftp.debian.org it fails to load, due to improperly 
configured HTTPS.
Firefox gives - Error code: SEC_ERROR_UNKNOWN_ISSUER

Other subdomains of Debian do not have this problem. Providing HTTPS on this 
domain provides security from MITM attacks among other concerns.

Bug#844789: [Debian-science-sagemath] Bug#844789: gap: Please discard d/p/fix-compressed-six-files patch

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Forum,

as a matter of fact, discarding the patch 
/debian/patches/fix-compressed-six-files
fixes the doctests failures related to gap (and libgap).

I have just uploaded un unpatched version of gap at the deb-sci-sage repository:
please double check !

Thanks,
Jerome



On 19/11/16 04:17, Jerome Benoit wrote:
> Package: gap
> Version: 4r8p3-2
> Severity: important
> Tags: patch
> 
> Dear Maintainer,
> 
>   the Sage[Math] [1] gap interface currently fails to invoke help (? 
> Whatever)
>   when the involved manual.six file is compressed and has the default 
> format:
>   a closer look shows that the very first character is eatean, hence the 
> failure.
>   Removing the patch debian/patches/fix-compressed-six-files fixes the 
> issue,
>   while its seems to not affect GAP itself. Unfortunately, I have not yet
>   figured a simple way not involing Sage[Math] doctests to reproduce the 
> issue.
>   Please consider to discard this patch in order to render Sage[Math] 
> ready
>   before the freeze.
> 
> Thanks in advance,
> Jerome
> 
> [1] https://wiki.debian.org/DebianScience/Sage
> 
> -- System Information:
> Debian Release: Jessie*
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'stable-updates')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages gap depends on:
> ii  gap-core 4r8p3-2
> ii  gap-libs 4r8p3-2
> ii  gap-online-help  4r8p3-2
> 
> Versions of packages gap recommends:
> ii  gap-dev   4r8p3-2
> ii  gap-doc   4r8p3-2
> pn  gap-prim-groups   
> ii  gap-small-groups  4r7p3-1
> ii  gap-trans-groups  4r7p3-1
> 
> Versions of packages gap suggests:
> pn  gap-character-tables
> ii  gap-small-groups-extra  4r7p3-1
> pn  gap-table-of-marks  
> 
> -- no debconf information
> 
> ___
> Debian-science-sagemath mailing list
> debian-science-sagem...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath
> 

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYL+CtAAoJED+SGaZ/NsaLo2Yf/3C6wnYNAqtWTvnkTfE51rox
DUsVoNRaEU+t+pIy6hjnx8pyY4LO/9a5QyJZ85UW7QfVExwmil2pqNgvtJqRq7tp
VOUQv74y4pad205w5PMpLiLT55z7SVnMpNYFf3ASX0/ZXxZLK7Vy+HrNWdHac14f
/G0btTwP/pa02UEA8z/etH1uSIe9KCuunKBd6MDxv5pqSMiHXtTBUqxVAVh8wrZ8
cyCY7jnii4EUUiusML9kqcQqy0m9binxVYhnyuQO+d1gmpdGzgoFi7tJjYvfEWZn
vqx1ZWoaQWZuWDNiG6FozTuVE2gTgNEIKnq39vl4NVZJX0Uk7LkPRKAFyPhtkV16
fD31Hi3KNe5fNA8ygA2HqXhQ90Jo8rhC2Lp1dNijbitdTGNkwGNgks8pOPq+UG8f
EreRXlaA+Ikqn5aaxzb4rPnqWfxtJ1eyy7senD1n4cxLANOWDxF7FOh5ii4k3Pdd
bEdhbroSov7tMtUzObsA0RUYZ6cMCzbAyrw09gKTjh3wGm+8mSxcrcJRW0uGNBJN
RqK3f2nbLEJNeqUMZ5Lp/weN9RgNG2DZDSzGdneo8+stlnaYxhlgRrcGNT96CO32
RrO3XPXZ/AcGJR4DpqAdKO7LYooeYoulubG7xMJk6LjOHzAihp2CSY/fxMNQjVja
nNmGiDXwPI8nVr3QjLPSPn2YQluRpe/vauOmmHFzyDdTxBfwbWDX8h2Zqyjsk/6t
bw+Hhvh8Z1eIM4yff9tC/YUWO0IGdmM0RRdOo+vkG0YJuJhEgzMQIiO0OMsRXBwV
f1wCSWC16lEGKg2KAU8/Z9p0aMAVRx/w9kWoFf4LIkW4I8fJHfPIxATTTiAMOmxT
q9TR+dZiW+Cor4l1a8m9HloySNS2jciMHur3rK+wGelfuteeemYEiYq3njEQ+5q1
mN6d/K332WgAkkvMBj6qoghcHCK8FFsrM1NlqJM1tDrZlamCT2TXMSCigI/kGswy
V8sg7HtQNfiUD2fZ4dA5PD1NHjBeV1qLDlCqNnyvzLbCe5FCgtr+JtoLY962IPmP
7kln3GUZxvXEF6pE6omTGSg6SX621AIb50UV+zrK8G9rXyyHJJl1bR/eWbtbsNUH
Wsu+p9hr4eqFn4ZAm+nEJ/bXoNOlg7axkmNxa5BR3a348DIwgMAr4GK7tjDK6EjE
yLZTrzhLs5Am+a6wdgUxKPGjRRZ6KItIslC2qj+FqEO5qF4flwHxojWuEyUrXnIT
lfwmIwvsR5Flt1JgWN8gLYjUK5MuE0gc3B7ib4CVG1E93Dl8aj9ZSGxSquSrdkxO
LJbbQVLO0aapH/u9Weqc1ynoijoWMoO+lmdmCSJNPkWq+bJkH075mHvj9kfWbnk=
=fK2V
-END PGP SIGNATURE-

Bug#844808: nifti2dicom: FTBFS: build-dependency not installable: libvtk6-qt-dev

[Lucas Nussbaum]

Source: nifti2dicom
Version: 0.4.11-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 7.3.16), cdbs, cmake (>= 2.6.4), 
> qtbase5-dev | libqt4-dev (>= 4.4), libinsighttoolkit4-dev (>= 4.3.0) | 
> libinsighttoolkit3-dev, libfftw3-dev, libtclap-dev (>= 1.2.0), libvtk6-qt-dev 
> | libvtk6-dev (<< 6.2) | libvtk5-qt4-dev
> Filtered Build-Depends: debhelper (>= 7.3.16), cdbs, cmake (>= 2.6.4), 
> qtbase5-dev, libinsighttoolkit4-dev (>= 4.3.0), libfftw3-dev, libtclap-dev 
> (>= 1.2.0), libvtk6-qt-dev
> dpkg-deb: building package 'sbuild-build-depends-nifti2dicom-dummy' in 
> '/<>/resolver-T3mUdd/apt_archive/sbuild-build-depends-nifti2dicom-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-nifti2dicom-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-T3mUdd/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-T3mUdd/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-T3mUdd/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-T3mUdd/apt_archive ./ Sources [457 B]
> Get:5 copy:/<>/resolver-T3mUdd/apt_archive ./ Packages [509 B]
> Fetched 1923 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 nifti2dicom 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-nifti2dicom-dummy : Depends: libvtk6-qt-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/nifti2dicom_0.4.11-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#844793: php7.0: FTBFS: unsatisfiable build-dependencies: apache2-dev

[Lucas Nussbaum]

Source: php7.0
Version: 7.0.12-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: apache2-dev (>= 2.4), autoconf (>= 2.63), automake (>= 
> 1.11) | automake1.11, bison, chrpath, debhelper (>= 9), dh-apache2, 
> dh-systemd (>= 1.3) | base-files (<< 7.2ubuntu5~), dpkg-dev (>= 1.16.1~), 
> firebird-dev | firebird2.5-dev | firebird2.1-dev, flex, freetds-dev, 
> libapparmor-dev, libapr1-dev (>= 1.2.7-8), libbz2-dev, libc-client-dev, 
> libcurl4-openssl-dev | libcurl-dev, libdb-dev, libedit-dev (>= 
> 2.11-20080614-4), libenchant-dev, libevent-dev (>= 1.4.11), libexpat1-dev (>= 
> 1.95.2-2.1), libfreetype6-dev, libgcrypt11-dev, libgd-dev (>= 2.1.0) | 
> libgd2-dev, libglib2.0-dev, libgmp3-dev, libicu-dev, libjpeg-dev | 
> libjpeg62-dev, libkrb5-dev, libldap2-dev, libmagic-dev, libmcrypt-dev, 
> libmhash-dev (>= 0.8.8), libmysqlclient-dev | libmysqlclient15-dev, 
> libnss-myhostname, libonig-dev, libpam0g-dev, libpcre3-dev (>= 8.20), 
> libpng-dev, libpq-dev, libpspell-dev, libqdbm-dev, librecode-dev, 
> libsasl2-dev, libsnmp-dev, libsqlite3-dev, libssl-dev, libsystemd-dev | 
> libsystemd-daemon-dev | base-files (<< 7.2ubuntu5~), libtidy-dev (>= 
> 1:5.2.0), libtool (>= 2.2), libwebp-dev, libwrap0-dev, libxml2-dev, 
> libxmlrpc-epi-dev, libxmltok1-dev, libxslt1-dev (>= 1.0.18), libzip-dev (>= 
> 1.0.0), locales-all | language-pack-de, mysql-server | virtual-mysql-server, 
> netbase, netcat-traditional, re2c, systemtap-sdt-dev, tzdata, unixodbc-dev, 
> zlib1g-dev
> Merged Build-Conflicts: bind-dev, libxmlrpc-core-c3-dev
> Filtered Build-Depends: apache2-dev (>= 2.4), autoconf (>= 2.63), automake 
> (>= 1.11), bison, chrpath, debhelper (>= 9), dh-apache2, dh-systemd (>= 1.3), 
> dpkg-dev (>= 1.16.1~), firebird-dev, flex, freetds-dev, libapparmor-dev, 
> libapr1-dev (>= 1.2.7-8), libbz2-dev, libc-client-dev, libcurl4-openssl-dev, 
> libdb-dev, libedit-dev (>= 2.11-20080614-4), libenchant-dev, libevent-dev (>= 
> 1.4.11), libexpat1-dev (>= 1.95.2-2.1), libfreetype6-dev, libgcrypt11-dev, 
> libgd-dev (>= 2.1.0), libglib2.0-dev, libgmp3-dev, libicu-dev, libjpeg-dev, 
> libkrb5-dev, libldap2-dev, libmagic-dev, libmcrypt-dev, libmhash-dev (>= 
> 0.8.8), libmysqlclient-dev, libnss-myhostname, libonig-dev, libpam0g-dev, 
> libpcre3-dev (>= 8.20), libpng-dev, libpq-dev, libpspell-dev, libqdbm-dev, 
> librecode-dev, libsasl2-dev, libsnmp-dev, libsqlite3-dev, libssl-dev, 
> libsystemd-dev, libtidy-dev (>= 1:5.2.0), libtool (>= 2.2), libwebp-dev, 
> libwrap0-dev, libxml2-dev, libxmlrpc-epi-dev, libxmltok1-dev, libxslt1-dev 
> (>= 1.0.18), libzip-dev (>= 1.0.0), locales-all, mysql-server, netbase, 
> netcat-traditional, re2c, systemtap-sdt-dev, tzdata, unixodbc-dev, zlib1g-dev
> Filtered Build-Conflicts: bind-dev, libxmlrpc-core-c3-dev
> dpkg-deb: building package 'sbuild-build-depends-php7.0-dummy' in 
> '/<>/resolver-AjtobH/apt_archive/sbuild-build-depends-php7.0-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-php7.0-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-AjtobH/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-AjtobH/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-AjtobH/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-AjtobH/apt_archive ./ Sources [981 B]
> Get:5 copy:/<>/resolver-AjtobH/apt_archive ./ Packages [896 B]
> Fetched 2840 B in 0s (260 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install php7.0 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 informati

Bug#844794: zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 0.10.1)

[Lucas Nussbaum]

Source: zaqar
Version: 3.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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 53~), po-debconf, python-all, python-pbr (>= 1.8), 
> python-setuptools, python-sphinx, mongodb, python-autobahn (>= 0.10.1), 
> python-babel (>= 2.3.4), python-coverage, python-ddt (>= 1.0.1), 
> python-enum34, python-falcon, python-fixtures (>= 3.0.0), python-futurist (>= 
> 0.11.0), python-hacking (>= 0.10.0), python-iso8601 (>= 0.1.11), 
> python-jsonschema, python-keystoneclient (>= 1:1.6.0), 
> python-keystonemiddleware (>= 4.0.0), python-memcache (>= 1.56), python-mock 
> (>= 2.0), python-msgpack, python-openstackdocstheme (>= 1.5.0), 
> python-oslo.cache (>= 1.5.0), python-oslo.config (>= 1:3.14.0), 
> python-oslo.context (>= 2.9.0), python-oslo.i18n (>= 2.1.0), python-oslo.log 
> (>= 2.0.0), python-oslo.policy (>= 1.9.0), python-oslo.serialization (>= 
> 2.0.0), python-oslo.utils (>= 3.16.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-pymongo (>= 3.0.2), python-redis, 
> python-requests (>= 2.10.0), python-six (>= 1.9.0), python-sqlalchemy (>= 
> 1.0.10), python-stevedore (>= 1.16.0), python-tempest (>= 1:12.1.0), 
> python-testtools (>= 1.4.0), python-trollius, python-webob, python-websocket, 
> subunit, tempest (>= 1:12.1.0), testrepository
> Filtered Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 53~), po-debconf, python-all, python-pbr (>= 1.8), 
> python-setuptools, python-sphinx, mongodb, python-autobahn (>= 0.10.1), 
> python-babel (>= 2.3.4), python-coverage, python-ddt (>= 1.0.1), 
> python-enum34, python-falcon, python-fixtures (>= 3.0.0), python-futurist (>= 
> 0.11.0), python-hacking (>= 0.10.0), python-iso8601 (>= 0.1.11), 
> python-jsonschema, python-keystoneclient (>= 1:1.6.0), 
> python-keystonemiddleware (>= 4.0.0), python-memcache (>= 1.56), python-mock 
> (>= 2.0), python-msgpack, python-openstackdocstheme (>= 1.5.0), 
> python-oslo.cache (>= 1.5.0), python-oslo.config (>= 1:3.14.0), 
> python-oslo.context (>= 2.9.0), python-oslo.i18n (>= 2.1.0), python-oslo.log 
> (>= 2.0.0), python-oslo.policy (>= 1.9.0), python-oslo.serialization (>= 
> 2.0.0), python-oslo.utils (>= 3.16.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-pymongo (>= 3.0.2), python-redis, 
> python-requests (>= 2.10.0), python-six (>= 1.9.0), python-sqlalchemy (>= 
> 1.0.10), python-stevedore (>= 1.16.0), python-tempest (>= 1:12.1.0), 
> python-testtools (>= 1.4.0), python-trollius, python-webob, python-websocket, 
> subunit, tempest (>= 1:12.1.0), testrepository
> dpkg-deb: building package 'sbuild-build-depends-zaqar-dummy' in 
> '/<>/resolver-01x08j/apt_archive/sbuild-build-depends-zaqar-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-zaqar-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-01x08j/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-01x08j/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-01x08j/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-01x08j/apt_archive ./ Sources [771 B]
> Get:5 copy:/<>/resolver-01x08j/apt_archive ./ Packages [853 B]
> Fetched 2587 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 zaqar 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:
> 
> Th

Bug#844792: python-django-debug-toolbar: FTBFS: unsatisfiable build-dependencies: python-sqlparse (< 0.2.0), python3-sqlparse (< 0.2.0)

[Lucas Nussbaum]

Source: python-django-debug-toolbar
Version: 1:1.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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, python3-all, 
> python-django, python3-django, python-setuptools, python3-setuptools, 
> python-sphinx (>= 1.0.7+dfsg-1~), python-sqlparse (<< 0.2.0), 
> python3-sqlparse (<< 0.2.0)
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, python3-all, 
> python-django, python3-django, python-setuptools, python3-setuptools, 
> python-sphinx (>= 1.0.7+dfsg-1~), python-sqlparse (<< 0.2.0), 
> python3-sqlparse (<< 0.2.0)
> dpkg-deb: building package 
> 'sbuild-build-depends-python-django-debug-toolbar-dummy' in 
> '/<>/resolver-7Z5M46/apt_archive/sbuild-build-depends-python-django-debug-toolbar-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-python-django-debug-toolbar-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-7Z5M46/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-7Z5M46/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-7Z5M46/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-7Z5M46/apt_archive ./ Sources [430 B]
> Get:5 copy:/<>/resolver-7Z5M46/apt_archive ./ Packages [523 B]
> Fetched 1910 B in 0s (171 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install python-django-debug-toolbar 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-python-django-debug-toolbar-dummy : Depends: 
> python-sqlparse (< 0.2.0) but it is not going to be installed
>   Depends: 
> python3-sqlparse (< 0.2.0) 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/python-django-debug-toolbar_1.5-1_unstable.log

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

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

Bug#844799: libapache2-mod-auth-cas: FTBFS: build-dependency not installable: libssl-dev

[Lucas Nussbaum]

Source: libapache2-mod-auth-cas
Version: 1.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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-apache2, apache2-dev, libssl-dev, 
> libcurl4-openssl-dev, libpcre3-dev, dpkg-dev (>= 1.16.1)
> Filtered Build-Depends: debhelper (>= 9), dh-apache2, apache2-dev, 
> libssl-dev, libcurl4-openssl-dev, libpcre3-dev, dpkg-dev (>= 1.16.1)
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-cas-dummy' in 
> '/<>/resolver-isX7Bp/apt_archive/sbuild-build-depends-libapache2-mod-auth-cas-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-cas-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-isX7Bp/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-isX7Bp/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-isX7Bp/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-isX7Bp/apt_archive ./ Sources [401 B]
> Get:5 copy:/<>/resolver-isX7Bp/apt_archive ./ Packages [492 B]
> Fetched 1850 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 libapache2-mod-auth-cas 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-libapache2-mod-auth-cas-dummy : Depends: libssl-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/libapache2-mod-auth-cas_1.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#844806: libapache2-mod-auth-pubtkt: FTBFS: build-dependency not installable: libssl-dev

[Lucas Nussbaum]

Source: libapache2-mod-auth-pubtkt
Version: 0.9-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-apache2, apache2-dev, libssl-dev
> Filtered Build-Depends: debhelper (>= 9), dh-apache2, apache2-dev, libssl-dev
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-pubtkt-dummy' in 
> '/<>/resolver-l76WNi/apt_archive/sbuild-build-depends-libapache2-mod-auth-pubtkt-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-pubtkt-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-l76WNi/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-l76WNi/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-l76WNi/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-l76WNi/apt_archive ./ Sources [377 B]
> Get:5 copy:/<>/resolver-l76WNi/apt_archive ./ Packages [466 B]
> Fetched 1800 B in 0s (178 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libapache2-mod-auth-pubtkt 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-libapache2-mod-auth-pubtkt-dummy : Depends: libssl-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/libapache2-mod-auth-pubtkt_0.9-1_unstable.log

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

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

Bug#844805: networking-ovn: FTBFS: unsatisfiable build-dependencies: python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0)

[Lucas Nussbaum]

Source: networking-ovn
Version: 1.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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, openstack-pkg-tools, 
> python-all, python-pbr, python-setuptools, python-sphinx, python-babel (>= 
> 2.3.4), python-coverage (>= 3.6), python-hacking, python-netaddr (>= 0.7.13), 
> python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0), python-os-testr 
> (>= 0.7.0), python-oslo.config (>= 1:3.14.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-openvswitch (>= 2.5.0), python-reno, 
> python-retrying (>= 1.2.3), python-six (>= 1.9.0), python-testresources (>= 
> 0.2.4), python-testscenarios (>= 0.4), python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), subunit (>= 0.0.18), testrepository (>= 0.0.18)
> Filtered Build-Depends: debhelper (>= 9), dh-python, openstack-pkg-tools, 
> python-all, python-pbr, python-setuptools, python-sphinx, python-babel (>= 
> 2.3.4), python-coverage (>= 3.6), python-hacking, python-netaddr (>= 0.7.13), 
> python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0), python-os-testr 
> (>= 0.7.0), python-oslo.config (>= 1:3.14.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-openvswitch (>= 2.5.0), python-reno, 
> python-retrying (>= 1.2.3), python-six (>= 1.9.0), python-testresources (>= 
> 0.2.4), python-testscenarios (>= 0.4), python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), subunit (>= 0.0.18), testrepository (>= 0.0.18)
> dpkg-deb: building package 'sbuild-build-depends-networking-ovn-dummy' in 
> '/<>/resolver-bmfO3a/apt_archive/sbuild-build-depends-networking-ovn-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-networking-ovn-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-bmfO3a/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-bmfO3a/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-bmfO3a/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-bmfO3a/apt_archive ./ Sources [591 B]
> Get:5 copy:/<>/resolver-bmfO3a/apt_archive ./ Packages [675 B]
> Fetched 2229 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 networking-ovn 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-networking-ovn-dummy : Depends: python-neutron (>= 
> 2:9.0.0) but it is not going to be installed
>  Depends: python-neutron-lib (>= 
> 0.4.0) 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/networking-ovn_1.0.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#844801: libapache2-mod-qos: FTBFS: build-dependency not installable: libssl-dev (>= 0.9.8g)

[Lucas Nussbaum]

Source: libapache2-mod-qos
Version: 11.32-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libssl-dev (>= 0.9.8g), libapr1-dev, 
> libaprutil1-dev, libpcre3-dev, libpng-dev, dh-apache2, apache2-dev (>= 
> 2.4.2-1~), dh-autoreconf
> Filtered Build-Depends: debhelper (>= 9), libssl-dev (>= 0.9.8g), 
> libapr1-dev, libaprutil1-dev, libpcre3-dev, libpng-dev, dh-apache2, 
> apache2-dev (>= 2.4.2-1~), dh-autoreconf
> dpkg-deb: building package 'sbuild-build-depends-libapache2-mod-qos-dummy' in 
> '/<>/resolver-LFPx3e/apt_archive/sbuild-build-depends-libapache2-mod-qos-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-libapache2-mod-qos-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-LFPx3e/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-LFPx3e/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-LFPx3e/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-LFPx3e/apt_archive ./ Sources [413 B]
> Get:5 copy:/<>/resolver-LFPx3e/apt_archive ./ Packages [505 B]
> Fetched 1875 B in 0s (167 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libapache2-mod-qos 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-libapache2-mod-qos-dummy : Depends: libssl-dev (>= 
> 0.9.8g) 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/libapache2-mod-qos_11.32-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#844803: libapache2-mod-auth-openidc: FTBFS: build-dependency not installable: libssl-dev

[Lucas Nussbaum]

Source: libapache2-mod-auth-openidc
Version: 1.8.10.1-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 8.0.0), autotools-dev, apache2-dev, 
> libssl-dev, libcurl4-openssl-dev, libjansson-dev, libhiredis-dev, 
> libpcre3-dev, pkg-config
> Filtered Build-Depends: debhelper (>= 8.0.0), autotools-dev, apache2-dev, 
> libssl-dev, libcurl4-openssl-dev, libjansson-dev, libhiredis-dev, 
> libpcre3-dev, pkg-config
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-openidc-dummy' in 
> '/<>/resolver-2tYMjU/apt_archive/sbuild-build-depends-libapache2-mod-auth-openidc-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-openidc-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-2tYMjU/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-2tYMjU/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-2tYMjU/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-2tYMjU/apt_archive ./ Sources [411 B]
> Get:5 copy:/<>/resolver-2tYMjU/apt_archive ./ Packages [500 B]
> Fetched 1868 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 libapache2-mod-auth-openidc 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-libapache2-mod-auth-openidc-dummy : Depends: libssl-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/libapache2-mod-auth-openidc_1.8.10.1-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#844804: zabbix: FTBFS: build-dependency not installable: libsnmp-dev

[Lucas Nussbaum]

Source: zabbix
Version: 1:3.0.5+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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), automake, dh-autoreconf, dh-systemd 
> (>= 1.5), dh-linktree, apache2-dev, libcurl4-gnutls-dev, libgnutls28-dev | 
> gnutls-dev, libiksemel-dev, libldap2-dev, default-libmysqlclient-dev, 
> libopenipmi-dev, libpq-dev, libsnmp-dev, libsqlite3-dev, libssh2-1-dev, 
> libxml2-dev, pkg-config, unixodbc-dev, libjs-prototype, libjs-jquery-ui (>= 
> 1.10.1), libjs-jquery (>= 1.10.1), javahelper, default-jdk, 
> libandroid-json-java, liblogback-java, libslf4j-java, junit4, gettext
> Filtered Build-Depends: debhelper (>= 9), automake, dh-autoreconf, dh-systemd 
> (>= 1.5), dh-linktree, apache2-dev, libcurl4-gnutls-dev, libgnutls28-dev, 
> libiksemel-dev, libldap2-dev, default-libmysqlclient-dev, libopenipmi-dev, 
> libpq-dev, libsnmp-dev, libsqlite3-dev, libssh2-1-dev, libxml2-dev, 
> pkg-config, unixodbc-dev, libjs-prototype, libjs-jquery-ui (>= 1.10.1), 
> libjs-jquery (>= 1.10.1), javahelper, default-jdk, libandroid-json-java, 
> liblogback-java, libslf4j-java, junit4, gettext
> dpkg-deb: building package 'sbuild-build-depends-zabbix-dummy' in 
> '/<>/resolver-J5z8jL/apt_archive/sbuild-build-depends-zabbix-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-zabbix-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-J5z8jL/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-J5z8jL/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-J5z8jL/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-J5z8jL/apt_archive ./ Sources [589 B]
> Get:5 copy:/<>/resolver-J5z8jL/apt_archive ./ Packages [643 B]
> Fetched 2195 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 zabbix 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-zabbix-dummy : Depends: libsnmp-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/zabbix_3.0.5+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#844798: epigrass: FTBFS: build-dependency not installable: python-sqlsoup

[Lucas Nussbaum]

Source: epigrass
Version: 2.4.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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python, python-setuptools, 
> python-virtualenv, python-sqlsoup, python-redis
> Filtered Build-Depends: debhelper (>= 9), dh-python, python, 
> python-setuptools, python-virtualenv, python-sqlsoup, python-redis
> dpkg-deb: building package 'sbuild-build-depends-epigrass-dummy' in 
> '/<>/resolver-I2SGBK/apt_archive/sbuild-build-depends-epigrass-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-epigrass-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-I2SGBK/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-I2SGBK/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-I2SGBK/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-I2SGBK/apt_archive ./ Sources [383 B]
> Get:5 copy:/<>/resolver-I2SGBK/apt_archive ./ Packages [474 B]
> Fetched 1814 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 epigrass 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-epigrass-dummy : Depends: python-sqlsoup 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/epigrass_2.4.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#844795: datanommer.consumer: FTBFS: build-dependency not installable: python-datanommer.models

[Lucas Nussbaum]

Source: datanommer.consumer
Version: 0.6.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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-datanommer.models, python-fedmsg, python-mock, python-nose, 
> python-setuptools
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-datanommer.models, python-fedmsg, python-mock, python-nose, 
> python-setuptools
> dpkg-deb: building package 'sbuild-build-depends-datanommer.consumer-dummy' 
> in 
> '/<>/resolver-MChyJR/apt_archive/sbuild-build-depends-datanommer.consumer-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-datanommer.consumer-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-MChyJR/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-MChyJR/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-MChyJR/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-MChyJR/apt_archive ./ Sources [396 B]
> Get:5 copy:/<>/resolver-MChyJR/apt_archive ./ Packages [485 B]
> Fetched 1838 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 datanommer.consumer 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-datanommer.consumer-dummy : Depends: 
> python-datanommer.models 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/datanommer.consumer_0.6.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#844802: shibboleth-resolver: FTBFS: unsatisfiable build-dependencies: libshibsp-dev (>= 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxmltooling-dev (>= 1.4)

[Lucas Nussbaum]

Source: shibboleth-resolver
Version: 1.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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libshibsp-dev (>= 
> 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxerces-c-dev, 
> libxmltooling-dev (>= 1.4), libkrb5-dev (>= 1.9), liblog4shib-dev, 
> libboost-dev
> Filtered Build-Depends: debhelper (>= 9), libshibsp-dev (>= 
> 2.5+dfsg~moonshot1), libsaml2-dev (>= 2.4), libxerces-c-dev, 
> libxmltooling-dev (>= 1.4), libkrb5-dev (>= 1.9), liblog4shib-dev, 
> libboost-dev
> dpkg-deb: building package 'sbuild-build-depends-shibboleth-resolver-dummy' 
> in 
> '/<>/resolver-VkSYYK/apt_archive/sbuild-build-depends-shibboleth-resolver-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-shibboleth-resolver-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-VkSYYK/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-VkSYYK/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-VkSYYK/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-VkSYYK/apt_archive ./ Sources [426 B]
> Get:5 copy:/<>/resolver-VkSYYK/apt_archive ./ Packages [515 B]
> Fetched 1898 B in 0s (177 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install shibboleth-resolver 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-shibboleth-resolver-dummy : Depends: libshibsp-dev (>= 
> 2.5+dfsg~moonshot1) but it is not going to be installed
>   Depends: libsaml2-dev (>= 
> 2.4) but it is not going to be installed
>   Depends: libxmltooling-dev 
> (>= 1.4) 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/shibboleth-resolver_1.0.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#844807: ceph: FTBFS: ld: cannot find -lncurses

[Lucas Nussbaum]

Source: ceph
Version: 0.80.11-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=CXX   --mode=link g++ -I/usr/include/nss 
> -I/usr/include/nspr  -Wall -Wtype-limits -Wignored-qualifiers -Winit-self 
> -Wpointer-arith -Werror=format-security -fno-strict-aliasing -fsigned-char 
> -rdynamic -ftemplate-depth-1024 -Wnon-virtual-dtor -Wno-invalid-offsetof   
> -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc 
> -fno-builtin-free -Wstrict-null-sentinel -std=gnu++98 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wl,--as-needed -latomic_ops -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -o libclient_fuse.la  client/fuse_ll.lo libclient.la -lfuse 
> -lboost_thread -lboost_system 
> libtool: link: (cd .libs/libclient_fuse.lax/libclient.a && ar x 
> "/<>/src/./.libs/libclient.a")
> libtool: link: /usr/bin/nm -B  .libs/libcephfs.o   ./.libs/libclient.a 
> ./.libs/libcommon.a | sed -n -e 's/^.*[ 
> ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
> ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' | /bin/sed 
> 's/.* //' | sort | uniq > .libs/libcephfs.exp
> libtool: link: ar cru .libs/libclient_fuse.a client/.libs/fuse_ll.o   
> .libs/libclient_fuse.lax/libclient.a/Client.o 
> .libs/libclient_fuse.lax/libclient.a/ClientSnapRealm.o 
> .libs/libclient_fuse.lax/libclient.a/Dentry.o 
> .libs/libclient_fuse.lax/libclient.a/Filer.o 
> .libs/libclient_fuse.lax/libclient.a/Inode.o 
> .libs/libclient_fuse.lax/libclient.a/Journaler.o 
> .libs/libclient_fuse.lax/libclient.a/MetaRequest.o 
> .libs/libclient_fuse.lax/libclient.a/MetaSession.o 
> .libs/libclient_fuse.lax/libclient.a/ObjectCacher.o 
> .libs/libclient_fuse.lax/libclient.a/Objecter.o 
> .libs/libclient_fuse.lax/libclient.a/Striper.o 
> .libs/libclient_fuse.lax/libclient.a/Trace.o 
> ar: `u' modifier ignored since `D' is the default (see `U')
> libtool: link: /bin/grep -E -e "^ceph_.*" ".libs/libcephfs.exp" > 
> ".libs/libcephfs.expT"
> libtool: link: mv -f ".libs/libcephfs.expT" ".libs/libcephfs.exp"
> libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/6/crtbeginS.o  .libs/libcephfs.o  
> -Wl,--whole-archive ./.libs/libclient.a ./.libs/libcommon.a 
> -Wl,--no-whole-archive  /usr/lib/x86_64-linux-gnu/libatomic_ops.a 
> -Wl,--as-needed -ledit -lncurses -lbsd -ldl -lpthread -lnss3 -lnssutil3 
> -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 -luuid -lrt -lboost_thread 
> -lboost_system -L/usr/lib/gcc/x86_64-linux-gnu/6 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib -L/lib/x86_64-linux-gnu 
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/x86_64-linux-gnu/6/../../.. -lstdc++ -lm -lc -lgcc_s 
> /usr/lib/gcc/x86_64-linux-gnu/6/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crtn.o  -g -O2 
> -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now   -Wl,-soname 
> -Wl,libcephfs.so.1 -Wl,-retain-symbols-file -Wl,.libs/libcephfs.exp -o 
> .libs/libcephfs.so.1.0.0
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/ceph_0.80.11-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#844800: alljoyn-core-1509: FTBFS: common/crypto/openssl/CryptoAES.cc:286:92: error: 'AES_ctr128_encrypt' was not declared in this scope

[Lucas Nussbaum]

Source: alljoyn-core-1509
Version: 15.09a-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):
> g++ -o build/linux/x86_64/release/obj/common/crypto/CryptoAES.o -c -std=c++11 
> -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
> -fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
> -fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
> -Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC -DNDEBUG -DROUTER 
> -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
> -Ibuild/linux/x86_64/release/dist/cpp/inc 
> -Ibuild/linux/x86_64/release/dist/c/inc 
> -Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
> -Icommon/crypto -Ibuild/linux/x86_64/release/dist/cpp/inc 
> common/crypto/openssl/CryptoAES.cc
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Encrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:286:92: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(T.data, U.data, 16, >key, ivec.data, 
> ecount_buf.data, );
>   
>   ^
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Decrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:339:104: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(U.data, T.data, sizeof(T.data), >key, 
> ivec.data, ecount_buf.data, );
>   
>   ^
> scons: *** [build/linux/x86_64/release/obj/common/crypto/CryptoAES.o] Error 1
> scons: building terminated because of errors.
> debian/rules:39: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/alljoyn-core-1509_15.09a-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#844797: cabal-debian: FTBFS: build-dependency not installable: libghc-debian-doc

[Lucas Nussbaum]

Source: cabal-debian
Version: 4.33-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-ansi-wl-pprint-dev (<< 0.7), 
> libghc-ansi-wl-pprint-dev (>= 0.6), libghc-ansi-wl-pprint-prof, 
> libghc-bifunctors-dev, libghc-bifunctors-prof, libghc-data-default-dev, 
> libghc-data-default-prof, libghc-debian-dev (>= 3.91), libghc-debian-prof, 
> libghc-diff-dev (>= 0.3.1), libghc-diff-prof, libghc-exceptions-dev, 
> libghc-exceptions-prof, libghc-hsemail-dev, libghc-hsemail-prof, 
> libghc-hunit-dev, libghc-hunit-prof, libghc-lens-dev, libghc-lens-prof, 
> libghc-memoize-dev (>= 0.7), libghc-memoize-prof, libghc-mtl-dev, 
> libghc-mtl-prof, libghc-network-uri-dev, libghc-network-uri-prof, 
> libghc-newtype-generics-dev (>= 0.4), libghc-newtype-generics-prof, 
> libghc-optparse-applicative-dev (>= 0.11), libghc-optparse-applicative-prof, 
> libghc-parsec3-dev (>= 3), libghc-parsec3-prof, libghc-puremd5-dev, 
> libghc-puremd5-prof, libghc-regex-tdfa-dev, libghc-regex-tdfa-prof, 
> libghc-set-extra-dev, libghc-set-extra-prof, libghc-syb-dev, libghc-syb-prof, 
> libghc-text-dev, libghc-text-prof, libghc-unixutils-dev (>= 1.53), 
> libghc-unixutils-prof, libghc-utf8-string-dev, libghc-utf8-string-prof, 
> ghc-doc, libghc-ansi-wl-pprint-doc, libghc-bifunctors-doc, 
> libghc-data-default-doc, libghc-debian-doc, libghc-diff-doc, 
> libghc-exceptions-doc, libghc-hsemail-doc, libghc-hunit-doc, libghc-lens-doc, 
> libghc-memoize-doc, libghc-mtl-doc, libghc-network-uri-doc, 
> libghc-newtype-generics-doc, libghc-optparse-applicative-doc, 
> libghc-parsec3-doc, libghc-puremd5-doc, libghc-regex-tdfa-doc, 
> libghc-set-extra-doc, libghc-syb-doc, libghc-text-doc, libghc-unixutils-doc, 
> libghc-utf8-string-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-ansi-wl-pprint-dev (<< 0.7), 
> libghc-ansi-wl-pprint-dev (>= 0.6), libghc-ansi-wl-pprint-prof, 
> libghc-bifunctors-dev, libghc-bifunctors-prof, libghc-data-default-dev, 
> libghc-data-default-prof, libghc-debian-dev (>= 3.91), libghc-debian-prof, 
> libghc-diff-dev (>= 0.3.1), libghc-diff-prof, libghc-exceptions-dev, 
> libghc-exceptions-prof, libghc-hsemail-dev, libghc-hsemail-prof, 
> libghc-hunit-dev, libghc-hunit-prof, libghc-lens-dev, libghc-lens-prof, 
> libghc-memoize-dev (>= 0.7), libghc-memoize-prof, libghc-mtl-dev, 
> libghc-mtl-prof, libghc-network-uri-dev, libghc-network-uri-prof, 
> libghc-newtype-generics-dev (>= 0.4), libghc-newtype-generics-prof, 
> libghc-optparse-applicative-dev (>= 0.11), libghc-optparse-applicative-prof, 
> libghc-parsec3-dev (>= 3), libghc-parsec3-prof, libghc-puremd5-dev, 
> libghc-puremd5-prof, libghc-regex-tdfa-dev, libghc-regex-tdfa-prof, 
> libghc-set-extra-dev, libghc-set-extra-prof, libghc-syb-dev, libghc-syb-prof, 
> libghc-text-dev, libghc-text-prof, libghc-unixutils-dev (>= 1.53), 
> libghc-unixutils-prof, libghc-utf8-string-dev, libghc-utf8-string-prof, 
> ghc-doc, libghc-ansi-wl-pprint-doc, libghc-bifunctors-doc, 
> libghc-data-default-doc, libghc-debian-doc, libghc-diff-doc, 
> libghc-exceptions-doc, libghc-hsemail-doc, libghc-hunit-doc, libghc-lens-doc, 
> libghc-memoize-doc, libghc-mtl-doc, libghc-network-uri-doc, 
> libghc-newtype-generics-doc, libghc-optparse-applicative-doc, 
> libghc-parsec3-doc, libghc-puremd5-doc, libghc-regex-tdfa-doc, 
> libghc-set-extra-doc, libghc-syb-doc, libghc-text-doc, libghc-unixutils-doc, 
> libghc-utf8-string-doc
> dpkg-deb: building package 'sbuild-build-depends-cabal-debian-dummy' in 
> '/<>/resolver-Wl2fHm/apt_archive/sbuild-build-depends-cabal-debian-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-cabal-debian-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Wl2fHm/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Wl2fHm/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Wl2fHm/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Wl2fHm/

Bug#844791: openmeeg: FTBFS: build-dependency not installable: libvtk6-dev

[Lucas Nussbaum]

Source: openmeeg
Version: 2.3.0~20160502-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 7.0.50~), cmake, doxygen, python-numpy, 
> swig | swig2.0, python-dev (>= 2.4), libatlas-base-dev, libvtk6-dev, 
> libtiff-dev | libtiff4-dev, libmatio-dev (>= 1.5)
> Filtered Build-Depends: debhelper (>= 7.0.50~), cmake, doxygen, python-numpy, 
> swig, python-dev (>= 2.4), libatlas-base-dev, libvtk6-dev, libtiff-dev, 
> libmatio-dev (>= 1.5)
> dpkg-deb: building package 'sbuild-build-depends-openmeeg-dummy' in 
> '/<>/resolver-cKsSN5/apt_archive/sbuild-build-depends-openmeeg-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-openmeeg-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-cKsSN5/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-cKsSN5/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-cKsSN5/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-cKsSN5/apt_archive ./ Sources [429 B]
> Get:5 copy:/<>/resolver-cKsSN5/apt_archive ./ Packages [507 B]
> Fetched 1893 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 openmeeg 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-openmeeg-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/openmeeg_2.3.0~20160502-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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#844725: libproj12 should conflict with libproj9

[Gianfranco Costamagna]

Source: proj
Version 4.9.3-1
Severity: Serious
Justification: breaks unrelated software when both libraries are installed.

Hi, as said, it took me two days to debug to understand this failure
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/m/mipp/20161118_053933_5e50e@/log.gz

the python binding fails and segfaults when both libproj9 and libproj12 are 
installed

(Reading database ... 65663 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [05:39:15]: test python2: [---
=== python2.7 ===
test_tsx (test_xsar.Test) ... Segmentation fault (core dumped)
autopkgtest [05:39:23]: test python2: ---]
autopkgtest [05:39:23]: test python2:  - - - - - - - - - - results - - - - - - 
- - - -
python2  FAIL non-zero exit status 139
autopkgtest [05:39:23]:  summary
python2  FAIL non-zero exit status 139

a no-change rebuild of mipp with both runtime libraries installed triggers the 
failure.

Since you can't force people from autoremoving the old libraries, I think this 
is an RC bug, and some sort
of conflict with previous version should be added to prevent such segfaults 
from happening.

thanks for understanding,

Gianfranco

Bug#844710: [Pkg-zsh-devel] Bug#844710: autocorrection suggested rm for typing mr without typing "y"

[Martin Steigerwald]

Am Freitag, 18. November 2016, 13:00:24 CET schrieben Sie:
> Hi Martin,
> 
> Martin Steigerwald wrote:
> > ms@intraws:~/Backup/Mail/Linux> mr kernel-ml_archive.gz
> > kernel-ml_archive_2014-1b.gz zsh: correct 'mr' to 'rm' [nyae]?
> > rm: das Entfernen von „kernel-ml_archive_2014-1b.gz“ ist nicht möglich:
> > Datei oder Verzeichnis nicht gefunden
> > 
> > I didn´t type yes, as when I type "y", it is shown on command line:
> > 
> > ms@intraws:~/Backup/Mail/Linux#1> LANG=C mr test
> > zsh: correct 'mr' to 'rm' [nyae]? y
> > rm: cannot remove 'test': No such file or directory
> > 
> > And I really didn´t type "y" there, I am pretty sure of that, but I may
> > have hit another key by accident.
> 
> Indeed scary.
> 
> From the output it look to as if "Enter" had been pressed on a
> first glance. But if I press "Enter" (on Sid at least) it shows an "n"
> instead afterwards. (Since I have mr installed, I tested it with "rmm"
> which is only available if nmh or mailutils-mh is installed.)
> 
> After some experimenting I noticed that while pressing Enter is
> equivalent to pressing "n" and also prints an "n", pressing the space
> bar is equivalent to "y" _without_ printing a "y".
> 
> So you very likely hit the space bar accidentially.

Yikes! Space bar to confirm? And correction to "rm".

Actually what I tried to type was "mv". I obviously wanted to move the file. 
But I accidentelly typed "mr". And then, yes, likely the spacebar.

I think this deserves a fix in the software :)

Thanks.

-- 
Martin Steigerwald  | Trainer

teamix GmbH
Südwestpark 43
90449 Nürnberg

Tel.:  +49 911 30999 55 | Fax: +49 911 30999 99
mail: martin.steigerw...@teamix.de | web:  http://www.teamix.de | blog: 
http://blog.teamix.de

Amtsgericht Nürnberg, HRB 18320 | Geschäftsführer: Oliver Kügow, Richard Müller

teamix Support Hotline: +49 911 30999-112
 
 *** Bitte liken Sie uns auf Facebook: facebook.com/teamix ***

Bug#844710: Fwd: Re: [Pkg-zsh-devel] Bug#844710: autocorrection suggested rm for typing mr without typing "y"

[Martin Steigerwald]

Dear Z-Shell developers,

I want to make you aware of the following issue with autocorrection I ran 
into:

autocorrection suggested rm for typing mr without typing "y"
https://bugs.debian.org/844710

Axel analysed this below a bit further an indeed, if I press the space bar, I 
get this:

ms@merkaba:~> cd /tmp   
ms@merkaba:/tmp> LANG=C mr test
zsh: correct 'mr' to 'rm' [nyae]?  
rm: cannot remove 'test': No such file or directory
ms@merkaba:/tmp#1>

So two fixes to consider:

1) Don´t confirm on space, as thats to easy to trigger accidentally. :)

2) Don´t autocorrect to dangerous commands like "rm". Could be a bit 
challenging to make a list of commands which are dangerous and can easily 
trigger unwanted actions. "rm" would IMO definately be one of this, while with 
"dd" it would be harder to trigger an unwanted action by accident due to 
syntax requirements.

Axel made me aware that I tell Z-Shell to ignore dangerous commands with 
CORRECT_IGNORE=rm, but I think it would be good to reconsider the standard 
behavior.

Thank you,
Martin

--  Weitergeleitete Nachricht  --

Betreff: Re: [Pkg-zsh-devel] Bug#844710: autocorrection suggested rm for 
typing mr without typing "y"
Datum: Freitag, 18. November 2016, 13:59:34 CET
Von: Martin Steigerwald 
An: Axel Beckert 
Kopie: 844...@bugs.debian.org

Am Freitag, 18. November 2016, 13:00:24 CET schrieben Sie:
> Hi Martin,
> 
> Martin Steigerwald wrote:
> > ms@intraws:~/Backup/Mail/Linux> mr kernel-ml_archive.gz
> > kernel-ml_archive_2014-1b.gz zsh: correct 'mr' to 'rm' [nyae]?
> > rm: das Entfernen von „kernel-ml_archive_2014-1b.gz“ ist nicht möglich:
> > Datei oder Verzeichnis nicht gefunden
> > 
> > I didn´t type yes, as when I type "y", it is shown on command line:
> > 
> > ms@intraws:~/Backup/Mail/Linux#1> LANG=C mr test
> > zsh: correct 'mr' to 'rm' [nyae]? y
> > rm: cannot remove 'test': No such file or directory
> > 
> > And I really didn´t type "y" there, I am pretty sure of that, but I may
> > have hit another key by accident.
> 
> Indeed scary.
> 
> From the output it look to as if "Enter" had been pressed on a
> first glance. But if I press "Enter" (on Sid at least) it shows an "n"
> instead afterwards. (Since I have mr installed, I tested it with "rmm"
> which is only available if nmh or mailutils-mh is installed.)
> 
> After some experimenting I noticed that while pressing Enter is
> equivalent to pressing "n" and also prints an "n", pressing the space
> bar is equivalent to "y" _without_ printing a "y".
> 
> So you very likely hit the space bar accidentially.

Yikes! Space bar to confirm? And correction to "rm".

Actually what I tried to type was "mv". I obviously wanted to move the file. 
But I accidentelly typed "mr". And then, yes, likely the space bar.

I think this deserves a fix in the software :)

Thanks.

-

-- 
Martin Steigerwald  | Trainer

teamix GmbH
Südwestpark 43
90449 Nürnberg

Tel.:  +49 911 30999 55 | Fax: +49 911 30999 99
mail: martin.steigerw...@teamix.de | web:  http://www.teamix.de | blog: 
http://blog.teamix.de

Amtsgericht Nürnberg, HRB 18320 | Geschäftsführer: Oliver Kügow, Richard Müller

teamix Support Hotline: +49 911 30999-112
 
 *** Bitte liken Sie uns auf Facebook: facebook.com/teamix ***

Bug#844724: apt: Does not seem to support new GnuPG keybox keyring format

[Julian Andres Klode]

Control: severity -1 wishlist

On Fri, Nov 18, 2016 at 01:58:18PM +0100, Guillem Jover wrote:
> Package: apt
> Version: 1.3.1
> Severity: important
> 
> [ Setting as important as this is GnuPG default, but if you think this
>   is a new feature or similar please just change it to wishlist. ]
> 
> Hi!
> 
> It seems like apt (and its gpgv method) do not support the new GnuPG
> keybox keyring format? Which is the one currently generated by default
> with newer GnuPG versions. A simple session to demonstrate:
> 
>   ,--- (line-wrapped for easier readability) ---
>   # cd /etc/apt/trusted.gpg.d
>   # file debian-archive-jessie-automatic.gpg
>   debian-archive-jessie-automatic.gpg: GPG key public ring,
>   created Fri Nov 21 21:01:13 2014
>   # mv debian-archive-jessie-automatic.gpg ~
>   # gpg --no-default-keyring --no-options --no-auto-check-trustdb \
> --keyring ./debian-archive-jessie-automatic.gpg --import \
> <~/debian-archive-jessie-automatic.gpg

The format we expect is the one generated by --export (standard concatenated
key packets), not the one used for creating keyrings by importing things.

We require that key files can be concatenated, otherwise we would have
to depend on gnupg to merge the key files for verification purposes.
-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#843402: reprepro cannot handle .changes files that reference .buildinfo files

[Guillem Jover]

Control: tags -1 patch

Hi!

On Fri, 2016-11-18 at 12:57:12 +0100, Guillem Jover wrote:
> On Sun, 2016-11-06 at 14:16:14 +0100, Helmut Grohne wrote:
> > Package: reprepro
> > Version: 4.17.1-1
> > Severity: important
> > User: helm...@debian.org
> > Usertags: rebootstrap
> > 
> > Since dpkg 1.18.11, a .buildinfo file is generated as part of package
> > builds and referenced by .changes files. Supplying such a .changes file
> > to "reprepro include" results in an error:
> > 
> > | Unknown file type: '2d3e9992648837b6a4a8a5b819e6da8e 4791 devel optional 
> > binutils_2.27.51.20161105-1_20161106T104833z-2d3e9992.buildinfo', assuming 
> > source format...
> > | .changes put in a
> > | distribution not listed within it!
> > | Ignoring as --ignore=wrongdistribution given.
> > | 'binutils_2.27.51.20161105-1_20161106T104833z-2d3e9992.buildinfo' looks 
> > like part of an source package, but no dsc file listed in the .changes file!
> > | There have been errors!   
> > 
> >   
> > 
> > So any workflow based on importing .changes files from unstable (soon
> > stretch) is now broken.
> 
> I've just prepared a patch supposedly fixing this, but I've never used
> reprepro and don't even know how it works, so it's just built-tested.
> We are now performing some tests, and will update the report once this
> is confirmed to work.
> 
> (The preliminary and perhaps non-working patch can be found for now at
> https://www.hadrons.org/~guillem/tmp/0001-Add-preliminary-.buildinfo-support.patch)

Ok, Michael Prokop deployed it on jenkins.grml.org and retriggered at
least the dpkg jobs and they seem to work now. I've fixed an inversion
logic error in the previous patch and I'm including the good one here.
Review and more testing would be very appreciated.

Thanks,
Guillem
From c059c721863ad0b33ab44417640c37f6f8cfabf1 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Fri, 18 Nov 2016 14:11:58 +0100
Subject: [PATCH] Add preliminary .buildinfo support

---
 changes.c   |  5 +++-
 changes.h   |  3 ++-
 checkin.c   | 51 +++--
 distribution.h  |  1 +
 docs/reprepro.1 |  3 +++
 incoming.c  | 78 +
 needbuild.c |  2 +-
 tracking.c  | 10 ++--
 trackingt.h |  1 +
 9 files changed, 141 insertions(+), 13 deletions(-)

diff --git a/changes.c b/changes.c
index 5d01754..2cafca3 100644
--- a/changes.c
+++ b/changes.c
@@ -237,6 +237,9 @@ retvalue changes_parsefileline(const char *fileline, /*@out@*/filetype *result_t
 		} else if (l > 6 && strncmp(p-6, ".build", 6) == 0) {
 			type = fe_LOG;
 			eoi = p - 6;
+		} else if (l > 10 && strncmp(p-10, ".buildinfo", 10) == 0) {
+			type = fe_BUILDINFO;
+			eoi = p - 10;
 		}
 		if (type != fe_UNKNOWN) {
 			/* check for a proper version */
@@ -255,7 +258,7 @@ retvalue changes_parsefileline(const char *fileline, /*@out@*/filetype *result_t
 	return RET_ERROR;
 }
 checkfilename = true;
-			} else if (type == fe_LOG) {
+			} else if (type == fe_LOG || type == fe_BUILDINFO) {
 if (*p == '_') {
 	archstart = p + 1;
 	archend = eoi;
diff --git a/changes.h b/changes.h
index 30ad136..f2b72c3 100644
--- a/changes.h
+++ b/changes.h
@@ -10,7 +10,8 @@ typedef enum {
 	fe_DEB, fe_UDEB,
 	fe_DSC, fe_DIFF, fe_ORIG, fe_TAR,
 	fe_ALTSRC,
-	fe_BYHAND, fe_LOG, fe_CHANGES
+	fe_BYHAND, fe_LOG, fe_CHANGES,
+	fe_BUILDINFO
 } filetype;
 
 #define FE_PACKAGE(ft) ((ft) == fe_DEB || (ft) == fe_UDEB || (ft) == fe_DSC)
diff --git a/checkin.c b/checkin.c
index 3b1ec32..3eb552e 100644
--- a/checkin.c
+++ b/checkin.c
@@ -161,7 +161,7 @@ static void changes_free(/*@only@*/struct changes *changes) {
 }
 
 
-static retvalue newentry(struct fileentry **entry, const char *fileline, const struct atomlist *packagetypes, const struct atomlist *forcearchitectures, const char *sourcename, bool includebyhand, bool includelogs, bool *ignoredlines_p, bool skip_binaries) {
+static retvalue newentry(struct fileentry **entry, const char *fileline, const struct atomlist *packagetypes, const struct atomlist *forcearchitectures, const char *sourcename, bool includebyhand, bool includelogs, bool includebuildinfos, bool *ignoredlines_p, bool skip_binaries) {
 	struct fileentry *e;
 	retvalue r;
 
@@ -207,7 +207,7 @@ static retvalue newentry(struct fileentry **entry, const char *fileline, const s
 		*ignoredlines_p = true;
 		return RET_NOTHING;
 	}
-	if (e->type != fe_LOG &&
+	if (e->type != fe_LOG && e->type != fe_BUILDINFO &&
 			e->architecture_into == architecture_source &&
 			strcmp(e->name, sourcename) != 0) {
 		fprintf(stderr,
@@ -242,6 +242,34 @@ static retvalue newentry(struct fileentry **entry, const char *fileline, const s
 			*ignoredlines_p = true;
 			return RET_NOTHING;
 		}
+	} else if (e->type == fe_BUILDINFO) {
+		if (strcmp(e->name, 

Bug#844708: maildir-utils: `--clearlinks' option seems broken

[Norbert Preining]

forwarded 844708 https://github.com/djcb/mu/issues/951
thanks

> Version 0.9.17-1 seems to have broken the `--clearlinks' functionality,
> at least on my system.

Also here. I have created an issue on the github page.

Thanks for your report

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#844726: w3m: CVE-2016-9439: stack overflow

[Salvatore Bonaccorso]

Source: w3m
Version: 0.5.3-8
Severity: normal
Tags: security upstream patch
Forwarded: https://github.com/tats/w3m/issues/20

Hi,

the following vulnerability was published for w3m, I'm aware that this
is as well already fixed in the upstream git master. This bug is just
to track the issue since unfixed in 0.5.3-30 so that we can record it
as fixed once enters unstable.

CVE-2016-9439[0]:
stack overflow

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9439

Regards and thanks for your work!
Salvatore

p.s.: all of the recently posted issues which got CVEs, seem to not
  warrant a DSA, but can be fixed via a point release. We have
  marked them already as such in the security-tracker.

Bug#844714: [Python-modules-team] Bug#844714: python-pycparser: Not installable

[Scott Kitterman]

It looks like '${python3-ply:Depends},' needs to be removed from Depends in 
debian/control.  We've never supported that construct for python3.  
'${python-ply:Depends},' should go as well, but in that case it's only cleaning 
up a bit of deprecated fluff.  That's not actively harmful.

Scott K

On November 18, 2016 5:44:54 AM CST, "Ondřej Nový"  wrote:
>Package: python-pycparser
>Version: 2.17-1
>Severity: grave
>Justification: renders package unusable
>
>Hi,
>
>this package can't be installed:
>
>The following packages have unmet dependencies:
> python-pycparser : Depends: python-ply-lex-3.5 but it is not
> installable
> Depends: python-ply-yacc-3.5 but it is not
> installable
>
>-- System Information:
>Debian Release: stretch/sid
>  APT prefers unstable
>  APT policy: (500, 'unstable'), (1, 'experimental')
>Architecture: amd64 (x86_64)
>
>Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores)
>Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>
>___
>Python-modules-team mailing list
>python-modules-t...@lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Bug#639910: Packaging sbt

[Frederic Bonnard]

Hello Mehdi/Emmanuel/all,
back on that topic,  I did some work and would need  your feedback on it
before going further.

What Mehdi said in his last comment, inspired me the following :

For sbt source package, I created 4 "sources" tarball :
1. sbt_0.13.13~RC1.orig.tar.gz : this is  the upstream source release of
sbt : https://github.com/sbt/sbt
2. sbt_0.13.13~RC1.orig-bootstrapsbt.tar.xz : this is the binary (mainly
sbt-launch.jar)  of the  previous sbt  version,  in our  case :  0.13.12
previous
3. sbt_0.13.13~RC1.orig-bootstrapdeps.tar.xz  : these  are all  the jars
that sbt 0.13.12 binary would fetch when running against that particular
project.
4.  sbt_0.13.13~RC1.orig-launcher.tar.xz  :  additional source  for  the
launcher : https://github.com/sbt/sbt-launcher-packag  e

1 and 4 are simply the tarballs from upstream projects.
2 and 3 are created from debian/rules get-orig-source target.
2  is the  binary tarball  that upstream  already provides,  but it's  a
"minimal" sbt  without all the  jars needed to  run. At launch  time, it
would detect that and will fetch all them.
For 3, I use the sbt binary of  2, to fetch all the jars it needs online
and I build a tarball from that.
This enables  to build the  source of  the project offline  (forcing it)
with all needed jars.

The point is  that the sbt package  I built is "nude". If  I install the
package built, the  0.13.13~RC1 version of sbt would need  a minimal set
of jars that is  missing (in the same way of 2)  and "sbt" command would
fail.
So I did the  same for all the dependencies needed  by this minimal sbt,
so that running "sbt" from the command line won't complain.
That is, for all dependencies that are  not already in Debian, I built a
package and as most of them (if not all if I remember) are sbt projects,
I  did that  3-tarball-source,  with the  upstream  project, a  prebuild
0.13.12 minimal binary sbt and a tarball of binary jars dependencies for
the latter.
This enabled to build packages for :
  https://github.com/bmc/classutil
  https://github.com/bmc/grizzled-scala
  https://github.com/bmc/scalasti
  https://github.com/foundweekends/giter8
  https://github.com/non/jawn
  https://github.com/json4s/json4s
  https://github.com/sbt/serialization
  https://github.com/sbt/test-interface
  https://github.com/scala/pickling
  https://github.com/harrah/sbinary
  https://github.com/scopt/scopt
and have a working sbt command  line without connecting online but using
Debian's local maven-repo.

There is much  work to finalize this  if that is ok,  but indeed, before
continuing I'd like to know if I'm on the good path.

F.

On Wed, 6 Jan 2016 01:58:13 +0100, Mehdi Dogguy  wrote:
> Hi,
> 
> On 05/01/2016 16:32, Emmanuel Bourg wrote:
> > The "easiest" solution is probably to start with a non-free sbt package
> > containing a prebuilt version of sbt, and then upload in main a sbt
> > package depending on itself with the prebuilt sbt removed. I would use
> > only one sbt package, instead of sbt-bootstrap in non-free and sbt in main.
> > 
> 
> Note that you can very much include a working sbt binary in the source
> package and use it the bootstrap sbt. The only condition that we must
> respect is to not ship that binary in the package, but ship the built
> binary only. This is done for many packages: OCaml for its bootstrap
> and most probably ghc (didn't check tbh). Also, compiling gcc requires
> a gcc. :-P
> 
> My 2 cents,
> 
> -- 
> Mehdi
> 

Bug#840186: [Debichem-devel] Bug#840186: nwchem builds on amd64 with -march=native

[Michael Banck]

tags 840186 +patch
tags 840186 +pending
thanks

On Fri, Nov 18, 2016 at 01:18:23AM +, Apra, Edoardo wrote:
> The attached patch disables the gfortran flag -march=native.
> Same patch can be found at the URL
> http://www.nwchem-sw.org/images/Disable_march_native.patch.gz

> --- nwchem-6.6/src/config/makefile.h  2016-11-17 22:29:09.794581240 +
> +++ nwchem-6.6/src/config/makefile.h.orig 2016-11-17 22:26:29.497599135 
> +
> @@ -1956,7 +1956,7 @@
>FOPTIONS +=  -ff2c -fno-second-underscore
>  endif
>  ifeq ($(GNU_GE_4_6),true) 
> -  FOPTIONS +=  -mtune=native
> +  FOPTIONS += -march=native -mtune=native
>FOPTIONS += -finline-functions
>  else
>  ifeq ($(_GOT3DNOW),Y) 

Thanks Edoardo, I've applied it to our packaging repository and will
look at uploading a new package with this patch later today.


Michael

Bug#837926: debian-installer: please use fonts-noto-hinted to display the Sinhala script

[Jonas Smedegaard]

Quoting Christian Perrier (2016-11-18 09:11:00)
> Le 17/11/2016 à 15:32, Jonas Smedegaard a écrit :
>> Quoting Harshula (2016-11-17 14:58:33)
>>> On 19/09/16 02:07, Christian PERRIER wrote:
 I'd be happy to do this, however the fonts-noto-hinted-udeb package 
 is 5 megabytes in size while the former fonts-lklug-sinhala-udeb 
 package is only 67kilobytes.

>> I can create a udeb specifically for Sinhala.  Or I can create a udeb 
>> for each single font part of the Noto deb.  What do the 
>> debian-installer team consider useful?

> Chagning the D-I font to Noto for all languages hasn't been 
> validated...and the current font is well tested and accepted.
> 
> So, as a consequence, I'd prefer a udeb that would be suited for 
> Sinhala.

Makes sense.

udeb package fonts-noto-hinted-udeb now, since 20161116-1, contains only 
fonts relevant for debian-installer - i.e. for now only Sinhala fonts.

 - Jonas

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

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

Bug#840186: [Debichem-devel] Bug#840186: Bug#840186: nwchem builds on amd64 with -march=native

[Michael Banck]

Hi,

> On Fri, Nov 18, 2016 at 01:18:23AM +, Apra, Edoardo wrote:
> > -  FOPTIONS +=  -mtune=native
> > +  FOPTIONS += -march=native -mtune=native

By the way, it seems this patch is reversed, as it adds -march=native.


Michael

Bug#844709: [Pkg-freeipa-devel] Bug#844709: certmonger: Certmonger runs its programs from nonexistent path

[Timo Aaltonen]

On 18.11.2016 12:47, Michal Kašpar wrote:
> Package: certmonger
> Version: 0.78.6-4
> Severity: important
> 
> Dear Maintainer,
> I've noticed the certmonger processes ends as defunct in process list.
> When looking into it via running certmonger in foreground debug mode
> (certmonger -f -d 5), I've found out the certmonger tries to run its
> components from /usr/lib/x86_64-linux-gnu/certmonger/ while they are
> installed in /usr/lib/certmonger. The symlink 
> /usr/lib/x86_64-linux-gnu/certmonger -> /usr/lib/certmonger fixes this, 
> however the correct fix is probably either to install those binaries to arch 
> dependent path or let them run from path where they are really installed.

That's weird, configure is told to use --libexecdir=/usr/lib.. are you
sure you don't have old files in /var/lib/certmonger/cas? Grep for
'usr/lib'.


-- 
t

Bug#844712: nginx: French debconf templates translation

[Julien Patriarca]

Package: nginx
Version: N/A
Severity: wishlist
Tags: patch l10n


Please find attached the french debconf templates translation, proofread by the
debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.



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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Translation of nginx debconf templates to French
# Copyright (C) 2016 Christos Trochalakis
# This file is distributed under the same license as the nginx package.
# Chrirtos Trochalakis , 2016.
# Julien Patriarca , 2016.
msgid ""
msgstr ""
"Project-Id-Version: nginx\n"
"Report-Msgid-Bugs-To: ng...@packages.debian.org\n"
"POT-Creation-Date: 2016-10-04 20:03+0300\n"
"PO-Revision-Date: 2016-11-02 09:52+0100\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Last-Translator: Julien Patriarca \n"
"Language-Team: French \n"
"X-Generator: Poedit 1.8.11\n"

#. Type: note
#. Description
#: ../nginx-common.templates:1001
msgid "Possible insecure nginx log files"
msgstr "Certains fichiers de journaux semblent non sécurisés"

#. Type: note
#. Description
#: ../nginx-common.templates:1001
msgid ""
"The following log files under /var/log/nginx directory are symlinks owned by "
"www-data:"
msgstr ""
"Les fichiers de journaux suivants se trouvant dans le dossier /var/log/nginx "
"sont des liens symboliques qui appartiennent à www-data :"

#. Type: note
#. Description
#: ../nginx-common.templates:1001
msgid "${logfiles}"
msgstr "${logfiles}"

#. Type: note
#. Description
#: ../nginx-common.templates:1001
msgid ""
"Since nginx 1.4.4-4 /var/log/nginx was owned by www-data. As a result www-"
"data could symlink log files to sensitive locations, which in turn could "
"lead to privilege escalation attacks. Although /var/log/nginx permissions "
"are now fixed it is possible that such insecure links already exist. So, "
"please make sure to check the above locations."
msgstr ""
"Depuis la version 1.4.4-4 de nginx, /var/log/nginx appartient à www-data. "
"Par conséquent www-data peut faire des liens symboliques des fichiers de "
"journaux vers des emplacements sensibles, ce qui pourrait amener à des "
"attaques par augmentation de droits. Même si désormais les droits de /var/"
"log/nginx ont été sécurisés, il est possible que de tels liens existent "
"déjà. Aussi, veuillez vous assurer d'avoir contrôlé les emplacements ci-"
"dessus."

Bug#810158: This needs to be fixed

[Marga Manterola]

Control: tags -1 -wontfix

With the change in debootstrap, this bug is now preventing ksh from getting
installed in a fresh installation.  In my case, this is even causing my
automated install to fail because there's a package that tries to pull in
ksh and so everything fails.

The patch is pretty straightforward and it's basically the same that has
already been applied in mksh:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807185

Please fix this.

Thanks.

-- 
Cheers,
Marga

Bug#844709: [Pkg-freeipa-devel] Bug#844709: certmonger: Certmonger runs its programs from nonexistent path

[Michal Kašpar]

# grep -r 'usr\/lib' /var/lib/certmonger/cas
/var/lib/certmonger/cas/20141030220219-
3:ca_external_helper=/usr/lib/x86_64-linux-gnu/certmonger/dogtag-ipa-
renew-agent-submit

So yes. They are there. Should I delete them or change the path?

> That's weird, configure is told to use --libexecdir=/usr/lib.. are
> you
> sure you don't have old files in /var/lib/certmonger/cas? Grep for
> 'usr/lib'.

-- 
Michal Kašpar

Bug#838768: sbuild-createchroot should let me re-create an existing chroot/tarball

[Ben Finney]

Control: found -1 sbuild/0.72.0-2
Control: tags -1 - moreinfo

On 24-Sep-2016, Julien Cristau wrote:

> I want to be able to update a sbuild chroot by re-creating the tarball
> from scratch, rather than running sbuild-update.  sbuild-createchroot
> used to let me do that by creating a new tarball and deleting the new
> duplicate config, but that doesn't seem to work anymore:
> chroot with name sid-amd64-sbuild already exists at 
> /usr/sbin/sbuild-createchroot line 214, <$pipe> line 7.

I get the same behaviour:

=
$ sudo rm /etc/sbuild/chroot/unstable-amd64-sbuild
rm: cannot remove '/etc/sbuild/chroot/unstable-amd64-sbuild': No such file or 
directory

$ sudo rm -r /srv/chroot/unstable-amd64-sbuild/
rm: cannot remove '/srv/chroot/unstable-amd64-sbuild/': No such file or 
directory

$ sudo sbuild-createchroot unstable /srv/chroot/unstable-amd64-sbuild/ 
http://httpredir.debian.org/debian/
chroot with name unstable-amd64-sbuild already exists at 
/usr/sbin/sbuild-createchroot line 214, <$pipe> line 1.
=


On 10-Nov-2016, Johannes Schauer wrote:

> so... is there then still a bug?

The bug in the above behaviour is:

* The obvious filesystem entries where the chroot might “already
  exist” do not actually exist, yet the tool refuses with the above
  message anyway.

* The user needs to make a decision about how to resolve the problem,
  but the message gives no help in finding what problematic thing
  “already exists”.

Both those, IMO, need to be correct to resolve this bug.

-- 
 \“I took a course in speed waiting. Now I can wait an hour in |
  `\ only ten minutes.” —Steven Wright |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#844220: maybe not /usr-merged but 0700 for / could be the culprit here

[Marco d'Itri]

On Nov 18, Holger Levsen  wrote:

> someone mailed me privately and pointed me to this forum post
> https://bbs.archlinux.org/viewtopic.php?id=186056=2 which made me
> realize that debootstrap had another change: TARGET is now created with
> 0700 permissions and not 0755 anymore, though I couldnt find this in
> debootstrap's changelog, so maybe I'm confused.
I can't see how this could be related to the usrmerge patch.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#836126: trafficserver: add Build-Depends to ensure tstop builds

[Jean Baptiste Favre]

Hello,

Thanks for your report.
I'll have a look at it.

Please note that tstop has been renamed to traffic_top since 2013

Regards,
JB



signature.asc
Description: OpenPGP digital signature

Bug#844714: python-pycparser: Not installable

[Ondřej Nový]

Package: python-pycparser
Version: 2.17-1
Severity: grave
Justification: renders package unusable

Hi,

this package can't be installed:

The following packages have unmet dependencies:
 python-pycparser : Depends: python-ply-lex-3.5 but it is not
 installable
 Depends: python-ply-yacc-3.5 but it is not
 installable

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

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

Bug#844713: ITP: partman-swapfile -- add support for creating swapfiles

[Dimitri John Ledkov]

Package: wnpp
Owner: Dimitri John Ledkov 
Severity: wishlist

* Package name: partman-swapfile
  Version : 1
  Upstream Author : d-i team
* URL or Web page : d-i
* License : GPL
  Description : add support for creating swapfiles

I am working on minimising number of partitions used in the default
instalations in Ubuntu. One of the things I have done already in Ubuntu is to
tweak and not use dedicated /boot partition for non-encrypted LVM based
installations. Simply by tweaking the partman-auto recipes, on
architectures/bootloaders that support booting off LVM.

Another thing I am investigating is moving away from swap partitions to
swap files, on non-lvm installations. This will involve tweaking the
default partman-auto recipes & the no-swap warning.

However, to provide swapfiles out of the box I wrote this
partman-swapfile module which hooks into /lib/partman/finish.d to create
/target/swapfile with an appropriate stanza in /target/etc/fstab. Care
is taken not to create swapfiles uncessory, reuse existing one, or do
nothing if a swap partition is already present, or swapfiles not
supported on a given filesystem (e.g. btrfs).

There are two control options to configure the size of the
swapfile. Absolute size, and percentage of free space on the
rootfs. The defaults are 2GB and 5%, meaning the swapfile will be 2GB in
size or 5% of the free space on rootfs, whichever is lower. Setting the
size or percentage to zero will skip creating the swapfile. This is a
strategy to make sure there is some swap available, without wasting too
much of disk space on high-memory-to-disk ratio systems (e.g. 1TB of RAM
with a 200GB hard drive).

I am not at all sure if this functionality is at all welcomed, needed,
or will generate any interest. I do not know if it's wanted to be
available by default in Debian's d-i. At the moment I created a git
repository in the d-i team, and plan to upload this to experimental for
people to try this out.

On the implementation side, swapfile is allocated using fallocate (if
avaialble and target filesystem creates files without holes using
fallocate) otherwise "slow" dd is used. This makes swapfile creation
really quick on ext4 rootfs.

All the glory details are here:
https://anonscm.debian.org/cgit/d-i/partman-swapfile.git/tree/finish.d

Regards,

Dimitri.

Bug#768495: Bug looks RC and is also in jessie

[Adrian Bunk]

Control: severity -1 serious
Countrl: found -1 2.14-1.1
Control: fixed -1 2.16-1
Control: close -1

Based on the initial bug report, this looks like an issue where the
fix should also be added to the package in jessie.

cu
Adrian

-- 

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

Bug#844709: [Pkg-freeipa-devel] Bug#844709: Bug#844709: certmonger: Certmonger runs its programs from nonexistent path

[Timo Aaltonen]

On 18.11.2016 13:33, Michal Kašpar wrote:
> # grep -r 'usr\/lib' /var/lib/certmonger/cas
> /var/lib/certmonger/cas/20141030220219-
> 3:ca_external_helper=/usr/lib/x86_64-linux-gnu/certmonger/dogtag-ipa-
> renew-agent-submit
> 
> So yes. They are there. Should I delete them or change the path?

Does stop/start of certmonger fix it? I wonder if postinst should mangle
them..


-- 
t