Bug#866758: Please close this bug
Hi Roger, On Wed, 29 May 2019 13:47:07 -0500 "Roger T. Imai" wrote: > I can't find a method or instructions for closing bug 866758, possibly > because I was a contributor, not the original submitter. A subsequent > kernel or Intel microcode update resolved the issue in my case. It's easy, just send mail to -d...@bugs.debian.org. However, I want to wait original reporter's reply for it. -- Hideki Yamane
Bug#927808: marked as done (gmsh: FTBFS in buster ("/usr/include/occt/Standard_Version.hxx" cannot be read))
Your message dated Thu, 30 May 2019 00:48:37 +
with message-id
and subject line Bug#927808: fixed in gmsh 4.1.5+really4.1.3+ds1-1
has caused the Debian Bug report #927808,
regarding gmsh: FTBFS in buster ("/usr/include/occt/Standard_Version.hxx"
cannot be read)
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.)
--
927808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gmsh
Version: 4.1.3+ds1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=cmake
--builddirectory=/<>/gmsh-4.1.3+ds1/debian/build --with python3
dh_update_autotools_config -i -O--buildsystem=cmake
-O--builddirectory=/<>/gmsh-4.1.3\+ds1/debian/build
dh_autoreconf -i -O--buildsystem=cmake
-O--builddirectory=/<>/gmsh-4.1.3\+ds1/debian/build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/gmsh-4.1.3+ds1'
dh_auto_configure -- -DENABLE_OS_SPECIFIC_INSTALL:BOOL=ON
-DENABLE_SYSTEM_CONTRIB:BOOL=ON -DENABLE_METIS:BOOL=OFF -DENABLE_MED:BOOL=OFF
-DENABLE_TAUCS:BOOL=OFF -DENABLE_OSMESA:BOOL=OFF -DENABLE_CGNS:BOOL=ON
-DENABLE_OCC:BOOL=ON -DENABLE_OCC_CAF:BOOL=ON -DENABLE_WRAP_PYTHON:BOOL=ON
-DENABLE_BUILD_SHARED:BOOL=ON -DENABLE_BUILD_DYNAMIC:BOOL=ON
-DENABLE_ONELAB:BOOL=ON -DCMAKE_SKIP_RPATH:BOOL=ON
-DCMAKE_INCLUDE_PATH:STRING="/usr/include/mpi"
-DOCC_INC:STRING="/usr/include/occt"
-DOCC_LIB:STRING="/usr/lib/x86_64-linux-gnu"
â -DCMAKE_CXX_FLAGS="-DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX
-lmpi -fPIC -Wall -g -O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=.
-fstack-protector-strong -Wformat -Werror=format-security" -DENABLE_MPI:BOOL=ON
cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DENABLE_OS_SPECIFIC_INSTALL:BOOL=ON -DENABLE_SYSTEM_CONTRIB:BOOL=ON
-DENABLE_METIS:BOOL=OFF -DENABLE_MED:BOOL=OFF -DENABLE_TAUCS:BOOL=OFF
-DENABLE_OSMESA:BOOL=OFF -DENABLE_CGNS:BOOL=ON -DENABLE_OCC:BOOL=ON
-DENABLE_OCC_CAF:BOOL=ON -DENABLE_WRAP_PYTHON:BOOL=ON
-DENABLE_BUILD_SHARED:BOOL=ON -DENABLE_BUILD_DYNAMIC:BOOL=ON
-DENABLE_ONELAB:BOOL=ON -DCMAKE_SKIP_RPATH:BOOL=ON
-DCMAKE_INCLUDE_PATH:STRING=/usr/include/mpi -DOCC_INC:STRING=/usr/include/occt
-DOCC_LIB:STRING=/usr/lib/x86_64-linux-gnu â
"-DCMAKE_CXX_FLAGS=-DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX -lmpi -fPIC -Wall -g
-O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=. -fstack-protec
tor-strong -Wformat -Werror=format-security" -DENABLE_MPI:BOOL=ON ../..
-- The CXX compiler identification is GNU 8.3.0
-- The C compiler identification is GNU 8.3.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
[... snipped ...]
make[3]: Leaving directory
'/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp'
make[2]: Leaving directory
'/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp'
Determining if the include file dlfcn.h exists passed with the following output:
Change Dir: /<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp
Run Build Command:"/usr/bin/make" "cmTC_c1405/fast"
make[2]: Entering directory
'/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_c1405.dir/build.make
CMakeFiles/cmTC_c1405.dir/build
make[3]: Entering directory
'/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_c1405.dir/CheckIncludeFile.c.o
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic
-Wdate-time -D_FORTIFY_SOURCE=2 -std=c99-o
CMakeFiles/cmTC_c1405.dir/CheckIncludeFile.c.o -c
/<>/gmsh-4.1.3+ds1/debian/build/CMakeFiles/CMakeTmp/CheckIncludeFile.c
Linking C executable cmTC_c1405
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_c1405.dir/link.txt
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>/gmsh-4.1.3+ds1=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic
-Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wl,-z,relro -Wl,-z,now
Bug#890669: marked as done (fmit: FTBFS with glibc 2.27: error: 'pow10' was not declared in this scope)
Your message dated Wed, 29 May 2019 23:03:38 + with message-id and subject line Bug#890669: fixed in fmit 1.0.0-1.1 has caused the Debian Bug report #890669, regarding fmit: FTBFS with glibc 2.27: error: 'pow10' was not declared in this scope 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.) -- 890669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fmit Version: 1.0.0-1 Severity: important Tags: patch User: debian-gl...@lists.debian.org Usertags: 2.27 fmit 1.0.0-1 fails to build with glibc 2.27 (2.27-0experimental0 from experimental): | cd /<>/obj-x86_64-linux-gnu/libs/Music && /usr/bin/c++ -DCAPTURE_ALSA -DCAPTURE_JACK -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtOpenGL -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore -I/<>/libs/Music/../../libs -I/<>/obj-x86_64-linux-gnu/libs/Music -Wall -DPREFIX=\"/usr\" -DPACKAGE_NAME=\"fmit\" -DPACKAGE_VERSION=\"1.0.0\" -o CMakeFiles/Music.dir/Algorithm.o -c /<>/libs/Music/Algorithm.cpp | In file included from /<>/libs/Music/Algorithm.h:28:0, | from /<>/libs/Music/Algorithm.cpp:20: | /<>/libs/Music/Music.h: In function 'double Music::invlp(double)': | /<>/libs/Music/Music.h:288:16: error: 'pow10' was not declared in this scope | return pow10(value/20.0); | ^ | /<>/libs/Music/Music.h:288:16: note: suggested alternative: 'powl' | return pow10(value/20.0); | ^ | powl | libs/Music/CMakeFiles/Music.dir/build.make:65: recipe for target 'libs/Music/CMakeFiles/Music.dir/Algorithm.o' failed | make[3]: *** [libs/Music/CMakeFiles/Music.dir/Algorithm.o] Error 1 | make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' | CMakeFiles/Makefile2:88: recipe for target 'libs/Music/CMakeFiles/Music.dir/all' failed | make[2]: *** [libs/Music/CMakeFiles/Music.dir/all] Error 2 | make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' | Makefile:154: recipe for target 'all' failed | make[1]: *** [all] Error 2 | make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' | dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2 | debian/rules:11: recipe for target 'build-arch' failed | make: *** [build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2cd /<>/obj-x86_64-linux-gnu/libs/Music && /usr/bin/c++ -DCAPTURE_ALSA -DCAPTURE_JACK -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtOpenGL -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore -I/<>/libs/Music/../../libs -I/<>/obj-x86_64-linux-gnu/libs/Music -Wall -DPREFIX=\"/usr\" -DPACKAGE_NAME=\"fmit\" -DPACKAGE_VERSION=\"1.0.0\" -o CMakeFiles/Music.dir/Algorithm.o -c /<>/libs/Music/Algorithm.cpp | In file included from /<>/libs/Music/Algorithm.h:28:0, | from /<>/libs/Music/Algorithm.cpp:20: | /<>/libs/Music/Music.h: In function 'double Music::invlp(double)': | /<>/libs/Music/Music.h:288:16: error: 'pow10' was not declared in this scope | return pow10(value/20.0); | ^ | /<>/libs/Music/Music.h:288:16: note: suggested alternative: 'powl' | return pow10(value/20.0); | ^ | powl | libs/Music/CMakeFiles/Music.dir/build.make:65: recipe for target 'libs/Music/CMakeFiles/Music.dir/Algorithm.o' failed | make[3]: *** [libs/Music/CMakeFiles/Music.dir/Algorithm.o] Error 1 | make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' | CMakeFiles/Makefile2:88: recipe for target 'libs/Music/CMakeFiles/Music.dir/all' failed | make[2]: *** [libs/Music/CMakeFiles/Music.dir/all] Error 2 | make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' | Makefile:154: recipe for target 'all' failed | make[1]: *** [all] Error 2 | make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' | dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2 | debian/rules:11: recipe for target 'build-arch' failed | make: *** [build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 A full build logs is available there: http://aws-logs.debian.net/2018/02/07/glibc-exp/fmit_1.0.0-1_unstable_glibc-exp.log Starting with glibc 2.27, the libm function pow10 is no longer supported for. The standard exp10 (from TS 18661-4:2015) should be used instead. The attached patch fixes that. diff -Nru fmit-1.0.0/debian/patches/pow10.patch
Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
Hello, Just so that the info is recorded here as well: as discussed on https://lists.debian.org/debian-accessibility/2019/02/msg4.html Wayland does not provide yet the support that the Orca screen reader needs to provide proper support for blind people (keyboard shortcuts for GUI review, basically). Samuel
Bug#929151: netdata-core: version in stretch-backports newer than version in buster
Hi, I'm on VAC until end of week, will ask for an unblock of 1.12.1-2 next week (there are a bunch of fixes in that version that need to be in buster anyway). Regards, Daniel
Bug#929735: marked as done (ltsp-client-builder: fails to build ltsp client environment when installing from CD)
Your message dated Wed, 29 May 2019 20:48:32 + with message-id and subject line Bug#929735: fixed in ltsp 5.18.12-3 has caused the Debian Bug report #929735, regarding ltsp-client-builder: fails to build ltsp client environment when installing from CD 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.) -- 929735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ltsp-client-builder Version: 5.18.12-1 Severity: serious Tags: patch ltsp-client-builder defaults are targeted at unsigned CD images, and currently fail because it does not pass the --trust-file-mirror to ltsp-build-client, which was introduced to solve this issue in: https://bugs.debian.org/911380 But the defaults for ltsp-client-builder were not updated to include --trust-file-mirror, the following one-line patch adds it: diff --git a/debian/ltsp-client-builder.templates b/debian/ltsp-client-builder.templates index 996dbda7..a85884a7 100644 --- a/debian/ltsp-client-builder.templates +++ b/debian/ltsp-client-builder.templates @@ -29,7 +29,7 @@ _Description: Compressing thin client image... Template: ltsp-client-builder/build-client-opts Type: string -Default: --mirror file:///media/cdrom --security-mirror none --updates-mirror none --accept-unsigned-packages +Default: --mirror file:///media/cdrom --security-mirror none --updates-mirror none --accept-unsigned-packages --trust-file-mirror # Only used for preseeding arguments to ltsp-client-builder. Description: for internal use: arguments for ltsp-build-client: this option is meant to be used with debconf preseeding. live well, vagrant signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ltsp Source-Version: 5.18.12-3 We believe that the bug you reported is fixed in the latest version of ltsp, 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 929...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vagrant Cascadian (supplier of updated ltsp 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, 29 May 2019 13:02:07 -0700 Source: ltsp Architecture: source Version: 5.18.12-3 Distribution: unstable Urgency: medium Maintainer: Debian LTSP Maintainers Changed-By: Vagrant Cascadian Closes: 929735 Changes: ltsp (5.18.12-3) unstable; urgency=medium . * ltsp-client-builder: Add --trust-file-mirror to ltsp-build-client options to fix builds from unsigned CDs (Closes: #929735). Checksums-Sha1: 5062b091c76ae349fc513da854797f862dbbf367 1684 ltsp_5.18.12-3.dsc a932514651ac22663da5e214a42dacc83e4721dd 76976 ltsp_5.18.12-3.debian.tar.xz eec5f889eafd054cff761f403339abc91170c028 6861 ltsp_5.18.12-3_amd64.buildinfo Checksums-Sha256: 184c380ad42f9d2b9b49bf30709083aaa843d6aff3baef4de9ec8e2bcb63d6cc 1684 ltsp_5.18.12-3.dsc e6cc02f383b2b9186169a1553becf0d603cdaab41559f3522a3f39aa4b047514 76976 ltsp_5.18.12-3.debian.tar.xz fdad26782786e30d4e206d801ab0384c9534a5f796e32c89bd76382ea6b477f7 6861 ltsp_5.18.12-3_amd64.buildinfo Files: b1e969e9dec77ed1ce012ac7be105c13 1684 misc optional ltsp_5.18.12-3.dsc 97beb5946a7583ea5e2c72dc233dbf05 76976 misc optional ltsp_5.18.12-3.debian.tar.xz c5ba383dfa43422bb9459bcae82c34d8 6861 misc optional ltsp_5.18.12-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCXO7mOBMcdmFncmFudEBk ZWJpYW4ub3JnAAoJENxRj8h/lxaq/lAA/R/L2AHS3q87tm8B+bDRbZ2zQHy8gEOP eHeSwi1i+sbNAP48Lc3a/k7WBNGl9WPFCZwlpBXw+86jtwblhMlBg6RQCQ== =h27M -END PGP SIGNATURE End Message ---
Bug#929735: ltsp-client-builder: fails to build ltsp client environment when installing from CD
Package: ltsp-client-builder Version: 5.18.12-1 Severity: serious Tags: patch ltsp-client-builder defaults are targeted at unsigned CD images, and currently fail because it does not pass the --trust-file-mirror to ltsp-build-client, which was introduced to solve this issue in: https://bugs.debian.org/911380 But the defaults for ltsp-client-builder were not updated to include --trust-file-mirror, the following one-line patch adds it: diff --git a/debian/ltsp-client-builder.templates b/debian/ltsp-client-builder.templates index 996dbda7..a85884a7 100644 --- a/debian/ltsp-client-builder.templates +++ b/debian/ltsp-client-builder.templates @@ -29,7 +29,7 @@ _Description: Compressing thin client image... Template: ltsp-client-builder/build-client-opts Type: string -Default: --mirror file:///media/cdrom --security-mirror none --updates-mirror none --accept-unsigned-packages +Default: --mirror file:///media/cdrom --security-mirror none --updates-mirror none --accept-unsigned-packages --trust-file-mirror # Only used for preseeding arguments to ltsp-client-builder. Description: for internal use: arguments for ltsp-build-client: this option is meant to be used with debconf preseeding. live well, vagrant signature.asc Description: PGP signature
Processed: Re: gucharmap: FTBFS: unsatisfiable build-dependency: unicode-data (< 11.1) but 12.1.0~pre1-2 is to be installed
Processing commands for cont...@bugs.debian.org: > fixed 929719 1:11.0.3-3 Bug #929719 [src:gucharmap] gucharmap: FTBFS: unsatisfiable build-dependency: unicode-data (< 11.1) but 12.1.0~pre1-2 is to be installed Marked as fixed in versions gucharmap/1:11.0.3-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 929719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929732: marked as done (firejail: seccomp bypass when joining jails)
Your message dated Wed, 29 May 2019 19:33:31 + with message-id and subject line Bug#929732: fixed in firejail 0.9.58.2-2 has caused the Debian Bug report #929732, regarding firejail: seccomp bypass when joining jails 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.) -- 929732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: firejail Version: 0.9.52-1 Severity: critical Tags: security upstream pending fixed-upstream Forwarded: https://github.com/netblue30/firejail/issues/2718 X-Debbugs-CC: t...@security.debian.org A bug in firejail allows bypassing seccomp protection when an existing jail is joined with another one [2]. Upstream description [0]: > Seccomp filters are copied into /run/firejail/mnt, and are writable > within the jail. A malicious process can modify files from inside the > jail. Processes that are later joined to the jail will not have seccomp > filters applied. A fix is available [1] and also released in the new upstream version 0.9.60. I will upload a backported fix to 0.9.58.2-1 to unstable soon. The earliest acknowledged version that is affected is 0.9.52 (upstream provides a patch for this version in [0]), but likely earlier versions are affected as well. According to [2], a CVE number has been requested. [0] https://github.com/netblue30/firejail/commit/30f6000e72bd8d9eee6a0d2e700d69ed9be3aa29 [1] https://github.com/netblue30/firejail/commit/eecf35c2f8249489a1d3e512bb07f0d427183134 [2] https://github.com/netblue30/firejail/issues/2718 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: firejail Source-Version: 0.9.58.2-2 We believe that the bug you reported is fixed in the latest version of firejail, 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 929...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated firejail 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, 29 May 2019 21:06:42 +0200 Source: firejail Architecture: source Version: 0.9.58.2-2 Distribution: unstable Urgency: high Maintainer: Reiner Herrmann Changed-By: Reiner Herrmann Closes: 929732 929733 Changes: firejail (0.9.58.2-2) unstable; urgency=high . * Cherry-pick security fix for seccomp bypass issue. (Closes: #929732) Seccomp filters were writable inside the jail, so they could be overwritten/truncated. Another jail that was then joined with the first one, had no seccomp filters applied. * Cherry-pick security fix for binary truncation issue. (Closes: #929733) When the jailed program was running as root, and firejail was killed from the outside (as root), the jailed program had the possibility to truncate the firejail binary outside the jail. Checksums-Sha1: 465593c08200ef411ce2efb628b62bd80e3b7cb8 2489 firejail_0.9.58.2-2.dsc 62daa05a45c60c10b94fc3d03d29b4281a2d0713 13356 firejail_0.9.58.2-2.debian.tar.xz 3afaf6ed7398611e20e6124c232f360eb0ea056f 5561 firejail_0.9.58.2-2_source.buildinfo Checksums-Sha256: 088a95f3ba986b97183b2654817e74c4c8659d9a9ad4a99dacfd8da74f48c73d 2489 firejail_0.9.58.2-2.dsc 1e8aad6ea5cebea03fd96016a2d5be69c8b9fc72c782adf168d0dcdad8cc264e 13356 firejail_0.9.58.2-2.debian.tar.xz a532acf96c3d07ab05b0c001139d1e611a4d96ddb50d674ab71eb35964b2ea84 5561 firejail_0.9.58.2-2_source.buildinfo Files: ecd8954cef22c1e8867682515b87c8fb 2489 utils optional firejail_0.9.58.2-2.dsc c54b379a0c10cb43da7db1ad7da49edb 13356 utils optional firejail_0.9.58.2-2.debian.tar.xz 780d17157665f16ab58ff60cd549950d 5561 utils optional firejail_0.9.58.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAlzu2HAACgkQzPBJKNsO 6qew+w/+K3a5QQEFz5LRCJmukcWivg/lYjTqLdbeRz2tseSK1J2SVmLgFCWDbh7f PXfKhnE28FvyPYNbDOFNVF72s9xlE4YgDMqLco8mLVtqlkLEGVGSv3ba3lDZ/GNt QpSaqMYpSrg+QxfxOdmfZf/OTB+hwc52EIT4YQl8qA968ml5SlyBZyEZbF3VneJm 0FfctbHdJQO02v6pyXKI4ZSHsGLPE30A/5vwz7G9qr3fITAKn/V4ZhdBvH7hQPiZ oCRl3M06PSaVw0l9OdbKJU+gRwXUVcVw0A5iyUEWVo8+Tzc9qaIXKujsXW5Wp97a
Bug#866758: Fwd: Please close this bug
CORRECTION: ...a subsequent AMD microcode update... (I have since switched from AMD to Intel hardware.) > I can't find a method or instructions for closing bug 866758, possibly because I was a contributor, not the original submitter. > A subsequent kernel or Intel microcode update resolved the issue in my case. --Roger T. Imai
Bug#866758: Please close this bug
I can't find a method or instructions for closing bug 866758, possibly because I was a contributor, not the original submitter. A subsequent kernel or Intel microcode update resolved the issue in my case. --Roger T. Imai
Bug#928631:
Exactly the same issue with AMD Vega 56 videocard, also depends on vega10_gpu_info.bin: May 29 11:49:37 debian1 kernel: [4.351872] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_gpu_info.bin <..> May 29 11:49:37 debian1 kernel: [4.352869] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sos.bin May 29 11:49:37 debian1 kernel: [4.352895] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_asd.bin May 29 11:49:37 debian1 kernel: [4.352971] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_acg_smc.bin May 29 11:49:37 debian1 kernel: [4.352996] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_pfp.bin May 29 11:49:37 debian1 kernel: [4.353008] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_me.bin May 29 11:49:37 debian1 kernel: [4.353019] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_ce.bin May 29 11:49:37 debian1 kernel: [4.353031] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_rlc.bin May 29 11:49:37 debian1 kernel: [4.353109] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_mec.bin May 29 11:49:37 debian1 kernel: [4.353188] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_mec2.bin May 29 11:49:37 debian1 kernel: [4.355194] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sdma.bin May 29 11:49:37 debian1 kernel: [4.355209] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sdma1.bin -- -Alex
Bug#929717: golang-fsnotify: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/fsnotify/fsnotify returned exit code 1
Control: severity -1 important On Wed, May 29, 2019 at 10:39 PM Lucas Nussbaum wrote: > > --- FAIL: TestInotifyOverflow (4.69s) > > inotify_test.go:442: Could not trigger overflow Unfortunately, this test expects your system's fs.inotify.max_queued_events is not greater than 128*1024. This is usually fine, as the default is 16384. Thus I also don't think this is RC. -- Shengjing Zhu
Bug#929732: firejail: seccomp bypass when joining jails
Source: firejail Version: 0.9.52-1 Severity: critical Tags: security upstream pending fixed-upstream Forwarded: https://github.com/netblue30/firejail/issues/2718 X-Debbugs-CC: t...@security.debian.org A bug in firejail allows bypassing seccomp protection when an existing jail is joined with another one [2]. Upstream description [0]: > Seccomp filters are copied into /run/firejail/mnt, and are writable > within the jail. A malicious process can modify files from inside the > jail. Processes that are later joined to the jail will not have seccomp > filters applied. A fix is available [1] and also released in the new upstream version 0.9.60. I will upload a backported fix to 0.9.58.2-1 to unstable soon. The earliest acknowledged version that is affected is 0.9.52 (upstream provides a patch for this version in [0]), but likely earlier versions are affected as well. According to [2], a CVE number has been requested. [0] https://github.com/netblue30/firejail/commit/30f6000e72bd8d9eee6a0d2e700d69ed9be3aa29 [1] https://github.com/netblue30/firejail/commit/eecf35c2f8249489a1d3e512bb07f0d427183134 [2] https://github.com/netblue30/firejail/issues/2718 signature.asc Description: PGP signature
Processed: Re: Bug#929717: golang-fsnotify: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/fsnotify/fsnotify returned exit code 1
Processing control commands: > severity -1 important Bug #929717 [src:golang-fsnotify] golang-fsnotify: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/fsnotify/fsnotify returned exit code 1 Severity set to 'important' from 'serious' -- 929717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#929716: notary: FTBFS: dh_auto_test: cd _build && go test -vet=off -v -p 4 github.com/theupdateframework/notary [...] github.com/theupdateframework/notary/version returned exit code
Processing control commands: > severity -1 normal Bug #929716 [src:notary] notary: FTBFS: dh_auto_test: cd _build && go test -vet=off -v -p 4 github.com/theupdateframework/notary [...] github.com/theupdateframework/notary/version returned exit code 1 Severity set to 'normal' from 'serious' -- 929716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929721: golang-github-gin-gonic-gin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding github.com/gin-gonic/gin/gin
Control: severity -1 normal On Wed, May 29, 2019 at 10:39 PM Lucas Nussbaum wrote: > [...] > > [GIN-debug] GET/test --> > > github.com/gin-gonic/gin.setupHTMLGlob.func1.1 (1 handlers) > > [GIN-debug] GET/raw --> > > github.com/gin-gonic/gin.setupHTMLGlob.func1.2 (1 handlers) > > [GIN-debug] Listening and serving HTTPS on : > > [GIN-debug] [ERROR] listen tcp :: bind: address already in use This test needs to listen on . I don't think this would be RC, so I will downgrade this bug. -- Shengjing Zhu
Processed: Re: Bug#929721: golang-github-gin-gonic-gin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding github.com/gi
Processing control commands: > severity -1 normal Bug #929721 [src:golang-github-gin-gonic-gin] golang-github-gin-gonic-gin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding github.com/gin-gonic/gin/ginS github.com/gin-gonic/gin/json github.com/gin-gonic/gin/render returned exit code 1 Severity set to 'normal' from 'serious' -- 929721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929716: notary: FTBFS: dh_auto_test: cd _build && go test -vet=off -v -p 4 github.com/theupdateframework/notary [...] github.com/theupdateframework/notary/version returned exit code 1
Control: severity -1 normal On Wed, May 29, 2019 at 10:39 PM Lucas Nussbaum wrote: > [...] > > --- FAIL: TestSetupNetListener (0.00s) > > require.go:794: > > Error Trace:config_test.go:61 > > Error: Received unexpected error: > > listen tcp 127.0.0.1:: bind: address > > already in use > > Test: TestSetupNetListener > > FAIL This test need to listen on . I don't think this would be RC, so I will downgrade this bug. -- Shengjing Zhu
Bug#928883: marked as done (libzorpll-dev: add Breaks)
Your message dated Wed, 29 May 2019 14:41:32 +
with message-id
and subject line Bug#928883: fixed in libzorpll 7.0.1.0~alpha1-1.1
has caused the Debian Bug report #928883,
regarding libzorpll-dev: add Breaks
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.)
--
928883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libzorpll-dev
Version: 7.0.1.0~alpha1-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch' in some scenarios, and the old version from stretch is kept
installed. This is related to the switch from libssl1.0-dev to
libssl-dev.
Adding
Breaks: libzorpll-6.0-10-dev, libssl1.0-dev
to libzorpll-7.0-1-dev pushes the scores in the right direction and apt
will remove libssl1.0-dev to perform this upgrade step.
Note that the synopsis of libzorpll-7.0-1-dev still mentions
"development files for version 6.0-10", you should fix that as well.
I've tested that the package built with the attached patch passes the
piuparts stretch->buster upgrade test without holding back any upgradable
package.
cheers,
Andreas
diff -Nru libzorpll-7.0.1.0~alpha1/debian/changelog
libzorpll-7.0.1.0~alpha1/debian/changelog
--- libzorpll-7.0.1.0~alpha1/debian/changelog 2018-10-10 22:21:22.0
+0200
+++ libzorpll-7.0.1.0~alpha1/debian/changelog 2019-05-12 12:20:04.0
+0200
@@ -1,3 +1,10 @@
+libzorpll (7.0.1.0~alpha1-1.1) UNRELEASED; urgency=medium
+
+ * libzorpll-7.0-1-dev: Add Breaks: libzorpll-6.0-10-dev, libssl1.0-dev for
+smoother upgrades from stretch. (Closes: #xx)
+
+ -- Andreas Beckmann Sun, 12 May 2019 12:20:04 +0200
+
libzorpll (7.0.1.0~alpha1-1) unstable; urgency=medium
* New upstream version (Closes: #859055)
diff -Nru libzorpll-7.0.1.0~alpha1/debian/control
libzorpll-7.0.1.0~alpha1/debian/control
--- libzorpll-7.0.1.0~alpha1/debian/control 2018-10-10 22:21:22.0
+0200
+++ libzorpll-7.0.1.0~alpha1/debian/control 2019-05-12 12:20:04.0
+0200
@@ -34,7 +34,7 @@
Package: libzorpll-7.0-1-dev
Section: libdevel
Replaces: libzorpll-dev ( << 6.0.8.0-1)
-Breaks: libzorpll-dev ( << 6.0.8.0-1)
+Breaks: libzorpll-dev ( << 6.0.8.0-1), libzorpll-6.0-10-dev, libssl1.0-dev
Conflicts: libzorpll-6.0-8-dev
Architecture: any
Depends: libzorpll-7.0-1 (= ${binary:Version}), ${misc:Depends},
libglib2.0-dev, libcap-dev [linux-any], libssl-dev
libzorpll-dev_7.0.1.0~alpha1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libzorpll
Source-Version: 7.0.1.0~alpha1-1.1
We believe that the bug you reported is fixed in the latest version of
libzorpll, 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 928...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lamb (supplier of updated libzorpll 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: Fri, 24 May 2019 14:06:05 +0100
Source: libzorpll
Binary: libzorpll-7.0-1 libzorpll-7.0-1-dbgsym libzorpll-7.0-1-dev libzorpll-dev
Architecture: source amd64 all
Version: 7.0.1.0~alpha1-1.1
Distribution: unstable
Urgency: medium
Maintainer: SZALAY Attila
Changed-By: Chris Lamb
Description:
libzorpll-7.0-1 - Zorp low-level functions
libzorpll-7.0-1-dev - Zorp low-level functions - development files for version
6.0-10
libzorpll-dev - Zorp low-level functions - development files
Closes: 928883
Changes:
libzorpll (7.0.1.0~alpha1-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Apply patch from Andreas Beckmann to add "Breaks" on libzorpll-6.0-10-dev
and libssl1.0-dev for smoother upgrades from stretch. This resulted from
the switch from libssl1.0-dev to libssl-dev. (Closes: #928883)
Checksums-Sha1:
c520e96461768f0d407e1fb137a6837ae09b8d96 2074 libzorpll_7.0.1.0~alpha1-1.1.dsc
d3cfe0b3f794629cc00486a8a22d368c08be65fc 195256
libzorpll_7.0.1.0~alpha1.orig.tar.gz
c02287414eb59e16cf9a51536d633e181da9efb4 10904
libzorpll_7.0.1.0~alpha1-1.1.debian.tar.xz
Bug#929718: gdcm: FTBFS: dh_makeshlibs: failing due to earlier errors
Source: gdcm Version: 2.8.8-6 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190529 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # do not compress .map file for doxygen graph > dh_compress -X.map -X.pdf > make[1]: Leaving directory '/<>' >dh_fixperms -O--buildsystem=cmake\+ninja >dh_clifixperms -O--buildsystem=cmake\+ninja >dh_missing -O--buildsystem=cmake\+ninja >dh_strip -O--buildsystem=cmake\+ninja >dh_makeshlibs -O--buildsystem=cmake\+ninja > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libvtkgdcm2.8a/DEBIAN/symbols doesn't match > completely debian/libvtkgdcm2.8a.symbols > --- debian/libvtkgdcm2.8a.symbols (libvtkgdcm2.8a_2.8.8-6_amd64) > +++ dpkg-gensymbolspIQKll 2019-05-29 05:16:07.185014757 + > @@ -855,17 +855,17 @@ > _ZN31vtkImageMapToWindowLevelColors2D1Ev@Base 2.8.7 > _ZN31vtkImageMapToWindowLevelColors2D2Ev@Base 2.8.7 > _ZN4gdcm11DataElement12SetByteValueEPKcNS_2VLE@Base 2.8.7 > - (arch-bits=64)_ZN4gdcm12SmartPointerINS_15SequenceOfItemsEEaSEPS1_@Base > 2.8.7-2~ > +#MISSING: 2.8.8-6# > (arch-bits=64)_ZN4gdcm12SmartPointerINS_15SequenceOfItemsEEaSEPS1_@Base > 2.8.7-2~ > _ZN4gdcm12SmartPointerINS_5ValueEEaSEPS1_@Base 2.8.7 > _ZN4gdcm20BitmapToBitmapFilterD1Ev@Base 2.8.7 > _ZN4gdcm20BitmapToBitmapFilterD2Ev@Base 2.8.7 > - > _ZN4gdcm22EncodingImplementationILi74550907EE4ReadINS_6StringILc92ELj16ELc32EvPT_mRSi@Base > 2.8.7 > +#MISSING: 2.8.8-6# > _ZN4gdcm22EncodingImplementationILi74550907EE4ReadINS_6StringILc92ELj16ELc32EvPT_mRSi@Base > 2.8.7 > > _ZN4gdcm22EncodingImplementationILi74550907EE4ReadINS_6StringILc92ELj64ELc0EvPT_mRSi@Base > 2.8.7 > > _ZN4gdcm22EncodingImplementationILi74550907EE4ReadINS_6StringILc92ELj64ELc32EvPT_mRSi@Base > 2.8.7 > _ZN4gdcm22EncodingImplementationILi74550907EE4ReadIdEEvPT_mRSi@Base 2.8.7 > _ZN4gdcm22EncodingImplementationILi74550907EE4ReadIiEEvPT_mRSi@Base 2.8.7-2~ > > _ZN4gdcm22EncodingImplementationILi74550907EE5WriteINS_6StringILc92ELj64ELc0EvPKT_mRSo@Base > 2.8.7 > - > (arch-bits=64)_ZN4gdcm22EncodingImplementationILi74550907EE5WriteINS_6StringILc92ELj64ELc32EvPKT_mRSo@Base > 2.8.7-2~ > +#MISSING: 2.8.8-6# > (arch-bits=64)_ZN4gdcm22EncodingImplementationILi74550907EE5WriteINS_6StringILc92ELj64ELc32EvPKT_mRSo@Base > 2.8.7-2~ > _ZN4gdcm4ItemD1Ev@Base 2.8.7 > _ZN4gdcm4ItemD2Ev@Base 2.8.7 > _ZN4gdcm6Object10UnRegisterEv@Base 2.8.7 > dh_makeshlibs: failing due to earlier errors > make: *** [debian/rules:49: binary] Error 2 The full build log is available from: http://qa-logs.debian.net/2019/05/29/gdcm_2.8.8-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#929721: golang-github-gin-gonic-gin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding github.com/gin-gonic/gin/gin
Source: golang-github-gin-gonic-gin Version: 1.3.0+dfsg1-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190529 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install > -gcflags=all=\"-trimpath=/<>/golang-github-gin-gonic-gin-1.3.0\+dfsg1/obj-x86_64-linux-gnu/src\" > > -asmflags=all=\"-trimpath=/<>/golang-github-gin-gonic-gin-1.3.0\+dfsg1/obj-x86_64-linux-gnu/src\" > -v -p 4 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding > github.com/gin-gonic/gin/ginS github.com/gin-gonic/gin/json > github.com/gin-gonic/gin/render > internal/race > errors > internal/cpu > runtime/internal/atomic > runtime/internal/sys > sync/atomic > unicode > unicode/utf8 > crypto/subtle > internal/bytealg > math/bits > math > encoding > internal/testlog > unicode/utf16 > container/list > runtime > crypto/internal/subtle > vendor/golang_org/x/crypto/cryptobyte/asn1 > vendor/golang_org/x/net/dns/dnsmessage > internal/nettrace > runtime/cgo > strconv > vendor/golang_org/x/crypto/curve25519 > crypto/rc4 > sync > io > math/rand > reflect > syscall > internal/singleflight > bytes > strings > bufio > hash > hash/crc32 > crypto/cipher > crypto > crypto/internal/randutil > crypto/sha512 > time > internal/syscall/unix > crypto/aes > crypto/hmac > crypto/md5 > crypto/sha1 > crypto/sha256 > vendor/golang_org/x/text/transform > path > html > github.com/mattn/go-isatty > internal/poll > encoding/binary > sort > os > regexp/syntax > encoding/base64 > crypto/des > vendor/golang_org/x/crypto/internal/chacha20 > encoding/pem > vendor/golang_org/x/crypto/poly1305 > path/filepath > fmt > vendor/golang_org/x/crypto/chacha20poly1305 > io/ioutil > regexp > compress/flate > encoding/xml > encoding/json > context > math/big > compress/gzip > encoding/hex > net > net/url > log > vendor/golang_org/x/text/unicode/bidi > vendor/golang_org/x/text/unicode/norm > vendor/golang_org/x/text/secure/bidirule > vendor/golang_org/x/net/http2/hpack > mime > crypto/rand > crypto/elliptic > encoding/asn1 > crypto/rsa > crypto/dsa > vendor/golang_org/x/net/idna > mime/quotedprintable > net/http/internal > crypto/ecdsa > crypto/x509/pkix > vendor/golang_org/x/crypto/cryptobyte > github.com/gin-gonic/gin/json > github.com/golang/protobuf/proto > encoding/gob > text/template/parse > text/template > gopkg.in/yaml.v2 > html/template > crypto/x509 > net/textproto > vendor/golang_org/x/net/http/httpproxy > gopkg.in/go-playground/validator.v8 > vendor/golang_org/x/net/http/httpguts > mime/multipart > crypto/tls > net/http/httptrace > net/http > github.com/gin-contrib/sse > net/rpc > net/http/httputil > github.com/ugorji/go/codec > github.com/gin-gonic/gin/binding > github.com/gin-gonic/gin/render > github.com/gin-gonic/gin > github.com/gin-gonic/gin/ginS >dh_auto_test -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 > github.com/gin-gonic/gin github.com/gin-gonic/gin/binding > github.com/gin-gonic/gin/ginS github.com/gin-gonic/gin/json > github.com/gin-gonic/gin/render > === RUN TestBasicAuth > --- PASS: TestBasicAuth (0.00s) > === RUN TestBasicAuthFails > --- PASS: TestBasicAuthFails (0.00s) > === RUN TestBasicAuthSearchCredential > --- PASS: TestBasicAuthSearchCredential (0.00s) > === RUN TestBasicAuthAuthorizationHeader > --- PASS: TestBasicAuthAuthorizationHeader (0.00s) > === RUN TestBasicAuthSecureCompare > --- PASS: TestBasicAuthSecureCompare (0.00s) > === RUN TestBasicAuthSucceed > --- PASS: TestBasicAuthSucceed (0.00s) > === RUN TestBasicAuth401 > --- PASS: TestBasicAuth401 (0.00s) > === RUN TestBasicAuth401WithCustomRealm > --- PASS: TestBasicAuth401WithCustomRealm (0.00s) > === RUN TestContextFormFile > --- PASS: TestContextFormFile (0.00s) > === RUN TestContextMultipartForm > --- PASS: TestContextMultipartForm (0.00s) > === RUN TestSaveUploadedOpenFailed > --- PASS: TestSaveUploadedOpenFailed (0.00s) > === RUN TestSaveUploadedCreateFailed > --- PASS: TestSaveUploadedCreateFailed
Bug#929719: gucharmap: FTBFS: unsatisfiable build-dependency: unicode-data (< 11.1) but 12.1.0~pre1-2 is to be installed
Source: gucharmap Version: 1:11.0.3-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190529 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster 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: debhelper-compat (= 12), desktop-file-utils, > gobject-introspection (>= 1.0.0), valac (>= 0.24.0-2~), > libgirepository1.0-dev (>= 0.9.0), libgtk-3-dev (>= 3.4.0), libglib2.0-dev > (>= 2.32.0), libpopt-dev, gnome-pkg-tools, gtk-doc-tools (>= 1.0), > yelp-tools, intltool (>= 0.40), libglib2.0-doc, libpango1.0-doc, > libgtk-3-doc, unicode-data (>= 11.0), unicode-data (<< 11.1) > Filtered Build-Depends: debhelper-compat (= 12), desktop-file-utils, > gobject-introspection (>= 1.0.0), valac (>= 0.24.0-2~), > libgirepository1.0-dev (>= 0.9.0), libgtk-3-dev (>= 3.4.0), libglib2.0-dev > (>= 2.32.0), libpopt-dev, gnome-pkg-tools, gtk-doc-tools (>= 1.0), > yelp-tools, intltool (>= 0.40), libglib2.0-doc, libpango1.0-doc, > libgtk-3-doc, unicode-data (>= 11.0), unicode-data (<< 11.1) > dpkg-deb: building package 'sbuild-build-depends-gucharmap-dummy' in > '/<>/resolver-RxwaiM/apt_archive/sbuild-build-depends-gucharmap-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-gucharmap-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-RxwaiM/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-RxwaiM/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-RxwaiM/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-RxwaiM/apt_archive ./ Sources [655 B] > Get:5 copy:/<>/resolver-RxwaiM/apt_archive ./ Packages [742 B] > Fetched 2360 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install gucharmap 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-gucharmap-dummy : Depends: unicode-data (< 11.1) but > 12.1.0~pre1-2 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://qa-logs.debian.net/2019/05/29/gucharmap_11.0.3-2_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#929720: hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require coroutines
Source: hkl Version: 5.0.0.2456-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190529 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o generator/generator.lo generator/generator.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I../.. -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c noerr/noerr.c > -fPIC -DPIC -o noerr/.libs/noerr.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I../.. -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c str/str.c -fPIC > -DPIC -o str/.libs/str.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I../.. -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c > generator/generator.c -fPIC -DPIC -o generator/.libs/generator.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I../.. -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c str/debug.c > -fPIC -DPIC -o str/.libs/debug.o > In file included from generator/generator.c:8: > ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require > coroutines > #error Generators require coroutines > ^ > make[5]: *** [Makefile:605: generator/generator.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2019/05/29/hkl_5.0.0.2456-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#929717: golang-fsnotify: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/fsnotify/fsnotify returned exit code 1
Source: golang-fsnotify Version: 1.4.7-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190529 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install > -gcflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" > -asmflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 4 > github.com/fsnotify/fsnotify > internal/race > errors > internal/cpu > runtime/internal/atomic > runtime/internal/sys > sync/atomic > unicode > unicode/utf8 > internal/testlog > internal/bytealg > math > math/bits > runtime > vendor/golang_org/x/net/dns/dnsmessage > internal/nettrace > runtime/cgo > strconv > sync > internal/singleflight > io > reflect > syscall > math/rand > bytes > strings > internal/syscall/unix > time > internal/poll > encoding/binary > sort > os > path/filepath > fmt > context > net > golang.org/x/sys/unix > github.com/fsnotify/fsnotify >dh_auto_test -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 > github.com/fsnotify/fsnotify > === RUN TestEventStringWithValue > --- PASS: TestEventStringWithValue (0.00s) > === RUN TestEventOpStringWithValue > --- PASS: TestEventOpStringWithValue (0.00s) > === RUN TestEventOpStringWithNoValue > --- PASS: TestEventOpStringWithNoValue (0.00s) > === RUN TestWatcherClose > === PAUSE TestWatcherClose > === RUN TestPollerWithBadFd > --- PASS: TestPollerWithBadFd (0.00s) > === RUN TestPollerWithData > --- PASS: TestPollerWithData (0.00s) > === RUN TestPollerWithWakeup > --- PASS: TestPollerWithWakeup (0.00s) > === RUN TestPollerWithClose > --- PASS: TestPollerWithClose (0.00s) > === RUN TestPollerWithWakeupAndData > --- PASS: TestPollerWithWakeupAndData (0.00s) > === RUN TestPollerConcurrent > --- PASS: TestPollerConcurrent (0.15s) > === RUN TestInotifyCloseRightAway > --- PASS: TestInotifyCloseRightAway (0.05s) > === RUN TestInotifyCloseSlightlyLater > --- PASS: TestInotifyCloseSlightlyLater (0.10s) > === RUN TestInotifyCloseSlightlyLaterWithWatch > --- PASS: TestInotifyCloseSlightlyLaterWithWatch (0.10s) > === RUN TestInotifyCloseAfterRead > --- PASS: TestInotifyCloseAfterRead (0.10s) > === RUN TestInotifyCloseCreate > --- PASS: TestInotifyCloseCreate (0.05s) > === RUN TestInotifyStress > --- PASS: TestInotifyStress (0.14s) > === RUN TestInotifyRemoveTwice > --- PASS: TestInotifyRemoveTwice (0.00s) > === RUN TestInotifyInnerMapLength > --- PASS: TestInotifyInnerMapLength (0.05s) > === RUN TestInotifyOverflow > --- FAIL: TestInotifyOverflow (4.69s) > inotify_test.go:442: Could not trigger overflow > === RUN TestFsnotifyMultipleOperations > --- PASS: TestFsnotifyMultipleOperations (0.67s) > integration_test.go:104: event received: > "/tmp/fsnotify244767993/TestFsnotifySeq.testfile": CREATE > integration_test.go:104: event received: > "/tmp/fsnotify244767993/TestFsnotifySeq.testfile": WRITE > integration_test.go:104: event received: > "/tmp/fsnotify244767993/TestFsnotifySeq.testfile": RENAME > integration_test.go:104: event received: > "/tmp/fsnotify244767993/TestFsnotifySeq.testfile": CREATE > integration_test.go:180: calling Close() > integration_test.go:182: waiting for the event channel to become closed... > integration_test.go:185: event channel closed > === RUN TestFsnotifyMultipleCreates > --- PASS: TestFsnotifyMultipleCreates (0.80s) > integration_test.go:217: event received: > "/tmp/fsnotify693647763/TestFsnotifySeq.testfile": CREATE > integration_test.go:217: event received: > "/tmp/fsnotify693647763/TestFsnotifySeq.testfile": WRITE > integration_test.go:217: event received: > "/tmp/fsnotify693647763/TestFsnotifySeq.testfile": REMOVE > integration_test.go:217: event received: > "/tmp/fsnotify693647763/TestFsnotifySeq.testfile": CREATE > integration_test.go:217: event received: > "/tmp/fsnotify693647763/TestFsnotifySeq.testfile": WRITE > integration_test.go:217: event received: > "/tmp/fsnotify693647763/TestFsnotifySeq.testfile": WRITE > integration_tes
Bug#929715: strace: FTBFS: open: /dev/kvm: No such file or directory
Source: strace Version: 4.26-0.2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190529 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[8]: Entering directory '/<>/build-udeb/tests-m32' > make[8]: Nothing to be done for 'all-am'. > make[8]: Leaving directory '/<>/build-udeb/tests-m32' > make[7]: Leaving directory '/<>/build-udeb/tests-m32' > === >strace 4.26: tests-m32/test-suite.log > === > > # TOTAL: 631 > # PASS: 589 > # SKIP: 38 > # XFAIL: 0 > # FAIL: 4 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > SKIP: bpf-obj_get_info_by_fd.gen > > > + ../strace -V > + TIMEOUT=timeout -k 5 -s XCPU 600 > + timeout -k 5 -s XCPU 600 true > + [ 1 -eq 0 ] > + exec timeout -k 5 -s XCPU 600 > ../../tests-m32/bpf-obj_get_info_by_fd.gen.test > + run_strace_match_diff -a20 -y -e trace=bpf > + args=-a20 -y -e trace=bpf > + [ -n -a20 -y -e trace=bpf -a -z ] > + run_prog > + [ 0 -eq 0 ] > + set -- ../bpf-obj_get_info_by_fd > + args=../bpf-obj_get_info_by_fd > + ../bpf-obj_get_info_by_fd > BPF_OBJ_GET_INFO_BY_FD map failed: Invalid argument > + rc=77 > + [ 77 -eq 77 ] > + skip_ ../bpf-obj_get_info_by_fd exited with code 77 > + warn_ bpf-obj_get_info_by_fd.gen.test: skipped test: > ../bpf-obj_get_info_by_fd exited with code 77 > + printf %s\n bpf-obj_get_info_by_fd.gen.test: skipped test: > ../bpf-obj_get_info_by_fd exited with code 77 > bpf-obj_get_info_by_fd.gen.test: skipped test: ../bpf-obj_get_info_by_fd > exited with code 77 > + exit 77 > > SKIP: bpf-obj_get_info_by_fd-v.gen > == > > + ../strace -V > + TIMEOUT=timeout -k 5 -s XCPU 600 > + timeout -k 5 -s XCPU 600 true > + [ 1 -eq 0 ] > + exec timeout -k 5 -s XCPU 600 > ../../tests-m32/bpf-obj_get_info_by_fd-v.gen.test > + run_strace_match_diff -a20 -y -v -e trace=bpf > + args=-a20 -y -v -e trace=bpf > + [ -n -a20 -y -v -e trace=bpf -a -z ] > + run_prog > + [ 0 -eq 0 ] > + set -- ../bpf-obj_get_info_by_fd-v > + args=../bpf-obj_get_info_by_fd-v > + ../bpf-obj_get_info_by_fd-v > BPF_OBJ_GET_INFO_BY_FD map failed: Invalid argument > + rc=77 > + [ 77 -eq 77 ] > + skip_ ../bpf-obj_get_info_by_fd-v exited with code 77 > + warn_ bpf-obj_get_info_by_fd-v.gen.test: skipped test: > ../bpf-obj_get_info_by_fd-v exited with code 77 > + printf %s\n bpf-obj_get_info_by_fd-v.gen.test: skipped test: > ../bpf-obj_get_info_by_fd-v exited with code 77 > bpf-obj_get_info_by_fd-v.gen.test: skipped test: ../bpf-obj_get_info_by_fd-v > exited with code 77 > + exit 77 > > SKIP: bpf-obj_get_info_by_fd-prog.gen > = > > + ../strace -V > + TIMEOUT=timeout -k 5 -s XCPU 600 > + timeout -k 5 -s XCPU 600 true > + [ 1 -eq 0 ] > + exec timeout -k 5 -s XCPU 600 > ../../tests-m32/bpf-obj_get_info_by_fd-prog.gen.test > + run_strace_match_diff -a20 -y -e trace=bpf > + args=-a20 -y -e trace=bpf > + [ -n -a20 -y -e trace=bpf -a -z ] > + run_prog > + [ 0 -eq 0 ] > + set -- ../bpf-obj_get_info_by_fd-prog > + args=../bpf-obj_get_info_by_fd-prog > + ../bpf-obj_get_info_by_fd-prog > BPF_OBJ_GET_INFO_BY_FD map failed: Invalid argument > + rc=77 > + [ 77 -eq 77 ] > + skip_ ../bpf-obj_get_info_by_fd-prog exited with code 77 > + warn_ bpf-obj_get_info_by_fd-prog.gen.test: skipped test: > ../bpf-obj_get_info_by_fd-prog exited with code 77 > + printf %s\n bpf-obj_get_info_by_fd-prog.gen.test: skipped test: > ../bpf-obj_get_info_by_fd-prog exited with code 77 > bpf-obj_get_info_by_fd-prog.gen.test: skipped test: > ../bpf-obj_get_info_by_fd-prog exited with code 77 > + exit 77 > > SKIP: bpf-obj_get_info_by_fd-prog-v.gen > === > > + ../strace -V > + TIMEOUT=timeout -k 5 -s XCPU 600 > + timeout -k 5 -s XCPU 600 true > + [ 1 -eq 0 ] > + exec timeout -k 5 -s XCPU 600 > ../../tests-m32/bpf-obj_get_info_by_fd-prog-v.gen.test > + run_strace_match_diff -a20 -y -v -e trace=bpf > + args=-a20 -y -v -e trace=bpf > + [ -n -a20 -y -v -e trace=bpf -a -z ] > + run_prog > + [ 0 -eq 0 ] > + set -- ../bpf-obj_get_info_by_fd-prog-v > + args=../bpf-obj_get_info_by_fd-prog-v > + ../bpf-obj_get_info_by_fd-prog-v > BPF_OBJ_GET_INFO_BY_FD map failed: Invalid argument > + rc=77 > + [ 77 -eq 77 ] > + skip_ ../bpf-obj_get_info_by_fd-prog-v exited with code 77 > + warn_ bpf-obj_get_info_by_fd-prog-v.gen.t
Bug#929713: openhft-chronicle-bytes: FTBFS: [ERROR] /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[78,48] cannot find symbol
Source: openhft-chronicle-bytes Version: 1.1.15-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190529 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibopenhft-chronicle-bytes-java --debian-build > --keep-pom-version --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] < net.openhft:chronicle-bytes > >- > [INFO] Building OpenHFT/Chronicle-Bytes 1.1.15 > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > chronicle-bytes --- > [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] skip non existing resourceDirectory /<>/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ > chronicle-bytes --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 52 source files to /<>/target/classes > [INFO] > /<>/src/main/java/net/openhft/chronicle/bytes/MappedBytes.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/net/openhft/chronicle/bytes/MappedBytes.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [WARNING] COMPILATION WARNING : > [INFO] - > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java:[23,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[27,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[23,16] > sun.misc.Unsafe is internal proprietary API and may be removed in a future > release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[24,18] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java:[42,76] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[142,22] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[144,21] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[426,33] > sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a > future release > [WARNING] > /<>/src/main/java/net/openhft/chronicle/bytes/VanillaBytes.java:[263,58] > appendUTF(long,char[],int,int)
Bug#929714: python-acora: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
Source: python-acora Version: 2.2-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190529 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm -f acora/_acora.c acora/_cacora.c > dh_auto_clean > I: pybuild base:217: python2.7 setup.py clean > WARNING: Generated .c files are missing, enabling Cython compilation > Building with Cython 0.29.2 > Compiling acora/_acora.py because it changed. > Compiling acora/_cacora.pyx because it changed. > [1/2] Cythonizing acora/_acora.py > [2/2] Cythonizing acora/_cacora.pyx > running clean > removing '/<>/.pybuild/cpython2_2.7_acora/build' (and everything > under it) > 'build/bdist.linux-amd64' does not exist -- can't clean it > 'build/scripts-2.7' does not exist -- can't clean it > I: pybuild base:217: python3.7 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.7_acora/build' (and everything > under it) > 'build/bdist.linux-amd64' does not exist -- can't clean it > 'build/scripts-3.7' does not exist -- can't clean it > make[1]: Leaving directory '/<>' >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building python-acora using existing > ./python-acora_2.2.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > python-acora-2.2/acora/_acora.c > python-acora-2.2/acora/_acora.html > python-acora-2.2/acora/_cacora.c > python-acora-2.2/acora/_cacora.html > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/python-acora_2.2-1.diff.VWSw_l > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2019-05-29T05:05:39Z The full build log is available from: http://qa-logs.debian.net/2019/05/29/python-acora_2.2-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#929709: libgdbm6: file exists in libgdbm-dev as well as gdbm
Package: libgdbm6 Version: 1.18.1-4 Severity: serious Justification: 2 Unpacking libgdbm-dev:amd64 (1.18.1-4) ... dpkg: error processing archive /var/cache/apt/archives/libgdbm-dev_1.18.1-4_amd64.deb (--unpack): trying to overwrite '/usr/share/info/gdbm.info.gz', which is also in package libgdbm3:amd64 1.8.3-11 Errors were encountered while processing: /var/cache/apt/archives/libgdbm-dev_1.18.1-4_amd64.deb -- System Information: Debian Release: 8.1 APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgdbm6 depends on: ii libc6 2.28-2 libgdbm6 recommends no packages. Versions of packages libgdbm6 suggests: pn gdbm-l10n -- no debconf information
Bug#929710: libopenzwave1.6-dev: missing Breaks+Replaces: libopenzwave1.5-dev
Package: libopenzwave1.6-dev Version: 1.6+ds-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libopenzwave1.6-dev_1.6+ds-1_amd64.deb ... Unpacking libopenzwave1.6-dev (1.6+ds-1) ... dpkg: error processing archive /var/cache/apt/archives/libopenzwave1.6-dev_1.6+ds-1_amd64.deb (--unpack): trying to overwrite '/usr/include/openzwave/Bitfield.h', which is also in package libopenzwave1.5-dev 1.5+ds-6 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libopenzwave1.6-dev_1.6+ds-1_amd64.deb cheers, Andreas libopenzwave1.5-dev=1.5+ds-6_libopenzwave1.6-dev=1.6+ds-1.log.gz Description: application/gzip
Bug#866758: Additional information kernel 4.9.0-4-amd64
Hi, https://bugs.debian.org/866758 is still open, is there any additional information for it? If not, I'll suggest you to close it. On Mon, 11 Dec 2017 02:20:56 -0600 "Roger T. Imai" wrote: > In further testing, I found that I am able to boot into X11/Gnome3 if I > revert to booting Linux kernel 4.9.0-*3*-amd64. I will continue with > 4.9.0-3-amd64 until the next amd64-related update. > > I am an intermediate user with no programming knowledge, but somewhat > familiar with the command line and file paths. Please feel free to send > instructions for extracting additional diagnostic information as needed. > I'm also willing to install additional debug tools as required. Thanks for > your attention. > > Attachment: If helpful, full hardware list for my notebook, an obscure HP > model sold to college engineering schools, probably with older components > than the commercial models. > > Roger T. Imai > Franklin (Nashville) TN -- Hideki Yamane
Bug#929697: pyglet: FTBFS randomly because of timing tests
Package: src:pyglet Version: 1.3.0-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions test -x debian/rules mkdir -p "." CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85 mkdir -p debian/python-module-stampdir cd . && python setup.py build --build-base="/<>/./build" running build running build_py creating /<>/build creating /<>/build/lib.linux-x86_64-2.7 creating /<>/build/lib.linux-x86_64-2.7/pyglet copying pyglet/lib.py -> /<>/./build/lib.linux-x86_64-2.7/pyglet [... snipped ...] copying _build/lib.linux-x86_64-2.7/pyglet/app/xlib.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app copying _build/lib.linux-x86_64-2.7/pyglet/app/win32.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app copying _build/lib.linux-x86_64-2.7/pyglet/app/__init__.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app copying _build/lib.linux-x86_64-2.7/pyglet/info.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet copying _build/lib.linux-x86_64-2.7/pyglet/compat.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet creating /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/base.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/carbon.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib_wgl.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glext_nv.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/cocoa.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_arb.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib_glx.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/wglext_arb.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_nv.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/xlib.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glx.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/wglext_nv.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glx_info.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glu.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glext_arb.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/wgl.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/win32.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/__init__.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_mesa.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/gl.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/gl_info.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/glu_info.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/agl.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib_agl.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl copying _build/lib.linux-x86_64-2.7/pyglet/gl/wgl_info.py -> /<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl running install_egg_info running egg_info writing pyglet.egg-info/PKG-INFO writing top-level names to pyglet.egg-info/top_level.txt writing
Bug#929527: [pkg-netfilter-team] Bug#929527: /usr/sbin/xtables-nft-multi: restoring IP Tables with an self-defined chain segfaults in libnftnl.so
On 5/28/19 11:26 AM, Arturo Borrero Gonzalez wrote: > On 5/27/19 12:29 PM, Arturo Borrero Gonzalez wrote: >> On 5/25/19 6:49 PM, Thomas Lamprecht wrote: >>> Package: iptables >>> Version: 1.8.2-4 >>> Severity: grave >>> File: /usr/sbin/xtables-nft-multi >>> Justification: renders package unusable by segfaulting on usage >>> >>> Reproducer: >>> # cat simple-segv-table >>> *filter >>> :NEW-OUTPUT - [0:0] >>> -A OUTPUT -j NEW-OUTPUT >>> -F NEW-OUTPUT >>> -A NEW-OUTPUT -j ACCEPT >>> COMMIT >>> >>> # iptables ./simple-segv-table >>> Segmentation fault >>> >>> # dmesg | tail -1 >>> [12860.813350] traps: iptables-restor[19173] general protection >>> ip:7f4894682793 sp:7ffcedc177d0 error:0 in >>> libnftnl.so.11.0.0[7f4894677000+17000] >>> >>> # addr2line -e /usr/lib/x86_64-linux-gnu/libnftnl.so.11.0.0 -fCi $(printf >>> "%x" $[0x7f2cb9882793 - 0x7f2cb9877000]) >>> nftnl_batch_is_supported >>> ??:? >>> >> >> I can reproduce this. >> >> I'm already looking for a fix. >> > > This should be fixed in iptables 1.8.3, which just got released. > Yes, I can confirm, it works again with iptables 1.8.3-1~exp1 and libnftnl 1.1.3-1~exp1. Much thanks for the quick response!
Processed: Re: CVE-2019-11502 CVE-2019-11503
Processing control commands: > tags -1 +fixed-upstream Bug #928052 [src:snapd] CVE-2019-11502 CVE-2019-11503 Added tag(s) fixed-upstream. -- 928052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928052: CVE-2019-11502 CVE-2019-11503
control: tags -1 +fixed-upstream On Fri, 26 Apr 2019 23:04:05 +0200 Moritz Muehlenhoff wrote: > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11502 It was fixed in upstream 2.38 https://github.com/snapcore/snapd/commit/bdbfeebef03245176ae0dc323392bb0522a339b1 > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11503 It was fixed in upstream 2.39 https://github.com/snapcore/snapd/commit/187893dee84e34ed40680217d2c3ce810985f97e -- Hideki Yamane
