Bug#768716: ns2: FTBFS in jessie: build-dependency not installable: xgraph
Source: ns2 Version: 2.35+dfsg-1.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install ns2 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-ns2-dummy : Depends: xgraph but it is not installable 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/ftbfs-logs/2014/11/08/ns2_2.35+dfsg-1.1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768722: myproxy: FTBFS in jessie: tests failures
Source: myproxy
Version: 6.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
make[3]: Entering directory '/«PKGBUILDDIR»'
/bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu'
/bin/bash ./libtool --mode=install /usr/bin/install -c libmyproxy.la
'/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/libmyproxy.so.6.0.0
/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libmyproxy.so.6.0.0
libtool: install: (cd /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu {
ln -s -f libmyproxy.so.6.0.0 libmyproxy.so.6 || { rm -f libmyproxy.so.6 ln
-s libmyproxy.so.6.0.0 libmyproxy.so.6; }; })
libtool: install: (cd /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu {
ln -s -f libmyproxy.so.6.0.0 libmyproxy.so || { rm -f libmyproxy.so ln -s
libmyproxy.so.6.0.0 libmyproxy.so; }; })
libtool: install: /usr/bin/install -c .libs/libmyproxy.lai
/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libmyproxy.la
libtool: install: warning: remember to run `libtool --finish
/usr/lib/x86_64-linux-gnu'
/bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/bin'
/bin/bash ./libtool --mode=install /usr/bin/install -c myproxy-init
myproxy-info myproxy-store myproxy-destroy myproxy-retrieve
myproxy-get-trustroots myproxy-get-delegation myproxy-logon
myproxy-change-pass-phrase '/«PKGBUILDDIR»/debian/tmp/usr/bin'
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-init
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-init
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-info
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-info
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-store
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-store
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-destroy
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-destroy
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-retrieve
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-retrieve
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-get-trustroots
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-get-trustroots
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-get-delegation
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-get-delegation
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-logon
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-logon
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-change-pass-phrase
/«PKGBUILDDIR»/debian/tmp/usr/bin/myproxy-change-pass-phrase
/bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/sbin'
/bin/bash ./libtool --mode=install /usr/bin/install -c myproxy-server
myproxy-admin-load-credential myproxy-admin-query myproxy-admin-change-pass
'/«PKGBUILDDIR»/debian/tmp/usr/sbin'
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-server
/«PKGBUILDDIR»/debian/tmp/usr/sbin/myproxy-server
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-admin-load-credential
/«PKGBUILDDIR»/debian/tmp/usr/sbin/myproxy-admin-load-credential
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-admin-query
/«PKGBUILDDIR»/debian/tmp/usr/sbin/myproxy-admin-query
libtool: install: warning: `./libmyproxy.la' has not been installed in
`/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/myproxy-admin-change-pass
/«PKGBUILDDIR»/debian/tmp/usr/sbin/myproxy-admin-change-pass
/bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/sbin'
/usr/bin/install -c myproxy-test myproxy-replicate myproxy-test-replicate
myproxy-admin-adduser myproxy-admin-addservice myproxy-server-setup
'/«PKGBUILDDIR
Bug#768719: d3: FTBFS in jessie: build-dependency not installable: node-jsdom
Source: d3 Version: 3.4.11-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install d3 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-d3-dummy : Depends: node-jsdom but it is not installable 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/ftbfs-logs/2014/11/08/d3_3.4.11-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768723: pry: FTBFS in jessie: ERROR: Test ruby2.1 failed: Bacon::Error: /\* $/.===([1] pry(main)* ) failed
Source: pry Version: 0.10.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): Bacon::Error: /\* $/.===([1] pry(main)* ) failed /«PKGBUILDDIR»/spec/spec_helpers/repl_tester.rb:75:in `prompt': eval_string and binding_stack - should immediately evaluate eval_string after cmd if complete /«PKGBUILDDIR»/spec/pry_repl_spec.rb:93:in `block (4 levels) in top (required)' /«PKGBUILDDIR»/spec/spec_helpers/repl_tester.rb:36:in `instance_eval' /«PKGBUILDDIR»/spec/spec_helpers/repl_tester.rb:36:in `block in start' /«PKGBUILDDIR»/spec/spec_helpers/mock_pry.rb:24:in `redirect_pry_io' /«PKGBUILDDIR»/spec/spec_helpers/repl_tester.rb:34:in `start' /«PKGBUILDDIR»/spec/pry_repl_spec.rb:90:in `block (3 levels) in top (required)' /«PKGBUILDDIR»/spec/pry_repl_spec.rb:81:in `block (2 levels) in top (required)' /«PKGBUILDDIR»/spec/pry_repl_spec.rb:30:in `block in top (required)' /«PKGBUILDDIR»/spec/pry_repl_spec.rb:3:in `top (required)' 1110 tests, 1628 assertions, 1 failures, 0 errors debian/ruby-tests.rb:1:in `main': unhandled exception ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/pry_0.10.1-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768727: t-code: FTBFS in jessie: build-dependency not installable: emacs23
Source: t-code Version: 2:2.3.1-3.4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install t-code 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-t-code-dummy : Depends: emacs23 but it is not installable 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/ftbfs-logs/2014/11/08/t-code_2.3.1-3.4_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768730: python-mne: FTBFS in jessie: Tests failures
Source: python-mne Version: 0.8.4+dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): mne.viz.epochs222 66 97 5163% 76, 80, 98, 103, 106, 157, 235-261, 270, 272, 274-277, 280-288, 293-315, 356, 367, 373 mne.viz.evoked120 36 75 2867% 59-63, 91, 96-97, 104-105, 111-116, 134-137, 146, 166-167, 279-296 mne.viz.ica 210 66 82 3864% 22-39, 76, 131, 134-136, 146, 187-188, 190, 198-199, 250-251, 302, 312, 315, 324, 376-387, 392, 417-445, 469 mne.viz.misc 239118124 6849% 64, 102, 156-242, 268-338, 364-390, 461 mne.viz.raw 354 31148 3687% 69, 101-103, 134, 140-141, 157, 171-172, 245-246, 261-262, 353-357, 377, 385, 387-394, 405-406, 541, 557, 594 mne.viz.topo 273100141 6361% 80, 84-85, 163-184, 193, 222, 224, 226, 295-298, 302, 311-312, 326-327, 337, 352, 375-397, 441-458, 520-544, 606-627, 640, 644, 647, 655, 657, 659, 709, 711, 713-714 mne.viz.topomap 46120120512851% 33-34, 43-45, 49, 56, 59-61, 72-100, 146-204, 237, 242-245, 294, 299, 375-377, 379, 395, 398-399, 416, 425, 429-434, 474, 477-481, 484-491, 538, 633, 645, 655-660, 773, 793-794, 802-803, 810, 921-1035 mne.viz.utils 164 52 69 3563% 77, 79, 81, 83, 103, 108-116, 127, 161-200, 211-213, 220-224, 231-232, 253, 282-283, 294-295, 337, 344, 360-361 --- TOTAL 26999 10372 10389 529158% -- Ran 376 tests in 495.111s FAILED (SKIP=109, errors=3) make[1]: *** [override_dh_auto_test] Error 1 debian/rules:18: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/python-mne_0.8.4+dfsg-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768726: libbitcoin: FTBFS in jessie: configure: error: cannot find install-sh, install.sh, or shtool in . ./.. ./../..
Source: libbitcoin
Version: 2.0-2.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
touch debian/stamp-autotools-files
chmod a+x /«PKGBUILDDIR»/./configure
mkdir -p .
cd .CFLAGS=-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall CXXFLAGS=-g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -Wall CPPFLAGS=-D_FORTIFY_SOURCE=2
LDFLAGS=-Wl,-z,relro /«PKGBUILDDIR»/./configure --build=x86_64-linux-gnu
--prefix=/usr --includedir=\${prefix}/include
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
--sysconfdir=/etc --localstatedir=/var
--libexecdir=\${prefix}/lib/libbitcoin --srcdir=. --disable-maintainer-mode
--disable-dependency-tracking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --enable-bdb --enable-leveldb
configure: WARNING: unrecognized options: --disable-maintainer-mode,
--enable-bdb
configure: error: cannot find install-sh, install.sh, or shtool in . ./..
./../..
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/libbitcoin_2.0-2.1_jessie.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.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768725: llvm-toolchain-3.5: FTBFS in jessie: linux-arm-atomic.c:19:14: error: redefinition of 'exchange_and_add'
Source: llvm-toolchain-3.5
Version: 1:3.5-6
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
make[3]: Entering directory '/«PKGBUILDDIR»/build-llvm/tools/clang/test'
Making Clang 'lit.site.cfg' file...
Making Clang 'Unit/lit.site.cfg' file...
--- Running clang tests for x86_64-pc-linux-gnu ---
lit.py: lit.cfg:201: note: using clang:
'/«PKGBUILDDIR»/build-llvm/Release/bin/clang'
lit.py: lit.cfg:329: note: Did not find clang-interpreter in
/«PKGBUILDDIR»/build-llvm/Release/bin:/«PKGBUILDDIR»/build-llvm/Release/bin
-- Testing: 7516 tests, 2 threads --
Testing: 0 .. 10..
FAIL: Clang :: CodeGen/linux-arm-atomic.c (1650 of 7516)
TEST 'Clang :: CodeGen/linux-arm-atomic.c' FAILED
Script:
--
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -cc1 -internal-isystem
/«PKGBUILDDIR»/build-llvm/Release/bin/../lib/clang/3.5.0/include
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c -emit-llvm -o -
-triple=armv7-unknown-linux | /«PKGBUILDDIR»/build-llvm/Release/bin/FileCheck
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -cc1 -internal-isystem
/«PKGBUILDDIR»/build-llvm/Release/bin/../lib/clang/3.5.0/include
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c -emit-llvm -o -
-triple=armv6-unknown-linux | /«PKGBUILDDIR»/build-llvm/Release/bin/FileCheck
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -cc1 -internal-isystem
/«PKGBUILDDIR»/build-llvm/Release/bin/../lib/clang/3.5.0/include
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c -emit-llvm -o -
-triple=thumbv7-unknown-linux |
/«PKGBUILDDIR»/build-llvm/Release/bin/FileCheck
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -cc1 -internal-isystem
/«PKGBUILDDIR»/build-llvm/Release/bin/../lib/clang/3.5.0/include
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c -emit-llvm -o -
-triple=armv7-unknown-linux | /«PKGBUILDDIR»/build-llvm/Release/bin/FileCheck
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -cc1 -internal-isystem
/«PKGBUILDDIR»/build-llvm/Release/bin/../lib/clang/3.5.0/include
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c -emit-llvm -o -
-triple=armv6-unknown-linux | /«PKGBUILDDIR»/build-llvm/Release/bin/FileCheck
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -cc1 -internal-isystem
/«PKGBUILDDIR»/build-llvm/Release/bin/../lib/clang/3.5.0/include
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c -emit-llvm -o -
-triple=thumbv7-unknown-linux |
/«PKGBUILDDIR»/build-llvm/Release/bin/FileCheck
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -cc1 -internal-isystem
/«PKGBUILDDIR»/build-llvm/Release/bin/../lib/clang/3.5.0/include
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c -emit-llvm -o -
-triple=armv6-unknown-freebsd |
/«PKGBUILDDIR»/build-llvm/Release/bin/FileCheck
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -cc1 -internal-isystem
/«PKGBUILDDIR»/build-llvm/Release/bin/../lib/clang/3.5.0/include
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c -emit-llvm -o -
-triple=armv6-unknown-bitrig |
/«PKGBUILDDIR»/build-llvm/Release/bin/FileCheck
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c
--
Exit Code: 2
Command Output (stderr):
--
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c:18:13: warning:
redefinition of typedef '_Atomic_word' is a C11 feature
typedef int _Atomic_word;
^
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c:5:13: note: previous
definition is here
typedef int _Atomic_word;
^
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c:19:14: error:
redefinition of 'exchange_and_add'
_Atomic_word exchange_and_add(volatile _Atomic_word *__mem, int __val) {
^
/«PKGBUILDDIR»/clang/test/CodeGen/linux-arm-atomic.c:6:14: note: previous
definition is here
_Atomic_word exchange_and_add(volatile _Atomic_word *__mem, int __val) {
^
FileCheck error: '-' is empty.
1 warning and 1 error generated.
--
Testing: 0 .. 10.. 20.. 30..
FAIL: Clang :: Driver/arm-mfpu.c (2919 of 7516)
TEST 'Clang :: Driver/arm-mfpu.c' FAILED
Script:
--
/«PKGBUILDDIR»/build-llvm/Release/bin/clang -target arm-linux-eabi
/«PKGBUILDDIR»/clang/test/Driver/arm-mfpu.c -### -o
/«PKGBUILDDIR»/build-llvm/tools/clang/test/Driver/Output/arm-mfpu.c.tmp.o
21| /«PKGBUILDDIR»/build-llvm
Bug#768728: ruby-net-http-persistent: FTBFS in jessie: ERROR: Test ruby2.1 failed: Errno::ECONNRESET: Connection reset by peer - SSL_connect
Source: ruby-net-http-persistent Version: 2.9-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): Errno::ECONNRESET: Connection reset by peer - SSL_connect /«PKGBUILDDIR»/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:70:in `connect' /«PKGBUILDDIR»/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:70:in `block in connect' /usr/lib/ruby/2.1.0/timeout.rb:76:in `timeout' /usr/lib/ruby/2.1.0/timeout.rb:127:in `timeout' /«PKGBUILDDIR»/debian/ruby-net-http-persistent/usr/lib/ruby/vendor_ruby/net/http/persistent/ssl_reuse.rb:70:in `connect' /usr/lib/ruby/2.1.0/net/http.rb:863:in `do_start' /usr/lib/ruby/2.1.0/net/http.rb:858:in `start' /«PKGBUILDDIR»/test/test_net_http_persistent_ssl_reuse.rb:94:in `test_ssl_connection_reuse' /usr/lib/ruby/vendor_ruby/minitest/test.rb:108:in `block (3 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:206:in `capture_exceptions' /usr/lib/ruby/vendor_ruby/minitest/test.rb:105:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:258:in `time_it' /usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:319:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest/test.rb:278:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:761:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:293:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:287:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:286:in `each' /usr/lib/ruby/vendor_ruby/minitest.rb:286:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:319:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest.rb:306:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest.rb:285:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:149:in `block in __run' /usr/lib/ruby/vendor_ruby/minitest.rb:149:in `map' /usr/lib/ruby/vendor_ruby/minitest.rb:149:in `__run' /usr/lib/ruby/vendor_ruby/minitest.rb:126:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:55:in `block in autorun' 102 runs, 342 assertions, 0 failures, 1 errors, 4 skips You have skipped tests. Run with --verbose for details. ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/ruby-net-http-persistent_2.9-2_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768729: paulstretch: FTBFS in jessie: ld: /tmp/ccAztzrN.o: undefined reference to symbol 'vorbis_comment_add_tag'
Source: paulstretch Version: 2.2-2-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): g++ GUI.cxx FreeEditUI.cxx *.cpp Input/*.cpp Output/*.cpp \ -o paulstretch \ -Wl,--as-needed \ `fltk-config --cflags` `fltk-config --ldflags` \ -DHAVE_JACK -DENABLE_RESAMPLING \ `pkg-config --cflags --libs jack samplerate` \ `pkg-config --cflags --libs fftw3f vorbisenc vorbisfile mad mxml audiofile` \ -lportaudio -lpthread -lz /usr/bin/ld: /tmp/ccAztzrN.o: undefined reference to symbol 'vorbis_comment_add_tag' //usr/lib/x86_64-linux-gnu/libvorbis.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/paulstretch_2.2-2-2_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768731: matplotlib: FTBFS in jessie: build-dependency not installable: python-wxgtk2.8
Source: matplotlib Version: 1.3.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install matplotlib 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-matplotlib-dummy : Depends: python-wxgtk2.8 but it is not installable 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/ftbfs-logs/2014/11/08/matplotlib_1.3.1-2_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768735: libgeometry-primitive-perl: FTBFS in jessie: Tests failures
Source: libgeometry-primitive-perl Version: 0.24-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): # Looks like your test exited with 2 before it could output anything. t/010-serialize.t .. Dubious, test returned 2 (wstat 512, 0x200) Failed 7/7 subtests t/dimension.t .. ok Test Summary Report --- t/010-serialize.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 7 tests but ran 0. Files=10, Tests=58, 3 wallclock secs ( 0.05 usr 0.05 sys + 2.59 cusr 0.24 csys = 2.93 CPU) Result: FAIL Failed 1/10 test programs. 0/58 subtests failed. make[1]: *** [test_dynamic] Error 255 Makefile:815: recipe for target 'test_dynamic' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/libgeometry-primitive-perl_0.24-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768736: mailsync: FTBFS in jessie: configure: error: a working c-client installation is required for building mailsync
Source: mailsync Version: 5.2.2-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): checking for krb5-config... not found checking for pam library... not found checking for c-client.h... found in /usr/include/c-client checking for c-client library... found /usr/lib/libc-client.so checking whether c-client built with kerberos gssapi support... yes configure: error: a working c-client installation is required for building mailsync checking if kerberos is required and available for linking against c-client... no The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/mailsync_5.2.2-3_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768732: plm: FTBFS in jessie: src/plm/core/model/Game.java:97: error: unmappable character for encoding ASCII
Source: plm Version: 2.4.11+repack-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«BUILDDIR»/plm-2.4.11+repack' # Copy our resource within the wannabe jar file mkdir -p debian/_jh_build.plm cp -r lib/resources debian/_jh_build.plm # Copy our image files (but prune the svg files) cp -r img debian/_jh_build.plm find debian/_jh_build.plm -name *.svg -print0 | xargs -0 rm # Copy other mandated files in place jarctn=`find src -name *.py; \ find src -name *.java; \ find src -name *.scala; \ find src -name *.c; \ find src -name *.html; \ find src -name *.png; \ find src -name *.map`; \ for file in $jarctn ; do\ whereto=`echo $file|sed 's|^src/||'` ; \ install -D -m 644 $file debian/_jh_build.plm/$whereto; \ done # Generate the translation files ant i18n-generate-jar Buildfile: /«BUILDDIR»/plm-2.4.11+repack/build.xml [taskdef] Could not load definitions from resource scala/tools/ant/antlib.xml. It could not be found. i18n-init: i18n-extract: [gettext-extract] src [gettext-extract] /tmp/srcfiles4590680762197888444.tmp [gettext-extract] Executing: xgettext -c --from-code=utf-8 --output=/«BUILDDIR»/plm-2.4.11+repack/l10n/engine/plm.pot --language=Java -ktrc:1c,2 -ktrnc:1c,2,3 -ktr -kmarktr -ktrn:1,2 -k --files-from=/tmp/srcfiles4590680762197888444.tmp i18n-update: [gettext-merge] Invoking msgmerge for po files in '/«BUILDDIR»/plm-2.4.11+repack/l10n/engine'. [gettext-merge] Processing en.po [gettext-merge] Executing: msgmerge -q --backup=numbered -U /«BUILDDIR»/plm-2.4.11+repack/l10n/engine/en.po /«BUILDDIR»/plm-2.4.11+repack/l10n/engine/plm.pot [gettext-merge] Processing fr.po [gettext-merge] Executing: msgmerge -q --backup=numbered -U /«BUILDDIR»/plm-2.4.11+repack/l10n/engine/fr.po /«BUILDDIR»/plm-2.4.11+repack/l10n/engine/plm.pot [gettext-merge] Processing it.po [gettext-merge] Executing: msgmerge -q --backup=numbered -U /«BUILDDIR»/plm-2.4.11+repack/l10n/engine/it.po /«BUILDDIR»/plm-2.4.11+repack/l10n/engine/plm.pot [gettext-merge] Processing pt_BR.po [gettext-merge] Executing: msgmerge -q --backup=numbered -U /«BUILDDIR»/plm-2.4.11+repack/l10n/engine/pt_BR.po /«BUILDDIR»/plm-2.4.11+repack/l10n/engine/plm.pot i18n-check: [exec] msggrep: warning: Locale charset ANSI_X3.4-1968 is different from [exec] input file charset UTF-8. [exec] msggrep: warning: Locale charset ANSI_X3.4-1968 is different from [exec] input file charset UTF-8. [exec] Output of 'msggrep' might be incorrect. [exec] Possible workarounds are: [exec] Output of 'msggrep' might be incorrect. [exec] Possible workarounds are: [exec] - Set LC_ALL to a locale with encoding UTF-8. [exec] - Convert the translation catalog to ASCII using 'msgconv', [exec] - Set LC_ALL to a locale with encoding UTF-8. [exec] - Convert the translation catalog to ASCII using 'msgconv', [exec] then apply 'msggrep', [exec] then convert back to UTF-8 using 'msgconv'. [exec] then apply 'msggrep', [exec] then convert back to UTF-8 using 'msgconv'. [exec] msggrep: warning: Locale charset ANSI_X3.4-1968 is different from [exec] input file charset UTF-8. [exec] msggrep: warning: Locale charset ANSI_X3.4-1968 is different from [exec] input file charset UTF-8. [exec] Output of 'msggrep' might be incorrect. [exec] Possible workarounds are: [exec] Output of 'msggrep' might be incorrect. [exec] Possible workarounds are: [exec] - Set LC_ALL to a locale with encoding UTF-8. [exec] - Convert the translation catalog to ASCII using 'msgconv', [exec] - Set LC_ALL to a locale with encoding UTF-8. [exec] - Convert the translation catalog to ASCII using 'msgconv', [exec] then apply 'msggrep', [exec] then convert back to UTF-8 using 'msgconv'. [exec] then apply 'msggrep', [exec] then convert back to UTF-8 using 'msgconv'. i18n-generate-jar: [mkdir] Created dir: /«BUILDDIR»/plm-2.4.11+repack/site/po [gettext-dist] Processing en.po [gettext-dist] msgfmt --java2 -d ./site/po -r
Bug#768733: winff: FTBFS in jessie: javaldx failed!
Source: winff Version: 1.5.3-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' soffice --headless --convert-to pdf --outdir docs docs/WinFF.*.od? [Java framework] Error in function createSettingsDocument (elements.cxx). javaldx failed! Warning: failed to read path from javaldx make[1]: *** [override_dh_auto_build-indep] Error 77 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/winff_1.5.3-4_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768734: wine-gecko-2.21: FTBFS in jessie: mcom_db.h:41:21: fatal error: prtypes.h: No such file or directory
Source: wine-gecko-2.21 Version: 2.21+dfsg2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): make[8]: Entering directory '/«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/security/dbm/src' i686-w64-mingw32-gcc -mwindows -o /«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/dbm/src/db.o -c -O2 -mwindows -mms-bitfields -mnop-fun-dllimport -DXP_PC -UDEBUG -U_DEBUG -DNDEBUG -DWIN32 -D_WINDOWS -DWIN95 -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DSTDC_HEADERS -DHAVE_STRERROR -DHAVE_SNPRINTF -DMEMMOVE -D__DBINTERFACE_PRIVATE -I/build/wine-gecko-2.21QXCLY/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/dist/include/nspr -I/build/wine-gecko-2.21QXCLY/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/dist/include/nspr -I/«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/build/../../dist/public/dbm -I/«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/build/../../dist/private/dbm -I../../../dbm/include ../../../dbm/src/db.c In file included from ../../../dbm/src/db.c:50:0: /«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/build/../../dist/public/dbm/mcom_db.h:41:21: fatal error: prtypes.h: No such file or directory #include prtypes.h ^ compilation terminated. make[8]: *** [/«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/dbm/src/db.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/wine-gecko-2.21_2.21+dfsg2-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768740: hol88: FTBFS in jessie: build-dependency not installable: gcl (= 2.6.11-6)
Source: hol88 Version: 2.02.19940316-28 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install hol88 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-hol88-dummy : Depends: gcl (= 2.6.11-6) 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/ftbfs-logs/2014/11/08/hol88_2.02.19940316-28_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768737: ruby-delorean: FTBFS in jessie: build-dependency not installable: ruby-activesupport-3.2
Source: ruby-delorean Version: 2.1.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install ruby-delorean 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-ruby-delorean-dummy : Depends: ruby-activesupport-3.2 but it is not installable 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/ftbfs-logs/2014/11/08/ruby-delorean_2.1.0-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768738: jarisplayer: FTBFS in jessie: build-dependency not installable: haxe
Source: jarisplayer Version: 2.0.15+20131104~dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install jarisplayer 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-jarisplayer-dummy : Depends: haxe but it is not installable 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/ftbfs-logs/2014/11/08/jarisplayer_2.0.15+20131104~dfsg-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768743: python-gear: FTBFS in jessie: build-dependency not installable: python-statsd (= 1.0.0)
Source: python-gear Version: 0.5.4-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install python-gear 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-gear-dummy : Depends: python-statsd (= 1.0.0) but it is not installable 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/ftbfs-logs/2014/11/08/python-gear_0.5.4-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768739: sphinxcontrib-actdiag: FTBFS in jessie: unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing
Source: sphinxcontrib-actdiag Version: 0.8.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install sphinxcontrib-actdiag 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-sphinxcontrib-actdiag-dummy : Depends: python-sphinx-testing but it is not installable Depends: python3-sphinx-testing but it is not installable 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/ftbfs-logs/2014/11/08/sphinxcontrib-actdiag_0.8.0-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768745: pocl: FTBFS in jessie: make[1]: *** [override_dh_makeshlibs] Error 1
Source: pocl
Version: 0.10-10
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: warning: debian/libpocl1/DEBIAN/symbols doesn't match
completely debian/libpocl1.symbols
--- debian/libpocl1.symbols (libpocl1_0.10-10_amd64)
+++ dpkg-gensymbolscYBc3Z 2014-11-09 04:29:38.023260306 +
@@ -21,7 +21,7 @@
(optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeEjEES1_RKT_RKT0_@Base
0.10
(optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeEjjEES1_RKT_RKT0_RKT1_@Base
0.10
(optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeElEES1_RKT_RKT0_@Base
0.10
-
(optional=templinst|subst|arch=kfreebsd-i386)_ZN4llvm12hash_combineI{int64_t}lEENS_9hash_codeERKT_RKT0_@Base
0.10
+
(optional=templinst|subst)_ZN4llvm12hash_combineI{int64_t}lEENS_9hash_codeERKT_RKT0_@Base
0.10
(optional=templinst)_ZN4llvm15SmallVectorImplIN5clang14TypoCorrectionEEaSEOS3_@Base
0.10
(optional=templinst)_ZN4llvm15SmallVectorImplIN5clang15CharSourceRangeEEaSERKS3_@Base
0.10
(optional=templinst|arch=!i386
!kfreebsd-i386)_ZN4llvm15SmallVectorImplIN5clang16LambdaIntroducer13LambdaCaptureEEaSEOS4_@Base
0.10
@@ -592,7 +592,7 @@
_ZN5clang11FileManager12addStatCacheEPNS_19FileSystemStatCacheEb@Base 0.10
_ZN5clang11FileManager12getDirectoryEN4llvm9StringRefEb@Base 0.10
_ZN5clang11FileManager12getStatValueEPKcRNS_8FileDataEbPSt10unique_ptrINS_3vfs4FileESt14default_deleteIS7_EE@Base
0.10
-
(subst|arch=kfreebsd-i386)_ZN5clang11FileManager14getVirtualFileEN4llvm9StringRefE{int64_t}l@Base
0.10
+
(subst)_ZN5clang11FileManager14getVirtualFileEN4llvm9StringRefE{int64_t}l@Base
0.10
_ZN5clang11FileManager15clearStatCachesEv@Base 0.10
_ZN5clang11FileManager15invalidateCacheEPKNS_9FileEntryE@Base 0.10
(subst)_ZN5clang11FileManager15modifyFileEntryEPNS_9FileEntryE{int64_t}l@Base
0.10
@@ -1576,7 +1576,7 @@
_ZN5clang13serialization13ModuleManager13removeModulesEPPNS0_10ModuleFileES4_RN4llvm15SmallPtrSetImplIS3_EEPNS_9ModuleMapE@Base
0.10
_ZN5clang13serialization13ModuleManager14setGlobalIndexEPNS_17GlobalModuleIndexE@Base
0.10
_ZN5clang13serialization13ModuleManager15visitDepthFirstEPFbRNS0_10ModuleFileEbPvES4_@Base
0.10
-
(subst|arch=kfreebsd-i386)_ZN5clang13serialization13ModuleManager16lookupModuleFileEN4llvm9StringRefE{int64_t}lRPKNS_9FileEntryE@Base
0.10
+
(subst)_ZN5clang13serialization13ModuleManager16lookupModuleFileEN4llvm9StringRefE{int64_t}lRPKNS_9FileEntryE@Base
0.10
_ZN5clang13serialization13ModuleManager16returnVisitStateEPNS1_10VisitStateE@Base
0.10
_ZN5clang13serialization13ModuleManager17addInMemoryBufferEN4llvm9StringRefEPNS2_12MemoryBufferE@Base
0.10
_ZN5clang13serialization13ModuleManager18allocateVisitStateEv@Base 0.10
@@ -1584,7 +1584,7 @@
_ZN5clang13serialization13ModuleManager5visitEPFbRNS0_10ModuleFileEPvES4_PN4llvm11SmallPtrSetIPS2_Lj4EEE@Base
0.10
_ZN5clang13serialization13ModuleManager6lookupEN4llvm9StringRefE@Base 0.10
_ZN5clang13serialization13ModuleManager6lookupEPKNS_9FileEntryE@Base 0.10
-
(subst|arch=kfreebsd-i386)_ZN5clang13serialization13ModuleManager9addModuleEN4llvm9StringRefENS0_10ModuleKindENS_14SourceLocationEPNS0_10ModuleFileEj{int64_t}lRS7_RSs@Base
0.10
+
(subst)_ZN5clang13serialization13ModuleManager9addModuleEN4llvm9StringRefENS0_10ModuleKindENS_14SourceLocationEPNS0_10ModuleFileEj{int64_t}lRS7_RSs@Base
0.10
_ZN5clang13serialization13ModuleManagerC1ERNS_11FileManagerE@Base 0.10
_ZN5clang13serialization13ModuleManagerC2ERNS_11FileManagerE@Base 0.10
_ZN5clang13serialization13ModuleManagerD1Ev@Base 0.10
if test -f debian/stamp-failed-testsuite ; then \
grep '^ .*FAILED' tests/testsuite.log ; \
exit 1 ; \
fi
make[1]: *** [override_dh_makeshlibs] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/pocl_0.10-10_jessie.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.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768744: libcatmandu-marc-perl: FTBFS in jessie: tests failures
Source: libcatmandu-marc-perl Version: 0.206-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): debian/rules build test -x debian/rules mkdir -p . Scanning upstream source for new/changed copyright notices... licensecheck -c '.*' -r --copyright -i '^debian/(changelog|copyright(|_hints|_newhints))' -l '9' * | /usr/lib/cdbs/licensecheck2dep5 debian/copyright_newhints 3 combinations of copyright and licensing found. No new copyright notices found - assuming no news is good news... touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft cd . perl Build.PL --installdirs vendor --config ccflags= --config cxxflags= --config cppflags= --config ldflags= --destdir /«PKGBUILDDIR»/debian/libcatmandu-marc-perl Checking prerequisites... requires: ! Catmandu is not installed ! MARC::File::MARCMaker is not installed ! MARC::File::MiJ is not installed ! MARC::Parser::RAW is not installed ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation Run 'Build installdeps' to install missing prerequisites. Created MYMETA.yml and MYMETA.json Creating new 'Build' script for 'Catmandu-MARC' version '0.206' cd . ./Build build Building Catmandu-MARC touch debian/stamp-perl-build cd . ./Build test --verbose 1 # Failed test 'use Catmandu::Importer::MARC;' # at t/00-load.t line 8. # Tried to use 'Catmandu::Importer::MARC'. # Error: Can't locate Catmandu/Sane.pm in @INC (you may need to install the Catmandu::Sane module) (@INC contains: /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /«PKGBUILDDIR»/blib/lib/Catmandu/Importer/MARC.pm line 113. # BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/Catmandu/Importer/MARC.pm line 113. # Compilation failed in require at t/00-load.t line 8. # BEGIN failed--compilation aborted at t/00-load.t line 8. # Failed test 'use Catmandu::Exporter::MARC;' # at t/00-load.t line 9. # Tried to use 'Catmandu::Exporter::MARC'. # Error: Can't locate Catmandu/Sane.pm in @INC (you may need to install the Catmandu::Sane module) (@INC contains: /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /«PKGBUILDDIR»/blib/lib/Catmandu/Exporter/MARC.pm line 48. # BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/Catmandu/Exporter/MARC.pm line 48. # Compilation failed in require at t/00-load.t line 9. # BEGIN failed--compilation aborted at t/00-load.t line 9. # Failed test 'use Catmandu::Fix::marc_map;' # at t/00-load.t line 10. # Tried to use 'Catmandu::Fix::marc_map'. # Error: Can't locate Catmandu/Sane.pm in @INC (you may need to install the Catmandu::Sane module) (@INC contains: /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /«PKGBUILDDIR»/blib/lib/Catmandu/Fix/marc_map.pm line 3. # BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/Catmandu/Fix/marc_map.pm line 3. # Compilation failed in require at t/00-load.t line 10. # BEGIN failed--compilation aborted at t/00-load.t line 10. # Failed test 'use Catmandu::Fix::marc_xml;' # at t/00-load.t line 11. # Tried to use 'Catmandu::Fix::marc_xml'. # Error: Can't locate Catmandu/Sane.pm in @INC (you may need to install the Catmandu::Sane module) (@INC contains: /«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /«PKGBUILDDIR»/blib/lib/Catmandu/Fix/marc_xml.pm line 3. # BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/Catmandu/Fix/marc_xml.pm line 3. # Compilation failed in require at t/00-load.t line 11. # BEGIN failed--compilation aborted at t/00-load.t line 11. # Failed test 'use Catmandu::Fix::marc_in_json;' # at t/00-load.t line 12. # Tried to use 'Catmandu::Fix
Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'
Source: phlipple Version: 0.8.5-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): gcc -std=gnu99 -Wall -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,defs -Wl,-as-needed -Wl,--no-undefined -o phlipple camera.o engine.o game.o gfxconstants.o gradientrenderer.o interpolator.o levels.o main.o mainscreen.o osinterface_sdl.o phlipplerootscene.o quad.o quadrenderer.o scenes.o settings.o textrenderer.o texture.o vertex.o -lSDL -lvorbisfile -lGLEW -lGLU -lGL-lGLU -lGL -lSDL_mixer -lSDL_image /usr/bin/ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/phlipple_0.8.5-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768746: snapper: FTBFS in jessie: BtrfsUtils.cc:127:27: error: 'btrfs_qgroup_inherit' was not declared in this scope
Source: snapper Version: 0.2.4-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -DCONFDIR='/etc/default' -D_FILE_OFFSET_BITS=64 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c++0x -Wall -Wextra -Wformat=2 -Wnon-virtual-dtor -Wno-unused-parameter -c -o BtrfsUtils.lo BtrfsUtils.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -DCONFDIR=\/etc/default\ -D_FILE_OFFSET_BITS=64 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -std=c++0x -Wall -Wextra -Wformat=2 -Wnon-virtual-dtor -Wno-unused-parameter -c BtrfsUtils.cc -fPIC -DPIC -o .libs/BtrfsUtils.o BtrfsUtils.cc: In function 'void snapper::create_snapshot(int, int, const string, bool, snapper::qgroup_t)': BtrfsUtils.cc:127:27: error: 'btrfs_qgroup_inherit' was not declared in this scope size_t size = sizeof(btrfs_qgroup_inherit) + sizeof(((btrfs_qgroup_inherit*) 0)-qgroups[0]); ^ BtrfsUtils.cc:127:81: error: expected primary-expression before ')' token size_t size = sizeof(btrfs_qgroup_inherit) + sizeof(((btrfs_qgroup_inherit*) 0)-qgroups[0]); ^ BtrfsUtils.cc:127:83: error: expected ')' before numeric constant size_t size = sizeof(btrfs_qgroup_inherit) + sizeof(((btrfs_qgroup_inherit*) 0)-qgroups[0]); ^ BtrfsUtils.cc:127:98: error: expected ')' before ';' token size_t size = sizeof(btrfs_qgroup_inherit) + sizeof(((btrfs_qgroup_inherit*) 0)-qgroups[0]); ^ BtrfsUtils.cc:129:43: error: invalid type in declaration before '=' token struct btrfs_qgroup_inherit* inherit = (btrfs_qgroup_inherit*) buffer[0]; ^ BtrfsUtils.cc:129:67: error: expected primary-expression before ')' token struct btrfs_qgroup_inherit* inherit = (btrfs_qgroup_inherit*) buffer[0]; ^ BtrfsUtils.cc:131:15: error: request for member 'num_qgroups' in '* inherit', which is of non-class type 'int' inherit-num_qgroups = 1; ^ BtrfsUtils.cc:132:15: error: request for member 'num_ref_copies' in '* inherit', which is of non-class type 'int' inherit-num_ref_copies = 0; ^ BtrfsUtils.cc:133:15: error: request for member 'num_excl_copies' in '* inherit', which is of non-class type 'int' inherit-num_excl_copies = 0; ^ BtrfsUtils.cc:134:15: error: request for member 'qgroups' in '* inherit', which is of non-class type 'int' inherit-qgroups[0] = qgroup; ^ BtrfsUtils.cc:136:23: error: 'BTRFS_SUBVOL_QGROUP_INHERIT' was not declared in this scope args_v2.flags |= BTRFS_SUBVOL_QGROUP_INHERIT; ^ BtrfsUtils.cc:137:14: error: 'struct btrfs_ioctl_vol_args_v2' has no member named 'size' args_v2.size = size; ^ BtrfsUtils.cc:138:14: error: 'struct btrfs_ioctl_vol_args_v2' has no member named 'qgroup_inherit' args_v2.qgroup_inherit = inherit; ^ BtrfsUtils.cc: In function 'void snapper::set_default_id(int, long long unsigned int)': BtrfsUtils.cc:176:16: error: 'BTRFS_IOC_DEFAULT_SUBVOL' was not declared in this scope if (ioctl(fd, BTRFS_IOC_DEFAULT_SUBVOL, id) != 0) ^ BtrfsUtils.cc: In function 'long long unsigned int snapper::get_default_id(int)': BtrfsUtils.cc:184:33: error: aggregate 'snapper::get_default_id(int)::btrfs_ioctl_search_args args' has incomplete type and cannot be defined struct btrfs_ioctl_search_args args; ^ BtrfsUtils.cc:188:4: error: invalid use of incomplete type 'struct snapper::get_default_id(int)::btrfs_ioctl_search_key' sk-tree_id = BTRFS_ROOT_TREE_OBJECTID; ^ BtrfsUtils.cc:187:9: error: forward declaration of 'struct snapper::get_default_id(int)::btrfs_ioctl_search_key' struct btrfs_ioctl_search_key* sk = args.key; ^ BtrfsUtils.cc:188:16: error: 'BTRFS_ROOT_TREE_OBJECTID' was not declared in this scope sk-tree_id = BTRFS_ROOT_TREE_OBJECTID; ^ BtrfsUtils.cc:189:4: error: invalid use of incomplete type 'struct snapper::get_default_id(int)::btrfs_ioctl_search_key' sk-nr_items = 1; ^ BtrfsUtils.cc:187:9: error: forward declaration of 'struct
Bug#768742: psychopy: FTBFS in jessie: build-dependency not installable: libavbin0
Source: psychopy Version: 1.79.00+git16-g30c9343.dfsg-1.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install psychopy 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-psychopy-dummy : Depends: libavbin0 but it is not installable 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/ftbfs-logs/2014/11/08/psychopy_1.79.00+git16-g30c9343.dfsg-1.1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768747: canl-java: FTBFS in jessie: cp: cannot stat 'target/apidocs': No such file or directory
Source: canl-java Version: 2.1.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules binary dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_installdocs cp: cannot stat 'target/apidocs': No such file or directory dh_installdocs: cp -a target/apidocs debian/libcanl-java-doc/usr/share/doc/libcanl-java-doc returned exit code 1 make: *** [binary-indep] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/canl-java_2.1.1-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768748: liblayout-manager-perl: FTBFS in jessie: Tests failures
Source: liblayout-manager-perl Version: 0.34-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): t/15-axis/01-all.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 29 tests but ran 0. t/20-grid/00-simple.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 17 tests but ran 0. t/20-grid/01-no_height.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 17 tests but ran 0. t/20-grid/02-no_width.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 17 tests but ran 0. Files=38, Tests=1, 13 wallclock secs ( 0.15 usr 0.15 sys + 11.05 cusr 1.52 csys = 12.87 CPU) Result: FAIL Failed 37/38 test programs. 0/1 subtests failed. Makefile:787: recipe for target 'test_dynamic' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/liblayout-manager-perl_0.34-1_jessie.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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
