Bug#946046: marked as done (unison-all should also depend on the old unison version, compatible with Debian 10)
Your message dated Fri, 14 Aug 2020 06:31:45 +0200 with message-id and subject line Re: Processed: reassign 946046 to src:meta-unison has caused the Debian Bug report #946046, regarding unison-all should also depend on the old unison version, compatible with Debian 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.) -- 946046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unison-all Version: 2.48+2 Severity: grave Justification: renders package unusable The purpose of unison-all is the following (see the latest sentence in particular): Description: file synchronization tool (all console versions) This is a metapackage that depends on all supported console versions of Unison, a file synchronization tool. . Each of the supported versions uses a different protocol version; installing this metapackage ensures the ability to synchronize with old systems. But it currently depends only on unison, which is no longer compatible with Debian 10 (buster), i.e. the current Debian/stable. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unison-all depends on: ii unison 2.48.4-1+b1 unison-all recommends no packages. unison-all suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 2.48.4+3 Le 13/08/2020 à 22:43, Vincent Lefevre a écrit : > found 946046 meta-unison/2.48+2 > found 946046 meta-unison/2.48.4+2 > fixed 946046 meta-unison/2.48.4+3 > thanks And closing again. -- Stéphane--- End Message ---
Bug#963659: pybind11: FTBFS with Sphinx 3.1: File "/usr/lib/python3/dist-packages/sphinx/domains/c.py", line 3093, in object_type / raise NotImplementedError()
Source: pybind11 Followup-For: Bug #963659 The new sphinx has various problems. Let's wait for pybind11 3.2.1 and see if that fixes things.
Bug#957795: marked as done (sigscheme: ftbfs with GCC-10)
Your message dated Fri, 14 Aug 2020 04:22:06 + with message-id and subject line Bug#957795: fixed in sigscheme 0.9.0-4 has caused the Debian Bug report #957795, regarding sigscheme: 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.) -- 957795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sigscheme Version: 0.9.0-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/sigscheme_0.9.0-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 [...] eval_c_string(): yes Backtrace:no Library: yes Interactive shell:yes [Developer-only debugging features] Debug: no [Build information (provide this on bug reports)] Package:SigScheme 0.9.0 build (compile on): x86_64-pc-linux-gnu host (compile for): x86_64-pc-linux-gnu host data model:LP64 host align (C/S/I/L/P): 1/2/4/8/8 host endian:little host char unsigned: no host arithmetic rshift: yes host safe va_list ref: no Compiler: gcc Compiler version: gcc (Debian 10-20200222-1) 10.0.1 20200222 (experimental) [master revision 01af7e0a0c2:487fe13f218:e99b18cf7101f205bfdd9f0f29ed51caaec52779] CFLAGS='-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pedantic -Wall -Wchar-subscripts -Wmissing-declarations -Wredundant-decls -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -Wno-overlength-strings -DNDEBUG' dh_auto_build make -j4 make[1]: Entering directory '/<>' Making all in doc make[2]: Entering directory '/<>/doc' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/<>/doc' Making all in m4 make[2]: Entering directory '/<>/m4' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/<>/m4' Making all in tools make[2]: Entering directory '/<>/tools' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/<>/tools' Making all in libgcroots make[2]: Entering directory '/<>/libgcroots' Making all in m4 make[3]: Entering directory '/<>/libgcroots/m4' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/libgcroots/m4' make[3]: Entering directory '/<>/libgcroots' /bin/bash ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"gcroots\" -DPACKAGE_TARNAME=\"libgcroots\" -DPACKAGE_VERSION=\"0.3.1\" -DPACKAGE_STRING=\"gcroots\ 0.3.1\" -DPACKAGE_BUGREPORT=\"sigscheme...@googlegroups.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libgcroots\" -DVERSION=\"0.3.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_VOID_P=8 -DALIGNOF_VOID_P=8 -DHAVE_GETCONTEXT=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DSMALL_CONFIG=1 -I./include -Wdate-time -D_FORTIFY_SOURCE=2 -fexceptions -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pedantic -Wall -Wchar-subscripts -Wmissing-declarations -Wredundant-decls -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -c -o mark.lo mark.c /bin/bash ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"gcroots\" -DPACKAGE_TARNAME=\"libgcroots\" -DPACKAGE_VERSION=\"0.3.1\" -DPACKAGE_STRING=\"gcroots\ 0.3.1\"
Bug#957628: marked as done (oflib: ftbfs with GCC-10)
Your message dated Fri, 14 Aug 2020 03:11:25 + with message-id and subject line Bug#957628: fixed in oflib 0git20070620-9 has caused the Debian Bug report #957628, regarding oflib: 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.) -- 957628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:oflib Version: 0git20070620-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/oflib_0git20070620-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 [...] APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/sbuild-nonexistent LANG=C.UTF-8 LC_ALL=C.UTF-8 LOGNAME=user42 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-35081716-5b65-40d7-b5db-d6a5a3f9fb06 SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package oflib dpkg-buildpackage: info: source version 0git20070620-8 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Nobuhiro Iwamatsu dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' rm -rf lib/*.o libofapi.a libofapi.so.* make[1]: Leaving directory '/<>' dh_clean debian/rules build dh build dh_update_autotools_config dh_autoreconf dh_auto_configure dh_auto_build make -j4 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -Wall -O2 -D_REENTRANT -DPIC -fpic -Wl,-z,relro -Wl,-soname -Wl,libofapi.so.0 lib/*.c -shared -o libofapi.so.0.0.0 /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_api.h:24: multiple definition of `OF_ROOT'; /tmp/ccfI9bcz.o:./lib/of_api.h:24: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:27: multiple definition of `_p_idx'; /tmp/ccfI9bcz.o:./lib/of_externals.h:27: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:25: multiple definition of `_p_array'; /tmp/ccfI9bcz.o:./lib/of_externals.h:25: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:26: multiple definition of `_p_sem'; /tmp/ccfI9bcz.o:./lib/of_externals.h:26: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:18: multiple definition of `_n_idx'; /tmp/ccfI9bcz.o:./lib/of_externals.h:18: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:17: multiple definition of `_n_array'; /tmp/ccfI9bcz.o:./lib/of_externals.h:17: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:19: multiple definition of `_n_sem'; /tmp/ccfI9bcz.o:./lib/of_externals.h:19: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:22: multiple definition of `_t_idx'; /tmp/ccfI9bcz.o:./lib/of_externals.h:22: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:21: multiple definition of `_t_array'; /tmp/ccfI9bcz.o:./lib/of_externals.h:21: first defined here /usr/bin/ld: /tmp/cceSsVfT.o:./lib/of_externals.h:23: multiple definition of `_t_sem'; /tmp/ccfI9bcz.o:./lib/of_externals.h:23: first
Bug#957853: marked as done (sxhkd: ftbfs with GCC-10)
Your message dated Fri, 14 Aug 2020 02:50:50 + with message-id and subject line Bug#957853: fixed in sxhkd 0.6.2-1 has caused the Debian Bug report #957853, regarding sxhkd: 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.) -- 957853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sxhkd Version: 0.6.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/sxhkd_0.6.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 [...] /usr/bin/ld: parse.o:./src/sxhkd.h:66: multiple definition of `caps_lock'; sxhkd.o:./src/sxhkd.h:66: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:67: multiple definition of `scroll_lock'; sxhkd.o:./src/sxhkd.h:67: first defined here /usr/bin/ld: parse.o:./src/types.h:77: multiple definition of `Meta_L'; sxhkd.o:./src/types.h:77: first defined here /usr/bin/ld: parse.o:./src/types.h:77: multiple definition of `Meta_R'; sxhkd.o:./src/types.h:77: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:55: multiple definition of `status_fifo'; sxhkd.o:./src/sxhkd.h:55: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:60: multiple definition of `hotkeys_tail'; sxhkd.o:./src/sxhkd.h:60: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:63: multiple definition of `abort_chord'; sxhkd.o:./src/sxhkd.h:63: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:62: multiple definition of `abort_keysym'; sxhkd.o:./src/sxhkd.h:62: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:61: multiple definition of `locked'; sxhkd.o:./src/sxhkd.h:61: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:61: multiple definition of `chained'; sxhkd.o:./src/sxhkd.h:61: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:61: multiple definition of `bell'; sxhkd.o:./src/sxhkd.h:61: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:61: multiple definition of `reload'; sxhkd.o:./src/sxhkd.h:61: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:61: multiple definition of `toggle_grab'; sxhkd.o:./src/sxhkd.h:61: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:61: multiple definition of `grabbed'; sxhkd.o:./src/sxhkd.h:61: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:61: multiple definition of `running'; sxhkd.o:./src/sxhkd.h:61: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:60: multiple definition of `hotkeys_head'; sxhkd.o:./src/sxhkd.h:60: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:58: multiple definition of `timeout'; sxhkd.o:./src/sxhkd.h:58: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:57: multiple definition of `mapping_count'; sxhkd.o:./src/sxhkd.h:57: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:56: multiple definition of `progress'; sxhkd.o:./src/sxhkd.h:56: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:54: multiple definition of `redir_fd'; sxhkd.o:./src/sxhkd.h:54: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:53: multiple definition of `num_extra_confs'; sxhkd.o:./src/sxhkd.h:53: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:52: multiple definition of `extra_confs'; sxhkd.o:./src/sxhkd.h:52: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:51: multiple definition of `config_path'; sxhkd.o:./src/sxhkd.h:51: first defined here /usr/bin/ld: parse.o:./src/sxhkd.h:50: multiple definition of `config_file'; sxhkd.o:./src/sxhkd.h:50: first defined here /usr/bin/ld:
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 963827 grave Bug #963827 [src:virtualbox] [virtualbox] guests limited to 800x600 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 963827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968302: marked as done (src:dovecot: multiple dovecot CVEs)
Your message dated Fri, 14 Aug 2020 00:18:33 + with message-id and subject line Bug#968302: fixed in dovecot 1:2.3.11.3+dfsg1-1 has caused the Debian Bug report #968302, regarding src:dovecot: multiple dovecot CVEs 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.) -- 968302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dovecot Version: 1:2.3.10.1+dfsg1-2 Severity: grave Tags: security bullseye sid Justification: user security hole Multiple security issues have been identified in dovecot. These were addressed in stable with dovecot 1:2.3.4.1-5+deb10u3 (DSA 4745-1), but need to be tracked in unstable and testing. >From the DSA: CVE-2020-12100 Receiving mail with deeply nested MIME parts leads to resource exhaustion as Dovecot attempts to parse it. CVE-2020-12673 Dovecot's NTLM implementation does not correctly check message buffer size, which leads to a crash when reading past allocation. CVE-2020-12674 Dovecot's RPA mechanism implementation accepts zero-length message, which leads to assert-crash later on. --- End Message --- --- Begin Message --- Source: dovecot Source-Version: 1:2.3.11.3+dfsg1-1 Done: Noah Meyerhans We believe that the bug you reported is fixed in the latest version of dovecot, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated dovecot 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
Bug#957760: marked as done (rfdump: ftbfs with GCC-10)
Your message dated Thu, 13 Aug 2020 22:38:44 +
with message-id
and subject line Bug#957760: fixed in rfdump 1.6-7
has caused the Debian Bug report #957760,
regarding rfdump: 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.)
--
957760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rfdump
Version: 1.6-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/rfdump_1.6-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
[...]
from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:33,
from main.h:22,
from xml.c:25:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is
deprecated [-Wdeprecated-declarations]
236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
| ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
from /usr/include/glib-2.0/gobject/gbinding.h:29,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from main.h:22,
from xml.c:25:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
679 | {
| ^
gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/gtk-2.0
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/fribidi -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid
-I/usr/include/freetype2 -I/usr/include/libpng16 -pthread
-I/usr/include/libglade-2.0 -I/usr/include/gtk-2.0
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/fribidi -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid
-I/usr/include/freetype2 -I/usr/
include/libpng16 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2
-Wall -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DVERSION=\"1.6\" -c -o tcpconnect.o
tcpconnect.c
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126,
from main.h:22,
from xml.c:25:
Bug#957360: marked as done (insighttoolkit4: ftbfs with GCC-10)
Your message dated Thu, 13 Aug 2020 22:23:32 + with message-id and subject line Bug#957360: fixed in insighttoolkit4 4.13.3withdata-dfsg1-1 has caused the Debian Bug report #957360, regarding insighttoolkit4: 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.) -- 957360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:insighttoolkit4 Version: 4.13.2-dfsg1-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/insighttoolkit4_4.13.2-dfsg1-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 [...] [ 21%] Building CXX object Modules/ThirdParty/VNL/src/vxl/core/vnl/CMakeFiles/itkvnl.dir/Templates/vnl_vector_fixed+double.3-.cxx.o cd /<>/BUILD/Modules/ThirdParty/VNL/src/vxl/core/vnl && /usr/bin/c++ -DVXL_LEGACY_ERROR_REPORTING -DVXL_WARN_DEPRECATED -DVXL_WARN_DEPRECATED_ONCE -Ditkvnl_EXPORTS -I/<>/Modules/ThirdParty/VNL/src/vxl/v3p/netlib -I/<>/Modules/ThirdParty/VNL/src/vxl/vcl -I/<>/Modules/ThirdParty/VNL/src/vxl/core -I/<>/BUILD/Modules/ThirdParty/VNL/src/vxl/v3p/netlib -I/<>/BUILD/Modules/ThirdParty/VNL/src/vxl/vcl -I/<>/BUILD/Modules/ThirdParty/VNL/src/vxl/core -I/<>/Modules/ThirdParty/VNL/src/vxl/core/vnl -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/nifti -g1 -Wall -Wcast-align -Wdisabled-optimization -Wextra -Wformat=2 -Winvalid-pch -Wno-format-nonliteral -Wpointer-arith -Wshadow -Wunused -Wwrite-strings -funit-at-a-time -Wno-strict-overflow -Wno-deprecated -Wno-invalid-offsetof -Woverloaded-vir tual -Wstrict-null-sentinel -w -fPIC -Wno-undefined-var-template -msse2 -o CMakeFiles/itkvnl.dir/Templates/vnl_vector_fixed+double.3-.cxx.o -c /<>/Modules/ThirdParty/VNL/src/vxl/core/vnl/Templates/vnl_vector_fixed+double.3-.cxx [ 21%] Building CXX object Modules/ThirdParty/VNL/src/vxl/core/vnl/CMakeFiles/itkvnl.dir/Templates/vnl_vector_fixed+double.4-.cxx.o cd /<>/BUILD/Modules/ThirdParty/VNL/src/vxl/core/vnl && /usr/bin/c++ -DVXL_LEGACY_ERROR_REPORTING -DVXL_WARN_DEPRECATED -DVXL_WARN_DEPRECATED_ONCE -Ditkvnl_EXPORTS -I/<>/Modules/ThirdParty/VNL/src/vxl/v3p/netlib -I/<>/Modules/ThirdParty/VNL/src/vxl/vcl -I/<>/Modules/ThirdParty/VNL/src/vxl/core -I/<>/BUILD/Modules/ThirdParty/VNL/src/vxl/v3p/netlib -I/<>/BUILD/Modules/ThirdParty/VNL/src/vxl/vcl -I/<>/BUILD/Modules/ThirdParty/VNL/src/vxl/core -I/<>/Modules/ThirdParty/VNL/src/vxl/core/vnl -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/nifti -g1 -Wall -Wcast-align -Wdisabled-optimization -Wextra -Wformat=2 -Winvalid-pch -Wno-format-nonliteral -Wpointer-arith -Wshadow -Wunused -Wwrite-strings -funit-at-a-time -Wno-strict-overflow -Wno-deprecated -Wno-invalid-offsetof -Woverloaded-vir tual -Wstrict-null-sentinel -w -fPIC -Wno-undefined-var-template -msse2 -o CMakeFiles/itkvnl.dir/Templates/vnl_vector_fixed+double.4-.cxx.o -c /<>/Modules/ThirdParty/VNL/src/vxl/core/vnl/Templates/vnl_vector_fixed+double.4-.cxx [ 21%] Building CXX object Modules/ThirdParty/VNL/src/vxl/core/vnl/CMakeFiles/itkvnl.dir/Templates/vnl_vector_fixed+double.5-.cxx.o cd /<>/BUILD/Modules/ThirdParty/VNL/src/vxl/core/vnl && /usr/bin/c++ -DVXL_LEGACY_ERROR_REPORTING -DVXL_WARN_DEPRECATED -DVXL_WARN_DEPRECATED_ONCE -Ditkvnl_EXPORTS
Bug#968377: marked as done (libplacebo FTBFS: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’ undeclared)
Your message dated Fri, 14 Aug 2020 00:04:38 +0200
with message-id <20200813220438.ga408...@ramacher.at>
and subject line Re: Bug#968377: libplacebo FTBFS: error:
‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’ undeclared
has caused the Debian Bug report #968377,
regarding libplacebo FTBFS: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’
undeclared
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.)
--
968377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libplacebo
Version: 1.29.1+dfsg1-2
Severity: serious
Tags: ftbfs
libplacebo fails to build from source in unstable. A build log ends
with:
| /usr/bin/mips64el-linux-gnuabi64-gcc -Isrc/libplacebo.so.29.p -Isrc -I../src
-I../src/include -I../subprojects/xtalloc/include -I../subprojects/bstr/include
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 -Wall -Wundef
-Wshadow -Wparentheses -Wpointer-arith -D_ISOC99_SOURCE -D_GNU_SOURCE
-D_XOPEN_SOURCE=700 -U__STRICT_ANSI__ -fvisibility=hidden -Wmissing-prototypes
-Wno-pointer-sign -Werror=implicit-function-declaration
-Werror=incompatible-pointer-types -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -pthread -MD -MQ
src/libplacebo.so.29.p/vulkan_context.c.o -MF
src/libplacebo.so.29.p/vulkan_context.c.o.d -o
src/libplacebo.so.29.p/vulkan_context.c.o -c ../src/vulkan/context.c
| ../src/vulkan/context.c: In function ‘pl_vulkan_choose_device’:
| ../src/vulkan/context.c:391:10: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’
undeclared (first use in this function); did you mean
‘VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM’?
| 391 | [VK_PHYSICAL_DEVICE_TYPE_END_RANGE+1]= {0},
| | ^
| | VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM
| ../src/vulkan/context.c:391:10: note: each undeclared identifier is reported
only once for each function it appears in
| ../src/vulkan/context.c:391:10: error: array index in initializer not of
integer type
| ../src/vulkan/context.c:391:10: note: (near initialization for ‘types’)
| ninja: build stopped: subcommand failed.
| dh_auto_build: error: cd obj-mips64el-linux-gnuabi64 && LC_ALL=C.UTF-8 ninja
-j1 -v returned exit code 1
| make: *** [debian/rules:7: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
Reproducible by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libplacebo_1.29.1+dfsg1-2.rbuild.log.gz
Also seen by crossqa:
http://crossqa.debian.net/build/libplacebo_1.29.1+dfsg1-2_mipsel_20200710170355.log
Helmut
--- End Message ---
--- Begin Message ---
Version: 2.72.0-1
On 2020-08-13 23:48:59 +0200, Helmut Grohne wrote:
> Source: libplacebo
> Version: 1.29.1+dfsg1-2
> Severity: serious
> Tags: ftbfs
>
> libplacebo fails to build from source in unstable. A build log ends
> with:
>
> | /usr/bin/mips64el-linux-gnuabi64-gcc -Isrc/libplacebo.so.29.p -Isrc
> -I../src -I../src/include -I../subprojects/xtalloc/include
> -I../subprojects/bstr/include -fdiagnostics-color=always -pipe
> -D_FILE_OFFSET_BITS=64 -std=c99 -Wall -Wundef -Wshadow -Wparentheses
> -Wpointer-arith -D_ISOC99_SOURCE -D_GNU_SOURCE -D_XOPEN_SOURCE=700
> -U__STRICT_ANSI__ -fvisibility=hidden -Wmissing-prototypes -Wno-pointer-sign
> -Werror=implicit-function-declaration -Werror=incompatible-pointer-types
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -pthread -MD
> -MQ src/libplacebo.so.29.p/vulkan_context.c.o -MF
> src/libplacebo.so.29.p/vulkan_context.c.o.d -o
> src/libplacebo.so.29.p/vulkan_context.c.o -c ../src/vulkan/context.c
> | ../src/vulkan/context.c: In function ‘pl_vulkan_choose_device’:
> | ../src/vulkan/context.c:391:10: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’
> undeclared (first use in this function); did you mean
> ‘VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM’?
> | 391 | [VK_PHYSICAL_DEVICE_TYPE_END_RANGE+1]= {0},
> | | ^
> | | VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM
> | ../src/vulkan/context.c:391:10: note: each undeclared identifier is
> reported only once for each function it appears in
> | ../src/vulkan/context.c:391:10: error: array index in initializer not of
> integer type
> | ../src/vulkan/context.c:391:10: note: (near initialization for ‘types’)
> | ninja: build stopped: subcommand failed.
> | dh_auto_build: error: cd
Bug#967205: marked as done (rfdump: Unversioned Python removal in sid/bullseye)
Your message dated Thu, 13 Aug 2020 23:56:56 +0200 with message-id <0e76d2a10e55394b148ef3ccd81b9f03a25d4a47.ca...@gmail.com> and subject line Close bug has caused the Debian Bug report #967205, regarding rfdump: Unversioned Python removal in sid/bullseye 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.) -- 967205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rfdump Version: 1.6-6 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- --- End Message ---
Bug#968377: libplacebo FTBFS: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’ undeclared
Source: libplacebo
Version: 1.29.1+dfsg1-2
Severity: serious
Tags: ftbfs
libplacebo fails to build from source in unstable. A build log ends
with:
| /usr/bin/mips64el-linux-gnuabi64-gcc -Isrc/libplacebo.so.29.p -Isrc -I../src
-I../src/include -I../subprojects/xtalloc/include -I../subprojects/bstr/include
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 -Wall -Wundef
-Wshadow -Wparentheses -Wpointer-arith -D_ISOC99_SOURCE -D_GNU_SOURCE
-D_XOPEN_SOURCE=700 -U__STRICT_ANSI__ -fvisibility=hidden -Wmissing-prototypes
-Wno-pointer-sign -Werror=implicit-function-declaration
-Werror=incompatible-pointer-types -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -pthread -MD -MQ
src/libplacebo.so.29.p/vulkan_context.c.o -MF
src/libplacebo.so.29.p/vulkan_context.c.o.d -o
src/libplacebo.so.29.p/vulkan_context.c.o -c ../src/vulkan/context.c
| ../src/vulkan/context.c: In function ‘pl_vulkan_choose_device’:
| ../src/vulkan/context.c:391:10: error: ‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’
undeclared (first use in this function); did you mean
‘VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM’?
| 391 | [VK_PHYSICAL_DEVICE_TYPE_END_RANGE+1]= {0},
| | ^
| | VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM
| ../src/vulkan/context.c:391:10: note: each undeclared identifier is reported
only once for each function it appears in
| ../src/vulkan/context.c:391:10: error: array index in initializer not of
integer type
| ../src/vulkan/context.c:391:10: note: (near initialization for ‘types’)
| ninja: build stopped: subcommand failed.
| dh_auto_build: error: cd obj-mips64el-linux-gnuabi64 && LC_ALL=C.UTF-8 ninja
-j1 -v returned exit code 1
| make: *** [debian/rules:7: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
Reproducible by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libplacebo_1.29.1+dfsg1-2.rbuild.log.gz
Also seen by crossqa:
http://crossqa.debian.net/build/libplacebo_1.29.1+dfsg1-2_mipsel_20200710170355.log
Helmut
Bug#967118: 0ad: Unversioned Python removal in sid/bullseye
Hello, I am a developer of 0ad and I am in charge of upgrading the SpiderMonkey library that we embed, which still depends on Python 2. I confirm what smcv said: the presence of a working `python2.7` executable should be enough to build spidermonkey, and I do not think that third-party modules are necessary. We are determined to remove our python2 dependency in our upcoming stable release, which is under active development. However, we will definitely not be able to get it out in time for the release of Debian bullseye. We hope that our latest stable version can be kept in bullseye, with our future release ready for bookworm. Please let me know if I should post additional information to bug #936101. Best regards, Nicolas
Bug#956967: Patch from upstream for FTBFS with gcc-10
Hello,
I am a developer of 0ad. As noticed by Reiner, this is fixed upstream.
As far as I can see, only a part of the upstream fix is necessary for
patching the latest 0ad release. I am attaching a patch which should fix
the issue for the Debian package.
We would like to offer any help we can in preventing the removal of 0ad
from the repository. The latest release is a bit old and unfortunately
our upcoming release will not be ready in time for the stabilization of
Debian bullseye. However, the project is still very active and we would
like to prevent a break in the availability of 0ad in your repos.
Thanks a lot for the maintaining work, do not hesitate to contact me if
needed.
Best regards,
Nicolas
From: Nicolas Auvray
Date: Thu, 13 Aug 2020 18:28:12 +0200
Subject: Fix #956967 on 0.0.23b
---
.../FColladaPlugins/FArchiveXML/FAXPhysicsExport.cpp | 12
.../src/FColladaPlugins/FArchiveXML/FArchiveXML.h| 11 ++-
2 files changed, 10 insertions(+), 13 deletions(-)
diff --git
a/libraries/source/fcollada/src/FColladaPlugins/FArchiveXML/FAXPhysicsExport.cpp
b/libraries/source/fcollada/src/FColladaPlugins/FArchiveXML/FAXPhysicsExport.cpp
index e999c4e..4272a16 100644
---
a/libraries/source/fcollada/src/FColladaPlugins/FArchiveXML/FAXPhysicsExport.cpp
+++
b/libraries/source/fcollada/src/FColladaPlugins/FArchiveXML/FAXPhysicsExport.cpp
@@ -330,15 +330,3 @@ void
FArchiveXML::WritePhysicsRigidBodyParameters(FCDPhysicsRigidBodyParameters*
}
}
-template
-xmlNode* FArchiveXML::AddPhysicsParameter(xmlNode* parentNode, const char*
name, FCDParameterAnimatableT& value)
-{
- xmlNode* paramNode = AddChild(parentNode, name);
- AddContent(paramNode, FUStringConversion::ToString((TYPE&) value));
- if (value.IsAnimated())
- {
- const FCDAnimated* animated = value.GetAnimated();
- FArchiveXML::WriteAnimatedValue(animated, paramNode, name);
- }
- return paramNode;
-}
diff --git
a/libraries/source/fcollada/src/FColladaPlugins/FArchiveXML/FArchiveXML.h
b/libraries/source/fcollada/src/FColladaPlugins/FArchiveXML/FArchiveXML.h
index a20abcb..4f18cc0 100644
--- a/libraries/source/fcollada/src/FColladaPlugins/FArchiveXML/FArchiveXML.h
+++ b/libraries/source/fcollada/src/FColladaPlugins/FArchiveXML/FArchiveXML.h
@@ -553,7 +553,16 @@ public:
static void
WritePhysicsRigidBodyParameters(FCDPhysicsRigidBodyParameters*
physicsRigidBodyParameters, xmlNode* techniqueNode);
template
- static xmlNode* AddPhysicsParameter(xmlNode* parentNode, const char*
name, FCDParameterAnimatableT& value);
+ static xmlNode* AddPhysicsParameter(xmlNode* parentNode, const char*
name, FCDParameterAnimatableT& value) {
+ xmlNode* paramNode = AddChild(parentNode, name);
+ AddContent(paramNode, FUStringConversion::ToString((TYPE&)
value));
+ if (value.IsAnimated())
+ {
+ const FCDAnimated* animated = value.GetAnimated();
+ FArchiveXML::WriteAnimatedValue(animated, paramNode,
name);
+ }
+ return paramNode;
+ }
//
--
Bug#967016: marked as done (libopenshot: FTBFS: CMakeFiles/openshot.dir/Qt/AudioPlaybackThread.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: multiple definition of `AV_G
Your message dated Thu, 13 Aug 2020 21:04:51 + with message-id and subject line Bug#967016: fixed in libopenshot 0.2.5+dfsg1-4 has caused the Debian Bug report #967016, regarding libopenshot: FTBFS: CMakeFiles/openshot.dir/Qt/AudioPlaybackThread.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: multiple definition of `AV_GET_CODEC_CONTEXT'; CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: first defined here 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.) -- 967016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libopenshot Version: 0.2.5+dfsg1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /usr/bin/ld: DWARF error: could not find variable specification > at offset 3c755 > CMakeFiles/openshot.dir/Qt/AudioPlaybackThread.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/Qt/PlayerDemo.cpp.o:./debian/build/src/./src/Qt/../../include/FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/Qt/PlayerPrivate.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/Qt/VideoCacheThread.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/Qt/VideoPlaybackThread.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/Qt/VideoRenderer.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/Qt/VideoRenderWidget.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/ImageReader.cpp.o:./debian/build/src/./src/../include/FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/ImageWriter.cpp.o:./debian/build/src/./src/../include/FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > /usr/bin/ld: > CMakeFiles/openshot.dir/TextReader.cpp.o:./debian/build/src/./src/../include/FFmpegUtilities.h:166: > multiple definition of `AV_GET_CODEC_CONTEXT'; > CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: > first defined here > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/08/02/libopenshot_0.2.5+dfsg1-3_unstable.log A list of current common problems and possible solutions is available at
Processed: Bug#967016 marked as pending in libopenshot
Processing control commands: > tag -1 pending Bug #967016 [src:libopenshot] libopenshot: FTBFS: CMakeFiles/openshot.dir/Qt/AudioPlaybackThread.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166: multiple definition of `AV_GET_CODEC_CONTEXT'; CMakeFiles/openshot.dir/openshot_autogen/mocs_compilation.cpp.o:./debian/build/src/./include/Qt/../FFmpegUtilities.h:166: first defined here Added tag(s) pending. -- 967016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967016: marked as pending in libopenshot
Control: tag -1 pending Hello, Bug #967016 in libopenshot 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/multimedia-team/libopenshot/-/commit/2131f128e7d34d3e733a7809ed07ba47eb0c9712 Fix FTBFS due to gcc-10 and ffmpeg. (Closes: #967016) (this message was generated automatically) -- Greetings https://bugs.debian.org/967016
Processed: Re: Processed: reassign 946046 to src:meta-unison
Processing commands for cont...@bugs.debian.org:
> found 946046 meta-unison/2.48+2
Bug #946046 {Done: =?utf-8?q?St=C3=A9phane_Glondu?= }
[src:meta-unison] unison-all should also depend on the old unison version,
compatible with Debian 10
Marked as found in versions meta-unison/2.48+2 and reopened.
> found 946046 meta-unison/2.48.4+2
Bug #946046 [src:meta-unison] unison-all should also depend on the old unison
version, compatible with Debian 10
Marked as found in versions meta-unison/2.48.4+2.
> fixed 946046 meta-unison/2.48.4+3
Bug #946046 [src:meta-unison] unison-all should also depend on the old unison
version, compatible with Debian 10
Marked as fixed in versions meta-unison/2.48.4+3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
946046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#957189: marked as done (f-irc: ftbfs with GCC-10)
Your message dated Thu, 13 Aug 2020 20:34:45 +
with message-id
and subject line Bug#957189: fixed in f-irc 1.36-1.1
has caused the Debian Bug report #957189,
regarding f-irc: 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.)
--
957189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:f-irc
Version: 1.36-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/f-irc_1.36-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
[...]
| ^~~
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DVERSION=\"1.36\"
-DSYSCONFDIR=\"/usr/local/etc\" -O3 -g -Wall -pedantic -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o dictionary.o dictionary.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DVERSION=\"1.36\"
-DSYSCONFDIR=\"/usr/local/etc\" -O3 -g -Wall -pedantic -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o lf_buffer.o lf_buffer.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DVERSION=\"1.36\"
-DSYSCONFDIR=\"/usr/local/etc\" -O3 -g -Wall -pedantic -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o ctcp.o ctcp.c
ctcp.c: In function ‘exec_and_strip_ctcp’:
ctcp.c:68:105: warning: macro "__DATE__" might prevent reproducible builds
[-Wdate-time]
68 |const char *reply = "f-irc v" VERSION " by m...@vanheusden.com -
http://www.vanheusden.com/f-irc/ (" __DATE__ " " __TIME__ ")";
|
^~~~
ctcp.c:68:118: warning: macro "__TIME__" might prevent reproducible builds
[-Wdate-time]
68 |const char *reply = "f-irc v" VERSION " by m...@vanheusden.com -
http://www.vanheusden.com/f-irc/ (" __DATE__ " " __TIME__ ")";
|
^~~~
ctcp.c:56:4: warning: ignoring return value of ‘asprintf’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
56 |asprintf(, "* \002%s\002 %s", nick, work);
|^~
ctcp.c:125:6: warning: ignoring return value of ‘asprintf’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
125 | asprintf(_buffer, "Ping to %s took aproximately %f seconds",
ps -> user_ping, get_ts() - ps -> t_user_ping);
|
^~~
ctcp.c:183:6: warning: ignoring return value of ‘asprintf’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
183 | asprintf(, "%s (%s)", p -> pw_gecos, p -> pw_name);
| ^~~~
ctcp.c:287:3: warning: ignoring return value of ‘asprintf’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
287 | asprintf(, "(incoming CTCP request)");
| ^
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DVERSION=\"1.36\"
-DSYSCONFDIR=\"/usr/local/etc\" -O3 -g -Wall -pedantic -Wdate-time
-D_FORTIFY_SOURCE=2 -c -o headlines.o headlines.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat
Bug#963856: marked as done (datalad: FTBFS on IPv6-only environments)
Your message dated Thu, 13 Aug 2020 20:34:32 +
with message-id
and subject line Bug#963856: fixed in datalad 0.13.2-1
has caused the Debian Bug report #963856,
regarding datalad: FTBFS on IPv6-only environments
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.)
--
963856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: datalad
Version: 0.12.6-1
Severity: serious
Justification: FTBFS (when it built before)
During archive-wide test rebuilding of an IPv6-only environment (which
appears on some normal buildds)[1] we noticed that this package fails:
ERROR: datalad.interface.tests.test_add_archive_content.test_add_archive_content
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/tests/utils.py",
line 1200, in newfunc
raise exc_info[1]
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/tests/utils.py",
line 1172, in newfunc
ret = func(*args, **kwargs)
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/tests/utils.py",
line 559, in newfunc
return t(*(arg + (d,)), **kw)
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/tests/utils.py",
line 671, in newfunc
return tfunc(*(args + (path, url)), **kwargs)
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/tests/utils.py",
line 732, in newfunc
return t(*(arg + (filename,)), **kw)
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/interface/tests/test_add_archive_content.py",
line 186, in test_add_archive_content
repo.add_urls([opj(url, '1.tar.gz')], options=["--pathdepth", "-1"])
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/support/annexrepo.py",
line 1967, in add_urls
self._run_annex_command('addurl', annex_options=options + urls,
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/support/annexrepo.py",
line 1003, in _run_annex_command
return self._run_command_files_split(
File
"/<>/.pybuild/cpython3_3.8_datalad/build/datalad/support/gitrepo.py",
line 1930, in _run_command_files_split
out_, err_ = func(
File "/<>/.pybuild/cpython3_3.8_datalad/build/datalad/cmd.py",
line 718, in run
out, err = super(GitRunner, self).run(
File "/<>/.pybuild/cpython3_3.8_datalad/build/datalad/cmd.py",
line 544, in run
raise CommandError(str(cmd), msg, status, out[0], out[1])
datalad.support.exceptions.CommandError: CommandError: command '['git-annex',
'addurl', '-c', 'annex.dotfiles=true', '--pathdepth', '-1',
'http://127.0.0.1:36559/1.tar.gz']' failed with exitcode 1
Failed to run ['git-annex', 'addurl', '-c', 'annex.dotfiles=true',
'--pathdepth', '-1', 'http://127.0.0.1:36559/1.tar.gz'] under
'/tmp/datalad_temp_test_add_archive_content59pn23bs'. Exit code=1.
The full log is available at
http://perl.debian.net/rebuild-logs/sid-v6only/datalad_0.12.6-1/datalad_0.12.6-1_amd64-2020-06-28T06:56:47Z.build
One way to replicate this environment is like so:
# unshare -n
# ip li set lo up
# ip li add dummy0 type dummy
# ip li set dummy0 up
Cheers
Dominic
[1] this test showed approximately 100 packages in the archive failing,
but nearly all of them were due to the behaviour of libio-socket-ip-perl,
so will be fixed centrally. I'm filing bugs about the small number of
unrelated cases.
--- End Message ---
--- Begin Message ---
Source: datalad
Source-Version: 0.13.2-1
Done: Yaroslav Halchenko
We believe that the bug you reported is fixed in the latest version of
datalad, 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.
Yaroslav Halchenko (supplier of updated datalad 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: Thu, 13 Aug 2020 09:37:20 -0400
Source: datalad
Binary: datalad python3-datalad
Architecture: source all
Version: 0.13.2-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team
Changed-By: Yaroslav
Bug#903213: marked as done (datalad: FTBFS in stretch/buster/sid)
Your message dated Thu, 13 Aug 2020 20:34:32 +
with message-id
and subject line Bug#903213: fixed in datalad 0.13.2-1
has caused the Debian Bug report #903213,
regarding datalad: FTBFS in stretch/buster/sid
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.)
--
903213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:datalad
Version: 0.4.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in stretch + security + stretch-proposed-updates
but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
dh_testdir -i -O--buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure --test-nose -i python{version} -p 2.7
I: pybuild base:184: python2.7 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
pybuild --build --test-nose -i python{version} -p 2.7
I: pybuild base:184: /usr/bin/python setup.py build
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/datalad
[... snipped ...]
File
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_annexrepo.py",
line 247, in test_AnnexRepo_is_under_annex
assert_equal(ar.is_under_annex(testfiles, batch=batch), target_value)
AssertionError: Lists differ: [False, False, False] != [True, False, False]
First differing element 0:
False
True
- [False, False, False]
+ [True, False, False]
==
FAIL: datalad.support.tests.test_gitrepo.test_GitRepo_get_toppath
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
line 706, in newfunc
t(*(arg + (uri,)), **kw)
File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
line 536, in newfunc
return t(*(arg + (filename,)), **kw)
File
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_gitrepo.py",
line 637, in test_GitRepo_get_toppath
eq_(GitRepo.get_toppath(repo, follow_up=False), reporeal)
AssertionError: '/tmp/datalad_temp_testrepo_bh4Q3X' !=
'/tmp/datalad_temp_testrepo_bh4Q3X/sub dataset1/subm 1'
==
FAIL: datalad.support.tests.test_gitrepo.test_submodule_deinit
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
line 706, in newfunc
t(*(arg + (uri,)), **kw)
File
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_gitrepo.py",
line 840, in test_submodule_deinit
eq_(['subm 1', 'subm 2'], [s.name for s in top_repo.get_submodules()])
AssertionError: ['subm 1', 'subm 2'] != []
--
Ran 616 tests in 167.088s
FAILED (SKIP=65, errors=63, failures=15)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose -s -v datalad
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --test-nose
returned exit code 13
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:19: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
This is just how the build ends in my autobuilder with dpkg-buildpackage -A,
but there are full build logs available here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/datalad.html
A diff between the previous successful build log and this (failed) one
yields this result:
-Get:63 http://deb.debian.org/debian-security stretch/updates/main amd64
git-annex amd64 6.20170101-1+deb9u1 [10.9 MB]
+Get:63 http://deb.debian.org/debian stretch-proposed-updates/main amd64
git-annex amd64 6.20170101-1+deb9u2 [10.9 MB]
so it seems git-annex now behaves in a way which
Bug#964595: marked as done (faust FTBFS with libmicrohttpd 0.9.71)
Your message dated Thu, 13 Aug 2020 20:34:58 +
with message-id
and subject line Bug#964595: fixed in faust 2.27.2~ds1-1
has caused the Debian Bug report #964595,
regarding faust FTBFS with libmicrohttpd 0.9.71
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.)
--
964595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: faust
Version: 2.20.2~ds0-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/faust.html
...
/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.cpp: In
member function 'bool httpdfaust::HTTPDServer::start(int)':
/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.cpp:118:75:
error: invalid conversion from 'int (*)(void*, MHD_Connection*, const char*,
const char*, const char*, const char*, size_t*, void**)' {aka 'int (*)(void*,
MHD_Connection*, const char*, const char*, const char*, const char*, long
unsigned int*, void**)'} to 'MHD_AccessHandlerCallback' {aka 'MHD_Result
(*)(void*, MHD_Connection*, const char*, const char*, const char*, const char*,
long unsigned int*, void**)'} [-fpermissive]
118 | fServer = MHD_start_daemon (MHD_USE_SELECT_INTERNALLY, port, NULL,
NULL, _answer_to_connection, this, MHD_OPTION_END);
|
^
|
|
|
int (*)(void*, MHD_Connection*, const char*, const char*, const char*, const
char*, size_t*, void**) {aka int (*)(void*, MHD_Connection*, const char*, const
char*, const char*, const char*, long unsigned int*, void**)}
In file included from
/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.h:48,
from
/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.cpp:32:
/usr/include/microhttpd.h:2428:45: note: initializing argument 5 of
'MHD_Daemon* MHD_start_daemon(unsigned int, uint16_t, MHD_AcceptPolicyCallback,
void*, MHD_AccessHandlerCallback, void*, ...)'
2428 | MHD_AccessHandlerCallback dh, void *dh_cls,
| ~~^~
/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.cpp: In
member function 'int httpdfaust::HTTPDServer::answer(MHD_Connection*, const
char*, const char*, const char*, const char*, size_t*, void**)':
/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.cpp:224:44:
error: invalid conversion from 'int (*)(void*, MHD_ValueKind, const char*,
const char*)' to 'MHD_KeyValueIterator' {aka 'MHD_Result (*)(void*,
MHD_ValueKind, const char*, const char*)'} [-fpermissive]
224 | MHD_get_connection_values (connection, t, _get_params, );
|^~~
||
|int (*)(void*,
MHD_ValueKind, const char*, const char*)
In file included from
/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.h:48,
from
/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.cpp:32:
/usr/include/microhttpd.h:2699:49: note: initializing argument 3 of 'int
MHD_get_connection_values(MHD_Connection*, MHD_ValueKind, MHD_KeyValueIterator,
void*)'
2699 |MHD_KeyValueIterator iterator,
|~^~~~
gmake[6]: *** [http/CMakeFiles/httpdynamic.dir/build.make:154:
http/CMakeFiles/httpdynamic.dir/build/1st/faust-2.20.2~ds0/architecture/httpdlib/src/httpd/HTTPDServer.cpp.o]
Error 1
--- End Message ---
--- Begin Message ---
Source: faust
Source-Version: 2.27.2~ds1-1
Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?=
We believe that the bug you reported is fixed in the latest version of
faust, 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.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
faust package)
(This message was generated automatically at their request; if you
Bug#903233: marked as done (datalad: FTBFS in stretch/buster/sid)
Your message dated Thu, 13 Aug 2020 20:34:32 +
with message-id
and subject line Bug#903213: fixed in datalad 0.13.2-1
has caused the Debian Bug report #903213,
regarding datalad: FTBFS in stretch/buster/sid
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.)
--
903213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:datalad
Version: 0.4.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in stretch + security + stretch-proposed-updates
but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
dh_testdir -i -O--buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure --test-nose -i python{version} -p 2.7
I: pybuild base:184: python2.7 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
pybuild --build --test-nose -i python{version} -p 2.7
I: pybuild base:184: /usr/bin/python setup.py build
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/datalad
[... snipped ...]
File
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_annexrepo.py",
line 247, in test_AnnexRepo_is_under_annex
assert_equal(ar.is_under_annex(testfiles, batch=batch), target_value)
AssertionError: Lists differ: [False, False, False] != [True, False, False]
First differing element 0:
False
True
- [False, False, False]
+ [True, False, False]
==
FAIL: datalad.support.tests.test_gitrepo.test_GitRepo_get_toppath
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
line 706, in newfunc
t(*(arg + (uri,)), **kw)
File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
line 536, in newfunc
return t(*(arg + (filename,)), **kw)
File
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_gitrepo.py",
line 637, in test_GitRepo_get_toppath
eq_(GitRepo.get_toppath(repo, follow_up=False), reporeal)
AssertionError: '/tmp/datalad_temp_testrepo_bh4Q3X' !=
'/tmp/datalad_temp_testrepo_bh4Q3X/sub dataset1/subm 1'
==
FAIL: datalad.support.tests.test_gitrepo.test_submodule_deinit
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
line 706, in newfunc
t(*(arg + (uri,)), **kw)
File
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_gitrepo.py",
line 840, in test_submodule_deinit
eq_(['subm 1', 'subm 2'], [s.name for s in top_repo.get_submodules()])
AssertionError: ['subm 1', 'subm 2'] != []
--
Ran 616 tests in 167.088s
FAILED (SKIP=65, errors=63, failures=15)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose -s -v datalad
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --test-nose
returned exit code 13
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:19: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
This is just how the build ends in my autobuilder with dpkg-buildpackage -A,
but there are full build logs available here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/datalad.html
A diff between the previous successful build log and this (failed) one
yields this result:
-Get:63 http://deb.debian.org/debian-security stretch/updates/main amd64
git-annex amd64 6.20170101-1+deb9u1 [10.9 MB]
+Get:63 http://deb.debian.org/debian stretch-proposed-updates/main amd64
git-annex amd64 6.20170101-1+deb9u2 [10.9 MB]
so it seems git-annex now behaves in a way which
Bug#948907: marked as done (ktp-call-ui: FTBFS: QDBusArgument: No such file or directory)
Your message dated Thu, 13 Aug 2020 20:36:19 + with message-id and subject line Bug#948907: fixed in ktp-call-ui 20.08.0-1 has caused the Debian Bug report #948907, regarding ktp-call-ui: FTBFS: QDBusArgument: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 948907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ktp-call-ui Version: 17.08.3-1 Severity: serious Tags: ftbfs sid Dear maintainer, During a recent rebuild ktp-call-ui failed with the following error: [ 35%] Building CXX object libqtf/CMakeFiles/qtf.dir/qtf_autogen/mocs_compilation.cpp.o [...] In file included from /usr/include/telepathy-qt5/TelepathyQt/types.h:30, from /usr/include/telepathy-qt5/TelepathyQt/Types:8, from /usr/include/telepathy-qt5/TelepathyQt/_gen/cli-channel.h:12, from /usr/include/telepathy-qt5/TelepathyQt/channel.h:30, from /usr/include/telepathy-qt5/TelepathyQt/Channel:8, from /usr/include/telepathy-qt5/TelepathyQt/call-channel.h:29, from /usr/include/telepathy-qt5/TelepathyQt/CallChannel:8, from /<>/obj-x86_64-linux-gnu/libqtf/qtf_autogen/EWIEGA46WW/../../../../libqtf/qtf.h:29, from /<>/obj-x86_64-linux-gnu/libqtf/qtf_autogen/EWIEGA46WW/moc_qtf.cpp:9, from /<>/obj-x86_64-linux-gnu/libqtf/qtf_autogen/mocs_compilation.cpp:2: /usr/include/telepathy-qt5/TelepathyQt/_gen/types.h:15:10: fatal error: QDBusArgument: No such file or directory 15 | #include | ^~~ compilation terminated. The full build log can be seen here: https://buildd.debian.org/status/fetch.php?pkg=ktp-call-ui=amd64=17.08.3-1%2Bb2=1578708417=0 Feel free to reassign to libtelepathy-qt5-dev if needed. -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ktp-call-ui Source-Version: 20.08.0-1 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of ktp-call-ui, 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 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated ktp-call-ui 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: Thu, 13 Aug 2020 22:04:53 +0200 Source: ktp-call-ui Architecture: source Version: 20.08.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 948907 Changes: ktp-call-ui (20.08.0-1) unstable; urgency=medium . * Team upload. * New upstream release: - fixes build with telepathy-qt 0.9.8 (Closes: #948907) * Update watch file to the new release-service location. * Update the build dependencies according to the upstream build system: - bump libktp-dev to 20.08.0 - explicitly add gettext * Switch from dhmk to the dh sequencer: - invoke the dh sequencer using the kf5 addon - call the right debhelper command instead of $(overridden_command) * Bump the debhelper compatibility to 13: - switch the debhelper build dependency to debhelper-compat 13 - remove debian/compat * Add Rules-Requires-Root: no. * Bump Standards-Version to 4.5.0, no changes required. * Switch Vcs-* fields to salsa.debian.org. * Update the patches: - dbus_include.patch: drop, seems not needed anymore Checksums-Sha1: 99c0ff8c22ed1c7e7e97745f9ef5c1579073b889 2558 ktp-call-ui_20.08.0-1.dsc f77d6fba3fd65b661b03b9f4a632d3df9db68832 97208 ktp-call-ui_20.08.0.orig.tar.xz 565974f4831f788d3756358b4c0295226da46bbc 4408 ktp-call-ui_20.08.0-1.debian.tar.xz 6bffab1cea0e7d1ce70b7127d55f1b84927b33b1 20276 ktp-call-ui_20.08.0-1_source.buildinfo Checksums-Sha256: 1f00407a532312c9833bc84be3421afd5fc54cf3c8d158ef7983314808857b22 2558 ktp-call-ui_20.08.0-1.dsc 2744e739456fd3aba322eb3c47be84511450dd713838e133be4f1957a3b9a0bf 97208 ktp-call-ui_20.08.0.orig.tar.xz
Bug#966948: marked as done (datalad: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 --test-nose returned exit code 13)
Your message dated Thu, 13 Aug 2020 20:34:32 +
with message-id
and subject line Bug#966948: fixed in datalad 0.13.2-1
has caused the Debian Bug report #966948,
regarding datalad: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i
python{version} -p 3.8 --test-nose returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: datalad
Version: 0.12.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PATH=/<>/bin:$PATH \
> dh_auto_test -- --test-nose
> pybuild --test --test-nose -i python{version} -p 3.8 --test-nose
> I: pybuild pybuild:284: PYTHONPATH=/<>/bin python3.8 setup.py
> develop --install-dir bin/;cp -rp datalad.egg-info
> /<>/.pybuild/cpython3_3.8_datalad/build/;
> running develop
> running egg_info
> writing datalad.egg-info/PKG-INFO
> writing dependency_links to datalad.egg-info/dependency_links.txt
> writing entry points to datalad.egg-info/entry_points.txt
> writing requirements to datalad.egg-info/requires.txt
> writing top-level names to datalad.egg-info/top_level.txt
> reading manifest file 'datalad.egg-info/SOURCES.txt'
> writing manifest file 'datalad.egg-info/SOURCES.txt'
> running build_ext
> Creating /<>/bin/datalad.egg-link (link to .)
> datalad 0.12.6 is already the active version in easy-install.pth
> Installing datalad script to bin/
> Installing git-annex-remote-datalad-archives script to bin/
> Installing git-annex-remote-datalad script to bin/
>
> Installed /<>
> Processing dependencies for datalad==0.12.6
> Searching for distro==1.5.0
> Best match: distro 1.5.0
> Adding distro 1.5.0 to easy-install.pth file
> Installing distro script to bin/
>
> Using /usr/lib/python3/dist-packages
> Searching for wrapt==1.11.2
> Best match: wrapt 1.11.2
> Adding wrapt 1.11.2 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Searching for tqdm==4.43.0
> Best match: tqdm 4.43.0
> Adding tqdm 4.43.0 to easy-install.pth file
> Installing tqdm script to bin/
>
> Using /usr/lib/python3/dist-packages
> Searching for requests==2.23.0
> Best match: requests 2.23.0
> Adding requests 2.23.0 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Searching for patool==1.12
> Best match: patool 1.12
> Adding patool 1.12 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Searching for iso8601==0.1.12
> Best match: iso8601 0.1.12
> Adding iso8601 0.1.12 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Searching for humanize==2.4.1
> Best match: humanize 2.4.1
> Adding humanize 2.4.1 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Searching for fasteners==0.14.1
> Best match: fasteners 0.14.1
> Adding fasteners 0.14.1 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Searching for chardet==3.0.4
> Best match: chardet 3.0.4
> Adding chardet 3.0.4 to easy-install.pth file
> Installing chardetect script to bin/
>
> Using /usr/lib/python3/dist-packages
> Searching for boto==2.49.0
> Best match: boto 2.49.0
> Adding boto 2.49.0 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Searching for appdirs==1.4.4
> Best match: appdirs 1.4.4
> Adding appdirs 1.4.4 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Searching for GitPython==3.1.7
> Best match: GitPython 3.1.7
> Adding GitPython 3.1.7 to easy-install.pth file
>
> Using /usr/lib/python3/dist-packages
> Finished processing dependencies for datalad==0.12.6
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8_datalad/build;
> python3.8 -m nose -v -s -v
> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
> /<>/.pybuild/cpython3_3.8_datalad/build/datalad/tests/test_utils.py:754:
> SyntaxWarning: "is" with a literal. Did you mean "=="?
> assert assure_unicode(1) is 1
> Failure: SkipTest () ... SKIP
> datalad.cmdline.tests.test_helpers.test_strip_arg_from_argv ... ok
> datalad.cmdline.tests.test_helpers.test_get_repo_instance_annex ... ok
> datalad.cmdline.tests.test_helpers.test_get_repo_instance_git ... ok
> datalad.cmdline.tests.test_main.test_version ... ok
> datalad.cmdline.tests.test_main.test_help_np ... ok
> datalad.cmdline.tests.test_main.test_usage_on_insufficient_args ... ok
>
Processed: Re: src:cyrus-imapd: Mail::JMAPTalk version 0.15 required--this is only version 0.13 at ./Cassandane/Cyrus/JMAPCore.pm
Processing control commands: > severity -1 important Bug #966114 [src:cyrus-imapd] src:cyrus-imapd: Mail::JMAPTalk version 0.15 required--this is only version 0.13 at ./Cassandane/Cyrus/JMAPCore.pm Severity set to 'important' from 'serious' -- 966114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966114: src:cyrus-imapd: Mail::JMAPTalk version 0.15 required--this is only version 0.13 at ./Cassandane/Cyrus/JMAPCore.pm
Control: severity -1 important Hi, bug is now fixed in upstream test libraries. > I must say I find it unacceptable that autopkgtests which are being > used to test migration from Debian unstable to Debian testing to rely > on code from random places on the Internet, which Debian Developers > have no control over. I understand your point of view. We found this way to reproduce upstream test in this package that had no test before. What would be the best: * embed test libraries in source package (like apache2) ? + embed copies of dovecot and some other package that exists in Debian but with a different version ? -- or -- + try to patch upstream test to use Debian packages in test ? (I tried without success) * remove autopkgtest files ? * render autopkgtest success "skippable" ? Cheers, Xavier
Bug#966433: [Help] Re: seqan autopkg test failures triggered by gcc-defaults
Hi folks, I tried to reproduce the issue. When I try to run the test in a chroot I get: ... Required dependency:Range-V3 found. -- Required dependency:SDSL found. -- Optional dependency:Cereal found. -- Optional dependency:Lemon not found. -- Optional dependency:ZLIB-1.2.11 found. -- Optional dependency:BZip2-1.0.8 found. -- Optional dependency:libexecinfo found. -- SeqAn3 platform.hpp build: passed. -- Found SeqAn3: /usr/include.. CMake Error at /tmp/autopkgtest.olJ5KS/autopkgtest_tmp/seqan3-test.cmake:104 (include): include could not find load file: seqan3_test_component Call Stack (most recent call first): CMakeLists.txt:11 (include) CMake Error at /tmp/autopkgtest.olJ5KS/autopkgtest_tmp/seqan3-test.cmake:105 (include): include could not find load file: seqan3_test_files Call Stack (most recent call first): CMakeLists.txt:11 (include) CMake Error at /tmp/autopkgtest.olJ5KS/autopkgtest_tmp/seqan3-test.cmake:106 (include): include could not find load file: seqan3_require_ccache Call Stack (most recent call first): CMakeLists.txt:11 (include) CMake Error at /tmp/autopkgtest.olJ5KS/autopkgtest_tmp/seqan3-test.cmake:107 (include): include could not find load file: seqan3_require_benchmark Call Stack (most recent call first): CMakeLists.txt:11 (include) CMake Error at /tmp/autopkgtest.olJ5KS/autopkgtest_tmp/seqan3-test.cmake:108 (include): include could not find load file: seqan3_require_test Call Stack (most recent call first): CMakeLists.txt:11 (include) CMake Error at /tmp/autopkgtest.olJ5KS/autopkgtest_tmp/seqan3-test.cmake:109 (include): include could not find load file: add_subdirectories Call Stack (most recent call first): CMakeLists.txt:11 (include) CMake Error at CMakeLists.txt:32 (seqan3_require_ccache): Unknown CMake command "seqan3_require_ccache". -- Configuring incomplete, errors occurred! See also "/tmp/autopkgtest.olJ5KS/autopkgtest_tmp/build_unit/CMakeFiles/CMakeOutput.log". See also "/tmp/autopkgtest.olJ5KS/autopkgtest_tmp/build_unit/CMakeFiles/CMakeError.log". For me this looks as if test/seqan3-test.cmake needs some patches. Kind regards Andreas. -- http://fam-tille.de
Processed: tagging 948907, tagging 906098, tagging 948853, tagging 948207
Processing commands for cont...@bugs.debian.org: > tags 948907 + pending Bug #948907 [src:ktp-call-ui] ktp-call-ui: FTBFS: QDBusArgument: No such file or directory Added tag(s) pending. > tags 906098 + pending Bug #906098 [kde-telepathy-text-ui] kde-telepathy-text-ui: Invisible characters in the chat window: File not found error message (html url encoded) in textbox. Added tag(s) pending. > tags 948853 + pending Bug #948853 [kaccounts-providers] kaccounts-providers: Broken Google authentication in "Accounts" Added tag(s) pending. > tags 948207 + pending Bug #948207 [kio-gdrive] kio-gdrive: No more work because google temoprarilly supressed the access Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 906098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906098 948207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948207 948853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948853 948907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936699: marked as done (hg-git: Python2 removal in sid/bullseye)
Your message dated Thu, 13 Aug 2020 19:19:50 + with message-id and subject line Bug#936699: fixed in hg-git 0.9.0-1 has caused the Debian Bug report #936699, regarding hg-git: Python2 removal in sid/bullseye 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.) -- 936699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hg-git Version: 0.8.12-1.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:hg-git If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: hg-git Source-Version: 0.9.0-1 Done: Tristan Seligmann We believe that the bug you reported is fixed in the latest version of hg-git, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tristan Seligmann (supplier of updated hg-git 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: Thu, 13 Aug 2020 20:57:14 +0200 Source: hg-git Architecture: source Version: 0.9.0-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Tristan Seligmann Closes: 936699 Changes: hg-git (0.9.0-1) unstable; urgency=medium . * New upstream release. - Python 3 support (closes: #936699). * Bump debhelper from old 11 to 13. + Replace python_distutils buildsystem with pybuild. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Fix day-of-week for changelog entry 0.2.5-1. * Update standards version to 4.5.0, no changes needed. * Set Rules-Requires-Root: no. * B-D: python3-setuptools. Checksums-Sha1: 413b477bf7246be0efad424bb604575a1bb86c7d 1897 hg-git_0.9.0-1.dsc 330739b9c03cb9750ff08a696128b8903facb7d7 129138 hg-git_0.9.0.orig.tar.bz2 b379240ff19c182e7f3ec811a1d7696949dd3a10 6636 hg-git_0.9.0-1.debian.tar.xz
Bug#966894: faucc: FTBFS: parse.tab.c:108:10: fatal error: parse.tab.h: No such file or directory
Hi,
turns out that my patch was not yet working, attached is an even simpler fix.
Cheers,
Stefan.
diff --git a/parse.y b/parse.y
index 3e108e3..57df757 100644
--- a/parse.y
+++ b/parse.y
@@ -21,6 +21,8 @@
#include "expr.h"
%}
+%define api.header.include {"parse.h"}
+
%union {
int nil;
unsigned long long integer;
signature.asc
Description: PGP signature
Processed: [bts-link] source package src:libjna-java
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libjna-java > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #966889 (http://bugs.debian.org/966889) > # Bug title: libjna-java: FTBFS: [exec] dispatch.c:1770:23: error: > alloca bound is unknown [-Werror=alloca-larger-than=] > # * https://github.com/java-native-access/jna/issues/1244 > # * remote status changed: open -> closed > # * closed upstream > tags 966889 + fixed-upstream Bug #966889 [src:libjna-java] libjna-java: FTBFS: [exec] dispatch.c:1770:23: error: ‘alloca’ bound is unknown [-Werror=alloca-larger-than=] Added tag(s) fixed-upstream. > usertags 966889 - status-open Usertags were: status-open. Usertags are now: . > usertags 966889 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 966889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: sylpheed: crash on startup
Processing control commands: > tags -1 + moreinfo Bug #968337 [sylpheed] sylpheed: crash on startup Added tag(s) moreinfo. -- 968337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: sylpheed: crash on startup
Processing control commands: > tags -1 + moreinfo Bug #968372 [libpango-1.0-0] libpango-1.0-0: causes sylpheed to crash on startup Added tag(s) moreinfo. -- 968372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968337: sylpheed: crash on startup
Control: tags -1 + moreinfo On Thu, 13 Aug 2020 at 19:17:08 +0100, Simon McVittie wrote: > If this isn't immediately reproducible in an unconfigured copy of sylpheed > (I haven't tried yet, I don't use it myself), then we'll need more > information than this to be able to diagnose what's happening. I couldn't reproduce this crash myself, so I'll need a backtrace from someone who can. smcv
Bug#968372: sylpheed: crash on startup
On Thu, 13 Aug 2020 at 19:31:38 +0200, Francesco Poli wrote:
> On Thu, 13 Aug 2020 09:20:30 +0100 Matthew Munro
> wrote:
> > Following libpango-1.0-0 (and others) upgrade this morning, gdb reports:
> >
> > Thread 1 "sylpheed" received signal SIGSEGV, Segmentation fault.
> > 0xb73cfebf in pango_renderer_part_changed ()
> >from /usr/lib/i386-linux-gnu/libpango-1.0.so.0
If this isn't immediately reproducible in an unconfigured copy of sylpheed
(I haven't tried yet, I don't use it myself), then we'll need more
information than this to be able to diagnose what's happening. Please
quote the whole backtrace, preferably after installing debugging
symbols for pango, sylpheed and any other libraries that show up in the
backtrace.
More information on detached debug symbols and getting a backtrace:
https://wiki.debian.org/HowToGetABacktrace
> I do not know whether a fix is needed in sylpheed or in libpango-1.0-0,
> but a RC bug report against libpango-1.0-0 is necessary in order to
> prevent its migration to testing.
My understanding had been that the preferred representation for that is to
reassign the bug to *both* packages ("reassign -1 libpango-1.0-0,sylpheed",
"found -1 pango1.0/x.y.z", "found -1 sylpheed/u.v.w"), which avoids having
to either duplicate relevant information between the two bugs, or have
the information only show up in one of the two places.
Thanks,
smcv
Processed: [bts-link] source package lynis
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package lynis > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #965359 (http://bugs.debian.org/965359) > # Bug title: lynis: Denial of service by user creating symlink to /, disk > space exhaustion due to verbose logging > # * https://github.com/CISOfy/lynis/issues/991 > # * remote status changed: open -> closed > # * closed upstream > tags 965359 + fixed-upstream Bug #965359 [lynis] lynis: Denial of service by user creating symlink to /, disk space exhaustion due to verbose logging Added tag(s) fixed-upstream. > usertags 965359 - status-open Usertags were: status-open. Usertags are now: . > usertags 965359 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 965359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968337: sylpheed: crash on startup
Control: clone -1 -2 Control: reassign -2 libpango-1.0-0 1.46.0-1 Control: affects -2 + sylpheed Control: retitle -2 libpango-1.0-0: causes sylpheed to crash on startup On Thu, 13 Aug 2020 09:20:30 +0100 Matthew Munro wrote: > Package: sylpheed > Version: 3.7.0-8 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: bugzilla...@gmail.com > > Dear Maintainer, > > Following libpango-1.0-0 (and others) upgrade this morning, gdb reports: > > > Thread 1 "sylpheed" received signal SIGSEGV, Segmentation fault. > 0xb73cfebf in pango_renderer_part_changed () >from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 [...] > ii libpango-1.0-0 1.46.0-1 [...] Hello, I am a user of Sylpheed who has just noticed your bug report. Since (on Debian testing) sylpheed/3.7.0-8 works correctly with libpango-1.0-0/1.44.7-4 , I would say that it is important to prevent the migration of libpango-1.0-0/1.46.0-1 from unstable to testing, until this issue is fixed. I do not know whether a fix is needed in sylpheed or in libpango-1.0-0, but a RC bug report against libpango-1.0-0 is necessary in order to prevent its migration to testing. I am consequently cloning this bug report and reassigning the clone to package libpango-1.0-0. Dear pango1.0 maintainers, please do not reassign back or downgrade this bug report, until the issue is solved for the best. Thanks. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpsvIfaf22Ig.pgp Description: PGP signature
Processed: Re: sylpheed: crash on startup
Processing control commands: > clone -1 -2 Bug #968337 [sylpheed] sylpheed: crash on startup Bug 968337 cloned as bug 968372 > reassign -2 libpango-1.0-0 1.46.0-1 Bug #968372 [sylpheed] sylpheed: crash on startup Bug reassigned from package 'sylpheed' to 'libpango-1.0-0'. No longer marked as found in versions sylpheed/3.7.0-8. Ignoring request to alter fixed versions of bug #968372 to the same values previously set Bug #968372 [libpango-1.0-0] sylpheed: crash on startup Marked as found in versions pango1.0/1.46.0-1. > affects -2 + sylpheed Bug #968372 [libpango-1.0-0] sylpheed: crash on startup Added indication that 968372 affects sylpheed > retitle -2 libpango-1.0-0: causes sylpheed to crash on startup Bug #968372 [libpango-1.0-0] sylpheed: crash on startup Changed Bug title to 'libpango-1.0-0: causes sylpheed to crash on startup' from 'sylpheed: crash on startup'. -- 968337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968337 968372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957829: marked as done (spacefm: ftbfs with GCC-10)
Your message dated Thu, 13 Aug 2020 17:04:12 + with message-id and subject line Bug#957829: fixed in spacefm 1.0.6-5 has caused the Debian Bug report #957829, regarding spacefm: 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.) -- 957829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spacefm Version: 1.0.6-4 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/spacefm_1.0.6-4_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/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:322: multiple definition of `evt_pnl_sel'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:322: first defined here /usr/bin/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:321: multiple definition of `evt_pnl_focus'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:321: first defined here /usr/bin/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:320: multiple definition of `evt_pnl_show'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:320: first defined here /usr/bin/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:319: multiple definition of `evt_win_close'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:319: first defined here /usr/bin/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:318: multiple definition of `evt_win_key'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:318: first defined here /usr/bin/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:317: multiple definition of `evt_win_click'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:317: first defined here /usr/bin/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:316: multiple definition of `evt_win_move'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:316: first defined here /usr/bin/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:315: multiple definition of `evt_win_focus'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:315: first defined here /usr/bin/ld: spacefm-find-files.o:./debian/build-gtk2/src/../../../src/settings.h:124: multiple definition of `xsets'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:124: first defined here /usr/bin/ld: spacefm-go-dialog.o:./debian/build-gtk2/src/../../../src/settings.h:379: multiple definition of `settings_graphical_su'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:379: first defined here /usr/bin/ld: spacefm-go-dialog.o:./debian/build-gtk2/src/../../../src/settings.h:378: multiple definition of `settings_terminal_su'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:378: first defined here /usr/bin/ld: spacefm-go-dialog.o:./debian/build-gtk2/src/../../../src/settings.h:330: multiple definition of `xset_cmd_history'; vfs/spacefm-vfs-file-info.o:./debian/build-gtk2/src/../../../src/settings.h:330: first defined here /usr/bin/ld: spacefm-go-dialog.o:./debian/build-gtk2/src/../../../src/settings.h:327: multiple definition of `evt_device';
Bug#950131: marked as done (mixxx: Baseline violation on i386)
Your message dated Thu, 13 Aug 2020 16:33:40 + with message-id and subject line Bug#950131: fixed in mixxx 2.2.4~dfsg-1 has caused the Debian Bug report #950131, regarding mixxx: Baseline violation 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.) -- 950131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mixxx Version: 2.0.0~dfsg-7 Severity: serious The package builds with -msse2, but SSE (or MMX) are not part of the baseline of the i386 port. --- End Message --- --- Begin Message --- Source: mixxx Source-Version: 2.2.4~dfsg-1 Done: m...@debian.org (Matteo F. Vescovi) We believe that the bug you reported is fixed in the latest version of mixxx, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated mixxx 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: Thu, 13 Aug 2020 18:17:10 +0200 Source: mixxx Architecture: source Version: 2.2.4~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Matteo F. Vescovi Closes: 950131 Changes: mixxx (2.2.4~dfsg-1) unstable; urgency=medium . * Team upload . * New upstream release * debian/patches/: patchset updated against v2.2.4 - 0005-scons-3.patch dropped (applied upstream) - 0005-remove_inappropriate_i386_flags.patch added (Closes: #950131) - 0006-features_fix.patch added * debian/copyright: by-tab indentation removed * debian/control: - debhelper bump 11 -> 13 - S-V bump 4.4.1 -> 4.5.0 (no changes needed) - RRR set - add missing b-dep libmodplug-dev - drop myself from Uploaders * debian/mixxx.install: add missing install path * debian/rules: - update clean path for pyc files - drop duplicate files on install Checksums-Sha1: 02ddcbbc8eb1d15522a37853c9cffaed89ac2b8f 2956 mixxx_2.2.4~dfsg-1.dsc 96293f2d8fd16b57723e92540ae070e3b62e 15337716 mixxx_2.2.4~dfsg.orig.tar.xz 98104bdbf3a5893c9e1bbff6527472b85c3f6830 21156 mixxx_2.2.4~dfsg-1.debian.tar.xz 57352de23436f9c4dc9b055763b786e9565609d9 7819 mixxx_2.2.4~dfsg-1_source.buildinfo Checksums-Sha256: 9759ae4bb1a1b15d12b954627288e5cd4a60bdfb484484371d4dbeefdaaccb66 2956 mixxx_2.2.4~dfsg-1.dsc bd1478b3fd43e27ecbb32ed729cc5c8a6dd8de13dcd52eca06d6772cdfcc32f7 15337716 mixxx_2.2.4~dfsg.orig.tar.xz 82731e03cc4b64a08e8688f8c9ecda96914a9d7e1ddee426c7d91e2358ca94fc 21156 mixxx_2.2.4~dfsg-1.debian.tar.xz 9c2ab8addf93bb991c696e74fc1fa2f53c3e919d7ce305a49d1811c979c82102 7819 mixxx_2.2.4~dfsg-1_source.buildinfo Files: 65c9e91d382dcc9cbbf591e5ac70b141 2956 sound optional mixxx_2.2.4~dfsg-1.dsc 1f6d460756bef34fd5651ca03e17f942 15337716 sound optional mixxx_2.2.4~dfsg.orig.tar.xz b4b6710bc6a4bc16ae485db5c02be00c 21156 sound optional mixxx_2.2.4~dfsg-1.debian.tar.xz 73494e285d99357615d9f0a7fb878c76 7819 sound optional mixxx_2.2.4~dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Debian powered! iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAl81Z8RfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N zVrHGg//UgjFr3AAi22ZtjzSPowiANQ/alnGXvEiPnYNhj2XXcbHnFPmoMEg2mMn Vt10GYkPxSTxTIvhUz0GyPh9b6waY4kvBLcGf8CmT9iDmDBb5yvjnmOyYplFewKn gg1RX8QRLFKEojRvOOd1lnDFgfj94kKnZPJClqjVJb6UbhJKVZk3EzNaof7rNd4C a8GDrHGcODJPzmct1In1lNSvTXUDjQAei0g6ruQp3NXPYpiO6WayKLkhMiwb5H/u mQrvPg4Xdfi/8YsF3prHzdRIbtHcMeILe7r/+HCBuGhceMHUynZ2uo5R74Q7ji1n JqTBFuQGkFFNa4PkA2/qJWQb9RoWHZM0ROd3jUP3vDp1LHQEDmZx85/F4myRdUPq ljUuPpeyWKKkcS7D1ZgW3ekyRTjT+d34imUh+KkVHGnEOuqzlUXBhJRDOI6XrZm/ k57dwPWMlEI5WTiJya+8zC/EAiT41I3rKGaYKHMPxv8y70bUme0Wm4OydMOBP0su hgHl+AP73WR4Dm1DzAXxX2dOnhEA0DcxHsRKe7tQLxBSdfxvz8BlQWm5xTJ6Bqbf ts9fJtL6n+GeI7KfipmGyhNxTxmNw4zSRADq+dhrEncWThsLmTPh1wKYi0hA/WX9 Ri1kV83q5Fhz21hTKnh8kmsdFqc1RMHubuZT2SHhkdodAwhel9I= =N4MM -END PGP SIGNATURE End Message ---
Bug#943164: marked as done (pidcat: Python2 removal in sid/bullseye)
Your message dated Thu, 13 Aug 2020 16:07:13 + with message-id and subject line Bug#943164: fixed in pidcat 2.1.0-4 has caused the Debian Bug report #943164, regarding pidcat: Python2 removal in sid/bullseye 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.) -- 943164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pidcat Version: 2.1.0-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: pidcat Source-Version: 2.1.0-4 Done: Manas Kashyap We believe that the bug you reported is fixed in the latest version of pidcat, 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. Manas Kashyap (supplier of updated pidcat 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: Thu, 13 Aug 2020 20:00:07 +0530 Source: pidcat Architecture: source Version: 2.1.0-4 Distribution: unstable Urgency: medium Maintainer: Hans-Christoph Steiner Changed-By: Manas Kashyap Closes: 943164 Changes: pidcat (2.1.0-4) unstable; urgency=medium . * Team upload * migrating to python3, patch included (Closes: #943164) . [ Hans-Christoph Steiner ] * Rules-Requires-Root: no Checksums-Sha1: 1c8e16b1620ea113881e9c2608c98dd97e1831bf 1612 pidcat_2.1.0-4.dsc 73c41a749731139428c3bb4e4face5877dede4a5 6108 pidcat_2.1.0-4.debian.tar.xz 901bd99d9610093509992ef565a9257b854f4a22 5603 pidcat_2.1.0-4_source.buildinfo Checksums-Sha256: 2a2fb1b68658e83e6f5792d537a992ba00b9f9268593842cca8d3d9660682d2d 1612 pidcat_2.1.0-4.dsc 448eb7ae5aa2d23927bc433add9477cd55c7584b74875e0576431d284d79415b 6108 pidcat_2.1.0-4.debian.tar.xz 1d1e691f277aeec3d593578a2dccef96450bf7c113b358bf2fa075942d089312 5603 pidcat_2.1.0-4_source.buildinfo Files: 9ba52b8ecbc4019a430d6385acf7be1d 1612 devel optional pidcat_2.1.0-4.dsc 4290b6fa845f4fb00f5c823a574c38f2 6108 devel optional pidcat_2.1.0-4.debian.tar.xz
Bug#966911: marked as done (mame: FTBFS: ../../../../../3rdparty/sol2/sol/stack_push.hpp:549:39: error: call of overloaded ‘push(lua_State*&, const wchar_t [2], const wchar_t*)’ is amb
Your message dated Thu, 13 Aug 2020 15:50:52 +
with message-id
and subject line Bug#966911: fixed in mame 0.223+dfsg.1-1
has caused the Debian Bug report #966911,
regarding mame: FTBFS: ../../../../../3rdparty/sol2/sol/stack_push.hpp:549:39:
error: call of overloaded ‘push(lua_State*&, const wchar_t [2],
const wchar_t*)’ is ambiguous
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.)
--
966911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mame
Version: 0.222+dfsg.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -g0 -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
> -D_FORTIFY_SOURCE=2 -MMD -MP -MP -DPTR64=1 -DNDEBUG -DCRLF=2 -DLSB_FIRST
> -DXMD_H -DFLAC__NO_DLL -DNATIVE_DRC=drcbe_x64 -DLUA_COMPAT_ALL
> -DLUA_COMPAT_5_1 -DLUA_COMPAT_5_2 -DNO_AFFINITY_NP -I"../../../../../src/osd"
> -I"../../../../../src/emu" -I"../../../../../src/devices"
> -I"../../../../../src/mame" -I"../../../../../src/lib"
> -I"../../../../../src/lib/util" -I"../../../../../src/lib/netlist"
> -I"../../../../../3rdparty" -I"../../../../generated/mame/layout"
> -I"../../../../../scripts" -m64 -pipe -O3 -fno-strict-aliasing
> -Wno-unknown-pragmas -Wall -Wcast-align -Wundef -Wformat-security
> -Wwrite-strings -Wno-sign-compare -Wno-conversion
> -Wno-error=deprecated-declarations -Wno-unused-result -Wno-array-bounds
> -Wno-format-overflow -Wno-stringop-truncation -Wno-stringop-overflow
> -Wno-return-local-addr -m64 -std=c++14 -Woverloaded-virtual
> -Wno-class-memaccess -Wsuggest-override -flifetime-dse=1 -include
> ../../../../linux_gcc/obj/x64/Release/emu.h -o
> "../../../../linux_gcc/obj/x64/Release/src/mame/drivers/fidel_excel.o" -c
> "../../../../../src/mame/drivers/fidel_excel.cpp"
> In file included from ../../../../../3rdparty/sol2/sol/stack.hpp:30,
> from ../../../../../3rdparty/sol2/sol/object.hpp:26,
> from ../../../../../3rdparty/sol2/sol/proxy.hpp:26,
> from ../../../../../3rdparty/sol2/sol/table_core.hpp:25,
> from ../../../../../3rdparty/sol2/sol/table.hpp:25,
> from ../../../../../3rdparty/sol2/sol/state_view.hpp:26,
> from ../../../../../3rdparty/sol2/sol/state.hpp:25,
> from ../../../../../3rdparty/sol2/sol.hpp:45,
> from ../../../../../src/frontend/mame/luaengine.h:27,
> from ../../../../../src/frontend/mame/clifront.cpp:19:
> ../../../../../3rdparty/sol2/sol/stack_push.hpp: In instantiation of ‘static
> int sol::stack::pusher::push(lua_State*, const wchar_t (&)[N],
> std::size_t) [with long unsigned int N = 2; lua_State = lua_State;
> std::size_t = long unsigned int]’:
> ../../../../../3rdparty/sol2/sol/stack_core.hpp:173:48: required from ‘int
> sol::stack::push(lua_State*, T&&, Args&& ...) [with T = const wchar_t (&)[2];
> Args = {int}; lua_State = lua_State]’
> ../../../../../3rdparty/sol2/sol/stack_push.hpp:579:33: required from here
> ../../../../../3rdparty/sol2/sol/stack_push.hpp:549:39: error: call of
> overloaded ‘push(lua_State*&, const wchar_t [2], const
> wchar_t*)’ is ambiguous
> 549 | return stack::push(L, str, str + sz);
> |~~~^~
> In file included from ../../../../../3rdparty/sol2/sol/stack.hpp:25,
> from ../../../../../3rdparty/sol2/sol/object.hpp:26,
> from ../../../../../3rdparty/sol2/sol/proxy.hpp:26,
> from ../../../../../3rdparty/sol2/sol/table_core.hpp:25,
> from ../../../../../3rdparty/sol2/sol/table.hpp:25,
> from ../../../../../3rdparty/sol2/sol/state_view.hpp:26,
> from ../../../../../3rdparty/sol2/sol/state.hpp:25,
> from ../../../../../3rdparty/sol2/sol.hpp:45,
> from ../../../../../src/frontend/mame/luaengine.h:27,
> from ../../../../../src/frontend/mame/clifront.cpp:19:
> ../../../../../3rdparty/sol2/sol/stack_core.hpp:172:14: note: candidate: ‘int
> sol::stack::push(lua_State*, T&&, Args&& ...) [with T = const wchar_t*; Args
> = {const wchar_t*};
Bug#968366: libproxy#126: buffer overflow when PAC is enabled
Source: libproxy Version: 0.4.14-2 Severity: grave Justification: user security hole Tags: security upstream Forwarded: https://github.com/libproxy/libproxy/pull/126 X-Debbugs-Cc: Debian Security Team Li Fei (@lifeibiren on Github) reported that if the server serving a PAC file sends more than 102400 bytes without a Content-Length present, libproxy can overflow its buffer by PAC_HTTP_BLOCK_SIZE (512) bytes. This PR is said to fix it, although I have not reviewed it in detail, and it would be better if someone who knows C++ better than me did the review: https://github.com/libproxy/libproxy/pull/126 Thanks to Michael Catanzaro for highlighting this as likely to be a security vulnerability during a more general conversation about libproxy. (Please reduce severity as desired if this is succesfully mitigated by some security measure - I'm assuming stack smashing is arbitrary code execution, but maybe it's just DoS.) >From source code inspection, versions >= 0.4.14-2 in stretch appear to be vulnerable. 0.4.11-4 in jessie does not appear to be vulnerable, because it assumes absence of Content-Length means a length of 0 (which is a bug, but not a security bug). Intermediate versions between jessie and stretch not checked. smcv
Processed: bug 968362 is forwarded to https://github.com/maxmind/MaxMind-DB-Writer-perl/issues/112
Processing commands for cont...@bugs.debian.org: > forwarded 968362 https://github.com/maxmind/MaxMind-DB-Writer-perl/issues/112 Bug #968362 [src:libmaxmind-db-writer-perl] FTBFS: test failures on some architectures Set Bug forwarded-to-address to 'https://github.com/maxmind/MaxMind-DB-Writer-perl/issues/112'. > thanks Stopping processing here. Please contact me if you need assistance. -- 968362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968362: FTBFS: test failures on some architectures
Source: libmaxmind-db-writer-perl Version: 0.33-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libmaxmind-db-writer-perl never built on all architectures: https://buildd.debian.org/status/logs.php?pkg=libmaxmind-db-writer-perl The history of the uploads goes like this: 0.33-1: testsuite disabled Result: successful build on all architectures where all build dependencies are available (esp. libmath-int128-perl is missing on quite a few). 0.33-2: testsuite enabled but tests needing Test::HexDifferences skipped (as it was not yet packaged) Result: additional failures in the tests on ppc64, s390x, sparc64 As (only) s390x is a release architecture, the package never migrated to testing. 0.33-3: all tests are run after libtest-hexdifferences entered the archive. Result: same as for 0.33-2 Logs of the failures (for 0.33-3): ppc64: https://buildd.debian.org/status/fetch.php?pkg=libmaxmind-db-writer-perl=ppc64=0.33-3=1596597051=0 sparc64: https://buildd.debian.org/status/fetch.php?pkg=libmaxmind-db-writer-perl=sparc64=0.33-3=1596597463=0 s390x: https://buildd.debian.org/status/fetch.php?pkg=libmaxmind-db-writer-perl=s390x=0.33-3=1596578449=0 The failing tests are always the same, quoting from the s390x log: # Failed test 'No tests run for subtest "Tree with 256 networks - IPv4 only - 24-bit records"' # at t/MaxMind/DB/Writer/Tree-freeze-thaw.t line 62. Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offset 1 of input at srl_decoder.c line 600 at /<>/blib/lib/MaxMind/DB/Writer/Tree.pm line 403. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 1. t/MaxMind/DB/Writer/Tree-freeze-thaw.t . # Subtest: Tree with 256 networks - IPv4 only - 24-bit records 1..0 not ok 1 - No tests run for subtest "Tree with 256 networks - IPv4 only - 24-bit records" Dubious, test returned 255 (wstat 65280, 0xff00) Failed 1/1 subtests […] Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offset 1 of input at srl_decoder.c line 600 at /<>/blib/lib/MaxMind/DB/Writer/Tree.pm line 403. t/MaxMind/DB/Writer/Tree-output/freeze-thaw-record-size.t .. Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run […] Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offset 1 of input at srl_decoder.c line 600 at /<>/blib/lib/MaxMind/DB/Writer/Tree.pm line 403. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 21. t/MaxMind/DB/Writer/Tree-record-collisions.t ... […] Dubious, test returned 255 (wstat 65280, 0xff00) All 21 subtests passed […] # Failed test 'Run without exceptions' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 86. # Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offset 1 of input at srl_decoder.c line 600 at /<>/blib/lib/MaxMind/DB/Writer/Tree.pm line 403. # Looks like you failed 1 test of 1. # Failed test 'check defaults work' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 89. # Failed test 'Run without exceptions' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 86. # Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offset 1 of input at srl_decoder.c line 600 at /<>/blib/lib/MaxMind/DB/Writer/Tree.pm line 403. # Looks like you failed 1 test of 1. # Failed test 'check no merging explictly' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 89. # Failed test 'Run without exceptions' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 86. # Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offset 1 of input at srl_decoder.c line 600 at /<>/blib/lib/MaxMind/DB/Writer/Tree.pm line 403. # Looks like you failed 1 test of 1. # Failed test 'check no merging and none explictly' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 89. # Failed test 'Run without exceptions' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 86. # Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offset 1 of input at srl_decoder.c line 600 at /<>/blib/lib/MaxMind/DB/Writer/Tree.pm line 403. # Looks like you failed 1 test of 1. # Failed test 'set mrc in constructor, toplevel in thaw' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 89. # Failed test 'Run without exceptions' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 86. # Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offset 1 of input at srl_decoder.c line 600 at /<>/blib/lib/MaxMind/DB/Writer/Tree.pm line 403. # Looks like you failed 1 test of 1. # Failed test 'set toplevel in constructor' # at t/MaxMind/DB/Writer/Tree-thaw-merge.t line 89. # Failed test 'Run without
Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Hello, wanted to add that the issue gets triggered when running the following script: #!/bin/sh if [ -x /usr/bin/certbot ]; then certbot -q--authenticator standalone \ --installer none renew \ --pre-hook "service apache2 stop" \ --post-hook "service apache2 start" sleep 60 /bin/systemctl restart apache2 fi if i run this script using previous kernel ( linux-image-4.19.0-9-amd64 ) no kernel crash is happening. tobias.
Bug#964908:
Success report. tomcat 9.0.37-3 works fine now. Thank you!
Processed: reassign 946046 to src:meta-unison
Processing commands for cont...@bugs.debian.org:
> reassign 946046 src:meta-unison
Bug #946046 {Done: =?utf-8?q?St=C3=A9phane_Glondu?= }
[unison-all] unison-all should also depend on the old unison version,
compatible with Debian 10
Bug reassigned from package 'unison-all' to 'src:meta-unison'.
No longer marked as found in versions meta-unison/2.48.4+2 and
meta-unison/2.48+2.
No longer marked as fixed in versions meta-unison/2.48.4+3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
946046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#964670: gsettings-qt: FTBFS: QQmlComponent: Component is not ready
Hi, On Do 01 Jan 1970 01:00:00 CET, handsome_feng wrote: Hi, Is there any progress on this? I found that it failed when running `$$[QT_INSTALL_BINS]/qmlplugindump -notrelocatable GSettings 1.0 ..` , but I can only reproduce it when pdebuild. And with the same generated file, If I chroot the pbuilder environment and mount the build dir, cd the GSettings dir and run `qmlplugindump -notrelocatable GSettings 1.0 ..`, it will failed with "QQmlComponent: Component is not ready", but if I run the same command in the same build dir in my local environment, everything is fine. Could it be a lack of dependency? regards, handsome_feng I have indeed made the same observation: local sid chroot with many packages installed (B-Ds of other packages mainly) -> the build works. Build in a clean chroot (via sbuild) -> build fails. I already started looking into this, but had to reprioritize. I will give more time to this (hopefully) the coming week. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpEzr3sS7ebK.pgp Description: Digitale PGP-Signatur
Bug#968338: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Hello, please close this bug. bug 968335 is about the same issue and does contain the relevant kernel log. tobias.
Bug#956556: marked as done (coinst FTBFS: Error: The implementation ptset.ml does not match the interface ptset.cmi)
Your message dated Thu, 13 Aug 2020 14:33:31 + with message-id and subject line Bug#956556: fixed in coinst 1.9.3-2 has caused the Debian Bug report #956556, regarding coinst FTBFS: Error: The implementation ptset.ml does not match the interface ptset.cmi 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.) -- 956556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coinst Version: 1.9.3-1 Severity: serious Tags: ftbfs bullseye sid https://buildd.debian.org/status/package.php?p=coinst ... usr/bin/make opt make[2]: Entering directory '/<>' ocamlfind ocamlc -package unix,str,bigarray,cudf -g -I viewer -annot -bin-annot -safe-string -c ptset.mli ocamlfind ocamlopt -package unix,str,bigarray,cudf -g -I viewer -annot -bin-annot -safe-string -c ptset.ml File "ptset.ml", line 305, characters 12-30: 305 | List.sort Pervasives.compare (elements_aux [] s) ^^ Alert deprecated: module Stdlib.Pervasives Use Stdlib instead. If you need to stay compatible with OCaml < 4.07, you can use the stdlib-shims library: https://github.com/ocaml/stdlib-shims File "ptset.ml", line 567, characters 14-32: 567 | List.sort Pervasives.compare (elements_aux [] s) ^^ Alert deprecated: module Stdlib.Pervasives Use Stdlib instead. If you need to stay compatible with OCaml < 4.07, you can use the stdlib-shims library: https://github.com/ocaml/stdlib-shims File "ptset.ml", line 1: Error: The implementation ptset.ml does not match the interface ptset.cmi: ... In module Big: The value `of_seq' is required but not provided File "set.mli", line 282, characters 4-31: Expected declaration In module Big: The value `add_seq' is required but not provided File "set.mli", line 278, characters 4-37: Expected declaration In module Big: The value `to_seq' is required but not provided File "set.mli", line 274, characters 4-31: Expected declaration In module Big: The value `to_seq_from' is required but not provided File "set.mli", line 269, characters 4-43: Expected declaration In module Big: The value `find_last_opt' is required but not provided File "set.mli", line 254, characters 4-55: Expected declaration In module Big: The value `find_last' is required but not provided File "set.mli", line 247, characters 4-44: Expected declaration In module Big: The value `find_first_opt' is required but not provided File "set.mli", line 240, characters 4-56: Expected declaration In module Big: The value `find_first' is required but not provided File "set.mli", line 227, characters 4-45: Expected declaration In module Big: The value `find_opt' is required but not provided File "set.mli", line 221, characters 4-40: Expected declaration In module Big: The value `choose_opt' is required but not provided File "set.mli", line 199, characters 4-35: Expected declaration In module Big: The value `max_elt_opt' is required but not provided File "set.mli", line 188, characters 4-36: Expected declaration In module Big: The value `min_elt_opt' is required but not provided File "set.mli", line 177, characters 4-36: Expected declaration In module Big: The value `map' is required but not provided File "set.mli", line 126, characters 4-35: Expected declaration In module Big: The value `disjoint' is required but not provided File "set.mli", line 101, characters 4-32: Expected declaration make[2]: *** [Makefile:69: ptset.cmx] Error 2 --- End Message --- --- Begin Message --- Source: coinst Source-Version: 1.9.3-2 Done: =?utf-8?q?St=C3=A9phane_Glondu?= We believe that the bug you reported is fixed in the latest version of coinst, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated coinst 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
Bug#968275: marked as done (wtdbg2,wtdbg2-examples: both ship /usr/lib/wtdbg2/simd-dispatch)
Your message dated Thu, 13 Aug 2020 14:34:30 + with message-id and subject line Bug#968275: fixed in wtdbg2 2.5-6 has caused the Debian Bug report #968275, regarding wtdbg2,wtdbg2-examples: both ship /usr/lib/wtdbg2/simd-dispatch 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.) -- 968275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wtdbg2,wtdbg2-examples Version: 2.5-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../wtdbg2-examples_2.5-5_all.deb ... Unpacking wtdbg2-examples (2.5-5) ... dpkg: error processing archive /var/cache/apt/archives/wtdbg2-examples_2.5-5_all.deb (--unpack): trying to overwrite '/usr/lib/wtdbg2/simd-dispatch', which is also in package wtdbg2 2.5-5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/wtdbg2-examples_2.5-5_all.deb cheers, Andreas wtdbg2=2.5-5_wtdbg2-examples=2.5-5.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: wtdbg2 Source-Version: 2.5-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of wtdbg2, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated wtdbg2 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: Thu, 13 Aug 2020 15:16:51 +0200 Source: wtdbg2 Architecture: source Version: 2.5-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 968275 Changes: wtdbg2 (2.5-6) unstable; urgency=medium . * Make sure simd-dispatch will be installed only in main package Closes: #968275 Checksums-Sha1: c34d01138009eed44d44deae58b75169613a26a5 2075 wtdbg2_2.5-6.dsc 929662fb4138ccc7b6d5763df5879d4f3d61e6c3 121142716 wtdbg2_2.5-6.debian.tar.xz d604ed2a3d191480d250cefe5e0eb4124796cddc 5963 wtdbg2_2.5-6_amd64.buildinfo Checksums-Sha256: 1ac1b406d132fa76afd6a12399c06127961fbdb917791033c68f4fa76068c4ba 2075 wtdbg2_2.5-6.dsc 75cfb08830e177dd332560568d993e69b01f89432ed22abf938e3c9bb50dd22e 121142716 wtdbg2_2.5-6.debian.tar.xz 0060f2eae5034bbd6bbd2dfdd6d28788f68043f508c7edd560fb59e1a2009342 5963 wtdbg2_2.5-6_amd64.buildinfo Files: ff764914f81f278effd986d6cf14a8ef 2075 science optional wtdbg2_2.5-6.dsc 7c3d451f58ed0c5324a60c3c70e8c39a 121142716 science optional wtdbg2_2.5-6.debian.tar.xz 60d7a64847f22e63f078eaf0f7a860c2 5963 science optional wtdbg2_2.5-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl81RGgRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGKSw/+PxRCc5klOEA5OgkTYyr+u8rfYJzMMJj0 jfBWNvlpaLnxAHi0s7Ywk5aEb4fGCZyTjHIGN7X93vQlhsDre3j1UvbDfzETg6pB UvbjZaCyPrT/jiPUzhdTn7RO/g4C7b373coZxm2wpQUXmZzrFh4yGAvUYb+ABYuA ZVXYgqrcCX8SNk1BJE63s1spwY9Jk0TGTaw0m8ykyih4bK6GGFRLitM06r7Cbl/T 5JETw5rjUJXxp7gnSVt9LAMXI2bEUU5w3YIVJ596vbjtsa/CWhQ9dJe32tWG8pys WJZvaCf/nNW7uWD6qb875GWdR+7kXshx0VBEx390KySvEgw0icwEh3aibykT53AW krIcfHfgc2RJLb+/JwWNJ0yMwQldB8TMIhWob3yw3HRXQ1PV/oPqVdROB8APn58k wnDAEv4IHkt8BDgQkFHnJj3x1wDaTXHD+ENSM0jorWsGXABvfsaUan8SBgE06Otb 0B9Bkl/wHr0Zwzg3kSTfg/9VVCtPIdopP2a+TdZl5m9CTH1094tykZs5shVWVwN6 AOUl1BtltfVO9mrkk0ETVuMQqM8rKWV3UEiCUngW7gjfveoAVhJWnAFILBPkl/4V LuPOslLHPc7jpdOnuG341VA/PBingdVDq1/vnkO5FC/k9Vw4p8aqjWM6sv3oy186 UnhAhUMK2lQ= =t2NM -END PGP SIGNATURE End Message ---
Bug#966289: Reassign
Control: reassign -1 ftp.debian.org
Processed: Reassign
Processing control commands: > reassign -1 ftp.debian.org Bug #966289 [python-pytc] RM: python-pytc -- ROM; python2-only; no rdeps; extremely low popcon Bug reassigned from package 'python-pytc' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #966289 to the same values previously set Ignoring request to alter fixed versions of bug #966289 to the same values previously set -- 966289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966289: (no subject)
Control: reassign -1 ftp.debian.org
Bug#966289: (no subject)
reassign -1 ftp.debian.org
Bug#967132: marked as done (fyre: Unversioned Python removal in sid/bullseye)
Your message dated Thu, 13 Aug 2020 11:10:37 +0200 with message-id <42a4d27cad82bac3db7dde1e961ca...@debian.org> and subject line Re: Bug#967132: fyre: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967132, regarding fyre: Unversioned Python removal in sid/bullseye 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.) -- 967132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fyre Version: 1.0.1-6 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Le 04/08/2020 11:27, Matthias Klose a écrit : Your package either build-depends, depends on one of those packages. No, it doesn’t. There was an indirect build-dependency through libglade2-dev but you’ve fixed that :-). Regards, Stephen--- End Message ---
Bug#968342: marked as done (libgegl-sc-0.4.so: undefined symbol: __exp_finite)
Your message dated Thu, 13 Aug 2020 13:29:32 +0100 with message-id <20200813122932.ga491...@espresso.pseudorandom.co.uk> and subject line Re: Bug#968342: libgegl-sc-0.4.so: undefined symbol: __exp_finite has caused the Debian Bug report #968342, regarding libgegl-sc-0.4.so: undefined symbol: __exp_finite 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.) -- 968342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gimp Version: 2.10.8-2 Severity: grave Justification: renders package unusable Dear Maintainer, Gimp does not start anymore (even after new install) $ gimp GEGL-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/seamless-clone.so' load error: /lib/x86_64-linux-gnu/libgegl-sc-0.4.so: undefined symbol: __exp_finite GEGL operation missing! GIMP requires the GEGL operation "gegl:seamless-clone". This operation cannot be found. Check your GEGL install and ensure it has been compiled with any dependencies required for GIMP. So it it not possible anymore to use Gimp. On an other computer we have the same issue. It worked before. -- System Information: Debian Release: 10.5 Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.8-2 ii libaa1 1.4p5-46 ii libbabl-0.1-00.1.62-1 ii libbz2-1.0 1.0.6-9.2~deb10u1 ii libc62.31-2 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.10.1-2 ii libgcc-s1 [libgcc1] 10-20200211-1 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgegl-0.4-00.4.12-2 ii libgexiv2-2 0.10.9-1 ii libgimp2.0 2.10.8-2 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgs9 9.27~dfsg-2+deb10u3 ii libgtk2.0-0 2.24.32-3 ii libgudev-1.0-0 232-2 ii libharfbuzz0b2.3.1-1 ii libheif1 1.3.2-2~deb10u1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-3 ii liblzma5 5.2.4-1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.3-0 1.3.0-2.1 ii libopenexr23 2.2.1-4.1 ii libopenjp2-7 2.3.0-2+deb10u1 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpangocairo-1.0-0 1.42.4-8~deb10u1 ii libpangoft2-1.0-01.42.4-8~deb10u1 ii libpng16-16 1.6.36-6 ii libpoppler-glib8 0.71.0-5 ii librsvg2-2 2.44.10-2.1 ii libstdc++6 9.2.1-8 ii libtiff5 4.1.0+git191117-2~deb10u1 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2 ii libwmf0.2-7 0.2.8.4-14 ii libx11-6 2:1.6.7-1 ii libxcursor1 1:1.1.15-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-1+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gimp recommends: ii ghostscript 9.27~dfsg-2+deb10u3 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help pn gimp-python ii gvfs-backends 1.38.1-5 ii libasound21.1.8-1 -- no debconf information --- End Message --- --- Begin Message --- Version: 0.4.18-1 On Thu, 13 Aug 2020 at 13:24:54 +0100, Simon McVittie wrote: > On Thu, 13 Aug 2020 at 12:38:00 +0200, W Forum W wrote: > > Gimp does not start anymore (even after new install) > > > > $ gimp > > GEGL-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/seamless-clone.so' > > load error: /lib/x86_64-linux-gnu/libgegl-sc-0.4.so: undefined symbol: > > __exp_finite > > This is fallout from upgrading glibc to 2.31. It appears to have > been fixed as a side-effect of build system changes in gegl 0.4.18, so > upgrading to the version of gegl from testing/unstable should fix this. > > This can only affect partial upgrades from Debian 10 'buster' to > testing/unstable or the future Debian 11 'bullseye'. Pure Debian 10 systems > are unaffected, and so are pure testing/unstable systems. Closing the bug on that basis, now that it has been reassigned to the right package. smcv--- End Message ---
Bug#968342: libgegl-sc-0.4.so: undefined symbol: __exp_finite
Control: retitle -1 libgegl-sc-0.4.so: undefined symbol: __exp_finite Control: reassign -1 libgegl-0.4-0 0.4.12-2 Control: affects -1 + gimp Control: tags -1 + bullseye sid Control: clone -1 -2 Control: severity -2 minor Control: retitle -2 libc6: please consider adding Breaks on libgegl-0.4-0 (<< 0.4.18) Control: reassign -2 libc6 2.31.2 On Thu, 13 Aug 2020 at 12:38:00 +0200, W Forum W wrote: > Gimp does not start anymore (even after new install) > > $ gimp > GEGL-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/seamless-clone.so' > load error: /lib/x86_64-linux-gnu/libgegl-sc-0.4.so: undefined symbol: > __exp_finite This is fallout from upgrading glibc to 2.31. It appears to have been fixed as a side-effect of build system changes in gegl 0.4.18, so upgrading to the version of gegl from testing/unstable should fix this. This can only affect partial upgrades from Debian 10 'buster' to testing/unstable or the future Debian 11 'bullseye'. Pure Debian 10 systems are unaffected, and so are pure testing/unstable systems. > -- System Information: > Debian Release: 10.5 > ii libc62.31-2 > ii libgegl-0.4-00.4.12-2 You appear to have a mixture of packages from the Debian 10 stable release, and the Debian testing/unstable rolling release that will eventually get released as Debian 11. This is referred to as a "Frankendebian" system, and is not something that can really be fully supported - we try to make it work, but realistically the bugs that can happen during a partial upgrade will never all be found or fixed. To make it work, you will have to upgrade some other packages (in this case gegl, but probably a lot more) to their testing/unstable versions. smcv
Processed: Re: Bug#968342: libgegl-sc-0.4.so: undefined symbol: __exp_finite
Processing control commands: > retitle -1 libgegl-sc-0.4.so: undefined symbol: __exp_finite Bug #968342 [gimp] gimp does not start, error GEGL operation missing! Changed Bug title to 'libgegl-sc-0.4.so: undefined symbol: __exp_finite' from 'gimp does not start, error GEGL operation missing!'. > reassign -1 libgegl-0.4-0 0.4.12-2 Bug #968342 [gimp] libgegl-sc-0.4.so: undefined symbol: __exp_finite Bug reassigned from package 'gimp' to 'libgegl-0.4-0'. No longer marked as found in versions gimp/2.10.8-2. Ignoring request to alter fixed versions of bug #968342 to the same values previously set Bug #968342 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite Marked as found in versions gegl/0.4.12-2. > affects -1 + gimp Bug #968342 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite Added indication that 968342 affects gimp > tags -1 + bullseye sid Bug #968342 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite Added tag(s) bullseye and sid. > clone -1 -2 Bug #968342 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite Bug 968342 cloned as bug 968349 > severity -2 minor Bug #968349 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite Severity set to 'minor' from 'grave' > retitle -2 libc6: please consider adding Breaks on libgegl-0.4-0 (<< 0.4.18) Bug #968349 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite Changed Bug title to 'libc6: please consider adding Breaks on libgegl-0.4-0 (<< 0.4.18)' from 'libgegl-sc-0.4.so: undefined symbol: __exp_finite'. > reassign -2 libc6 2.31.2 Bug #968349 [libgegl-0.4-0] libc6: please consider adding Breaks on libgegl-0.4-0 (<< 0.4.18) Bug reassigned from package 'libgegl-0.4-0' to 'libc6'. No longer marked as found in versions gegl/0.4.12-2. Ignoring request to alter fixed versions of bug #968349 to the same values previously set Bug #968349 [libc6] libc6: please consider adding Breaks on libgegl-0.4-0 (<< 0.4.18) There is no source info for the package 'libc6' at version '2.31.2' with architecture '' Unable to make a source version for version '2.31.2' Marked as found in versions 2.31.2. -- 968342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968342 968349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957837: sprng: ftbfs with GCC-10
Nilesh, On 12 August 2020 at 21:17, Nilesh wrote: | Hi, | | This patch fixes the build. Let me know if something else is needed: | | --- a/SRC/primes_32.c | +++ b/SRC/primes_32.c | @@ -7,7 +7,7 @@ | #define NO 0 | #define NPRIMES 1000 | | -int primes[NPRIMES]; | +extern int primes[NPRIMES]; | | #ifdef __STDC__ | int init_prime_32(void) Thanks! That was easy enough -- my other gcc-10 "victim" (dieharder) required much more extensive changes (but then CRAN already made me make the same change last December (!!) when it was their turn to ask for gcc-10 fixes in my R package RDieHarder using the same code). I was about to let sprng die its natural cause as I had assumed that r-cran-rsprng was its only reverse dependency (and that package was removed from CRAN years ago). As I now see that another package depends on sprng I will maintain sprng for a while longer---but it too is outdated. Its build system was a mess, they rewrote for sprng4 and sprng5 but I guess there is no real demand for that in Debian. I find it a little rude and inconstructive that this was NMUed without even emailing me first, but that's just how it is with some people. Cheers, Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#965218: marked as done (ruby-sentry-raven: FTBFS with rails 6 in experimental)
Your message dated Thu, 13 Aug 2020 11:18:50 + with message-id and subject line Bug#965218: fixed in ruby-sentry-raven 2.13.0-3 has caused the Debian Bug report #965218, regarding ruby-sentry-raven: FTBFS with rails 6 in experimental 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.) -- 965218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-sentry-raven Version: 2.13.0-1 Severity: important User: pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: rails6-transition Control: forwarded -1 https://github.com/getsentry/raven-ruby/issues/966 Hi, This package's autopkgtest and rebuilds failed with rails 6 currently in experimental. rails 6 will be uploaded to unstable in two weeks, so please make sure this package is ready for rails 6. The severity of this bug will be raised to serious after rails 6 is uploaded to unstable. Relevant errors, Failures: 1) Rails Integration doesn't do anything on a normal route Failure/Error: expect(response.status).to eq(200) expected: 200 got: 403 (compared using ==) # ./spec/raven/integrations/rails_spec.rb:19:in `block (2 levels) in ' 2) Rails Integration should capture exceptions in production Failure/Error: expect(response.status).to eq(500) expected: 500 got: 403 (compared using ==) # ./spec/raven/integrations/rails_spec.rb:26:in `block (2 levels) in ' 3) Rails Integration should properly set the exception's URL Failure/Error: event = JSON.parse!(Raven.client.transport.events.first[1]) NoMethodError: undefined method `[]' for nil:NilClass # ./spec/raven/integrations/rails_spec.rb:35:in `block (2 levels) in ' 4) Rails Integration sets transaction to ControllerName#method Failure/Error: event = JSON.parse!(Raven.client.transport.events.first[1]) NoMethodError: undefined method `[]' for nil:NilClass # ./spec/raven/integrations/rails_spec.rb:42:in `block (2 levels) in ' Finished in 1.48 seconds (files took 2.82 seconds to load) 289 examples, 4 failures, 2 pending Failed examples: rspec ./spec/raven/integrations/rails_spec.rb:16 # Rails Integration doesn't do anything on a normal route rspec ./spec/raven/integrations/rails_spec.rb:23 # Rails Integration should capture exceptions in production rspec ./spec/raven/integrations/rails_spec.rb:32 # Rails Integration should properly set the exception's URL rspec ./spec/raven/integrations/rails_spec.rb:39 # Rails Integration sets transaction to ControllerName#method This is also reported upstream at https://github.com/getsentry/raven-ruby/issues/966 --- End Message --- --- Begin Message --- Source: ruby-sentry-raven Source-Version: 2.13.0-3 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of ruby-sentry-raven, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-sentry-raven 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: Thu, 13 Aug 2020 16:16:34 +0530 Source: ruby-sentry-raven Architecture: source Version: 2.13.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Closes: 965218 Changes: ruby-sentry-raven (2.13.0-3) unstable; urgency=medium . * Support rails 6 (Closes: #965218) * Fix typo: Rules-Requires-root => Rules-Requires-Root Checksums-Sha1: 36ce1d6ab8c7226396ecd0b5f939adca371b8b3c 2264 ruby-sentry-raven_2.13.0-3.dsc e622dd7ab56234c5693dc89fc18e2325d39f6602 4640 ruby-sentry-raven_2.13.0-3.debian.tar.xz 215d700980a87425e7a49f4ebe542b6345b23e8f 16727 ruby-sentry-raven_2.13.0-3_amd64.buildinfo Checksums-Sha256: b2376b1674ca911549a2b28c677b9c1d289bb9d9eebf33487b28d61d0d46d2ad 2264 ruby-sentry-raven_2.13.0-3.dsc 018e17b58e585df3b3f70578501c5e47e38ed2b5d3ccafe1c3c52851ed0b2cb8 4640 ruby-sentry-raven_2.13.0-3.debian.tar.xz 864c3b6785b9d5baa1fc0660834f4f13e4b55916652e1d1fa978d6e31103c77b 16727
Bug#957837: marked as done (sprng: ftbfs with GCC-10)
Your message dated Thu, 13 Aug 2020 11:06:38 + with message-id and subject line Bug#957837: fixed in sprng 2.0a-12.1 has caused the Debian Bug report #957837, regarding sprng: 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.) -- 957837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sprng Version: 2.0a-12 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/sprng_2.0a-12_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 [...] primes_64.c:5:1: note: include ‘’ or provide a declaration of ‘memcpy’ 4 | #include "primelist_64.h" +++ |+#include 5 | gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ fwrap_mpi.c gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ cputime.c gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT makeseed.c gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT store.c gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT simple_mpi.c gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT memory.c gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT communicate.c gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT checkid.c make[4]: Leaving directory '/<>/SRC' make[4]: Entering directory '/<>/SRC/lfg' gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ lfg.c -I.. make[4]: Leaving directory '/<>/SRC/lfg' make[4]: Entering directory '/<>/SRC/lcg' gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ lcg.c -I.. make[4]: Leaving directory '/<>/SRC/lcg' make[4]: Entering directory '/<>/SRC/lcg64' gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ -I.. lcg64.c make[4]: Leaving directory '/<>/SRC/lcg64' make[4]: Entering directory '/<>/SRC/cmrg' gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ cmrg.c -I.. make[4]: Leaving directory '/<>/SRC/cmrg' make[4]: Entering directory '/<>/SRC/mlfg' gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ mlfg.c -I.. make[4]: Leaving directory '/<>/SRC/mlfg' make[4]: Entering directory '/<>/SRC/pmlcg' gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ pmlcg.c -I.. pmlcg.c: In function ‘pmlcg_pack_rng’: pmlcg.c:699:10: warning: implicit declaration of function ‘store_int’ [-Wimplicit-function-declaration] 699 | pos += store_int(q->rng_type,4,temp_buffer+pos); | ^ make[4]: Leaving directory '/<>/SRC/pmlcg' rm -f ../../lib/libsprng.a make ../../lib/libsprng.a make[4]: Entering directory '/<>/SRC/sprng' gcc -c -O -fpic -DUSE_PMLCG -O2 -D_REENTRANT -DAdd_ sprng.c -I.. sprng.c: In function ‘unpack_rng’: sprng.c:295:2: warning: implicit declaration of function ‘load_int’ [-Wimplicit-function-declaration] 295 | load_int(packed,4,(unsigned int *)_type); | ^~~~ ar cr ../../lib/libsprng.a sprng.o \ ../lcg/lcg.o ../lfg/lfg.o \ ../lcg64/lcg64.o \ ../pmlcg/pmlcg.o \ ../mlfg/mlfg.o ../cmrg/cmrg.o \ ../primes_32.o ../primes_64.o ../fwrap_mpi.o ../cputime.o ../makeseed.o ../simple_mpi.o ../memory.o ../communicate.o ../checkid.o ../store.o ranlib ../../lib/libsprng.a gcc -shared -Wl,-soname,libsprng.so.2 \ -o ../../lib/libsprng.so.2.0 sprng.o \ ../lcg/lcg.o ../lfg/lfg.o \ ../lcg64/lcg64.o \ ../pmlcg/pmlcg.o \ ../mlfg/mlfg.o ../cmrg/cmrg.o \ ../primes_32.o ../primes_64.o ../fwrap_mpi.o ../cputime.o ../makeseed.o ../simple_mpi.o ../memory.o ../communicate.o ../checkid.o ../store.o -lgmp /usr/bin/ld:
Bug#965218: marked as pending in ruby-sentry-raven
Control: tag -1 pending Hello, Bug #965218 in ruby-sentry-raven 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/ruby-team/ruby-sentry-raven/-/commit/e8052182bf19ff920113dca510dfcd20e32d37cb Support rails 6 (Closes: #965218) (this message was generated automatically) -- Greetings https://bugs.debian.org/965218
Processed: Bug#965218 marked as pending in ruby-sentry-raven
Processing control commands: > tag -1 pending Bug #965218 [ruby-sentry-raven] ruby-sentry-raven: FTBFS with rails 6 in experimental Added tag(s) pending. -- 965218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968342: gimp does not start, error GEGL operation missing!
Package: gimp Version: 2.10.8-2 Severity: grave Justification: renders package unusable Dear Maintainer, Gimp does not start anymore (even after new install) $ gimp GEGL-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/seamless-clone.so' load error: /lib/x86_64-linux-gnu/libgegl-sc-0.4.so: undefined symbol: __exp_finite GEGL operation missing! GIMP requires the GEGL operation "gegl:seamless-clone". This operation cannot be found. Check your GEGL install and ensure it has been compiled with any dependencies required for GIMP. So it it not possible anymore to use Gimp. On an other computer we have the same issue. It worked before. -- System Information: Debian Release: 10.5 Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.8-2 ii libaa1 1.4p5-46 ii libbabl-0.1-00.1.62-1 ii libbz2-1.0 1.0.6-9.2~deb10u1 ii libc62.31-2 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.10.1-2 ii libgcc-s1 [libgcc1] 10-20200211-1 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgegl-0.4-00.4.12-2 ii libgexiv2-2 0.10.9-1 ii libgimp2.0 2.10.8-2 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgs9 9.27~dfsg-2+deb10u3 ii libgtk2.0-0 2.24.32-3 ii libgudev-1.0-0 232-2 ii libharfbuzz0b2.3.1-1 ii libheif1 1.3.2-2~deb10u1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-3 ii liblzma5 5.2.4-1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.3-0 1.3.0-2.1 ii libopenexr23 2.2.1-4.1 ii libopenjp2-7 2.3.0-2+deb10u1 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpangocairo-1.0-0 1.42.4-8~deb10u1 ii libpangoft2-1.0-01.42.4-8~deb10u1 ii libpng16-16 1.6.36-6 ii libpoppler-glib8 0.71.0-5 ii librsvg2-2 2.44.10-2.1 ii libstdc++6 9.2.1-8 ii libtiff5 4.1.0+git191117-2~deb10u1 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2 ii libwmf0.2-7 0.2.8.4-14 ii libx11-6 2:1.6.7-1 ii libxcursor1 1:1.1.15-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-1+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gimp recommends: ii ghostscript 9.27~dfsg-2+deb10u3 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help pn gimp-python ii gvfs-backends 1.38.1-5 ii libasound21.1.8-1 -- no debconf information
Bug#968338: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Hello, wanted to add that the issue gets triggered when running the following script: #!/bin/sh if [ -x /usr/bin/certbot ]; then certbot -q--authenticator standalone \ --installer none renew \ --pre-hook "service apache2 stop" \ --post-hook "service apache2 start" sleep 60 /bin/systemctl restart apache2 fi if i run this script using previous kernel ( linux-image-4.19.0-9-amd64 ) no kernel crash is happening. tobias.
Bug#968339: kodi: FTBFS in sid (test failures)
Source: kodi Version: 2:18.8+dfsg1-1 Severity: serious Hello, the package fails its testsuite on amd64 and armhf because of: 99% tests passed, 1 tests failed out of 520 Total Test time (real) = 44.44 sec The following tests FAILED: 418 - TestSharedSection.TwoCase (Child aborted) and 99% tests passed, 1 tests failed out of 520 Total Test time (real) = 58.55 sec The following tests FAILED: 424 - TestEvent.Group (SEGFAULT) Errors while running CTest Can you please have a look? thanks Gianfranco
Bug#964670: gsettings-qt: FTBFS: QQmlComponent: Component is not ready
Hi, Is there any progress on this? I found that it failed when running `$$[QT_INSTALL_BINS]/qmlplugindump -notrelocatable GSettings 1.0 ..` , but I can only reproduce it when pdebuild. And with the same generated file, If I chroot the pbuilder environment and mount the build dir, cd the GSettings dir and run `qmlplugindump -notrelocatable GSettings 1.0 ..`, it will failed with "QQmlComponent: Component is not ready", but if I run the same command in the same build dir in my local environment, everything is fine. Could it be a lack of dependency? regards, handsome_feng
Bug#968338: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Package: src:linux Version: 4.19.132-1 Severity: critical -- Package-specific info: ** Version: Linux version 4.19.0-10-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64 root=/dev/mapper/vol00-lvroot ro ipv6.disable=1 quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Gigabyte Technology Co., Ltd. product_name: To be filled by O.E.M. product_version: To be filled by O.E.M. chassis_vendor: Gigabyte Technology Co., Ltd. chassis_version: To Be Filled By O.E.M. bios_vendor: American Megatrends Inc. bios_version: U1l board_vendor: Gigabyte Technology Co., Ltd. board_name: Z68X-UD3H-B3 board_version: To be filled by O.E.M. ** Loaded modules: xt_nat veth ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_chain_nat_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc overlay nft_counter xt_tcpudp nft_compat nf_tables nfnetlink fuse snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp i915 kvm mxm_wmi evdev snd_hda_intel irqbypass drm_kms_helper crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel intel_cstate intel_uncore snd_hda_core snd_hwdep snd_pcm pcspkr intel_rapl_perf drm snd_timer mei_me snd iTCO_wdt mei i2c_algo_bit sg soundcore iTCO_vendor_support pcc_cpufreq ie31200_edac wmi button video nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 xfs libcrc32c crc32c_generic dm_mod hid_generic usbhid hid sd_mod crc32c_intel ahci libahci aesni_intel lpc_ich mfd_core firewire_ohci libata i2c_i801 xhci_pci r8169 aes_x86_64 crypto_simd realtek cryptd glue_helper libphy xhci_hcd ehci_pci scsi_mod ehci_hcd usbcore firewire_core crc_itu_t usb_common thermal fan ** Network interface configuration: source /etc/network/interfaces.d/* auto lo iface lo inet loopback allow-hotplug enp6s0 auto enp6s0 iface enp6s0 inet static netmask 255.255.255.0 address 192.168.1.3 gateway 192.168.1.1 ** Network status: *** IP interfaces and addresses: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: enp6s0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 90:2b:34:15:b8:c8 brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global enp6s0 valid_lft forever preferred_lft forever 3: br-ac54b3c767fd: mtu 1500 qdisc noqueue state UP group default link/ether 02:42:bf:91:58:ff brd ff:ff:ff:ff:ff:ff inet 172.24.0.1/16 brd 172.24.255.255 scope global br-ac54b3c767fd valid_lft forever preferred_lft forever 4: br-e3629fe1bfea: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:92:58:c2:77 brd ff:ff:ff:ff:ff:ff inet 172.18.0.1/16 brd 172.18.255.255 scope global br-e3629fe1bfea valid_lft forever preferred_lft forever 5: br-fe62f52dfde8: mtu 1500 qdisc noqueue state UP group default link/ether 02:42:61:ba:7f:21 brd ff:ff:ff:ff:ff:ff inet 172.27.0.1/16 brd 172.27.255.255 scope global br-fe62f52dfde8 valid_lft forever preferred_lft forever 6: br-08c6beaaf033: mtu 1500 qdisc noqueue state UP group default link/ether 02:42:82:5f:84:db brd ff:ff:ff:ff:ff:ff inet 172.25.0.1/16 brd 172.25.255.255 scope global br-08c6beaaf033 valid_lft forever preferred_lft forever 7: br-146a710c5787: mtu 1500 qdisc noqueue state UP group default link/ether 02:42:bf:51:27:4d brd ff:ff:ff:ff:ff:ff inet 172.19.0.1/16 brd 172.19.255.255 scope global br-146a710c5787 valid_lft forever preferred_lft forever 8: docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:c1:7b:74:e6 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 9: br-415df0c66794: mtu 1500 qdisc noqueue state UP group default link/ether 02:42:9f:da:4b:b5 brd ff:ff:ff:ff:ff:ff inet 172.30.0.1/16 brd 172.30.255.255 scope global br-415df0c66794 valid_lft forever preferred_lft forever 10: br-6e796151f364: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:e7:3e:6b:21 brd ff:ff:ff:ff:ff:ff inet 172.28.0.1/16 brd 172.28.255.255 scope global br-6e796151f364 valid_lft forever preferred_lft forever 11: br-8b808097d753: mtu 1500 qdisc noqueue state UP group default link/ether 02:42:f9:1b:5c:14 brd ff:ff:ff:ff:ff:ff inet 172.21.0.1/16 brd 172.21.255.255 scope global br-8b808097d753 valid_lft forever preferred_lft forever 12: br-9adc15211594: mtu 1500 qdisc noqueue state UP group default link/ether 02:42:47:42:ef:62 brd ff:ff:ff:ff:ff:ff inet
Bug#968337: sylpheed: crash on startup
Package: sylpheed Version: 3.7.0-8 Severity: grave Justification: renders package unusable X-Debbugs-Cc: bugzilla...@gmail.com Dear Maintainer, Following libpango-1.0-0 (and others) upgrade this morning, gdb reports: Thread 1 "sylpheed" received signal SIGSEGV, Segmentation fault. 0xb73cfebf in pango_renderer_part_changed () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 -- System Information: Debian Release: bullseye/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 5.7.0-2-686-pae (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sylpheed depends on: ii libc62.31-3 ii libcairo21.16.0-4 ii libcompfaceg11:1.5.2-5+b2 ii libenchant-2-2 2.2.8-1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.64.4-1 ii libgpgme11 1.14.0-1 ii libgtk2.0-0 2.24.32-4 ii libgtkspell0 2.0.16-1.3 ii libldap-2.4-22.4.50+dfsg-1+b1 ii libonig5 6.9.5-2 ii libpango-1.0-0 1.46.0-1 ii libpangocairo-1.0-0 1.46.0-1 ii libssl1.11.1.1g-1 ii pinentry-gtk21.1.0-4 ii sensible-utils 0.0.12+nmu1 Versions of packages sylpheed recommends: ii aspell-en [aspell-dictionary] 2018.04.16-0-1 ii ca-certificates20200601 ii sylfilter 0.8-7 ii sylpheed-i18n 3.7.0-8 Versions of packages sylpheed suggests: pn claws-mail-tools ii curl 7.68.0-1+b1 pn sylpheed-doc pn sylpheed-plugins -- no debconf information
Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Package: src:linux Version: 4.19.132-1 Severity: critical -- Package-specific info: ** Version: Linux version 4.19.0-10-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64 root=/dev/mapper/vol00-lvroot ro ipv6.disable=1 quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 19.844379] eth0: renamed from veth6e32f53 [ 19.900781] br-9adc15211594: port 1(vethffa81fd) entered blocking state [ 19.900783] br-9adc15211594: port 1(vethffa81fd) entered forwarding state [ 19.900868] eth0: renamed from veth05d3208 [ 19.981224] br-8b808097d753: port 1(veth292ad2c) entered blocking state [ 19.981226] br-8b808097d753: port 1(veth292ad2c) entered forwarding state [ 19.981300] eth0: renamed from veth4ed0069 [ 20.004228] eth0: renamed from veth2fd413c [ 20.052594] br-d3165f3cf7f6: port 1(veth9b852c9) entered blocking state [ 20.052596] br-d3165f3cf7f6: port 1(veth9b852c9) entered forwarding state [ 20.054598] br-9adc15211594: port 5(veth06a6956) entered blocking state [ 20.054600] br-9adc15211594: port 5(veth06a6956) entered disabled state [ 20.054650] device veth06a6956 entered promiscuous mode [ 20.054737] br-9adc15211594: port 5(veth06a6956) entered blocking state [ 20.054738] br-9adc15211594: port 5(veth06a6956) entered forwarding state [ 20.056275] br-fecbb2e5e4e3: port 1(vethed4a268) entered blocking state [ 20.056276] br-fecbb2e5e4e3: port 1(vethed4a268) entered forwarding state [ 20.056314] br-9adc15211594: port 5(veth06a6956) entered disabled state [ 20.056379] eth0: renamed from veth8e2c368 [ 20.100495] eth0: renamed from vethdae281b [ 20.116540] br-fecbb2e5e4e3: port 3(vethcb5bab4) entered blocking state [ 20.116542] br-fecbb2e5e4e3: port 3(vethcb5bab4) entered forwarding state [ 20.119620] br-9adc15211594: port 2(vethc5cbaba) entered blocking state [ 20.119622] br-9adc15211594: port 2(vethc5cbaba) entered forwarding state [ 20.168874] eth0: renamed from veth656f734 [ 20.215752] br-146a710c5787: port 1(veth3fce3b7) entered blocking state [ 20.215754] br-146a710c5787: port 1(veth3fce3b7) entered forwarding state [ 20.218129] eth0: renamed from vethd0397de [ 20.240654] br-d3165f3cf7f6: port 3(veth2e30ace) entered blocking state [ 20.240656] br-d3165f3cf7f6: port 3(veth2e30ace) entered forwarding state [ 20.440464] eth0: renamed from vethdfb9ca8 [ 20.464753] br-fecbb2e5e4e3: port 4(veth6b7c50a) entered blocking state [ 20.464755] br-fecbb2e5e4e3: port 4(veth6b7c50a) entered forwarding state [ 20.716533] eth0: renamed from veth6ff3ad7 [ 20.736843] br-9adc15211594: port 3(veth8fb547c) entered blocking state [ 20.736846] br-9adc15211594: port 3(veth8fb547c) entered forwarding state [ 20.772575] eth0: renamed from vetha05b0dc [ 20.836690] br-9adc15211594: port 4(veth2373900) entered blocking state [ 20.836692] br-9adc15211594: port 4(veth2373900) entered forwarding state [ 20.836800] eth0: renamed from veth0e5430e [ 20.880947] br-fe62f52dfde8: port 1(vethb0af17f) entered blocking state [ 20.880949] br-fe62f52dfde8: port 1(vethb0af17f) entered forwarding state [ 20.904934] eth0: renamed from veth32bf55f [ 20.924361] eth1: renamed from veth5cb45a4 [ 20.945859] br-ac54b3c767fd: port 1(veth0b33dfa) entered blocking state [ 20.945862] br-ac54b3c767fd: port 1(veth0b33dfa) entered forwarding state [ 20.964643] br-08c6beaaf033: port 2(veth972e005) entered blocking state [ 20.964644] br-08c6beaaf033: port 2(veth972e005) entered forwarding state [ 20.996932] eth0: renamed from veth0d9f11d [ 21.036982] eth1: renamed from veth270bc0f [ 21.052253] br-9adc15211594: port 5(veth06a6956) entered blocking state [ 21.052255] br-9adc15211594: port 5(veth06a6956) entered forwarding state [ 21.052359] eth0: renamed from vethbeadc4a [ 21.068555] br-415df0c66794: port 1(veth8d2b916) entered blocking state [ 21.068557] br-415df0c66794: port 1(veth8d2b916) entered forwarding state [ 21.069499] br-fecbb2e5e4e3: port 2(veth617798a) entered blocking state [ 21.069501] br-fecbb2e5e4e3: port 2(veth617798a) entered forwarding state [ 21.100993] eth1: renamed from veth1ffa0e5 [ 21.136350] br-d3165f3cf7f6: port 2(veth50514f1) entered blocking state [ 21.136354] br-d3165f3cf7f6: port 2(veth50514f1) entered forwarding state [ 265.816084] r8169 :06:00.0: invalid short VPD tag 00 at offset 1 [ 290.118158] [ cut here ] [ 290.118163] percpu ref (css_release) <= 0 (-21) after switching to atomic [ 290.118172] WARNING: CPU: 2 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120 [ 290.118172] Modules linked in: xt_nat veth ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_chain_nat_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc overlay nft_counter xt_tcpudp
Bug#968336: afl++: Illegal instruction
Package: afl++ Version: 2.66c-1 Severity: grave afl-fuzz crashes with illegal instruction every time. GDB says: Program received signal SIGILL, Illegal instruction. 0x5657e8ef in rand_set_seed () => 0x5657e8ef : c5 f9 6e c0 vmovd %eax,%xmm0 It's an AVX instruction, which is indeed not supported by my CPU. -- System Information: Architecture: i386 Versions of packages afl++ depends on: ii build-essential 12.8 ii libc62.31-3 ii libpython3.8 3.8.5-2 -- Jakub Wilk
Bug#957616: marked as done (ntpsec: ftbfs with GCC-10)
Your message dated Thu, 13 Aug 2020 07:48:35 + with message-id and subject line Bug#957616: fixed in ntpsec 1.1.9+dfsg1-1 has caused the Debian Bug report #957616, regarding ntpsec: 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.) -- 957616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ntpsec Version: 1.1.8+dfsg1-4 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/ntpsec_1.1.8+dfsg1-4_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 [...] Note: meta author : see http://docbook.sf.net/el/authorntpfrob Warn: meta author : no author data, so inserted a fixmentpfrob Note: Writing ntpfrob.8 a2x: chdir /<>/build/main a2x: deleting /<>/build/main/ntpfrob/ntpfrob-man.adoc.xml a2x: args: ['--format', 'manpage', '--no-xmllint', '-v', '/<>/build/main/ntpd/ntp.conf-man.adoc.man-tmp'] a2x: resource files: [] a2x: resource directories: ['/etc/asciidoc/images', '/etc/asciidoc/stylesheets'] a2x: executing: "/usr/bin/asciidoc" --backend docbook -a "a2x-format=manpage" --doctype manpage --verbose --out-file "/<>/build/main/ntpd/ntp.conf-man.adoc.xml" "/<>/build/main/ntpd/ntp.conf-man.adoc.man-tmp" asciidoc: reading: /etc/asciidoc/asciidoc.conf asciidoc: reading: /<>/build/main/ntpd/ntp.conf-man.adoc.man-tmp asciidoc: include: /<>/docs/manual.include asciidoc: ntp.conf-man.adoc.man-tmp: line 3: reading: /<>/docs/manual.include asciidoc: include: /<>/docs/asciidoc.include asciidoc: manual.include: line 4: reading: /<>/docs/asciidoc.include asciidoc: reading: /etc/asciidoc/docbook45.conf asciidoc: reading: /etc/asciidoc/filters/graphviz/graphviz-filter.conf asciidoc: reading: /etc/asciidoc/filters/code/code-filter.conf asciidoc: reading: /etc/asciidoc/filters/music/music-filter.conf asciidoc: reading: /etc/asciidoc/filters/source/source-highlight-filter.conf asciidoc: reading: /etc/asciidoc/filters/latex/latex-filter.conf asciidoc: reading: /etc/asciidoc/lang-en.conf asciidoc: writing: /<>/build/main/ntpd/ntp.conf-man.adoc.xml asciidoc: include: /<>/docs/includes/ntp-conf-body.adoc asciidoc: ntp.conf-man.adoc.man-tmp: line 7: reading: /<>/docs/includes/ntp-conf-body.adoc asciidoc: include: /<>/docs/includes/assoc-commands.adoc asciidoc: ntp-conf-body.adoc: line 72: reading: /<>/docs/includes/assoc-commands.adoc asciidoc: include: /<>/docs/includes/assoc-options.adoc asciidoc: ntp-conf-body.adoc: line 76: reading: /<>/docs/includes/assoc-options.adoc asciidoc: include: /<>/docs/includes/assoc-auxcommands.adoc asciidoc: ntp-conf-body.adoc: line 80: reading: /<>/docs/includes/assoc-auxcommands.adoc asciidoc: include: /<>/docs/includes/auth-commands.adoc asciidoc: ntp-conf-body.adoc: line 84: reading: /<>/docs/includes/auth-commands.adoc asciidoc: include: /<>/docs/includes/nts-commands.adoc asciidoc: ntp-conf-body.adoc: line 88: reading: /<>/docs/includes/nts-commands.adoc asciidoc: include: /<>/docs/includes/mon-commands.adoc asciidoc: ntp-conf-body.adoc: line 104: reading: /<>/docs/includes/mon-commands.adoc asciidoc: include: /<>/docs/includes/access-commands.adoc asciidoc: ntp-conf-body.adoc: line 167: reading: /<>/docs/includes/access-commands.adoc asciidoc: include: /<>/docs/includes/clock-options.adoc asciidoc: ntp-conf-body.adoc: line 218: reading: /<>/docs/includes/clock-options.adoc asciidoc: include: /<>/docs/includes/misc-options.adoc asciidoc:
