Bug#1033517: yt-dlp: mpv fails to work with yt-dlp, after yt-dlp upgrade (uncoordinated API change?)
Severity: important Howdy On Sun, 26 Mar 2023, Francesco Poli (wintermute) wrote: Package: yt-dlp Version: 2023.03.04-1 Severity: grave Justification: renders package unusable This doesn't actually render the package unusuable, on the contrary it works around throttling. Instead, it hinders compatibility with another package. Hello and thanks for maintaining this useful package! After upgrading from yt-dlp/2023.02.17-1 to yt-dlp/2023.03.04-1, mpv is no longer able to use yt-dlp to play YouTube videos: This actually "only" happens when you use bestvideo, other formats such as '22' still work. Eg, `mpv --ytdl-format=22 https://www.youtube.com/watch?v=RZAq-_gz_W8` What's wrong? Did yt-dlp change API? If this is the case, the new version of yt-dlp Debian package should wait for an updated mpv Debian package, before migrating to testing... Not API, but yt-dlp made a change to solve widespread, severe throttling, to the point of being unusable really. I saw one report that had it going at an average speed of 30kb/s. mpv didn't cope well, but that has been fixed upstream in subsequent[0] commits[1]. [0]: https://github.com/mpv-player/mpv/commit/94c189dae76ba280d9883b16346c3dfb9720687e [1]: https://github.com/mpv-player/mpv/commit/362256edbc4f95c63e69c1fa8c8dce9cc6c44288 Or is it a bug in yt-dlp that shows up only when yt-dlp is called by mpv behind the scenes, and not when it is directly invoked from the user's command line? It's not really a bug in yt-dlp, but instead in mpv. Please fix this issue as soon as possible, or revert to the previous version (yt-dlp/2023.02.17-1), until this behavior has been properly investigated and solved. And here lies the problem. Seemingly one of the big fixes in 2023.03.03 is a workaround for the aforementioned throttling, to revert would mean to make yt-dlp unusably slow. But to leave it as is, mpv can't directly utilize yt-dlp with the default quality option. If we weren't so close to the freeze I'd say the right option would be to simply patch the yt-dlp hook in mpv and move on, but that's not precisely an option anymore either. So to sum up, at least for things I can do: 1. Break yt-dlp integration with mpv under the default options for one specific (granted, highly popular) site, but usable by itself and other tools. 2. Revert and break the ability to use yt-dlp to watch a video without first downloading, for all tools. Reverting also wouldn't cover backporting new releases to bookworm eventually either. Thanks for your time and patience! Regards, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Processed: bug 1033480 is forwarded to https://gitlab.com/gitlab-org/gitlab-runner/-/issues/30859
Processing commands for cont...@bugs.debian.org: > forwarded 1033480 https://gitlab.com/gitlab-org/gitlab-runner/-/issues/30859 Bug #1033480 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner: FTBFS on 32 bit archs: src/gitlab.com/gitlab-org/gitlab-runner/common/buildtest/masking.go:48:32: cannot use math.MaxInt64 (untyped int constant 9223372036854775807) as int value in argument to buf.Bytes (overflows) Set Bug forwarded-to-address to 'https://gitlab.com/gitlab-org/gitlab-runner/-/issues/30859'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1033480
Processing commands for cont...@bugs.debian.org: > tags 1033480 + upstream Bug #1033480 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner: FTBFS on 32 bit archs: src/gitlab.com/gitlab-org/gitlab-runner/common/buildtest/masking.go:48:32: cannot use math.MaxInt64 (untyped int constant 9223372036854775807) as int value in argument to buf.Bytes (overflows) Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: zsnes: diff for NMU version 1.510+bz2-10.2
Processing control commands: > tags 1031963 + patch Bug #1031963 [src:zsnes] FTBFS: error: ISO C++17 does not allow dynamic exception specifications Added tag(s) patch. > tags 1031963 + pending Bug #1031963 [src:zsnes] FTBFS: error: ISO C++17 does not allow dynamic exception specifications Added tag(s) pending. -- 1031963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031963: zsnes: diff for NMU version 1.510+bz2-10.2
Control: tags 1031963 + patch Control: tags 1031963 + pending Dear maintainer, I've prepared an NMU for zsnes (versioned as 1.510+bz2-10.2) and uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru zsnes-1.510+bz2/debian/changelog zsnes-1.510+bz2/debian/changelog --- zsnes-1.510+bz2/debian/changelog 2021-05-14 15:46:32.0 +0300 +++ zsnes-1.510+bz2/debian/changelog 2023-03-26 23:50:58.0 +0300 @@ -1,3 +1,11 @@ +zsnes (1.510+bz2-10.2) unstable; urgency=medium + + * Non-maintainer upload. + * Build with -std=gnu++14 to workaround FTBFS with gcc 11. +(Closes: #1031963) + + -- Adrian Bunk Sun, 26 Mar 2023 23:50:58 +0300 + zsnes (1.510+bz2-10.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru zsnes-1.510+bz2/debian/rules zsnes-1.510+bz2/debian/rules --- zsnes-1.510+bz2/debian/rules 2021-05-05 23:23:56.0 +0300 +++ zsnes-1.510+bz2/debian/rules 2023-03-26 23:50:58.0 +0300 @@ -13,7 +13,7 @@ DPKG_EXPORT_BUILDFLAGS=1 include /usr/share/dpkg/buildflags.mk -CFLAGS += $(CPPFLAGS) +CFLAGS += $(CPPFLAGS) -std=gnu++14 CXXFLAGS += $(CPPFLAGS) export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed -lpthread
Bug#1031315: marked as done (libjpeg9: libjpeg.so.9* missing)
Your message dated Sun, 26 Mar 2023 20:42:56 +
with message-id
and subject line Bug#1031315: fixed in libjpeg9 1:9e-1
has caused the Debian Bug report #1031315,
regarding libjpeg9: libjpeg.so.9* missing
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.)
--
1031315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjpeg9
Version: 1:9d-1.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
/usr/lib/*/{libjpeg.so.9,libjpeg.so.9.4.0} are missing in the package, making
it completely unusable:
$ dpkg -L libjpeg9
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libjpeg9
/usr/share/doc/libjpeg9/README.gz
/usr/share/doc/libjpeg9/changelog.Debian.gz
/usr/share/doc/libjpeg9/changelog.gz
/usr/share/doc/libjpeg9/copyright
This issue may related to changes in the build system. While libjpeg.so.9*
appear in the old version 1:9d-1, a rebuilt package of version 1:9d-1 on a
latest unstable Debian system also lacks libjpeg.so.9*.
The following lines appeared in the latest build log on buildd[1]:
checking whether the x86_64-linux-gnu-gcc linker (/usr/bin/ld -m elf_x86_64)
supports shared libraries... ./configure: line 11202: : supported targets:.*
elf: command not found
no
which corresponds to the following lines in the regenerated `configure':
if $LD --help 2>&1 | $EGREP ': supported targets:.* elf' > /dev/null \
&& test no = "$tmp_diet"
It can be found from `config.status' that $EGREP is empty, which may cause this
issue:
EGREP=''
I didn't figure out why $EGREP is empty, but adding the following line into
debian/rules will generate a normal package with libjpeg.so.9* included:
diff -Nru libjpeg9-9d/debian/rules libjpeg9-9d/debian/rules
--- libjpeg9-9d/debian/rules2023-02-15 03:52:51.0 +0800
+++ libjpeg9-9d/debian/rules2022-11-04 03:14:38.0 +0800
@@ -18,8 +18,6 @@
CFLAGS += -O2
endif
-export EGREP = grep -E
-
export AUTOMAKE = automake-1.16
export ACLOCAL = aclocal-1.16
export AUTOHEADER = true
[1]
https://buildd.debian.org/status/fetch.php?pkg=libjpeg9=amd64=1%3A9d-1.1=1667678775=0
Regards,
Roy Clark
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: libjpeg9
Source-Version: 1:9e-1
Done: Bill Allombert
We believe that the bug you reported is fixed in the latest version of
libjpeg9, 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 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bill Allombert (supplier of updated libjpeg9 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 26 Mar 2023 18:58:30 +0200
Source: libjpeg9
Architecture: source
Version: 1:9e-1
Distribution: unstable
Urgency: medium
Maintainer: Bill Allombert
Changed-By: Bill Allombert
Closes: 998986 1031315
Changes:
libjpeg9 (1:9e-1) unstable; urgency=medium
.
* New upstream release.
- Rebuild with fix for egrep. Thanks Roy Clark. Closes: #1031315
* debian/rules; add missing targets build-{arch,indep}.
Thanks Markos Talau. Closes: #998986.
* debian/watch: update.
* debian/control:
- Bump Standards-Version to 4.6.1.
- Build-Depends on debhelper-compat (= 13)
- Add Rules-Requires-Root: no
- Remove Build-Depends on autotools-dev, dh-autoreconf
* debian/compat: removed
* debian/extra/Makefile: update for Rules-Requires-Root
* debian/copyright: use https and update URL
Checksums-Sha1:
aae66b880c5bca27b8f553022d58709419d4a4e1 1824 libjpeg9_9e-1.dsc
ed959b5f3551bc965fe6d0aff6ca48a26f8ce346
Bug#1033531: bdebstrap: autopkgtest regression: ubuntu-keyring not available in testing
Source: bdebstrap Version: 0.5.0-1 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, one of the tests depends on ubuntu-keyring which was removed from testing on 2019-07-24 and hence your test fails in testing. [Release Team hat on] Because of the timing of this bug (during the hard freeze) and because it doesn't seem to indicate functionality failure of this package, I have marked it as bookworm-ignore. However, if done reasonably soon, we'll unblock an upload fixing this issue. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1029944: A couple of patches
Actually, it wasn't much more work to get all the failing tests to
pass. Version 2 of the patches attached.
J.
From 1f6b8e55807794c2466603116ae8ba9e6a50919a Mon Sep 17 00:00:00 2001
From: Jeremy Sowden
Date: Sun, 26 Mar 2023 14:49:09 +0100
Subject: [PATCH v2 1/2] Use ipv6 lookback address if ipv4 is not available
Note that the `bind_local` parameter of `spawn_server_addr` is now
ignored. It wasn't actually possible to set `hn_addr`, so passing `0`
would never have worked anyway.
---
test/common/child.c | 160 +---
test/common/child.h | 4 ++
test/utils.c| 5 +-
3 files changed, 143 insertions(+), 26 deletions(-)
diff --git a/test/common/child.c b/test/common/child.c
index 872fbdaddf4f..5c480def6c44 100644
--- a/test/common/child.c
+++ b/test/common/child.c
@@ -43,6 +43,10 @@
#include
#include
+#include
+#include
+#include
+
#include "ne_socket.h"
#include "ne_utils.h"
#include "ne_string.h"
@@ -50,14 +54,23 @@
#include "tests.h"
#include "child.h"
+#ifndef NI_MAXHOST
+#define NI_MAXHOST 1025
+#endif
+
static pid_t child = 0;
int clength;
-static struct in_addr lh_addr, hn_addr;
-
static int have_lh_addr;
+static union {
+ struct sockaddr_in in;
+ struct sockaddr_in6 in6;
+} lh_sockaddr;
+static int lh_family = AF_UNSPEC;
+static char lh_name[NI_MAXHOST];
+
const char *want_header = NULL;
got_header_fn got_header = NULL;
char *local_hostname = NULL;
@@ -72,13 +85,98 @@ char *local_hostname = NULL;
int lookup_localhost(void)
{
-/* this will break if a system is set up so that `localhost' does
- * not resolve to 127.0.0.1, but... */
-lh_addr.s_addr = inet_addr("127.0.0.1");
+struct ifaddrs *ifaddr;
+
+if (have_lh_addr)
+return OK;
+
+if (getifaddrs() == -1)
+goto err_use_ipv4;
+
+for (struct ifaddrs *ifa = ifaddr; ifa != NULL; ifa = ifa->ifa_next) {
+if (ifa->ifa_addr == NULL)
+continue;
+
+if (strcmp(ifa->ifa_name, "lo") != 0)
+continue;
+
+if (ifa->ifa_addr->sa_family != AF_INET &&
+ifa->ifa_addr->sa_family != AF_INET6)
+continue;
+
+if (getnameinfo(ifa->ifa_addr,
+ifa->ifa_addr->sa_family == AF_INET
+? sizeof(struct sockaddr_in)
+: sizeof(struct sockaddr_in6),
+lh_name, sizeof lh_name,
+NULL, 0,
+NI_NUMERICHOST))
+continue;
+
+memcpy(_sockaddr, ifa->ifa_addr,
+ ifa->ifa_addr->sa_family == AF_INET
+ ? sizeof(lh_sockaddr.in)
+ : sizeof(lh_sockaddr.in6));
+
+lh_family = ifa->ifa_addr->sa_family;
+
+if (lh_family == AF_INET)
+break;
+}
+
+freeifaddrs(ifaddr);
+
+err_use_ipv4:
+
+if (lh_family == AF_UNSPEC) {
+lh_family = AF_INET;
+strcpy(lh_name, "127.0.0.1");
+lh_sockaddr.in.sin_family = lh_family;
+lh_sockaddr.in.sin_addr.s_addr = inet_addr(lh_name);
+}
+
have_lh_addr = 1;
return OK;
}
+int
+get_lh_family(void)
+{
+if (!have_lh_addr)
+lookup_localhost();
+
+return lh_family;
+}
+
+const char *
+get_lh_addr(void)
+{
+if (!have_lh_addr)
+lookup_localhost();
+
+return lh_name;
+}
+
+ne_inet_addr *
+get_lh_inet_addr(void)
+{
+ne_iaddr_type type;
+unsigned char *raw;
+
+if (!have_lh_addr)
+lookup_localhost();
+
+if (lh_family == AF_INET) {
+type = ne_iaddr_ipv4;
+raw = (unsigned char *) _sockaddr.in.sin_addr.s_addr;
+} else {
+type = ne_iaddr_ipv6;
+raw = lh_sockaddr.in6.sin6_addr.s6_addr;
+}
+
+return ne_iaddr_make(type, raw);
+}
+
int lookup_hostname(void)
{
char buf[BUFSIZ];
@@ -101,19 +199,26 @@ int lookup_hostname(void)
return OK;
}
-static int do_listen(struct in_addr addr, int port)
+static int do_listen(int port)
{
-int ls = socket(AF_INET, SOCK_STREAM, 0);
-struct sockaddr_in saddr = {0};
+int ls = socket(lh_family, SOCK_STREAM, 0);
+struct sockaddr *saddr;
+socklen_t saddrlen;
int val = 1;
setsockopt(ls, SOL_SOCKET, SO_REUSEADDR, (void *), sizeof(int));
-
-saddr.sin_addr = addr;
-saddr.sin_port = htons(port);
-saddr.sin_family = AF_INET;
-if (bind(ls, (struct sockaddr *), sizeof(saddr))) {
+if (lh_family == AF_INET) {
+ lh_sockaddr.in.sin_port = htons(port);
+ saddr = (struct sockaddr *) _sockaddr.in;
+ saddrlen = sizeof(lh_sockaddr.in);
+} else {
+ lh_sockaddr.in6.sin6_port = htons(port);
+ saddr = (struct sockaddr *) _sockaddr.in6;
+ saddrlen = sizeof(lh_sockaddr.in6);
+}
+
+if (bind(ls, saddr, saddrlen)) {
printf("bind failed: %s\n", strerror(errno));
return -1;
}
@@ -171,7 +276,7 @@ static int close_socket(ne_socket *sock)
}
/* This runs as the child process.
Bug#1033530: auto-apt-proxy: autopkgtest regression: squid-deb-proxy not available in testing
Source: auto-apt-proxy Version: 14 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, one of the tests depends on squid-deb-proxy which was removed from testing on 2022-10-19 and hence your test fails in testing (and it's in principle too late to fix squid-deb-proxy in bookworm). [Release Team hat on] Because of the timing of this bug (during the hard freeze) and because it doesn't seem to indicate functionality failure of this package, I have marked it as bookworm-ignore. However, if done reasonably soon, we'll unblock an upload fixing this issue. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Hi Graham, Am Sonntag, dem 26.03.2023 um 19:28 +0200 schrieb Graham Inggs: > Hi Markus > > On Sun, 26 Mar 2023 at 16:34, Markus Koschany wrote: > > 1. There is no transition needed because only shrinksafe is affected by the > > new > > rhino version. > How did you determine this? Rhino 1.7.14 was mostly API compatible meaning I only had to fix an issue in closure-compiler. All other packages can be built from source without modifications. I didn't find any other runtime / ABI issues so far. > > > 2. shrinksafe has no reverse-dependencies > > That is true, but src:dojo has ledgersmb and tt-rss as reverse-dependencies. I used codesearch.debian.net and found only documentation or other minor references of shrinksafe in affected packages. https://codesearch.debian.net/search?q=shrinksafe=1 Since all Java tests in dojo pass after the rebuild and almost all of the code in dojo is Javascript anyway, I don't see how ledgersmb and tt-rss can be affected by the new rhino version. Wouldn't those packages depend on rhino in some way? To me it seems rhino is only required to build shrinksafe which can be used for compressing Javascript files. But maybe the dojo maintainers can chime in here. Regards, Markus signature.asc Description: This is a digitally signed message part
Processed: apbs: autopkgtest regression: apbs_tester.py': [Errno 2] No such file or directory
Processing control commands: > found -1 3.0.0+dfsg1-3 Bug #1033528 [src:apbs] apbs: autopkgtest regression: apbs_tester.py': [Errno 2] No such file or directory Marked as found in versions apbs/3.0.0+dfsg1-3. -- 1033528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033528: apbs: autopkgtest regression: apbs_tester.py': [Errno 2] No such file or directory
Source: apbs
Version: 3.4.1-5
Severity: serious
Tags: bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Control: found -1 3.0.0+dfsg1-3
Dear maintainer(s),
Your package has an autopkgtest, great. However, it started to fail in
testing (October 2022). As it started to fail in stable around the same
time, I rather expect some external dependency, so I marked it as
bookworm-ignore, but please investigate.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/a/apbs/32295202/log.gz
autopkgtest [18:11:22]: test test-apbs: [---
cp: cannot stat '/usr/share/apbs/{tests,examples}': No such file or
directory
/tmp/autopkgtest-lxc.nft4zx67/downtmp/build.RPN/src/debian/tests/test-apbs:
2: cd: can't cd to
/tmp/autopkgtest-lxc.nft4zx67/downtmp/autopkgtest_tmp/tests
python3: can't open file
'/tmp/autopkgtest-lxc.nft4zx67/downtmp/build.RPN/src/apbs_tester.py':
[Errno 2] No such file or directory
autopkgtest [18:11:22]: test test-apbs: ---]
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1032221: marked as done (cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work)
Your message dated Sun, 26 Mar 2023 18:48:59 + with message-id and subject line Bug#1032221: fixed in cryptsetup 2:2.6.1-3~deb12u1 has caused the Debian Bug report #1032221, regarding cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work 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.) -- 1032221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cryptsetup Version: 2:2.6.1-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: kai.weber+deb...@glorybox.de Dear Maintainer, Today's upgrade triggered a rebuild of the initramfs. After a reboot I can no longer login to my system. Using an older kernel worked. This ist the error message: Please unlock disk nvme0n1p3_crypt: libgcc_s.so.1 must be installed for pthread_exit to work Aborted cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or options? Some investigations: - update-initramfs does indeed not copy libpthread.so or libgcc_s.so - none of the binaries copied during the update seem to depend on those libraries - attached is the debug output I added to the copy_exec function (echo "$src $x" >> /tmp/dependencies.log) Doing some research I found an older bug #950254 that helped me debugging the issue -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/vmlinuz-6.1.0-4-amd64 root=/dev/mapper/dummy--vg-root ro quiet -- /etc/crypttab nvme0n1p3_crypt UUID=e9aff144-a836-49d6-8640-01f4b7c3bb8b none luks,discard -- /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # systemd generates mount units based on this file, see systemd.mount(5). # Please run 'systemctl daemon-reload' after making changes here. # # /dev/mapper/dummy--vg-root / ext4errors=remount-ro 0 1 # /boot was on /dev/nvme0n1p2 during installation UUID=0d9a09b3-abe6-4831-ad3a-166f68e6c77f /boot ext2defaults 0 2 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=D114-FD63 /boot/efi vfatumask=0077 0 1 /dev/mapper/dummy--vg-swap_1 noneswapsw 0 0 -- lsmod Module Size Used by snd_usb_audio 376832 1 snd_usbmidi_lib45056 1 snd_usb_audio snd_rawmidi53248 1 snd_usbmidi_lib xt_conntrack 16384 1 nft_chain_nat 16384 3 xt_MASQUERADE 20480 1 nf_nat 57344 2 nft_chain_nat,xt_MASQUERADE nf_conntrack_netlink57344 0 nf_conntrack 188416 4 xt_conntrack,nf_nat,nf_conntrack_netlink,xt_MASQUERADE nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack xfrm_user 53248 1 xfrm_algo 16384 1 xfrm_user xt_addrtype16384 2 nft_compat 20480 4 nf_tables 286720 57 nft_compat,nft_chain_nat libcrc32c 16384 3 nf_conntrack,nf_nat,nf_tables nfnetlink 20480 4 nft_compat,nf_conntrack_netlink,nf_tables br_netfilter 32768 0 bridge311296 1 br_netfilter stp16384 1 bridge llc16384 2 bridge,stp typec_displayport 16384 1 ctr16384 2 ccm20480 6 uhid 20480 1 rfcomm 94208 4 cmac 16384 3 snd_seq_dummy 16384 0 snd_hrtimer16384 1 algif_hash 16384 1 snd_seq90112 7 snd_seq_dummy algif_skcipher 16384 1 snd_seq_device 16384 2 snd_seq,snd_rawmidi af_alg 36864 6 algif_hash,algif_skcipher overlay 159744 0 qrtr 49152 4 bnep 28672 2 binfmt_misc24576 1 nls_ascii 16384 1 nls_cp437 20480 1 vfat 24576 1 fat90112 1 vfat snd_sof_pci_intel_skl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_skl soundwire_intel49152 1 snd_sof_intel_hda_common soundwire_generic_allocation16384 1 soundwire_intel snd_hda_codec_hdmi 81920 1 soundwire_cadence 40960 1 soundwire_intel snd_sof_intel_hda 20480 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_skl
Bug#1033526: svn-load: autopkgtest fails: No module named 'pysvn'
Source: svn-load
Version: 1.6-1
Severity: serious
Tags: bookworm-ignore
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails. Can you
please investigate the situation and fix it? I copied some of the output
at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. (But because of the freeze, let's
ignore this for bookworm).
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/s/svn-load/32132782/log.gz
autopkgtest [23:15:28]: test command1: [---
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FTraceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
:1: DeprecationWarning: invalid escape sequence '\('
ETraceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
F..Adding /tmp/tmp4zf5llte/importdir/foo
Committing transaction...
Committed revision 1.
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FAdding /tmp/tmpproq1ryt/importdir/bar
Adding /tmp/tmpproq1ryt/importdir/foo
Committing transaction...
Committed revision 1.
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FAdding /tmp/tmpsusv3tkb/importdir/foo
Committing transaction...
Committed revision 1.
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
.Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FTraceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FTraceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FTraceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FTraceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FTraceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
FAdding /tmp/tmp39bht1d1/importdir/src
Adding /tmp/tmp39bht1d1/importdir/src/bang.png
Adding /tmp/tmp39bht1d1/importdir/src/bar.gif
Adding /tmp/tmp39bht1d1/importdir/src/baz.png
Adding /tmp/tmp39bht1d1/importdir/src/blast
Adding /tmp/tmp39bht1d1/importdir/src/blast/boom.jpg
Adding /tmp/tmp39bht1d1/importdir/src/foo.jpg
Adding /tmp/tmp39bht1d1/importdir/src/main.c
Committing transaction...
Committed revision 1.
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
F./tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./test.py:232:
ResourceWarning: unclosed file <_io.TextIOWrapper
name='/tmp/tmpqrrh042w' mode='w' encoding='UTF-8'>
self.makeMoveMap()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
Adding /tmp/tmp8zmys6ht/importdir/bar$baz
Adding /tmp/tmp8zmys6ht/importdir/foo
Committing transaction...
Committed revision 1.
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./svn-load", line
48, in
import pysvn
ModuleNotFoundError: No module named 'pysvn'
F/tmp/autopkgtest-lxc.mx6xh_um/downtmp/build.yiw/src/./test.py:232:
ResourceWarning: unclosed file <_io.TextIOWrapper
name='/tmp/tmp04uqmv75' mode='w' encoding='UTF-8'>
self.makeMoveMap()
ResourceWarning: Enable tracemalloc to
Bug#1020445: numba: autopkgtest regression on ppc64el: inf != 0.625
On Fri, 27 Jan 2023 15:35:29 +0100 Bastian Germann wrote: Control: fixed -1 0.56.4+dfsg-1 This seems to have gone away with the latest upload. But numba now fails everywhere, except on amd64 if run on a very powerful host (most of our hosts, it times out). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Hi Markus On Sun, 26 Mar 2023 at 16:34, Markus Koschany wrote: > 1. There is no transition needed because only shrinksafe is affected by the > new > rhino version. How did you determine this? > 2. shrinksafe has no reverse-dependencies That is true, but src:dojo has ledgersmb and tt-rss as reverse-dependencies. > 4. I have rebuilt all rhino reverse-dependencies successfully. That's great, although we do have regular test rebuilds which should find FTBFS with the new rhino. > 7. Summary: I recommend to rebuild dojo to fix the autopkgtests. I suggest to > reconsider the current autopkgtest behavior. At least there should be a > warning > or a note for maintainers in the future that dojo requires a rebuild whenever > rhino changes. I wait to hear the opinion of the dojo maintainers, but if it does turn out that only dojo needs a rebuild, then dojo should be uploaded, adding a versioned dependency on librhino-java >= 1.7.14 and << 1.7.15 (or similar). Also, Rhino will need an upload, declaring a Breaks on shrinksafe << 1.17.2+dfsg1-3 (or similar). Regards Graham
Processed: severity of 1033408 is serious
Processing commands for cont...@bugs.debian.org: > severity 1033408 serious Bug #1033408 [apache2] apache2: Segmentation fault + 503 on frontpage on 2.4.56-1 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1033408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033425: marked as done (python-scrapy: FTBFS in testing: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Sun, 26 Mar 2023 15:51:37 + with message-id and subject line Bug#1033425: fixed in python-scrapy 2.8.0-2 has caused the Debian Bug report #1033425, regarding python-scrapy: FTBFS in testing: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 1033425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-scrapy Version: 2.8.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230323 ftbfs-bookworm Hi, During a rebuild of all packages in testing (bookworm), your package failed to build on amd64. Relevant part (hopefully): > tests/test_linkextractors.py ... [ > 60%] > tests/test_loader.py ... [ > 61%] > [ > 62%] > tests/test_loader_deprecated.py [ > 63%] > ... [ > 64%] > tests/test_logformatter.py [ > 64%] > tests/test_mail.py ... [ > 65%] > tests/test_middleware.py [ > 65%] > tests/test_pipeline_crawl.py [ > 65%] > tests/test_pipeline_files.py sss [ > 66%] > tests/test_pipeline_images.py . [ > 67%] > tests/test_pipeline_media.py .. [ > 68%] > tests/test_pipelines.py s[ > 68%] > tests/test_pqueues.py s...s..[ > 68%] > tests/test_proxy_connect.py > E: Build killed with signal TERM after 150 minutes of inactivity I don't think this is #921803. The full build log is available from: http://qa-logs.debian.net/2023/03/23/python-scrapy_2.8.0-1_testing.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230323;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230323=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: python-scrapy Source-Version: 2.8.0-2 Done: Andrey Rakhmatullin We believe that the bug you reported is fixed in the latest version of python-scrapy, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrey Rakhmatullin (supplier of updated python-scrapy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 26 Mar 2023 17:57:50 +0400 Source: python-scrapy Architecture: source Version: 2.8.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Andrey Rakhmatullin Closes: 1033425 Changes: python-scrapy (2.8.0-2) unstable; urgency=medium . * Remove B-D: mitmproxy as tests break with the new version of it (Closes: #1033425). Checksums-Sha1: a7c35b36ce432224d1f1f6faec07b56280b41f7e 2945 python-scrapy_2.8.0-2.dsc 59f9e72563bdc34710823f629ba72c7955eddb3e 9208 python-scrapy_2.8.0-2.debian.tar.xz ed212763ba974a4d97e75b0a7029ae7573fb1f2c 10054 python-scrapy_2.8.0-2_amd64.buildinfo Checksums-Sha256: 621758e347b8cd98e16d604d54f111b464ecd747f79a36bf3f277d754b1c8aa1 2945 python-scrapy_2.8.0-2.dsc
Bug#1029944: A couple of patches
Here are a couple of patches that seem to fix the test failures. The
first patch updates the test-harness to use ::1 if 127.0.0.1 is not
available. The second patch updates a few test-cases to prevent them
failing, either by changing them to work with ::1, or just skipping
them.
I've tested by running the build in a net namespace where lo doesn't
have 127.0.0.1:
$ sudo ip netns exec ipv6test ip -4 addr show lo
$ sudo ip netns exec ipv6test ip -6 addr show lo
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
$ sudo ip netns exec ipv6test sudo -u $USER fakeroot debian/rules clean binary
[...]
make[2]: Entering directory
'/space/azazel/tmp/neon27/debian/build-tree/neon-openssl/test'
[...]
rm -rf ca ca2
OPENSSL=/usr/bin/openssl \
/bin/bash makekeys ../../../../test 2>makekeys.out
gzip -c --no-name ../../../../NEWS > file1.gz
gzip -c --name ../../../../NEWS > file2.gz
gzip -c --no-name ../../../../NEWS > trailing.gz
echo "hello, world" >> trailing.gz
dd of=badcsum.gz if=file1.gz bs=1 count=`perl -e 'printf "%d",
(stat("file1.gz"))[7] - 8;'`
25010+0 records in
25010+0 records out
25010 bytes (25 kB, 24 KiB) copied, 0.0247032 s, 1.0 MB/s
echo 'broken!' >> badcsum.gz
dd if=file1.gz of=truncated.gz bs=2048 count=2
2+0 records in
2+0 records out
4096 bytes (4.1 kB, 4.0 KiB) copied, 3.8031e-05 s, 108 MB/s
dd of=corrupt1.gz if=file1.gz bs=1 count=500
500+0 records in
500+0 records out
500 bytes copied, 0.000968376 s, 516 kB/s
cat ../../../../NEWS >> corrupt1.gz
cat ../../../../NEWS > corrupt2.gz
touch empty.gz
cat ../../../../NEWS > random.txt
echo hello world > hello.txt
gzip -c hello.txt > hello.gz
echo foobar > foobar.txt
../../../../test/run.sh: line 5: ulimit: core file size: cannot modify limit:
Operation not permitted
uri-tests. 15/15 passed
util-tests 9/ 9 passed
string-tests.. 32/32 passed
socket 10/47 SKIPPED - addr_connect
socket 11/47 SKIPPED - addr_peer
socket 36/47 SKIPPED - prebind
socket 44/47 passed (3 skipped)
session... 8/ 8 passed
request... 82/92 SKIPPED - local_addr
request... 84/92 SKIPPED - addrlist
request... 90/92 passed (2 skipped)
auth.. 21/21 passed
basic. 11/11 passed
stubs. 1/ 1 passed
redirect.. 6/ 6 passed
socket-ssl 11/48 SKIPPED - addr_connect
socket-ssl 12/48 SKIPPED - addr_peer
socket-ssl 22/48 SKIPPED - ssl_session_id (zero-length session
ID, cannot test further)
socket-ssl 37/48 SKIPPED - prebind
socket-ssl 44/48 passed (4 skipped)
ssl... 62/63 WARNING: NSS required for PKCS#11 testing
ssl... 62/63 SKIPPED - pkcs11
ssl... 63/63 WARNING: NSS required for PKCS#11 testing
ssl... 63/63 SKIPPED - pkcs11_dsa
ssl... 61/63 passed (2 skipped) (2 warnings)
compress.. 22/22 passed
xml... 5/ 5 passed
xmlreq 3/ 3 passed
oldacl 4/ 4 passed
acl3744... 4/ 4 passed
props. 7/ 7 passed
lock.. 16/16 passed
make[2]: Leaving directory
'/space/azazel/tmp/neon27/debian/build-tree/neon-openssl/test'
[...]
make[2]: Entering directory
'/space/azazel/tmp/neon27/debian/build-tree/neon-gnutls/test'
[...]
rm -rf ca ca2
OPENSSL=/usr/bin/openssl \
/bin/bash makekeys ../../../../test 2>makekeys.out
gzip -c --no-name ../../../../NEWS > file1.gz
gzip -c --name ../../../../NEWS > file2.gz
gzip -c --no-name ../../../../NEWS > trailing.gz
echo "hello, world" >> trailing.gz
dd of=badcsum.gz if=file1.gz bs=1 count=`perl -e 'printf "%d",
(stat("file1.gz"))[7] - 8;'`
25010+0 records in
25010+0 records out
25010 bytes (25 kB, 24 KiB) copied, 0.0250625 s, 998 kB/s
echo 'broken!' >> badcsum.gz
dd if=file1.gz of=truncated.gz bs=2048 count=2
2+0 records in
2+0 records out
4096 bytes (4.1 kB, 4.0 KiB) copied, 4.0065e-05 s, 102 MB/s
dd of=corrupt1.gz if=file1.gz bs=1 count=500
500+0 records in
500+0 records out
500 bytes copied, 0.000531978 s, 940 kB/s
cat ../../../../NEWS >> corrupt1.gz
cat ../../../../NEWS > corrupt2.gz
touch empty.gz
cat ../../../../NEWS > random.txt
echo hello world > hello.txt
gzip -c hello.txt > hello.gz
echo foobar > foobar.txt
../../../../test/run.sh: line 5: ulimit: core file size: cannot modify limit:
Operation not permitted
uri-tests. 15/15 passed
util-tests 9/ 9 passed
string-tests.. 31/32 SKIPPED - strhash_sha_512_256 (SHA-2-512/256 not
supported)
string-tests.. 31/32 passed (1 skipped)
Bug#1033155: marked as done (migration test fails when EC key present in test keyrings)
Your message dated Sun, 26 Mar 2023 14:46:25 +
with message-id
and subject line Bug#1033155: fixed in gnupg2 2.2.40-1.1
has caused the Debian Bug report #1033155,
regarding migration test fails when EC key present in test keyrings
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.)
--
1033155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg2
Version: 2.2.40-1
Severity: important
Tags: patch
X-Debbugs-Cc: j...@debian.org
Hi,
The stable release key for bookworm is EC, and this causes gpg1 to bail
out when it is imported as part of the migration test. Attached patch
limits the keyrings used to the archive's automatic keys, which are
still RSA.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Index: gnupg2-2.2.40/debian/tests/migration
===
--- gnupg2-2.2.40.orig/debian/tests/migration
+++ gnupg2-2.2.40/debian/tests/migration
@@ -11,7 +11,7 @@ gpg1=(gpg1 --homedir "$GPG_HOME" --batch
mkdir "$GPG_HOME"
chmod 700 "$GPG_HOME"
-cat /usr/share/keyrings/debian-archive-*.gpg | "${gpg1[@]}" --import
+cat /usr/share/keyrings/debian-archive-*-automatic.gpg | "${gpg1[@]}" --import
"${gpg1[@]}" --list-keys
"${gpg[@]}" --list-keys > "$DIR/key.list.before"
migrate-pubring-from-classic-gpg "$GPG_HOME"
--- End Message ---
--- Begin Message ---
Source: gnupg2
Source-Version: 2.2.40-1.1
Done: Andreas Metzler
We believe that the bug you reported is fixed in the latest version of
gnupg2, 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 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Metzler (supplier of updated gnupg2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 26 Mar 2023 15:03:05 +0200
Source: gnupg2
Architecture: source
Version: 2.2.40-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers
Changed-By: Andreas Metzler
Closes: 1033155
Changes:
gnupg2 (2.2.40-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* In migration CI test skip debian-archive-bookworm-stable.gpg (and
aggregated keyring), gpg1 cannot read the ed25519 key. Closes: #1033155
Checksums-Sha1:
232914bc9255d520624c27911e0d1e6c925d0481 3832 gnupg2_2.2.40-1.1.dsc
f5a066103188620ac638ecd51f6a55c709fae79b 62368 gnupg2_2.2.40-1.1.debian.tar.xz
Checksums-Sha256:
89bdffd4176066d37fb5d250a1e5512c428529d10f13413a12893f86a757697f 3832
gnupg2_2.2.40-1.1.dsc
356b7c86afdbaab286c5b92816cd1e1f4616cb67d22407c616618ef4d1680a9b 62368
gnupg2_2.2.40-1.1.debian.tar.xz
Files:
a6fc2770e0a29cac8daecfa41d9b59ed 3832 utils optional gnupg2_2.2.40-1.1.dsc
262947a69bddf462a00614f3e800fb43 62368 utils optional
gnupg2_2.2.40-1.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmQgSG8ACgkQpU8BhUOC
FIQMxA//aezfrIDq1ph2bqoGwMRNGcq/LxkfxAOHOpn9TiHLTel97iN7qVxWm9BB
fEKReMThnFla8OUwJZaNEumRZnEfBsq8q6nXxonhHWov9SrUrEwBXKaew8Qn4eWu
lDtua+gXro8TQPMyFDBz5eDwWNLPLyH86H1MC0PFoBifbrFwuTOLC1EdA/9HVYYG
uIpDpWBVjHv0XBVXMn9xzIDKN/ZkuxxNMz4Kj8kIIlAxM97dNVQXpVO7jXfMaEQH
1FdvGe0dBAgRY1KJxUrU78DwGZpg0/Nn/OxVPUNLBK4fRy8jCwAO02Zors32DHpw
KIq1hwD0kAH9fWD+vQiXMnre42e23W4E6NjqHV+Uf1B1Vqr7XiTVC/HuJZSuIZEB
CUrX4aAe97zZ0roheUlTgjXvTonVjHUW0+B+Gj2qrxNBuQDH1iVXMQSYTNrDxVOR
K4cu5GQDghK8qKCFghH1oF2GXE+u4I94RG6S/5SPw22Px6fruKllJ3aXBrQg8kxD
8VWu/N/IgQDL2RKjOhSplGXOrNNB1TfErApj1w0iypFA/sPzk8BXBrJLtEhtGf9D
oBTReLbkrI7Gmr0g7256z4di0ibOjp4jyZkaw14U4ryB5pyNZxRRkA8Wjk4MvZIi
XUmXhipXwRgGKSugoPlrMmfxaOeF6T67B/JzHMdoWSMCl1xqHq0=
=6rMp
-END PGP SIGNATURE End Message ---
Bug#1033456: marked as done (genomicsdb may need build adjustment)
Your message dated Sun, 26 Mar 2023 14:46:05 + with message-id and subject line Bug#1033456: fixed in genomicsdb 1.4.4-3 has caused the Debian Bug report #1033456, regarding genomicsdb may need build adjustment 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.) -- 1033456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: genomicsdb Severity: normal I recently filed #1033410 and requested to have tiledb removed from Debian as the build has always severely constrained by both a lack of 'cloud' support, a mismatch with pinned dependencies at different versions of required libraries, an upcoming change to use of vcpkg, and a general mismatch as upstream really only looks at x86_64 and arm64. As I understand it, genomicsdb primarily builds off htslib. I am herebe asking you to kindly adjust the build to no longer require libtiledb-dev. Thanks, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org --- End Message --- --- Begin Message --- Source: genomicsdb Source-Version: 1.4.4-3 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of genomicsdb, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated genomicsdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 26 Mar 2023 15:28:08 +0200 Source: genomicsdb Architecture: source Version: 1.4.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Pierre Gruet Closes: 1033456 Changes: genomicsdb (1.4.4-3) unstable; urgency=medium . * Removing B-D on libtiledb-dev (Closes: #1033456) * Raising Standards version to 4.6.2 (no change) Checksums-Sha1: f8a86b45198df62dd9309fc45dca58d5ca8a5f68 3433 genomicsdb_1.4.4-3.dsc bf47b81ff08646107dceca4ec5b7ea758a5c77bc 26772 genomicsdb_1.4.4-3.debian.tar.xz 6b440e6db58af336b057c430115043ff70dec5af 18233 genomicsdb_1.4.4-3_source.buildinfo Checksums-Sha256: 498d331c9f1bd70c4ca28f220e7efd534a1a011a96e5df6d9e627f95d3cdfb17 3433 genomicsdb_1.4.4-3.dsc 309886d859d8d209c9c08d96d03e8accb9c2eb40ae4ddc0af4b6022921acd3e5 26772 genomicsdb_1.4.4-3.debian.tar.xz 8c1a541d58d80a66962ae3522ebe3f26a412ba73201962b27b7c72f5692f7cfa 18233 genomicsdb_1.4.4-3_source.buildinfo Files: c688b5bde1b61f5687f4b8665de2e822 3433 science optional genomicsdb_1.4.4-3.dsc e46c04c827e3ebeb50a9bd3044163d10 26772 science optional genomicsdb_1.4.4-3.debian.tar.xz 094e803c22961a1da82e32fe2ce2b6b0 18233 science optional genomicsdb_1.4.4-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmQgTE0ACgkQYAMWptwn dHYAghAAspuyhkZQ1yJbqMJYnFu1xdsa6LWMWtI5K9oHPDhIYUSBzJ8mEAJNkA/Z ODp/NFJtb0Nh34NNQdWrW0iXM+zWZs63mxGJ0Z/BnR31Uc9f5s6MhRnemH0DlN5k kCqqDaqEFBiuEeTqF6qJaFhX6XqDKSBiRK3TdKRlObfwAQ6CBAoTezHqEYg3XIq2 UJmbmhMo0LCvltXNLOxFjgoMdN/VUpEKLNoYA7D1yj8toDPrqARukb1nwBY6ddhv sc/floe3FFmaHQJjSewOAKtypMN6v+G4ruYnq91h2GiGNXxfqssy4WYURt/ovI+V LahQSDU+eD6FyebgaZZZOFw0fgeBUeUQdObOUTsC1QcIVw9eMtORuw24X9Sb26fe 4uNbZhE7wra1WbF8YwJdRNm3JxoW3g4X5hxyDCTBlH3MxntEZsR9d6u2PrM4eOw7 pP0jpt5G2TnbWw0GWSnsqjnu5fVCR9z4gk+65Gzp2+BvROamxYoM7RYE3cR/S+fT 5UM4lDHHWoZrnkE1XosYsSjD1kUMao2Vnftu82JhCMgnbbnOmMqwEwUFRstXlEFb fGKg35c8zfbX9p3Jo11TFiSNyCM5ZhutvtUtE/CmYA1sxc3fHfbNnl28n+5TgI5l lqdrJpFJA42EnGuoIWYrtWEtgBCCrdVfiePPpjERqaU+m7ROhJM= =QmFw -END PGP SIGNATURE End Message ---
Bug#1030050: fixed in rails 2:6.1.7.3+dfsg-1
Hi, On 26/03/23 at 19:34 +0530, Pirate Praveen wrote: > Two autopkgtest regressions are blocking the migration to testing. Both look random: > ruby-clockwork (arm64 only): > 1) Failure: > Clockwork#test_0006_should pass all arguments to every > [/tmp/autopkgtest-lxc.42fb1p3k/downtmp/build.WCJ/src/test/clockwork_test.rb:88]: > Expected false to be truthy. > > 69 runs, 135 assertions, 1 failures, 0 errors, 0 skips > > Full log > https://ci.debian.net/data/autopkgtest/testing/arm64/r/ruby-clockwork/32418759/log.gz I requested retries for both the reference and the migration test, and now the reference fails and the migration test succeeds. https://ci.debian.net/packages/r/ruby-clockwork/testing/arm64/ > ruby-moneta (amd64 only): Yes, that one was failing randomly for me as well. I requested retries. The retry for the migration test succeeded. https://ci.debian.net/packages/r/ruby-moneta/testing/amd64/ Lucas
Processed: closing 1033434
Processing commands for cont...@bugs.debian.org: > close 1033434 2.23.3 Bug #1033434 [src:devscripts] devscripts: FTBFS in testing: AssertionError: pylint found issues: Marked as fixed in versions devscripts/2.23.3. Bug #1033434 [src:devscripts] devscripts: FTBFS in testing: AssertionError: pylint found issues: Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1033434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033517: yt-dlp: mpv fails to work with yt-dlp, after yt-dlp upgrade (uncoordinated API change?)
Package: yt-dlp Version: 2023.03.04-1 Severity: grave Justification: renders package unusable Hello and thanks for maintaining this useful package! After upgrading from yt-dlp/2023.02.17-1 to yt-dlp/2023.03.04-1, mpv is no longer able to use yt-dlp to play YouTube videos: $ mpv https://www.youtube.com/watch?v=... EDL specifies no segments.' EDL parsing failed. Error in EDL. EDL: source file 'edl://!mp4_dash,init=%915%https://rr1---sn-hpa7znzy.googlevideo.com/videoplayback?expire=1679861814=1lMgZOdpiqvXAtvOorAL=176.207.81.113=.=251=youtube=yes=Ud=31%2C29=sn-hpa7znzy%2Csn-hpa7kn76=au%2Crdu=m=1=21=it=742500=99c5CXNHIzrXpm8d9GnEVnYuvfkNUx0=1=1=audio%2Fwebm=yes=2393695=146.021=1565382960171852=1679839757=2=yes=24007246=ANDROID=5431432=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cgcr%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt=AOq0QJ8wRQIgK694JvtFcYR2CD8XvmJn6i09Q9lraFGyVhAMcpRX-UICIQCCGeSN6JZGoxj5dZMwNp-qBqRmJ11_PZLZI2eZCTLkhg%3D%3D=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps=AG3C_xAwRgIhAJd3QxRLmHXqr04xeeC1fjZSFZr9k6cv2So71H8l6Ax2AiEAhKnq5EgVOp84xsaGYrOL8Uga7UxrqNJG6fCqH4mH238%3D=0-2393695;' has unknown duration. EDL specifies no segments.' EDL parsing failed. Error in EDL. EDL: source file 'edl://!mp4_dash,init=%915%https://rr1---sn-hpa7znzy.googlevideo.com/videoplayback?expire=1679861814=1lMgZOdpiqvXAtvOorAL=176.207.81.113=.=248=youtube=yes=Ud=31%2C29=sn-hpa7znzy%2Csn-hpa7kn76=au%2Crdu=m=1=21=it=742500=99c5CXNHIzrXpm8d9GnEVnYuvfkNUx0=1=1=video%2Fwebm=yes=8861743=146.000=1565383003479714=1679839757=2=yes=24007246=ANDROID=5431432=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cgcr%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt=AOq0QJ8wRQIhAKRzV0x6RiHkG_vxxixrOMea0A9COXLNQKnMXZMH-JjoAiBflw-hlwAKQUe_kv1e7oI91GhJbXwXdDtknxSqJXSdVg%3D%3D=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps=AG3C_xAwRgIhAJd3QxRLmHXqr04xeeC1fjZSFZr9k6cv2So71H8l6Ax2AiEAhKnq5EgVOp84xsaGYrOL8Uga7UxrqNJG6fCqH4mH238%3D=0-8861743;' has unknown duration. File tags: Uploader: . - . Channel_URL: https://www.youtube.com/channel/ No video or audio streams selected. Exiting... (Errors when loading file) Instead, if I manually download the YouTube video: $ yt-dlp -o test https://www.youtube.com/watch?v=... [youtube] Extracting URL: https://www.youtube.com/watch?v=... [youtube] ...: Downloading webpage [youtube] ...: Downloading android player API JSON [info] ...: Downloading 1 format(s): 248+251 [dashsegments] Total fragments: 1 [download] Destination: test.f248.webm [download] 100% of8.45MiB in 00:00:00 at 8.71MiB/s [dashsegments] Total fragments: 1 [download] Destination: test.f251.webm [download] 100% of2.28MiB in 00:00:00 at 6.66MiB/s [Merger] Merging formats into "test.webm" Deleting original file test.f251.webm (pass -k to keep) Deleting original file test.f248.webm (pass -k to keep) I obtain a 'test.webm' file, that can later be played with mpv: $ mpv test.webm (+) Video --vid=1 (*) (vp9 1080x1080 25.000fps) (+) Audio --aid=1 --alang=eng (*) (opus 2ch 48000Hz) AO: [jack] 44100Hz stereo 2ch floatp VO: [gpu] 1080x1080 yuv420p AV: 00:00:03 / 00:02:26 (2%) A-V: 0.000 Exiting... (Quit) If I downgrade yt-dlp to version 2023.02.17-1, everything works again: $ mpv https://www.youtube.com/watch?v=... (+) Video --vid=1 (*) (vp9 1080x1080 25.000fps) (+) Audio --aid=1 --alang=eng (*) (opus 2ch 48000Hz) File tags: Uploader: . - . Channel_URL: https://www.youtube.com/channel/ AO: [jack] 44100Hz stereo 2ch floatp VO: [gpu] 1080x1080 yuv420p AV: 00:00:03 / 00:02:26 (3%) A-V: 0.000 Cache: 141s/15MB Exiting... (Quit) What's wrong? Did yt-dlp change API? If this is the case, the new version of yt-dlp Debian package should wait for an updated mpv Debian package, before migrating to testing... Or is it a bug in yt-dlp that shows up only when yt-dlp is called by mpv behind the scenes, and not when it is directly invoked from the user's command line? Please fix this issue as soon as possible, or revert to the previous version (yt-dlp/2023.02.17-1), until this behavior has been properly investigated and solved. Thanks for your time and patience! -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (800, 'testing-security'), (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yt-dlp depends on: ii python33.11.2-1 ii python3-brotli 1.0.9-2+b6 ii python3-certifi2022.9.24-1 ii python3-mutagen
Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Hello, On Sun, 26 Mar 2023 09:41:48 +0200 Graham Inggs wrote: [...] > To both the rhino and dojo maintainers, please investigate so we can > have this resolved for bookworm. Here are my investigations: 1. There is no transition needed because only shrinksafe is affected by the new rhino version. 2. shrinksafe has no reverse-dependencies 3. We had the exact same problem before [1]. Back then the fix was to rebuild the package and to fix the shrinksafe tests by setting a specific Javascript version. [2] Since just rebuilding dojo also fixes the problem, I assume that we don't have to change this option. 4. I have rebuilt all rhino reverse-dependencies successfully. 5. I have tested yui-compressor, a similar tool, with rhino 1.7.14 and without rebuilding the existing package and this one works as expected. 6. Regarding Openrefine: It does only work with rhino 1.7.14 in unstable. Hence why I tightened the dependency on rhino to 1.7.14. The current version of rhino in testing breaks the Javascript application. 7. Summary: I recommend to rebuild dojo to fix the autopkgtests. I suggest to reconsider the current autopkgtest behavior. At least there should be a warning or a note for maintainers in the future that dojo requires a rebuild whenever rhino changes. Regards, Markus [1] https://bugs.debian.org/970501 [2] https://salsa.debian.org/js-team/dojo/-/commit/68e6a048b4c4386d0495e7faf11bd46bf0516604 signature.asc Description: This is a digitally signed message part
Processed: twisted: autopkgtest fails: failures=21, errors=35
Processing control commands: > found -1 18.9.0-3 Bug #1033516 [src:twisted] twisted: autopkgtest fails: failures=21, errors=35 Marked as found in versions twisted/18.9.0-3. -- 1033516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033516: twisted: autopkgtest fails: failures=21, errors=35
Source: twisted
Version: 22.4.0-4
Severity: serious
Tags: bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Control: found -1 18.9.0-3
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails. Can you
please investigate the situation and fix it? I copied some of the output
at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/t/twisted/32195474/log.gz
twisted.test.test_application.LoadingTests.test_simpleStoreAndLoad
===
[ERROR]
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/twisted/test/test_tcp.py", line
1232, in clientDisconnected
hamcrest.assert_that(
File "/usr/lib/python3/dist-packages/hamcrest/core/assert_that.py",
line 58, in assert_that
_assert_match(actual=actual, matcher=matcher, reason=reason)
File "/usr/lib/python3/dist-packages/hamcrest/core/assert_that.py",
line 73, in _assert_match
raise AssertionError(description)
builtins.AssertionError:
Expected: a sequence containing [a sequence containing ['SSL routines',
('SSL_write' or 'ssl_write_internal'), 'protocol is shutdown']]
but: item 0: item 1: was ''
twisted.test.test_ssl.StolenTCPTests.test_properlyCloseFiles
---
Ran 11861 tests in 1260.901s
FAILED (skips=1673, failures=21, errors=35, successes=10149)
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1033515: wit: autopkgtest regression: [[: not found
Source: wit Version: 3.01a-4 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it recently (October 2022) started to fail in testing. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/w/wit/32146692/log.gz autopkgtest [11:20:32]: test wdf-test: [--- /tmp/autopkgtest-lxc.moidampy/downtmp/build.ztX/src/debian/tests/wdf-test: 7: [[: not found autopkgtest [11:20:32]: test wdf-test: ---] autopkgtest [1autopkgtest [11:20:35]: test wdf-cat-test: [--- /tmp/autopkgtest-lxc.moidampy/downtmp/build.ztX/src/debian/tests/wdf-cat-test: 7: [[: not found autopkgtest [11:20:35]: test wdf-cat-test: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1033514: xchain: autopkgtest fails: xvfb-run: command not found
Source: xchain Version: 1.0.1-10 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/x/xchain/32146659/log.gz autopkgtest [11:18:09]: test command1: [--- bash: line 1: xvfb-run: command not found autopkgtest [11:18:09]: test command1: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1033513: xsel: autopkgtest fails: Inappropriate ioctl for device
Source: xsel Version: 1.2.0+git9bfc13d.20180109-3 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/x/xsel/32227709/log.gz autopkgtest [22:21:32]: test command1: [--- xsel: Can't open display: (null) : Inappropriate ioctl for device autopkgtest [22:21:32]: test command1: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1033512: zc.buildout: autopkgtest fails: cannot open /usr/share/python3-zope.testing/test_helper
Source: zc.buildout Version: 2.13.2-4 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/z/zc.buildout/32140722/log.gz autopkgtest [06:23:21]: test all: [--- /tmp/autopkgtest-lxc.4d5588j5/downtmp/build.MKN/src/debian/tests/all: 2: .: cannot open /usr/share/python3-zope.testing/test_helper: No such file autopkgtest [06:23:22]: test all: ---] OpenPGP_signature Description: OpenPGP digital signature
Processed: gnupg2: diff for NMU version 2.2.40-1.1
Processing control commands: > tags 1033155 + pending Bug #1033155 [src:gnupg2] migration test fails when EC key present in test keyrings Added tag(s) pending. -- 1033155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033510: vim-ultisnips: flaky autopkgtest: Invalid multiword trigger
Source: vim-ultisnips Version: 3.2-2 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/v/vim-ultisnips/32171934/log.gz == FAIL: runTest (test_ParseSnippets.ParseSnippets_MultiWord_UnmatchedContainer.runTest) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.yoo62zj7/downtmp/build.SFF/src/test/vim_test_case.py", line 67, in runTest self.assertRegex(self.output, self.expected_error) AssertionError: Regex didn't match: "Invalid multiword trigger: '!inv snip/' in \\S+:2" not found in 'An error occured. This is either a bug in UltiSnips or a bug in a\nsnippet definition. If you think this is a bug, please report it to\nhttps://github.com/SirVer/ultisnips/issues/new\nPlease read and follow:\nhttps://github.com/SirVer/ultisnips/blob/master/CONTRIBUTING.md#reproducing-bugs\n\nFollowing is the full stack trace:\nTraceback (most recent call last):\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/err_to_scratch_buffer.py", line 18, in wrapper\nreturn func(self, *args, **kwds)\n ^\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 905, in _track_change\n self._try_expand(autotrigger_only=True)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 749, in _try_expand\nsnippets = self._snips(before, False, autotrigger_only)\n \n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 629, in _snips\nsource.ensure(filetypes)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 31, in ensure\nself._load_snippets_for(ft)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 53, in _load_snippets_for\nself._parse_snippets(ft, fn)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 69, in _parse_snippets\nraise SnippetSyntaxError(filename, line_index, msg)\nUltiSnips.snippet.source.file.base.SnippetSyntaxError: Invalid multiword trigger: \'!inv snip/\' in /nip\tp/autopkgtest-lxc.yoo62zj7/downtmp/autopkgtest_tmp/UltiSnipsTest_Casemj4yxyks/us/all.snippets:2' -- OpenPGP_signature Description: OpenPGP digital signature
Bug#1033155: gnupg2: diff for NMU version 2.2.40-1.1
Control: tags 1033155 + pending
Dear maintainer,
I've prepared an NMU for gnupg2 (versioned as 2.2.40-1.1) and
uploaded it non-delayed.
Kind regards
Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru gnupg2-2.2.40/debian/changelog gnupg2-2.2.40/debian/changelog
--- gnupg2-2.2.40/debian/changelog 2022-10-19 17:09:42.0 +0200
+++ gnupg2-2.2.40/debian/changelog 2023-03-26 15:03:05.0 +0200
@@ -1,3 +1,11 @@
+gnupg2 (2.2.40-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * In migration CI test skip debian-archive-bookworm-stable.gpg (and
+aggregated keyring), gpg1 cannot read the ed25519 key. Closes: #1033155
+
+ -- Andreas Metzler Sun, 26 Mar 2023 15:03:05 +0200
+
gnupg2 (2.2.40-1) unstable; urgency=medium
* new upstream version
diff -Nru gnupg2-2.2.40/debian/tests/migration gnupg2-2.2.40/debian/tests/migration
--- gnupg2-2.2.40/debian/tests/migration 2022-09-02 00:08:12.0 +0200
+++ gnupg2-2.2.40/debian/tests/migration 2023-03-26 15:03:05.0 +0200
@@ -11,7 +11,9 @@
mkdir "$GPG_HOME"
chmod 700 "$GPG_HOME"
-cat /usr/share/keyrings/debian-archive-*.gpg | "${gpg1[@]}" --import
+cat $(ls /usr/share/keyrings/debian-archive-*.gpg \
+ | grep -vE 'debian-archive-bookworm-stable.gpg|debian-archive-keyring.gpg') \
+ | "${gpg1[@]}" --import
"${gpg1[@]}" --list-keys
"${gpg[@]}" --list-keys > "$DIR/key.list.before"
migrate-pubring-from-classic-gpg "$GPG_HOME"
signature.asc
Description: PGP signature
Bug#1033508: refstack-client: autopkgtest regression: Invalid version: '0.0.0.02021.08.18.fa73ef2524'
Source: refstack-client
Version: 0.0.0~2021.08.18.fa73ef2524-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it recently (around
beginning of February 2023) started to fail in testing.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/r/refstack-client/32427783/log.gz
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.zvo2tfw5/downtmp/build.pFl/src/setup.py",
line 27, in
setuptools.setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line
108, in setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py",
line 185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py",
line 201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213,
in run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/pbr/packaging.py", line 243, in run
return du_install.install.run(self)
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/install.py",
line 698, in run
self.run_command('build')
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py",
line 318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213,
in run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py",
line 132, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py",
line 318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213,
in run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 63, in run
self.build_package_data()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 159, in build_package_data
for target, srcfile in self._get_package_data_output_mapping():
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 151, in _get_package_data_output_mapping
for package, src_dir, build_dir, filenames in self.data_files:
^^^
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 72, in __getattr__
self.data_files = self._get_data_files()
^^
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 84, in _get_data_files
self.analyze_manifest()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 181, in analyze_manifest
self.run_command('egg_info')
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py",
line 318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213,
in run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 987, in run_command
cmd_obj.ensure_finalized()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py",
line 111, in ensure_finalized
self.finalize_options()
File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py",
line 219, in finalize_options
parsed_version = parse_version(self.egg_version)
^^^
File
"/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/version.py",
line 266, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version:
'0.0.0.02021.08.18.fa73ef2524'
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1033155: migration test fails when EC key present in test keyrings
On 2023-03-26 Andreas Metzler wrote: > On 2023-03-18 Jonathan Wiltshire wrote: [...] > > The stable release key for bookworm is EC, and this causes gpg1 to bail > > out when it is imported as part of the migration test. Attached patch > > limits the keyrings used to the archive's automatic keys, which are > > still RSA. > [...] > afaict currently all keys are RSA except for > debian-archive-bookworm-stable.gpg. Wouldn't it be better to just skip > this single key? Hello, I am going to fix this by NMU. (non-delayed, Daniel is on the LowThresholdNmu list.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: PGP signature
Processed: Re: [Debian-med-packaging] Bug#1033456: genomicsdb may need build adjustment
Processing control commands: > tags -1 pending Bug #1033456 [genomicsdb] genomicsdb may need build adjustment Added tag(s) pending. -- 1033456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033456: [Debian-med-packaging] Bug#1033456: genomicsdb may need build adjustment
Control: tags -1 pending Hello, Thanks, you're right. I will proceed soon! Best, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Bug#1031816: [Pkg-freeipa-devel] Bug#1031816: Bug#1031816: Bug#1031816: tomcatjss: Migrate to Tomcat 10
Am Sonntag, dem 26.03.2023 um 12:15 +0300 schrieb Timo Aaltonen: > Markus Koschany kirjoitti 24.3.2023 klo 15.35: > > Am Freitag, dem 24.03.2023 um 09:21 +0200 schrieb Timo Aaltonen: > > > Markus Koschany kirjoitti 23.3.2023 klo 19.00: > > > > Control: severity -1 serious > > > > > > > > On Fri, 24 Feb 2023 11:48:36 +0200 Timo Aaltonen > > > > wrote: > > > > > > > > > Upstream doesn't support tomcat10 yet, and tomcatjss fails to build > > > > > with > > > > > it. > > > > > > > > Unfortunately we can only support one Tomcat version per release. We > > > > should > > > > either migrate to tomcat10 or maybe it is possible to embed some of the > > > > required tomcat9 classes in your source package as a workaround > > > > provided > > > > the > > > > changes are rather small and the security impact is negligible. > > > > > > Right, but that's for bookworm+1? By that time I'm sure > > > jss/tomcatjss/dogtag have gained upstream support for tomcat10. > > > > We are targeting Bookworm. We had Tomcat 8 in Stretch and Tomcat 9 in > > Buster > > and Bullseye already. Tomcat 10 also targets Java 11 and later while Tomcat > > 9 > > was intended for Java 8 and later. We ship OpenJDK 17 in Bookworm. > > resteasy3.0 > > and tomcatjss are the only packages apart from i2p that still depend on > > libtomcat9-java. > > Nice, so you expect them to migrate after bookworm is already frozen? Targeted fixes are still allowed. Including required tomcat9 classes in your package may be a solution too. If you can find an agreement with the security and release team, then even shipping libtomcat9-java might be possible. But then your packages will not receive any security support. signature.asc Description: This is a digitally signed message part
Bug#1017953: marked as done (webext-tb-goodies depends on non-existent webext-xnote)
Your message dated Sun, 26 Mar 2023 12:29:38 + with message-id and subject line Bug#1017953: fixed in tb-goodies 1.0.1 has caused the Debian Bug report #1017953, regarding webext-tb-goodies depends on non-existent webext-xnote 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.) -- 1017953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: webext-tb-goodies Version: 1.0.0 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic Hi Mechtilde, The webext-tb-goodies package is unreleasable because it depends on webext-xnote, which does not exist in Debian. There is a webext-xnotepp package, perhaps this is what you meant? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: tb-goodies Source-Version: 1.0.1 Done: Mechtilde Stehmann We believe that the bug you reported is fixed in the latest version of tb-goodies, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mechtilde Stehmann (supplier of updated tb-goodies package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 26 Mar 2023 13:40:36 +0200 Source: tb-goodies Architecture: source Version: 1.0.1 Distribution: unstable Urgency: medium Maintainer: Debian Mozilla Extension Maintainers Changed-By: Mechtilde Stehmann Closes: 1017953 Changes: tb-goodies (1.0.1) unstable; urgency=medium . [ Mechtilde ] * [41a1683] Added d/u/metadata * [6812407] Improved VCS-Path and bumped version of thunderbird * [7712f11] Patched file name of dependency (Closes: #1017953) * [52ca91b] Bumped year in d/copyright * [7a7cd49] Bumped standard version - no changes needed Checksums-Sha1: 32777e4f8ed6de81344373ccbe11fa5a78572576 1657 tb-goodies_1.0.1.dsc 717daa58144a272e8cb76a153641473205716dfd 1924 tb-goodies_1.0.1.tar.xz 0a55177f387d272592986fd3bdce9dab8bae7915 6015 tb-goodies_1.0.1_amd64.buildinfo Checksums-Sha256: fef1f7b49a6c5d5e68abdf247d3562454358f72ed73ccf10c7ef75e9782fc8a6 1657 tb-goodies_1.0.1.dsc 1bc637f0d490dd798fed589725951caae1731370917504f2becb4730fd5c11f5 1924 tb-goodies_1.0.1.tar.xz 076edf3bd5b84da51bce1f576f8f12f8450397a0bca72ae09efda274f903543b 6015 tb-goodies_1.0.1_amd64.buildinfo Files: 763360072afd2aaafa0e850086482299 1657 metapackages optional tb-goodies_1.0.1.dsc 8acc7d6e8cb80c1e4c69468158c2673d 1924 metapackages optional tb-goodies_1.0.1.tar.xz 4a953d32a528a62e992c415c85f1b89c 6015 metapackages optional tb-goodies_1.0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAmQgL/8ACgkQ8od7uhQa rX/Rdw/+JmzM7Ojlov1gqGaYrLsh8l6rYjRMAgskLmTLqTxXyM7qpodrGTStsoQp AQBZt39w+eyNNZMaD6oIdsSWiuHwe9GWfL0b7k/GW3xDk/RYYIS89Y2Eb8tRNlhs 7oGRJDh+92S73nrkVq9oOQG6eWkVHIr3IgYRX9VIW5WBQ6281eEQ1ZTPg/QSbXZQ rGASumok6c6Tyzbz05VlVLFLwzxQtONF9ipdtCTU0iMeeYO7uinOpkhhDJxLY2CD y+qZG0zWTkJJS0LhPkwdrMROveiFjgzQkZ/u1aZmLsPl5VIuybF6ZY0MILG5pFMb sTJd26F6dcNdfO4/QhrveNcK8uLqWD5UaOzKrGNWpo2aAlCBMOy3zEphgZSunaz6 ECgnJEST4K2Jn07r/c6zEmBDGpNWB0ociwYcDaUHsdiL1E+u/NMc938f660f3Ck2 Sk0jYW2OscwejzT+q99546bQZPK51BGxFRfL5xCncadzZlRjS1rgfpb0ocDoqisT XPDdb+rhhWwjzUlaSEvxENgEea+j1vXB33edhVGLBGRdDadljdDWIMLhieV4KjZO y4s7+Ry7XFi+oOeWVHuuYHw1QU8BYiQxRhqouMw1CK/HdnoO6TGGxsSyPrPK2QuH w1e31wkFzlfk0bEgFMr9xHEBPKg/RQ5K2Ms5oM4jxZZMMZAjgAQ= =iDRl -END PGP SIGNATURE End Message ---
Bug#1033155: migration test fails when EC key present in test keyrings
On 2023-03-18 Jonathan Wiltshire wrote: > Source: gnupg2 > Version: 2.2.40-1 > Severity: important > Tags: patch > X-Debbugs-Cc: j...@debian.org > Hi, > The stable release key for bookworm is EC, and this causes gpg1 to bail > out when it is imported as part of the migration test. Attached patch > limits the keyrings used to the archive's automatic keys, which are > still RSA. [...] Hello Jonathan, afaict currently all keys are RSA except for debian-archive-bookworm-stable.gpg. Wouldn't it be better to just skip this single key? cu Andreas
Bug#1033427: marked as done (emoslib: FTBFS in testing: intf2.c:251:27: error: ‘GRIB_UTIL_SET_SPEC_FLAGS_ONLY_PACKING’ undeclared (first use in this function))
Your message dated Sun, 26 Mar 2023 10:34:36 + with message-id and subject line Bug#1033427: fixed in emoslib 2:4.5.9-8 has caused the Debian Bug report #1033427, regarding emoslib: FTBFS in testing: intf2.c:251:27: error: ‘GRIB_UTIL_SET_SPEC_FLAGS_ONLY_PACKING’ undeclared (first use in this function) 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.) -- 1033427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emoslib Version: 2:4.5.9-7 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230323 ftbfs-bookworm Hi, During a rebuild of all packages in testing (bookworm), your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/libemos-sp-shared && /usr/bin/cc > -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 -DINTEGER_IS_INT > -DPOINTER_64 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE > -Demos_sp_shared_EXPORTS -Dgfortran -Dlinux > -I/<>/obj-x86_64-linux-gnu/module -I/<> > -I/<>/obj-x86_64-linux-gnu -I/<>/interpolation > -I/<>/bufrdc_wmo -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -fPIC -fPIC -mcmodel=medium -MD -MT > libemos-sp-shared/CMakeFiles/emos_sp_shared.dir/__/interpolation/intuvs2.c.o > -MF CMakeFiles/emos_sp_shared.dir/__/interpolation/intuvs2.c.o.d -o > CMakeFiles/emos_sp_shared.dir/__/interpolation/intuvs2.c.o -c > /<>/interpolation/intuvs2.c > /<>/interpolation/intf2.c:251:27: error: > ‘GRIB_UTIL_SET_SPEC_FLAGS_ONLY_PACKING’ undeclared (first use in this > function) > 251 | set_spec_flags |= GRIB_UTIL_SET_SPEC_FLAGS_ONLY_PACKING; > | ^ > /<>/interpolation/intf2.c:251:27: note: each undeclared > identifier is reported only once for each function it appears in > make[3]: *** > [libemos-sp-shared/CMakeFiles/emos_sp_shared.dir/build.make:3127: > libemos-sp-shared/CMakeFiles/emos_sp_shared.dir/__/interpolation/intf2.c.o] > Error 1 The full build log is available from: http://qa-logs.debian.net/2023/03/23/emoslib_4.5.9-7_testing.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230323;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230323=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: emoslib Source-Version: 2:4.5.9-8 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of emoslib, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated emoslib 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: Sun, 26 Mar 2023 09:55:22 +0100 Source: emoslib Architecture: source Version: 2:4.5.9-8 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1033427 Changes: emoslib (2:4.5.9-8) unstable; urgency=medium . * Fix for FTBFS because of deprecated code in eccodes. Closes: #1033427 Checksums-Sha1: d561c05fe49c75da1029dde1850f280e1ae22bb8 2238 emoslib_4.5.9-8.dsc 7ccd5d42b29485e3e9a1c657d4ef6bd3d9614f2c 15184 emoslib_4.5.9-8.debian.tar.xz Checksums-Sha256: 99a803090d7070318ffce2beba83896304af857aac2b1befdf6efe4a2a368733 2238 emoslib_4.5.9-8.dsc 4d3fca702bb2e807f83574e1b4172c5e59bac04e6a8862495d57aa8058792796 15184 emoslib_4.5.9-8.debian.tar.xz Files:
Processed: reassign 1033484 to libmutter-11-0
Processing commands for cont...@bugs.debian.org: > reassign 1033484 libmutter-11-0 43.2-1 Bug #1033484 [mutter] mutter assert and kills the session on displaying popups (multiple apps liek nautilus) Bug reassigned from package 'mutter' to 'libmutter-11-0'. No longer marked as found in versions mutter/43.2-1 and mutter/43.3-5. Ignoring request to alter fixed versions of bug #1033484 to the same values previously set Bug #1033484 [libmutter-11-0] mutter assert and kills the session on displaying popups (multiple apps liek nautilus) Marked as found in versions mutter/43.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1033484 in 43.2-1
Processing commands for cont...@bugs.debian.org: > found 1033484 43.2-1 Bug #1033484 [mutter] mutter assert and kills the session on displaying popups (multiple apps liek nautilus) Marked as found in versions mutter/43.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031816: [Pkg-freeipa-devel] Bug#1031816: Bug#1031816: Bug#1031816: tomcatjss: Migrate to Tomcat 10
Markus Koschany kirjoitti 24.3.2023 klo 15.35: Am Freitag, dem 24.03.2023 um 09:21 +0200 schrieb Timo Aaltonen: Markus Koschany kirjoitti 23.3.2023 klo 19.00: Control: severity -1 serious On Fri, 24 Feb 2023 11:48:36 +0200 Timo Aaltonen wrote: Upstream doesn't support tomcat10 yet, and tomcatjss fails to build with it. Unfortunately we can only support one Tomcat version per release. We should either migrate to tomcat10 or maybe it is possible to embed some of the required tomcat9 classes in your source package as a workaround provided the changes are rather small and the security impact is negligible. Right, but that's for bookworm+1? By that time I'm sure jss/tomcatjss/dogtag have gained upstream support for tomcat10. We are targeting Bookworm. We had Tomcat 8 in Stretch and Tomcat 9 in Buster and Bullseye already. Tomcat 10 also targets Java 11 and later while Tomcat 9 was intended for Java 8 and later. We ship OpenJDK 17 in Bookworm. resteasy3.0 and tomcatjss are the only packages apart from i2p that still depend on libtomcat9-java. Nice, so you expect them to migrate after bookworm is already frozen? -- t
Bug#1014831: marked as done (android-platform-frameworks-base: aapt2 command does not work at all)
Your message dated Sun, 26 Mar 2023 08:36:28 + with message-id and subject line Bug#1014831: fixed in android-platform-frameworks-base 1:13.0.0+r30-1~exp2 has caused the Debian Bug report #1014831, regarding android-platform-frameworks-base: aapt2 command does not work at all 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.) -- 1014831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: android-platform-frameworks-base Version: 1:13~beta3-1~exp1 Severity: serious Justification: must Dear Maintainer, aapt2 does not work at all, even `aapt2 version` fails. So I disabled the aapt2 invoking while building for 1:13~beta3-1~exp1: - https://salsa.debian.org/android-tools-team/android-platform-frameworks-base/-/commit/887382e Need to fix this issue before uploading to sid. Cheers, Roger --- End Message --- --- Begin Message --- Source: android-platform-frameworks-base Source-Version: 1:13.0.0+r30-1~exp2 Done: Roger Shimizu We believe that the bug you reported is fixed in the latest version of android-platform-frameworks-base, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Shimizu (supplier of updated android-platform-frameworks-base package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 Mar 2023 23:55:31 -0700 Source: android-platform-frameworks-base Architecture: source Version: 1:13.0.0+r30-1~exp2 Distribution: experimental Urgency: medium Maintainer: Android Tools Maintainers Changed-By: Roger Shimizu Closes: 1014831 Changes: android-platform-frameworks-base (1:13.0.0+r30-1~exp2) experimental; urgency=medium . * Team upload. * debian/rules: Update SDK version and sync with android-platform-tools * Split debian/aapt2.mk to debian/libaapt2.mk (Closes: #1014831) * Add debian/aapt2_test.mk * Revert "Tentatively disable invoking aapt2". Checksums-Sha1: d3a1a118429ecff350fbdf388d7f75d485252e15 3213 android-platform-frameworks-base_13.0.0+r30-1~exp2.dsc b36f0c0311d6dd32c0b319692d59ddd4d15cdd2e 17024 android-platform-frameworks-base_13.0.0+r30-1~exp2.debian.tar.xz 1b8138aba352505b084d69ca682ad156b9ef4ef8 6013 android-platform-frameworks-base_13.0.0+r30-1~exp2_source.buildinfo Checksums-Sha256: 802f14328dae908e6ff35aaf9ebbfc0771f09f892e9cc479b2cd13e856e8c621 3213 android-platform-frameworks-base_13.0.0+r30-1~exp2.dsc 67f3f75f90e1eb3405de81058afaf43ebe99fa287c69eb20f55121c4d32bb6d3 17024 android-platform-frameworks-base_13.0.0+r30-1~exp2.debian.tar.xz 10344c40d0e5ce303c539206fa1fd1c12bffb2237aaacae9399caa5933a2c1d4 6013 android-platform-frameworks-base_13.0.0+r30-1~exp2_source.buildinfo Files: dc53cabacfd119c7fc10daf3caa9a8d9 3213 devel optional android-platform-frameworks-base_13.0.0+r30-1~exp2.dsc 3f09bccfd9ddb3e4b45525b5faf3f25c 17024 devel optional android-platform-frameworks-base_13.0.0+r30-1~exp2.debian.tar.xz c8b6bc3a19e2903d0611266a7b8aa12f 6013 devel optional android-platform-frameworks-base_13.0.0+r30-1~exp2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAmQf9rAQHHJvc2hAZGVi aWFuLm9yZwAKCRCkeGsNpwM0qFpYEACarf8q57eGAUv7aZYy6++NbENAinVpsVCr 6Y0XbJzMi9CRzl7v/qiBkPvnfsYl59X4BRvOapuljjcwdzOc+dWOhkAt3TsHmrEB Iv/jQQSe5FP7u6AkGtihKn9AX26prh5NFEOKA7OWpgVAypLaUtKV3yoDVMjQfXaJ uoqdV6Rx/aEWTw9lalYplUebZKYvXHneIz688DZZ5F7ho/Ywz35BCbIxLmsZ4U+v BB4KPlPgd9str0Z+y0SVn8FcP6sASPptfupqeWiLc4h7e3G03u/LfchnbJkxyn/c 1qrAOGHaqmxWiHc0xeeb5IaJRQz/PTnwLlgnxGMyoiFCE0urvHZeUtJUCmlj9iL7 7702AZpCM/vQITr5x4AwJbN4M4Dz/tX/7PobTMMqOXO4Mvnje86j8qptZE4JRo/6 jQVWXSighQrYPszO40HZggIjnjOK6GYSzBU9G9tzA7RiRK7vTErsnO2IHQxFvau8 8X3vgsSGBPMy44W1ndtcvfJRH/D/Rb9yLQhzRNQ9t88Jt6iDxc3bDzuQI7Z/ta86 sxKWkjaHdAxs3JAhEkgN2bPss7ofJZOxFoh16gyT9+s+jbwRxsP5qqqibFJYIBH9 R3j96QoMaE+RNVaWXVDzuJ9klYZRlZ5a5zmqMUghj0t2fPXoicrdKkiZKFHk/X6c HaxonFoUXQ== =E8De -END PGP SIGNATURE End Message ---
Bug#1033496: scilab: cannot start scilab at all
Package: scilab Version: 6.1.1+dfsg2-5 Severity: grave Justification: renders package unusable X-Debbugs-Cc: rloo...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? executing scilab * What exactly did you do (or not do) that was effective (or ineffective)? typed scilab in the terminal * What was the outcome of this action? ~$ scilab Picked up _JAVA_OPTIONS: -Djava.class.path=/usr/share/java/flexdock.jar:/usr/share/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons- logging.jar:/usr/share/java/jhall.jar:/usr/share/java/lucene- core-4.10.4.jar:/usr/share/java/lucene-analyzers- common-4.10.4.jar:/usr/share/java/lucene- queryparser-4.10.4.jar:/usr/share/maven-repo/org/freehep/freehep- util/debian/freehep-util-debian.jar:/usr/share/maven-repo/org/freehep/freehep- io/debian/freehep-io-debian.jar:/usr/share/maven-repo/org/freehep/freehep- graphicsio/debian/freehep-graphicsio-debian.jar:/usr/share/java/freehep- graphicsio-emf.jar:/usr/share/java/freehep- graphics2d.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta- engine.jar:/usr/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jeuclid- core.jar:/usr/share/java/jlatexmath- fop.jar:/usr/share/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/java/xml- apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics- commons.jar:/usr/share/java/avalon- framework.jar:/usr/share/java/jlatexmath.jar:/usr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb- runtime.jar:/usr/share/scilab/modules/gui/jar/org.scilab.modules.gui.jar:/usr/share/scilab/modules/core/jar/org.scilab.modules.core.jar:/usr/share/scilab/modules/xcos/jar/org.scilab.modules.xcos.jar:/usr/share/scilab/modules/ui_data/jar/org.scilab.modules.ui_data.jar:/usr/share/scilab/modules/external_objects_java/jar/org.scilab.modules.external_objects_java.jar:/usr/share/scilab/modules/helptools/jar/org.scilab.modules.helptools.jar:/usr/share/scilab/modules/helptools/jar/scilab_en_US_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_images.jar:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar:/usr/share/scilab/modules/scinotes/jar/org.scilab.modules.scinotes.jar:/usr/share/scilab/modules/action_binding/jar/org.scilab.modules.action_binding.jar:/usr/share/scilab/modules/console/jar/org.scilab.modules.console.jar:/usr/share/scilab/modules/history_browser/jar/org.scilab.modules.history_browser.jar:/usr/share/scilab/modules/completion/jar/org.scilab.modules.completion.jar:/usr/share/scilab/modules/renderer/jar/org.scilab.modules.renderer.jar:/usr/share/scilab/modules/javasci/jar/org.scilab.modules.javasci.jar:/usr/share/scilab/modules/commons/jar/org.scilab.modules.commons.jar:/usr/share/scilab/modules/scirenderer/jar/scirenderer.jar:/usr/share/scilab/modules/graph/jar/org.scilab.modules.graph.jar:/usr/share/scilab/modules/history_manager/jar/org.scilab.modules.history_manager.jar:/usr/share/scilab/modules/types/jar/org.scilab.modules.types.jar:/usr/share/scilab/modules/graphic_objects/jar/org.scilab.modules.graphic_objects.jar:/usr/share/scilab/modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:/usr/share/scilab/modules/localization/jar/org.scilab.modules.localization.jar:/usr/share/scilab/modules/preferences/jar/org.scilab.modules.preferences.jar: -Djava.library.path=/usr/lib/jni:/usr/lib/scilab --add- opens=java.desktop/sun.awt.X11=ALL-UNNAMED --add- opens=java.desktop/sun.java2d.opengl=ALL-UNNAMED The configuration file is severely corrupted and cannot be read. It will be deleted. **note there is no configuration directory/file on my system, in my home directory. * What outcome did you expect instead? the scilab program to start. *** End of the template - remove these template lines *** -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages scilab depends on: ii scilab-cli 6.1.1+dfsg2-5 ii scilab-full-bin 6.1.1+dfsg2-5 Versions of packages scilab recommends: ii scilab-doc 6.1.1+dfsg2-5 Versions of packages scilab suggests: pn scilab-doc-fr pn scilab-doc-ja pn scilab-doc-pt-br -- no debconf information
Processed: Re: [Debian-med-packaging] Bug#1033456: genomicsdb may need build adjustment
Processing control commands: > severity -1 serious Bug #1033456 [genomicsdb] genomicsdb may need build adjustment Severity set to 'serious' from 'normal' -- 1033456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Processing commands for cont...@bugs.debian.org: > found 977027 rhino/1.7.14-1 Bug #977027 [src:rhino,src:dojo] rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]" Marked as found in versions rhino/1.7.14-1. > found 977027 dojo/1.17.2+dfsg1-2 Bug #977027 [src:rhino,src:dojo] rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]" Marked as found in versions dojo/1.17.2+dfsg1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 977027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Control: reassign -1 src:rhino, src:dojo
Control: found -1 rhino/ 1.7.14-1
Control: found -1 dojo/ 1.17.2+dfsg1-2
It appears that dojo needs to be rebuilt against the new rhino, and
rebuilding dojo against the new rhino makes it incompatible with the
old rhino.
The changes that the new rhino makes to the shrinksafe binary package
can be seen by rebuilding dojo in testing and unstable, and comparing
the results with diffoscope. I attach the diffoscope output of my own
attempt to do that.
There seems to be some kind of transition here.
It is not clear how many of the 25 packages that build-depend on rhino
are affected, as only three of them have autopkgtests, and a fourth
(ckbuilder) has an autopkgtest that is never run. At least openrefine
seems affected, as it gained a versioned dependency on librhino-java
[1] to avoid a "silent error".
To both the rhino and dojo maintainers, please investigate so we can
have this resolved for bookworm.
Regards
Graham
[1]
https://salsa.debian.org/java-team/openrefine/-/commit/eb72e6639974335db42a627e06c83aabbdb5bbc5
--- testing-binnmu/shrinksafe_1.17.2+dfsg1-2_all.deb
+++ unstable-binnmu/shrinksafe_1.17.2+dfsg1-2_all.deb
├── file list
│ @@ -1,3 +1,3 @@
│ -rw-r--r-- 0004 2022-08-13 16:48:08.00
debian-binary
│ -rw-r--r-- 000 1916 2022-08-13 16:48:08.00
control.tar.xz
│ --rw-r--r-- 00087236 2022-08-13 16:48:08.00
data.tar.xz
│ +-rw-r--r-- 00087244 2022-08-13 16:48:08.00
data.tar.xz
├── control.tar.xz
│ ├── control.tar
│ │ ├── ./md5sums
│ │ │ ├── ./md5sums
│ │ │ │┄ Files differ
├── data.tar.xz
│ ├── data.tar
│ │ ├── file list
│ │ │ @@ -43,15 +43,15 @@
│ │ │ -rw-r--r-- 0 root (0) root (0) 42 2022-08-13
16:48:08.00 ./usr/share/doc/shrinksafe/api/tag-search-index.js
│ │ │ -rw-r--r-- 0 root (0) root (0) 363 2022-08-13
16:48:08.00 ./usr/share/doc/shrinksafe/api/type-search-index.js
│ │ │ -rw-r--r-- 0 root (0) root (0) 964 2022-08-13
16:48:08.00 ./usr/share/doc/shrinksafe/changelog.Debian.gz
│ │ │ -rw-r--r-- 0 root (0) root (0)20663 2022-08-13
13:50:32.00 ./usr/share/doc/shrinksafe/copyright
│ │ │ drwxr-xr-x 0 root (0) root (0)0 2022-08-13
16:48:08.00 ./usr/share/doc-base/
│ │ │ -rw-r--r-- 0 root (0) root (0) 259 2022-08-13
16:48:08.00 ./usr/share/doc-base/shrinksafe.shrinksafe
│ │ │ drwxr-xr-x 0 root (0) root (0)0 2022-08-13
16:48:08.00 ./usr/share/java/
│ │ │ --rwxr-xr-x 0 root (0) root (0)23469 2022-08-13
16:48:08.00 ./usr/share/java/shrinksafe-1.17.2.jar
│ │ │ +-rwxr-xr-x 0 root (0) root (0)23479 2022-08-13
16:48:08.00 ./usr/share/java/shrinksafe-1.17.2.jar
│ │ │ drwxr-xr-x 0 root (0) root (0)0 2022-08-13
16:48:08.00 ./usr/share/lintian/
│ │ │ drwxr-xr-x 0 root (0) root (0)0 2022-08-13
16:48:08.00 ./usr/share/lintian/overrides/
│ │ │ -rw-r--r-- 0 root (0) root (0) 239 2022-08-13
15:14:30.00 ./usr/share/lintian/overrides/shrinksafe
│ │ │ drwxr-xr-x 0 root (0) root (0)0 2022-08-13
16:48:08.00 ./usr/share/man/
│ │ │ drwxr-xr-x 0 root (0) root (0)0 2022-08-13
16:48:08.00 ./usr/share/man/man1/
│ │ │ -rw-r--r-- 0 root (0) root (0) 575 2022-08-13
16:48:08.00 ./usr/share/man/man1/shrinksafe.1.gz
│ │ │ lrwxrwxrwx 0 root (0) root (0)0 2022-08-13
16:48:08.00 ./usr/bin/shrinksafe -> ../share/java/shrinksafe.jar
│ │ ├── ./usr/share/java/shrinksafe-1.17.2.jar
│ │ │ ├── zipinfo {}
│ │ │ │ @@ -1,14 +1,14 @@
│ │ │ │ -Zip file size: 23469 bytes, number of entries: 12
│ │ │ │ +Zip file size: 23479 bytes, number of entries: 12
│ │ │ │ -rw 2.0 fat0 bx stor 22-Aug-13 16:48 META-INF/
│ │ │ │ -rw-r--r-- 2.0 unx 175 b- defN 22-Aug-13 16:48
META-INF/MANIFEST.MF
│ │ │ │ -rw 1.0 fat0 b- stor 22-Aug-13 16:48 org/
│ │ │ │ -rw 1.0 fat0 b- stor 22-Aug-13 16:48 org/dojotoolkit/
│ │ │ │ -rw 1.0 fat0 b- stor 22-Aug-13 16:48
org/dojotoolkit/shrinksafe/
│ │ │ │ --rw 2.0 fat17182 bl defN 22-Aug-13 16:48
org/dojotoolkit/shrinksafe/Compressor.class
│ │ │ │ +-rw 2.0 fat17210 bl defN 22-Aug-13 16:48
org/dojotoolkit/shrinksafe/Compressor.class
│ │ │ │ -rw 2.0 fat 534 bl defN 22-Aug-13 16:48
org/dojotoolkit/shrinksafe/DebugData.class
│ │ │ │ -rw 2.0 fat 1557 bl defN 22-Aug-13 16:48
org/dojotoolkit/shrinksafe/Main$IProxy.class
│ │ │ │ -rw 2.0 fat 7781 bl defN 22-Aug-13 16:48
org/dojotoolkit/shrinksafe/Main.class
│ │ │ │ -rw 2.0 fat 4714 bl defN 22-Aug-13 16:48
Processed (with 2 errors): rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Processing control commands: > reassign -1 src:rhino, src:dojo Bug #977027 [shrinksafe] rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]" Bug reassigned from package 'shrinksafe' to 'src:rhino,src:dojo'. Ignoring request to alter found versions of bug #977027 to the same values previously set Ignoring request to alter fixed versions of bug #977027 to the same values previously set > found -1 rhino/ 1.7.14-1 Unknown command or malformed arguments to command. > found -1 dojo/ 1.17.2+dfsg1-2 Unknown command or malformed arguments to command. -- 977027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
