Bug#897975: [gdm3]
The wayland issue should be gone in bookworm/sid. As stated in https://gitlab.gnome.org/GNOME/gdm/-/issues/103, https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/128 is merged (in gdm 40). It supersedes https://gitlab.gnome.org/GNOME/gdm/merge_requests/37 I cannot tell about the initial gdm3 "ICELockAuthFile fail: Already exists" Xorg related issue. It seems unrelated. Cheers, Alban
Bug#1018211: mirror submission for mirror.gi.co.id
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirror.gi.co.id Type: leaf Archive-architecture: amd64 arm64 armel armhf i386 mips mips64el mipsel powerpc ppc64el s390x Archive-http: /debian/ Archive-rsync: debian/ Maintainer: Wahyu Wijanarko Country: ID Indonesia Location: Jakarta Sponsor: PT. Global Intermedia Nusantara https://www.gi.co.id Trace Url: http://mirror.gi.co.id/debian/project/trace/ Trace Url: http://mirror.gi.co.id/debian/project/trace/ftp-master.debian.org Trace Url: http://mirror.gi.co.id/debian/project/trace/mirror.gi.co.id
Bug#1018210: gnome-shell: Shell doesn't work because of libsoup2 and libsoup3 symbols
Package: gnome-shell Version: 42.4-1+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: sebastianlacue...@gmail.com Gnome shell does not start (neither gdm3 does). Relevant errors: journalctl -p 3 -xb ... ago 26 21:42:58 colossus gnome-session-binary[1630]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ago 26 21:42:58 colossus gnome-session-binary[1630]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ago 26 21:43:01 colossus gnome-shell[1682]: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. ago 26 21:43:01 colossus gnome-session-binary[1630]: Unrecoverable failure in required component org.gnome.Shell.desktop ago 26 21:43:01 colossus gdm-launch-environment][1411]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ago 26 21:43:02 colossus gnome-session-binary[1844]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ago 26 21:43:02 colossus gnome-session-binary[1844]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ago 26 21:43:03 colossus gnome-shell[1870]: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. ago 26 21:43:03 colossus gnome-shell[1895]: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. ago 26 21:43:03 colossus gnome-session-binary[1844]: Unrecoverable failure in required component org.gnome.Shell.desktop ago 26 21:43:03 colossus gsd-datetime[1942]: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. ago 26 21:43:03 colossus gsd-datetime[1973]: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. ago 26 21:43:03 colossus gnome-session-binary[1844]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Datetime.desktop -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (700, 'testing'), (699, 'unstable'), (698, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8), LANGUAGE=es_UY:es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gir1.2-accountsservice-1.0 22.08.8-1 ii gir1.2-adw-1 1.2~beta-1 ii gir1.2-atk-1.0 2.38.0-1 ii gir1.2-atspi-2.0 2.44.1-1 ii gir1.2-freedesktop 1.73.0-2 ii gir1.2-gcr-3 3.41.1-1 ii gir1.2-gdesktopenums-3.0 43~alpha-1 ii gir1.2-gdkpixbuf-2.0 2.42.9+dfsg-1 ii gir1.2-gdm-1.0 42.0-1 ii gir1.2-geoclue-2.0 2.6.0-1 ii gir1.2-glib-2.0 1.73.0-2 ii gir1.2-gnomebluetooth-3.042.3-1 ii gir1.2-gnomedesktop-3.0 43~alpha-3 ii gir1.2-graphene-1.0 1.10.8-1 ii gir1.2-gstreamer-1.0 1.20.3-1 ii gir1.2-gtk-3.0 3.24.34-3 ii gir1.2-gtk-4.0 4.7.2+ds-3 ii gir1.2-gweather-4.0 4.1.0-2 ii gir1.2-ibus-1.0 1.5.26-4 ii gir1.2-mutter-10 42.4-2 ii gir1.2-nm-1.01.38.4-1 ii gir1.2-nma-1.0 1.8.40-1 ii gir1.2-pango-1.0 1.50.9+ds-1 ii gir1.2-polkit-1.0121-2 ii gir1.2-rsvg-2.0 2.54.4+dfsg-1 ii gir1.2-soup-2.4 2.74.2-3 ii gir1.2-upowerglib-1.00.99.20-1 ii gir1.2-webkit2-4.0 2.37.90-1 ii gnome-backgrounds42.0-1 ii gnome-settings-daemon43~beta-1+b1 ii gnome-shell-common 42.4-1 ii gsettings-desktop-schemas43~alpha-1 ii gstreamer1.0-pipewire0.3.56-1 ii libatk-bridge2.0-0 2.38.0-4 ii libatk1.0-0 2.38.0-1 ii libc62.34-4 ii libcairo21.16.0-6 ii libecal-2.0-13.44.4-1 ii libedataserver-1.2-263.44.4-1 ii libgcr-base-3-1 3.41.1-1 ii libgdk-pixbuf-2.0-0 2.42.9+dfsg-1 ii libgirepository-1.0-11.73.0-2 ii
Bug#1018209: osk-sdl: Add all available DRI drivers
Package: osk-sdl
Version: 0.67-2
Severity: normal
Tags: patch
X-Debbugs-Cc: drati...@gmail.com
Dear Maintainer,
In the past days, I have found two systems where osk-sdl didn't include the
correct DRI library in the initramfs. (A Steam Deck, which needs
radeonsi_drm.so and an Asus T100TA Bay Trail tablet, which needs crocus_drm.so)
So instead of trying to maintain a list of all the possible DRI libraries that
might be needed, I propose we just include them all. This is reasonable,
because they are already hardlinks of the same file.
I have checked that in Debian main, files ending in "_dri.so" only come from
libgl1-mesa-dri, and that on amd64 and on the Pinephone, all of those files are
hardlinks.
On my Steam Deck, I have checked that my patch changes the size of the initrd
from 120600 to 120601 kB, and that it works. I haven't yet tested it on any
other devices.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 5.18.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages osk-sdl depends on:
ii cryptsetup 2:2.5.0-2
ii cryptsetup-initramfs 2:2.5.0-2
ii debconf [debconf-2.0] 1.5.79
ii fonts-dejavu-core 2.37-2
ii libc6 2.34-3
ii libcryptsetup122:2.5.0-2
ii libegl11.4.0-1
ii libgcc-s1 12.1.0-8
ii libgl1 1.4.0-1
ii libgles2 1.4.0-1
ii libsdl2-2.0-0 2.0.22+dfsg-6
ii libsdl2-ttf-2.0-0 2.20.0+dfsg-1
ii libstdc++6 12.1.0-8
osk-sdl recommends no packages.
osk-sdl suggests no packages.
-- debconf information excluded
>From 848e446a00efb3ce5ffb07832659caa5e7a4688f Mon Sep 17 00:00:00 2001
From: Balint Kovacs
Date: Sat, 27 Aug 2022 01:32:26 +0100
Subject: [PATCH] Include every possible DRI driver
---
debian/initramfs/hooks/osk-sdl | 37 --
1 file changed, 13 insertions(+), 24 deletions(-)
diff --git a/debian/initramfs/hooks/osk-sdl b/debian/initramfs/hooks/osk-sdl
index 2b65692..1f59fb9 100755
--- a/debian/initramfs/hooks/osk-sdl
+++ b/debian/initramfs/hooks/osk-sdl
@@ -18,52 +18,41 @@ esac
# Many dri modules are kmsro, use a symlink there
dri_inst() {
-so_src="${libdir}/dri/$1"
-shift
-sos=$@
-so_sum=$(md5sum "${so_src}" | awk '{ print $1 }')
-
-copy_exec "${so_src}"
-for so in $sos; do
-if [ "$(md5sum "${libdir}/dri/${so}" | awk '{ print $1 }')" =
"${so_sum}" ]; then
- ln -s "$(basename "${so_src}")" "${DESTDIR}/${libdir}/dri/${so}"
+for so in "${libdir}/dri/"*_dri.so; do
+current_so_sum="$(md5sum "${so}" | awk '{ print $1 }')"
+if [ "x${current_so_sum}" = "x${so_sum}" ]; then
+ln -s "$(basename "${so_src}")" "${DESTDIR}/${so}"
else
- copy_exec "${libdir}/dri/${so}"
+copy_exec "${so}"
+so_sum="${current_so_sum}"
+so_src="${so}"
fi
done
}
-IMX_KMSRO="etnaviv_dri.so imx-drm_dri.so imx-dcss_dri.so mxsfb-drm_dri.so"
-
case "$DPKG_ARCH" in
arm64)
libdir=/usr/lib/aarch64-linux-gnu
+dri_inst
+copy_exec "$libdir/libGLESv2.so.2"
+
# Pinephone
if grep -q "allwinner" /proc/device-tree/compatible 2>/dev/null; then
-copy_exec "$libdir/dri/sun4i-drm_dri.so"
-copy_exec "$libdir/libGLESv2.so.2"
manual_add_modules goodix goodix_ts
# Librem 5 and Librem 5 Devkit
elif grep -q "imx" /proc/device-tree/compatible 2>/dev/null; then
-dri_inst ${IMX_KMSRO}
-copy_exec "$libdir/libGLESv2.so.2"
manual_add_modules edt-ft5x06 goodix pwm_vibra goodix_ts
- # PinePhone Pro
- elif grep -q "PinePhonePro" /proc/device-tree/model 2>/dev/null; then
-dri_inst ${IMX_KMSRO} panfrost_dri.so rockchip_dri.so
-copy_exec "$libdir/libGLESv2.so.2"
+# PinePhone Pro
+elif grep -q "PinePhonePro" /proc/device-tree/model 2>/dev/null; then
manual_add_modules goodix pwm_vibra goodix_ts
# Generic / Installer (needs to include all of the above)
else
-dri_inst ${IMX_KMSRO} sun4i-drm_dri.so panfrost_dri.so
rockchip_dri.so
-copy_exec "$libdir/libGLESv2.so.2"
manual_add_modules edt-ft5x06 goodix pwm_vibra goodix_ts
fi
;;
amd64)
libdir=/usr/lib/x86_64-linux-gnu
-AMD64_KMSRO="vmwgfx_dri.so virtio_gpu_dri.so i965_dri.so iris_dri.so
kms_swrast_dri.so"
-dri_inst ${AMD64_KMSRO}
+dri_inst
copy_exec
Bug#1018208: RM: gnome-shell-extension-xrdesktop -- RoQA; unmaintained, depends on removed package
Package: ftp.debian.org X-Debbugs-Cc: gnome-shell-extension-xrdesk...@packages.debian.org Affects: src:gnome-shell-extension-xrdesktop Please remove gnome-shell-extension-xrdesktop from Debian. The extension only works with gnome-shell-xrdesktop which was removed from Debian with https://bugs.debian.org/1008471 (The package depends on gnome-shell instead of gnome-shell-xrdesktop like it should.) It was removed from Testing because it never declared compatibility with GNOME Shell 40+ a year ago. https://bugs.debian.org/993065 On behalf of the Debian GNOME team, Jeremy Bicha
Bug#993014: cifs-utils non-parallel FTBFS
Hi. Now that this is finally fixed in sid, here is a proposed diff for bullseye, including changelog. It's the same fix which is now in sid. I've tested and it works for me. Thanks. diff -Nru cifs-utils-6.11/debian/changelog cifs-utils-6.11/debian/changelog --- cifs-utils-6.11/debian/changelog2022-05-10 22:12:42.0 +0200 +++ cifs-utils-6.11/debian/changelog2022-08-27 02:20:00.0 +0200 @@ -1,3 +1,9 @@ +cifs-utils (2:6.11-3.1+deb11u2) bullseye; urgency=medium + + * Fix non-parallel build. Closes: #993014. + + -- Michael Tokarev Sat, 27 Aug 2022 02:20:00 +0200 + cifs-utils (2:6.11-3.1+deb11u1) bullseye-security; urgency=high * Non-maintainer upload by the Security Team. diff -Nru cifs-utils-6.11/debian/patches/root_sbindir-hook.patch cifs-utils-6.11/debian/patches/root_sbindir-hook.patch --- cifs-utils-6.11/debian/patches/root_sbindir-hook.patch 1970-01-01 01:00:00.0 +0100 +++ cifs-utils-6.11/debian/patches/root_sbindir-hook.patch 2022-08-27 02:20:00.0 +0200 @@ -0,0 +1,11 @@ +--- a/Makefile.am b/Makefile.am +@@ -118,7 +118,7 @@ + + SUBDIRS = contrib + +-install-exec-hook: ++install-exec-hook: install-root_sbinPROGRAMS + (cd $(DESTDIR)$(ROOTSBINDIR) && ln -sf mount.cifs mount.smb3) + + install-data-hook: diff -Nru cifs-utils-6.11/debian/patches/series cifs-utils-6.11/debian/patches/series --- cifs-utils-6.11/debian/patches/series 2022-05-10 22:12:42.0 +0200 +++ cifs-utils-6.11/debian/patches/series 2022-08-27 02:20:00.0 +0200 @@ -5,3 +5,4 @@ 0011-fix-regression-for-CVE-2021-20208.patch CVE-2022-27239-mount.cifs-fix-length-check-for-ip-op.patch mount.cifs-fix-verbose-messages-on-option-parsing.patch +root_sbindir-hook.patch
Bug#1018205: rumur: possible missing linking to latomic
On 8/26/22 15:57, Tobias Frost wrote: Source: rumur Version: 2020.12.20-1 Severity: important Looking at the autopkgtest results for arm64 and armel: /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_read': checker.c:(.text+0x3b90): undefined reference to `__atomic_load_16' /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_write': checker.c:(.text+0x3bb8): undefined reference to `__atomic_store_16' /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_cas': checker.c:(.text+0x3bf0): undefined reference to `__atomic_compare_exchange_16' /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_cas_val': checker.c:(.text+0x3c2c): undefined reference to `__atomic_compare_exchange_16' This could be missing linking to libatomic. (Did not check if it is actually the case, just by looking at the symbols) I thought this was fixed in 620e514c1d322e05a9e67bb09cd0dc68cb810d38¹ that made it into 2020.05.27-1, but it seems not. Am I expected to fix this in a patch release to 2020.12.20-1? Because I’m also the upstream maintainer and this package has a relatively small community of users who upgrade frequently, I usually just roll fixes into the next upstream release. So if this is not reproducible on the latest (2022.08.20-1) is there anything to be done? ¹ https://github.com/Smattr/rumur/commit/620e514c1d322e05a9e67bb09cd0dc68cb810d38
Bug#1018202: rumur: VCS-* pointing to upstream repository
On 8/26/22 15:48, Tobias Frost wrote: Source: rumur Version: 2020.12.20-1 Severity: normal Dear Maintainer, d/control VCS-* fields are pointing to the upstream repository, however, they are reserverd for the VCS of the packaging. (See Policy 5.6.26) [1] [1] https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-vcs-fields I’m sorry, I don’t understand what’s being objected to here. d/control lists: Vcs-Git: https://github.com/Smattr/rumur.git -b packaging/debian Yes, this is the upstream repository. But it is also the repository where packaging happens. Specifically the branch indicated here (`packaging/debian`) is where I do the Debian packaging. I’m the upstream maintainer as well. Is this not how I should list this?
Bug#1018206: luatex loses or changes text when discretionaries with priorities are used
Package: texlive-latex-base Version: 2022.20220605-1 Severity: wishlist As described in https://tex.stackexchange.com/q/652458 https://tex.stackexchange.com/q/652458, luatex loses or changes text (not formatting!) in particular circumstances. According to https://mailman.ntg.nl/pipermail/dev-luatex/2022-July/006684.html https://mailman.ntg.nl/pipermail/dev-luatex/2022-July/006684.html, this seems to be repaired in the revision 7531 in TL 2023 (perhaps a revision or two later). I know it's a long stretch, but I'd welcome it if, for proper testing, the fix finds its way into Debian, ideally into Debian stable, better sooner than later. Thanks in advance, Peter
Bug#1018205: rumur: possible missing linking to latomic
Source: rumur Version: 2020.12.20-1 Severity: important Looking at the autopkgtest results for arm64 and armel: /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_read': checker.c:(.text+0x3b90): undefined reference to `__atomic_load_16' /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_write': checker.c:(.text+0x3bb8): undefined reference to `__atomic_store_16' /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_cas': checker.c:(.text+0x3bf0): undefined reference to `__atomic_compare_exchange_16' /usr/bin/ld: /tmp/ccbniKRN.o: in function `atomic_cas_val': checker.c:(.text+0x3c2c): undefined reference to `__atomic_compare_exchange_16' This could be missing linking to libatomic. (Did not check if it is actually the case, just by looking at the symbols) -- tobi
Bug#1018204: RM: nrepl-clojure [i386 ppc64el s390x] -- NBS; no longer built on these architectures
Package: ftp.debian.org Severity: normal Control: block 1014918 by -1 nrepl-clojure (0.9.0-6) unstable; urgency=medium * Team upload. [ Louis-Philippe Véronneau ] * d/control: stop building on s390x. That one too fails to build. -- Louis-Philippe Véronneau Fri, 19 Aug 2022 23:39:04 -0400 nrepl-clojure (0.9.0-5) unstable; urgency=medium * Team upload. [ Louis-Philippe Véronneau ] * d/control: stop building on ppc64el. That one too fails to build... -- Louis-Philippe Véronneau Wed, 17 Aug 2022 20:35:04 -0400 nrepl-clojure (0.9.0-4) unstable; urgency=medium * Team upload. [ Louis-Philippe Véronneau ] * d/control: stop building on i386 and armhf. Apparently armhf FTBFS, at this point all 32-bit arches are getting axed. -- Louis-Philippe Véronneau Fri, 12 Aug 2022 23:35:22 -0400 dak shows several build dependencies for binary-all packages that are not relevant for the removal.
Bug#1018203: kodi-inputstream-adaptive: FTBFS on ppc64el (regression in endian detection)
Package: kodi-inputstream-adaptive Version: 20.2.0+ds1-1 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Hi Vasyl, The kodi-inputstream-adaptive package is failing to build on ppc64el in Debian because it fails to detect the endianness of the platform. The attached patch fixes this build failure by making use of the general-purpose macros that are exported by default by gcc. (This also fixes the build on riscv64, which is not a release architecture in Debian but is in Ubuntu.) Please consider applying this patch in Debian. -- 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 diff -Nru kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/byte-order-all-archs kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/byte-order-all-archs --- kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/byte-order-all-archs 1969-12-31 16:00:00.0 -0800 +++ kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/byte-order-all-archs 2022-08-26 14:04:30.0 -0700 @@ -0,0 +1,18 @@ +Description: fix endian detection to be portable to all gcc archs +Author: Steve Langasek +Last-Update: 2022-08-26 +Forwarded: no + +Index: kodi-inputstream-adaptive-20.2.0+ds1/bento4-embedded/Source/C++/Core/Ap4Config.h +=== +--- kodi-inputstream-adaptive-20.2.0+ds1.orig/bento4-embedded/Source/C++/Core/Ap4Config.h kodi-inputstream-adaptive-20.2.0+ds1/bento4-embedded/Source/C++/Core/Ap4Config.h +@@ -56,7 +56,7 @@ + #if defined(_M_IX86) || defined(_M_X64) || defined(_M_ARM) || defined(_M_ARM64) + #define AP4_PLATFORM_BYTE_ORDER AP4_PLATFORM_BYTE_ORDER_LITTLE_ENDIAN + #endif +-#elif defined(__i386__) || defined(__x86_64__) || defined(__arm__) || defined(__arm64__) || defined(__aarch64__) ++#elif defined(__i386__) || defined(__x86_64__) || defined(__arm__) || defined(__arm64__) || defined(__aarch64__) || (__BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__) + #define AP4_PLATFORM_BYTE_ORDER AP4_PLATFORM_BYTE_ORDER_LITTLE_ENDIAN + #endif + #endif diff -Nru kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/series kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/series --- kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/series 2022-08-04 00:19:38.0 -0700 +++ kodi-inputstream-adaptive-20.2.0+ds1/debian/patches/series 2022-08-26 13:54:03.0 -0700 @@ -1,2 +1,3 @@ 0001-Use-packaged-libwebm.patch 0002-CVE-2019-17452-2021-32265-etc.patch +byte-order-all-archs
Bug#1018202: rumur: VCS-* pointing to upstream repository
Source: rumur Version: 2020.12.20-1 Severity: normal Dear Maintainer, d/control VCS-* fields are pointing to the upstream repository, however, they are reserverd for the VCS of the packaging. (See Policy 5.6.26) [1] [1] https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-vcs-fields -- Cheers, tobi
Bug#1018201: mirror submission for mirror.clarkson.edu
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirror.clarkson.edu Type: leaf Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x Archive-http: /debian/ Archive-rsync: debian/ Maintainer: Admins Country: US United States Location: Potsdam NY Sponsor: Clarkson Open Source Institute https://cosi.clarkson.edu Trace Url: http://mirror.clarkson.edu/debian/project/trace/ Trace Url: http://mirror.clarkson.edu/debian/project/trace/ftp-master.debian.org Trace Url: http://mirror.clarkson.edu/debian/project/trace/mirror.clarkson.edu
Bug#1018200: antennavis recommends nec which isn't available anymore
Package: antennavis Version: 0.3.1-4+b1 Severity: normal X-Debbugs-Cc: dfo...@gmail.com Dear maintainer, antennavis has "Recommends: nec" but nec was removed from Debian: https://tracker.debian.org/pkg/nec thanks, Daniele
Bug#1018140: override: clutter-1.0:oldlibs/optional
Hello, On Fri 26 Aug 2022 at 01:33AM +01, Simon McVittie wrote: > > On Thu, 25 Aug 2022 at 16:26:21 -0700, Sean Whitton wrote: >> On Thu 25 Aug 2022 at 08:50PM +01, Simon McVittie wrote: >> > clutter-1.0 is unmaintained upstream (#996690), but has too many >> > reverse-dependencies to remove immediately. Please move all of its binary >> > packages into oldlibs to make this more obvious. >> >> Done. Just for next time, please list the binary packages in the >> request, as we have to feed the names of each of them to dak. > > Sorry, reportbug asked me for "either source of [sic] binary package" > so I assumed either one was equally useful to the ftp team. Is there a > syntax in which the ftp team would prefer to receive override requests > for easiest review/copy/paste, so I can ask for reportbug to populate > the bug report with that syntax, analogous to how it knows how to compose > ben and wanna-build syntax for release team bugs? That would be great. This is used for most requests: dak override --done=NNN PACKAGE SECTION PRIORITY And there is also dak control-overrides, where you feed it lines: echo "PACKAGE PRIORITY SECTION\nPACKAGE2 PRIORITY2 SECTION2\n" \ | dak control-overrides -C and then manually close the bug. The latter is what I used for your case because I had to build up a list of package names anyway. But the former is probably best for reportbug generation, as more copy-pastable? > (Perhaps the ideal thing would be if I could tell reportbug that I > want to override "src:clutter-1.0 src:cogl", and it would do the > appropriate apt queries to expand that into a list of binary packages > ready for the ftp team's use?) I think sometimes you might want to just change the source package overrides though? -- Sean Whitton signature.asc Description: PGP signature
Bug#1018199: buster-pu: package evemu/2.7.0-1+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Stephen Kitt
* Add upstream fix for FTBFS with recent kernel headers.
(Closes: #971161)
Test-only issue, I was able to reproduce the FTBFS on buster.
diff -Nru evemu-2.7.0/debian/changelog evemu-2.7.0/debian/changelog
--- evemu-2.7.0/debian/changelog2018-05-26 22:01:16.0 +0300
+++ evemu-2.7.0/debian/changelog2022-08-26 22:17:57.0 +0300
@@ -1,3 +1,11 @@
+evemu (2.7.0-1+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for FTBFS with recent kernel headers.
+(Closes: #971161)
+
+ -- Adrian Bunk Fri, 26 Aug 2022 22:17:57 +0300
+
evemu (2.7.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru evemu-2.7.0/debian/patches/series evemu-2.7.0/debian/patches/series
--- evemu-2.7.0/debian/patches/series 2018-05-25 22:40:58.0 +0300
+++ evemu-2.7.0/debian/patches/series 2022-08-26 22:17:50.0 +0300
@@ -1,2 +1,3 @@
0002-check-test-conditions.patch
0003-fix-python-startup-crash.patch
+swmax-test.patch
diff -Nru evemu-2.7.0/debian/patches/swmax-test.patch
evemu-2.7.0/debian/patches/swmax-test.patch
--- evemu-2.7.0/debian/patches/swmax-test.patch 1970-01-01 02:00:00.0
+0200
+++ evemu-2.7.0/debian/patches/swmax-test.patch 2022-08-26 22:17:40.0
+0300
@@ -0,0 +1,94 @@
+commit 86a5627dbeac8d9d9bc34326a758d6a477e876e4
+Author: Peter Hutterer
+Date: Wed Sep 30 08:53:36 2020 +1000
+
+test: replace the hardcoded EV_MAX array with the libevdev one
+
+Kernel 5.8 changed the value of SW_MAX but libevdev has a built-in check
for
+out-of-range bits (it silently discards those).
+
+So where evemu is built against a new kernel but a libevdev that hasn't
been
+updated yet, our test expects bit up to the new SW_MAX while libevdev
+discards all bits above the old SW_MAX.
+
+Fix this by making sure the test and uses the same value of the
+respective type max as evemu itself does.
+
+Fixes #3
+
+Signed-off-by: Peter Hutterer
+
+--- a/test/Makefile.am
b/test/Makefile.am
+@@ -11,8 +11,12 @@
+ test_cxx_compile_LDADD = $(top_builddir)/src/libevemu.la
+
+ test_evemu_create_SOURCES = test-evemu-create.c
+-test_evemu_create_LDADD = $(top_builddir)/src/libevemu.la
+-test_evemu_create_LDFLAGS = -static
++test_evemu_create_LDADD = \
++ $(top_builddir)/src/libevemu.la \
++ $(LIBEVDEV_LIBS) \
++ $(NULL)
++test_evemu_create_LDFLAGS = -no-install
++test_evemu_create_CFLAGS = $(LIBEVDEV_CFLAGS)
+ endif
+
+ CLEANFILES = evemu.tmp.*
+--- a/test/test-evemu-create.c
b/test/test-evemu-create.c
+@@ -10,6 +10,7 @@
+ #include
+ #include "evemu.h"
+ #include
++#include
+
+ #define UNUSED __attribute__((unused))
+
+@@ -45,19 +46,6 @@
+ ALLFLAGS = (WITHNAME << 1) - 1
+ };
+
+-static int max[EV_CNT] = {
+- 0, /* EV_SYN */
+- KEY_MAX, /* EV_KEY */
+- REL_MAX, /* EV_REL */
+- ABS_MAX, /* EV_ABS */
+- MSC_MAX, /* EV_MSC */
+- SW_MAX, /* EV_SW */
+- LED_MAX, /* EV_LED */
+- SND_MAX, /* EV_SND */
+- REP_MAX, /* EV_REP */
+- FF_MAX /* EV_FF */
+-};
+-
+ static void println(int fd, int flags, const char *format, ...)
+ {
+ va_list args;
+@@ -119,8 +107,8 @@
+ if (flags & BITS) {
+ int i;
+ for (i = 0; i < EV_CNT; i++) {
+- int j;
+- for (j = 0; j <= max[i]; j += 8) {
++ int max = libevdev_event_type_get_max(i);
++ for (int j = 0; j <= max; j += 8) {
+ println(fd, flags, bits, i, 0xff, 0xff, 0xff,
0xff, 0xff, 0xff, 0xff, 0xff);
+ if (flags & EMPTYLINE)
+ println(fd, flags, "%s", emptyline);
+@@ -177,11 +165,14 @@
+ if (flags & BITS) {
+ int i, j;
+ for (i = 1; i < EV_CNT; i++) {
++ int max = libevdev_event_type_get_max(i);
++
+ if (!evemu_has_bit(dev, i))
+ continue;
+
+- for (j = 0; j <= max[i]; j++)
++ for (j = 0; j <= max; j++) {
+ assert(evemu_has_event(dev, i, j));
++ }
+ }
+ }
+
Bug#1017777: bullseye-pu: package glibc/2.31-13+deb11u4
On 2022-08-26 18:48, Adam D. Barratt wrote: > Control: tags -1 + confirmed d-i > > On Sat, 2022-08-20 at 10:35 +0200, Aurelien Jarno wrote: > > There are multiple fixes in this upload, mostly coming from the > > upstream > > stable branch: > > - One security issue with CVE entry > > - Multiple overflow fixes to wide string functions > > - Failure to enforce libio vtable protection > > - A performance issue with string functions affecting Skylake-X CPUs > > (up > > to 40% slower) > > - A new NEW.Debian.gz entry for libc6-dev explaining users how to > > switch > > from to the TI-RPC implementation following the Sun RPC > > implementation > > removal in glibc 2.31 > > - Make grantpt usable after multi-threaded fork to prevent Ansible > > deadlocks. > > > > Please go ahead, thanks. > Thanks for the review, I have just uploaded it. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1017034: ITP: golang-github-marten-seemann-qtls-go1-19 -- Go standard library TLS 1.30 implementation, modified for QUIC (Go-1.19)
Hi William, Thank you for your contribution; reply follows inline: William Wilson writes: > > I have packaged this and uploaded it to a PPA: > https://launchpad.net/~jawn-smith/+archive/ubuntu/devel-proposed/+sourcefiles/golang-github-marten-seemann-qtls-go1-19/0.1.0-1~ppa1/golang-github-marten-seemann-qtls-go1-19_0.1.0-1~ppa1.dsc > This package is not Debian Policy compliant https://www.debian.org/doc/debian-policy > If someone could sponsor this I'd be very appreciative! > If you're interested in sponsorship, here is one entry point into the process: https://wiki.debian.org/Mentors However, if you're not interested in making your package Policy-compliant, and/or are not not interested in maintaining golang-github-marten-seemann-qtls-go1-19 long-term, either by yourself, or as part of the Debian Golang Team, then it may be best to convert this ITP to an RFP. Sadly I won't have much free time until October, so won't be much help. By the way, do you know when Ubuntu 22.10 will make its last sync from Debian? Take care, Nicholas signature.asc Description: PGP signature
Bug#1018198: modemmanager: FTBFS test failing with common_test_ccwa_response: assertion failed: (result)
Package: modemmanager Version: 1.18.10-1 Severity: serious Tags: upstream patch bookworm sid ftbfs Justification: FTBFS Forwarded: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/870 X-Debbugs-Cc: he...@debian.org Hey, when I try a recompiliation of ModemManager, the tests are failing with: /test_ccwa_response: ** ERROR:test-modem-helpers.c:4204:common_test_ccwa_response: assertion failed: (result) FAIL GTester: last random seed: R02S1c9c8a2a8c689230b60594a14f54dc63 make[5]: *** [Makefile:889: test-nonrecursive] Terminated make[5]: Leaving directory '/<>/src/tests' make[4]: *** [Makefile:736: check-am] Error 2 make[4]: Leaving directory '/<>/src/tests' make[3]: *** [Makefile:1991: check-recursive] Error 1 make[3]: Leaving directory '/<>/src' make[2]: *** [Makefile:2142: check] Error 2 make[2]: Leaving directory '/<>/src' make[1]: *** [Makefile:540: check-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2 make: *** [debian/rules:12: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 This bug is also reported upstream https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/601 It seems like the issue is that with new glibc >= 2.73.2 PCRE1 is replaced with PCRE2. There is also a first patch for it, but this does not fix this issue completly. I initally wanted to fix my breakage of my UMTS stick failing https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/621 I will not open a second bug report as the bugfix is don with same MR. regards, hefee -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages modemmanager depends on: ii libc6 2.34-6 ii libglib2.0-0 2.73.3-2 ii libgudev-1.0-0 237-2 ii libmbim-glib4 1.26.4-1 ii libmbim-proxy 1.26.4-1 ii libmm-glib01.18.10-1 ii libpolkit-gobject-1-0 0.105-33 ii libqmi-glib5 1.30.8-1 ii libqmi-proxy 1.30.8-1 ii libqrtr-glib0 1.2.2-1 ii libsystemd0251.4-1 ii policykit-10.105-33 Versions of packages modemmanager recommends: ii usb-modeswitch 2.6.1-3+b1 modemmanager suggests no packages. -- no debconf information
Bug#1018173: libreoffice: Please upload final releases
Hi, Am 26.08.22 um 15:55 schrieb Itaï BEN YAACOV: Since 7.3.1 (which is no longer installable) you have only uploaded release candidates to Debian/sid. Please consider uploading final releases as well, before moving on to candidates of the next release. 1. I understand that unstable is the place to stage pre-release software. But this does not mean it must only contain such. Moreover, given Debian's slow release cycle some users (such as myself) use it for daily work, rather than for testing new software. Oh, and for completeness; given this sounds like you do that (or even think of doing this): you are *NOT* supposed to keep your unstable at a point in time or even selectively install stuff from older/newer unstables. This ia a distribution, not something to cherry-pick anything you like from/to. (Except for experimental packages that is) Even if I uploaded let's say 7.4.0 and uploaded 7.4.1 rc1 immediately there will be no support for 7.4.0 in unstable anymore. Making your wish moot except only for the cosmetic 7.4.0 rc3 vs. 7.4.0. There's no "we support any random version which might be in unstable at some point in time for time X". Bugs and other issues (like rebuilds for newer libraries) get fixed with new uploads/bin-NMUs and that will be it. Regards, Rene
Bug#1018197: Removal notice: obsolete
Source: haskell-cprng-aes Version: 0.6.1-8 Severity: serious This package is deprecated in favor or cryptonite. I intend to remove this package. -- Ilias
Bug#1018196: Removal notice: obsolete
Source: haskell-cipher-aes Version: 0.2.11-9 Severity: serious This package is deprecated in favor of cryptonite. I intend to remove this package. -- Ilias
Bug#1018195: gnome-shell-extension-dashtodock: needs update for GNOME Shell 43
Package: gnome-shell-extension-dashtodock Version: 72-2 Severity: important Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-43 Forwarded: https://github.com/micheleg/dash-to-dock/releases/tag/extensions.gnome.org-v73 This extension looks like it needs code changes for GNOME Shell 43, which is currently in experimental and should be going to unstable soon. After updating it for gnome-shell 43 compatibility, I'd recommend giving it a dependency on gnome-shell (<< 44~) so that it won't be co-installable with GNOME Shell 44 (including alphas/betas) during the Debian 13 cycle. smcv
Bug#1018194: gnome-shell-extension-dash-to-panel: needs update for GNOME Shell 43
Package: gnome-shell-extension-dash-to-panel Version: 50-1 Severity: important Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-43 Forwarded: https://github.com/home-sweet-gnome/dash-to-panel/commits/4cb72cbc588db74ca302fadcae638d102bd984a6 This extension looks like it needs code changes for GNOME Shell 43. After updating it for gnome-shell 43 compatibility, I'd recommend giving it a dependency on gnome-shell (<< 44~) so that it won't be co-installable with GNOME Shell 44 (including alphas/betas) during the Debian 13 cycle. smcv
Bug#1018193: ITP: the-foundation -- Opinionated C11 library for low-level functionality
Package: wnpp Severity: wishlist Owner: Michel Alexandre Salim X-Debbugs-Cc: debian-de...@lists.debian.org, mic...@michel-slm.name * Package name: the-foundation Version : 1.4.0 Upstream Author : Jaakko Keränen * URL : https://codeberg.org/skyjake/the_Foundation * License : BSD Programming Lang: C Description : Opinionated C11 library for low-level functionality An object-oriented C library whose API is designed for a particular coding style, taking cues from C++ STL and Qt. This is a dependency for Lagrange, a desktop Gemini client: https://codeberg.org/skyjake/lagrange I already maintain both in Fedora, and would be nice to be able to use them as native packages when on Debian.
Bug#964884: gplaycli does not seem to be suitable for stable releases
severity 964884 serious thanks This now appears to no longer be developed upstream, and also is currently broken. It probably should not be released with bookworm.
Bug#1017720: nfs-common: No such file or directory
I was able to identify another workaround today which may help you to identify the issue. The workaround is to touch the directory where the troubled files live on the file server. I believe this tells us that updating the modify time attribute is used by the cache. It should be noted that access time updates are disabled on the file server. I also wanted to restate that we use rsync to push out these application updates and also use rsync to sync data files. Our rsync options preserve timestamps, so it is possible that the new files have an older timestamp than "now". It is not the case that the new files have an older timestamp than the prior version that is stuck in the cache. The rsync process that I describe has not changed and has been in use for many years. > -Original Message- > From: Jason Breitman > Sent: Thursday, August 25, 2022 11:54 AM > To: Ben Hutchings ; 1017...@bugs.debian.org > Subject: RE: Bug#1017720: nfs-common: No such file or directory > > I have the same issue after adding actimeo=30 to /etc/fstab, rebooting and > testing. > I also confirmed that those settings applied via /proc/mounts which shows > the below snippet for each mountpoint. > nfs4 > rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,acregmin=30,a > cregmax=30,acdirmax=30,hard,noresvport,proto=tcp,timeo=600,retrans=2,s > ec=krb5,clientaddr=X.X.X.X,lookupcache=pos,local_lock=none,addr=Y.Y.Y.Y 0 > 0 > > > -Original Message- > > From: Jason Breitman > > Sent: Tuesday, August 23, 2022 2:42 PM > > To: Ben Hutchings ; 1017...@bugs.debian.org > > Subject: RE: Bug#1017720: nfs-common: No such file or directory > > > > What additional information can I provide for us to move forward with this > > process? > > > > To summarize and include further details, rsync is used to sync applications > to > > a file server which behaves like a repository. > > We do preserve timestamps from the build server and also use --delete. > We > > do not run the applications from the file server. All servers use NTP. > > > > The application has a sub-directory that contain files with version numbers. > > These are libraries. > > When a new build is complete, a developer pushes their updates via rsync > to > > the file server / repository. > > > > I believe that the dentry cache thinks the "old" files exist and generates a > No > > such file or directory error showing question marks for that files > > attributes. > > Dropping the dentry cache via echo 2 > /proc/sys/vm/drop_caches > resolves > > the issue. > > > > This behavior is not observed in Debian 10.8 with that distributions > associated > > kernel and packages. > > > > > -Original Message- > > > From: Jason Breitman > > > Sent: Friday, August 19, 2022 9:52 PM > > > To: Ben Hutchings ; 1017...@bugs.debian.org > > > Subject: RE: Bug#1017720: nfs-common: No such file or directory > > > > > > > -Original Message- > > > > From: Ben Hutchings > > > > Sent: Friday, August 19, 2022 7:27 PM > > > > To: Jason Breitman ; > > > > 1017...@bugs.debian.org > > > > Subject: Re: Bug#1017720: nfs-common: No such file or directory > > > > > > > > Control: tag -1 moreinfo > > > > > > > > On Fri, 2022-08-19 at 13:16 +, Jason Breitman wrote: > > > > > Package: nfs-common > > > > > Version: 1:1.3.4-6 > > > > > Severity: important > > > > > > > > > > Kernel: 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) > x86_64 > > > > > GNU/Linux > > > > > > > > > > -- Description > > > > > After updating and or creating new files on our file server via > > > > > rsync, we see many files report the error message below from NFSv4 > > > > > clients since upgrading from Debian 10.8 to Debian 11.4. > > > > > Clearing the dentry cache resolves the issue right away. > > > > > I am not sure that nfs-common is the package to blame, but listed > > > > > it based on the bug submission recommendations. > > > > > > > > The NFS implementation is mostly in the kernel, so probably this issue > > > > belongs there. But the kernel team is responsible for both packages. > > > > > > > > [...] > > > > > -- Error message > > > > > ls: cannot access 'filename': No such file or directory > > > > > -? ? ???? filename > > > > [...] > > > > > > > > So we know the file's there but can't stat it. I think this means the > > > > client has cached the handle of the old file of that name, which has > > > > been deleted. > > > > > > > > - Are client and server clocks closely synchronised? If not, that > > > > needs to be fixed. > > > > > > > The clocks are synchronized using NTP. > > > > > > > - Are clients likely to read this directory while rsync is running, or > > > > shortly before? If so, it may help to reduce the attribute caching > > > > timeout on the client. See the "Directory entry caching" section in > > > > the nfs(5) manual page. > > > > > > > Clients are not likely to read this directory while rsync is running for > > > the
Bug#1018191: libapreq2: CVE-2022-22728: multipart form parse memory corruption
Source: libapreq2 Version: 2.13-7 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for libapreq2. CVE-2022-22728[0]: | A flaw in Apache libapreq2 versions 2.16 and earlier could cause a | buffer overflow while processing multipart form uploads. A remote | attacker could send a request causing a process crash which could lead | to a denial of service attack. It has been asked in [2] if there is an isolated patch or upstream issue as reference as there are not much details on the CVE. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-22728 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22728 [1] https://www.openwall.com/lists/oss-security/2022/08/25/3 [2] https://www.openwall.com/lists/oss-security/2022/08/26/4 Regards, Salvatore
Bug#1018190: nmu: deal.ii_9.4.0-1+b1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Now that pmix has been reverted, deal.ii can be rebuilt against opencascade 7.6.3, to make it installable again. Please add an additional Dep-Wait on pmix > 4.2.0+really.4.1.2-1~ as pmix for mips64el is not yet built (it seems to run out of memory on this arch) nmu deal.ii_9.4.0-1+b1 . ANY . unstable . -m "rebuild against opencascade 7.6.3" -- Thanks tobi
Bug#472477: #472477 ssh-add -D does not remove SSH key from gnome-keyring-daemon memory (workaround)
Hi, So, my workaround for this annoying issue was to use gpg-agent instead. As a nice side effect, you can then use a gpg key to authenticate. The tricky part for me was to make sure gnome woudn't try to set SSH_AUTH_SOCK to gnome keyring anyway. In case others want to go this route, here is what I've done: - make sure your gpg-agent can handle ssh agent role by including `enable-ssh-support` in ~/.gnupg/gpg-agent.conf (you can also set ttls there while you're at it if you want, e,g, `default-cache-ttl-ssh 1200`, `max_cache_ttl-ssh 7200`) - disable ssh component of gnome-keyring in systemd user units: ``` systemctl --user mask gcr-ssh-agent.socket --now systemctl --user mask gcr-ssh-agent.service --now ``` - disable ssh component of gnome-keyring also in XDG autostart by adding the Hidden property: ``` cp /etc/xdg/autostart/gnome-keyring-ssh.desktop ~/.config/autostart/ echo "Hidden=true" >> ~/.config/autostart/gnome-keyring-ssh.desktop ``` Then restart the session. Be aware that when you use ssh-add for the first time when having the gpg-agent socket in SSH_AUTH_SOCK, you'll be first prompted by ssh-add, then by gpg-agent. Set a passphrase in gpg-agent when prompted, otherwise it will be stored in clear in your private keys. Usual gpg-agent stuff applies, it will lock whenever you lock the session, you get a timeout, etc. Cheers, -- nodens
Bug#1017993: reverse dependencies
Control: tags -1 + moreinfo Hi Samuel, there are reverse dependencies that needs to be taken care of: Checking reverse dependencies... # Broken Depends: bully: bully forensics-all: forensics-all mdk3: mdk3 mdk4: mdk4 wifite: wifite # Broken Build-Depends: wifite: aircrack-ng In case they matter, this needs to be addressed first. Please remove the moreinfo tag once that is done. Thorsten
Bug#1017984: reverse dependencies
control: tags -1 + moreinfo Hi Bastian, according to dak there are reverse dependencies that needs to be taken care of: Checking reverse dependencies... # Broken Build-Depends: cadabra: libpcre++-dev httest: libpcre++-dev restinio: libpcre++-dev sord: libpcre++-dev In case they matter, this needs to be addressed first. Please remove the moreinfo tag once that is done. Thorsten
Bug#1018098: foxtrotgps 1.2.2+bzr331-1~deb11u1 flagged for acceptance
package release.debian.org tags 1018098 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: foxtrotgps Version: 1.2.2+bzr331-1~deb11u1 Explanation: fix crash by ensuring that threads are always unreferenced
Bug#1017999: krb5 1.18.3-6+deb11u2 flagged for acceptance
package release.debian.org tags 1017999 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: krb5 Version: 1.18.3-6+deb11u2 Explanation: use SHA256 as Pkinit CMS Digest
Bug#1017841: pcre2 10.36-2+deb11u1 flagged for acceptance
package release.debian.org tags 1017841 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: pcre2 Version: 10.36-2+deb11u1 Explanation: fix out-of-bounds read issues [CVE-2022-1586 CVE-2022-1587]
Bug#1017987: debian-security-support 11+2022.08.23 flagged for acceptance
package release.debian.org tags 1017987 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: debian-security-support Version: 11+2022.08.23 Explanation: update support status of various packages
Bug#1018082: golang-github-pkg-term 1.1.0-4~deb11u1 flagged for acceptance
package release.debian.org tags 1018082 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: golang-github-pkg-term Version: 1.1.0-4~deb11u1 Explanation: fix building on newer Linux kernels
Bug#1018045: publicsuffix 20220811.1734-0+deb11u1 flagged for acceptance
package release.debian.org tags 1018045 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: publicsuffix Version: 20220811.1734-0+deb11u1 Explanation: update included data
Bug#1017502: http-parser 2.9.4-4+deb11u1 flagged for acceptance
package release.debian.org tags 1017502 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: http-parser Version: 2.9.4-4+deb11u1 Explanation: unset F_CHUNKED on new Transfer-Encoding, fixing possible HTTP request smuggling issue [CVE-2020-8287]
Bug#1016803: [Pkg-utopia-maintainers] Bug#1016803: Bug#1016803: Generates unusable resolv.conf
On Thu, Aug 25, 2022 at 10:50:01PM +0200, Michael Biebl wrote: > Output of "nmcli" as well, please. wlp61s0: connected to sirena "Intel 8265 / 8275" wifi (iwlwifi), 48:F1:7F:C0:88:CF, hw, mtu 1500 ip4 default inet4 192.168.8.100/16 route4 192.168.0.0/16 route4 0.0.0.0/0 inet6 fe80::788e:1990:4d51:7a42/64 route6 fe80::/64 docker0: connected to docker0 "docker0" bridge, 02:42:62:06:90:BF, sw, mtu 1500 inet4 172.17.0.1/16 route4 172.17.0.0/16 inet6 fe80::ddf5:758f:ebbd:71dc/64 route6 fe80::/64 lxcbr0: connected to lxcbr0 "lxcbr0" bridge, 00:16:3E:00:00:00, sw, mtu 1500 inet4 10.0.3.1/24 route4 10.0.3.0/24 route4 169.254.0.0/16 p2p-dev-wlp61s0: disconnected "p2p-dev-wlp61s0" wifi-p2p, hw enp0s31f6: unavailable "Intel Ethernet" ethernet (e1000e), E8:6A:64:AB:B8:78, hw, mtu 1500 lo: unmanaged "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 Use "nmcli device show" to get complete information about known devices and "nmcli connection show" to get an overview on active connection profiles. Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details. > Is /etc/resolv.conf a real file or a symlink pointing somewhere? Normal file. -rw-r--r-- 1 root root 72 Aug 26 19:15 /etc/resolv.conf > Please also post the content of /run/NetworkManager/no-stub-resolv.conf # Generated by NetworkManager nameserver 192.168.8.1 (which is good for this network). signature.asc Description: PGP signature
Bug#1018118: transition: mutter & gnome-shell 43
On Thu, 25 Aug 2022 at 15:17:05 -0400, Jeremy Bicha wrote: > This transition is blocked on someone going through all the packaged > gnome-shell extensions to report bugs for them to either declare > compatibility with GNOME Shell 43 (if compatible, the metadata file > and debian/control need to be updated) or to let them be removed from > Testing. I've started this process, I'll continue over the weekend. Usertag: https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-gnome-maintainers%40lists.alioth.debian.org=gnome-shell-43 smcv
Bug#1018188: gnome-shell-extension-hard-disk-led: needs update for GNOME Shell 43
Package: gnome-shell-extension-hard-disk-led Version: 30-2 Severity: important Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-43 This extension's dependencies say it is compatible with GNOME Shell 43~beta-1 (currently available in experimental), but its metadata disagrees and does not list 43 as a compatible version. Even if its JavaScript code is compatible with Shell 43, debian/control will need updating for the final release of Shell 43. (I'd recommend using gnome-shell (<< 44~) rather than gnome-shell (<< 44) as the upper bound for the version range after it has been confirmed to be compatible with 44, so that alphas and betas of 44 are treated as 44.) If not updated, it will have to be removed from testing for the GNOME Shell 43 transition (see https://bugs.debian.org/1018118 for details). This bug will be raised to serious severity when the transition is ready to go ahead. smcv
Bug#1018189: gnome-shell-extension-arc-menu: needs update for GNOME Shell 43
Package: gnome-shell-extension-arc-menu Version: 49+forkv29-1 Severity: important Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-43 This extension's apt/dpkg dependencies say it is compatible with GNOME Shell 43~beta-1 (currently available in experimental), but its metadata disagrees and does not list 43 as a compatible version. Depending what has changed, it might need either a simple metadata update or code changes. After updating it for gnome-shell 43 compatibility, I'd recommend giving it a dependency on gnome-shell (<< 44~) so that it won't be co-installable with GNOME Shell 44 (including alphas/betas) during the Debian 13 cycle. smcv
Bug#1018187: gnome-shell-extension-caffeine: needs update for GNOME Shell 43
Package: gnome-shell-extension-caffeine Severity: important Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-43 This extension has not been checked for compatibility with GNOME Shell 43. Depending how compatible it is, it will either need an update to its metadata.json and debian/control to declare compatibility with the new version, or code changes to adapt it to the new Shell version. If not updated, it will have to be removed from testing for the GNOME Shell 43 transition (see https://bugs.debian.org/1018118 for details). This bug will be raised to serious severity when the transition is ready to go ahead. smcv
Bug#1018186: gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 43
Package: gnome-shell-extension-bluetooth-quick-connect Severity: serious Tags: bookworm sid upstream Forwarded: https://github.com/bjarosze/gnome-bluetooth-quick-connect/issues/65 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-43 This extension is known not to be compatible with the new design of the system menu in GNOME Shell 43, and will need to be updated. A fix is not trivial, so it will probably need to be temporarily removed from testing for the GNOME Shell 43 transition (see https://bugs.debian.org/1018118). smcv
Bug#1017777: bullseye-pu: package glibc/2.31-13+deb11u4
Control: tags -1 + confirmed d-i On Sat, 2022-08-20 at 10:35 +0200, Aurelien Jarno wrote: > There are multiple fixes in this upload, mostly coming from the > upstream > stable branch: > - One security issue with CVE entry > - Multiple overflow fixes to wide string functions > - Failure to enforce libio vtable protection > - A performance issue with string functions affecting Skylake-X CPUs > (up > to 40% slower) > - A new NEW.Debian.gz entry for libc6-dev explaining users how to > switch > from to the TI-RPC implementation following the Sun RPC > implementation > removal in glibc 2.31 > - Make grantpt usable after multi-threaded fork to prevent Ansible > deadlocks. > Please go ahead, thanks. Regards, Adam
Bug#1016837: bullseye-pu: package avahi/0.8-5+deb11u1
Control: tags -1 + confirmed On Mon, 2022-08-08 at 11:35 +0200, Michael Biebl wrote: > avahi (0.8-5+deb11u1) bullseye; urgency=medium > > [ Simon McVittie ] > * Add patch to fix display of URLs containing '&' in avahi- > discover. > Otherwise, a TXT entry containing a URL with '&' will cause an > error. > > [ Michael Biebl ] > * Do not disable timeout cleanup on watch cleanup. > This was causing timeouts to never be removed from the linked > list that > tracks them, resulting in both memory and CPU usage to grow > larger over > time. Thanks to Gustavo Noronha Silva. (Closes: #993051) > * Fix NULL pointer crashes when trying to resolve badly-formatted > hostnames. > Fixes a local DoS in avahi-daemon that can be triggered by trying > to > resolve badly-formatted hostnames on the /run/avahi-daemon/socket > interface. (CVE-2021-3502, Closes: #986018) > Please go ahead. Regards, Adam
Bug#1016786: bullseye-pu: package systemd/247.3-7+deb11u1
Control: tags -1 + confirmed d-i On Sun, 2022-08-07 at 15:31 +0200, Michael Biebl wrote: > I'd like to make a stable upload for systemd fixing two issues in > systemd-detect-virt > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013342 > systemd - Please backport support for Hyper-V on arm64 to stable > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016157 > systemd-detect-virt fails to detect Openstack on arm64 > > All changes are cherry-picks from upstream Git and are already in > unstable/testing. > > > While at it, I also pulled a patch to fix build failures when systemd > is > built against newer kernel headers (>= 5.14). > Please go ahead; thanks. Regards, Adam
Bug#1018185: buster-pu: package ruby-riddle/2.3.1-2~deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian Ruby Team
* d/start_mysqld_and_run.sh: allow LOAD DATA LOCAL INFILE
* Add patch to make mysql2 client allow local_infile
(Closes: #988028)
Test-only FTBFS fix (the local_infile changes are not in files that
end up in the binary package).
Additionally, there are some harmless Standards-Version/salsa-ci.yml
packaging changes.
diff -Nru ruby-riddle-2.3.1/debian/changelog ruby-riddle-2.3.1/debian/changelog
--- ruby-riddle-2.3.1/debian/changelog 2019-01-18 14:26:07.0 +0200
+++ ruby-riddle-2.3.1/debian/changelog 2022-08-26 20:27:26.0 +0300
@@ -1,3 +1,24 @@
+ruby-riddle (2.3.1-2~deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for buster. (Closes: #988028)
+
+ -- Adrian Bunk Fri, 26 Aug 2022 20:27:26 +0300
+
+ruby-riddle (2.3.1-2) unstable; urgency=medium
+
+ * Team upload.
+
+ [ Utkarsh Gupta ]
+ * Add salsa-ci.yml
+
+ [ Lucas Kanashiro ]
+ * d/start_mysqld_and_run.sh: allow LOAD DATA LOCAL INFILE
+ * Add patch to make mysql2 client allow local_infile
+ * Declare compliance with Debian Policy 4.4.1
+
+ -- Lucas Kanashiro Thu, 05 Dec 2019 09:04:01
-0300
+
ruby-riddle (2.3.1-1) unstable; urgency=medium
* Team upload.
diff -Nru ruby-riddle-2.3.1/debian/control ruby-riddle-2.3.1/debian/control
--- ruby-riddle-2.3.1/debian/control2019-01-18 14:26:07.0 +0200
+++ ruby-riddle-2.3.1/debian/control2019-12-05 14:04:01.0 +0200
@@ -12,7 +12,7 @@
ruby-mysql2,
ruby-rspec,
sphinxsearch
-Standards-Version: 4.3.0
+Standards-Version: 4.4.1
Vcs-Git: https://salsa.debian.org/ruby-team/ruby-riddle.git
Vcs-Browser: https://salsa.debian.org/ruby-team/ruby-riddle
Homepage: https://pat.github.io/riddle/
diff -Nru
ruby-riddle-2.3.1/debian/patches/0002-Make-mysql2-client-allow-local_infile.patch
ruby-riddle-2.3.1/debian/patches/0002-Make-mysql2-client-allow-local_infile.patch
---
ruby-riddle-2.3.1/debian/patches/0002-Make-mysql2-client-allow-local_infile.patch
1970-01-01 02:00:00.0 +0200
+++
ruby-riddle-2.3.1/debian/patches/0002-Make-mysql2-client-allow-local_infile.patch
2019-12-05 14:04:01.0 +0200
@@ -0,0 +1,23 @@
+From: Lucas Kanashiro
+Date: Thu, 5 Dec 2019 08:56:44 -0300
+Subject: Make mysql2 client allow local_infile
+
+This is needed to use the LOAD DATA LOCAL INFILE fixture command.
+---
+ spec/support/mri_client.rb | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/spec/support/mri_client.rb b/spec/support/mri_client.rb
+index 5906d81..4bd8580 100644
+--- a/spec/support/mri_client.rb
b/spec/support/mri_client.rb
+@@ -5,7 +5,8 @@ class MRIClient
+ @client = Mysql2::Client.new(
+ :host => host,
+ :username => username,
+- :password => password
++ :password => password,
++ :local_infile => true
+ )
+ end
+
diff -Nru ruby-riddle-2.3.1/debian/patches/series
ruby-riddle-2.3.1/debian/patches/series
--- ruby-riddle-2.3.1/debian/patches/series 2019-01-18 14:26:07.0
+0200
+++ ruby-riddle-2.3.1/debian/patches/series 2019-12-05 14:04:01.0
+0200
@@ -1 +1,2 @@
0001-Remove-bundler-and-relative-paths-from-specs.patch
+0002-Make-mysql2-client-allow-local_infile.patch
diff -Nru ruby-riddle-2.3.1/debian/salsa-ci.yml
ruby-riddle-2.3.1/debian/salsa-ci.yml
--- ruby-riddle-2.3.1/debian/salsa-ci.yml 1970-01-01 02:00:00.0
+0200
+++ ruby-riddle-2.3.1/debian/salsa-ci.yml 2019-12-05 14:04:01.0
+0200
@@ -0,0 +1,4 @@
+---
+include:
+ - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+ -
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
diff -Nru ruby-riddle-2.3.1/debian/start_mysqld_and_run.sh
ruby-riddle-2.3.1/debian/start_mysqld_and_run.sh
--- ruby-riddle-2.3.1/debian/start_mysqld_and_run.sh2019-01-18
14:26:07.0 +0200
+++ ruby-riddle-2.3.1/debian/start_mysqld_and_run.sh2019-12-05
14:04:01.0 +0200
@@ -18,7 +18,7 @@
DO_MYSQL_DATABASE=/${DO_MYSQL_DBNAME}
mysql_install_db --no-defaults --datadir=${MYTEMP_DIR} --force
--skip-name-resolve --user=${DO_MYSQL_USER}
-/usr/sbin/mysqld --no-defaults --user=${DO_MYSQL_USER}
--socket=${MYSQL_UNIX_PORT} --datadir=${MYTEMP_DIR} --skip-networking
--skip-grant &
+/usr/sbin/mysqld --no-defaults --user=${DO_MYSQL_USER}
--socket=${MYSQL_UNIX_PORT} --datadir=${MYTEMP_DIR} --skip-networking
--local-infile=1 --skip-grant &
echo -n pinging mysqld.
attempts=0
while ! /usr/bin/mysqladmin --socket=${MYSQL_UNIX_PORT} ping ; do
Bug#1015791: additional info
Hi all, This bug is still present in debian testing. But here is a new information: After a fresh reboot and log in in xfce there is low hdd (a fast ssd!) activity for few seconds. If one starts libreoffice-writer or firefox-esr or thunderbird then there is a long hdd activity for more then 20seconds at first time! After that the load time and hdd activity is much shorter! Example1: 1. reboot 2. start thunderbird (takes more then 20seconds) and quit thunderbird 3. start libreoffice (starts in less then 2 seconds) Example2: 1. reboot 2. start libreoffice (takes more then 20seconds) and quit libreoffice 3. start libreoffice (starts in less then 2 seconds) Example3: 1. reboot 2. start firefox (takes more then 20seconds) and quit firefox 3. start libreoffice (starts in less then 2 seconds) It looks like, that firefox/thunderbird are loading stuff that is also needed by libreoffice. This is very strange. There seems to be a huge amount of memory usage!(20 seconds read with a fast ssd) best regards Reiner
Bug#998390: ruby-activeldap 5.2.2-2+deb10u1 flagged for acceptance
package release.debian.org tags 998390 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: ruby-activeldap Version: 5.2.2-2+deb10u1 Explanation: add missing dependency on ruby-builder
Bug#1018152: pglogical 2.2.1-4+deb10u1 flagged for acceptance
package release.debian.org tags 1018152 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: pglogical Version: 2.2.1-4+deb10u1 Explanation: fix build failure
Bug#1018151: ruby-http-parser.rb 0.6.0-4+deb10u1 flagged for acceptance
package release.debian.org tags 1018151 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: ruby-http-parser.rb Version: 0.6.0-4+deb10u1 Explanation: fix build failure when using http-parser containing the fix for CVE-2019-15605
Bug#1018108: ruby-hiredis 0.6.1-2+deb10u1 flagged for acceptance
package release.debian.org tags 1018108 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: ruby-hiredis Version: 0.6.1-2+deb10u1 Explanation: skip some unreliable tests in order to fix build failure
Bug#1018107: golang-github-docker-go-connections 0.3.0-3+deb10u1 flagged for acceptance
package release.debian.org tags 1018107 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: golang-github-docker-go-connections Version: 0.3.0-3+deb10u1 Explanation: skip tests that use expired certificates
Bug#1018101: kannel 1.4.5-2+deb10u1 flagged for acceptance
package release.debian.org tags 1018101 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: kannel Version: 1.4.5-2+deb10u1 Explanation: fix build failure by disabling generation of Postscript documentation
Bug#1018097: foxtrotgps 1.2.1-1+deb10u1 flagged for acceptance
package release.debian.org tags 1018097 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: foxtrotgps Version: 1.2.1-1+deb10u1 Explanation: fix build failure with newer imagemagick versions
Bug#1018086: golang-github-pkg-term 0.0~git20181116.27bbf2e-1+deb10u1 flagged for acceptance
package release.debian.org tags 1018086 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: golang-github-pkg-term Version: 0.0~git20181116.27bbf2e-1+deb10u1 Explanation: fix building on newer 4.19 kernels
Bug#1018096: ftgl 2.4.0-2.1~deb10u1 flagged for acceptance
package release.debian.org tags 1018096 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: ftgl Version: 2.4.0-2.1~deb10u1 Explanation: don't try to convert PNG to EPS for latex, as our imagemagick has EPS disabled for security reasons
Bug#1018048: publicsuffix 20220811.1734-0+deb10u1 flagged for acceptance
package release.debian.org tags 1018048 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: publicsuffix Version: 20220811.1734-0+deb10u1 Explanation: updae included data
Bug#1018095: node-require-from-string 2.0.1-1+deb10u1 flagged for acceptance
package release.debian.org tags 1018095 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: node-require-from-string Version: 2.0.1-1+deb10u1 Explanation: fix test for nodejs >= 10.16
Bug#1018080: python-keystoneauth1 3.10.0-2+deb10u1 flagged for acceptance
package release.debian.org tags 1018080 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: python-keystoneauth1 Version: 3.10.0-2+deb10u1 Explanation: update tests to fix build failure
Bug#1018092: sctk 2.4.10-20151007-1312Z+dfsg2-3.1~deb10u1 flagged for acceptance
package release.debian.org tags 1018092 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: sctk Version: 2.4.10-20151007-1312Z+dfsg2-3.1~deb10u1 Explanation: use "pdftoppm" instead of "convert" to convert PDF to JPEG as the latter fails with the changed security policy of ImageMagick
Bug#1017998: krb5 1.17-3+deb10u4 flagged for acceptance
package release.debian.org tags 1017998 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: krb5 Version: 1.17-3+deb10u4 Explanation: use SHA256 as Pkinit CMS Digest
Bug#1018184: buster-pu: package python-udatetime/0.0.16-1+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: Ilias Tsitsimpis * Backport upstream patch to fix failing test (Closes: #953539) * Patch udatetime to properly link against libm library. Thanks to Aurelien Jarno for the patch (Closes: #954305) The first change is a FTBFS fix. The second change is correct, it might or might not make a difference when upgrading to bullseye. python-udatetime was not previously rebuilt to drop the C extension for Python 3.6 (not in buster), only the Python 3.7 extension is built now. diff -Nru python-udatetime-0.0.16/debian/changelog python-udatetime-0.0.16/debian/changelog --- python-udatetime-0.0.16/debian/changelog2018-02-15 21:10:47.0 +0200 +++ python-udatetime-0.0.16/debian/changelog2022-08-26 20:11:06.0 +0300 @@ -1,3 +1,12 @@ +python-udatetime (0.0.16-1+deb10u1) buster; urgency=medium + + * Non-maintainer upload. + * Backport upstream patch to fix failing test (Closes: #953539) + * Patch udatetime to properly link against libm library. +Thanks to Aurelien Jarno for the patch (Closes: #954305) + + -- Adrian Bunk Fri, 26 Aug 2022 20:11:06 +0300 + python-udatetime (0.0.16-1) unstable; urgency=low [ Ondřej Nový ] diff -Nru python-udatetime-0.0.16/debian/patches/fix-test.patch python-udatetime-0.0.16/debian/patches/fix-test.patch --- python-udatetime-0.0.16/debian/patches/fix-test.patch 1970-01-01 02:00:00.0 +0200 +++ python-udatetime-0.0.16/debian/patches/fix-test.patch 2020-10-17 07:31:51.0 +0300 @@ -0,0 +1,23 @@ +From: Simon Pirschel +Date: Wed, 14 Mar 2018 11:42:36 +0100 +Subject: test with calculated offset based on diff between utc and local time + +--- + test/test_udatetime.py | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/test/test_udatetime.py b/test/test_udatetime.py +index e9a00b7..3fbde87 100644 +--- a/test/test_udatetime.py b/test/test_udatetime.py +@@ -75,7 +75,9 @@ class Test(unittest.TestCase): + self.assertEqual(udt.second, dt.second) + self.assertEqual(udt.microsecond, dt.microsecond) + +-self.assertEqual(udt.utcoffset(), timedelta(0)) ++offset = datetime.fromtimestamp(t) - datetime.utcfromtimestamp(t) ++ ++self.assertEqual(udt.utcoffset(), offset) + self.assertEqual(udt.dst(), NO_DST) + + for t in range(0, DAY, HOUR): diff -Nru python-udatetime-0.0.16/debian/patches/Link-against-libm.patch python-udatetime-0.0.16/debian/patches/Link-against-libm.patch --- python-udatetime-0.0.16/debian/patches/Link-against-libm.patch 1970-01-01 02:00:00.0 +0200 +++ python-udatetime-0.0.16/debian/patches/Link-against-libm.patch 2020-10-17 07:31:51.0 +0300 @@ -0,0 +1,22 @@ +From: Ilias Tsitsimpis +Date: Fri, 1 May 2020 20:29:16 +0300 +Subject: Link against libm + +Bug: https://github.com/freach/udatetime/issues/30 +Bug-Debian: https://bugs.debian.org/954305 +--- + setup.py | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/setup.py b/setup.py +index 2770298..498f40c 100644 +--- a/setup.py b/setup.py +@@ -36,6 +36,7 @@ if __pypy__ is None: + Extension( + 'udatetime.rfc3339', + ['./src/rfc3339.c'], ++libraries=['m'], + define_macros=macros, + extra_compile_args=['-Ofast', '-std=c99'] + ) diff -Nru python-udatetime-0.0.16/debian/patches/series python-udatetime-0.0.16/debian/patches/series --- python-udatetime-0.0.16/debian/patches/series 1970-01-01 02:00:00.0 +0200 +++ python-udatetime-0.0.16/debian/patches/series 2022-08-26 20:10:30.0 +0300 @@ -0,0 +1,2 @@ +fix-test.patch +Link-against-libm.patch
Bug#1017393: debian-security-support 10+2022.08.23 flagged for acceptance
package release.debian.org tags 1017393 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: debian-security-support Version: 10+2022.08.23 Explanation: update security status of various packages
Bug#1018183: Installation successfully at AMD Desktop PC
Package: installation-reports Boot method: Network PXE Boot Image version: PXE Boot with daily: > https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/initrd.gz > https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/linux Date: 2022-08-26 Machine: Self-made Desktop PC Processor: AMD A10-5700 APU with Radeon(tm) HD Graphics Memory: 4GB Partitions: > DateisystemTyp 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf > udev devtmpfs 18956320 18956320% /dev > tmpfs tmpfs 383796 9363828601% /run > /dev/sda1 ext4 113809604 10207144 97775084 10% / > tmpfs tmpfs 191897211396 19075761% /dev/shm > tmpfs tmpfs 5120 12 51081% /run/lock > tmpfs tmpfs 383792 1083836841% /run/user/1000 Output of lspci -knn: > 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h > (Models 10h-1fh) Processor Root Complex [1022:1410] > Subsystem: ASUSTeK Computer Inc. Family 15h (Models 10h-1fh) Processor > Root Complex [1043:8526] > 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. > [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] > Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526] > Kernel driver in use: radeon > Kernel modules: radeon, amdgpu > 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity > HDMI Audio Controller [1002:9902] > Subsystem: ASUSTeK Computer Inc. Trinity HDMI Audio Controller > [1043:8526] > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB > XHCI Controller [1022:7812] (rev 03) > Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8527] > Kernel driver in use: xhci_hcd > Kernel modules: xhci_pci > 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB > XHCI Controller [1022:7812] (rev 03) > Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8527] > Kernel driver in use: xhci_hcd > Kernel modules: xhci_pci > 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA > Controller [AHCI mode] [1022:7801] (rev 40) > Subsystem: ASUSTeK Computer Inc. FCH SATA Controller [AHCI mode] > [1043:8527] > Kernel driver in use: ahci > Kernel modules: ahci > 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB > OHCI Controller [1022:7807] (rev 11) > Subsystem: ASUSTeK Computer Inc. FCH USB OHCI Controller [1043:8527] > Kernel driver in use: ohci-pci > Kernel modules: ohci_pci > 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB > EHCI Controller [1022:7808] (rev 11) > Subsystem: ASUSTeK Computer Inc. FCH USB EHCI Controller [1043:8527] > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB > OHCI Controller [1022:7807] (rev 11) > Subsystem: ASUSTeK Computer Inc. FCH USB OHCI Controller [1043:8527] > Kernel driver in use: ohci-pci > Kernel modules: ohci_pci > 00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB > EHCI Controller [1022:7808] (rev 11) > Subsystem: ASUSTeK Computer Inc. FCH USB EHCI Controller [1043:8527] > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller > [1022:780b] (rev 14) > Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:8527] > Kernel driver in use: piix4_smbus > Kernel modules: i2c_piix4, sp5100_tco > 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia > Controller [1022:780d] (rev 01) > Subsystem: ASUSTeK Computer Inc. F2A85-M Series [1043:8444] > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge > [1022:780e] (rev 11) > Subsystem: ASUSTeK Computer Inc. FCH LPC Bridge [1043:8527] > 00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge > [1022:780f] (rev 40) > 00:15.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Hudson PCI to > PCI bridge (PCIE port 0) [1022:43a0] > Subsystem: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge > (PCIE port 0) [1022:] > Kernel driver in use: pcieport > 00:15.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Hudson PCI to > PCI bridge (PCIE port 1) [1022:43a1] > Subsystem: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge > (PCIE port 1) [1022:] > Kernel driver in use: pcieport > 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h >
Bug#1018182: buster-pu: package libhttp-cookiejar-perl/0.008-1+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian Perl Group
* Add patch to fix FTBFS after 09 Jun 2021. (Closes: #991649)
diff -Nru libhttp-cookiejar-perl-0.008/debian/changelog
libhttp-cookiejar-perl-0.008/debian/changelog
--- libhttp-cookiejar-perl-0.008/debian/changelog 2015-11-08
19:01:33.0 +0200
+++ libhttp-cookiejar-perl-0.008/debian/changelog 2022-08-26
19:58:25.0 +0300
@@ -1,3 +1,10 @@
+libhttp-cookiejar-perl (0.008-1+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to fix FTBFS after 09 Jun 2021. (Closes: #991649)
+
+ -- Adrian Bunk Fri, 26 Aug 2022 19:58:25 +0300
+
libhttp-cookiejar-perl (0.008-1) unstable; urgency=medium
* Import upstream version 0.008.
diff -Nru
libhttp-cookiejar-perl-0.008/debian/patches/postpone-test-expiry.patch
libhttp-cookiejar-perl-0.008/debian/patches/postpone-test-expiry.patch
--- libhttp-cookiejar-perl-0.008/debian/patches/postpone-test-expiry.patch
1970-01-01 02:00:00.0 +0200
+++ libhttp-cookiejar-perl-0.008/debian/patches/postpone-test-expiry.patch
2022-08-26 19:58:12.0 +0300
@@ -0,0 +1,21 @@
+Description: postpone expiry dates in test suites to 2041
+Author: David Golden
+Origin: upstream,
https://github.com/dagolden/HTTP-CookieJar/commit/7a3b9b163526784bf18a69172df736d190c15940
+Bug: https://github.com/dagolden/HTTP-CookieJar/issues/11
+Bug-Debian: https://bugs.debian.org/991649
+Applied-Upstream: 0.011
+Reviewed-by: Étienne Mollier
+Last-Update: 2021-07-29
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- libhttp-cookiejar-perl.orig/t/examples.t
libhttp-cookiejar-perl/t/examples.t
+@@ -38,7 +38,7 @@
+
+ subtest "expiration" => sub {
+ $jar->clear;
+-$jar->add( $req, "lang=en-US; Expires=Wed, 09 Jun 2021 10:18:14 GMT" );
++$jar->add( $req, "lang=en-US; Expires=Sun, 09 Jun 2041 10:18:14 GMT" );
+ is( $jar->cookie_header($req), "lang=en-US" );
+ $jar->add( $req, "lang=; Expires=Sun, 06 Nov 1994 08:49:37 GMT" );
+ is( $jar->cookie_header($req), "" );
diff -Nru libhttp-cookiejar-perl-0.008/debian/patches/series
libhttp-cookiejar-perl-0.008/debian/patches/series
--- libhttp-cookiejar-perl-0.008/debian/patches/series 1970-01-01
02:00:00.0 +0200
+++ libhttp-cookiejar-perl-0.008/debian/patches/series 2021-07-29
20:12:41.0 +0300
@@ -0,0 +1 @@
+postpone-test-expiry.patch
Bug#1018181: ITP: just - Save and run project-specific commands
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name: just Version : 1.4.0 Upstream Author : Casey Rodarmor * URL : https://github.com/casey/just * License : CC0-1.0 Programming Lang: Rust Description : Save and run project-specific commands just is a command runner with a configuration file similar to Makefile but can be written in arbitrary languages. It has improvements over make e.g. no .PHONY, is cross-platform, has detailed error output, and comes with command line completions for popular shells. This package provides an alternative to make in daily development, with modern and friendly experience. Also, its author RFP'd it, #971726. The package is a Rust crate, thus fits in the Rust team packaging process. -- Regards, Blair Noctis OpenPGP_0xC21D9AD423A39727.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#981669: gettext: incorrect build dependencies for nojava architectures
El 17/8/22 a las 20:10, Santiago Vila escribió: However, before doing so, I wonder if it would be possible for you to try the current gettext in unstable with nojava profile, just to be sure that it will work when I upload the version using --list-missing. Nevermind. After fixing debian/not-installed, gettext now builds on hppa: https://buildd.debian.org/status/package.php?p=gettext Thanks a lot.
Bug#1018173: libreoffice: Please upload final releases
Hi, Am 26.08.22 um 17:41 schrieb Rene Engelhard: Am 26.08.22 um 15:55 schrieb Itaï BEN YAACOV: 1. I understand that unstable is the place to stage pre-release software. But this does not mean it must only contain such. Moreover, given Debian's slow release cycle some users (such as myself) use it for daily work, rather than for testing new software. Come on, it's not as if I uploaded alphas or betas to unstable. Just RCs. Addendum to that: That's not what unstable and testing are for. It's sole purpose is to prepare for the next release. That people use it like you do is also true, but that is not it's purpose. There is backports, too. (Though I have been uploading those rcs there anyway, though less often, I skipped 7.4.0 rcX for example. And the backports' rules demand of the packages being in testing first. So that would even mean uploading the final. wait for it to migrate. do the thing.) If the final release is indeed equal to some rc#, then, as pointless as this may seem to you, could you please just bump up the version number and upload again as final? And do a fuill build cycle on all architectures just for this? No. Would you want to upload a release just to replace it with the next rc when it gets out? Even more unneeded build cycles. And not only that. All the tests: see e.g. https://qa.debian.org/excuses.php?package=libreoffice right now: Issues preventing migration: missing build on arm64 missing build on s390x arch:arm64 not built yet, autopkgtest delayed there arch:s390x not built yet, autopkgtest delayed there autopkgtest for apparmor/3.0.7-1: amd64: Pass, armel: Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress autopkgtest for grammalecte/2.1.2+ds2-1: amd64: Pass, armel: Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress autopkgtest for libnumbertext/1.0.10-1: amd64: Pass, armel: Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress autopkgtest for libreoffice/1:7.4.1~rc1-2: amd64: Pass, armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression) autopkgtest for lloconv/6.1.0-3: amd64: Pass, armel: Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress autopkgtest for natbraille/2.0rc3-13: amd64: No test results, armel: Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress autopkgtest for openlp/2.9.5-1: amd64: No test results, armel: Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress autopkgtest for paperwork/2.1.1-1: amd64: Pass, armel: Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress autopkgtest for parlatype-libreoffice-extension/3.1.1-1: amd64: Pass, armel: Test in progress (will not be considered a regression), armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress and if you look at the build times, amd64 even takes 10 hours+, some slower archs even 1 day or more. Just doing this for something which will be overwritten anyway is a waste. Would you want *only* upload of releases? Thus e.g. not getting all the bugfixes in 7.4.1? That would be the consequence. I'll then tell you on any bug "try the version in experimental, since that one is developed". Do you want that instead? Note that at some point in time I'll stick to releases, let alone for the freeze. I see that you didn't want that but that would be the consequence, let alone not to do a "useless", time-wasting upload. I actually even planned to just stick to releases when I uploaded a release. (and already updated debian/watch for it) Regards, Rene
Bug#1018180: wcc: autopkgtest fails with glibc 2.36
Package: wcc
Version: 0.0.2+dfsg-4.1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Hi Philippe,
In Ubuntu, the wcc autopkgtest is failing because Ubuntu has moved to glibc
2.36, which results in some changes to the output of ldd. The wldd wrapper
does not handle all of these changes correctly.
Please find attached a patch that adjusts wldd to handle this new ldd
output.
--
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
diff -Nru wcc-0.0.2+dfsg/debian/patches/glibc-2.36-compat.patch
wcc-0.0.2+dfsg/debian/patches/glibc-2.36-compat.patch
--- wcc-0.0.2+dfsg/debian/patches/glibc-2.36-compat.patch 1969-12-31
16:00:00.0 -0800
+++ wcc-0.0.2+dfsg/debian/patches/glibc-2.36-compat.patch 2022-08-26
09:18:41.0 -0700
@@ -0,0 +1,21 @@
+Description: fix wldd to be compatible with glibc 2.36's ldd output
+ wldd assumes everything in the output of ldd with a => pointer is a
+ shared library, but glibc 2.36 now also outputs the information about
+ the linker in the same format. Filter it out.
+Author: Steve Langasek
+Last-Update: 2022-08-26
+Forwarded: no
+
+Index: wcc-0.0.2+dfsg/src/tools/wldd
+===
+--- wcc-0.0.2+dfsg.orig/src/tools/wldd
wcc-0.0.2+dfsg/src/tools/wldd
+@@ -19,7 +19,7 @@
+ }
+
+ getlibs (){
+- ldd $1|grep "=> /"|awk '{print $1}'|sed s#"\..*"##|sed
s#"^lib"#"-l"#|tr "\n" " "
++ ldd $1|awk '/ld-linux/ { next; } /=> \// {print $1}'|sed s#"\..*"##|sed
s#"^lib"#"-l"#|tr "\n" " "
+ echo ""
+ }
+
diff -Nru wcc-0.0.2+dfsg/debian/patches/series
wcc-0.0.2+dfsg/debian/patches/series
--- wcc-0.0.2+dfsg/debian/patches/series2020-03-21 10:02:12.0
-0700
+++ wcc-0.0.2+dfsg/debian/patches/series2022-08-26 09:15:40.0
-0700
@@ -10,3 +10,4 @@
spelling_in_src.patch
latex_build.patch
glibc.patch
+glibc-2.36-compat.patch
Bug#1018179: buster-pu: package librose-db-object-perl/1:0.815-1+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Debian Perl Group
* Add upstream fix for test failure after 6/6/2020. (Closes: #962482)
diff -Nru librose-db-object-perl-0.815/debian/changelog
librose-db-object-perl-0.815/debian/changelog
--- librose-db-object-perl-0.815/debian/changelog 2015-10-28
00:32:38.0 +0200
+++ librose-db-object-perl-0.815/debian/changelog 2022-08-26
19:06:16.0 +0300
@@ -1,3 +1,10 @@
+librose-db-object-perl (1:0.815-1+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for test failure after 6/6/2020. (Closes: #962482)
+
+ -- Adrian Bunk Fri, 26 Aug 2022 19:06:16 +0300
+
librose-db-object-perl (1:0.815-1) unstable; urgency=medium
[ Salvatore Bonaccorso ]
diff -Nru
librose-db-object-perl-0.815/debian/patches/0001-Fixed-tests-that-were-failing-due-to-future-dates-th.patch
librose-db-object-perl-0.815/debian/patches/0001-Fixed-tests-that-were-failing-due-to-future-dates-th.patch
---
librose-db-object-perl-0.815/debian/patches/0001-Fixed-tests-that-were-failing-due-to-future-dates-th.patch
1970-01-01 02:00:00.0 +0200
+++
librose-db-object-perl-0.815/debian/patches/0001-Fixed-tests-that-were-failing-due-to-future-dates-th.patch
2022-08-26 19:06:16.0 +0300
@@ -0,0 +1,237 @@
+From f349d74149d1c493d8fd6e385526cea8a02ba127 Mon Sep 17 00:00:00 2001
+From: John Siracusa
+Date: Mon, 8 Jun 2020 12:47:32 -0400
+Subject: Fixed tests that were failing due to "future" dates that are now in
+ the past (RT 132782)
+
+--- a/t/db-object-manager.t
b/t/db-object-manager.t
+@@ -635,7 +635,7 @@ SKIP: foreach my $db_type (qw(pg)) #pg_with_schema
+ save_col => [ 1, 5, 123 ],
+ nums => [ 4, 5, 6 ],
+ fk1=> 1,
+-last_modified => { le => '6/6/2020' }, # XXX: breaks in 2020!
++last_modified => { le => '6/6/2099' }, # XXX: breaks in 2099!
+ date_created => '5/10/2002 10:34:56 am'
+ ],
+ clauses => [ "LOWER(status) LIKE 'w%'" ],
+@@ -688,7 +688,7 @@ SKIP: foreach my $db_type (qw(pg)) #pg_with_schema
+ save_col => [ 1, 5, 123 ],
+ nums => [ 4, 5, 6 ],
+ fk1=> 1,
+-last_modified => { le => '6/6/2020' }, # XXX: breaks in 2020!
++last_modified => { le => '6/6/2099' }, # XXX: breaks in 2099!
+ date_created => '5/10/2002 10:34:56 am'
+ ],
+ clauses => [ "LOWER(status) LIKE 'w%'" ],
+@@ -734,7 +734,7 @@ SKIP: foreach my $db_type (qw(pg)) #pg_with_schema
+ save_col => [ 1, 5, 123 ],
+ nums => [ 4, 5, 6 ],
+ fk1=> 1,
+-last_modified => { le => '6/6/2020' }, # XXX: breaks in 2020!
++last_modified => { le => '6/6/2099' }, # XXX: breaks in 2099!
+ date_created => '5/10/2002 10:34:56 am'
+ ],
+ clauses => [ "LOWER(status) LIKE 'w%'" ],
+@@ -795,7 +795,7 @@ SKIP: foreach my $db_type (qw(pg)) #pg_with_schema
+ save_col => [ 1, 5, 123 ],
+ nums => [ 4, 5, 6 ],
+ fk1=> 1,
+-last_modified => { le => '6/6/2020' }, # XXX: breaks in 2020!
++last_modified => { le => '6/6/2099' }, # XXX: breaks in 2099!
+ date_created => '5/10/2002 10:34:56 am'
+ ],
+ clauses => [ "LOWER(status) LIKE 'w%'" ],
+@@ -1342,7 +1342,7 @@ SKIP: foreach my $db_type (qw(pg)) #pg_with_schema
+ save_col => [ 1, 5 ],
+ nums => [ 1, 2, 3 ],
+ fk1=> 2,
+-last_modified => { le => '6/6/2020' }, # XXX: breaks in 2020!
++last_modified => { le => '6/6/2099' }, # XXX: breaks in 2099!
+ date_created => '3/30/2004 12:34:56 pm'
+ ],
+ clauses => [ "LOWER(status) LIKE 'ac%'" ],
+@@ -3780,7 +3780,7 @@ SKIP: foreach my $db_type ('mysql')
+ save_col => [ 1, 5, 123 ],
+ nums => [ 4, 5, 6 ],
+ fk1=> 1,
+-last_modified => { le => '6/6/2020' }, # XXX: breaks in 2020!
++last_modified => { le => '6/6/2099' }, # XXX: breaks in 2099!
+ date_created => '5/10/2002 10:34:56 am'
+ ],
+ clauses => [ "LOWER(status) LIKE 'w%'" ],
+@@ -3841,7 +3841,7 @@ SKIP: foreach my $db_type ('mysql')
+ save_col => [ 1, 5, 123 ],
+ nums => [ 4, 5, 6 ],
+ fk1=> 1,
+-last_modified => { le => '6/6/2020' }, # XXX: breaks in 2020!
++last_modified => { le => '6/6/2099' }, # XXX: breaks in 2099!
+ date_created => '5/10/2002 10:34:56 am'
+ ],
+ hints => { ignore_index => 'rose_db_object_test_idx' },
+@@ -4371,7 +4371,7 @@ SKIP: foreach my $db_type ('mysql')
+ save_col => [ 1, 5 ],
+ nums => [ 1, 2, 3 ],
+ fk1=> 2,
+-last_modified => { le => '6/6/2020' }, # XXX: breaks in 2020!
++last_modified => { le => '6/6/2099' }, # XXX: breaks in 2099!
+
Bug#1018178: buster-pu: package gnucash/1:3.4-1+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Dmitry Smirnov
* Add upstream fix for test-gnc-timezone with recent tzdata.
(Closes: #978208).
diff -Nru gnucash-3.4/debian/changelog gnucash-3.4/debian/changelog
--- gnucash-3.4/debian/changelog2019-01-02 23:51:54.0 +0200
+++ gnucash-3.4/debian/changelog2022-08-26 01:24:12.0 +0300
@@ -1,3 +1,11 @@
+gnucash (1:3.4-1+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for test-gnc-timezone with recent tzdata.
+(Closes: #978208).
+
+ -- Adrian Bunk Fri, 26 Aug 2022 01:24:12 +0300
+
gnucash (1:3.4-1) unstable; urgency=medium
* New upstream release (Closes: #918059).
diff -Nru
gnucash-3.4/debian/patches/0001-Fix-test-gnc-timezone-failure-caused-by-latest-zonei.patch
gnucash-3.4/debian/patches/0001-Fix-test-gnc-timezone-failure-caused-by-latest-zonei.patch
---
gnucash-3.4/debian/patches/0001-Fix-test-gnc-timezone-failure-caused-by-latest-zonei.patch
1970-01-01 02:00:00.0 +0200
+++
gnucash-3.4/debian/patches/0001-Fix-test-gnc-timezone-failure-caused-by-latest-zonei.patch
2022-08-26 01:16:52.0 +0300
@@ -0,0 +1,31 @@
+From ae66da96324e6b8545456c980caf81c93d368402 Mon Sep 17 00:00:00 2001
+From: John Ralls
+Date: Sat, 26 Dec 2020 13:45:28 -0800
+Subject: Fix test-gnc-timezone failure caused by latest zoneinfo release.
+
+See the comment for details.
+---
+ libgnucash/engine/test/gtest-gnc-timezone.cpp | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/libgnucash/engine/test/gtest-gnc-timezone.cpp
b/libgnucash/engine/test/gtest-gnc-timezone.cpp
+index a676ff1a9..25d9d9d45 100644
+--- a/libgnucash/engine/test/gtest-gnc-timezone.cpp
b/libgnucash/engine/test/gtest-gnc-timezone.cpp
+@@ -134,6 +134,13 @@ TEST(gnc_timezone_constructors, test_IANA_Belize_tz)
+ EXPECT_EQ(tz->dst_zone_abbrev(), "CDT");
+ EXPECT_EQ(tz->dst_offset().total_seconds(), 3600);
+ }
++/* An IANA update on 22 Dec 2020 added missing DST transitions
++ * for Belize between 1943 and 1967. Ignore those years until
++ * the oldest supported OS version release is later than that
++ * because distros updating of zoneinfo is spotty.
++ */
++else if (year >= 1943 && year <= 1967)
++continue;
+ else
+ {
+ EXPECT_EQ(tz->std_zone_abbrev(), "CST");
+--
+2.20.1
+
diff -Nru gnucash-3.4/debian/patches/series gnucash-3.4/debian/patches/series
--- gnucash-3.4/debian/patches/series 2019-01-02 23:51:54.0 +0200
+++ gnucash-3.4/debian/patches/series 2022-08-26 01:24:11.0 +0300
@@ -1,2 +1,3 @@
test--fix-test-transaction.scm.patch
test--skip-test-stress-options.patch
+0001-Fix-test-gnc-timezone-failure-caused-by-latest-zonei.patch
Bug#1018173: libreoffice: Please upload final releases
tag 1018173 + wontfix thanks Hi, Am 26.08.22 um 15:55 schrieb Itaï BEN YAACOV: 1. I understand that unstable is the place to stage pre-release software. But this does not mean it must only contain such. Moreover, given Debian's slow release cycle some users (such as myself) use it for daily work, rather than for testing new software. Come on, it's not as if I uploaded alphas or betas to unstable. Just RCs. 2. I am **guessing** that you might answer that the last release candidate in each cycle is the final release -- but this is merely a guess (is it, actually?) It is. It is a exact copy of the last release. This is also why 7.4.0 internally is 7.4.0.3 (aka 7.4.0 rc3). The point is that this is developer logic, but from the point of view of a user, just being told "this is the final 7.something.whatever release" is so much easier and does not involve any guesswork. (Also, you know it when it is uploaded, rather than when the first candidate for the next release is uploaded). Untrue. https://wiki.documentfoundation.org/ReleasePlan/7.4 (as was also for 7.3) is a clear plan on whet will happen when. If the final release is indeed equal to some rc#, then, as pointless as this may seem to you, could you please just bump up the version number and upload again as final? And do a fuill build cycle on all architectures just for this? No. Would you want to upload a release just to replace it with the next rc when it gets out? Even more unneeded build cycles. Here it would be directly one week. (And here 7.4.1 rc1 was there when 7.4.0 rc3 was in the poppler transition.) Would you want *only* upload of releases? Thus e.g. not getting all the bugfixes in 7.4.1? That would be the consequence. I'll then tell you on any bug "try the version in experimental, since that one is developed". Do you want that instead? Note that at some point in time I'll stick to releases, let alone for the freeze. Regards, Rene
Bug#1018177: tabbed: Mod- fails on keysyms mapped to multiple keycodes
Package: suckless-tools
Version: 46-2
Severity: minor
On my machine with a reconfigured keypad to give the same behavior of
the digit row of the keyboard (independently of the NumLock status),
Mod-[0..9] works with the keys of the digit row, but not with those
of the keypad.
According to xev:
[1 on the digit row]
state 0x0, keycode 10 (keysym 0x31, 1), same_screen YES,
[Ctrl-1 on the digit row]
state 0x4, keycode 10 (keysym 0x31, 1), same_screen YES,
[1 on the keypad]
state 0x0, keycode 87 (keysym 0x31, 1), same_screen YES,
XKeysymToKeycode returns keycode: 10
[Ctrl-1 on the keypad]
state 0x4, keycode 87 (keysym 0x31, 1), same_screen YES,
XKeysymToKeycode returns keycode: 10
The bug sems to be the following:
for(i = 0; i < LENGTH(keys); i++) {
if((code = XKeysymToKeycode(dpy, keys[i].keysym))) {
for(j = 0; j < LENGTH(modifiers); j++) {
XGrabKey(dpy, code, keys[i].mod
| modifiers[j], w,
True, GrabModeAsync,
GrabModeAsync);
}
}
}
So this will grab only what XKeysymToKeycode gives, thus for 1, it
is keycode 10, which corresponds to the key 1 on the digit row, and
keycode 87 (on the keypad) is ignored.
Instead of the above code, shouldn't it enumerate keycodes and look
for all those that match a wanted keysym?
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages suckless-tools depends on:
ii libc6 2.34-5
ii libcap2-bin 1:2.44-1
ii libfontconfig1 2.13.1-4.4
ii libpam0g1.5.2-2
ii libx11-62:1.8.1-2
ii libxft2 2.3.4-1
ii libxinerama12:1.1.4-3
ii libxrandr2 2:1.5.2-2+b1
ii libxss1 1:1.2.3-1
suckless-tools recommends no packages.
Versions of packages suckless-tools suggests:
pn dwm
pn stterm
pn surf
-- no debconf information
--
Vincent Lefèvre - Web:
Bug#993014: [Pkg-samba-maint] Bug#993014: Processed: Re: cifs-utils non-parallel FTBFS
Hai,
> -Oorspronkelijk bericht-
> Van: Pkg-samba-maint lists.debian.net> Namens Michael Tokarev
> Verzonden: vrijdag 26 augustus 2022 16:05
> Aan: be...@samba.org; 993...@bugs.debian.org
> Onderwerp: [Pkg-samba-maint] Bug#993014: Processed: Re: cifs-utils non-
> parallel FTBFS
>
> 25.08.2022 11:49, L. van Belle wrote:
> ...
> > The shown fix, commit aeaa786aceb0ea781ded2c151fb68f6b34880ad4
> > is the patch I added.
> > and cifs-utils 7.0 also fails to build without that patch with parallel=1
>
> It's difficult to follow.
Ok, i'll try to explain better here..
>
> Commit aeaa786aceb0ea781ded2c151fb68f6b34880ad4 is wrong by its own
> because it adds dependency on install-sbinPROGRAMS while it should add
> dependency on install-root_sbinPROGRAMS (which creates the necessary
> directory). So that commit just adds unnecessary complexity but does not fix
> the problem in any way.
>
> Was it you who added this commit to upstream samba?
No, that wasn't me..
But I did get that your where saying "the fix is works but is wrongly fixed..
And I leave that to you, your way more qualified for that then me.
>
> I didn't notice this difference either, before closing this bug. I thought I
> verified the single-job build locally but it turned out my -j1 has been
> overridden by later -j8 on the same command line. Oh well.
>
> Technically this dependency is wrong too because the symlink itself does not
> need the installation of the binary, it needs only the directory. The right
> fix
> would be to create directory in its own target and refer in both install- and
> hook- to that target but I don't know if it is solvable in terms of regular
> make.
> GNU make has order-only targets which fits here nicely. But install-
> root_sbinPROGRAMS target as whole is generated by automake, together
> with the mkdir call. So the only way to "fix" this is to add similar mkdir
> into the
> hook rule, as Sanvilla did in his patch.
>
> Now, you wrote above that cifs-utils 7.0 "also fails to build without this
> patch", but this patch is included in 7.0. This is even more confusing.. :)
The source i have from ftp.samba.org on cifs didn't have that patch in.
The patch in this bug report, did work for me, so I pulled it from this
bugreport.
>
> Anyway. I'm changing install-sbinPROGRAMS to install-root_sbinPROGRAMS
> there to do what aeaa786aceb0ea781ded2c151fb68f6b34880ad4 has meant
> to do. This will fix this issue "the way upstream wanted it to be fixed", so
> to
> say.
>
> Oh well.
>
> /mjt
Thank you for your attention Michael. {tumpsUp}
I can share my sources and build if you want.
Greetz,
Louis
Bug#1017919: firefox: All firefox tabs crash at startup and cannot be restored
This bug is still unfixed as of version 104.0-1. I am able to use the flatpak version without any problems, so I have to assume that this is a dependency version issue. On Mon, 22 Aug 2022 09:44:14 -0500 Pierce Griffiths wrote: > Package: firefox > Version: 103.0.2-2 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: pierceagriffi...@gmail.com > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** > After upgrading firefox from 103.0-1 to 103.0.2-2, all tabs say that they have > crashed as soon as the browser is opened, and I am unable to restore them. The > following is the backtrace from gdb: > [Detaching after fork from child process 34472] > [New Thread 0x7fffebaaf640 (LWP 34473)] > [New Thread 0x7fffeba6e640 (LWP 34474)] > [New Thread 0x7fffeba2d640 (LWP 34475)] > [New Thread 0x7fffeb9ec640 (LWP 34476)] > [New Thread 0x7fffeb9ab640 (LWP 34477)] > [New Thread 0x7fffeb96a640 (LWP 34478)] > [New Thread 0x7fffeb5ff640 (LWP 34479)] > [Thread 0x7fffeb5ff640 (LWP 34479) exited] > [New Thread 0x76fff640 (LWP 34480)] > [Detaching after fork from child process 34481] > [New Thread 0x7fffeb929640 (LWP 34482)] > [New Thread 0x7fffeb57c640 (LWP 34492)] > [New Thread 0x7fffe55ff640 (LWP 34493)] > [New Thread 0x7fffe5400640 (LWP 34494)] > [New Thread 0x7fffe5201640 (LWP 34495)] > [New Thread 0x7fffe5002640 (LWP 34496)] > [New Thread 0x7fffe4e03640 (LWP 34497)] > [New Thread 0x7fffe4c04640 (LWP 34498)] > [New Thread 0x7fffe4a05640 (LWP 34499)] > [New Thread 0x7fffe4806640 (LWP 34500)] > [New Thread 0x7fffeb52f640 (LWP 34501)] > [New Thread 0x7fffeb0ff640 (LWP 34502)] > [New Thread 0x7fffeb0be640 (LWP 34503)] > [New Thread 0x7fffe41ff640 (LWP 34504)] > [New Thread 0x7fffeb07d640 (LWP 34505)] > [New Thread 0x7fffe93ff640 (LWP 34507)] > [New Thread 0x7fffe3aff640 (LWP 34509)] > [New Thread 0x7fffe32fe640 (LWP 34511)] > [New Thread 0x7fffdfdff640 (LWP 34513)] > [Thread 0x7fffdfdff640 (LWP 34513) exited] > [New Thread 0x7fffdfdff640 (LWP 34514)] > [New Thread 0x7fffdf1ff640 (LWP 34515)] > [Thread 0x7fffdfdff640 (LWP 34514) exited] > [New Thread 0x7fffdfdff640 (LWP 34517)] > [New Thread 0x7fffde9fe640 (LWP 34518)] > [Thread 0x7fffdf1ff640 (LWP 34515) exited] > [Thread 0x7fffde9fe640 (LWP 34518) exited] > [Thread 0x7fffdfdff640 (LWP 34517) exited] > [New Thread 0x7fffdfdff640 (LWP 34519)]
Bug#1018175: ITP: funing -- a simple face recognition GUI
I am interested On Fri, Aug 26, 2022 at 4:18 PM Bo YU wrote: > Package: wnpp > Severity: wishlist > Owner: Bo YU > X-Debbugs-Cc: debian-de...@lists.debian.org > > * Package name: funing > Version : 0.2.54 > Upstream Author : larryw3i > * URL : https://pypi.org/project/funing/ > * License : MIT > Programming Lang: Python > Description : a simple face recognition GUI > > > a simple face recognition GUI. > > I will maintain it under Python team. > > -- > Regards, > -- > Bo YU > >
Bug#1018176: xorg process leaks file descriptors until it's no longer functional
Package: xorg Version: 1:7.7+23 Severity: normal Dear Maintainer, since around 2022-08-10 I've noticed that over time the number of open file descriptors of the xorg process increases to near the process's limit of 1024. This happens about once per day, where the computer is on around 9h and put to standby once or twice per day. About every minute, there are two further open files. Looking at /proc/pid_of_xorg/fd/ I see that file descriptors like these are added all the time: lrwx-- 1 root root 64 26. Aug 15:05 1000 -> /memfd:xshmfence (deleted) lrwx-- 1 root root 64 26. Aug 15:05 1001 -> /memfd:xshmfence (deleted) lrwx-- 1 root root 64 26. Aug 15:05 1002 -> /memfd:xshmfence (deleted) lrwx-- 1 root root 64 26. Aug 15:05 1003 -> /memfd:xshmfence (deleted) lrwx-- 1 root root 64 26. Aug 15:05 1004 -> /memfd:xshmfence (deleted) lrwx-- 1 root root 64 26. Aug 15:05 1005 -> /memfd:xshmfence (deleted) lrwx-- 1 root root 64 26. Aug 15:05 1006 -> /memfd:xshmfence (deleted) lrwx-- 1 root root 64 26. Aug 15:05 1007 -> /memfd:xshmfence (deleted) At some point, not exactly when the limit of 1024 is reached (or at least I couldn't measure it) the desktop stops mapping new windows. The currently visible application still works and accepts mouse clicks and keyboard events, but switching to a different running application, or new application, has no effect. Environment: - Debian sid - KDE Plasma - Chromium - some electron apps - Terminals - eclipse An external display is hooked up to an HDMI port of an attached USB3 dock. Is there any way to find out what's causing this? Maybe it's not even a bug in xorg, but an application leaking connections? How could I find out which this might be? Thanks a lot! -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- :00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) :01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA107GLM [RTX A2000 Mobile] [10de:25b8] (rev a1) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 4 -rw-r--r-- 1 root root 226 Nov 21 2021 90-xpra-virtual.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 5.18.0-4-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.18.16-1 (2022-08-10) Xorg X server log files on system: -- -rw-r--r-- 1 root root 86265 Aug 26 15:06 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 25044.463] (--) Log file renamed from "/var/log/Xorg.pid-47577.log" to "/var/ log/Xorg.0.log" [ 25044.463] X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 [ 25044.463] Current Operating System: Linux nb-4 5.18.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.16-1 (2022-08-10) x86_64 [ 25044.463] Kernel command line: BOOT_IMAGE=/vmlinuz-5.18.0-4-amd64 root=/ dev/mapper/main-root ro quiet mem_sleep_default=deep [ 25044.463] xorg-server 2:21.1.4-1 (https://www.debian.org/support) [ 25044.463] Current version of pixman: 0.40.0 [ 25044.463]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 25044.463] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 25044.463] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 26 15:06:00 2022 [ 25044.463] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 25044.463] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 25044.463] (==) No Layout section. Using the first Screen section. [ 25044.463] (==) No screen section available. Using defaults. [ 25044.463] (**) |-->Screen "Default Screen Section" (0) [ 25044.463] (**) | |-->Monitor "" [ 25044.464] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 25044.464] (==) Automatically adding devices [ 25044.464] (==) Automatically enabling devices [ 25044.464] (==) Automatically adding GPU devices [ 25044.464] (==) Automatically binding GPU devices [ 25044.464] (==) Max clients allowed: 256, resource mask: 0x1f [ 25044.464] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 25044.464]Entry deleted from font path. [ 25044.464] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1,
Bug#1018175: ITP: funing -- a simple face recognition GUI
Package: wnpp Severity: wishlist Owner: Bo YU X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: funing Version : 0.2.54 Upstream Author : larryw3i * URL : https://pypi.org/project/funing/ * License : MIT Programming Lang: Python Description : a simple face recognition GUI a simple face recognition GUI. I will maintain it under Python team. -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#993014: Processed: Re: cifs-utils non-parallel FTBFS
25.08.2022 11:49, L. van Belle wrote: ... The shown fix, commit aeaa786aceb0ea781ded2c151fb68f6b34880ad4 is the patch I added. and cifs-utils 7.0 also fails to build without that patch with parallel=1 It's difficult to follow. Commit aeaa786aceb0ea781ded2c151fb68f6b34880ad4 is wrong by its own because it adds dependency on install-sbinPROGRAMS while it should add dependency on install-root_sbinPROGRAMS (which creates the necessary directory). So that commit just adds unnecessary complexity but does not fix the problem in any way. Was it you who added this commit to upstream samba? I didn't notice this difference either, before closing this bug. I thought I verified the single-job build locally but it turned out my -j1 has been overridden by later -j8 on the same command line. Oh well. Technically this dependency is wrong too because the symlink itself does not need the installation of the binary, it needs only the directory. The right fix would be to create directory in its own target and refer in both install- and hook- to that target but I don't know if it is solvable in terms of regular make. GNU make has order-only targets which fits here nicely. But install-root_sbinPROGRAMS target as whole is generated by automake, together with the mkdir call. So the only way to "fix" this is to add similar mkdir into the hook rule, as Sanvilla did in his patch. Now, you wrote above that cifs-utils 7.0 "also fails to build without this patch", but this patch is included in 7.0. This is even more confusing.. :) Anyway. I'm changing install-sbinPROGRAMS to install-root_sbinPROGRAMS there to do what aeaa786aceb0ea781ded2c151fb68f6b34880ad4 has meant to do. This will fix this issue "the way upstream wanted it to be fixed", so to say. Oh well. /mjt
Bug#1018174: AttributeError exception with --reverse
Package: urlscan Version: 0.9.5-1 Severity: normal Control: forwarded -1 https://github.com/firecat53/urlscan/issues/99 Control: fixed -1 0.9.6-1 The `--reverse` option doesn't seem to work at all in bullseye. It crashes with an exception, regardless of what I throw at it. ie. this works: anarcat@curie:~$ urlscan --no-browser < /dev/null > /dev/null anarcat@curie:~$ This doesn't: anarcat@curie:~$ urlscan --no-browser --reverse < /dev/null > /dev/null Traceback (most recent call last): File "/usr/bin/urlscan", line 216, in main() File "/usr/bin/urlscan", line 206, in main out = urlchoose.URLChooser(urlscan.msgurls(msg), File "/usr/lib/python3/dist-packages/urlscan/urlchoose.py", line 226, in __init__ self._reverse() File "/usr/lib/python3/dist-packages/urlscan/urlchoose.py", line 465, in _reverse fpo = self.top.body.focus_position AttributeError: 'Padding' object has no attribute 'body' anarcat@curie:~[1]$ I can also reproduce with an actual input of course: anarcat@curie:~$ urlscan --no-browser --reverse < /etc/motd > /dev/null Traceback (most recent call last): File "/usr/bin/urlscan", line 216, in main() File "/usr/bin/urlscan", line 206, in main out = urlchoose.URLChooser(urlscan.msgurls(msg), File "/usr/lib/python3/dist-packages/urlscan/urlchoose.py", line 226, in __init__ self._reverse() File "/usr/lib/python3/dist-packages/urlscan/urlchoose.py", line 465, in _reverse fpo = self.top.body.focus_position AttributeError: 'Padding' object has no attribute 'body' anarcat@curie:~[1]$ It looks like the --reverse option is just completely broken. It looks like this was reported upstream as: https://github.com/firecat53/urlscan/issues/99 ... and fixed in 0.9.6. a. -- System Information: Debian Release: 11.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages urlscan depends on: ii python33.9.2-3 ii python3-urwid 2.1.2-1 Versions of packages urlscan recommends: ii libcanberra-gtk3-module 0.30-7 Versions of packages urlscan suggests: ii chromium [www-browser] 104.0.5112.101-1~deb11u1 ii firefox-esr [www-browser] 91.13.0esr-1~deb11u1 ii lynx [www-browser] 2.9.0dev.6-3~deb11u1 ii mutt 2.0.5-4.1+deb11u1 ii neomutt20201127+dfsg.1-1.2 ii w3m [www-browser] 0.5.3+git20210102-6 -- debconf-show failed
Bug#1018173: libreoffice: Please upload final releases
Source: libreoffice Version: 1:7.4.0~rc3-1 Severity: wishlist Dear Maintainer, Since 7.3.1 (which is no longer installable) you have only uploaded release candidates to Debian/sid. Please consider uploading final releases as well, before moving on to candidates of the next release. 1. I understand that unstable is the place to stage pre-release software. But this does not mean it must only contain such. Moreover, given Debian's slow release cycle some users (such as myself) use it for daily work, rather than for testing new software. 2. I am **guessing** that you might answer that the last release candidate in each cycle is the final release -- but this is merely a guess (is it, actually?) The point is that this is developer logic, but from the point of view of a user, just being told "this is the final 7.something.whatever release" is so much easier and does not involve any guesswork. (Also, you know it when it is uploaded, rather than when the first candidate for the next release is uploaded). If the final release is indeed equal to some rc#, then, as pointless as this may seem to you, could you please just bump up the version number and upload again as final? Many thanks !! Cheers, Itaï -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (600, 'unstable') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1018085: hplip fails to setup wired printer HP P 1102w
The latest HPLIP has been installed. I have tried installing the proprietary plugin via original HP CD and also download. Both installs fail because the "cannot find port". I.e. it is looking for the WiFi port to connect to the printer. Incidentally, the printer WiFi install does work successfully on my laptop. The issue at hand is that the install fails for a wired connection. There should be no reason to require the plugin at all for a wired connection. -Original Message- From: Brian Potkin Sent: Aug 25, 2022 7:32 PM To: William Melgaard , <1018...@bugs.debian.org> Subject: Re: Bug#1018085: hplip fails to setup wired printer HP P 1102w On Thu 25 Aug 2022 at 08:41:20 -0500, William Melgaard wrote: > Package: hplip > Version: 3.21.2+dfsg1-2 > Severity: normal > X-Debbugs-Cc: piob...@mindspring.com Thank you for your report, William. > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > print driver failed after upgrade to bullseye TBH, this issue gives the impression of being a user support issue. > * What exactly did you do (or not do) that was effective (or > ineffective)? > Instlled latest hplip; deleted existing driver and installed printer > HP Laserjet Pro P1102w It hoped by "latest hplip" the version for Debian 11 was installed? > * What was the outcome of this action > The install insists on the installation of a proprietary plugin. > However, attempts to install that plugin from HP CD fails because the > workstation does not have a WiFi port HPLIP does offer the option of > USB vs WiFi connection. However, chosing USB appears ineffectual. The > setup still insists that the plugin is missing. Upstream offen advise the following technique: * Download the plugin for your HPLIP version from https://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/ * Install the plugin with 'sh DOWNLOADED_PLUGIN' > * What outcome did you expect instead? > Successful test print That should be possible with a correct setup. Please give lpstat -t lpinfo -v lpinfo -m | grep p1102w Regards, Brian.
Bug#1017083: [pkg-crosswire-devel] Bug#1017083: All sources are included, the bug report is invalid
On Fri, 26 Aug 2022 at 14:40, Bastian Germann wrote:
> Control: severity -1 serious
>
> Am 26.08.22 um 14:15 schrieb Teus Benschop:
> > Additionally the quill code was downloaded from the official quill
> releases in whatever form their official releases are.
> > "Webpack" does not come in here.
>
> The point is that the quill releases do not fit Debian's definition of
> source, so the bug IS valid at least for quill.
> Bastien pointed to the non-minifies quill files because they are readable
> ("full") source but not source that is defined
> by preferred form for modification.
>
> The right thing would be to create a libjs-quill package that builds the
> module from the source available at:
> https://github.com/quilljs/quill. Then depend on that package.
>
> Actually, this is a serious bug as filed by Bastien. If we as a team
> cannot afford the time to make this package abide
> by the DFSG, then it is justified that the autoremove automation kicks in.
>
Okay, the explanation you have given is clear, thanks for that.
We'll see what the team is able to do before the package is automatically
removed from the testing distribution.
It could happen that upstream generates the Quill source in Javascript
from, and includes that in the Bibledit upstream source. That's a possible
solution too.
Teus.
Bug#1018172: RM: evolution-rss -- RoM; unbuildable and uninstallable with evolution 3.45+
Package: ftp.debian.org X-Debbugs-Cc: evolution-...@packages.debian.org Affects: src:evolution-rss Please remove evolution-rss from Debian. evolution-data-server and evolution 3.45 have switched to libsoup3. evolution-rss uses libsoup2.4 directly in its code. It's not possible for a process to link against both libsoup2.4 and libsoup3. Therefore, evolution-rss fails to build and is uninstallable with evolution 3.45. evolution-rss has been archived upstream which means bug reports, bug fixes, and even translation updates are no longer being accepted. https://gitlab.gnome.org/GNOME/evolution-rss On behalf of the Debian GNOME team, Jeremy Bicha
Bug#1018171: evolution-rss: Incompatible with evolution 3.45+
Source: evolution-rss Version: 0.3.96-4 Severity: serious Tags: ftbfs bookworm sid evolution-data-server and evolution 3.45 have switched to libsoup3. evolution-rss uses libsoup2.4 directly in its code. It's not possible for process to link against both libsoup2.4 and libsoup3. Therefore, evolution-rss fails to build and is uninstallable with evolution 3.45. evolution-rss has been abandoned upstream. I will file for its removal from Debian. https://gitlab.gnome.org/Archive/evolution-rss Thank you, Jeremy Bicha
Bug#1018098: bullseye-pu: package foxtrotgps/1.2.2+bzr331-1~deb11u1
Control: tags -1 - moreinfo On Fri, Aug 26, 2022 at 08:36:36AM +0800, Paul Wise wrote: > On Thu, 2022-08-25 at 19:21 +0300, Adrian Bunk wrote: > > > Paul, please ACK/NAK whether you as maintainer consider this appropriate. > > Looks good to me, thanks. Thanks, uploaded. > bye, > pabs cu Adrian
Bug#1018170: neomutt: corrupted redraw when jumping to new email
Package: neomutt
Version: 20220429+dfsg1-1
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
the upstream commit e33ff7cab64e2be32a9282a31c418f069af1f023 introduced
a regression that corrupts the user interface under certain conditions:
diff --git a/gui/msgwin.c b/gui/msgwin.c
index 204c0dac2..34c5ece8f 100644
- --- a/gui/msgwin.c
+++ b/gui/msgwin.c
@@ -123,8 +123,9 @@ static int msgwin_repaint(struct MuttWindow *win)
mutt_curses_set_color_by_id(priv->cid);
mutt_window_move(win, 0, 0);
- - mutt_paddstr(win, win->state.cols, priv->text);
+ mutt_window_addstr(win, priv->text);
mutt_curses_set_color_by_id(MT_COLOR_NORMAL);
+ mutt_window_clrtoeol(win);
mutt_debug(LL_DEBUG5, "repaint done\n");
return 0;
I am not exactly sure what causes the regression, typically it only
occurs once when a mailbox is (re-)opened and TAB is used to jump to the
first unread mail, corrupting the index view (see attached screenshots).
However, I found that commit 80b28623d312693c845312bb7053b49d6e0253f0
from the main branch inadvertently fixes the issue again.
I attached said commit as patch.
Cheers
Timo
- -- Package-specific info:
NeoMutt 20220429
Copyright (C) 1996-2022 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.
System: Linux 5.18.0-4-amd64 (x86_64)
ncurses: ncurses 6.3.20220423 (compiled with 6.3.20220423)
libidn: 1.41 (compiled with 1.41)
GPGME: 1.17.1
GnuTLS: 3.7.7
libnotmuch: 5.6.0
storage: tokyocabinet
Configure options: --build=x86_64-linux-gnu --prefix=/usr
{--includedir=${prefix}/include} {--mandir=${prefix}/share/man}
{--infodir=${prefix}/share/info} --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
{--libdir=${prefix}/lib/x86_64-linux-gnu} --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --mandir=/usr/share/man
--libexecdir=/usr/libexec --with-mailpath=/var/mail --gpgme --lua --notmuch
--with-ui --gnutls --gss --idn --mixmaster --sasl --tokyocabinet --sqlite
--autocrypt
Compilation CFLAGS: -g -O2 -ffile-prefix-map=/build/neomutt-20220429+dfsg1=.
-fstack-protector-strong -Wformat -Werror=format-security -std=c99
-D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include
-I/usr/include/lua5.4 -DNCURSES_WIDECHAR -isystem /usr/include/mit-krb5
Default options:
+attach_headers_color +compose_to_sender +compress +cond_date +debug
+encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color
+initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop
+progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar
+skip_quoted +smtp +status_color +timeout +tls_sni +trash
Compile options:
+autocrypt +fcntl -flock -fmemopen +futimens +getaddrinfo +gnutls +gpgme +gss
+hcache -homespool +idn +inotify -locales_hack +lua +mixmaster +nls +notmuch
-openssl +pgp +regex +sasl +smime +sqlite +sun_attachment
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"
To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to:
- -- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages neomutt depends on:
ii libc6 2.34-6
ii libgnutls30 3.7.7-2
ii libgpg-error0 1.45-2
ii libgpgme111.17.1-4
ii libgssapi-krb5-2 1.20-1
ii libidn12 1.41-1
ii liblua5.4-0 5.4.4-3
ii libncursesw6 6.3+20220423-2
ii libnotmuch5 0.37-1
ii libsasl2-22.1.28+dfsg-7
ii libsqlite3-0 3.39.2-1
ii libtinfo6 6.3+20220423-2
ii libtokyocabinet9 1.4.48-15
ii sensible-utils0.0.17
Versions of packages neomutt recommends:
ii libsasl2-modules 2.1.28+dfsg-7
ii locales 2.34-6
ii mailcap 3.70+nmu1
Versions of packages neomutt suggests:
pn aspell | ispell
ii ca-certificates 20211016
ii gnupg 2.2.35-3
pn mixmaster
ii msmtp-mta [mail-transport-agent] 1.8.16-1+b1
ii openssl 3.0.5-2
pn urlview
Versions of packages neomutt is related to:
ii neomutt 20220429+dfsg1-1
- -- no debconf information
-BEGIN PGP SIGNATURE-
Bug#726456: Package rebuilt
When building a dompdf package I got an error for a missing autoload.php file from the package php-font-lib. That prompted me to rebuild the php-font-lib package and take the opportunity to update the version. It can be found here: https://salsa.debian.org/php-team/pear/php-font-lib It would be nice if someone reviewed and uploaded this version.
Bug#1018169: ITP:php-svg-lib -- SVG file parsing / rendering library
Package: wnpp * Package name: php-svg-lib Upstream Author : Fabien Ménager · * License : GPL-3+ Description : SVG sanitizer in PHP. The main purpose of this lib is to rasterize SVG to a surface which can be an image or a PDF for example, through a \Svg\Surface PHP interface. Regards Katharina --
Bug#1018168: nix-bin: fails to list packages?
Package: nix-bin Version: 2.3.7+dfsg1-1+b1 Severity: normal X-Debbugs-Cc: wim.bert...@khleuven.be Dear Maintainer, After install nix-bin and adding the regular user1 to nix-users, no packages can be found or installed, by user1 or root. following /usr/share/doc/nix-bin/README.Debian it is unclear anything should be done than adding user1 to nix-users if it helps: * libpam-systemd is installed * root5639 0.0 0.1 456204 15024 ?Ssl 14:31 0:00 nix-daemon --daemo * standard debian 11 installation (systemd) for example $ nix-env -qa gives nothing $ nix-env -i hello error: selector 'hello' matches no derivations hth, Wim -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-17-amd64 (SMP w/4 CPU threads) 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 Versions of packages nix-bin depends on: ii bzip2 1.0.8-4 ii curl7.74.0-1.3+deb11u2 ii libboost-context1.74.0 1.74.0-9 ii libbrotli1 1.0.9-2+b2 ii libbz2-1.0 1.0.8-4 ii libc6 2.31-13+deb11u2 ii libcurl3-gnutls 7.74.0-1.3+deb11u2 ii libdbd-sqlite3-perl 1.66-1+b1 ii libgc1 1:8.0.4-3 ii libgcc-s1 10.2.1-6 ii liblzma55.2.5-2.1~deb11u1 ii libreadline88.1-1 ii libseccomp2 2.5.1-1+deb11u1 ii libsodium23 1.0.18-1 ii libsqlite3-03.34.1-3 ii libssl1.1 1.1.1n-0+deb11u3 ii libstdc++6 10.2.1-6 ii libwww-curl-perl4.17-7+b1 ii lsb-base11.1.0 ii perl5.32.1-4+deb11u2 ii xz-utils5.2.5-2.1~deb11u1 Versions of packages nix-bin recommends: ii nix-setup-systemd 2.3.7+dfsg1-1 nix-bin suggests no packages. -- no debconf information
Bug#1018131: ITP: neo-cli -- digital rain simulator
Le jeu. 25 août 2022 à 21:30, a écrit : > * Package name: neo-cli > [...] > Description : digital rain simulator > > I intend to package neo-cli, a digital rain simulator like cmatrix. > It will not match your need but I wonder if 'neo-rain' would be better name. >
Bug#1018167: gettext: FTBFS on hurd-i386
Hello, Santiago Vila, le ven. 26 août 2022 14:25:19 +0200, a ecrit: > > FAIL: msgcat-17 > > === > > > > 16,18c16,18 > > < "Fehler beim Schreiben eines großen Ergebnisses auf eine zu kleine " > > < "Platte% s% smit der jederzeitigen Möglichkeit eines Fehlers in jedem > > Moment " > > < "und an jeder Stelle" > > --- > > > "Fehler beim Schreiben eines großen Ergebnisses auf eine zu kleine > > > Platte% s" > > > "% smit der jederzeitigen Möglichkeit eines Fehlers in jedem Moment und > > > an " > > > "jeder Stelle" > > I have the feeling that this may have something to do with terminal width on > Hurd, but I don't really know. I don't pay particular attention to my terminal width when I restart buildd, but I also had a quick try, and building gettext in various terminal sizes doesn't change the result (and it should really not, otherwise it's a gettext test suite bug, I'd say :) Also, note that: > > < "Fehler beim Schreiben eines großen Ergebnisses auf eine zu kleine " > > < "Platte% s% smit der jederzeitigen Möglichkeit eines Fehlers in jedem > > Moment " > > --- > > > "Fehler beim Schreiben eines großen Ergebnisses auf eine zu kleine > > > Platte% s" > > > "% smit der jederzeitigen Möglichkeit eines Fehlers in jedem Moment und > > > an " In the second line of the reference, there are more characters than in the first line of the obtained result. So it's probably not a question of width, but I guess it may rather be related to e.g. word breaking rules. Investigation would be needed to find out what exactly makes the break happen at a different position. Samuel
Bug#1017083: [pkg-crosswire-devel] Bug#1017083: All sources are included, the bug report is invalid
Control: severity -1 serious
Am 26.08.22 um 14:15 schrieb Teus Benschop:
Additionally the quill code was downloaded from the official quill releases in
whatever form their official releases are.
"Webpack" does not come in here.
The point is that the quill releases do not fit Debian's definition of source,
so the bug IS valid at least for quill.
Bastien pointed to the non-minifies quill files because they are readable ("full") source but not source that is defined
by preferred form for modification.
The right thing would be to create a libjs-quill package that builds the module from the source available at:
https://github.com/quilljs/quill. Then depend on that package.
Actually, this is a serious bug as filed by Bastien. If we as a team cannot afford the time to make this package abide
by the DFSG, then it is justified that the autoremove automation kicks in.
Bug#1018004: qt6-tools: does not build and link with system litehtml
Hi Rob! On Thu, 25 Aug 2022 at 21:37, Rob Savoury wrote: > > Hi Lisandro, > > It's a good suggestion about doing a MR using Salsa in future, an > option that I didn't consider (three years ago I did make a Salsa > account for one task with another package, so an MR is possible). > > There are actually two issues here. A key one is certainly with the > missing litehtmlConfig.cmake file, which I did actually mention in > the first paragraph of the bug report. Indeed you did, sorry for that! > So until litehtml is updated > it does block this bug being resolved. > > However, there is another issue with qt6-tools CMake logic causing > the CMake configure phase to error out when trying to build with a > system litehtml package. Here are the errors (can be confirmed by > attempting to build qt6-tools with a version of litehtml that does > include litehtmlConfig.cmake): > > ``` > CMake Error at > /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFlagHandlingHelpers.cmake:171 > (target_compile_definitions): > Cannot specify compile definitions for target "litehtml" which is > not built > by this project. > Call Stack (most recent call first): > src/assistant/CMakeLists.txt:34 (qt_internal_set_exceptions_flags) > > > CMake Error at > /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFlagHandlingHelpers.cmake:190 > (get_target_property): > get_target_property() called with non-existent target "litehtml". > Call Stack (most recent call first): > src/assistant/CMakeLists.txt:35 (qt_disable_warnings) > > > CMake Error at > /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFlagHandlingHelpers.cmake:190 > (get_target_property): > get_target_property() called with non-existent target "gumbo". > Call Stack (most recent call first): > src/assistant/CMakeLists.txt:37 (qt_disable_warnings) > ``` > > These errors cause FTBFS unless src/assistant/CMakeLists.txt in > qt6-tools is also patched. In the patch I attached to this bug > report is then a proposed patch to include in qt6-tools package. > > The proposed patch to include in qt6-tools package simply removes > the three offending CMake commands that cause the above quoted > errors. So it appears to be an upstream bug with CMake logic used by > qt6-tools as well (though I haven't filed a bug with Qt directly yet > as I first wanted to report it here). It seems that upstream does > not properly cater to using a system litehtml library after all. > > Also a change to the header path for litehtml will be required if a > version of litehtml > 0.5 is packaged by the maintainer due to newer > litehtml moving headers into a litehtml directory. Thus, the patch > that I proposed to include in qt6-tools would also modify this file: > > src/assistant/qlitehtml/src/container_qpainter_p.h > > The header path in that file would be changed from litehtml.h to > litehtml/litehtml.h as per litehtml > 0.5 source. Yes, ideally we need to solve this directly upstream. > Therefore it does certainly seem easier just to use the litehtml > source included in qt6-tools in the end! However, as litehtml is > already packaged in Debian and given that qt6-tools has a BD on > liblitehtml-dev that was not actually being used it is indeed a bug > (and with both packages, as explained above). At least in terms of > the intended outcomes! So that's why I filed the two bug reports. The two bugs are totally fine! but first we need liblitehtml to move forward first. Again, thanks for your effort and time! -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/
Bug#1018167: gettext: FTBFS on hurd-i386
Package: src:gettext Version: 0.21-9 X-Debbugs-CC: sanv...@debian.org,debian-h...@lists.debian.org After applying the patch proposed in Bug#982085 (with minor changes), the build-dependencies of gettext now allow building under hurd-i386, but currently it fails some tests. Example: FAIL: msgcat-17 === 16,18c16,18 < "Fehler beim Schreiben eines großen Ergebnisses auf eine zu kleine " < "Platte% s% smit der jederzeitigen Möglichkeit eines Fehlers in jedem Moment " < "und an jeder Stelle" --- "Fehler beim Schreiben eines großen Ergebnisses auf eine zu kleine Platte% s" "% smit der jederzeitigen Möglichkeit eines Fehlers in jedem Moment und an " "jeder Stelle" I have the feeling that this may have something to do with terminal width on Hurd, but I don't really know. It would be really nice if some Hurd porter could look at this and propose a patch which works (hence the X-Debbugs-CC). Full build log available here: https://buildd.debian.org/status/fetch.php?pkg=gettext=hurd-i386=0.21-8=1661482459=0 Note: Version 0.21-9 which I have just uploaded right now is expected to fail in the same way, because the changes are not related at all with the tests. Thanks.
Bug#1018164: ITP: sonivox -- Embedded Audio Synthesis Library
I already packaged it here: https://salsa.debian.org/multimedia-team/sonivox
