Bug#957847: Fixed in git
I just fixed this in version control, but there's more to do, and I'm not releasing anything into the archive. https://salsa.debian.org/science-team/sundials/-/commit/dc8951dabd913d2cc4c259b5c5e59f90f4c60f26
Bug#971972: vde-switch,vde-wirefilter,vdeplug: Miissing Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in package vde2 2.3.2+r586-2.2+b1"
Package: vde-switch,vde-wirefilter,vdeplug Version: 2.3.2+r586-5 Severity: serious Upgrading vde2 from 2.3.2+r586-2.2+b1 to 2.3.2+r586-5 fails for me as follows: Selecting previously unselected package vde-switch. Preparing to unpack .../44-vde-switch_2.3.2+r586-5_amd64.deb ... Unpacking vde-switch (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/44-vde-switch_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/vde_switch', which is also in package vde2 2.3.2+r586-2.2+b1 Selecting previously unselected package vde-wirefilter. Preparing to unpack .../45-vde-wirefilter_2.3.2+r586-5_amd64.deb ... Unpacking vde-wirefilter (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/45-vde-wirefilter_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/wirefilter', which is also in package vde2 2.3.2+r586-2.2+b1 Selecting previously unselected package vdeplug. Preparing to unpack .../46-vdeplug_2.3.2+r586-5_amd64.deb ... Unpacking vdeplug (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/46-vdeplug_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/dpipe', which is also in package vde2 2.3.2+r586-2.2+b1 Preparing to unpack .../47-vde2_2.3.2+r586-5_amd64.deb ... Unpacking vde2 (2.3.2+r586-5) over (2.3.2+r586-2.2+b1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-leAAf0/44-vde-switch_2.3.2+r586-5_amd64.deb /tmp/apt-dpkg-install-leAAf0/45-vde-wirefilter_2.3.2+r586-5_amd64.deb /tmp/apt-dpkg-install-leAAf0/46-vdeplug_2.3.2+r586-5_amd64.deb Looks as if the required Breaks and Replaces headers against the older versions of vde2 are missing in all three new packages. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled
Processed: tagging 964195
Processing commands for cont...@bugs.debian.org: > tags 964195 + upstream fixed-upstream Bug #964195 [src:guacamole-server] CVE-2020-9497 CVE-2020-9498 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 964195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971967: src:libzorpll: fails to migrate to testing for too long: unresolved RC bug and maintainer built arch:all binaries
Source: libzorpll Version: 7.0.1.0~alpha1-1.1 Severity: serious Control: close -1 7.0.4.0-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 968274 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:libzorpll in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=libzorpll signature.asc Description: OpenPGP digital signature
Processed: src:libzorpll: fails to migrate to testing for too long: unresolved RC bug and maintainer built arch:all binaries
Processing control commands:
> close -1 7.0.4.0-1
Bug #971967 [src:libzorpll] src:libzorpll: fails to migrate to testing for too
long: unresolved RC bug and maintainer built arch:all binaries
Marked as fixed in versions libzorpll/7.0.4.0-1.
Bug #971967 [src:libzorpll] src:libzorpll: fails to migrate to testing for too
long: unresolved RC bug and maintainer built arch:all binaries
Marked Bug as done
> block -1 by 968274
Bug #971967 {Done: Paul Gevers } [src:libzorpll]
src:libzorpll: fails to migrate to testing for too long: unresolved RC bug and
maintainer built arch:all binaries
971967 was not blocked by any bugs.
971967 was not blocking any bugs.
Added blocking bug(s) of 971967: 968274
--
971967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#964195: guacamole-client: CVE-2020-9497 and CVE-2020-9498
Hi, On Sat, Oct 10, 2020 at 06:28:39PM +0200, Markus Koschany wrote: > I somehow missed the guacamole-server package in Debian. Right, I reassigned earlier today then the bug to guacamole-server and adjusted the tracking in the security-tracker. Thanks for investigating. > Currently I > believe it is possible to backport the patch from 1.2.0 to 0.9.9. > However there is still the problem with freerdp2 (#888321), most likely > a new upstream version for unstable/testing is required anyway. I cannot judge here at the moment, in any case it should be outweight if it wise to backport the fix vs. potential breakage. For unstable I agree new upstream versions are probably the best option. Regards, Salvatore
Processed: severity of 971773 is serious
Processing commands for cont...@bugs.debian.org: > severity 971773 serious Bug #971773 [gvmd] Needs porting to PostgreSQL 13 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 971773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966659: marked as done (libghc-monad-gen-doc: Depends on missing haddock-interface-33)
Your message dated Sat, 10 Oct 2020 17:00:11 + with message-id and subject line Bug#971952: Removed package(s) from unstable has caused the Debian Bug report #966659, regarding libghc-monad-gen-doc: Depends on missing haddock-interface-33 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.) -- 966659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libghc-monad-gen-doc Version: 0.3.0.1-1 Severity: grave Justification: renders package unusable This package should be rebuild against the latest ghc (8.8.3) available on unstable. Alternatively, since this package looks unmaintained (last upstream upload at 2014), is not part of Stackage and has no rev dependencies, we may consider removing it. Thanks, -- Ilias --- End Message --- --- Begin Message --- Version: 0.3.0.1-1+rm Dear submitter, as the package haskell-monad-gen has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/971952 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#971667: marked as done (gnome-shell-extension-workspaces-to-dock: Not working on gnome-shell 3.38)
Your message dated Sat, 10 Oct 2020 16:57:39 + with message-id and subject line Bug#971803: Removed package(s) from unstable has caused the Debian Bug report #971667, regarding gnome-shell-extension-workspaces-to-dock: Not working on gnome-shell 3.38 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.) -- 971667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-workspaces-to-dock Version: 53-1 Severity: grave Tags: upstream X-Debbugs-Cc: setig...@yahoo.com The extension isn't compatible with gnome-shell 3.38. The API changed and the upstream isn't maintaing the package. Is a very good extension, but needs to be adapted to 3.38. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-extension-workspaces-to-dock depends on: ii gnome-shell 3.38.0-2 ii gnome-shell-extension-prefs 3.38.0-2 gnome-shell-extension-workspaces-to-dock recommends no packages. gnome-shell-extension-workspaces-to-dock suggests no packages. --- End Message --- --- Begin Message --- Version: 53-1+rm Dear submitter, as the package gnome-shell-extension-workspaces-to-dock has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/971803 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#918163: marked as done (Broken in Stretch)
Your message dated Sat, 10 Oct 2020 16:57:01 + with message-id and subject line Bug#971772: Removed package(s) from unstable has caused the Debian Bug report #918163, regarding Broken in Stretch 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.) -- 918163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-sieve Version: 0.2.3h+dfsg-1 Severity: grave The plugin is broken with Thunderbird 60 in stretch, after installation it's disabled and only prints "Sieve is incompatible with Thunderbird 60.4". TB 60 was uploaded to stretch over two months ago, given that noone filed a bug so far, it makes me wonder whether this package is used at all... Martín, do you intend to update it in stretch or should it rather be removed by the next point release? Cheers, Moritz --- End Message --- --- Begin Message --- Version: 0.3.0+dfsg-1+rm Dear submitter, as the package sieve-extension has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/971772 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#953182: marked as done (xul-ext-nostalgy: new version available which fixes the thunderbird 68 conflict)
Your message dated Sat, 10 Oct 2020 16:59:35 + with message-id and subject line Bug#971848: Removed package(s) from unstable has caused the Debian Bug report #953182, regarding xul-ext-nostalgy: new version available which fixes the thunderbird 68 conflict 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.) -- 953182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-nostalgy Severity: grave Justification: renders package unusable Dear Maintainer, the version of xul-ext-nostalgy currently available in debian is uninstallable since it is not compatible with thunderbird 68. There is a new release available (0.3) which works with tb68: https://addons.thunderbird.net/en-US/thunderbird/addon/nostalgy/ Would you consider packaging it ? Thanks -- Rémi -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xul-ext-nostalgy depends on: ii thunderbird 1:68.5.0-1+b1 xul-ext-nostalgy recommends no packages. xul-ext-nostalgy suggests no packages. --- End Message --- --- Begin Message --- Version: 0.2.36-1.2+rm Dear submitter, as the package nostalgy has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/971848 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#957646: marked as done (openvas-manager: ftbfs with GCC-10)
Your message dated Sat, 10 Oct 2020 16:51:46 + with message-id and subject line Bug#971711: Removed package(s) from unstable has caused the Debian Bug report #957646, regarding openvas-manager: 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.) -- 957646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:openvas-manager Version: 7.0.3-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/openvas-manager_7.0.3-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 [...] from /<>/src/ompd.h:30, from /<>/src/scanner.c:27: In function ‘strncpy’, inlined from ‘openvas_scanner_connect_unix’ at /<>/src/scanner.c:600:3: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 108 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ [ 70%] Building C object src/CMakeFiles/manage.dir/sql_sqlite3.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DOPENVASMD_CERT_DATABASE_VERSION=6 -DOPENVASMD_DATABASE_VERSION=184 -DOPENVASMD_SCAP_DATABASE_VERSION=15 -DOPENVAS_SQLITE_SLEEP_MAX=0 -I/usr/include/openvas -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/p11-kit-1 -I/usr/include/libmount -I/usr/include/blkid -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -O2 -D_FORTIFY_SOURCE=2 -fstack-protector -Wall -D_BSD_SOURCE -D_ISOC99_SOURCE -D_SVID_SOURCE -D_DEFAULT_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -DNDEBUG -DOPENVASMD_VERSION=\"7.0.3\" -DOMP_VERSION=\"7.0\" -DOPENVAS_OS_NAME=\"Linux-4.19.0-6-cloud-amd64\" -DPREFIX=\"/usr\" -DOPENVAS_SCAP_RES_DIR=\"/usr/share/openvas/scap\" -DOPENVAS_SCAP_DATA_DIR=\"/var/lib/openvas/scap-data\" -DOPENVAS_CERT_RES_DIR=\"/usr/share/openvas/cert\" -DOPENVAS_CERT_DATA_DIR=\"/var/lib/openvas/cert-data \" -DSCANNERCERT=\"/var/lib/openvas/CA/servercert.pem\" -DSCANNERKEY=\"/var/lib/openvas/private/CA/serverkey.pem\" -DCLIENTCERT=\"/var/lib/openvas/CA/clientcert.pem\" -DCLIENTKEY=\"/var/lib/openvas/private/CA/clientkey.pem\" -DCACERT=\"/var/lib/openvas/CA/cacert.pem\" -DCA_DIR=\"/var/lib/openvas/openvasmd/trusted_certs\" -DOPENVAS_LOG_DIR=\"/var/log/openvas\" -DOPENVAS_STATE_DIR=\"/var/lib/openvas\" -DOPENVAS_RUN_DIR=\"/var/run\" -DOPENVAS_SYSCONF_DIR=\"/etc/openvas\" -DOPENVAS_DATA_DIR=\"/usr/share/openvas\" -DOPENVAS_LIB_INSTALL_DIR=\"/usr/lib\" -DOPENVAS_NVT_DIR=\"/var/lib/openvas/plugins/\" -DSBINDIR=\"/usr/sbin\" -o CMakeFiles/manage.dir/sql_sqlite3.c.o -c /<>/src/sql_sqlite3.c [ 73%] Building C object src/CMakeFiles/manage.dir/manage_sqlite3.c.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc -DOPENVASMD_CERT_DATABASE_VERSION=6 -DOPENVASMD_DATABASE_VERSION=184 -DOPENVASMD_SCAP_DATABASE_VERSION=15 -DOPENVAS_SQLITE_SLEEP_MAX=0 -I/usr/include/openvas -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/p11-kit-1 -I/usr/include/libmount -I/usr/include/blkid -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -O2 -D_FORTIFY_SOURCE=2 -fstack-protector -Wall -D
Bug#933110: marked as done (pkg-components: No upstream maintainer ⇒ unsuitable for Bullseye)
Your message dated Sat, 10 Oct 2020 16:45:49 + with message-id and subject line Bug#971661: Removed package(s) from unstable has caused the Debian Bug report #933110, regarding pkg-components: No upstream maintainer ⇒ unsuitable for 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.) -- 933110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pkg-components Version: 0.11 Severity: serious Hi, The Debian Perl group has, somewhat unwillingly, inherited the role of upstream maintainer for this native package, when its original author stopped taking care of it. We don't feel we're in a good position to wear this hat and would rather not to. Therefore, we decided at the pkg-perl BoF today at DebConf that we don't want this package to be included in Bullseye, unless someone else steps up and becomes its upstream maintainer. I'll file bugs against all reverse-dependencies to alert their maintainer about this situation. Cheers, -- intrigeri --- End Message --- --- Begin Message --- Version: 0.13+rm Dear submitter, as the package pkg-components has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/971661 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#885188: marked as done (freehdl: please migrate to guile-2.2)
Your message dated Sat, 10 Oct 2020 16:40:52 + with message-id and subject line Bug#971534: Removed package(s) from unstable has caused the Debian Bug report #885188, regarding freehdl: please migrate to guile-2.2 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.) -- 885188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freehdl Severity: normal I'd like to remove guile-2.0 before the buster release, so please migrate to guile-2.2 when you can. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 --- End Message --- --- Begin Message --- Version: 0.0.8-2.2+rm Dear submitter, as the package freehdl has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/971534 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#942331: marked as done (google-cloud-print-connector: FTBFS during rebuild with libsnmp35)
Your message dated Sat, 10 Oct 2020 16:36:05 + with message-id and subject line Bug#970847: Removed package(s) from unstable has caused the Debian Bug report #942331, regarding google-cloud-print-connector: FTBFS during rebuild with libsnmp35 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.) -- 942331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: google-cloud-print-connector Version: 1.12-1 Severity: serious Tags: ftbfs Justification: FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainer(s), Your package is part of the libsnmp transition. During a rebuild your package FTBFS on all architectures. Paul Tail of log for google-cloud-print-connector on amd64: golang.org/x/net/context/ctxhttp golang.org/x/oauth2/internal golang.org/x/oauth2 github.com/google/cloud-print-connector/gcp database/sql/driver github.com/satori/go.uuid github.com/google/cloud-print-connector/gcp-connector-util github.com/google/cloud-print-connector/privet encoding/xml github.com/google/cloud-print-connector/xmpp hash/adler32 github.com/google/cloud-print-connector/manager os/signal dh_auto_build: cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/google/cloud-print-connector/cdd github.com/google/cloud-print-connector/cups github.com/google/cloud-print-connector/gcp github.com/google/cloud-print-connector/gcp-connector-util github.com/google/cloud-print-connector/gcp-cups-connector github.com/google/cloud-print-connector/lib github.com/google/cloud-print-connector/log github.com/google/cloud-print-connector/manager github.com/google/cloud-print-connector/monitor github.com/google/cloud-print-connector/privet github.com/google/cloud-print-connector/xmpp returned exit code 2 make: *** [debian/rules:4: build-arch] Error 255 - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl2kuQMACgkQnFyZ6wW9 dQpg1wf/Q5fKVllmhS6O2sOP7Fgnyw7ae8RIVdOEZ8a36zc4s55/eVT0sOivL8JI b9l0ll4UxOxXEQ8NXtq0/IJAXa+ZCzxO96IxomC73q8n0K76w43pmiMHWeo++boy QBzMzlUvIHBb/dW0IpjEgTB+DfitOcECr1v7di9PN1TQ1Aa0kVkiJPK8tnX74nFO 5S7qEbcnCMR2dW/ci+V8dUgxp9+vIkl2ca5FlBZ+LAw03dsut5cESyfi76Z0tOXl usmH5EQWW840HDa9lTfbIrT3cAnhWe8aU+MrUpu0nlYB60ocyjDVoquctHCZVtLf 0oFAjFuDl7sSizJWPfdP8K5LrYXB6A== =mTrh -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 1.12-1+rm Dear submitter, as the package google-cloud-print-connector has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/970847 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#932796: marked as done (Non-DFSG license in dyndns.pl file)
Your message dated Sat, 10 Oct 2020 16:37:24 + with message-id and subject line Bug#970868: Removed package(s) from unstable has caused the Debian Bug report #932796, regarding Non-DFSG license in dyndns.pl file 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.) -- 932796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dyndns Version: 2016.1021-3 Severity: serious Tags: upstream When searching for a license inside dyndns.pl, I found the information shown below: #!/usr/bin/perl # # Copyright # # Copyright (C) 1999-2016 Jari Aalto # # License # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. [...] [...] The last block says about a PROPRIETARY source code. This notice was shown two times in dyndns main file. Regards, Eriberto -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Version: 2016.1021-3+rm Dear submitter, as the package dyndns has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/970868 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#943542: marked as done (google-cloud-print-connector: hardcoded dependency on libsnmp30)
Your message dated Sat, 10 Oct 2020 16:36:05 + with message-id and subject line Bug#970847: Removed package(s) from unstable has caused the Debian Bug report #943542, regarding google-cloud-print-connector: hardcoded dependency on libsnmp30 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.) -- 943542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: google-cloud-print-connector Version: 1.12.1 Severity: serious Tags: bullseye, sid After uploading my fix for 942331 to Raspbian bullseye I discovered another problem. The dependency on libsnmp30 is hardcoded. In raspbian I have just gone ahead and changed the dependency. a debdiff should appear soon at https://debdiffs.raspbian.org/main/g/google-cloud-print-connector/ --- End Message --- --- Begin Message --- Version: 1.12-1+rm Dear submitter, as the package google-cloud-print-connector has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/970847 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#964195: guacamole-client: CVE-2020-9497 and CVE-2020-9498
I somehow missed the guacamole-server package in Debian. Currently I believe it is possible to backport the patch from 1.2.0 to 0.9.9. However there is still the problem with freerdp2 (#888321), most likely a new upstream version for unstable/testing is required anyway. Markkus signature.asc Description: OpenPGP digital signature
Bug#957498: marked as done (loadmeter: ftbfs with GCC-10)
Your message dated Sat, 10 Oct 2020 16:23:29 + with message-id and subject line Bug#970449: Removed package(s) from unstable has caused the Debian Bug report #957498, regarding loadmeter: 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.) -- 957498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:loadmeter Version: 1.20-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/loadmeter_1.20-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 [...] /usr/bin/ld: getinfo.o:./loadmeter.h:36: multiple definition of `win'; loadmeter.o:./loadmeter.h:36: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:35: multiple definition of `disp'; loadmeter.o:./loadmeter.h:35: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:34: multiple definition of `metergc'; loadmeter.o:./loadmeter.h:34: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:34: multiple definition of `hlgc'; loadmeter.o:./loadmeter.h:34: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:34: multiple definition of `warngc'; loadmeter.o:./loadmeter.h:34: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:33: multiple definition of `popbgc'; loadmeter.o:./loadmeter.h:33: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:33: multiple definition of `poptgc'; loadmeter.o:./loadmeter.h:33: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:33: multiple definition of `popgc'; loadmeter.o:./loadmeter.h:33: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:32: multiple definition of `bkgc'; loadmeter.o:./loadmeter.h:32: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:32: multiple definition of `bgc'; loadmeter.o:./loadmeter.h:32: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:32: multiple definition of `tgc'; loadmeter.o:./loadmeter.h:32: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:31: multiple definition of `ptextgc'; loadmeter.o:./loadmeter.h:31: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:31: multiple definition of `blgc'; loadmeter.o:./loadmeter.h:31: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:31: multiple definition of `ygc'; loadmeter.o:./loadmeter.h:31: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:31: multiple definition of `ggc'; loadmeter.o:./loadmeter.h:31: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:31: multiple definition of `rgc'; loadmeter.o:./loadmeter.h:31: first defined here /usr/bin/ld: getinfo.o:./loadmeter.h:31: multiple definition of `gc'; loadmeter.o:./loadmeter.h:31: first defined here /usr/bin/ld: popup.o:./loadmeter.h:37: multiple definition of `pfont'; loadmeter.o:./loadmeter.h:37: first defined here /usr/bin/ld: popup.o:./loadmeter.h:41: multiple definition of `pwidth'; loadmeter.o:./loadmeter.h:41: first defined here /usr/bin/ld: popup.o:./loadmeter.h:36: multiple definition of `popup'; loadmeter.o:./loadmeter.h:36: first defined here /usr/bin/ld: popup.o:./loadmeter.h:35: multiple definition of `disp'; loadmeter.o:./loadmeter.h:35: first defined here /usr/bin/ld: popup.o:./loadmeter.h:31: multiple definition of `ptextgc'; loadmeter.o:./loadmeter.h:31: first defined here /usr/bin/ld: popup.o:./loadmeter.h:43: multiple definition of `davg'; loadmeter.o:./loadmeter.h:43: first defined here /usr/bin/ld: popup.o:./loadmeter.h:43: multiple definition of `avg'; loadmeter.o:./loadmeter.h:43: firs
Bug#937255: marked as done (pbgenomicconsensus: Python2 removal in sid/bullseye)
Your message dated Sat, 10 Oct 2020 16:21:07 + with message-id and subject line Bug#970413: Removed package(s) from unstable has caused the Debian Bug report #937255, regarding pbgenomicconsensus: 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.) -- 937255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pbgenomicconsensus Version: 2.3.2-5 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:pbgenomicconsensus 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 --- Version: 2.3.2-5+rm Dear submitter, as the package pbgenomicconsensus has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/970413 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#957663: marked as done (paris-traceroute: ftbfs with GCC-10)
Your message dated Sat, 10 Oct 2020 16:13:22 + with message-id and subject line Bug#970290: Removed package(s) from unstable has caused the Debian Bug report #957663, regarding paris-traceroute: 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.) -- 957663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:paris-traceroute Version: 0.93+git20160927-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/paris-traceroute_0.93+git20160927-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 [...] libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c probe_group.c -o probe_group.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c -o protocol.lo protocol.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c protocol.c -fPIC -DPIC -o .libs/protocol.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c protocol.c -o protocol.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c -o protocols/icmpv4.lo protocols/icmpv4.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c protocols/icmpv4.c -fPIC -DPIC -o protocols/.libs/icmpv4.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c protocols/icmpv4.c -o protocols/icmpv4.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c -o protocols/icmpv6.lo protocols/icmpv6.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c protocols/icmpv6.c -fPIC -DPIC -o protocols/.libs/icmpv6.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c protocols/icmpv6.c -o protocols/icmpv6.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c -o protocols/ipv4.lo protocols/ipv4.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -c prot
Processed: reassign 964195 to src:guacamole-server
Processing commands for cont...@bugs.debian.org: > reassign 964195 src:guacamole-server Bug #964195 [src:guacamole-client] CVE-2020-9497 CVE-2020-9498 Bug reassigned from package 'src:guacamole-client' to 'src:guacamole-server'. Ignoring request to alter found versions of bug #964195 to the same values previously set Ignoring request to alter fixed versions of bug #964195 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 964195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970878: ghostscript breaks doc-rfc autopkgtest: segmentation fault
Dear Maintainer, tried to have a look at this one, found the segfault [1], and can point to the place where the pointer gets overwritten [2]. Unfortunately Valgrind or ASAN gave me not more details. Kind regards, Bernhard [1] Program received signal SIGSEGV, Segmentation fault. 0x7fa54364fc11 in gs_grestore (pgs=0x1) at ./base/gsstate.c:409 409 if (!pgs->saved) (rr) bt #0 0x7fa54364fc11 in gs_grestore (pgs=0x1) at ./base/gsstate.c:409 #1 0x7fa543662c39 in gx_default_text_restore_state (pte=) at ./base/gxchar.c:252 #2 0x7fa54358ad46 in textw_text_process (pte=0x55dc1a95c2f8) at ./devices/vector/gdevtxtw.c:2287 #3 0x7fa54371ca20 in op_show_continue (i_ctx_p=0x55dc17e6be98) at ./psi/zchar.c:690 #4 op_show_continue (i_ctx_p=0x55dc17e6be98) at ./psi/zchar.c:685 #5 0x7fa5436fd7e5 in interp (perror_object=, pref=, pi_ctx_p=) at ./psi/interp.c:1300 #6 gs_call_interp (pi_ctx_p=pi_ctx_p@entry=0x55dc17e38bf0, pref=pref@entry=0x7ffeafc82fa0, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x7ffeafc83050, perror_object=) at ./psi/interp.c:520 #7 0x7fa5436fee08 in gs_interpret (pi_ctx_p=pi_ctx_p@entry=0x55dc17e38bf0, pref=pref@entry=0x7ffeafc82fa0, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x7ffeafc83050, perror_object=, perror_object@entry=0x7ffeafc83060) at ./psi/interp.c:477 #8 0x7fa5436f17de in gs_main_interpret (perror_object=0x7ffeafc83060, pexit_code=0x7ffeafc83050, user_errors=1, pref=0x7ffeafc82fa0, minst=) at ./psi/imain.c:927 #9 gs_main_run_string_end (minst=minst@entry=0x55dc17e38b50, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x7ffeafc83050, perror_object=perror_object@entry=0x7ffeafc83060) at ./psi/imain.c:927 #10 0x7fa5436f1871 in gs_main_run_string_with_length (perror_object=0x7ffeafc83060, pexit_code=0x7ffeafc83050, user_errors=1, length=9, str=0x7fa543801aef ".runstdin", minst=0x55dc17e38b50) at ./psi/imain.c:871 #11 gs_main_run_string_with_length (minst=0x55dc17e38b50, str=0x7fa543801aef ".runstdin", length=9, user_errors=1, pexit_code=0x7ffeafc83050, perror_object=0x7ffeafc83060) at ./psi/imain.c:857 #12 0x7fa5436f4323 in run_string (perror_object=0x7ffeafc83060, pexit_code=0x7ffeafc83050, user_errors=, options=2, str=0x7fa543801aef ".runstdin", minst=0x55dc17e38b50) at ./psi/imainarg.c:1166 #13 swproc (minst=minst@entry=0x55dc17e38b50, arg=0x7ffeafc83060 "\001\017", pal=pal@entry=0x7ffeafc837a0) at ./psi/imainarg.c:367 #14 0x7fa5436f5543 in gs_main_init_with_args01 (minst=minst@entry=0x55dc17e38b50, argc=7, argv=0x7ffeafc84318) at ./psi/imainarg.c:224 #15 0x7fa5436f5739 in gs_main_init_with_args (minst=0x55dc17e38b50, argc=, argv=) at ./psi/imainarg.c:289 #16 0x55dc1650e1bc in main (argc=7, argv=0x7ffeafc84318) at ./psi/dxmainc.c:86 [2] Pointer gets overwritten here: Hardware watchpoint 1: *0x55dc1a95c680 Old value = (void *) 0x1 New value = (void *) 0x55dc17e6c188 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:419 419 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: Datei oder Verzeichnis nicht gefunden. 1: x/i $pc => 0x7fa543294d50 <__memmove_avx_unaligned_erms+480>: vmovdqa %ymm3,0x60(%rdi) (rr) bt #0 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:419 #1 0x7fa5437355d7 in memmove (__len=, __src=0x55dc1a95c888, __dest=0x55dc1a95c600) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:40 #2 gc_objects_compact (gcst=0x7ffeafc81cf0, gcst=0x7ffeafc81cf0, cp=0x55dc1a7d1eb0) at ./psi/igc.c:1348 #3 gs_gc_reclaim (pspaces=, global=0) at ./psi/igc.c:481 #4 0x7fa543700eb5 in gs_vmreclaim (global=0, dmem=0x55dc17e6bea0) at ./psi/ireclaim.c:165 #5 ireclaim (dmem=0x55dc17e6bea0, space=-1) at ./psi/ireclaim.c:80 #6 0x7fa5436fc3ed in interp_reclaim (pi_ctx_p=pi_ctx_p@entry=0x55dc17e38bf0, space=space@entry=-1) at ./psi/interp.c:450 #7 0x7fa5436fe1e6 in interp (perror_object=, pref=, pi_ctx_p=) at ./psi/interp.c:1817 #8 gs_call_interp (pi_ctx_p=pi_ctx_p@entry=0x55dc17e38bf0, pref=pref@entry=0x7ffeafc82fa0, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x7ffeafc83050, perror_object=) at ./psi/interp.c:520 #9 0x7fa5436fee08 in gs_interpret (pi_ctx_p=pi_ctx_p@entry=0x55dc17e38bf0, pref=pref@entry=0x7ffeafc82fa0, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x7ffeafc83050, perror_object=, perror_object@entry=0x7ffeafc83060) at ./psi/interp.c:477 #10 0x7fa5436f17de in gs_main_interpret (perror_object=0x7ffeafc83060, pexit_code=0x7ffeafc83050, user_errors=1, pref=0x7ffeafc82fa0, minst=) at ./psi/imain.c:927 #11 gs_main_run_string_end (minst=minst@entry=0x55dc17e38b50, user_errors=user_errors@entry=1, pexit_code=pexit_code@entry=0x7ffeafc83050, perror_object=perror_object@entry=0x7ffeafc83060) at ./psi/imain.c:927 #12 0x7fa5436f1871 in gs_main_run_string_with_length (perror_o
Bug#971949: pitivi: missing dependency on gir1.2-gst-plugins-bad-1.0
Package: pitivi Version: 2020.09-1 Severity: serious Justification: Policy 3.5 Dear Maintainer, After the upgrade to 2020.09-1, pitivi fails to start. I tried first via the GNOME UI, and nothing happened. Then I tried on a terminal, and got this: ~$ pitivi Não foi possível importar “GstTranscoder”. Certifique-se de que ele está disponível. That's pt_BR for `Impossible to import "GstTranscoder". Make sure it's available'`, but for some reason even setting LANG=C doesn't get me the message in English). Installing gir1.2-gst-plugins-bad-1.0 makes pitivi start. I have not tested it on a clean system to see if there are any other missing dependencies. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64, i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pitivi depends on: ii gir1.2-gdkpixbuf-2.02.40.0+dfsg-5 ii gir1.2-ges-1.0 1.18.0-2 ii gir1.2-glib-2.0 1.66.0-1 ii gir1.2-gst-plugins-base-1.0 1.18.0-2 ii gir1.2-gstreamer-1.01.18.0-3 ii gir1.2-gtk-3.0 3.24.23-2 ii gir1.2-pango-1.01.46.2-1 pn gstreamer1.0-audiosink ii gstreamer1.0-gl [gstreamer1.0-videosink]1.18.0-2 ii gstreamer1.0-gtk3 [gstreamer1.0-videosink] 1.18.0-1 ii gstreamer1.0-plugins-bad [gstreamer1.0-videosink] 1.18.0-2+b1 ii gstreamer1.0-plugins-base 1.18.0-2 ii gstreamer1.0-plugins-good [gstreamer1.0-videosink] 1.18.0-1 ii gstreamer1.0-x [gstreamer1.0-videosink] 1.18.0-2 ii libc6 2.31-3 ii libcairo2 1.16.0-4 ii libglib2.0-02.66.0-2 ii libgstreamer1.0-0 1.18.0-3 ii libpython3.83.8.6-1 ii python3 3.8.2-3 ii python3-cairo 1.16.2-4 ii python3-dbus1.2.16-3 ii python3-gi 3.38.0-1 ii python3-gi-cairo3.38.0-1 ii python3-gst-1.0 1.18.0-1 ii python3-matplotlib 3.3.2-1 ii python3-numpy 1:1.19.2-2 ii python3-xdg 0.26-3 ii python3.8 3.8.6-1 pitivi recommends no packages. Versions of packages pitivi suggests: pn frei0r-plugins ii gir1.2-gnomedesktop-3.03.38.1-1 pn gir1.2-gsound-1.0 ii gir1.2-notify-0.7 0.7.9-1 ii gstreamer1.0-libav 1.18.0-1 ii gstreamer1.0-plugins-ugly 1.18.0-1 -- no debconf information signature.asc Description: PGP signature
Bug#964195: guacamole-client: CVE-2020-9497 and CVE-2020-9498
Hi, I am currently investigating the security vulnerabilities in guacamole-client. I believe the reported CVE-2020-9497 and CVE-2020-9498 issues only affect the server part of guacamole but this one has not been packaged yet. The security researchers who reported the vulnerabilities have discussed them in detail at https://research.checkpoint.com/2020/apache-guacamole-rce/ The paragraph about the Disclosure Timeline mentions the following commit which appears to fix both issues. (or all four according to checkpoint.com) https://github.com/apache/guacamole-server/commit/a0e11dc81727528224d28466903454e1cb0266bb Please double-check if the findings are correct. At the moment I am inclined to mark the guacamole-client package as not affected by CVE-2020-9497 and CVE-2020-9498. Then I also looked into CVE-2016-1566. It appears to me the current version in stretch and unstable has already been fixed. If https://github.com/glyptodon/guacamole-client/commit/7da13129c432d1c0a577342a9bf23ca2bde9c367 is the fixing commit, then it is already included in version 0.9.9+dfsg-1 The other CVE, CVE-2018-1340 and CVE-2017-3158, are still relevant though. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#971948: python-bleach triggers autopkg test failures on every package
Package: src:python-bleach Version: 3.2.1-1 Severity: serious Tags: sid bullseye python-bleach triggers autopkg test failures on every package, as seen at https://tracker.debian.org/pkg/python-bleach autopkgtest for loggerhead/1.19~bzr501-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻) autopkgtest for nbconvert/5.6.1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻) autopkgtest for python-bleach/3.2.1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻) autopkgtest for python-readme-renderer/24.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)
Processed: Re: Bug#971947: calibre: crashes immediatly
Processing control commands: > close -1 Bug #971947 [calibre] calibre: crashes immediatly Marked Bug as done -- 971947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971947: calibre: crashes immediatly
Control: close -1 yes. seems the fault is on my side... sorry for the noise, i didnt realize the local path. Am 10. Oktober 2020 13:26:32 MESZ schrieb Norbert Preining : >Hi > >I don't really think that this: > >> RuntimeError: Failed to load the progress_indicator C extension, with >error: >/home/tobi/.local/lib/python3.8/site-packages/PyQt5/Qt/lib/libQt5Core.so. > >Sounds like something of a good idea. Are you really having you local >copy of Qt??? > >Best > >Norbert
Bug#971947: calibre: crashes immediatly
On Sat, Oct 10, 2020 at 11:42:30AM +, Norbert Preining wrote: > Hi Tobias, > > No problem, only one question I'm interested: how did you end up with a local > copy of Qt? I have seen a lot of things, but that was new! :-D Can't recall for sure, but not long a go I installed a python developement enviorment to hack on Octoprint. I guess thats where I got it… > -- > PREINING Norbert https://www.preining.info > Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev > GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 > > Oct 10, 2020 20:36:32 Tobias Frost : > > > Control: close -1 > > > > yes. seems the fault is on my side... sorry for the noise, i didnt realize > > the local path. > > > > Am 10. Oktober 2020 13:26:32 MESZ schrieb Norbert Preining > > : > >> Hi > >> > >> I don't really think that this: > >> > >>> RuntimeError: Failed to load the progress_indicator C extension, with > >> error: > >> /home/tobi/.local/lib/python3.8/site-packages/PyQt5/Qt/lib/libQt5Core.so. > >> > >> Sounds like something of a good idea. Are you really having you local > >> copy of Qt??? > >> > >> Best > >> > >> Norbert > >
Bug#971205: marked as done (netkit-ntalk: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_
Your message dated Sat, 10 Oct 2020 11:48:34 + with message-id and subject line Bug#971205: fixed in netkit-ntalk 0.17-17 has caused the Debian Bug report #971205, regarding netkit-ntalk: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1 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.) -- 971205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netkit-ntalk Version: 0.17-16 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=cmake >dh_update_autotools_config -O--buildsystem=cmake >dh_autoreconf -O--buildsystem=cmake >dh_auto_configure -O--buildsystem=cmake > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > -- The C compiler identification is GNU 10.2.0 > -- The CXX compiler identification is GNU 10.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > CMake Error at CMakeLists.txt:10 (find_library): > Could not find NCURSES using the following names: lncurses > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > //Path to a program. > CMAKE_AR:FILEPATH=/usr/bin/ar > > //Choose the type of build, options are: None Debug Release RelWithDebInfo > // MinSizeRel ... > CMAKE_BUILD_TYPE:STRING=None > > //Enable/Disable color output during build. > CMAKE_COLOR_MAKEFILE:BOOL=ON > > //CXX compiler > CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ > > //A wrapper around 'ar' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-10 > > //A wrapper around 'ranlib' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-10 > > //Flags used by the CXX compiler during all build types. > CMAKE_CXX_FLAGS:STRING=-g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 > > //Flags used by the CXX compiler during DEBUG builds. > CMAKE_CXX_FLAGS_DEBUG:STRING=-g > > //Flags used by the CXX compiler during MINSIZEREL builds. > CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG > > //Flags used by the CXX compiler during NONE builds. > CMAKE_CXX_FLAGS_NONE:STRING= > > //Flags used by the CXX compiler during RELEASE builds. > CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG > > //Flags used by the CXX compiler during RELWITHDEBINFO builds. > CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG > > //C compiler > CMAKE_C_COMPILER:FILEPATH=/usr/bin/c
Bug#971947: calibre: crashes immediatly
Hi Tobias, No problem, only one question I'm interested: how did you end up with a local copy of Qt? I have seen a lot of things, but that was new! :-D -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 Oct 10, 2020 20:36:32 Tobias Frost : > Control: close -1 > > yes. seems the fault is on my side... sorry for the noise, i didnt realize > the local path. > > Am 10. Oktober 2020 13:26:32 MESZ schrieb Norbert Preining > : >> Hi >> >> I don't really think that this: >> >>> RuntimeError: Failed to load the progress_indicator C extension, with >> error: >> /home/tobi/.local/lib/python3.8/site-packages/PyQt5/Qt/lib/libQt5Core.so. >> >> Sounds like something of a good idea. Are you really having you local >> copy of Qt??? >> >> Best >> >> Norbert >
Bug#971947: calibre: crashes immediatly
Hi
I don't really think that this:
> RuntimeError: Failed to load the progress_indicator C extension, with error:
> /home/tobi/.local/lib/python3.8/site-packages/PyQt5/Qt/lib/libQt5Core.so.
Sounds like something of a good idea. Are you really having you local copy of
Qt???
Best
Norbert
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Oct 10, 2020 20:21:09 Tobias Frost :
> Package: calibre
> Version: 5.2.0+dfsg-1
> Severity: serious
>
> calibre crashes immediatly on start:
>
> tobi@isildor:~$ calibre
> Traceback (most recent call last):
> File "/usr/bin/calibre", line 20, in
> sys.exit(calibre())
> File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre
> main(args)
> File "/usr/lib/calibre/calibre/gui2/main.py", line 529, in main
> app, opts, args = init_qt(args)
> File "/usr/lib/calibre/calibre/gui2/main.py", line 114, in init_qt
> app = Application(args, override_program_name=override,
> windows_app_uid=MAIN_APP_UID)
> File "/usr/lib/calibre/calibre/gui2/__init__.py", line 885, in __init__
> raise RuntimeError('Failed to load the progress_indicator C extension, with
> error: {}'.format(pi_err))
> RuntimeError: Failed to load the progress_indicator C extension, with error:
> /home/tobi/.local/lib/python3.8/site-packages/PyQt5/Qt/lib/libQt5Core.so.5:
> version `Qt_5.14' not found (required by
> /usr/lib/calibre/calibre/plugins/progress_indicator.so)
>
> (I've installed calibre on a partial updated sid machine; I will update and
> report if that fixes it.
> Maybe it misses some versioned depenencies)
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages calibre depends on:
> ii calibre-bin 5.2.0+dfsg-1
> ii dpkg 1.20.5
> ii fonts-liberation 1:1.07.4-11
> ii imagemagick 8:6.9.11.24+dfsg-1+b1
> ii imagemagick-6.q16 [imagemagick] 8:6.9.11.24+dfsg-1+b1
> ii libjpeg-turbo-progs 1:2.0.5-1.1
> ii libjxr-tools 1.1-6+b1
> ii optipng 0.7.7-1+b1
> ii poppler-utils 20.09.0-2
> ii python3 3.8.2-3
> ii python3-apsw 3.32.2-r1-1
> ii python3-bs4 4.9.2-1
> ii python3-chardet 3.0.4-7
> ii python3-chm 0.8.6-2+b1
> ii python3-css-parser 1.0.4-2
> ii python3-cssselect 1.1.0-2
> ii python3-cssutils 1.0.2-3
> ii python3-dateutil 2.8.1-4
> ii python3-dbus 1.2.16-3
> ii python3-feedparser 5.2.1-2
> ii python3-html2text 2020.1.16-1
> ii python3-html5-parser 0.4.9-3+b1
> ii python3-html5lib 1.1-2
> ii python3-lxml 4.5.2-1
> ii python3-markdown 3.2.2-2
> ii python3-mechanize 1:0.4.5-2
> ii python3-msgpack 0.6.2-1+b1
> ii python3-netifaces 0.10.9-0.2+b1
> ii python3-pil 7.2.0-1
> ii python3-pkg-resources 49.3.1-2
> ii python3-pygments 2.3.1+dfsg-4
> ii python3-pyparsing 2.4.7-1
> ii python3-pyqt5 5.15.1+dfsg-2
> ii python3-pyqt5.qtsvg 5.15.1+dfsg-2
> ii python3-pyqt5.qtwebengine 5.15.1-1
> ii python3-regex 0.1.20200714-1
> ii python3-routes 2.4.1-2
> ii python3-zeroconf 0.26.1-1
> ii xdg-utils 1.1.3-2
>
> Versions of packages calibre recommends:
> ii python3-dnspython 2.0.0-1
> ii udisks2 2.9.1-2
>
> Versions of packages calibre suggests:
> ii python3-openssl 19.1.0-2
> pn python3-unrardll
>
> -- no debconf information
>
Bug#971947: calibre: crashes immediatly
Package: calibre
Version: 5.2.0+dfsg-1
Severity: serious
calibre crashes immediatly on start:
tobi@isildor:~$ calibre
Traceback (most recent call last):
File "/usr/bin/calibre", line 20, in
sys.exit(calibre())
File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre
main(args)
File "/usr/lib/calibre/calibre/gui2/main.py", line 529, in main
app, opts, args = init_qt(args)
File "/usr/lib/calibre/calibre/gui2/main.py", line 114, in init_qt
app = Application(args, override_program_name=override,
windows_app_uid=MAIN_APP_UID)
File "/usr/lib/calibre/calibre/gui2/__init__.py", line 885, in __init__
raise RuntimeError('Failed to load the progress_indicator C extension, with
error: {}'.format(pi_err))
RuntimeError: Failed to load the progress_indicator C extension, with error:
/home/tobi/.local/lib/python3.8/site-packages/PyQt5/Qt/lib/libQt5Core.so.5:
version `Qt_5.14' not found (required by
/usr/lib/calibre/calibre/plugins/progress_indicator.so)
(I've installed calibre on a partial updated sid machine; I will update and
report if that fixes it.
Maybe it misses some versioned depenencies)
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages calibre depends on:
ii calibre-bin 5.2.0+dfsg-1
ii dpkg 1.20.5
ii fonts-liberation 1:1.07.4-11
ii imagemagick 8:6.9.11.24+dfsg-1+b1
ii imagemagick-6.q16 [imagemagick] 8:6.9.11.24+dfsg-1+b1
ii libjpeg-turbo-progs 1:2.0.5-1.1
ii libjxr-tools 1.1-6+b1
ii optipng 0.7.7-1+b1
ii poppler-utils20.09.0-2
ii python3 3.8.2-3
ii python3-apsw 3.32.2-r1-1
ii python3-bs4 4.9.2-1
ii python3-chardet 3.0.4-7
ii python3-chm 0.8.6-2+b1
ii python3-css-parser 1.0.4-2
ii python3-cssselect1.1.0-2
ii python3-cssutils 1.0.2-3
ii python3-dateutil 2.8.1-4
ii python3-dbus 1.2.16-3
ii python3-feedparser 5.2.1-2
ii python3-html2text2020.1.16-1
ii python3-html5-parser 0.4.9-3+b1
ii python3-html5lib 1.1-2
ii python3-lxml 4.5.2-1
ii python3-markdown 3.2.2-2
ii python3-mechanize1:0.4.5-2
ii python3-msgpack 0.6.2-1+b1
ii python3-netifaces0.10.9-0.2+b1
ii python3-pil 7.2.0-1
ii python3-pkg-resources49.3.1-2
ii python3-pygments 2.3.1+dfsg-4
ii python3-pyparsing2.4.7-1
ii python3-pyqt55.15.1+dfsg-2
ii python3-pyqt5.qtsvg 5.15.1+dfsg-2
ii python3-pyqt5.qtwebengine5.15.1-1
ii python3-regex0.1.20200714-1
ii python3-routes 2.4.1-2
ii python3-zeroconf 0.26.1-1
ii xdg-utils1.1.3-2
Versions of packages calibre recommends:
ii python3-dnspython 2.0.0-1
ii udisks22.9.1-2
Versions of packages calibre suggests:
ii python3-openssl 19.1.0-2
pn python3-unrardll
-- no debconf information
Bug#971919: marked as done (texlive-lang breaks logidee-tools autopkgtest: Command \fnum@table undefined)
Your message dated Sat, 10 Oct 2020 08:34:53 + with message-id and subject line Bug#971919: fixed in texlive-lang 2020.20200925-2 has caused the Debian Bug report #971919, regarding texlive-lang breaks logidee-tools autopkgtest: Command \fnum@table undefined 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.) -- 971919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: texlive-lang, logidee-tools Control: found -1 texlive-lang/2020.20200925-1 Control: found -1 logidee-tools/1.2.18 Control: affects -1 src:ghostscript Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of texlive-lang the autopkgtest of logidee-tools fails in testing when that autopkgtest is run with the binary packages of texlive-lang from unstable. It passes when run with only packages from testing. In tabular form: passfail texlive-lang from testing2020.20200925-1 logidee-tools from testing1.2.18 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of texlive-lang to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from texlive-lang/2020.20200925-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=texlive-lang https://ci.debian.net/data/autopkgtest/testing/amd64/l/logidee-tools/7376710/log.gz autopkgtest [16:46:54]: test basic: [--- Trying to run setup-logidee-tools Which directories may contain xml documents ? Creating Makefile in doc Trying to run some make commands make formations make[1]: Entering directory '/tmp/autopkgtest-lxc.y6fk1y54/downtmp/autopkgtest_tmp/mydocs/doc' make -f makefile.tmp formation_doc.tex make[2]: Entering directory '/tmp/autopkgtest-lxc.y6fk1y54/downtmp/autopkgtest_tmp/mydocs/doc' xsltproc --xinclude --stringparam selection none --stringparam cycle false --stringparam charte default --stringparam trainer false --stringparam lang en --stringparam slide true --stringparam description true /tmp/autopkgtest-lxc.y6fk1y54/downtmp/autopkgtest_tmp/mydocs/xsl/formation-tex.xsl formation_doc.xml > formation_doc.tex make[2]: Leaving directory '/tmp/autopkgtest-lxc.y6fk1y54/downtmp/autopkgtest_tmp/mydocs/doc' rm makefile.tmp # Three times to get cross-references right (argh) latex formation_doc.tex && latex formation_doc.tex && latex formation_doc.tex This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./formation_doc.tex LaTeX2e <2020-02-02> patch level 5 L3 programming layer <2020-09-24> (../charte/default/tex/logidoc.cls Document Class: logidoc 2000/19/04 v1.0 Standard Default logidee-tools document class (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def) (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def)) (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty) (/usr/share/texlive/texmf-dist/tex/latex/fancybox/fancybox.sty Style option: `fancybox' v1.4 <2010/05/15> (tvz) ) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg))) (/usr/share/texlive/texmf-dist/tex/latex/pstricks/pstricks.sty (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty) (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)) (/usr/share/texlive/texmf-dist/tex/generic/xkeyval
Bug#961491: fixed in sympa 6.2.40~dfsg-5
On 10/7/20 3:03 PM, Sylvain Beucler wrote: > Hi, > > I noticed this local root escalation yesterday and I'm working on a > Stretch LTS update. > See also https://salsa.debian.org/sympa-team/sympa/-/merge_requests/1 > > Are there plans to update buster? > > Cheers! > Sylvain > Hello Sylvain, thanks a lot of for your patch! I will talk to the security team concerning buster. Regards Racke -- Ecommerce and Linux consulting + Perl and web application programming. Debian and Sympa administration. Provisioning with Ansible. signature.asc Description: OpenPGP digital signature
Bug#971940: r-cran-shinystan: autopkgtest regression
Source: r-cran-shinystan
Version: 2.5.0-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the removal of r-cran-rstanarm from testing on 2020-07-22,
r-cran-shinystan's autopkgtests have been failing there [1].
However, r-cran-shinystan's tests currently also fail in unstable [2],
where r-cran-rstanarm is still available.
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-shinystan/testing/amd64/
[2] https://ci.debian.net/packages/r/r-cran-shinystan/unstable/amd64/
> library(testthat)
> library(shinystan)
Loading required package: shiny
code for methods in class “Rcpp_model_base” was not checked for
suspicious field assignments (recommended package ‘codetools’ not
available?)
code for methods in class “Rcpp_model_base” was not checked for
suspicious field assignments (recommended package ‘codetools’ not
available?)
code for methods in class “Rcpp_stan_fit” was not checked for
suspicious field assignments (recommended package ‘codetools’ not
available?)
code for methods in class “Rcpp_stan_fit” was not checked for
suspicious field assignments (recommended package ‘codetools’ not
available?)
This is shinystan version 2.5.0
>
> test_check("shinystan")
*** caught segfault ***
address 0x7f883b78e008, cause 'invalid permissions'
Traceback:
1: dyn.load(file, DLLpath = DLLpath, ...)
2: library.dynam(lib, package, package.lib)
3: loadNamespace(package, lib.loc)
4: doTryCatch(return(expr), name, parentenv, handler)
5: tryCatchOne(expr, names, parentenv, handlers[[1L]])
6: tryCatchList(expr, classes, parentenv, handlers)
7: tryCatch({attr(package, "LibPath") <- which.lib.locns <-
loadNamespace(package, lib.loc)env <- attachNamespace(ns, pos =
pos, deps, exclude, include.only)}, error = function(e) {P <- if
(!is.null(cc <- conditionCall(e))) paste(" in",
deparse(cc)[1L])else ""msg <- gettextf("package or namespace
load failed for %s%s:\n %s", sQuote(package), P,
conditionMessage(e))if (logical.return)
message(paste("Error:", msg), domain = NA)else stop(msg, call. =
FALSE, domain = NA)})
8: library(rstanarm)
9: withCallingHandlers(expr, packageStartupMessage = function(c)
tryInvokeRestart("muffleMessage"))
10: suppressPackageStartupMessages(library(rstanarm))
11: eval(code, test_env)
12: eval(code, test_env)
13: withCallingHandlers({eval(code, test_env)if (!handled &&
!is.null(test)) {skip_empty()}}, expectation =
handle_expectation, skip = handle_skip, warning = handle_warning,
message = handle_message, error = handle_error)
14: doTryCatch(return(expr), name, parentenv, handler)
15: tryCatchOne(expr, names, parentenv, handlers[[1L]])
16: tryCatchList(expr, names[-nh], parentenv, handlers[-nh])
17: doTryCatch(return(expr), name, parentenv, handler)
18: tryCatchOne(tryCatchList(expr, names[-nh], parentenv,
handlers[-nh]), names[nh], parentenv, handlers[[nh]])
19: tryCatchList(expr, classes, parentenv, handlers)
20: tryCatch(withCallingHandlers({eval(code, test_env)if
(!handled && !is.null(test)) {skip_empty()}}, expectation
= handle_expectation, skip = handle_skip, warning = handle_warning,
message = handle_message, error = handle_error), error =
handle_fatal, skip = function(e) {})
21: test_code(NULL, exprs, env)
22: source_file(path, new.env(parent = env), chdir = TRUE, wrap = wrap)
23: force(code)
24: doWithOneRestart(return(expr), restart)
25: withOneRestart(expr, restarts[[1L]])
26: withRestarts(testthat_abort_reporter = function() NULL, force(code))
27: with_reporter(reporter = reporter, start_end_reporter =
start_end_reporter, {reporter$start_file(basename(path))
lister$start_file(basename(path))source_file(path,
new.env(parent = env), chdir = TRUE, wrap = wrap)
reporter$.end_context()reporter$end_file()})
28: FUN(X[[i]], ...)
29: lapply(paths, test_file, env = env, reporter = current_reporter,
start_end_reporter = FALSE, load_helpers = FALSE, wrap = wrap)
30: force(code)
31: doWithOneRestart(return(expr), restart)
32: withOneRestart(expr, restarts[[1L]])
33: withRestarts(testthat_abort_reporter = function() NULL, force(code))
34: with_reporter(reporter = current_reporter, results <-
lapply(paths, test_file, env = env, reporter = current_reporter,
start_end_reporter = FALSE, load_helpers = FALSE, wrap = wrap))
35: test_files(paths, reporter = reporter, env = env, stop_on_failure
= stop_on_failure, stop_on_warning = stop_on_warning, wrap = wrap)
36: test_dir(path = test_path, reporter = reporter, env = env, filter
= filter, ..., stop_on_failure = stop_on_failure, stop_on_warning
= stop_on_warning, wrap = wrap)
37: test_package_dir(package = package, test_path = test_path, filter
= filter, reporter = reporter, ..., stop_on_failure =
stop_on_failure,
Processed: Re: Bug#971919: texlive-lang breaks logidee-tools autopkgtest: Command \fnum@table undefined
Processing commands for cont...@bugs.debian.org: > forwarded 971919 https://tug.org/pipermail/tex-live/2020-October/046197.html Bug #971919 [src:texlive-lang, src:logidee-tools] texlive-lang breaks logidee-tools autopkgtest: Command \fnum@table undefined Set Bug forwarded-to-address to 'https://tug.org/pipermail/tex-live/2020-October/046197.html'. > thanks Stopping processing here. Please contact me if you need assistance. -- 971919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971919: texlive-lang breaks logidee-tools autopkgtest: Command \fnum@table undefined
forwarded 971919 https://tug.org/pipermail/tex-live/2020-October/046197.html thanks Hi Paul, On Fri, 09 Oct 2020, Paul Gevers wrote: > With a recent upload of texlive-lang the autopkgtest of logidee-tools > fails in testing when that autopkgtest is run with the binary packages Yes, I am aware of that and have already initiated a fix in upupstream. The problem is a bug in babel-french. See the thread started here https://tug.org/pipermail/tex-live/2020-October/046197.html I hope this is fixed soon in babel-french, so that it goes into upstream TeX Live and then into Debian. Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
