Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade
Package: gvfs-backends Version: 1.50.0-1 Severity: grave Tags: a11y Justification: renders package unusable X-Debbugs-Cc: draco...@gmail.com Dear Maintainer, When try access smb://host/sharing on all file systens managers the system report fails when mount Windows sharing. Invalid argument. This sharing is accessible via smbclient //host/sharing. This problem started after upgrading the package. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 gvfs-backends depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gvfs 1.50.0-1 ii gvfs-common 1.50.0-1 ii gvfs-daemons 1.50.0-1 ii gvfs-libs1.50.0-1 ii libarchive13 3.6.0-1 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libavahi-glib1 0.8-5 ii libc62.33-7 ii libcdio-cdda210.2+2.0.0-1+b2 ii libcdio-paranoia210.2+2.0.0-1+b2 ii libcdio192.1.0-3 ii libgcrypt20 1.10.1-2 ii libgdata22 0.18.1-2 ii libglib2.0-0 2.72.1-1 ii libgoa-1.0-0b3.44.0-1 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port122.5.27-1 ii libgudev-1.0-0 237-2 ii libimobiledevice61.3.0-6+b1 ii libmtp9 1.1.19-1 ii libnfs13 4.0.0-1 ii libplist32.2.0-6+b1 ii libpolkit-gobject-1-00.105-33 ii libsmbclient 2:4.16.0+dfsg-6 ii libsoup-3.0-03.0.6-1 ii libusb-1.0-0 2:1.0.26-1 ii libxml2 2.9.13+dfsg-1 ii psmisc 23.4-2 Versions of packages gvfs-backends recommends: ii gnome-keyring 40.0-3 Versions of packages gvfs-backends suggests: ii bluez-obexd 5.64-1 ii samba-common 2:4.16.0+dfsg-6 -- no debconf information
Bug#1008573: gpg-agent -managed SSH keys stored in Yubikeys cannot be used with OpenSSH 8.9
On Mon, 11 Apr 2022 11:00:55 -0700 Vagrant Cascadian wrote: > Same problem with Gnuk, presumably multiple or all smartcards are > affected? I found an issue of scdaemon. At upstream development, it is tracked by: https://dev.gnupg.org/T5935 When the data is not so large (smaller than the buffer size of token), it works using Gnuk, with the patch of scdaemon. --
Processed: oneliner-el: diff for NMU version 0.3.6-9.2
Processing control commands: > tags 965756 + patch Bug #965756 [src:oneliner-el] oneliner-el: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965756 + pending Bug #965756 [src:oneliner-el] oneliner-el: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005500: NMU upload pending
Quoting Timo Röhling (2022-04-22 00:02:37) > I took the liberty to massage the PR to apply cleanly to version 2.4.8 > and uploaded the fix. Great! Thanks a lot! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#965756: oneliner-el: diff for NMU version 0.3.6-9.2
Control: tags 965756 + patch Control: tags 965756 + pending Dear maintainer, I've prepared an NMU for oneliner-el (versioned as 0.3.6-9.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -u oneliner-el-0.3.6/debian/changelog oneliner-el-0.3.6/debian/changelog --- oneliner-el-0.3.6/debian/changelog +++ oneliner-el-0.3.6/debian/changelog @@ -1,3 +1,16 @@ +oneliner-el (0.3.6-9.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: +- debian/compat: removed. +- debian/control: changed from 'debhelper' to 'debhelper-compat' in + Build-Depends field and bumped level to 13. +- debian/rules: using 'dh_prep' instead of 'dh_clean -k' because the + '-k' option is not supported since compat 12. +- Closes: #965756 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 11:01:29 -0300 + oneliner-el (0.3.6-9.1) unstable; urgency=medium * Non-maintainer upload. reverted: --- oneliner-el-0.3.6/debian/compat +++ oneliner-el-0.3.6.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u oneliner-el-0.3.6/debian/control oneliner-el-0.3.6/debian/control --- oneliner-el-0.3.6/debian/control +++ oneliner-el-0.3.6/debian/control @@ -1,6 +1,6 @@ Source: oneliner-el Section: editors -Build-Depends: debhelper (>= 5.0.0) +Build-Depends: debhelper-compat (= 13) Priority: optional Maintainer: OHURA Makoto Build-Depends-Indep: docbook-to-man, emacs, texinfo, po-debconf diff -u oneliner-el-0.3.6/debian/rules oneliner-el-0.3.6/debian/rules --- oneliner-el-0.3.6/debian/rules +++ oneliner-el-0.3.6/debian/rules @@ -68,7 +68,7 @@ install: build dh_testdir dh_testroot - dh_clean -k + dh_prep dh_installdirs # Add here commands to install the package into debian/oneliner-el.
Processed: nagios-plugins-rabbitmq: diff for NMU version 1:1.2.0-2.4
Processing control commands: > tags 965742 + patch Bug #965742 [src:nagios-plugins-rabbitmq] nagios-plugins-rabbitmq: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965742 + pending Bug #965742 [src:nagios-plugins-rabbitmq] nagios-plugins-rabbitmq: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965742: nagios-plugins-rabbitmq: diff for NMU version 1:1.2.0-2.4
Control: tags 965742 + patch Control: tags 965742 + pending Dear maintainer, I've prepared an NMU for nagios-plugins-rabbitmq (versioned as 1:1.2.0-2.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u nagios-plugins-rabbitmq-1.2.0/debian/changelog nagios-plugins-rabbitmq-1.2.0/debian/changelog --- nagios-plugins-rabbitmq-1.2.0/debian/changelog +++ nagios-plugins-rabbitmq-1.2.0/debian/changelog @@ -1,3 +1,14 @@ +nagios-plugins-rabbitmq (1:1.2.0-2.4) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965742 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 10:46:52 -0300 + nagios-plugins-rabbitmq (1:1.2.0-2.3) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. reverted: --- nagios-plugins-rabbitmq-1.2.0/debian/compat +++ nagios-plugins-rabbitmq-1.2.0.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u nagios-plugins-rabbitmq-1.2.0/debian/control nagios-plugins-rabbitmq-1.2.0/debian/control --- nagios-plugins-rabbitmq-1.2.0/debian/control +++ nagios-plugins-rabbitmq-1.2.0/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Cyril Bouthors Uploaders: Cyril Bouthors , Cyril Bouthors -Build-Depends: debhelper (>= 5), rsync, libmodule-build-perl +Build-Depends: debhelper-compat (= 13), rsync, libmodule-build-perl Standards-Version: 3.9.5 Package: nagios-plugins-rabbitmq
Processed: mylvmbackup: diff for NMU version 0.15-1.2
Processing control commands: > tags 965738 + patch Bug #965738 [src:mylvmbackup] mylvmbackup: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965738 + pending Bug #965738 [src:mylvmbackup] mylvmbackup: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965738: mylvmbackup: diff for NMU version 0.15-1.2
Control: tags 965738 + patch Control: tags 965738 + pending Dear maintainer, I've prepared an NMU for mylvmbackup (versioned as 0.15-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru mylvmbackup-0.15/debian/changelog mylvmbackup-0.15/debian/changelog --- mylvmbackup-0.15/debian/changelog 2017-01-13 17:34:08.0 -0200 +++ mylvmbackup-0.15/debian/changelog 2022-04-21 10:42:15.0 -0300 @@ -1,3 +1,14 @@ +mylvmbackup (0.15-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: +- debian/compat: removed. +- debian/control: changed from 'debhelper' to 'debhelper-compat' in + Build-Depends field and bumped level to 13. +- Closes: #965738 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 10:42:15 -0300 + mylvmbackup (0.15-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru mylvmbackup-0.15/debian/compat mylvmbackup-0.15/debian/compat --- mylvmbackup-0.15/debian/compat 2014-05-22 14:26:26.0 -0300 +++ mylvmbackup-0.15/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru mylvmbackup-0.15/debian/control mylvmbackup-0.15/debian/control --- mylvmbackup-0.15/debian/control 2017-01-13 17:34:08.0 -0200 +++ mylvmbackup-0.15/debian/control 2022-04-21 10:42:15.0 -0300 @@ -3,7 +3,7 @@ Priority: extra Maintainer: Debian MySQL Maintainers Uploaders: Norbert Tretkowski -Build-Depends: debhelper (>= 7.0.50), asciidoc (>= 8.2.0), xsltproc, docbook-xsl +Build-Depends: debhelper-compat (= 13), asciidoc (>= 8.2.0), xsltproc, docbook-xsl Standards-Version: 3.9.4 Homepage: http://lenzg.net/mylvmbackup/ Vcs-Browser: http://svn.debian.org/wsvn/pkg-mysql/mylvmbackup/
Bug#965733: mrb: diff for NMU version 0.3+nmu2
Control: tags 965733 + patch Control: tags 965733 + pending Dear maintainer, I've prepared an NMU for mrb (versioned as 0.3+nmu2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru mrb-0.3+nmu1/debian/changelog mrb-0.3+nmu2/debian/changelog --- mrb-0.3+nmu1/debian/changelog 2021-01-08 09:47:17.0 -0300 +++ mrb-0.3+nmu2/debian/changelog 2022-04-21 10:33:07.0 -0300 @@ -1,3 +1,14 @@ +mrb (0.3+nmu2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965733 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 10:33:07 -0300 + mrb (0.3+nmu1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru mrb-0.3+nmu1/debian/compat mrb-0.3+nmu2/debian/compat --- mrb-0.3+nmu1/debian/compat 2016-08-15 07:56:16.0 -0300 +++ mrb-0.3+nmu2/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 diff -Nru mrb-0.3+nmu1/debian/control mrb-0.3+nmu2/debian/control --- mrb-0.3+nmu1/debian/control 2016-08-15 07:56:16.0 -0300 +++ mrb-0.3+nmu2/debian/control 2022-04-21 10:33:07.0 -0300 @@ -2,7 +2,7 @@ Section: admin Priority: optional Maintainer: Ron Lee -Build-Depends: debhelper (>= 5), perl +Build-Depends: debhelper-compat (= 13), perl Standards-Version: 3.9.8.0 Package: mrb
Processed: mrb: diff for NMU version 0.3+nmu2
Processing control commands: > tags 965733 + patch Bug #965733 [src:mrb] mrb: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965733 + pending Bug #965733 [src:mrb] mrb: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005500: NMU upload pending
Hi,
I took the liberty to massage the PR to apply cleanly to version
2.4.8 and uploaded the fix.
Cheers
Timo
--
⢀⣴⠾⠻⢶⣦⠀ ╭╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄ ╰╯
diff -Nru doctest-2.4.8~ds/debian/changelog doctest-2.4.8~ds/debian/changelog
--- doctest-2.4.8~ds/debian/changelog 2022-01-14 22:32:17.0 +0100
+++ doctest-2.4.8~ds/debian/changelog 2022-04-21 23:47:01.0 +0200
@@ -1,3 +1,10 @@
+doctest (2.4.8~ds-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix build failure with move-only types (Closes: #1005500)
+
+ -- Timo Röhling Thu, 21 Apr 2022 23:47:01 +0200
+
doctest (2.4.8~ds-1) unstable; urgency=medium
[ upstream ]
diff -Nru doctest-2.4.8~ds/debian/patches/0001_Backport_PR_634.patch doctest-2.4.8~ds/debian/patches/0001_Backport_PR_634.patch
--- doctest-2.4.8~ds/debian/patches/0001_Backport_PR_634.patch 1970-01-01 01:00:00.0 +0100
+++ doctest-2.4.8~ds/debian/patches/0001_Backport_PR_634.patch 2022-04-21 23:45:26.0 +0200
@@ -0,0 +1,224 @@
+From: Stefan <29021710+saalv...@users.noreply.github.com>
+Date: Thu, 21 Apr 2022 23:41:36 +0200
+Subject: Fix move-only types failing to decompose correctly
+
+This is a backport of commit ce13bc44b99c87e918b98bdadb17008d2dd54d55
+
+Forwarded: https://github.com/doctest/doctest/pull/634
+---
+ doctest/doctest.h | 12 +--
+ doctest/parts/doctest_fwd.h| 6 +++---
+ examples/all_features/CMakeLists.txt | 1 +
+ examples/all_features/decomposition.cpp| 25 ++
+ .../all_features/test_output/decomposition.cpp.txt | 13 +++
+ .../test_output/decomposition.cpp_junit.txt| 14
+ .../test_output/decomposition.cpp_xml.txt | 20 +
+ examples/all_features/test_output/filter_2.txt | 2 +-
+ examples/all_features/test_output/filter_2_xml.txt | 3 ++-
+ 9 files changed, 85 insertions(+), 11 deletions(-)
+ create mode 100644 examples/all_features/decomposition.cpp
+ create mode 100644 examples/all_features/test_output/decomposition.cpp.txt
+ create mode 100644 examples/all_features/test_output/decomposition.cpp_junit.txt
+ create mode 100644 examples/all_features/test_output/decomposition.cpp_xml.txt
+
+diff --git a/doctest/doctest.h b/doctest/doctest.h
+index d25f526..31096ff 100644
+--- a/doctest/doctest.h
b/doctest/doctest.h
+@@ -390,9 +390,9 @@ namespace doctest { namespace detail {
+ static DOCTEST_CONSTEXPR int consume(const int*, int) { return 0; }
+ }}
+
+-#define DOCTEST_GLOBAL_NO_WARNINGS(var, ...) \
+-DOCTEST_CLANG_SUPPRESS_WARNING_WITH_PUSH("-Wglobal-constructors") \
+-static const int var = doctest::detail::consume(, __VA_ARGS__);\
++#define DOCTEST_GLOBAL_NO_WARNINGS(var, ...) \
++DOCTEST_CLANG_SUPPRESS_WARNING_WITH_PUSH("-Wglobal-constructors")\
++static const int var = doctest::detail::consume(, __VA_ARGS__); /* NOLINT(cert-err58-cpp) */ \
+ DOCTEST_CLANG_SUPPRESS_WARNING_POP
+
+ #ifndef DOCTEST_BREAK_INTO_DEBUGGER
+@@ -1320,7 +1320,7 @@ DOCTEST_CLANG_SUPPRESS_WARNING_WITH_PUSH("-Wunused-comparison")
+ assertType::Enum m_at;
+
+ explicit Expression_lhs(L&& in, assertType::Enum at)
+-: lhs(doctest::detail::forward(in))
++: lhs(static_cast(in))
+ , m_at(at) {}
+
+ DOCTEST_NOINLINE operator Result() {
+@@ -1394,8 +1394,8 @@ DOCTEST_CLANG_SUPPRESS_WARNING_POP
+ // https://github.com/catchorg/Catch2/issues/870
+ // https://github.com/catchorg/Catch2/issues/565
+ template
+-Expression_lhs operator<<(const L &) {
+-return Expression_lhs(doctest::detail::forward(operand), m_at);
++Expression_lhs operator<<(L&& operand) {
++return Expression_lhs(static_cast(operand), m_at);
+ }
+
+ template ::value,void >::type* = nullptr>
+diff --git a/doctest/parts/doctest_fwd.h b/doctest/parts/doctest_fwd.h
+index b0d786f..ff9fed0 100644
+--- a/doctest/parts/doctest_fwd.h
b/doctest/parts/doctest_fwd.h
+@@ -1317,7 +1317,7 @@ DOCTEST_CLANG_SUPPRESS_WARNING_WITH_PUSH("-Wunused-comparison")
+ assertType::Enum m_at;
+
+ explicit Expression_lhs(L&& in, assertType::Enum at)
+-: lhs(doctest::detail::forward(in))
++: lhs(static_cast(in))
+ , m_at(at) {}
+
+ DOCTEST_NOINLINE operator Result() {
+@@ -1391,8 +1391,8 @@ DOCTEST_CLANG_SUPPRESS_WARNING_POP
+ // https://github.com/catchorg/Catch2/issues/870
+
Bug#1005500: marked as done (doctest breaks argh build: doctest.h:1398:92: error: use of deleted function ‘doctest::detail::Expression_lhs >::Expression_l
Your message dated Thu, 21 Apr 2022 22:05:18 +
with message-id
and subject line Bug#1005500: fixed in doctest 2.4.8~ds-1.1
has caused the Debian Bug report #1005500,
regarding doctest breaks argh build: doctest.h:1398:92: error: use of deleted
function ‘doctest::detail::Expression_lhs
>::Expression_lhs(doctest::detail::Expression_lhs >&&)’
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.)
--
1005500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: argh
Version: 1.3.1+ds-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wshadow -Wnon-virtual-dtor -pedantic
> -std=gnu++11 -MD -MT CMakeFiles/argh_example.dir/example.cpp.o -MF
> CMakeFiles/argh_example.dir/example.cpp.o.d -o
> CMakeFiles/argh_example.dir/example.cpp.o -c /<>/example.cpp
> /<>/argh_tests.cpp: In function ‘void DOCTEST_ANON_FUNC_31()’:
> /<>/argh_tests.cpp:415:24: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 415 | char* argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> |^~~
> /<>/argh_tests.cpp:415:29: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 415 | char* argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~~
> /<>/argh_tests.cpp:415:35: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 415 | char* argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~
> /<>/argh_tests.cpp:415:40: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 415 | char* argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> |^~~~
> /<>/argh_tests.cpp:415:46: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 415 | char* argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~
> /<>/argh_tests.cpp:415:51: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 415 | char* argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~
> /<>/argh_tests.cpp:415:56: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 415 | char* argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> |^~~
> /<>/argh_tests.cpp:422:31: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 422 | char * const argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~
> /<>/argh_tests.cpp:422:36: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 422 | char * const argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> |^~~~
> /<>/argh_tests.cpp:422:42: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 422 | char * const argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~
> /<>/argh_tests.cpp:422:47: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 422 | char * const argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~~
> /<>/argh_tests.cpp:422:53: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 422 | char * const argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~
> /<>/argh_tests.cpp:422:58: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 422 | char * const argv[] = { "0", "-a", "1", "-b", "2", "3", "4" };
> | ^~~
> /<>/argh_tests.cpp:422:63: warning: ISO C++ forbids converting a
> string constant to ‘char*’ [-Wwrite-strings]
> 422 | char *
Processed: cli-common: diff for NMU version 0.10+nmu1
Processing control commands: > tags 965460 + patch Bug #965460 [src:cli-common] cli-common: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965460 + pending Bug #965460 [src:cli-common] cli-common: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965460: cli-common: diff for NMU version 0.10+nmu1
Control: tags 965460 + patch Control: tags 965460 + pending Dear maintainer, I've prepared an NMU for cli-common (versioned as 0.10+nmu1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru cli-common-0.10/debian/changelog cli-common-0.10+nmu1/debian/changelog --- cli-common-0.10/debian/changelog 2019-03-11 12:26:56.0 -0300 +++ cli-common-0.10+nmu1/debian/changelog 2022-04-21 09:30:10.0 -0300 @@ -1,3 +1,14 @@ +cli-common (0.10+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965460 + + -- Guilherme de Paula Xavier Segundo Thu, 21 Apr 2022 09:30:10 -0300 + cli-common (0.10) unstable; urgency=medium * The Cambridge BSP ‘Let’s RM the world’ release. diff -Nru cli-common-0.10/debian/compat cli-common-0.10+nmu1/debian/compat --- cli-common-0.10/debian/compat 2019-03-11 12:26:56.0 -0300 +++ cli-common-0.10+nmu1/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -5 \ Nenhum caractere de nova linha no final do arquivo diff -Nru cli-common-0.10/debian/control cli-common-0.10+nmu1/debian/control --- cli-common-0.10/debian/control 2019-03-11 12:26:56.0 -0300 +++ cli-common-0.10+nmu1/debian/control 2022-04-21 09:30:10.0 -0300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Mono Group Uploaders: Mirco Bauer -Build-Depends: debhelper (>= 5) +Build-Depends: debhelper-compat (= 13) Build-Depends-Indep: debiandoc-sgml, texlive-base-bin, texlive-base,
Bug#1008653: backintime-qt broken in sid after python upgrade
El jue, 21 abr 2022 a las 23:47, Agustin Martin () escribió: > If a new upstream version contains many changes that maintainer wants > to inspect closely, it is trivial to just include upstream fix for > this issue. I am attaching a patch (with unclosed changelog formatted > for NMU, modify as appropriate) that should deal with this problem, > just adapting upstream commit to Debian patch system. Really attaching patch, sorry for the noise. -- Agustin diff --git a/debian/changelog b/debian/changelog index faed735..0e926fc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +backintime (1.2.1-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * 01_tools.py_fix-1008653.patch: Get upstream changes to fix "tests no +longer work with Python 3.10" (Closes: #1008653). + + -- + backintime (1.2.1-3) unstable; urgency=medium * Cherry-pick patch for #946349 from upstream Git repository diff --git a/debian/patches/01_tools.py_fix-1008653.patch b/debian/patches/01_tools.py_fix-1008653.patch new file mode 100644 index 000..0ffcbe2 --- /dev/null +++ b/debian/patches/01_tools.py_fix-1008653.patch @@ -0,0 +1,28 @@ +From e1ae23ddc0b4229053e3e9c6c61adcb7f3d8e9b3 Mon Sep 17 00:00:00 2001 +From: Germar Reitze +Date: Mon, 5 Jul 2021 19:11:58 +0200 +Subject: [PATCH] Tests no longer work with Python 3.10 (fixes: #1175) + +--- a/common/tools.py b/common/tools.py +@@ -25,7 +25,10 @@ + import errno + import gzip + import tempfile +-import collections ++try: ++from collections.abc import MutableSet ++except ImportError: ++from collections import MutableSet + import hashlib + import ipaddress + import atexit +@@ -1802,7 +1805,7 @@ def reset(self, path): + self.history = [path,] + self.index = 0 + +-class OrderedSet(collections.MutableSet): ++class OrderedSet(MutableSet): + """ + OrderedSet from Python recipe + http://code.activestate.com/recipes/576694/ diff --git a/debian/patches/series b/debian/patches/series index 78aacb2..c486f48 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1 +1,2 @@ 00-fix-946349.patch +01_tools.py_fix-1008653.patch
Processed: Bug#1008653: backintime-qt broken in sid after python upgrade
Processing control commands: > tags -1 + patch fixed-upstream Bug #1008653 [backintime-qt] backintime-qt broken in sid after python upgrade Added tag(s) fixed-upstream and patch. -- 1008653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008653: backintime-qt broken in sid after python upgrade
Control: tags -1 + patch fixed-upstream On Wed, Apr 20, 2022 at 09:45:26AM +0200, Leonardo Canducci wrote: > Package: backintime-qt > Followup-For: Bug #1008653 > > I've installed backintime-qt from github (it's pretty straightforward, > just donwload the source and build two deb files with the provided > makedeb.sh) and it works fine. > > Please update this package. I'm by no means a developer but it seems > like a trivial fix. Hi, If a new upstream version contains many changes that maintainer wants to inspect closely, it is trivial to just include upstream fix for this issue. I am attaching a patch (with unclosed changelog formatted for NMU, modify as appropriate) that should deal with this problem, just adapting upstream commit to Debian patch system. Regards, -- Agustin
Bug#999139: marked as done (bplay: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 21 Apr 2022 20:22:43 + with message-id and subject line Bug#999139: fixed in bplay 0.991-10.1 has caused the Debian Bug report #999139, regarding bplay: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bplay Version: 0.991-10 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: bplay Source-Version: 0.991-10.1 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of bplay, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated bplay package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Apr 2022 16:32:45 -0300 Source: bplay Architecture: source Version: 0.991-10.1 Distribution: unstable Urgency: medium Maintainer: Carlos Laviola Changed-By: Joao Eriberto Mota Filho Closes: 965440 999139 Changes: bplay (0.991-10.1) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965440 * debian/rules: added missing targets build-arch and build-indep. (Closes: #999139) Checksums-Sha1: c957ef07083447355b951a6df58b997bae6538c3 1633 bplay_0.991-10.1.dsc 9a46fd2a10ce65b431847b5640363f3cd65fe5eb 15145 bplay_0.991-10.1.diff.gz 3dbe57cb343e8f4a7c93f07ce5c15cbbc8eb016f 5634 bplay_0.991-10.1_source.buildinfo Checksums-Sha256: 48c436eac57686f115f9a08880c5fd96b49996bd711f308d61a8e911a1339f11 1633 bplay_0.991-10.1.dsc 63374d038a52e2808936532997f26516e8c90f6b7dd48fda1369f1ec1911dc94 15145 bplay_0.991-10.1.diff.gz 2916802d4b649a6150b5a911dbb25dae24024a55e70c821c85b6ff0e764e5a87 5634 bplay_0.991-10.1_source.buildinfo Files: 0379c81ae7bc0e6c1d1c9a6e25174827 1633 sound optional bplay_0.991-10.1.dsc c6b0cccbd5484a061dfa381e5c28ad39 15145 sound optional bplay_0.991-10.1.diff.gz 451bea9b25cfae7466f7a5e4e5c6dcf9 5634 sound optional bplay_0.991-10.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJbHFsACgkQ3mO5xwTr 6e9OnQ/+IX1gMb6GzoTd+OnNiigy6lVLmRI1KsZyxoAhrch6BrMYBuqSTyiKgOcf iITdiqhC1AQclOw6lLysQOsuskJ+ijLdZnYOM9/NKfpim1VSIm4dz2Y1KsQHFkey Q6T950XfMzrB99b71QhfBXz8oDdcGqJ2SbnFVn/2nizYllZGuKLpxNoZzSqOb5ai 93Fx5JbZEq97rqifzBB/EFx/tD6POzldEHiM+P1XjPaS88mAxFEzw0n94sIfCnzN oeJPLPULQkQQCUDcGraQwYRkxxiE7Q7AgkTASY9lL5iJLiLI65k7uoSx4ts05HNq F0DrQK3/fv0cFRYzJLKq+LEh6k1FMb+A9zPZkervaCOS5BDaq/tg8udnOl+4uTk5 1mhBtaBYOrS+aKzqdkR40Kafr4FdaJB0nvS8D0iFXqpT6pvrBFl8rXVib+XWlGK7 XIQRLGHqnRyf6nSrhVOU2H77MvnTvlvpatBpBXBvurV6qpzJhubuin5RqKJLcVcc w6wFcS8spFIbH8Nwi5lr7EEF5+9ktbIA0KxkTk+cN5zF6ptvRO78xoi2qEDBaZri xvx88QBMYfDAyiQHs95Phkcpb55F+Fy+S4QCsGfBX/HA0UV+Bc3TAvHAAT6SBy3p 9DcBStnvNlTEkh1W0qpAXemIeAwclkgy0laVCqumnRDs1Cow22I= =ee8Q -END PGP SIGNATURE End Message ---
Bug#965610: marked as done (kdc2tiff: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 21 Apr 2022 20:23:03 + with message-id and subject line Bug#965610: fixed in kdc2tiff 0.35-10.1 has caused the Debian Bug report #965610, regarding kdc2tiff: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kdc2tiff Version: 0.35-10 Severity: normal Usertags: compat-5-6-removal Hi, The package kdc2tiff uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: kdc2tiff Source-Version: 0.35-10.1 Done: Guilherme de Paula Xavier Segundo We believe that the bug you reported is fixed in the latest version of kdc2tiff, 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. Guilherme de Paula Xavier Segundo (supplier of updated kdc2tiff 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, 21 Apr 2022 09:50:13 -0300 Source: kdc2tiff Architecture: source Version: 0.35-10.1 Distribution: unstable Urgency: medium Maintainer: Martin Wuertele Changed-By: Guilherme de Paula Xavier Segundo Closes: 965610 Changes: kdc2tiff (0.35-10.1) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965610 Checksums-Sha1: f5b8d3d113dff5b7de0302349ed189be6ca8345a 1737 kdc2tiff_0.35-10.1.dsc 02d6d7389a3830eb0bdbac41f3c78f6411b9acee 2925 kdc2tiff_0.35-10.1.diff.gz 7c346b2b27fade6ffa45ad74e50fa04bff179bcb 6034 kdc2tiff_0.35-10.1_source.buildinfo Checksums-Sha256: b574e6d57c86d1c5766e2e70f3000d654d564f0665f5ba7abf023d0a34a12f7d 1737 kdc2tiff_0.35-10.1.dsc e9467d44781fcf55af9d62c3c367fc78eeb071bf6d185c439ff4dad08f01d25b 2925 kdc2tiff_0.35-10.1.diff.gz 3241cebea4e40a496f29e330f807945b8d6c697478012cbc4c8b88d93d433f0c 6034 kdc2tiff_0.35-10.1_source.buildinfo Files: a8aa0b3ed7ff0e8591737c8053cf301c 1737 utils optional kdc2tiff_0.35-10.1.dsc 1d6053d16e27310bf56396759e969897 2925 utils optional kdc2tiff_0.35-10.1.diff.gz b451e944b73d0a553c97848240a24776 6034 utils optional kdc2tiff_0.35-10.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJhtncACgkQ3mO5xwTr 6e9PFxAAq23Q4YFqzB3ysj42yffVm3ZOLqNGS4eCx3gl/ZpreKCKr6U+JmguEgMn rPKKqHYBUQG8AONYElrJERIHQD5OwrGjnp5WHctsdMqe4eF/aLjpLITdKb/7EUTz RDfluIzxgocleSe2ml5jvFTMqRhWfeP1DA4OKNh8J+3gAGcwDNzOzZiPzDDWi2Y+ Uem08duQkkgE7tcsfqekexc1qmxGydQDIrL+tva1j94tIWsnI6ydvlPBE7r0q6Pw roavpzyQGFimEme2zieXlq5tj2gV9rWinqRjZ2tz9nrHZdr7TDTtkT/pqRrNjqR1 LIQTLlAJ0G/UE5uKJGhINKsF2K6BMXCxorql24RI54q/y+Nh1/VLOXklphd5iauK hmUHe0EXwZAmPUL7GpDK2rQUs7FONVHAPIgzWOB8jbMRXPrn4bkBvayVVpBunfce 0/KZxmB4uUx0OrEW3a5ND3MmlRIcpbKTmtG3iDL2fFlrx3ySlqSC6dJ0b/S84Pv+ /u1BcJqKH0favuXduQNgdHfTwQvXaooj48l5ao0TKVEHooVlfX0p9TX4zeChB+wA
Bug#1009606: marked as done (node-browserify-aes: FTBFS: ERROR: Coverage for statements (97.19%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 20:24:55 + with message-id and subject line Bug#1009606: fixed in node-browserify-aes 1.2.0-5 has caused the Debian Bug report #1009606, regarding node-browserify-aes: FTBFS: ERROR: Coverage for statements (97.19%) does not meet global threshold (100%) 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.) -- 1009606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-browserify-aes Version: 1.2.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/browserify-aes > /bin/sh -ex debian/tests/pkg-js/test > + tap -R spec test/index.js > > (node:3873976) [DEP0106] DeprecationWarning: crypto.createCipher is > deprecated. > (Use `node --trace-deprecation ...` to show where the warning was created) > (node:3873976) [DEP0005] DeprecationWarning: Buffer() is deprecated due to > security and usability issues. Please use the Buffer.alloc(), > Buffer.allocUnsafe(), or Buffer.from() methods instead. > (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr > (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr > test/index.js > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ should be strictly equal > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ should be strictly equal > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ should be strictly equal > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ should be strictly equal > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ should be strictly equal > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ should be strictly equal > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ final > > ✓ should be strictly equal > > ✓ intermediate > > ✓ intermediate 2 > > ✓ should be
Bug#965440: marked as done (bplay: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 21 Apr 2022 20:22:43 + with message-id and subject line Bug#965440: fixed in bplay 0.991-10.1 has caused the Debian Bug report #965440, regarding bplay: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bplay Version: 0.991-10 Severity: normal Usertags: compat-5-6-removal Hi, The package bplay uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: bplay Source-Version: 0.991-10.1 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of bplay, 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. Joao Eriberto Mota Filho (supplier of updated bplay package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Apr 2022 16:32:45 -0300 Source: bplay Architecture: source Version: 0.991-10.1 Distribution: unstable Urgency: medium Maintainer: Carlos Laviola Changed-By: Joao Eriberto Mota Filho Closes: 965440 999139 Changes: bplay (0.991-10.1) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965440 * debian/rules: added missing targets build-arch and build-indep. (Closes: #999139) Checksums-Sha1: c957ef07083447355b951a6df58b997bae6538c3 1633 bplay_0.991-10.1.dsc 9a46fd2a10ce65b431847b5640363f3cd65fe5eb 15145 bplay_0.991-10.1.diff.gz 3dbe57cb343e8f4a7c93f07ce5c15cbbc8eb016f 5634 bplay_0.991-10.1_source.buildinfo Checksums-Sha256: 48c436eac57686f115f9a08880c5fd96b49996bd711f308d61a8e911a1339f11 1633 bplay_0.991-10.1.dsc 63374d038a52e2808936532997f26516e8c90f6b7dd48fda1369f1ec1911dc94 15145 bplay_0.991-10.1.diff.gz 2916802d4b649a6150b5a911dbb25dae24024a55e70c821c85b6ff0e764e5a87 5634 bplay_0.991-10.1_source.buildinfo Files: 0379c81ae7bc0e6c1d1c9a6e25174827 1633 sound optional bplay_0.991-10.1.dsc c6b0cccbd5484a061dfa381e5c28ad39 15145 sound optional bplay_0.991-10.1.diff.gz 451bea9b25cfae7466f7a5e4e5c6dcf9 5634 sound optional bplay_0.991-10.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJbHFsACgkQ3mO5xwTr 6e9OnQ/+IX1gMb6GzoTd+OnNiigy6lVLmRI1KsZyxoAhrch6BrMYBuqSTyiKgOcf iITdiqhC1AQclOw6lLysQOsuskJ+ijLdZnYOM9/NKfpim1VSIm4dz2Y1KsQHFkey Q6T950XfMzrB99b71QhfBXz8oDdcGqJ2SbnFVn/2nizYllZGuKLpxNoZzSqOb5ai 93Fx5JbZEq97rqifzBB/EFx/tD6POzldEHiM+P1XjPaS88mAxFEzw0n94sIfCnzN oeJPLPULQkQQCUDcGraQwYRkxxiE7Q7AgkTASY9lL5iJLiLI65k7uoSx4ts05HNq F0DrQK3/fv0cFRYzJLKq+LEh6k1FMb+A9zPZkervaCOS5BDaq/tg8udnOl+4uTk5 1mhBtaBYOrS+aKzqdkR40Kafr4FdaJB0nvS8D0iFXqpT6pvrBFl8rXVib+XWlGK7 XIQRLGHqnRyf6nSrhVOU2H77MvnTvlvpatBpBXBvurV6qpzJhubuin5RqKJLcVcc
Processed: Bug#1009606 marked as pending in node-browserify-aes
Processing control commands: > tag -1 pending Bug #1009606 [src:node-browserify-aes] node-browserify-aes: FTBFS: ERROR: Coverage for statements (97.19%) does not meet global threshold (100%) Added tag(s) pending. -- 1009606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009606: marked as pending in node-browserify-aes
Control: tag -1 pending Hello, Bug #1009606 in node-browserify-aes 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/js-team/node-browserify-aes/-/commit/fe01c893088d0d60432ba77eba8ee3efc29111bb Fix test for tap >= 15 (--no-cov) Closes: #1009606 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009606
Bug#1009519: marked as pending in node-fstream-ignore
Control: tag -1 pending Hello, Bug #1009519 in node-fstream-ignore 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/js-team/node-fstream-ignore/-/commit/d664a3003a2c9a15fccb0604c1071d963d122e4d Fix test for tap >= 15 Closes: #1009519 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009519
Processed: Bug#1009519 marked as pending in node-fstream-ignore
Processing control commands: > tag -1 pending Bug #1009519 [src:node-fstream-ignore] node-fstream-ignore: FTBFS: ERROR: Coverage for statements (87.6%) does not meet global threshold (100%) Added tag(s) pending. -- 1009519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005175: marked as done (libtest-harness-perl: uninstallable, older than Perl 5.34 bundled version)
Your message dated Thu, 21 Apr 2022 19:49:19 + with message-id and subject line Bug#1005175: fixed in libtest-harness-perl 3.44-1 has caused the Debian Bug report #1005175, regarding libtest-harness-perl: uninstallable, older than Perl 5.34 bundled version 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.) -- 1005175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtest-harness-perl Version: 3.42-2 Severity: serious User: debian-p...@lists.debian.org Usertags: perl-5.34-transition Control: block 1003176 with -1 This package is currently uninstallable with Perl 5.34, which bundles a newer version and Provides a corresponding versioned virtual package. The following packages have unmet dependencies: perl-modules-5.34 : Breaks: libtest-harness-perl (< 3.43) 3.43 is not currently on CPAN. This separate package should probably just be removed from testing for now. Apologies for not spotting this earlier. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: libtest-harness-perl Source-Version: 3.44-1 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libtest-harness-perl, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libtest-harness-perl 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, 21 Apr 2022 21:19:50 +0200 Source: libtest-harness-perl Architecture: source Version: 3.44-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1005175 Changes: libtest-harness-perl (3.44-1) unstable; urgency=medium . * Import upstream version 3.44. Fixes "uninstallable, older than Perl 5.34 bundled version" (Closes: #1005175) * Update patches: drop hunks which are applied upstream. * Update years of packaging copyright. * Declare compliance with Debian Policy 4.6.0. * Bump debhelper-compat to 13. Checksums-Sha1: b3b7d6192272f4f5be1a6c300c373eaad9c5c9dc 2416 libtest-harness-perl_3.44-1.dsc 3221b5a6bdf6010e6ade23472e7a16f502dc9c60 215148 libtest-harness-perl_3.44.orig.tar.gz cda42ed1a32f5fa9c09ad81b710bef5f08851014 6128 libtest-harness-perl_3.44-1.debian.tar.xz Checksums-Sha256: c8709b2b26a32ca5e177abd41c62848165b07e841bca7de10346c1fdf6f7fbd7 2416 libtest-harness-perl_3.44-1.dsc 7eb591ea6b499ece6745ff3e80e60cee669f0037f9ccbc4e4511425f593e5297 215148 libtest-harness-perl_3.44.orig.tar.gz e043f449acd89d70030e6bd14b7718e8b2b1cba2304e5d1f101b1ee9bc6efd5b 6128 libtest-harness-perl_3.44-1.debian.tar.xz Files: 5fdba1fe6c8f9e31e28190c626691b32 2416 perl optional libtest-harness-perl_3.44-1.dsc a3482cded62f68c710a9955c4afb3dcf 215148 perl optional libtest-harness-perl_3.44.orig.tar.gz fbb42d7941d205a9cddbfecf588d8179 6128 perl optional libtest-harness-perl_3.44-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmJhrwNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZ8ig//arG9KsAXWpSLZ4Bl9xP1Om041jIuPcuGO01v0lktgt0gutz3pTWVP8Zu dn6FP8J445+0ALjBZS72/DGdrMDiOi3KZLQGdagsC/LLe9EAu62F2QQIsnFbdkB1 DqkPaLdmGIx/yjuoNSPzCoM3QGyUqyIifsXxBGSaV+4OcRAlOL5qRI0DsazGAlDD GLKTpvlFhpn4nhAGSW+t++kE3H8Ifpo9naAe8Wiu+gLkHX5gasmTRUUWHkJ7prVP bTSLbbFedh7Wb6de7cqNlck1kp93WpEMYN5uwimmqZdFnQ4gga3vw142mZsMppKM XJUUJLAF4qNolfqbMJxNaNCvOvxKpKm3lf+Y1i5tx3KsHROIchNbSoUOJ04Q2cga CG3prEr5nrSbJcHIjbRTuuzepEccRXEpZA7WZXYinEXSWDRCLkTYWn/Br0C/Y11E M/m6rBxF6jy8lDWlBfQrnE1HgPubMEP9ofjBevPOSHtbwX+kveHlxnq6KQScf6r+ XnGmMF0WLMIpxWkCDEq0hXVEWuGro5PWlg1TW4CP51nMKp204FqV7fhEAIfWuJ0A x9LdHpsMvU+oG6RdZnjFgFTj7gLNZBFSlTYpRHhn/lT7sSnBA1tQRJGSpOPOmiCR TwBzirJI8yHdp10XFakvF+nQ+RTaRB4nLBHdpvv2JHhpUep/KLo= =gTqU -END PGP SIGNATURE End Message ---
Bug#1009917: (no subject)
Thanks for your quick answer. > Mobian appears to be a Debian derivative, containing modifications > relative to Debian. I reported the bug using 'reportbug', you can see the related packages, seems there is no mobian specific packages. The mobian packages are here: https://packages.mobian-project.org There is a gtk3 mobian package, no related to this bug. The gtk4 packages are taken from debian. > Is this bug reproducible on a Debian system? Not here, I can't reproduce it on debian testing in PC. > The patch appears to be reverting a change that was made to fix a > different bug, so I'm not comfortable with reverting it without a better > idea of what is going on and what (if anything) the revert is likely > to break. yes, I understand you, I opened the debian bug because I see no advance in the upstream, and it is a critical bug. Best regards, Pablo.
Bug#1009418: autokey: diff for NMU version 0.95.10-2.1
Control: tags 1009418 + patch Control: tags 1009418 + pending Dear maintainer, I've prepared an NMU for autokey (versioned as 0.95.10-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru autokey-0.95.10/debian/changelog autokey-0.95.10/debian/changelog --- autokey-0.95.10/debian/changelog 2021-01-04 12:49:17.0 +0100 +++ autokey-0.95.10/debian/changelog 2022-04-21 20:38:41.0 +0200 @@ -1,3 +1,11 @@ +autokey (0.95.10-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS by relaxing hard-coded python path in d/not-installed +(Closes: #1009418). + + -- Tobias Frost Thu, 21 Apr 2022 20:38:41 +0200 + autokey (0.95.10-2) unstable; urgency=medium [ Ondřej Nový ] diff -Nru autokey-0.95.10/debian/not-installed autokey-0.95.10/debian/not-installed --- autokey-0.95.10/debian/not-installed 2021-01-04 12:48:25.0 +0100 +++ autokey-0.95.10/debian/not-installed 2022-04-19 07:18:09.0 +0200 @@ -1,2 +1,2 @@ -usr/lib/python3.9/dist-packages/autokey/__pycache__/ -usr/lib/python3.9/dist-packages/autokey/iomediator/__pycache__/ +usr/lib/python*/dist-packages/autokey/__pycache__/ +usr/lib/python*/dist-packages/autokey/iomediator/__pycache__/
Processed: autokey: diff for NMU version 0.95.10-2.1
Processing control commands: > tags 1009418 + patch Bug #1009418 [src:autokey] autokey: FTBFS: dh_missing: warning: usr/lib/python3.10/dist-packages/autokey/__pycache__/__init__.cpython-310.pyc exists in debian/tmp but is not installed to anywhere Added tag(s) patch. > tags 1009418 + pending Bug #1009418 [src:autokey] autokey: FTBFS: dh_missing: warning: usr/lib/python3.10/dist-packages/autokey/__pycache__/__init__.cpython-310.pyc exists in debian/tmp but is not installed to anywhere Added tag(s) pending. -- 1009418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: update bts metadata
Processing commands for cont...@bugs.debian.org:
> reassign 1009207 src:python-hbmqtt 0.9.6-1.2
Bug #1009207 {Done: Debian FTP Masters }
[src:python-websockets, src:python-hbmqtt] python-websockets breaks
python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri'
Bug reassigned from package 'src:python-websockets, src:python-hbmqtt' to
'src:python-hbmqtt'.
No longer marked as found in versions python-websockets/10.2-1 and
python-hbmqtt/0.9.6-1.2.
No longer marked as fixed in versions 0.9.6-1.2+rm.
Bug #1009207 {Done: Debian FTP Masters }
[src:python-hbmqtt] python-websockets breaks python-hbmqtt autopkgtest: cannot
import name 'InvalidURI' from 'websockets.uri'
Marked as found in versions python-hbmqtt/0.9.6-1.2.
> fixed 1009207 0.9.6-1.2+rm
Bug #1009207 {Done: Debian FTP Masters }
[src:python-hbmqtt] python-websockets breaks python-hbmqtt autopkgtest: cannot
import name 'InvalidURI' from 'websockets.uri'
The source 'python-hbmqtt' and version '0.9.6-1.2+rm' do not appear to match
any binary packages
Marked as fixed in versions python-hbmqtt/0.9.6-1.2+rm.
> affects 1009207 src:python-websockets
Bug #1009207 {Done: Debian FTP Masters }
[src:python-hbmqtt] python-websockets breaks python-hbmqtt autopkgtest: cannot
import name 'InvalidURI' from 'websockets.uri'
Added indication that 1009207 affects src:python-websockets
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1009207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1009987: bluez: Bluetooth service does not start
Package: bluez Version: 5.64-1 Severity: grave Justification: renders package unusable Hi, I installed testing non-free and immediately upgraded to unstable on a lenovo thinkbook in the last two day. After that bluetooth was not working. Note, that I did not test bluetooth while still being on testing. After many attempts to get latest firmware I eventually figured out the root cause: the bluetooth.service was not starting due to a missing /var/lib/bluetooth directory. Output for service status: × bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2022-04-21 19:56:46 CEST; 12min ago Docs: man:bluetoothd(8) Process: 2411 ExecStart=/usr/libexec/bluetooth/bluetoothd (code=exited, status=226/NAMESPACE) Main PID: 2411 (code=exited, status=226/NAMESPACE) CPU: 4ms Apr 21 19:56:46 lenovo-ben systemd[1]: Starting Bluetooth service... Apr 21 19:56:46 lenovo-ben systemd[2411]: bluetooth.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/lib/bluetooth: No such file or directory Apr 21 19:56:46 lenovo-ben systemd[2411]: bluetooth.service: Failed at step NAMESPACE spawning /usr/libexec/bluetooth/bluetoothd: No such file or directory Apr 21 19:56:46 lenovo-ben systemd[1]: bluetooth.service: Main process exited, code=exited, status=226/NAMESPACE Apr 21 19:56:46 lenovo-ben systemd[1]: bluetooth.service: Failed with result 'exit-code'. Calling install -m 700 -d /var/lib/bluetooth and restarting bluetooth service eventually fixed the issue. It cost me a couple of hours to find the solution, for a less tech-savy user bluetooth will be not usable. Therefore I set severity to grave. Regards Ben -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bluez depends on: ii dbus [default-dbus-system-bus] 1.14.0-1 ii init-system-helpers 1.62 ii kmod29-1 ii libasound2 1.2.6.1-2+b1 ii libc6 2.33-7 ii libdbus-1-3 1.14.0-1 ii libdw1 0.186-1 ii libglib2.0-02.72.1-1 ii libreadline88.1.2-1.2 ii libudev1250.4-1 ii lsb-base11.1.0 ii udev250.4-1 bluez recommends no packages. Versions of packages bluez suggests: pn pulseaudio-module-bluetooth -- no debconf information
Bug#1009917: gtk4 applications randomly crash on Mobian Pinephone
Control: retitle -1 gtk4 applications randomly crash on Mobian Pinephone Control: tags -1 = upstream moreinfo On Wed, 20 Apr 2022 at 18:03:34 +0200, ZenWalker wrote: > Unable to run these applications 10 times without crash with mobian pinephone: > > megapixels, gnome-calculator, and gnome-clocks and probably more gtk4 apps Mobian appears to be a Debian derivative, containing modifications relative to Debian. Is this bug reproducible on a Debian system? > The issue in gtk repo: > https://gitlab.gnome.org/GNOME/gtk/-/issues/4763 > > This patch fixes the bug: > https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4570.patch The patch appears to be reverting a change that was made to fix a different bug, so I'm not comfortable with reverting it without a better idea of what is going on and what (if anything) the revert is likely to break. I see you're already in contact with upstream. Please work with them to provide the information they need about what is happening on your Pinephone, which appears to be an embedded device, and therefore seems likely to have a graphics stack that does not match what is typically used on Debian and GNOME systems. smcv
Processed: Re: Bug#1009917: gtk4 applications randomly crash on Mobian Pinephone
Processing control commands: > retitle -1 gtk4 applications randomly crash on Mobian Pinephone Bug #1009917 [libgtk-4-1] gtk4 applications randomly crash Changed Bug title to 'gtk4 applications randomly crash on Mobian Pinephone' from 'gtk4 applications randomly crash'. > tags -1 = upstream moreinfo Bug #1009917 [libgtk-4-1] gtk4 applications randomly crash on Mobian Pinephone Added tag(s) upstream and moreinfo; removed tag(s) patch. -- 1009917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008312: marked as done (clementine doesn't start)
Your message dated Thu, 21 Apr 2022 17:04:32 +
with message-id
and subject line Bug#1008312: fixed in clementine
1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1
has caused the Debian Bug report #1008312,
regarding clementine doesn't start
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.)
--
1008312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clementine
Version: 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: scorpion2...@protonmail.com
Dear Maintainer,
clementine doesn't start:
-
clementine
17:53:14.456 WARN unknown QSqlDatabase: QSQLITE
driver not loaded
17:53:14.456 WARN unknown QSqlDatabase: available
drivers:
17:53:14.482 WARN unknown QSqlDatabase: QSQLITE
driver not loaded
17:53:14.482 WARN unknown QSqlDatabase: available
drivers:
17:53:14.482 WARN unknown QSqlQuery::prepare:
database not open
17:53:14.482 ERROR Database:601 db error: QSqlError("",
"Driver not loaded", "Driver not loaded")
17:53:14.483 ERROR Database:602 faulty query: ""
17:53:14.483 ERROR Database:603 bound values: QMap()
17:53:14.509 WARN unknown QSqlDatabase: QSQLITE
driver not loaded
17:53:14.509 WARN unknown QSqlDatabase: available
drivers:
17:53:14.509 WARN unknown
QSqlDatabasePrivate::removeDatabase: connection '1_thread_94661172328960' is
still in use, all queries will cease to work.
17:53:14.509 WARN unknown
QSqlDatabasePrivate::addDatabase: duplicate connection name
'1_thread_94661172328960', old connection removed.
17:53:14.509 WARN unknown QSqlQuery::prepare:
database not open
17:53:14.509 ERROR Database:601 db error: QSqlError("",
"Driver not loaded", "Driver not loaded")
17:53:14.509 ERROR Database:602 faulty query: ""
17:53:14.509 ERROR Database:603 bound values: QMap()
17:53:14.509 WARN unknown QSqlDatabase: QSQLITE
driver not loaded
17:53:14.509 WARN unknown QSqlDatabase: available
drivers:
17:53:14.510 WARN unknown
QSqlDatabasePrivate::removeDatabase: connection '1_thread_94661172328960' is
still in use, all queries will cease to work.
17:53:14.510 WARN unknown
QSqlDatabasePrivate::addDatabase: duplicate connection name
'1_thread_94661172328960', old connection removed.
17:53:15.335 WARN unknown QColor::fromHsv: HSV
parameters out of range
17:53:15.609 WARN unknown QSqlDatabase: QSQLITE
driver not loaded
17:53:15.609 WARN unknown QSqlDatabase: available
drivers:
17:53:15.610 WARN unknown
QSqlDatabasePrivate::removeDatabase: connection '1_thread_94661170634576' is
still in use, all queries will cease to work.
17:53:15.610 WARN unknown
QSqlDatabasePrivate::addDatabase: duplicate connection name
'1_thread_94661170634576', old connection removed.
17:53:15.920 WARN unknown QSqlQuery::prepare:
database not open
17:53:15.921 ERROR Database:601 db error: QSqlError("",
"Driver not loaded", "Driver not loaded")
17:53:15.921 ERROR Database:602 faulty query: ""
17:53:15.922 ERROR Database:603 bound values: QMap()
17:53:15.923 WARN unknown QSqlDatabase: QSQLITE
driver not loaded
17:53:15.928 WARN unknown QSqlDatabase: available
drivers:
17:53:15.929 WARN unknown
QSqlDatabasePrivate::removeDatabase: connection '1_thread_94661170634576' is
still in use, all queries will cease to work.
17:53:15.929 WARN unknown
QSqlDatabasePrivate::addDatabase: duplicate connection name
'1_thread_94661170634576', old connection removed.
17:53:15.942 WARN unknown QSqlQuery::prepare:
database not open
17:53:15.942 ERROR Database:601 db error: QSqlError("",
"Driver not loaded", "Driver not loaded")
17:53:15.942 ERROR Database:602 faulty query: ""
17:53:15.943 ERROR Database:603 bound values: QMap()
17:53:16.057 WARN unknown QSqlDatabase: QSQLITE
driver not loaded
17:53:16.058 WARN unknown QSqlDatabase: available
drivers:
17:53:16.058 WARN unknown
Bug#828550: marked as done (socat: FTBFS with openssl 1.1.0)
Your message dated Thu, 21 Apr 2022 19:01:23 +0200 with message-id and subject line Re: Bug#828550: socat: FTBFS with openssl 1.1.0 has caused the Debian Bug report #828550, regarding socat: FTBFS with openssl 1.1.0 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.) -- 828550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: socat Version: 1.7.3.1-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/socat_1.7.3.1-1_amd64-20160529-1537 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- On Mon, Nov 28, 2016 at 4:21 PM Gerhard Rieger wrote: > there are plans but no schedule for a stable version 2 release. Do not > rely on it. Since then socat 2.x has been abandoned and only 1.x releases are present - 2.0.0~beta was removed from Debian archives. Closing this bug report accordingly. Regards, Laszlo/GCS--- End Message ---
Bug#979719: marked as done (socat in experimental is obsolete and no installable)
Your message dated Thu, 21 Apr 2022 18:55:41 +0200 with message-id and subject line Re: Bug#979719: socat in experimental is obsolete and no installable has caused the Debian Bug report #979719, regarding socat in experimental is obsolete and no installable 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.) -- 979719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: socat Version: 2.0.0~beta9-1 1 Severity: grave Justification: renders package unusable I can no more be installed apt-get -t experimental install socat Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: socat : Depends: libssl1.0.2 (>= 1.0.2d) but it is not installable -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.6 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) Versions of packages socat depends on: ii libc6 2.31-9 ii libssl1.1 1.1.1i-1 ii libwrap0 7.6.q-31 socat recommends no packages. socat suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On Sun, Jan 10, 2021 at 6:57 PM Eric Valette wrote: > I can no more be installed > > apt-get -t experimental install socat Thanks for the heads-up. It's finally removed from the archives.--- End Message ---
Bug#1009555: marked as done (node-ini: FTBFS: ERROR: Coverage for statements (88.98%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 16:36:27 +
with message-id
and subject line Bug#1009555: fixed in node-ini 2.0.1-2
has caused the Debian Bug report #1009555,
regarding node-ini: FTBFS: ERROR: Coverage for statements (88.98%) does not
meet global threshold (100%)
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.)
--
1009555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-ini
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/ini
> /bin/sh -ex debian/tests/pkg-js/test
> + + grepls test/bar.js test/foo.js test/proto.js test/win32.js
> -v test/foo.js
> + tap test/bar.js test/proto.js test/win32.js
> TAP version 13
> ok 1 - test/bar.js # time=31.642ms {
> # Subtest: parse(stringify(x)) is same as x
> # count=10
> # { count: 10 }
> ok 1 - should be equivalent
> # drink=white russian
> # { drink: 'white russian' }
> ok 2 - should be equivalent
> # isTrue=true
> # { isTrue: true }
> ok 3 - should be equivalent
> # [theDude]
> # abides=true
> # rugCount=1
> # { theDude: { abides: true, rugCount: 1 } }
> ok 4 - should be equivalent
> 1..4
> ok 1 - parse(stringify(x)) is same as x # time=24.752ms
>
> 1..1
> # time=31.642ms
> }
>
> ok 2 - test/proto.js # time=6.257ms {
> ok 1 - should be equivalent
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equal
> ok 8 - should be equal
> ok 9 - should be equal
> ok 10 - should be equal
> ok 11 - should be equal
> ok 12 - should be equal
> 1..12
> # time=6.257ms
> }
>
> ok 3 - test/win32.js # time=15.89ms {
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equivalent
> ok 4 - should be equivalent
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equal
> ok 8 - should be equal
> 1..8
> # time=15.89ms
> }
>
> 1..3
> # time=1346.938ms
> ERROR: Coverage for lines (88.79%) does not meet global threshold (100%)
> ERROR: Coverage for branches (83%) does not meet global threshold (100%)
> ERROR: Coverage for statements (88.98%) does not meet global threshold (100%)
> --|-|--|-|-|--
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>
> --|-|--|-|-|--
> All files | 88.98 | 83 | 100 | 88.79 |
>
> ini.js | 88.98 | 83 | 100 | 88.79 |
> 26-27,46,101,166-170,179-184,197
> --|-|--|-|-|--
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-ini_2.0.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-ini
Source-Version: 2.0.1-2
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-ini, which is due to be installed in the Debian FTP
Bug#1009535: marked as done (node-console-control-strings: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 16:36:22 +
with message-id
and subject line Bug#1009535: fixed in node-console-control-strings 1.1.0-3
has caused the Debian Bug report #1009535,
regarding node-console-control-strings: FTBFS: ERROR: Coverage for branches
(90%) does not meet global threshold (100%)
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.)
--
1009535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-console-control-strings
Version: 1.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/console-control-strings
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test/console-strings.js
> TAP version 13
> (node:379108) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> not ok 1 - test/console-strings.js # time=36.939ms
> ---
> env: {}
> file: test/console-strings.js
> timeout: 3
> command: /usr/bin/node
> args:
> - test/console-strings.js
> stdio:
> - 0
> - pipe
> - 2
> cwd: /<>
> exitCode: 1
> ...
> {
> # Subtest: consoleControl
> ok 1 - up
> ok 2 - up 10
> ok 3 - down
> ok 4 - down 10
> ok 5 - forward
> ok 6 - forward 10
> ok 7 - back
> ok 8 - back 10
> ok 9 - nextLine
> ok 10 - nextLine 10
> ok 11 - previousLine
> ok 12 - previousLine 10
> ok 13 - eraseData
> ok 14 - eraseLine
> ok 15 - hideCursor
> ok 16 - showCursor
> ok 17 - horizontalAbsolute 10
> ok 18 - horizontalAbsolute 0
> ok 19 - horizontalAbsolute
> ok 20 - set color
> ok 21 - set invalid color
> ok 22 - absolute position
> ok 23 - goto start of line
> ok 24 - beep beeps
> not ok 25 - t.done is not a function
> ---
> stack: |
> Test. (test/console-strings.js:45:5)
> Test.cb (/usr/share/nodejs/libtap/lib/test.js:127:40)
> /usr/share/nodejs/libtap/lib/test.js:369:21
> Test.main (/usr/share/nodejs/libtap/lib/test.js:376:7)
> Test.runMain (/usr/share/nodejs/libtap/lib/base.js:178:15)
> /usr/share/nodejs/libtap/lib/test.js:485:13
> TAP.writeSubComment (/usr/share/nodejs/libtap/lib/test.js:556:5)
> Test. (/usr/share/nodejs/libtap/lib/test.js:484:14)
> at:
> line: 45
> column: 5
> file: test/console-strings.js
> function: Test.
> type: TypeError
> tapCaught: testFunctionThrow
> test: consoleControl
> source: |2
> t.is(consoleControl.beep(), '\x07', 'beep beeps')
> t.done()
> ^
> })
> ...
>
> 1..25
> # failed 1 of 25 tests
> not ok 1 - consoleControl # time=27.979ms
>
> 1..1
> # failed 1 test
> # time=36.939ms
> }
>
> 1..1
> # failed 1 test
> # time=1058.185ms
> ERROR: Coverage for branches (90%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
> --|-|--|-|-|---
> All files | 100 | 90 | 100 | 100 |
> index.js | 100 | 90 | 100 | 100 | 116
> --|-|--|-|-|---
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-console-control-strings_1.1.0-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
Processed: Bug#1009535 marked as pending in node-console-control-strings
Processing control commands: > tag -1 pending Bug #1009535 [src:node-console-control-strings] node-console-control-strings: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%) Added tag(s) pending. -- 1009535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009555: marked as pending in node-ini
Control: tag -1 pending Hello, Bug #1009555 in node-ini 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/js-team/node-ini/-/commit/809f90105ebd891f0345da7e7d1ed4e9e38b7c68 Fix test for tap >= 15 (--no-cov) Closes: #1009555 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009555
Bug#1009535: marked as pending in node-console-control-strings
Control: tag -1 pending Hello, Bug #1009535 in node-console-control-strings 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/js-team/node-console-control-strings/-/commit/e086087c8e09771412a5987289a81ec10d7d5931 Fix test for tap >= 15 (--no-cov) Closes: #1009535 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009535
Processed: Bug#1009555 marked as pending in node-ini
Processing control commands: > tag -1 pending Bug #1009555 [src:node-ini] node-ini: FTBFS: ERROR: Coverage for statements (88.98%) does not meet global threshold (100%) Added tag(s) pending. -- 1009555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009685: Resolved due to migration of Python3.10 (was: opm-grid: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.10.so')
Dear Paul, thanks for noticing. You are right the migration was not possible due to the Python transition. The problem was a chicken and egg one. And the update of the package was done to make the python migration possible (by removing remnants of the old python version from all opm packages). In retrospect that might not have been the best idea? Seems like this has actually worked as after the python transition finished all the autopkgtests are green on [1]. Or am I missing something? But maybe the correct fix would be to have a versioned dependency on the python lib for all binary packages that have references to it in the CMake configuration files? That would then be for all libopm-*-dev packages which ship these. At least this might prevent problems in future transitions. On a side note: We seem to have similar (or more serious) problems with opm-material, see [2]. There I do not understand why opm-models (which requires opm-material) can actually block the migration. But that might my limited knowledge. Would be cool if someone would enlighten me in this regard. Cheers, Markus [1] https://qa.debian.org/excuses.php?package=opm-grid [2] https://qa.debian.org/excuses.php?package=opm-material signature.asc Description: PGP signature
Bug#1008708: Bug is fixed in 2.14, current is 2.15
Unfortunately PysolFC is severely outdated in Debian. PysolFC not running with Python 3.10 has been fixed in 2.14, the current version is 2.15. The Debian package hasn't seen updates since two years ago, and now it's broken. Please update to 2.15 a.s.a.p.!
Bug#912682: marked as done (libextutils-parsexs-perl: version is older than Replaces+Breaks in perl-modules-5.28)
Your message dated Thu, 21 Apr 2022 15:25:37 + with message-id and subject line Bug#1009785: Removed package(s) from unstable has caused the Debian Bug report #912682, regarding libextutils-parsexs-perl: version is older than Replaces+Breaks in perl-modules-5.28 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.) -- 912682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libextutils-parsexs-perl Version: 3.35-1 Severity: serious The following packages have unmet dependencies: perl-modules-5.28 : Breaks: libextutils-parsexs-perl (< 3.39) --- End Message --- --- Begin Message --- Version: 3.35-1+rm Dear submitter, as the package libextutils-parsexs-perl 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/1009785 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1009836: marked as done (python3-pylsp-flake8: give upstream source in the d/copyright file)
Your message dated Thu, 21 Apr 2022 15:25:07 + with message-id and subject line Bug#1009941: Removed package(s) from unstable has caused the Debian Bug report #1009836, regarding python3-pylsp-flake8: give upstream source in the d/copyright 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.) -- 1009836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pylsp-flake8 Version: 0.4.0-2 Severity: serious The debian/copyright file for this package currently does not state the location of the upstream sources. (Marked "serious" because this is a violation of Policy section 12.5.) I'm happy to fix this myself if you would like me to. Best wishes, Julian --- End Message --- --- Begin Message --- Version: 0.4.0-2+rm Dear submitter, as the package python-lsp-flake8 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/1009941 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#978869: marked as done (nemiver: ftbfs with autoconf 2.70)
Your message dated Thu, 21 Apr 2022 15:21:01 + with message-id and subject line Bug#1009860: Removed package(s) from unstable has caused the Debian Bug report #978869, regarding nemiver: ftbfs with autoconf 2.70 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.) -- 978869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nemiver Version: 0.9.6-1.2 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/nemiver_0.9.6-1.2_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:116: the top level configure.ac:116: warning: The macro `AC_OUTPUT_COMMANDS' is obsolete. configure.ac:116: You should run autoupdate. ./lib/autoconf/status.m4:1025: AC_OUTPUT_COMMANDS is expanded from... /usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from... /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:116: the top level configure.ac:17: warning: The macro `AC_CONFIG_HEADER' is obsolete. configure.ac:17: You should run autoupdate. ./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from... configure.ac:17: the top level configure.ac:90: warning: The macro `AC_HELP_STRING' is obsolete. configure.ac:90: You should run autoupdate. ./lib/autoconf/general.m4:203: AC_HELP_STRING is expanded from... configure.ac:90: the top level configure.ac:116: warning: The macro `GLIB_GNU_GETTEXT' is obsolete. configure.ac:116: You should run autoupdate. aclocal.m4:388: GLIB_GNU_GETTEXT is expanded from... aclocal.m4:488: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:116: the top level configure.ac:116: warning: The macro `AC_TRY_LINK' is obsolete. configure.ac:116: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from... aclocal.m4:73: GLIB_LC_MESSAGES is expanded from... aclocal.m4:388: GLIB_GNU_GETTEXT is expanded from... aclocal.m4:488: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:116: the top level configure.ac:116: warning: The macro `AC_TRY_LINK' is obsolete. configure.ac:116: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/headers.m4:89: _AC_CHECK_HEADER_COMPILE is expanded from... ./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from... aclocal.m4:172: GLIB_WITH_NLS is expanded from... aclocal.m4:388: GLIB_GNU_GETTEXT is expanded from... aclocal.m4:488: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:116: the top level configure.ac:116: warning: The macro `AC_TRY_LINK' is obsolete. configure.ac:116: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/headers.m4:89: _AC_CHECK_HEADER_COMPILE is expanded from... ./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from... aclocal.m4:172: GLIB_WITH_NLS is expanded from... aclocal.m4:388: GLIB_GNU_GETTEXT is expanded from... aclocal.m4:488: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:116: the top level configure.ac:116: warning: The macro `AC_OUTPUT_COMMANDS' is obsolete. configure.ac:116: You should run autoupdate. ./lib/autoconf/status.m4:1025: AC_OUTPUT_COMMANDS is expanded from... aclocal.m4:172: GLIB_WITH_NLS is expanded from... aclocal.m4:388: GLIB_GNU_GETTEXT is expanded
Bug#966745: marked as done (gjots2: Unversioned Python removal in sid/bullseye)
Your message dated Thu, 21 Apr 2022 15:23:03 + with message-id and subject line Bug#1009932: Removed package(s) from unstable has caused the Debian Bug report #936619, regarding gjots2: 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.) -- 936619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gjots2 Version: 3.0.2-0.1 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 --- Version: 3.0.2-0.1+rm Dear submitter, as the package gjots2 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/1009932 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#936619: marked as done (gjots2: Python2 removal in sid/bullseye)
Your message dated Thu, 21 Apr 2022 15:23:03 + with message-id and subject line Bug#1009932: Removed package(s) from unstable has caused the Debian Bug report #936619, regarding gjots2: 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.) -- 936619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gjots2 Version: 3.0.2-0.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:gjots2 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: 3.0.2-0.1+rm Dear submitter, as the package gjots2 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/1009932 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1008781: marked as done (nemiver: Intent to remove from Debian)
Your message dated Thu, 21 Apr 2022 15:21:01 + with message-id and subject line Bug#1009860: Removed package(s) from unstable has caused the Debian Bug report #1008781, regarding nemiver: Intent to remove from Debian 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.) -- 1008781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nemiver Severity: serious Version: 0.9.6-1.2 I intend to file a removal bug for nemiver soon. It has failed to build for more than a year. It wasn't autoremoved sooner because it was included in one of the metapackages in meta-gnome3. GNOME Builder is the maintained recommended replacement. Nemiver has been archived upstream, which means that bugfixes, translations, and even bug reports are no longer accepted: https://gitlab.gnome.org/Archive/nemiver Thank you, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 0.9.6-1.2+rm Dear submitter, as the package nemiver 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/1009860 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#996263: marked as done (ctop: Should this package be removed?)
Your message dated Thu, 21 Apr 2022 15:19:18 + with message-id and subject line Bug#1009800: Removed package(s) from unstable has caused the Debian Bug report #996263, regarding ctop: Should this package be removed? 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.) -- 996263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ctop Severity: serious Version: 1.0.0-2.1 X-Debbugs-CC: czc...@debian.org Dear Debian ctop package maintainer, As discussed in https://bugs.debian.org/922061 , the current ctop software in Debian is unmaintained, incompatible with Debian 11 and later, and has a dead upstream. I believe this package should be removed from Debian to avoid confusion. I may submit a package removal request within 1 month if there's no other opinions. Also please let me know if we should choose other solutions. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 1.0.0-3+rm Dear submitter, as the package ctop 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/1009800 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#930874: marked as done ([ERROR] Failed to locate cgroup mountpoints.)
Your message dated Thu, 21 Apr 2022 15:19:18 + with message-id and subject line Bug#1009800: Removed package(s) from unstable has caused the Debian Bug report #930874, regarding [ERROR] Failed to locate cgroup mountpoints. 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.) -- 930874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ctop Version: 1.0.0-2 Severity: important anthony@Zia:~$ ctop [ERROR] Failed to locate cgroup mountpoints. But it's mounted, and being used: $ ls /sys/fs/cgroup/ cgroup.controllers cgroup.procscgroup.threads system.slice cgroup.max.depthcgroup.stat init.scope user.slice cgroup.max.descendants cgroup.subtree_control machine.slice Possibly ctop doesn't understand the cgroup2 unified hierarchy? -- System Information: Debian Release: 10.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'unstable-debug'), (200, 'unstable'), (150, 'stable'), (100, 'experimental-debug'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 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_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ctop depends on: ii python3 3.7.3-1 ctop recommends no packages. ctop suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.0.0-3+rm Dear submitter, as the package ctop 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/1009800 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1009522: marked as done (node-move-concurrently: FTBFS: ERROR: Coverage for branches (93.75%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 15:18:46 +
with message-id
and subject line Bug#1009522: fixed in node-move-concurrently 1.0.1-5
has caused the Debian Bug report #1009522,
regarding node-move-concurrently: FTBFS: ERROR: Coverage for branches (93.75%)
does not meet global threshold (100%)
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.)
--
1009522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-move-concurrently
Version: 1.0.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/move-concurrently
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test
> TAP version 13
> (node:4153194) DeprecationWarning: isDeeply() is deprecated, use strictSame()
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:4153194) DeprecationWarning: is() is deprecated, use equal() instead
> not ok 1 - test/integration.js # time=92.054ms
> ---
> env: {}
> file: test/integration.js
> timeout: 3
> command: /usr/bin/node
> args:
> - test/integration.js
> stdio:
> - 0
> - pipe
> - 2
> cwd: /<>
> exitCode: 1
> ...
> {
> # Subtest: setup
> not ok 1 - t.done is not a function
> ---
> stack: |
> Test. (test/integration.js:58:5)
> Test.cb (/usr/share/nodejs/libtap/lib/test.js:127:40)
> /usr/share/nodejs/libtap/lib/test.js:369:21
> Test.main (/usr/share/nodejs/libtap/lib/test.js:376:7)
> Test.runMain (/usr/share/nodejs/libtap/lib/base.js:178:15)
> /usr/share/nodejs/libtap/lib/test.js:485:13
> TAP.writeSubComment (/usr/share/nodejs/libtap/lib/test.js:556:5)
> Test. (/usr/share/nodejs/libtap/lib/test.js:484:14)
> at:
> line: 58
> column: 5
> file: test/integration.js
> function: Test.
> type: TypeError
> tapCaught: testFunctionThrow
> test: setup
> source: |2
> testDirContent = loadFromDir(testdir('test-dir'))
> t.done()
> ^
> })
> ...
>
> 1..1
> # failed 1 test
> not ok 1 - setup # time=33.094ms
>
> # Subtest: move
> 1..4
> ok 1 - moved file content
> ok 2 - moved symlink
> ok 3 - moved dir symlink
> # Subtest: moved test directory
> ok 1 - /: type
> ok 2 - /subdir: type
> ok 3 - /subdir/file1.json: type
> ok 4 - /subdir/file1.json: file string content
> ok 5 - /subdir/file2.json: type
> ok 6 - /subdir/file2.json: file string content
> ok 7 - /subdir2: type
> ok 8 - /subdir2/file2.json: type
> ok 9 - /subdir2/file2.json: file string content
> ok 10 - /subdir2/linky: type
> ok 11 - /subdir2/linky: symlink destination
> ok 12 - /subdir2/subsub: type
> ok 13 - /subdir2/subsub/: type
> ok 14 - /subdir2/subsub/: symlink destination
> ok 15 - /subdir2/subsub/: type
> ok 16 - /subdir2/subsub/.json: type
> ok 17 - /subdir2/subsub/.json: file string content
> not ok 18 - t.done is not a function
> ---
> stack: |
> Test. (/usr/share/nodejs/tacks/tap.js:5:7)
> Test.cb (/usr/share/nodejs/libtap/lib/test.js:127:40)
> /usr/share/nodejs/libtap/lib/test.js:369:21
> Test.main (/usr/share/nodejs/libtap/lib/test.js:376:7)
> Test.runMain (/usr/share/nodejs/libtap/lib/base.js:178:15)
> /usr/share/nodejs/libtap/lib/test.js:485:13
> Test.writeSubComment
> (/usr/share/nodejs/libtap/lib/test.js:556:5)
> Test. (/usr/share/nodejs/libtap/lib/test.js:484:14)
> at:
> line: 5
> column: 7
>
Bug#1007126: marked as done (laszip: Should not be included in bookworm)
Your message dated Thu, 21 Apr 2022 15:15:49 + with message-id and subject line Bug#1009625: Removed package(s) from unstable has caused the Debian Bug report #1007126, regarding laszip: Should not be included in bookworm 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.) -- 1007126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: laszip Version: 3.4.3-2 Severity: serious Tags: bookworm sid Justification: in the maintainer's opinion, makes the package unsuitable for release Control: block -1 by 1006910 LASzip is dead upstream, literally. It should not be included in bookworm, but cannot be removed before PDAL is. --- End Message --- --- Begin Message --- Version: 3.4.3-2+rm Dear submitter, as the package laszip 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/1009625 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1006910: marked as done (pdal: Should not be included in bookworm)
Your message dated Thu, 21 Apr 2022 15:15:07 + with message-id and subject line Bug#1009624: Removed package(s) from unstable has caused the Debian Bug report #1006910, regarding pdal: Should not be included in bookworm 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.) -- 1006910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdal Version: 2.3.0+ds-2 Severity: serious Tags: upstream Justification: in the maintainer's opinion, makes the package unsuitable for release PDAL upstream has exhausted my tolerance of his combative attitude. I am no longer willing to spend time on maintaining this package. The package should be removed from Debian, as others should not be subjected to his attitude either. At time of writing cloudcompare and facet-analyser have pdal as a build dependency, and paraview also has it in its binary package dependencies. These packages will need to remove their pdal support. Once that's done pdal can be removed from Debian. If anyone wants to take over maintenance of the pdal package despite a combative upstream, that will need to happen outside the GIS team. --- End Message --- --- Begin Message --- Version: 2.3.0+ds-2+rm Dear submitter, as the package pdal 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/1009624 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#938544: marked as done (sphinx-patchqueue: Python2 removal in sid/bullseye)
Your message dated Thu, 21 Apr 2022 15:12:09 + with message-id and subject line Bug#1009269: Removed package(s) from unstable has caused the Debian Bug report #938544, regarding sphinx-patchqueue: 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.) -- 938544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sphinx-patchqueue Version: 0.5.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. 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:sphinx-patchqueue 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: 0.5.0-2+rm Dear submitter, as the package sphinx-patchqueue 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/1009269 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937869: marked as done (python-keepkey: Python2 removal in sid/bullseye)
Your message dated Thu, 21 Apr 2022 15:13:24 + with message-id and subject line Bug#1009335: Removed package(s) from unstable has caused the Debian Bug report #937869, regarding python-keepkey: 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.) -- 937869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-keepkey Version: 0.7.3-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:python-keepkey 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: 0.7.3-1+rm Dear submitter, as the package python-keepkey 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/1009335 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#934839: marked as done (python-keepkey: depends on cruft package.)
Your message dated Thu, 21 Apr 2022 15:13:24 + with message-id and subject line Bug#1009335: Removed package(s) from unstable has caused the Debian Bug report #934839, regarding python-keepkey: depends on cruft package. 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.) -- 934839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-keepkey Severity: serious Version: 0.7.3-1 Tags: bullseye, sid python-keepkey depends on the python-ecdsa binary package which is no longer built by the corresponding source package. If you want your package to stay around you need to migrate to python 3. --- End Message --- --- Begin Message --- Version: 0.7.3-1+rm Dear submitter, as the package python-keepkey 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/1009335 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1009273: marked as done (Should python-keepkey be removed?)
Your message dated Thu, 21 Apr 2022 15:13:24 + with message-id and subject line Bug#1009335: Removed package(s) from unstable has caused the Debian Bug report #1009273, regarding Should python-keepkey be removed? 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.) -- 1009273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-keepkey Version: 0.7.3-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 and thus removed from testing since 2019 - Last upload back in 2016 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz --- End Message --- --- Begin Message --- Version: 0.7.3-1+rm Dear submitter, as the package python-keepkey 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/1009335 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. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1009207: marked as done (python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri')
Your message dated Thu, 21 Apr 2022 15:14:10 + with message-id and subject line Bug#1009377: Removed package(s) from unstable has caused the Debian Bug report #1009207, regarding python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri' 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.) -- 1009207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-websockets, python-hbmqtt Control: found -1 python-websockets/10.2-1 Control: found -1 python-hbmqtt/0.9.6-1.2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of python-websockets the autopkgtest of python-hbmqtt fails in testing when that autopkgtest is run with the binary packages of python-websockets from unstable. It passes when run with only packages from testing. In tabular form: passfail python-websockets from testing10.2-1 python-hbmqtt from testing0.9.6-1.2 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 python-websockets 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 [1] https://qa.debian.org/excuses.php?package=python-websockets https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-hbmqtt/20680286/log.gz ..EE == ERROR: Failure: ImportError (cannot import name 'InvalidURI' from 'websockets.uri' (/usr/lib/python3/dist-packages/websockets/uri.py)) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in loadTestsFromName module = self.importer.importFromPath( File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.9/imp.py", line 234, in load_module return load_source(name, filename, file) File "/usr/lib/python3.9/imp.py", line 171, in load_source module = _load(spec) File "", line 711, in _load File "", line 680, in _load_unlocked File "", line 850, in exec_module File "", line 228, in _call_with_frames_removed File "/tmp/autopkgtest-lxc.2lsi273v/downtmp/build.QiD/src/tests/test_broker.py", line 21, in from hbmqtt.client import MQTTClient, ConnectException File "/tmp/autopkgtest-lxc.2lsi273v/downtmp/build.QiD/src/hbmqtt/client.py", line 21, in from websockets.uri import InvalidURI ImportError: cannot import name 'InvalidURI' from 'websockets.uri' (/usr/lib/python3/dist-packages/websockets/uri.py) == ERROR: Failure: ImportError (cannot import name 'InvalidURI' from 'websockets.uri' (/usr/lib/python3/dist-packages/websockets/uri.py)) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in loadTestsFromName module = self.importer.importFromPath( File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.9/imp.py", line 234, in load_module return load_source(name, filename, file) File "/usr/lib/python3.9/imp.py", line 171, in load_source module = _load(spec) File "", line 711, in _load File "", line 680, in _load_unlocked File
Bug#1009113: marked as done (python-hbmqtt: (autopkgtest) needs update for python3.10: the *loop* parameter was removed from Queue() since it is no longer necessary)
Your message dated Thu, 21 Apr 2022 15:14:10 + with message-id and subject line Bug#1009377: Removed package(s) from unstable has caused the Debian Bug report #1009113, regarding python-hbmqtt: (autopkgtest) needs update for python3.10: the *loop* parameter was removed from Queue() since it is no longer necessary 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.) -- 1009113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-hbmqtt Version: 0.9.6-1.2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of python-hbmqtt fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.4-1 python-hbmqtt from testing0.9.6-1.2 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 python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists what's new in Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-hbmqtt/20664028/log.gz EE....E.E. == ERROR: test_init_handler (tests.mqtt.protocol.test_handler.ProtocolHandlerTest) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.86erqpai/downtmp/build.Dj7/src/tests/mqtt/protocol/test_handler.py", line 42, in test_init_handler Session() File "/tmp/autopkgtest-lxc.86erqpai/downtmp/build.Dj7/src/hbmqtt/session.py", line 132, in __init__ self.retained_messages = Queue(loop=self._loop) File "/usr/lib/python3.10/asyncio/queues.py", line 34, in __init__ super().__init__(loop=loop) File "/usr/lib/python3.10/asyncio/mixins.py", line 17, in __init__ raise TypeError( TypeError: As of 3.10, the *loop* parameter was removed from Queue() since it is no longer necessary >> begin captured logging << passlib.utils.compat: DEBUG: loaded lazy attr 'SafeConfigParser': 'configparser.ConfigParser'> passlib.utils.compat: DEBUG: loaded lazy attr 'NativeStringIO': '_io.StringIO'> passlib.utils.compat: DEBUG: loaded lazy attr 'BytesIO': '_io.BytesIO'> asyncio: DEBUG: Using selector: EpollSelector hbmqtt.test.plugins: DEBUG: Loading plugins for namespace hbmqtt.test.plugins hbmqtt.test.plugins: DEBUG: Loading plugin event_plugin = tests.plugins.test_manager:EventTestPlugin hbmqtt.test.plugins: DEBUG: Initializing plugin event_plugin = tests.plugins.test_manager:EventTestPlugin hbmqtt.test.plugins: DEBUG: Plugin event_plugin ready hbmqtt.test.plugins: DEBUG: Loading plugin packet_logger_plugin = hbmqtt.plugins.logging:PacketLoggerPlugin hbmqtt.test.plugins: DEBUG: Initializing plugin packet_logger_plugin = hbmqtt.plugins.logging:PacketLoggerPlugin hbmqtt.test.plugins: DEBUG: Plugin packet_logger_plugin ready hbmqtt.test.plugins: DEBUG: Loading plugin test_plugin = tests.plugins.test_manager:TestPlugin hbmqtt.test.plugins: DEBUG: Initializing plugin test_plugin = tests.plugins.test_manager:TestPlugin hbmqtt.test.plugins: DEBUG: Plugin test_plugin ready - >> end captured logging << - == ERROR: test_publish_qos0 (tests.mqtt.protocol.test_handler.ProtocolHandlerTest) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.86erqpai/downtmp/build.Dj7/src/tests/mqtt/protocol/test_handler.py", line 110, in test_publish_qos0 server =
Processed: Re: Bug#1009475: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'
Processing commands for cont...@bugs.debian.org: > forcemerge 1009097 1009475 Bug #1009097 [src:meson] meson: (autopkgtest) needs update for python3.10: MesonVersionMismatchException.__init__() missing 1 required positional argument: 'current_version' Bug #1009475 [src:meson] meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function' Added indication that 1009475 affects src:python3-defaults Marked as found in versions meson/0.61.2-1. Bug #1009097 [src:meson] meson: (autopkgtest) needs update for python3.10: MesonVersionMismatchException.__init__() missing 1 required positional argument: 'current_version' Marked as found in versions meson/0.62.0-1. Added tag(s) ftbfs. Merged 1009097 1009475 > stop Stopping processing here. Please contact me if you need assistance. -- 1009097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009097 1009475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1009522 marked as pending in node-move-concurrently
Processing control commands: > tag -1 pending Bug #1009522 [src:node-move-concurrently] node-move-concurrently: FTBFS: ERROR: Coverage for branches (93.75%) does not meet global threshold (100%) Added tag(s) pending. -- 1009522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009522: marked as pending in node-move-concurrently
Control: tag -1 pending Hello, Bug #1009522 in node-move-concurrently 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/js-team/node-move-concurrently/-/commit/f69674fed92f9559a0fd6c6b574d93c1b59f9684 Fix test for tap >= 15 (--no-cov) Closes: #1009522 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009522
Bug#1008608: marked as done (r-cran-purrrogress: autopkgtest failure: Error in `is(pb, c("winProgressBar", "tkProgressBar", "txtProgressBar"))`: length(class2) == 1L is not TRUE)
Your message dated Thu, 21 Apr 2022 15:06:03 +
with message-id
and subject line Bug#1009121: Removed package(s) from unstable
has caused the Debian Bug report #1008608,
regarding r-cran-purrrogress: autopkgtest failure: Error in `is(pb,
c("winProgressBar", "tkProgressBar", "txtProgressBar"))`: length(class2) == 1L
is not TRUE
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.)
--
1008608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-purrrogress
Version: 0.1.1-3
Severity: serious
Dear Maintainer,
r-cran-purrrogress is failing its autopkgtest, some of the output
is pasted below.
| ══ Failed tests
| ── Error (apply.R:86:5): with_apply_progress
───
| Error in `is(pb, c("winProgressBar", "tkProgressBar", "txtProgressBar"))`:
length(class2) == 1L is not TRUE
| Backtrace:
| ▆
| 1. ├─base::sapply(...) at R/apply.R:86:4
| 2. │ └─base::match.fun(FUN)
| 3. └─purrrogress::with_progress(...)
| 4. └─purrrogress:::with_apply_progress(i, ..., fun = fun)
| 5. └─purrrogress:::push_progress(pb, "with_progress")
| 6. └─methods::is(pb, c("winProgressBar", "tkProgressBar",
"txtProgressBar"))
| 7. └─base::stopifnot(length(class2) == 1L)
| ── Error (purrr.R:193:5): with_purrr_progress
──
| Error in `is(pb, c("winProgressBar", "tkProgressBar", "txtProgressBar"))`:
length(class2) == 1L is not TRUE
Full log at:
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-purrrogress/20434057/log.gz
Regards,
Nilesh
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages r-cran-purrrogress depends on:
ii r-base-core [r-api-4.0] 4.1.2-1
ii r-cran-assertthat0.2.1-2
ii r-cran-glue 1.5.1-1
ii r-cran-hms 1.1.1-1
pn r-cran-pkgcond
ii r-cran-purrr 0.3.4-1+b1
ii r-cran-r62.5.1-1
ii r-cran-rlang 0.4.12-2
pn r-cran-testextra
Versions of packages r-cran-purrrogress recommends:
ii r-cran-testthat 3.1.0-2
Versions of packages r-cran-purrrogress suggests:
ii r-cran-covr 3.5.1+dfsg-2
ii r-cran-stringi 1.7.6-1
ii r-cran-tibble 3.1.6+dfsg-1
--- End Message ---
--- Begin Message ---
Version: 0.1.1-3+rm
Dear submitter,
as the package r-cran-purrrogress 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/1009121
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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#994036: marked as done (x11-xkb-utils: xkbcomp gives internal errors on unknown keysyms (e.g. some XF86* with xkb-data 2.33-1))
Your message dated Thu, 21 Apr 2022 13:33:56 +
with message-id
and subject line Bug#953032: fixed in x11-xkb-utils 7.7+6
has caused the Debian Bug report #953032,
regarding x11-xkb-utils: xkbcomp gives internal errors on unknown keysyms (e.g.
some XF86* with xkb-data 2.33-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.)
--
953032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xkb-data
Version: 2.33-1
Severity: normal
On one of my machines, with a default configuration:
cventin:~> cat .xkb/keymap/custom
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
xkb_symbols { include "pc+gb+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};
cventin:~> xkbcomp -w 0 -I$HOME/.xkb -R$HOME/.xkb keymap/custom $DISPLAY
Internal error: Could not resolve keysym XF86BrightnessAuto
Internal error: Could not resolve keysym XF86DisplayOff
Internal error: Could not resolve keysym XF86Info
Internal error: Could not resolve keysym XF86AspectRatio
Internal error: Could not resolve keysym XF86DVD
Internal error: Could not resolve keysym XF86Audio
Internal error: Could not resolve keysym XF86ChannelUp
Internal error: Could not resolve keysym XF86ChannelDown
Internal error: Could not resolve keysym XF86Break
Internal error: Could not resolve keysym XF86VideoPhone
Internal error: Could not resolve keysym XF86ZoomReset
Internal error: Could not resolve keysym XF86Editor
Internal error: Could not resolve keysym XF86GraphicsEditor
Internal error: Could not resolve keysym XF86Presentation
Internal error: Could not resolve keysym XF86Database
Internal error: Could not resolve keysym XF86Voicemail
Internal error: Could not resolve keysym XF86Addressbook
Internal error: Could not resolve keysym XF86DisplayToggle
Internal error: Could not resolve keysym XF86SpellCheck
Internal error: Could not resolve keysym XF86ContextMenu
Internal error: Could not resolve keysym XF86MediaRepeat
Internal error: Could not resolve keysym XF8610ChannelsUp
Internal error: Could not resolve keysym XF8610ChannelsDown
Internal error: Could not resolve keysym XF86Images
Internal error: Could not resolve keysym XF86NotificationCenter
Internal error: Could not resolve keysym XF86PickupPhone
Internal error: Could not resolve keysym XF86HangupPhone
Internal error: Could not resolve keysym XF86Fn
Internal error: Could not resolve keysym XF86Fn_Esc
Internal error: Could not resolve keysym XF86FnRightShift
Internal error: Could not resolve keysym XF86Numeric0
Internal error: Could not resolve keysym XF86Numeric1
Internal error: Could not resolve keysym XF86Numeric2
Internal error: Could not resolve keysym XF86Numeric3
Internal error: Could not resolve keysym XF86Numeric4
Internal error: Could not resolve keysym XF86Numeric5
Internal error: Could not resolve keysym XF86Numeric6
Internal error: Could not resolve keysym XF86Numeric7
Internal error: Could not resolve keysym XF86Numeric8
Internal error: Could not resolve keysym XF86Numeric9
Internal error: Could not resolve keysym XF86NumericStar
Internal error: Could not resolve keysym XF86NumericPound
Internal error: Could not resolve keysym XF86NumericA
Internal error: Could not resolve keysym XF86NumericB
Internal error: Could not resolve keysym XF86NumericC
Internal error: Could not resolve keysym XF86NumericD
Internal error: Could not resolve keysym XF86CameraFocus
Internal error: Could not resolve keysym XF86WPSButton
Internal error: Could not resolve keysym XF86CameraZoomIn
Internal error: Could not resolve keysym XF86CameraZoomOut
Internal error: Could not resolve keysym XF86CameraUp
Internal error: Could not resolve keysym XF86CameraDown
Internal error: Could not resolve keysym XF86CameraLeft
Internal error: Could not resolve keysym XF86CameraRight
Internal error: Could not resolve keysym XF86AttendantOn
Internal error: Could not resolve keysym XF86AttendantOff
Internal error: Could not resolve keysym XF86AttendantToggle
Internal error: Could not resolve keysym XF86LightsToggle
Internal error: Could not resolve keysym XF86ALSToggle
Internal error: Could not resolve keysym XF86Buttonconfig
Internal error: Could not resolve keysym XF86Taskmanager
Internal error: Could not resolve keysym XF86Journal
Internal error: Could not resolve keysym
Bug#953032: marked as done (xkbcomp: Internal error: Could not resolve keysym XF86FullScreen)
Your message dated Thu, 21 Apr 2022 13:33:56 + with message-id and subject line Bug#953032: fixed in x11-xkb-utils 7.7+6 has caused the Debian Bug report #953032, regarding xkbcomp: Internal error: Could not resolve keysym XF86FullScreen 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.) -- 953032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: x11-xkb-utils Version: 7.7+5 journalctl reports thousands of sh[1052]: The XKEYBOARD keymap compiler (xkbcomp) reports: sh[1052]: > Internal error: Could not resolve keysym XF86FullScreen sh[1052]: Errors from xkbcomp are not fatal to the X server Versions of packages x11-xkb-utils depends on: ii libc62.29-10 ii libx11-6 2:1.6.9-2 ii libxaw7 2:1.0.13-1+b2 ii libxkbfile1 1:1.0.9-2+b12 ii libxt6 1:1.1.5-1+b3 --- End Message --- --- Begin Message --- Source: x11-xkb-utils Source-Version: 7.7+6 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of x11-xkb-utils, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated x11-xkb-utils 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, 21 Apr 2022 16:06:35 +0300 Source: x11-xkb-utils Built-For-Profiles: noudeb Architecture: source Version: 7.7+6 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 953032 Changes: x11-xkb-utils (7.7+6) unstable; urgency=medium . [ Jelmer Vernooij ] * Replace XC-Package-Type with Package-Type. . [ Timo Aaltonen ] * setxkbmap 1.3.3. * xkbcomp 1.4.5. (Closes: #953032) * control: Migrate to x11proto-dev. * control: Add libxrandr-dev build-dep for setxkbmap. Checksums-Sha1: dd71a88591189277f7664d85e8de5d7a10f26dde 1813 x11-xkb-utils_7.7+6.dsc cbdaa941107d75678a81c304cce0dc1ca670ee9d 1087207 x11-xkb-utils_7.7+6.tar.gz b4946fabd6f8555ac5a25c6d428fdf76a474cfd7 7468 x11-xkb-utils_7.7+6_source.buildinfo Checksums-Sha256: ed47e07f1adda56eb56c355328d7e8b2bcf38b2b3655997b6471a53080787095 1813 x11-xkb-utils_7.7+6.dsc e26a86ea637c9085e021d5b08fb82a467aabea34c30ec0c3aed4993961d80b05 1087207 x11-xkb-utils_7.7+6.tar.gz dfff4bfaf256ccf6a3bb81d6a9587baa4fcb2bebbaa5b8419d57c9240c5c4a53 7468 x11-xkb-utils_7.7+6_source.buildinfo Files: cdd7066ce7e17936c8f478b56431ba0d 1813 x11 optional x11-xkb-utils_7.7+6.dsc 5147eb8faf1098eb5837924ff383fef3 1087207 x11 optional x11-xkb-utils_7.7+6.tar.gz 6d594b5b7217dba774c054f1ae56969d 7468 x11 optional x11-xkb-utils_7.7+6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmJhVuoACgkQy3AxZaiJ hNwjVhAArMBgz1jVeyCi89QSjr1Z94oqkQD3nTmOaHau9c/C6FAlH1lInc3XbPwk y0q7b5rEB9W2Kg2nCf4yN08Do0WtNJ0NDvI4anBzgeyLOO9FQN4xhRQ4jLmjajs0 pMEnO+uqIUyQl/es5rbodQoJiyHit+KRzwHrBJNfB3vSpsBZ2TxVCvpSZCwHqFvR RyUKqzThi9lzu+qCtYNywrHoKWOZnM1YSdcHPm7dasNt22goqriLtFr/ydsu1/zv 9zcTELDB2Waqlu9g5r8NbzmJNTVWdf/qPUbdfRqKhJkDR0q03kKqx+dANBkWnGL4 aWum6Klxfi8wAWAdgb9lJyYO1FuOfgMsWnwzzp5HmGFRftfKlBKJZ9BCJdqdGbsj WUkCIwzT5B8DC/T03PnQZauSqT0zDueJRG2Rh3ZE0vGGJiwljRasJYYp/8zp4TE3 Dqls8WkGndoDsD5SQWpVv8TDQ6BQN07+WBKGEkWdK1c2G8mWNveWS4KVNDLopumD mH/YJFlgfZrpPfpVH8XSr1H/6RQ7T7kdlcIzSeQSKNwRmGmF8zgRuz2Chh7QVUTY 1qU7ukqBPVTsowKrG3Og0HFR7Fel0o9EGDZcPhOPgSp2O93+Aggu0915wR+HkIQn hOzLRHZ7Q2Fyxc5lH0fhqytk5pQtDBMu/UWvooJEZDWlFT01Q5w= =JIMy -END PGP SIGNATURE End Message ---
Bug#1009968: cannot import name 'Mapping' from 'collections' with Python 3.10 -- new upstream version needed
Package: python3-frozen-flask Version: 0.11-3.1 Severity: critical Using this library in Python 3.10 generates an ImportError. % python3 Python 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from flask_frozen import Freezer Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/flask_frozen/__init__.py", line 29, in from collections import Mapping ImportError: cannot import name 'Mapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py) Upstream has a version 0.15 available.
Bug#1009184: marked as done (FTBFS against Octave 7)
Your message dated Thu, 21 Apr 2022 14:42:32 +0200 with message-id <5b5e22b0ccb50f5966ff2c7b69a3f7733df75dc8.ca...@debian.org> and subject line Re: Bug#1009184: FTBFS against Octave 7 has caused the Debian Bug report #1009184, regarding FTBFS against Octave 7 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.) -- 1009184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-tisean Version: 0.2.3.hg.2019.08.26-1 Severity: important Tags: ftbfs User: debian-oct...@lists.debian.org Usertags: octave7 Dear Maintainer, octave-tisean FTBFS against octave 7.1.0, which is currently in experimental. A build log is attached. The severity of this bug will be raised once Octave 7 is uploaded to unstable. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org octave-tisean_0.2.3.hg.2019.08.26-1.gz Description: application/gzip --- End Message --- --- Begin Message --- Le vendredi 08 avril 2022 à 14:10 +0200, Sébastien Villemot a écrit : > Source: octave-tisean > Version: 0.2.3.hg.2019.08.26-1 > Severity: important > Tags: ftbfs > User: debian-oct...@lists.debian.org > Usertags: octave7 > > octave-tisean FTBFS against octave 7.1.0, which is currently in experimental. Actually octave-tisean built fine against octave 7.1.0 on amd64. The build failure I experienced must therefore be linked to something else. Closing as invalid. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: #1003463 found outside experimental too
Processing commands for cont...@bugs.debian.org: > found 1003463 arcanist/0~git20200925-1 Bug #1003463 [arcanist] Functionally broken with current PHP The source arcanist and version 0~git20200925-1 do not appear to match any binary packages Marked as found in versions arcanist/0~git20200925-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1003463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009966: libpam-tacplus: CVE-2016-20014
Source: libpam-tacplus Version: 1.3.8-2.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.3.8-2+deb10u1 Control: found -1 1.3.8-2 Hi, The following vulnerability was published for libpam-tacplus. CVE-2016-20014[0]: | In pam_tacplus.c in pam_tacplus before 1.4.1, pam_sm_acct_mgmt does | not zero out the arep data structure. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2016-20014 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-20014 [1] https://github.com/kravietz/pam_tacplus/commit/e4c00eba70a0f72c4de77b5f072c69708ec2beab Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: libpam-tacplus: CVE-2016-20014
Processing control commands: > found -1 1.3.8-2+deb10u1 Bug #1009966 [src:libpam-tacplus] libpam-tacplus: CVE-2016-20014 Marked as found in versions libpam-tacplus/1.3.8-2+deb10u1. > found -1 1.3.8-2 Bug #1009966 [src:libpam-tacplus] libpam-tacplus: CVE-2016-20014 Marked as found in versions libpam-tacplus/1.3.8-2. -- 1009966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1009888 is grave
Processing commands for cont...@bugs.debian.org: > severity 1009888 grave Bug #1009888 [rust-h2] rust-h2, existing version is badly broken, new upstream needs new package Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1009888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009504: marked as done (node-create-hmac: FTBFS: ERROR: Coverage for statements (97.1%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 11:18:54 +
with message-id
and subject line Bug#1009504: fixed in node-create-hmac 1.1.7+~1.1.0-2
has caused the Debian Bug report #1009504,
regarding node-create-hmac: FTBFS: ERROR: Coverage for statements (97.1%) does
not meet global threshold (100%)
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.)
--
1009504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-create-hmac
Version: 1.1.7+~1.1.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/@types/create-hmac -> ../../types-create-hmac
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> ln -s ../. node_modules/create-hmac
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test.js
> TAP version 13
> ok 1 - test.js # time=1077.956ms {
> # hmac(sha1) w/ 486920... as undefined
> ok 1 should be strictly equal
> # hmac(sha1) w/ 486920... as base64
> ok 2 should be strictly equal
> # hmac(sha1) w/ 486920... as hex
> ok 3 should be strictly equal
> # hmac(sha1) w/ 486920... as binary
> ok 4 should be strictly equal
> # hmac(sha1) w/ 776861... as undefined
> ok 5 should be strictly equal
> # hmac(sha1) w/ 776861... as base64
> ok 6 should be strictly equal
> # hmac(sha1) w/ 776861... as hex
> ok 7 should be strictly equal
> # hmac(sha1) w/ 776861... as binary
> ok 8 should be strictly equal
> # hmac(sha1) w/ dd... as undefined
> ok 9 should be strictly equal
> # hmac(sha1) w/ dd... as base64
> ok 10 should be strictly equal
> # hmac(sha1) w/ dd... as hex
> ok 11 should be strictly equal
> # hmac(sha1) w/ dd... as binary
> ok 12 should be strictly equal
> # hmac(sha1) w/ cdcdcd... as undefined
> ok 13 should be strictly equal
> # hmac(sha1) w/ cdcdcd... as base64
> ok 14 should be strictly equal
> # hmac(sha1) w/ cdcdcd... as hex
> ok 15 should be strictly equal
> # hmac(sha1) w/ cdcdcd... as binary
> ok 16 should be strictly equal
> # hmac(sha1) w/ 546573... as undefined
> ok 17 should be strictly equal
> # hmac(sha1) w/ 546573... as base64
> ok 18 should be strictly equal
> # hmac(sha1) w/ 546573... as hex
> ok 19 should be strictly equal
> # hmac(sha1) w/ 546573... as binary
> ok 20 should be strictly equal
> # hmac(sha1) w/ 546869... as undefined
> ok 21 should be strictly equal
> # hmac(sha1) w/ 546869... as base64
> ok 22 should be strictly equal
> # hmac(sha1) w/ 546869... as hex
> ok 23 should be strictly equal
> # hmac(sha1) w/ 546869... as binary
> ok 24 should be strictly equal
> # hmac(sha1) as stream w/ 486920...
> ok 25 should be strictly equal
> # hmac(sha1) as stream w/ 776861...
> ok 26 should be strictly equal
> # hmac(sha1) as stream w/ dd...
> ok 27 should be strictly equal
> # hmac(sha1) as stream w/ cdcdcd...
> ok 28 should be strictly equal
> # hmac(sha1) as stream w/ 546573...
> ok 29 should be strictly equal
> # hmac(sha1) as stream w/ 546869...
> ok 30 should be strictly equal
> # hmac(sha224) w/ 486920... as undefined
> ok 31 should be strictly equal
> # hmac(sha224) w/ 486920... as base64
> ok 32 should be strictly equal
> # hmac(sha224) w/ 486920... as hex
> ok 33 should be strictly equal
> # hmac(sha224) w/ 486920... as binary
> ok 34 should be strictly equal
> # hmac(sha224) w/ 776861... as undefined
> ok 35 should be strictly equal
> # hmac(sha224) w/ 776861... as base64
> ok 36 should be strictly equal
> # hmac(sha224) w/ 776861... as hex
> ok 37 should be strictly equal
> # hmac(sha224) w/ 776861... as binary
> ok 38 should be strictly equal
> # hmac(sha224) w/ dd... as undefined
> ok 39 should be strictly equal
> # hmac(sha224) w/ dd... as base64
> ok 40 should be strictly equal
> # hmac(sha224) w/ dd... as hex
> ok 41 should be strictly equal
> # hmac(sha224) w/ dd... as
Bug#1009531: marked as done (node-browserify: FTBFS: ERROR: Coverage for statements (84.75%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 11:18:48 + with message-id and subject line Bug#1009531: fixed in node-browserify 17.0.0+ds-4 has caused the Debian Bug report #1009531, regarding node-browserify: FTBFS: ERROR: Coverage for statements (84.75%) does not meet global threshold (100%) 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.) -- 1009531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-browserify Version: 17.0.0+ds-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p node_modules > ln -s .. node_modules/browserify > dh_auto_build -i --buildsystem=nodejs > No build command found, searching known files > make[1]: Leaving directory '/<>' >dh_auto_test --buildsystem=nodejs > test -e node_modules > ln -s ../. node_modules/browserify > ln: failed to create symbolic link 'node_modules/browserify/.': File exists > /bin/sh -ex debian/tests/pkg-js/test > + set -ex > + export NODE_PATH=/usr/share/nodejs:/usr/lib/nodejs > + grep -v test/crypto > + + lsgrep -v test/spread.js > + grep -v test/quotes.js > + grep test/args.js test/array.js test/async.js test/backbone.js test/bare.js > test/bare_shebang.js test/bin.js test/bin_entry.js test/bin_tr_error.js > test/bom.js test/browser_field_file.js test/browser_field_resolve.js > test/buffer.js test/bundle-bundle-external.js test/bundle-stream.js > test/bundle.js test/bundle_external.js test/bundle_external_global.js > test/bundle_sourcemap.js test/catch.js test/circular.js test/coffee_bin.js > test/coffeeify.js test/comment.js test/constants.js test/crypto.js > test/crypto_ig.js test/cycle.js test/debug_standalone.js test/dedupe-deps.js > test/dedupe-nomap.js test/delay.js test/dep.js test/dollar.js > test/double_buffer.js test/double_bundle.js test/double_bundle_error.js > test/double_bundle_json.js test/double_bundle_parallel.js > test/double_bundle_parallel_cache.js test/entry.js test/entry_exec.js > test/entry_expose.js test/entry_relative.js test/error_code.js > test/exclude.js test/export.js test/external.js test/external_shim.js > test/externalize.js test/fake.js test/field.js test/file_event.js > test/five_bundle.js test/full_paths.js test/glob.js test/global.js > test/global_coffeeify.js test/global_noparse.js test/global_recorder.js > test/hash.js test/hash_instance_context.js test/identical.js > test/identical_different.js test/ignore.js test/ignore_browser_field.js > test/ignore_missing.js test/ignore_transform_key.js test/json.js test/leak.js > test/maxlisteners.js test/multi_bundle.js test/multi_bundle_unique.js > test/multi_entry.js test/multi_entry_cross_require.js test/multi_require.js > test/multi_symlink.js test/no_builtins.js test/noparse.js test/pack.js > test/paths.js test/paths_transform.js test/pipeline_deps.js test/pkg.js > test/pkg_event.js test/plugin.js test/preserve-symlinks.js test/process.js > test/quotes.js test/relative_dedupe.js test/require_cache.js > test/require_expose.js test/reset.js test/resolve_exposed.js > test/retarget.js+ test/reverse_multi_bundle.js test/shared_symlink.js > test/shebang.js test/spread.js test/standalone.js test/standalone_events.js > test/standalone_sourcemap.js test/stdin.js test/stream.js test/stream_file.js > test/subdep.js test/symlink_dedupe.js test/syntax_cache.js test/tr.js+ > test/tr_args.js test/tr_error.js test/tr_flags.js test/tr_global.js > test/tr_no_entry.js test/tr_once.js test/tr_order.js test/tr_symlink.jsgrep > test/unicode.js -v test/util.js test/coffee_bin.js test/yield.js > > grep -v coffeeify.js > -v+ test/syntax_cache.js > grep -v test/multi_entry.js > + grep -v test/backbone.js > + tap -R spec test/args.js test/array.js test/async.js test/bare.js > test/bare_shebang.js test/bin.js test/bin_entry.js test/bin_tr_error.js > test/bom.js test/browser_field_file.js test/browser_field_resolve.js > test/buffer.js test/bundle-bundle-external.js test/bundle-stream.js > test/bundle.js test/bundle_external.js test/bundle_external_global.js > test/bundle_sourcemap.js test/catch.js test/circular.js test/comment.js > test/constants.js test/cycle.js test/debug_standalone.js test/dedupe-deps.js > test/dedupe-nomap.js test/delay.js test/dep.js test/dollar.js > test/double_buffer.js test/double_bundle.js
Bug#1009420: irssi is marked for autoremoval from testing
tags 1009420 + patch thanks Hi, given the potential autoremoval of irssi we looked into this, irssi upstream suggested the attached patch which I can confirm to fix the build. Cheers, Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los| --- a/tests/regression/client/client.c +++ b/tests/regression/client/client.c @@ -29,6 +29,7 @@ #include #include #include +#include #include #include
Processed: Re: irssi is marked for autoremoval from testing
Processing commands for cont...@bugs.debian.org: > tags 1009420 + patch Bug #1009420 [src:libotr] libotr: FTBFS: client.c:624:30: error: ‘PF_UNIX’ undeclared (first use in this function) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1009504 marked as pending in node-create-hmac
Processing control commands: > tag -1 pending Bug #1009504 [src:node-create-hmac] node-create-hmac: FTBFS: ERROR: Coverage for statements (97.1%) does not meet global threshold (100%) Added tag(s) pending. -- 1009504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009531: marked as pending in node-browserify
Control: tag -1 pending Hello, Bug #1009531 in node-browserify 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/js-team/node-browserify/-/commit/33bbc9db5d2a7457827ac6da7493cedbf0885a46 Fix test for tap >= 15 (--no-cov) Closes: #1009531 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009531
Bug#1009504: marked as pending in node-create-hmac
Control: tag -1 pending Hello, Bug #1009504 in node-create-hmac 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/js-team/node-create-hmac/-/commit/166cd9e2f7a10daf2e21c291fe2ebdd5896413ab Fix test for tap >= 15 (--no-cov) Closes: #1009504 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009504
Processed: Bug#1009531 marked as pending in node-browserify
Processing control commands: > tag -1 pending Bug #1009531 [src:node-browserify] node-browserify: FTBFS: ERROR: Coverage for statements (84.75%) does not meet global threshold (100%) Added tag(s) pending. -- 1009531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009517: marked as done (node-function-bind: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 10:49:01 + with message-id and subject line Bug#1009517: fixed in node-function-bind 1.1.1+repacked+~1.0.3-2 has caused the Debian Bug report #1009517, regarding node-function-bind: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%) 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.) -- 1009517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-function-bind Version: 1.1.1+repacked+~1.0.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with nodejs >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link node_modules/has -> ../has >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > ln -s ../. node_modules/function-bind > cd ./has && sh -ex ../debian/nodejs/has/test > + tap -R spec test > > test/index.js > > ✓ object literal does not have own property "hasOwnProperty" > > ✓ Object.prototype has own property "hasOwnProperty" > > 2 passing (790.317ms) > --|-|--|-|-|--- > File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s > --|-|--|-|-|--- > All files | 100 | 100 | 100 | 100 | > index.js | 100 | 100 | 100 | 100 | > --|-|--|-|-|--- > /bin/sh -ex debian/tests/pkg-js/test > + tap -R spec test/index.js > > test/index.js > > ✓ should be strictly equal > > ✓ throws when given true > > ✓ throws when given false > > ✓ throws when given > > ✓ throws when given [object Object] > > ✓ throws when given 42 > > ✓ throws when given foo > > ✓ throws when given NaN > > ✓ throws when given /a/g > > ✓ should be deeply equivalent > > ✓ should be strictly equal > > ✓ should be deeply equivalent > > ✓ should be strictly equal > > ✓ returned context is namespaced context > > ✓ passed arguments are correct > > ✓ returned context is namespaced context > > ✓ passed arguments are correct > > ✓ should be strictly equal > > ✓ should not be strictly equal > > ✓ result is instance of bound constructor > > ✓ result is instance of original constructor > > ✓ binds a context properly > > ✓ supplies passed arguments > > ✓ binds a context properly > > ✓ supplies bound and passed arguments > > ✓ returned context is bound context > > ✓ returned context is not lexical context > > ✓ passed arguments are correct > > ✓ returned context is bound context > > ✓ returned context is not lexical context > > ✓ passed arguments are correct > > ✓ returns the right arg when called as a constructor > > ✓ should be strictly equal > > ✓ should not be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > 46 passing (820.589ms) > ERROR: Coverage for branches (90%) does not meet global threshold (100%) > ---|-|--|-|-|--- > File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line > #s > ---|-|--|-|-|--- > All files | 100 | 90 | 100 | 100 | > > implementation.js | 100 | 90 | 100 | 100 | 44 > > ---|-|--|-|-|--- > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2022/04/12/node-function-bind_1.1.1+repacked+~1.0.3-1_unstable.log All bugs filed during this archive rebuild are listed at:
Bug#1009543: marked as done (node-callback-stream: FTBFS: ERROR: Coverage for branches (83.33%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 10:33:53 +
with message-id
and subject line Bug#1009543: fixed in node-callback-stream 1.1.0-4
has caused the Debian Bug report #1009543,
regarding node-callback-stream: FTBFS: ERROR: Coverage for branches (83.33%)
does not meet global threshold (100%)
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.)
--
1009543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-callback-stream
Version: 1.1.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/callback-stream
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test.js
> TAP version 13
> (node:537207) DeprecationWarning: deepEqual() is deprecated, use same()
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test.js # time=29.659ms {
> # Subtest: call the callback after end with object mode
> ok 1 - should return the ending value
> 1..1
> ok 1 - call the callback after end with object mode # time=15ms
>
> # Subtest: support multiple writes with object mode
> ok 1 - should return the ending value
> 1..1
> ok 2 - support multiple writes with object mode # time=2.455ms
>
> # Subtest: works without object mode
> ok 1 - should contain only one value
> ok 2 - should return the ending value
> 1..2
> ok 3 - works without object mode # time=1.26ms
>
> # Subtest: is pipeable
> ok 1 - should have the same content of the file
> 1..1
> ok 4 - is pipeable # time=4.084ms
>
> # Subtest: callback.obj shortcut for objectMode
> ok 1 - should return the ending value
> 1..1
> ok 5 - callback.obj shortcut for objectMode # time=1.302ms
>
> 1..5
> # time=29.659ms
> }
>
> 1..1
> # time=716.531ms
> ERROR: Coverage for branches (83.33%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
> --|-|--|-|-|---
> All files | 100 |83.33 | 100 | 100 |
> index.js | 100 |83.33 | 100 | 100 | 41
> --|-|--|-|-|---
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-callback-stream_1.1.0-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-callback-stream
Source-Version: 1.1.0-4
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-callback-stream, 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 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-callback-stream package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please
Bug#1009517: marked as pending in node-function-bind
Control: tag -1 pending Hello, Bug #1009517 in node-function-bind 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/js-team/node-function-bind/-/commit/d7f0b932f78d7e7301f13e98ac7fd31698fd933c Fix test for tap >= 15 (--no-cov) Closes: #1009517 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009517
Processed: Bug#1009517 marked as pending in node-function-bind
Processing control commands: > tag -1 pending Bug #1009517 [src:node-function-bind] node-function-bind: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%) Added tag(s) pending. -- 1009517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1009608 marked as pending in node-fstream
Processing control commands: > tag -1 pending Bug #1009608 [src:node-fstream] node-fstream: FTBFS: ERROR: Coverage for statements (73.3%) does not meet global threshold (100%) Added tag(s) pending. -- 1009608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1009543 marked as pending in node-callback-stream
Processing control commands: > tag -1 pending Bug #1009543 [src:node-callback-stream] node-callback-stream: FTBFS: ERROR: Coverage for branches (83.33%) does not meet global threshold (100%) Added tag(s) pending. -- 1009543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009608: marked as pending in node-fstream
Control: tag -1 pending Hello, Bug #1009608 in node-fstream 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/js-team/node-fstream/-/commit/d105b07e45f3a2f45b8afd6a20ff3212642d9a0a Fix test for tap >= 15 (--no-cov) Closes: #1009608 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009608
Bug#1009543: marked as pending in node-callback-stream
Control: tag -1 pending Hello, Bug #1009543 in node-callback-stream 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/js-team/node-callback-stream/-/commit/da22073bb1656e634752977a61ffdc2cb405049d Fix test for tap >= 15 (--no-cov) Closes: #1009543 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009543
Bug#1008465: #1008465 (python-fabio FTBFS): works for me
Hi, I was trying to reproduce bug #1008465 to see if I could fix it, but an up-to-date pbuilder and an up-to-date git clone build fine. Maybe something changed in the dependencies? I suggest closing this bug, because python-fabio is marked for autoremoval from testing and several packages will be removed as a consequence. Roland.
Bug#1009542: marked as done (node-libravatar: FTBFS: ERROR: Coverage for statements (80.19%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 09:18:52 +
with message-id
and subject line Bug#1009542: fixed in node-libravatar 3.0.0-3
has caused the Debian Bug report #1009542,
regarding node-libravatar: FTBFS: ERROR: Coverage for statements (80.19%) does
not meet global threshold (100%)
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.)
--
1009542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-libravatar
Version: 3.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/libravatar
> /bin/sh -ex debian/tests/pkg-js/test
> + tap tests/federation.js tests/url.js
> TAP version 13
> ok 1 - tests/federation.js # time=26.174ms {
> # Subtest: sanitization of invalid SRV responses
> ok 1 - both parameters missing
> ok 2 - first parameter missing
> ok 3 - second parameter missing
> ok 4 - port too small
> ok 5 - port too big
> ok 6 - invalid hostname
> ok 7 - invalid port
> 1..7
> ok 1 - sanitization of invalid SRV responses # time=5.915ms
>
> # Subtest: sanitization of valid SRV responses
> ok 1 - normal http
> ok 2 - normal https
> ok 3 - weird http
> ok 4 - weird https
> 1..4
> ok 2 - sanitization of valid SRV responses # time=1.491ms
>
> # Subtest: ordering of invalid SRV hostnames
> ok 1 - empty array [0]
> ok 2 - empty array [1]
> ok 3 - single empty array [0]
> ok 4 - single empty array [1]
> 1..4
> ok 3 - ordering of invalid SRV hostnames # time=1.166ms
>
> # Subtest: ordering of valid SRV hostnames on priority
> ok 1 - single hostname [0]
> ok 2 - single hostname [1]
> ok 3 - two hostnames [0]
> ok 4 - two hostnames [1]
> ok 5 - four hostnames [0]
> ok 6 - four hostnames [1]
> 1..6
> ok 4 - ordering of valid SRV hostnames on priority # time=1.42ms
>
> # Subtest: ordering of valid SRV hostnames on weight
> ok 1 - random 1 [0]
> ok 2 - random 1 [1]
> ok 3 - random 2 [0]
> ok 4 - random 2 [1]
> ok 5 - random 3 [0]
> ok 6 - random 3 [1]
> ok 7 - random 4 [0]
> ok 8 - random 4 [1]
> ok 9 - random 5 [0]
> ok 10 - random 5 [1]
> 1..10
> ok 5 - ordering of valid SRV hostnames on weight # time=1.848ms
>
> # Subtest: ordering of valid SRV hostnames on weight
> ok 1 - degenerate case
> ok 2 - simple domain over http
> ok 3 - simple domain over https
> ok 4 - longer domain over http
> 1..4
> ok 6 - ordering of valid SRV hostnames on weight # time=0.9ms
>
> 1..6
> # time=26.174ms
> }
>
> ok 2 - tests/url.js # time=24.161ms {
> # Subtest: parsing of user identity
> ok 1 - both parameters missing [0]
> ok 2 - both parameters missing [1]
> ok 3 - both parameters supplied [0]
> ok 4 - both parameters supplied [1]
> ok 5 - standard email [0]
> ok 6 - standard email [1]
> ok 7 - standard openid [0]
> ok 8 - standard openid [1]
> 1..8
> ok 1 - parsing of user identity # time=7.286ms
>
> # Subtest: parsing of email address
> ok 1 - empty email [0]
> ok 2 - empty email [1]
> ok 3 - missing hostname [0]
> ok 4 - missing hostname [1]
> ok 5 - uppercase username [0]
> ok 6 - uppercase username [1]
> ok 7 - mixed-case username and hostname [0]
> ok 8 - mixed-case username and hostname [1]
> ok 9 - untrimmed email [0]
> ok 10 - untrimmed email [1]
> 1..10
> ok 2 - parsing of email address # time=1.905ms
>
> # Subtest: parsing of openid urls
> ok 1 - empty openid [0]
> ok 2 - empty openid [1]
> ok 3 - invalid url [0]
> ok 4 - invalid url [1]
> ok 5 - mixed-case hostname [0]
> ok 6 - mixed-case
Bug#1009526: marked as done (node-buffer: FTBFS: ERROR: Coverage for statements (60.25%) does not meet global threshold (100%))
Your message dated Thu, 21 Apr 2022 09:18:47 + with message-id and subject line Bug#1009526: fixed in node-buffer 6.0.3-3 has caused the Debian Bug report #1009526, regarding node-buffer: FTBFS: ERROR: Coverage for statements (60.25%) does not meet global threshold (100%) 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.) -- 1009526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-buffer Version: 6.0.3-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/buffer > /bin/sh -ex debian/tests/pkg-js/test > + tap -R spec test/base64.js test/basic.js test/compare.js > test/constructor.js test/from-string.js test/is-buffer.js test/methods.js > test/slice.js test/static.js test/to-string.js test/write.js > test/write_infinity.js > > test/base64.js > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be deeply equivalent > test/basic.js > > ✓ should be truthy > > ✓ should be truthy > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > test/compare.js > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should throw > > ✓ should throw > > ✓ should throw > > ✓ should be truthy > > ✓ should be truthy > > ✓ should be truthy > > ✓ should throw > test/constructor.js > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly equal > > ✓ should be strictly
Processed: Bug#1009542 marked as pending in node-libravatar
Processing control commands: > tag -1 pending Bug #1009542 [src:node-libravatar] node-libravatar: FTBFS: ERROR: Coverage for statements (80.19%) does not meet global threshold (100%) Added tag(s) pending. -- 1009542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009542: marked as pending in node-libravatar
Control: tag -1 pending Hello, Bug #1009542 in node-libravatar 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/js-team/node-libravatar/-/commit/ba83e753e65cbbb8b62eb95de784e175ee017ead Fix test for tap >= 15 (--no-cov) Closes: #1009542 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009542
Processed: Bug#1009526 marked as pending in node-buffer
Processing control commands: > tag -1 pending Bug #1009526 [src:node-buffer] node-buffer: FTBFS: ERROR: Coverage for statements (60.25%) does not meet global threshold (100%) Added tag(s) pending. -- 1009526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009526: marked as pending in node-buffer
Control: tag -1 pending Hello, Bug #1009526 in node-buffer 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/js-team/node-buffer/-/commit/f81e31cbce88cf6671354075d4d8b50de78f0b55 Fix test for tap >= 15 (--no-cov) Closes: #1009526 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009526
Bug#1009962: src:python-pytest-asyncio: fails to migrate to testing for too long: causes autopkgtest regression
Source: python-pytest-asyncio Version: 0.16.0-1 Severity: serious Control: close -1 0.18.2-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1006736 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:python-pytest-asyncio has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The cause of the migration failure has been reported in bug #1006736. 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 bookworm, 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=python-pytest-asyncio OpenPGP_signature Description: OpenPGP digital signature
Processed: src:python-pytest-asyncio: fails to migrate to testing for too long: causes autopkgtest regression
Processing control commands:
> close -1 0.18.2-1
Bug #1009962 [src:python-pytest-asyncio] src:python-pytest-asyncio: fails to
migrate to testing for too long: causes autopkgtest regression
Marked as fixed in versions python-pytest-asyncio/0.18.2-1.
Bug #1009962 [src:python-pytest-asyncio] src:python-pytest-asyncio: fails to
migrate to testing for too long: causes autopkgtest regression
Marked Bug as done
> block -1 by 1006736
Bug #1009962 {Done: Paul Gevers }
[src:python-pytest-asyncio] src:python-pytest-asyncio: fails to migrate to
testing for too long: causes autopkgtest regression
1009962 was not blocked by any bugs.
1009962 was not blocking any bugs.
Added blocking bug(s) of 1009962: 1006736
--
1009962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug #1005500: doctest breaks argh build: doctest.h:1398:92: error: use of deleted function
Processing control commands: > affects 1005500 src:fenics-basix src:fenics-dolfinx Bug #1005500 [src:doctest] doctest breaks argh build: doctest.h:1398:92: error: use of deleted function ‘doctest::detail::Expression_lhs >::Expression_lhs(doctest::detail::Expression_lhs >&&)’ Added indication that 1005500 affects src:fenics-basix and src:fenics-dolfinx -- 1005500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
