Bug#769211: dpkg: FTBFS in jessie: tests failed
Source: dpkg
Version: 1.17.21
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2014-11-11 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[5]: Entering directory '/«PKGBUILDDIR»/build-tree/lib/dpkg/test'
[ -z t.tmp ] || /bin/mkdir -p t.tmp
PATH=../../../src:../../../scripts:../../../utils:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
\
LC_ALL=C \
\
srcdir=../../../../lib/dpkg/test builddir=. \
PERL_DL_NONLAZY=1 \
PERL5OPT= \
/usr/bin/perl -MTAP::Harness -e ' my $harness = TAP::Harness-new({ lib =
[ ../../../../scripts ], color = 1, verbosity = 0, failures = 1, }); my
$aggregate = $harness-runtests(@ARGV); die FAIL: test suite has errors\n
if $aggregate-has_errors;' \
./t-test ./t-test-skip ./t-macros ./t-error ./t-string ./t-buffer
./t-path ./t-progname ./t-subproc ./t-command ./t-varbuf ./t-ar
./t-deb-version ./t-arch ./t-version ./t-pkginfo ./t-pkg-list ./t-pkg-queue
./t-trigger ./t-mod-db \
../../../../lib/dpkg/test/t-tar.t
./t-test ... ok
./t-test-skip .. skipped: ignore all tests
./t-macros . ok
./t-error .. ok
./t-string . ok
./t-buffer . ok
./t-path ... ok
./t-progname ... ok
./t-subproc ok
./t-command ok
./t-varbuf . ok
./t-ar . ok
./t-deb-version ok
./t-arch ... ok
./t-version ok
./t-pkginfo ok
./t-pkg-list ... ok
./t-pkg-queue .. ok
./t-trigger ok
./t-mod-db . ok
# Failed test 'tar extractor ustar is ok'
# at ../../../../lib/dpkg/test/t-tar.t line 148.
# got: '. mode=40755 time=1.0 uid=1001 gid=200
uname=user gname=group type=dir
# ./fifo mode=10750 time=1.0 uid=1001 gid=200 uname=user
gname=group type=fifo
# ./file mode=100644 time=1.0 uid=1001 gid=200 uname=user
gname=group type=file size=0
# ./hardlink mode=100644 time=1.0 uid=1001 gid=200 uname=user
gname=group type=hardlink linkto=./file size=0
# ./a mode=40755 time=1.0
uid=1001 gid=200 uname=user gname=group type=dir
# ./a/b mode=40755
time=1.0 uid=1001 gid=200 uname=user gname=group type=dir
#
./a/b/c
mode=40755 time=1.0 uid=1001 gid=200 uname=user gname=group
type=dir
#
./a/b/c/d
mode=40755 time=1.0 uid=1001 gid=200 uname=user gname=group
type=dir
#
./a/b/c/d/e
mode=40755 time=1.0 uid=1001 gid=200 uname=user gname=group
type=dir
#
./a/b/c/d/e/ff
mode=40755 time=1.0 uid=1001 gid=200 uname=user gname=group
type=dir
#
./a/b/c/d/e/ff/long
mode=100644 time=1.0 uid=1001 gid=200 uname=user gname=group
type=file size=0
# ./directory mode=40755 time=1.0 uid=1001 gid=200 uname=user
gname=group type=dir
# ./symlink-a mode=120777 time=1.0 uid=1001 gid=200
uname=user gname=group type=symlink linkto=file size=0
# ./symlink-b mode=120777 time=1.0 uid=1001 gid=200
uname=user gname=group type=symlink linkto=hardlink size=0
# ./symlink-c mode=120777 time=1.0 uid=1001 gid=200
uname=user gname=group type=symlink linkto=dangling size=0
# '
# expected: '. mode=40755 time=1.0 uid=100 gid=200
uname=user gname=group type=dir
# ./fifo mode=10750 time=1.0 uid=100 gid=200 uname=user
gname=group type=fifo
# ./file mode=100644 time=1.0 uid=100 gid=200 uname=user
gname=group type=file size=0
# ./hardlink mode=100644 time=1.0 uid=100 gid=200 uname=user
gname=group type=hardlink linkto=./file size=0
#
Bug#769214: dmtcp: FTBFS in jessie: test failures
Source: dmtcp Version: 2.3.1-5 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-2014-11-11 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[2]: Entering directory '/«PKGBUILDDIR»/contrib' make[2]: Nothing to be done for 'default'. make[2]: Leaving directory '/«PKGBUILDDIR»/contrib' make[1]: Leaving directory '/«PKGBUILDDIR»' env PWD=`pwd` ./test/autotest.py --retry-once --slow Making all in mtcp Making all in plugin /tmp/ccJfpFuf.o: In function `xtmpnam': /«PKGBUILDDIR»/test/syscall-tester.c:208: warning: the use of `tmpnam' is dangerous, better use `mkstemp' dmtcp1 Verifying there is enough disk space ... == Tests == ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp3 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp4 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp5 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsyscall-tester ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDfile1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcpaware1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDplugin-sleep2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDplugin-example-db ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDgettimeofday ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsigchild ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDshared-fd ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDstale-fd ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpoll ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDforkexec ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDwaitpid ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDclient-server ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDfrisbee ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDshared-memory ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-shm1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-shm2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-sem ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-msg ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDposix-mq1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDposix-mq2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpty2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDtimer ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDclock ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdlopen1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread3 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread4 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread5 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDgzip ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDperl ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpython ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDbash ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdash ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDscript ckpt: FAILED script root-pids: [23184] msg: checkpoint error, 4 expected, 0 found, running=0 Trying once again ckpt: FAILED openmp-1 root-pids: [23208] msg: checkpoint error, 4 expected, 0 found, running=0 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDopenmp-2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSED == Summary == ip-172-31-15-17: 42 of 43 tests passed make: *** [build-stamp] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014-11-11/dmtcp_2.3.1-5_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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766884: libxml2: lots of validity error : ID ... already defined errors with xmllint --valid
As said on https://bugzilla.gnome.org/show_bug.cgi?id=737840#c4 this affects the building process of KDE documentation. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769216: djangorestframework: FTBFS in jessie: unsatisfiable build-dependencies: python-django-guardian (= 1.1.1), python3-django-guardian (= 1.1.1)
Source: djangorestframework Version: 2.4.3-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-2014-11-11 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 djangorestframework 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-djangorestframework-dummy : Depends: python-django-guardian (= 1.1.1) but it is not installable Depends: python3-django-guardian (= 1.1.1) 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-11/djangorestframework_2.4.3-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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769212: mariadb-10.0: FTBFS in jessie: Tests failures
Source: mariadb-10.0 Version: 10.0.14-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-2014-11-11 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): 542 tests were skipped, 188 by the test itself. make[5]: *** [mysql-test/CMakeFiles/test-force] Error 1 mysql-test/CMakeFiles/test-force.dir/build.make:49: recipe for target 'mysql-test/CMakeFiles/test-force' failed make[5]: Leaving directory '/«PKGBUILDDIR»/builddir' make[4]: *** [mysql-test/CMakeFiles/test-force.dir/all] Error 2 CMakeFiles/Makefile2:9862: recipe for target 'mysql-test/CMakeFiles/test-force.dir/all' failed make[4]: Leaving directory '/«PKGBUILDDIR»/builddir' make[3]: *** [mysql-test/CMakeFiles/test-force.dir/rule] Error 2 CMakeFiles/Makefile2:9870: recipe for target 'mysql-test/CMakeFiles/test-force.dir/rule' failed make[3]: Leaving directory '/«PKGBUILDDIR»/builddir' make[2]: *** [test-force] Error 2 Makefile:3132: recipe for target 'test-force' failed make[2]: Leaving directory '/«PKGBUILDDIR»/builddir' make[1]: *** [override_dh_auto_test] Error 1 debian/rules:123: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014-11-11/mariadb-10.0_10.0.14-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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769218: gcc-4.9: FTBFS in jessie: Error! CRCs do not match! Got 264aca47, expected 95962ba4
Source: gcc-4.9
Version: 4.9.1-19
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2014-11-11 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[2]: Entering directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
rm -f src.zip
here=`pwd`; \
( \
( cd ../../../src/libjava/classpath; \
find java gnu javax org sun -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava/classpath; \
echo $file; \
done ); \
( cd ../../../src/libjava/classpath/external/sax; \
find org -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava/classpath/external/sax; \
echo $file; \
done ); \
( cd ../../../src/libjava/classpath/external/relaxngDatatype; \
find org -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava/classpath/external/relaxngDatatype; \
echo $file; \
done ); \
( cd ../../../src/libjava/classpath/external/w3c_dom; \
find org -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava/classpath/external/w3c_dom; \
echo $file; \
done ); \
( cd classpath; \
find gnu java -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo `pwd`; \
echo $file; \
done ); \
) | \
jar -cfM@ $here/src.zip
find: `java': No such file or directory
here=`pwd`; \
( \
( cd ../../../src/libjava; \
find gnu java -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava; \
echo $file; \
done ); \
) | \
jar -ufM@ $here/src.zip
make[2]: Leaving directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
touch stamps/05-build-javasrc-stamp
dh_testdir
dh_testroot
dh_installdirs -pgcj-4.9-source usr/share/java
/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
cp -p /«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava/src.zip \
debian/gcj-4.9-source/usr/share/java/libgcj-src-4.9.zip
dh_link -pgcj-4.9-source \
usr/share/java/libgcj-src-4.9.zip \
/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/src.zip
debian/dh_doclink -pgcj-4.9-source gcc-4.9-base
WARNING: removing doc directory gcj-4.9-source
debian/dh_rmemptydirs -pgcj-4.9-source
dh_compress -pgcj-4.9-source
dh_fixperms -pgcj-4.9-source
dh_gencontrol -pgcj-4.9-source -- -v4.9.1-19 '-Vlibgcc:Version=1:4.9.1-19'
'-Vgcc:Version=4.9.1-19' '-Vgcc:EpochVersion=1:4.9.1-19'
'-Vgcc:SoftVersion=4.9' '-Vgdc:Version=4.9.1-19' '-Vgcj:Version=4.9.1-19'
'-Vgcj:SoftVersion=4.9' '-Vgcj:BaseVersion=4.9' '-Vgnat:Version=4.9.1-19'
'-Vbinutils:Version=2.24.90.20141023' '-Vdep:libgcc=libgcc1 (= 1:4.9.1-19)'
'-Vdep:libgccdev=libgcc-4.9-dev (= 4.9.1-19)' '-Vdep:libgccbiarch=lib32gcc1
(= 1:4.9.1-19), libx32gcc1 (= 1:4.9.1-19)'
'-Vdep:libgccbiarchdev=lib32gcc-4.9-dev (= ${gcc:Version}), libx32gcc-4.9-dev
(= ${gcc:Version})' '-Vdep:libc=libc6 (= 2.11)' '-Vdep:libcdev=libc6-dev (=
2.13-5)' '-Vdep:libcbiarch=${shlibs:Depends}'
'-Vdep:libcbiarchdev=libc6-dev-i386 (= 2.11), libc6-dev-x32 (= 2.11)'
'-Vdep:libunwinddev=' '-Vdep:libcxxbiarchdev=lib32stdc++-4.9-dev (=
${gcc:Version}), libx32stdc++-4.9-dev (= ${gcc:Version})'
'-Vdep:libcxxbiarchdbg=lib32stdc++6-4.9-dbg (= ${gcc:Version}),
libx32stdc++6-4.9-dbg (= ${gcc:Version})' '-Vdep:libgnat='
'-Vdep:ecj=ecj-gcj, libecj-java-gcj (= 3.5.1)' '-Vdep:libcloog='
'-Vgcc:multilib=gcc-4.9-multilib' '-Vgxx:multilib=g++-4.9-multilib'
'-Vgobjc:multilib=gobjc-4.9-multilib'
'-Vgobjcxx:multilib=gobjc++-4.9-multilib'
'-Vgfortran:multilib=gfortran-4.9-multilib' '-Vdep:gold=binutils-gold (=
2.24.90.20141023)' '-Vdep:libgomp=libgomp1 (= ${gcc:Version})'
'-Vdep:libitm=libitm1 (= ${gcc:Version})' '-Vdep:libatomic=libatomic1 (=
${gcc:Version})' '-Vdep:libasan=libasan1 (= ${gcc:Version})'
'-Vdep:liblsan=liblsan0 (= ${gcc:Version})' '-Vdep:libtsan=libtsan0 (=
${gcc:Version})' '-Vdep:libubsan=libubsan0 (= ${gcc:Version})'
'-Vdep:libcilkrts=libcilkrts5 (= ${gcc:Version})'
'-Vdep:libqmath=libquadmath0 (= ${gcc:Version})'
'-Vdep:libgfortranbiarchdev=lib32gfortran-4.9-dev (= ${gcc:Version}),
libx32gfortran-4.9-dev (= ${gcc:Version})'
'-Vdep:libobjcbiarchdev=lib32objc-4.9-dev (= ${gcc:Version}),
libx32objc-4.9-dev (= ${gcc:Version})' '-Vdep:libgompbiarch=lib32gomp1 (=
${gcc:Version}), libx32gomp1 (= ${gcc:Version})'
'-Vdep:libitmbiarch=lib32itm1 (= ${gcc:Version}), libx32itm1 (=
${gcc:Version})' '-Vdep:libatomicbiarch=lib32atomic1 (= ${gcc:Version}),
libx32atomic1 (= ${gcc:Version})' '-Vdep:libasanbiarch=lib32asan1 (=
${gcc:Version}), libx32asan1 (= ${gcc:Version})'
'-Vdep:libubsanbiarch=lib32ubsan0 (=
Bug#769213: clam: FTBFS in jessie: Checking that libogg sample program links...no
Source: clam Version: 1.4.0-5.2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-2014-11-11 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»' mkdir -p /«PKGBUILDDIR»/debian/tmp/usr scons -c scons: Reading SConscript files ... Version: 1.4.0 Package version: 1.4.0 Configure phase... ### CLAM GLOBAL DEPENDENCIES CHECKING### Checking for pkg-config... yes COMPILING IN DEBUG MODE Checking for C header file pthread.h... yes Checking for pthread_join() in C library pthread... yes Checking that pthread sample program compiles...yes Checking that pthread sample program links...yes Checking that pthread sample program runs... yes # ### CLAM CORE DEPENDENCIES CHECKING ### # Checking for C++ header file xercesc/util/PlatformUtils.hpp... yes path of app: /«PKGBUILDDIR»/bin:/«PKGBUILDDIR»/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games Checking that xerces-c sample program compiles...yes Checking that xerces-c sample program links...yes Checking that xerces-c sample program runs... yes Checking for C header file ladspa.h... yes Checking that ladspa sample program compiles...yes Checking that ladspa sample program links...yes Checking that ladspa sample program runs... yes ### ### CLAM PROCESSING DEPENDENCIES CHECKING ### ### Checking for fftw3 pkg-config file... yes ### CLAM AUDIOIO DEPENDENCIES CHECKING ### Checking for C header file sndfile.h... yes Checking for sf_open_fd() in C library sndfile... yes Checking that libsndfile sample program compiles...yes Checking that libsndfile sample program links...yes Checking that libsndfile sample program runs... yes Checking for vorbisfile vorbisenc pkg-config file... yes Checking that libogg sample program compiles...yes Checking that libogg sample program links...no make[1]: *** [override_dh_auto_clean] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014-11-11/clam_1.4.0-5.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769219: debian-policy: FTBFS in jessie: emacs24 fails
Source: debian-policy Version: 3.9.6.0 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-2014-11-11 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»' nsgmls -wall -gues policy.sgml nsgmls -wall -gues menu-policy.sgml nsgmls -wall -gues perl-policy.sgml nsgmls -wall -gues upgrading-checklist.sgml LANG=C debiandoc2html policy.sgml LANG=C debiandoc2html -1 -b upgrading-checklist-1d upgrading-checklist.sgml \ mv upgrading-checklist-1d.html/index.html upgrading-checklist-1.html \ rmdir upgrading-checklist-1d.html cp -p upgrading-checklist-1.html policy.html/upgrading-checklist.html tar -czf policy.html.tar.gz policy.html LANG=C debiandoc2html menu-policy.sgml tar -czf menu-policy.html.tar.gz menu-policy.html LANG=C debiandoc2html perl-policy.sgml tar -czf perl-policy.html.tar.gz perl-policy.html LANG=C debiandoc2html upgrading-checklist.sgml tar -czf upgrading-checklist.html.tar.gz upgrading-checklist.html LANG=C debiandoc2html -1 -b policy-1d policy.sgml \ mv policy-1d.html/index.html policy-1.html \ rmdir policy-1d.html LANG=C debiandoc2html -1 -b menu-policy-1d menu-policy.sgml \ mv menu-policy-1d.html/index.html menu-policy-1.html \ rmdir menu-policy-1d.html LANG=C debiandoc2html -1 -b perl-policy-1d perl-policy.sgml \ mv perl-policy-1d.html/index.html perl-policy-1.html \ rmdir perl-policy-1d.html make[1]: 'upgrading-checklist-1.html' is up to date. LANG=C debiandoc2text policy.sgml gzip -cf9 policy.txt policy.txt.gz LANG=C debiandoc2text menu-policy.sgml gzip -cf9 menu-policy.txt menu-policy.txt.gz LANG=C debiandoc2text perl-policy.sgml gzip -cf9 perl-policy.txt perl-policy.txt.gz LANG=C debiandoc2text upgrading-checklist.sgml gzip -cf9 upgrading-checklist.txt upgrading-checklist.txt.gz LANG=C debiandoc2latexps policy.sgml gzip -cf9 policy.ps policy.ps.gz LANG=C debiandoc2latexpdf policy.sgml gzip -cf9 policy.pdf policy.pdf.gz rm menu-policy.html/index.html perl-policy.html/index.html upgrading-checklist.html/index.html upgrading-checklist.txt perl-policy.txt menu-policy.txt make[1]: Leaving directory '/«PKGBUILDDIR»' /usr/bin/make Process.html README.html \ Process.txt README.txt make[1]: Entering directory '/«PKGBUILDDIR»' emacs24 --batch -Q -l ./README-css.el -l org --visit Process.org \ --funcall org-export-as-html-batch /dev/null 21 make[1]: *** [Process.html] Error 255 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014-11-11/debian-policy_3.9.6.0_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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769215: witty: FTBFS in jessie: Error parsing arguments in: AuthModel.js
Source: witty
Version: 3.3.3+dfsg-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2014-11-11 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
cp /usr/share/asciidoc/javascripts/asciidoc.js doc/tutorial/
(cd src/js; for I in *.js; do /usr/bin/uglifyjs -c --no-seqs -nc $I
`basename $I .js`.min.js; done)
Dot
Error parsing arguments in: AuthModel.js
Dot
Error parsing arguments in: BootstrapValidate.js
Dot
Error parsing arguments in: CssThemeValidate.js
Dot
Error parsing arguments in: PopupWindow.js
Dot
Error parsing arguments in: Resizable.js
Dot
Error parsing arguments in: SizeHandle.js
Dot
Error parsing arguments in: StdGridLayoutImpl2.js
Dot
Error parsing arguments in: ToolTip.js
Dot
Error parsing arguments in: WAbstractMedia.js
Dot
Error parsing arguments in: WDateEdit.js
Dot
Error parsing arguments in: WDateValidator.js
`WDialog_center.js` is not a supported option
Supported options:
{ sequences: true,
properties: true,
dead_code: true,
drop_debugger: true,
unsafe: false,
unsafe_comps: false,
conditionals: true,
comparisons: true,
evaluate: true,
booleans: true,
loops: true,
unused: true,
hoist_funs: true,
keep_fargs: false,
hoist_vars: false,
if_return: true,
join_vars: true,
cascade: true,
side_effects: true,
pure_getters: false,
pure_funcs: null,
negate_iife: true,
screw_ie8: false,
drop_console: false,
angular: false,
warnings: true,
global_defs: {} }
Dot
Error parsing arguments in: WDialog.js
Dot
Error parsing arguments in: WDoubleValidator.js
Dot
Error parsing arguments in: WFormWidget.js
Dot
Error parsing arguments in: WGLWidget.js
Dot
Error parsing arguments in: WIntValidator.js
Dot
Error parsing arguments in: WLengthValidator.js
Dot
Error parsing arguments in: WLineEdit.js
Dot
Error parsing arguments in: WMediaPlayer.js
Dot
Error parsing arguments in: WPopupMenu.js
Dot
Error parsing arguments in: WPopupWidget.js
Dot
Error parsing arguments in: WRegExpValidator.js
Dot
Error parsing arguments in: WSpinBox.js
Dot
Error parsing arguments in: WStackedWidget.js
Dot
Error parsing arguments in: WSuggestionPopup.js
Dot
Error parsing arguments in: WTableView.js
Dot
Error parsing arguments in: WTextEdit.js
Dot
Error parsing arguments in: WTreeTable.js
Dot
Error parsing arguments in: WTreeView.js
Dot
Error parsing arguments in: WWebWidget.js
Dot
Error parsing arguments in: WtGlMatrix.js
Dot
Error parsing arguments in: WtResize.js
make: *** [build-resources] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014-11-11/witty_3.3.3+dfsg-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-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768547: gnat-gps-doc: wrong license for user guide (GPL instead of GFDL)
Source: gnat-gps Followup-For: Bug #768547 Control: tags -1 pending I have modified the com.adacore.gps.debian and org.debian.gnat-gps branches of the VCS so that the new license is unchanged and mentioned in debian/copyright. To minimize changes during the freeze, I have not removed the gnatlib/ subdirectory. The package is waiting for build reverse dependencies to be checked for installability on all architectures (dh-ada-library may have marked lib*-dev as depending on gnat-4.9.1, especially libgtkada-dev recently), but I think the issue is solved. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: gnat-gps-doc: wrong license for user guide (GPL instead of GFDL)
Processing control commands: tags -1 pending Bug #768547 [gnat-gps-doc] gnat-gps-doc: wrong license for user guide (GPL instead of GFDL) Added tag(s) pending. -- 768547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 768205 pending Bug #768205 [python-chameleon-doc] python-chameleon-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc/python-chameleon/manual/conf.py.gz Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 768205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768922: pacemaker: stopped working after upgrade to 1.1.10+git20130802-4.1
Hello! Pacemaker was compiled in unstable to a newer version of libqb0 (0.14 or 0.17). In testing/jessie there's only libqb0 (0.11). fix would be to add a libqb0 (=0.14) as dependency in package libcrmcommon3. manually updating libqb0 to the version in unstable and restart of pacemaker fixes the problem. On Mon, 10 Nov 2014 00:08:48 -0800 Frank Edelhaeuser mrpa...@gmail.com wrote: Package: pacemaker Version: 1.1.10+git20130802-4.1 Severity: grave Justification: renders package unusable Hello, After upgrading pacemaker to 1.1.10+git20130802-4.1, the cluster doesn't work any more. All resources are unavailable. Command line tools report an undefined symbol in libcrmcommon. # pacemakerd --help pacemakerd: symbol lookup error: /usr/lib/libcrmcommon.so.3: undefined symbol: qb_ipcs_connection_auth_set # crm crmd: symbol lookup error: /usr/lib/libcrmcommon.so.3: undefined symbol: qb_ipcs_connection_auth_set ERROR: crmd exited with 127 crm(live)# -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769221: serverspec-runner: can't grab templates correctly.
Package: serverspec-runner Version: 0.2.4-1 Severity: grave Justification: renders package unusable for the record, serverspec-runner searches its templates path relatively from its command script's, and assumes bad place for debian's FHS. # This package doesn't places templates, so users can't start using it from scratch. I will fix this soon.. - placing templates to /usr/share - patching script to search above location regards, -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-30-pve (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages serverspec-runner depends on: ii bundler 1.7.4-1 ii rake 10.3.2-2 ii ruby 1:2.1.0.4 ii ruby-net-ssh 1:2.9.1-1 ii ruby-rspec-core 2.14.7-2 ii ruby-serverspec 1.14.0-2 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-2 ii ruby2.0 [ruby-interpreter]2.0.0.484+really457-3 ii ruby2.1 [ruby-interpreter]2.1.4-1 serverspec-runner recommends no packages. serverspec-runner suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768699: [pkg-apparmor] Bug#768699: apparmor-profiles-extra: FTBFS in jessie: Tests failures
Lucas Nussbaum wrote (11 Nov 2014 16:50:23 GMT) : I can confirm that it builds fine with a newer kernel. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Correct control syntax
Processing commands for cont...@bugs.debian.org:
fixed 768722 6.0-2
Bug #768722 {Done: Mattias Ellert mattias.ell...@fysast.uu.se} [src:myproxy]
myproxy: FTBFS in jessie: tests failures
Marked as fixed in versions myproxy/6.0-2.
End of message, stopping processing here.
Please contact me if you need assistance.
--
768722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 767504 with 767846
Processing commands for cont...@bugs.debian.org: block 767504 with 767846 Bug #767504 [mpd] mpd: licence clash with libmp4v2 (MPL) and mpd GPL-+2 767504 was not blocked by any bugs. 767504 was not blocking any bugs. Added blocking bug(s) of 767504: 767846 thanks Stopping processing here. Please contact me if you need assistance. -- 767504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767554: python-persistent and python-zodb: error when trying to install together
Hello, Andreas Beckmann a...@debian.org writes: Package: python-persistent,python-zodb Version: 4.0.8-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 1:3.9.7-2 First of all, thanks for finding and reporting such issues, it's greatly appreciated! Selecting previously unselected package python-zodb. Preparing to unpack .../python-zodb_1%3a3.9.7-2_amd64.deb ... Unpacking python-zodb (1:3.9.7-2) ... dpkg: error processing archive /var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/wref.py', which is also in package python-persistent 4.0.8-1 Errors were encountered while processing: /var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/lib/python2.7/dist-packages/persistent/__init__.py [...] From upstream point of view, ZODB3 (aka python-zodb in Debian) used to include persistent, BTrees, ZODB and ZEO modules. However, since ZODB3 3.11.0a1, upstream has split it up into 4 distinct packages (one for each module), bump the version to 4.0 and made ZODB3 a metapackage depending on all of them. As of fixing this RC bug for Jessie: Among the four, only persistent package is currently available in Debian, so there is no way to get rid of ZODB3 (at least for Jessie). Barry: If persistent = 4.0 Debian package is useful on its own to anyone (and thus should not be removed From testing), then can I add a Conflict on both packages and upload them to fix this bug? Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature
Bug#769211: dpkg: FTBFS in jessie: tests failed
Hi! On Wed, 2014-11-12 at 08:53:28 +0100, Lucas Nussbaum wrote: Source: dpkg Version: 1.17.21 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-2014-11-11 qa-ftbfs Justification: FTBFS in jessie on amd64 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[5]: Entering directory '/«PKGBUILDDIR»/build-tree/lib/dpkg/test' # Failed test 'tar extractor ustar is ok' # at ../../../../lib/dpkg/test/t-tar.t line 148. # got: '. mode=40755 time=1.0 uid=1001 gid=200 uname=user gname=group type=dir […] # ' # expected: '. mode=40755 time=1.0 uid=100 gid=200 uname=user gname=group type=dir […] # ' Ok, the uid differs, and that's because *that* build system does have a user “user”, and the tar code in dpkg always prefers to use the system uid instead of the one provided by the tarball. I'll fix the test case for 1.17.22. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769093: marked as done (Please stop build-depending on libcatalyst-engine-psgi-perl which will be removed)
Your message dated Wed, 12 Nov 2014 09:19:35 +
with message-id e1xou5p-0002y0...@franck.debian.org
and subject line Bug#769093: fixed in libcatalyst-perl 5.90075-2
has caused the Debian Bug report #769093,
regarding Please stop build-depending on libcatalyst-engine-psgi-perl which
will be removed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
769093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libcatalyst-engine-psgi-perl
Version: 0.13+dfsg-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 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
'/«BUILDDIR»/libcatalyst-engine-psgi-perl-0.13+dfsg'
PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -MTest::Harness
-e undef *Test::Harness::Switches; test_harness(0, 'inc', 'blib/lib',
'blib/arch') t/*.t
Possible precedence issue with control flow operator at
/«BUILDDIR»/libcatalyst-engine-psgi-perl-0.13+dfsg/inc/Test/Builder.pm line
917.
t/00_compile.t ... ok
Possible precedence issue with control flow operator at
/«BUILDDIR»/libcatalyst-engine-psgi-perl-0.13+dfsg/inc/Test/Builder.pm line
917.
[debug] Debug messages enabled
[debug] Statistics enabled
Term::Size::Any is not installed, can't autodetect terminal column width
Trouble trying to detect your terminal size, looking at $ENV{COLUMNS}
Cannot determine desired terminal width, using default of 80 columns
[debug] Loaded PSGI Middleware:
..
| Catalyst::Middleware::Stash|
| Plack::Middleware::HTTPExceptions |
| Plack::Middleware::RemoveRedundantBody 0.04 |
| Plack::Middleware::FixMissingBodyInRedirect 0.10 |
| Plack::Middleware::ContentLength |
| Plack::Middleware::MethodOverride 0.10|
| Plack::Middleware::Head|
''
[debug] Loaded Request Data Handlers:
..
| application/x-www-form-urlencoded |
| application/json |
''
[debug] Loaded dispatcher Catalyst::Dispatcher
[debug] Loaded engine Catalyst::Engine
[debug] Found home
/«BUILDDIR»/libcatalyst-engine-psgi-perl-0.13+dfsg/t/Hello
[debug] Loaded components:
.-+--.
| Class | Type |
+-+--+
| Hello::Controller::Metalic | instance |
| Hello::Controller::Root | instance |
'-+--'
[debug] Loaded Private actions:
.--+--+--.
| Private | Class| Method |
+--+--+--+
| /welcome | Hello::Controller::Root | welcome |
| /default | Hello::Controller::Root | default |
| /headers | Hello::Controller::Root | headers |
| /index | Hello::Controller::Root | index|
| /end | Hello::Controller::Root | end |
'--+--+--'
[debug] Loaded Path actions:
.-+--.
| Path| Private |
+-+--+
| / | /index |
| /...| /default
Bug#768205: marked as done (python-chameleon-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc/python-chameleon/manual/conf.py.gz)
Your message dated Wed, 12 Nov 2014 09:21:13 + with message-id e1xou6z-0003zz...@franck.debian.org and subject line Bug#768205: fixed in python-chameleon 2.16-4 has caused the Debian Bug report #768205, regarding python-chameleon-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc/python-chameleon/manual/conf.py.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-chameleon-doc Version: 2.16-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package python-chameleon-doc. Unpacking python-chameleon-doc (from .../python-chameleon-doc_2.16-3_all.deb) ... dpkg: error processing /var/cache/apt/archives/python-chameleon-doc_2.16-3_all.deb (--unpack): trying to overwrite '/usr/share/doc/python-chameleon/manual/conf.py.gz', which is also in package python-chameleon 2.6.1-1 Errors were encountered while processing: /var/cache/apt/archives/python-chameleon-doc_2.16-3_all.deb cheers, Andreas python-chameleon=2.6.1-1_python-chameleon-doc=2.16-3.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: python-chameleon Source-Version: 2.16-4 We believe that the bug you reported is fixed in the latest version of python-chameleon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arnaud Fontaine ar...@debian.org (supplier of updated python-chameleon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 12 Nov 2014 16:37:07 +0900 Source: python-chameleon Binary: python-chameleon python3-chameleon python-chameleon-doc Architecture: source all Version: 2.16-4 Distribution: unstable Urgency: medium Maintainer: Debian/Ubuntu Zope Team pkg-zope-develop...@lists.alioth.debian.org Changed-By: Arnaud Fontaine ar...@debian.org Description: python-chameleon - XML-based template compiler python-chameleon-doc - XML-based template compiler python3-chameleon - XML-based template compiler Closes: 768205 Changes: python-chameleon (2.16-4) unstable; urgency=medium . * Team upload. * d/control: Add missing python-chameleon-doc Breaks/Replaces against python-chameleon. Thanks to Andreas Beckmann. Closes: #768205. Checksums-Sha1: c6cbcc54a4d3d82e150217662008970a7e659245 2313 python-chameleon_2.16-4.dsc c2d4cc298eba48b4ec29c317f403fbe61be28184 4616 python-chameleon_2.16-4.debian.tar.xz 077be9efa2507b4f91ae156815435934ef817bd1 132422 python-chameleon_2.16-4_all.deb eccc5561f75d530741d596a0197a0b1cefbe338a 132586 python3-chameleon_2.16-4_all.deb 7e595b4b4a530648454111d77c58d4b205423b8d 43170 python-chameleon-doc_2.16-4_all.deb Checksums-Sha256: 8c988b2c4984de2f0e1033045f1541d36627088f6a0677f83b534db8fdcf9cfa 2313 python-chameleon_2.16-4.dsc cd92ea67d565a372a425f7a2c4f1edf6081a72ce93a12d181e7781bc614d6509 4616 python-chameleon_2.16-4.debian.tar.xz c7193dca2e085f082ded4b15c79a59d6791aeeb3c22657596400268c982c5f4c 132422 python-chameleon_2.16-4_all.deb c1bc5ab1110b5998b9619b7a2dd69a2adb53da2ef6ab5f785bc5619271e2ea61 132586 python3-chameleon_2.16-4_all.deb ecf20cb2c072c05f449e8a7d1253b1281d02a1d00a7d7f4695c2704262dbf8ea 43170 python-chameleon-doc_2.16-4_all.deb Files: 4ee74b647e647cf48fa65b05ce347806 2313 python optional python-chameleon_2.16-4.dsc 89821871b6d307526481f8183b2bd062 4616 python optional python-chameleon_2.16-4.debian.tar.xz 6375e159104b1157652b8eaa1ff988d0 132422 python optional python-chameleon_2.16-4_all.deb 2f6ee86139288cd55738816cfdc72101 132586 python optional
Bug#768769: marked as done (plastimatch: FTBFS in jessie: Tests failures)
Your message dated Wed, 12 Nov 2014 09:21:04 + with message-id e1xou6q-0003wa...@franck.debian.org and subject line Bug#768769: fixed in plastimatch 1.5.16+dfsg-2 has caused the Debian Bug report #768769, regarding plastimatch: FTBFS in jessie: Tests failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: plastimatch Version: 1.5.16+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): Start 286: plm-sift-a-check-1 Start 287: plm-sift-a-check-2 351/352 Test #286: plm-sift-a-check-1 Passed0.02 sec 352/352 Test #287: plm-sift-a-check-2 Passed0.02 sec 99% tests passed, 3 tests failed out of 352 Total Test time (real) = 41.57 sec The following tests FAILED: 297 - plm-union (Failed) 298 - plm-union-stats (Failed) 299 - plm-union-check (Failed) Errors while running CTest make[2]: *** [test] Error 8 Makefile:140: recipe for target 'test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/plastimatch_1.5.16+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. ---End Message--- ---BeginMessage--- Source: plastimatch Source-Version: 1.5.16+dfsg-2 We believe that the bug you reported is fixed in the latest version of plastimatch, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated plastimatch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 12 Nov 2014 08:24:38 +0100 Source: plastimatch Binary: plastimatch Architecture: source amd64 Version: 1.5.16+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: plastimatch - medical image reconstruction and registration Closes: 768769 Changes: plastimatch (1.5.16+dfsg-2) unstable; urgency=medium . * Add needed cmake dependencies to enable parallel builds (thanks to Colin Watson cjwat...@debian.org for the patch) Closes: #768769 Checksums-Sha1: 921525e709dcf57f2bf8844962298830c083a945 2301 plastimatch_1.5.16+dfsg-2.dsc 70df4762dd24707d4c3ab1fd0a46d338a0012192 7888 plastimatch_1.5.16+dfsg-2.debian.tar.xz bc9fd9c6e008e56004dbf61ddaaf39a6f4c1d2f1 6628120 plastimatch_1.5.16+dfsg-2_amd64.deb Checksums-Sha256: c76394df0afc2f4e5df210e219f0d82701b55c80ff33c16b55ed50b16f8863d3 2301 plastimatch_1.5.16+dfsg-2.dsc 5ebead64bb640d8e08918da1f711a0851d1606d37f4dee2b1391656d432990ba 7888 plastimatch_1.5.16+dfsg-2.debian.tar.xz 9d0cc6c5fa8ccbac6c37d40602f5874b6f678d4067569a4e2c5cc8eaaac7d4b2 6628120 plastimatch_1.5.16+dfsg-2_amd64.deb Files: e2736e279ba7e0629a3283844466a86e 2301 science optional plastimatch_1.5.16+dfsg-2.dsc fe676855a5722891cc4d90812abebcd0 7888 science optional plastimatch_1.5.16+dfsg-2.debian.tar.xz b6663af9f0fc0241b88a85f1cca022ae 6628120 science optional plastimatch_1.5.16+dfsg-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUYxJAAAoJEFeKBJTRxkbRR2kP/RX3f9UXNBCk/QfT77D9Mz5J 9OUpzbxYo07/hZROUpvkWkZ/1e9zLhG9cS6vT42du2RbcC+kTRNR3lrs1Lc+TS34 vNrBaNP1c1bO14QqIt/9FBwgxyM2oLTkRdoMMmaxUq69GsBBzt7uSol5yU0CsJMl +vlndQ7GztGWQVxgBDYl99Upq7whUb8qnRnaf8bNdy+bO8iWcn0bcJ4qtUnt8d51
Processed: Re: Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
Processing control commands: reassign -1 src:python-defaults Bug #769106 [python2.7-minimal] python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook. Bug reassigned from package 'python2.7-minimal' to 'src:python-defaults'. No longer marked as found in versions python2.7/2.7.8-11. Ignoring request to alter fixed versions of bug #769106 to the same values previously set tags -1 + moreinfo Bug #769106 [src:python-defaults] python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook. Added tag(s) moreinfo. -- 769106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
Control: reassign -1 src:python-defaults Control: tags -1 + moreinfo Am 11.11.2014 um 12:38 schrieb Andreas Beckmann: Package: python2.7-minimal Version: 2.7.8-11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails. From the attached log (scroll to the bottom...): Setting up python2.7-minimal (2.7.8-11) ... python or pycompile not found in public_modules.rtinstall hook. dpkg: error processing package python2.7-minimal (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: python2.7-minimal This was observed during an upgrade test of texlive-music. looks like python wasn't installed into jessie at all, and then is newly installed. Looking at the build log, you see that Selecting previously unselected package python. (Reading database ... 14654 files and directories currently installed.) Preparing to unpack .../python_2.7.8-1_amd64.deb ... Unpacking python (2.7.8-1) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.8-11_amd64.deb ... Unpacking python2.7 (2.7.8-11) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.8-11_amd64.deb ... Unpacking python2.7-minimal (2.7.8-11) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.8-11_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.8-11) ... Setting up libpython2.7-minimal:amd64 (2.7.8-11) ... Setting up python2.7-minimal (2.7.8-11) ... python or pycompile not found in public_modules.rtinstall hook. dpkg: error processing package python2.7-minimal (--configure): subprocess installed post-installation script returned error exit status 1 Note that python-minimal isn't yet touched, although python depends on it. Wondering why this is not seen for updates to wheezy, and wondering if that could be resolved if python would pre-depend on python-minimal. -- To UNSUBSCRIBE, email to debian-bugs-rc-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
Hello, I must confess that I fail to reproduce your bug. it seems to me that the bug comes from a strange setting in LC_ALL. before the java compiler, msggrep complains that ANSI_X3.4-1968 is not a valid value for UTF-encoded files. Did your chroot have any unconventional settings with that regard? Thanks for any additional info, Mt On Sun, Nov 09, 2014 at 08:14:08AM +0100, Lucas Nussbaum wrote: 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]
Bug#769236: android-platform-frameworks-base: FTBFS in jessie/i386: libutils.so: undefined reference to `android_atomic_or'
Source: android-platform-frameworks-base Version: 21-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): g++ -fPIC -Wl,-rpath=/usr/lib/android -Wl,-z,relro -o aapt AaptAssets.o Command.o CrunchCache.o FileFinder.o Main.o Package.o StringPool.o XMLNode.o ResourceFilter.o ResourceTable.o Images.o Resource.o SourcePos.o ZipEntry.o ZipFile.o -lrt -ldl -lpthread -lz -lexpat -lpng -L/usr/lib/android -lcutils -lhost -llog -lutils -L../../libs/androidfw -landroidfw /usr/lib/android/libutils.so: undefined reference to `android_atomic_or' /usr/lib/android/libutils.so: undefined reference to `android_atomic_dec' /usr/lib/android/libutils.so: undefined reference to `android_atomic_inc' /usr/lib/android/libutils.so: undefined reference to `android_atomic_release_cas' /usr/lib/android/libutils.so: undefined reference to `android_atomic_add' collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/android-platform-frameworks-base_21-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769239: kgb-bot: FTBFS in jessie/i386: Tests failures
Source: kgb-bot Version: 1.33-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): Non-zero exit status: 1 t/55-client-git-merges-ff.t (Wstat: 256 Tests: 14 Failed: 1) Failed test: 14 Non-zero exit status: 1 t/56-client-git-ff-merge-2.t (Wstat: 256 Tests: 15 Failed: 1) Failed test: 15 Non-zero exit status: 1 t/57-client-git-squash-tags.t (Wstat: 256 Tests: 9 Failed: 1) Failed test: 9 Non-zero exit status: 1 Files=16, Tests=268, 23 wallclock secs ( 0.10 usr 0.10 sys + 14.70 cusr 6.08 csys = 20.98 CPU) Result: FAIL Failed 4/16 test programs. 4/268 subtests failed. dh_auto_test: perl Build test returned exit code 255 make[1]: *** [override_dh_auto_test] Error 255 debian/rules:12: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/kgb-bot_1.33-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769241: python-crypto: FTBFS in jessie/i386: Tests failures
Source: python-crypto
Version: 2.6.1-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
core.setup(**kw)
File /usr/lib/python2.7/distutils/core.py, line 151, in setup
dist.run_commands()
File /usr/lib/python2.7/distutils/dist.py, line 953, in run_commands
self.run_command(cmd)
File /usr/lib/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File setup.py, line 331, in run
SelfTest.run(module=moduleObj, verbosity=self.verbose, stream=sys.stdout,
config=self.config)
File
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/Crypto/SelfTest/__init__.py,
line 76, in run
raise SelfTestError(Self-test failed, result)
Crypto.SelfTest.SelfTestError: ('Self-test failed',
unittest.runner.TextTestResult run=1071 errors=1 failures=0)
E: pybuild pybuild:256: test: plugin custom failed with: exit code=1:
python2.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 2.7 -s custom
--test-args={interpreter} setup.py test --dir . returned exit code 13
make[1]: *** [override_dh_auto_test] Error 13
debian/rules:21: recipe for target 'override_dh_auto_test' failed
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/12/python-crypto_2.6.1-5_jessie-i386.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-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769240: libcatalyst-controller-formbuilder-perl: FTBFS in jessie/i386: Tests failures
Source: libcatalyst-controller-formbuilder-perl Version: 0.06-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): # Testing Catalyst::Controller::FormBuilder 0.06 t/00-load.t ok [error] Caught exception in TestApp::Controller::Books-basic Can't locate object method param_fetch via package Catalyst::Request at /usr/share/perl5/CGI/FormBuilder/Field.pm line 192. [error] Caught exception in TestApp::Component::Rendered-process Can't call method render on an undefined value at /«PKGBUILDDIR»/t/lib/TestApp/Component/Rendered.pm line 9. # Failed test 'GET /books/basic' # at t/01-basic.t line 11. # 500 # Internal Server Error # Failed test 'Form found' # at t/01-basic.t line 14. Bailout called. Further testing stopped: Can't do anything without a form FAILED--Further testing stopped: Can't do anything without a form make[1]: *** [test_dynamic] Error 255 Makefile:761: recipe for target 'test_dynamic' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/libcatalyst-controller-formbuilder-perl_0.06-2_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769238: xaos: FTBFS in jessie/i386: zoom.c:156:18: error: conflicting types for 'fillline_8'
Source: xaos Version: 3.5+ds1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -march=pentiumpro -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/«BUILDDIR»/xaos-3.5+ds1/src/include -c -o zoom.o zoom.c zoom.c:156:18: error: conflicting types for 'fillline_8' #define fillline fillline_8 ^ zoomd.c:283:20: note: in expansion of macro 'fillline' static INLINE void fillline(int line) ^ zoom.c:144:13: note: previous declaration of 'fillline_8' was here static void fillline_8(int line) REGISTERS(0); ^ zoom.c:163:18: error: conflicting types for 'fillline_32' #define fillline fillline_32 ^ zoomd.c:283:20: note: in expansion of macro 'fillline' static INLINE void fillline(int line) ^ zoom.c:147:13: note: previous declaration of 'fillline_32' was here static void fillline_32(int line) REGISTERS(0); ^ zoom.c:170:18: error: conflicting types for 'fillline_24' #define fillline fillline_24 ^ zoomd.c:283:20: note: in expansion of macro 'fillline' static INLINE void fillline(int line) ^ zoom.c:146:13: note: previous declaration of 'fillline_24' was here static void fillline_24(int line) REGISTERS(0); ^ zoom.c:177:18: error: conflicting types for 'fillline_16' #define fillline fillline_16 ^ zoomd.c:283:20: note: in expansion of macro 'fillline' static INLINE void fillline(int line) ^ zoom.c:145:13: note: previous declaration of 'fillline_16' was here static void fillline_16(int line) REGISTERS(0); ^ zoom.c:937:1: error: conflicting types for 'moveoldpoints' moveoldpoints(void /*@unused@ */ *data1, ^ zoom.c:142:1: note: previous declaration of 'moveoldpoints' was here moveoldpoints(void *data1, struct taskinfo *task, int r1, int r2) ^ make[3]: *** [zoom.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/xaos_3.5+ds1-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769242: samba: FTBFS in jessie/i386: rm: cannot remove '/«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/share/man/man1/vfstest.1': No such file or directory
Source: samba Version: 2:4.1.13+dfsg-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): # Included in python-tevent rm /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/lib/python*/*-packages/_tevent.so rm /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/lib/python*/*-packages/tevent.py # Already included in various system packages rm -r /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/lib/python*/*-packages/samba/external # Already documented in debian/copyright rm /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/share/samba/setup/ad-schema/licence.txt # System ldb loads its modules from a different path mkdir -p /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/lib/i386-linux-gnu/ldb/modules/ldb ln -sf ../../../samba/ldb /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/lib/i386-linux-gnu/ldb/modules/ldb/samba # pam stuff mkdir -p /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/share/pam-configs install -m 0644 debian/libpam-smbpass.pam-config /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/share/pam-configs/smbpasswd-migrate install -m 0644 debian/winbind.pam-config /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/share/pam-configs/winbind mv /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/lib/i386-linux-gnu/libnss_* /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/lib/i386-linux-gnu/ # we don't ship the symlinks rm /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/lib/i386-linux-gnu/libnss_*.so #Remove unused ldb share configuration plugin rm /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/lib/i386-linux-gnu/samba/share/ldb.so #Remove unused vfstest manpage as there is no more vfstest apparently rm /«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/share/man/man1/vfstest.1 rm: cannot remove '/«BUILDDIR»/samba-4.1.13+dfsg/debian/tmp/usr/share/man/man1/vfstest.1': No such file or directory make[1]: *** [override_dh_install] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/samba_4.1.13+dfsg-2_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769237: mipp: FTBFS in jessie/i386: Tests failures
Source: mipp Version: 0.9.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): == FAIL: test_mtsat (test_xrit.Test) -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/test_xrit.py, line 119, in test_mtsat cross_sum, mtsat_sum)) AssertionError: MTSAT image reading/slicing failed, wrong cross_sum (11148104.000 != 11148074.000) -- Ran 9 tests in 1.220s FAILED (failures=2) ['/«PKGBUILDDIR»/build/lib.linux-i686-2.7', '/«PKGBUILDDIR»/tests', '', '/«PKGBUILDDIR»', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-i386-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages'] make[1]: *** [override_dh_auto_test] Error 1 debian/rules:21: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/mipp_0.9.1-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769250: python-dugong: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit code 13
Source: python-dugong Version: 3.3+dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): make[1]: Entering directory '/«BUILDDIR»/python-dugong-3.3+dfsg' dh_auto_build I: pybuild base:170: /usr/bin/python3 setup.py build running build running build_py creating /«BUILDDIR»/python-dugong-3.3+dfsg/.pybuild/pythonX.Y_3.4/build/dugong copying ./dugong/__init__.py - /«BUILDDIR»/python-dugong-3.3+dfsg/.pybuild/pythonX.Y_3.4/build/dugong # Build docs python3 setup.py build_sphinx running build_sphinx creating /«BUILDDIR»/python-dugong-3.3+dfsg/doc/doctrees creating /«BUILDDIR»/python-dugong-3.3+dfsg/doc/html Running Sphinx v1.2.3 loading pickled environment... failed: [Errno 2] No such file or directory: '/«BUILDDIR»/python-dugong-3.3+dfsg/doc/doctrees/environment.pickle' loading intersphinx inventory from ../debian/python.inv... building [html]: targets for 7 source files that are out of date updating environment: 7 added, 0 changed, 0 removed reading sources... [ 14%] api reading sources... [ 28%] coroutines reading sources... [ 42%] index reading sources... [ 57%] intro reading sources... [ 71%] issues reading sources... [ 85%] tutorial reading sources... [100%] whatsnew looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done writing output... [ 14%] api writing output... [ 28%] coroutines writing output... [ 42%] index writing output... [ 57%] intro writing output... [ 71%] issues writing output... [ 85%] tutorial writing output... [100%] whatsnew writing additional files... genindex search copying static files... done copying extra files... done dumping search index... done dumping object inventory... done build succeeded. make[1]: Leaving directory '/«BUILDDIR»/python-dugong-3.3+dfsg' dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: cd /«BUILDDIR»/python-dugong-3.3+dfsg/.pybuild/pythonX.Y_3.4/build; python3.4 -m pytest /«BUILDDIR»/python-dugong-3.3+dfsg/test/ = test session starts == platform linux -- Python 3.4.2 -- py-1.4.25 -- pytest-2.6.3 -- /usr/bin/python3.4 collecting ... collected 106 items ../../../test/test_aio.py::test_aio_future PASSED ../../../test/test_dugong.py::test_connect_ssl SKIPPED ../../../test/test_dugong.py::test_invalid_ssl SKIPPED ../../../test/test_dugong.py::test_get_pipeline[plain] PASSED ../../../test/test_dugong.py::test_ssl_info[plain] PASSED ../../../test/test_dugong.py::test_blocking_send[plain] PASSED ../../../test/test_dugong.py::test_blocking_read[plain] PASSED ../../../test/test_dugong.py::test_discard[plain] PASSED ../../../test/test_dugong.py::test_discard_chunked[plain] PASSED ../../../test/test_dugong.py::test_read_text[plain] PASSED ../../../test/test_dugong.py::test_read_text2[plain] PASSED ../../../test/test_dugong.py::test_read_text3[plain] PASSED ../../../test/test_dugong.py::test_read_identity[plain] PASSED ../../../test/test_dugong.py::test_exhaust_buffer[plain] PASSED ../../../test/test_dugong.py::test_full_buffer[plain] PASSED ../../../test/test_dugong.py::test_readinto_identity[plain] PASSED ../../../test/test_dugong.py::test_read_chunked[plain] PASSED ../../../test/test_dugong.py::test_read_chunked2[plain] PASSED ../../../test/test_dugong.py::test_readinto_chunked[plain] PASSED ../../../test/test_dugong.py::test_double_read[plain] PASSED ../../../test/test_dugong.py::test_read_raw[plain] PASSED ../../../test/test_dugong.py::test_abort_read[plain] PASSED ../../../test/test_dugong.py::test_abort_co_read[plain] PASSED ../../../test/test_dugong.py::test_abort_write[plain] PASSED ../../../test/test_dugong.py::test_write_toomuch[plain] PASSED ../../../test/test_dugong.py::test_write_toolittle[plain] PASSED ../../../test/test_dugong.py::test_write_toolittle2[plain] PASSED ../../../test/test_dugong.py::test_write_toolittle3[plain] PASSED ../../../test/test_dugong.py::test_put[plain] PASSED ../../../test/test_dugong.py::test_put_separate[plain] PASSED ../../../test/test_dugong.py::test_100cont[plain] PASSED ../../../test/test_dugong.py::test_100cont_2[plain] PASSED ../../../test/test_dugong.py::test_100cont_3[plain] PASSED ../../../test/test_dugong.py::test_aborted_write1[plain] PASSED ../../../test/test_dugong.py::test_aborted_write2[plain] PASSED ../../../test/test_dugong.py::test_tunnel[plain] PASSED ../../../test/test_dugong.py::test_read_toomuch[plain] PASSED ../../../test/test_dugong.py::test_read_toolittle[plain] PASSED ../../../test/test_dugong.py::test_empty_response[plain] PASSED ../../../test/test_dugong.py::test_head[plain] PASSED ../../../test/test_dugong.py
Bug#769245: libcatmandu-store-lucy-perl: FTBFS in jessie/i386: build-dependency not installable: libcatmandu-perl
Source: libcatmandu-store-lucy-perl Version: 0.0101-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ┌──┐ │ Install libcatmandu-store-lucy-perl 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-libcatmandu-store-lucy-perl-dummy : Depends: libcatmandu-perl 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/12/libcatmandu-store-lucy-perl_0.0101-3_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769246: libcatmandu-importer-getjson-perl: FTBFS in jessie/i386: build-dependency not installable: libcatmandu-perl
Source: libcatmandu-importer-getjson-perl Version: 0.40-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ┌──┐ │ Install libcatmandu-importer-getjson-perl 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-libcatmandu-importer-getjson-perl-dummy : Depends: libcatmandu-perl 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/12/libcatmandu-importer-getjson-perl_0.40-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769252: libcatmandu-atom-perl: FTBFS in jessie/i386: build-dependency not installable: libcatmandu-perl
Source: libcatmandu-atom-perl Version: 0.02-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ┌──┐ │ Install libcatmandu-atom-perl 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-libcatmandu-atom-perl-dummy : Depends: libcatmandu-perl 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/12/libcatmandu-atom-perl_0.02-2_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769249: gf2x: FTBFS in jessie/i386: emmintrin.h:1145:1: error: inlining failed in call to always_inline '_mm_slli_epi64': target specific option mismatch
Source: gf2x Version: 1.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): /bin/bash ./libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I./gf2x -I. -I. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -W -c -o gf2x.lo gf2x.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I./gf2x -I. -I. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -W -c gf2x.c -fPIC -DPIC -o .libs/gf2x.o gf2x.c: In function 'gf2x_mul_pool_init': gf2x.c:82:24: warning: argument to 'sizeof' in 'memset' call is the same expression as the destination; did you mean to dereference it? [-Wsizeof-pointer-memaccess] memset(p, 0, sizeof(p)); ^ In file included from gf2x/gf2x-small.h:102:0, from gf2x.c:31: ./gf2x/gf2x_mul3.h: In function 'gf2x_mul3': ./gf2x/gf2x_mul3.h:69:19: warning: SSE vector return without SSE enabled changes the ABI [-Wpsabi] #define SHL(x, r) _mm_slli_epi64((x), (r)) ^ ./gf2x/gf2x_mul3.h:82:12: note: in expansion of macro 'SHL' g[2] = SHL(g[1], 1); ^ In file included from ./gf2x/gf2x_mul3.h:34:0, from gf2x/gf2x-small.h:102, from gf2x.c:31: /usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1145:1: error: inlining failed in call to always_inline '_mm_slli_epi64': target specific option mismatch _mm_slli_epi64 (__m128i __A, int __B) ^ In file included from gf2x/gf2x-small.h:102:0, from gf2x.c:31: ./gf2x/gf2x_mul3.h:69:19: error: called from here #define SHL(x, r) _mm_slli_epi64((x), (r)) ^ ./gf2x/gf2x_mul3.h:82:12: note: in expansion of macro 'SHL' g[2] = SHL(g[1], 1); ^ In file included from ./gf2x/gf2x_mul3.h:34:0, from gf2x/gf2x-small.h:102, from gf2x.c:31: /usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1145:1: error: inlining failed in call to always_inline '_mm_slli_epi64': target specific option mismatch _mm_slli_epi64 (__m128i __A, int __B) ^ In file included from gf2x/gf2x-small.h:102:0, from gf2x.c:31: ./gf2x/gf2x_mul3.h:69:19: error: called from here #define SHL(x, r) _mm_slli_epi64((x), (r)) ^ ./gf2x/gf2x_mul3.h:84:12: note: in expansion of macro 'SHL' g[4] = SHL(g[2], 1); ^ In file included from ./gf2x/gf2x_mul3.h:34:0, from gf2x/gf2x-small.h:102, from gf2x.c:31: /usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1145:1: error: inlining failed in call to always_inline '_mm_slli_epi64': target specific option mismatch _mm_slli_epi64 (__m128i __A, int __B) ^ In file included from gf2x/gf2x-small.h:102:0, from gf2x.c:31: ./gf2x/gf2x_mul3.h:69:19: error: called from here #define SHL(x, r) _mm_slli_epi64((x), (r)) ^ ./gf2x/gf2x_mul3.h:86:12: note: in expansion of macro 'SHL' g[6] = SHL(g[3], 1); ^ In file included from ./gf2x/gf2x_mul3.h:34:0, from gf2x/gf2x-small.h:102, from gf2x.c:31: /usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1145:1: error: inlining failed in call to always_inline '_mm_slli_epi64': target specific option mismatch _mm_slli_epi64 (__m128i __A, int __B) ^ In file included from gf2x/gf2x-small.h:102:0, from gf2x.c:31: ./gf2x/gf2x_mul3.h:69:19: error: called from here #define SHL(x, r) _mm_slli_epi64((x), (r)) ^ ./gf2x/gf2x_mul3.h:88:12: note: in expansion of macro 'SHL' g[8] = SHL(g[4], 1); ^ In file included from ./gf2x/gf2x_mul3.h:34:0, from gf2x/gf2x-small.h:102, from gf2x.c:31: /usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1145:1: error: inlining failed in call to always_inline '_mm_slli_epi64': target specific option mismatch _mm_slli_epi64 (__m128i __A, int __B) ^ In file included from gf2x/gf2x-small.h:102:0, from gf2x.c:31: ./gf2x/gf2x_mul3.h:69:19: error: called from here #define SHL(x, r) _mm_slli_epi64((x), (r)) ^ ./gf2x/gf2x_mul3.h:90:13: note: in expansion of macro 'SHL' g[10] = SHL(g[5], 1); ^ In file included from ./gf2x/gf2x_mul3.h:34:0, from gf2x/gf2x-small.h:102, from gf2x.c:31: /usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1145:1: error: inlining failed in call to always_inline '_mm_slli_epi64': target specific option mismatch _mm_slli_epi64 (__m128i __A, int __B) ^ In file included from gf2x/gf2x-small.h
Bug#769248: androidsdk-tools: FTBFS in jessie/i386: sdkstats/src/main/java/com/android/sdkstats/DdmsPreferenceStore.java:22: error: package org.eclipse.jface.preference does not exist
Source: androidsdk-tools Version: 22.2+git20130830~92d25d6-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): debian/rules build test -x debian/rules mkdir -p . jh_linkjars jh_build -J find common/src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javac -g -cp androidsdk-common.jar:androidsdk-ddmlib.jar:androidsdk-ddmuilib.jar:androidsdk-sdkstats.jar:androidsdk-swtmenubar.jar:androidsdk-hierarchyviewerlib.jar:/usr/share/java/swt.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jfreechart-swt.jar:/usr/share/java/org.eclipse.jface.jar:/usr/share/java/org.eclipse.core.commands.jar:/usr/share/java/org.eclipse.equinox.common.jar:/usr/share/java/guava.jar:/usr/share/java/kxml2.jar:debian/_jh_build.androidsdk-common -d debian/_jh_build.androidsdk-common -source 1.5 -target 1.5 warning: [options] bootstrap class path not set in conjunction with -source 1.5 1 warning find common/src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javadoc -classpath androidsdk-common.jar:androidsdk-ddmlib.jar:androidsdk-ddmuilib.jar:androidsdk-sdkstats.jar:androidsdk-swtmenubar.jar:androidsdk-hierarchyviewerlib.jar:/usr/share/java/swt.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jfreechart-swt.jar:/usr/share/java/org.eclipse.jface.jar:/usr/share/java/org.eclipse.core.commands.jar:/usr/share/java/org.eclipse.equinox.common.jar:/usr/share/java/guava.jar:/usr/share/java/kxml2.jar:debian/_jh_build.androidsdk-common -d debian/_jh_build.javadoc/api -quiet -source 1.5 Creating destination directory: debian/_jh_build.javadoc/api/ warning: [options] bootstrap class path not set in conjunction with -source 1.5 1 warning /usr/lib/jvm/default-java/bin/jar cfm /«BUILDDIR»/androidsdk-tools-22.2+git20130830~92d25d6/androidsdk-common.jar ../_jh_manifest.androidsdk-common com find sdklib/src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javac -g -cp androidsdk-common.jar:androidsdk-ddmlib.jar:androidsdk-ddmuilib.jar:androidsdk-sdkstats.jar:androidsdk-swtmenubar.jar:androidsdk-hierarchyviewerlib.jar:/usr/share/java/swt.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jfreechart-swt.jar:/usr/share/java/org.eclipse.jface.jar:/usr/share/java/org.eclipse.core.commands.jar:/usr/share/java/org.eclipse.equinox.common.jar:/usr/share/java/guava.jar:/usr/share/java/kxml2.jar:debian/_jh_build.androidsdk-sdklib -d debian/_jh_build.androidsdk-sdklib -source 1.5 -target 1.5 warning: [options] bootstrap class path not set in conjunction with -source 1.5 1 warning find sdklib/src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javadoc -classpath androidsdk-common.jar:androidsdk-ddmlib.jar:androidsdk-ddmuilib.jar:androidsdk-sdkstats.jar:androidsdk-swtmenubar.jar:androidsdk-hierarchyviewerlib.jar:/usr/share/java/swt.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jfreechart-swt.jar:/usr/share/java/org.eclipse.jface.jar:/usr/share/java/org.eclipse.core.commands.jar:/usr/share/java/org.eclipse.equinox.common.jar:/usr/share/java/guava.jar:/usr/share/java/kxml2.jar:debian/_jh_build.androidsdk-sdklib -d debian/_jh_build.javadoc/api -quiet -source 1.5 warning: [options] bootstrap class path not set in conjunction with -source 1.5 sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:455: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:470: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:455: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:455: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:470: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:470: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:769: warning - Tag @link: reference not found: Accept#CONTINUE sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:769: warning - Tag @link: reference not found: Accept#ACCEPT_AND_STOP sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:769: warning - Tag @link: reference not found: Accept#REJECT_AND_STOP sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:455: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:470: warning - Tag @link: reference not found: Arg 12 warnings /usr/lib/jvm/default-java/bin/jar cfm
Bug#769251: android-platform-build: FTBFS in jessie/i386: libutils.so: undefined reference to `android_atomic_or'
Source: android-platform-build Version: 21-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): g++ -fPIC -Wl,-rpath=/usr/lib/android -Wl,-z,relro -o zipalign ZipAlign.o ZipEntry.o ZipFile.o -lz -lpthread -L/usr/lib/android -llog -lutils -lcutils /usr/lib/android/libutils.so: undefined reference to `android_atomic_or' /usr/lib/android/libutils.so: undefined reference to `android_atomic_dec' /usr/lib/android/libutils.so: undefined reference to `android_atomic_inc' /usr/lib/android/libutils.so: undefined reference to `android_atomic_release_cas' /usr/lib/android/libutils.so: undefined reference to `android_atomic_add' collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/android-platform-build_21-2_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769253: libcatmandu-sru-perl: FTBFS in jessie/i386: build-dependency not installable: libcatmandu-perl
Source: libcatmandu-sru-perl Version: 0.037-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ┌──┐ │ Install libcatmandu-sru-perl 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-libcatmandu-sru-perl-dummy : Depends: libcatmandu-perl 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/12/libcatmandu-sru-perl_0.037-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769243: libcatmandu-rdf-perl: FTBFS in jessie/i386: build-dependency not installable: libcatmandu-perl
Source: libcatmandu-rdf-perl Version: 0.18-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ┌──┐ │ Install libcatmandu-rdf-perl 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-libcatmandu-rdf-perl-dummy : Depends: libcatmandu-perl 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/12/libcatmandu-rdf-perl_0.18-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769244: libcatmandu-mab2-perl: FTBFS in jessie/i386: unsatisfiable build-dependencies: libcatmandu-perl, libcatmandu-sru-perl
Source: libcatmandu-mab2-perl Version: 0.07-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ┌──┐ │ Install libcatmandu-mab2-perl 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-libcatmandu-mab2-perl-dummy : Depends: libcatmandu-perl but it is not going to be installed Depends: libcatmandu-sru-perl 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/12/libcatmandu-mab2-perl_0.07-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769247: libcatmandu-perl: FTBFS in jessie/i386: build-dependency not installable: libmarpa-r2-perl
Source: libcatmandu-perl Version: 0.9206-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ┌──┐ │ Install libcatmandu-perl 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-libcatmandu-perl-dummy : Depends: libmarpa-r2-perl 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/12/libcatmandu-perl_0.9206-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769254: libcatmandu-wikidata-perl: FTBFS in jessie/i386: build-dependency not installable: libcatmandu-importer-getjson-perl
Source: libcatmandu-wikidata-perl Version: 0.06-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ┌──┐ │ Install libcatmandu-wikidata-perl 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-libcatmandu-wikidata-perl-dummy : Depends: libcatmandu-importer-getjson-perl 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/12/libcatmandu-wikidata-perl_0.06-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769219: debian-policy: FTBFS in jessie: emacs24 fails
On Wed, Nov 12, 2014 at 08:52:21AM +0100, Lucas Nussbaum wrote: 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): rm menu-policy.html/index.html perl-policy.html/index.html upgrading-checklist.html/index.html upgrading-checklist.txt perl-policy.txt menu-policy.txt make[1]: Leaving directory '/«PKGBUILDDIR»' /usr/bin/make Process.html README.html \ Process.txt README.txt make[1]: Entering directory '/«PKGBUILDDIR»' emacs24 --batch -Q -l ./README-css.el -l org --visit Process.org \ --funcall org-export-as-html-batch /dev/null 21 make[1]: *** [Process.html] Error 255 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014-11-11/debian-policy_3.9.6.0_jessie.log Hello all, This is with emacs-nox 24.4+1-4. This error does not occur with emacs24-nox 24.3+1-5+b1. The error message is: emacs24 --batch -Q -l ./README-css.el -l org --visit Process.org \ --funcall org-export-as-html-batch Symbol's function definition is void: org-export-as-html-batch I do not know how to fix that. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769255: flufl.lock: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit code 13
Source: flufl.lock Version: 2.3.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): debian/rules build dh build --with python2,python3,sphinxdoc --buildsystem=pybuild dh_testdir -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:170: python2.7 setup.py config running config I: pybuild base:170: python3.4 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:170: /usr/bin/python setup.py build running build running build_py creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl copying flufl/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock copying flufl/lock/conf.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock copying flufl/lock/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock copying flufl/lock/_lockfile.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/docs copying flufl/lock/docs/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/docs creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests copying flufl/lock/tests/subproc.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests copying flufl/lock/tests/test_lockfile.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests copying flufl/lock/tests/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests copying flufl/lock/tests/test_documentation.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests running egg_info creating flufl.lock.egg-info writing flufl.lock.egg-info/PKG-INFO writing namespace_packages to flufl.lock.egg-info/namespace_packages.txt writing top-level names to flufl.lock.egg-info/top_level.txt writing dependency_links to flufl.lock.egg-info/dependency_links.txt writing manifest file 'flufl.lock.egg-info/SOURCES.txt' reading manifest file 'flufl.lock.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching '.gitignore' no previously-included directories found matching 'build' writing manifest file 'flufl.lock.egg-info/SOURCES.txt' copying flufl/lock/NEWS.rst - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock copying flufl/lock/README.rst - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock copying flufl/lock/docs/using.rst - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/docs I: pybuild base:170: /usr/bin/python3 setup.py build running build running build_py creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl copying flufl/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock copying flufl/lock/conf.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock copying flufl/lock/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock copying flufl/lock/_lockfile.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/docs copying flufl/lock/docs/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/docs creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests copying flufl/lock/tests/subproc.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests copying flufl/lock/tests/test_lockfile.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests copying flufl/lock/tests/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests copying flufl/lock/tests/test_documentation.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests running egg_info writing flufl.lock.egg-info/PKG-INFO writing top-level names to flufl.lock.egg-info/top_level.txt writing namespace_packages to flufl.lock.egg-info/namespace_packages.txt writing dependency_links to flufl.lock.egg-info/dependency_links.txt reading manifest file 'flufl.lock.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching '.gitignore' no previously-included directories found matching 'build' writing manifest file 'flufl.lock.egg-info/SOURCES.txt' copying flufl/lock/NEWS.rst - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock copying flufl/lock/README.rst - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock copying flufl/lock/docs/using.rst - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/docs dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: python2.7 setup.py test running test running egg_info writing
Processed: lower severity
Processing commands for cont...@bugs.debian.org: package: src:mapsembler2 Limiting to bugs with field 'package' containing at least one of 'src:mapsembler2' Limit currently set to 'package':'src:mapsembler2' severity 765285 important Bug #765285 [src:mapsembler2] mapsembler2: FTBFS on non-x86: xmmintrin.h: No such file or directory Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 765285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769241: python-crypto: FTBFS in jessie/i386: Tests failures
Control: severity -1 important
Control: tags -1 moreinfo unreproducible
On 2014-11-12 11:21:47, Lucas Nussbaum wrote:
Source: python-crypto
Version: 2.6.1-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
core.setup(**kw)
File /usr/lib/python2.7/distutils/core.py, line 151, in setup
dist.run_commands()
File /usr/lib/python2.7/distutils/dist.py, line 953, in run_commands
self.run_command(cmd)
File /usr/lib/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File setup.py, line 331, in run
SelfTest.run(module=moduleObj, verbosity=self.verbose,
stream=sys.stdout, config=self.config)
File
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/Crypto/SelfTest/__init__.py,
line 76, in run
raise SelfTestError(Self-test failed, result)
Crypto.SelfTest.SelfTestError: ('Self-test failed',
unittest.runner.TextTestResult run=1071 errors=1 failures=0)
E: pybuild pybuild:256: test: plugin custom failed with: exit code=1:
python2.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 2.7 -s custom
--test-args={interpreter} setup.py test --dir . returned exit code 13
make[1]: *** [override_dh_auto_test] Error 13
debian/rules:21: recipe for target 'override_dh_auto_test' failed
The relevant part is:
| ==
| ERROR: runTest
(Crypto.SelfTest.Random.test__UserFriendlyRNG.RNGMultiprocessingForkTest)
| --
| Traceback (most recent call last):
| File
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/Crypto/SelfTest/Random/test__UserFriendlyRNG.py,
line 146, in runTest
| pool = multiprocessing.Pool(processes=n_procs,
initializer=Crypto.Random.atfork)
| File /usr/lib/python2.7/multiprocessing/__init__.py, line 232, in Pool
| return Pool(processes, initializer, initargs, maxtasksperchild)
| File /usr/lib/python2.7/multiprocessing/pool.py, line 138, in __init__
| self._setup_queues()
| File /usr/lib/python2.7/multiprocessing/pool.py, line 234, in
_setup_queues
| self._inqueue = SimpleQueue()
| File /usr/lib/python2.7/multiprocessing/queues.py, line 352, in __init__
| self._rlock = Lock()
| File /usr/lib/python2.7/multiprocessing/synchronize.py, line 147, in
__init__
| SemLock.__init__(self, SEMAPHORE, 1, 1)
| File /usr/lib/python2.7/multiprocessing/synchronize.py, line 75, in
__init__
| sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
| OSError: [Errno 13] Permission denied
I cannot reproduce it. Looks like the chroot is broken somehow. Why is
/dev/shm not usable in the chroot?
Reducing severity and tagging accordingly.
Cheers
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Processed: Re: Bug#769241: python-crypto: FTBFS in jessie/i386: Tests failures
Processing control commands: severity -1 important Bug #769241 [src:python-crypto] python-crypto: FTBFS in jessie/i386: Tests failures Severity set to 'important' from 'serious' tags -1 moreinfo unreproducible Bug #769241 [src:python-crypto] python-crypto: FTBFS in jessie/i386: Tests failures Added tag(s) unreproducible and moreinfo. -- 769241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757037: liblzop alignment problem
On 11/12/2014 01:20 AM, Simon McVittie wrote:
Control: severity 757037 grave
Control: tags 757037 + patch
I'm bumping this bug up to grave severity, because it seems it makes
this liblzo2 version entirely useless on a fairly common armel CPU (my armel
has a Marvell Kirkwood armv5tel, as used in the SheevaPlug and its
derivatives) in the default Debian configuration. It also makes liblzo2
FTBFS on such machines, because the tests fail.
Thanks.
On Sun, 09 Nov 2014 at 21:26:37 +0100, Marc Kleine-Budde wrote:
So from my point of view switching unaligned access
off in libzop with -DLZO_CFG_NO_UNALIGNED should be done on at least
ARMel. Are there other alignment sensitive platforms in debian?
(Please Cc me, I am not subscribed to this bug. Non-maintainer contributors
to Debian bugs usually aren't.)
Done
I think alignment-sensitivity is the common case, and quietly accepting
unaligned accesses (and giving the correct answer!) as is done on x86 is the
exceptional case...
Looking at the linux Kernel, there we have the
HAVE_EFFICIENT_UNALIGNED_ACCESS kconfig symbol. When an unaligned access
occurs in the kernel it's always fixed up. So the bad code will run, but
not as fast as it could.
arch/arm/Kconfig:44: select HAVE_EFFICIENT_UNALIGNED_ACCESS if (CPU_V6 ||
CPU_V6K || CPU_V7) MMU
Translated to debian this mean:
armel - unaligned access will silently fail on = ARMv5
(unless configured otherwise in /proc/cpu/alignment)
will work if run on = ARMv6, e.g. Raspberry Pi, Beagle Bone
But usually you would use armhf on such a system.
armhf - ok with unaligned access
arch/arm64/Kconfig:50:select HAVE_EFFICIENT_UNALIGNED_ACCESS
arm64 - ok
arch/powerpc/Kconfig:103: select HAVE_EFFICIENT_UNALIGNED_ACCESS if
!CPU_LITTLE_ENDIAN
ppc, ppc64 - ok
ppcel - not ok
arch/x86/Kconfig:64: select HAVE_EFFICIENT_UNALIGNED_ACCESS
i386, amd64 - ok
According to http://www.ibm.com/developerworks/library/pa-dalign/
the mips family are alignment-sensitive, and so is powerpc sometimes,
although it might do automatic fixup.
According to https://bugs.launchpad.net/ubuntu/+source/zmqpp/+bug/1256886
Ubuntu armhf is alignment-sensitive (presumably Debian armhf is the same?)
The just starting lzop testcase works on my ARMv7, current debian
testing, both with armhf and armel root filesystem. /proc/cpu/alignment
shows now Problems with the user space.
I've also seen references to sparc not liking unaligned accesses.
s390 can do unaligned accesses fine according to
http://lxr.free-electrons.com/source/include/asm-s390/unaligned.h?v=2.2.26,
but realistically, who's going to test that? Not me :-)
I think the safest thing would be to use -DLZO_CFG_NO_UNALIGNED
on all Debian architectures except i386, amd64, and maybe the powerpc
family if someone can test those. I attach a patch that restricts
use of unaligned accesses to i386 and amd64 CPUs (any kernel);
it's easy to extend to whitelist other CPUs where unaligned
accesses are OK.
liblzo2 does actually try to avoid using unsafe unaligned accesses
by using a structure
typedef struct lzo_memops_TU2_struct { unsigned char a[2]; }
lzo_memops_TU2;
and only doing a type-punning assignment similar to[1]
*(lzo_memops_TU2 *) (void *) dest = *(const lzo_memops_TU2 *) (void *)
src;
Which AFAIK should boil down to some kind of memcpy() with compile time
constant length.
if that structure has required alignment 1... but it seems (recent?) gcc
might be optimizing that into a single 2-byte operation which requires
alignment. This might be a gcc bug, but then, I suspect this might be
a violation of strict aliasing (hence undefined behaviour) if you get all
language-lawyer about it. Pessimistically assuming that we have to access
byte-by-byte on miscellaneous architectures seems both quicker and safer
than working out whether this is the compiler's fault.
tl;dr: the attached patch works, I would suggest using it.
Regards,
S
[1] Actually it's a little more complicated than that; there are another
couple of layers of typedef between the source code and the reality
regards,
Marc
signature.asc
Description: OpenPGP digital signature
Bug#769257: python-tblib: FTBFS in jessie/i386: Tests failures
Source: python-tblib Version: 0.1.0-5 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): File /usr/lib/python3.4/doctest.py, line 1324, in __run compileflags, 1), test.globs) File doctest README.rst[39], line 1, in module pool.terminate() NameError: name 'pool' is not defined ** 1 items had failures: 6 of 40 in README.rst ***Test Failed*** 6 failures. TestResults(failed=6, attempted=40) ERROR: InvocationError: '/«PKGBUILDDIR»/.tox/py3/bin/python /«PKGBUILDDIR»/tests/test_tblib.py' ___ summary ERROR: py: commands failed ERROR: py3: commands failed make[1]: *** [override_dh_auto_test] Error 1 debian/rules:23: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/python-tblib_0.1.0-5_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769260: openturns: FTBFS in jessie/i386: Tests failures
Source: openturns Version: 1.3-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): 356/359 Test #356: cppcheck_Wilks_std ... Passed0.03 sec Start 358: cppcheck_FittingTest_std 357/359 Test #358: cppcheck_FittingTest_std . Passed1.37 sec Start 359: cppcheck_NormalityTest_std 358/359 Test #359: cppcheck_NormalityTest_std ... Passed0.21 sec 359/359 Test #357: cppcheck_VisualTest_std .. Passed8.30 sec 99% tests passed, 1 tests failed out of 359 Total Test time (real) = 93.02 sec The following tests FAILED: 234 - cppcheck_TrapezoidalFactory_std (Failed) Errors while running CTest make[2]: *** [test] Error 8 Makefile:140: recipe for target 'test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/openturns_1.3-2_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769258: sawfish: FTBFS in jessie/i386: /usr/lib/rep/i486-pc-linux-gnu/libtool: line 7834: i486-linux-gnu-gcc: command not found
Source: sawfish Version: 1:1.5.3-2.4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): make[2]: Entering directory '/«PKGBUILDDIR»/src' /bin/sh -ec 'gcc -MM -DHAVE_CONFIG_H -DSAWFISH -D__STRICT_ANSI__ -I. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 play-sample.c \ | sed '\''s/play-sample\.o/ play-sample.lo .play-sample\.d/g'\'' .play-sample.d' /bin/sh -ec 'gcc -MM -DHAVE_CONFIG_H -DSAWFISH -D__STRICT_ANSI__ -I. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 selection.c \ | sed '\''s/selection\.o/ selection.lo .selection\.d/g'\'' .selection.d' /bin/sh -ec 'gcc -MM -DHAVE_CONFIG_H -DSAWFISH -D__STRICT_ANSI__ -I. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 x.c \ | sed '\''s/x\.o/ x.lo .x\.d/g'\'' .x.d' /bin/sh -ec 'gcc -MM -DHAVE_CONFIG_H -DSAWFISH -D__STRICT_ANSI__ -I. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 flippers.c \ | sed '\''s/flippers\.o/ flippers.lo .flippers\.d/g'\'' .flippers.d' /bin/sh -ec 'gcc -MM -DHAVE_CONFIG_H -DSAWFISH -D__STRICT_ANSI__ -I. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 gradient.c \ | sed '\''s/gradient\.o/ gradient.lo .gradient\.d/g'\'' .gradient.d' /bin/sh -ec 'gcc -MM -DHAVE_CONFIG_H -DSAWFISH -D__STRICT_ANSI__ -I. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 windows.c \ | sed '\''s/windows\.o/ windows.lo .windows\.d/g'\'' .windows.d' /bin/sh -ec 'gcc -MM -DHAVE_CONFIG_H -DSAWFISH -D__STRICT_ANSI__ -I. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2
Bug#769259: golang-testify: FTBFS in jessie/i386: dh_auto_test: go test -v github.com/stretchr/testify github.com/stretchr/testify/assert github.com/stretchr/testify/http github.com/stretchr/testify/m
Source: golang-testify Version: 0.0~git20140717-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): debian/rules build dh build --buildsystem=golang --with=golang dh_testdir -O--buildsystem=golang dh_auto_configure -O--buildsystem=golang dh_auto_build -O--buildsystem=golang github.com/stretchr/testify/assert github.com/stretchr/objx github.com/stretchr/testify/suite github.com/stretchr/testify/mock github.com/stretchr/testify/http github.com/stretchr/testify dh_auto_test -O--buildsystem=golang === RUN TestImports --- PASS: TestImports (0.00 seconds) PASS okgithub.com/stretchr/testify 0.008s === RUN TestObjectsAreEqual --- PASS: TestObjectsAreEqual (0.00 seconds) === RUN TestImplements --- PASS: TestImplements (0.00 seconds) === RUN TestIsType --- PASS: TestIsType (0.00 seconds) === RUN TestEqual --- FAIL: TestEqual (0.00 seconds) assertions_test.go:94: Equal should return true === RUN TestNotNil --- PASS: TestNotNil (0.00 seconds) === RUN TestNil --- PASS: TestNil (0.00 seconds) === RUN TestTrue --- PASS: TestTrue (0.00 seconds) === RUN TestFalse --- PASS: TestFalse (0.00 seconds) === RUN TestExactly --- PASS: TestExactly (0.00 seconds) === RUN TestNotEqual --- PASS: TestNotEqual (0.00 seconds) === RUN TestContains --- PASS: TestContains (0.00 seconds) === RUN TestNotContains --- PASS: TestNotContains (0.00 seconds) === RUN TestDidPanic --- PASS: TestDidPanic (0.00 seconds) === RUN TestPanics --- PASS: TestPanics (0.00 seconds) === RUN TestNotPanics --- PASS: TestNotPanics (0.00 seconds) === RUN TestEqual_Funcs --- PASS: TestEqual_Funcs (0.00 seconds) === RUN TestNoError --- PASS: TestNoError (0.00 seconds) === RUN TestError --- PASS: TestError (0.00 seconds) === RUN TestEqualError --- PASS: TestEqualError (0.00 seconds) === RUN Test_isEmpty --- PASS: Test_isEmpty (0.00 seconds) === RUN TestEmpty --- PASS: TestEmpty (0.00 seconds) === RUN TestNotEmpty --- PASS: TestNotEmpty (0.00 seconds) === RUN Test_getLen --- PASS: Test_getLen (0.00 seconds) === RUN TestLen --- PASS: TestLen (0.00 seconds) === RUN TestWithinDuration --- PASS: TestWithinDuration (0.00 seconds) === RUN TestInDelta --- PASS: TestInDelta (0.00 seconds) === RUN TestImplementsWrapper --- PASS: TestImplementsWrapper (0.00 seconds) === RUN TestIsTypeWrapper --- PASS: TestIsTypeWrapper (0.00 seconds) === RUN TestEqualWrapper --- PASS: TestEqualWrapper (0.00 seconds) === RUN TestNotNilWrapper --- PASS: TestNotNilWrapper (0.00 seconds) === RUN TestNilWrapper --- PASS: TestNilWrapper (0.00 seconds) === RUN TestTrueWrapper --- PASS: TestTrueWrapper (0.00 seconds) === RUN TestFalseWrapper --- PASS: TestFalseWrapper (0.00 seconds) === RUN TestExactlyWrapper --- PASS: TestExactlyWrapper (0.00 seconds) === RUN TestNotEqualWrapper --- PASS: TestNotEqualWrapper (0.00 seconds) === RUN TestContainsWrapper --- PASS: TestContainsWrapper (0.00 seconds) === RUN TestNotContainsWrapper --- PASS: TestNotContainsWrapper (0.00 seconds) === RUN TestDidPanicWrapper --- PASS: TestDidPanicWrapper (0.00 seconds) === RUN TestPanicsWrapper --- PASS: TestPanicsWrapper (0.00 seconds) === RUN TestNotPanicsWrapper --- PASS: TestNotPanicsWrapper (0.00 seconds) === RUN TestEqualWrapper_Funcs --- PASS: TestEqualWrapper_Funcs (0.00 seconds) === RUN TestNoErrorWrapper --- PASS: TestNoErrorWrapper (0.00 seconds) === RUN TestErrorWrapper --- PASS: TestErrorWrapper (0.00 seconds) === RUN TestEqualErrorWrapper --- PASS: TestEqualErrorWrapper (0.00 seconds) === RUN TestEmptyWrapper --- PASS: TestEmptyWrapper (0.00 seconds) === RUN TestNotEmptyWrapper --- PASS: TestNotEmptyWrapper (0.00 seconds) === RUN TestLenWrapper --- PASS: TestLenWrapper (0.00 seconds) === RUN TestWithinDurationWrapper --- PASS: TestWithinDurationWrapper (0.00 seconds) FAIL FAIL github.com/stretchr/testify/assert 0.013s ? github.com/stretchr/testify/http[no test files] === RUN Test_Mock_TestData --- PASS: Test_Mock_TestData (0.00 seconds) === RUN Test_Mock_On --- PASS: Test_Mock_On (0.00 seconds) === RUN Test_Mock_On_WithArgs --- PASS: Test_Mock_On_WithArgs (0.00 seconds) === RUN Test_Mock_Return --- PASS: Test_Mock_Return (0.00 seconds) === RUN Test_Mock_Return_Once --- PASS: Test_Mock_Return_Once (0.00 seconds) === RUN Test_Mock_Return_Twice --- PASS: Test_Mock_Return_Twice (0.00 seconds) === RUN Test_Mock_Return_Times --- PASS: Test_Mock_Return_Times (0.00 seconds) === RUN Test_Mock_Return_Nothing --- PASS: Test_Mock_Return_Nothing (0.00 seconds) === RUN Test_Mock_findExpectedCall --- PASS: Test_Mock_findExpectedCall (0.00 seconds) === RUN Test_Mock_findExpectedCall_For_Unknown_Method
Bug#769263: glide: FTBFS in jessie/i386: install: cannot stat '/«PKGBUILDDIR»/debian/tmp.h3/usr/lib/libglide3.so.3.10.0': No such file or directory
Source: glide Version: 2002.04.10ds1-10 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): fakeroot debian/rules binary # Nothing to do. dh_testdir dh_testroot dh_prep -s dh_installdirs -s # libglide2 install -m 644 /«PKGBUILDDIR»/glide2x/cvg/lib/libglide.so.2.53 \ /«PKGBUILDDIR»/debian/libglide2/usr/lib/glide2/libglide_cvg.so.2.53 install -m 644 /«PKGBUILDDIR»/glide2x/h3/lib/libglide.so.2.60 \ /«PKGBUILDDIR»/debian/libglide2/usr/lib/glide2/libglide_h3.so.2.60 install -m 644 /«PKGBUILDDIR»/glide2x/swlibs/lib/libtexus.so.1.1 \ /«PKGBUILDDIR»/debian/libglide2/usr/lib/ # libglide3 install -m 644 /«PKGBUILDDIR»/debian/tmp.h3/usr/lib/libglide3.so.3.10.0 \ /«PKGBUILDDIR»/debian/libglide3/usr/lib/glide3/libglide3_h3.so.3.10.0 install: cannot stat '/«PKGBUILDDIR»/debian/tmp.h3/usr/lib/libglide3.so.3.10.0': No such file or directory make: *** [binary-arch] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/glide_2002.04.10ds1-10_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769266: canl-java: FTBFS in jessie/i386: 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-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. 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/12/canl-java_2.1.1-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769262: shortuuid: FTBFS in jessie/i386: Tests failures
Source: shortuuid Version: 0.4.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): running build running build_py creating build3.4 creating build3.4/lib creating build3.4/lib/shortuuid copying shortuuid/main.py - build3.4/lib/shortuuid copying shortuuid/__init__.py - build3.4/lib/shortuuid copying shortuuid/tests.py - build3.4/lib/shortuuid make[1]: Leaving directory '/«PKGBUILDDIR»' debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' set -e ; \ python2.7 $BLDDIR27/shortuuid/tests.py python2.7: can't open file 'build2.7/lib.linux-i586-2.7/shortuuid/tests.py': [Errno 2] No such file or directory make[1]: *** [override_dh_auto_test] Error 2 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/12/shortuuid_0.4.2-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769267: javamail: FTBFS in jessie/i386: tests failures
Source: javamail
Version: 1.5.2-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
debian/rules build
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
mh_patchpoms -plibmail-java --debian-build --keep-pom-version
--maven-repo=/«PKGBUILDDIR»/debian/maven-repo
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo install
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] JavaMail API distribution
[INFO] JavaMail API
[INFO] JavaMail API (no providers)
[INFO] JavaMail API jar
[INFO] JavaMail API smtp provider
[INFO] JavaMail API imap provider
[INFO] JavaMail API Gmail IMAP provider
[INFO] JavaMail API pop3 provider
[INFO] JavaMail API dsn support
[INFO]
[INFO] Building JavaMail API distribution
[INFO]task-segment: [install]
[INFO]
[INFO] [build-helper:add-source {execution: add-source}]
[INFO] Source directory: /«PKGBUILDDIR»/target/sources added.
[INFO] Source directory: /«PKGBUILDDIR»/target/classes added.
[INFO] [bundle:manifest {execution: osgi-manifest}]
[WARNING] Ignoring project type pom - supportedProjectTypes = [jar, bundle]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [source:jar-no-fork {execution: attach-sources}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/com/sun/mail/all/1.5.2/all-1.5.2.pom
[INFO]
[INFO] Building JavaMail API
[INFO]task-segment: [install]
[INFO]
[INFO] [build-helper:add-source {execution: add-source}]
[INFO] Source directory: /«PKGBUILDDIR»/mail/target/sources added.
[INFO] Source directory: /«PKGBUILDDIR»/mail/target/classes added.
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 8 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 227 source files to /«PKGBUILDDIR»/mail/target/classes
[INFO] [bundle:manifest {execution: osgi-manifest}]
[INFO] maven-bundle-plugin 2.3.5 compatibility enabled
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 7 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 77 source files to /«PKGBUILDDIR»/mail/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: /«PKGBUILDDIR»/mail/target/surefire-reports
---
T E S T S
---
Running MimeMultipartParseTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.194 sec
Running javax.mail.URLNameTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.083 sec
Running javax.mail.internet.AddFromTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
Running javax.mail.internet.HeaderTokenizerTest
Tests run: 56, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.073 sec
Running javax.mail.internet.MimeMultipartPropertyTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
Running javax.mail.internet.MimeMessageTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
Running javax.mail.internet.MimeMultipartPreambleTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running javax.mail.internet.FoldTest
Tests run: 39, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec
Running javax.mail.internet.MimeUtilityTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Bug#769261: sslh: FTBFS in jessie/i386: Build killed with signal TERM after 150 minutes of inactivity
Source: sslh Version: 1.16-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): ***Test: One SSL half-started then one SSH Connection refused ***Test: One SSH half-started then one SSL Connection refused cat: /tmp/sslh_test.pid: No such file or directory killing Can't kill a non-numeric process ID at ./t line 221. # Looks like your test exited with 1 before it could output anything. make[1]: *** [test] Error 1 Makefile:99: recipe for target 'test' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_test: make -j1 test returned exit code 2 make: *** [build] Error 2 debian/rules:31: recipe for target 'build' failed dpkg-buildpackage: error: debian/rules build gave error exit status 2 Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/sslh_1.16-2_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769265: libmarpa-r2-perl: FTBFS in jessie/i386: Bailout called. Further testing stopped: Could not load Marpa::R2
Source: libmarpa-r2-perl Version: 2.086000~dfsg-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): make[2]: Entering directory '/«PKGBUILDDIR»' /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o marpa.lo /«PKGBUILDDIR»/libmarpa_dist/marpa.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/libmarpa_dist/marpa.c -fPIC -DPIC -o marpa.o /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o marpa_obs.lo /«PKGBUILDDIR»/libmarpa_dist/marpa_obs.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/libmarpa_dist/marpa_obs.c -fPIC -DPIC -o marpa_obs.o /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o marpa_avl.lo /«PKGBUILDDIR»/libmarpa_dist/marpa_avl.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/libmarpa_dist/marpa_avl.c -fPIC -DPIC -o marpa_avl.o /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o marpa_tavl.lo /«PKGBUILDDIR»/libmarpa_dist/marpa_tavl.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/libmarpa_dist/marpa_tavl.c -fPIC -DPIC -o marpa_tavl.o /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o marpa_ami.lo /«PKGBUILDDIR»/libmarpa_dist/marpa_ami.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes -Wwrite-strings -Wshadow -Wmissing-declarations -Wconversion -ansi -pedantic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/libmarpa_dist/marpa_ami.c -fPIC -DPIC -o marpa_ami.o /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/libmarpa_dist -Wundef -Wendif-labels -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -Wstrict-prototypes
Bug#769264: freebirth: FTBFS in jessie/i386: XXX
Source: freebirth Version: 0.3.2-8 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' gcc -MM -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 oscillator.c sequencer.c envelope.c filter.c gtkdial.c mixer.c raw_wave.c event.c sample_producer.c blender.c delay.c reverb.c all_pass.c delay_panel.c reverb_panel.c multi_tap_delay.c sample_freq_strip.c Makefile.deps gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o freebirth.o freebirth.c gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o oscillator.o oscillator.c gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o sequencer.o sequencer.c gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o envelope.o envelope.c gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o filter.o filter.c filter.c: In function 'filter_init_lookup_table': filter.c:101:28: warning: variable 'table_length' set but not used [-Wunused-but-set-variable] int freq_range, q_range, table_length; ^ gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o gtkdial.o gtkdial.c gtkdial.c: In function 'gtk_dial_realize': gtkdial.c:207:18: warning: variable 'dial' set but not used [-Wunused-but-set-variable] GtkDial *dial; ^ gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0
Bug#769272: oasis: FTBFS in jessie/i386: Tests failures
Source: oasis Version: 0.4.4-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): Exit status of command '/tmp/ounit-721c90-ip-172-31-8-38#01.dir/precompile/setup -info -debug -install' expected: Exited with code 0 but got: Exited with code 127 -- Ran: 227 tests in: 127.75 seconds. FAILED: Cases: 227 Tried: 227 Errors: 0 Failures: 30 Skip: 3 Todo: 0 Timeouts: 0. W: Test 'main' fails: Command '/«PKGBUILDDIR»/_build/test/test.byte -oasis /«PKGBUILDDIR»/_build/src/cli/Main.byte -is-native true \ -native-dynlink true \ -ocamlmod /usr/bin/ocamlmod -fake-ocamlfind /«PKGBUILDDIR»/_build/test/utils/fake_ocamlfind.byte' terminated with error code 1 .. Ran: 2 tests in: 0.18 seconds. OK E: Failure(Tests had a 33.33% failure rate) make[1]: *** [override_dh_auto_test] Error 1 debian/rules:35: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/oasis_0.4.4-2_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769271: metamonger: FTBFS in jessie/i386: Tests failures
Source: metamonger Version: 0.20141008-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): # Looks like you failed 9 tests of 14. t/200-no-dereference.t .. Dubious, test returned 9 (wstat 2304, 0x900) Failed 9/14 subtests t/500-fix-84ee7f6b65.t .. ok Test Summary Report --- t/200-no-dereference.t(Wstat: 2304 Tests: 14 Failed: 9) Failed tests: 3, 6, 8-14 Non-zero exit status: 9 Files=19, Tests=724, 11 wallclock secs ( 0.14 usr 0.10 sys + 9.10 cusr 2.18 csys = 11.52 CPU) Result: FAIL Failed 1/19 test programs. 9/724 subtests failed. make[1]: *** [test_dynamic] Error 255 Makefile:767: recipe for target 'test_dynamic' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/metamonger_0.20141008-1_jessie-i386.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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769268: serf: FTBFS in jessie/i386: TypeError: Directory /usr/include/mit-krb5 found where file expected.:
Source: serf
Version: 1.3.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
debian/rules build
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch libtool
patching file SConstruct
Now at patch libtool
touch debian/stamp-patched
dh_testdir
scons GSSAPI=/usr CFLAGS=-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2
LINKFLAGS=-Wl,-z,relro -Wl,-z,defs -Wl,--as-needed
scons: Reading SConscript files ...
TypeError: Directory /usr/include/mit-krb5 found where file expected.:
File /«PKGBUILDDIR»/SConstruct, line 360:
env.ParseConfig('$GSSAPI --cflags gssapi')
File /usr/lib/scons/SCons/Environment.py, line 1555:
return function(self, self.backtick(command))
File /usr/lib/scons/SCons/Environment.py, line 1550:
return env.MergeFlags(cmd, unique)
File /usr/lib/scons/SCons/Environment.py, line 814:
args = self.ParseFlags(args)
File /usr/lib/scons/SCons/Environment.py, line 800:
do_parse(arg)
File /usr/lib/scons/SCons/Environment.py, line 730:
dict['LIBS'].append(self.fs.File(arg))
File /usr/lib/scons/SCons/Node/FS.py, line 1340:
return self._lookup(name, directory, File, create)
File /usr/lib/scons/SCons/Node/FS.py, line 1319:
return root._lookup_abs(p, fsclass, create)
File /usr/lib/scons/SCons/Node/FS.py, line 2216:
result.diskcheck_match()
File /usr/lib/scons/SCons/Node/FS.py, line 2362:
Directory %s found where file expected.)
File /usr/lib/scons/SCons/Node/FS.py, line 385:
return self.func(*args, **kw)
File /usr/lib/scons/SCons/Node/FS.py, line 406:
raise TypeError(errorfmt % node.abspath)
make: *** [debian/stamp-build] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/12/serf_1.3.7-1_jessie-i386.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-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769269: rep-gtk: FTBFS in jessie/i386: /usr/lib/rep/i486-pc-linux-gnu/libtool: line 7834: i486-linux-gnu-gcc: command not found
Source: rep-gtk Version: 1:0.90.0-2.2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' mkdir gtk-2 /usr/lib/rep/i486-pc-linux-gnu/libtool --tag CC --mode=compile --tag=CC i586-linux-gnu-gcc -c -DHAVE_CONFIG_H -I. -Wall -g -O2 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include rep-types.c libtool: compile: i586-linux-gnu-gcc -c -DHAVE_CONFIG_H -I. -Wall -g -O2 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include rep-types.c -fPIC -DPIC -o .libs/rep-types.o rep-types.c: In function 'sgtk_rep_to_list': rep-types.c:443:6: warning: ignoring return value of 'g_list_concat', declared with attribute warn_unused_result [-Wunused-result] g_list_concat (tail, n); ^ rep-types.c:464:8: warning: ignoring return value of 'g_list_concat', declared with attribute warn_unused_result [-Wunused-result] g_list_concat (tail, n); ^ libtool: compile: i586-linux-gnu-gcc -c -DHAVE_CONFIG_H -I. -Wall -g -O2 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include rep-types.c -o rep-types.o /dev/null 21 /usr/lib/rep/i486-pc-linux-gnu/libtool --tag CC --mode=link --tag=CC i586-linux-gnu-gcc -avoid-version -module -rpath /usr/lib/rep/i486-pc-linux-gnu -DHAVE_CONFIG_H -I. -Wall -g -O2 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-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/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -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/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/ -I/usr/lib/rep/i486-pc-linux-gnu/ -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -o gtk-2/types.la rep-types.lo -lglib-2.0 libtool: link: i486-linux-gnu-gcc -shared .libs/rep-types.o -lglib-2.0 -pthread -pthread -pthread -Wl,-soname -Wl,types.so -o gtk-2/.libs/types.so /usr/lib/rep/i486-pc-linux-gnu/libtool: line 7834: i486-linux-gnu-gcc: command not found make[1]: *** [gtk-2/types.la] Error 127 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/rep-gtk_0.90.0-2.2_jessie-i386.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
Bug#769273: bsdutils: Dependency on libsystemd0 violates policy
Package: bsdutils Version: 1:2.25.2-2 Severity: serious Justification: Policy 2.5 Dear Maintainer, libsystemd0 dependancy violates constraint at the end of section 2.5 of the policy manual that requires packages not depend on packages with lower priority.. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bsdutils depends on: ii libc62.19-13 ii libsystemd0 215-5+b1 Versions of packages bsdutils recommends: ii bsdmainutils 9.0.6 bsdutils suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769257: marked as done (python-tblib: FTBFS in jessie/i386: Tests failures)
Your message dated Wed, 12 Nov 2014 12:07:52 +0100 with message-id 20141112110752.ga26...@xanadu.blop.info and subject line Re: Bug#769257: Acknowledgement (python-tblib: FTBFS in jessie/i386: Tests failures) has caused the Debian Bug report #769257, regarding python-tblib: FTBFS in jessie/i386: Tests failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-tblib Version: 0.1.0-5 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): File /usr/lib/python3.4/doctest.py, line 1324, in __run compileflags, 1), test.globs) File doctest README.rst[39], line 1, in module pool.terminate() NameError: name 'pool' is not defined ** 1 items had failures: 6 of 40 in README.rst ***Test Failed*** 6 failures. TestResults(failed=6, attempted=40) ERROR: InvocationError: '/«PKGBUILDDIR»/.tox/py3/bin/python /«PKGBUILDDIR»/tests/test_tblib.py' ___ summary ERROR: py: commands failed ERROR: py3: commands failed make[1]: *** [override_dh_auto_test] Error 1 debian/rules:23: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/python-tblib_0.1.0-5_jessie-i386.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. ---End Message--- ---BeginMessage--- Caused by a broken chroot, closing. Lucas---End Message---
Bug#769255: marked as done (flufl.lock: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit code 13)
Your message dated Wed, 12 Nov 2014 12:09:57 +0100
with message-id 20141112110957.ga26...@xanadu.blop.info
and subject line Re: Bug#769255: Acknowledgement (flufl.lock: FTBFS in
jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir .
returned exit code 13)
has caused the Debian Bug report #769255,
regarding flufl.lock: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i
python{version} -p 2.7 --dir . returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
769255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: flufl.lock
Version: 2.3.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
debian/rules build
dh build --with python2,python3,sphinxdoc --buildsystem=pybuild
dh_testdir -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:170: python2.7 setup.py config
running config
I: pybuild base:170: python3.4 setup.py config
running config
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:170: /usr/bin/python setup.py build
running build
running build_py
creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl
copying flufl/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl
creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock
copying flufl/lock/conf.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock
copying flufl/lock/__init__.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock
copying flufl/lock/_lockfile.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock
creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/docs
copying flufl/lock/docs/__init__.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/docs
creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests
copying flufl/lock/tests/subproc.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests
copying flufl/lock/tests/test_lockfile.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests
copying flufl/lock/tests/__init__.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests
copying flufl/lock/tests/test_documentation.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/tests
running egg_info
creating flufl.lock.egg-info
writing flufl.lock.egg-info/PKG-INFO
writing namespace_packages to flufl.lock.egg-info/namespace_packages.txt
writing top-level names to flufl.lock.egg-info/top_level.txt
writing dependency_links to flufl.lock.egg-info/dependency_links.txt
writing manifest file 'flufl.lock.egg-info/SOURCES.txt'
reading manifest file 'flufl.lock.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files found matching '.gitignore'
no previously-included directories found matching 'build'
writing manifest file 'flufl.lock.egg-info/SOURCES.txt'
copying flufl/lock/NEWS.rst -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock
copying flufl/lock/README.rst -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock
copying flufl/lock/docs/using.rst -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/flufl/lock/docs
I: pybuild base:170: /usr/bin/python3 setup.py build
running build
running build_py
creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl
copying flufl/__init__.py - /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl
creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock
copying flufl/lock/conf.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock
copying flufl/lock/__init__.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock
copying flufl/lock/_lockfile.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock
creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/docs
copying flufl/lock/docs/__init__.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/docs
creating /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests
copying flufl/lock/tests/subproc.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests
copying flufl/lock/tests/test_lockfile.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests
copying flufl/lock/tests/__init__.py -
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.4/build/flufl/lock/tests
copying flufl/lock/tests
Bug#768881: [Debian-ha-maintainers] Bug#768881: FTBFS: unable to parse drbdsetup.xml.in
Hi Adam, Thanks for the report. On 22:06 Sun 09 Nov , Adam Borowski wrote: Package: src:drbd-utils Version: 8.9.2~rc1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid that during a rebuild of jessie on armhf your package failed to build: /usr/bin/xsltproc -o drbdsetup.xml drbdsetup.xsl drbdsetup.xml.in http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:139: parser error : Comment must not contain '--' (double-hyphen) !-- Redeclaration placeholder . -- ^ http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:142: parser warning : PEReference: %intermod.redec l.module; not found ![%intermod.redecl.module;[ ^ http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:142: parser error : conditional section INCLUDE or IGNORE keyword expected ![%intermod.redecl.module;[ ^ http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:142: parser error : Content error in the external subset !-- Defining rdbmods here makes some buggy XML parsers happy. -- ^ http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:142: validity error : All markup of the conditiona l section is not in the same entity !-- Defining rdbmods here makes some buggy XML parsers happy. -- ^ http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:142: parser error : Content error in the external subset !-- Defining rdbmods here makes some buggy XML parsers happy. -- ^ http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:142: validity error : All markup of the conditiona l section is not in the same entity !-- Defining rdbmods here makes some buggy XML parsers happy. -- ^ http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:142: parser error : Content error in the external subset !-- Defining rdbmods here makes some buggy XML parsers happy. -- ^ http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:142: parser error : Content error in the external subset !-- Defining rdbmods here makes some buggy XML parsers happy. -- ^ unable to parse drbdsetup.xml.in Unfortunately I am unable to reproduce this on harris.debian.org (armhf porterbox), with a clean jessie schroot. This looks similar to #355374, which was not reproducible as well. Furthermore, these messages look at least suspicious (XML comments cannot contain double dashes?!), so I tend to think this might be a problem with xsltproc. Can you reliably reproduce it on your system? Messages during configure suggest it checks udev on the build (rather than target) system, without Build-Depending on udev. Adding this B-Dep significantly reduces the amount of noise, including parser errors above: 4 errors 0 warnings instead of 8 errors 1 warnings, but the build still fails. Thanks for pointing this out, I'll have to check that the udev rules are there on all arch's, since it seems to ship them with a .disabled suffix if it can't find udevadm/udevinfo. Regards, Apollon signature.asc Description: Digital signature
Bug#769160: marked as done (nasm 2.11.06-1 in unstable makes syslinux FTBFS)
Your message dated Wed, 12 Nov 2014 11:19:15 + with message-id e1xovxd-0003mv...@franck.debian.org and subject line Bug#769160: fixed in nasm 2.11.06-1really2.11.05-1 has caused the Debian Bug report #769160, regarding nasm 2.11.06-1 in unstable makes syslinux FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nasm Version: 2.11.06-1 Severity: serious nasm 2.11.06-1 uploaded to unstable on 2014-11-06(!) makes syslinux FTBFS. patches to syslinux (if minimal and if they keep it working for both the version of nasm in unstable and testing at the same time) are welcome. otherwise i guess the best thing to do would be to revert to 2.11.05-1 until jessie is released. Regards, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ ---End Message--- ---BeginMessage--- Source: nasm Source-Version: 2.11.06-1really2.11.05-1 We believe that the bug you reported is fixed in the latest version of nasm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated nasm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 12 Nov 2014 10:42:57 + Source: nasm Binary: nasm Architecture: source amd64 Version: 2.11.06-1really2.11.05-1 Distribution: unstable Urgency: low Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: nasm - General-purpose x86 assembler Closes: 769160 Changes: nasm (2.11.06-1really2.11.05-1) unstable; urgency=low . * Upload 2.11.05-1 to unstable. 2.11.06-1 in unstable makes syslinux FTBFS. Closes: #769160. Checksums-Sha1: a8b8c7eeb57c368f6cb2b629690d67065b0eb92b 1828 nasm_2.11.06-1really2.11.05-1.dsc 20536831011b07015913964ddedbce916375e5ad 744740 nasm_2.11.06-1really2.11.05.orig.tar.xz 88ec13de60cfa99d133d9af0c346a8d02557ad89 15348 nasm_2.11.06-1really2.11.05-1.debian.tar.xz a24fa7958950a3a0ad575769863edf68039949b2 1465186 nasm_2.11.06-1really2.11.05-1_amd64.deb Checksums-Sha256: 1c7d3b7a45cbfe4e11ff283f41b24902ebdfa695233704a1503436a1b11fc421 1828 nasm_2.11.06-1really2.11.05-1.dsc 2f4769c2fc88dbd8df4383ce30bc86919b5d488854ab906ebcee5d5a38828a6b 744740 nasm_2.11.06-1really2.11.05.orig.tar.xz 670c0b1ed9f56f2598011b5833a586aa466ab019e11716831d0a969fa403cebc 15348 nasm_2.11.06-1really2.11.05-1.debian.tar.xz 59817ac29296be2fb01a7eabed5f47312dc4b6cb87df6dc29056aa909ce2 1465186 nasm_2.11.06-1really2.11.05-1_amd64.deb Files: 08e37fc283873fe7e3c6a83a27dd0066 1828 devel optional nasm_2.11.06-1really2.11.05-1.dsc 3544d7068206b583915394693c0e933c 744740 devel optional nasm_2.11.06-1really2.11.05.orig.tar.xz b929d77ceeab5cdf66ac464433dc826f 15348 devel optional nasm_2.11.06-1really2.11.05-1.debian.tar.xz 1f14c986e1528b87813079177e6c4b16 1465186 devel optional nasm_2.11.06-1really2.11.05-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUYz7OAAoJEHxWrP6UeJfYKEgQAMAohmK2NUCLTLGyGyOcq2sC Xf9pvWWMc/NYCHINMf+DkYZougdx35GOt72m+SOPC0wK1To+z5yliKB9kgT+xRM7 esl5wwDNbArsPjfShMmxRr0sgAidnZHgGgxT1LXKPZJ/fo4664JnDJ0eib4vMV+U zGToOO9CeVzHbEpy/4KYDwyzs+ATARGPlvBo5dV5Hv59WKIlaYSQYVTgrsO83bI7 haFWI8kaq/kPYXkOFme3LH6Mzw4zXzWai6/av+Y9RVusRw2an77E5oCLXvazZjCx JIGCb2nvZfRgGzwrR7TjHgk1wRhHbl+eNAHv934F3o2SqeHa7XiEvzG/pd/Qz62l 171Qy5uyzNzTHHkZqHwdB6Q/uDKcztEpv5OzGmdXfbDzrE4tGBkwU6j1AocCSBqm KVFfedZhkIDzFIyrANUqNIZhjIpzvkBSUpgLk21k4/Yec/zoSvygT1EvVgVvjPHa C2LM3TBXy95+jMuO6RCUs6NgYL/6HzgXJZAXCV/aDpc7BxNZCXsRl8wZjU/f6iiu 6ekNS0wTy07IVay4j8wj0H6FCuH8x4+O2iO+dhkK3PO8EnCKjmHTEIRwjhNMlYm9 xio8li4/WJq6UREN4khgeI9nUg2ClIS5tJAkVO/td8d/vLuwrQ6rLxCrIoFWXqth ig8PaxKXQMy+QWv99vGh =jWSW -END PGP SIGNATUREEnd Message---
Bug#769257: python-tblib: FTBFS in jessie/i386: Tests failures
On Wed, Nov 12, 2014 at 11:41:24AM +0100, Lucas Nussbaum wrote: During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. I think this might be a bug in your build setup. Here's the point where it starts going wrong: File /«PKGBUILDDIR»/tests/../README.rst, line 195, in README.rst Failed example: pool = Pool() Exception raised: Traceback (most recent call last): File /usr/lib/python2.7/doctest.py, line 1315, in __run compileflags, 1) in test.globs File doctest README.rst[32], line 1, in module pool = Pool() File /usr/lib/python2.7/multiprocessing/__init__.py, line 232, in Pool return Pool(processes, initializer, initargs, maxtasksperchild) File /usr/lib/python2.7/multiprocessing/pool.py, line 138, in __init__ self._setup_queues() File /usr/lib/python2.7/multiprocessing/pool.py, line 234, in _setup_queues self._inqueue = SimpleQueue() File /usr/lib/python2.7/multiprocessing/queues.py, line 352, in __init__ self._rlock = Lock() File /usr/lib/python2.7/multiprocessing/synchronize.py, line 147, in __init__ SemLock.__init__(self, SEMAPHORE, 1, 1) File /usr/lib/python2.7/multiprocessing/synchronize.py, line 75, in __init__ sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) OSError: [Errno 13] Permission denied This looks as though sem_open is failing, which I think is likely to be because /dev/shm is not properly mounted. Perhaps the sbuild setup here is missing a tmpfs mount on /dev/shm? -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738195: [pkg-cli-apps-team] Processed: reopening 738195
On Wed, Nov 12, 2014 at 12:38:32AM +0800, Chow Loong Jin wrote:
On Tue, Nov 11, 2014 at 04:06:06PM +, Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
reopen 738195
Bug #738195 {Done: Chow Loong Jin hyper...@debian.org} [gnome-do]
gnome-do: Changed location of homepage
Bug #757056 {Done: Chow Loong Jin hyper...@debian.org} [gnome-do]
gnome-do: URL needs updating
Bug reopened
Ignoring request to alter fixed versions of bug #738195 to the same values
previously set
Ignoring request to alter fixed versions of bug #757056 to the same values
previously set
thanks
Stopping processing here.
Why are you reopening this bug? Are there any outdated references left?x
https://packages.debian.org/sid/gnome-do seems to show an updated URL to me.
Grepping the source for davebsd.com shows nothing.
As I explained, the bug is not fixed. The About button for each plug-in
in the Preferences window still sends me off to oneclickads.net.
I did take a brief look at the source package and I also don't see where
the old URL is coming from, but it's still there.
--
Kind regards,
Loong Jin
--
Sam Morris https://robots.org.uk/
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769161: [pkg-firebird-general] Bug#769161: ppc64el port is wrong
I have committed to both 3.0 and 2.5 branches Here is the 2.5 list of patches (you can diff it with the release branch) https://sourceforge.net/p/firebird/code/60194/ https://sourceforge.net/p/firebird/code/60195/ https://sourceforge.net/p/firebird/code/60198/ https://sourceforge.net/p/firebird/code/60201/ In the last patch I have add an ARM64 define twice in common.h , but corrected after that On Tue, Nov 11, 2014 at 10:16 PM, Damyan Ivanov d...@debian.org wrote: Package: src:firebird2.5 Subject: firebird2.5: ppc64el built as bigendian Version: 2.5.3.26778.ds4-2 Severity: serious Justification: possible data corruption -=| marius adrian popa, 11.11.2014 15:57:19 +0200 |=- From the build log i see that ppc64el is treated like a bigendian port https://buildd.debian.org/status/fetch.php?pkg=firebird2.5arch=ppc64elver=2.5.3.26778.ds4-3%2Bb1stamp=1415464014 Good catch. Forwarding as a bugreport. In my understanding this would cause data corruption when transferring data between ppc64el client/server and a non ppc64-el system -- doubles and big integers would be swapped when there's no need to and won't be swapped when there is need to do so. We need to create a new port for it Please let me know when the implementation ID/patch/commit is available. -- Damyan ___ pkg-firebird-general mailing list pkg-firebird-gene...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-firebird-general
Bug#769218: marked as done (gcc-4.9: FTBFS in jessie: Error! CRCs do not match! Got 264aca47, expected 95962ba4)
Your message dated Wed, 12 Nov 2014 12:48:12 +0100
with message-id 546348fc.1030...@debian.org
and subject line Re: Bug#769218: gcc-4.9: FTBFS in jessie: Error! CRCs do not
match! Got 264aca47, expected 95962ba4
has caused the Debian Bug report #769218,
regarding gcc-4.9: FTBFS in jessie: Error! CRCs do not match! Got 264aca47,
expected 95962ba4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
769218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: gcc-4.9
Version: 4.9.1-19
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2014-11-11 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[2]: Entering directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
rm -f src.zip
here=`pwd`; \
( \
( cd ../../../src/libjava/classpath; \
find java gnu javax org sun -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava/classpath; \
echo $file; \
done ); \
( cd ../../../src/libjava/classpath/external/sax; \
find org -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava/classpath/external/sax; \
echo $file; \
done ); \
( cd ../../../src/libjava/classpath/external/relaxngDatatype; \
find org -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava/classpath/external/relaxngDatatype; \
echo $file; \
done ); \
( cd ../../../src/libjava/classpath/external/w3c_dom; \
find org -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava/classpath/external/w3c_dom; \
echo $file; \
done ); \
( cd classpath; \
find gnu java -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo `pwd`; \
echo $file; \
done ); \
) | \
jar -cfM@ $here/src.zip
find: `java': No such file or directory
here=`pwd`; \
( \
( cd ../../../src/libjava; \
find gnu java -name '*.java' -print | \
while read file; do \
echo x-C | sed -e 's/^.//'; \
echo ../../../src/libjava; \
echo $file; \
done ); \
) | \
jar -ufM@ $here/src.zip
make[2]: Leaving directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
touch stamps/05-build-javasrc-stamp
dh_testdir
dh_testroot
dh_installdirs -pgcj-4.9-source usr/share/java
/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
cp -p /«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava/src.zip \
debian/gcj-4.9-source/usr/share/java/libgcj-src-4.9.zip
dh_link -pgcj-4.9-source \
usr/share/java/libgcj-src-4.9.zip \
/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/src.zip
debian/dh_doclink -pgcj-4.9-source gcc-4.9-base
WARNING: removing doc directory gcj-4.9-source
debian/dh_rmemptydirs -pgcj-4.9-source
dh_compress -pgcj-4.9-source
dh_fixperms -pgcj-4.9-source
dh_gencontrol -pgcj-4.9-source -- -v4.9.1-19 '-Vlibgcc:Version=1:4.9.1-19'
'-Vgcc:Version=4.9.1-19' '-Vgcc:EpochVersion=1:4.9.1-19'
'-Vgcc:SoftVersion=4.9' '-Vgdc:Version=4.9.1-19' '-Vgcj:Version=4.9.1-19'
'-Vgcj:SoftVersion=4.9' '-Vgcj:BaseVersion=4.9' '-Vgnat:Version=4.9.1-19'
'-Vbinutils:Version=2.24.90.20141023' '-Vdep:libgcc=libgcc1 (= 1:4.9.1-19)'
'-Vdep:libgccdev=libgcc-4.9-dev (= 4.9.1-19)' '-Vdep:libgccbiarch=lib32gcc1
(= 1:4.9.1-19), libx32gcc1 (= 1:4.9.1-19)'
'-Vdep:libgccbiarchdev=lib32gcc-4.9-dev (= ${gcc:Version}), libx32gcc-4.9-dev
(= ${gcc:Version})' '-Vdep:libc=libc6 (= 2.11)' '-Vdep:libcdev=libc6-dev (=
2.13-5)' '-Vdep:libcbiarch=${shlibs:Depends}'
'-Vdep:libcbiarchdev=libc6-dev-i386 (= 2.11), libc6-dev-x32 (= 2.11)'
'-Vdep:libunwinddev=' '-Vdep:libcxxbiarchdev=lib32stdc++-4.9-dev (=
${gcc:Version}), libx32stdc++-4.9-dev (= ${gcc:Version})'
'-Vdep:libcxxbiarchdbg=lib32stdc++6-4.9-dbg (= ${gcc:Version}),
libx32stdc++6-4.9-dbg (= ${gcc:Version})' '-Vdep:libgnat='
'-Vdep:ecj=ecj-gcj, libecj-java-gcj (= 3.5.1)' '-Vdep:libcloog='
'-Vgcc:multilib=gcc-4.9-multilib' '-Vgxx:multilib=g++-4.9-multilib'
'-Vgobjc:multilib=gobjc-4.9-multilib'
'-Vgobjcxx:multilib=gobjc++-4.9-multilib'
'-Vgfortran:multilib=gfortran-4.9-multilib' '-Vdep:gold=binutils-gold (=
2.24.90.20141023)' '-Vdep:libgomp=libgomp1 (= ${gcc:Version})'
'-Vdep:libitm=libitm1 (= ${gcc:Version})'
Bug#769238: xaos: FTBFS in jessie/i386: zoom.c:156:18: error: conflicting types for 'fillline_8'
Control: tags -1 + confirmed patch
On Wed, Nov 12, 2014 at 11:16:05AM +0100, Lucas Nussbaum wrote:
[snip]
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386
[snip]
Relevant part (hopefully):
gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math
-march=pentiumpro -D_REENTRANT-I/usr/include -fomit-frame-pointer
-DSFFE_USING -DSFFE_CMPLX_GSL -I/«BUILDDIR»/xaos-3.5+ds1/src/include -c
-o zoom.o zoom.c
zoom.c:156:18: error: conflicting types for 'fillline_8'
#define fillline fillline_8
^
zoomd.c:283:20: note: in expansion of macro 'fillline'
static INLINE void fillline(int line)
^
zoom.c:144:13: note: previous declaration of 'fillline_8' was here
static void fillline_8(int line) REGISTERS(0);
[snip]
Hi Ansgar,
What do you think about the attached patch that adds a, well, a patch to
fix this failure to build by adding the REGISTERS(0) specification to
the function definitions, too, just as it is specified in the
prototypes?
The actual patch is in the first attachment; the second one is there
just to provide a sample changelog entry and to allow me to build the
package here :) Of course, if you agree, I could commit the change to
the pkg-games Git repo myself and then prepare a package and put it up
for sponsoring.
Thanks, both Ansgar and Lucas, for your unceasing Debian work!
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@freebsd.org p.penc...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
From d99242d375ff983f2fd278c76a2c96bcea34c988 Mon Sep 17 00:00:00 2001
From: Peter Pentchev r...@ringlet.net
Date: Wed, 12 Nov 2014 13:43:53 +0200
Subject: [PATCH 1/2] Fix the build on i386 - match the regparm attrs.
Add the REGISTERS(n) (a.k.a. __attribute__((regparm(n specification
to the definitions of two functions that already have it in their
prototypes.
Bug-Debian: https://bugs.debian.org/769238
---
debian/patches/engine-registers.patch | 26 ++
debian/patches/series | 1 +
2 files changed, 27 insertions(+)
create mode 100644 debian/patches/engine-registers.patch
diff --git a/debian/patches/engine-registers.patch
b/debian/patches/engine-registers.patch
new file mode 100644
index 000..057fac9
--- /dev/null
+++ b/debian/patches/engine-registers.patch
@@ -0,0 +1,26 @@
+Description: Fix the build on i386 - matching function definitions
+Debian-Bug: https://bugs.debian.org/769238
+Author: Peter Pentchev r...@ringlet.net
+Forwarded: not-yet
+Last-Update: 2014-11-12
+
+--- a/src/engine/zoom.c
b/src/engine/zoom.c
+@@ -933,6 +933,7 @@
+ }
+
+ #ifndef USE_i386ASM
++REGISTERS(0)
+ static /*INLINE */ void
+ moveoldpoints(void /*@unused@ */ *data1,
+ struct taskinfo /*@unused@ */ *task,
+--- a/src/engine/zoomd.c
b/src/engine/zoomd.c
+@@ -280,6 +280,7 @@
+ #endif
+ #undef bpp1
+
++REGISTERS(0)
+ static INLINE void fillline(int line)
+ {
+ register unsigned char *RESTRICT vbuff = cimage.currlines[line];
diff --git a/debian/patches/series b/debian/patches/series
index 2a31258..10415a8 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -3,3 +3,4 @@ free-static-string.patch
make.patch
window-size.patch
spelling.patch
+engine-registers.patch
--
2.1.1
From 6a066a589c429e62467c01122b1451e99c095556 Mon Sep 17 00:00:00 2001
From: Peter Pentchev r...@ringlet.net
Date: Wed, 12 Nov 2014 13:48:31 +0200
Subject: [PATCH 2/2] Add a changelog entry for the fix for #769238.
---
debian/changelog | 9 +
debian/control | 2 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index bb2253f..3637c70 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+xaos (3.5+ds1-2) UNRELEASED; urgency=medium
+
+ * Team upload.
+ * Add myself to Uploaders.
+ * Add the engine-registers patch to fix the build on i386 - match two
+functions' definitions with their prototypes. (Closes: #769238)
+
+ -- Peter Pentchev r...@ringlet.net Wed, 12 Nov 2014 13:46:54 +0200
+
xaos (3.5+ds1-1) unstable; urgency=low
* New upstream release. (Closes: #577739)
diff --git a/debian/control b/debian/control
index 26e5d8c..649373a 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: graphics
Priority: optional
Build-Depends: debhelper (= 7.0.50~), libaa1-dev, libx11-dev, libpng3-dev,
zlib1g-dev, libxext-dev, x11proto-core-dev, autoconf (= 2.63), autotools-dev,
libtool, libgsl0-dev
Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org
-Uploaders: Ansgar Burchardt ans...@debian.org
+Uploaders: Ansgar Burchardt ans...@debian.org, Peter Pentchev
r...@ringlet.net
Standards-Version: 3.8.4
Homepage: http://wmi.math.u-szeged.hu/xaos/
Vcs-Git: git://git.debian.org/git/pkg-games/xaos.git
--
2.1.1
signature.asc
Description
Processed: Re: Bug#769238: xaos: FTBFS in jessie/i386: zoom.c:156:18: error: conflicting types for 'fillline_8'
Processing control commands: tags -1 + confirmed patch Bug #769238 [src:xaos] xaos: FTBFS in jessie/i386: zoom.c:156:18: error: conflicting types for 'fillline_8' Added tag(s) confirmed and patch. -- 769238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768581: opal: FTBFS in experimental: error: 'CodecID' has not been declared
On 08/11/14 15:24, Andreas Beckmann wrote: Package: opal Version: 3.12.8~dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, opal/experimental fails to build in a current sid+experimental environment, see https://buildd.debian.org/status/fetch.php?pkg=opalarch=arm64ver=3.12.8~dfsg-1stamp=1414123156 [CC] .common/dyna.cxx In file included from ../common/ffmpeg.cxx:41:0: .../common/ffmpeg.h:123:30: error: 'CodecID' has not been declared virtual bool InitEncoder(CodecID codecId); ^ .../common/ffmpeg.h:124:30: error: 'CodecID' has not been declared virtual bool InitDecoder(CodecID codecId); ^ I could reproduce this rebuilding it for amd64 locally. For me, the version in experimental should be simply removed. Honestly, I prefer spending the little time I have on testing version, and or on version 3.14 or master upstream, as a developer. Kind regards, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769268: serf: FTBFS in jessie/i386: TypeError: Directory /usr/include/mit-krb5 found where file expected.:
Control: reassign -1 scons 2.3.1-1 Control: forcemerge 760804 -1 On Wed, Nov 12, 2014 at 11:55:24AM +0100, Lucas Nussbaum wrote: During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): debian/rules build QUILT_PATCHES=debian/patches \ quilt --quiltrc /dev/null push -a || test $? = 2 Applying patch libtool patching file SConstruct Now at patch libtool touch debian/stamp-patched dh_testdir scons GSSAPI=/usr CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro -Wl,-z,defs -Wl,--as-needed scons: Reading SConscript files ... TypeError: Directory /usr/include/mit-krb5 found where file expected.: Same issue you reported on amd64. Same reason. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769268: serf: FTBFS in jessie/i386: TypeError: Directory /usr/include/mit-krb5 found where file expected.:
Processing control commands:
reassign -1 scons 2.3.1-1
Bug #769268 [src:serf] serf: FTBFS in jessie/i386: TypeError: Directory
/usr/include/mit-krb5 found where file expected.:
Bug reassigned from package 'src:serf' to 'scons'.
No longer marked as found in versions serf/1.3.7-1.
Ignoring request to alter fixed versions of bug #769268 to the same values
previously set
Bug #769268 [scons] serf: FTBFS in jessie/i386: TypeError: Directory
/usr/include/mit-krb5 found where file expected.:
Marked as found in versions scons/2.3.1-1.
forcemerge 760804 -1
Bug #760804 {Done: Jörg Frings-Fürst deb...@jff-webhosting.net} [scons] serf:
FTBFS: Directory /usr/include/mit-krb5 found where file expected.
Bug #761565 {Done: Jörg Frings-Fürst deb...@jff-webhosting.net} [scons] serf:
FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected
Bug #765671 {Done: Jörg Frings-Fürst deb...@jff-webhosting.net} [scons] serf:
FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected.
Bug #768714 {Done: Jörg Frings-Fürst deb...@jff-webhosting.net} [scons] serf:
FTBFS in jessie: TypeError: Directory /usr/include/mit-krb5 found where file
expected.:
Bug #769268 [scons] serf: FTBFS in jessie/i386: TypeError: Directory
/usr/include/mit-krb5 found where file expected.:
Set Bug forwarded-to-address to
'https://bitbucket.org/scons/scons/pull-request/184/support-isystem-in-parseflags/diff'.
Marked Bug as done
Owner recorded as Jörg Frings-Fürst deb...@jff-webhosting.net.
Added indication that 769268 affects serf,src:serf
Marked as fixed in versions scons/2.3.1-2.
Added tag(s) patch.
Bug #761565 {Done: Jörg Frings-Fürst deb...@jff-webhosting.net} [scons] serf:
FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected
Bug #765671 {Done: Jörg Frings-Fürst deb...@jff-webhosting.net} [scons] serf:
FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected.
Bug #768714 {Done: Jörg Frings-Fürst deb...@jff-webhosting.net} [scons] serf:
FTBFS in jessie: TypeError: Directory /usr/include/mit-krb5 found where file
expected.:
Merged 760804 761565 765671 768714 769268
--
760804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760804
761565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761565
765671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765671
768714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768714
769268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-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
Hi, On 12/11/14 at 11:27 +0100, Martin Quinson wrote: Hello, I must confess that I fail to reproduce your bug. it seems to me that the bug comes from a strange setting in LC_ALL. # locale LANG= LANGUAGE= LC_CTYPE=POSIX LC_NUMERIC=POSIX LC_TIME=POSIX LC_COLLATE=POSIX LC_MONETARY=POSIX LC_MESSAGES=POSIX LC_PAPER=POSIX LC_NAME=POSIX LC_ADDRESS=POSIX LC_TELEPHONE=POSIX LC_MEASUREMENT=POSIX LC_IDENTIFICATION=POSIX LC_ALL= before the java compiler, msggrep complains that ANSI_X3.4-1968 is not a valid value for UTF-encoded files. Did your chroot have any unconventional settings with that regard? No. Also, I did not notice any other locale-related failure while filing bugs. Lucas signature.asc Description: Digital signature
Bug#769238: marked as done (xaos: FTBFS in jessie/i386: zoom.c:156:18: error: conflicting types for 'fillline_8')
Your message dated Wed, 12 Nov 2014 13:04:36 + with message-id e1xoxba-0001it...@franck.debian.org and subject line Bug#769238: fixed in xaos 3.5+ds1-2 has caused the Debian Bug report #769238, regarding xaos: FTBFS in jessie/i386: zoom.c:156:18: error: conflicting types for 'fillline_8' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xaos Version: 3.5+ds1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): gcc -O3 -fomit-frame-pointer -malign-double -fstrict-aliasing -ffast-math -march=pentiumpro -D_REENTRANT-I/usr/include -fomit-frame-pointer -DSFFE_USING -DSFFE_CMPLX_GSL -I/«BUILDDIR»/xaos-3.5+ds1/src/include -c -o zoom.o zoom.c zoom.c:156:18: error: conflicting types for 'fillline_8' #define fillline fillline_8 ^ zoomd.c:283:20: note: in expansion of macro 'fillline' static INLINE void fillline(int line) ^ zoom.c:144:13: note: previous declaration of 'fillline_8' was here static void fillline_8(int line) REGISTERS(0); ^ zoom.c:163:18: error: conflicting types for 'fillline_32' #define fillline fillline_32 ^ zoomd.c:283:20: note: in expansion of macro 'fillline' static INLINE void fillline(int line) ^ zoom.c:147:13: note: previous declaration of 'fillline_32' was here static void fillline_32(int line) REGISTERS(0); ^ zoom.c:170:18: error: conflicting types for 'fillline_24' #define fillline fillline_24 ^ zoomd.c:283:20: note: in expansion of macro 'fillline' static INLINE void fillline(int line) ^ zoom.c:146:13: note: previous declaration of 'fillline_24' was here static void fillline_24(int line) REGISTERS(0); ^ zoom.c:177:18: error: conflicting types for 'fillline_16' #define fillline fillline_16 ^ zoomd.c:283:20: note: in expansion of macro 'fillline' static INLINE void fillline(int line) ^ zoom.c:145:13: note: previous declaration of 'fillline_16' was here static void fillline_16(int line) REGISTERS(0); ^ zoom.c:937:1: error: conflicting types for 'moveoldpoints' moveoldpoints(void /*@unused@ */ *data1, ^ zoom.c:142:1: note: previous declaration of 'moveoldpoints' was here moveoldpoints(void *data1, struct taskinfo *task, int r1, int r2) ^ make[3]: *** [zoom.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/xaos_3.5+ds1-1_jessie-i386.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. ---End Message--- ---BeginMessage--- Source: xaos Source-Version: 3.5+ds1-2 We believe that the bug you reported is fixed in the latest version of xaos, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt ans...@debian.org (supplier of updated xaos package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 12 Nov 2014 13:46:40 +0100 Source: xaos Binary: xaos Architecture: source Version: 3.5+ds1-2 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Ansgar Burchardt ans...@debian.org Description: xaos - real-time interactive fractal zoomer Closes: 769238 Changes: xaos (3.5+ds1-2) unstable; urgency=low . [ Peter Pentchev ] * Add the engine-registers patch to fix the build
Bug#757037: liblzop alignment problem
On 12/11/14 10:51, Marc Kleine-Budde wrote:
On 11/12/2014 01:20 AM, Simon McVittie wrote:
Translated to debian this mean: armel - unaligned access will
silently fail on = ARMv5 (unless configured otherwise in
/proc/cpu/alignment) will work if run on = ARMv6, e.g. Raspberry
Pi, Beagle Bone But usually you would use armhf on such a system.
armhf - ok with unaligned access
If the lzo2 maintainer would prefer, I'd be happy to adapt my patch to
allow unaligned accesses on additional architectures, or to swap the
assumption around so that it only forbids unaligned architectures on
specific architectures (which should include armel, and I don't
personally care about any others, but the mips* porters might).
If we need to differentiate between armel and armhf then it will be
necessary to use DEB_HOST_ARCH instead of DEB_HOST_ARCH_CPU (both
armel and armhf have arm as their DEB_HOST_ARCH_CPU), with something
like:
# whitelist approach
ifeq ($(filter amd64 %-amd64 i386 %-i386 armhf,$(DEB_HOST_ARCH)),)
# neither x86 family nor armhf: unaligned accesses are not good
endif
or
# blacklist approach
ifeq ($(filter-out armel mips%,$(DEB_HOST_ARCH)),)
# armel or mips-family: unaligned accesses are not good
endif
However, I will not be able to test on a baseline specimen of each
Debian architecture, because Debian porterboxes are not guaranteed to
match the baseline for the architecture: armel porterboxes are likely
to be better than armv5 in practice, i386 porterboxes are definitely
better than i586, and so on.
The only non-porterbox machines that I can personally test are an
armv5tel and a modern x86-64.
liblzo2 does actually try to avoid using unsafe unaligned
accesses by using a structure
typedef struct lzo_memops_TU2_struct { unsigned char a[2]; }
lzo_memops_TU2;
and only doing a type-punning assignment similar to[1]
*(lzo_memops_TU2 *) (void *) dest = *(const lzo_memops_TU2 *)
(void *) src;
Which AFAIK should boil down to some kind of memcpy() with compile
time constant length.
That's what I'd expect too, but judging by the failure we're seeing,
it looks as though the compiler might be producing a single load
16-bit instruction, which is considerably cheaper but assumes alignment.
S
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769212: [debian-mysql] Bug#769212: mariadb-10.0: FTBFS in jessie: Tests failures
On 12/11/14 at 15:30 +0200, Otto Kekäläinen wrote: I've analyzed the log and found the issue (test comparison failed due to capitalization issues in the word USER vs user). With the help of upstream a patch has been produced and I've tested it and pushed it in commit http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=8f5470f7d7d60368c1e4a9d270addcd7205f2f71 Shall I now proceed to upload this to normal Debian unstable despite the freeze as this is a serious FTBFS bug? yes, but limit the changes to a minimum due to the freeze. Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769212: [debian-mysql] Bug#769212: mariadb-10.0: FTBFS in jessie: Tests failures
I've analyzed the log and found the issue (test comparison failed due to capitalization issues in the word USER vs user). With the help of upstream a patch has been produced and I've tested it and pushed it in commit http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=8f5470f7d7d60368c1e4a9d270addcd7205f2f71 Shall I now proceed to upload this to normal Debian unstable despite the freeze as this is a serious FTBFS bug? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769257: python-tblib: FTBFS in jessie/i386: Tests failures
On 12/11/14 at 11:19 +, Colin Watson wrote: On Wed, Nov 12, 2014 at 11:41:24AM +0100, Lucas Nussbaum wrote: During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. I think this might be a bug in your build setup. Here's the point where it starts going wrong: File /«PKGBUILDDIR»/tests/../README.rst, line 195, in README.rst Failed example: pool = Pool() Exception raised: Traceback (most recent call last): File /usr/lib/python2.7/doctest.py, line 1315, in __run compileflags, 1) in test.globs File doctest README.rst[32], line 1, in module pool = Pool() File /usr/lib/python2.7/multiprocessing/__init__.py, line 232, in Pool return Pool(processes, initializer, initargs, maxtasksperchild) File /usr/lib/python2.7/multiprocessing/pool.py, line 138, in __init__ self._setup_queues() File /usr/lib/python2.7/multiprocessing/pool.py, line 234, in _setup_queues self._inqueue = SimpleQueue() File /usr/lib/python2.7/multiprocessing/queues.py, line 352, in __init__ self._rlock = Lock() File /usr/lib/python2.7/multiprocessing/synchronize.py, line 147, in __init__ SemLock.__init__(self, SEMAPHORE, 1, 1) File /usr/lib/python2.7/multiprocessing/synchronize.py, line 75, in __init__ sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) OSError: [Errno 13] Permission denied This looks as though sem_open is failing, which I think is likely to be because /dev/shm is not properly mounted. Perhaps the sbuild setup here is missing a tmpfs mount on /dev/shm? Indeed. Sorry for the noise. It's #769289 in sbuild. (I already closed the bug earlier today) Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Pkg-mozext-maintainers] Bug#769231: xul-ext-adblock-plus: incompatible with iceweasel in stable-security
Processing control commands: severity -1 serious Bug #769231 [xul-ext-adblock-plus] xul-ext-adblock-plus: incompatible with iceweasel in stable-security Severity set to 'serious' from 'wishlist' fixed -1 2.6.5+dfsg-1 Bug #769231 [xul-ext-adblock-plus] xul-ext-adblock-plus: incompatible with iceweasel in stable-security Marked as fixed in versions adblock-plus/2.6.5+dfsg-1. -- 769231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768732: plm: FTBFS in jessie: src/plm/core/model/Game.java:97: error: unmappable character for encoding ASCII
Processing commands for cont...@bugs.debian.org: retitle 768732 plm: FTBFS in non-UTF-8 settings Bug #768732 [src:plm] plm: FTBFS in jessie: src/plm/core/model/Game.java:97: error: unmappable character for encoding ASCII Changed Bug title to 'plm: FTBFS in non-UTF-8 settings' from 'plm: FTBFS in jessie: src/plm/core/model/Game.java:97: error: unmappable character for encoding ASCII' thanks Stopping processing here. Please contact me if you need assistance. -- 768732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769273: bsdutils: Dependency on libsystemd0 violates policy
Hello Tim Wootton, release-team, et.al.! Thanks for your bug report. On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote: Package: bsdutils Version: 1:2.25.2-2 Severity: serious Justification: Policy 2.5 Dear Maintainer, libsystemd0 dependancy violates constraint at the end of section 2.5 of the policy manual that requires packages not depend on packages with lower priority. This (general) problem has been discussed (several times?) on debian-devel already and as far as I remember and understood it was that raising the priority of the relevant systemd binary packages could be done but it did not solve any *practical* problem. Instead it seemed easier to just fix policy. I guess that's where everyone lost interest I'd like to defer this issue to release team to decide what the best course of action is. They can decide if this is a wontfix/jessie-ignore, if policy editors must update the policy before the jessie release or if systemd maintainers needs to adjust their priority. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-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
retitle 768732 plm: FTBFS in non-UTF-8 settings thanks Hello, thanks for this additional information, that's indeed the source of the problem. The PLM package builds correctly if I set LC_ALL=C.UTF-8 in addition to your settings and fails without it. But, it seems to me that the package built with non-utf locale settings will not be functionnal for non-english speakers. At least that's what I understand from the msggrep warnings. Could you please point me to the part of the policy that is relevant to the locale settings of the builder? I fail to find anything relevant by myself, sorry. In the meanwhile, I will patch most of the java files to not use the UTF encoding. I'm just reluctant do so in some cases where it would not be an improvement. For example, it would request to write the name of Gérald Oster as Gerald Oster. Not a big deal, but not nice. I guess that it would not be ok to set LC_ALL=C.UTF-8 in the rules file, right? Thanks for your patience and sorry for the complications, Mt. On Wed, Nov 12, 2014 at 01:34:04PM +0100, Lucas Nussbaum wrote: Hi, On 12/11/14 at 11:27 +0100, Martin Quinson wrote: Hello, I must confess that I fail to reproduce your bug. it seems to me that the bug comes from a strange setting in LC_ALL. # locale LANG= LANGUAGE= LC_CTYPE=POSIX LC_NUMERIC=POSIX LC_TIME=POSIX LC_COLLATE=POSIX LC_MONETARY=POSIX LC_MESSAGES=POSIX LC_PAPER=POSIX LC_NAME=POSIX LC_ADDRESS=POSIX LC_TELEPHONE=POSIX LC_MEASUREMENT=POSIX LC_IDENTIFICATION=POSIX LC_ALL= before the java compiler, msggrep complains that ANSI_X3.4-1968 is not a valid value for UTF-encoded files. Did your chroot have any unconventional settings with that regard? No. Also, I did not notice any other locale-related failure while filing bugs. Lucas -- HARDWARE n.m.: partie de l'ordinateur qui reçoit les coups quand le software se plante. signature.asc Description: Digital signature
Bug#769261: sslh: FTBFS in jessie/i386: Build killed with signal TERM after 150 minutes of inactivity
On Wed, Nov 12, 2014 at 11:41:57AM +0100, Lucas Nussbaum wrote: Source: sslh Version: 1.16-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): You've missed a relevant part from the build log: [...] ./sslh-select -v -f -u user --listen localhost:9002 --ssh ::1:9000 --ssl ::1:9001 -P /tmp/sslh_test.pid ssh addr: localhost:9000. libwrap service: sshd family 10 10 ssl addr: localhost:9001. libwrap service: (null) family 10 10 listening on: localhost:9002 localhost:9002 timeout: 2 on-timeout: ssh listening to 2 addresses localhost:9002:bind: Address already in use [...] Apparently, the bind of localhost:9002 fail on this machine, is there any other process listening on this socket ? ***Test: One SSL half-started then one SSH Connection refused ***Test: One SSH half-started then one SSL Connection refused cat: /tmp/sslh_test.pid: No such file or directory killing Can't kill a non-numeric process ID at ./t line 221. # Looks like your test exited with 1 before it could output anything. make[1]: *** [test] Error 1 Makefile:99: recipe for target 'test' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_test: make -j1 test returned exit code 2 make: *** [build] Error 2 debian/rules:31: recipe for target 'build' failed dpkg-buildpackage: error: debian/rules build gave error exit status 2 Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/sslh_1.16-2_jessie-i386.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. -- Guillaume Delacour signature.asc Description: Digital signature
Bug#769161: [pkg-firebird-general] Bug#769161: Bug#769161: ppc64el port is wrong
Seems that i have copied the prefix from trunk , now i fixed and added the lines OS_ServerFiles=inet_server.cpp EMBED_UTIL_TARGETS=gstat gds_relay gsec nbackup fb_lock_print fbguard fbsvcmgr fbtracemgr CLIENT_UTIL_TARGETS=gstat gds_relay gsec nbackup fb_lock_print fbguard fbmgr_bin fbsvcmgr fbtracemgr Physical_IO_Module=unix.cpp just a quick test /opt/firebird2.5/bin/isql employee.fdb Database: employee.fdb SQL show version CON ; ISQL Version: LI-V2.5.3.26799 Firebird 2.5 Server version: Firebird/linux PPC64EL (access method), version LI-V2.5.3.26799 Firebird 2.5 on disk structure version 11.2 On Wed, Nov 12, 2014 at 1:48 PM, marius adrian popa map...@gmail.com wrote: I have committed to both 3.0 and 2.5 branches Here is the 2.5 list of patches (you can diff it with the release branch) https://sourceforge.net/p/firebird/code/60194/ https://sourceforge.net/p/firebird/code/60195/ https://sourceforge.net/p/firebird/code/60198/ https://sourceforge.net/p/firebird/code/60201/ In the last patch I have add an ARM64 define twice in common.h , but corrected after that On Tue, Nov 11, 2014 at 10:16 PM, Damyan Ivanov d...@debian.org wrote: Package: src:firebird2.5 Subject: firebird2.5: ppc64el built as bigendian Version: 2.5.3.26778.ds4-2 Severity: serious Justification: possible data corruption -=| marius adrian popa, 11.11.2014 15:57:19 +0200 |=- From the build log i see that ppc64el is treated like a bigendian port https://buildd.debian.org/status/fetch.php?pkg=firebird2.5arch=ppc64elver=2.5.3.26778.ds4-3%2Bb1stamp=1415464014 Good catch. Forwarding as a bugreport. In my understanding this would cause data corruption when transferring data between ppc64el client/server and a non ppc64-el system -- doubles and big integers would be swapped when there's no need to and won't be swapped when there is need to do so. We need to create a new port for it Please let me know when the implementation ID/patch/commit is available. -- Damyan ___ pkg-firebird-general mailing list pkg-firebird-gene...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-firebird-general ___ pkg-firebird-general mailing list pkg-firebird-gene...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-firebird-general
Bug#769273: bsdutils: Dependency on libsystemd0 violates policy
Am 12.11.2014 um 15:04 schrieb Andreas Henriksson: Hello Tim Wootton, release-team, et.al.! Thanks for your bug report. On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote: Package: bsdutils Version: 1:2.25.2-2 Severity: serious Justification: Policy 2.5 Dear Maintainer, libsystemd0 dependancy violates constraint at the end of section 2.5 of the policy manual that requires packages not depend on packages with lower priority. This (general) problem has been discussed (several times?) on debian-devel already and as far as I remember and understood it was that raising the priority of the relevant systemd binary packages could be done but it did not solve any *practical* problem. Instead it seemed easier to just fix policy. I guess that's where everyone lost interest Indeed, it doesn't fix any actual problem, but raising priority of library and helper packages actually creates problems. Let's take rsyslog as an example, which is priority important, so raising all the library dependencies to = important now means, if I debootstrap a chroot and want to exclude rsyslog, I have to exclude all dependend libraries as well. Or if I remove rsyslog (e.g. because I switched to another syslogger or no syslogger), I have to manually uninstall the unused libraries. Please, let's not continue doing this non-sense and fix policy. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#766943: systemd: server no longer gets networking after switching to systemd
Am 12.11.2014 um 05:04 schrieb Cameron Norman: On Tue, 11 Nov 2014 20:05:53 +0100 Michael Biebl bi...@debian.org wrote: Am 11.11.2014 um 20:01 schrieb Michael Biebl: Attached is a patch against /etc/init.d/networking. While we discussed yesterday, to only run udevadm settle if there are any auto interfaces, I changed it, to also cover allow-hotplug. I also changed the init script to handle allow-hotplug interfaces. [..] Please test and report back. Grr, the attached patch had a typo, please try this v2. So with this change, $network and network.target mean that all interfaces marked auto or allow-hotplug have been configured, or hotplug events have been settled and as many interfaces as could be brought up have been, correct? And if an auto interface is never brought up, that is ignored after udev settles? Are you sure that is desired behavior, seeing as allow-hotplug is the only configuration that explicitly references hotplug devices/events? I'm not quite sure what problem you're referring too, please elaborate. If you are using auto for an interface which is plugged in after /etc/init.d/networking start has been run, then yeah, it won't be configured. But the patch doesn't change that. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#768723: (no subject)
On Wed, Nov 12, 2014 at 10:57:30AM +0900, Youhei SASAKI wrote: Tags: moreinfo Tags: help Hi, This bug is unreproducible by my pbuilder/cowbuilder environments. Thus I'll try setup sbuild for check this bug. If someone who has jessies's sbuild environments, please try rebuild this package and send report me. I can't reproduce this with sbuild in either sid or jessie; both build just fine. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#769273: bsdutils: Dependency on libsystemd0 violates policy
On Wed, Nov 12, 2014 at 03:04:56PM +0100, Andreas Henriksson wrote: Hello Tim Wootton, release-team, et.al.! Thanks for your bug report. On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote: Package: bsdutils Version: 1:2.25.2-2 Severity: serious Justification: Policy 2.5 Dear Maintainer, libsystemd0 dependancy violates constraint at the end of section 2.5 of the policy manual that requires packages not depend on packages with lower priority. This (general) problem has been discussed (several times?) on debian-devel already and as far as I remember and understood it was that raising the priority of the relevant systemd binary packages could be done but it did not solve any *practical* problem. Instead it seemed easier to just fix policy. I guess that's where everyone lost interest It is well settled that priority changes are done throught the distribution override file and not in the package control file and thus, an error of priority is not a RC bug in the package. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769273: re Bug#769273: bsdutils: Dependency on libsystemd0 violates policy - like hundreds of others
Hi, 1752 packages are listed to violate this same policy: https://qa.debian.org/debcheck.php?dist=sidlist=main-only-priorityarch=ANY policy discussion about this is happening at #758234 Riku -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769273: bsdutils: Dependency on libsystemd0 violates policy
Am 12.11.2014 um 15:35 schrieb Bill Allombert: It is well settled that priority changes are done throught the distribution override file and not in the package control file and thus, an error of priority is not a RC bug in the package. And that. Adjusting library package priorities is useless busy work for our ftp-masters and wasting their scarce time which they could better spend elsewhere. It's often followed by a source package upload as well, where the maintainer adjusts debian/control to match what's in the archive, creating more busy work. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#768732: plm: FTBFS in jessie: src/plm/core/model/Game.java:97: error: unmappable character for encoding ASCII
On 12/11/14 at 15:06 +0100, Martin Quinson wrote: retitle 768732 plm: FTBFS in non-UTF-8 settings thanks Hello, thanks for this additional information, that's indeed the source of the problem. The PLM package builds correctly if I set LC_ALL=C.UTF-8 in addition to your settings and fails without it. But, it seems to me that the package built with non-utf locale settings will not be functionnal for non-english speakers. At least that's what I understand from the msggrep warnings. Could you please point me to the part of the policy that is relevant to the locale settings of the builder? I fail to find anything relevant by myself, sorry. I'm not sure if this is specified. my chroot is generated by sbuild-createchroot, without any further customization. One could argue that sbuild could default to C.UTF-8, but OTOH, all other packages build fine (or fail for unrelated reasons). In the meanwhile, I will patch most of the java files to not use the UTF encoding. I'm just reluctant do so in some cases where it would not be an improvement. For example, it would request to write the name of Gérald Oster as Gerald Oster. Not a big deal, but not nice. couldn't you build with javac -encoding UTF-8? See http://stackoverflow.com/questions/1726174/how-to-compile-a-java-source-file-which-is-encoded-as-utf-8 Regarding the msggrep warnings, I'm not sure if they are really harmless. I guess that it would not be ok to set LC_ALL=C.UTF-8 in the rules file, right? That would probably work, yes. Lucas signature.asc Description: Digital signature
Bug#766920: initramfs-tools: update-initramfs makes system unbootable due to missing rootfs
On Mon, 27 Oct 2014 00:54:54 + Ben Hutchings b...@decadent.org.uk wrote: Processing triggers for initramfs-tools (0.116) ... update-initramfs: Generating /boot/initrd.img-3.16-3-amd64 /803: No such file or directory [update continues] After a reboot, the system is unbootable due to a missing rootfs. [...] We support hexadecimal device numbers in the 'root=' kernel parameter when booting, but do not expect to see them at build time in the mount table. [..] You are recommended to specify the root device on the kernel command line using the syntax 'root=UUID=...' Setting fstab to UUID does not make any difference, OTOH, setting lilo.conf to root=UUID=x resolves the problem. The command mount does not show up with 803 anymore. As an initramfs nitwit, I'd say it seems to be a bug anyway. Am I right or wrong? R. -- ___ It is better to remain silent and be thought a fool, than to speak aloud and remove all doubt. +--+ | Richard Lucassen, Utrecht| +--+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: beignet: yes, we know 0.8-1.1 now FTBFS...
Processing commands for cont...@bugs.debian.org:
reassign 768691 beignet
Bug #768691 [src:beignet] beignet: FTBFS in jessie: /bin/sh: 1: llvm-as-3.4:
not found
Bug reassigned from package 'src:beignet' to 'beignet'.
No longer marked as found in versions beignet/0.8-1.1.
Ignoring request to alter fixed versions of bug #768691 to the same values
previously set
forcemerge 764930 768691
Bug #764930 {Done: Andreas Beckmann a...@debian.org} [beignet] beignet: FTBFS
- uses versioned llvm commands, but unversioned build dependency
Bug #764930 {Done: Andreas Beckmann a...@debian.org} [beignet] beignet: FTBFS
- uses versioned llvm commands, but unversioned build dependency
Added tag(s) sid and jessie.
Bug #768691 [beignet] beignet: FTBFS in jessie: /bin/sh: 1: llvm-as-3.4: not
found
Marked Bug as done
Marked as fixed in versions beignet/0.9.3~dfsg-1.
Marked as found in versions beignet/0.8-1.1.
Added tag(s) patch.
Merged 764930 768691
End of message, stopping processing here.
Please contact me if you need assistance.
--
764930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764930
768691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
