Bug#1054298: apt-listchanges: 4.4 still/again showing old changelogs
Package: apt-listchanges Version: 4.4 Severity: normal Hello, I had tested 4.0 and 4.1 and had seen old changelogs. Upgrading to 4.2 did not fix this (although it should have) so I purged apt-listchanges, manually removed /var/lib/apt/listchanges* and reinstalled apt-listchanges. Things seemed to work for some time. Then today I upgraded to 4.4, and afterwards did a dist-upgrade and was shown e.g: linux (4.19.37-6) unstable; urgency=high [...] -- Salvatore Bonaccorso Fri, 19 Jul 2019 00:23:17 +0200 cu Andreas -- Package-specific info: ==> /etc/apt/listchanges.conf <== [apt] frontend=pager which=both no_network=false email_address=root email_format=text confirm=true headers=false reverse=false save_seen=none capture_snapshots=auto snapshot_dir=/var/lib/apt/listchanges-snapshots -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.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 apt-listchanges depends on: ii apt2.7.6 ii debconf [debconf-2.0] 1.5.82 ii python33.11.4-5+b1 ii python3-apt2.6.0 ii python3-debconf1.5.82 ii sensible-utils 0.0.20 ii ucf3.0043+nmu1 apt-listchanges recommends no packages. Versions of packages apt-listchanges suggests: ii exim4-daemon-light [mail-transport-agent] 4.97~RC2-2 ii firefox [www-browser] 118.0.2-1 ii lynx [www-browser] 2.9.0dev.12-1 ii mlterm [x-terminal-emulator] 3.9.3-1 ii python3-gi 3.46.0-1 ii w3m [www-browser] 0.5.3+git20230121-2 ii xterm [x-terminal-emulator]385-1 -- debconf-show failed ~ ~ ~ ~
Bug#1053188:
'apt install libsvtav1enc1d1' resolved the problem for me. Doing so removed blender (and rendered it uninstallable? 'apt install blender' finds no installation candidate), but I don't need blender at present. With that package installed, 'apt dist-upgrade' upgraded only libavif15:i386 , and all was well. On Fri, Oct 20, 2023 at 9:56 PM Charlie Hagedorn wrote: > As a week has passed and regular updates haven't resolved the issue, so > I've dug in deeper. Following a suggestion here ( > https://unix.stackexchange.com/questions/446729/can-i-see-why-apt-get-install-f-is-removing-my-package > ) was helpful. > > It appears that a single package is the root of the trouble. "Holding Back > libsvtav1enc1d1:amd64 rather than change libsvtav1enc1:amd64" > > Through a dependency chain, this has downstream impacts to gimp, > gnome-control-center, flowblade, blender, viking, wine64, and more. > > $ sudo apt -o Debug::pkgProblemResolver=true dist-upgrade 2>&1 | grep > rather > Holding Back libsvtav1enc1d1:amd64 rather than change libsvtav1enc1:amd64 > Holding Back libavif16:amd64 rather than change libsvtav1enc1d1:amd64 > Removing libgd3:amd64 rather than change libavif16:amd64 > Removing gnuplot-x11:amd64 rather than change libgd3:amd64 > Removing libgphoto2-6:amd64 rather than change libgd3:amd64 > Removing libwebkit2gtk-4.1-0:amd64 rather than change libavif16:amd64 > Removing libsane1:amd64 rather than change libgphoto2-6:amd64 > Removing yelp:amd64 rather than change libwebkit2gtk-4.1-0:amd64 > Removing libyelp0:amd64 rather than change libwebkit2gtk-4.1-0:amd64 > Removing libopencv-videoio406:amd64 rather than change libgphoto2-6:amd64 > Removing sane-utils:amd64 rather than change libsane1:amd64 > Removing graphviz:amd64 rather than change libgd3:amd64 > Removing libgvc6:amd64 rather than change libgd3:amd64 > Removing gvfs-backends:amd64 rather than change libgphoto2-6:amd64 > Removing libgoa-backend-1.0-1:amd64 rather than change > libwebkit2gtk-4.1-0:amd64 > Removing gnome-control-center:amd64 rather than change > libgoa-backend-1.0-1:amd64 > Removing gnome-online-accounts:amd64 rather than change > libgoa-backend-1.0-1:amd64 > Removing libwine:amd64 rather than change libgphoto2-6:amd64 > Removing gnome-user-docs:amd64 rather than change yelp:amd64 > Removing python3-pygraphviz:amd64 rather than change graphviz:amd64 > Removing gir1.2-webkit2-4.1:amd64 rather than change > libwebkit2gtk-4.1-0:amd64 > Removing libc-devtools:amd64 rather than change libgd3:amd64 > Removing xsane:amd64 rather than change libsane1:amd64 > Removing python3-pydot:amd64 rather than change graphviz:amd64 > Removing gnome-sushi:amd64 rather than change gir1.2-webkit2-4.1:amd64 > Removing dvipng:amd64 rather than change libgd3:amd64 > Removing libgmic1:amd64 rather than change libopencv-videoio406:amd64 > Removing python3-opencv:amd64 rather than change > libopencv-videoio406:amd64 > Removing gimp:amd64 rather than change graphviz:amd64 > Removing libimage-sane-perl:amd64 rather than change libsane1:amd64 > Removing libopenimageio2.4:amd64 rather than change > libopencv-videoio406:amd64 > Removing gnumeric-doc:amd64 rather than change yelp:amd64 > Removing gmic:amd64 rather than change libgmic1:amd64 > Removing darktable:amd64 rather than change libgphoto2-6:amd64 > Removing gphoto2:amd64 rather than change libgphoto2-6:amd64 > Removing viking:amd64 rather than change yelp:amd64 > Removing flowblade:amd64 rather than change gmic:amd64 > Removing gscan2pdf:amd64 rather than change libimage-sane-perl:amd64 > Removing libgphoto2-dev:amd64 rather than change libgphoto2-6:amd64 > Removing blender:amd64 rather than change libopenimageio2.4:amd64 > Removing gimp-ufraw:amd64 rather than change gimp:amd64 > Removing wine64:amd64 rather than change libwine:amd64 > Holding Back libsvtav1enc1d1:amd64 rather than change libsvtav1enc1:amd64 > Holding Back libavif16:amd64 rather than change libsvtav1enc1d1:amd64 > Removing libgd3:amd64 rather than change libavif16:amd64 > Holding Back libgd3:i386 rather than change libgd3:amd64 > Holding Back libavif15:i386 rather than change libavif15:amd64 > > Will report back if I find a way to resolve the issue. > > On Sun, Oct 15, 2023 at 4:31 PM Charlie Hagedorn > wrote: > >> I've encountered the same behavior twice. First time was a total surprise >> and I had to 'apt install darktable', which fortunately worked. >> >> Today, I noted that darktable would be removed with apt dist-upgrade >> >> Requested output follows: >> >> [charlie@dicke:~]$ sudo apt dist-upgrade >> Reading package lists... Done >> Building dependency tree... Done >> Reading state information... Done >> Calculating upgrade... Done >> The following packages were automatically installed and are no longer >> required: >> apg blender-data bolt cracklib-runtime djvulibre-bin docbook-xml >> docbook-xsl expect fonts-liberation2 fwupd
Bug#1054180: openssl: FTBFS on loong64
On 10/21/23 01:58, Sebastian Andrzej Siewior wrote: On 2023-10-20 13:49:01 [+0800], WANG Xuerui wrote: This is likely upstream issue https://github.com/openssl/openssl/issues/21340, manifesting on Debian due to the packaged binutils not having Loongson SIMD support yet, and fixed by upstream commit 160f48941d143cf2682df4e938ba953c96ac3c7a. I'd suggest including the upstream patch so we don't have to touch anywhere else. So submitting patches for projects before having the upstream in the building tools. Nobody can build this then. What about uploading a custom binutils with the needed support to ports until it is merged upstream? Hmm, not quite; with the commit I linked to applied, the build will get fixed, only that the asm code won't get built. It's a matter of the original change adding SIMD optimization not taking care of toolchain probing. Also the binutils instruction set support is actually complete and released in 2.41, so a custom build isn't necessary either: we'd only have to wait until Debian bumps the binutils version to 2.41 across the board. It's a good thing to not move so quickly, on the other hand; we've already hit some interesting bugs in Gentoo land due to the linker relaxation thing...
Bug#1053188:
As a week has passed and regular updates haven't resolved the issue, so I've dug in deeper. Following a suggestion here ( https://unix.stackexchange.com/questions/446729/can-i-see-why-apt-get-install-f-is-removing-my-package ) was helpful. It appears that a single package is the root of the trouble. "Holding Back libsvtav1enc1d1:amd64 rather than change libsvtav1enc1:amd64" Through a dependency chain, this has downstream impacts to gimp, gnome-control-center, flowblade, blender, viking, wine64, and more. $ sudo apt -o Debug::pkgProblemResolver=true dist-upgrade 2>&1 | grep rather Holding Back libsvtav1enc1d1:amd64 rather than change libsvtav1enc1:amd64 Holding Back libavif16:amd64 rather than change libsvtav1enc1d1:amd64 Removing libgd3:amd64 rather than change libavif16:amd64 Removing gnuplot-x11:amd64 rather than change libgd3:amd64 Removing libgphoto2-6:amd64 rather than change libgd3:amd64 Removing libwebkit2gtk-4.1-0:amd64 rather than change libavif16:amd64 Removing libsane1:amd64 rather than change libgphoto2-6:amd64 Removing yelp:amd64 rather than change libwebkit2gtk-4.1-0:amd64 Removing libyelp0:amd64 rather than change libwebkit2gtk-4.1-0:amd64 Removing libopencv-videoio406:amd64 rather than change libgphoto2-6:amd64 Removing sane-utils:amd64 rather than change libsane1:amd64 Removing graphviz:amd64 rather than change libgd3:amd64 Removing libgvc6:amd64 rather than change libgd3:amd64 Removing gvfs-backends:amd64 rather than change libgphoto2-6:amd64 Removing libgoa-backend-1.0-1:amd64 rather than change libwebkit2gtk-4.1-0:amd64 Removing gnome-control-center:amd64 rather than change libgoa-backend-1.0-1:amd64 Removing gnome-online-accounts:amd64 rather than change libgoa-backend-1.0-1:amd64 Removing libwine:amd64 rather than change libgphoto2-6:amd64 Removing gnome-user-docs:amd64 rather than change yelp:amd64 Removing python3-pygraphviz:amd64 rather than change graphviz:amd64 Removing gir1.2-webkit2-4.1:amd64 rather than change libwebkit2gtk-4.1-0:amd64 Removing libc-devtools:amd64 rather than change libgd3:amd64 Removing xsane:amd64 rather than change libsane1:amd64 Removing python3-pydot:amd64 rather than change graphviz:amd64 Removing gnome-sushi:amd64 rather than change gir1.2-webkit2-4.1:amd64 Removing dvipng:amd64 rather than change libgd3:amd64 Removing libgmic1:amd64 rather than change libopencv-videoio406:amd64 Removing python3-opencv:amd64 rather than change libopencv-videoio406:amd64 Removing gimp:amd64 rather than change graphviz:amd64 Removing libimage-sane-perl:amd64 rather than change libsane1:amd64 Removing libopenimageio2.4:amd64 rather than change libopencv-videoio406:amd64 Removing gnumeric-doc:amd64 rather than change yelp:amd64 Removing gmic:amd64 rather than change libgmic1:amd64 Removing darktable:amd64 rather than change libgphoto2-6:amd64 Removing gphoto2:amd64 rather than change libgphoto2-6:amd64 Removing viking:amd64 rather than change yelp:amd64 Removing flowblade:amd64 rather than change gmic:amd64 Removing gscan2pdf:amd64 rather than change libimage-sane-perl:amd64 Removing libgphoto2-dev:amd64 rather than change libgphoto2-6:amd64 Removing blender:amd64 rather than change libopenimageio2.4:amd64 Removing gimp-ufraw:amd64 rather than change gimp:amd64 Removing wine64:amd64 rather than change libwine:amd64 Holding Back libsvtav1enc1d1:amd64 rather than change libsvtav1enc1:amd64 Holding Back libavif16:amd64 rather than change libsvtav1enc1d1:amd64 Removing libgd3:amd64 rather than change libavif16:amd64 Holding Back libgd3:i386 rather than change libgd3:amd64 Holding Back libavif15:i386 rather than change libavif15:amd64 Will report back if I find a way to resolve the issue. On Sun, Oct 15, 2023 at 4:31 PM Charlie Hagedorn wrote: > I've encountered the same behavior twice. First time was a total surprise > and I had to 'apt install darktable', which fortunately worked. > > Today, I noted that darktable would be removed with apt dist-upgrade > > Requested output follows: > > [charlie@dicke:~]$ sudo apt dist-upgrade > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: > apg blender-data bolt cracklib-runtime djvulibre-bin docbook-xml > docbook-xsl expect fonts-liberation2 fwupd fwupd-amd64-signed > geocode-glib-common > gimp-data gir1.2-evince-3.0 gir1.2-goocanvas-2.0 > gir1.2-javascriptcoregtk-4.1 gir1.2-malcontent-0 gjs gkbd-capplet > gnome-control-center-data > gnome-remote-desktop gnome-settings-daemon gnome-settings-daemon-common > gnome-user-share gstreamer1.0-gtk3 gtk2-engines-pixbuf jq libann0 > libapache2-mod-dnssd libavdevice59 libavfilter8 libavformat59 > libbabl-0.1-0 libcapi20-3 libcbor0.8 libcdk5nc6 libcdt5 libcgraph6 > libcolord-gtk4-1 > libconfig-general-perl libconfig9
Bug#1054297: exabgp can not bind to IP:179
Package: exabgp Version: 4.2.21-1.1 Severity: normal X-Debbugs-Cc: ldav...@syt.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I was trying to establish a BGP sessionbetween two exabgp services, sniffing the interface I've noticed that exabgp was sending a RST after the TCP SYN, leading me to run `ss -naltp` and not seeing exabgp listening on port 179. After changing the exabgp.tcp.bind from '' to '0.0.0.0' in exabgp.env, exabgp was not able to start informing that can not bind to 0.0.0.0:179 because it was not running as root. * What exactly did you do (or not do) that was effective (or ineffective)? I was able to let exabgp service to bind on port 179 adding the following lines to /lib/systemd/system/exabgp.service ``` CapabilityBoundingSet=CAP_NET_BIND_SERVICE CapabilityBoundingSet=CAP_NET_BIND_SERVICE ``` * What was the outcome of this action? Exabgp was able to start succesfully binding to 0.0.0.0:179 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 6.1.21-v8+ (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP 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) Versions of packages exabgp depends on: ii adduser3.137 ii debconf1.5.82 ii dpkg 1.22.0 ii init-system-helpers1.65.2 ii lsb-base 11.6 ii python3-exabgp 4.2.21-1.1 ii python3-pkg-resources 68.1.2-2 ii sysvinit-utils [lsb-base] 3.08-3 ii ucf3.0043+nmu1 exabgp recommends no packages. exabgp suggests no packages. -- no debconf information
Bug#967333: exult: depends on deprecated GTK 2
Control: block -1 by 967394 The GIMP plugin is the only thing that needs GTK 2.
Bug#1054218: texlive-latex-base: pdflatex failures on big-endian architectures (s390x)
Control: notfound -1 2020.20200327.54578-7+deb11u1 I don't recall if annotating as above actually helps the BTS at all... but for reference, since I was already fiddling about with schroot on zelenka.d.o, I tested this out in a bullseye s390x chroot and text extraction works fine. I suppose that in some way narrows it down to a regression somewhere between texlive 2020 and texlive 2022. That's probably not particularly 'narrow' but might help. regards Stuart (bullseye_s390x-dchroot)stuart@zelenka:~$ gs -q -sDEVICE=txtwrite -o %stdout% test.pdf |od -c 000 h 020 i \r \n 023 -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#1051497: closed by Debian FTP Masters (reply to Hilmar Preusse ) (Bug#1051497: fixed in texlive-extra 2023.20231007-1)
Dear Hilmar, Thank you for a quick answer. Note that the version of the package NewTX (most likely, 1.726 (cf. https://ctan.org/pkg/newtx), since all the mentioned bugs are repaired, whereas it was not the case for a few immediately preceeding versions) deviates from the version of the file newtx.sty (namely, still 1.724). My question concerns the version of the whole NewTX package and not the versions of the constituent files. (Since you wrote that the present bug report 1051497 is repaired, I highly believe you that you put 1.726 into texlive-fonts-extra, and what I'd like to know is how to check this in the future.) Cheers, AlMa.
Bug#967328: emu8051: depends on deprecated GTK 2
Am 21.10.23 um 01:51 schrieb Bastian Germann: The GTK GUI can be dropped by replacing the build dependency libgtk2.0-dev with libglib2.0-dev, and by excluding src/gtk from make's SUBDIRS. The emu8051.desktop and the emu8051-gtk.1 link should be removed then as well.
Bug#972761: Info received (telemetry data for thunderbird is still opt-out in 1:102.15.1-1~deb12u1)
hi again
Sorry, I didn't include the line numbers in the patch. The patch should
be:
--- python/mach/mach/telemetry.py.orig 2023-10-21 00:34:41.135764889 +0200
+++ python/mach/mach/telemetry.py 2023-10-21 01:08:02.500039001 +0200
@@ -99,7 +99,9 @@
def is_telemetry_enabled(settings):
-if os.environ.get("DISABLE_TELEMETRY") == "1":
+if os.environ.get("DISABLE_TELEMETRY") == "0":
+return True
+else:
return False
return settings.mach_telemetry.is_enabled
The same suggestion patch is at https://paste.debian.net/1295726 (email clients
may
modify the formatting when viewing this email).
My guess is that the initialize_telemetry_setting() part starting on line 281
is either
for the case where someone is a Mozilla employee or uses the script
interactively,
so the section probably doesn't need to be changed.
Cheers
Boud
Bug#967328: emu8051: depends on deprecated GTK 2
The GTK GUI can be dropped by replacing the build dependency libgtk2.0-dev with libglib2.0-dev, and by excluding src/gtk from make's SUBDIRS.
Bug#1054296: pass-otp: Man page does not document the URI format
Package: pass-otp Version: 1.2.0-9 Severity: wishlist Tags: patch upstream X-Debbugs-Cc: tipos...@tiscali.it Dear Maintainer, I noticed that there is a URI needed to configure a seed, but that format is not documented anywhere in the manpage. I made a patch (which I've also sent upstream) to have some examples in the manpage so that people can read how to configure their seeds. Best -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 pass-otp depends on: ii pass 1.7.4-6 Versions of packages pass-otp recommends: ii oathtool 2.6.9-1 ii qrencode 4.1.1-1 Versions of packages pass-otp suggests: pn zbar-tools -- no debconf information >From f93d3206c6f16f3ef3b7dafadd1e0156e1d64f8c Mon Sep 17 00:00:00 2001 From: Salvo 'LtWorf' Tomaselli Date: Sat, 21 Oct 2023 01:42:01 +0200 Subject: [PATCH] Add examples to manpage I copied the more relevant examples from the README and put them in the manpage, so that it should be possible to use the tool by learning its usage from man. Without the url format being documented it is not possible to use it. --- pass-otp.1 | 28 +++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/pass-otp.1 b/pass-otp.1 index 9bded0c..1928ebe 100644 --- a/pass-otp.1 +++ b/pass-otp.1 @@ -1,4 +1,4 @@ -.TH PASS-OTP 1 "2017 March 19" "Password store OTP extension" +.TH PASS-OTP 1 "2023 September 21" "Password store OTP extension" .SH NAME pass-otp - A \fBpass\fP(1) extension for managing one-time-password (OTP) tokens. @@ -113,6 +113,32 @@ information about this format, see the documentation at \fBhelp\fP, \fB\-h\fP, \fB\-\-help\fP Show usage message. +.SH EXAMPLES + +.TP +.B Insert new OTP seed +$ pass otp insert totp-secret +.br +For totp the secret will be in the format: otpauth://totp/totp-secret?secret=AAA=totp-secret +.TP +.B To use your webcam to scan a QR code +$ zbarcam -q --raw | pass otp insert totp-secret +.TP +.B To use your webcam to append to an existing passfile +$ zbarimg -q --raw google-qrcode.png | pass otp append google/exam...@gmail.com +.br +If you have a clipboard management console tool such as `wl-clipboard` for +Wayland installed, you can also select "Copy Image" in your favorite browser +and run +.br +$ wl-paste | zbarimg -q --raw - | pass otp append google/exam...@gmail.com +.TP +.B Generate a 2FA code using seed +$ pass otp totp-secret +.TP +.B Display a QR code for an OTP token: +$ pass otp uri -q totp-secret + .SH SEE ALSO .BR pass (1), .BR qrencode (1), -- 2.42.0
Bug#1054295: RFP: python-iconify -- Python wrapper for the Iconify API to load standard icons
Package: wnpp Severity: wishlist X-Debbugs-Cc: stu...@debian.org * Package name: python-iconify Version : 0.1.5 Upstream Contact: Talley Lambert https://github.com/tlambert03 * URL : https://github.com/pyapp-kit/pyconify * License : BSD 3-clause Programming Lang: Python Description : Python wrapper for the Iconify API to load standard icons Iconify is a versatile icon framework that includes 100+ icon sets with more than 100,000 icons from FontAwesome, Material Design Icons, DashIcons, Feather Icons, EmojiOne, Noto Emoji and many other open source icon sets. This package provides a simple Python wrapper around the Iconify API that fetches and caches icons for use by GUI applications. This package is an optional dependency of the most recent version of superqt; the QIconifyIcon class provides a QIcon that is backed by the specified iconify icon.
Bug#1049209: mfgtools build twice fixed in git
Control: tags -1 + pending The problem should be fixed in https://salsa.debian.org/DebianOnMobile-team/mfgtools/-/commit/bbf6e01fba27d959bafc757cdef8d1fe54295dcc and will be part of next uploaded package version. Regards, Andreas Henriksson
Bug#967569: libcanberra: depends on deprecated GTK 2
On Sun, 15 Oct 2023 10:49:19 +0100 Simon McVittie wrote: # Broken Build-Depends: gnubg: libcanberra-gtk-dev gnubg has been upgraded to gtk3. So the patch can now be applied.
Bug#1054279: Adjusted Swedish translation
Hi Martin, I took the liberty of fixing up a few typos. Can be seen in the diff. Regards, Anders# Translation of mini-buildd debconf template to Swedish # Copyright (C) 2023 Martin Bagge # This file is distributed under the same license as the mini-buildd package. # # Martin Bagge , 2010, 2023 msgid "" msgstr "" "Project-Id-Version: mini-buildd\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-10-19 20:25+\n" "PO-Revision-Date: 2023-10-20 15:09+0200\n" "Last-Translator: Martin Bagge / brother \n" "Language-Team: Swedish \n" "Language: Swedish\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: note #. Description #: ../mini-buildd.templates:2001 msgid "mini-buildd data purge warning" msgstr "Dataraderings-varning för mini-buildd" #. Type: note #. Description #: ../mini-buildd.templates:2001 msgid "You have chosen to purge mini-buildd." msgstr "Du har valt att radera mini-buildd." #. Type: note #. Description #: ../mini-buildd.templates:2001 msgid "" "As a consequence, the mini-buildd user will be removed along with all the " "files it owns, possibly including Debian repositories." msgstr "" "Detta innebär att mini-buildd-användaren kommer att tas bort tillsammans med " "alla dess filer, detta kan inkludera eventuella Debian-förråd." #. Type: note #. Description #: ../mini-buildd.templates:2001 msgid "To keep this data, you need to back it up now." msgstr "För att behålla dessa data måste du göra en säkerhetskopia nu." #. Type: string #. Description #: ../mini-buildd.templates:3001 msgid "Home path:" msgstr "Sökväg för hemkatalog:" #. Type: string #. Description #: ../mini-buildd.templates:3001 msgid "" "Please choose the directory where mini-buildd data will be stored. The " "directory will also be the home directory for the mini-buildd user." msgstr "" "Ange an katalog där mini-buildd-data ska lagras. Katalogen kommer också vara " "hemkatalog för mini-buildd-användaren." #. Type: string #. Description #: ../mini-buildd.templates:3001 msgid "" "It should have enough space for all the builders and repositories you plan " "to use." msgstr "" "Den behöver ha plats för alla byggare och förråd som du planerar att använda." #. Type: password #. Description #: ../mini-buildd.templates:4001 msgid "Administrator password for mini-buildd:" msgstr "Administrativt lösenord för mini-buildd:" #. Type: password #. Description #: ../mini-buildd.templates:4001 msgid "" "Please choose the password for the administrative user of mini-buildd. This " "password will be used for the \"admin\" user in mini-buildd's web interface " "and API." msgstr "" "Ange lösenord för mini-buildd-användaren. Detta lösenord kommer att användas " "för \"admin\"-användaren i mini-buildds webbgränssnitt och API." #. Type: password #. Description #: ../mini-buildd.templates:4001 msgid "" "If you enter a password, this will also trigger the creation of a local " "\"admin\" user (if not existing already)." msgstr "" "Anges ett lösenord innebär det att en lokal \"admin\"-användare kommer att " "skapas om den inte redan finns." #. Type: password #. Description #: ../mini-buildd.templates:4001 msgid "" "If you leave this empty, nothing will be done (no potential \"admin\" user " "creation, no password change)." msgstr "" "Lämnas detta tomt kommer inga ändringar att genomföras (ingen \"admin\"-" "användare skapas och inga lösenord kommer att ändras)." #. Type: string #. Description #: ../mini-buildd.templates:5001 msgid "Extra options:" msgstr "Extra alternativ:" #. Type: string #. Description #: ../mini-buildd.templates:5001 msgid "" "Using no extra options is perfectly fine, and would run (unencrypted) HTTP " "on port 8066." msgstr "" "Det är helt i sin ordning att inte ha några extra alternativ angivna. Det " "leder till att okrypterad HTTP används på port 8066." #. Type: string #. Description #: ../mini-buildd.templates:5001 msgid "" "To run (encrypted) HTTPS, please check out option \"--http-" "endpoint\" (details in the \"Administrator's Manual\")." msgstr "" "För att köra HTTPS (alltså med kryptering) kan du läsa om växeln \"--http-" "endpoint\" (djupare detaljer i Administrationsmanualen - \"Administrator's " "Manual\" på engelska)." #. Type: string #. Description #: ../mini-buildd.templates:5001 msgid "\"mini-buildd --help\" gives a list of all available options." msgstr "\"mini-buildd --help\" visar en lista med alla tillgängliga flaggor." #. Type: note #. Description #: ../mini-buildd.templates:6001 msgid "Configuration of mini-buildd complete" msgstr "mini-buildd redo att användas" #. Type: note #. Description #: ../mini-buildd.templates:6001 msgid "" "Unless you changed the defaults, you should now be able to visit the new " "home of the local mini-buildd instance at http://localhost:8066.; msgstr "" "Så länge du inte ändrade standardvärdena så ska du nu kunna besöka din " "lokala mini-buildd-instans på http://localhost:8066.; #. Type: note #.
Bug#972761: telemetry data for thunderbird is still opt-out in 1:102.15.1-1~deb12u1
Dear Maintainers,
The current bookworm version 1:102.15.1-1~deb12u1 of Thunderbird
still has opt-*out*, not opt-in, for telemetry. While we don't
seem to have a formal Debian policy on this, it would be within
the spirit of Debian to set this to opt-in, not opt-out.
We do have some warnings at https://wiki.debian.org/PrivacyIssues,
but better that telemetry options are patched to be opt-in, not
opt-out. This is what people would expect from Debian.
The opt-out telemetry that I could find is this:
./python/mozbuild/mozbuild/test/test_telemetry_settings.py-135-
./python/mozbuild/mozbuild/test/test_telemetry_settings.py-136-def
test_initialize_noop_when_telemetry_disabled_env(monkeypatch):
./python/mozbuild/mozbuild/test/test_telemetry_settings.py:137:
monkeypatch.setenv("DISABLE_TELEMETRY", "1")
./python/mozbuild/mozbuild/test/test_telemetry_settings.py-138-with
mock.patch("mach.telemetry.record_telemetry_settings") as record_mock:
./python/mozbuild/mozbuild/test/test_telemetry_settings.py-139-
did_prompt = _initialize_telemetry(None, False)
--
./python/mach/mach/telemetry.py-100-
./python/mach/mach/telemetry.py-101-def is_telemetry_enabled(settings):
./python/mach/mach/telemetry.py:102:if os.environ.get("DISABLE_TELEMETRY") ==
"1":
./python/mach/mach/telemetry.py-103-return False
./python/mach/mach/telemetry.py-104-
--
./python/mach/mach/telemetry.py-289-state_dir = Path(state_dir)
./python/mach/mach/telemetry.py-290-
./python/mach/mach/telemetry.py:291:if os.environ.get("DISABLE_TELEMETRY") ==
"1":
./python/mach/mach/telemetry.py-292-return
./python/mach/mach/telemetry.py-293-
So I propose the following patch:
--- python/mach/mach/telemetry.py.orig 2023-10-21 00:34:41.135764889 +0200
+++ python/mach/mach/telemetry.py 2023-10-21 01:05:01.073107778 +0200
def is_telemetry_enabled(settings):
-if os.environ.get("DISABLE_TELEMETRY") == "1":
+if os.environ.get("DISABLE_TELEMETRY") == "0":
+return True
+else:
return False
return settings.mach_telemetry.is_enabled
to switch from opt-out to opt-in. *Unless* the user has set DISABLE_TELEMETRY
to 0,
the value of settings.mach_telemetry.is_enabled will be 'False'. (Python experts
might wish to leave the 'else' part blank, but making the alternative explicit
is safer and more readable.)
I haven't tested this, though
./python/mozbuild/mozbuild/test/test_telemetry_settings.py
is presumably used for testing it, and the test might have to be toggled in
order to pass with the ethically correct value: opt-in.
Cheers
Boud
Bug#967321: dwarf-fortress: depends on deprecated GTK 2
https://github.com/svenstaro/dwarf_fortress_unfuck has patches that enable building with GTK 3 or without GTK.
Bug#1054294: mlpack: binary-all FTBFS
Source: mlpack Version: 4.2.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mlpack=all=4.2.1-1=1697842001=0 ... debian/rules execute_after_dh_install make[1]: Entering directory '/<>' use shared jquery.js javascript library for f in $(find debian/mlpack-doc -name jquery.js); do \ ln --verbose --symbolic --force /usr/share/javascript/jquery/jquery.js $f; \ done find: ‘debian/mlpack-doc’: No such file or directory remove byte-compiled python files per policy find debian/python-mlpack -name '*.pyc' -ls -delete || true find: ‘debian/python-mlpack’: No such file or directory find debian/python3-mlpack -name '*.pyc' -ls -delete || true find: ‘debian/python3-mlpack’: No such file or directory remove extra license file rm --verbose debian/libmlpack-dev/usr/include/mlpack/core/std_backport/LICENSE.txt rm: cannot remove 'debian/libmlpack-dev/usr/include/mlpack/core/std_backport/LICENSE.txt': No such file or directory make[1]: [debian/rules:107: execute_after_dh_install] Error 1 (ignored) move stray documentation files into /usr/share/doc/ (cd debian/libmlpack-dev && \ for f in $(find usr/include -type f \! -name '*.hpp' \! -name '*.cpp'); do \ mkdir -p usr/share/doc/libmlpack-dev/$(dirname $f) && \ mv --verbose $f usr/share/doc/libmlpack-dev/$(dirname $f)/; \ done) /bin/sh: 1: cd: can't cd to debian/libmlpack-dev make[1]: *** [debian/rules:109: execute_after_dh_install] Error 2
Bug#1054293: network-manager-vpnc FTBFS: dh_install: warning: network-manager-vpnc missing files: usr/libecec/nm-vpnc-service-vpnc-helper
Source: network-manager-vpnc Version: 1.2.8-6 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=network-manager-vpnc=1.2.8-6 ... dh_install -a dh_install: warning: Cannot find (any matches for) "usr/libecec/nm-vpnc-service-vpnc-helper" (tried in ., debian/tmp) dh_install: warning: network-manager-vpnc missing files: usr/libecec/nm-vpnc-service-vpnc-helper dh_install: error: missing files, aborting make: *** [debian/rules:7: binary-arch] Error 25
Bug#1054292: gpsim: Build-Depends unnecessarily on gtkextra
I am uploading a NMU to DELAYED/10 in order to fix this. The debdiff is attached.diff -Nru gpsim-0.31.0/debian/changelog gpsim-0.31.0/debian/changelog --- gpsim-0.31.0/debian/changelog 2019-09-08 20:12:59.0 +0200 +++ gpsim-0.31.0/debian/changelog 2023-10-21 00:06:02.0 +0200 @@ -1,3 +1,10 @@ +gpsim (0.31.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Drop unnecessary Build-Depends: quilt, libgtkextra-dev. Closes: #1054292 + + -- Bastian Germann Sat, 21 Oct 2023 00:06:02 +0200 + gpsim (0.31.0-2) unstable; urgency=medium * adopted Slávek Banko's patch, thanks! Closes: #939338 diff -Nru gpsim-0.31.0/debian/control gpsim-0.31.0/debian/control --- gpsim-0.31.0/debian/control 2019-08-25 18:24:58.0 +0200 +++ gpsim-0.31.0/debian/control 2023-10-21 00:06:02.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Georges Khaznadar Build-Depends: debhelper (>= 11), libreadline-dev, libncurses5-dev, libpopt-dev, libglib2.0-dev, libtool, flex, automake, autotools-dev, - libtool-bin, bison, chrpath, gputils, quilt, libgtkextra-dev, libgtk2.0-dev + libtool-bin, bison, chrpath, gputils, libgtk2.0-dev Standards-Version: 4.1.4 Vcs-Browser:https://salsa.debian.org/georgesk/gpsim Vcs-Git: https://salsa.debian.org/georgesk/gpsim.git
Bug#1054292: gpsim: Build-Depends unnecessarily on gtkextra
Source: gpsim Version: 0.31.0-2 Control: unblock 967489 by 967454 Please drop the unnecessary build dependency libgtkextra-dev.
Bug#1052297:
Package: node-heya-globalize Version: 1.2.1
Bug#967874: libgnomecanvas: depends on deprecated libglade2
No reverse dependency depends on the optional glade support, so it can be dropped. I am uploading a NMU to DELAYED/10 in order to fix this. The debdiff is attached.diff -Nru libgnomecanvas-2.30.3/debian/changelog libgnomecanvas-2.30.3/debian/changelog --- libgnomecanvas-2.30.3/debian/changelog 2018-08-30 22:19:52.0 +0200 +++ libgnomecanvas-2.30.3/debian/changelog 2023-10-20 22:44:18.0 +0200 @@ -1,3 +1,10 @@ +libgnomecanvas (2.30.3-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Drop glade support. (Closes: #967874) + + -- Bastian Germann Fri, 20 Oct 2023 22:44:18 +0200 + libgnomecanvas (2.30.3-4) unstable; urgency=low * New maintainer. (Closes: #873351, #886063, #895247) diff -Nru libgnomecanvas-2.30.3/debian/control libgnomecanvas-2.30.3/debian/control --- libgnomecanvas-2.30.3/debian/control2018-08-30 22:19:52.0 +0200 +++ libgnomecanvas-2.30.3/debian/control2023-10-20 22:43:06.0 +0200 @@ -12,7 +12,6 @@ intltool, libart-2.0-dev (>= 2.3.16), libgail-dev (>= 1.9.0), - libglade2-dev (>= 1:2.6.4-2~), libgtk2.0-dev (>= 2.8.17), xauth , xvfb diff -Nru libgnomecanvas-2.30.3/debian/libgnomecanvas2-0.install libgnomecanvas-2.30.3/debian/libgnomecanvas2-0.install --- libgnomecanvas-2.30.3/debian/libgnomecanvas2-0.install 2016-10-21 01:59:09.0 +0200 +++ libgnomecanvas-2.30.3/debian/libgnomecanvas2-0.install 2023-10-20 22:44:18.0 +0200 @@ -1,2 +1 @@ -usr/lib/*/libglade/2.0/libcanvas.so usr/lib/*/libgnomecanvas-2.so.* diff -Nru libgnomecanvas-2.30.3/debian/rules libgnomecanvas-2.30.3/debian/rules --- libgnomecanvas-2.30.3/debian/rules 2018-08-30 22:19:52.0 +0200 +++ libgnomecanvas-2.30.3/debian/rules 2023-10-20 22:43:56.0 +0200 @@ -12,8 +12,7 @@ override_dh_auto_configure: dh_auto_configure -- \ - --enable-gtk-doc \ - --enable-glade + --enable-gtk-doc override_dh_auto_test: ifeq (, $(filter nocheck, $(DEB_BUILD_OPTIONS)))
Bug#1031192: toil: FTBFS (The job JobClass is requesting 2.0 cores)
El 20/10/23 a las 23:08, Andreas Tille escribió: Am Fri, Oct 20, 2023 at 10:12:17PM +0200 schrieb Santiago Vila: But then I also realized that version tagged "debian/5.9.2-2" in git is different than version 5.9.2-2 in the FTP archive, i.e. what I can get by doing "apt-get source toil" in bookworm. I've compared tag debian/5.12.0-2 with apt source toil and did not found any diff. Are you sure about your finding? Yes. Try this: debcheckout toil cd toil git checkout debian/5.9.2-2 Then take a look at debian/changelog and compare it with the one in the archive. Thanks.
Bug#1033791: closed by Debian FTP Masters (reply to Jan Wagner ) (Bug#1033791: fixed in nagios-plugins-contrib 44.20231012)
On Thu, Oct 12, 2023 at 09:36:03PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the monitoring-plugins-contrib package: > > #1033791: check_running_kernel fails to find version on bookworm/(arm64|armhf) > > It has been closed by Debian FTP Masters > (reply to Jan Wagner ). Would it make sense to backport this fix as well in a upcoming point release for bookworm? Regards, Salvatore
Bug#1031192: toil: FTBFS (The job JobClass is requesting 2.0 cores)
Am Fri, Oct 20, 2023 at 10:12:17PM +0200 schrieb Santiago Vila: > > But then I also realized that version tagged "debian/5.9.2-2" in git > is different than version 5.9.2-2 in the FTP archive, i.e. > what I can get by doing "apt-get source toil" in bookworm. I've compared tag debian/5.12.0-2 with apt source toil and did not found any diff. Are you sure about your finding? Kind regards Andreas. > I attach the differences that I found. In the diff, "toil" is git > and "toil-5.9.2" is the version actually in the archive. > > I believe somebody should investigate this and decide > what to do. As a newcomer I don't feel capable. > > (Until them I'm going to reopen the bug so that it's not archived again). > > Thanks. > diff -ru toil/debian/changelog toil-5.9.2/debian/changelog > --- toil/debian/changelog 2023-10-20 19:42:39.746659034 + > +++ toil-5.9.2/debian/changelog 2023-02-06 18:04:14.0 + > @@ -2,16 +2,15 @@ > >* Add patch to handle errors when testing on ec2. > > - -- Michael R. Crusoe Mon, 06 Feb 2023 19:24:07 +0100 > + -- Michael R. Crusoe Mon, 06 Feb 2023 19:04:14 +0100 > > toil (5.9.2-1) unstable; urgency=medium > > - * Team upload. > + * correct build-dep on pytest-xdist > + * d/test/control: depend on "@" instead of the unversioned "toil". >* New upstream version > - * Build-Depends: s/python3-xdist/python3-pytest-xdist/ > -Closes: #1030558 > > - -- Andreas Tille Sun, 05 Feb 2023 08:38:00 +0100 > + -- Michael R. Crusoe Sat, 04 Feb 2023 19:21:49 +0100 > > toil (5.9.0-1) unstable; urgency=medium > > diff -ru toil/debian/tests/control toil-5.9.2/debian/tests/control > --- toil/debian/tests/control 2023-10-20 19:42:39.746659034 + > +++ toil-5.9.2/debian/tests/control 2023-02-04 17:45:57.0 + > @@ -1,7 +1,7 @@ > Tests: smoke-test > -Depends: toil, python3-wdlparse > +Depends: @, python3-wdlparse > Restrictions: allow-stderr, superficial > > Tests: run-unit-tests > -Depends: toil, python3, python3-wdlparse, python3-pytest, > python3-pytest-xdist, python3-mock, python3-boto3, rsync, python3-boto, > python3-stubserver, python3-yaml, quilt > +Depends: @, python3, python3-wdlparse, python3-pytest, python3-pytest-xdist, > python3-mock, python3-boto3, rsync, python3-boto, python3-stubserver, > python3-yaml, quilt > Restrictions: allow-stderr, needs-internet -- http://fam-tille.de
Bug#977160: new info?
> I'll think a bit more about what's the right thing to do now... Hi Joost, is there an update on that topic? -- regards Thomas
Bug#354432: what should be done now
Can anyone decide what to do with this bug? Wontfix, closing or is the patch working? -- regards Thomas
Bug#643663: gnat-12: Legal program rejected (record component with no supplied value) and invalid access to atomic variable
Package: gnat-12 Followup-For: Bug #643663 Control: reassign 643663 gnat-13 13.2.0-5 Control: retitle 643663 gnat: invalid access to atomic variable Hello. With gnat-13, the following sources compile without error. On the other hand, the invalid access to the atomic variable may not be fixed. Do you think we can close this bug? Upstream seems to think so (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50558) package Pkg is type Byte is mod 2**8; type Reserved_24 is mod 2**24; type Data_Record is record Data : Byte; Reserved : Reserved_24; end record; for Data_Record use record Data at 0 range 0 .. 7; Reserved at 0 range 8 .. 31; end record; for Data_Record'Size use 32; for Data_Record'Alignment use 4; Data_Register : Data_Record; pragma Atomic (Data_Register); end Pkg; with Pkg; procedure Test is begin Pkg.Data_Register := ( Data => 255, others => <> -- expected error: no value supplied for component "Reserved" ); end Test;
Bug#1031192: toil: FTBFS (The job JobClass is requesting 2.0 cores)
El 20/10/23 a las 17:53, Andreas Tille escribió: Am Fri, Oct 20, 2023 at 04:14:16PM +0200 schrieb Santiago Vila: I'd like to fix this in bookworm as well (with a "team upload"). (Unless, of course, you tell me that you prefer to take care of it yourself). Please, pretty please care for it. ;-) Ok, I tried for all this afternoon. I was first unable to build the package either with dpkg-buildpackage or with gbp buildpackage (the patches do not apply cleanly, maybe I'm doing something wrong). But then I also realized that version tagged "debian/5.9.2-2" in git is different than version 5.9.2-2 in the FTP archive, i.e. what I can get by doing "apt-get source toil" in bookworm. I attach the differences that I found. In the diff, "toil" is git and "toil-5.9.2" is the version actually in the archive. I believe somebody should investigate this and decide what to do. As a newcomer I don't feel capable. (Until them I'm going to reopen the bug so that it's not archived again). Thanks.diff -ru toil/debian/changelog toil-5.9.2/debian/changelog --- toil/debian/changelog 2023-10-20 19:42:39.746659034 + +++ toil-5.9.2/debian/changelog 2023-02-06 18:04:14.0 + @@ -2,16 +2,15 @@ * Add patch to handle errors when testing on ec2. - -- Michael R. Crusoe Mon, 06 Feb 2023 19:24:07 +0100 + -- Michael R. Crusoe Mon, 06 Feb 2023 19:04:14 +0100 toil (5.9.2-1) unstable; urgency=medium - * Team upload. + * correct build-dep on pytest-xdist + * d/test/control: depend on "@" instead of the unversioned "toil". * New upstream version - * Build-Depends: s/python3-xdist/python3-pytest-xdist/ -Closes: #1030558 - -- Andreas Tille Sun, 05 Feb 2023 08:38:00 +0100 + -- Michael R. Crusoe Sat, 04 Feb 2023 19:21:49 +0100 toil (5.9.0-1) unstable; urgency=medium diff -ru toil/debian/tests/control toil-5.9.2/debian/tests/control --- toil/debian/tests/control 2023-10-20 19:42:39.746659034 + +++ toil-5.9.2/debian/tests/control 2023-02-04 17:45:57.0 + @@ -1,7 +1,7 @@ Tests: smoke-test -Depends: toil, python3-wdlparse +Depends: @, python3-wdlparse Restrictions: allow-stderr, superficial Tests: run-unit-tests -Depends: toil, python3, python3-wdlparse, python3-pytest, python3-pytest-xdist, python3-mock, python3-boto3, rsync, python3-boto, python3-stubserver, python3-yaml, quilt +Depends: @, python3, python3-wdlparse, python3-pytest, python3-pytest-xdist, python3-mock, python3-boto3, rsync, python3-boto, python3-stubserver, python3-yaml, quilt Restrictions: allow-stderr, needs-internet
Bug#1054291: wget2: Please enable tests during build
Source: wget2 Version: 2.1.0-2 Severity: normal Tags: patch Dear maintainer, currently the tests don't run when building the binary packages. That is because '$(MAKE) check' is missing in debian/rules and it also needs libmicrohttpd-dev as another build-dependency to avoid the following lines when running configure: checking for libmicrohttpd... no checking for library containing MHD_start_daemon... no configure: WARNING: *** LIBMICROHTTPD was not found. Several tests will not run. checking for MHD_free... no So could you please enable the tests? In addition, libidn-dev is no longer needed as a build-dependency because wget2 prefers libidn2-dev which appears to be already a build-dependency. For your convenience, I have prepared the attached patch that addresses all of these issues and adds dh_dwz for packaging the debug information as well. Thank you in advance for considering these changes! Best regards, Thomas Uhle wget2-enable-testsuite.diff.gz Description: GNU Zip compressed data
Bug#1054290: zlib: CVE-2023-45853
Source: zlib Version: 1:1.2.13.dfsg-3 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for zlib. CVE-2023-45853[0]: | MiniZip in zlib through 1.3 has an integer overflow and resultant | heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long | filename, comment, or extra field. NOTE: MiniZip is not a supported | part of the zlib product. 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-2023-45853 https://www.cve.org/CVERecord?id=CVE-2023-45853 [1] https://github.com/madler/zlib/pull/843 [2] https://github.com/madler/zlib/commit/73331a6a0481067628f065ffe87bb1d8f787d10c Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1051888: Should Kino be removed?
Control: severity -1 normal Control: reassign -1 ftp.debian.org Control: retitle -1 RM: kino -- RoQA; RC-buggy; dead upstream; depends on gtk2 Please remove kino. It is is RC-buggy for 1.5 years and dead upstream. It depends on various legacy libs (GTK2, Glade).
Bug#754601: still a problem?
Hi victory, is this still a problem? -- regards Thomas
Bug#772822: link to mail possible
There's now a new list which includes a direct link to the DSA announcement mail and the security tracker. This can also be done for DLAs. https://www.debian.org/security/dsa.html#DSAS -- regards Thomas
Bug#1054289: rust-pleaser: CVE-2023-46277: RUSTSEC-2023-0066
Source: rust-pleaser Version: 0.5.3-2 Severity: important Tags: security upstream Forwarded: https://gitlab.com/edneville/please/-/issues/13 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for rust-pleaser. CVE-2023-46277[0]: | please (aka pleaser) through 0.5.4 allows privilege escalation | through the TIOCSTI and/or TIOCLINUX ioctl. (If both TIOCSTI and | TIOCLINUX are disabled, this cannot be exploited.) 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-2023-46277 https://www.cve.org/CVERecord?id=CVE-2023-46277 [1] https://gitlab.com/edneville/please/-/issues/13 [2] https://rustsec.org/advisories/RUSTSEC-2023-0066.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#974622: drawxtl: Please migrate to FLTK 1.3
I am uploading a NMU to DELAYED/5 in order to fix this. The debdiff is attached.diff -Nru drawxtl-5.5/debian/changelog drawxtl-5.5/debian/changelog --- drawxtl-5.5/debian/changelog2022-12-02 17:43:57.0 +0100 +++ drawxtl-5.5/debian/changelog2023-10-20 20:57:06.0 +0200 @@ -1,3 +1,10 @@ +drawxtl (5.5-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * Migrate to FLTK 1.3 (closes: #974622). + + -- Bastian Germann Fri, 20 Oct 2023 20:57:06 +0200 + drawxtl (5.5-6) unstable; urgency=medium * Team upload. diff -Nru drawxtl-5.5/debian/control drawxtl-5.5/debian/control --- drawxtl-5.5/debian/control 2022-12-02 17:16:42.0 +0100 +++ drawxtl-5.5/debian/control 2023-10-20 20:56:18.0 +0200 @@ -6,7 +6,7 @@ Build-Depends: debhelper-compat (= 12), dpkg-dev (>= 1.16.1), freeglut3-dev, - libfltk1.1-dev | libfltk-dev, + libfltk1.3-dev | libfltk-dev, libgl1-mesa-dev, libgl2ps-dev, libglu1-mesa-dev,
Bug#1054288: RM: xscorch -- RoQA; RC-buggy; depends on gtk2
Source: xscorch Version: 0.2.1-1+nmu6 Please remove xscorch from Debian. It is RC-buggy and nobody noticed that it is unusable, so it is probably not used anymore. If nobody complains about it being removed, I am going to file a RM bug when it is removed from testing.
Bug#1052297:
Giving up on packaging because the package had a dependency problem that made it impossible to advance in autopkgtests. Nilson F. Silva
Bug#1037557: Thanks
A big thank you to the debian maintainers for applying this fix. It makes Plasma so much more comfortable!
Bug#1053870: CVE-2023-42118 and perceived impact
It looks to me like the default Exim config in Debian explicitly calls /usr/bin/spfquery.mail-spf-perl from the spf-tools-perl package, not the libspf2 implementation supplied by the spfquery package. Also spf-tools-perl is suggested by exim4-base, while neither spfquery nor any other packages built from libspf2 seem to be referenced by any of the exim4 packages. I seems the only way Exim users on Debian are likely to be impacted is if they've edited their configuration to call the alternative spfquery implementation instead of the suggested one, and explicitly installed that package.
Bug#1054180: openssl: FTBFS on loong64
On 2023-10-20 13:49:01 [+0800], WANG Xuerui wrote: > Hi, Hi, > This is likely upstream issue > https://github.com/openssl/openssl/issues/21340, manifesting on Debian due > to the packaged binutils not having Loongson SIMD support yet, and fixed by > upstream commit 160f48941d143cf2682df4e938ba953c96ac3c7a. > > I'd suggest including the upstream patch so we don't have to touch anywhere > else. So submitting patches for projects before having the upstream in the building tools. Nobody can build this then. What about uploading a custom binutils with the needed support to ports until it is merged upstream? Sebastian
Bug#1053935: www.debian.org: outdated debian-cd, debian-archive, debian-ports mirror lists
Control: tags -1 + moreinfo On Sun, 2023-10-15 at 00:14 +0900, Jing Luo wrote: > The debian-cd [1][2], debian-archive [3], debian-ports [4] mirror > lists are > outdated. They do not reflect Mirrors.masterlist.in [5]. > Related bug report: #1034832 > [...] > [1] https://www.debian.org/CD/http-ftp/ > [2] https://www.debian.org/CD/mirroring/rsync-mirrors > [3] https://www.debian.org/distrib/archive > [4] https://www.ports.debian.org/mirrors > [5] > https://salsa.debian.org/mirror-team/masterlist/-/blob/master/Mirrors.masterlist.in > Note that Mirrors.masterlist.in is not used verbatim by any part of the website. Rather, the Mirror Team's status monitoring tools (see e.g. https://mirror-master.debian.org/status/mirror-status.html ) generate a filtered list containing those mirrors which are considered to be currently "good enough" (i.e. have managed to stay up-to-date for long enough), so not all mirrors in the .in file will appear in the results. I haven't checked the ports list, but the debian-cd and debian-archive lists being published on the web pages certainly appear to match those included in the generated version of Mirrors.masterlist. Can you point to specific examples that you believe should be included in each, but are not? Regards, Adam
Bug#1054286: bookworm-pu: package python-cogent/2023.2.12a1+dfsg-2+deb12u1
Sorry, forgot the debdiff. Here it is.
Thanks.diff -Nru python-cogent-2023.2.12a1+dfsg/debian/changelog
python-cogent-2023.2.12a1+dfsg/debian/changelog
--- python-cogent-2023.2.12a1+dfsg/debian/changelog 2023-02-24
14:18:01.0 +0100
+++ python-cogent-2023.2.12a1+dfsg/debian/changelog 2023-10-20
19:04:00.0 +0200
@@ -1,3 +1,11 @@
+python-cogent (2023.2.12a1+dfsg-2+deb12u1) bookworm; urgency=medium
+
+ * Team upload.
+ * Update fix-build-on-single-cpu-systems.patch to skip
+"test_write_db_parallel" again. Closes: #1030885.
+
+ -- Santiago Vila Fri, 20 Oct 2023 19:04:00 +0200
+
python-cogent (2023.2.12a1+dfsg-2) unstable; urgency=medium
* Restrict to 64 bit architectures
diff -Nru
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build-on-single-cpu-systems.patch
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build-on-single-cpu-systems.patch
---
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build-on-single-cpu-systems.patch
2023-02-24 14:18:01.0 +0100
+++
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build-on-single-cpu-systems.patch
2023-10-20 19:03:12.0 +0200
@@ -1,11 +1,11 @@
-Author:: Santiago Vila
-Last-Upate: Wed, 8 Feb 2023 19:40:13 +0100
+Author: Santiago Vila
+Last-Update: 2023-10-20
Bug-Debian: https://bugs.debian.org/1030885
Description: Skip tests that are failing on single-cpu systems
--- a/tests/test_app/test_evo.py
+++ b/tests/test_app/test_evo.py
-@@ -2,7 +2,7 @@ import pathlib
+@@ -2,7 +2,7 @@
from os.path import dirname, join
from tempfile import TemporaryDirectory
@@ -14,7 +14,7 @@
from unittest.mock import MagicMock
from numpy.testing import assert_allclose, assert_raises
-@@ -854,6 +854,7 @@ class TestBootstrap(TestCase):
+@@ -854,6 +854,7 @@
# correct message being relayed
self.assertTrue("ValueError: '-' at" in result.message)
@@ -24,7 +24,7 @@
aln = load_aligned_seqs(join(data_dir, "brca1.fasta"), moltype="dna")
--- a/tests/test_util/test_parallel.py
+++ b/tests/test_util/test_parallel.py
-@@ -2,7 +2,7 @@ import multiprocessing
+@@ -2,7 +2,7 @@
import sys
import time
@@ -33,7 +33,7 @@
import numpy
-@@ -35,6 +35,7 @@ def check_is_master_process(n):
+@@ -35,6 +35,7 @@
class ParallelTests(TestCase):
@@ -41,7 +41,7 @@
def test_create_processes(self):
"""Procressor pool should create multiple distingue processes"""
max_worker_count = multiprocessing.cpu_count() - 1
-@@ -45,6 +46,7 @@ class ParallelTests(TestCase):
+@@ -45,6 +46,7 @@
self.assertEqual(sorted(list(result_values)), index)
self.assertEqual(len(set(result_processes)), max_worker_count)
@@ -49,7 +49,7 @@
def test_random_seeding(self):
"""Random seed should be set every function call"""
# On Windows process ids are not guaranteed to be
sequential(1,2,3,4...)
-@@ -56,6 +58,7 @@ class ParallelTests(TestCase):
+@@ -56,6 +58,7 @@
self.assertEqual(result1[0], result2[0])
self.assertNotEqual(result1, result2)
@@ -57,3 +57,21 @@
@skipIf(sys.version_info[1] < 7, "method exclusive to Python 3.7 and
above")
def test_is_master_process(self):
"""
+--- a/tests/test_app/test_io_new.py
b/tests/test_app/test_io_new.py
+@@ -6,6 +6,7 @@
+ import pickle
+
+ from pathlib import Path
++from unittest import skip
+
+ import numpy
+ import pytest
+@@ -479,6 +480,7 @@
+ assert isinstance(writer.data_store.summary_not_completed, Table)
+
+
++@skip("Does not work on single-cpu systems")
+ def test_write_db_parallel(tmp_dir, fasta_dir):
+ """writing with overwrite in parallel should reset db"""
+ dstore = open_data_store(fasta_dir, suffix="fasta")
Bug#1054287: bookworm-pu: package devscripts/2.23.4+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: devscri...@packages.debian.org
Control: affects -1 + src:devscripts
[ Reason ]
`dch --bpo` & `dch --stable` still use bullseye in 2.23.4.
Now that bookworm is releases it should be used instead.
[ Impact ]
Needs to manually change the version and codename to correct the changelog.
[ Tests ]
Package test suite.
[ Risks ]
Low, only the commit for debchange was cherry-picked.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
The gbp.conf & Vcs-Git changes are required to let git-buildpackage and
debcheckout use the correct branch.
The debchange changes are cherry-picked from 2.23.5 which is in testing for a
while now.
[ Other info ]
N/A
Kind Regards,
Bas
diff -Nru devscripts-2.23.4/debian/changelog
devscripts-2.23.4+deb12u1/debian/changelog
--- devscripts-2.23.4/debian/changelog 2023-04-05 12:40:28.0 +0200
+++ devscripts-2.23.4+deb12u1/debian/changelog 2023-10-20 18:54:42.0
+0200
@@ -1,3 +1,16 @@
+devscripts (2.23.4+deb12u1) bookworm; urgency=medium
+
+ * Team upload.
+
+ [ Bas Couwenberg ]
+ * Update branch in gbp.conf & Vcs-Git URL.
+
+ [ Benjamin Drung ]
+ * debchange: Update to current Debian distributions
+(closes: #1037336, #1038389, #1043021)
+
+ -- Bas Couwenberg Fri, 20 Oct 2023 18:54:42 +0200
+
devscripts (2.23.4) unstable; urgency=medium
[ Johannes Schauer Marin Rodrigues ]
diff -Nru devscripts-2.23.4/debian/control
devscripts-2.23.4+deb12u1/debian/control
--- devscripts-2.23.4/debian/control2023-04-05 12:36:46.0 +0200
+++ devscripts-2.23.4+deb12u1/debian/control2023-10-20 18:54:42.0
+0200
@@ -66,7 +66,7 @@
Standards-Version: 4.6.2
Rules-Requires-Root: no
Vcs-Browser: https://salsa.debian.org/debian/devscripts
-Vcs-Git: https://salsa.debian.org/debian/devscripts.git
+Vcs-Git: https://salsa.debian.org/debian/devscripts.git -b bookworm
Package: devscripts
Architecture: any
diff -Nru devscripts-2.23.4/debian/gbp.conf
devscripts-2.23.4+deb12u1/debian/gbp.conf
--- devscripts-2.23.4/debian/gbp.conf 2022-06-18 18:14:16.0 +0200
+++ devscripts-2.23.4+deb12u1/debian/gbp.conf 2023-10-20 18:54:42.0
+0200
@@ -1,2 +1,3 @@
[DEFAULT]
debian-tag = v%(version)s
+debian-branch = bookworm
diff -Nru devscripts-2.23.4/scripts/debchange.bash_completion
devscripts-2.23.4+deb12u1/scripts/debchange.bash_completion
--- devscripts-2.23.4/scripts/debchange.bash_completion 2022-06-18
18:14:15.0 +0200
+++ devscripts-2.23.4+deb12u1/scripts/debchange.bash_completion 2023-10-20
18:54:42.0 +0200
@@ -25,11 +25,11 @@
#--
#FIXME: I don't want hard-coding codename...
#--
-oldstable_codename='squeeze'
-stable_codename='wheezy'
-testing_codename='jessie'
+oldstable_codename='bullseye'
+stable_codename='bookworm'
+testing_codename='trixie'
-lts='squeeze-lts'
+lts='buster-lts'
distro="oldstable-security oldstable-proposed-updates\
"$oldstable_codename"-security\
diff -Nru devscripts-2.23.4/scripts/debchange.pl
devscripts-2.23.4+deb12u1/scripts/debchange.pl
--- devscripts-2.23.4/scripts/debchange.pl 2023-04-03 01:03:09.0
+0200
+++ devscripts-2.23.4+deb12u1/scripts/debchange.pl 2023-10-20
18:54:42.0 +0200
@@ -163,7 +163,7 @@
distribution name
--bpo
Increment the Debian release number for a backports upload
- to "bullseye-backports"
+ to "bookworm-backports"
--stable
Increment the Debian release number for a stable upload.
-l, --local
@@ -507,7 +507,7 @@
if (defined $opt_D) {
if ($vendor eq 'Debian') {
unless ($opt_D
-=~
/^(experimental|unstable|sid|UNRELEASED|((old){0,2}stable|testing|wheezy|jessie|stretch|buster|bullseye)(-proposed-updates|-security)?|proposed-updates)$/
+=~
/^(experimental|unstable|sid|UNRELEASED|((old){0,2}stable|testing|buster|bullseye|bookworm|trixie)(-proposed-updates|-security)?|proposed-updates)$/
) {
my $deb_info = get_debian_distro_info();
my ($oldstable_backports, $stable_backports) = ("", "");
@@ -530,9 +530,9 @@
if $oldstable_backports;
warn "$progname warning: Recognised distributions are: \n"
. "experimental, unstable, testing, stable, oldstable,
oldoldstable,\n"
- .
"{bullseye,buster,stretch,jessie,wheezy}-proposed-updates,\n"
+ . "{trixie,bookworm,bullseye,buster}-proposed-updates,\n"
.
Bug#1054286: bookworm-pu: package python-cogent/2023.2.12a1+dfsg-2+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: python-cog...@packages.debian.org, sanv...@debian.org Control: affects -1 + src:python-cogent [ Reason ] This upload fixes #1030885. FTBFS on single-CPU systems. [ Impact ] Users who try to build the package from source on a single-cpu system will see that the build fails unexpectedly. [ Tests ] I've tested that the fixed package builds ok on a single-cpu system. [ Risks ] Risk is minimal because the package builds the same. The only difference is that a test which required more than one cpu to work is now disabled. [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] The only change has been to disable a test in the test suite. [ Other info ] I'm going to upload the package shortly after submitting this report.
Bug#1054285: libunwind: package new upstream version 1.7.2
Source: libunwind X-Debbugs-Cc: Noah Meyerhans Severity: important Affects: src:dovecot Dear Maintainer, please consider packaging the newest upstream version 1.7.2 (released in July). Due to the outdated version currently in sid dovecot FTBFS on arm64. With the recent addition of the default hardening flag -mbranch-protection=standard backtraces do not longer contain the actual stack trace. A test rebuild against libunwind 1.7.2 solved this issue.
Bug#1054263: faicd64-large_6.0.3.iso "Cannot find grub.cfg"
Thank you Will try your suggestionAs I am just experimenting i will just play around with this. Thannk you again Suresh On Friday, October 20, 2023 at 11:15:28 PM GMT+8, Thomas Lange wrote: Thanks for the screenshots. I found the problem. It only occurs in an UEFI environment. If you boot in an EFI environment and your hostname is faiserver, then the FAI class FAISERVER is defined. In package_config/FAISERVER the package grub-pc is listed, which conflicts with grub-efi. That's why no grub is installed and your host cannot boot. Since you cannot edit the files on the ISO, you can only enter the grub menu (pressing e) and remove the part hostname=faiserver But then some other things may be missing. -- regards Thomas
Bug#1054284: xscorch: Segmentation fault
Source: xscorch Severity: grave Version: 0.2.1-1+nmu6 Running xscorch on sid/i386 gives the following segfault, preventing the program from starting: #0 0x00441792 in shashlist_insert_by_int (list=0x4c84c0, data=0x4cf950, class=2, key=1) at shashlist.c:202 #1 0x00411fec in sc_registry_add_by_int (registry=0x4c84b0, data=0x4cf950, class=2, key=1) at sregistry.c:101 #2 0x0041797b in _sc_accessory_read_item (ac=0x4cdd90, reader=0x4cdd10, item=0x4ccca0) at saddconf.c:137 #3 0x004182fe in sc_addconf_append_file (type=SC_ADDCONF_ACCESSORIES, filename=0x449ec0 "/usr/share/games/xscorch//accessories.def", container=0x4cdd90) at saddconf.c:458 #4 0x004174e0 in sc_accessory_config_create (c=0x4be840) at saccessory.c:366 #5 0x00406502 in sc_config_new (argc=0xb120, argv=0xb124) at sconfig.c:186 #6 0x00406048 in main (argc=, argv=) at xscorch.c:86
Bug#1054267: RM: fltk1.1 -- RoQA; leaf library
Am 20.10.23 um 18:22 schrieb Aaron M. Ucko: Thanks! To confirm, I don't need to do anything active here, just leave this bug open at RC severity and reencourage drawxtl to migrate? You can also file a RM bug yourself, which would be better from a process perspective. I have only announced filing it in case nobody acts on the request.
Bug#851042: molds: FTBFS: liblapacke.so: undefined reference to `sgemqr_'
El 20/10/23 a las 17:19, Graham Inggs escribió: On Wed, 18 Oct 2023 at 00:27, Santiago Vila wrote: OTOH, if this bug is being kept open to track something different (what Graham Inggs called "a recurring problem" in a previous message), maybe it would make sense to retitle at least. It seems a similar problem happened in #897488 [1] in May 2018. Unfortunately, that was before Adrian tagged this bug FTBFS, and molds was removed from testing for eight months unnecessarily. AFAIK it is the severity of the bug (serious in this case) what triggers the autoremoval from testing, not the "ftbfs" tag. And the severity was set by Lucas Nussbaum in the initial report, because he was reporting (as he usually does) "the FTBFS of the day" (so to speak). For the purposes of this bug, we can consider the report by Lucas Nussbaum as if it was the action of an automatic mechanism. He detected a package which did FTBFS at a given time, so he reported it as a serious bug. So, I don't see an easy way to improve that. Lucas is amazingly productive at reporting FTBFS bugs, so I would rather adapt to the way he report bugs than ask him to do things differently to avoid cases like this one. Thanks.
Bug#1054267: RM: fltk1.1 -- RoQA; leaf library
Bastian Germann writes: > Please remove fltk1.1. I'm on board with this removal in general. > drawxtl is the only reverse build dependency with "libfltk1.1-dev | > libfltk-dev", so it can also build with fltk1.3. IIRC, our autobuilders ignore alternative build dependencies, so the package will still need a sourceful upload; copying its migration bug accordingly. > I am going to file a RM bug when this is autoremoved from testing. Thanks! To confirm, I don't need to do anything active here, just leave this bug open at RC severity and reencourage drawxtl to migrate? -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#1054283: ITP: mmlib -- mmlib library (shared lib)
Package: wnpp Severity: wishlist Subject: ITP: mmlib -- mmlib library (shared lib) Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: mmlib Version : 1.4.2 Upstream Author : MindMaze SA * URL : https://github.com/mmlabs-mindmaze/mmlib * License : Apache-2.0 Programming Lang: C Description : mmlib library (shared lib) mmlib is the general purpose library providing helper functions to other module. It provides a cross-platform OS abstaction layer as well as facilities like logging or error reporting. . This package contains the shared library Remark: This package is maintained by Debian Med Packaging Team at https://salsa.debian.org/med-team/mmlib
Bug#1038389: dch bookworm patch
This is wrong. dch --bpo in bookworm should create bullseye-backport, exactly as it does. dch --bpo in trixie should create bookworm-backport, exactly as it does. /mjt
Bug#1051497: closed by Debian FTP Masters (reply to Hilmar Preusse ) (Bug#1051497: fixed in texlive-extra 2023.20231007-1)
On 20.10.2023 15:03, Al Ma wrote:
Hi,
How to find out the NewTX version shipped with Debian
texlive-fonts-extra? Running locate newtx | xargs grep -r "1\.726"
returns nothing from the system-wide directories.
(Running tlmgr info newtx as a normal user yields no results, and I
don't know whether running this command as root would break anything.)
>
You may install (and use) apt-file to find out, which files are which
package. The newtx is still in texlive-extra-fonts and it is:
/usr/share/texlive/texmf-dist/tex/latex/newtx/newtx.sty
\NeedsTeXFormat{LaTeX2e}
%Package to simplify loading of newtxmath with a text font family such
as newtxtext for all latex engines, or for newtxtext and an otf math
package.
\def\fileversion{1.724}
\def\filedate{2023/08/20}
\ProvidesPackage{newtx}[%
H.
--
sigfault
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1040901: Upcoming changes to Debian Linux kernel packages
[ Removing some lists ] On Sat, Oct 07, 2023 at 04:53:33PM +0200, Bastian Blank wrote: > > ## Image packages contains more version info > > > > Example: linux-image-6.5.3-cloud-arm64 > > > It will not longer be possible to reliably derive the package name from > > kernel release (see above), as both values are not really related > > anymore. > What should work: We define a new control field. It contains both the > kernel name and a version prefix. Or would it be easier to re-use normal dependency resolving, like: Kernel-Provides: linux (>> 6.6.1~), linux (<< 6.6.1.) This would allow full flexibility and re-uses existing code to check such definitions. Regards, Bastian -- Women professionals do tend to over-compensate. -- Dr. Elizabeth Dehaver, "Where No Man Has Gone Before", stardate 1312.9.
Bug#1031192: toil: FTBFS (The job JobClass is requesting 2.0 cores)
Am Fri, Oct 20, 2023 at 04:14:16PM +0200 schrieb Santiago Vila: > I'd like to fix this in bookworm as well (with a "team upload"). > > (Unless, of course, you tell me that you prefer to > take care of it yourself). Please, pretty please care for it. ;-) Thanks a lot Andreas. -- http://fam-tille.de
Bug#1049836: closed by Debian FTP Masters (reply to Benjamin Drung ) (Bug#1049836: fixed in multiprocess 0.70.15-1)
Thanks Benjamin! Best wishes, Julian On Fri, Oct 20, 2023 at 11:27:03AM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the python3-multiprocess package: > > #1049836: Update to newer upstream (>= 0.70.15) to allow python3-pathos to > build > > It has been closed by Debian FTP Masters > (reply to Benjamin Drung ). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters > (reply to Benjamin Drung > ) by > replying to this email. > > > -- > 1049836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049836 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Date: Fri, 20 Oct 2023 11:22:18 + > From: Debian FTP Masters > Subject: Bug#1049836: fixed in multiprocess 0.70.15-1 > To: 1049836-cl...@bugs.debian.org > > Source: multiprocess > Source-Version: 0.70.15-1 > Done: Benjamin Drung > > We believe that the bug you reported is fixed in the latest version of > multiprocess, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 1049...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Benjamin Drung (supplier of updated multiprocess package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Fri, 20 Oct 2023 12:48:41 +0200 > Source: multiprocess > Built-For-Profiles: noudeb > Architecture: source > Version: 0.70.15-1 > Distribution: unstable > Urgency: medium > Maintainer: Sandro Tosi > Changed-By: Benjamin Drung > Closes: 1049836 > Changes: > multiprocess (0.70.15-1) unstable; urgency=medium > . >* Team upload. > . >[ Sandro Tosi ] >* New upstream release (Closes: #1049836) >* debian/copyright > - extend packaging copyright years >* debian/control > - bump Standards-Version to 4.6.2.0 (no changes needed) > . >[ Benjamin Drung ] >* Bump required python3-dill version to >= 0.3.7 >* Switch to debhelper 13 >* Set Rules-Requires-Root >* Remove generated */multiprocess/__info__.py files on clean > Checksums-Sha1: > 42923d027c5f974181a2e657f119c3929b779b0c 2081 multiprocess_0.70.15-1.dsc > b5198d2f28a918193aeb6a19f422da4a18c2d0a9 1928413 > multiprocess_0.70.15.orig.tar.gz > 0fb9c7976b031d728a7b95c808dbd771bfe16a5f 2992 > multiprocess_0.70.15-1.debian.tar.xz > d2e48053288f9187f396a1b905187c486b56c009 7665 > multiprocess_0.70.15-1_source.buildinfo > Checksums-Sha256: > 6ec5dc7ca53052557677093fcc0cabd6a3c123a8e2230ae51b28053a9d38ac2a 2081 > multiprocess_0.70.15-1.dsc > 03f632949a1c552c593735faf3a45cd4d0fa83a8b44cfca6a98d5ffc2f4e1930 1928413 > multiprocess_0.70.15.orig.tar.gz > 71376a4060860986283486d91840a98aeb257e5a26e80841879ee2a793112257 2992 > multiprocess_0.70.15-1.debian.tar.xz > 61b4e899a9e512c5241100300b3dc31416b3f862d2a0efdf3ae1ae9f4968aee7 7665 > multiprocess_0.70.15-1_source.buildinfo > Files: > 273ec65a475e04f2c1ae2f238ddd9bc7 2081 python optional > multiprocess_0.70.15-1.dsc > 8d6eae0660554c8362fbd9fb70e87573 1928413 python optional > multiprocess_0.70.15.orig.tar.gz > e0e5bc2d7ee24558b9709a8bd8405487 2992 python optional > multiprocess_0.70.15-1.debian.tar.xz > dc5241a3fa11d9d7bb67cdec833a7c8c 7665 python optional > multiprocess_0.70.15-1_source.buildinfo > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmUyXN8ACgkQFZ61xO/I > d0yigw//ZHUsLpO75MTMX9X3t7SV/oLt0AZw909RkdzVTKlXWBwpgGC5Nh0fQEQQ > zBlSeW/APg4gD7L+UL57xnJDLRWZod/jJbb7RQNlrh7ZqDyYevxZO8jG+74WMo2i > C5ljHPqi+4ckaxQLTuEtLYA88mV8IiPaL/NgRNvrTD+J3O3GIp7KKwlsHz+5pIFs > 7jznNQgxyfxNjHMgaqzgX7hLV42Onk01hUE8mGqxnxwoOB+0iBzcCHn55qA13uVm > 7Umjt0LaUitZWcmZurA03ad376DU9sui369yeb8/QSICEEAMaBDtCMbskduXWzPt > CY8dMMltt74YcSLL9LJlslJjmgeOkm/Lkd63z7PrwYnLyBP3E+iWjdQPphatqUbK > iyKgV3K6g/zxfIkQk2A73nFtjcQwCUdzUH3bUF0Kx2u0wKGy185VVGbEoTLF8kyx > fTmhjSoHTxtE9ktQMLc1IOQ82qbxqu+bjdl+jDUOh716NbRQemKu9VRgIdvRLEL7 > TXWfZphtZdgbG8yUYVJv0xK9YozgXJAQFll24KiEuhjCBu3SQOG7PzQqnUbKj3/7 > HgxQe+y51bfTkh+fEd69RQzjv95ge36cG3IfugjlJW/+vvJarCBUGo95WpVY7sOG > 42FmfNsOMCWRALubvPomR4yPA68HYxAk2viqOpA35QJjRH/zm/w= > =5svr > -END PGP SIGNATURE- > Date: Wed, 16 Aug 2023 09:29:12 +0100 > From: Julian Gilbey > Subject: Update to newer upstream (>= 0.70.15) to allow python3-pathos to > build > To: Debian Bug Tracking System > > Package: python3-multiprocess >
Bug#851042: molds: FTBFS: liblapacke.so: undefined reference to `sgemqr_'
On Wed, 18 Oct 2023 at 00:27, Santiago Vila wrote: > OTOH, if this bug is being kept open to track something > different (what Graham Inggs called "a recurring problem" > in a previous message), maybe it would make sense to > retitle at least. It seems a similar problem happened in #897488 [1] in May 2018. Unfortunately, that was before Adrian tagged this bug FTBFS, and molds was removed from testing for eight months unnecessarily. [1] https://bugs.debian.org/897488
Bug#1054263: faicd64-large_6.0.3.iso "Cannot find grub.cfg"
Thanks for the screenshots. I found the problem. It only occurs in an UEFI environment. If you boot in an EFI environment and your hostname is faiserver, then the FAI class FAISERVER is defined. In package_config/FAISERVER the package grub-pc is listed, which conflicts with grub-efi. That's why no grub is installed and your host cannot boot. Since you cannot edit the files on the ISO, you can only enter the grub menu (pressing e) and remove the part hostname=faiserver But then some other things may be missing. -- regards Thomas
Bug#1053873: cronie: Crond with high load after 19-01-2038
Thank you for reporting this bug! Probably cron_sleep is wrong. The actual sleep() is never called after 2038 cron_sleep was recently updated to address a different issue, but it may apply to your bug. Would you try testing cronie with the changes in this commit [1] applied? Also, this bug has been forwarded upstream if you would like to contact the upstream maintainer directly about this issue. [1] https://github.com/cronie-crond/cronie/commit/78e634967d6886339be57854f0e11c6ab1fb73cd Thank you, -- Lance Lin GPG Fingerprint: 4A31 DB5A 1EE4 096C 8739 9880 9036 4929 4C33 F9B7 OpenPGP_0x903649294C33F9B7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1001045: libconfig-model-dpkg-perl: scan-copyright reports empty license
On Sat, 17 Jun 2023 18:26:12 +0200 Dominique Dumont wrote: > Then I would suggest to override the license information reported by licensecheck. > > For details, please see > > https://github.com/dod38fr/config-model/wiki/Updating-debian-copyright-file-with-cme#filling-missing-information This is not a bug on libconfig-model-dpkg-perl, closing.
Bug#1019202: dh-make-elpa: crashes with: Can't locate object method "gecos"
Hi Richard, Чт 19 окт 2023 @ 22:42 Richard Lewis : > On Mon, 16 Oct 2023 at 09:00, Lev Lamberov wrote: >> Вс 15 окт 2023 @ 19:37 Richard Lewis : >> > On Mon, 05 Sep 2022 19:44:27 -0300 David Bremner >> > wrote: >> >> Lev Lamberov writes: > >> > I also see this bug in bookwork: dh-make-elpa doesnt work at all >> > unless DEBFULLNAME (and maybe DEBEMAIL) is set. > >> > I could send a patch to mention these variables in the man-page > >> That would be great. > > It turned out that i could do even better! > > Have fixed the whole bug, and improved the detection of both name and > email address. > I've also added some tests, and refreshed the lintian overrides and > standards-version > > MR is here > https://salsa.debian.org/emacsen-team/dh-make-elpa/-/merge_requests/3 Cool! Thanks! I'll take a look into your MR in the coming days. Cheers! Lev
Bug#1054150: surf: no longer display web pages after webkitgtk upgrades
On Wed, Oct 18, 2023 at 05:06:16PM +0900, Dominique Martinet wrote: > After upgrading my system to the latest security updates surf no > longer displays anything. I had a look at this, the problem is caused by Surf's AppArmor configuration. I can make it run on my computer with something like this added to /etc/apparmor.d/usr.bin.surf, but your mileage may vary: /sys/devices/virtual/dmi/id/chassis_type r, /etc/glvnd/egl_vendor.d/ r, /etc/glvnd/egl_vendor.d/** r, /usr/share/glvnd/egl_vendor.d/ r, /usr/share/glvnd/egl_vendor.d/** r, /usr/share/libdrm/* r, I think that Surf's AppArmor profile is just too restrictive for a program that has so many dependencies. Berto
Bug#1031192: toil: FTBFS (The job JobClass is requesting 2.0 cores)
Hello. I'd like to fix this in bookworm as well (with a "team upload"). (Unless, of course, you tell me that you prefer to take care of it yourself). Thanks.
Bug#717778: checkinstall: mkdir -p fails (fstrans broken again?)
Is the package no longer maintained? If it is, it should be removed from the repo. It is 2023, and checkinstall is still broken. Thanks, Siddh On Sat, 02 Jul 2022 02:18:35 + Geoffrey Hausheer wrote: > Package: checkinstall > Version: 1.6.2+git20170426.d24a630-2 > Followup-For: Bug #717778 > X-Debbugs-Cc: debianbug...@pblue.org > > It appears that the root of this issue may be in instw_setpathrel > Specifically, the 'stat' command that is used to get the length of a symlink > should > be 'lstat' instead. > > Here is a 1 line-patch that addressed the issue for me: > > --- a/installwatch/installwatch.c > +++ b/installwatch/installwatch.c > @@ -1691,7 +1691,7 @@ > if ( dirfd == AT_FDCWD ) return instw_setpath(instw, relpath); > > snprintf(proc_path, PROC_PATH_LEN, "/proc/self/fd/%d", dirfd); > - if(true_stat(proc_path, ) == -1) > + if(true_lstat(proc_path, ) == -1) > goto out; > if(!(newpath = malloc(s.st_size+strlen(relpath)+2))) > goto out; > > > > -- System Information: > Debian Release: 11.3 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, > 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.10.67-zfs (SMP w/4 CPU threads) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /bin/dash > Init: unable to detect > > Versions of packages checkinstall depends on: > ii dpkg-dev1.20.10 > ii file1:5.39-3 > ii libc6 2.31-13+deb11u3 > ii sensible-utils 0.0.14 > > Versions of packages checkinstall recommends: > ii make 4.3-4.1 > > Versions of packages checkinstall suggests: > ii gettext 0.21-4 > > -- Configuration Files: > /etc/checkinstallrc changed [not included] > > -- no debconf information > >
Bug#1054259: [Pkg-javascript-devel] Bug#1054259: Bug#1054259: nodejs: cannot bootstrap nodejs
Quoting Jérémy Lal (2023-10-20 10:42:58) > Le ven. 20 oct. 2023 à 10:33, Christopher Obbard > a écrit : > > > Control: retitle -1 nodejs: cannot bootstrap nodejs > > > > Hi Jérémy, > > > > On Fri, 2023-10-20 at 02:25 +0200, Jérémy Lal wrote: > > > https://salsa.debian.org/js-team/nodejs/-/blob/master- > > > 18.x/debian/README.source > > > > Thanks for your suggestion. I actually did follow those instructions to > > attempt to build nodejs 18.13.0+dfsg1-1. > > > > For nodejs 16.15.1+dfsg-1 following those instructions bootstraps the > > package > > just fine, I think because the "externalized builtin" JS files are present > > in > > the packaging. > > > > I have attached the three patches to debian/ to get _something_ bootstrap > > for > > 18x but it still fails with the error "Cannot load externalized builtin" > > when > > trying to launch bootstrapped node. > > > > Maybe the README.source isn't clear enough. > The node package built at first stage is just good enough to build the > second stage. > It is not feature-complete. Typically you can't run node REPL with it. > Once you have first stage, you install the resulting deb, and use that as a > build-dependency > to build second stage (which is a normal build). Perhaps updating that text to point the the Debian wiki page on staged builds would be a helpful hint. (on weak internet right now, so haven't checked if that is already done) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1054169: ares 132-1 fails to build on many architectures
On Wed, 18 Oct 2023 17:29:23 + Benjamin Drung wrote: > On Wed, 2023-10-18 at 16:45 +, Tobias Frost wrote: > > Control: severity -1 important > > > > (this is not RC as it never has been built on those architectures before) > > Note: ares 126-3 has been built for armhf, riscv64, and s390x on Ubuntu > in the past: https://launchpad.net/ubuntu/+source/ares/126-3 There was an deliberate choice in Debian to remove those archs: #1042895 -- tobi
Bug#1054282: buku: add zsh completion file
Package: buku Version: 4.7+ds-1 Severity: normal Dear Maintainer, please add the zsh completion file, just like the bash completion file. It can be found on https://github.com/jarun/buku/blob/master/auto-completion/zsh/_buku and should be placed into /usr/share/zsh/vendor-completions/ Thanks.
Bug#1037376: gnome-chemistry-utils: build-depends on transitional package libgdk-pixbuf2.0-dev
I am uploading a NMU to fix this. Please find the debdiff attached.diff -Nru gnome-chemistry-utils-0.14.17/debian/changelog gnome-chemistry-utils-0.14.17/debian/changelog --- gnome-chemistry-utils-0.14.17/debian/changelog 2021-12-04 14:51:53.0 + +++ gnome-chemistry-utils-0.14.17/debian/changelog 2023-10-20 12:17:45.0 + @@ -1,3 +1,12 @@ +gnome-chemistry-utils (0.14.17-6.2) unstable; urgency=medium + + * Non-maintainer upload. + * Drop unnecessary B-D libgdk-pixbuf2.0-dev. The used parts are implied by +libgtk-3-dev. (Closes: #1037376) + * Drop unnecessary libgtkglext1-dev. (Closes: #1054277) + + -- Bastian Germann Fri, 20 Oct 2023 12:17:45 + + gnome-chemistry-utils (0.14.17-6.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru gnome-chemistry-utils-0.14.17/debian/control gnome-chemistry-utils-0.14.17/debian/control --- gnome-chemistry-utils-0.14.17/debian/control2021-03-08 14:06:12.0 + +++ gnome-chemistry-utils-0.14.17/debian/control2023-10-20 12:16:39.0 + @@ -14,13 +14,11 @@ gnumeric (>= 1.11.6), intltool (>= 0.40.6), libcairo2-dev (>= 1.6.0), - libgdk-pixbuf2.0-dev (>= 2.22.0), libglib2.0-dev (>= 2.36.0), libglu1-mesa-dev, libgoffice-0.10-dev (>= 0.10.12), libgsf-1-dev (>= 1.14.9), libgtk-3-dev (>= 3.0.0), - libgtkglext1-dev (>= 1.0.0), libopenbabel-dev (>= 3.0.0), libosmesa6-dev, libtool (>= 2.2.6),
Bug#834129: pgadmin4 adopter wanted
This RFP has languished for almost 3 years now and was opened almost 7 years ago. The pgadmin4 package provided upstream works without issue on Trixie. Is the delay licencing-related or is there not interest in carrying this package in Debian's repos?
Bug#1054281: ITP: ruby-maven-tools
Package: wnpp Severity: wishlist Owner: Jérôme Charaoui Package name : ruby-maven-tools Version : 1.2.1 Upstream author : Christian Meier URL : https://github.com/jruby/maven-tools License : Expat Programming Lang : Ruby Description : helpers for maven related tasks adds versions conversion from rubygems to maven and vice versa, ruby DSL for POM (Project Object Model from maven), pom generators, etc This is part of an effort to improve the JRuby build chain in Debian. Thanks, -- Jerome
Bug#1054280: mirror submission for mirror.hoobly.com
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirror.hoobly.com Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd-amd64 i386 mips mips64el mipsel powerpc ppc64el riscv64 s390x Archive-http: /debian/ Maintainer: Peter Grigor Country: US United States Sponsor: Hoobly Classifieds https://www.hoobly.com Comment: Hi there, please let me know if the mirror is in order. :) Trace Url: http://mirror.hoobly.com/debian/project/trace/ Trace Url: http://mirror.hoobly.com/debian/project/trace/ftp-master.debian.org Trace Url: http://mirror.hoobly.com/debian/project/trace/mirror.hoobly.com
Bug#1054279: [INTL:sv] Swedish strings for mini-buildd debconf
package: mini-buildd severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. -- brother mini-buildd.sv.po.gz Description: application/gzip
Bug#1054278: unifont-bin: Consider dropping unifont-viewer and therefore the dependency on unmaintained libwx-perl
Package: unifont-bin Version: 1:15.1.01-1 Severity: wishlist Tags: d-i X-Debbugs-Cc: Scott Talbert , debian-b...@lists.debian.org unifont-bin depends on libwx-perl, which as mentioned in #1054146 is unmaintained upstream and only minimally maintained in Debian. debian-installer build-depends on unifont-bin, which brings libwx-perl into the critical path for being able to build d-i. Scott Talbert wrote: > it probably would be good to see if that dependency could be removed As far as I can see, removing the unifont-viewer GUI tool (and its man page, etc.) would be enough to be able to drop the libwx-perl dependency. I suspect that unifont-viewer is not considered to be core functionality for unifont-bin? smcv
Bug#1051497: closed by Debian FTP Masters (reply to Hilmar Preusse ) (Bug#1051497: fixed in texlive-extra 2023.20231007-1)
Thank you! Now all the mentioned bugs seem to be repaired. How to find out the NewTX version shipped with Debian texlive-fonts-extra? Running locate newtx | xargs grep -r "1\.726" returns nothing from the system-wide directories. (Running tlmgr info newtx as a normal user yields no results, and I don't know whether running this command as root would break anything.)
Bug#1052064: libelogind0: need to be updated to ≥254
On Wed, 18 Oct 2023 11:43:59 +0200 Mathieu Mirmont wrote: > On Sat, Sep 16, 2023 at 09:55:25PM +0200, Adam Borowski wrote: > > Package: libelogind0 > > Version: 246.10-1debian1 > > Severity: normal > > > > Hi! > > While this problem hasn't hit amd64 yet due to procps FTBFSing, on riscv64 > > it already requires symbols from libsystemd0 (>= 254~rc1). So it does on > > most other architectures. And we can expect amd64+i386 to join soon. > > > > Thus: please update libelogind to provide systemd 254 symbols, quite > > urgently (procps being a Priority: important package). > > It has now happened on amd64. Unfortunately upstream elogind is only > on version 252 so it will need to be updated first. This is a sad state of affairs as this makes all packages depending on libsystemd0 currently uninstallable. I was setting up my new machine yesterday (with openrc and sid) and even firefox or thunderbird are uninstallable because the depend on packages depending on libsystemd0. imho this would warrant a grave bug since those are breaking changes but since the majority of users/developers have settled on systemd that's of no use. I hope consolekit2 becomes the drop-in replacement. best, -- Matthias Geiger Debian Maintainer "Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1054277: gnome-chemistry-utils: unnecessarily build-depends on libgtkglext1-dev
Source: gnome-chemistry-utils Version: 0.14.17-6 Please drop Build-Depends: libgtkglext1-dev, which is not used anymore.
Bug#1032495: (no subject)
Paride Legovini wronte on 19/10/2023:
> Luigi Baldoni wrote on 15/10/2023:
> > Same deal here, but on bookworm using systemd and the installation is some
> > 10 days old.
>
> Hello Luigi, that is likely a different issue. Can you please file a ne
> bug report, describing the problem you are facing in more detail, possibly
> providing steps to reproduce from a clean Bookworm system?
Unfortunately (or not) I couldn't reproduce it anymore, even on a live debian
VM.
For future reference, the error was:
audit[7919]: AVC apparmor="DENIED" operation="mknod" profile="kea-dhcp4"
name="/run/kea/logger_lockfile" pid=7919 comm="kea-dhcp4" requested_mask="c"
denied_mask="c" fsuid=107 ouid=107
which was fixed by this patch:
diff -udpr etc/apparmor.d.orig/usr.sbin.kea-dhcp4
etc/apparmor.d/usr.sbin.kea-dhcp4
--- etc/apparmor.d.orig/usr.sbin.kea-dhcp4 2023-10-20 13:17:59.724793546
+0200
+++ etc/apparmor.d/usr.sbin.kea-dhcp4 2023-10-20 13:18:54.981066011 +0200
@@ -27,7 +27,7 @@ profile kea-dhcp4 /usr/sbin/kea-dhcp4 {
/usr/sbin/kea-lfc Px,
owner /run/kea/kea-dhcp4.kea-dhcp4.pid w,
- owner /run/lock/kea/logger_lockfile rwk,
+ owner /run/{lock,}/kea/logger_lockfile rwk,
# Control sockets
# Before LP: #1863100, these were in /tmp. For compatibility, let's keep both
diff -udpr etc/apparmor.d.orig/usr.sbin.kea-lfc etc/apparmor.d/usr.sbin.kea-lfc
--- etc/apparmor.d.orig/usr.sbin.kea-lfc2023-10-20 13:17:59.724793546
+0200
+++ etc/apparmor.d/usr.sbin.kea-lfc 2023-10-20 13:19:04.205111517 +0200
@@ -11,7 +11,7 @@ profile kea-lfc /usr/sbin/kea-lfc {
/usr/sbin/kea-lfc mr,
owner /run/kea/logger_lockfile rwk,
- owner /run/lock/kea/logger_lockfile rw,
+ owner /run/{lock,}/kea/logger_lockfile rwk,
# Control sockets
# Before LP: #1863100, these were in /tmp. For compatibility, let's keep both
Bug#1054276: DeprecationWarning: 'cgi' is deprecated
The patch is here: https://github.com/jarun/buku/pull/605/files Greetings
Bug#1054276: /usr/bin/buku:22: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13
Package: buku Version: 4.7+ds-1 Severity: normal Dear Maintainer, when I start buku, it always prints this message first: /usr/bin/buku:22: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13 Please fix it so that this annoying message is not printed anymore. Thanks -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages buku depends on: ii python3 3.11.2-1+b1 ii python3-bs4 4.11.2-2 ii python3-certifi 2022.9.24-1 ii python3-cryptography 38.0.4-3 ii python3-html5lib 1.1-3 ii python3-urllib3 1.26.12-1 buku recommends no packages. buku suggests no packages. -- no debconf information
Bug#1054275: photocollage: please remove extraneous dependency on python3-six
Package: photocollage Version: 1.4.5-0.1 Severity: normal User: python3-...@packages.debian.org Usertags: python3-six-removal Dear Maintainer, Your package doesn't require python3-six at all. $ grep six /usr/bin/photocollage /usr/lib/python3/dist-packages/photocollage* -r $ (nothing) Please remove the extraneous dependency. Greetings https://wiki.debian.org/Python3-six-removal -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages photocollage depends on: ii gir1.2-gtk-3.03.24.38-5 ii python3 3.11.4-5+b1 ii python3-cairo 1.24.0-3 ii python3-gi-cairo 3.46.0-1 ii python3-pil 10.0.0-1 ii python3-six 1.16.0-4 photocollage recommends no packages. photocollage suggests no packages. -- no debconf information
Bug#1054274: pipewire: Sound changes volume with cracking noise
Package: pipewire Version: 0.3.82-1 Severity: important Dear Maintainer, Since my pipewire adoption, sound has many problems. I have installed -alsa, -pulse and -jack, configuring them properly (I hope). I use many sounding programs: firefox, mocp, ardour, mpv... and all fail one time or another, without giving no clue about reason. Problems can be volume changes in both stereo channels, annoying cracking on youtuve videos or podcasts, films in mpv, flac files in mocp... Pipewire is almost in 1.0 version. How can it fail so much in no many cases? I configure mocp for using alsa; firefox uses pulseaudio, I supose. Any clue about a solution to my problems? Thanks. -- David -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 pipewire depends on: ii adduser 3.137 ii init-system-helpers 1.65.2 ii libpipewire-0.3-modules 0.3.82-1 ii pipewire-bin 0.3.82-1 pipewire recommends no packages. pipewire suggests no packages. -- no debconf information
Bug#1039145: cachefilesd: ships sysv-init script without systemd unit
Note that a .service file is attached to: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053890
Bug#1020480: hunspell-be: Package the Qt WebEngine binary dictionary files from your Hunspell source
Yes, please. -- Celestia real-time space simulator: * https://celestiaproject.space * https://github.com/CelestiaProject
Bug#988592: waybar: Missing dependency for module "custom/media"
Control: tag -1 moreinfo On Sun, 16 May 2021 13:53:21 + Peymaneh Nejad wrote: > Package: waybar > Version: 0.9.5-2 > > I would get an error when using the custom mediaplayer module, a python > script at that is shipped with waybar > (resources/custom_modules/mediaplayer.py) > > Turns out the script depends on gir1.2-playerctl-2.0 to be installed. > I'm using ubuntu but it seems to me this applies for debian already. In version 0.9.18-1 a dependency to libplayerctl2 was added (indirectly) and my guess is that it solved this bug. Or otherwise since version 0.9.21. Can you test whether the version in Testing/Sid does indeed fix this bug? signature.asc Description: This is a digitally signed message part.
Bug#1054273: ITP: golang-github-checkpoint-restore-checkpointctl -- Tool to inspect Kubernetes and Podman checkpoints
Package: wnpp Severity: wishlist Owner: Reinhard Tartler * Package name: golang-github-checkpoint-restore-checkpointctl Version : 1.1.0-1 Upstream Author : * URL : https://github.com/checkpoint-restore/checkpointctl * License : Apache-2.0 Programming Lang: Go Description : Tool to inspect Kubernetes and Podman checkpoints Container engines like *Podman* and *CRI-O* have the ability to checkpoint a container. All data related to a checkpoint is collected in a checkpoint archive. With the help of this tool, checkpointctl, it is possible to display information about these checkpoint archives. This is a dependency of podman. I plan to maintain it as part of the pkg-golang team umbrella
Bug#1054272: gcc-13: Regression in SH backend results in binutils FTBFS
Source: gcc-13 Version: 13.2.0-5 Severity: normal Tags: upstream User: debian-sup...@lists.debian.org Usertags: sh4 X-Debbugs-Cc: debian-sup...@lists.debian.org Hello! There is currently a known regression in gcc-13 which causes binutils and e2fsprogs to FTBFS on sh4 [1][2]: libtool: compile: sh4-linux-gnu-gcc (...) .deps/elf64-aarch64.Tpo -c elf64-aarch64.c -fPIC -DPIC -o .libs/elf64-aarch64.o elfnn-aarch64.c: In function ‘elf64_aarch64_merge_gnu_properties’: elfnn-aarch64.c:10408: warning: ‘/<>/builddir-multi/bfd/.libs/elf64-aarch64.gcda’ profile count data file not found [-Wmissing-profile] terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Unhandled trap: 0x180 pc=0x3f9a38e0 sr=0x0001 pr=0x3f9a38d2 fpscr=0x00080004 spc=0x ssr=0x gbr=0x3f975aa0 vbr=0x sgr=0x dbr=0x delayed_pc=0x3f9a38d2 fpul=0x0064 r0=0x0004 r1=0x3fb01170 r2=0x0005 r3=0x r4=0x002e5a00 r5=0x002e5a00 r6=0x0006 r7=0x011c r8=0x3fb01164 r9=0x0518 r10=0x3f9755e0 r11=0x09bc r12=0x3fb00c58 r13=0x01766344 r14=0x01bed424 r15=0x407fb580 r16=0x r17=0x r18=0x r19=0x r20=0x r21=0x r22=0x r23=0x Testing on real hardware reveals the actual bug: root@tirpitz:..lib/ext2fs> gcc-13 -I. -I../../lib -I../../../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=$(pwd)=. -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -pthread -DHAVE_CONFIG_H -c ../../../../lib/ext2fs/rw_bitmaps.c -o rw_bitmaps.o terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc during RTL pass: sh_treg_combine2 ../../../../lib/ext2fs/rw_bitmaps.c: In function ‘read_bitmaps_range_start’: ../../../../lib/ext2fs/rw_bitmaps.c:447:1: internal compiler error: Illegal instruction 447 | } | ^ 0x29a738e0 __GI_abort ./stdlib/abort.c:107 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See for instructions. root@tirpitz:..lib/ext2fs> which has been been reported upstream [3]. The issue does not reproduce on gcc-12. This bug report has been created to raise awareness within Debian. Thanks, Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=binutils=sh4=2.41-6=1697044502=0 > [2] > https://buildd.debian.org/status/fetch.php?pkg=e2fsprogs=sh4=1.47.0-2%2Bb1=1697478803=0 > [3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111892 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1054271: ITP: golang-github-coreos-stream-metadata-go -- Go library for parsing Fedora CoreOS streams
Package: wnpp Severity: wishlist Owner: Reinhard Tartler * Package name: golang-github-coreos-stream-metadata-go Version : 0.4.3-1 Upstream Author : CoreOS * URL : https://github.com/coreos/stream-metadata-go * License : Apache-2.0 Programming Lang: Go Description : Go library for parsing Fedora CoreOS streams Go library for parsing Fedora CoreOS streams . See the Fedora CoreOS documentation (https://docs.fedoraproject.org/en- US/fedora-coreos/getting-started/) for basic information about streams. . This is a Go library which exposes API to decode streams into Go structs, as well as a convenience API to find the URL for a given stream. This package is used by podman machine. I plan to maintain it under the pkg-golang team umbrella
Bug#1054270: ITP: python-schwifty -- work with IBANs and BICs
Package: wnpp Severity: wishlist Owner: Matthias Geiger X-Debbugs-Cc: debian-de...@lists.debian.org, , werdah...@riseup.net Control: block 1013317 by -1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-schwifty Version : 2023.9.0 Upstream Contact: Martin Domke * URL : https://github.com/mdomke/schwifty * License : Expat Programming Lang: Python Description : easily work with IBANs and BICs as specified by the ISO python-schwifty is a library to work with IBANs and BICs. IBAN is the Internation Bank Account Number and BIC the Business Identifier Code. Both are used for international money transfer. This is the last library needed for banking. The packaging for it is done; it'll be maintained with the debian python team. best, werdahias -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmUyVfYVHHdlcmRhaGlh c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1FYAQAKNt1iuLovnYuOv8IV1Fy9zNs3Bp ofjjKyIE4MSyX7+d3iF2kThq0wjeVwhIDviWVkkMDYtLgGgYjNvd9X16ex6W61JC BcMJlLJzhCm4AIOCJdhbzdGt7DoipW2+MRKN26AQRe0Txi08CL70nkkfQApvV1Hm TgxJ4u9HcuRRlfV20jAqkQzVSGjU3mqv0akiCXJvzfO/7IPMoyWZ+T1JeyoA7Wuq ouqcZMiZVgLVgDY4+srBvBC4SM1NMxB143ONr2ms57fUGhJx2F40O23WnRkuQwmi ie5cQyQfGiZMqbrxIyS66ag8ICKIKOffqa50ntrW2jW4xBE6HWDfi5WcrydazrFo 72frJAkGam7XJb2jLZ+8ttRN3bw/XH/jkMmkg25LAQVcDhwZKZBolw8PTpWc8PIr UUDOiejcFjDi0RwLojkptpYRPVsiwuCs79OfM2SgXaSX8nVPyqvGXzr0lH8+1b+K DDn/vZGJY6+Nk9T8VO6H8w7JQtJfdh8jAeo0wUulcHoR7cmxZpb7XZhS34QKVLQn ETblnoeKTYB1KG+Mw7LiVtdQQommmp96+NAHzu45ODA984Ne1ZgIhGlLEReMDgUy b5SOIPIUMnVm1swIF3NYCgyIGyaUUHRJROOvAPMq7SK0q9MOx0XKzZ/j8848fprB RKlw5KFWfZY7uFJ5 =nMre -END PGP SIGNATURE-
Bug#1054269: RFP: wmenu -- wmenu is an efficient dynamic menu for Sway and wlroots based Wayland compositors
Package: wnpp Severity: wishlist X-Debbugs-Cc: team+swa...@tracker.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: wmenu Version : 0.1.4 Upstream Contact: Adnan Maolood * URL : https://sr.ht/~adnano/wmenu/ * License : MIT/X Consortium License Programming Lang: C Description : wmenu is an efficient dynamic menu for Sway and wlroots based Wayland compositors wmenu is an efficient dynamic menu for Sway and wlroots based Wayland compositors. It provides a Wayland-native dmenu replacement which maintains the look and feel of dmenu. Sway will switch to wmenu as its default menu for sway 1.9. See https://github.com/swaywm/sway/issues/7410 and the upstream merge request https://github.com/swaywm/sway/pull/7384 is already merged into master. -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZTJS7wAKCRDXblvOeH7b btWGAP9YQQCVHrsDqaYTYBo40Dr2XKz18zR548ACdUTo22aUcQD+J2CqhmbwAYce ewTUC/2hF6e3BmieYIAr2UtcR6aP7QE= =Pgy4 -END PGP SIGNATURE-
Bug#1054268: mate-applets: mate weather applet not retrieving data
Package: mate-applets Version: 1.26.1-2 Severity: important X-Debbugs-Cc: mrdowdsouthmo...@gmail.com Dear Maintainer, The Mate Weather info has stopped being retrieved sometime over the past week. I checked other sites in the United States, Ireland, and China and it does not seem to get data from any of them. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mate-applets depends on: ii gsettings-desktop-schemas 45.0-1 ii gvfs 1.52.0-1 ii libatk1.0-02.50.0-1 ii libc6 2.37-12 ii libcairo2 1.18.0-1 ii libcpupower1 6.5.3-1 ii libdbus-glib-1-2 0.112-3 ii libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-0 3.24.38-5 ii libgtop-2.0-11 2.40.0-2 ii libgucharmap-2-90-71:15.0.4-1 ii libmate-panel-applet-4-1 1.27.1-2 ii libmateweather11.26.0-1.1 ii libnl-3-2003.7.0-0.2+b1 ii libnl-genl-3-200 3.7.0-0.2+b1 ii libnotify4 0.8.2-1 ii libpango-1.0-0 1.51.0+ds-2 ii libpangocairo-1.0-01.51.0+ds-2 ii libpolkit-gobject-1-0 123-1 ii libupower-glib31.90.2-5 ii libwnck-3-043.0-3 ii libx11-6 2:1.8.7-1 ii libxml22.9.14+dfsg-1.3 ii mate-applets-common1.26.1-2 ii mate-panel 1.27.1-2 Versions of packages mate-applets recommends: ii mate-media 1.26.0-2 ii mate-polkit 1.26.1-4 ii mate-system-monitor 1.26.0-5 mate-applets suggests no packages. -- no debconf information
Bug#983290: worklog: summary prints 0.0 even when no work done
Sorry, my description of what is expected was incorrect. I think just looking at the code shows that the current code is wrong, since the first time through the loop, "seconds" is uninitialized, which is incorrect. A better set of steps to reproduce: /usr/bin/worklog ~/worklog/projects time.log Add time to a project and quit Contents of time.log: ProjectB : 1.00 seconds : finished Fri Oct 20 06:01:20 2023 -- Worklog summary begins : Fri Oct 20 06:01:16 2023 -- ProjectA : total 0.00 seconds -- Worklog summary ends : Fri Oct 20 06:01:21 2023 -- /usr/bin/worklog ~/worklog/projects time.log Quit immediately: New contents of time.log: -- Worklog summary begins : Fri Oct 20 06:01:27 2023 -- ProjectA : total 0.00 seconds -- Worklog summary ends : Fri Oct 20 06:01:28 2023 -- ProjectB isn't listed at all. What it should look like is this: Complete contents of time.log when running the aboe steps after the patch is applied: ProjectB : 1.00 seconds : finished Fri Oct 20 06:04:27 2023 -- Worklog summary begins : Fri Oct 20 06:04:24 2023 -- ProjectB : total 1.00 seconds -- Worklog summary ends : Fri Oct 20 06:04:28 2023 -- -- Worklog summary begins : Fri Oct 20 06:04:33 2023 -- ProjectB : total 1.00 seconds -- Worklog summary ends : Fri Oct 20 06:04:34 2023 --
Bug#944748: [pkg-netfilter-team] Bug#944748: nftables: no init script
On Fri, 20 Oct 2023 11:35:38 +0200 Magnus Holmgren wrote: Reminder that this bug isn't about building support for saving the currently loaded ruleset to a file and reloading it after reboot, only about adding a minimal init script that does the same job as the existing systemd unit. There wont be any sysvinit integration in this package. Sorry. rules and then saving the changes, but to facilitate integration of other packages with nftables, I think coming up with some scheme where those packages can drop configuration snippets in /etc/nftables.d, or perhaps /etc/ This should be done by other components such as firewalld. No such functions will be added to the nftables package. The nftables package will just deploy the `nft` binary plus a few skeleton ruleset and other example. I'm already regretting the systemd integration at all.
Bug#1054101: webkit2gtk: No provider of eglCreateImage found. Requires one of: EGL 15, yelp can't start
Yes! Good! libwebkit2gtk-4.0-37:amd64 (2.42.1-1~deb11u2) fixed this bug! 在 2023/10/20 14:56, Alberto Garcia 写道: I just uploaded a new version of webkit2gtk to debian-security, you'll see it soon when you do a normal apt update + upgrade. It should fix the problem, tell me if it doesn't. Berto Thanks very much! -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page:https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa:https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1027069: waybar: improve its .service file?
On 2 Jan 2023 15:59:50 +0100 Patrice Duroux wrote: > Note also that using sid: > $ weston-info > > *** Please use wayland-info instead > *** weston-info is deprecated and will be removed in a future version > > > And I think that wayland-info is part of wayland-utils(1) that is not > yet packaged, isn't it? Note that in Trixie/Sid, `weston-info` is no longer available as it has been removed from the `weston` package. The `wayland-utils` package with the `wayland-info` package is available since Bookworm (looks like they were just in time). signature.asc Description: This is a digitally signed message part.
Bug#944748: [pkg-netfilter-team] Bug#944748: nftables: no init script
On Fri, 15 Nov 2019 14:29:44 + (UTC) Thorsten Glaser wrote: > Arturo Borrero Gonzalez dixit: > > >I'm sorry, but I don't plan to work on any kind of sysvinit support for nftables. > […] > >Anyway, I'm closing the bug report as wontfix. > > Feel free to have it as wontfix, but it’s still a serious > current Policy violation and thus RC. Not fixing it will > make your package unsuitable for a stable release. Reminder that this bug isn't about building support for saving the currently loaded ruleset to a file and reloading it after reboot, only about adding a minimal init script that does the same job as the existing systemd unit. I actually like how you can actually write your rules in a fairly readable, structured format, making it easier to make changes by editing the configuration and reloading as opposed to executing commands to add or delete rules and then saving the changes, but to facilitate integration of other packages with nftables, I think coming up with some scheme where those packages can drop configuration snippets in /etc/nftables.d, or perhaps /etc/ nftables/input.d etc., could be helpful. (This would work because the include statement can be used in various places, not just at the top level, and an include statement with wildcard symbols that matches no files is no error.) This is again a whole separate issue, though. -- Magnus Holmgren Debian Developer
Bug#1054150: surf: no longer display web pages after webkitgtk upgrades
On Wed, Oct 18, 2023 at 05:06:16PM +0900, Dominique Martinet wrote: > For bullseye, this package upgrade reliably triggers the issue, and > installing old packages back makes surf work again: > Unpacking libwebkit2gtk-4.0-37:amd64 (2.42.1-1~deb11u1) over > (2.40.5-1~deb11u1) ... > Unpacking libjavascriptcoregtk-4.0-18:amd64 (2.42.1-1~deb11u1) over > (2.40.5-1~deb11u1) ... I checked and every other WebKitGTK browser that I tested in bullseye works fine (epiphany, luakit, midori, giara, and WebKitGTK's own MiniBrowser), so I suspect that there's something odd that Surf is doing. Until this is investigated I would just run it with WEBKIT_DISABLE_COMPOSITING_MODE=1. Surf could also be patched downstream in Debian to force this, it also needs to force the x11 backend because its Wayland support is broken (see #1012739). Berto
Bug#1053347: still not working on linux-image-6.5.0-2-amd64
Hi, just upgraded to linux-image-6.5.0-2-amd64 but same symptoms. Last working kernel was linux-image-6.4.0-4-amd64 thanks -- Ivan Sergio Borgonovo https://www.webthatworks.it https://www.borgonovo.net
