Bug#966698: rasdaemon: fails to start by default under systemd due to EnvironmentFile=/etc/sysconfig/rasdaemon
Package: rasdaemon Version: 0.6.6-1 Severity: serious rasdaemon fails to start by default on Debian systemd based systems because the unit references an environment file that doesn't exist, since it is a path that is only used on RedHat not on Debian. Aug 02 13:07:15 systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory Aug 02 13:07:15 systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory Aug 02 13:07:15 systemd[1]: rasdaemon.service: Failed with result 'resources'. Aug 02 13:07:15 systemd[1]: Failed to start RAS daemon to log the RAS events. [Service] EnvironmentFile=/etc/sysconfig/rasdaemon -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rasdaemon depends on: ii init-system-helpers 1.58 ii libc62.31-2 ii libdbd-sqlite3-perl 1.64-1+b1 ii libsqlite3-0 3.32.3-1 ii perl 5.30.3-4 ii sqlite3 3.32.3-1 rasdaemon recommends no packages. rasdaemon suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#966696: emacs Segmentation fault
Package: libx11-6 Version: 2:1.6.10-1 Severity: critical $ emacs -Q Fatal error 11: Segmentation fault Backtrace: emacs[0x5111be] emacs[0x4f6ead] emacs[0x50f63e] emacs[0x50f86d] emacs[0x50f8e9] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14140)[0x7fb642ee6140] emacs[0x4d94b0] emacs[0x4d9897] emacs[0x4da4df] emacs[0x56dc2c] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x56f90b] emacs[0x56dc2c] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x570726] emacs[0x56fcc6] emacs[0x571c1c] emacs[0x56cd7e] emacs[0x4f8470] emacs[0x56cced] emacs[0x4f71f8] emacs[0x4fc2b3] emacs[0x4fc5f8] emacs[0x41a5c2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7fb642c06cca] emacs[0x41b29a] Segmentation fault # dpkg -i libx11-6_2%3a1.6.9-2+b1_amd64.deb dpkg: warning: downgrading libx11-6:amd64 from 2:1.6.10-1 to 2:1.6.9-2+b1 $ emacs -Q now works OK again. Versions of packages libx11-6:amd64 depends on: ii libc62.31-2 ii libx11-data 2:1.6.10-1 ii libxcb1 1.14-2
Processed: retitle 966289 to RM: python-pytc -- ROM; python2-only; no rdeps; extremely low popcon
Processing commands for cont...@bugs.debian.org: > retitle 966289 RM: python-pytc -- ROM; python2-only; no rdeps; extremely low > popcon Bug #966289 [python-pytc] python-pytc: should this package be removed? Changed Bug title to 'RM: python-pytc -- ROM; python2-only; no rdeps; extremely low popcon' from 'python-pytc: should this package be removed?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 966289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957242: marked as done (fuse-emulator: ftbfs with GCC-10)
Your message dated Sun, 02 Aug 2020 00:48:36 + with message-id and subject line Bug#957242: fixed in fuse-emulator 1.5.7+dfsg1-4 has caused the Debian Bug report #957242, regarding fuse-emulator: ftbfs with GCC-10 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.) -- 957242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fuse-emulator Version: 1.5.7+dfsg1-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/fuse-emulator_1.5.7+dfsg1-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -DFUSEDATADIR="\"/usr/share/fuse\"" -I/usr/include/libpng16 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DG_DISABLE_CAST_CHECKS -I/usr/include -Wall -Wwrite-strings -pthread -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o peripherals/disk/disk.o ../peripherals/disk/disk.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -DFUSEDATADIR="\"/usr/share/fuse\"" -I/usr/include/libpng16 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DG_DISABLE_CAST_CHECKS -I/usr/include -Wall -Wwrite-strings -pthread -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o peripherals/disk/fdd.o ../peripherals/disk/fdd.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -DFUSEDATADIR="\"/usr/share/fuse\"" -I/usr/include/libpng16 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DG_DISABLE_CAST_CHECKS -I/usr/include -Wall -Wwrite-strings -pthread -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o peripherals/disk/opus.o ../peripherals/disk/opus.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -DFUSEDATADIR="\"/usr/share/fuse\"" -I/usr/include/libpng16 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DG_DISABLE_CAST_CHECKS -I/usr/include -Wall -Wwrite-strings -pthread -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o peripherals/disk/plusd.o ../peripherals/disk/plusd.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -DFUSEDATADIR="\"/usr/share/fuse\"" -I/usr/include/libpng16 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DG_DISABLE_CAST_CHECKS -I/usr/include -Wall -Wwrite-strings -pthread -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o peripherals/disk/trdos.o ../peripherals/disk/trdos.c gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -DFUSEDATADIR="\"/usr/share/fuse\"" -I/usr/include/libpng16 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DG_DISABLE_CAST_CHECKS -I/usr/include -Wall -Wwrite-strings -pthread -g -O2 -fdebug-prefix-map=/<>=.
Bug#957834: marked as done (sphinxbase: ftbfs with GCC-10)
Your message dated Sun, 02 Aug 2020 00:19:24 + with message-id and subject line Bug#957834: fixed in sphinxbase 0.8+5prealpha+1-11 has caused the Debian Bug report #957834, regarding sphinxbase: ftbfs with GCC-10 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.) -- 957834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sphinxbase Version: 0.8+5prealpha+1-8 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/sphinxbase_0.8+5prealpha+1-8_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] libtool: link: gcc -I../../../../include/sphinxbase -I../../../../include -I../../../include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/test_log_int16 test_log_int16.o ../../../src/libsphinxbase/.libs/libsphinxbase.so -lpulse -lpulse-simple -lpthread -lm -lblas -llapack libtool: link: gcc -I../../../../include/sphinxbase -I../../../../include -I../../../include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/test_log_shifted test_log_shifted.o ../../../src/libsphinxbase/.libs/libsphinxbase.so -lpulse -lpulse-simple -lpthread -lm -lblas -llapack make[6]: Leaving directory '/<>/build-python3.8/test/unit/test_logmath' make check-TESTS make[6]: Entering directory '/<>/build-python3.8/test/unit/test_logmath' make[7]: Entering directory '/<>/build-python3.8/test/unit/test_logmath' PASS: test_log_int16 FAIL: test_log_shifted PASS: test_log_int8 = sphinxbase 5prealpha: test/unit/test_logmath/test-suite.log = # TOTAL: 3 # PASS: 2 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test_log_shifted == INFO: logmath.c(283): Writing log table file 'tmp.logadd' INFO: logmath.c(174): Reading log table file 'tmp.logadd' FAIL: abs((logmath_log(lmath, 1e-150)) - (-13493)) < LOG_EPSILON log(1e-150) = -13493 exp(log(1e-150)) = 9.843575e-151 log(1e-48) = -4318 exp(log(1e-48)) = 9.888735e-49 log(42) = 146 exp(log(42)) = 41.989229 log(1e-3 + 5e-3) = -270 l+ -207 = -200 log(1e-3 + 5e-3) = 9.961084e-04 + 4.996912e-03 = 5.977553e-03 log(1e-150) = -115301 FAIL test_log_shifted (exit status: 1) Testsuite summary for sphinxbase 5prealpha # TOTAL: 3 # PASS: 2 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See test/unit/test_logmath/test-suite.log make[7]: *** [Makefile:711: test-suite.log] Error 1 make[7]: Leaving directory '/<>/build-python3.8/test/unit/test_logmath' make[6]: *** [Makefile:819: check-TESTS] Error 2 make[6]: Leaving directory '/<>/build-python3.8/test/unit/test_logmath' make[5]: *** [Makefile:907: check-am] Error 2 make[5]: Leaving directory '/<>/build-python3.8/test/unit/test_logmath' make[4]: *** [Makefile:393: check-recursive] Error 1 make[4]: Leaving directory '/<>/build-python3.8/test/unit' make[3]: *** [Makefile:372: check-recursive] Error 1
Bug#957181: marked as done (espeak-ng: ftbfs with GCC-10)
Your message dated Sun, 02 Aug 2020 00:04:41 + with message-id and subject line Bug#957181: fixed in espeak-ng 1.50+dfsg-7 has caused the Debian Bug report #957181, regarding espeak-ng: ftbfs with GCC-10 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.) -- 957181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:espeak-ng Version: 1.50+dfsg-6 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/espeak-ng_1.50+dfsg-6_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -pedantic -fno-exceptions -D PATH_ESPEAK_DATA=\"/usr/lib/x86_64-linux-gnu/espeak-ng-data\" -DLIBESPEAK_NG_EXPORT -Isrc/include -Isrc/include/compat -I src/ucd-tools/src/include -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200112L -Wno-endif-labels -DINCLUDE_KLATT -DINCLUDE_MBROLA -DUSE_ASYNC -Wunused-parameter -Wunused -Wuninitialized -Wreturn-type -Wmissing-prototypes -Wimplicit -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -c src/libespeak-ng/translate.c -fPIC -DPIC -o src/libespeak-ng/.libs/la-translate.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -pedantic -fno-exceptions -D PATH_ESPEAK_DATA=\"/usr/lib/x86_64-linux-gnu/espeak-ng-data\" -DLIBESPEAK_NG_EXPORT -Isrc/include -Isrc/include/compat -I src/ucd-tools/src/include -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200112L -Wno-endif-labels -DINCLUDE_KLATT -DINCLUDE_MBROLA -DUSE_ASYNC -Wunused-parameter -Wunused -Wuninitialized -Wreturn-type -Wmissing-prototypes -Wimplicit -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -c src/libespeak-ng/translate.c -o src/libespeak-ng/la-translate.o >/dev/null 2>&1 /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -pedantic -fno-exceptions -D PATH_ESPEAK_DATA=\"/usr/lib/x86_64-linux-gnu/espeak-ng-data\" -DLIBESPEAK_NG_EXPORT -Isrc/include -Isrc/include/compat -I src/ucd-tools/src/include -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200112L -Wno-endif-labels -DINCLUDE_KLATT -DINCLUDE_MBROLA -DUSE_ASYNC -Wunused-parameter -Wunused -Wuninitialized -Wreturn-type -Wmissing-prototypes -Wimplicit -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -c -o src/libespeak-ng/la-tr_languages.lo `test -f 'src/libespeak-ng/tr_languages.c' || echo './'`src/libespeak-ng/tr_languages.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -pedantic -fno-exceptions -D PATH_ESPEAK_DATA=\"/usr/lib/x86_64-linux-gnu/espeak-ng-data\" -DLIBESPEAK_NG_EXPORT -Isrc/include -Isrc/include/compat -I src/ucd-tools/src/include -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200112L -Wno-endif-labels -DINCLUDE_KLATT -DINCLUDE_MBROLA -DUSE_ASYNC -Wunused-parameter -Wunused -Wuninitialized -Wreturn-type -Wmissing-prototypes -Wimplicit -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -c src/libespeak-ng/tr_languages.c -fPIC -DPIC -o src/libespeak-ng/.libs/la-tr_languages.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
Bug#966692: stunnel4: FTBFS because of test hang
Source: stunnel4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: Michał Mirosław
The bug #955710 turns out to be only partially fixed. Now without a binary
to exec the test runtime doesn't hang. When the binary is correct, though,
it still can't stop asking the pipe for more data after EOF.
$ dpkg-buildpackage -b
[...]
env TEST_STUNNEL=.../stunnel4-5.56+dfsg/src/stunnel debian/tests/runtime
Found the certificate at debian/tests/certs/certificate.pem and the private key
at debian/tests/certs/key.pem
Using the /tmp/AgCSdk8YKw temporary directory
About to get the stunnel version information
Got stunnel version 5.56
^Cmake[1]: *** [debian/rules:32: execute_before_dh_auto_test] Interrupt
make: *** [debian/rules:106: binary] Error 1
From the manual run under strace:
$ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime
I can see (excerpt):
11715 read(5,
11715 <... read resumed> "stunnel 5.56 on x86_64-pc-linux-"..., 8192) = 95
[more reads]
11715 read(5, "TIMEOUTbusy= 300 sec"..., 8192) = 178
11715 epoll_wait(3,
11715 <... epoll_wait resumed> [{EPOLLHUP, {u32=5, u64=4294967301}}], 64,
59743) = 1
11715 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}
[11716 +++ exited with 0 +++]
11715 <... epoll_ctl resumed> ) = 0
11715 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=11716,
si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
11715 write(4, "\1\0\0\0\0\0\0\0", 8) = 8
11715 rt_sigreturn({mask=[]}) = 0
11715 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}, {EPOLLIN, {u32=4,
u64=4294967300}}], 64, 59743) = 2
11715 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0
11715 read(4, "\1\0\0\0\0\0\0\0", 8)= 8
11715 wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}],
WNOHANG|WSTOPPED|WCONTINUED, NULL) = 11716
11715 wait4(-1, 0x7ffc665c7904, WNOHANG|WSTOPPED|WCONTINUED, NULL) = -1 ECHILD
(No child processes)
11715 wait4(-1, 0x7ffc665c76b4, WNOHANG, NULL) = -1 ECHILD (No child processes)
11715 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1
11715 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0
11715 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1
11715 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0
11715 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1
11715 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0
11715 read(5, "", 8192) = 0
11715 write(1, "Got stunnel version 5.56\n", 25) = 25
11715 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1
11715 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0
11715 read(5, "", 8192) = 0
[last 3 lines repeated forever]
-- System Information:
Debian Release: 10.5
APT prefers stable-debug
APT policy: (900, 'stable-debug'), (900, 'proposed-updates'), (900,
'stable'), (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (540,
'oldstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'proposed-updates-debug'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.10mq+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
test-runtime.strace.log.gz
Description: application/gzip
Bug#966301: guile oom test fails on ppc64el
Matthias Klose writes: > https://buildd.debian.org/status/fetch.php?pkg=guile-2.2=ppc64el=2.2.7%2B1-5.1=1595497537=0 > > Apparently this is known, and already reported by Debian: > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=+29464 > but no update since 2017. > > For some reason the test succeeds on the Ubuntu buildds. I believe we originally avoided this via # https://debbugs.gnu.org/29464 export DEB_CFLAGS_MAINT_APPEND += -fno-stack-protector in debian/rules. I wonder if that doesn't avoid the problem anymore, or somehow the option's no longer making it all the way through. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Processed: tagging 957827, bug 957827 is forwarded to https://github.com/FreeSpacenav/spacenavd/issues/17
Processing commands for cont...@bugs.debian.org: > tags 957827 + fixed-upstream Bug #957827 [src:spacenavd] spacenavd: ftbfs with GCC-10 Added tag(s) fixed-upstream. > forwarded 957827 https://github.com/FreeSpacenav/spacenavd/issues/17 Bug #957827 [src:spacenavd] spacenavd: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://github.com/FreeSpacenav/spacenavd/issues/17'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 957829 is forwarded to https://github.com/IgnorantGuru/spacefm/issues/770
Processing commands for cont...@bugs.debian.org: > forwarded 957829 https://github.com/IgnorantGuru/spacefm/issues/770 Bug #957829 [src:spacefm] spacefm: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://github.com/IgnorantGuru/spacefm/issues/770'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 957853, bug 957853 is forwarded to https://github.com/baskerville/sxhkd/issues/189
Processing commands for cont...@bugs.debian.org: > tags 957853 + fixed-upstream Bug #957853 [src:sxhkd] sxhkd: ftbfs with GCC-10 Added tag(s) fixed-upstream. > forwarded 957853 https://github.com/baskerville/sxhkd/issues/189 Bug #957853 [src:sxhkd] sxhkd: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://github.com/baskerville/sxhkd/issues/189'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 957877
Processing commands for cont...@bugs.debian.org: > tags 957877 + fixed-upstream Bug #957877 [src:thinkfan] thinkfan: ftbfs with GCC-10 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 957877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 957891, bug 957891 is forwarded to https://github.com/greatscottgadgets/ubertooth/pull/409
Processing commands for cont...@bugs.debian.org: > tags 957891 + fixed-upstream Bug #957891 [src:ubertooth] ubertooth: ftbfs with GCC-10 Added tag(s) fixed-upstream. > forwarded 957891 https://github.com/greatscottgadgets/ubertooth/pull/409 Bug #957891 [src:ubertooth] ubertooth: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://github.com/greatscottgadgets/ubertooth/pull/409'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957896: uget: ftbfs with GCC-10
Control: tags -1 + fixed-upstream Hi, this issue has been fixed in upstream commit: https://sourceforge.net/p/urlget/uget2/ci/14890943c52e0a5cd2a87d8a1c51cbffebee7cf9/ Regards, Reiner signature.asc Description: PGP signature
Processed: Re: uget: ftbfs with GCC-10
Processing control commands: > tags -1 + fixed-upstream Bug #957896 [src:uget] uget: ftbfs with GCC-10 Added tag(s) fixed-upstream. -- 957896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966691: emacs-gtk: Segmentation fault with libx11-6 v. 2:1.6.10-1
Package: emacs-gtk Version: 1:26.3+1-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Upgrade to v. 2:1.6.10-1 of libx11-6 (and related packages) * What was the outcome of this action? Segmentation fault of emacs-gtk: [1] 3915 Fatal error 11: Segmentation fault Backtrace: emacs-gtk[0x5111be] emacs-gtk[0x4f6ead] emacs-gtk[0x50f63e] emacs-gtk[0x50f86d] emacs-gtk[0x50f8e9] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14140)[0x7f3e63809140] emacs-gtk[0x4d94b0] emacs-gtk[0x4d9897] emacs-gtk[0x4da4df] emacs-gtk[0x56dc2c] emacs-gtk[0x5a74c0] emacs-gtk[0x56dbab] emacs-gtk[0x5a74c0] emacs-gtk[0x56dbab] emacs-gtk[0x56f90b] emacs-gtk[0x56dc2c] emacs-gtk[0x5a74c0] emacs-gtk[0x56dbab] emacs-gtk[0x5a74c0] emacs-gtk[0x56dbab] emacs-gtk[0x5a74c0] emacs-gtk[0x56dbab] emacs-gtk[0x5a74c0] emacs-gtk[0x56dbab] emacs-gtk[0x5a74c0] emacs-gtk[0x570726] emacs-gtk[0x56fcc6] emacs-gtk[0x571c1c] emacs-gtk[0x56cd7e] emacs-gtk[0x4f8470] emacs-gtk[0x56cced] emacs-gtk[0x4f71f8] emacs-gtk[0x4fc2b3] emacs-gtk[0x4fc5f8] emacs-gtk[0x41a5c2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7f3e63529cca] emacs-gtk[0x41b29a] [1]+ Doneexport LANG=C Segmentation fault Reverting libx11-6, libx11-data and libx11-xcb1 to previous version (2:1.6.9-2+b1) solves the issue. Best regards and thank you so much, Domenico -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs-gtk depends on: ii emacs-bin-common 1:26.3+1-2 ii emacs-common 1:26.3+1-2 ii libacl12.2.53-8 ii libasound2 1.2.2-2.3 ii libc6 2.31-2 ii libcairo2 1.16.0-4 ii libdbus-1-31.12.20-1 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.2+dfsg-3 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libgif75.1.9-1 ii libglib2.0-0 2.64.4-1 ii libgnutls303.6.14-2+b1 ii libgpm21.20.7-6 ii libgtk-3-0 3.24.20-1 ii libice62:1.0.9-2 ii libjpeg62-turbo1:2.0.5-1 ii liblcms2-2 2.9-4+b1 ii libm17n-0 1.8.0-2 ii libmagickcore-6.q16-6 8:6.9.11.24+dfsg-1 ii libmagickwand-6.q16-6 8:6.9.11.24+dfsg-1 ii libotf00.9.13-7 ii libpango-1.0-0 1.44.7-4 ii libpng16-161.6.37-2 ii librsvg2-2 2.48.7-1 ii libselinux13.1-2 ii libsm6 2:1.2.3-1 ii libsystemd0245.7-1 ii libtiff5 4.1.0+git191117-2 ii libtinfo6 6.2-1 ii libx11-6 2:1.6.10-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-2 ii libxft22.3.2-2 ii libxml22.9.10+dfsg-5+b1 ii libxpm41:3.5.12-1 ii libxrender11:0.9.10-1 ii zlib1g 1:1.2.11.dfsg-2 emacs-gtk recommends no packages. Versions of packages emacs-gtk suggests: pn emacs-common-non-dfsg -- no debconf information
Processed: tagging 957905, bug 957905 is forwarded to https://github.com/uTox/uTox/issues/1412
Processing commands for cont...@bugs.debian.org: > tags 957905 + fixed-upstream Bug #957905 [src:utox] utox: ftbfs with GCC-10 Added tag(s) fixed-upstream. > forwarded 957905 https://github.com/uTox/uTox/issues/1412 Bug #957905 [src:utox] utox: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://github.com/uTox/uTox/issues/1412'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957910: vifm: ftbfs with GCC-10
Control: tags -1 + fixed-upstream Hi, this issue has been fixed in upstream commit: https://github.com/vifm/vifm/commit/0205c8d76bd33228b33bcceb6afffa2a77925c76 Regards, Reiner signature.asc Description: PGP signature
Processed: Re: vifm: ftbfs with GCC-10
Processing control commands: > tags -1 + fixed-upstream Bug #957910 [src:vifm] vifm: ftbfs with GCC-10 Added tag(s) fixed-upstream. -- 957910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 957912 is forwarded to https://gitlab.gnome.org/GNOME/vinagre/-/merge_requests/8
Processing commands for cont...@bugs.debian.org: > forwarded 957912 https://gitlab.gnome.org/GNOME/vinagre/-/merge_requests/8 Bug #957912 [src:vinagre] vinagre: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/vinagre/-/merge_requests/8'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966419: marked as done (libjpeg-turbo: versions in debian/*.symbols files are missing the epochs)
Your message dated Sat, 01 Aug 2020 21:49:05 + with message-id and subject line Bug#966409: fixed in libjpeg-turbo 1:2.0.5-1.1 has caused the Debian Bug report #966409, regarding libjpeg-turbo: versions in debian/*.symbols files are missing the epochs 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.) -- 966409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjpeg-turbo Version: 1:2.0.5-1 Severity: serious The versions in the debian/*.symbols files are missing the epochs. This means that packages using symbols newer than buster will not upgrade libjpeg62-turbo and libturbojpeg0 when being upgraded to bullseye. For example if I install bullseye libjpeg-turbo-progs on buster, the programs will not work as libjpeg62-turbo and libturbojpeg0 will not be upgraded so the new symbols like jpeg_write_icc_profile are missing. $ rmadison -u debian libjpeg-turbo libjpeg-turbo | 1:1.3.1-12| oldoldstable | source libjpeg-turbo | 1:1.5.1-2 | oldstable | source libjpeg-turbo | 1:1.5.2-2 | stable | source libjpeg-turbo | 1:1.5.2-2 | testing| source libjpeg-turbo | 1:1.5.2-2 | unstable | source libjpeg-turbo | 1:1.5.2-2 | unstable-debug | source libjpeg-turbo | 1:2.0.5-1 | unstable | source libjpeg-turbo | 1:2.0.5-1 | unstable-debug | source $ grep -v 1.3.1 debian/*.symbols | grep -v 1.2.90 | grep -v 1.4.0 | grep -v 1.5.0 debian/libjpeg62-turbo.symbols:libjpeg.so.62 libjpeg62-turbo #MINVER# debian/libjpeg62-turbo.symbols:* Build-Depends-Package: libjpeg62-turbo-dev debian/libjpeg62-turbo.symbols: jpeg_read_icc_profile@LIBJPEG_6.2 2.0.2 debian/libjpeg62-turbo.symbols: jpeg_write_icc_profile@LIBJPEG_6.2 2.0.2 debian/libturbojpeg0.symbols:libturbojpeg.so.0 libturbojpeg0 #MINVER# debian/libturbojpeg0.symbols:* Build-Depends-Package: libturbojpeg0-dev debian/libturbojpeg0.symbols: TURBOJPEG_2.0@TURBOJPEG_2.0 2.0.2 debian/libturbojpeg0.symbols: tjGetErrorCode@TURBOJPEG_2.0 2.0.2 debian/libturbojpeg0.symbols: tjGetErrorStr2@TURBOJPEG_2.0 2.0.2 debian/libturbojpeg0.symbols: tjLoadImage@TURBOJPEG_2.0 2.0.2 debian/libturbojpeg0.symbols: tjSaveImage@TURBOJPEG_2.0 2.0.2 # cat /etc/apt/sources.list deb https://deb.debian.org/debian buster main # apt -qq install libjpeg-turbo-progs The following additional packages will be installed: libjpeg62-turbo libturbojpeg0 The following NEW packages will be installed: libjpeg-turbo-progs libjpeg62-turbo libturbojpeg0 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 266 kB/399 kB of archives. After this operation, 1275 kB of additional disk space will be used. Do you want to continue? [Y/n] debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libjpeg62-turbo:amd64. (Reading database ... 12518 files and directories currently installed.) Preparing to unpack .../libjpeg62-turbo_1%3a1.5.2-2+b1_amd64.deb ... Unpacking libjpeg62-turbo:amd64 (1:1.5.2-2+b1) ... Selecting previously unselected package libturbojpeg0:amd64. Preparing to unpack .../libturbojpeg0_1%3a1.5.2-2+b1_amd64.deb ... Unpacking libturbojpeg0:amd64 (1:1.5.2-2+b1) ... Selecting previously unselected package libjpeg-turbo-progs. Preparing to unpack .../libjpeg-turbo-progs_1%3a1.5.2-2+b1_amd64.deb ... Unpacking libjpeg-turbo-progs (1:1.5.2-2+b1) ... Setting up libturbojpeg0:amd64 (1:1.5.2-2+b1) ... Setting up libjpeg62-turbo:amd64 (1:1.5.2-2+b1) ... Setting up libjpeg-turbo-progs (1:1.5.2-2+b1) ... Processing triggers for libc-bin (2.28-10) ... # cat /etc/apt/sources.list | grep buster | sed s/buster/sid/ >> /etc/apt/sources.list # cat /etc/apt/sources.list deb https://deb.debian.org/debian buster main deb https://deb.debian.org/debian sid main # apt update Hit:1 https://deb.debian.org/debian buster InRelease Get:2 https://deb.debian.org/debian sid InRelease [146 kB] Get:3 https://deb.debian.org/debian sid/main amd64 Packages [8345 kB] Fetched 8491 kB in 6s (1365 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 126 packages can be upgraded. Run 'apt list --upgradable' to see them. # apt policy libjpeg-turbo-progs libjpeg-turbo-progs: Installed: 1:1.5.2-2+b1 Candidate: 1:2.0.5-1 Version table: 1:2.0.5-1 500 500 https://deb.debian.org/debian sid/main amd64
Bug#966421: marked as done (libjpeg-turbo FTBFS on alpha/mips64el/powerpc/sparc64: test failures)
Your message dated Sat, 01 Aug 2020 21:49:05 + with message-id and subject line Bug#966421: fixed in libjpeg-turbo 1:2.0.5-1.1 has caused the Debian Bug report #966421, regarding libjpeg-turbo FTBFS on alpha/mips64el/powerpc/sparc64: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjpeg-turbo Version: 1:2.0.2-1~exp1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/package.php?p=libjpeg-turbo ... 177/302 Test #83: djpeg-shared-3x2-float-prog-cmp ...***Failed 0.01 sec testout_3x2_float.ppm: FAILED. Checksum is f6bfab038438ed8f5522fbd33595dcdc ... 267/302 Test #234: djpeg-static-3x2-float-prog-cmp ...***Failed 0.01 sec testout_3x2_float.ppm: FAILED. Checksum is f6bfab038438ed8f5522fbd33595dcdc ... 99% tests passed, 2 tests failed out of 302 Total Test time (real) = 186.96 sec The following tests FAILED: 83 - djpeg-shared-3x2-float-prog-cmp (Failed) 234 - djpeg-static-3x2-float-prog-cmp (Failed) Errors while running CTest make[1]: *** [Makefile:121: test] Error 8 For determining the correct md5 of expected test results libjpeg-turbo wrongly guesses for some architectures. This is fixed by the first commit in https://salsa.debian.org/debian/libjpeg-turbo/-/merge_requests/2 --- End Message --- --- Begin Message --- Source: libjpeg-turbo Source-Version: 1:2.0.5-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of libjpeg-turbo, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated libjpeg-turbo 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: Fri, 31 Jul 2020 17:51:51 +0300 Source: libjpeg-turbo Architecture: source Version: 1:2.0.5-1.1 Distribution: unstable Urgency: medium Maintainer: Ondřej Surý Changed-By: Adrian Bunk Closes: 966409 966421 Changes: libjpeg-turbo (1:2.0.5-1.1) unstable; urgency=medium . [ Adrian Bunk ] * Non-maintainer upload. * Fix incorrect FLOATTEST guesses causing test failures. (Closes: #966421) * Add -ffloat-store only on m68k. * Add the missing epochs to symbols files, thanks to Paul Wise. (Closes: #966409) * Remove non-working Rules-Requires-Root. . [ Mike Gabriel ] * lintian: Renamed tag: shlib-calls-exit -> exit-in-shared-library. * debian/rules: Drop explicit setting of DEB_LDFLAGS_MAINT_APPEND. Checksums-Sha1: 14e79d35fd75ac98129034b59984a834322506e9 2298 libjpeg-turbo_2.0.5-1.1.dsc e9881711c29f5d432093775c1d882bd6cc58b687 87212 libjpeg-turbo_2.0.5-1.1.debian.tar.xz Checksums-Sha256: c591cf0cc7b1316f3247c873ad4fb7a1c8d3d049338dc5876006da67dd20dea3 2298 libjpeg-turbo_2.0.5-1.1.dsc d4370be8fabaef3be0007a75df92f964986f03d648c5f97cbeb750067f53a493 87212 libjpeg-turbo_2.0.5-1.1.debian.tar.xz Files: c6750e6679a5854e3757a91e319a6c5d 2298 graphics optional libjpeg-turbo_2.0.5-1.1.dsc f6b0387f69485730a51f04f9d92d3d3b 87212 graphics optional libjpeg-turbo_2.0.5-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8ly2EACgkQiNJCh6LY mLEmWBAAmpVFcNMZBBNqOerp7v3YLTLipd2Din835FNDzVybcgo6AQ/rItFBZhcS cn5Y9apgS+Bxd+MAxiSKQIGcgQgmObMC8Z78dkYXT6R8sIIiBWT5UDWyFNSh90/w GHqlRUA+SsLKYw+kYOj3cYB6GCRIu69PUOjgrxmpo2RJfgkU2cIHu9LL1FR4qTcO 4YLPldq89KrR1uFTr+3luZFvpCf+0jLYdSDiafgTBA4/a3280cM8zbNOEsX7AymQ 8HIepNSCm8GAw2EKA/Ki8ZWkPCiZ31U7s3P+sMQRxXRYi1mE+f1DAbCjRHnTVJfk PIvTzV7HuNxIAd0Hn60uwYiIzwNdsugXASEkZCkMT8AlLKtBYMI2GE8OtQyakx9b FWpspbARjHUgJU8F8++nItrx8EI4Giovt5GgE3RHysPU795oJa3RH+rperYAuG0B GifwUsVV6bSCZcIg9Pok2T7dtm7FW/exQfA0Og9ALOej59p+O/+C3D9bIBepUscV JS8vQy9D7wiq/iG6HY9mcMAgrfy0Uz47xCiA0zjVbriCGRle4dOw37xvNK5Qxqfk PBFZwmOrxdL7QOIBKu2lK70u3cv8/q/9YaJTBvsoRzHnXcwLO7T8MHW6m5eUENWa wrF+SJsj2yzy7uAo63hlTJsbM7vWePVLgClQUpM/i2GihzzXkvk= =UAKG -END PGP SIGNATURE End Message ---
Bug#966409: marked as done (libjpeg-turbo: versions in debian/*.symbols files are missing the epochs)
Your message dated Sat, 01 Aug 2020 21:49:05 + with message-id and subject line Bug#966409: fixed in libjpeg-turbo 1:2.0.5-1.1 has caused the Debian Bug report #966409, regarding libjpeg-turbo: versions in debian/*.symbols files are missing the epochs 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.) -- 966409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjpeg-turbo Version: 1:2.0.5-1 Severity: serious The versions in the debian/*.symbols files are missing the epochs. This means that packages using symbols newer than buster will not upgrade libjpeg62-turbo and libturbojpeg0 when being upgraded to bullseye. For example if I install bullseye libjpeg-turbo-progs on buster, the programs will not work as libjpeg62-turbo and libturbojpeg0 will not be upgraded so the new symbols like jpeg_write_icc_profile are missing. $ rmadison -u debian libjpeg-turbo libjpeg-turbo | 1:1.3.1-12| oldoldstable | source libjpeg-turbo | 1:1.5.1-2 | oldstable | source libjpeg-turbo | 1:1.5.2-2 | stable | source libjpeg-turbo | 1:1.5.2-2 | testing| source libjpeg-turbo | 1:1.5.2-2 | unstable | source libjpeg-turbo | 1:1.5.2-2 | unstable-debug | source libjpeg-turbo | 1:2.0.5-1 | unstable | source libjpeg-turbo | 1:2.0.5-1 | unstable-debug | source $ grep -v 1.3.1 debian/*.symbols | grep -v 1.2.90 | grep -v 1.4.0 | grep -v 1.5.0 debian/libjpeg62-turbo.symbols:libjpeg.so.62 libjpeg62-turbo #MINVER# debian/libjpeg62-turbo.symbols:* Build-Depends-Package: libjpeg62-turbo-dev debian/libjpeg62-turbo.symbols: jpeg_read_icc_profile@LIBJPEG_6.2 2.0.2 debian/libjpeg62-turbo.symbols: jpeg_write_icc_profile@LIBJPEG_6.2 2.0.2 debian/libturbojpeg0.symbols:libturbojpeg.so.0 libturbojpeg0 #MINVER# debian/libturbojpeg0.symbols:* Build-Depends-Package: libturbojpeg0-dev debian/libturbojpeg0.symbols: TURBOJPEG_2.0@TURBOJPEG_2.0 2.0.2 debian/libturbojpeg0.symbols: tjGetErrorCode@TURBOJPEG_2.0 2.0.2 debian/libturbojpeg0.symbols: tjGetErrorStr2@TURBOJPEG_2.0 2.0.2 debian/libturbojpeg0.symbols: tjLoadImage@TURBOJPEG_2.0 2.0.2 debian/libturbojpeg0.symbols: tjSaveImage@TURBOJPEG_2.0 2.0.2 # cat /etc/apt/sources.list deb https://deb.debian.org/debian buster main # apt -qq install libjpeg-turbo-progs The following additional packages will be installed: libjpeg62-turbo libturbojpeg0 The following NEW packages will be installed: libjpeg-turbo-progs libjpeg62-turbo libturbojpeg0 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 266 kB/399 kB of archives. After this operation, 1275 kB of additional disk space will be used. Do you want to continue? [Y/n] debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libjpeg62-turbo:amd64. (Reading database ... 12518 files and directories currently installed.) Preparing to unpack .../libjpeg62-turbo_1%3a1.5.2-2+b1_amd64.deb ... Unpacking libjpeg62-turbo:amd64 (1:1.5.2-2+b1) ... Selecting previously unselected package libturbojpeg0:amd64. Preparing to unpack .../libturbojpeg0_1%3a1.5.2-2+b1_amd64.deb ... Unpacking libturbojpeg0:amd64 (1:1.5.2-2+b1) ... Selecting previously unselected package libjpeg-turbo-progs. Preparing to unpack .../libjpeg-turbo-progs_1%3a1.5.2-2+b1_amd64.deb ... Unpacking libjpeg-turbo-progs (1:1.5.2-2+b1) ... Setting up libturbojpeg0:amd64 (1:1.5.2-2+b1) ... Setting up libjpeg62-turbo:amd64 (1:1.5.2-2+b1) ... Setting up libjpeg-turbo-progs (1:1.5.2-2+b1) ... Processing triggers for libc-bin (2.28-10) ... # cat /etc/apt/sources.list | grep buster | sed s/buster/sid/ >> /etc/apt/sources.list # cat /etc/apt/sources.list deb https://deb.debian.org/debian buster main deb https://deb.debian.org/debian sid main # apt update Hit:1 https://deb.debian.org/debian buster InRelease Get:2 https://deb.debian.org/debian sid InRelease [146 kB] Get:3 https://deb.debian.org/debian sid/main amd64 Packages [8345 kB] Fetched 8491 kB in 6s (1365 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 126 packages can be upgraded. Run 'apt list --upgradable' to see them. # apt policy libjpeg-turbo-progs libjpeg-turbo-progs: Installed: 1:1.5.2-2+b1 Candidate: 1:2.0.5-1 Version table: 1:2.0.5-1 500 500 https://deb.debian.org/debian sid/main amd64
Bug#957356: marked as done (ident2: ftbfs with GCC-10)
Your message dated Sat, 01 Aug 2020 20:46:47 +
with message-id
and subject line Bug#957356: fixed in ident2 1.07-2
has caused the Debian Bug report #957356,
regarding ident2: ftbfs with GCC-10
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.)
--
957356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ident2
Version: 1.07-1.1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ident2_1.07-1.1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
110 | cl->lp, cl->rp, rslt, info);
| ~~~
common.c:109:48: warning: ‘%s’ directive output may be truncated writing up to
128 bytes into a region of size between 102 and 110 [-Wformat-truncation=]
109 | snprintf (buf, ID_BUF_SIZE-1, "%d , %d : %s : %s\r\n",
|^~
..
199 | _clreply (cl, "USERID", buf);
| ~~~
common.c:109:2: note: ‘snprintf’ output between 20 and 156 bytes into a
destination of size 127
109 | snprintf (buf, ID_BUF_SIZE-1, "%d , %d : %s : %s\r\n",
| ^~
110 | cl->lp, cl->rp, rslt, info);
| ~~~
gcc -Wall -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -c -o daemon.o
daemon.c
daemon.c: In function ‘declient’:
daemon.c:87:45: warning: pointer targets in passing argument 3 of ‘accept’
differ in signedness [-Wpointer-sign]
87 | close (accept (s, (struct sockaddr *), ));
| ^~~
| |
| int *
In file included from ident2.h:50,
from daemon.c:34:
/usr/include/x86_64-linux-gnu/sys/socket.h:233:28: note: expected ‘socklen_t *
restrict’ {aka ‘unsigned int * restrict’} but argument is of type ‘int *’
233 | socklen_t *__restrict __addr_len);
| ~~^~
daemon.c: In function ‘_accept_connect’:
daemon.c:100:50: warning: passing argument 3 of ‘accept’ from incompatible
pointer type [-Wincompatible-pointer-types]
100 | while ((cl = accept(sv, (struct sockaddr *)sin, )) == -1) {
| ^~~
| |
| size_t * {aka long
unsigned int *}
In file included from ident2.h:50,
from daemon.c:34:
/usr/include/x86_64-linux-gnu/sys/socket.h:233:28: note: expected ‘socklen_t *
restrict’ {aka ‘unsigned int * restrict’} but argument is of type ‘size_t *’
{aka ‘long unsigned int *’}
233 | socklen_t *__restrict __addr_len);
| ~~^~
gcc -Wall -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -c -o machine.o
machine.c
gcc -Wall -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -o ident2 ident2.o
common.o daemon.o machine.o
/usr/bin/ld: common.o:./ident2.h:78: multiple definition of `User_Ident_File';
ident2.o:./ident2.h:78: first defined here
/usr/bin/ld: common.o:./ident2.h:79: multiple definition of
`Reply_Always_Random'; ident2.o:./ident2.h:79: first defined here
/usr/bin/ld:
Bug#957621: marked as done (nyquist: ftbfs with GCC-10)
Your message dated Sat, 01 Aug 2020 19:49:31 + with message-id and subject line Bug#957621: fixed in nyquist 3.12+ds-4 has caused the Debian Bug report #957621, regarding nyquist: ftbfs with GCC-10 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.) -- 957621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nyquist Version: 3.12+ds-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/nyquist_3.12+ds-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/c++ -DOSC -DSTK_NYQUIST -DUNIX -I/<>/ffts/src -I/<>/snd -I/<>/cmt -I/<>/xlisp -I/<>/tran -I/<>/nyqsrc -I/<>/nyqstk -I/<>/nyqstk/include -I/<>/cmupv/src -I/<>/portaudio/include -I/<>/sys/unix -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/ny.dir/nyqstk/src/FileRead.cpp.o -c /<>/nyqstk/src/FileRead.cpp [ 87%] Building CXX object CMakeFiles/ny.dir/nyqstk/src/FileWvIn.cpp.o /usr/bin/c++ -DOSC -DSTK_NYQUIST -DUNIX -I/<>/ffts/src -I/<>/snd -I/<>/cmt -I/<>/xlisp -I/<>/tran -I/<>/nyqsrc -I/<>/nyqstk -I/<>/nyqstk/include -I/<>/cmupv/src -I/<>/portaudio/include -I/<>/sys/unix -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/ny.dir/nyqstk/src/FileWvIn.cpp.o -c /<>/nyqstk/src/FileWvIn.cpp [ 88%] Building CXX object CMakeFiles/ny.dir/nyqstk/src/Flute.cpp.o /usr/bin/c++ -DOSC -DSTK_NYQUIST -DUNIX -I/<>/ffts/src -I/<>/snd -I/<>/cmt -I/<>/xlisp -I/<>/tran -I/<>/nyqsrc -I/<>/nyqstk -I/<>/nyqstk/include -I/<>/cmupv/src -I/<>/portaudio/include -I/<>/sys/unix -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/ny.dir/nyqstk/src/Flute.cpp.o -c /<>/nyqstk/src/Flute.cpp [ 88%] Building CXX object CMakeFiles/ny.dir/nyqstk/src/Function.cpp.o /usr/bin/c++ -DOSC -DSTK_NYQUIST -DUNIX -I/<>/ffts/src -I/<>/snd -I/<>/cmt -I/<>/xlisp -I/<>/tran -I/<>/nyqsrc -I/<>/nyqstk -I/<>/nyqstk/include -I/<>/cmupv/src -I/<>/portaudio/include -I/<>/sys/unix -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/ny.dir/nyqstk/src/Function.cpp.o -c /<>/nyqstk/src/Function.cpp [ 89%] Building CXX object CMakeFiles/ny.dir/nyqstk/src/Generator.cpp.o /usr/bin/c++ -DOSC -DSTK_NYQUIST -DUNIX -I/<>/ffts/src -I/<>/snd -I/<>/cmt -I/<>/xlisp -I/<>/tran -I/<>/nyqsrc -I/<>/nyqstk -I/<>/nyqstk/include -I/<>/cmupv/src -I/<>/portaudio/include -I/<>/sys/unix -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/ny.dir/nyqstk/src/Generator.cpp.o -c /<>/nyqstk/src/Generator.cpp [ 89%] Building CXX object CMakeFiles/ny.dir/nyqstk/src/JCRev.cpp.o /usr/bin/c++ -DOSC -DSTK_NYQUIST -DUNIX -I/<>/ffts/src -I/<>/snd -I/<>/cmt -I/<>/xlisp -I/<>/tran -I/<>/nyqsrc -I/<>/nyqstk -I/<>/nyqstk/include -I/<>/cmupv/src -I/<>/portaudio/include -I/<>/sys/unix -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/ny.dir/nyqstk/src/JCRev.cpp.o -c /<>/nyqstk/src/JCRev.cpp [ 89%] Building CXX object CMakeFiles/ny.dir/nyqstk/src/JetTable.cpp.o /usr/bin/c++ -DOSC
Processed: src:acpica-unix: fails to migrate to testing for too long: FTBFS on s390x
Processing control commands: > close -1 20200528-1 Bug #966680 [src:acpica-unix] src:acpica-unix: fails to migrate to testing for too long: FTBFS on s390x Marked as fixed in versions acpica-unix/20200528-1. Bug #966680 [src:acpica-unix] src:acpica-unix: fails to migrate to testing for too long: FTBFS on s390x Marked Bug as done -- 966680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966680: src:acpica-unix: fails to migrate to testing for too long: FTBFS on s390x
Source: acpica-unix Version: 20190509-1 Severity: serious Control: close -1 20200528-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:acpica-unix in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=acpica-unix signature.asc Description: OpenPGP digital signature
Bug#957188: patch to fix linking with gcc-10
Dear maintainer,
Attached is a patch to make gimp-lqr-plugin and wavelet-denoise-0.3.1 link
properly with gcc-10.
suggested changelog entry
lqr/gimp-lqr-plugin/src/interface_aux.c,
lqr/gimp-lqr-plugin/src/interface_I.c: declare variables as extern that
would otherwise clash with those in lqr/gimp-lqr-plugin/src/interface.c
wavelet-denoise/wavelet-denoise-0.3.1/src/interface.h,
wavelet-denoise/wavelet-denoise-0.3.1/src/plugin.h: declare global
variables as extern
wavelet-denoise/wavelet-denoise-0.3.1/src/interface.c,
wavelet-denoise/wavelet-denoise-0.3.1/src/plugin.c: add some global
variables now declared extern in the corresponding header files
Kind regards,
Arnold Metselaar
diff --git a/lqr/gimp-lqr-plugin/src/interface_I.c b/lqr/gimp-lqr-plugin/src/interface_I.c
index 2719167..dbe2717 100644
--- a/lqr/gimp-lqr-plugin/src/interface_I.c
+++ b/lqr/gimp-lqr-plugin/src/interface_I.c
@@ -73,10 +73,10 @@ static void callback_alarm_triggered (GtkWidget * size_entry, gpointer data);
gint dialog_I_response = GTK_RESPONSE_OK;
-PlugInUIVals *ui_state;
-PlugInVals *state;
-PlugInDialogVals *dialog_state;
-gboolean features_are_sensitive;
+extern PlugInUIVals *ui_state;
+extern PlugInVals *state;
+extern PlugInDialogVals *dialog_state;
+extern gboolean features_are_sensitive;
InterfaceIData interface_I_data;
//volatile sig_atomic_t interface_locked = 0;
diff --git a/lqr/gimp-lqr-plugin/src/interface_aux.c b/lqr/gimp-lqr-plugin/src/interface_aux.c
index 6461757..ceed0d9 100644
--- a/lqr/gimp-lqr-plugin/src/interface_aux.c
+++ b/lqr/gimp-lqr-plugin/src/interface_aux.c
@@ -49,11 +49,11 @@ static void callback_dialog_aux_response (GtkWidget * dialog, gint response_id,
gint dialog_aux_response = GTK_RESPONSE_OK;
-PlugInUIVals *ui_state;
-PlugInVals *state;
-PlugInDialogVals *dialog_state;
+extern PlugInUIVals *ui_state;
+extern PlugInVals *state;
+extern PlugInDialogVals *dialog_state;
-GtkWidget *dlg;
+extern GtkWidget *dlg;
/*** Public functions ***/
diff --git a/wavelet-denoise/wavelet-denoise-0.3.1/src/interface.c b/wavelet-denoise/wavelet-denoise-0.3.1/src/interface.c
index 170894b..2f95572 100644
--- a/wavelet-denoise/wavelet-denoise-0.3.1/src/interface.c
+++ b/wavelet-denoise/wavelet-denoise-0.3.1/src/interface.c
@@ -16,8 +16,36 @@
#include "plugin.h"
#include "interface.h"
+/* Global variables declared in interface.h */
+/* colour mode frame */
+GtkWidget *fr_mode, *mode_radio[3], *mode_vbox;
+GSList *mode_list;
+
+/* preview select frame */
+GtkWidget *fr_preview, *preview_radio[3], *preview_vbox, *preview_check;
+GSList *preview_list;
+
+/* channel select frame */
+GtkWidget *fr_channel, *channel_radio[4], *channel_vbox;
+GSList *channel_list;
+
+/* threshold frame */
+GtkWidget *fr_threshold, *thr_label[2], *thr_spin[2];
+GtkWidget *thr_hbox[2], *thr_vbox, *thr_scale[2];
+GtkObject *thr_adj[2];
+
+/* reset buttons */
+GtkWidget *reset_button[2], *reset_hbox, *reset_align, *reset_button_icon[2];
+
+/* dialog */
+GtkWidget *dialog, *dialog_hbox, *dialog_vbox, *frame_hbox, *dialog_aspect;
+GtkWidget *preview, *preview_reset, *preview_hbox, *preview_reset_icon;
+
GtkWidget **radios_labels[] = { channel_radio, thr_label };
+char **names;
+
+
gboolean
user_interface (GimpDrawable * drawable)
{
diff --git a/wavelet-denoise/wavelet-denoise-0.3.1/src/interface.h b/wavelet-denoise/wavelet-denoise-0.3.1/src/interface.h
index f0ce8ad..0f5430e 100644
--- a/wavelet-denoise/wavelet-denoise-0.3.1/src/interface.h
+++ b/wavelet-denoise/wavelet-denoise-0.3.1/src/interface.h
@@ -14,29 +14,29 @@
*/
/* colour mode frame */
-GtkWidget *fr_mode, *mode_radio[3], *mode_vbox;
-GSList *mode_list;
+extern GtkWidget *fr_mode, *mode_radio[3], *mode_vbox;
+extern GSList *mode_list;
/* preview select frame */
-GtkWidget *fr_preview, *preview_radio[3], *preview_vbox, *preview_check;
-GSList *preview_list;
+extern GtkWidget *fr_preview, *preview_radio[3], *preview_vbox, *preview_check;
+extern GSList *preview_list;
/* channel select frame */
-GtkWidget *fr_channel, *channel_radio[4], *channel_vbox;
-GSList *channel_list;
+extern GtkWidget *fr_channel, *channel_radio[4], *channel_vbox;
+extern GSList *channel_list;
/* threshold frame */
-GtkWidget *fr_threshold, *thr_label[2], *thr_spin[2];
-GtkWidget *thr_hbox[2], *thr_vbox, *thr_scale[2];
-GtkObject *thr_adj[2];
+extern GtkWidget *fr_threshold, *thr_label[2], *thr_spin[2];
+extern GtkWidget *thr_hbox[2], *thr_vbox, *thr_scale[2];
+extern GtkObject *thr_adj[2];
/* reset buttons */
-GtkWidget *reset_button[2], *reset_hbox, *reset_align, *reset_button_icon[2];
+extern GtkWidget *reset_button[2], *reset_hbox, *reset_align, *reset_button_icon[2];
/* dialog */
-GtkWidget *dialog, *dialog_hbox, *dialog_vbox, *frame_hbox, *dialog_aspect;
-GtkWidget *preview, *preview_reset, *preview_hbox, *preview_reset_icon;
+extern GtkWidget *dialog, *dialog_hbox, *dialog_vbox, *frame_hbox, *dialog_aspect;
+extern GtkWidget *preview, *preview_reset,
Bug#966679: src:rust-csv: fails to migrate to testing for too long: autopkgtest regression
Source: rust-csv Version: 1.1.1-1 Severity: serious Control: close -1 1.1.3-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 962803 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:rust-csv in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=rust-csv signature.asc Description: OpenPGP digital signature
Processed: closing 872405
Processing commands for cont...@bugs.debian.org:
> close 872405
Bug #872405 {Done: Salvatore Bonaccorso } [src:mariadb-10.0]
mariadb-10.0: FTBFS on s390x
Bug 872405 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
872405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:rust-csv: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 1.1.3-1
Bug #966679 [src:rust-csv] src:rust-csv: fails to migrate to testing for too
long: autopkgtest regression
Marked as fixed in versions rust-csv/1.1.3-1.
Bug #966679 [src:rust-csv] src:rust-csv: fails to migrate to testing for too
long: autopkgtest regression
Marked Bug as done
> block -1 by 962803
Bug #966679 {Done: Paul Gevers } [src:rust-csv]
src:rust-csv: fails to migrate to testing for too long: autopkgtest regression
966679 was not blocked by any bugs.
966679 was not blocking any bugs.
Added blocking bug(s) of 966679: 962803
--
966679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 872404
Processing commands for cont...@bugs.debian.org:
> close 872404
Bug #872404 {Done: Salvatore Bonaccorso } [src:mariadb-10.0]
mariadb-10.0: FTBFS on mipsel
Bug 872404 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
872404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 872403
Processing commands for cont...@bugs.debian.org:
> close 872403
Bug #872403 {Done: Salvatore Bonaccorso } [src:mariadb-10.0]
mariadb-10.0: FTBFS on mips
Bug 872403 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
872403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#872405: closing 872405
close 872405 thanks
Bug#872403: closing 872403
close 872403 thanks
Bug#872404: closing 872404
close 872404 thanks
Processed: closing 872405
Processing commands for cont...@bugs.debian.org: > # not supported anymore > close 872405 Bug #872405 [src:mariadb-10.0] mariadb-10.0: FTBFS on s390x Marked Bug as done > close 872404 Bug #872404 [src:mariadb-10.0] mariadb-10.0: FTBFS on mipsel Marked Bug as done > close 872403 Bug #872403 [src:mariadb-10.0] mariadb-10.0: FTBFS on mips Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 872403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872403 872404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872404 872405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 966330 in 2.35.2-8
Processing commands for cont...@bugs.debian.org:
> found 966330 2.35.2-8
Bug #966330 {Done: Chris Hofstaedtler } [libblkid-dev]
e2fsprogs: FTBFS since libblkid-dev dropped libblkid.a
Marked as found in versions util-linux/2.35.2-8.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 902720, fixed 902720 in 1.2.0-1.1+deb9u1
Processing commands for cont...@bugs.debian.org:
> unarchive 902720
Bug #902720 {Done: Markus Koschany } [ruby-zip]
CVE-2018-1000544
Unarchived Bug 902720
> fixed 902720 1.2.0-1.1+deb9u1
Bug #902720 {Done: Markus Koschany } [ruby-zip]
CVE-2018-1000544
There is no source info for the package 'ruby-zip' at version
'1.2.0-1.1+deb9u1' with architecture ''
Unable to make a source version for version '1.2.0-1.1+deb9u1'
Marked as fixed in versions 1.2.0-1.1+deb9u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966330: marked as done (e2fsprogs: FTBFS since libblkid-dev dropped libblkid.a)
Your message dated Sat, 01 Aug 2020 18:35:44 + with message-id and subject line Bug#966330: fixed in util-linux 2.36-2 has caused the Debian Bug report #966330, regarding e2fsprogs: FTBFS since libblkid-dev dropped libblkid.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.) -- 966330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: e2fsprogs Version: 1.45.6-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Control: found -1 1.46~WIP.2019.10.03-1 Hi, libblkid-dev recently dropped libblkid.a causing e2fsprogs to FTBFS: make[2]: Entering directory '/build/e2fsprogs-1.45.6/debian/BUILD-STD/e2fsck' gcc -Wl,-z,relro -Wl,-z,now -static -o e2fsck.static unix.o e2fsck.o super.o pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o badblocks.o util.o dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o quota.o recovery.o region.o revoke.o ea_refcount.o rehash.o logfile.o sigcatcher.o readahead.o extents.o ../lib/libsupport.a ../lib/libext2fs.a ../lib/libcom_err.a -lpthread -lblkid -luuid -luuid ../lib/libe2p.a -ldl /usr/bin/ld: cannot find -lblkid /usr/bin/ld: logfile.o: in function `expand_percent_expression': ./debian/BUILD-STD/e2fsck/../../../e2fsck/logfile.c:141: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking collect2: error: ld returned 1 exit status make[2]: *** [Makefile:449: e2fsck.static] Error 1 Andreas --- End Message --- --- Begin Message --- Source: util-linux Source-Version: 2.36-2 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of util-linux, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated util-linux 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: Sat, 01 Aug 2020 17:28:26 + Source: util-linux Architecture: source Version: 2.36-2 Distribution: unstable Urgency: medium Maintainer: util-linux packagers Changed-By: Chris Hofstaedtler Closes: 966330 Changes: util-linux (2.36-2) unstable; urgency=medium . * Reinstate libblkid.a (Closes: #966330) Checksums-Sha1: c5c56391ffa877769e99549a4df9d574ad3ba784 4323 util-linux_2.36-2.dsc 731dbbb9431f9b3854d3799a3e10a27883c23575 95208 util-linux_2.36-2.debian.tar.xz 55d553bbcec5ee969a01e342cf3dfa614e66c05c 6527 util-linux_2.36-2_source.buildinfo Checksums-Sha256: ccf999e8d8b8e4bd27b80533deba36170405835873794ba745df32e0eda7aa25 4323 util-linux_2.36-2.dsc 0feac62c2f93ec3d3939c57704e16d81a500eb188b69b615f5dfd793dcb209e8 95208 util-linux_2.36-2.debian.tar.xz 29048669be2126344d16f978f2fd14ea9d25cbe3777935833e486c31d00a4949 6527 util-linux_2.36-2_source.buildinfo Files: 022bf40acdbfcac534e387a70580b467 4323 base required util-linux_2.36-2.dsc 36fe1bfb355f787378d321113e898777 95208 base required util-linux_2.36-2.debian.tar.xz ebd9985a62fab408c5440c9870b59eeb 6527 base required util-linux_2.36-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAl8lr0AACgkQXBPW25MF LgMTsA//TWbFlTfsNk9pxxu049VFJr27jbtcVG5v1s4kEg5/V2bGn/mfKwcOjM8N R2sMRo8UARUXKs3fxEa9KgGM5Fh/ZX/hP5EHX677CFL1LIz4mBPssV3+HpBI3UpS TisZZoYr8bslikeAA7A8/mrvn6gETAdAjamK9G41pC6RSSHx5QEUSIlvre2wJecr 8ko1LtoL4jWGu7o182fl9SP+E6pqm2GkQOJydub4g3A3TP+OwtEYl7XluIHU6APe pbHh9xs0QwX8VLnyqcCz5kk8TgAoOEMAhE64BntOXYhOpukfNpZDAvtcrAMvimjB mm1mWFWysofLCFTY7q0O0kLCWW+/NptsT9FmSKJsPohuBFrVV1GhAu92TW2nc0EE V7himWL9ZbDkksK5DMlY+M/tWVm2f0/hS3/pOZh2qTcYHObAc0wisD2MzKZCFjJM zTX5HawTfKRdFkTXZDTe9X6YJZRbBeYqwt+qbqC5hmQVdRVK/Og5xHQTBbtTXuSO dgpIto0I3Cm+Xem5oAQBEalIQrdra60pxEUITZRjtcbkHHarTcDpEO0sIhQduCxu DNvA3z6eIbjGgkNVOZ31naBUjldKv2iiO4IoL61PdOZsElespxac0ZHEHEr8RsEV 4xj7a9U6QwnH/Nm9nT4JxOl8WviDbw7ZPnEjMxKZvEvceKeGCf0= =mUeg -END PGP SIGNATURE End Message ---
Bug#963286: libisnativec-java: diff for NMU version 5.3.20100629+fix-2.1
Just for the records - I cancelled the NMU and uploaded it as "Team upload" as discussed in https://lists.debian.org/debian-java/2020/08/msg0.html. -- Regards Sudip
Bug#966330: marked as pending in util-linux
Control: tag -1 pending Hello, Bug #966330 in util-linux reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/util-linux/-/commit/c962118f4af10d18deafb665f85305554299bb8a Reinstate libblkid.a Closes: #966330 (this message was generated automatically) -- Greetings https://bugs.debian.org/966330
Processed: Bug#966330 marked as pending in util-linux
Processing control commands: > tag -1 pending Bug #966330 [libblkid-dev] e2fsprogs: FTBFS since libblkid-dev dropped libblkid.a Added tag(s) pending. -- 966330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964573: marked as done (xrdp: CVE-2020-4044)
Your message dated Sat, 01 Aug 2020 18:03:51 + with message-id and subject line Bug#964573: fixed in xrdp 0.9.9-1+deb10u1 has caused the Debian Bug report #964573, regarding xrdp: CVE-2020-4044 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.) -- 964573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xrdp Version: CVE-2020-4044 Severity: grave Tags: security upstream Hi, The following vulnerability was published for xrdp. CVE-2020-4044[0]: | The xrdp-sesman service before version 0.9.13.1 can be crashed by | connecting over port 3350 and supplying a malicious payload. Once the | xrdp-sesman process is dead, an unprivileged attacker on the server | could then proceed to start their own imposter sesman service | listening on port 3350. This will allow them to capture any user | credentials that are submitted to XRDP and approve or reject arbitrary | login credentials. For xorgxrdp sessions in particular, this allows an | unauthorized user to hijack an existing session. This is a buffer | overflow attack, so there may be a risk of arbitrary code execution as | well. 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-2020-4044 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-4044 [1] https://github.com/neutrinolabs/xrdp/security/advisories/GHSA-j9fv-6fwf-p3g4 [2] https://github.com/neutrinolabs/xrdp/commit/e593f58a82bf79b556601ae08e9e25e366a662fb Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: xrdp Source-Version: 0.9.9-1+deb10u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of xrdp, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated xrdp 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: Sun, 19 Jul 2020 17:02:11 +0200 Source: xrdp Architecture: source Version: 0.9.9-1+deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian Remote Maintainers Changed-By: Salvatore Bonaccorso Closes: 964573 Changes: xrdp (0.9.9-1+deb10u1) buster-security; urgency=high . * Non-maintainer upload by the Security Team. * libscp v1 server set height twice, and not set width * xrdp-sesman can be crashed remotely over port 3350 (CVE-2020-4044) (Closes: #964573) * Fixed CVE-2020-4044 CI errors Checksums-Sha1: aa097733cf0226ef0140e93bbb91bfc7cde2cdc8 2430 xrdp_0.9.9-1+deb10u1.dsc 4d797be6e270305273806fe42d80a6e746f4c818 1866532 xrdp_0.9.9.orig.tar.gz e8f4c6f15994e432e7071072cc65ad4782306352 27872 xrdp_0.9.9-1+deb10u1.debian.tar.xz Checksums-Sha256: a6124cdaad754910c3d5def99c23e17f1d363a98d0fb2889a2422153a8c34fff 2430 xrdp_0.9.9-1+deb10u1.dsc 8edf33346a8b3718a828d2c998ac1a036ea707e7f02b47092c8ae20dd71a9362 1866532 xrdp_0.9.9.orig.tar.gz 813d5156e9f7cd8b81819c26b42da3696f2c504dbcd910f1d29e11d514a23b15 27872 xrdp_0.9.9-1+deb10u1.debian.tar.xz Files: beb677205062dba8302b3db291664279 2430 net optional xrdp_0.9.9-1+deb10u1.dsc d2f57182036c3f69dcaca0dfed4aaa6b 1866532 net optional xrdp_0.9.9.orig.tar.gz d9f383856dec7ff03ca29726c0542432 27872 net optional xrdp_0.9.9-1+deb10u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl8UYVlfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89E/TQP/2kBfYRy0ux9X9ViRsQvJDeQiWgs7OVx 2Rynt93/9nDV/OEctrUqPztHuZKac0bLQJm5A20RxWmWMItudQvHm1ahiA625r83 5QJIx4IgFN2FlGnQiMyoTOCcERmSO7GqC9/sQHSkyvP6anuqWgjRW6ls3+U+MA84 IhFuH9xKourffjZ7JRzeO6VWNw6cnIQg1lRns2RK9iYe0ckbVck+3AQTCylLDwdF bC4HBFOV7lziFOrANPEE1YIz6TAJqH84MyXNfTVumH1CfEaNXLAhgvx+WbPoFI/T au8ol0ABxCS96YtJXQdPgymtPNpFCb1slxQOwBVnSvjAb6VB8YtN9wm/ewgwQkZ3
Bug#963286: marked as done (libisnativec-java: FTBFS: ./src/de/intarsys/nativec/jna/JnaNativeHandle.java:129: error: incompatible types: boolean cannot be converted to String)
Your message dated Sat, 01 Aug 2020 17:48:43 + with message-id and subject line Bug#963286: fixed in libisnativec-java 5.3.20100629+fix-3 has caused the Debian Bug report #963286, regarding libisnativec-java: FTBFS: ./src/de/intarsys/nativec/jna/JnaNativeHandle.java:129: error: incompatible types: boolean cannot be converted to String 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.) -- 963286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libisnativec-java Version: 5.3.20100629+fix-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with javahelper >dh_update_autotools_config >dh_autoreconf >jh_linkjars >jh_build > warning: [options] bootstrap class path not set in conjunction with -source 7 > ./src/de/intarsys/nativec/jna/JnaNativeHandle.java:129: error: incompatible > types: boolean cannot be converted to String > return getPointer().getString(index, true); >^ > ./src/de/intarsys/nativec/jna/JnaNativeHandle.java:184: error: incompatible > types: boolean cannot be converted to String > getPointer().setString(index, value, true); >^ > Note: Some input files use or override a deprecated API. > Note: Recompile with -Xlint:deprecation for details. > Note: ./src/de/intarsys/nativec/jna/JnaNativeFunction.java uses unchecked or > unsafe operations. > Note: Recompile with -Xlint:unchecked for details. > Note: Some messages have been simplified; recompile with -Xdiags:verbose to > get full output > 2 errors > 1 warning > jh_build: error: find ./src -name '*.java' -and -type f -print0 | xargs -s > 512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp > /usr/share/java/jna.jar:/usr/share/java/isrt.jar:debian/_jh_build.isnativec > -d debian/_jh_build.isnativec -encoding ISO8859-1 -source 1.7 -target 1.7 > returned exit code 123 > make: *** [debian/rules:6: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/06/20/libisnativec-java_5.3.20100629+fix-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: libisnativec-java Source-Version: 5.3.20100629+fix-3 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of libisnativec-java, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated libisnativec-java 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: Sat, 01 Aug 2020 18:28:33 +0100 Source: libisnativec-java Architecture: source Version: 5.3.20100629+fix-3 Distribution: unstable Urgency: medium Maintainer: Steffen Moeller Changed-By: Sudip Mukherjee Closes: 963286 Changes: libisnativec-java (5.3.20100629+fix-3) unstable; urgency=medium . * Team upload. * Fix FTBFS. (Closes: #963286) Checksums-Sha1: 19267317ed9954382f0e6a1c6f0b39d358214ad6 2172 libisnativec-java_5.3.20100629+fix-3.dsc 8be20c17001783ae371e63c8b79e8d8028b0807a 4028 libisnativec-java_5.3.20100629+fix-3.debian.tar.xz 4300dbf0b7c58733a1e57a2521df605b272eb5fe 10803 libisnativec-java_5.3.20100629+fix-3_amd64.buildinfo Checksums-Sha256: f46d254e1277bfce9dc0d060550c9a154fe649509f4a292e8d8cc7659e463302 2172 libisnativec-java_5.3.20100629+fix-3.dsc 79c72babb9949ae8c0992930bff588c54a0c03e55d4f636871301f5f5f43d09b 4028 libisnativec-java_5.3.20100629+fix-3.debian.tar.xz
Processed: reassign 966330 to libblkid-dev, affects 966330
Processing commands for cont...@bugs.debian.org: > reassign 966330 libblkid-dev Bug #966330 [src:e2fsprogs] e2fsprogs: FTBFS since libblkid-dev dropped libblkid.a Bug reassigned from package 'src:e2fsprogs' to 'libblkid-dev'. No longer marked as found in versions e2fsprogs/1.45.6-1 and e2fsprogs/1.46~WIP.2019.10.03-1. Ignoring request to alter fixed versions of bug #966330 to the same values previously set > affects 966330 + src:e2fsprogs Bug #966330 [libblkid-dev] e2fsprogs: FTBFS since libblkid-dev dropped libblkid.a Added indication that 966330 affects src:e2fsprogs > thanks Stopping processing here. Please contact me if you need assistance. -- 966330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
>From conversation in IRC: 1. If the device(s) mentioned in grub-pc/install_devices multiselect don't exist when grub-install is run, it should stop and warn the user that there might be a problem DSA have this on a VM, for example: grub-pc grub-pc/install_devices multiselect/dev/disk/by-id/scsi-3600508b1001052395358323050350006 2. Warn if install_devices is empty? -- Steve McIntyre, Cambridge, UK.st...@einval.com "You can't barbecue lettuce!" -- Ellie Crane
Bug#957180: marked as done (ettercap: ftbfs with GCC-10)
Your message dated Sat, 01 Aug 2020 15:18:35 + with message-id and subject line Bug#957180: fixed in ettercap 1:0.8.3.1-1 has caused the Debian Bug report #957180, regarding ettercap: ftbfs with GCC-10 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.) -- 957180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ettercap Version: 1:0.8.3-7 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/ettercap_0.8.3-7_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] [ 9%] Building C object src/interfaces/CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_menu.c.o cd /<>/obj-text-only/src/interfaces && /usr/bin/cc -Dec_interfaces_EXPORTS -I/<>/obj-text-only/include -I/<>/include -I/usr/include/ncurses -I/<>/src/interfaces/text -I/<>/src/interfaces/daemon -I/<>/src/interfaces/curses -I/<>/src/interfaces/curses/widgets -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIC -o CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_menu.c.o -c /<>/src/interfaces/curses/widgets/wdg_menu.c [ 9%] Building C object src/interfaces/CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_panel.c.o cd /<>/obj-text-only/src/interfaces && /usr/bin/cc -Dec_interfaces_EXPORTS -I/<>/obj-text-only/include -I/<>/include -I/usr/include/ncurses -I/<>/src/interfaces/text -I/<>/src/interfaces/daemon -I/<>/src/interfaces/curses -I/<>/src/interfaces/curses/widgets -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIC -o CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_panel.c.o -c /<>/src/interfaces/curses/widgets/wdg_panel.c [ 9%] Building C object src/interfaces/CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_percentage.c.o cd /<>/obj-text-only/src/interfaces && /usr/bin/cc -Dec_interfaces_EXPORTS -I/<>/obj-text-only/include -I/<>/include -I/usr/include/ncurses -I/<>/src/interfaces/text -I/<>/src/interfaces/daemon -I/<>/src/interfaces/curses -I/<>/src/interfaces/curses/widgets -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIC -o CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_percentage.c.o -c /<>/src/interfaces/curses/widgets/wdg_percentage.c [ 10%] Creating PDF for /<>/obj-text-only/man/ettercap_curses.8 /usr/bin/groff -mandoc -Tpdf /<>/obj-text-only/man/ettercap_curses.8 > /<>/obj-text-only/man/ettercap_curses.8.pdf [ 11%] Building C object src/interfaces/CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_scroll.c.o cd /<>/obj-text-only/src/interfaces && /usr/bin/cc -Dec_interfaces_EXPORTS -I/<>/obj-text-only/include -I/<>/include -I/usr/include/ncurses -I/<>/src/interfaces/text -I/<>/src/interfaces/daemon -I/<>/src/interfaces/curses -I/<>/src/interfaces/curses/widgets -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIC -o CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_scroll.c.o -c /<>/src/interfaces/curses/widgets/wdg_scroll.c [ 11%] Building C object src/interfaces/CMakeFiles/ec_interfaces.dir/curses/widgets/wdg_window.c.o cd /<>/obj-text-only/src/interfaces && /usr/bin/cc -Dec_interfaces_EXPORTS -I/<>/obj-text-only/include
Processed: found 966671 in 4.5.1.1-1.1
Processing commands for cont...@bugs.debian.org: > # as not specific to the deb10u1 revision in buster and affecting all other > versions > found 966671 4.5.1.1-1.1 Bug #966671 [coturn] coturn: unlimited number of /var/log/turn_*.log are created Marked as found in versions coturn/4.5.1.1-1.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 966671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908694: album-data: diff for NMU version 4.05-7.1
Control: tags 908694 + patch
Control: tags 908694 + pending
Dear maintainer,
I've prepared an NMU for album-data (versioned as 4.05-7.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru album-data-4.05/debian/changelog album-data-4.05/debian/changelog
--- album-data-4.05/debian/changelog2016-04-05 17:02:39.0 +0100
+++ album-data-4.05/debian/changelog2020-08-01 15:43:30.0 +0100
@@ -1,3 +1,11 @@
+album-data (4.05-7.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed dependency on libjs-swfobject. (Closes: #908694)
+- Upstream has confirmed. (See: #964105)
+
+ -- Sudip Mukherjee Sat, 01 Aug 2020 15:43:30
+0100
+
album-data (4.05-7) unstable; urgency=low
* Change Vcs-Browser to use https.
diff -Nru album-data-4.05/debian/control album-data-4.05/debian/control
--- album-data-4.05/debian/control 2016-04-05 16:08:03.0 +0100
+++ album-data-4.05/debian/control 2020-08-01 15:41:25.0 +0100
@@ -10,7 +10,7 @@
Package: album-data
Architecture: all
-Depends: ${misc:Depends}, album, libjs-swfobject
+Depends: ${misc:Depends}, album
Description: themes, plugins and translations for album
Album is a perl script that can create HTML photo albums for your
directories of images. This package provides themes, plugins and
Processed: album-data: diff for NMU version 4.05-7.1
Processing control commands: > tags 908694 + patch Bug #908694 [album-data] album-data: please remove dependency on libjs-swfobject, which is going away Added tag(s) patch. > tags 908694 + pending Bug #908694 [album-data] album-data: please remove dependency on libjs-swfobject, which is going away Added tag(s) pending. -- 908694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957565: marked as done (mpgrafic: ftbfs with GCC-10)
Your message dated Sat, 1 Aug 2020 16:31:29 +0200 (CEST) with message-id and subject line Re: Bug#957565: mpgrafic: ftbfs with GCC-10 has caused the Debian Bug report #957565, regarding mpgrafic: ftbfs with GCC-10 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.) -- 957565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mpgrafic Version: 0.3.18-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/mpgrafic_0.3.18-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking whether we are using the GNU Fortran compiler... yes checking whether gfortran accepts -g... yes checking for mpifort... mpifort checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking how to get verbose linking output from mpifort... -v checking for Fortran libraries of mpifort... -L/usr/lib/x86_64-linux-gnu/openmpi/lib -L/usr/lib/gcc/x86_64-linux-gnu/10 -L/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/10/../../.. -lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi -lgfortran -lm -lquadmath -lpthread checking for fftw3d_f77_create_plan in -ldfftw... no checking for fftw3d_f77_create_plan in -lfftw... yes checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) none checking for main in -lgcc... yes checking for cblas_dgemv in -lgslcblas... yes checking for gsl_spline_init in -lgsl... yes checking for mpicc... mpicc checking for MPI_Init... yes checking for mpi.h... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating config.h config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' mpifort -cpp -DDOUB -DHAVE_USE_MPI_F08 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -c -o grafic_types.o grafic_types.f90 mpicc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o parallel_io.o parallel_io.c mpifort -cpp -DDOUB -DHAVE_USE_MPI_F08 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -c -o wrap_gsl_rng_mod.o wrap_gsl_rng_mod.f90 mpicc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o c_gsl_wrap.o c_gsl_wrap.c mpifort -cpp -DDOUB -DHAVE_USE_MPI_F08 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -c -o wrap_rfftw3d_mod.o wrap_rfftw3d_mod.f90 mpicc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o rfftw3d_mpi_create_plan_c_wrap.o
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
[ Dropping the CC to Chad here ]
On Sat, Aug 01, 2020 at 02:36:25PM +0100, Colin Watson wrote:
>On Sat, Aug 01, 2020 at 01:52:41PM +0100, Steve McIntyre wrote:
>> * Do we need to scan? if grub is installed and doing an upgrade and
>>there is only one disk of an appropriate type (BIOS with DOS, or
>>UEFI with GPT), then always install there?
>
>Possibly. I'd still be inclined to have a scan as a guard-rail in that
>case, since we'd need to have the code anyway, and the point is to try
>to discover the disk that the system booted from so by definition it
>must have GRUB there if it's to be valid.
Nod. Of course, it's a guess at best - we have ~no way to know *for
sure* which disk we actually booted off. It would be lovely if we did,
but there's no protocol for grub to pass on that information that I
can see.
>> * (Maybe) we could add an option for grub-pc to always grub-install
>>to *all* the BIOS-visible disks? Yes, I know there's a potential
>>for breakage there with multi-boot systems. Maybe only do this on
>>systems where os-prober has not found anything but the Debian
>>installation?
>
>One concern I have is filtering out things like optical drives, which
>are BIOS-visible but not sensible grub-install targets. I'm also
>slightly reluctant to add more invocations of os-prober while it's as
>slow as it can sometimes be. I do see the utility of this though.
Nod. Can we not rely on os-prober already having been run once and use
that data? (Sorry, not sure of the ordering here.)
>> * If we do add the code to scan boot sectors, maybe check all the
>>BIOS-visible disks and flag any that look like they have GRUB, but
>>are not our version? (Not sure how feasible this is without
>>digging!)
>
>Unfortunately I believe this to be essentially infeasible. As an
>illustration, this is the scan code which exists in the current postinst
>to support migration from GRUB Legacy, and believe me I didn't resort to
>this horror before trying to find more sensible alternatives:
>
> # In order to determine whether we accidentally ran grub-install without
> # upgrade-from-grub-legacy on versions older than 1.98+20100617-1, we need
> # to be able to scan a disk to determine whether GRUB 2 was installed in its
> # boot sector. This is specific to i386-pc (but that's the only platform
> # where we need it).
> scan_grub2()
> {
>if ! dd if="$1" bs=512 count=1 2>/dev/null | grep -aq GRUB; then
> # No version of GRUB is installed.
> return 1
>fi
>
># The GRUB boot sector always starts with a JMP instruction.
>initial_jmp="$(dd if="$1" bs=2 count=1 2>/dev/null | od -Ax -tx1 | \
> head -n1 | cut -d' ' -f2,3)"
>[ "$initial_jmp" ] || return 1
>initial_jmp_opcode="${initial_jmp%% *}"
>[ "$initial_jmp_opcode" = eb ] || return 1
>initial_jmp_operand="${initial_jmp#* }"
>case $initial_jmp_operand in
> 47|4b|4c|63)
># I believe this covers all versions of GRUB 2 up to the package
># version where we gained a more explicit mechanism. GRUB Legacy
># always had 48 here.
>return 0
> ;;
>esac
>
>return 1
> }
>
>The actual package version does get embedded in the boot loader, but
>only in the "normal" module, not anywhere that could be usefully
>discovered by a scan. Otherwise the best we could do would basically be
>a big list of signatures, which I'm not enthusiastic about.
Argh, yes. Basically what I expected, I'll be honest. Oh, hmmm -
that's the boot sector. Could we pick up on more from the embedded
binary "stage 1.5" lump? This is getting hairy, maybe, but
could/should be a wider thing to go upstream?
>> * For UEFI, I'd love to switch to using the monolithic GRUB image
>>even for non-signed use. It makes a lot of the issues go away if
>>~all the modules necessary for boot are always built-in.
>
>I think I agree, though we should take that to a separate bug; I'd like
>to keep this one for the BIOS situation.
Agreed. Just something I thought to mention while it was in my
head. :-)
>> * Finally, we should also stop using debconf as a registry like we
>>are. It's annoying the DSA folks (at least). By all means use
>>debconf to help manage things, but we should be storing the lasting
>>config in a config file that people can edit. We already store some
>>of our stuff in /etc/default/grub, let's push more of our config
>>there?
>
>Agreed in general terms; this has been on my to-do list for a long time.
>Of course we need to consider the migration path carefully. In terms of
>specifics, I'm not sure I want to extend /etc/default/grub for this,
>though; that has configuration file management issues, and generally I
>don't really want to overload the upstream grub-mkconfig configuration
>file with packaging-specific things for grub-install. I'd be inclined
>to go for /etc/default/grub-pc instead, or maybe something under
>/etc/grub/.
Sure.
Bug#966671: coturn: unlimited number of /var/log/turn_*.log are created
Package: coturn Version: 4.5.1.1-1.1+deb10u1 Severity: serious Justification: Policy 10.8 Dear Maintainer, An unlimited number of /var/log/turn_*.log are created. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (400, 'proposed-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages coturn depends on: ii adduser 3.118 ii libc62.28-10 ii libevent-core-2.1-6 2.1.8-stable-4 ii libevent-extra-2.1-6 2.1.8-stable-4 ii libevent-openssl-2.1-6 2.1.8-stable-4 ii libevent-pthreads-2.1-6 2.1.8-stable-4 ii libhiredis0.14 0.14.0-3 ii libmariadb3 1:10.3.22-0+deb10u1 ii libpq5 11.7-0+deb10u1 ii libsqlite3-0 3.27.2-3 ii libssl1.11.1.1d-0+deb10u3 ii lsb-base 10.2019051400 ii sqlite3 3.27.2-3 ii telnet [telnet-client] 0.17-41.2 coturn recommends no packages. -- Configuration Files: /etc/default/coturn changed: TURNSERVER_ENABLED=1 /etc/turnserver.conf changed: no-tlsv1 no-tlsv1_1 listening-ip= external-ip= realm=domain.tld denied-peer-ip=10.0.0.0-10.255.255.255 denied-peer-ip=192.168.0.0-192.168.255.255 denied-peer-ip=172.16.0.0-172.31.255.255 allowed-peer-ip=10.8.0.0-10.8.255.255 use-auth-secret static-auth-secret= user-quota=16 syslog mobility cert=/etc/ssl/localcerts/domain.tld-cert.pem pkey=/etc/ssl/localcerts/domain.tld-key.pem cipher-list="CHACHA20:AESGCM:!AES128" dh2066 no-cli cli-password=pass -- no debconf information
Bug#957068: cavezofphear: ftbfs with GCC-10
Control: tags -1 + patch
Hi,
the attached patches fixes the FTBFS with GCC 10.
Regards,
Reiner
diff -Nru cavezofphear-0.5.1/debian/patches/gcc10.patch cavezofphear-0.5.1/debian/patches/gcc10.patch
--- cavezofphear-0.5.1/debian/patches/gcc10.patch 1970-01-01 01:00:00.0 +0100
+++ cavezofphear-0.5.1/debian/patches/gcc10.patch 2020-08-01 15:44:47.0 +0200
@@ -0,0 +1,26 @@
+Author: Reiner Herrmann
+Description: Fix FTBFS with GCC 10
+Bug-Debian: https://bugs.debian.org/957068
+
+--- a/src/frame.c
b/src/frame.c
+@@ -26,7 +26,7 @@
+ void sigint_handler();
+ void sigwinch_handler();
+
+-int need_refresh;
++extern int need_refresh;
+
+ void curses_start(void)
+ {
+--- a/src/editor.c
b/src/editor.c
+@@ -24,7 +24,7 @@
+ #include "common.h"
+ #include "proto.h"
+
+-char map[MAP_YSIZE][MAP_XSIZE];
++extern char map[MAP_YSIZE][MAP_XSIZE];
+ int lock;
+ int last_obj;
+
diff -Nru cavezofphear-0.5.1/debian/patches/series cavezofphear-0.5.1/debian/patches/series
--- cavezofphear-0.5.1/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ cavezofphear-0.5.1/debian/patches/series 2020-08-01 15:44:47.0 +0200
@@ -0,0 +1 @@
+gcc10.patch
signature.asc
Description: PGP signature
Processed: Re: cavezofphear: ftbfs with GCC-10
Processing control commands: > tags -1 + patch Bug #957068 [src:cavezofphear] cavezofphear: ftbfs with GCC-10 Added tag(s) patch. -- 957068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 957049 is forwarded to https://github.com/khvzak/bluez-tools/pull/34
Processing commands for cont...@bugs.debian.org: > forwarded 957049 https://github.com/khvzak/bluez-tools/pull/34 Bug #957049 [src:bluez-tools] bluez-tools: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://github.com/khvzak/bluez-tools/pull/34'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966670: pixelmed FTBFS: iconv: illegal input sequence at position 19
Source: pixelmed Version: 20200416-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=pixelmed=all=20200416-1=1596210399=0 ... # native2ascii -encoding UTF8 ApplicationEntityConfigurationDialog_el.utf-8_properties >ApplicationEntityConfigurationDialog_el.properties iconv -f UTF8 -t ascii//TRANSLIT ApplicationEntityConfigurationDialog_el.utf-8_properties >ApplicationEntityConfigurationDialog_el.properties iconv: illegal input sequence at position 19 make[3]: *** [../../../Makefile.common.mk:85: ApplicationEntityConfigurationDialog_el.properties] Error 1
Processed: tagging 957010
Processing commands for cont...@bugs.debian.org: > tags 957010 + fixed-upstream Bug #957010 [src:artha] artha: ftbfs with GCC-10 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 957010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
On Sat, Aug 01, 2020 at 01:52:41PM +0100, Steve McIntyre wrote:
> * Do we need to scan? if grub is installed and doing an upgrade and
>there is only one disk of an appropriate type (BIOS with DOS, or
>UEFI with GPT), then always install there?
Possibly. I'd still be inclined to have a scan as a guard-rail in that
case, since we'd need to have the code anyway, and the point is to try
to discover the disk that the system booted from so by definition it
must have GRUB there if it's to be valid.
> * (Maybe) we could add an option for grub-pc to always grub-install
>to *all* the BIOS-visible disks? Yes, I know there's a potential
>for breakage there with multi-boot systems. Maybe only do this on
>systems where os-prober has not found anything but the Debian
>installation?
One concern I have is filtering out things like optical drives, which
are BIOS-visible but not sensible grub-install targets. I'm also
slightly reluctant to add more invocations of os-prober while it's as
slow as it can sometimes be. I do see the utility of this though.
> * If we do add the code to scan boot sectors, maybe check all the
>BIOS-visible disks and flag any that look like they have GRUB, but
>are not our version? (Not sure how feasible this is without
>digging!)
Unfortunately I believe this to be essentially infeasible. As an
illustration, this is the scan code which exists in the current postinst
to support migration from GRUB Legacy, and believe me I didn't resort to
this horror before trying to find more sensible alternatives:
# In order to determine whether we accidentally ran grub-install without
# upgrade-from-grub-legacy on versions older than 1.98+20100617-1, we need
# to be able to scan a disk to determine whether GRUB 2 was installed in its
# boot sector. This is specific to i386-pc (but that's the only platform
# where we need it).
scan_grub2()
{
if ! dd if="$1" bs=512 count=1 2>/dev/null | grep -aq GRUB; then
# No version of GRUB is installed.
return 1
fi
# The GRUB boot sector always starts with a JMP instruction.
initial_jmp="$(dd if="$1" bs=2 count=1 2>/dev/null | od -Ax -tx1 | \
head -n1 | cut -d' ' -f2,3)"
[ "$initial_jmp" ] || return 1
initial_jmp_opcode="${initial_jmp%% *}"
[ "$initial_jmp_opcode" = eb ] || return 1
initial_jmp_operand="${initial_jmp#* }"
case $initial_jmp_operand in
47|4b|4c|63)
# I believe this covers all versions of GRUB 2 up to the package
# version where we gained a more explicit mechanism. GRUB Legacy
# always had 48 here.
return 0
;;
esac
return 1
}
The actual package version does get embedded in the boot loader, but
only in the "normal" module, not anywhere that could be usefully
discovered by a scan. Otherwise the best we could do would basically be
a big list of signatures, which I'm not enthusiastic about.
> * For UEFI, I'd love to switch to using the monolithic GRUB image
>even for non-signed use. It makes a lot of the issues go away if
>~all the modules necessary for boot are always built-in.
I think I agree, though we should take that to a separate bug; I'd like
to keep this one for the BIOS situation.
> * Finally, we should also stop using debconf as a registry like we
>are. It's annoying the DSA folks (at least). By all means use
>debconf to help manage things, but we should be storing the lasting
>config in a config file that people can edit. We already store some
>of our stuff in /etc/default/grub, let's push more of our config
>there?
Agreed in general terms; this has been on my to-do list for a long time.
Of course we need to consider the migration path carefully. In terms of
specifics, I'm not sure I want to extend /etc/default/grub for this,
though; that has configuration file management issues, and generally I
don't really want to overload the upstream grub-mkconfig configuration
file with packaging-specific things for grub-install. I'd be inclined
to go for /etc/default/grub-pc instead, or maybe something under
/etc/grub/.
--
Colin Watson (he/him) [cjwat...@debian.org]
Processed: tagging 957007
Processing commands for cont...@bugs.debian.org: > tags 957007 + patch Bug #957007 [src:arpack] arpack: ftbfs with GCC-10 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 957007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 957003 is forwarded to https://github.com/tobimensch/aqemu/issues/74
Processing commands for cont...@bugs.debian.org: > forwarded 957003 https://github.com/tobimensch/aqemu/issues/74 Bug #957003 [src:aqemu] aqemu: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://github.com/tobimensch/aqemu/issues/74'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957247: galculator: ftbfs with GCC-10
control: tags -1 patch
Hi, I've attached a patch.
I've also send PR for upstream.
https://github.com/galculator/galculator/pull/45
>From 501a9e3feeb2e56889c0ff98ab6d0ab20348ccd6 Mon Sep 17 00:00:00 2001
From: Kentaro Hayashi
Date: Sat, 1 Aug 2020 22:25:37 +0900
Subject: [PATCH] Fix multiple definition of `prefs` compile error with GCC-10
This commit fixes the following error:
libtool: link: gcc -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/workspace/galculator-2.1.4=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z -Wl,relro -o galculator galculator-main.o galculator-math_functions.o galculator-display.o galculator-general_functions.o galculator-calc_basic.o galculator-config_file.o galculator-callbacks.o galculator-ui.o galculator-flex_parser.o -Wl,--export-dynamic -Wl,--as-n
eeded -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lm -lquadmath -pthread
/usr/bin/ld: galculator-config_file.o:./src/config_file.c:42: multiple definition of `prefs'; galculator-main.o:./src/main.c:52: first defined here
collect2: error: ld returned 1 exit status
Signed-off-by: Kentaro Hayashi
---
src/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/main.c b/src/main.c
index 10d0868..d22fea0 100644
--- a/src/main.c
+++ b/src/main.c
@@ -49,7 +49,7 @@
#define MASK_NUMLOCK GDK_MOD2_MASK
-s_preferences prefs;
+extern s_preferences prefs;
s_current_status current_status = {0, 0, 0, 0, FALSE, FALSE, TRUE};
s_arraymemory;
s_constant *constant;
--
2.28.0
Processed: Re: galculator: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957247 [src:galculator] galculator: ftbfs with GCC-10 Added tag(s) patch. -- 957247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 966131
Processing commands for cont...@bugs.debian.org: > affects 966131 src:buildstream Bug #966131 [pylint] pylint: Requires old python3-isort (<<5) which won't be available in Debian Added indication that 966131 affects src:buildstream > thanks Stopping processing here. Please contact me if you need assistance. -- 966131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962197: marked as done (buildstream: Event loop broken on Python 3.8)
Your message dated Sat, 01 Aug 2020 13:18:26 + with message-id and subject line Bug#962197: fixed in buildstream 1.4.3-0.1 has caused the Debian Bug report #962197, regarding buildstream: Event loop broken on Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: buildstream Version: 1.4.1-1 Severity: grave Dear Maintainer, Un-cached builds with builstream currently fail like this: [--:--:--][][] BUG no running event loop Traceback (most recent call last): File "/usr/bin/bst", line 8, in sys.exit(cli()) File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/buildstream/_frontend/cli.py", line 173, in override_main original_main(self, args=args, prog_name=prog_name, complete_var=None, File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 27, in new_func return f(get_current_context().obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/buildstream/_frontend/cli.py", line 340, in build app.stream.build(elements, File "/usr/lib/python3/dist-packages/buildstream/_stream.py", line 211, in build self._run() File "/usr/lib/python3/dist-packages/buildstream/_stream.py", line 1022, in _run _, status = self._scheduler.run(self.queues) File "/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 153, in run self._sched() File "/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 427, in _sched self._sched_queue_jobs() File "/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 401, in _sched_queue_jobs self._spawn_job(job) File "/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 281, in _spawn_job job.spawn() File "/usr/lib/python3/dist-packages/buildstream/_scheduler/jobs/job.py", line 162, in spawn self._watcher.add_child_handler(self._process.pid, self._parent_child_completed) File "/usr/lib/python3.8/asyncio/unix_events.py", line 1293, in add_child_handler loop = events.get_running_loop() RuntimeError: no running event loop This was reported upstream as: https://gitlab.com/BuildStream/buildstream/-/issues/1246 but is now tracked in: https://gitlab.com/BuildStream/buildstream/-/issues/1173 Ben. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages buildstream depends on: ii python3 3.8.2-3 ii python3-buildstream 1.4.1-1 Versions of packages buildstream recommends: ii python3-bst-external 0.18.0-1 buildstream suggests no packages. -- no debconf information -- Ben Hutchings, Software Developer Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street Manchester, M1 2HF, United Kingdom --- End Message --- --- Begin Message --- Source: buildstream Source-Version: 1.4.3-0.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of buildstream, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated buildstream package) (This message was
Bug#962205: marked as done (buildstream: Missing dependency on bubblewrap)
Your message dated Sat, 01 Aug 2020 13:18:26 + with message-id and subject line Bug#962205: fixed in buildstream 1.4.3-0.1 has caused the Debian Bug report #962205, regarding buildstream: Missing dependency on bubblewrap 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.) -- 962205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: buildstream Version: 1.4.1-1 Severity: serious Dear Maintainer, bubblewrap is a run-time dependency for BuildStream on Linux, but is not included in the package dependencies. Ben. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF- 8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages buildstream depends on: ii python3 3.8.2-3 ii python3-buildstream 1.4.1-1 Versions of packages buildstream recommends: ii python3-bst-external 0.18.0-1 buildstream suggests no packages. -- no debconf information -- Ben Hutchings, Software Developer Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street Manchester, M1 2HF, United Kingdom --- End Message --- --- Begin Message --- Source: buildstream Source-Version: 1.4.3-0.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of buildstream, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated buildstream 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: Sat, 18 Jul 2020 10:03:58 +0300 Source: buildstream Architecture: source Version: 1.4.3-0.1 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers Changed-By: Adrian Bunk Closes: 962197 962205 Changes: buildstream (1.4.3-0.1) unstable; urgency=low . * Non-maintainer upload. * New upstream release. - Works with Python 3.8. (Closes: #962197) * Add the missing dependency on bubblewrap. (Closes: #962205) Checksums-Sha1: 6434120b3e244d7efa0ec27706c67c8c96a002cb 2642 buildstream_1.4.3-0.1.dsc 0489f154e229e7ec75f3d176e2279845096b3950 364024 buildstream_1.4.3.orig.tar.xz b6dd80a9e3fd474c2eaf609d13a46b10a3455506 5532 buildstream_1.4.3-0.1.debian.tar.xz Checksums-Sha256: 60f8d9c23dcf5e48c224d3a2cd9d36464e05de0c54a4e3a786328d9ce60a64a4 2642 buildstream_1.4.3-0.1.dsc a8d89952d97e78744c42f1577fa06935dc704707e7b391b65d820ef734d17ade 364024 buildstream_1.4.3.orig.tar.xz 923938fa233c33087e3997453f15b995b846ffb9215b81b65eaab5bacd883cf6 5532 buildstream_1.4.3-0.1.debian.tar.xz Files: d3542c09022f8e8a7599539de6cb189e 2642 gnome optional buildstream_1.4.3-0.1.dsc 73931e8cebd1fe593f3238f769bcaee3 364024 gnome optional buildstream_1.4.3.orig.tar.xz d0b1cfdae15e29c4d32a24fc938822e2 5532 gnome optional buildstream_1.4.3-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8SuXsACgkQiNJCh6LY mLH+eg/8DWUgMGYg1qCB7VkOnCVG0fCIwhbgQyKdAGnoOmyXVmBtwaVChMLbvGFi 8Zn01Vsry2KHKqkgnYibQdPNZMJob+xWWJKCOVLda5+N4oS+01nFCdsXJ2BqnBfX UbJo3u9neuDhwLcpAUj3whgRR43umSeiPlpzvM10R4CHG5pfKX4o6LlC8IWO2jhC pACV1Qfs5S/x4il9heVCU4bFlz/SBGNGdRmVghgpwOCSUinXVlgWZT6OAOZokWpb oy07PQMzk97gn/Ucf0hMqdDO3Ps4dMPwbJEqRzi8QGvmvHNN8mS2M5GRFQ05f/L9 tA0F1jSiU6Yz9clgzgjFvqwDCtvjvjj0uXTg/2AseZNWlcUyJKZAYgVauH2csaic R8hduhvKVJCrM0QOyvgxzG0tItZOPEgFMlmp1p98sY6nVjR+uedpGgn3srOgxJbI EMzh2zgiVcB2uq/nuQIvJ3gRGDtqa4Ca1tIqEMybgwqFxvOV9GyPo5Fz/eIBiKZ2 dDQfRXWXIe0AEdpOrgEDnmjKt+mShwsNdeZf7NseE7VcrKcmtrPYU9paQzVGPP5Y PhLb6gd7k/MRmPn7smuK7admkkkMN+dW6iiwU2g3B+n7I6WJyCbRyfH9GMNluDMY uFsz3mrv9tJCRzGKp8Q9nqmwoHhR1aoUZK70vXb5ksEZTdsmBGg= =MQOi -END PGP SIGNATURE End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 957642 fixed-upstream Bug #957642 [src:openrc] openrc: ftbfs with GCC-10 Added tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 957642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 949190 in 1.2.13-1
Processing commands for cont...@bugs.debian.org:
> fixed 949190 1.2.13-1
Bug #949190 {Done: Adrian Bunk } [src:fwupd] fwupd FTBFS since
August 2019
Marked as fixed in versions fwupd/1.2.13-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#957642: openrc: ftbfs with GCC-10
control tags -1 fixed-upstream Hi, It seems that this issue was already fixed in upstream. 0.42.1 was released from upstream - which is newer than packaged in Debian (0.42-1), but this fix is not included yet. so we need a patch to fix it. Here is the link to upstream fix. https://github.com/OpenRC/openrc/commit/375ef42393f3dc6edbaa2cb70c79b2366072db38 Regards, -- Kentaro Hayashi
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
On Fri, Jul 31, 2020 at 11:49:06PM +0100, Colin Watson wrote: ... >It looks like the base VM image provided by bento/debian-10 hardcodes >some details of how it was built that don't carry over to other systems >booting the same image, and this causes problems. > >debian/buster64 has a similar problem, but with different details. It >has: > > vagrant@buster:~$ sudo debconf-show grub-pc | grep grub-pc/install_devices: > * grub-pc/install_devices: /dev/vda Ah! >> I'm using the (admittedly insecure) solution of "sudo apt-mark hold grub*" >> shown here: https://askubuntu.com/a/1263204 > >As several comments there note, a better fix is "sudo dpkg-reconfigure >grub-pc". Definitely! >This is in some ways the most interesting subtype of this bug, because >it's one we can easily reproduce! It falls into the category of "error >in a cloning process"; but it also makes it relatively straightforward >to experiment with ways to mitigate the problem further. > >We could at minimum make this be an upgrade error in the noninteractive >case, ensuring that it doesn't touch modules if the target device is >just plain missing: the upgrade error might be a bit rough for some >people, but it would be better than a boot failure. > >A refinement of this might be that if the system only has one disk, and >that disk appears to have GRUB installed on it (by relatively crude boot >sector scanning), then we could assume that this is the common case of a >disk having been swapped out and automatically change >grub-pc/install_devices to point to that instead. With appropriate >guard rails, I think that could help quite a lot of the people affected >by this sort of problem. Yes, definitely. Let's have a chat about how to do stuff. I was thinking about some topics here: * Do we need to scan? if grub is installed and doing an upgrade and there is only one disk of an appropriate type (BIOS with DOS, or UEFI with GPT), then always install there? * (Maybe) we could add an option for grub-pc to always grub-install to *all* the BIOS-visible disks? Yes, I know there's a potential for breakage there with multi-boot systems. Maybe only do this on systems where os-prober has not found anything but the Debian installation? * If we do add the code to scan boot sectors, maybe check all the BIOS-visible disks and flag any that look like they have GRUB, but are not our version? (Not sure how feasible this is without digging!) * For UEFI, I'd love to switch to using the monolithic GRUB image even for non-signed use. It makes a lot of the issues go away if ~all the modules necessary for boot are always built-in. * Finally, we should also stop using debconf as a registry like we are. It's annoying the DSA folks (at least). By all means use debconf to help manage things, but we should be storing the lasting config in a config file that people can edit. We already store some of our stuff in /etc/default/grub, let's push more of our config there? -- Steve McIntyre, Cambridge, UK.st...@einval.com < sladen> I actually stayed in a hotel and arrived to find a post-it note stuck to the mini-bar saying "Paul: This fridge and fittings are the correct way around and do not need altering"
Bug#966664: marked as done (ERROR: libx11-dev-1.6.10-r0: trying to overwrite usr/include/X11/extensions/XKBgeom.h owned by xorgproto-2018.4-r0.)
Your message dated Sat, 1 Aug 2020 15:40:07 +0300 with message-id <20200801124007.GA20308@localhost> and subject line Re: Bug#94: ERROR: libx11-dev-1.6.10-r0: trying to overwrite usr/include/X11/extensions/XKBgeom.h owned by xorgproto-2018.4-r0. has caused the Debian Bug report #94, regarding ERROR: libx11-dev-1.6.10-r0: trying to overwrite usr/include/X11/extensions/XKBgeom.h owned by xorgproto-2018.4-r0. 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.) -- 94: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=94 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libx11-dev Version: 1.6.10-r0 Severity: serious Justification: fails to install Hi When trying to install libx11-dev, I get the following error: (80/129) Installing libx11-dev (1.6.10-r0) ERROR: libx11-dev-1.6.10-r0: trying to overwrite usr/include/X11/extensions/XKBgeom.h owned by xorgproto-2018.4-r0. Regards, Jervy --- End Message --- --- Begin Message --- On Sat, Aug 01, 2020 at 07:55:39PM +0800, jervy escoto wrote: > Package: libx11-dev > Version: 1.6.10-r0 > Severity: serious > Justification: fails to install > > Hi > > When trying to install libx11-dev, I get the following error: > > (80/129) Installing libx11-dev (1.6.10-r0) > ERROR: libx11-dev-1.6.10-r0: trying to overwrite > usr/include/X11/extensions/XKBgeom.h owned by xorgproto-2018.4-r0. 1.6.10-r0 is not the version of a package in Debian. > Regards, > Jervy cu Adrian--- End Message ---
Bug#966428: marked as done (sbuild autopkg test fails with dpkg 1.20.x)
Your message dated Sat, 01 Aug 2020 12:37:57 + with message-id and subject line Bug#966428: fixed in sbuild 0.80.0 has caused the Debian Bug report #966428, regarding sbuild autopkg test fails with dpkg 1.20.x 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.) -- 966428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src_sbuild Version: 0.79.1-1 Severity: serious Tags: sid bullseye patch The sbuild autopkg test fails with dpkg 1.20.x, preventing migration of dpkg. patch at http://launchpadlibrarian.net/490472280/sbuild_0.79.1-1ubuntu1_0.79.1-1ubuntu2.diff.gz --- End Message --- --- Begin Message --- Source: sbuild Source-Version: 0.80.0 Done: Johannes 'josch' Schauer We believe that the bug you reported is fixed in the latest version of sbuild, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes 'josch' Schauer (supplier of updated sbuild 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: Sat, 01 Aug 2020 14:07:53 +0200 Source: sbuild Architecture: source Version: 0.80.0 Distribution: unstable Urgency: medium Maintainer: sbuild maintainers Changed-By: Johannes 'josch' Schauer Closes: 884428 891247 917849 924500 947755 948799 950684 950939 961623 963845 966428 Changes: sbuild (0.80.0) unstable; urgency=medium . [ Johannes 'josch' Schauer ] * New release * Convert packaging to a native package to make maintenance easier by avoiding the complicated upstream release and debian packaging procedure * lib/Sbuild/Conf.pm: fix example for individual_stalled_pkg_timeout (closes: #924500) * man/sbuild.1.in: remove from docs of --autopkgtest-virt-server-opts (closes: #948799) * lib/Sbuild/Build.pm: check for defined-ness and even print a '0' Version (closes: #950939) * debian/control: due to using Dpkg::Build::Info::get_build_env_allowed, we now require libdpkg-perl (>= 1.20) * man/sbuild.1.in: starting/finished/failed-build-commands are run as root (closes: #961623) * bin/sbuild-createchroot: chown root dir 0755 (closes: #950684) * use Dpkg::Build::Info::get_build_env_allowed instead of deprecated Dpkg::Build::Info::get_build_env_whitelist for dpkg >= 1.20.0 (closes: #963845, #966428) . [ Pierre-Elliott Bécue ] * Workaround to pass on dpkg-genchanges specific options until dpkg bug #902856 is fixed (closes: #884428, #891247, #917849, #947755) Checksums-Sha1: e65f86a736ec44121709b786bbbcd0c3e0066240 2303 sbuild_0.80.0.dsc 0214f15d1cdc5f62be6f2734ad9db8fb9b38f9d6 242360 sbuild_0.80.0.tar.xz Checksums-Sha256: 86055ed3392c582b5dd68bad762b28db2b29d403d8076cee3bf62e68a7b08a7c 2303 sbuild_0.80.0.dsc 02a0be8d3b8857b37891e819ba2bebf1f2eacd0d22c517a6e2fbe227e5e909c3 242360 sbuild_0.80.0.tar.xz Files: 16ffa4750379d17c7e1064c0574d0f9e 2303 devel optional sbuild_0.80.0.dsc 18b446c6380fbbeabf0d6b9a1bbb4950 242360 devel optional sbuild_0.80.0.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAl8lW2YACgkQ8sulx4+9 g+GrnBAAg2wloumeQxODF5ReyATZeYFCJSrDQ2uoEtYRxsbU7jIhUJC8XFg9c/Hg 36BcSgi39XLx4K6cN1e+MP25rcGxg8iMCCjqgWc/CcOuzSmyHdhN8ikVo1ZTy4ry a2Clrha+USjaA2lTdsI5Zbia+znsXdZafW6foJ28flZ3WhxexHwZggIcPkOrscTp CFGg0vfAF4aPtNLuSpNMr6soRaEGk0JLzid6yL7BsUy/pUx9WyIx2eVNQFHpJnze 5TbOY9Qo8gmco6xfzousXxXH+IeK1G8sNd1s0XQQLMQX0TC9bnSo3EURj8aeBCR7 JjKOcFeUy5mHU5px589LrCL8ji2wvwdV46AxfkOHJrco6yG6u+RyLEnrI0wg3Abb 79klD+TUw5dSxipJdQP4hhyi3u8ghZvUnKz4X+4zV9WsMm4C9Ay9cy0v3sT7UIHc NV5gZVWbRKc8w4LnDpfxigjDwT0rZSMj7RveHZh0LHRzQT8zAz5bhlzBvGoQJ83G TIdB2bTtnMewt8VRhv9kNYagpD52DDkXJ82e2pEP182IazJcdavoWHRc9++YsdGx pIgsN/SZUP03W5qsy7D85yt5O6ALNq+UjiCz3bJPTkEaukEvRUfNdF9dFrPWHepy 9ORzProXMA1+3SJxFWSclU2Knstn47OUvN1ng4epqFkdShLGicI= =k604 -END PGP SIGNATURE End Message ---
Processed: tagging 966659
Processing commands for cont...@bugs.debian.org: > tags 966659 + bullseye sid Bug #966659 [libghc-monad-gen-doc] libghc-monad-gen-doc: Depends on missing haddock-interface-33 Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 966659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
On Sat, Aug 01, 2020 at 01:32:33PM +0200, Miklos Quartus wrote: > I am reporting this bug here Please could you file this as a *new* bug report, *not* as a followup to #966575 which I would much rather keep for just the more common BIOS case? Ideally you would do this by typing "reportbug grub-efi-amd64" and following the prompts from there; this will automatically include some more information about your system that you haven't yet provided. If reportbug doesn't work for some reason, you can send email to sub...@bugs.debian.org with this paragraph at the top of your email: Package: grub-efi-amd64 Version: 2.02+dfsg1-20+deb10u2 ... and we can ask for more information from there. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#966664: ERROR: libx11-dev-1.6.10-r0: trying to overwrite usr/include/X11/extensions/XKBgeom.h owned by xorgproto-2018.4-r0.
Package: libx11-dev Version: 1.6.10-r0 Severity: serious Justification: fails to install Hi When trying to install libx11-dev, I get the following error: (80/129) Installing libx11-dev (1.6.10-r0) ERROR: libx11-dev-1.6.10-r0: trying to overwrite usr/include/X11/extensions/XKBgeom.h owned by xorgproto-2018.4-r0. Regards, Jervy
Bug#943394: marked as done (libkeduvocdocument FTBFS: symbol errors)
Your message dated Sat, 01 Aug 2020 11:40:44 + with message-id and subject line Bug#943394: fixed in libkeduvocdocument 4:20.04.3-1 has caused the Debian Bug report #943394, regarding libkeduvocdocument FTBFS: symbol errors 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.) -- 943394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libkeduvocdocument Version: 4:17.08.3-1 Severity: serious Tags: ftbfs libkeduvocdocument fails to build from source in unstable when using sbuild natively on amd64. A log ends with: | dh_makeshlibs '-Xusr/lib/libkdeinit5_*' | dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below | dpkg-gensymbols: warning: debian/libkeduvocdocument5/DEBIAN/symbols doesn't match completely debian/libkeduvocdocument5.symbols | --- debian/libkeduvocdocument5.symbols (libkeduvocdocument5_4:17.08.3-1_amd64) | +++ dpkg-gensymbolsBsVKoI 2019-10-24 10:41:15.691855166 + | @@ -339,21 +339,21 @@ | _ZNK22KEduVocPersonalPronoun15personalPronounE6QFlagsIN15KEduVocWordFlag5FlagsEE@Base 14.11.95 | _ZNK22KEduVocPersonalPronoun19maleFemaleDifferentEv@Base 14.11.95 | _ZNK22KEduVocPersonalPronouneqERKS_@Base 14.11.95 | - _ZTI10KFilterDev@Base 4:16.08.0 | +#MISSING: 4:17.08.3-1# _ZTI10KFilterDev@Base 4:16.08.0 | _ZTI13KEduVocLesson@Base 14.11.95 | _ZTI15KEduVocDocument@Base 14.11.95 | _ZTI15KEduVocWordType@Base 14.11.95 | _ZTI16KEduVocContainer@Base 14.11.95 | _ZTI16QXmlStreamReader@Base 14.11.95 | _ZTI17KEduVocLeitnerBox@Base 14.11.95 | - _ZTS10KFilterDev@Base 4:16.08.0 | +#MISSING: 4:17.08.3-1# _ZTS10KFilterDev@Base 4:16.08.0 | _ZTS13KEduVocLesson@Base 14.11.95 | _ZTS15KEduVocDocument@Base 14.11.95 | _ZTS15KEduVocWordType@Base 14.11.95 | _ZTS16KEduVocContainer@Base 14.11.95 | _ZTS16QXmlStreamReader@Base 14.11.95 | _ZTS17KEduVocLeitnerBox@Base 14.11.95 | - _ZTV10KFilterDev@Base 4:16.08.0 | +#MISSING: 4:17.08.3-1# _ZTV10KFilterDev@Base 4:16.08.0 | _ZTV13KEduVocLesson@Base 14.11.95 | _ZTV15KEduVocDocument@Base 14.11.95 | _ZTV15KEduVocWordType@Base 14.11.95 | dh_makeshlibs: failing due to earlier errors | make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: pre_binary_dh_makeshlibs] Error 255 | make[1]: Leaving directory '/<>' | make: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: debian/dhmk_binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 The failure is also reproduced by reproducible builds https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libkeduvocdocument_17.08.3-1.rbuild.log.gz as well as crossqa.debian.net: http://crossqa.debian.net/build/libkeduvocdocument_4:17.08.3-1_ppc64el_20190922053217.log It appears to affect any architecture (at least amd64, arm64, ppc64el). Helmut --- End Message --- --- Begin Message --- Source: libkeduvocdocument Source-Version: 4:20.04.3-1 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of libkeduvocdocument, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated libkeduvocdocument 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: Sat, 01 Aug 2020 11:39:43 +0200 Source: libkeduvocdocument Architecture: source Version: 4:20.04.3-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 943394 960714 Changes: libkeduvocdocument (4:20.04.3-1) unstable; urgency=medium . * Team upload. * New upstream release. * Switch Vcs-* fields to salsa.debian.org. * Bump Standards-Version to 4.5.0, no changes required. * Update the build dependencies according to the upstream build system: - bump cmake to 3.5.0 - explicitly add gettext * Bump the debhelper compatibility to 12: - switch the debhelper build dependency to debhelper-compat 12 - remove debian/compat * Drop the migration from
Bug#960714: marked as done (libkeduvocdocument: autopkgtest failure: kdeinit5: not found)
Your message dated Sat, 01 Aug 2020 11:40:44 + with message-id and subject line Bug#960714: fixed in libkeduvocdocument 4:20.04.3-1 has caused the Debian Bug report #960714, regarding libkeduvocdocument: autopkgtest failure: kdeinit5: not found 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.) -- 960714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libkeduvocdocument Version: 4:17.08.3-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? You seem to be missing a test dependency. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkeduvocdocument/5496019/log.gz autopkgtest [18:12:57]: test testsuite: [--- debian/tests/testsuite.xsession: 4: kdeinit5: not found dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/tests/testsuite.xsession: 1: kdeinit5_shutdown: not found autopkgtest [18:12:58]: test testsuite: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libkeduvocdocument Source-Version: 4:20.04.3-1 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of libkeduvocdocument, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated libkeduvocdocument 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: Sat, 01 Aug 2020 11:39:43 +0200 Source: libkeduvocdocument Architecture: source Version: 4:20.04.3-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 943394 960714 Changes: libkeduvocdocument (4:20.04.3-1) unstable; urgency=medium . * Team upload. * New upstream release. * Switch Vcs-* fields to salsa.debian.org. * Bump Standards-Version to 4.5.0, no changes required. * Update the build dependencies according to the upstream build system: - bump cmake to 3.5.0 - explicitly add gettext * Bump the debhelper compatibility to 12: - switch the debhelper build dependency to debhelper-compat 12 - remove debian/compat * Drop the migration from libkeduvocdocument-dbg, no more needed after two Debian stable releases. * Stop using library-packages.mk, as there is only one library package. * Update symbols file. (Closes: #943394) * Pass -DBUILD_TESTING=OFF to cmake to disable the build of tests, as they are not run at build time anyway. * Drop the 'testsuite' autopkgtest, as it does not test the installed packages. (Closes: #960714) * Update watch file to the new release-service location. * Avoid a small ABI break; patch revert-abi-change.diff. * Switch from dhmk to the dh sequencer: - invoke the dh sequencer using the kf5, and pkgkde_symbolshelper addons - call the right debhelper command instead of $(overridden_command) - manually force the generation of the substvars for the kde-l10n breaks * Add the configuration for the CI on salsa. * Add Rules-Requires-Root: no. * Drop the leftovers of the unused 'acc' autopkgtest. * Mark libkeduvocdocument5 as Multi-Arch: same. Checksums-Sha1: 04f2bed1af939746be943ba30524a23d6e583ceb 2590 libkeduvocdocument_20.04.3-1.dsc 84ff411699ab481a0eca3acf653c6d60c02ad3d9 206876 libkeduvocdocument_20.04.3.orig.tar.xz a34e70aed7a049580252b90ae7963f3555c7670c 488 libkeduvocdocument_20.04.3.orig.tar.xz.asc c9be88cc8723bcac822843b06387e7c53ff0e32b 13496 libkeduvocdocument_20.04.3-1.debian.tar.xz 7450f06ee2875f6e334524d71cfecd70635230a2 14279
Bug#964844: marked as done (haskell-cborg: FTBFS on i386)
Your message dated Sat, 01 Aug 2020 11:38:16 + with message-id and subject line Bug#964844: fixed in haskell-cborg 0.2.3.0-3 has caused the Debian Bug report #964844, regarding haskell-cborg: FTBFS on i386 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.) -- 964844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-cborg Version: 0.2.3.0-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) The package failed to build on i386: | pre-encoded | single term, same bytes: OK | +++ OK, passed 100 tests. | single term, same tokens: FAIL (0.01s) | *** Failed! Exception: 'toFlatTerm: encodePreEncoded used with invalid CBOR: DeserialiseFailure 0 "expected tag"' (after 55 tests and 46 shrinks): | TTagged 4294967296 (TStringI "") | Use --quickcheck-replay=612406 to reproduce. | list terms, same bytes: OK (0.53s) | +++ OK, passed 100 tests. | list terms, same tokens: FAIL | *** Failed! Exception: 'toFlatTerm: encodePreEncoded used with invalid CBOR: DeserialiseFailure 0 "expected tag"' (after 18 tests and 46 shrinks): | [(TTagged 4294967296 (TSimple 0),True)] | Use --quickcheck-replay=406779 to reproduce. | | 2 out of 262 tests failed (1.55s) | Test suite tests: FAIL See https://buildd.debian.org/status/fetch.php?pkg=haskell-cborg=i386=0.2.3.0-1=1594060794=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: haskell-cborg Source-Version: 0.2.3.0-3 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-cborg, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-cborg 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: Sat, 01 Aug 2020 12:32:53 +0300 Source: haskell-cborg Architecture: source Version: 0.2.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 964844 Changes: haskell-cborg (0.2.3.0-3) unstable; urgency=medium . * Apply patch to fix FTBFS on 32-bit systems (Closes: #964844) Checksums-Sha1: 1268347e4e99cd1e3de050cf5a3f20ce9bf64400 2755 haskell-cborg_0.2.3.0-3.dsc 18a49336510b098ca8d7b411753fba00baef0c68 3088 haskell-cborg_0.2.3.0-3.debian.tar.xz 316e9d9a0243e0b6b3ffb2cd782c35cdae7fc0d9 5562 haskell-cborg_0.2.3.0-3_source.buildinfo Checksums-Sha256: 0a0d2400ed03804b1bd71239e579880ad98174ae0440ac0445a85b0335ab52bd 2755 haskell-cborg_0.2.3.0-3.dsc c7c4b407fc259b1cf286ae5a84569fc2dd0342976659d3e742b3892a7d638e3d 3088 haskell-cborg_0.2.3.0-3.debian.tar.xz a331e3034e2c0f18b5bb296cc0f9e5f022445e9e4bc1812cc157be5fa92c21ca 5562 haskell-cborg_0.2.3.0-3_source.buildinfo Files: 2d8df4532c63e61be00528e11a6eeb56 2755 haskell optional haskell-cborg_0.2.3.0-3.dsc 8cc7697bbaa3b201077203422922af2d 3088 haskell optional haskell-cborg_0.2.3.0-3.debian.tar.xz e096b0bc7e7a7f22c32e6a094ba61992 5562 haskell optional haskell-cborg_0.2.3.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl8lO6MUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDxsXhAAwcsj1SZiJQj8Pi15P02Nx3VhsTHM HnNwDOFVaUzZ9P8Rwk0GPgzsnBKIbmnsYXwhR1UOwreC2RbSm3GOsORgnuHMYuYh Ag8HaKc/CEA2HrSc7+y3nRHVsZDHwQ3PaOyCxycAQL4LiEawrSFxMHKPZUleLsMs i7A30/mcn+h7ckUZzZBg0d/uanmjpcFCIQzRytYwr/tDBXRXNLOsIIGZwO4jZZAX wswN7BtOWtiv9R+4P6tRyki+ZVmEca2hZVtxSUqRoMKIRUrXAau54amA3J49yC0Q bC9ppHew+cf3bSRXGiTjHsOXwoBxRxroqO3SmtIQt3mSfjKyalsAg3UHer0uZuOu qYbbfLHmicC1W35X7XX2TJVoZN5KL1LKJKvjR2mljG1JwlQ2o3NnjdWy63aKHxbi P1USjyagwkmvNfXq+L+AaF2BmvqHInLxdUVXzQ42ucWgBvhEM+f8Y6E1p3sdY6du
Processed: syslinux GCC-10 patch (help/review requested)
Processing control commands: > tags -1 + patch Bug #957858 [src:syslinux] syslinux: ftbfs with GCC-10 Added tag(s) patch. -- 957858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966662: libghc-curry-base-doc: Depends on missing haddock-interface-33
Package: libghc-curry-base-doc Version: 1.1.1-2 Severity: grave Justification: renders package unusable Dear maintainer, This package should be rebuild against the latest ghc (8.8.3) available on unstable. Thanks, -- Ilias
Bug#966661: libghc-propellor-doc: Depends on missing haddock-interface-33
Package: libghc-propellor-doc Version: 5.10.2-1 Severity: grave Justification: renders package unusable Dear maintainer, This package should be rebuild against the latest ghc (8.8.3) available on unstable. Thanks, -- Ilias
Bug#966659: libghc-monad-gen-doc: Depends on missing haddock-interface-33
Package: libghc-monad-gen-doc Version: 0.3.0.1-1 Severity: grave Justification: renders package unusable This package should be rebuild against the latest ghc (8.8.3) available on unstable. Alternatively, since this package looks unmaintained (last upstream upload at 2014), is not part of Stackage and has no rev dependencies, we may consider removing it. Thanks, -- Ilias
Bug#956975: Removing acfax (acfax: ftbfs with GCC-10)
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: severity -2 normal Control: retitle -2 RM: acfax -- RoM: obsolete and buggy Re: To 956...@bugs.debian.org > I believe acfax has long reached the end of its usefulness. The build > log is full of ugly warnings, the last upstream release was in 1998, > the Debian release number has reached an impressive -17, and the > program doesn't even start because it wants to open /dev/dsp which is > long gone. > > I suspect qsstv is a modern replacement, but I'm not an active > fax/sstv user so can't say for sure. > > I'll request removal from unstable shortly if I don't get any > objections. Doing so now: Please remove acfax from unstable. Thanks, Christoph
Processed: Re: Bug#956975: Removing acfax (acfax: ftbfs with GCC-10)
Processing control commands: > clone -1 -2 Bug #956975 [src:acfax] acfax: ftbfs with GCC-10 Bug 956975 cloned as bug 966658 > reassign -2 ftp.debian.org Bug #966658 [src:acfax] acfax: ftbfs with GCC-10 Bug reassigned from package 'src:acfax' to 'ftp.debian.org'. No longer marked as found in versions acfax/981011-17. Ignoring request to alter fixed versions of bug #966658 to the same values previously set > severity -2 normal Bug #966658 [ftp.debian.org] acfax: ftbfs with GCC-10 Severity set to 'normal' from 'serious' > retitle -2 RM: acfax -- RoM: obsolete and buggy Bug #966658 [ftp.debian.org] acfax: ftbfs with GCC-10 Changed Bug title to 'RM: acfax -- RoM: obsolete and buggy' from 'acfax: ftbfs with GCC-10'. -- 956975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956975 966658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#965057: transition: libgc
Processing control commands: > block -1 by 966300 966301 Bug #965057 [release.debian.org] transition: libgc 965057 was blocked by: 961230 957517 961295 961280 965054 965057 was not blocking any bugs. Added blocking bug(s) of 965057: 966300 and 966301 -- 965057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#963338: sagemath: FTBFS: RuntimeError: Aborted
Processing control commands: > tags 963338 + help Bug #963338 [src:sagemath] sagemath: FTBFS: RuntimeError: Aborted Added tag(s) help. -- 963338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963338: sagemath: FTBFS: RuntimeError: Aborted
Control: tags 963338 + help Just yesterday I just did a test build of vanilla sage (not the Debian package) 9.2.beta6 with the python 3.8 patch from [1] and Debian's python 3.8 to see if the file handle leak that happens during parallel builds of the Debian package also happens there. It didn't. I don't know how to debug this. Best, Tobias [1] https://trac.sagemath.org/ticket/27754 On 8/1/20 10:43 AM, Jerome BENOIT wrote: > Thanks for the report. Meanwhile the Sagemath Debian team take a summer > break. Cheers, Jerome
Processed: forward
Processing commands for cont...@bugs.debian.org: > forwarded 961438 https://github.com/silnrsi/grcompiler/issues/32 Bug #961438 [src:grcompiler] grcompiler FTBFS on i386: compare_PigLatinTest_v2 failed Set Bug forwarded-to-address to 'https://github.com/silnrsi/grcompiler/issues/32'. > End of message, stopping processing here. Please contact me if you need assistance. -- 961438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
Hello, My case was indeed a disk switch from USB to internal. I probably had invoked directly grub-install (dunno if it'd make sense to warn about the mismatch with debconf there?), now I know I should rather use dpkg-reconfigure instead. # debconf-get-selections |grep 'grub-pc/install_devices' grub-pc grub-pc/install_devices_disks_changed multiselect /dev/disk/by-id/usb-KINGSTON_SA400S37240G_AB12362D-0:0 grub-pc grub-pc/install_devices_failed_upgrade boolean true grub-pc grub-pc/install_devices_failed boolean false grub-pc grub-pc/install_devices_empty boolean false grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/usb-KINGSTON_SA400S37240G_AB12362D-0:0 # ls /dev/disk/by-id/usb-KINGSTON_SA400S37240G_AB12362D-0:0 ls: impossible d'accéder à '/dev/disk/by-id/usb-KINGSTON_SA400S37240G_AB12362D-0:0': Aucun fichier ou dossier de ce type # ls /dev/disk/by-id/ata-KINGSTON_SA400S37240G_50026B7683315755 /dev/disk/by-id/ata-KINGSTON_SA400S37240G_50026B7683315755@ # dpkg-reconfigure grub-pc # debconf-get-selections |grep 'grub-pc/install_devices' grub-pc grub-pc/install_devices_failed boolean false grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/ata-KINGSTON_SA400S37240G_50026B7683315755 grub-pc grub-pc/install_devices_disks_changed multiselect /dev/disk/by-id/ata-KINGSTON_SA400S37240G_50026B7683315755 grub-pc grub-pc/install_devices_empty boolean false grub-pc grub-pc/install_devices_failed_upgrade boolean true Thanks for the explanations!
Processed: tagging 943394, tagging 960714
Processing commands for cont...@bugs.debian.org: > tags 943394 + pending Bug #943394 [src:libkeduvocdocument] libkeduvocdocument FTBFS: symbol errors Added tag(s) pending. > tags 960714 + pending Bug #960714 [src:libkeduvocdocument] libkeduvocdocument: autopkgtest failure: kdeinit5: not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 943394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943394 960714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forward grcompiler FTBFS on big endian
Processing commands for cont...@bugs.debian.org: > forwarded 961445 https://github.com/silnrsi/grcompiler/issues/31 Bug #961445 [src:grcompiler] grcompiler FTBFS on big endian Set Bug forwarded-to-address to 'https://github.com/silnrsi/grcompiler/issues/31'. > End of message, stopping processing here. Please contact me if you need assistance. -- 961445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966655: [Debian-med-packaging] Bug#966655: orthanc: using tzdata but missing dependency on it?
Hello, Thanks for your report. Unfortunately, as long as orthanc-1.7.2+dfsg-2 is pending in the NEW queue [1], no further patch can be applied. Kind Regards, Sébastien- [1] https://ftp-master.debian.org/new.html On 1/08/20 11:08, Gianfranco Costamagna wrote: > Source: orthanc > Version: 1.7.2+dfsg-1 > Severity: serious > tags: patch > > Hello, looks like orthanc fails to build from source (testsuite error) when > tzdata is not installed in the chroot. > > I'm not sure if this is an essential package or not, but looks like it can be > removed, or not be available on some chroots > > > this is an example of failure > > mkdir -p /<>/debian/tmp/locale/ > localedef -f UTF-8 -i en_US /<>/debian/tmp/locale/en_US.UTF-8/ > ( cd Build; LOCPATH=/<>/debian/tmp/locale/ ./UnitTests ) > E0731 17:53:29.829350 OrthancException.h:76] Internal error: On UNIX-like > systems, the file /etc/localtime must be present on the filesystem (install > "tzdata" package on Debian) > terminate called after throwing an instance of 'Orthanc::OrthancException' > Aborted (core dumped) > make[1]: *** [debian/rules:73: override_dh_auto_test] Error 134 > > > I think adding it as explicit dependency might solve some headaches. > > G.
Bug#966655: orthanc: using tzdata but missing dependency on it?
Source: orthanc Version: 1.7.2+dfsg-1 Severity: serious tags: patch Hello, looks like orthanc fails to build from source (testsuite error) when tzdata is not installed in the chroot. I'm not sure if this is an essential package or not, but looks like it can be removed, or not be available on some chroots this is an example of failure mkdir -p /<>/debian/tmp/locale/ localedef -f UTF-8 -i en_US /<>/debian/tmp/locale/en_US.UTF-8/ ( cd Build; LOCPATH=/<>/debian/tmp/locale/ ./UnitTests ) E0731 17:53:29.829350 OrthancException.h:76] Internal error: On UNIX-like systems, the file /etc/localtime must be present on the filesystem (install "tzdata" package on Debian) terminate called after throwing an instance of 'Orthanc::OrthancException' Aborted (core dumped) make[1]: *** [debian/rules:73: override_dh_auto_test] Error 134 I think adding it as explicit dependency might solve some headaches. G.
Bug#963338: sagemath: FTBFS: RuntimeError: Aborted
Thanks for the report. Meanwhile the Sagemath Debian team take a summer break. Cheers, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B signature.asc Description: OpenPGP digital signature
Bug#957563: mpg321: ftbfs with GCC-10
NMU uploaded to delayed/10. Basically mpg321_common.diff plus an additional fix for another FTBFS related to circular build dependencies. Updated diff attached. Best regards, Joachim diff -Nru mpg321-0.3.2/debian/changelog mpg321-0.3.2/debian/changelog --- mpg321-0.3.2/debian/changelog 2019-03-13 15:59:02.0 +0100 +++ mpg321-0.3.2/debian/changelog 2020-07-23 17:22:42.0 +0200 @@ -1,3 +1,15 @@ +mpg321 (0.3.2-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Export CFLAGS to make them take effect. + * Add -Wno-error=format-security to CFLAGS to disable the default from +dpkg-buildflags as workaround for some build error. + * Add -fcommon to CFLAGS (Closes: #957563). + * Remove circular build dependencies around build-stamp which make the +package FTBFS in clean environments. + + -- Joachim Reichel Thu, 23 Jul 2020 17:22:42 +0200 + mpg321 (0.3.2-3) unstable; urgency=medium * Fix compilation error diff -Nru mpg321-0.3.2/debian/rules mpg321-0.3.2/debian/rules --- mpg321-0.3.2/debian/rules 2012-05-01 08:53:43.0 +0200 +++ mpg321-0.3.2/debian/rules 2020-07-23 17:22:42.0 +0200 @@ -4,7 +4,7 @@ #export DH_VERBOSE=1 -CFLAGS = $(shell dpkg-buildflags --get CFLAGS) -Wall -Wunused +export CFLAGS = $(shell dpkg-buildflags --get CFLAGS) -Wall -Wunused -Wno-error=format-security -fcommon MPG321_ARCH = $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS) @@ -24,15 +24,14 @@ endif touch configure-stamp -build: configure-stamp build-arch build-indep -build-arch: build-stamp -build-indep: build-stamp -build-stamp: build install +build: build-arch build-indep +build-arch: configure-stamp +build-indep: configure-stamp clean: dh_testdir dh_testroot - rm -f build-stamp configure-stamp + rm -f configure-stamp # Add here commands to clean up after the build process. [ ! -f Makefile ] || $(MAKE) distclean
Bug#966654: libgpiod: symbol mismatches with gcc-10/O3 optimization
Source: libgpiod Version: 1.5.1-1 Severity: serious tags: patch Hello, looks like some symbols are disappearing when built with -O3 optimization level, and some other changed in armhf and ppc64el (probably due to gcc-10) the following patch seems to be enough to make everybody happy, by making some symbols optional. thanks for considering it G. --- libgpiod-1.5.1/debian/changelog 2020-07-01 05:27:41.0 +0200 +++ libgpiod-1.5.1/debian/changelog 2020-07-31 20:08:33.0 +0200 @@ -1,3 +1,9 @@ +libgpiod (1.5.1-1.1) unstable; urgency=medium + + * Refresh symbols (Closes: #-1) + + -- Gianfranco Costamagna Fri, 31 Jul 2020 20:08:33 +0200 + libgpiod (1.5.1-1) unstable; urgency=medium * Import new upstream release diff -Nru libgpiod-1.5.1/debian/libgpiod2.symbols libgpiod-1.5.1/debian/libgpiod2.symbols --- libgpiod-1.5.1/debian/libgpiod2.symbols 2020-07-01 05:27:19.0 +0200 +++ libgpiod-1.5.1/debian/libgpiod2.symbols 2020-07-31 20:08:33.0 +0200 @@ -99,6 +99,8 @@ gpiod_line_update@Base 1.1 gpiod_version_string@Base 1.1 libgpiodcxx.so.1 libgpiod2 #MINVER# + (c++|optional)"std::_Function_base::~_Function_base()@Base" 1.5.1 + (c++|optional)"std::_Function_base::~_Function_base()@Base" 1.5.1 (c++)"gpiod::line_request::FLAG_ACTIVE_LOW@Base" 1.1 (c++)"gpiod::line_request::FLAG_OPEN_DRAIN@Base" 1.1 (c++)"gpiod::line_request::FLAG_OPEN_SOURCE@Base" 1.1 @@ -209,7 +211,7 @@ (c++)"std::system_error::system_error(int, std::_V2::error_category const&, std::__cxx11::basic_string, std::allocator > const&)@Base" 1.1 (c++)"std::system_error::system_error(std::error_code, char const*)@Base" 1.1 (c++)"std::system_error::system_error(int, std::_V2::error_category const&, std::__cxx11::basic_string, std::allocator > const&)@Base" 1.1 - (c++)"std::_Function_base::_Base_manager, std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data const&, std::_Manager_operation)@Base" 1.1 + (c++|optional)"std::_Function_base::_Base_manager, std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data const&, std::_Manager_operation)@Base" 1.1 (c++|arch= !armel !riscv64)"std::_Sp_counted_ptr::_M_dispose()@Base" 1.1 (c++|arch= !armel !riscv64)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_destroy()@Base" 1.1 (c++)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()@Base" 1.4.1 @@ -219,8 +221,8 @@ (c++|optional|arch-bits=32)"std::vector >::_M_default_append(unsigned int)@Base" 1.5.1 (c++|optional)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char const*, char const*, std::forward_iterator_tag)@Base" 1.1 (c++|optional)"std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_get_insert_unique_pos(int const&)@Base" 1.1 - (c++|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, int const&)@Base" 1.1 - (c++)"std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_erase(std::_Rb_tree_node >*)@Base" 1.1 + (c++|optional|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, int const&)@Base" 1.1 + (c++|optional)"std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_erase(std::_Rb_tree_node >*)@Base" 1.1 (c++|arch= !armel !riscv64)"typeinfo for std::_Mutex_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.1 (c++|arch= !armel !riscv64)"typeinfo for std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.1 (c++|arch= !armel !riscv64)"typeinfo name for std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.4 @@ -235,6 +237,6 @@ (c++|arch= armel riscv64)"typeinfo name for __gnu_cxx::__mutex@Base" 1.2 (c++|arch= armel riscv64)"typeinfo name for std::_Mutex_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2 (c++|arch= armel riscv64)"typeinfo name for std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2 - (c++|arch= i386 armel mipsel armhf s390x)"std::map, std::allocator > >::map(std::initializer_list >, std::less const&, std::allocator > const&)@Base" 1.3 + (c++|optional|arch= i386 armel mipsel armhf s390x)"std::map, std::allocator > >::map(std::initializer_list >, std::less const&, std::allocator > const&)@Base" 1.3 (c++|arch= !armel !riscv64)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()@Base" 1.4.1 (c++|arch= !armel !riscv64)"typeinfo name for std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.4.1
Processed: retitle 966599 to snmpd: Elevation of Privileges due to symlink handling (CVE-2020-15861)
Processing commands for cont...@bugs.debian.org:
> retitle 966599 snmpd: Elevation of Privileges due to symlink handling
> (CVE-2020-15861)
Bug #966599 {Done: Craig Small } [snmpd] snmpd: Elevation of
Privileges due to symlink handling
Changed Bug title to 'snmpd: Elevation of Privileges due to symlink handling
(CVE-2020-15861)' from 'snmpd: Elevation of Privileges due to symlink handling'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966651: libgc-dev: missing dependency on libatomic-ops-dev
Package: libgc-dev
Version: 1:8.0.4-1
Severity: serious
Justification: undeclared dependency
Tags: patch
bdw-gc.pc includes -latomic_ops on some architectures. However, the
binary package misses the required dependency on libatomic-ops-dev to
allow for such a use. I'm attaching a patch for your convenience.
Helmut
diff --minimal -Nru libgc-8.0.4/debian/changelog libgc-8.0.4/debian/changelog
--- libgc-8.0.4/debian/changelog2020-07-22 02:37:12.0 +0200
+++ libgc-8.0.4/debian/changelog2020-07-31 22:02:10.0 +0200
@@ -1,3 +1,10 @@
+libgc (1:8.0.4-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix missing libgc-dev -> libatomic-ops-dev dependency. (Closes: #-1)
+
+ -- Helmut Grohne Fri, 31 Jul 2020 22:02:10 +0200
+
libgc (1:8.0.4-1) unstable; urgency=medium
* Team upload.
diff --minimal -Nru libgc-8.0.4/debian/control libgc-8.0.4/debian/control
--- libgc-8.0.4/debian/control 2020-04-07 11:13:30.0 +0200
+++ libgc-8.0.4/debian/control 2020-07-31 21:59:44.0 +0200
@@ -35,7 +35,7 @@
Package: libgc-dev
Architecture: any
Section: libdevel
-Depends: ${misc:Depends}, libgc1 (= ${binary:Version}), libc-dev
+Depends: ${misc:Depends}, libgc1 (= ${binary:Version}), libc-dev,
${atomic:Depends}
Multi-Arch: same
Description: conservative garbage collector for C (development)
Boehm-Demers-Weiser's GC is a garbage collecting storage allocator that is
diff --minimal -Nru libgc-8.0.4/debian/rules libgc-8.0.4/debian/rules
--- libgc-8.0.4/debian/rules2020-04-07 11:03:33.0 +0200
+++ libgc-8.0.4/debian/rules2020-07-31 22:02:10.0 +0200
@@ -45,3 +45,6 @@
override_dh_installchangelogs:
dh_installchangelogs ChangeLog
+
+override_dh_gencontrol:
+ dh_gencontrol -- -Vatomic:Depends=$$(grep -q '[-]latomic_ops'
debian/libgc-dev/usr/lib/*/pkgconfig/*.pc && echo libatomic-ops-dev)
