Processed: src:libnetconf2: fails to migrate to testing for too long: (Build-)Depends on new package that's not migrating
Processing control commands: > close -1 2.0.24-3 Bug #1003759 [src:libnetconf2] src:libnetconf2: fails to migrate to testing for too long: (Build-)Depends on new package that's not migrating Marked as fixed in versions libnetconf2/2.0.24-3. Bug #1003759 [src:libnetconf2] src:libnetconf2: fails to migrate to testing for too long: (Build-)Depends on new package that's not migrating Marked Bug as done -- 1003759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003759: src:libnetconf2: fails to migrate to testing for too long: (Build-)Depends on new package that's not migrating
Source: libnetconf2 Version: 1.1.16-1.1 Severity: serious Control: close -1 2.0.24-3 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync 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:libnetconf2 has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and 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=libnetconf2 OpenPGP_signature Description: OpenPGP digital signature
Processed: src:fastjet: fails to migrate to testing for too long: unresolved RC bug
Processing control commands:
> close -1 3.4.0-1
Bug #1003758 [src:fastjet] src:fastjet: fails to migrate to testing for too
long: unresolved RC bug
Marked as fixed in versions fastjet/3.4.0-1.
Bug #1003758 [src:fastjet] src:fastjet: fails to migrate to testing for too
long: unresolved RC bug
Marked Bug as done
> block -1 by 999761
Bug #1003758 {Done: Paul Gevers } [src:fastjet] src:fastjet:
fails to migrate to testing for too long: unresolved RC bug
1003758 was not blocked by any bugs.
1003758 was not blocking any bugs.
Added blocking bug(s) of 1003758: 999761
--
1003758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1003758: src:fastjet: fails to migrate to testing for too long: unresolved RC bug
Source: fastjet Version: 3.0.6+dfsg-3 Severity: serious Control: close -1 3.4.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 999761 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:fastjet has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and 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=fastjet OpenPGP_signature Description: OpenPGP digital signature
Bug#1002140: marked as done (freetds: FTBFS: configure.ac:115: error: possibly undefined macro: AC_LTDL_DLLIB)
Your message dated Sat, 15 Jan 2022 06:48:46 + with message-id and subject line Bug#1002140: fixed in freetds 1.3.6-1 has caused the Debian Bug report #1002140, regarding freetds: FTBFS: configure.ac:115: error: possibly undefined macro: AC_LTDL_DLLIB 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.) -- 1002140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freetds Version: 1.2.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --parallel >dh_update_autotools_config >dh_autoreconf > libtoolize: putting auxiliary files in '.'. > libtoolize: copying file './ltmain.sh' > libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. > libtoolize: copying file 'm4/libtool.m4' > libtoolize: copying file 'm4/ltoptions.m4' > libtoolize: copying file 'm4/ltsugar.m4' > libtoolize: copying file 'm4/ltversion.m4' > libtoolize: copying file 'm4/lt~obsolete.m4' > configure.ac:97: warning: The macro `AC_GNU_SOURCE' is obsolete. > configure.ac:97: You should run autoupdate. > ./lib/autoconf/specific.m4:312: AC_GNU_SOURCE is expanded from... > configure.ac:97: the top level > configure.ac:116: warning: The macro `LT_AC_PROG_RC' is obsolete. > configure.ac:116: You should run autoupdate. > m4/libtool.m4:8175: LT_AC_PROG_RC is expanded from... > configure.ac:116: the top level > configure.ac:273: warning: The macro `AC_LANG_C' is obsolete. > configure.ac:273: You should run autoupdate. > ./lib/autoconf/c.m4:72: AC_LANG_C is expanded from... > m4/acx_pthread.m4:49: ACX_PTHREAD is expanded from... > configure.ac:273: the top level > configure.ac:273: warning: The macro `AC_TRY_LINK' is obsolete. > configure.ac:273: You should run autoupdate. > ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from... > m4/acx_pthread.m4:49: ACX_PTHREAD is expanded from... > configure.ac:273: the top level > configure.ac:296: warning: The macro `AC_HEADER_STDC' is obsolete. > configure.ac:296: You should run autoupdate. > ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from... > configure.ac:296: the top level > configure.ac:297: warning: The macro `AC_HEADER_TIME' is obsolete. > configure.ac:297: You should run autoupdate. > ./lib/autoconf/headers.m4:743: AC_HEADER_TIME is expanded from... > configure.ac:297: the top level > configure.ac:429: warning: The macro `AC_TRY_LINK' is obsolete. > configure.ac:429: You should run autoupdate. > ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from... > configure.ac:429: the top level > configure.ac:503: warning: The macro `AC_TRY_LINK' is obsolete. > configure.ac:503: You should run autoupdate. > ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from... > configure.ac:503: the top level > configure.ac:523: warning: The macro `AC_TRY_COMPILE' is obsolete. > configure.ac:523: You should run autoupdate. > ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from... > m4/gettimemilli.m4:28: TDS_CLOCK_GETTIME_CONST is expanded from... > m4/gettimemilli.m4:53: TDS_GETTIMEMILLI is expanded from... > configure.ac:523: the top level > configure.ac:721: warning: The macro `AC_TRY_COMPILE' is obsolete. > configure.ac:721: You should run autoupdate. > ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from... > configure.ac:721: the top level > configure.ac:735: warning: The macro `AC_TRY_COMPILE' is obsolete. > configure.ac:735: You should run autoupdate. > ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from... > configure.ac:735: the top level > configure.ac:715: warning: The macro `AC_TRY_COMPILE' is obsolete. > configure.ac:715: You should run autoupdate. > ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from... > configure.ac:715: the top level > configure.ac:789: warning: The macro `AC_TRY_LINK' is obsolete. > configure.ac:789: You should run autoupdate. > ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from... > configure.ac:772: TDS_CHECK_GMP is expanded from... > configure.ac:779: TDS_HAVE_GMP is expanded from... > aclocal.m4:2417: PKG_CHECK_MODULES is expanded from... > configure.ac:789: the top level > configure.ac:789: warning: The macro `AC_TRY_LINK' is obsolete. > configure.ac:789: You should run autoupdate. > ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from... > configure.ac:772: TDS_CHECK_GMP is
Bug#1001545: [Pkg-opencl-devel] Bug#1001545: pyopencl, build-depends on package that is no longer in testing
On Wed, 12 Jan 2022 19:33:11 + "Rebecca N. Palmer" wrote: Probably just Build-Depends: pocl-opencl-icd [amd64 arm64 armel armhf i386 hurd-i386] and skip the tests on the other architectures. (Linking uses libopencl1, not *-opencl-icd.) As a slightly unrelated note, if that Build-Depends is only used during testing, than please also mark it with the build profile to document that fact. That makes reasoning about these kind of things easier for non-experts. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1003704: bugs.debian.org: error compiling kernel 5.16
Control: severity -1 important Control: reassign -1 binutils Control: found -1 binutils/2.35.2-2 Control: tag -1 moreinfo On Thu, 13 Jan 2022, gdaniel1358 wrote: > Package: bugs.debian.org > Severity: grave > Justification: can not compile kernel 5.16 > X-Debbugs-Cc: gdaniel1...@hotmail.com > > Dear Maintainer, > > Hi, tried to compile kernel 5.16.0 from kernel.org. > At linking point I get: > > CHK include/generated/compile.h > LD vmlinux.o > MODPOST vmlinux.symvers > MODINFO modules.builtin.modinfo > GEN modules.builtin > LD .tmp_vmlinux.btf > ld: BFD (GNU Binutils for Debian) 2.35.2 internal error, aborting at > ../../bfd/merge.c:939 in _bfd_merged_section_offset > > ld: Please report this bug. This looks like a bug in ld (part of binutils), not a bug in bugs.debian.org. I'm guessing that this is binutils 2.35.2-2. Please confirm the version and the architecture that you are seeing this bug in. -- Don Armstrong https://www.donarmstrong.com The whole modern world has divided itself into Conservatives and Progressives. The business of Progressives is to go on making mistakes. The business of the Conservatives is to prevent the mistakes from being corrected. -- G. K. Chesterton "Illustrated London News (1924-04-19)"
Bug#1003756: squeekboard, build-depends unsatisfiable
Package: squeekboard
Version: 1.14.0-3
Severity: serious
x-debbugs-cc: deb...@nilux.be
squeekboard's build-dependencies are unsatisfiable in unstable due to the
new version of the rust gtk stack. I tried relaxing the depenencies
(on both the Debian side and cargo side), but it failed with the following
error[E0432]: unresolved import `gtk::WidgetExt`
--> /remap-pwd/src/drawing.rs:13:5
|
13 | use gtk::WidgetExt;
| ^-
| ||
| |help: a similar name exists in the module: `Widget`
| no `WidgetExt` in the root
error[E0432]: unresolved import `gio::ActionMapExt`
--> /remap-pwd/src/popover.rs:16:5
|
16 | use gio::ActionMapExt;
| ^
| ||
| |help: a similar name exists in the module: `ActionMap`
| no `ActionMapExt` in the root
error[E0432]: unresolved import `gio::SettingsExt`
--> /remap-pwd/src/popover.rs:17:5
|
17 | use gio::SettingsExt;
| ^---
| ||
| |help: a similar name exists in the module: `Settings`
| no `SettingsExt` in the root
error[E0432]: unresolved import `gtk::BuilderExtManual`
--> /remap-pwd/src/popover.rs:23:5
|
23 | use gtk::BuilderExtManual;
| ^ no `BuilderExtManual` in the root
error[E0432]: unresolved import `gtk::PopoverExt`
--> /remap-pwd/src/popover.rs:24:5
|
24 | use gtk::PopoverExt;
| ^--
| ||
| |help: a similar name exists in the module: `Popover`
| no `PopoverExt` in the root
error[E0432]: unresolved import `gtk::WidgetExt`
It seems to me that the new version of the rust gtk stack has changed the
API quite substantially. I haven't looked deeper into porting this myself
Debdiff adjusting the dependencies is attatched.
diff -Nru squeekboard-1.14.0/debian/changelog
squeekboard-1.14.0/debian/changelog
--- squeekboard-1.14.0/debian/changelog 2021-11-16 18:41:52.0 +
+++ squeekboard-1.14.0/debian/changelog 2022-01-15 05:09:34.0 +
@@ -1,3 +1,12 @@
+squeekboard (1.14.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop dependencies on obsolete cargo features in rust gtk stack.
+ * Use -f in rm command in clean target so it doesn't fail if the file
+is already gone.
+
+ -- Peter Michael Green Sat, 15 Jan 2022 05:09:34 +
+
squeekboard (1.14.0-3) unstable; urgency=medium
* Team upload.
diff -Nru squeekboard-1.14.0/debian/patches/relax-dep.patch
squeekboard-1.14.0/debian/patches/relax-dep.patch
--- squeekboard-1.14.0/debian/patches/relax-dep.patch 1970-01-01
00:00:00.0 +
+++ squeekboard-1.14.0/debian/patches/relax-dep.patch 2022-01-15
05:09:34.0 +
@@ -0,0 +1,53 @@
+Description: relax cargo dependencies
+Author: Peter Michael Green
+
+Index: squeekboard-1.14.0/Cargo.deps
+===
+--- squeekboard-1.14.0.orig/Cargo.deps
squeekboard-1.14.0/Cargo.deps
+@@ -1,22 +1,19 @@
+ # Dependencies which change based on build flags
+-bitflags = "1.2.*"
++bitflags = "^1.2"
+ clap = { version = "2.33.*", default-features = false }
+-regex = { version = "1.3.*", default-features = false, features = ["std",
"unicode-case"] }
++regex = { version = "^1.3", default-features = false, features = ["std",
"unicode-case"] }
+
+ [dependencies.cairo-rs]
+-version = "0.7.*"
++version = "0.14.*"
+
+ [dependencies.gdk]
+-version = "0.11.*"
++version = "0.14.*"
+
+ [dependencies.gio]
+-version = "0.7.*"
+-features = ["v2_44"]
++version = "0.14.*"
+
+ [dependencies.glib]
+-version = "0.8.*"
+-features = ["v2_44"]
++version = "0.14.*"
+
+ [dependencies.gtk]
+-version = "0.7.*"
+-features = ["v3_22"]
++version = "0.14.*"
+Index: squeekboard-1.14.0/Cargo.toml.in
+===
+--- squeekboard-1.14.0.orig/Cargo.toml.in
squeekboard-1.14.0/Cargo.toml.in
+@@ -27,11 +27,9 @@ version = "*"
+
+ [dependencies.glib-sys]
+ version = "*"
+-features = ["v2_44"]
+
+ [dependencies.gtk-sys]
+ version = "*"
+-features = ["v3_22"]
+
+ [dependencies]
+ maplit = "1.0.*"
diff -Nru squeekboard-1.14.0/debian/patches/series
squeekboard-1.14.0/debian/patches/series
--- squeekboard-1.14.0/debian/patches/series2021-11-16 17:09:40.0
+
+++ squeekboard-1.14.0/debian/patches/series2022-01-15 05:09:34.0
+
@@ -1,2 +1,3 @@
fix_cargo_error.patch
fix_meson_ftbfs.patch
+relax-dep.patch
diff -Nru squeekboard-1.14.0/debian/rules squeekboard-1.14.0/debian/rules
--- squeekboard-1.14.0/debian/rules 2021-11-16 16:18:30.0 +
+++ squeekboard-1.14.0/debian/rules 2022-01-15 05:09:25.0 +
@@ -24,7 +24,7 @@
# The Debian version of linked-hash-map doesn't provide any hash,
# causing Cargo to refuse to build with a crates.io copy
build-arch:
- rm Cargo.lock
+ rm -f Cargo.lock
dh $@ --builddirectory=_build
Bug#1003755: mailutils: mail(1) completely broken, fails with "undefined symbol: mu_stream_timed_getdelim" on start
Package: mailutils
Version: 1:3.14-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I upgraded today;
the changelog in my root mail (heh) shows just 1:3.14-1,
so this is broken vs. previous (1:3.13-1).
When running mail(1), at all, it doesn't:
-- >8 --
$ mail
mail: symbol lookup error: mail: undefined symbol: mu_stream_timed_getdelim
$ date | mail -s test
mail: symbol lookup error: mail: undefined symbol: mu_stream_timed_getdelim
-- >8 --
Kind of a big deal, I think :/
There's usable parts (decoodemail(1)), hence grave.
Nevertheless, well, it's mail(1). Kinda important or whatever.
strace, ldd, readelf -d, readelf -s outputs below.
Alas,
наб
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: amd64, i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 mailutils depends on:
ii libc6 2.33-2
ii libcrypt1 1:4.4.27-1
ii libfribidi0 1.0.8-2
ii libgnutls30 3.7.2-5
ii libgsasl7 1.10.0-5+b1
ii libldap-2.4-2 2.4.59+dfsg-1
ii libmailutils8 1:3.13-1
ii libncurses6 6.3-1
ii libpam0g 1.4.0-11
ii libreadline8 8.1.2-1
ii libtinfo6 6.3-1
ii libunistring2 0.9.10-6
ii mailutils-common 1:3.14-1
Versions of packages mailutils recommends:
ii nullmailer [mail-transport-agent] 1:2.2-3
Versions of packages mailutils suggests:
pn mailutils-doc
pn mailutils-mh
-- no debconf information
execve("/bin/mail", ["mail"], 0xff940354 /* 24 vars */) = 0
brk(NULL) = 0x58084000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf7f23000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=30367, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 30367, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf7f1b000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnux32/libmuaux.so.8", O_RDONLY|O_CLOEXEC)
= 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0 9\0\0004\0\0\0"...,
512) = 512
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=75572, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 79332, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xf7f07000
mprotect(0xf7f0a000, 61440, PROT_NONE) = 0
mmap(0xf7f0a000, 45056, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0xf7f0a000
mmap(0xf7f15000, 12288, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0xe000) = 0xf7f15000
mmap(0xf7f19000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x11000) = 0xf7f19000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnux32/libunistring.so.2",
O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300\320\0\0004\0\0\0"..., 512)
= 512
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=1549716, ...}, AT_EMPTY_PATH)
= 0
mmap(NULL, 1553604, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xf7d8b000
mmap(0xf7d97000, 217088, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc000) = 0xf7d97000
mmap(0xf7dcc000, 1273856, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x41000) = 0xf7dcc000
mmap(0xf7f03000, 16384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x177000) = 0xf7f03000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnux32/libmu_mbox.so.8",
O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320(\0\0004\0\0\0"...,
512) = 512
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=54820, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 57508, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xf7d7c000
mmap(0xf7d7e000, 32768, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0xf7d7e000
mmap(0xf7d86000, 8192, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0xa000) = 0xf7d86000
mmap(0xf7d88000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xb000) = 0xf7d88000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnux32/libmu_mh.so.8", O_RDONLY|O_CLOEXEC)
= 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360\23\0\0004\0\0\0"..., 512) =
512
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=17896, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 20592, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xf7d76000
mmap(0xf7d77000, 8192, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0xf7d77000
mmap(0xf7d79000, 4096, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x3000) =
Bug#1003684: marked as done (double-conversion: autopkgtest regression on i386: ./run_tests: terminated by signal 6)
Your message dated Sat, 15 Jan 2022 03:03:36 + with message-id and subject line Bug#1003684: fixed in double-conversion 3.1.7-4 has caused the Debian Bug report #1003684, regarding double-conversion: autopkgtest regression on i386: ./run_tests: terminated by signal 6 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.) -- 1003684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: double-conversion Version: 3.1.7-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of double-conversion the autopkgtest of double-conversion fails in testing when that autopkgtest is run with the binary packages of double-conversion from unstable on i386. It passes when run with only packages from testing. In tabular form: passfail double-conversion from testing3.1.7-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=double-conversion https://ci.debian.net/data/autopkgtest/testing/i386/d/double-conversion/1826/log.gz CXX test/cctest/test-fixed-dtoa.cc CXX test/cctest/test-conversions.cc CXX test/cctest/test-diy-fp.cc CXX test/cctest/cctest.cc CXX test/cctest/gay-shortest-single.cc CXX test/cctest/gay-precision.cc CXX test/cctest/gay-shortest.cc CXX test/cctest/test-ieee.cc CXX test/cctest/test-fast-dtoa.cc CXX test/cctest/gay-fixed.cc CXX test/cctest/test-strtod.cc CXX test/cctest/test-bignum.cc CXX test/cctest/test-dtoa.cc CXX test/cctest/test-bignum-dtoa.cc LD run_tests xargs: ./run_tests: terminated by signal 6 autopkgtest [11:10:53]: test unittest.sh OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: double-conversion Source-Version: 3.1.7-4 Done: Mo Zhou We believe that the bug you reported is fixed in the latest version of double-conversion, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated double-conversion package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Jan 2022 21:49:29 -0500 Source: double-conversion Architecture: source Version: 3.1.7-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Mo Zhou Closes: 1003684 Changes: double-conversion (3.1.7-4) unstable; urgency=medium . * Use the correct CXXFLAGS for autopkgtest. (Closes: #1003684) Checksums-Sha1: e28d68a1032aae098ba4e849cb6bbdbe1e3e 2212 double-conversion_3.1.7-4.dsc 01f46525c1d4e97322751a8cf458f681ee538a84 8940 double-conversion_3.1.7-4.debian.tar.xz 22de617a59424fd42d7d66ae5bebdd986a5d2fc4 5655 double-conversion_3.1.7-4_source.buildinfo Checksums-Sha256: 8247fe981e8494422e7b43973f2da083d728c3c3979bd35d0bc0fa7382c62af8 2212 double-conversion_3.1.7-4.dsc 7cd8218794dba7ee62b413284c8b90ef15b9bd30e4464835c18fdc5dfabc973e 8940 double-conversion_3.1.7-4.debian.tar.xz 710fe1ae9b27f32cbe58e6db5f4b31e6697af2f5c3fb4625c15eac9563619101 5655 double-conversion_3.1.7-4_source.buildinfo Files: f35b4cdfb0201ea761a356afd5f82859 2212 libs optional double-conversion_3.1.7-4.dsc aa017d55e67e4df42228a5d80dc7c981 8940 libs optional double-conversion_3.1.7-4.debian.tar.xz bd40b4da61f02713c0ffc182555ef095 5655 libs optional double-conversion_3.1.7-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmHiNlYRHGx1bWluQGRl Ymlhbi5vcmcACgkQYmRes19oaopsahAAkEIUV3i0gFRBKTUXeHFvf0c4uEv/pAZ9 9w8+hJdSPTSBwWbIlHTAedLR1tK7fHMvQFgOhxeM3FNxgAa8iR++daeIblgD8B9k 5+0+09x4Ge4ek2nvCFxWVUy6AYKtHDYxQAXo4EfEj28K0iAZ48U/4nJBfkxRa5Do
Processed: Bug#1003003 marked as pending in libqalculate
Processing control commands: > tag -1 pending Bug #1003003 [src:libqalculate] libqalculate FTBFS on architectures where char is unsigned Added tag(s) pending. -- 1003003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 984027 in 1.3-2
Processing commands for cont...@bugs.debian.org:
> found 984027 1.3-2
Bug #984027 {Done: Adrian Bunk } [src:darkice] darkice: ftbfs
with GCC-11
Marked as found in versions darkice/1.3-2 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#670860: spell: diff for NMU version 1.0-24.2
Control: tags 670860 + pending
Dear maintainer,
I've prepared an NMU for spell (versioned as 1.0-24.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
diff -Nru spell-1.0/debian/changelog spell-1.0/debian/changelog
--- spell-1.0/debian/changelog 2022-01-15 03:00:29.0 +0100
+++ spell-1.0/debian/changelog 2022-01-15 02:58:06.0 +0100
@@ -1,3 +1,13 @@
+spell (1.0-24.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "[PATCH] spell: Helping to update to packaging format 3.0":
+Convert to source format 3.0 from 1.0+dpatch.
+Based on a patch by Jari Aalto from 2012.
+(Closes: #670860)
+
+ -- gregor herrmann Sat, 15 Jan 2022 02:58:06 +0100
+
spell (1.0-24.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru spell-1.0/debian/control spell-1.0/debian/control
--- spell-1.0/debian/control 2022-01-15 03:00:29.0 +0100
+++ spell-1.0/debian/control 2022-01-15 02:47:33.0 +0100
@@ -2,7 +2,7 @@
Section: text
Priority: optional
Maintainer: Giacomo Catenazzi
-Build-Depends: debhelper (>= 7), dpatch, texinfo
+Build-Depends: debhelper (>= 7), texinfo
Standards-Version: 3.8.2
Homepage: http://directory.fsf.org/project/spell/
diff -Nru spell-1.0/debian/patches/00list spell-1.0/debian/patches/00list
--- spell-1.0/debian/patches/00list 2022-01-15 03:00:29.0 +0100
+++ spell-1.0/debian/patches/00list 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-01-conglomeration.dpatch
diff -Nru spell-1.0/debian/patches/01-conglomeration.dpatch spell-1.0/debian/patches/01-conglomeration.dpatch
--- spell-1.0/debian/patches/01-conglomeration.dpatch 2022-01-15 03:00:29.0 +0100
+++ spell-1.0/debian/patches/01-conglomeration.dpatch 1970-01-01 01:00:00.0 +0100
@@ -1,599 +0,0 @@
-#!/bin/sh /usr/share/dpatch/dpatch-run
-## 01-conglomeration.dpatch
-##
-## DP: Needs to be broken out (FIXME).
-
-@DPATCH@
-
-diff -Naur spell-1.0.orig/spell.c spell-1.0/spell.c
spell-1.0.orig/spell.c 1996-04-10 04:41:09.0 +
-+++ spell-1.0/spell.c 2006-09-08 18:49:47.0 +
-@@ -71,17 +71,17 @@
- struct pipe
- {
- /* File descriptors used by the parent process. */
--int pin; /* Input channel. */
--int pout; /* Output channel. */
--int perr; /* Error channel (for reading). */
-+int pin;/* Input channel. */
-+int pout; /* Output channel. */
-+int perr; /* Error channel (for reading). */
-
- /* File descriptors used by the child process. */
--int cin; /* Input channel. */
--int cout; /* Output channel. */
--int cerr; /* Error channel (for writing). */
-+int cin;/* Input channel. */
-+int cout; /* Output channel. */
-+int cerr; /* Error channel (for writing). */
-
--fd_set error_set; /* Descriptor set used to check for
-- errors (contains perr). */
-+fd_set error_set; /* Descriptor set used to check for
-+ errors (contains perr). */
- };
- typedef struct pipe pipe_t;
-
-@@ -116,6 +116,7 @@
- {"ispell", required_argument, NULL, 'i'},
- {"ispell-version", no_argument, NULL, 'I'},
- {"number", no_argument, NULL, 'n'},
-+ {"ispell-dictionary", required_argument, NULL, 'D'},
- {"print-file-name", no_argument, NULL, 'o'},
- {"print-stems", no_argument, NULL, 'x'},
- {"stop-list", required_argument, NULL, 's'},
-@@ -130,9 +131,12 @@
- /* Ispell's location. */
- char *ispell_prog = NULL;
-
--/* Dictionary to use. Just use the default if NULL. */
-+/* Personal dictionary to use. Just use the default if NULL. */
- char *dictionary = NULL;
-
-+/* Ispell dictionary to use via ispell's -d argument */
-+char *idict = NULL;
-+
- /* Display Ispell's version (--ispell-version, -I). */
- int show_ispell_version = 0;
-
-@@ -159,69 +163,75 @@
- int
- main (int argc, char **argv)
- {
-- char opt = 0; /* Current option. */
-- int opt_error = 0; /* Whether an option error occurred. */
-- int show_help = 0; /* Display help (--help, -h). */
-- int show_version = 0; /* Display the version (--version, -V). */
-- pid_t pid = 0; /* Child's pid. */
-- pipe_t ispell_pipe; /* The descriptors for our pipe. */
-+ int opt = 0; /* Current option. */
-+ int opt_error = 0;/* Whether an option error occurred. */
-+ int show_help = 0;/* Display help (--help, -h). */
-+ int show_version = 0; /* Display the version (--version, -V). */
-+ pid_t pid = 0;/* Child's pid. */
-+ pipe_t ispell_pipe; /* The
Processed: spell: diff for NMU version 1.0-24.2
Processing control commands: > tags 670860 + pending Bug #670860 [spell] [PATCH] spell: Helping to update to packaging format 3.0 Added tag(s) pending. -- 670860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997346: routes: FTBFS: SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 1-2: truncated \uXXXX escape
Dear Maintainer,
Please find attached a trivial patch to fix this issue.
Kind Regards--- a/docs/conf.py
+++ b/docs/conf.py
@@ -159,7 +159,7 @@
#latex_use_parts = False
# Additional stuff for the LaTeX preamble.
-latex_preamble = '''
+latex_preamble = r'''
\usepackage{palatino}
\definecolor{TitleColor}{rgb}{0.7,0,0}
\definecolor{InnerLinkColor}{rgb}{0.7,0,0}
Processed: php-horde-ldap: (autopkgtest) needs update for php8.1: internal LDAP link is invalid
Processing control commands: > affects -1 src:php-defaults Bug #1003747 [src:php-horde-ldap] php-horde-ldap: (autopkgtest) needs update for php8.1: internal LDAP link is invalid Added indication that 1003747 affects src:php-defaults > block 976811 by -1 Bug #976811 [release.debian.org] transition: php8.1 976811 was blocked by: 1000619 1002504 1002242 977385 1003746 980567 977401 1000593 1000571 1002215 977186 977389 977403 1002020 1000574 1000647 1000653 1000263 977378 1002218 977337 1000654 1003472 1003744 977377 977658 990322 1002232 1000655 1000596 1003479 977404 1003432 977384 977379 1003473 1000650 978457 977396 1003007 1000642 977687 978151 977400 977376 977388 1000474 977340 1000568 1000637 976811 was blocking: 1000585 1002681 977373 Added blocking bug(s) of 976811: 1003747 -- 1003747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003747 976811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003747: php-horde-ldap: (autopkgtest) needs update for php8.1: internal LDAP link is invalid
Source: php-horde-ldap Version: 2.4.2-4 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:php-defaults Control: block 976811 by -1 Dear maintainer(s), We are in the transition of replacing php7.4 with php8.1 [0]. With a recent upload of php-defaults the autopkgtest of php-horde-ldap fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing92 php-horde-ldap from testing2.4.2-4 versioned deps from testingfrom unstable 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 php-defaults to testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 7.4 and may help to identify what needs to be updated. php-commom added a whole set of versioned Breaks to make sure the right packages from current unstable are pulled in during testing. If the issue is caused by a missing breaks, please reasign this bug to php-common. 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/976811 [1] https://qa.debian.org/excuses.php?package=php-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-ldap/18284154/log.gz PHP Deprecated: Return type of Horde_Ldap_Search::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Search.php on line 508 ..E..EE.EEF..E.. 41 / 41 (100%) Time: 00:01.573, Memory: 6.00 MB There were 6 errors: 1) Horde_Ldap_LdapTest::testModify Horde_Ldap_Exception: Could not modify entry: Could not update entry: internal LDAP link is invalid /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:729 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:280 2) Horde_Ldap_LdapTest::testGetEntry Horde_Ldap_Exception: Unable to create connected entry: Parameter $entry needs to be a ldap entry resource! /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Entry.php:186 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Search.php:153 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1082 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:475 3) Horde_Ldap_LdapTest::testMove Horde_Ldap_Exception: Could not update entry: internal LDAP link is invalid /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Entry.php:637 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1133 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:530 4) Horde_Ldap_LdapTest::testRootDSE Horde_Ldap_Exception: Unable to create connected entry: Parameter $entry needs to be a ldap entry resource! /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Entry.php:186 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Search.php:153 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/RootDse.php:58 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1305 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:640 5) Horde_Ldap_LdapTest::testSchema Horde_Ldap_Exception: Unable to create connected entry: Parameter $entry needs to be a ldap entry resource! /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Entry.php:186 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Search.php:153 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/RootDse.php:58 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1305 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Schema.php:96 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1347 /tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:649 6) Horde_Ldap_SearchTest::testSPLIterator Horde_Ldap_Exception: Unable to create connected entry: Parameter $entry needs to be a ldap entry resource!
Bug#984114: liblastfm: ftbfs with GCC-11
forwarded 984114 https://github.com/lastfm/liblastfm/issues/39
tags 984114 + patch
thanks
On Wed, Mar 03, 2021 at 04:14:30PM +, Matthias Klose wrote:
> [...]
> /<>/src/fingerprint/Fingerprint.cpp:97:60: error: ISO C++17 does
> not allow dynamic exception specifications
>97 | lastfm::Fingerprint::generate( FingerprintableSource* ms ) throw(
> Error )
> |^
> /<>/src/fingerprint/Fingerprint.cpp:309:91: error: ISO C++17
> does not allow dynamic exception specifications
> 309 | lastfm::Fingerprint::decode( QNetworkReply* reply, bool*
> complete_fingerprint_requested ) throw( Error )
> |
> ^
> make[4]: ***
> [src/fingerprint/CMakeFiles/lastfm_fingerprint5.dir/build.make:111:
> src/fingerprint/CMakeFiles/lastfm_fingerprint5.dir/Fingerprint.cpp.o] Error 1
> [...]
FWIW, I can confirm that 1.0.9-1.1 still FTBFS in the manner originally
reported in this bug, but with the attached debdiff implementing the fix
from upstream I was able to build it again.
This is referenced in https://github.com/lastfm/liblastfm/issues/39 from
where I extracted the patch.
HTH, and please feel free to adjust to your liking.
Cheers,
Florian
diff -Nru liblastfm-1.0.9/debian/changelog liblastfm-1.0.9/debian/changelog
--- liblastfm-1.0.9/debian/changelog2019-08-23 23:37:23.0 +0200
+++ liblastfm-1.0.9/debian/changelog2022-01-14 22:30:53.0 +0100
@@ -1,3 +1,11 @@
+liblastfm (1.0.9-1.2) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with GCC-11 by removing dynamic exception specifications,
+patch taken from upstream. (Closes: #984114)
+
+ -- Florian Ernst Fri, 14 Jan 2022 22:30:53 +0100
+
liblastfm (1.0.9-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch
liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch
--- liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch1970-01-01
01:00:00.0 +0100
+++ liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch2022-01-14
22:30:47.0 +0100
@@ -0,0 +1,46 @@
+Description: Fix GCC-11 build issue
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984114
+Index: liblastfm-1.0.9/src/fingerprint/Fingerprint.cpp
+===
+--- liblastfm-1.0.9.orig/src/fingerprint/Fingerprint.cpp
liblastfm-1.0.9/src/fingerprint/Fingerprint.cpp
+@@ -94,7 +94,7 @@ lastfm::Fingerprint::data() const
+
+
+ void
+-lastfm::Fingerprint::generate( FingerprintableSource* ms ) throw( Error )
++lastfm::Fingerprint::generate( FingerprintableSource* ms )
+ {
+ //TODO throw if we can't get required metadata from the track object
+
+@@ -306,7 +306,7 @@ lastfm::Fingerprint::submit() const
+
+
+ void
+-lastfm::Fingerprint::decode( QNetworkReply* reply, bool*
complete_fingerprint_requested ) throw( Error )
++lastfm::Fingerprint::decode( QNetworkReply* reply, bool*
complete_fingerprint_requested )
+ {
+ // The response data will consist of a number and a string.
+ // The number is the fpid and the string is either FOUND or NEW
+Index: liblastfm-1.0.9/src/fingerprint/Fingerprint.h
+===
+--- liblastfm-1.0.9.orig/src/fingerprint/Fingerprint.h
liblastfm-1.0.9/src/fingerprint/Fingerprint.h
+@@ -71,7 +71,7 @@ namespace lastfm
+ };
+
+ /** This is CPU intensive, do it in a thread in your GUI application
*/
+-void generate( FingerprintableSource* ) throw( Error );
++void generate( FingerprintableSource* );
+
+ /** Submits the fingerprint data to Last.fm in order to get a
FingerprintId
+ * back. You need to wait for the QNetworkReply to finish before you
can
+@@ -82,7 +82,7 @@ namespace lastfm
+ * will be valid. Otherwise we will throw. You always get a valid id
+ * or a throw.
+ */
+-void decode( QNetworkReply*, bool*
lastfm_needs_a_complete_fingerprint = 0 ) throw( Error );
++void decode( QNetworkReply*, bool*
lastfm_needs_a_complete_fingerprint = 0 );
+ };
+
+
diff -Nru liblastfm-1.0.9/debian/patches/series
liblastfm-1.0.9/debian/patches/series
--- liblastfm-1.0.9/debian/patches/series 2015-11-20 16:42:23.0
+0100
+++ liblastfm-1.0.9/debian/patches/series 2022-01-14 22:27:26.0
+0100
@@ -1,2 +1,3 @@
change_target-name.patch
strip_README.patch
+fix_gcc11_ftbfs.patch
Processed: Re: Bug#984114: liblastfm: ftbfs with GCC-11
Processing commands for cont...@bugs.debian.org: > forwarded 984114 https://github.com/lastfm/liblastfm/issues/39 Bug #984114 [src:liblastfm] liblastfm: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/lastfm/liblastfm/issues/39'. > tags 984114 + patch Bug #984114 [src:liblastfm] liblastfm: ftbfs with GCC-11 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 984114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003746: php-horde-imp: (autopkgtest) needs update for php8.1: Failed asserting that 'This action is not supported. horde.warning' contains "Reply Sent."
Source: php-horde-imp Version: 6.2.27-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:php-defaults Control: block 976811 by -1 Dear maintainer(s), [In contrast to horde bugs filed yesterday, this issue seems to really break functionality.] We are in the transition of replacing php7.4 with php8.1 [0]. With a recent upload of php-defaults the autopkgtest of php-horde-imp fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing92 php-horde-imp from testing6.2.27-2 versioned deps from testingfrom unstable 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 php-defaults to testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 7.4 and may help to identify what needs to be updated. php-commom added a whole set of versioned Breaks to make sure the right packages from current unstable are pulled in during testing. If the issue is caused by a missing breaks, please reasign this bug to php-common. 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/976811 [1] https://qa.debian.org/excuses.php?package=php-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-imp/18284144/log.gz PHP Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /usr/share/php/Horde/Date.php on line 558 PHP Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /usr/share/php/Horde/Date.php on line 558 PHP Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /usr/share/php/Horde/Date.php on line 558 F. 49 / 49 (100%) Time: 00:00.086, Memory: 12.00 MB There were 40 failures: 1) Imp_Unit_Mime_Viewer_ItipTest::testAcceptingAnInvitationResultsInReplySent Failed asserting that 'This action is not supported. horde.warning' contains "Reply Sent.". /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:235 2) Imp_Unit_Mime_Viewer_ItipTest::testAcceptingAnInvitationResultsInMimeMessageSent Missing second message part! /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:260 3) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsProductId Missing second message part! /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:266 4) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageIndicatesMethodReply Missing second message part! /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:272 5) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsVevent Missing second message part! /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:626 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:278 6) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsCopiedUid Missing second message part! /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:626 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:284 7) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsCopiedSummary Missing second message part! /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:626 /tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:304 8) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsEmptySummaryIfNotAvailable Missing second message part!
Processed: php-horde-imp: (autopkgtest) needs update for php8.1: Failed asserting that 'This action is not supported. horde.warning' contains "Reply Sent."
Processing control commands: > affects -1 src:php-defaults Bug #1003746 [src:php-horde-imp] php-horde-imp: (autopkgtest) needs update for php8.1: Failed asserting that 'This action is not supported. horde.warning' contains "Reply Sent." Added indication that 1003746 affects src:php-defaults > block 976811 by -1 Bug #976811 [release.debian.org] transition: php8.1 976811 was blocked by: 980567 977340 1003472 1000655 990322 1002504 977186 1000568 977379 1003479 1002218 1000653 1000647 1003744 977384 977404 977389 977376 1000642 978151 978457 1000637 977658 977337 977403 977396 977378 1002242 1002215 1002020 1000593 977687 1000596 1000650 977385 977400 1002232 1003007 977401 1003473 1003432 1000619 977377 1000263 977388 1000574 1000474 1000571 1000654 976811 was blocking: 1000585 1002681 977373 Added blocking bug(s) of 976811: 1003746 -- 1003746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003746 976811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#984014: clementine: ftbfs with GCC-11
Processing commands for cont...@bugs.debian.org: > forwarded 984014 https://github.com/clementine-player/Clementine/issues/6865 Bug #984014 [src:clementine] clementine: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/clementine-player/Clementine/issues/6865'. > tags 984014 + patch Bug #984014 [src:clementine] clementine: ftbfs with GCC-11 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 984014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984014: clementine: ftbfs with GCC-11
forwarded 984014 https://github.com/clementine-player/Clementine/issues/6865
tags 984014 + patch
thanks
On Wed, Oct 27, 2021 at 11:05:04PM +0300, Alexander Kernozhitsky wrote:
> It's worth noting that the upstream has already fixed this bug:
>
> https://github.com/clementine-player/Clementine/commit/cfcd0a956e6758624fab0ff20aee9eb08b3df0b3
Indeed, and this is tracked in
https://github.com/clementine-player/Clementine/issues/6865 where that
patch is referenced.
FWIW, I can confirm that 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1 still FTBFS
in the manner originally reported in this bug, but with the attached
debdiff implementing the fix from upstream I was able to build it again.
HTH, and please feel free to adjust to your liking.
Cheers,
Florian
diff -Nru clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
2020-10-27 11:30:27.0 +0100
+++ clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
2022-01-14 21:44:24.0 +0100
@@ -1,3 +1,11 @@
+clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with GCC-11 by dropping -std=c++0x and -U__STRICT_ANSI__,
+patch taken from upstream. (Closes: #984014)
+
+ -- Florian Ernst Fri, 14 Jan 2022 21:44:24 +0100
+
clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1) unstable; urgency=medium
* New upstream snapshot.
diff -Nru
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/patches/fix_gcc11_ftbfs.patch
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/patches/fix_gcc11_ftbfs.patch
---
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/patches/fix_gcc11_ftbfs.patch
1970-01-01 01:00:00.0 +0100
+++
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/patches/fix_gcc11_ftbfs.patch
2022-01-14 21:44:24.0 +0100
@@ -0,0 +1,52 @@
+Description: Fix GCC-11 build issue
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984014
+Index:
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/ext/clementine-spotifyblob/CMakeLists.txt
+===
+---
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg.orig/ext/clementine-spotifyblob/CMakeLists.txt
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/ext/clementine-spotifyblob/CMakeLists.txt
+@@ -7,7 +7,7 @@ include_directories(${CMAKE_SOURCE_DIR}/
+ include_directories(${CMAKE_SOURCE_DIR}/ext/libclementine-common)
+ include_directories(${CMAKE_SOURCE_DIR}/src)
+
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Woverloaded-virtual -Wall
-Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs
-Wno-unused-private-field -Wno-unknown-warning-option --std=c++0x
-U__STRICT_ANSI__")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Woverloaded-virtual -Wall
-Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs
-Wno-unused-private-field -Wno-unknown-warning-option")
+
+ link_directories(${SPOTIFY_LIBRARY_DIRS})
+
+Index:
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/ext/clementine-tagreader/CMakeLists.txt
+===
+---
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg.orig/ext/clementine-tagreader/CMakeLists.txt
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/ext/clementine-tagreader/CMakeLists.txt
+@@ -7,7 +7,7 @@ include_directories(${CMAKE_BINARY_DIR}/
+ include_directories(${CMAKE_SOURCE_DIR}/src)
+ include_directories(${CMAKE_BINARY_DIR}/src)
+
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} --std=c++0x -U__STRICT_ANSI__")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
+
+ set(EXECUTABLE_OUTPUT_PATH ${CMAKE_BINARY_DIR})
+
+Index: clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/src/CMakeLists.txt
+===
+--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg.orig/src/CMakeLists.txt
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/src/CMakeLists.txt
+@@ -1,6 +1,6 @@
+
+ set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall")
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Woverloaded-virtual -Wall
-Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs
--std=c++0x -U__STRICT_ANSI__")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Woverloaded-virtual -Wall
-Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs")
+
+ option(BUILD_WERROR "Build with -Werror" ON)
+
+Index: clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/tests/CMakeLists.txt
+===
+--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg.orig/tests/CMakeLists.txt
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/tests/CMakeLists.txt
+@@ -1,6 +1,6 @@
+ cmake_minimum_required(VERSION 2.8.11)
+
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++0x -fpermissive
-Wno-c++11-narrowing -U__STRICT_ANSI__")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fpermissive -Wno-c++11-narrowing")
+
Processed: php-horde-crypt: (autopkgtest) needs update for php8.1: errorHandler(), 4 passed and exactly 5 expected
Processing control commands: > affects -1 src:php-defaults Bug #1003744 [src:php-horde-crypt] php-horde-crypt: (autopkgtest) needs update for php8.1: errorHandler(), 4 passed and exactly 5 expected Added indication that 1003744 affects src:php-defaults > block 976811 by -1 Bug #976811 [release.debian.org] transition: php8.1 976811 was blocked by: 977340 1000619 1003479 977400 977401 1000655 977403 1000263 977337 977389 1002242 1000650 1000571 1000568 977186 978151 1000474 1002020 1003007 1002232 977687 977396 1003432 977404 977378 1000596 1000642 1000574 1002504 980567 990322 1003473 978457 1000647 977376 1000593 977377 977379 1002218 1000654 977384 1002215 1000637 977385 977388 1000653 1003472 977658 976811 was blocking: 1000585 1002681 977373 Added blocking bug(s) of 976811: 1003744 -- 1003744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003744 976811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003744: php-horde-crypt: (autopkgtest) needs update for php8.1: errorHandler(), 4 passed and exactly 5 expected
Source: php-horde-crypt Version: 2.7.12-6 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:php-defaults Control: block 976811 by -1 Dear maintainer(s), [In contrast to earlier bugs filed, this issue seems to really break functionality.] We are in the transition of replacing php7.4 with php8.1 [0]. With a recent upload of php-defaults the autopkgtest of php-horde-crypt fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing92 php-horde-cryptfrom testing2.7.12-6 versioned deps from testingfrom unstable 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 php-defaults to testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 7.4 and may help to identify what needs to be updated. php-commom added a whole set of versioned Breaks to make sure the right packages from current unstable are pulled in during testing. If the issue is caused by a missing breaks, please reasign this bug to php-common. 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/976811 [1] https://qa.debian.org/excuses.php?package=php-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-crypt/18284133/log.gz PHP Deprecated: Horde_Stream implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /usr/share/php/Horde/Stream.php on line 27 PHP Deprecated: Horde_Stream_Temp implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /usr/share/php/Horde/Stream/Temp.php on line 23 PHPUnit 9.5.11 by Sebastian Bergmann and contributors. Runtime: PHP 8.1.1 Configuration: /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/phpunit.xml Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/Pgp/BinaryTest.php Class name was 'Horde_Crypt_Pgp_BinaryTest', expected 'BinaryTest' Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/PgpKeyserverTest.php Class name was 'Horde_Crypt_PgpKeyserverTest', expected 'PgpKeyserverTest' Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/PgpParseTest.php Class name was 'Horde_Crypt_PgpParseTest', expected 'PgpParseTest' Warning: Test case class not matching filename is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/SmimeTest.php Class name was 'Horde_Crypt_SmimeTest', expected 'SmimeTest' PHP Deprecated: Function strftime() is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php on line 247 PHP Deprecated: Function strftime() is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php on line 248 ..PHP Deprecated: Function strftime() is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php on line 247 PHP Deprecated: Function strftime() is deprecated in /tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php on line 247 .PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/share/php/Horde/Url.php on line 269 EPHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/share/php/Horde/Url.php on line 269 EPHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/share/php/Horde/Url.php on line 269 PHP Deprecated: Return type of Horde_Support_CaseInsensitiveArray::offsetExists($offset) should either be compatible with ArrayIterator::offsetExists(mixed $key): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Horde/Support/CaseInsensitiveArray.php on line 47 PHP Deprecated:
Bug#999250: marked as done (wnn7egg: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Fri, 14 Jan 2022 20:37:42 + with message-id and subject line Bug#999250: fixed in wnn7egg 1.02-10 has caused the Debian Bug report #999250, regarding wnn7egg: 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.) -- 999250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wnn7egg Version: 1.02-9 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: wnn7egg Source-Version: 1.02-10 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of wnn7egg, 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. Andreas Beckmann (supplier of updated wnn7egg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 14 Jan 2022 20:32:53 +0100 Source: wnn7egg Architecture: source Version: 1.02-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 999250 Changes: wnn7egg (1.02-10) unstable; urgency=medium . * QA upload. * Switch to dh. (Closes: #999250) * Switch to debhelper-compat (= 13). * Set Rules-Requires-Root: no. Checksums-Sha1: 2bdd2091173bd9ff182babb8e454e533f2230bff 1702 wnn7egg_1.02-10.dsc aedb977c5e7e990f3245d14c1cb4fdab864dcf4c 14684 wnn7egg_1.02-10.debian.tar.xz 64b8915b10ed4f0e042ad76a306b4b3f1f61a002 5438 wnn7egg_1.02-10_source.buildinfo Checksums-Sha256: d4193feda44f636b48f945e260c325b3f7d7ea9835bb106cd806498a7ac034e5 1702 wnn7egg_1.02-10.dsc bf51638a4c4aff6d7768fab441a53cb11387ed6bd73b0c68fcbe803259437635 14684 wnn7egg_1.02-10.debian.tar.xz 76f52275866c19b0c2127f2cf255f0c0c24c06dd599436d000d7bc19b8a92c69 5438 wnn7egg_1.02-10_source.buildinfo Files: 6be4e1dadab558ccaea3f940aa7bbbc4 1702 contrib/utils optional wnn7egg_1.02-10.dsc db2a8d49188a15dd7fe66825239d294e 14684 contrib/utils optional wnn7egg_1.02-10.debian.tar.xz 13effb529c2da32696013e25c22d7126 5438 contrib/utils optional wnn7egg_1.02-10_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmHh0GEQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCLcSEACFm+A1CsW7YiEYfh2gJqEhyzWNg0XuanfI mYdP/Cyaru4D3p66INGOx5IMbhcmpgvf58/I74V1/8klor6AD1HqLSvr7hg+z7I3 n6L5rATvNzQRZ93n2bYhO8xWfB9e/t/0SXI69shGgel9ULQt9BRfgl5o+oGU/l7w 61/LeApHN9t66IQGj6Cn6mjqAZLKUihhFxPT3WyIYqyMgtOune02m9NjUCw2WQD2 R5dit+mgwSmT0sPqmYbMrbbq2pLiL0UVyD/lMQtoFZ2EiuOf0ZsMYD7+S1i1E7++ qPlzjfujHfDQC95bzTP2lvm3sFwILDId89E3/NRTOk84oHyfcgQD+oIQ4Y2yZxJx hva+N4G6rwxBmeWO1c9ak+O8Xd3SeLeUe1STBhHQZbewUS1UmynrQoxY230XxLY5 UAbcGRL/Gny3AtifXeENxeqSAG+3J1MgfglB5pqqdmcHulXbibocsl6s/ISRWrjM tZNFBGXABZTwgCFGF1KcgoaFjfYP+iAWXstTiuN2GSBJmGTaLIzIjrNgY4bWin0B 7VAfi5URcM9ax4ymao/JdUTVBAUDBY0y1zhPOskyRVDi6QabNtwUxeXDtPhmnC0o iUjYsxzDk3T9Wt8zigzkEf/CWcEGd5W15qvDqLCR/MCvHev8BeZXjeEW7GCCVDY4 p7J+zqeoxw== =ljS1 -END PGP SIGNATURE End Message ---
Bug#1002877: marked as done (src:vnlog: fails to migrate to testing for too long: uploader built binaries)
Your message dated Fri, 14 Jan 2022 20:37:31 + with message-id and subject line Bug#1002877: fixed in vnlog 1.32-1.1 has caused the Debian Bug report #1002877, regarding src:vnlog: fails to migrate to testing for too long: uploader built binaries 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.) -- 1002877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vnlog Version: 1.31-1 Severity: serious Control: close -1 1.32-1 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync 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:vnlog has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=vnlog OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: vnlog Source-Version: 1.32-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of vnlog, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated vnlog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 30 Dec 2021 19:52:30 +0100 Source: vnlog Architecture: source Version: 1.32-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Paul Gevers Closes: 1002877 Changes: vnlog (1.32-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1002877) Checksums-Sha1: 58cc1a76f033d6a97e1f28b673d4981634d59981 2067 vnlog_1.32-1.1.dsc 5fe093b3d474790a7da9d35eaefecb7a455b857c 5784 vnlog_1.32-1.1.debian.tar.xz Checksums-Sha256: ef4acfc4d2722a25501ee49903e6964422141fe202a81560f281664ab80f7a72 2067 vnlog_1.32-1.1.dsc 269168ae0a12e1d39636a5e056c71f2e63b15015a419a0ef5f3aa961318e8517 5784 vnlog_1.32-1.1.debian.tar.xz Files: 997c20b31c041cd160aa68aeb56a1e80 2067 devel optional vnlog_1.32-1.1.dsc 066e81832896068aa2bf7ef7f689dcfd 5784 devel optional vnlog_1.32-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmHOAB4ACgkQnFyZ6wW9 dQrkCQf/dbEw7iEgP4r/upNpBgnU+93ZN4syrNhtunpBrduqd5Ah8DzeZLp3S3qk 6PDWZ8CMAF3xR9n7bXzDESdQ9r9VGPgiuBoX8QqJOVDicGBXGn3l510HGzaWmluh hH518pmMuPsIjUWWiZ/8yCu4CGOh/J+3F1XI51KDKWPgXdcC5WqLOREnO0KF2WAB 5iJbPlDs/hej3lOHO1LYdIKL/lkTwvnbIeJbCxfikFnxcT8UpVNCTNYv4dGEuQ9Q uXEfSCSTvPUM0P/3noBOb4idy9ZkgP1FXTjYHG0P+5opSKuyiE2QjqWVBGeQ9J3g QEt1QQXgkd4J0j++kxbKkny85aQe9Q== =tAe5 -END PGP SIGNATURE End Message ---
Processed: bug 993241 is forwarded to https://sourceforge.net/p/minidlna/bugs/341/
Processing commands for cont...@bugs.debian.org: > forwarded 993241 https://sourceforge.net/p/minidlna/bugs/341/ Bug #993241 [src:minidlna] minidlna FTBFS: configure: error: Could not find libid3tag Set Bug forwarded-to-address to 'https://sourceforge.net/p/minidlna/bugs/341/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 993241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1003696 in 0.11.9-2, found 1003696 in 0.11.2-1+deb10u2, found 1003696 in 0.11.2-1
Processing commands for cont...@bugs.debian.org:
> found 1003696 0.11.9-2
Bug #1003696 {Done: Victor Seva } [src:prosody] prosody:
CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket
interface
Ignoring request to alter found versions of bug #1003696 to the same values
previously set
> found 1003696 0.11.2-1+deb10u2
Bug #1003696 {Done: Victor Seva } [src:prosody] prosody:
CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket
interface
Marked as found in versions prosody/0.11.2-1+deb10u2.
> found 1003696 0.11.2-1
Bug #1003696 {Done: Victor Seva } [src:prosody] prosody:
CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket
interface
Marked as found in versions prosody/0.11.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 1003696 in 0.11.9-2
Processing commands for cont...@bugs.debian.org:
> found 1003696 0.11.9-2
Bug #1003696 {Done: Victor Seva } [src:prosody] prosody:
CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket
interface
Marked as found in versions prosody/0.11.9-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive
Hi, On 14-01-2022 13:06, Sebastian Ramacher wrote: The ocaml dependencies are installable again after a round of binNMUs. guestfs-tools however fails almost everywhere: https://buildd.debian.org/status/package.php?p=guestfs-tools A new upload fixed most of that, it failed on arm64 (and not yet built on mips*el). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1003020: openblas breaks hypre autopkgtest on armhf: test times out after 2:47h
Hi, On 14-01-2022 18:16, Drew Parsons wrote: The passing machine was ci-worker-armel-01, but it was also the host for failing tests. So it's not a simple as some difference between different CPU variants of armhf. We only have one host for our armhf testing. (We did change host in the middle of 2021). If I can be of any help, I can try to run explicitly given commands in or extract information from the testbed of a (passing) test run (I'm not sure if I can do the same from a failing test as that may be shortcutted somehow, but I can try). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#999314: marked as done (xinv3d: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Fri, 14 Jan 2022 18:45:16 +
with message-id
and subject line Bug#999314: fixed in xinv3d 1.3.6-7
has caused the Debian Bug report #999314,
regarding xinv3d: 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.)
--
999314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xinv3d
Version: 1.3.6-6
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: xinv3d
Source-Version: 1.3.6-7
Done: Ricardo Mones
We believe that the bug you reported is fixed in the latest version of
xinv3d, 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.
Ricardo Mones (supplier of updated xinv3d package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 14 Jan 2022 19:07:09 +0100
Source: xinv3d
Architecture: source
Version: 1.3.6-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Ricardo Mones
Closes: 900345 965904 999314
Changes:
xinv3d (1.3.6-7) unstable; urgency=medium
.
* Move package under Games Team umbrella (Closes: #900345)
* Bump debhelper compat level to 13 (Closes: #965904)
* Update Standards-Version to latest
* Add ${misc:Depends} to binary
* Add a homepage URL
* Add Vcs-* URLs for current packaging
* Switch to source format 3.0
* Migrate to debhelper sequencer (Closes: #999314)
* Add a watch file
* Add Rules-Requires-Root field
* Switch copyright to machine readable format
Checksums-Sha1:
3e67c5c2112f4e4b9f4ec118e465c5b60eb5d50c 1926 xinv3d_1.3.6-7.dsc
a0e61bbf68d01cd5d099d21ab70bcf5d405421ff 3784 xinv3d_1.3.6-7.debian.tar.xz
a3729723d057da6b6ec36138c09bff9b199213b3 6603 xinv3d_1.3.6-7_amd64.buildinfo
Checksums-Sha256:
1201b3dd4842d26595cadab8ea805484e3bd4feddc9fb0f58bdefe003e72813e 1926
xinv3d_1.3.6-7.dsc
3556a60e185ebc23579c456720a54a6266e4ffcf8ed72a470272927a06cd68eb 3784
xinv3d_1.3.6-7.debian.tar.xz
77f49a5e61c1b563c838b751b09f736b910b481ac5024a35d9211fb5e43b 6603
xinv3d_1.3.6-7_amd64.buildinfo
Files:
8a9db1cb79159a5918d006ca0f1f676c 1926 games optional xinv3d_1.3.6-7.dsc
da6848884d04af3c848038d2601e22e6 3784 games optional
xinv3d_1.3.6-7.debian.tar.xz
7d1f9e9a3cf9ee51725c550dbcdc 6603 games optional
xinv3d_1.3.6-7_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAmHhvjoACgkQHw8KiN5b
zKYZjg/+KAZimWe481FA71oMtNnkQwTu/Y3Qkta13VzrWjZQdxSMI7JSTBiu4wsr
m0DArlD5Ht3cs1z2siUlZ377h/wrDLXdMToKXNNcXL/uIvrO33UaJQskrIny/rKW
qSobDtD6tVHOI06dRBa8gDWod1ZPNQpGR5VFmp+tJQlmyz2/SWw7nD+ieWc8X936
ITRRmRyM4GvP8utf2E47aBP1fntUMPwhK6AaOEQlqE4IhmQMn0vCheQm2xGVuruq
UbtGKe7+rEo10ZMyyVIWQtb7VUaMedPpCSxMPHtKcZcCjt6e1zoukIa1W7x3Kcbx
fAzK9xxro4NZvAX6gw88JvzXIcUqb+52y6V3mXGiobwKFw1L+qr2duWvE7er0Ni4
2jcm7dsqLcJz1hIHylWUbfjaUuVJuRy8hS266+gJesJbcvClZ4l+yBNA5UiLg7sa
hhvdScEWStdZDvLxY3Yc4IeNWuarPQz99RwZllewx92wrhJ81GkbNsU+fj+XCPfq
I5Cw06JN6MVYfYTTRrX928HqjjZ2Tga4emCgMl/2zllkGeU0V3y86voZ/HWOsioQ
6HILNkgiTOa2QcqMxaoVGtJYHasSFfiG4AfTadaQA2d4B1UDxWyOkPuiYKWlfpWo
q0FEW3GcjqRA9ElWsHZQZdO+qZ5Q11/21rok+P8N64Bxy4L+ZIs=
=dzBE
-END PGP SIGNATURE End Message ---
Bug#965904: marked as done (xinv3d: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Fri, 14 Jan 2022 18:45:16 +
with message-id
and subject line Bug#965904: fixed in xinv3d 1.3.6-7
has caused the Debian Bug report #965904,
regarding xinv3d: 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.)
--
965904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xinv3d
Version: 1.3.6-6
Severity: normal
Usertags: compat-5-6-removal
Hi,
The package xinv3d 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: xinv3d
Source-Version: 1.3.6-7
Done: Ricardo Mones
We believe that the bug you reported is fixed in the latest version of
xinv3d, 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.
Ricardo Mones (supplier of updated xinv3d package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 14 Jan 2022 19:07:09 +0100
Source: xinv3d
Architecture: source
Version: 1.3.6-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Ricardo Mones
Closes: 900345 965904 999314
Changes:
xinv3d (1.3.6-7) unstable; urgency=medium
.
* Move package under Games Team umbrella (Closes: #900345)
* Bump debhelper compat level to 13 (Closes: #965904)
* Update Standards-Version to latest
* Add ${misc:Depends} to binary
* Add a homepage URL
* Add Vcs-* URLs for current packaging
* Switch to source format 3.0
* Migrate to debhelper sequencer (Closes: #999314)
* Add a watch file
* Add Rules-Requires-Root field
* Switch copyright to machine readable format
Checksums-Sha1:
3e67c5c2112f4e4b9f4ec118e465c5b60eb5d50c 1926 xinv3d_1.3.6-7.dsc
a0e61bbf68d01cd5d099d21ab70bcf5d405421ff 3784 xinv3d_1.3.6-7.debian.tar.xz
a3729723d057da6b6ec36138c09bff9b199213b3 6603 xinv3d_1.3.6-7_amd64.buildinfo
Checksums-Sha256:
1201b3dd4842d26595cadab8ea805484e3bd4feddc9fb0f58bdefe003e72813e 1926
xinv3d_1.3.6-7.dsc
3556a60e185ebc23579c456720a54a6266e4ffcf8ed72a470272927a06cd68eb 3784
xinv3d_1.3.6-7.debian.tar.xz
77f49a5e61c1b563c838b751b09f736b910b481ac5024a35d9211fb5e43b 6603
xinv3d_1.3.6-7_amd64.buildinfo
Files:
8a9db1cb79159a5918d006ca0f1f676c 1926 games optional xinv3d_1.3.6-7.dsc
da6848884d04af3c848038d2601e22e6 3784 games optional
xinv3d_1.3.6-7.debian.tar.xz
7d1f9e9a3cf9ee51725c550dbcdc 6603 games optional
xinv3d_1.3.6-7_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAmHhvjoACgkQHw8KiN5b
zKYZjg/+KAZimWe481FA71oMtNnkQwTu/Y3Qkta13VzrWjZQdxSMI7JSTBiu4wsr
m0DArlD5Ht3cs1z2siUlZ377h/wrDLXdMToKXNNcXL/uIvrO33UaJQskrIny/rKW
qSobDtD6tVHOI06dRBa8gDWod1ZPNQpGR5VFmp+tJQlmyz2/SWw7nD+ieWc8X936
ITRRmRyM4GvP8utf2E47aBP1fntUMPwhK6AaOEQlqE4IhmQMn0vCheQm2xGVuruq
UbtGKe7+rEo10ZMyyVIWQtb7VUaMedPpCSxMPHtKcZcCjt6e1zoukIa1W7x3Kcbx
fAzK9xxro4NZvAX6gw88JvzXIcUqb+52y6V3mXGiobwKFw1L+qr2duWvE7er0Ni4
2jcm7dsqLcJz1hIHylWUbfjaUuVJuRy8hS266+gJesJbcvClZ4l+yBNA5UiLg7sa
Processed: severity of 1003717 is important
Processing commands for cont...@bugs.debian.org: > severity 1003717 important Bug #1003717 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: ttm buffer eviction failed + failed to load nvd9_fuc084 (regression db11-db10) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1003717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003020: openblas breaks hypre autopkgtest on armhf: test times out after 2:47h
On 2022-01-14 14:50, Sébastien Villemot wrote: Le dimanche 02 janvier 2022 à 21:19 +0100, Paul Gevers a écrit : With a recent upload of openblas the autopkgtest of hypre fails in testing when that autopkgtest is run with the binary packages of openblas from unstable on armhf due to a timeout after 2:47 h. It passes when run with only packages from testing in about 9-12 minutes. In tabular form: passfail openblas from testing0.3.19+ds-1 hypre from testing2.22.1-3 all others from testingfrom testing ... First note that there has been no change to the ARM32-specific code of openblas between 0.3.18+ds-1 and 0.3.19+ds-1. Also, I tried to replicate the problem on a porterbox (abel), but the autopkgtest succeeds (with hypre 2.22.1-3 and openblas 0.3.19+ds-2, in an armhf chroot): ... So at this point I don’t know how to tackle this issue. Drew, any idea? No clear ideas at this point. I ran a battery of tests on debci. One armhf test passed on unstable, but 10 or so failed. So there's some random irreproducibility of the problem. The passing machine was ci-worker-armel-01, but it was also the host for failing tests. So it's not a simple as some difference between different CPU variants of armhf. There's a new version waiting in NEW (actually there are 2 versions waiting in NEW). There's not much more constructive testing I can do until they get processed. Once they're cleared we'll be able to compare the new version from experimental. Drew
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
在 2022/1/14 23:30, Sandro Tosi 写道: On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su wrote: On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel wrote: > Built with gcc-11 and -fno-lto it doesn not work. > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ ../../../test.py > Segmentation fault > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ PYTHONPATH=. ../../../test.py > Segmentation fault > > It seems due to gcc-11. I tried to build with gcc-10 on sid, it works again. yes, that's what PICCA found and reported at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 are you going to look into a fix for gcc-11? Sure, I will dig it, since it may effect lots of other packages. Thanks,
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su wrote: > > On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel > wrote: > > Built with gcc-11 and -fno-lto it doesn not work. > > > > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > ../../../test.py > > Segmentation fault > > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > PYTHONPATH=. ../../../test.py > > Segmentation fault > > > > > > It seems due to gcc-11. > > I tried to build with gcc-10 on sid, it works again. yes, that's what PICCA found and reported at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 are you going to look into a fix for gcc-11? Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#1003344: restfuldb: FTBFS with SQLite3 3.37.0+
Hi, On 2022-01-08 19:46, László Böszörményi (GCS) wrote: > SQLite3 3.37.0 and onwards changed its inner working. Now table column > data types are stored as a value and always returned as uppercase > text. This breaks your package as it relies on the old behavior, when > this was stored as text and returned in a case it was defined. > As I broke it, I've created a fix for you, patch is attached. Couldn't > make it work with older SQLite3 versions thus you will need to build > depend on SQLite3 3.37.0 and newer. Thanks a lot for the patch. Since I am one of the upstream developers I will see how this could be fixed upstream. My priority would be to support both SQLite3 << 3.37.0 and >= 3.37.0, but I can see that for Debian your patch is sufficient. > Sorry for the inconvenience, No problem, such breakages sometimes happen with dependency updates. Thanks, Andrius
Bug#965499: marked as done (docbook-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Fri, 14 Jan 2022 15:08:43 + with message-id and subject line Bug#965499: fixed in docbook-utils 0.6.14-4 has caused the Debian Bug report #965499, regarding docbook-utils: 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.) -- 965499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: docbook-utils Version: 0.6.14-3.3 Severity: normal Usertags: compat-5-6-removal Hi, The package docbook-utils 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: docbook-utils Source-Version: 0.6.14-4 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of docbook-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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated docbook-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: Fri, 14 Jan 2022 15:36:16 +0100 Source: docbook-utils Architecture: source Version: 0.6.14-4 Distribution: unstable Urgency: medium Maintainer: Debian XML/SGML Group Changed-By: Mathieu Malaterre Closes: 965499 Changes: docbook-utils (0.6.14-4) unstable; urgency=medium . * d/compat: Migrate to compat 11. Closes: #965499 * d/control: Update Vcs URLs to new git location * d/control: Bump Std-Vers to 4.6.0 no changes needed Checksums-Sha1: 450dc98cc55b38f46c4fd40f7f4c5a84c0dea24e 2132 docbook-utils_0.6.14-4.dsc b1641b178826e451196f336b744425fce4022469 13780 docbook-utils_0.6.14-4.debian.tar.xz b7643bd070b77614b4a11f9dc9c3b4db33d4982d 4705 docbook-utils_0.6.14-4_source.buildinfo Checksums-Sha256: 4677398e7986144e50a25089c5552f1bca086d4008ca10e1e9d6fc94c2adbb16 2132 docbook-utils_0.6.14-4.dsc fbb348de6c92f966b92f9e9c9348dceba4dd6fa8e61321177265c2c52a2ab981 13780 docbook-utils_0.6.14-4.debian.tar.xz 96e4e4454590bcb454ead4917e6d904d08f9307a007e5cd81b017f1fb6f9b9f6 4705 docbook-utils_0.6.14-4_source.buildinfo Files: 43d3a7797b89e5cb3ec33ad840b1a4f0 2132 text optional docbook-utils_0.6.14-4.dsc fb2d5fdbf41f120ab5b66bbaafb729ef 13780 text optional docbook-utils_0.6.14-4.debian.tar.xz 309a380250a0cb4787997b3abdc5f61a 4705 text optional docbook-utils_0.6.14-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmHhirQRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0WXdw/9H75Krt+c6KAir6pp7WS0giCHqOLTHAec ua8nEfeYDeHh2CRltYjioSwTaYtf7bLyiVahVS2n8nCbSE9sZsIvIqwf7/p0Kezf 3OI4mDPwbu7U37HN0Brn5AJ/7NBFR0N/LiPubJrdpxLmcdCowN7s+1na6kCi6TNV qaGMwqZgwFbIuk613nnzc7IuC65ryLm396d8TZ32NMdB2AU44SsVcgwOmhAwLauv 9ouvwpAqWknp6L4/w5Zk+xAyQC0wVbZLIzeB3vZ9HaOS7MJaviBMnqM1yChuyqZh 4MyUEdkps7UhAeEVMvKS1y6lttzv16SRqXxF+jWuMq/jouJ/ySfuFcmimsLMdxlO niN8QNtWED2fs9l9o+ShR2K5Jaz84uB6f2ehv9/rX/X9ZhoE3LnvklkbEXE1mr04 hPYjNqhJNQlqosoqW7LRqiCzBuepInBIBKBCdbhxY1nwUKvXPKuAAyZOcCXTn2q2 vT1Te4XyoA5Gx23U5Q3XZRrh8Hjd44NDF6X773KWvJMeTG844pz+lqxV29khmWYN N48SRuCL0TXQHC9oFA3QGTVhKhQC6G/C3b2p12Bplozu38v2jC6SZLsYfhXpD4Ze
Bug#1001181: marked as done (docbook-mathml should switch from w3-dtd-mathml to w3c-sgml-lib)
Your message dated Fri, 14 Jan 2022 15:08:37 + with message-id and subject line Bug#1001181: fixed in docbook-mathml 1.1CR1-3 has caused the Debian Bug report #1001181, regarding docbook-mathml should switch from w3-dtd-mathml to w3c-sgml-lib 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.) -- 1001181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: docbook-mathml Version: 1.1CR1-2.1 Severity: serious Tags: bookworm sid Control: block 994795 by -1 w3-dtd-mathml contains an older version of mathml2.dtd that no longer works with libxml2 2.9.12, see #994795 for background. --- End Message --- --- Begin Message --- Source: docbook-mathml Source-Version: 1.1CR1-3 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of docbook-mathml, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated docbook-mathml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Jan 2022 15:45:29 +0100 Source: docbook-mathml Architecture: source Version: 1.1CR1-3 Distribution: unstable Urgency: medium Maintainer: Debian XML/SGML Group Changed-By: Mathieu Malaterre Closes: 1001181 Changes: docbook-mathml (1.1CR1-3) unstable; urgency=medium . * d/compat: Migrate to compat 11 * d/rules: Remove explicit --parallel flag from dh sequence * d/control: Update Vcs URLs to new git location * d/control: Bump Std-Vers to 4.6.0 no changes needed * d/control: switch from w3-dtd-mathml to w3c-sgml-lib. Closes: #1001181 * d/watch: Update to version 4 Checksums-Sha1: 2030c59ebe7968c9bcb05afea2368335b2d6564e 2040 docbook-mathml_1.1CR1-3.dsc 99e77d11c506cb83897dc9708d579d2ef960b30c 4060 docbook-mathml_1.1CR1-3.debian.tar.xz 15f2e5f7434cef7152e0eae5b07b3c73713e9f64 4729 docbook-mathml_1.1CR1-3_source.buildinfo Checksums-Sha256: ef7891a3df864ddcf089841a21da08365522eb022d85a4af6dc846cff9c44473 2040 docbook-mathml_1.1CR1-3.dsc b5d55914db2a42b9c3e42040ad68896672ba80cc77edf5cf7617821bc6994068 4060 docbook-mathml_1.1CR1-3.debian.tar.xz 4d268716012a15d58d87794c6294c6730d6fc33bd11fd3e0c94fa659f1f4689b 4729 docbook-mathml_1.1CR1-3_source.buildinfo Files: f9c8fa7210712288d3bd49ab55a5aefd 2040 text optional docbook-mathml_1.1CR1-3.dsc d793ae3668ac01049efc4bb2be13883b 4060 text optional docbook-mathml_1.1CR1-3.debian.tar.xz be020a37798ff86d4819f0bbbe31a92d 4729 text optional docbook-mathml_1.1CR1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmHhjLURHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0Wi5g//chmsHPQIYICqZlXuad2WCW03fLjZnU9s AGhtVzf0K89DKtCjo2NNTMDL9K+FO8puPB/SbugKz71ipKeONRBtSz/8yiFARwi1 5B6AsUu+viCNnMyK4dE+gsDA3hW4GWyEPe1XFVCkNDK1l2scJAj3sTpcPhA87250 KlgvQ9/BJTMl/96yAaywdFbjqByWWec4luLke8aBJ9efQepWMOYocxoUBBZLQHRa 6vdFa7DE6/yevN1WeFeB8pmukfdembcxRqy9E7e0i0dTkKfVsM7gHPyUZCmFcrkD Bh4Y3TOzYL66gyvLsawGFgA/CHbFC3d4B4c2tjPaBJ+TfDwclBxwDMu8BrfnQTRs SlTaxH8sS836U3cOJiieAV9a3qPcYeCbqVvafuUz5qozh3/ogw5VYV3RZwwx12d8 UFBGZ14DyXeNTVtACezrg7GEGGG+yFpgOCeeASeGJuD8xjvAXCI242p+H8AyJzHZ 8MwYXay9lJNkEmhJTNROwcQImhOM0/Yh/I8Cb38xeT8PDmr4Q46gyF2MxQQl/ngp HuNRzRAit1ebUYj1adMCPl5ASVb2fZ2+7pWDjJnvIYwe5FGMzlvycRP7lFz/12OV uCxbkOhPJc91uzul1gq1g55kb9pKMQVttLxAKO5cBGvsfVKZgo5twtxSu7C9MqE4 WR98tmUjpgQ= =Fggi -END PGP SIGNATURE End Message ---
Processed: bug #1002357: forwarded to upstream fix
Processing commands for cont...@bugs.debian.org:
> forwarded 1002357 https://github.com/maxcountryman/flask-login/commit/3d316b
Bug #1002357 [src:flask-login] flask-login: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/maxcountryman/flask-login/commit/3d316b'.
> --
Stopping processing here.
Please contact me if you need assistance.
--
1002357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel wrote: > Built with gcc-11 and -fno-lto it doesn not work. > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ ../../../test.py > Segmentation fault > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ PYTHONPATH=. ../../../test.py > Segmentation fault > > It seems due to gcc-11. I tried to build with gcc-10 on sid, it works again.
Bug#1003020: openblas breaks hypre autopkgtest on armhf: test times out after 2:47h
Hi, Le dimanche 02 janvier 2022 à 21:19 +0100, Paul Gevers a écrit : > Source: openblas, hypre > Control: found -1 openblas/0.3.19+ds-1 > Control: found -1 hypre/2.22.1-3 > Severity: serious > Tags: sid bookworm > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: breaks needs-update > > With a recent upload of openblas the autopkgtest of hypre fails in > testing when that autopkgtest is run with the binary packages of > openblas from unstable on armhf due to a timeout after 2:47 h. It passes > when run with only packages from testing in about 9-12 minutes. In > tabular form: > > passfail > openblas from testing0.3.19+ds-1 > hypre from testing2.22.1-3 > all others from testingfrom testing > > I copied some of the output at the bottom of this report, but as the > test times out, I suspect it just hangs and there's not much useful to see. > > Currently this regression is blocking the migration of openblas 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? First note that there has been no change to the ARM32-specific code of openblas between 0.3.18+ds-1 and 0.3.19+ds-1. Also, I tried to replicate the problem on a porterbox (abel), but the autopkgtest succeeds (with hypre 2.22.1-3 and openblas 0.3.19+ds-2, in an armhf chroot): Running tests for HYPRE testing began at Fri Jan 14 13:24:29 UTC 2022 running TEST_ams ... ok test TEST_ams for HYPRE completed in 54 s skipping TEST_bench skipping TEST_examples running TEST_fac ... ok test TEST_fac for HYPRE completed in 106 s skipping TEST_fei running TEST_ij ... ok test TEST_ij for HYPRE completed in 256 s running TEST_lobpcg ... ok test TEST_lobpcg for HYPRE completed in 116 s running TEST_longdouble ... ok test TEST_longdouble for HYPRE completed in 136 s running TEST_single ... ok test TEST_single for HYPRE completed in 78 s running TEST_sstruct ... ok test TEST_sstruct for HYPRE completed in 271 s running TEST_struct ... ok test TEST_struct for HYPRE completed in 186 s running TEST_superlu ... ok test TEST_superlu for HYPRE completed in 58 s skipping TEST_timing all tests for HYPRE completed at Fri Jan 14 13:45:30 UTC 2022 in 1261s So at this point I don’t know how to tackle this issue. Drew, any idea? Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#984360: marked as done (tango: ftbfs with GCC-11)
Your message dated Fri, 14 Jan 2022 13:36:45 + with message-id and subject line Bug#984267: fixed in omniorb-dfsg 4.2.4-3 has caused the Debian Bug report #984267, regarding tango: ftbfs with GCC-11 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.) -- 984267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tango Version: 9.3.4+dfsg1-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. 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://people.debian.org/~doko/logs/20210228/filtered/gcc11/tango_9.3.4+dfsg1-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /bin/bash ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/cpp/client -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/server -I/usr/include -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -D_TANGO_LIB -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -DOMNI_UNLOADABLE_STUBS -c -o pollcmds.lo pollcmds.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/cpp/client -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/server -I/usr/include -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -D_TANGO_LIB -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -DOMNI_UNLOADABLE_STUBS -c pollcmds.cpp -fPIC -DPIC -o .libs/pollcmds.o /bin/bash ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/cpp/client -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/server -I/usr/include -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -D_TANGO_LIB -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -DOMNI_UNLOADABLE_STUBS -c -o pollobj.lo pollobj.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/cpp/client -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/server -I/usr/include -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -D_TANGO_LIB -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -DOMNI_UNLOADABLE_STUBS -c pollobj.cpp -fPIC -DPIC -o .libs/pollobj.o /bin/bash ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/cpp/client -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/log4tango/include -I../../../lib/cpp/server -I/usr/include -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -D_TANGO_LIB -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT
Bug#984267: marked as done (omnievents: ftbfs with GCC-11)
Your message dated Fri, 14 Jan 2022 13:36:45 + with message-id and subject line Bug#984267: fixed in omniorb-dfsg 4.2.4-3 has caused the Debian Bug report #984267, regarding omnievents: ftbfs with GCC-11 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.) -- 984267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:omnievents Version: 1:2.6.2-5.1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. 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://people.debian.org/~doko/logs/20210228/filtered/gcc11/omnievents_2.6.2-5.1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] from ProxyPushConsumer.cc:25: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC ProxyPushSupplier.cc In file included from ProxyPushSupplier.h:38, from ProxyPushSupplier.cc:24: EventQueue.h:93:3: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 93 | auto_ptr _filter; | ^~~~ In file included from /usr/include/c++/11/memory:76, from EventQueue.h:34, from ProxyPushSupplier.h:38, from ProxyPushSupplier.cc:24: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from ProxyPushSupplier.h:38, from ProxyPushSupplier.cc:24: EventQueue.h: In member function ‘void OmniEvents::EventQueue::setFilter(OmniEvents::Filter*)’: EventQueue.h:74:5: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 74 | auto_ptr f(filter); | ^~~~ In file included from /usr/include/c++/11/memory:76, from EventQueue.h:34, from ProxyPushSupplier.h:38, from ProxyPushSupplier.cc:24: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC Servant.cc g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC SupplierAdmin.cc g++ -c -I../idl -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include -DHAVE_CONFIG_H -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC
Bug#984269: marked as done (omniorb-dfsg: ftbfs with GCC-11)
Your message dated Fri, 14 Jan 2022 13:36:45 + with message-id and subject line Bug#984267: fixed in omniorb-dfsg 4.2.4-3 has caused the Debian Bug report #984267, regarding omniorb-dfsg: ftbfs with GCC-11 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.) -- 984267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:omniorb-dfsg Version: 4.2.2-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. 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://people.debian.org/~doko/logs/20210228/filtered/gcc11/omniorb-dfsg_4.2.2-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] g++ -M -MD -MG -p static/ -p shared/ -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I../../../../../src/lib/omniORB/orbcore/.. -I../../../../include/omniORB4/internal -I../../../../../include/omniORB4/internal -D_REENTRANT -DUSE_omniORB_logStream -D_OMNIORB_LIBRARY -DOMNIORB_VERSION_STRING="4.2.2" -DOMNIORB_VERSION_HEX=0x040202F1 -DCONFIG_DEFAULT_LOCATION="/etc/omniORB.cfg" -DCONFIG_ENV="OMNIORB_CONFIG" -DUnixArchitecture -I. -I../../../../../src/lib/omniORB/orbcore -I../../../../include -I../../../../../include -D__OSVERSION__=2 -D__linux__ -D__x86_64__ ../../../../../src/lib/omniORB/orbcore/unix/unixActive.cc ../../../../../src/lib/omniORB/orbcore/unix/unixAddress.cc ../../../../../src/lib/omniORB/orbcore/unix/unixEndpoint.cc ../../../../../src/lib/omniORB/orbcore/unix/unixConnection.cc ../../../../../src/lib/omniORB/orbcore/unix/unixTransportImpl.cc ../../../../../src/lib/omniORB/orbcore/tcp/tcpActive.cc ../../../../../src/lib/omniORB/orbcore/tcp/tcpAddress.cc ../../../../../src/lib/omniOR B/orbcore/tcp/tcpEndpoint.cc ../../../../../src/lib/omniORB/orbcore/tcp/tcpConnection.cc ../../../../../src/lib/omniORB/orbcore/tcp/tcpTransportImpl.cc ../../../../../src/lib/omniORB/orbcore/tcpSocket.cc ../../../../../src/lib/omniORB/orbcore/Namingstub.cc ../../../../../src/lib/omniORB/orbcore/poastubs.cc ../../../../../src/lib/omniORB/orbcore/objectStub.cc ../../../../../src/lib/omniORB/orbcore/bootstrapstub.cc ../../../../../src/lib/omniORB/orbcore/cs-UTF-16.cc ../../../../../src/lib/omniORB/orbcore/cs-UTF-8.cc ../../../../../src/lib/omniORB/orbcore/cs-8859-1.cc ../../../../../src/lib/omniORB/orbcore/cs-16bit.cc ../../../../../src/lib/omniORB/orbcore/cs-8bit.cc ../../../../../src/lib/omniORB/orbcore/codeSets.cc ../../../../../src/lib/omniORB/orbcore/SocketCollection.cc ../../../../../src/lib/omniORB/orbcore/giopMonitor.cc ../../../../../src/lib/omniORB/orbcore/giopBiDir.cc ../../../../../src/lib/omniORB/orbcore/giopImpl12.cc ../../../../../src/lib/omniORB/orbcore/giopImpl11.cc .. /../../../../src/lib/omniORB/orbcore/giopImpl10.cc ../../../../../src/lib/omniORB/orbcore/giopStreamImpl.cc ../../../../../src/lib/omniORB/orbcore/GIOP_S.cc ../../../../../src/lib/omniORB/orbcore/GIOP_C.cc ../../../../../src/lib/omniORB/orbcore/giopRendezvouser.cc ../../../../../src/lib/omniORB/orbcore/giopWorker.cc ../../../../../src/lib/omniORB/orbcore/giopServer.cc ../../../../../src/lib/omniORB/orbcore/giopStream.cc ../../../../../src/lib/omniORB/orbcore/giopStrand.cc ../../../../../src/lib/omniORB/orbcore/giopRope.cc
Bug#1003727: debian-edu-config: exim4 on TJENER does not accept system mails from Debian Edu clients
control: severity -1 important thanks On Fri, Jan 14, 2022 at 11:54:12AM +, Mike Gabriel wrote: > When a client on the Debian Edu network (.intern, 10.0.0.0/8) tries to send > system mails to postoffice.intern aka TJENER, then exim4 on TJENER won't > accept these SMTP connects without proper authentication: and how is this a serious bug in debian-edu-config? I've pointed you at the severity documentation several times already, I won't do it again here. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ If a monkey hoarded more bananas than it could eat, while most of the other monkeys starved, scientists would study that monkey to figure out what the heck was wrong with it. When humans do it, we put them on the cover of Forbes. signature.asc Description: PGP signature
Processed: Re: Bug#1003727: debian-edu-config: exim4 on TJENER does not accept system mails from Debian Edu clients
Processing control commands: > severity -1 important Bug #1003727 [debian-edu-config] debian-edu-config: exim4 on TJENER does not accept system mails from Debian Edu clients Severity set to 'important' from 'serious' -- 1003727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive
Hi On 2022-01-13 13:06:21, Paul Gevers wrote: > Hi, > > guestfs-tools was accepted in the archive, but it can't be (re)built > anywhere because it requires: > libcamomile-ocaml-dev- that isn't provided by > libcamomile-ocaml-dev. I have no idea how ocaml packages work, but this > needs to be fixed. The ocaml dependencies are installable again after a round of binNMUs. guestfs-tools however fails almost everywhere: https://buildd.debian.org/status/package.php?p=guestfs-tools Cheers -- Sebastian Ramacher
Bug#993699: marked as done (libxtrx: FTBFS with libsoapysdr 0.8)
Your message dated Fri, 14 Jan 2022 12:00:39 +
with message-id
and subject line Bug#993699: fixed in libxtrx 0.0.1+git20191219.98458ce-2
has caused the Debian Bug report #993699,
regarding libxtrx: FTBFS with libsoapysdr 0.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
993699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxtrx
Version: 0.0.1+git20191219.98458ce-1
Severity: important
Tags: ftbfs upstream
I am building rdeps of libsoapysdr in preparation of the transition to
version 0.8. This version has changed the SoapySDRDevice_setupStream()
function signature to return the SoapySDRStream directly rather than
through a pointer:
* Recommended keys to use in the args dictionary:
*- "WIRE" - format of the samples between device and host
* \endparblock
- * \return 0 for success or error code on failure
+ * \return the stream pointer or nullptr for failure
*/
-SOAPY_SDR_API int SoapySDRDevice_setupStream(SoapySDRDevice *device,
-SoapySDRStream **stream,
+SOAPY_SDR_API SoapySDRStream *SoapySDRDevice_setupStream(SoapySDRDevice
*device,
const int direction,
const char *format,
const size_t *channels,
This causes a build failure in libxtrx when building against the new
libsoapysdr. Upstream appears to have switched to the new call signature
in their current code, dropping compatibility with libsoapysdr 0.7 at
the same time. A way to be compatible with both would be using
preprocessor directives to discriminate between API version using
SOAPY_SDR_API_VERSION.
Log of the failed build:
/build/libxtrx-0.0.1+git20191219.98458ce/soapy/test_xtrx_soapy.c: In function
'main':
/build/libxtrx-0.0.1+git20191219.98458ce/soapy/test_xtrx_soapy.c:70:41:
warning: passing argument 2 of 'SoapySDRDevice_setupStream' makes integer from
pointer without a cast [-Wint-conversion]
70 | if (SoapySDRDevice_setupStream(sdr, , SOAPY_SDR_RX,
SOAPY_SDR_CF32, NULL, 0, NULL) != 0)
| ^
| |
| SoapySDRStream **
In file included from
/build/libxtrx-0.0.1+git20191219.98458ce/soapy/test_xtrx_soapy.c:1:
/usr/include/SoapySDR/Device.h:307:15: note: expected 'int' but argument is of
type 'SoapySDRStream **'
307 | const int direction,
| ~~^
/build/libxtrx-0.0.1+git20191219.98458ce/soapy/test_xtrx_soapy.c:70:52:
warning: passing argument 3 of 'SoapySDRDevice_setupStream' makes pointer from
integer without a cast [-Wint-conversion]
70 | if (SoapySDRDevice_setupStream(sdr, , SOAPY_SDR_RX,
SOAPY_SDR_CF32, NULL, 0, NULL) != 0)
|^~~~
||
|int
In file included from
/build/libxtrx-0.0.1+git20191219.98458ce/soapy/test_xtrx_soapy.c:1:
/usr/include/SoapySDR/Device.h:308:17: note: expected 'const char *' but
argument is of type 'int'
308 | const char *format,
| ^~
/build/libxtrx-0.0.1+git20191219.98458ce/soapy/test_xtrx_soapy.c:70:66:
warning: passing argument 4 of 'SoapySDRDevice_setupStream' from incompatible
pointer type [-Wincompatible-pointer-types]
70 | if (SoapySDRDevice_setupStream(sdr, , SOAPY_SDR_RX,
SOAPY_SDR_CF32, NULL, 0, NULL) != 0)
|
^~
| |
| char *
In file included from
/build/libxtrx-0.0.1+git20191219.98458ce/soapy/test_xtrx_soapy.c:1:
/usr/include/SoapySDR/Device.h:309:19: note: expected 'const size_t *' {aka
'const long unsigned int *'} but argument is of type 'char *'
309 | const size_t *channels,
| ~~^~~~
/build/libxtrx-0.0.1+git20191219.98458ce/soapy/test_xtrx_soapy.c:70:82:
warning: passing argument 5 of 'SoapySDRDevice_setupStream' makes integer from
pointer without a cast [-Wint-conversion]
70 | if (SoapySDRDevice_setupStream(sdr, , SOAPY_SDR_RX,
SOAPY_SDR_CF32, NULL, 0, NULL) != 0)
|
^~~~
|
|
|
Bug#1002827: marked as done (Should be in contrib; expects an installation of Steam)
Your message dated Fri, 14 Jan 2022 12:00:41 + with message-id and subject line Bug#1002827: fixed in rust-proton-call 3.0.1-2 has caused the Debian Bug report #1002827, regarding Should be in contrib; expects an installation of Steam 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.) -- 1002827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: proton-caller Severity: serious X-Debbugs-Cc: j...@joshtriplett.org While portions of Proton are Open Source (being based on the LGPLed Wine), proton-caller appears to specifically expect an installation of Steam. The description says "Simply configure your Steam and common directories", and the upstream documentation similarly talks about configuring the path to a Steam installation. - Josh -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages proton-caller depends on: ii libc6 2.33-1 ii libgcc-s1 11.2.0-13 proton-caller recommends no packages. proton-caller suggests no packages. --- End Message --- --- Begin Message --- Source: rust-proton-call Source-Version: 3.0.1-2 Done: Ben Westover We believe that the bug you reported is fixed in the latest version of rust-proton-call, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Westover (supplier of updated rust-proton-call package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 8 Jan 2022 01:25:26 CET Source: rust-proton-call Binary: librust-proton-call-dev proton-caller proton-caller-dbgsym Architecture: amd64 source Version: 3.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Ben Westover Description: librust-proton-call-dev - Run any Windows program through Valve's Proton - Rust source code proton-caller - Run any Windows program through Valve's Proton Closes: 1002827 Changes: rust-proton-call (3.0.1-2) unstable; urgency=medium . * Add manpages and examples * Move package to contrib and add steam to suggests (Closes: #1002827) Checksums-Sha256: 9ef6b4698255eb4b72db92f2627cbc37b3da40232505aa2b93d74902f4e9086d 11504 librust-proton-call-dev_3.0.1-2_amd64.deb a27afc34b787f1ac8c25a9251b58eea20bd3345253accbc0d26957d141d7816a 1568232 proton-caller-dbgsym_3.0.1-2_amd64.deb d80b42a1df53cfcd2ec4d55e33a3db9d0bd135c89cbd8b8c8d1e18ea9a7f09ba 212980 proton-caller_3.0.1-2_amd64.deb 1159145f6d7d6a03acb5d46baf9b87bed292f5c343ef18f55983fbab076366d3 8611 rust-proton-call_3.0.1-2_amd64.buildinfo 6e4e1b13d88a30477d6a8ca02170cc99afdac473fd4e4f2f227a137a33185c40 2429 rust-proton-call_3.0.1-2.dsc bb821f4e16e920ca58266bd760d73833b9a98abd23de3f0a7f11de145e7da2d5 10507 rust-proton-call_3.0.1.orig.tar.gz 7678beb6876d9a857bd7830465d1157fe69acd9bb8cc91fd7bdd16b0ec71f2c6 3220 rust-proton-call_3.0.1-2.debian.tar.xz Checksums-Sha1: 01aa85aa5ebe44937362da40075b3fb67b9a3b51 11504 librust-proton-call-dev_3.0.1-2_amd64.deb 47da455979b5901beb481f21ce8cdeebcc3994a4 1568232 proton-caller-dbgsym_3.0.1-2_amd64.deb 701bff408281017245ecf2d125d0f57677357f91 212980 proton-caller_3.0.1-2_amd64.deb 4e0f09f2f662df8411750782d58ca2cbe0bb2c59 8611 rust-proton-call_3.0.1-2_amd64.buildinfo dbf6615d07f7196de7cdf8e0a3d7bd982f751b05 2429 rust-proton-call_3.0.1-2.dsc 923a75cb3dd42a75a58983e56a0c96c4312df3c7 10507 rust-proton-call_3.0.1.orig.tar.gz 95d8b6790ea5c2eca67c8ad8d22fda1e21ff1b37 3220 rust-proton-call_3.0.1-2.debian.tar.xz Files: 0f0227e5d21849451174127e33734ee6 11504 contrib/otherosfs optional librust-proton-call-dev_3.0.1-2_amd64.deb ef82b406007ada3d795410b05e4b27fd 1568232 contrib/debug
Bug#1001541: marked as done (run-time shared lib not placed in package with proper name)
Your message dated Fri, 14 Jan 2022 12:00:09 + with message-id and subject line Bug#1001541: fixed in ecl 21.2.1+ds-2 has caused the Debian Bug report #1001541, regarding run-time shared lib not placed in package with proper name 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.) -- 1001541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ecl Version: 21.2.1+ds-1 Severity: critical X-Debbugs-Cc: jspri...@debian.org Hi, according to policy: "The run-time shared library must be placed in a package whose name changes whenever the SONAME of the shared library changes." https://www.debian.org/doc/debian-policy/ch-sharedlibs.html This breaks unrelated software, for example sagemath: $ sage -c "solve(x, x)" Traceback (most recent call last): File "/usr/share/sagemath/bin/sage-eval", line 10, in eval(compile(s,'','exec')) File "", line 1, in File "/usr/lib/python3/dist-packages/sage/symbolic/relation.py", line 1044, in solve return _solve_expression(f, x, explicit_solutions, multiplicities, to_poly_solve, solution_dict, algorithm, domain) File "/usr/lib/python3/dist-packages/sage/symbolic/relation.py", line 1283, in _solve_expression m = ex._maxima_() File "sage/symbolic/expression.pyx", line 1015, in sage.symbolic.expression.Expression._maxima_ (build/cythonized/sage/symbolic/expression.cpp:7931) File "sage/structure/sage_object.pyx", line 680, in sage.structure.sage_object.SageObject._interface_ (build/cythonized/sage/structure/sage_object.c:5480) File "sage/misc/lazy_import.pyx", line 329, in sage.misc.lazy_import.LazyImport.__getattr__ (build/cythonized/sage/misc/lazy_import.c:3870) File "sage/misc/lazy_import.pyx", line 191, in sage.misc.lazy_import.LazyImport.get_object (build/cythonized/sage/misc/lazy_import.c:2435) File "sage/misc/lazy_import.pyx", line 228, in sage.misc.lazy_import.LazyImport._get_object (build/cythonized/sage/misc/lazy_import.c:2842) File "sage/misc/lazy_import.pyx", line 224, in sage.misc.lazy_import.LazyImport._get_object (build/cythonized/sage/misc/lazy_import.c:2704) File "/usr/lib/python3/dist-packages/sage/interfaces/maxima_lib.py", line 92, in from sage.libs.ecl import EclObject, ecl_eval ImportError: libecl.so.20.4: cannot open shared object file: No such file or directory -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ecl depends on: ii gcc 4:11.2.0-2 ii libatomic-ops-dev 7.6.12-1 ii libc6 2.32-5 ii libffi-dev3.4.2-3 ii libffi8 3.4.2-3 ii libgc-dev 1:8.0.6-1.1 ii libgc11:8.0.6-1.1 ii libgmp-dev2:6.2.1+dfsg-3 ii libgmp10 2:6.2.1+dfsg-3 ii libncurses-dev [libncurses5-dev] 6.3-1 ii libncurses5-dev 6.3-1 ecl recommends no packages. Versions of packages ecl suggests: pn ecl-doc pn slime -- no debconf information --- End Message --- --- Begin Message --- Source: ecl Source-Version: 21.2.1+ds-2 Done: Tobias Hansen We believe that the bug you reported is fixed in the latest version of ecl, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Hansen (supplier of updated ecl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 10 Jan 2022 22:33:42 + Source: ecl Binary: ecl ecl-dbgsym libecl-dev libecl21.2 libecl21.2-dbgsym Architecture: source amd64 Version: 21.2.1+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Common Lisp Team Changed-By: Tobias Hansen Description:
Processed: debian-edu-config: exim4 on TJENER does not accept system mails from Debian Edu clients
Processing control commands: > found -1 2.12.15 Bug #1003727 [debian-edu-config] debian-edu-config: exim4 on TJENER does not accept system mails from Debian Edu clients Marked as found in versions debian-edu-config/2.12.15. -- 1003727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003678: marked as done (sqlite3 breaks crowdsec autopkgtest: invalid type \"INTEGER\" for column)
Your message dated Fri, 14 Jan 2022 11:48:44 + with message-id and subject line Bug#1003678: fixed in golang-github-facebook-ent 0.5.4-3 has caused the Debian Bug report #1003678, regarding sqlite3 breaks crowdsec autopkgtest: invalid type \"INTEGER\" for column 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.) -- 1003678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sqlite3, crowdsec Control: found -1 sqlite3/3.37.2-1 Control: found -1 crowdsec/1.0.9-3 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of sqlite3 the autopkgtest of crowdsec fails in testing when that autopkgtest is run with the binary packages of sqlite3 from unstable. It passes when run with only packages from testing. In tabular form: passfail sqlite3from testing3.37.2-1 crowdsec from testing1.0.9-3 versioned deps [0] from testingfrom unstable 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 sqlite3 to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from sqlite3/3.37.2-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=sqlite3 https://ci.debian.net/data/autopkgtest/testing/amd64/c/crowdsec/18271072/log.gz === RUN TestSimulatedAlert time="2022-01-12T20:11:40Z" level=info msg="Creating new API server" - [Wed, 12 Jan 2022 20:11:41 UTC] "POST /v1/watchers HTTP/1.1 201 98.133294ms "crowdsec-test/" " time="2022-01-12T20:11:41Z" level=fatal msg="unable to create new database client: failed creating schema resources: sql/schema: invalid type \"INTEGER\" for column \"events_count\"" FAILgithub.com/crowdsecurity/crowdsec/pkg/apiserver 0.130s ? github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers [no test files] ? github.com/crowdsecurity/crowdsec/pkg/apiserver/controllers/v1 [no test files] ? github.com/crowdsecurity/crowdsec/pkg/apiserver/middlewares/v1 [no test files] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: golang-github-facebook-ent Source-Version: 0.5.4-3 Done: Cyril Brulebois We believe that the bug you reported is fixed in the latest version of golang-github-facebook-ent, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated golang-github-facebook-ent package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Jan 2022 12:27:21 +0100 Source: golang-github-facebook-ent Architecture: source Version: 0.5.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Cyril Brulebois Closes: 1003678 Changes: golang-github-facebook-ent (0.5.4-3) unstable; urgency=medium . * Avoid issues due to recent changes in SQLite related on how it deals with letter case: convert type names to lowercase before testing them against expected values. Thanks to László Böszörményi for the explanations and the patch! (Closes: #1003678). Checksums-Sha1: 6b732dadd2dbe026dc3943ba20a9049048294564 2813 golang-github-facebook-ent_0.5.4-3.dsc 4caf65f12bb2b361d9ffa70ec162ae72b41a1c66 3680 golang-github-facebook-ent_0.5.4-3.debian.tar.xz 295ba5808c298c2433105c8ffc0e692a6ab1950f
Bug#1003696: marked as done (prosody: CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket interface)
Your message dated Fri, 14 Jan 2022 11:33:47 + with message-id and subject line Bug#1003696: fixed in prosody 0.11.12-1 has caused the Debian Bug report #1003696, regarding prosody: CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket interface 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.) -- 1003696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prosody Version: 0.11.11-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for prosody. CVE-2022-0217[0]: | Unauthenticated Remote Denial of Service Attack in the WebSocket | interface 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-2022-0217 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0217 [1] https://prosody.im/security/advisory_20220113/ [2] https://www.openwall.com/lists/oss-security/2022/01/13/3 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: prosody Source-Version: 0.11.12-1 Done: Victor Seva We believe that the bug you reported is fixed in the latest version of prosody, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Victor Seva (supplier of updated prosody package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Jan 2022 12:12:44 +0100 Source: prosody Architecture: source Version: 0.11.12-1 Distribution: unstable Urgency: high Maintainer: Debian XMPP Maintainers Changed-By: Victor Seva Closes: 1003696 Changes: prosody (0.11.12-1) unstable; urgency=high . * New upstream version 0.11.12 addressing security issue - https://prosody.im/security/advisory_20220113/ + fixes CVE-2022-0217 (Closes: #1003696) Checksums-Sha1: 8f504db0b197ff744f172764e9a02e876f192ee6 1840 prosody_0.11.12-1.dsc 64c918439c2df130204dcd86398832cb7a481eb3 439656 prosody_0.11.12.orig.tar.gz 212f49e93ba3009bfe78509a0d9c37c7fb6151b9 28664 prosody_0.11.12-1.debian.tar.xz 5439e97e6ad896543d58a2ac63c8e93c7e2fa821 6686 prosody_0.11.12-1_amd64.buildinfo Checksums-Sha256: 3bec68f7614d83d59fcdb8c2090932e845d06bae3e3834d61dd835fb7b8653f1 1840 prosody_0.11.12-1.dsc 56cd52d820f5b3ed37e02d8a2577aa064bbc04db8e87fd18a6020eba0c10560d 439656 prosody_0.11.12.orig.tar.gz 74b470e74da60d637319fb83f5418794ba79e32a08149caf397687f62afd3d57 28664 prosody_0.11.12-1.debian.tar.xz 9b1d08f4ff70f005b5e06e0ce1e4a3b5b67d2d2e1f129bcdd2651876a687ba28 6686 prosody_0.11.12-1_amd64.buildinfo Files: 8bfa03dd20364d90e036fc3a3ef6567f 1840 net optional prosody_0.11.12-1.dsc 64a99571a5de84ace24d8142a1556d68 439656 net optional prosody_0.11.12.orig.tar.gz 232365b3ab53301cba536ff2801d0394 28664 net optional prosody_0.11.12-1.debian.tar.xz 2a0103ce61d41b031c21a656e876104b 6686 net optional prosody_0.11.12-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEE3S3PbKiJPTunbGuNsViYiXJxmOAFAmHhW/8RHHZzZXZhQGRl Ymlhbi5vcmcACgkQsViYiXJxmOC4Cgf+Jnle9mSdm7UVcGloRwqNQsHG9+hsXFWw ADd57vl9gfT5R4N94dabnhpNIFWex8pc+z4yziAqD7kKaQiFTpR/cppN0uAqTki4 eMdv1MSXN5JcYTV4vzet5xozDfX1oN7Oavswe1Q45GK2i585d0+3tIuRRQmbDOY/ fWPnFkLk+L/Hx9b0q+0ZYJfTocEOgSC2NkB2Mt98nKsz9fu9EQ/sx33fi6hZCgNF DTBwSya70AizinoMs4A/A2OVs7eEySj23HskXTbZ3ps8Phj8SY5AV8lGEGxfLDX7 cfI8O4m3B3CKAZCGI0TnpJkSeh6VQcHIfkaNLK8DHadjMADFmTL/wg== =qbK3 -END PGP SIGNATURE End Message ---
Processed: Bug#1003678 marked as pending in golang-github-facebook-ent
Processing control commands: > tag -1 pending Bug #1003678 [src:golang-github-facebook-ent] sqlite3 breaks crowdsec autopkgtest: invalid type \"INTEGER\" for column Added tag(s) pending. -- 1003678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003678: marked as pending in golang-github-facebook-ent
Control: tag -1 pending Hello, Bug #1003678 in golang-github-facebook-ent 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/go-team/packages/golang-github-facebook-ent/-/commit/f6323ba2a835ebbd9e398e24ae665c129d851292 Fix SQLite type testing (Closes: #1003678). Thanks to László Böszörményi! (this message was generated automatically) -- Greetings https://bugs.debian.org/1003678
Bug#1003696: prosody: CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket interface
Hi folks, This is a link to the upstream patch for our 0.11.x series: https://hg.prosody.im/0.11/raw-rev/783056b4e448 Let me know if you have any questions! Regards, Matthew (Prosody developer)
Bug#1000577: marked as done (abyss: autopkgtest regression on armhf and i386: Floating point exception)
Your message dated Fri, 14 Jan 2022 09:03:32 + with message-id and subject line Bug#1000577: fixed in abyss 2.3.4+dfsg-1 has caused the Debian Bug report #1000577, regarding abyss: autopkgtest regression on armhf and i386: Floating point exception 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.) -- 1000577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abyss Version: 2.3.3-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of abyss the autopkgtest of abyss fails in testing when that autopkgtest is run with the binary packages of abyss from unstable on armhf and i386. It passes when run with only packages from testing. In tabular form: passfail abyss from testing2.3.3-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Seems like a 32 bit issue? Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=abyss https://ci.debian.net/data/autopkgtest/testing/armhf/a/abyss/16976314/log.gz abyss-stack-size 65536 abyss-bloom-dbg -k25 -q3 -b1G -j2 test-data/reads1.fastq test-data/reads2.fastq > test-1.fa Running with max stack size of 65536 KB: abyss-bloom-dbg -k25 -q3 -b1G -j2 test-data/reads1.fastq test-data/reads2.fastq AdjList-k25 -m0 --dot test-1.fa >test-1.dot abyss-rresolver-short -b1G -j2 -k25 \ -h test-1-rr --dot -c test-1-rr.fa -g test-1-rr.dot test-1.fa test-1.dot test-data/reads1.fastq test-data/reads2.fastq make: *** [/usr/bin/abyss-pe:585: test-1-rr.dot] Floating point exception autopkgtest [23:11:23]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: abyss Source-Version: 2.3.4+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of abyss, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated abyss package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Jan 2022 09:36:02 +0100 Source: abyss Architecture: source Version: 2.3.4+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1000577 Changes: abyss (2.3.4+dfsg-1) unstable; urgency=medium . * Upstream declares that only 64bit architectures are supported (https://github.com/bcgsc/abyss/issues/384) thus restricting architectures accordingly Closes: #1000577 * Exclude i386 from salsa-ci * New upstream version * Add missing build dependency on dh addon. * Exclude external files from RResolver/btllib/external/sdsl-lite Checksums-Sha1: fafdd846ef83c929717b1d38f0aefc3bec98f56d 2285 abyss_2.3.4+dfsg-1.dsc 88a9973a45fcf738ce7d6b786175c2aceb0824df 1514956 abyss_2.3.4+dfsg.orig.tar.xz b850e146dcd2e880feb2dfc3608a0a3a36f22971 1497176 abyss_2.3.4+dfsg-1.debian.tar.xz ab72f40d72ad889fe8331f66d0fa6ede9958aed8 9022 abyss_2.3.4+dfsg-1_amd64.buildinfo Checksums-Sha256: 09eb2ca25b6f9e8dcfd9af22848e3e3dfb1201b20ad89122afef2dcf65f364dc 2285 abyss_2.3.4+dfsg-1.dsc b21e05b230f2802b61767dd814992a416574009f4009896385c701e959dfd129 1514956 abyss_2.3.4+dfsg.orig.tar.xz 21ad75ce8470ebaa8d3c79330abc0522554415f6e53a69da05ff0226b05d8927 1497176 abyss_2.3.4+dfsg-1.debian.tar.xz 5988c4db7226eb05597a7f87a51caa0f3d1a826298d780dcedc7dde9e9cbbe7c 9022 abyss_2.3.4+dfsg-1_amd64.buildinfo Files: 5900ba2f975f06a5d67a6498cf739cf2 2285 science optional abyss_2.3.4+dfsg-1.dsc d7585169d452972212ac7eb7bd4a3db7 1514956 science optional abyss_2.3.4+dfsg.orig.tar.xz
Bug#1003717: xserver-xorg-video-nouveau: ttm buffer eviction failed + failed to load nvd9_fuc084 (regression db11-db10)
Package: xserver-xorg-video-nouveau Version: 1:1.0.17-1 Severity: serious Justification: serious Hello, This behaviour started with the upgrade from debian 10 to debian 11, (regression) and has gotten worse since, the graphical interface locks up on frequent base for a long time, (more than once per hour, locking up from 10minutes to more than a hour, rebooting with a hard reset) rendering the laptop useless it might be related to the following bugs: #990662 #989705 #903426 the errors from dmesg, * [TTM] Buffer eviction failed * firmware: failed to load nouveau/nvd9_fuc084 (maybe onrelated?) a file is attached with more background. hth, Wim -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 5 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Dec 16 18:08 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 5.10.0-10-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.84-1 (2021-12-08) Xorg X server log files on system: -- -rw-r--r-- 1 wim wim 44389 Mar 27 2019 /home/wim/.local/share/xorg/Xorg.2.log -rw-r--r-- 1 wim wim 42624 Nov 12 2019 /home/wim/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 wim wim 47577 Nov 12 2019 /home/wim/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 63438 Nov 23 11:31 /var/log/Xorg.1.log -rw-r--r-- 1 root root 43325 Jan 14 09:22 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [36.852] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [36.852] Build Operating System: linux Debian [36.852] Current Operating System: Linux lolifant 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 [36.852] Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-10-amd64 root=/dev/mapper/lolifant--vg-root ro quiet [36.852] Build Date: 16 December 2021 05:08:23PM [36.852] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support) [36.852] Current version of pixman: 0.40.0 [36.852]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [36.852] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [36.852] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 14 09:05:05 2022 [36.956] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [36.989] (==) No Layout section. Using the first Screen section. [36.989] (==) No screen section available. Using defaults. [36.989] (**) |-->Screen "Default Screen Section" (0) [36.989] (**) | |-->Monitor "" [36.996] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [36.996] (==) Automatically adding devices [36.996] (==) Automatically enabling devices [36.996] (==) Automatically adding GPU devices [36.996] (==) Max clients allowed: 256, resource mask: 0x1f [37.035] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [37.035]Entry deleted from font path. [37.060] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [37.060] (==) ModulePath set to "/usr/lib/xorg/modules" [37.060] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [37.060] (II) Loader magic: 0x557d2d752e40 [37.060] (II) Module ABI versions: [37.060]X.Org ANSI C Emulation: 0.4 [37.060]X.Org Video Driver: 24.1 [37.060]X.Org XInput driver : 24.1 [37.060]X.Org Server Extension : 10.0 [37.061] (++) using VT number 7 [37.061] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [37.062] (II) xfree86: Adding drm device (/dev/dri/card0) [37.072] (--) PCI:*(1@0:0:0) 10de:06eb:1028:024f rev 161, Mem @ 0xf500/16777216, 0xe000/268435456, 0xf200/33554432, I/O @ 0xdf00/128, BIOS @ 0x/131072 [37.079] (II) LoadModule: "glx" [37.103] (II)
