Bug#860612: debian-parl: FTBFS: unsatisfiable build-dependency: boxer-data (>= 10.5.18) but 10.5.15 is to be installed
Source: debian-parl Version: 1.9.10 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, debhelper, dh-buildinfo, boxer (>= 0.004~), > dpkg-dev (>= 1.17.0), shellcheck, boxer-data (>= 10.5.18), boxer-data (<< > 10.6) > Filtered Build-Depends: cdbs, debhelper, dh-buildinfo, boxer (>= 0.004~), > dpkg-dev (>= 1.17.0), shellcheck, boxer-data (>= 10.5.18), boxer-data (<< > 10.6) > dpkg-deb: building package 'sbuild-build-depends-debian-parl-dummy' in > '/<>/resolver-MTSFkl/apt_archive/sbuild-build-depends-debian-parl-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-debian-parl-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-MTSFkl/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-MTSFkl/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-MTSFkl/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-MTSFkl/apt_archive ./ Sources [548 B] > Get:5 copy:/<>/resolver-MTSFkl/apt_archive ./ Packages [632 B] > Fetched 2143 B in 0s (0 B/s) > Reading package lists... > W: No sandbox user '_apt' on the system, can not drop privileges > Reading package lists... > > Install debian-parl 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-debian-parl-dummy : Depends: boxer-data (>= 10.5.18) > but 10.5.15 is 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/2017/04/18/debian-parl_1.9.10_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU
Hei, Denne patchen: https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/tree/debian/patches/fix_use_after_free_in_mysql_prune_stmt_list.patch?h=debian/wheezy Ble lagt til (kun debian 7) for 5.5.54, og får konflikt i 5.5.55. Har du tid til å ta en titt og evt. lage oppdatert patch? -- Lars - norvald.ry...@oracle.com wrote: > Source: mysql-5.5 > Version: 5.5.54-0+deb8u1 > Severity: grave > Tags: security upstream fixed-upstream > > The Oracle Critical Patch Update for April 2017 will be released on > Tuesday, April 18. According to the pre-release announcement [1], it > > will contain information about CVEs fixed in MySQL 5.5.55. > > The CVE numbers will be available when the CPU is released. > > Please note that the MySQL release cycle has changed from every two > months to every three months. The releases are now synchronized with > the CPU announcements. > > Best regards, > > Norvald H. Ryeng > > [1] > http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html > > ___ > pkg-mysql-maint mailing list > pkg-mysql-ma...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
Bug#860611: dsniff: FTBFS: ld: cannot find -lmissing
Source: dsniff Version: 2.4b1+debian-24 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > x86_64-linux-gnu-gcc -Wl,-z,relro -Wl,-z,now -o macof macof.o -lresolv -lnsl > -lrpcsvc -L. -lmissing -L/usr/lib -lpcap -L/usr/lib -lnet > /usr/bin/ld: cannot find -lmissing > collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/2017/04/18/dsniff_2.4b1+debian-24_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#860610: gnat-mingw-w64: FTBFS: make[3]: *** No rule to make target 'gcov-dump.texi', needed by 'gcov-dump.pod'. Stop.
Source: gnat-mingw-w64 Version: 19.3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory > '/<>/build/i686-w64-mingw32-posix/gcc' > TARGET_CPU_DEFAULT="" \ > HEADERS="auto-host.h ansidecl.h" DEFINES="" \ > /bin/bash ../../../src/gcc/mkconfig.sh config.h > TARGET_CPU_DEFAULT="" \ > HEADERS="options.h insn-constants.h config/vxworks-dummy.h config/i386/i386.h > config/i386/unix.h config/i386/bsd.h config/i386/gas.h config/dbxcoff.h > config/i386/cygming.h config/i386/mingw-pthread.h config/i386/mingw32.h > config/i386/mingw-w64.h config/i386/mingw-stdint.h config/initfini-array.h > defaults.h" DEFINES="LIBC_GLIBC=1 LIBC_UCLIBC=2 LIBC_BIONIC=3 LIBC_MUSL=4" \ > /bin/bash ../../../src/gcc/mkconfig.sh tm.h > TARGET_CPU_DEFAULT="" \ > HEADERS="config/i386/i386-protos.h tm-preds.h" DEFINES="" \ > /bin/bash ../../../src/gcc/mkconfig.sh tm_p.h > configure: creating cache ./config.cache > TARGET_CPU_DEFAULT="" \ > HEADERS="auto-host.h ansidecl.h" DEFINES="" \ > /bin/bash ../../../src/gcc/mkconfig.sh bconfig.h > g++-6 -c -g -O2 -fdebug-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wall > -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti > -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings > -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic > -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H > -DGENERATOR_FILE -fno-PIE -I. -Ibuild -I../../../src/gcc > -I../../../src/gcc/build -I../../../src/gcc/../include > -I../../../src/gcc/../libcpp/include -Wdate-time -D_FORTIFY_SOURCE=2 \ > -DBASEVER="\"6.3.0\"" -DDATESTAMP="\" 20170406\"" \ > -DREVISION="\"\"" \ > -DDEVPHASE="\"\"" -DPKGVERSION="\"(GCC) \"" \ > -DBUGURL="\"<http://gcc.gnu.org/bugs.html>\"" -o build/version.o > ../../../src/gcc/version.c > gawk -f ../../../src/gcc/opt-gather.awk > ../../../src/gcc/ada/gcc-interface/lang.opt ../../../src/gcc/c-family/c.opt > ../../../src/gcc/common.opt ../../../src/gcc/fortran/lang.opt > ../../../src/gcc/go/lang.opt ../../../src/gcc/java/lang.opt > ../../../src/gcc/lto/lang.opt ../../../src/gcc/config/fused-madd.opt > ../../../src/gcc/config/i386/i386.opt > ../../../src/gcc/config/i386/cygming.opt > ../../../src/gcc/config/i386/mingw.opt > ../../../src/gcc/config/i386/mingw-w64.opt > tmp-optionlist > checking build system type... x86_64-pc-linux-gnu > checking host system type... x86_64-pc-linux-gnu > checking target system type... i686-w64-mingw32 > checking for x86_64-linux-gnu-gcc... gcc-6 > /bin/bash ../../../src/gcc/../move-if-change tmp-gi.list gtyp-input.list > echo "#define BUILDING_GCC_MAJOR `echo 6.3.0 | sed -e > 's/^\([0-9]*\).*$/\1/'`" > bversion.h > if test no = yes \ >|| test -n "../lib64 ../lib"; then \ > /bin/bash ../../../src/gcc/genmultilib \ > "m64/m32" \ > "64 32" \ > "" \ > "" \ > "" \ > "" \ > "../lib64 ../lib" \ > "" \ > "" \ > "" \ > "no" \ > > tmp-mlib.h; \ > else \ > /bin/bash ../../../src/gcc/genmultilib '' '' '' '' '' '' '' '' \ > "" '' no \ > > tmp-mlib.h; \ > fi > echo "#define BUILDING_GCC_MINOR `echo 6.3.0 | sed -e > 's/^[0-9]*\.\([0-9]*\).*$/\1/'`" >> bversion.h > lsf="../../../src/gcc/ada/gcc-interface/lang-specs.h > ../../../src/gcc/lto/lang-specs.h"; for f in $lsf; do \ > echo "#include \"$f\""; \ > done | sed 's|../../../src/gcc/||' > tmp-specs.h > rm -f tmp-all-tree.def > echo timestamp > s-gtyp-input > echo "#define BUILDING_GCC_PATCHLEVEL `echo 6.3.0 | sed -e > 's/^[0-9]*\.[0-9]*\.\([0-9]*\)$/\1/'`" >> bversion.h > /bin/bash ../../../src/gcc/../move-if-change tmp-specs.h specs.h > echo '#include "tree.def"' > tmp-all-tree.def > gawk -f ../../../src/gcc/gen-pass-instances.awk \ > ../../../src/gcc/passes.def > pass-inst
Bug#860609: influxdb: FTBFS: Test failures
Source: influxdb Version: 1.1.1+dfsg1-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > --- PASS: TestTSMWriter_Write_MaxKey (1.42s) > [tsm1] 2017/04/18 22:30:50 Snapshot for path /tmp/tsm1-930652078/data written > in 4.939975ms > [tsm1] 2017/04/18 22:30:50 Snapshot for path /tmp/tsm1-248119605/data written > in 4.998884ms > --- PASS: TestEngine_CreateIterator_Cache_Ascending (2.00s) > --- PASS: TestEngine_CreateIterator_Aux (2.00s) > --- PASS: TestEngine_CreateIterator_TSM_Ascending (2.00s) > --- PASS: TestEngine_CreateIterator_Cache_Descending (2.00s) > --- PASS: TestEngine_CreateIterator_TSM_Descending (2.00s) > --- PASS: TestEngine_CreateIterator_Condition (2.00s) > FAIL > exit status 1 > FAIL github.com/influxdata/influxdb/tsdb/engine/tsm1 54.021s > ? github.com/influxdata/influxdb/tsdb/internal[no test files] > ? github.com/influxdata/influxdb/uuid [no test files] > dh_auto_test: go test -v -p 1 -timeout 12000s github.com/influxdata/influxdb > github.com/influxdata/influxdb/client > github.com/influxdata/influxdb/client/v2 github.com/influxdata/influxdb/cmd > github.com/influxdata/influxdb/cmd/influx > github.com/influxdata/influxdb/cmd/influx/cli > github.com/influxdata/influxdb/cmd/influx_inspect > github.com/influxdata/influxdb/cmd/influx_inspect/dumptsm > github.com/influxdata/influxdb/cmd/influx_inspect/export > github.com/influxdata/influxdb/cmd/influx_inspect/help > github.com/influxdata/influxdb/cmd/influx_inspect/report > github.com/influxdata/influxdb/cmd/influx_inspect/verify > github.com/influxdata/influxdb/cmd/influx_stress > github.com/influxdata/influxdb/cmd/influx_tsm > github.com/influxdata/influxdb/cmd/influx_tsm/b1 > github.com/influxdata/influxdb/cmd/influx_tsm/bz1 > github.com/influxdata/influxdb/cmd/influx_tsm/stats > github.com/influxdata/influxdb/cmd/influx_tsm/tsdb > github.com/influxdata/influxdb/cmd/influx_tsm/tsdb/internal > github.com/influxdata/influxdb/cmd/influxd > github.com/influxdata/influxdb/cmd/influxd/backup > github.com/influxdata/influxdb/cmd/influxd/help > github.com/influxdata/influxdb/cmd/influxd/restore > github.com/influxdata/influxdb/cmd/influxd/run > github.com/influxdata/influxdb/coordinator > github.com/influxdata/influxdb/importer/v8 > github.com/influxdata/influxdb/influxql > github.com/influxdata/influxdb/influxql/internal > github.com/influxdata/influxdb/influxql/neldermead > github.com/influxdata/influxdb/internal github.com/influxdata/influxdb/models > github.com/influxdata/influxdb/monitor > github.com/influxdata/influxdb/monitor/diagnostics > github.com/influxdata/influxdb/pkg/deep > github.com/influxdata/influxdb/pkg/escape > github.com/influxdata/influxdb/pkg/limiter > github.com/influxdata/influxdb/pkg/pool > github.com/influxdata/influxdb/pkg/slices > github.com/influxdata/influxdb/services/admin > github.com/influxdata/influxdb/services/admin/statik > github.com/influxdata/influxdb/services/collectd > github.com/influxdata/influxdb/services/collectd/test_client > github.com/influxdata/influxdb/services/continuous_querier > github.com/influxdata/influxdb/services/graphite > github.com/influxdata/influxdb/services/httpd > github.com/influxdata/influxdb/services/meta > github.com/influxdata/influxdb/services/meta/internal > github.com/influxdata/influxdb/services/opentsdb > github.com/influxdata/influxdb/services/precreator > github.com/influxdata/influxdb/services/retention > github.com/influxdata/influxdb/services/snapshotter > github.com/influxdata/influxdb/services/subscriber > github.com/influxdata/influxdb/services/udp > github.com/influxdata/influxdb/stress > github.com/influxdata/influxdb/stress/stress_test_server > github.com/influxdata/influxdb/stress/v2 > github.com/influxdata/influxdb/stress/v2/statement > github.com/influxdata/influxdb/stress/v2/stress_client > github.com/influxdata/influxdb/stress/v2/stressql > github.com/influxdata/influxdb/stress/v2/stressql/statement > github.com/influxdata/influxdb/tcp > github.com/influxdata/influxdb/tests/urlgen > github.com/influxdata/influxdb/toml github.com/influxdata/influxdb/tsdb > github.com/influxdata/influxdb/tsdb/engine > github.com/influxdata/influxdb/tsdb/engine/tsm1 > github.com/influxdata/influxdb/tsdb/internal > github.com/influxdata/influxdb/uuid returned exit code 1 > debian/rules:66: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aw
Processed: found 859472 in 0.8.4-3
Processing commands for cont...@bugs.debian.org: > found 859472 0.8.4-3 Bug #859472 [src:khal] khal FTBFS: tests/event_test.py:307: AssertionError Marked as found in versions khal/0.8.4-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 859472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860607: gcc-mingw-w64: FTBFS: make[3]: *** No rule to make target 'gcov-dump.texi', needed by 'gcov-dump.pod'
Source: gcc-mingw-w64 Version: 19.2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory > '/<>/build/i686-w64-mingw32-posix/gcc' > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > /bin/bash ../../../src/gcc/../mkinstalldirs po > mkdir -p -- po > /bin/bash ../../../src/gcc/../mkinstalldirs po > mkdir -p -- po > /bin/bash ../../../src/gcc/../mkinstalldirs po > mkdir -p -- po > mkdir -p -- po > /bin/bash ../../../src/gcc/../mkinstalldirs po > mkdir -p -- po > /usr/bin/msgfmt --statistics -o po/be.gmo ../../../src/gcc/po/be.po > mkdir -p -- po > mkdir -p -- po > mkdir -p -- po > /usr/bin/msgfmt --statistics -o po/da.gmo ../../../src/gcc/po/da.po > /usr/bin/msgfmt --statistics -o po/de.gmo ../../../src/gcc/po/de.po > /usr/bin/msgfmt --statistics -o po/el.gmo ../../../src/gcc/po/el.po > /usr/bin/msgfmt --statistics -o po/fi.gmo ../../../src/gcc/po/fi.po > /usr/bin/msgfmt --statistics -o po/fr.gmo ../../../src/gcc/po/fr.po > /usr/bin/msgfmt --statistics -o po/hr.gmo ../../../src/gcc/po/hr.po > /usr/bin/msgfmt --statistics -o po/id.gmo ../../../src/gcc/po/id.po > /usr/bin/msgfmt --statistics -o po/ja.gmo ../../../src/gcc/po/ja.po > /usr/bin/msgfmt --statistics -o po/nl.gmo ../../../src/gcc/po/nl.po > /usr/bin/msgfmt --statistics -o po/ru.gmo ../../../src/gcc/po/ru.po > /usr/bin/msgfmt --statistics -o po/sr.gmo ../../../src/gcc/po/sr.po > /usr/bin/msgfmt --statistics -o po/sv.gmo ../../../src/gcc/po/sv.po > /usr/bin/msgfmt --statistics -o po/tr.gmo ../../../src/gcc/po/tr.po > /usr/bin/msgfmt --statistics -o po/uk.gmo ../../../src/gcc/po/uk.po > /usr/bin/msgfmt --statistics -o po/vi.gmo ../../../src/gcc/po/vi.po > /usr/bin/msgfmt --statistics -o po/zh_CN.gmo ../../../src/gcc/po/zh_CN.po > /bin/bash ../../../src/gcc/../mkinstalldirs po > TARGET_CPU_DEFAULT="" \ > HEADERS="auto-host.h ansidecl.h" DEFINES="" \ > /bin/bash ../../../src/gcc/mkconfig.sh config.h > TARGET_CPU_DEFAULT="" \ > HEADERS="options.h insn-constants.h config/vxworks-dummy.h config/i386/i386.h > config/i386/unix.h config/i386/bsd.h config/i386/gas.h config/dbxcoff.h > config/i386/cygming.h config/i386/mingw-pthread.h config/i386/mingw32.h > config/i386/mingw-w64.h config/i386/mingw-stdint.h config/initfini-array.h > defaults.h" DEFINES="LIBC_GLIBC=1 LIBC_UCLIBC=2 LIBC_BIONIC=3 LIBC_MUSL=4" \ > /bin/bash ../../../src/gcc/mkconfig.sh tm.h > TARGET_CPU_DEFAULT="" \ > HEADERS="config/i386/i386-protos.h tm-preds.h" DEFINES="" \ > /bin/bash ../../../src/gcc/mkconfig.sh tm_p.h > configure: creating cache ./config.cache > TARGET_CPU_DEFAULT="" \ > HEADERS="auto-host.h ansidecl.h" DEFINES="" \ > /bin/bash ../../../src/gcc/mkconfig.sh bconfig.h > /usr/bin/msgfmt --statistics -o po/zh_TW.gmo ../../../src/gcc/po/zh_TW.po > g++-6 -c -g -O2 -fdebug-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wall > -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti > -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings > -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic > -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H > -DGENERATOR_FILE -fno-PIE -I. -Ibuild -I../../../src/gcc > -I../../../src/gcc/build -I../../../src/gcc/../include > -I../../../src/gcc/../libcpp/include -Wdate-time -D_FORTIFY_SOURCE=2 \ > -DBASEVER="\"6.3.0\"" -DDATESTAMP="\" 20170406\"" \ > -DREVISION="\"\"" \ > -DDEVPHASE="\"\"" -DPKGVERSION="\"(GCC) \"" \ > -DBUGURL="\"<http://gcc.gnu.org/bugs.html>\"" -o build/version.o > ../../../src/gcc/version.c > gawk -f ../../../src/gcc/opt-gather.awk > ../../../src/gcc/ada/gc
Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt
Source: golang Version: 2:1.6.1-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > set -ex; \ > cd src; \ > export PATH="/<>/bin:$PATH"; \ > eval "$(go tool dist env)"; \ > bash run.bash -k -no-rebuild; > + cd src > + export > PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > + go tool dist env > + eval CC="gcc" > CC_FOR_TARGET="gcc" > GOROOT="/<>" > GOBIN="/<>/bin" > GOARCH="amd64" > GOOS="linux" > GOHOSTARCH="amd64" > GOHOSTOS="linux" > GOTOOLDIR="/<>/pkg/tool/linux_amd64" > + CC=gcc > + CC_FOR_TARGET=gcc > + GOROOT=/<> > + GOBIN=/<>/bin > + GOARCH=amd64 > + GOOS=linux > + GOHOSTARCH=amd64 > + GOHOSTOS=linux > + GOTOOLDIR=/<>/pkg/tool/linux_amd64 > + bash run.bash -k -no-rebuild > > # Testing packages. > okarchive/tar 0.019s > okarchive/zip 0.215s > okbufio 0.193s > okbytes 0.204s > okcompress/bzip2 0.247s > okcompress/flate 0.831s > okcompress/gzip 0.100s > okcompress/lzw0.039s > okcompress/zlib 0.168s > okcontainer/heap 0.009s > okcontainer/list 0.038s > okcontainer/ring 0.017s > okcrypto/aes 0.083s > okcrypto/cipher 0.015s > okcrypto/des 0.085s > okcrypto/dsa 0.055s > okcrypto/ecdsa0.072s > okcrypto/elliptic 0.125s > okcrypto/hmac 0.024s > okcrypto/md5 0.047s > okcrypto/rand 0.050s > okcrypto/rc4 0.213s > okcrypto/rsa 0.146s > okcrypto/sha1 0.049s > okcrypto/sha256 0.036s > okcrypto/sha512 0.019s > okcrypto/subtle 0.008s > okcrypto/tls 2.594s > okcrypto/x509 3.088s > okdatabase/sql0.136s > okdatabase/sql/driver 0.066s > okdebug/dwarf 0.039s > okdebug/elf 0.117s > okdebug/gosym 0.520s > okdebug/macho 0.032s > okdebug/pe0.034s > okdebug/plan9obj 0.017s > okencoding/ascii850.088s > okencoding/asn1 0.021s > okencoding/base32 0.020s > okencoding/base64 0.035s > okencoding/binary 0.043s > okencoding/csv0.037s > okencoding/gob0.055s > okencoding/hex0.048s > okencoding/json 0.412s > okencoding/pem0.046s > okencoding/xml0.024s > okerrors 0.021s > okexpvar 0.017s > okflag0.026s > okfmt 0.205s > okgo/ast 0.040s > okgo/build0.205s > okgo/constant 0.023s > okgo/doc 0.125s > okgo/format 0.041s > okgo/internal/gccgoimporter 0.013s > okgo/internal/gcimporter 0.314s > okgo/parser 0.086s > okgo/printer 0.716s > okgo/scanner 0.049s > okgo/token0.044s > okgo/types1.656s > okhash/adler320.032s > okhash/crc32 0.039s > okhash/crc64 0.045s > okhash/fnv0.038s > okhtml0.019s > okhtml/template 0.078s > okimage 0.226s > okimage/color 0.110s > okimage/draw 0.117s > okimage/gif 0.160s > okimage/jpeg 0.341s > okimage/png 0.103s > okindex/suffixarray 0.044s > okinternal/golang.org/x/net/http2/hpack 0.029s > okinternal/singleflight 0.062s > okinternal/trace 0.069s > okio 0.048s > okio/ioutil 0.014s > oklog 0.020s > oklog/syslog 2.055s > okmath0.017s > okmath/big1.017s > okmath/cmplx 0.009s > okmath/rand 0.189s > okmime0.087s > okmime/multipart 1.560s > okmime/quotedprintable0.759s > oknet 1.464s > oknet/http10.894s > oknet/http/cgi0.616s > oknet/http/cookiejar 0.012s > oknet/http/fcgi 0.009s > oknet/http/httptest 0.026s > oknet/http/httputil 0.218s > oknet/http/internal 0.066s > oknet/internal/socktest 0.007s > oknet/mail0.021s > oknet/rpc 0.182s > oknet/rpc/jsonrpc 0.109s > oknet/smtp0.047s > oknet/textproto 0.021s > oknet/url 0.124s > okos 0.361s > okos/exec 0.947s >
Bug#860606: golang-1.6: FTBFS: Go version is "go1.6.3", ignoring -next /<>/api/next.txt
Source: golang-1.6 Version: 1.6.3-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > set -ex; \ > cd src; \ > export PATH="/<>/bin:$PATH"; \ > eval "$(go tool dist env)"; \ > bash run.bash -k -no-rebuild; > + cd src > + export > PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > + go tool dist env > + eval CC="gcc" > CC_FOR_TARGET="gcc" > GOROOT="/<>" > GOBIN="/<>/bin" > GOARCH="amd64" > GOOS="linux" > GOHOSTARCH="amd64" > GOHOSTOS="linux" > GOTOOLDIR="/<>/pkg/tool/linux_amd64" > + CC=gcc > + CC_FOR_TARGET=gcc > + GOROOT=/<> > + GOBIN=/<>/bin > + GOARCH=amd64 > + GOOS=linux > + GOHOSTARCH=amd64 > + GOHOSTOS=linux > + GOTOOLDIR=/<>/pkg/tool/linux_amd64 > + bash run.bash -k -no-rebuild > > # Testing packages. > okarchive/tar 0.121s > okarchive/zip 0.207s > okbufio 0.168s > okbytes 0.254s > okcompress/bzip2 0.209s > okcompress/flate 0.832s > okcompress/gzip 0.125s > okcompress/lzw0.008s > okcompress/zlib 0.142s > okcontainer/heap 0.015s > okcontainer/list 0.037s > okcontainer/ring 0.029s > okcrypto/aes 0.066s > okcrypto/cipher 0.032s > okcrypto/des 0.025s > okcrypto/dsa 0.066s > okcrypto/ecdsa0.125s > okcrypto/elliptic 0.067s > okcrypto/hmac 0.019s > okcrypto/md5 0.021s > okcrypto/rand 0.070s > okcrypto/rc4 0.154s > okcrypto/rsa 0.156s > okcrypto/sha1 0.029s > okcrypto/sha256 0.015s > okcrypto/sha512 0.030s > okcrypto/subtle 0.031s > okcrypto/tls 2.701s > okcrypto/x509 2.735s > okdatabase/sql0.201s > okdatabase/sql/driver 0.025s > okdebug/dwarf 0.039s > okdebug/elf 0.060s > okdebug/gosym 0.476s > okdebug/macho 0.035s > okdebug/pe0.078s > okdebug/plan9obj 0.061s > okencoding/ascii850.026s > okencoding/asn1 0.010s > okencoding/base32 0.018s > okencoding/base64 0.030s > okencoding/binary 0.018s > okencoding/csv0.037s > okencoding/gob0.107s > okencoding/hex0.062s > okencoding/json 0.350s > okencoding/pem0.064s > okencoding/xml0.016s > okerrors 0.036s > okexpvar 0.112s > okflag0.018s > okfmt 0.270s > okgo/ast 0.034s > okgo/build0.111s > okgo/constant 0.020s > okgo/doc 0.124s > okgo/format 0.077s > okgo/internal/gccgoimporter 0.023s > okgo/internal/gcimporter 0.369s > okgo/parser 0.079s > okgo/printer 0.624s > okgo/scanner 0.110s > okgo/token0.080s > okgo/types1.885s > okhash/adler320.053s > okhash/crc32 0.013s > okhash/crc64 0.009s > okhash/fnv0.021s > okhtml0.072s > okhtml/template 0.095s > okimage 0.326s > okimage/color 0.306s > okimage/draw 0.143s > okimage/gif 0.183s > okimage/jpeg 0.349s > okimage/png 0.084s > okindex/suffixarray 0.092s > okinternal/golang.org/x/net/http2/hpack 0.015s > okinternal/singleflight 0.122s > okinternal/trace 0.060s > okio 0.115s > okio/ioutil 0.082s > oklog 0.064s > oklog/syslog 2.079s > okmath0.031s > okmath/big0.949s > okmath/cmplx 0.039s > okmath/rand 0.126s > okmime0.019s > okmime/multipart 1.139s > okmime/quotedprintable0.639s > oknet 1.470s > oknet/http10.713s > oknet/http/cgi1.495s > oknet/http/cookiejar 0.034s > oknet/http/fcgi 0.033s > oknet/http/httptest 0.045s > oknet/http/httputil 0.200s > oknet/http/internal 0.077s > oknet/internal/socktest 0.088s > oknet/mail0.022s > oknet/rpc 0.118s > oknet/rpc/jsonrpc 0.108s > oknet/smtp0.052s > oknet/textproto 0.008s > oknet/url 0.089s > okos 0.737s > okos/exec 0.899s >
Bug#860605: openbios: FTBFS: make[4]: *** No rule to make target 'gcov-dump.texi', needed by 'doc/gcc.info'. Stop.
Source: openbios Version: 1.1.git20161120-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory > '/<>/cross-toolchain/gcc-powerpc-elf/gcc' > configure: creating cache ./config.cache > checking build system type... x86_64-pc-linux-gnu > checking host system type... TARGET_CPU_DEFAULT="" \ > HEADERS="auto-host.h ansidecl.h" DEFINES="" \ > /bin/bash /<>/cross-toolchain/gcc-source/gcc/mkconfig.sh config.h > TARGET_CPU_DEFAULT="" \ > HEADERS="options.h insn-constants.h config/rs6000/rs6000.h config/dbxelf.h > config/elfos.h config/usegas.h config/freebsd-spec.h config/newlib-stdint.h > config/rs6000/sysv4.h config/rs6000/option-defaults.h config/initfini-array.h > defaults.h" DEFINES="LIBC_GLIBC=1 LIBC_UCLIBC=2 LIBC_BIONIC=3 LIBC_MUSL=4" \ > /bin/bash /<>/cross-toolchain/gcc-source/gcc/mkconfig.sh tm.h > TARGET_CPU_DEFAULT="" \ > HEADERS="config/rs6000/rs6000-protos.h tm-preds.h" DEFINES="" \ > /bin/bash /<>/cross-toolchain/gcc-source/gcc/mkconfig.sh tm_p.h > TARGET_CPU_DEFAULT="" \ > HEADERS="auto-host.h ansidecl.h" DEFINES="" \ > /bin/bash /<>/cross-toolchain/gcc-source/gcc/mkconfig.sh > bconfig.h > x86_64-pc-linux-gnu > checking target system type... x86_64-linux-gnu-g++ -c -g -O2 -DIN_GCC > -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti > -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings > -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic > -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H > -DGENERATOR_FILE -fno-PIE -I. -Ibuild > -I/<>/cross-toolchain/gcc-source/gcc > -I/<>/cross-toolchain/gcc-source/gcc/build > -I/<>/cross-toolchain/gcc-source/gcc/../include > -I/<>/cross-toolchain/gcc-source/gcc/../libcpp/include > -Wdate-time -D_FORTIFY_SOURCE=2 \ > -DBASEVER="\"6.3.0\"" -DDATESTAMP="\"\"" \ > -DREVISION="\"\"" \ > -DDEVPHASE="\"\"" -DPKGVERSION="\"(GCC) \"" \ > -DBUGURL="\"<http://gcc.gnu.org/bugs.html>\"" -o build/version.o > /<>/cross-toolchain/gcc-source/gcc/version.c > gawk -f /<>/cross-toolchain/gcc-source/gcc/opt-gather.awk > /<>/cross-toolchain/gcc-source/gcc/ada/gcc-interface/lang.opt > /<>/cross-toolchain/gcc-source/gcc/fortran/lang.opt > /<>/cross-toolchain/gcc-source/gcc/go/lang.opt > /<>/cross-toolchain/gcc-source/gcc/java/lang.opt > /<>/cross-toolchain/gcc-source/gcc/lto/lang.opt > /<>/cross-toolchain/gcc-source/gcc/c-family/c.opt > /<>/cross-toolchain/gcc-source/gcc/common.opt > /<>/cross-toolchain/gcc-source/gcc/config/g.opt > /<>/cross-toolchain/gcc-source/gcc/config/fused-madd.opt > /<>/cross-toolchain/gcc-source/gcc/config/rs6000/rs6000-tables.opt > /<>/cross-toolchain/gcc-source/gcc/config/rs6000/rs6000.opt > /<>/cross-toolchain/gcc-source/gcc/config/rs6000/sysv4.opt > > tmp-optionlist > powerpc-unknown-elf > checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc > checking for C compiler default output file name... /bin/bash > /<>/cross-toolchain/gcc-source/gcc/../move-if-change tmp-gi.list > gtyp-input.list > echo "#define BUILDING_GCC_MAJOR `echo 6.3.0 | sed -e > 's/^\([0-9]*\).*$/\1/'`" > bversion.h > if test no = yes \ >|| test -n ""; then \ > /bin/bash /<>/cross-toolchain/gcc-source/gcc/genmultilib \ > "msoft-float mlittle/mbig fleading-underscore" \ > "nof le be und" \ > " msoft-float=mcpu?e300c2 msoft-float=mcpu?401 msoft-float=mcpu?403 > msoft-float=mcpu?405 msoft-float=mcpu?440 msoft-float=mcpu?464 > msoft-float=mcpu?476 msoft-float=mcpu?ec603e msoft-float=mcpu?801 > msoft-float=mcpu?821 msoft-float=mcpu?823 msoft-float=mcpu?860 > mlittle=mlittle-endian mbig=mbig-endian" \ > "" \ > "mrelocatable-lib mno-eabi mstrict-align" \ > "" \ > "" \ > "" \ > "" \ > "" \ > "no" \ > > tmp-mlib.h; \ > else \ > /bin/bash /<>/cross-toolchain/gcc-source/gcc/genmultilib '' '' > '' '' '' '&
Bug#860601: altos: FTBFS: ld: final link failed: Bad value
Source: altos Version: 1.6.8-4 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/gcc/arm-none-eabi/5.4.1/../../../arm-none-eabi/bin/ld: > telegps-v0.3-1.6.8.elf: Not enough room for program headers, try linking with > -N > /usr/lib/gcc/arm-none-eabi/5.4.1/../../../arm-none-eabi/bin/ld: final link > failed: Bad value > collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/2017/04/18/altos_1.6.8-4_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Processed: found 858250 in 0.1.1+dfsg1-2
Processing commands for cont...@bugs.debian.org: > found 858250 0.1.1+dfsg1-2 Bug #858250 [runc] Fails to build, build-depends not strict enough Marked as found in versions runc/0.1.1+dfsg1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 858250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860602: ruby-net-ldap: FTBFS: ERROR: Test "ruby2.3" failed.
Source: ruby-net-ldap
Version: 0.12.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418 qa-ftbfs
Justification: FTBFS in stretch on amd64
Hi,
During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-test-files.yaml
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-net-ldap/usr/lib/ruby/vendor_ruby:.
> GEM_PATH=debian/ruby-net-ldap/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
> ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> Loaded suite -e
> Started
> ..Deprecation warning:
> Net::LDAP::ConnectionRefused will be deprecated. Use Errno::ECONNREFUSED
> instead.
> .Deprecation warning: Net::LDAP::ConnectionRefused will be deprecated. Use
> Errno::ECONNREFUSED instead.
> Deprecation warning: Net::LDAP::ConnectionRefused will be deprecated. Use
> Errno::ECONNREFUSED instead.
> Deprecation warning: Net::LDAP::ConnectionRefused will be deprecated. Use
> Errno::ECONNREFUSED instead.
> Deprecation warning: Net::LDAP::ConnectionRefused will be deprecated. Use
> Errno::ECONNREFUSED instead.
> F
> ===
> Failure: test_unresponsive_host(TestLDAPConnection)
> /<>/test/test_ldap_connection.rb:64:in `test_unresponsive_host'
> 61: end
> 62:
> 63: def test_unresponsive_host
> => 64: assert_raise Net::LDAP::Error do
> 65: Net::LDAP::Connection.new(:host => 'test.mocked.com', :port =>
> 636)
> 66: end
> 67: end
>
> expected but was
> "test.mocked.com" port 636>)>Deprecation warning:
> Net::LDAP::ConnectionRefused will be deprecated. Use Errno::ECONNREFUSED
> instead.
>
>
> diff:
> ? Net::LDAP::ConnectionRefusedError( "test.mocked.com" port 636>)
> ===
> .
>
> Finished in 0.238979812 seconds.
> --
> 89 tests, 265 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0
> notifications
> 98.8764% passed
> --
> 372.42 tests/s, 1108.88 assertions/s
> ERROR: Test "ruby2.3" failed.
The full build log is available from:
http://aws-logs.debian.net/2017/04/18/ruby-net-ldap_0.12.1-1_testing.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Bug#860604: python-escript: FTBFS: escriptcore/src/BinaryDataReadyOps.cpp:314:40: error: unused variable 'valcount' [-Werror=unused-variable]
Source: python-escript Version: 5.0-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > g++ -o debian/tmp2/posix/paso/src/Options.os -c -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fopenmp -O3 -std=c++11 -pedantic -Wall -fPIC > -Wno-unknown-pragmas -Wno-sign-compare -Wno-system-headers -Wno-long-long > -Wno-strict-aliasing -finline-functions -isystem /usr/include/python2.7 > -isystem /usr/include/boost -Werror -fPIC -DSVN_VERSION=6403 > -DHAVE_GETHOSTNAME -DHAVE_BYTESWAP_H -DESYS_HAVE_NUMPY_H -DESYS_HAVE_NETCDF > -DESYS_HAVE_PASO -DESYS_HAVE_DUDLEY -DESYS_HAVE_FINLEY -DESYS_HAVE_RIPLEY > -DESYS_HAVE_SPECKLEY -DESYS_HAVE_WEIPA -Idebian/stage2/include -I/usr/include > paso/src/Options.cpp > escriptcore/src/BinaryDataReadyOps.cpp: In instantiation of 'void > escript::binaryOpDataReadyHelperEET(escript::DataExpanded&, const > escript::DataExpanded&, const escript::DataTagged&, escript::ES_optype) [with > ResSCALAR = std::complex; LSCALAR = std::complex; RSCALAR = > std::complex]': > escriptcore/src/BinaryDataReadyOps.cpp:344:118: required from here > escriptcore/src/BinaryDataReadyOps.cpp:314:40: error: unused variable > 'valcount' [-Werror=unused-variable] >DataTypes::RealVectorType::size_type > valcount=res.getNumDPPSample()*DataTypes::noValues(res.getShape()); > ^~~~ > escriptcore/src/BinaryDataReadyOps.cpp: In instantiation of 'void > escript::binaryOpDataReadyHelperEET(escript::DataExpanded&, const > escript::DataExpanded&, const escript::DataTagged&, escript::ES_optype) [with > ResSCALAR = std::complex; LSCALAR = std::complex; RSCALAR = > double]': > escriptcore/src/BinaryDataReadyOps.cpp:348:118: required from here > escriptcore/src/BinaryDataReadyOps.cpp:314:40: error: unused variable > 'valcount' [-Werror=unused-variable] > escriptcore/src/BinaryDataReadyOps.cpp: In instantiation of 'void > escript::binaryOpDataReadyHelperEET(escript::DataExpanded&, const > escript::DataExpanded&, const escript::DataTagged&, escript::ES_optype) [with > ResSCALAR = std::complex; LSCALAR = double; RSCALAR = > std::complex]': > escriptcore/src/BinaryDataReadyOps.cpp:355:118: required from here > escriptcore/src/BinaryDataReadyOps.cpp:314:40: error: unused variable > 'valcount' [-Werror=unused-variable] > escriptcore/src/BinaryDataReadyOps.cpp: In instantiation of 'void > escript::binaryOpDataReadyHelperEET(escript::DataExpanded&, const > escript::DataExpanded&, const escript::DataTagged&, escript::ES_optype) [with > ResSCALAR = double; LSCALAR = double; RSCALAR = double]': > escriptcore/src/BinaryDataReadyOps.cpp:359:118: required from here > escriptcore/src/BinaryDataReadyOps.cpp:314:40: error: unused variable > 'valcount' [-Werror=unused-variable] > escriptcore/src/BinaryDataReadyOps.cpp: In instantiation of 'void > escript::binaryOpDataReadyHelperETE(escript::DataExpanded&, const > escript::DataTagged&, const escript::DataExpanded&, escript::ES_optype) [with > ResSCALAR = std::complex; LSCALAR = std::complex; RSCALAR = > std::complex]': > escriptcore/src/BinaryDataReadyOps.cpp:402:118: required from here > escriptcore/src/BinaryDataReadyOps.cpp:372:40: error: unused variable > 'valcount' [-Werror=unused-variable] >DataTypes::RealVectorType::size_type > valcount=res.getNumDPPSample()*DataTypes::noValues(res.getShape()); > ^~~~ > escriptcore/src/BinaryDataReadyOps.cpp: In instantiation of 'void > escript::binaryOpDataReadyHelperETE(escript::DataExpanded&, const > escript::DataTagged&, const escript::DataExpanded&, escript::ES_optype) [with > ResSCALAR = std::complex; LSCALAR = std::complex; RSCALAR = > double]': > escriptcore/src/BinaryDataReadyOps.cpp:406:118: required from here > escriptcore/src/BinaryDataReadyOps.cpp:372:40: error: unused variable > 'valcount' [-Werror=unused-variable] > escriptcore/src/BinaryDataReadyOps.cpp: In instantiation of 'void > escript::binaryOpDataReadyHelperETE(escript::DataExpanded&, const > escript::DataTagged&, const escript::DataExpanded&, escript::ES_optype) [with > ResSCALAR = std::complex; LSCALAR = double; RSCALAR = > std::complex]': > escriptcore/src/BinaryDataReadyOps.cpp:413:118: required from here >
Bug#860603: debian-design: FTBFS: unsatisfiable build-dependency: boxer-data (>= 10.5.18) but 10.5.15 is to be installed
Source: debian-design Version: 3.0.6 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, licensecheck, debhelper, dh-buildinfo, boxer (>= > 0.004~), dpkg-dev (>= 1.17.0), shellcheck, boxer-data (>= 10.5.18), > boxer-data (<< 10.6) > Filtered Build-Depends: cdbs, licensecheck, debhelper, dh-buildinfo, boxer > (>= 0.004~), dpkg-dev (>= 1.17.0), shellcheck, boxer-data (>= 10.5.18), > boxer-data (<< 10.6) > dpkg-deb: building package 'sbuild-build-depends-debian-design-dummy' in > '/<>/resolver-T8fHSe/apt_archive/sbuild-build-depends-debian-design-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-debian-design-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-T8fHSe/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-T8fHSe/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-T8fHSe/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-T8fHSe/apt_archive ./ Sources [556 B] > Get:5 copy:/<>/resolver-T8fHSe/apt_archive ./ Packages [643 B] > Fetched 2162 B in 0s (0 B/s) > Reading package lists... > W: No sandbox user '_apt' on the system, can not drop privileges > Reading package lists... > > Install debian-design 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-debian-design-dummy : Depends: boxer-data (>= 10.5.18) > but 10.5.15 is 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/2017/04/18/debian-design_3.0.6_testing.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#860547: [debian-mysql] Bug#860547: Security fixes from the April 2017 CPU
CVE List for 5.7: CVE-2017-3308 CVE-2017-3309 CVE-2017-3329 CVE-2017-3331 CVE-2017-3450 CVE-2017-3453 CVE-2017-3454 CVE-2017-3455 CVE-2017-3456 CVE-2017-3457 CVE-2017-3458 CVE-2017-3459 CVE-2017-3460 CVE-2017-3461 CVE-2017-3462 CVE-2017-3463 CVE-2017-3464 CVE-2017-3465 CVE-2017-3467 CVE-2017-3468 CVE-2017-3599 CVE-2017-3600 -- Lars
Bug#860544: [debian-mysql] Bug#860544: Security fixes from the April 2017 CPU
CVE list for 5.5: CVE-2017-3302 CVE-2017-3305 CVE-2017-3308 CVE-2017-3309 CVE-2017-3329 CVE-2017-3453 CVE-2017-3456 CVE-2017-3461 CVE-2017-3462 CVE-2017-3463 CVE-2017-3464 CVE-2017-3600 -- Lars
Bug#857794: marked as done (reportbug: crash when encountering some non-ASCII characters)
Your message dated Wed, 19 Apr 2017 01:33:55 +
with message-id
and subject line Bug#857794: fixed in reportbug 7.1.6
has caused the Debian Bug report #857794,
regarding reportbug: crash when encountering some non-ASCII characters
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.)
--
857794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.1.5
Severity: grave
Dear Maintainer,
-- Package-specific info:
** Environment settings:
EDITOR="emacs"
PAGER="less"
DEBEMAIL="dko...@debian.org"
** /home/dima/.reportbugrc:
reportbug_version "7.1.1"
mode standard
ui text
Hi. I just tried to send an unblock, and reportbug crashed. Session:
dima@scrawny:~$ sudo apt install reportbug
...
Setting up reportbug (7.1.5) ...
dima@scrawny:~$ reportbug
Please enter the name of the package in which you have found a problem, or
type 'other' to report a more
general problem. If you don't know what package the bug is in, please
contact debian-u...@lists.debian.org for
assistance.
> release.debian.org
Are you sure you want to file a bug on release.debian.org? [y|N|q|?]? y
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the
submitter).
Detected character set: us-ascii
Please change your locale if this is incorrect.
Using 'Dima Kogan ' as your from address.
Will send report to Debian (per lsb_release).
What sort of request is this? (If none of these things mean anything to
you, or you are trying to report a bug
in an existing package, please press Enter to exit reportbug.)
1 binnmu binNMU requests
2 britney testing migration script bugs
3 jessie-pu jessie proposed updates requests
4 other None of the other options
5 rm Stable/Testing removal requests
6 transition transition tracking
7 unblock unblock requests
8 wheezy-pu wheezy proposed updates requests
Choose the request type: 7
Please enter the name of the package: geda-gaf
Checking status database...
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2234, in
main()
File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 1698, in user_interface
self.options.http_proxy)
File "/usr/bin/reportbug", line 540, in special_prompts
return pkgprompts(package, bts, ui, fromaddr, timeout, online,
http_proxy)
File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 450, in
handle_debian_release
info = utils.get_source_package(package)
File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 540, in
get_source_package
data = subprocess.getoutput('apt-cache showsrc ' + pipes.quote(package))
File "/usr/lib/python3.5/subprocess.py", line 514, in getoutput
return getstatusoutput(cmd)[1]
File "/usr/lib/python3.5/subprocess.py", line 495, in getstatusoutput
data = check_output(cmd, shell=True, universal_newlines=True,
stderr=STDOUT)
File "/usr/lib/python3.5/subprocess.py", line 316, in check_output
**kwargs).stdout
File "/usr/lib/python3.5/subprocess.py", line 385, in run
stdout, stderr = process.communicate(input, timeout=timeout)
File "/usr/lib/python3.5/subprocess.py", line 788, in communicate
stdout = self.stdout.read()
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd8 in position 327:
ordinal not in range(128)
Presumably there's some non-ascii something somewhere that's tripping it
up. It is 100% reproducible, and as you can see I'm using the latest
available reportbug. Thanks.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages reportbug depends on:
ii apt1.4~beta2
ii python3-reportbug 7.1.5
pn python3:any
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail
Processed: [reportbug/master] wrap every command execution in a helper function to (eventually) decode the command output, this will prevent non-UTF-8 output to crash reportbug; patch by Nis Martensen
Processing commands for cont...@bugs.debian.org: > tag 857794 pending Bug #857794 [reportbug] reportbug: crash when encountering some non-ASCII characters Added tag(s) pending. > tag 857794 pending Bug #857794 [reportbug] reportbug: crash when encountering some non-ASCII characters Ignoring request to alter tags of bug #857794 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 857794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#857794: [reportbug/master] wrap every command execution in a helper function to (eventually) decode the command output, this will prevent non-UTF-8 output to crash reportbug; patch by Nis Martense
tag 857794 pending tag 857794 pending thanks Date: Tue Apr 18 20:53:16 2017 -0400 Author: Sandro Tosi Commit ID: df3421fcd603037616d28b1d78a86374adb7acfb Commit URL: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=df3421fcd603037616d28b1d78a86374adb7acfb Patch URL: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=df3421fcd603037616d28b1d78a86374adb7acfb wrap every command execution in a helper function to (eventually) decode the command output, this will prevent non-UTF-8 output to crash reportbug; patch by Nis Martensen; Closes: #857794
Bug#857794: [Reportbug-maint] Bug#857794: reportbug: crash when encountering some non-ASCII characters
On Tue, Apr 11, 2017 at 12:16 PM, Niels Thykier wrote: > Is there an update on this bug? :) apologies for the delay, i'm preparing an upload -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Processed: Re: Bug#859262: Re: freezes Orca screen reader
Processing control commands: > reassign -1 gnome-orca Bug #859262 [synaptic] freezes Orca screen reader Bug reassigned from package 'synaptic' to 'gnome-orca'. No longer marked as found in versions synaptic/0.84.2. Ignoring request to alter fixed versions of bug #859262 to the same values previously set > affects -1 synaptic Bug #859262 [gnome-orca] freezes Orca screen reader Added indication that 859262 affects synaptic -- 859262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859262: Re: freezes Orca screen reader
Control: reassign -1 gnome-orca Control: affects -1 synaptic Tim Retout: > Hey, > > I managed to reproduce this issue by: > > 1) running orca and synaptic > 2) clicking "Reload" > 3) clicking "Mark all upgrades" > 4) clicking "Apply" and proceeding to install ~12 packages. > > Orca stopped speaking until synaptic was closed. > > This only happened when upgrading via "Mark all upgrades"; I didn't > seem to have the same problems when just installing a new package. > > I'm attaching a log with various error messages that orca printed to > the console; sorry I've not narrowed it down further yet! > > Hope that helps, > Thanks Tim, that is a very interesting log file. Reading the log file, we at least have one bug in Orca itself (a Python "NameError"). I am not entirely sure whether this bug triggers the "hung" process or the "hung" process triggers the "NameError". I am reassigning this bug to gnome-orca for now, so the maintainer of orca can have a look at it. @Orca maintainers: The Orca log shows: """ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 234, in generate result = eval(formatting, globalsDict) File "", line 1, in NameError: name 'ancestors' is not defined During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 245, in generate globalsDict[arg] = self._methodsDict[arg](obj, **args) File "/usr/lib/python3/dist-packages/orca/braille_generator.py", line 278, in _generateAncestors and not self._script.utilities.isLayoutOnly(parent): File "/usr/lib/python3/dist-packages/orca/script_utilities.py", line 1203, in isLayoutOnly elif obj.childCount == 1 and obj.name and obj.name == firstChild.name: GLib.GError: atspi_error: The process appears to be hung. (1) """ Thanks, ~Niels
Bug#859150: marked as done (installation-guide: leaves many /tmp/tmp* files behind)
Your message dated Tue, 18 Apr 2017 23:04:18 +
with message-id
and subject line Bug#859150: fixed in installation-guide 20170419
has caused the Debian Bug report #859150,
regarding installation-guide: leaves many /tmp/tmp* files behind
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.)
--
859150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: installation-guide
Severity: serious
Tags: patch
Justification: Fills up /tmp on dillon.debian.org
Hi,
Maybe to ease hands-on debugging, dblatex is called with the -d flag,
which tells it to leave temporary files behind. This ends up filling
up dillon's /tmp (in addition to being rather bad style in the first
place…).
Two possibilities:
- remove the -d flag entirely (untested);
- or set TMPDIR to a subdirectory of $tempdir, which gets automatically
removed after a build.
The attached patch implements the second solution, but comments are
welcome.
KiBi.
Index: build/buildone.sh
===
--- build/buildone.sh (revision 70645)
+++ build/buildone.sh (working copy)
@@ -232,7 +232,8 @@
echo "Info: creating .pdf file..."
-( dblatex -d -V -T db2latex -b xetex -p ./stylesheets/dblatex.xsl \
+mkdir -p $tempdir/dblatex
+(TMPDIR=$tempdir/dblatex dblatex -d -V -T db2latex -b xetex -p ./stylesheets/dblatex.xsl \
-o $tempdir/install.${language}.pdf \
$tempdir/install.${language}.profiled.xml --param=lingua=${language} )
RET=$?; [ $RET -ne 0 ] && return $RET
--- End Message ---
--- Begin Message ---
Source: installation-guide
Source-Version: 20170419
We believe that the bug you reported is fixed in the latest version of
installation-guide, 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 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Thibault (supplier of updated installation-guide
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, 19 Apr 2017 00:38:24 +0200
Source: installation-guide
Binary: installation-guide-amd64 installation-guide-arm64
installation-guide-armel installation-guide-armhf installation-guide-i386
installation-guide-mips installation-guide-mips64el installation-guide-mipsel
installation-guide-ppc64el installation-guide-s390x
Architecture: source all
Version: 20170419
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Samuel Thibault
Description:
installation-guide-amd64 - Debian installation guide for amd64
installation-guide-arm64 - Debian installation guide for arm64
installation-guide-armel - Debian installation guide for armel
installation-guide-armhf - Debian installation guide for armhf
installation-guide-i386 - Debian installation guide for i386
installation-guide-mips - Debian installation guide for mips
installation-guide-mips64el - Debian installation guide for mips64el
installation-guide-mipsel - Debian installation guide for mipsel
installation-guide-ppc64el - Debian installation guide for powerpc
installation-guide-s390x - Debian installation guide for s390x
Closes: 859150 859438
Changes:
installation-guide (20170419) unstable; urgency=medium
.
[ Samuel Thibault ]
* Re-enable Dutch translation. Thanks a lot to Frans Spiesschaert!
* Document shortcuts for expert, rescue, and automated installation with
accessibility.
* Update distrib name about the absence of graphical installer on arm64.
* Drop the note about USB not being supported on Mustang, that was fixed.
.
[ Geert Stappers ]
* Add header to preseed file. Closes: #859438
.
[ Holger Wansing ]
* Set TMPDIR variable, to get dblatex debugging files removed after pdf
build. Closes: #859150
Checksums-Sha1:
9dc0f5770dcc6deaa4ce21c732bd857dec479abd 2853 installation-guide_20170419.dsc
398de78f5d28e1429ebbd1c3c36f25c39018676b 9819125
installation-guide_20170419.tar.gz
efe219d11516b639f767024753a596945cfd397b 16602244
installation-guide-amd64_20170419_all.deb
babb51a3409d091086c7c0446e9faa5ecf76a2de 14927756
Bug#860584: libqt5charts5-dev: missing Depends: libqt5charts5 (= ${binary:Version})
Package: libqt5charts5-dev Version: 5.7.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m57.1s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libQt5Charts.so -> libQt5Charts.so.5.7.1 cheers, Andreas libqt5charts5-dev_5.7.1-1.log.gz Description: application/gzip
Processed: tagging 860576
Processing commands for cont...@bugs.debian.org: > tags 860576 + pending Bug #860576 [wdm] wdm: Missing dependency on an X server Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 860576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860464: wdm: Missing handling of plymouth (#782456)
Control: tag -1 unreproducible moreinfo Hi again, Niels Thykier wrote: > Axel Beckert: > > Niels Thykier wrote: > >> I have reviewed the wdm init.d script and I cannot see that it takes > >> plymouth into account (which leads to #782456). To the best of my > >> knowledge, #782456 have to be fixed in the DMs. Unfortunately I cannot reproduce #782456 at all, neither with wdm nor with lightdm (1.18.3-1 from testing where this should be still present), neither with plymouth-x11 installed nor without, neither with any theme provided by desktop-base or plymouth-themes. I only tested with systemd so far as the original reporter of #782456 reported it with systemd as init system. I think I've rebooted that VM (which I specifically set up for testing this) now about 50 times and haven't seen any case where the DM (be it wdm or lightdm) didn't come up properly (except for #860576 related cases, see below). But I've only tested it in a KVM-based VM with a minimal installation, no specific graphics driver, etc. (Not even all Recommends are installed.) > > [...] As I'm currently travelling, I can't promise to get this > > tested before Tuesday evening. Well, now I have nothing which I could test as I can't reproduce this issue at all -- even after having read all of https://bugs.debian.org/782456. :-/ > > If the release team prefers a soon upload, I can do an upload with > > that feature untested. > > I am okay with the wait. :) So I wonder: Shall I upload the fix suggested by Niels anyways? (Not untested, but unverified.) Niels: I'd also include a fix for #860576 (wdm: Missing dependency on an X server) in which I ran into recently and was able to verify and debug it in this minimal VM setup I intended primarly for this bug report. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE signature.asc Description: Digital signature
Processed: Re: Bug#860464: wdm: Missing handling of plymouth (#782456)
Processing control commands: > tag -1 unreproducible moreinfo Bug #860464 [wdm] wdm: Missing handling of plymouth (#782456) Added tag(s) unreproducible and moreinfo. -- 860464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858112: gcc-defaults: broken symlinks: gcc-: /usr/share/doc/cpp-/README.Bugs -> ../gcc-6/README.Bugs
Control: severity -1 important On Wed, 5 Apr 2017 21:21:06 +0200 Andreas Beckmann wrote: > Control: severity -1 serious > and resulting in packages without copyright file after upgrade > e.g. gdc-mips64-linux-gnuabi64 4:6.3.0-1 -> 4:6.3.0-2 This is tracked separately as #860117 Andreas
Processed: Re: gcc-defaults: broken symlinks: gcc-: /usr/share/doc/cpp-/README.Bugs -> ../gcc-6/README.Bugs
Processing control commands: > severity -1 important Bug #858112 [src:gcc-defaults] gcc-defaults: broken symlinks: gcc-: /usr/share/doc/cpp-/README.Bugs -> ../gcc-6/README.Bugs Severity set to 'important' from 'serious' -- 858112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: gcc-defaults: broken symlinks: gcc-: /usr/share/doc/cpp-/README.Bugs -> ../gcc-6/README.Bugs
Processing control commands:
> reopen -1
Bug #858112 {Done: Matthias Klose } [src:gcc-defaults]
gcc-defaults: broken symlinks: gcc-:
/usr/share/doc/cpp-/README.Bugs -> ../gcc-6/README.Bugs
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gcc-defaults/1.167.
> found -1 1.168
Bug #858112 [src:gcc-defaults] gcc-defaults: broken symlinks:
gcc-: /usr/share/doc/cpp-/README.Bugs ->
../gcc-6/README.Bugs
Marked as found in versions gcc-defaults/1.168.
--
858112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#858112: gcc-defaults: broken symlinks: gcc-: /usr/share/doc/cpp-/README.Bugs -> ../gcc-6/README.Bugs
Followup-For: Bug #858112 Control: reopen -1 Control: found -1 1.168 Hi, the broken README.Bugs symlink is still there ... /usr/share/doc/cpp-mips-linux-gnu/README.Bugs -> ../gcc-6-base/README.Bugs /usr/share/doc/cpp-s390x-linux-gnu/README.Bugs -> ../gcc-6-base/README.Bugs /usr/share/doc/cpp-alpha-linux-gnu/README.Bugs -> ../gcc-6-base/README.Bugs ... Andreas
Bug#860580: clang-3.8: broken symlink: /usr/bin/scan-build-py-3.8 -> ../share/clang/scan-build-py-3.8/bin/scan-build
Package: clang-3.8 Version: 1:3.8.1-20 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m39.1s ERROR: FAIL: Broken symlinks: /usr/bin/scan-build-py-3.8 -> ../share/clang/scan-build-py-3.8/bin/scan-build Looks like a change was unneccessarily backported from 3.9, since that was previously working correctly in 3.8 cheers, Andreas clang-3.8_1:3.8.1-20.log.gz Description: application/gzip
Bug#860576: wdm: Missing dependency on an X server
Package: wdm Version: 1.28-19 Severity: serious If you install wdm on a minimal Debian system, you don't get a working login manager, but error messages about not finding /usr/bin/X in the syslog. Installing xserver-xorg-core suffices to make wdm start up, but no input device (mouse, keyboard) works. Installing one of the xserver-xorg-input packages is needed, too. The sanest approach to this issue seems to be the one by sddm by adding a dependency on "xserver-xorg | xserver". (xserver-org pulls in xserver-org-core, at least one xserver-org-video and one xserver-org-input package; the xserver alternative is for flexibility when needing wdm only for a non-standard X server, e.g. a virtual X server.) So I plan to follow sddm's example and plan to add a dependency on "xserver-xorg | xserver". -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages wdm depends on: ii cdebconf [debconf-2.0] 0.227 ii debconf [debconf-2.0] 1.5.60 ii libc6 2.24-10 ii libpam-modules 1.1.8-3.5 ii libpam-runtime 1.1.8-3.5 ii libpam0g1.1.8-3.5 ii libselinux1 2.6-3+b1 ii libwings3 0.95.7-8 ii libwraster5 0.95.7-8 ii libwutil5 0.95.7-8 ii libx11-62:1.6.4-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-3 ii libxinerama12:1.1.3-1+b3 ii libxmu6 2:1.1.2-2 ii psmisc 22.21-2.1+b2 ii x11-apps7.7+6+b1 ii x11-common 1:7.7+18 ii x11-utils 7.7+3+b1 ii x11-xserver-utils 7.7+7+b1 wdm recommends no packages. Versions of packages wdm suggests: ii xfonts-base 1:1.0.4+nmu1 -- Configuration Files: /etc/X11/wdm/wdm-config [Errno 13] Permission denied: '/etc/X11/wdm/wdm-config' -- debconf information: wdm/daemon_name: /usr/bin/wdm * shared/default-x-display-manager: wdm
Bug#859262: synaptic + orca going silent
Hey, I managed to reproduce this issue by: 1) running orca and synaptic 2) clicking "Reload" 3) clicking "Mark all upgrades" 4) clicking "Apply" and proceeding to install ~12 packages. Orca stopped speaking until synaptic was closed. This only happened when upgrading via "Mark all upgrades"; I didn't seem to have the same problems when just installing a new package. I'm attaching a log with various error messages that orca printed to the console; sorry I've not narrowed it down further yet! Hope that helps, -- Tim Retout /usr/lib/python3/dist-packages/pyatspi/registry.py:155: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Atspi.event_main() Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 234, in generate result = eval(formatting, globalsDict) File "", line 1, in NameError: name 'ancestors' is not defined During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 245, in generate globalsDict[arg] = self._methodsDict[arg](obj, **args) File "/usr/lib/python3/dist-packages/orca/braille_generator.py", line 278, in _generateAncestors and not self._script.utilities.isLayoutOnly(parent): File "/usr/lib/python3/dist-packages/orca/script_utilities.py", line 1203, in isLayoutOnly elif obj.childCount == 1 and obj.name and obj.name == firstChild.name: GLib.GError: atspi_error: The process appears to be hung. (1) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 234, in generate result = eval(formatting, globalsDict) File "", line 1, in NameError: name 'ancestors' is not defined During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 245, in generate globalsDict[arg] = self._methodsDict[arg](obj, **args) File "/usr/lib/python3/dist-packages/orca/braille_generator.py", line 278, in _generateAncestors and not self._script.utilities.isLayoutOnly(parent): File "/usr/lib/python3/dist-packages/orca/script_utilities.py", line 1203, in isLayoutOnly elif obj.childCount == 1 and obj.name and obj.name == firstChild.name: GLib.GError: atspi_error: The process appears to be hung. (1) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 234, in generate result = eval(formatting, globalsDict) File "", line 1, in NameError: name 'ancestors' is not defined During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 245, in generate globalsDict[arg] = self._methodsDict[arg](obj, **args) File "/usr/lib/python3/dist-packages/orca/braille_generator.py", line 278, in _generateAncestors and not self._script.utilities.isLayoutOnly(parent): File "/usr/lib/python3/dist-packages/orca/script_utilities.py", line 1203, in isLayoutOnly elif obj.childCount == 1 and obj.name and obj.name == firstChild.name: GLib.GError: atspi_error: The process appears to be hung. (1) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 234, in generate result = eval(formatting, globalsDict) File "", line 1, in NameError: name 'ancestors' is not defined During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 245, in generate globalsDict[arg] = self._methodsDict[arg](obj, **args) File "/usr/lib/python3/dist-packages/orca/braille_generator.py", line 278, in _generateAncestors and not self._script.utilities.isLayoutOnly(parent): File "/usr/lib/python3/dist-packages/orca/script_utilities.py", line 1203, in isLayoutOnly elif obj.childCount == 1 and obj.name and obj.name == firstChild.name: GLib.GError: atspi_error: The process appears to be hung. (1) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 234, in generate result = eval(formatting, globalsDict) File "", line 1, in NameError: name 'ancestors' is not defined During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/orca/generator.py", line 245, in generate globalsDict[arg] = self._methodsDict[arg](obj, **args) File "/usr/lib/python3/dist-packages/orca/braille_generator.py", line 278, in _generateAncestors and not self._script.utilities.isLayoutOnly(parent): File "/usr/lib/python3/dist-packages/orca/script_utilities.py", line 1203, in isLayoutOnly elif obj.childCount == 1 and obj.name and obj.name == firstChild.name: GLib.GError: atspi_error: The process appears to be hung. (1) Traceback (most recent call la
Processed: Re: Bug#857992: openjdk-8-jre-headless: please add Breaks: tzdata-java
Processing control commands: > tag -1 patch pending Bug #857992 [openjdk-8-jre-headless] openjdk-8-jre-headless: please add Breaks: tzdata-java Added tag(s) pending. -- 857992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#857992: openjdk-8-jre-headless: please add Breaks: tzdata-java
Control: tag -1 patch pending
On 2017-04-14 22:11, anarcat wrote:
> I have tried to do a NMU for this and failed to build OpenJDK through
I had previously succeeded to build openjdk-8, so I just uploaded that
as a NMU to DELAYED/5. Please let me know if I should delay it longer or
cancel.
Andreas
diff -Nru openjdk-8-8u121-b13/debian/changelog
openjdk-8-8u121-b13/debian/changelog
--- openjdk-8-8u121-b13/debian/changelog2017-03-03 18:46:54.0
+0100
+++ openjdk-8-8u121-b13/debian/changelog2017-04-18 22:32:33.0
+0200
@@ -1,3 +1,11 @@
+openjdk-8 (8u121-b13-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * openjdk-8-jre-headless: Add Breaks: tzdata-java to ensure openjdk gets
+upgraded on dist-upgrades from jessie. (Closes: #857992)
+
+ -- Andreas Beckmann Tue, 18 Apr 2017 22:32:33 +0200
+
openjdk-8 (8u121-b13-4) unstable; urgency=medium
* Drop Recommends on obsolete GNOME libraries so they are not in a
diff -Nru openjdk-8-8u121-b13/debian/control openjdk-8-8u121-b13/debian/control
--- openjdk-8-8u121-b13/debian/control 2017-02-08 07:24:37.0 +0100
+++ openjdk-8-8u121-b13/debian/control 2017-04-10 01:00:58.0 +0200
@@ -55,6 +55,7 @@
java7-runtime-headless, java8-runtime-headless,
${defaultvm:Provides}, ${jvm:Provides}
Breaks: oracle-java8-installer (<< 8u77+8u77arm-1),
+ tzdata-java,
ca-certificates-java (<< 20160321~)
Description: OpenJDK Java runtime, using ${vm:Name} (headless)
Minimal Java runtime - needed for executing non GUI Java programs,
diff -Nru openjdk-8-8u121-b13/debian/control.in
openjdk-8-8u121-b13/debian/control.in
--- openjdk-8-8u121-b13/debian/control.in 2017-01-19 12:16:07.0
+0100
+++ openjdk-8-8u121-b13/debian/control.in 2017-04-10 01:00:21.0
+0200
@@ -55,6 +55,7 @@
java7-runtime-headless, java8-runtime-headless,
${defaultvm:Provides}, ${jvm:Provides}
Breaks: oracle-java8-installer (<< 8u77+8u77arm-1),
+ tzdata-java,
ca-certificates-java (<< 20160321~)
Description: OpenJDK Java runtime, using ${vm:Name} (headless)
Minimal Java runtime - needed for executing non GUI Java programs,
Bug#859926: speechd-up: fails to install
Hi all, I don't know what to make of it, but when I first start the speechd-up daemon by hand, then the init script succeeds (because it finds the daemon already running). But now it comes, I then can stop and start the daemon successfully, but only when I am quick enough. This is reproducible, sleep 4 works always, sleep 5 always fails (so far). paul@testavoira ~/ $ sudo /sbin/start-stop-daemon --start --nicelevel 0 --quiet --oknodo --chdir "/" --exec "/usr/bin/speechd-up" --oknodo --pidfile "/var/run/speechd-up.pid" -- -l1 [Tue Apr 18 21:46:42 2017] speechd: Configuration has been read from "/etc/speechd-up.conf" paul@testavoira ~ $ sudo service speechd-up start paul@testavoira ~ $ sudo service speechd-up stop ; sleep 4 ; sudo service speechd-up start paul@testavoira ~ $ sudo service speechd-up stop ; sleep 5 ; sudo service speechd-up start Job for speechd-up.service failed because the control process exited with error code. See "systemctl status speechd-up.service" and "journalctl -xe" for details. If I look at the processes that are running after a sleep 4 look, I notice that speech-dispatcher keeps the same PID, so apparently with sleep 4 it isn't killed and still alive when speechd-up wants to connect to it. With sleep 4, the speech-dispatcher is killed and speechd-up fails to connect (as seen in the speechd-up.log). The big question is why systemd can't get speech-dispatcher up before speechd-up wants to talk to it. One thing I noticed is that /etc/default/speech-dispatcher has RUN=no, so starting speech-dispatcher with the init script succeeds, but doesn't do anything. I think that that may cause the confusion of systemd as the speechd-up init script depends on the speech-dispatcher init script. Setting RUN=yes, allows systemd to start speech-dispatcher, but apparently that isn't enough, because it still fails to start speechd-up. Speech-dispatcher isn't running anymore after starting speechd-up while it was running before calling the init script, so it looks like systemd tries to restart speech-dispatcher and fails doing that properly. Paul signature.asc Description: OpenPGP digital signature
Bug#858876: libjna-jni: causes NoClassDefFoundError
Hi,
Am 18.04.2017 um 11:15 schrieb Emmanuel Bourg:
> Le 18/04/2017 à 00:07, Emmanuel Bourg a écrit :
>
>> I'll get another look.
>
> I wrote a simple test case:
>
> import com.sun.jna.platform.unix.X11;
> public class JNATest {
> public static void main(String[] args) throws Exception {
> System.setProperty("jna.boot.library.name", "jnidispatch.foo");
> System.out.println("XAllocSizeHints: " +
> X11.INSTANCE.XAllocSizeHints());
> }
> }
>
> Compiled and executed with the system JNA jar:
>
> java -cp .:/usr/share/java/jna.jar:/usr/share/java/jna-platform.jar
> JNATest
>
> And this always works, even if the jna.boot.library.name property
> contains a bogus name.
>
> Renaming libjnidispatch.system.so to libjnidispatch.so triggers
> an UnsatisfiedLinkError.
>
> I checked again the JNA code and there is no other occurrence of
> jna.boot.library.* besides the ones removed in 4.2.2-3.
>
> This issue really looks like an embedded jar. If it isn't in netbeans
> directly, it could be in one of its dependencies.
I must admit I don't know what's going wrong here. I have checked
libnb-platform18-java again but I can't find embedded code copies of
JNA. (I grepped for com.sun.jna). I have also made sure that no external
jar files are downloaded at build time. [1]
I suggest to reassign this bug to libnb-platform18-java for now. I will
update the netbeans-platform-nojnabinaries.patch accordingly which will
hopefully fix this permanently. If you or someone else find an embedded
code copy of JNA in Netbeans or libnb-platform18-java, please let me
know. Obviously this would be very disappointing after all the work that
went into the packaging.
Regards,
Markus
[1]
https://sources.debian.net/src/libnb-platform18-java/8.1%2Bdfsg1-4/debian/patches/netbeans-platform-empty-binaries-list.patch/
signature.asc
Description: OpenPGP digital signature
Bug#860341: marked as done (libmtp-common: libmtp does not work w/ recent Android phones)
Your message dated Tue, 18 Apr 2017 20:43:39 +0100 with message-id and subject line has caused the Debian Bug report #860341, regarding libmtp-common: libmtp does not work w/ recent Android phones 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.) -- 860341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmtp-common Version: 1.1.12-1 Severity: grave Justification: renders package unusable Hi, libmtp should be upgraded to version 1.1.13 as it renders many recent smartphone unable to mount. Issue is reported there : https://sourceforge.net/p/libmtp/bugs/1625/ Many Android 6+ smartphones are actually affected, and users cannot mount them at all. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1.13-1 Hi, The release team has unblocked libmtp 1.1.13-1, hence closing. Thanks. -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A--- End Message ---
Bug#860341:
Version: 1.1.13-1 Hi, The release team has unblocked libmtp 1.1.13-1, hence closing. Thanks. -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A
Bug#860317: upgrade to latest stretch version breaks
On Tue, 2017-04-18 at 18:50 +0200, Andreas Metzler wrote: > On 2017-04-17 "Brent S. Elmer Ph.D." wrote: > > On Sat, 2017-04-15 at 13:33 +0200, Andreas Metzler wrote: > > > On 2017-04-14 "Brent S. Elmer" wrote: > > [...] > > > > Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail > > > > Transport Agent... > > > > Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4. > > > > Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog > > > > /var/log/exim4/pa…oken > > > > Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file > > > > /run/exim4/exim.…tory > > > > Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never > > > > wrote its > > > > PI…ing. > > > > Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim > > > > Mail > > > > Transport…ent. > > Hello, > > you have set > QUEUERUNNER='nodaemon' > in /etc/default/exim4, haven't you? > > cu Andreas No, it is 'combined'. I don't think I have ever done anything to change it.
Processed: rdiff-backup-fs
Processing commands for cont...@bugs.debian.org: > retitle 858316 rdiff-backup-fs: segmentation fault on i386 Bug #858316 [rdiff-backup-fs] rdiff-backup-fs: segmentation fault Changed Bug title to 'rdiff-backup-fs: segmentation fault on i386' from 'rdiff-backup-fs: segmentation fault'. > kthxbye Stopping processing here. Please contact me if you need assistance. -- 858316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860011: xspim
severity 860011 serious thanks I can confirm the broken GUI. I had to run "xspim -font 6x10" to get it to launch, as per a comment at the end of this Ubuntu issue, a different issue to #670949: https://bugs.launchpad.net/ubuntu/+source/spim/+bug/824084 Marking as 'serious' because at least the CLI program still works... -- Tim Retout
Processed: xspim
Processing commands for cont...@bugs.debian.org: > severity 860011 serious Bug #860011 [spim] xspim: white screen, broken gui Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 860011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860007: marked as done (z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory)
Your message dated Tue, 18 Apr 2017 17:49:15 + with message-id and subject line Bug#860007: fixed in gtkglext 1.2.0-7 has caused the Debian Bug report #860007, regarding z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory 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.) -- 860007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: z88 Version: 13.0.0+dfsg2-4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, z88 fails to build from source in unstable/amd64: […] /usr/bin/cc -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I«BUILDDIR»/src -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20170410083852.GxeF3Wr8r6.db.z88/z88-13.0.0+dfsg2=. -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -DFR_UNIX -DFR_XINT -DFR_XDOUB -DFR_LINUX -O3 -fomit-frame-pointer -O3 -DNDEBUG -o CMakeFiles/z88d.dir/span88.c.o -c /home/lamby/temp/cdt.20170410083852.GxeF3Wr8r6.db.z88/z88-13.0.0+dfsg2/src/span88.c «BUILDDIR»/src/ri588i.c: In function 'ri588i': «BUILDDIR»/src/ri588i.c:139:1: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result [-Wunused-result] fgets(cline,256,fi5); ^~~~ «BUILDDIR»/src/ri588i.c:154:3: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result [-Wunused-result] fgets(cline,256,fi5); ^~~~ [ 56%] Building C object CMakeFiles/z88d.dir/who88d.c.o /usr/bin/cc -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I«BUILDDIR»/src -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20170410083852.GxeF3Wr8r6.db.z88/z88-13.0.0+dfsg2=. -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -DFR_UNIX -DFR_XINT -DFR_XDOUB -DFR_LINUX -O3 -fomit-frame-pointer -O3 -DNDEBUG -o CMakeFiles/z88d.dir/who88d.c.o -c /home/lamby/temp/cdt.20170410083852.GxeF3Wr8r6.db.z88/z88-13.0.0+dfsg2/src/who88d.c [ 57%] Building C object CMakeFiles/z88d.dir/wlog88d.c.o /usr/bin/cc -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I«BUILDDIR»/src -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20170410083852.GxeF3Wr8r6.db.z88/z88-13.0.0+dfsg2=. -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -DFR_UNIX -DFR_XINT -DFR_XDOUB -DFR_LINUX -O3 -fomit-frame-pointer -O3 -DNDEBUG -o CMakeFiles/z88d.dir/wlog88d.c.o -c /home/lamby/temp/cdt.20170410083852.GxeF3Wr8r6.db.z88/z88-13.0.0+dfsg2/src/wlog88d.c [ 57%] Building C object CMakeFiles/z88d.dir/wrim88d.c.o /usr/bin/cc -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I«BUILDDIR»/src -g -O2 -fdebug-prefix-map=/home/lamby/temp/cdt.20170410083852.GxeF3Wr8r6.db.z88/z88-13.0.0+dfsg2=. -fstack-protec
Bug#859560: marked as done (xen: CVE-2017-7228: x86: broken check in memory_exchange() permits PV guest breakout (XSA-212))
Your message dated Tue, 18 Apr 2017 17:34:15 + with message-id and subject line Bug#859560: fixed in xen 4.8.1-1 has caused the Debian Bug report #859560, regarding xen: CVE-2017-7228: x86: broken check in memory_exchange() permits PV guest breakout (XSA-212) 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.) -- 859560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xen Version: 4.8.1~pre.2017.01.23-1 Severity: grave Tags: security upstream Justification: user security hole Hi, the following vulnerability was published for xen. CVE-2017-7228[0]: | An issue (known as XSA-212) was discovered in Xen, with fixes available | for 4.8.x, 4.7.x, 4.6.x, 4.5.x, and 4.4.x. The earlier XSA-29 fix | introduced an insufficient check on XENMEM_exchange input, allowing the | caller to drive hypervisor memory accesses outside of the guest | provided input/output arrays. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-7228 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7228 [1] https://xenbits.xen.org/xsa/advisory-212.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: xen Source-Version: 4.8.1-1 We believe that the bug you reported is fixed in the latest version of xen, 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 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson (supplier of updated xen 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: Tue, 18 Apr 2017 18:05:00 +0100 Source: xen Binary: libxen-4.8 libxenstore3.0 libxen-dev xenstore-utils xen-utils-common xen-utils-4.8 xen-hypervisor-4.8-amd64 xen-system-amd64 xen-hypervisor-4.8-arm64 xen-system-arm64 xen-hypervisor-4.8-armhf xen-system-armhf Architecture: source Version: 4.8.1-1 Distribution: unstable Urgency: high Maintainer: Debian Xen Team Changed-By: Ian Jackson Description: libxen-4.8 - Public libs for Xen libxen-dev - Public headers and libs for Xen libxenstore3.0 - Xenstore communications library for Xen xen-hypervisor-4.8-amd64 - Xen Hypervisor on AMD64 xen-hypervisor-4.8-arm64 - Xen Hypervisor on ARM64 xen-hypervisor-4.8-armhf - Xen Hypervisor on ARMHF xen-system-amd64 - Xen System on AMD64 (meta-package) xen-system-arm64 - Xen System on ARM64 (meta-package) xen-system-armhf - Xen System on ARMHF (meta-package) xen-utils-4.8 - XEN administrative tools xen-utils-common - Xen administrative tools - common files xenstore-utils - Xenstore command line utilities for Xen Closes: 856229 859560 Changes: xen (4.8.1-1) unstable; urgency=high . * Update to upstream 4.8.1 release. Changes include numerous bugfixes, including security fixes for: XSA-212 / CVE-2017-7228 Closes:#859560 XSA-207 / no cve yet Closes:#856229 XSA-206 / no cve yet no Debian bug Checksums-Sha1: 4d5f9a55dfd26f17beb4e1c9228a13d36dca21c4 2757 xen_4.8.1-1.dsc 0733a15f1186a7190e41cdcd4d5bfaddb0a204a7 5551737 xen_4.8.1.orig.tar.gz aa7c09c63c887504deafde1b55962750c4e780bb 51960 xen_4.8.1-1.debian.tar.xz Checksums-Sha256: b08be4d996ea40e5965dd0d8eb53cb2fbdb7f408d82eab00c139a1d692963259 2757 xen_4.8.1-1.dsc 0b91b4461cb9b583325516a8bcf1c34f30abf04b667271fa2790c8d7886695bf 5551737 xen_4.8.1.orig.tar.gz 91926fef457f17ee7f33fb73c2fab5a2be923e8d7cd5c1823b5626f490eb38ca 51960 xen_4.8.1-1.debian.tar.xz Files: be3499586dccca23244585d9fa93f1a9 2757 kernel optional xen_4.8.1-1.dsc ecc695ca67e4545d57592cf6d8c8ffb0 5551737 kernel optional xen_4.8.1.orig.tar.gz 516438b4a0194458ac0282f0b6841611 51960 kernel optional xen_4.8.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAlj2SMgACgkQ4+M5I0i1 DTlLvAgAjuIzb2iJxU+4vfSJ524t6CvMfEvXA5jZDP6WyDjZ7aZG9xRSiXOZEXdQ L4sO+G84bZR41SAAt74oQaPwbXtB0SJXPwtiqrEO+Ynk7cKSoV6gN9DiaVLhj2yd cvhAMYyD84IGro2hFOfdVb
Processed: Re: z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory
Processing commands for cont...@bugs.debian.org: > tags 860007 + pending Bug #860007 [gtkglext] z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 860007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#860317: upgrade to latest stretch version breaks
Processing control commands: > retitle -1 daemon startup under systemd fails when exim is configured without > daemon process Bug #860317 [exim4] upgrade to latest stretch version breaks Changed Bug title to 'daemon startup under systemd fails when exim is configured without daemon process' from 'upgrade to latest stretch version breaks'. > severity -1 serious Bug #860317 [exim4] daemon startup under systemd fails when exim is configured without daemon process Severity set to 'serious' from 'normal' > tags -1 pending Bug #860317 [exim4] daemon startup under systemd fails when exim is configured without daemon process Added tag(s) pending. -- 860317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: #860007: z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory
Processing commands for cont...@bugs.debian.org: > reassign 860007 gtkglext Bug #860007 [src:z88] z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory Bug reassigned from package 'src:z88' to 'gtkglext'. No longer marked as found in versions z88/13.0.0+dfsg2-4. Ignoring request to alter fixed versions of bug #860007 to the same values previously set > found 860007 1.2.0-5 Bug #860007 [gtkglext] z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory There is no source info for the package 'gtkglext' at version '1.2.0-5' with architecture '' Unable to make a source version for version '1.2.0-5' Marked as found in versions 1.2.0-5. > tags 860007 + patch Bug #860007 [gtkglext] z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory Added tag(s) patch. > affects 860007 + z88 Bug #860007 [gtkglext] z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory Added indication that 860007 affects z88 > thanks Stopping processing here. Please contact me if you need assistance. -- 860007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860007: #860007: z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory
reassign 860007 gtkglext found 860007 1.2.0-5 tags 860007 + patch affects 860007 + z88 thanks Hi, This actually seems to be a regresion due to multi-arching gtkglext in the 1.2.0-5 upload. Patch attached. After applying it to gtkglext, z88 builds successfully. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/libgtkglext1-dev.install b/debian/libgtkglext1-dev.install index 1453766..b9d1fa7 100644 --- a/debian/libgtkglext1-dev.install +++ b/debian/libgtkglext1-dev.install @@ -5,7 +5,6 @@ examples/*.rgb /usr/share/doc/libgtkglext1-dev/examples examples/Makefile.am /usr/share/doc/libgtkglext1-dev/examples m4macros/gtkglext.m4 /usr/share/aclocal usr/include -usr/lib/*/gtkglext-1.0 usr/lib/*/lib*.a usr/lib/*/lib*.la usr/lib/*/lib*.so diff --git a/gdk/Makefile.am b/gdk/Makefile.am index 525bfc2..1344303 100644 --- a/gdk/Makefile.am +++ b/gdk/Makefile.am @@ -180,7 +180,7 @@ $(srcdir)/gdkglenumtypes.c: @REBUILD@ $(gdkglext_public_h_sources) Makefile # # Rule to install gdkglext-config.h header file # -configexecincludedir = $(libdir)/gtkglext-@GTKGLEXT_API_VERSION@/include +configexecincludedir = $(includedir)/gtkglext-@GTKGLEXT_API_VERSION@ #configexecinclude_DATA = gdkglext-config.h install-exec-local: gdkglext-config.h
Bug#814030: CVE-2017-6100: Security flaw fixed in version 6.2.0
On Tue, Apr 18, 2017 at 05:04:15PM +0200, Raphael Hertzog wrote: > Hello everybody, > > On Sat, 14 Jan 2017, Moritz Mühlenhoff wrote: > > > The upstream bug is now public: > > > https://sourceforge.net/p/tcpdf/bugs/1005/ > > > > Since K_TCPDF_CALLS_IN_HTML defaults to true in jessie, we should fix > > this in jessie. > > > > Could someone of the maintainers prepare an update? > > Laurent prepared an update in git a while ago: > https://anonscm.debian.org/cgit/collab-maint/tcpdf.git/log/?h=jessie > > Patch here: > https://anonscm.debian.org/cgit/collab-maint/tcpdf.git/commit/?h=jessie&id=7242bd1072bae9e4126c0003d257b8cd097dc6aa > > Moritz/Salvatore, do you want this in jessie-proposed-updates or in > jessie-security? Please fix these via the upcoming jessie point update. Thanks, Moritz
Bug#778720: bind9: hangs / crashes on mips after some time
Control: notforwarded -1
Control: tags -1 pending
[Only the old patch was forwarded]
On 17/04/17 20:00, James Cowgill wrote:
> As discussed in #839010 and after looking at this a bit more, I think
> this bug should be release-critical for stretch. Although I can get
> bind9 to start working on MIPS, it usually crashes after a few minutes
> with it more likely to crash under load.
>
> The bug is related to atomics issues in libisc on MIPS. There was a
> patch in this bug to fix the MIPS assembly bits, but while that does fix
> the hangs it isn't enough to fix the crashes. I created a test program
> which tests the rwlock from libisc and managed to get a situation where
> 2 threads were both inside the same exclusive lock which obviously
> should not happen. I expect the weak memory ordering of MIPS has
> something to do with it (which would explain why this doesn't happen on
> x86 and other arches).
Here's a patch to fix this. The problem was not enough sync instructions
around the MIPS atomic operations (in addition to needing the patch from
earlier in this bug). My patch just removes all the MIPS assembly and
uses stdatomic functions which are implemented correctly. This should be
fine for Debian - even jessie's GCC should support them.
bind9-9.10.3.dfsg.P4-12.2-nmu.debdiff is the NMU which I have uploaded
to DELAYED/2.
The NMU was generated using combinediff on the old atomics patch and
MIPS-replace-stdatomic.patch (also attached).
Thanks,
James
diff -Nru bind9-9.10.3.dfsg.P4/debian/changelog
bind9-9.10.3.dfsg.P4/debian/changelog
--- bind9-9.10.3.dfsg.P4/debian/changelog 2017-03-17 18:07:16.0
+
+++ bind9-9.10.3.dfsg.P4/debian/changelog 2017-04-18 16:42:50.0
+0100
@@ -1,3 +1,11 @@
+bind9 (1:9.10.3.dfsg.P4-12.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Replace 32_mips_atomic.diff with a version that uses C11 atomics. Fixes
+hangs and crashes on MIPS. (Closes: #778720)
+
+ -- James Cowgill Tue, 18 Apr 2017 16:42:50 +0100
+
bind9 (1:9.10.3.dfsg.P4-12.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru bind9-9.10.3.dfsg.P4/debian/patches/32_mips_atomic.diff
bind9-9.10.3.dfsg.P4/debian/patches/32_mips_atomic.diff
--- bind9-9.10.3.dfsg.P4/debian/patches/32_mips_atomic.diff 2017-02-19
22:38:45.0 +
+++ bind9-9.10.3.dfsg.P4/debian/patches/32_mips_atomic.diff 2017-04-18
16:42:50.0 +0100
@@ -1,22 +1,29 @@
-Author: Thiemo Seufer
-Date: Thu Nov 8 15:11:48 2007 -0700
-Forwarded: yes RT#41965
-
-mips:atomic.h: improve implementation of atomic ops, fix mips{el,64}
-
-The appended patch extends the configure check to cover mips64 and
-mipsel, and improves the mips atomics implementation.
-
-See http://bugs.debian.org/406409 for more detail.
-
-Signed-off-by: LaMont Jones
+Description: Replace MIPS atomics assembly with calls to C11 atomic functions
+ This fixes various hangs and crashes on MIPS.
+Author: James Cowgill
+Forwarded: no
+Bug-Debian: https://bugs.debian.org/778720
--- a/lib/isc/mips/include/isc/atomic.h
+++ b/lib/isc/mips/include/isc/atomic.h
-@@ -31,18 +31,20 @@
- isc_atomic_xadd(isc_int32_t *p, int val) {
- isc_int32_t orig;
+@@ -19,32 +19,19 @@
+ #ifndef ISC_ATOMIC_H
+ #define ISC_ATOMIC_H 1
+
++#include
++
+ #include
+ #include
+-#ifdef ISC_PLATFORM_USEGCCASM
+ /*
+ * This routine atomically increments the value stored in 'p' by 'val', and
+ * returns the previous value.
+ */
+ static inline isc_int32_t
+ isc_atomic_xadd(isc_int32_t *p, int val) {
+- isc_int32_t orig;
+-
- /* add is a cheat, since MIPS has no mov instruction */
- __asm__ volatile (
- "1:"
@@ -29,24 +36,13 @@
- : "m"(*p), "r"(val)
- : "memory", "$3"
- );
-+ __asm__ __volatile__ (
-+ " .setpush\n"
-+ " .setmips2 \n"
-+ " .setnoreorder \n"
-+ " .setnoat\n"
-+ "1: ll $1, %1 \n"
-+ " addu%0, $1, %2 \n"
-+ " sc %0, %1 \n"
-+ " beqz%0, 1b \n"
-+ " move%0, $1 \n"
-+ " .setpop \n"
-+ : "=&r" (orig), "+R" (*p)
-+ : "r" (val)
-+ : "memory");
- return (orig);
+- return (orig);
++ return atomic_fetch_add(p, val);
}
-@@ -52,16 +54,7 @@
+
+ /*
+@@ -52,16 +39,7 @@ isc_atomic_xadd(isc_int32_t *p, int val)
*/
static inline void
isc_atomic_store(isc_int32_t *p, isc_int32_t val) {
@@ -60,16 +56,16 @@
- : "m"(*p), "r"(val)
- : "memory", "$3"
- );
-+ *p = val;
++ atomic_store(p, val);
}
/*
-@@ -72,20 +65,23 @@
+@@ -71,28 +49,8 @@ isc_atomic_store(isc_int32_t *p, isc_int
+ */
static inline isc_int32_t
isc_atomic_cmpxchg(isc_int32_t *p, int cmpval, int val) {
- isc_int32_t orig;
-+ isc_int32_t
Processed: Re: Bug#778720: bind9: hangs / crashes on mips after some time
Processing control commands: > notforwarded -1 Bug #778720 [bind9] bind9: hangs / crashes on mips after some time Unset Bug forwarded-to-address > tags -1 pending Bug #778720 [bind9] bind9: hangs / crashes on mips after some time Added tag(s) pending. -- 778720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860007: z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or directory
Hi, > z88: FTBFS: gdkgl.h:22:29: fatal error: gdkglext-config.h: No such file or > directory This seems related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185307 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: Re: Many translations missing in french KDE lang packages while we're close to release
Processing commands for cont...@bugs.debian.org: > retitle 860515 Translations missing in French KDE language packages Bug #860515 [kde-l10n-fr] Many translations missing in french KDE lang packages while we're close to release Changed Bug title to 'Translations missing in French KDE language packages' from 'Many translations missing in french KDE lang packages while we're close to release'. > thanks Stopping processing here. Please contact me if you need assistance. -- 860515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860489: apache-log4j2: CVE-2017-5645: socket receiver deserialization vulnerability
Le 17/04/2017 à 21:20, Salvatore Bonaccorso a écrit : > the following vulnerability was published for apache-log4j2. > > CVE-2017-5645[0]: > Apache Log4j socket receiver deserialization vulnerability Hi Salvatore, The vulnerability has been fixed in unstable. liblog4j2-java isn't used in jessie, this CVE can be ignored there. Emmanuel Bourg
Bug#856024: armhf bootstrap + molly-guard
reassign 856024 multistrap forcemerge 591518 856024 kthxbye It appears multistrap has longstanding issues with dpkg-divert, e.g.: - https://lists.debian.org/debian-embedded/2010/04/msg00025.html - https://bugs.launchpad.net/ubuntu/+source/multistrap/+bug/646901 (in Ubuntu, but same issue) I don't think there's anything specifically wrong with how molly-guard is using dpkg-divert, so I'm merging this bug in with the relevant multistrap bug (#591518). Hope that's all right. Kind regards, On 18 April 2017 at 15:28, Tim Retout wrote: > tags 856024 - unreproducible > thanks > > On 18 April 2017 at 13:53, Jonas Smedegaard wrote: >> Possibly this (sub)issue is tied to this: >> >> 1) install both packages _without_ executing postinst >> while *not* running systemd (e.g. in a chroot) >> 2) execute postinst of each package (in varying order) >> while *not* running systemd (e.g. in a chroot) >> 3) run systemd (e.g. boot the system on real hardware) >> 4) update systemd-sysv > > Okay, please find attached a multistrap config for helping to > reproduce this on amd64. > > $ sudo multistrap -f config > $ sudo cp /var/cache/apt/archives/systemd-sysv_232-22_amd64.deb > /opt/multistrap/ > $ sudo chroot /opt/multistrap > # dpkg --configure -a # I chose "Europe/London" as timezone when > prompted, and did not make dash the default shell > # dpkg -i systemd-sysv_232-22_amd64.deb > > Produces this output: > > (Reading database ... 7170 files and directories currently installed.) > Preparing to unpack systemd-sysv_232-22_amd64.deb ... > Unpacking systemd-sysv (232-22) over (232-22) ... > dpkg: error processing archive systemd-sysv_232-22_amd64.deb (--install): > trying to overwrite '/sbin/halt', which is also in package molly-guard 0.6.4 > Errors were encountered while processing: > systemd-sysv_232-22_amd64.deb > > I think this happens because molly-guard's preinst was not run - I > also had troubles with dash's /bin/sh diversion, hence choosing "no" > in the instructions above. > > Jonas: is there a step in your install process where preinst scripts get run? > > If this is the issue, I'm now trying to work out what to do about > it... the preinst does seem to be the right place according to Policy > Appendix G. > > Kind regards, > > -- > Tim Retout -- Tim Retout
Processed: Re: armhf bootstrap + molly-guard
Processing commands for cont...@bugs.debian.org: > reassign 856024 multistrap Bug #856024 [molly-guard] molly-guard: causes failure to update systemd-sysv Bug reassigned from package 'molly-guard' to 'multistrap'. No longer marked as found in versions molly-guard/0.6.4. Ignoring request to alter fixed versions of bug #856024 to the same values previously set > forcemerge 591518 856024 Bug #591518 [multistrap] preinst not run in foreign multistrap Bug #627068 [multistrap] Issues arising from not running foreign preinst scripts Bug #696315 [multistrap] dash: postinst fails on fresh minimal system Bug #627068 [multistrap] Issues arising from not running foreign preinst scripts Added tag(s) help. Added tag(s) help. Added tag(s) help. Bug #856024 [multistrap] molly-guard: causes failure to update systemd-sysv Severity set to 'normal' from 'serious' Marked as found in versions multistrap/2.1.13. Bug #696315 [multistrap] dash: postinst fails on fresh minimal system Merged 591518 627068 696315 856024 > kthxbye Stopping processing here. Please contact me if you need assistance. -- 591518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591518 627068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627068 696315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696315 856024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 852059 is important, severity of 859418 is important, severity of 859419 is important
Processing commands for cont...@bugs.debian.org: > severity 852059 important Bug #852059 [opendnssec-signer] opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long Severity set to 'important' from 'serious' > severity 859418 important Bug #859418 [opendnssec-signer] non-functional after installation (service fails to start) Severity set to 'important' from 'serious' > severity 859419 important Bug #859419 [opendnssec-enforcer] non-functional after installation (service fails to start) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 852059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852059 859418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859418 859419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#814030: CVE-2017-6100: Security flaw fixed in version 6.2.0
Hello everybody, On Sat, 14 Jan 2017, Moritz Mühlenhoff wrote: > > The upstream bug is now public: > > https://sourceforge.net/p/tcpdf/bugs/1005/ > > Since K_TCPDF_CALLS_IN_HTML defaults to true in jessie, we should fix > this in jessie. > > Could someone of the maintainers prepare an update? Laurent prepared an update in git a while ago: https://anonscm.debian.org/cgit/collab-maint/tcpdf.git/log/?h=jessie Patch here: https://anonscm.debian.org/cgit/collab-maint/tcpdf.git/commit/?h=jessie&id=7242bd1072bae9e4126c0003d257b8cd097dc6aa Moritz/Salvatore, do you want this in jessie-proposed-updates or in jessie-security? Laurent, did you test the updated package against any reverse dependency like pypmyadmin or dolibarr? Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Processed: Re: armhf bootstrap + molly-guard
Processing commands for cont...@bugs.debian.org: > tags 856024 - unreproducible Bug #856024 [molly-guard] molly-guard: causes failure to update systemd-sysv Removed tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 856024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#856024: armhf bootstrap + molly-guard
tags 856024 - unreproducible thanks On 18 April 2017 at 13:53, Jonas Smedegaard wrote: > Possibly this (sub)issue is tied to this: > > 1) install both packages _without_ executing postinst > while *not* running systemd (e.g. in a chroot) > 2) execute postinst of each package (in varying order) > while *not* running systemd (e.g. in a chroot) > 3) run systemd (e.g. boot the system on real hardware) > 4) update systemd-sysv Okay, please find attached a multistrap config for helping to reproduce this on amd64. $ sudo multistrap -f config $ sudo cp /var/cache/apt/archives/systemd-sysv_232-22_amd64.deb /opt/multistrap/ $ sudo chroot /opt/multistrap # dpkg --configure -a # I chose "Europe/London" as timezone when prompted, and did not make dash the default shell # dpkg -i systemd-sysv_232-22_amd64.deb Produces this output: (Reading database ... 7170 files and directories currently installed.) Preparing to unpack systemd-sysv_232-22_amd64.deb ... Unpacking systemd-sysv (232-22) over (232-22) ... dpkg: error processing archive systemd-sysv_232-22_amd64.deb (--install): trying to overwrite '/sbin/halt', which is also in package molly-guard 0.6.4 Errors were encountered while processing: systemd-sysv_232-22_amd64.deb I think this happens because molly-guard's preinst was not run - I also had troubles with dash's /bin/sh diversion, hence choosing "no" in the instructions above. Jonas: is there a step in your install process where preinst scripts get run? If this is the issue, I'm now trying to work out what to do about it... the preinst does seem to be the right place according to Policy Appendix G. Kind regards, -- Tim Retout config Description: Binary data
Bug#860489: marked as done (apache-log4j2: CVE-2017-5645: socket receiver deserialization vulnerability)
Your message dated Tue, 18 Apr 2017 13:03:51 + with message-id and subject line Bug#860489: fixed in apache-log4j2 2.7-2 has caused the Debian Bug report #860489, regarding apache-log4j2: CVE-2017-5645: socket receiver deserialization vulnerability 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.) -- 860489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apache-log4j2 Version: 2.0~beta9-1 Severity: grave Tags: security upstream Forwarded: https://issues.apache.org/jira/browse/LOG4J2-1863 Hi, the following vulnerability was published for apache-log4j2. CVE-2017-5645[0]: Apache Log4j socket receiver deserialization vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. This one might warrant a DSA, but please check back with t...@security.debian.org . For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-5645 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645 [1] https://issues.apache.org/jira/browse/LOG4J2-1863 Regards, Salvatore --- End Message --- --- Begin Message --- Source: apache-log4j2 Source-Version: 2.7-2 We believe that the bug you reported is fixed in the latest version of apache-log4j2, 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 860...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated apache-log4j2 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: Tue, 18 Apr 2017 14:30:00 +0200 Source: apache-log4j2 Binary: liblog4j2-java liblog4j2-java-doc Architecture: source Version: 2.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: liblog4j2-java - Apache Log4j - Logging Framework for Java liblog4j2-java-doc - Documentation for Apache Log4j 2 Closes: 860489 Changes: apache-log4j2 (2.7-2) unstable; urgency=medium . * Team upload. * Fixed CVE-2017-5645: When using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code (Closes: #860489) Checksums-Sha1: 876caec08e0dd244c2f659a5929b77003362360e 2886 apache-log4j2_2.7-2.dsc e0d5b663d2238cc59c0d7a9e1efaea4aaa4825b9 8440 apache-log4j2_2.7-2.debian.tar.xz 9c1f873b9743e386c1829f3f62d062a943fdac2e 14653 apache-log4j2_2.7-2_source.buildinfo Checksums-Sha256: dfa96b6d21c6c4d698640d2ba5e918306da215cdabf0dbc1b3c65686379e0d26 2886 apache-log4j2_2.7-2.dsc 68fef80f76648b9835ce7990a9238d86cff99af722e2d28a5528ddced3f07c71 8440 apache-log4j2_2.7-2.debian.tar.xz 33ce7f2156f8ec4ee5c9aebf0b54296343f772cd2aad6937eb550e47351e9b60 14653 apache-log4j2_2.7-2_source.buildinfo Files: ee59e794d0c7205f735742c58a83dd76 2886 java optional apache-log4j2_2.7-2.dsc c405df976dea2058f26495918141df8b 8440 java optional apache-log4j2_2.7-2.debian.tar.xz 978daedb3c643314ebdb5030a63f5d5c 14653 java optional apache-log4j2_2.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlj2Cp8SHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsOzIP+wSzPlVMZO9SrnlPh9rlRL/p3DLYlAXB Fh0LbqaN4IFur1LyzIUGfWFLXNdHQW/CSwfGql1hUC07MohRjAdznUQe0BQzAb2W 8KYUvabxnpkRoLaFJ+4Y1nC8X/fXTqp+2285oFWwmshp5nbQFynIgB+i6MxWab4m dPuGD1bEtNqoA9XcVl3mKyHwHwNk+T7mpmTjRNyZ2HSCAu3s4fRHn/C8C8vs6k0c iQ94coHJ18fMF1O1bKP9ShQt2W+eesmUI7AnaOVb1CE+UpziIGPRYz9WxAWLpSg+ zDY2eh0FEocPHZfuJPkngWGfjS6fjNsYx/HgEWJw2kZc8GQdk257VR++0cbPRzbc rQJKizXC34E7lWu8U9jKVCG8SBOqbcITMUlgNut2a/qdAgELl4O/Nv5vTE67mF81 2uJ7FSRPShDQxlo9PRz+oJ7pRRKFJAULnYZBrAjsyqtWcrDI+/MpEhit21GX3Hs3 OiZS2wdHXyfxmzjk/AiDdkc669HHu0uWcGTVrZYY81hxBP1Jpn9cbXhCQ1CDW07b TODQE1RF81fJtauNpp2yE3wqG9TlywY4SK6255PVIZDeUM+EbuTXV3YOgL3P1Lo7 sFCs0+meoqQXyPGjfiXo15qdj9bSF0QEiRogidtqYhVDIdNZ6GimVyVa1D6r3Smp wHsiqOUV8l7u =BcgQ -END PGP SIGNATURE End Message ---
Bug#856024: armhf bootstrap + molly-guard
Quoting Tim Retout (2017-04-18 11:00:54) > On 17 April 2017 at 18:59, Jonas Smedegaard wrote: >> I don't recall, but believe I installed using plain standard >> debian-installer with the "netboot" image. But possibly I might have >> used multistrap, which means the order of installing the various >> packages may be different from (c)debootrap-based installs. >> Something that is *not* a bug in multistrap - Debian Policy mandates >> package relations but no specific install order. > > Thanks - I'll break out some real armhf hardware later. So far I've > mainly been testing by reinstalling rather than upgrading > systemd-sysv. Let me repeat: I do *not* think this issue is specific to armhf. I *do* think this (sub)issue is tied to _upgrading_ systemd-sysv. > I don't *think* multistrap install order should be an issue - I've > even tried uninstalling systemd-sysv in a chroot (so that /sbin/halt > doesn't exist), installing molly-guard, then installing systemd-sysv > again - but this seemed to be handled fine. Possibly this (sub)issue is tied to this: 1) install both packages _without_ executing postinst while *not* running systemd (e.g. in a chroot) 2) execute postinst of each package (in varying order) while *not* running systemd (e.g. in a chroot) 3) run systemd (e.g. boot the system on real hardware) 4) update systemd-sysv I believe 1) through 2) mimicks multistrap, and since various packages have invented their own probing mechanisms for whether being on real hardware or not that might be relevant for triggering this (sub)issue. > If you used multistrap, does this mean there was another package repo > involved? No. I use multistrap for each separation of unpacking and postinst execution - since on slow archs that gives a speedup by doing the former on a different more powerful host and the latter either on emulated hardware (slow) or target hardware (cumbersome esp. when creating several similar setups). > The bit I can't get my head round is why dpkg-divert would not have > reported molly-guard having any diversions in place (which seems to > match the error message "also in package molly-guard 0.6.4"). For any > recently-installed stretch system, molly-guard should definitely have > been using diversions. Right: 0.6.4 entered Stretch only 3 days prior to my bugreport, but that bit of the log message indicates no earlier version was involved. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#860233: marked as done (gnome-paint: Segmentation fault on startup)
Your message dated Tue, 18 Apr 2017 12:48:58 + with message-id and subject line Bug#860233: fixed in gnome-paint 0.4.0-5 has caused the Debian Bug report #860233, regarding gnome-paint: Segmentation fault on startup 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.) -- 860233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-paint Version: 0.4.0-4+b1 Severity: grave Justification: renders package unusable % gnome-paint Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-primary-button-warps-slider' of type `gboolean' from rc file value "((GString*) 0x560fa1f6e280)" of type `gboolean' [1]17767 segmentation fault gnome-paint -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-paint depends on: ii libatk1.0-0 2.22.0-1 ii libc62.24-9 ii libcairo21.14.8-1 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.1 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii libpango-1.0-0 1.40.4-1 ii libpangocairo-1.0-0 1.40.4-1 ii libpangoft2-1.0-01.40.4-1 ii libx11-6 2:1.6.4-3 gnome-paint recommends no packages. gnome-paint suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gnome-paint Source-Version: 0.4.0-5 We believe that the bug you reported is fixed in the latest version of gnome-paint, 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 860...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang <073p...@gmail.com> (supplier of updated gnome-paint 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: Mon, 17 Apr 2017 21:42:56 +0800 Source: gnome-paint Binary: gnome-paint Architecture: source amd64 Version: 0.4.0-5 Distribution: unstable Urgency: medium Maintainer: Aron Xu Changed-By: Boyuan Yang <073p...@gmail.com> Description: gnome-paint - simple, easy to use paint program for GNOME Closes: 727874 860233 Changes: gnome-paint (0.4.0-5) unstable; urgency=medium . * Sponsored upload. * d/control: Add myself into uploaders list. * d/control: Bump Standards Version to 3.9.8. * d/control: Use secure URI for homepage. * d/control: Add Vcs-Git and Vcs-Browser. * control,rules: Use dh-autoreconf instead of autotools-dev. (Closes: #727874) * d/patches: Add patch to enable deprecated gdk functions. (Closes: #860233) Checksums-Sha1: 26d1d2258cb7d928b80470eb5f37bf66ad96704b 1616 gnome-paint_0.4.0-5.dsc 588b08959db071fd12178b5dd4086ddca8232bc1 6516 gnome-paint_0.4.0-5.debian.tar.xz 19a19520754f43f6171bd19c3d6c2995efa4f260 220024 gnome-paint-dbgsym_0.4.0-5_amd64.deb 5db926b255c40ad253de8e0141221d1e002c2054 10109 gnome-paint_0.4.0-5_amd64.buildinfo e65ff0f77370d9c2de837386e23479785cf1ea26 85918 gnome-paint_0.4.0-5_amd64.deb Checksums-Sha256: 755eb1effb0cfc2917c8fd3ae26179ce04409d9e22e24e1c3065ee625ceb381d 1616 gnome-paint_0.4.0-5.dsc 5da8f1a6d74a9d6fbb663c99595d4fbb7ce3d50e737d71b3b5dafb65f9ca80ad 6516 gnome-paint_0.4.0-5.debian.tar.xz ec02234bb4ec6e34b6d791c607dfca0a0d4e158bf7de5b0a4f73b581b168a1d4 220024 gnome-paint-dbgsym_0.4.0-5_amd64.deb 38751654a2fe5fb15d8cedc1ee6ce2108f096ac7ee1157b6f509cab93606077a 10109 gnome-paint_0.4.0-5_amd64.buildinfo 0c02d239cd4e06830dddf8974ddb309a1a488e2b17bc18c70651953204850e33 85918 gnome-paint_0.4.0-5_amd64.deb Files: dd882fe7680a01ee24854cdd92df8a87 1616 graphics optional gnome-paint_0.4.0-5.dsc 18dffb047b76122056ec32adc381e423 6516 graphics optional gnome-paint_0.4.0-5.debian.tar.xz 6ce73ccb970658cd25c15d2fcbc74b39 220024 debug extra gnome-paint-dbgsym_0.4.0-5_amd64.de
Bug#860489: Pending fixes for bugs in the apache-log4j2 package
tag 860489 + pending thanks Some bugs in the apache-log4j2 package are closed in revision 799b96337bcf909193aa76c6090ba511c05b64f6 in branch 'master' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/apache-log4j2.git/commit/?id=799b963 Commit message: Fixed CVE-2017-5645: Remote code execution with the TCP/UDP socket server (Closes: #860489)
Processed: Pending fixes for bugs in the apache-log4j2 package
Processing commands for cont...@bugs.debian.org: > tag 860489 + pending Bug #860489 [src:apache-log4j2] apache-log4j2: CVE-2017-5645: socket receiver deserialization vulnerability Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 860489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#854130: marked as done (libbson FTBFS on mips/mipsel: test-results.json aborted)
Your message dated Tue, 18 Apr 2017 08:24:36 -0400
with message-id
and subject line
has caused the Debian Bug report #854130,
regarding libbson FTBFS on mips/mipsel: test-results.json aborted
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.)
--
854130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbson
Version: 1.5.0-1
Severity: serious
https://buildd.debian.org/status/package.php?p=libbson&suite=sid
...
{ "status": "PASS", "test_file": "/bson/utf8/from_unichar", "seed":
"3897722749", "start": 918303.161886737, "end": 918303.161907618, "elapsed":
0.20881 },
{ "status": "PASS", "test_file": "/bson/utf8/invalid", "seed":
"3495301312", "start": 918303.172066716, "end": 918303.172096569, "elapsed":
0.29853 },
{ "status": "PASS", "test_file":
"/bson/decimal128/from_string/exponent_normalization", "seed": "2524386511",
"start": 918303.160139775, "end": 918303.172289377, "elapsed": 0.012149602 },
{ "status": "PASS", "test_file": "/bson/as_json/stack_overflow", "seed":
"4062366096", "start": 918303.082477899, "end": 918303.199222704, "elapsed":
0.116744805 },
{ "status": "PASS", "test_file": "/type/decimal128/decimal128-2", "seed":
"973167199", "start": 918303.151844572, "end": 918303.202736059, "elapsed":
0.050891487 },
{ "status": "PASS", "test_file": "/type/decimal128/decimal128-3", "seed":
"3407436287", "start": 918303.160160818, "end": 918303.227553065, "elapsed":
0.067392247 },
{ "status": "PASS", "test_file": "/bson/as_json/x1000", "seed":
"3264176593", "start": 918303.082226314, "end": 918303.360835632, "elapsed":
0.278609318 },
/bin/bash: line 1: 2488 Aborted /bin/bash ./libtool
--mode=execute $VALGRIND ./$TEST_PROG --threads --no-fork -F test-results.json
Makefile:2398: recipe for target 'test' failed
make[1]: *** [test] Error 134
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
debian/rules:21: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
--- End Message ---
--- Begin Message ---
Package: libbson
Version: 1.6.1
Fixed upstream.--- End Message ---
Bug#859969: marked as done (ocaml-dtools FTBFS on ppc64el: dh_install: Cannot find (any matches for) "src/*.a")
Your message dated Tue, 18 Apr 2017 12:04:28 + with message-id and subject line Bug#859969: fixed in ocaml-dtools 0.3.1-2 has caused the Debian Bug report #859969, regarding ocaml-dtools FTBFS on ppc64el: dh_install: Cannot find (any matches for) "src/*.a" 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.) -- 859969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-dtools Version: 0.3.1-1 Severity: serious ocaml-dtools FTBFS on ppc64el (originally reported by Frederic Bonnard): ... dh_lintian -plibdtools-ocaml-dev dh_bugfiles -plibdtools-ocaml-dev dh_install -plibdtools-ocaml-dev dh_install: Compatibility levels before 9 are deprecated (level 7 in use) dh_install: Cannot find (any matches for) "src/*.a" (tried in "." and "debian/tmp") dh_install: missing files, aborting /usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 'binary-install/libdtools-ocaml-dev' failed make: *** [binary-install/libdtools-ocaml-dev] Error 255 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Complete log is attached. LOG.ocaml-dtools.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ocaml-dtools Source-Version: 0.3.1-2 We believe that the bug you reported is fixed in the latest version of ocaml-dtools, 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 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml-dtools 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: Tue, 18 Apr 2017 13:37:34 +0200 Source: ocaml-dtools Binary: libdtools-ocaml-dev Architecture: source amd64 Version: 0.3.1-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Description: libdtools-ocaml-dev - library for writing daemons in OCaml Closes: 859969 Changes: ocaml-dtools (0.3.1-2) unstable; urgency=medium . * Team upload * Fix compilation on bytecode architectures (Closes: #859969) Checksums-Sha1: e8509e9c8538f8eb375c4cd85d9e70e5f2fac5cf 2109 ocaml-dtools_0.3.1-2.dsc 8abf050a32ea811399e05f7eed186685ef2d6d94 2744 ocaml-dtools_0.3.1-2.debian.tar.xz 27f9d87f563b7db34a29309c57847b7f87afa18b 48328 libdtools-ocaml-dev_0.3.1-2_amd64.deb cb01897109cc8c9f8d29072630c4f3811634490d 5899 ocaml-dtools_0.3.1-2_amd64.buildinfo Checksums-Sha256: 59764a0160033f0286af970e9ede9357011c6c044307b246fd6f5471b669a6f4 2109 ocaml-dtools_0.3.1-2.dsc 4731c638d7887dc1a6d6a39742d29dbcb7f6d9c9b2bd08271c476f3a557fa15f 2744 ocaml-dtools_0.3.1-2.debian.tar.xz cce6ba8cb87dcda81ab694ac75bf7cc2be304166ba4ca17e929783e4c64197b4 48328 libdtools-ocaml-dev_0.3.1-2_amd64.deb 9789f35775f1bf2d3a1238123027c49a1a304f9dfd84de7539c9569ae917778b 5899 ocaml-dtools_0.3.1-2_amd64.buildinfo Files: 18685321f21b99f8a14cd15f0543b1ab 2109 ocaml optional ocaml-dtools_0.3.1-2.dsc 93933856ee31e440ee7a86a39a1b970e 2744 ocaml optional ocaml-dtools_0.3.1-2.debian.tar.xz 2e1794fac134e16362e24e3fdefdacb9 48328 ocaml optional libdtools-ocaml-dev_0.3.1-2_amd64.deb 77f9be1dfddb93a126b5b73200150b5e 5899 ocaml optional ocaml-dtools_0.3.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWOsJmcZOiX7olLgDeFPaTUmIGtMFAlj1+zwACgkQeFPaTUmI GtMzTxAAsLtKXjBuj5Ij1wCFRkZ4PWo0tfeRSDibNrHb7B2sX9mpn7uGNvuEzUFD 5njB+yrKC3AhCMEZuHJ2zuBZIXK2nhmjCkHDd88W6YAfqK5YV3QyyiaRWN93QdbI e+ix1IruFN4+7RoL0nJVHRzQh1/CEV46cBQZtjTzrrk9QfO2YbHKyIhcYWBBJtJH YA5YBLMdg6cyvO2OhYPG/4SRWxYvtzPJ/mVxv+GiPd3lmhwj7Kdo9PnDH21SZzIH nWUtBrRu7Har/pyiVh95WkWwP6LNydGCjlWf8zN2rFJAOrum261EcjafPSMRdYBk CPgHYudlJED/8UTXTZqMYHgZTGYcK5BA++6wdoYZ9QktwKRC2jKk1cjvDa/Thu46 WhAOrP+3UPb3vPsPZuilh6gbbgeF1wiGwDluOTvSugSWWDnzyP3Qv4yTmgEV8Dph PhJ+9m8XJzy79gSQd/U2hYCVy+0Tt0Ic1Jx27HEH7bilw9I9eCj5qWPmLgBVTenj MJH1zMpXBCrVTifLRxrUYGv+pZFIEsIyiT8cpeK5Lrq+VGR7qG0T0/JvhlU52ybW neGB7bD9exkmgbi9pId82c2N9lQXq36c9m+TRqulVnzq7mM3ODzJ0AhZvy/2iLO7 8c9ovxaYEDPI5E6aJYb33R3elMph3UxCG9/dUV2G+FAyg3rkmWc= =1Mcg -END PGP SIGNATURE End Message ---
Bug#860548: r10k - rugged provider does neither HTTPS, nor SSH
Package: r10k Version: 2.5.0-1 Severity: grave The rugged provider, as provided by ruby-rugged in Debian, does neither support HTTPS, nor SSH. As this is a hard dependency, I think it is safe to assume it should work. As long as rugged is in this state, I don't think a dependency with all the problems is in order. Output: | ERROR-> Failed to authenticate SSH session: Unable to extract public key from private key file: Method unimplemented in libgcrypt backend at HOME/.r10k/git/ssh---...@gitlab-bla-blub.git | ERROR-> Failed to resolve address for https: Name or service not known at HOME/.r10k/git/https---github.com-foo-bar.git Bastian -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages r10k depends on: ii ruby 1:2.3.3 ii ruby-colored 1.2-2 ii ruby-cri 2.7.0-2 ii ruby-gettext-setup0.7-1 ii ruby-log4r1.1.10-4 ii ruby-minitar 0.5.4-3.1 ii ruby-multi-json 1.11.2-3 ii ruby-puppet-forge 2.2.2-2 ii ruby-rugged 0.24.0+ds1-2 ii ruby-semantic-puppet 0.1.4-2 Versions of packages r10k recommends: ii git 1:2.11.0-2 r10k suggests no packages. -- no debconf information
Bug#859966: marked as done (ocaml-ao FTBFS on ppc64el: dh_install: Cannot find (any matches for) "src/*.cmx")
Your message dated Tue, 18 Apr 2017 11:48:50 + with message-id and subject line Bug#859966: fixed in ocaml-ao 0.2.0-2 has caused the Debian Bug report #859966, regarding ocaml-ao FTBFS on ppc64el: dh_install: Cannot find (any matches for) "src/*.cmx" 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.) -- 859966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-ao Version: 0.2.0-1 Severity: serious ocaml-ao FTBFS on ppc64el (originally reported by Frederic Bonnard): ... dh_bugfiles -plibao-ocaml-dev dh_install -plibao-ocaml-dev dh_install: Compatibility levels before 9 are deprecated (level 7 in use) dh_install: Cannot find (any matches for) "src/*.cmx" (tried in "." and "debian/tmp") dh_install: Cannot find (any matches for) "src/*.cmxa" (tried in "." and "debian/tmp") dh_install: missing files, aborting /usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 'binary-install/libao-ocaml-dev' failed make: *** [binary-install/libao-ocaml-dev] Error 255 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Complete log is attached. LOG.ocaml-ao.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ocaml-ao Source-Version: 0.2.0-2 We believe that the bug you reported is fixed in the latest version of ocaml-ao, 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 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml-ao 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: Tue, 18 Apr 2017 11:35:17 +0200 Source: ocaml-ao Binary: libao-ocaml libao-ocaml-dev Architecture: source amd64 Version: 0.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Description: libao-ocaml - OCaml bindings for libao -- runtime files libao-ocaml-dev - OCaml bindings for libao -- development files Closes: 859966 Changes: ocaml-ao (0.2.0-2) unstable; urgency=medium . * Team upload * Fix compilation on bytecode architectures (Closes: #859966) * Switch to source format 3.0 (quilt) Checksums-Sha1: c47ccdde273e14959072c0d5a14189c1fe3c71d7 2086 ocaml-ao_0.2.0-2.dsc b4378018afcc60ebde1f6fa1aa218675326883ff 2852 ocaml-ao_0.2.0-2.debian.tar.xz 8f66348eaf6a7def6cc0c9ed19d0896866480d1f 10366 libao-ocaml-dbgsym_0.2.0-2_amd64.deb 8c435fdfc8b3b374f2adfa2cd41c338edb1a90e3 21654 libao-ocaml-dev_0.2.0-2_amd64.deb 797d90890f65bbbdcef55b0d8a9364f9ec50e15d 8108 libao-ocaml_0.2.0-2_amd64.deb 8162975ba4fff620650d1c7cc7d022259d80385b 6426 ocaml-ao_0.2.0-2_amd64.buildinfo Checksums-Sha256: 2a0401cc3c6d8b3b6e6fbf395c12ec66a6ddff409e9521441fe11eb8c2734ecd 2086 ocaml-ao_0.2.0-2.dsc f09ce86d02cafb8319a8ba02e748de6ede7e1dbbaf36939beccbd50ba03056d4 2852 ocaml-ao_0.2.0-2.debian.tar.xz 97447c54508d03f92b02d08b3aefa044342a02278efdbdab8309eb8ea9e5a1ea 10366 libao-ocaml-dbgsym_0.2.0-2_amd64.deb 3f58301046ae12bbdc58ce3354bcffd94ac860670a3786d1380f5bc911aa5c2f 21654 libao-ocaml-dev_0.2.0-2_amd64.deb ee4cd49681dc000d4f63decf4bae48c577f2e5a76e9e552647ddd46d2d10e1b5 8108 libao-ocaml_0.2.0-2_amd64.deb 869e7e1659b6872d9ebdbee34e896e36e2d4d1d0bab5cc80fe06b15b1a58838f 6426 ocaml-ao_0.2.0-2_amd64.buildinfo Files: d970cd66584992f2251cd6f6fbf6e70c 2086 ocaml optional ocaml-ao_0.2.0-2.dsc ed22c041ede8208215fbe63ef1105505 2852 ocaml optional ocaml-ao_0.2.0-2.debian.tar.xz 2a129d19c6b9a8eac726019e02cdd8db 10366 debug extra libao-ocaml-dbgsym_0.2.0-2_amd64.deb a7fd0e4020122fc9b853e74204ebc91e 21654 ocaml optional libao-ocaml-dev_0.2.0-2_amd64.deb 6f5e8bcad40464c64b6378fbb8a43a9b 8108 ocaml optional libao-ocaml_0.2.0-2_amd64.deb 3e447349e05bbdc201b8749c8a18681a 6426 ocaml optional ocaml-ao_0.2.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWOsJmcZOiX7olLgDeFPaTUmIGtMFAlj1+VgACgkQeFPaTUmI GtNPDw//RPTYh8QXlGOlkggv9p8HYCfDwyL1i8esyrDPi96u8MukwLIKs5aExqmT o7C0kuHg0/b/yPlWNTlqD3+wikk3Fd88O+hHgzgXnmBYwpJC8Y2VO3wshXcuRoFL jsJO5ZJiWJyFnxoztj/ZEOErz6fOTUXoHXXlmIFnSyUAKE4uQuv2bF1102ea7ZMt
Bug#860547: Security fixes from the April 2017 CPU
Source: mysql-5.7 Version: 5.7.17-1 Severity: grave Tags: security upstream fixed-upstream The Oracle Critical Patch Update for April 2017 will be released on Tuesday, April 18. According to the pre-release announcement [1], it will contain information about CVEs fixed in MySQL 5.7.18. The CVE numbers will be available when the CPU is released. Please note that the MySQL release cycle has changed from every two months to every three months. The releases are now synchronized with the CPU announcements. Best regards, Norvald H. Ryeng [1] http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html
Bug#860544: Security fixes from the April 2017 CPU
Source: mysql-5.5 Version: 5.5.54-0+deb8u1 Severity: grave Tags: security upstream fixed-upstream The Oracle Critical Patch Update for April 2017 will be released on Tuesday, April 18. According to the pre-release announcement [1], it will contain information about CVEs fixed in MySQL 5.5.55. The CVE numbers will be available when the CPU is released. Please note that the MySQL release cycle has changed from every two months to every three months. The releases are now synchronized with the CPU announcements. Best regards, Norvald H. Ryeng [1] http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html
Bug#859969: Make native related files optional on bytecode archs
Hi again Stéphane, On Tue, 18 Apr 2017 10:28:38 +0200, Stéphane Glondu wrote: > On 13/04/2017 18:39, Frederic Bonnard wrote: > > on bytecode only architectures, the native related files won't be compiled > > because > > ocamlopt is not available in ocaml. So I made those files optional in the > > attached patch. > > Note that on ppc64el, ocamlopt is available starting with ocaml 4.03 and > > .a, .cmx and .cmxa will be generated. > > ocaml-dtools compiles on other bytecode only architectures. Do you have > an explanation on why it fails only on powerpcspe, ppc64 and sparc64? > > https://buildd.debian.org/status/package.php?p=ocaml-dtools&suite=sid As explained, in #859966, I guess the problem occurred at a later time and the build was re-run after this on those failing architectures, but it should happen on other bytecode archs. As for #859966, here is an updated patch with a correct destination directory (tested on amd64). F. diff -Nru ocaml-dtools-0.3.1/debian/libdtools-ocaml-dev.install.in ocaml-dtools-0.3.1/debian/libdtools-ocaml-dev.install.in --- ocaml-dtools-0.3.1/debian/libdtools-ocaml-dev.install.in2013-05-09 00:54:19.0 + +++ ocaml-dtools-0.3.1/debian/libdtools-ocaml-dev.install.in2013-05-09 00:54:35.0 + @@ -1 +1,2 @@ -src/META src/*.a src/*.cm* src/*.mli @OCamlStdlibDir@/dtools +src/META src/*.cm* src/*.mli @OCamlStdlibDir@/dtools +OPT: src/*.a @OCamlStdlibDir@/dtools pgpAKpMGPjWu9.pgp Description: PGP signature
Bug#859966: Make native related files optional on bytecode archs
Hi Stéphane, On Tue, 18 Apr 2017 10:50:16 +0200, Stéphane Glondu wrote: > On 18/04/2017 10:25, Stéphane Glondu wrote: > >> on bytecode only architectures, the native related files won't be > >> compiled because > >> ocamlopt is not available in ocaml. So I made those files optional in > >> the attached patch. > >> Note that on ppc64el, ocamlopt is available starting with ocaml 4.03 and > >> .cmx and .cmxa will be generated. > > > > I am suprised. How come ocaml-ao compiles as is on other bytecode only > > architectures, e.g. mips, s390x? > > > > https://buildd.debian.org/status/package.php?p=ocaml-ao&suite=unstable > As for #859969, I think we don't see the issue on other bytecode only architectures due to the fact that the builds occurred long time ago, before the issue actually appeared. See the attached log where the problem happens on mips. > Actually, debhelper changed meanwhile. In particular, changelog of > version 9.20160402 says: > > > * dh_install: Fix a regression where a non-existing file > > was ignored if another file was matched for the same > > destination dir. Thanks to Ben Hutchings for reporting > > the issue. (Closes: #818834) That explains indeed. > Thanks for the patch. However, did you try it on a native architectures? > It looks like the destination dir is missing on the OPT line... That's right, sorry for that, here is better patch which I tested on amd64 and that puts the .cmx and .cmxa in the good place. F. sbuild (Debian sbuild) 0.72.0 (25 Oct 2016) on misc-debomatic2 +==+ | ocaml-ao 0.2.0-1 (mips) Tue, 18 Apr 2017 09:52:48 + | +==+ Package: ocaml-ao Version: 0.2.0-1 Source Version: 0.2.0-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: mips Build Architecture: mips I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-mips-debomatic-0176e65b-066a-4725-8496-f547cccf4e71' with '<>' +--+ | Chroot Setup Commands| +--+ /home/debomatic/debomatic/sbuildcommands/chroot-setup-commands/dpkg-speedup ocaml-ao_0.2.0-1 unstable mips -- I: Finished running '/home/debomatic/debomatic/sbuildcommands/chroot-setup-commands/dpkg-speedup ocaml-ao_0.2.0-1 unstable mips'. Finished processing commands. +--+ | Update chroot| +--+ Get:1 http://debomatic-mips.debian.net/debomatic/unstable unstable InRelease [2300 B] Hit:2 http://ftp.debian.org/debian unstable InRelease Hit:3 http://cdn-fastly.deb.debian.org/debian unstable InRelease Ign:1 http://debomatic-mips.debian.net/debomatic/unstable unstable InRelease Fetched 2300 B in 12s (178 B/s) Reading package lists... W: No sandbox user '_apt' on the system, can not drop privileges W: GPG error: http://debomatic-mips.debian.net/debomatic/unstable unstable InRelease: The following signatures were invalid: 5EF4B898B5705C8953CFEF9136BF8574F4914DAB W: The repository 'http://debomatic-mips.debian.net/debomatic/unstable unstable InRelease' is not signed. W: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/debomatic-mips.debian.net_debomatic_unstable_dists_unstable_Release Reading package lists... Building dependency tree... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Local sources - /srv/debomatic-mips/ocaml-ao_0.2.0-1.dsc exists in /srv/debomatic-mips; copying to chroot I: NOTICE: Log filtering will replace 'build/ocaml-ao-f9tSe2/ocaml-ao-0.2.0' with '<>' I: NOTICE: Log filtering will replace 'build/ocaml-ao-f9tSe2' with '<>' +--+ | Install build-essential | +--+ Setup apt archive - Merged Build-Depends: build-essential, fakeroot Filtered Build-Depends: build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/<>/resolver-Uj6JNc/apt_archiv
Bug#823688: marked as pending
tag 823688 pending thanks Hello, Bug #823688 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/debian-edu/upstream/sitesummary.git/commit/?id=8eea2c3 --- commit 8eea2c38820da4b284d334499b15062879c4bc39 Author: Wolfgang Schweer Date: Tue Apr 18 12:48:57 2017 +0200 Fix d/sitesummary.prerm; cherrypicked from commit 3cff262 (master branch). (Closes: #823688). diff --git a/debian/changelog b/debian/changelog index 5b11151..eea7e46 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +sitesummary (0.1.17+deb8u3) UNRELEASED; urgency=medium + + * Fix d/sitesummary.prerm; cherrypicked from commit 3cff262 (master branch). +(Closes: #823688). + + -- Wolfgang Schweer Tue, 18 Apr 2017 12:40:49 +0200 + sitesummary (0.1.17+deb8u2) jessie-security; urgency=high * Backport RC fix from unstable.
Processed: Bug#823688 marked as pending
Processing commands for cont...@bugs.debian.org:
> tag 823688 pending
Bug #823688 {Done: Petter Reinholdtsen } [sitesummary]
sitesummary: prerm called with unknown argument `upgrade'
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
823688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 856487
Processing commands for cont...@bugs.debian.org: > tags 856487 + patch Bug #856487 [libsbc1] libsbc1: compiling with gcc > 4.9 causes stack corruption Ignoring request to alter tags of bug #856487 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 856487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858876: libjna-jni: causes NoClassDefFoundError
Le 18/04/2017 à 00:07, Emmanuel Bourg a écrit :
> I'll get another look.
I wrote a simple test case:
import com.sun.jna.platform.unix.X11;
public class JNATest {
public static void main(String[] args) throws Exception {
System.setProperty("jna.boot.library.name", "jnidispatch.foo");
System.out.println("XAllocSizeHints: " +
X11.INSTANCE.XAllocSizeHints());
}
}
Compiled and executed with the system JNA jar:
java -cp .:/usr/share/java/jna.jar:/usr/share/java/jna-platform.jar JNATest
And this always works, even if the jna.boot.library.name property
contains a bogus name.
Renaming libjnidispatch.system.so to libjnidispatch.so triggers
an UnsatisfiedLinkError.
I checked again the JNA code and there is no other occurrence of
jna.boot.library.* besides the ones removed in 4.2.2-3.
This issue really looks like an embedded jar. If it isn't in netbeans
directly, it could be in one of its dependencies.
Bug#857744: marked as done (qemu: CVE-2016-9603: cirrus: heap buffer overflow via vnc connection)
Your message dated Tue, 18 Apr 2017 09:04:13 + with message-id and subject line Bug#857744: fixed in qemu 1:2.8+dfsg-4 has caused the Debian Bug report #857744, regarding qemu: CVE-2016-9603: cirrus: heap buffer overflow via vnc connection 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.) -- 857744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Version: 1:2.8+dfsg-3 Severity: grave Tags: patch security upstream Justification: user security hole Control: found -1 2.1+dfsg-1 Hi, the following vulnerability was published for qemu. CVE-2016-9603[0]: cirrus: heap buffer overflow via vnc connection If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2016-9603 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9603 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1430056 Regards, Salvatore --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:2.8+dfsg-4 We believe that the bug you reported is fixed in the latest version of qemu, 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 857...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu 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: Mon, 03 Apr 2017 16:28:49 +0300 Source: qemu Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 1:2.8+dfsg-4 Distribution: unstable Urgency: high Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Description: qemu - fast processor emulator qemu-block-extra - extra block backend modules for qemu-system and qemu-utils qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscellaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user qemu-user-static - QEMU user mode emulation binaries (static version) qemu-utils - QEMU utilities Closes: 840950 844566 846084 856969 857744 859854 Changes: qemu (1:2.8+dfsg-4) unstable; urgency=high . * usb-ohci-limit-the-number-of-link-eds-CVE-2017-6505.patch Closes: #856969, CVE-2017-6505 * linux-user-fix-apt-get-update-on-linux-user-hppa.patch Closes: #846084 * update to 2.8.1 upstream stable/bugfix release (v2.8.1.diff from upstream, except of seabios blob bits). Closes: #857744, CVE-2016-9603 Patches dropped because they're included in 2.8.1 release: 9pfs-symlink-attack-fixes-CVE-2016-9602.patch char-fix-ctrl-a-b-not-working.patch cirrus-add-blit_is_unsafe-to-cirrus_bitblt_cputovideo-CVE-2017-2620.patch cirrus-fix-oob-access-issue-CVE-2017-2615.patch cirrus-ignore-source-pitch-as-needed-in-blit_is_unsafe.patch linux-user-fix-s390x-safe-syscall-for-z900.patch nbd_client-fix-drop_sync-CVE-2017-2630.patch s390x-use-qemu-cpu-model-in-user-mode.patch sd-sdhci-check-data-length-during-dma_memory_read-CVE-2017-5667.patch virtio-crypto-fix-possible-integer-and-heap-overflow-CVE-2017-5931.patch vmxnet3-fix-memory-corruption-on-vlan-header-stripping-CVE-2017-6058.patch * bump seabios dependency to 1.10.2 due to ahci fix in 2.8.1 * 9pfs-fix-file-descripto
Bug#856024: armhf bootstrap + molly-guard
# not reproducible on maintainer's system tags 856024 unreproducible thanks On 17 April 2017 at 18:59, Jonas Smedegaard wrote: > I don't recall, but believe I installed using plain standard > debian-installer with the "netboot" image. But possibly I might have > used multistrap, which means the order of installing the various > packages may be different from (c)debootrap-based installs. Something > that is *not* a bug in multistrap - Debian Policy mandates package > relations but no specific install order. Thanks - I'll break out some real armhf hardware later. So far I've mainly been testing by reinstalling rather than upgrading systemd-sysv. I don't *think* multistrap install order should be an issue - I've even tried uninstalling systemd-sysv in a chroot (so that /sbin/halt doesn't exist), installing molly-guard, then installing systemd-sysv again - but this seemed to be handled fine. If you used multistrap, does this mean there was another package repo involved? The bit I can't get my head round is why dpkg-divert would not have reported molly-guard having any diversions in place (which seems to match the error message "also in package molly-guard 0.6.4"). For any recently-installed stretch system, molly-guard should definitely have been using diversions. -- Tim Retout
Processed: Re: armhf bootstrap + molly-guard
Processing commands for cont...@bugs.debian.org: > # not reproducible on maintainer's system > tags 856024 unreproducible Bug #856024 [molly-guard] molly-guard: causes failure to update systemd-sysv Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 856024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859966: Make native related files optional on bytecode archs
On 18/04/2017 10:25, Stéphane Glondu wrote: on bytecode only architectures, the native related files won't be compiled because ocamlopt is not available in ocaml. So I made those files optional in the attached patch. Note that on ppc64el, ocamlopt is available starting with ocaml 4.03 and .cmx and .cmxa will be generated. I am suprised. How come ocaml-ao compiles as is on other bytecode only architectures, e.g. mips, s390x? https://buildd.debian.org/status/package.php?p=ocaml-ao&suite=unstable Actually, debhelper changed meanwhile. In particular, changelog of version 9.20160402 says: * dh_install: Fix a regression where a non-existing file was ignored if another file was matched for the same destination dir. Thanks to Ben Hutchings for reporting the issue. (Closes: #818834) Thanks for the patch. However, did you try it on a native architectures? It looks like the destination dir is missing on the OPT line... Cheers, -- Stéphane
Bug#859969: Make native related files optional on bytecode archs
On 13/04/2017 18:39, Frederic Bonnard wrote: on bytecode only architectures, the native related files won't be compiled because ocamlopt is not available in ocaml. So I made those files optional in the attached patch. Note that on ppc64el, ocamlopt is available starting with ocaml 4.03 and .a, .cmx and .cmxa will be generated. ocaml-dtools compiles on other bytecode only architectures. Do you have an explanation on why it fails only on powerpcspe, ppc64 and sparc64? https://buildd.debian.org/status/package.php?p=ocaml-dtools&suite=sid Cheers, -- Stéphane
Bug#859966: Make native related files optional on bytecode archs
On 13/04/2017 18:33, Frederic Bonnard wrote: on bytecode only architectures, the native related files won't be compiled because ocamlopt is not available in ocaml. So I made those files optional in the attached patch. Note that on ppc64el, ocamlopt is available starting with ocaml 4.03 and .cmx and .cmxa will be generated. I am suprised. How come ocaml-ao compiles as is on other bytecode only architectures, e.g. mips, s390x? https://buildd.debian.org/status/package.php?p=ocaml-ao&suite=unstable Cheers, -- Stéphane
