Bug#1003351: Update package to upstream version 5.0 (patches provided)
Hello, I'm a developer of the game Naev and just would like to say that new versions have been blocked on libunibreak for 3ish years now, since we require features in newer versions. I really look forward to debian packaging newer versions of libunibreak. Keep up the good work! Best, Edgar On Thu, 22 Jun 2023 11:49:13 +0200 Nils =?iso-8859-1?Q?K=F6nig?= wrote: Hi, On Fri, Jun 16, 2023 at 22:01:54 +0200, Oneric wrote: > Hi! > > I’ve been considering taking over this package (if I can > find a sponsor) now that it can be utilised by libass. > > On Sat, 8 Jan 2022 20:42:54 +0100 Nils König wrote: > > Thus I believe it would be a good idea to upgrade; patches to update > > the Debian package to 5.0 are attached (also fixing lintian warnings). > > First of all thanks for your effort. I already had a version of this > for upstream’s 5.1 release for private use, but after looking through > your patches adopted some bits from your version too. > If it all goes well, how would you like to be credited? Oh, no need to attribute anything to me. I just updated this once for my own use and then didn't think much about it anymore. Whatever saves me the trouble of manually building this package is welcome by me. You can consider whatever of my work remains in the to be packaged version as CC0 or 0BSD. In fact, given that I didn't really follow up on this after the initial post, I’d prefer to not be listed. > > > [...] > > > > It appears like most packages, include a copyright declaration for debian/* > > with past and current maintainers as copyright holders; this package does not, > > but obviously I cannot choose a licence for someone else. If this is required, > > what licence did/do you intend Eugene? > > Just to be sure: did you receive a reply to this from Eugene (perhaps > by accident as a private reply instead of sending to BTS)? Unfortunately, I did not get any reply. > Best, > Oneric Cheers Nils König
Bug#1040956: systemd: Internal USB devices disconnected when `udevadm settle` run in early boot
Control: tags -1 - moreinfo commit 88d8ab119df0239e70a5312f1f2c179c7f642dec Author: Dmitry V. Levin Date: Thu Mar 16 08:00:00 2023 + udev-rules: fix matching of token types that support alternative patterns Thanks a lot! The relevant upstream PR is https://github.com/systemd/systemd/pull/26886 I left a comment there that this has caused a regression. OpenPGP_signature Description: OpenPGP digital signature
Bug#1041145: firmware-free: Non-debian build dependency linux-support (= 5.4.0-3) prevents local revision build.
Source: firmware-free Version: 20200122-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: kerd...@gmail.com Dear Maintainer, When building debian packages with local CFLAGS and other environment changes, the recommended procedure is to update the package version with a local revision number. When doing so for firmware-free, this package considers a version change to be a change to the source code, which triggers some checks and a python error about the missing module. This package should be updated to depend on a debian version of linux-support, or the suitable versions of linux support required to follow the recommended build procedures should be available in bookworm to build this bookworm package, and this package should depend on them. Thank you, Theodoric stier -- System Information: Debian Release: 12.0 Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1037256: debian-installer: GUI font for Japanese was incorrectly rendered
FYI: I've updated a PoC patch. Mainly the explanation of patch was updated.
0001-frontend-avoid-han-unification-for-Japanese-take2.patch
>From b388a793b19a0afeb9110a6dd7633b1734ffb759 Mon Sep 17 00:00:00 2001
From: Kentaro Hayashi
Date: Wed, 7 Jun 2023 17:50:40 +0900
Subject: [PATCH] frontend: avoid han-unification for Japanese
Because of Han unification, wrong font typefaces are
rendered by default when you choose Japanese language
using GUI installer.
Most of typefaces are correct, but there are wrong
typefaces (Simplified Chinese) which is used for widget rendering.
This issue [1] will not be solved by using DroidSansFallback.ttf
(which is shipped by fonts-android udeb) for Japanese.
It means that we need to switch font itself which contains Japanese
typeface to fix this issue.
Prerequisite for verifying issue:
Step1: Make fonts-motoya-l-cedar-udeb
which ships MotoyaLCedar (MTLc3m.ttf)
Step2: Install fonts-motoya-l-cedar with listing it
in installer/build/pkg-lists/gtk-common.
Step3: Apply this patch for cdebconf package
[1] Your Code Displays Japanese Wrong
https://heistak.github.io/your-code-displays-japanese-wrong/
Signed-off-by: Kentaro Hayashi
---
src/modules/frontend/gtk/di.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/src/modules/frontend/gtk/di.c b/src/modules/frontend/gtk/di.c
index a6cb38f1..4c036cd5 100644
--- a/src/modules/frontend/gtk/di.c
+++ b/src/modules/frontend/gtk/di.c
@@ -355,6 +355,30 @@ static GtkTextDirection get_text_direction(struct frontend * fe)
return direction;
}
+/** Set language specific gtk-font-name explicitly
+ *
+ * @param fe
+ */
+static void set_language_specific_font_name(struct frontend *fe)
+{
+char * language = cdebconf_gtk_get_text(fe, "debconf/language",
+"Current language for installer");
+if (language && strcmp(language, "ja") == 0) {
+/* font-android-udeb is used for CJK, but because of Han unification,
+ * some of font typefaces are rendered as Simplified Chinese, not
+ * Japanese.
+ * This issue is not solved by using DroidSansFallback.ttf
+ * (fonts-android-udeb), thus another font which contains
+ * Japanese font typeface must be used for Japanese.
+ *
+ * MotoyaLCedar is suitable font which can be bundled as
+ * fonts-motoya-l-cedar-udeb.
+ * [1] https://wiki.debian.org/DebianInstaller/GUIFonts
+ */
+gtk_rc_parse_string('gtk-font-name = "MotoyaLCedar"');
+}
+}
+
/** Update various settings with the current language settings.
*
* @param fe cdebconf frontend
@@ -365,6 +389,9 @@ static void refresh_language(struct frontend * fe)
gtk_rc_reparse_all();
/* Adapt text direction. */
gtk_widget_set_default_direction(get_text_direction(fe));
+
+/* Override specific font name */
+set_language_specific_font_name(fe);
}
/** Update what needs to be updated on a new user interaction.
--
2.40.1
Bug#1041144: firewire_ohci 0000:0c:00.0: register access failure for FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05)
Package: linux-image-6.1.0-10-amd64 Version: 6.1.37-1 In the journal we find the following error (the line “firewire_ohci … failure” is red, the line “firewire_ohci … 0x10” is bright white, and the remaining three lines are grey-white as usual): … Jul 15 03:35:14 AnonymizedMachneName kernel: sdhci: Secure Digital Host Controller Interface driver Jul 15 03:35:14 AnonymizedMachneName kernel: PTP clock support registered Jul 15 03:35:14 AnonymizedMachneName kernel: sdhci: Copyright(c) Pierre Ossman Jul 15 03:35:14 AnonymizedMachneName kernel: firewire_ohci :0c:00.0: register access failure Jul 15 03:35:14 AnonymizedMachneName kernel: firewire_ohci :0c:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x10 … The computer is Dell Mobile Precision M6700. BIOS is at its latest available version A20. As the machine experiences high-level issues later at boot (e.g., some services can't start), we wish to be sure about the contribution of the error here. How much do we have to worry? The outputs of modprobing the driver and lspci are attached. Perhaps, the driver could be a bit cleverer for the particular hardware “Dell 1394 OHCI Compliant Host Controller” and not issue a user-visible error in first place. Gratefully, AlMa0c:00.0 FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05) (prog-if 10 [OHCI]) Subsystem: Dell 1394 OHCI Compliant Host Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- # modprobe -v firewire_ohci debug=-1 2>&1 insmod /lib/modules/6.1.0-10-amd64/kernel/drivers/firewire/firewire-ohci.ko debug=-1 [ 6997.901108] firewire_ohci :0c:00.0: added OHCI v1.10 device as card 5, 8 IR + 8 IT contexts, quirks 0x10 [ 6997.901120] firewire_ohci :0c:00.0: IRQ 0004 regAccessFail [ 6997.902591] firewire_ohci :0c:00.0: register access failure [ 6997.903295] firewire_ohci :0c:00.0: IRQ 00030010 selfID AR_req busReset [ 6997.904508] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.904531] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.906641] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.906651] firewire_ohci :0c:00.0: AR evt_bus_reset, generation 1 [ 6997.906657] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.908958] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.908984] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.909006] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.909044] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.909091] firewire_ohci :0c:00.0: IRQ 0002 busReset # [ 6997.914578] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.914609] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.914634] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.917379] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.917406] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.917423] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.920802] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.920823] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.920840] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.923896] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.925292] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.926671] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.927953] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.928982] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.930342] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.931326] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.932286] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.933139] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.934349] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.935605] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.936851] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.937779] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.939030] firewire_ohci :0c:00.0: IRQ 0002 busReset [ 6997.939810] firewire_ohci :0c:00.0: 1 selfIDs, generation 1, local node ID ffc0 [ 6997.940587] firewire_ohci :0c:00.0: selfID 0: 807f8842, phy 0 [-..] S400 gc=63 +0W Lci [ 6998.453197] firewire_core :0c:00.0: created device fw0: GUID 0027c741444fc000, S400
Bug#1041143: Module for accelerometer lis3lv02d isn't loaded at start for Dell Mobile Precision M6700; is this right?
Package: linux-image-6.1.0-10-amd64 Version: 6.1.37-1 Severity: wishlist In the journal we find the following warning concerning an accelerometer (the last line is orange): … Jul 15 03:35:14 AnonymizedMachneName kernel: i801_smbus :00:1f.3: SMBus using PCI interrupt Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: bus type USB registered Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: video: Video Device [VID] (multi-head: yes rom: no post: no) Jul 15 03:35:14 AnonymizedMachneName kernel: i801_smbus :00:1f.3: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration … The machine is a Dell Mobile Precision M6700. BIOS is at its latest available version A20. As the machine experiences high-level issues later at boot (e.g., some services can't start), we wish to be sure about the contribution of the issues warned about here. How much do we have to worry? During boot, /sys/devices/platform does NOT have files referring to lis3lv02d. Trying to `modprobe -v lis3lv02d` succeeds and yields new /sys/kernel/btf/lis3lv02d /sys/module/lis3lv02d Trying to `modprobe -v lis3lv02d_i2c` generates even more contents in /sys: /sys/kernel/btf/lis3lv02d_i2c /sys/bus/i2c/drivers/lis3lv02d_i2c /sys/module/lis3lv02d_i2c /sys/module/lis3lv02d_i2c/drivers/i2c:lis3lv02d_i2c /sys/module/lis3lv02d/holders/lis3lv02d_i2c So the kernel might be unaware of the accelerometer by default (which is probably not ideal because, e.g., the we might wish to cut/reduce power to, say, fans, when the laptop starts falling/vibrating (and therefore also reduce the power consumption by various chips, e.g., reducing the CPU frequency) and restore the settings after fall). Moreover, the documentation on lis3lv02d present in /usr/share/doc/linux-doc-6.1 talks about HP laptops with this accelerometer. Here, we have a Dell laptop. So IF the driver is correct for our accelerometer (how do we find this out with certainty?), the documentation has to be adapted. Gratefully, AlMa
Bug#1040956: systemd: Internal USB devices disconnected when `udevadm settle` run in early boot
Bisect done (though between v253 and v253.5). Looks like it's the
following commit that breaks it.
88d8ab119df0239e70a5312f1f2c179c7f642dec is the first bad commit
commit 88d8ab119df0239e70a5312f1f2c179c7f642dec
Author: Dmitry V. Levin
Date: Thu Mar 16 08:00:00 2023 +
udev-rules: fix matching of token types that support alternative
patterns
For those token types that support matching of alternative patterns,
their token values are interpreted as nulstr, so make sure the parser
does the right thing and makes these token values terminated by two
subsequent NULs so they could be safely interpreted as nulstr.
Before this fix, the following rules would result to "echo foo"
invocation:
ENV{foo}=", RUN"
ENV{foo}=="bar", RUN+="echo foo"
because the value of `ENV{foo}` is treated as nulstr, and it used
to match
against alternative patterns, in this case `bar`, `, RUN`, and
`="echo foo`.
Fixes: 25de7aa7b90c ("udev: modernize udev-rules.c")
(cherry picked from commit c43ff248f94266cfc93e300a2d3d163ed805e55b)
Bug#1041142: ACPI Warning: SystemIO range … conflicts with OpRegion … . lpc_ich: Resource conflict(s) found affecting gpio_ich
Package: linux-image-6.1.0-10-amd64 Version: 6.1.37-1 Severity: wishlist In the journal we find the following warnings (the texts "ACPI Warning: … (20220331/utaddress-204)" and “lpc_ich: … gpio_ich” are orange, and everything else is white as usual): … Jul 15 03:35:14 AnonymizedMachneName kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: button: Power Button [PWRF] Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\PMIO) (20220331/utaddress-204) Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: battery: Slot [BAT0] (battery present) Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI Warning: SystemIO range 0x0540-0x054F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20220331/utaddress-204) Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: battery: Slot [BAT1] (battery absent) Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI Warning: SystemIO range 0x0530-0x053F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20220331/utaddress-204) Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI Warning: SystemIO range 0x0500-0x052F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20220331/utaddress-204) Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? Jul 15 03:35:14 AnonymizedMachneName kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich … The machine is a Dell Mobile Precision M6700 with the processor Intel Core i7-3720QM, 32 GB RAM, and AMD FirePro M6000 Mobility Pro graphic chip with 2GB GDDR5. BIOS is at its latest available version A20. As the machine experiences high-level issues later at boot (e.g., some services can't start), we wish to be sure about the contribution of the issues warned about here. If we believe Jean Delvare from https://bugzilla.kernel.org/show_bug.cgi?id=48811 , these warnings might be just informative; the user probably needn't be warned. If this is really so (myself, I have no idea), there's no need for the orange color. Gratefully, AlMa
Bug#1041141: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
Package: linux-image-6.1.0-10-amd64 Version: 6.1.37-1 In the journal we find the following warning (“pmd_set_huge … override.” line is yellow, everything else is white): … Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Jul 15 03:35:14 AnonymizedMachneName kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 Jul 15 03:35:14 AnonymizedMachneName kernel: PCI: MMCONFIG for domain [bus 00-3f] at [mem 0xf800-0xfbff] (base 0xf800) Jul 15 03:35:14 AnonymizedMachneName kernel: PCI: MMCONFIG at [mem 0xf800-0xfbff] reserved in E820 Jul 15 03:35:14 AnonymizedMachneName kernel: pmd_set_huge: Cannot satisfy [mem 0xf800-0xf820] with a huge-page mapping due to MTRR override. Jul 15 03:35:14 AnonymizedMachneName kernel: PCI: Using configuration type 1 for base access … The machine is a Dell Mobile Precision M6700 with the processor Intel Core i7-3720QM, 32 GB RAM, and AMD FirePro M6000 Mobility Pro graphic chip with 2GB GDDR5. The BIOS is at its last available version A20. As the machine experiences high-level issues later at boot (e.g., some services can't start), we wish to be sure about the contribution of the issue warned about here. Can the issue underlying this warning be easily "fixed" or are we already running a "safe" setting? I took a look into https://www.kernel.org/doc/html/v4.10/admin-guide/kernel-parameters.html , but it seems to me that changing anything _safely_ would require me going into the depths of the memory layout of x86/amd64; nothing that I would test myself without proper advice. Gratefully, AlMa
Bug#1041140: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found; ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0
Package: linux-image-6.1.0-10-amd64 Version: 6.1.37-1 In the journal I see two yellow lines (which, probably, constitute warnings) directly following one another: … 02:38:24 hostname kernel: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found … 02:38:24 hostname kernel: ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (20220331/utaddress-203) Later in the journal we see a white line … 02:38:27 hostname kernel: input: Dell WMI hotkeys as /devices/platform/PNP0C14:00/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input10 As the machine (Dell Mobile Precision M6700) experiences various high-level issues later in the boot process, I'm unsure about the contribution of the two issues in the log. Which software or hardware problems do these warnings inform us about? Any fix or remedy? Gratefully, AlMa
Bug#1041139: gdm3: login greeting timeout causes reboot when screen blanks
Package: gdm3 Version: 43.0-3 Severity: normal X-Debbugs-Cc: j...@jimfriedeck.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Fresh install of debian 12 on a Lenovo M630e Core i5 with latest firmware. Noticed machine rebooted itself after sitting at login screen for 5 minutes. Cycle repeats. * What exactly did you do (or not do) that was effective (or ineffective)? Start the machine. * What was the outcome of this action? Machine reboots every 5 minutes when login screen blanks. Also occurs any time screen is set to go to sleep. Login screen timeout can't be changed. * What outcome did you expect instead? Computer to idle or sleep, not reboot. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT) 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 gdm3 depends on: ii accountsservice 22.08.8-6 ii adduser 3.134 ii dbus [default-dbus-system-bus]1.14.6-1 ii dbus-bin 1.14.6-1 ii dbus-daemon 1.14.6-1 ii dconf-cli 0.40.0-4 ii dconf-gsettings-backend 0.40.0-4 ii debconf [debconf-2.0] 1.5.82 ii gir1.2-gdm-1.043.0-3 ii gnome-session [x-session-manager] 43.0-1 ii gnome-session-bin 43.0-1 ii gnome-session-common 43.0-1 ii gnome-settings-daemon 43.0-4 ii gnome-shell 43.4-1 ii gnome-terminal [x-terminal-emulator] 3.46.8-1 ii gsettings-desktop-schemas 43.0-1 ii libaccountsservice0 22.08.8-6 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9 ii libcanberra-gtk3-00.30-10 ii libcanberra0 0.30-10 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgdm1 43.0-3 ii libglib2.0-0 2.74.6-2 ii libglib2.0-bin2.74.6-2 ii libgtk-3-03.24.37-2 ii libgudev-1.0-0237-2 ii libkeyutils1 1.6.3-2 ii libpam-modules1.5.2-6 ii libpam-runtime1.5.2-6 ii libpam-systemd [logind] 252.6-1 ii libpam0g 1.5.2-6 ii librsvg2-common 2.54.5+dfsg-1 ii libselinux1 3.4-1+b6 ii libsystemd0 252.6-1 ii libx11-6 2:1.8.4-2+deb12u1 ii libxau6 1:1.0.9-1 ii libxcb1 1.15-1 ii libxdmcp6 1:1.1.2-3 ii polkitd 122-3 ii procps2:4.0.2-3 ii systemd-sysv 252.6-1 ii ucf 3.0043+nmu1 ii x11-common1:7.7+23 ii x11-xserver-utils 7.7+9+b1 ii xterm [x-terminal-emulator] 379-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.46.0-5 ii desktop-base 12.0.6 ii gnome-session [x-session-manager] 43.0-1 ii x11-xkb-utils 7.7+7 ii xserver-xephyr 2:21.1.7-3 ii xserver-xorg 1:7.7+23 ii zenity 3.44.0-1 Versions of packages gdm3 suggests: pn libpam-fprintd ii libpam-gnome-keyring 42.1-1+b2 pn libpam-pkcs11 pn libpam-sss ii orca 43.1-1 -- Configuration Files: /etc/gdm3/daemon.conf changed: [daemon] AutomaticLoginEnable=True AutomaticLogin=jim [security] [xdmcp] [chooser] [debug] -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3
Bug#1000133: tagging 1000133
On Sun, Dec 05, 2021 at 05:29:30PM +0100, Chris Hofstaedtler wrote: > tags 1000133 + upstream help > thanks kannel builds without the -enable-pcre, would that be an option or does that lose too much functionality? cu Adrian
Bug#1041138: memtailor FTBFS with googletest 1.13.0
Source: memtailor Version: 1.0~git20220104-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/memtailor.html ... In file included from /usr/src/gtest/include/gtest/gtest-message.h:57, from /usr/src/gtest/include/gtest/gtest-assertion-result.h:46, from /usr/src/gtest/include/gtest/gtest.h:64, from src/test/ArenaTest.cpp:19: /usr/src/gtest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by removing the -std=gnu++0x from unittest_CXXFLAGS in Makefile.am
Bug#1041137: simple-tpm-pk11 FTBFS with googletest 1.13.0
Source: simple-tpm-pk11 Version: 0.06-4 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/simple-tpm-pk11.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /usr/src/gtest/src/gtest_main.cc:32, from src/libgtest.cc:20: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by removing the -std=gnu++0x in configure.ac
Bug#1041135: libusermetrics FTBFS with googletest 1.13.0
Source: libusermetrics Version: 1.3.0-1 Severity: serious Tags: ftbfs trixie sid Forwarded: https://gitlab.com/ubports/development/core/libusermetrics/-/merge_requests/11 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libusermetrics.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /build/1st/libusermetrics-1.3.0/tests/testutils/main.cpp:21: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ...
Bug#1041136: lomiri-indicator-transfer FTBFS with googletest 1.13.0
Source: lomiri-indicator-transfer Version: 1.0.0-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lomiri-indicator-transfer.html ... In file included from /usr/src/googletest/googlemock/include/gmock/internal/gmock-port.h:57, from /usr/src/googletest/googlemock/include/gmock/internal/gmock-internal-utils.h:49, from /usr/src/googletest/googlemock/include/gmock/gmock-actions.h:145, from /usr/src/googletest/googlemock/include/gmock/gmock.h:56, from /build/1st/lomiri-indicator-transfer-1.0.0/tests/source-mock.h:25, from /build/1st/lomiri-indicator-transfer-1.0.0/tests/mock-source-plugin.cpp:20: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=c++11 to -std=c++14 in tests/CMakeLists.txt
Bug#1041134: tiny-dnn FTBFS with googletest 1.13.0
Source: tiny-dnn Version: 1.0.0a3+ds-3 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tiny-dnn.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /build/1st/tiny-dnn-1.0.0a3+ds/test/test.cpp:30: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ...
Bug#1041133: apt-cacher-ng: Cannot allocate memory error from client after network outage
Package: apt-cacher-ng Version: 3.7.4-1+b2 Severity: normal Due to a power outage the system running apt-cacher-ng had been without Internet access for a while, when access was restored systems connecting to it got the following errors: W: Failed to fetch http://ftp.au.debian.org/debian/dists/unstable/InRelease 503 Cannot allocate memory [IP: 10.0.0.1 3142] W: Failed to fetch http://ftp.au.debian.org/debian/dists/bookworm/InRelease 503 Cannot allocate memory [IP: 10.0.0.1 3142] W: Failed to fetch http://security.debian.org/debian-security/dists/bookworm-security/InRelease 503 Cannot allocate memory [IP: 10.0.0.1 3142] It didn't work until apt-cacher-ng had been restarted. The error message displayed was wrong, but also apt-cacher-ng should have realised that the network was back and connected to the outside world. -- Package-specific info: -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-10-amd64 (SMP w/6 CPU threads; PREEMPT) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Enforcing - Policy name: default Versions of packages apt-cacher-ng depends on: ii adduser3.134 ii debconf [debconf-2.0] 1.5.82 ii dpkg 1.21.22 ii libbz2-1.0 1.0.8-5+b1 ii libc-ares2 1.18.1-3 ii libc6 2.36-9 ii libevent-2.1-7 2.1.12-stable-8 ii libevent-pthreads-2.1-72.1.12-stable-8 ii libfuse2 2.9.9-6+b1 ii libgcc-s1 12.2.0-14 ii liblzma5 5.4.1-0.2 ii libssl33.0.9-1 ii libstdc++6 12.2.0-14 ii libsystemd0252.6-1 ii libwrap0 7.6.q-32 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.06-4 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages apt-cacher-ng recommends: ii ca-certificates 20230311 Versions of packages apt-cacher-ng suggests: pn avahi-daemon pn doc-base -- Configuration Files: /etc/apt-cacher-ng/acng.conf changed: CacheDir: /var/cache/apt-cacher-ng LogDir: /var/log/apt-cacher-ng SupportDir: /usr/lib/apt-cacher-ng BindAddress: localhost 10.0.0.1 Remap-debrep: file:deb_mirror*.gz /debian ; file:backends_debian # Debian Archives Remap-uburep: file:ubuntu_mirrors /ubuntu ; file:backends_ubuntu # Ubuntu Archives Remap-klxrep: file:kali_mirrors /kali ; file:backends_kali # Kali Linux Archives Remap-cygwin: file:cygwin_mirrors /cygwin # ; file:backends_cygwin # incomplete, please create this file or specify preferred mirrors here Remap-sfnet: file:sfnet_mirrors # ; file:backends_sfnet # incomplete, please create this file or specify preferred mirrors here Remap-alxrep: file:archlx_mirrors /archlinux # ; file:backend_archlx # Arch Linux Remap-fedora: file:fedora_mirrors # Fedora Linux Remap-epel: file:epel_mirrors # Fedora EPEL Remap-slrep: file:sl_mirrors # Scientific Linux Remap-gentoo: file:gentoo_mirrors.gz /gentoo ; file:backends_gentoo # Gentoo Archives Remap-secdeb: security.debian.org security.debian.org/debian-security deb.debian.org/debian-security /debian-security cdn-fastly.deb.debian.org/debian-security ; deb.debian.org/debian-security security.debian.org cdn-fastly.deb.debian.org/debian-security ReportPage: acng-report.html ExThreshold: 4 FollowIndexFileRemoval: 1 LocalDirs: acng-doc /usr/share/doc/apt-cacher-ng /etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: '/etc/apt-cacher-ng/security.conf' -- debconf-show failed
Bug#1041132: persistent-cache-cpp FTBFS with googletest 1.13.0 ^
Source: persistent-cache-cpp Version: 1.0.5-4 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/persistent-cache-cpp.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /build/1st/persistent-cache-cpp-1.0.5/tests/core/persistent_cache/persistent_cache_test.cpp:25: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=c++11 to -std=c++14 in CMakeLists.txt
Bug#1041131: prometheus-cpp FTBFS with googletest 1.13.0
Source: prometheus-cpp Version: 1.0.1-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-cpp.html ... CMakeFiles/gmock_main.dir/usr/src/googletest/googlemock/src/gmock_main.cc.o -MF CMakeFiles/gmock_main.dir/usr/src/googletest/googlemock/src/gmock_main.cc.o.d -o CMakeFiles/gmock_main.dir/usr/src/googletest/googlemock/src/gmock_main.cc.o -c /usr/src/googletest/googlemock/src/gmock_main.cc In file included from /usr/src/googletest/googlemock/include/gmock/internal/gmock-port.h:57, from /usr/src/googletest/googlemock/include/gmock/internal/gmock-internal-utils.h:49, from /usr/src/googletest/googlemock/include/gmock/gmock-actions.h:145, from /usr/src/googletest/googlemock/include/gmock/gmock.h:56, from /usr/src/googletest/googlemock/src/gmock_main.cc:32: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by configuring with -DOVERRIDE_CXX_STANDARD_FLAGS=OFF
Bug#1037538: gerbera: FTBFS with libupnp17
On Tue, 20 Jun 2023 21:17:01 +0200 Bastian Germann wrote: This is the last package that prevents fulfilling the pupnp transition. Would you please go ahead with a team upload? I do not think James is still around. I have prepared a NMU with a new upstream version: https://salsa.debian.org/multimedia-team/gerbera/-/merge_requests/1 If nobody objects I am going to upload it soon.
Bug#1041130: google-compute-engine-oslogin FTBFS with googletest 1.13.0
Source: google-compute-engine-oslogin Version: 20210907.00-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/google-compute-engine-oslogin.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from oslogin_utils_test.cc:17: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=c++11 to -std=c++14 in test/Makefile
Bug#1041129: krb5-config install doesn't gracefully handle read-only /etc/krb5.conf file and errors out
Package: krb5-config Version: 2.7 When attempting to install krb5-config, if there is a pre-existing /etc/krb5.conf file that is part of a read-only filesystem,example: mounted through something like a container Docker/Kubernetes,the install process will error and fail. Here are reproducible steps: 1. Start a Debain instance with a read-only copy of /etc/krb5.conf. 2. $ apt-get update && apt-get -y install krb5-config Unpacking krb5-config (2.7) ... dpkg: krb5-config: dependency problems, but configuring anyway as you requested: krb5-config depends on bind9-host; however: Package bind9-host is not installed. Setting up krb5-config (2.7) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype Unable to rename file: Device or resource busy, stopped at /var/lib/dpkg/info/krb5-config.postinst line 79, line 22. dpkg: error processing package krb5-config (--install): installed krb5-config package post-installation script subprocess returned error exit status 16 Errors were encountered while processing: krb5-config Based on my investigation it appears that /var/lib/dpkg/info/krb5-config.postinst will always try to replace /etc/krb5.conf even if it would be unable to. I suggest that a check be added before attempting to replace to ensure that it will be able to do so. If it is unable to replace it should exit successfully, but potentially log a warning. I'm not too familiar with the script, but potentially using a "test -w /etc/krb5.conf" before trying to replace the file would work here. "test -w /etc/krb5.conf" does properly detect that the file is read only, so it's more of a question of whether it is usable in the install script. Installing Kerberos on other distributions with a similar setup does not result in this type of error. Which is why I'm opening this bug report. I am running on Debian GNU/Linux 12 (bookworm), Linux 25bb0bdce857 3.10.0-1160.92.1.el7.x86_64 #1 SMP Tue Jun 20 11:48:01 UTC 2023 x86_64 GNU/Linux Thanks, Ben
Bug#1041128: qcodeeditor FTBFS with googletest 1.13.0
Source: qcodeeditor Version: 1.0+1gitdc644d-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qcodeeditor.html ... In file included from /usr/include/c++/13/type_traits:35, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:45, from /usr/include/x86_64-linux-gnu/qt5/QtGui/qtguiglobal.h:43, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtwidgetsglobal.h:43, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:43, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1, from /build/1st/qcodeeditor-1.0+1gitdc644d/include/internal/QLineNumberArea.hpp:4, from /build/1st/qcodeeditor-1.0+1gitdc644d/include/QLineNumberArea:3, from /build/1st/qcodeeditor-1.0+1gitdc644d/src/internal/QCodeEditor.cpp:2: /usr/include/c++/13/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options. 32 | #error This file requires compiler and library support \ | ^ ...
Bug#1041126: krb5-config install doesn't gracefully handle read-only /etc/krb5.conf file and errors out
Apologies, this email got really mangled when sending, I will resubmit with corrected formatting.
Bug#1041127: pbcopper FTBFS with gcc 13
Source: pbcopper Version: 2.0.0+dfsg-2 Severity: serious Tags: ftbfs trixie sid experimental https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pbcopper.html ... In file included from ../src/align/LocalAlignment.cpp:5: ../include/pbcopper/align/LocalAlignment.h:20:40: error: ‘uint16_t’ has not been declared 20 |int32_t mismatches, uint16_t score, std::vector cigar, |^~~~ ../include/pbcopper/align/LocalAlignment.h:20:68: error: ‘uint32_t’ was not declared in this scope 20 |int32_t mismatches, uint16_t score, std::vector cigar, | ^~~~ ../include/pbcopper/align/LocalAlignment.h:12:1: note: ‘uint32_t’ is defined in header ‘’; did you forget to ‘#include ’? 11 | #include +++ |+#include 12 | ...
Bug#1041126: krb5-config install doesn't gracefully handle read-only /etc/krb5.conf file and errors out
Package: krb5-configVersion: 2.7 When attempting to install krb5-config, if there is a pre-existing /etc/krb5.conf file that is part of a read-only filesystem,example: mounted through something like a container Docker/Kubernetes,the install process will error and fail. Here are reproducible steps: 1. Start a Debain instance with a read-only copy of /etc/krb5.conf.2. Run$ apt-get update && apt-get -y install krb5-config Unpacking krb5-config (2.7) ...dpkg: krb5-config: dependency problems, but configuring anyway as you requested: krb5-config depends on bind9-host; however: Package bind9-host is not installed.Setting up krb5-config (2.7) ...debconf: unable to initialize frontend: Dialogdebconf: (TERM is not set, so the dialog frontend is not usable.)debconf: falling back to frontend: Readlinedebconf: unable to initialize frontend: Readlinedebconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)debconf: falling back to frontend: TeletypeUnable to rename file: Device or resource busy, stopped at /var/lib/dpkg/info/krb5-config.postinst line 79, line 22.dpkg: error processing package krb5-config (--install): installed krb5-config package post-installation script subprocess returned error exit status 16Errors were encountered while processing: krb5-config Based on my investigation it appears that /var/lib/dpkg/info/krb5-config.postinst will always try to replace /etc/krb5.conf even if it would be unable to.I suggest that a check be added before attempting to replace to ensure that it will be able to do so. If it is unable to replace it should exit successfully, but potentially log a warning. I'm not too familiar with the script, but potentially using a "test -w" before trying to replace the file would work here. (test -w does properly detect that the file is read only, so it's more of a question of whether it is usable in the install script. Installing Kerberos on other distributions with a similar setup does not result in this type of error. Which is why I'm opening this bug report. I am running on Debian GNU/Linux 12 (bookworm), Linux 25bb0bdce857 3.10.0-1160.92.1.el7.x86_64 #1 SMP Tue Jun 20 11:48:01 UTC 2023 x86_64 GNU/Linux
Bug#1041125: properties-cpp FTBFS with googletest 1.13.0
Source: properties-cpp Version: 0.0.2-7 Severity: serious Tags: ftbfs trixie sid Forwarded: https://gitlab.com/ubports/development/core/lib-cpp/properties-cpp/-/commit/21b42a02ccf5346e158c5202b858eaa0e8e0a0f0 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/properties-cpp.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /build/1st/properties-cpp-0.0.2/tests/properties_test.cpp:21: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ...
Bug#1041124: dlt-daemon FTBFS with googletest 1.13.0
Source: dlt-daemon Version: 2.18.9-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dlt-daemon.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /build/1st/dlt-daemon-2.18.9/tests/gtest_dlt_user.cpp:27: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=gnu++11 to -std=gnu++14 in CMakeLists.txt
Bug#1041123: libkiwix FTBFS with googletest 1.13.0
Source: libkiwix Version: 11.0.0-2 Severity: serious Tags: ftbfs trixie sid experimental Forwarded: https://github.com/kiwix/libkiwix/issues/877 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libkiwix.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from ../test/kiwixserve.cpp:1: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ...
Bug#1041122: net-cpp FTBFS with googletest 1.13.0
Source: net-cpp Version: 3.1.0+dfsg-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/net-cpp.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /build/1st/net-cpp-3.1.0+dfsg/tests/header_test.cpp:21: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=c++11 to -std=c++14 in CMakeLists.txt
Bug#1041121: libecpint FTBFS with googletest 1.13.0
Source: libecpint Version: 1.0.7-3 Severity: serious Tags: ftbfs trixie sid Forwarded: https://github.com/robashaw/libecpint/issues/58 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libecpint.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /build/1st/libecpint-1.0.7/tests/units/bessel/bessel.cpp:1: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ...
Bug#1041120: lomiri-url-dispatcher FTBFS with googletest 1.13.0
Source: lomiri-url-dispatcher Version: 0.1.2-1 Severity: serious Tags: ftbfs trixie sid Forwarded: https://gitlab.com/ubports/development/core/lomiri-url-dispatcher/-/commit/7f41a2e8a7d65eb24b9ddd1e1ede4a3004b21a8d https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lomiri-url-dispatcher.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /build/1st/lomiri-url-dispatcher-0.1.2/tests/directory-update-test.cc:19: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ...
Bug#1041119: aerc: Raw HTML when quoting HTML email
Package: aerc
Version: 0.15.2-1
Severity: normal
Dear aerc maintainer,
When creating a quoted reply to an email that _only_ has an HTML part, the
quoted email is in raw HTML:
>
>
>
>
> ...
I was hoping that the quote by default would be converted to plaintext.
I worked around this by editing the quoted_reply template to use lynx to dump
the rendered HTML:
```
X-Mailer: aerc {{version}}
On {{dateFormat (.OriginalDate | toLocal) "Mon Jan 2, 2006 at 3:04 PM MST"}},
{{(index .OriginalFrom 0).Name}} wrote:
{{if eq .OriginalMIMEType "text/html"}}
{{quote (.OriginalText | exec `lynx -dump -stdin`)}}
{{else}}
{{quote .OriginalText}}
{{end}}
```
Would it make sense to have something like that as default behaviour, perhaps
using w3m which is already a recommended dependency?
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.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 aerc depends on:
ii libc62.37-5
ii libnotmuch5 0.37-1+b1
Versions of packages aerc recommends:
ii dante-client 1.4.2+dfsg-7
ii gnupg 2.2.40-1.1
pn w3m
Versions of packages aerc suggests:
ii notmuch 0.37-1+b1
-- no debconf information
Bug#1028532: copyright fixed
Upstream has fixed the copyright information. -- Regards Sudip
Bug#1041118: ska FTBFS with googletest 1.13.0
Source: ska Version: 1.0+dfsg-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ska.html ... In file included from googletest/include/gtest/gtest-message.h:57, from googletest/include/gtest/gtest-assertion-result.h:46, from googletest/include/gtest/gtest.h:64, from googletest/src/gtest-all.cc:38: googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by removing the -std=c++0x in tests/Makefile
Bug#1041117: dde-network-utils FTBFS with googletest 1.13.0
Source: dde-network-utils Version: 5.4.13-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dde-network-utils.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from tst_networkmodel.cpp:1: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing c++11 to c++14 in tests/dde-network-utils/tst_dde-network-utils.pro
Bug#1041116: orthanc-postgresql FTBFS with googletest 1.13.0
Source: orthanc-postgresql Version: 4.0-7 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/orthanc-postgresql.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /build/1st/orthanc-postgresql-4.0/PostgreSQL/UnitTests/PostgreSQLTests.cpp:22: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=gnu++11 to -std=gnu++14 in Resources/Orthanc/CMake/DownloadOrthancFramework.cmake
Bug#1040979: write_files: defer not working any more
Also, I'm curious to see what happens if you invoke the write_files_deferred module by hand with a command like $ sudo cloud-init single --name cc_write_files_deferred \ --frequency always --report It should generate messages in /var/log/cloud-init.log.
Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user
Michael Tokarev dixit: >> >> From the comment, it reserves 16 MiB after the main executable. >> >> In klibc/armhf, however, the main executable starts around >> 0x0001 whereas the interpreter starts after that, around >> 0x0038… > > Aren't it happens on all architectures, not just armhf? bullseye/amd64: 0x0020 interp 0x0040 main executable So no, this applies only to some architectures, but not because… > I had an impression it is not arch-specific. $subject … it’s arch-specific but because klibc memory map is, so the effect only occurs on those arches where klibc puts the interp before the main executable. This is unfortunately hard to grep for, because… usr/klibc/arch/arm/MCONFIG:KLIBCSHAREDFLAGS = $(LD_IMAGE_BASE_OPT) 0x38 … this applies to the interp, but for the main executables it uses the linker’s default AFAICT. There is… usr/klibc/arch/arm64/MCONFIG:KLIBCLDFLAGS = $(LD_IMAGE_BASE_OPT) 0x0040 usr/klibc/arch/arm64/MCONFIG:KLIBCSHAREDFLAGS = $(LD_IMAGE_BASE_OPT) 0x020 … which does transfer to main at 0040 interp at 0020 respectively, but only arm64 and “x32”, which really builds as amd64, do that. And Itanic uses a linker script, putting the interp at 0x2000 (which seems to be standard for ia64). 0x41c8 is the beginning of the main executable there, from analysing the built binaries. It would be more robust if klibc always specified both. But, as I said earlier, this won’t help bookworm and earlier so fixing this in qemu is appreciated ;-) >> The BSD manpage begins with… >> DESCRIPTION >> The brk() and sbrk() functions are historical curiosities left over from >> earlier days before the advent of virtual memory management. >> … so… oh well. > > That's lovely. There's another change for brk() pending in qemu right > now (to make it page-aligned; and no, it does not fix this issue). > I guess it is not just curiocities :) Perhaps. In the BSD world, malloc has been always using mmap for ages, especially as the kernel randomises anon mmap addresses. >> Anyway, while my proposed fix in theory moves the “end of the >> process’ data segment” to behind the interpreter instead of >> behind the main executable, processes are not supposed to use >> it in combination with _end, only the returned pointers. It’s >> something to at least consider. Will you forward this upstream? > > Yeah, already did, was just waiting for it to appear in the archives > for the URL. I meant the suggested fix. I’m not sure people over there will dig through all of the analysis and discussion here… but maybe a tl;dr could be posted there as well? Thanks, //mirabilos -- “It is inappropriate to require that a time represented as seconds since the Epoch precisely represent the number of seconds between the referenced time and the Epoch.” -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
Bug#1041115: e2fsprogs: `apropos lsattr` mentions "Linux second extended file system"
Package: e2fsprogs Version: 1.47.0-2 Severity: normal Dear Maintainer, `apropos lsattr` mentions "Linux second extended file system" This comes from the first line in the manpage for lsattr. "Linux second extended file system" is confusing because it's not immediately obvious it refers to ext2 filesystem. Additionally, it also works for ext3 and ext4 and many other filesystems. Please reword the sentence. Thank you. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=C, 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 e2fsprogs depends on: ii libblkid12.38.1-5+b1 ii libc62.36-9 ii libcom-err2 1.47.0-2 ii libext2fs2 1.47.0-2 ii libss2 1.47.0-2 ii libuuid1 2.38.1-5+b1 ii logsave 1.47.0-2 Versions of packages e2fsprogs recommends: pn e2fsprogs-l10n Versions of packages e2fsprogs suggests: pn e2fsck-static pn fuse2fs pn gpart pn parted -- no debconf information
Bug#1041114: sox error and audio glitch when -t not specified and libsox-fmt-pulse is not installed
Package: sox Version: 14.4.2+git20190427-3.5 Severity: normal Dear Maintainer, When `-t` is not specified then sox attempts to probe the audio driver as described at https://groups.google.com/g/linux.debian.bugs.dist/c/jCqdwFWPUKk/m/xi1AThVtMwkJ According to the list in that discussion, pulseaudio is the first driver to be probed on Linux. If libsox-fmt-pulse is not installed, then the probe fails with the error `play WARN alsa: can't encode 0-bit Unknown or not applicable`, and there is an audible pop glitch before the actual audio is played. $ play -t raw -r 48k -e signed -b 16 -c 1 dummy play WARN alsa: can't encode 0-bit Unknown or not applicable (note libsox-fmt-pulse was not installed by default on my system, the alsa driver was, so this warning and audio glitch would occur every time by default) -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sox depends on: ii libc62.36-9 ii libsox-fmt-alsa 14.4.2+git20190427-3.5 ii libsox-fmt-base 14.4.2+git20190427-3.5 ii libsox3 14.4.2+git20190427-3.5 sox recommends no packages. Versions of packages sox suggests: pn libsox-fmt-all -- no debconf information
Bug#1040979: write_files: defer not working any more
On 7/14/23 06:49, Sven Strickroth wrote:
I'm not able to reproduce the behavior you describe. defer seems to
work as expected. For example:
admin@ip-10-0-0-87:~$ ec2-metadata --ami-id
ami-id: ami-0544719b13af6edc3
admin@ip-10-0-0-87:~$ sudo cat /var/lib/cloud/instance/user-data.txt
#cloud-config
write_files:
- content: |
testing. this file should be owned by the dynamically created user
path: /test-file
owner: admin:admin
defer: true
admin@ip-10-0-0-87:~$ ls -l /test-file
-rw-r--r-- 1 admin admin 67 Jul 13 16:59 /test-file
That example does not work for me on Hetzner.cloud.
Strange. The functionality works as expected for me using the current
bookworm AMIs on Amazon EC2, as shown in the output below. I don't have
an account with Hetzner, so I'm afraid you're going to have to collect
some more information.
Can you show that the "defer" field in your cloud-config is making
through to the input that's passed to cloud-init?
Can you show that write_files works without the defer flag?
The write_files modules are defined to run once per instance. Is it
possible that your launches are not showing up as new instances,
resulting in cloud-init skipping their execution?
noah
admin@ip-10-0-0-199:~$ sudo cat /var/lib/cloud/instance/user-data.txt
#cloud-config
locale: de_DE.UTF-8
timezone: Europe/Berlin
package_update: true # Implied with `package_upgrade: true`
package_upgrade: true
packages:
['joe','mariadb-server','aptitude','psmisc','bzip2','fail2ban','postfix','apticron','nagios-nrpe-server','monitoring-plugins','libmariadb3','borgbackup','logwatch']
write_files:
- content: |
[mysqldump]
max_allowed_packet = 60M
path: /etc/mysql/mariadb.conf.d/51-dump.cnf
defer: true
admin@ip-10-0-0-199:~$ cat /etc/mysql/mariadb.conf.d/51-dump.cnf
[mysqldump]
max_allowed_packet = 60M
admin@ip-10-0-0-199:~$ grep write-files-deferred /var/log/cloud-init.log
2023-07-14 21:28:41,034 - modules.py[DEBUG]: Running module
write-files-deferred (from
'/usr/lib/python3/dist-packages/cloudinit/config/cc_write_files_deferred.py'>)
with frequency once-per-instance
2023-07-14 21:28:41,034 - handlers.py[DEBUG]: start:
modules-final/config-write-files-deferred: running
config-write-files-deferred with frequency once-per-instance
2023-07-14 21:28:41,036 - helpers.py[DEBUG]: Running
config-write-files-deferred using lock ('/var/lib/cloud/instances/i-096c9d6b1c3c04be6/sem/config_write_files_deferred'>)
2023-07-14 21:28:41,036 - handlers.py[DEBUG]: finish:
modules-final/config-write-files-deferred: SUCCESS:
config-write-files-deferred ran successfully
Bug#1040265: fixing CVE-2023-36813 in kanboard/bookworm
Am Wed, Jul 12, 2023 at 08:32:56PM -0400 schrieb Joe Nahmias: > Please see attached proposed debdiff for fixing CVE-2023-36813 in bookworm. > > --Joe > diff -Nru kanboard-1.2.26+ds/debian/changelog > kanboard-1.2.26+ds/debian/changelog > --- kanboard-1.2.26+ds/debian/changelog 2023-06-15 23:02:33.0 > -0400 > +++ kanboard-1.2.26+ds/debian/changelog 2023-07-12 20:13:20.0 > -0400 > @@ -1,3 +1,13 @@ > +kanboard (1.2.26+ds-2+deb12u2) bookworm; urgency=high This should be bookworm-security, with that change please upload to security-master, I'll take care of the DSA. Cheers, Moritz
Bug#1041113: sox: CVE-2023-26590
Source: sox X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for sox. CVE-2023-26590[0]: | A floating point exception vulnerability was found in sox, in the | lsx_aiffstartwrite function at sox/src/aiff.c:622:58. This flaw can | lead to a denial of service. https://bugzilla.redhat.com/show_bug.cgi?id=2212279 https://sourceforge.net/p/sox/bugs/370/ 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-26590 https://www.cve.org/CVERecord?id=CVE-2023-26590 Please adjust the affected versions in the BTS as needed.
Bug#1041112: sox: CVE-2023-32627
Source: sox X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for sox. CVE-2023-32627[0]: | A floating point exception vulnerability was found in sox, in the | read_samples function at sox/src/voc.c:334:18. This flaw can lead to | a denial of service. https://bugzilla.redhat.com/show_bug.cgi?id=2212282 https://sourceforge.net/p/sox/bugs/369/ 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-32627 https://www.cve.org/CVERecord?id=CVE-2023-32627 Please adjust the affected versions in the BTS as needed.
Bug#1041111: sox: CVE-2023-34318
Source: sox X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for sox. CVE-2023-34318[0]: | A heap buffer overflow vulnerability was found in sox, in the | startread function at sox/src/hcom.c:160:41. This flaw can lead to a | denial of service, code execution, or information disclosure. https://bugzilla.redhat.com/show_bug.cgi?id=2212283 https://sourceforge.net/p/sox/bugs/368/ 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-34318 https://www.cve.org/CVERecord?id=CVE-2023-34318 Please adjust the affected versions in the BTS as needed.
Bug#1041110: sox: CVE-2023-34432
Source: sox X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for sox. CVE-2023-34432[0]: | A heap buffer overflow vulnerability was found in sox, in the | lsx_readbuf function at sox/src/formats_i.c:98:16. This flaw can | lead to a denial of service, code execution, or information | disclosure. https://bugzilla.redhat.com/show_bug.cgi?id=2212291 https://sourceforge.net/p/sox/bugs/367/ 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-34432 https://www.cve.org/CVERecord?id=CVE-2023-34432 Please adjust the affected versions in the BTS as needed.
Bug#1041107: opendkim: CVE-2022-48521
Source: opendkim X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for opendkim. CVE-2022-48521[0]: | An issue was discovered in OpenDKIM through 2.10.3, and 2.11.x | through 2.11.0-Beta2. It fails to keep track of ordinal numbers when | removing fake Authentication-Results header fields, which allows a | remote attacker to craft an e-mail message with a fake sender | address such that programs that rely on Authentication-Results from | OpenDKIM will treat the message as having a valid DKIM signature | when in fact it has none. https://github.com/trusteddomainproject/OpenDKIM/issues/148 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-48521 https://www.cve.org/CVERecord?id=CVE-2022-48521 Please adjust the affected versions in the BTS as needed.
Bug#1041109: modsecurity-crs: CVE-2023-38199
Source: modsecurity-crs X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for modsecurity-crs. CVE-2023-38199[0]: | coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does | not block multiple Content-Type headers, which might allow attackers | to bypass a WAF with a crafted payload, aka "Content-Type | confusion." This occurs when the web application relies on only the | last Content-Type header. https://github.com/coreruleset/coreruleset/issues/3191 https://github.com/coreruleset/coreruleset/pull/3237 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-38199 https://www.cve.org/CVERecord?id=CVE-2023-38199 Please adjust the affected versions in the BTS as needed.
Bug#1041108: apache-jena: CVE-2023-32200
Source: apache-jena X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for apache-jena. CVE-2023-32200[0]: | There is insufficient restrictions of called script functions in | Apache Jena versions 4.8.0 and earlier. It allows a remote user to | execute javascript via a SPARQL query. This issue affects Apache | Jena: from 3.7.0 through 4.8.0. https://www.openwall.com/lists/oss-security/2023/07/11/11 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-32200 https://www.cve.org/CVERecord?id=CVE-2023-32200 Please adjust the affected versions in the BTS as needed.
Bug#1041106: qtbase-opensource-src-gles: CVE-2023-38197
Source: qtbase-opensource-src-gles X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for qtbase-opensource-src-gles. CVE-2023-38197[0]: | An issue was discovered in Qt before 5.15.15, 6.x before 6.2.10, and | 6.3.x through 6.5.x before 6.5.3. There are infinite loops in | recursive entity expansion. https://codereview.qt-project.org/c/qt/qtbase/+/488960 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-38197 https://www.cve.org/CVERecord?id=CVE-2023-38197 Please adjust the affected versions in the BTS as needed.
Bug#1041105: qtbase-opensource-src: CVE-2023-38197
Source: qtbase-opensource-src X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for qtbase-opensource-src. CVE-2023-38197[0]: | An issue was discovered in Qt before 5.15.15, 6.x before 6.2.10, and | 6.3.x through 6.5.x before 6.5.3. There are infinite loops in | recursive entity expansion. https://codereview.qt-project.org/c/qt/qtbase/+/488960 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-38197 https://www.cve.org/CVERecord?id=CVE-2023-38197 Please adjust the affected versions in the BTS as needed.
Bug#1041104: qt6-base: CVE-2023-38197
Source: qt6-base X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for qt6-base. CVE-2023-38197[0]: | An issue was discovered in Qt before 5.15.15, 6.x before 6.2.10, and | 6.3.x through 6.5.x before 6.5.3. There are infinite loops in | recursive entity expansion. https://codereview.qt-project.org/c/qt/qtbase/+/488960 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-38197 https://www.cve.org/CVERecord?id=CVE-2023-38197 Please adjust the affected versions in the BTS as needed.
Bug#1034590: precedence of /etc/containers/storage.conf should higher than /usr/share/containers/storage.conf
So | Before upgrade to 4.4.0+ds1-1 (4.3) | 4.4.0+ /etc/containers/strorage.conf | use btrfs | btrfs /usr/share/containers/storage.conf | use overlayfs | overlayfs When use 4.3, podman takes /etc/containers/storage.conf, so the storage is btrfs. But after upgrade 4.4.0+ (at least when it was April). Podman takes values in /usr/share/containers/storage.conf instead of /etc/containers/strorage.conf (wrong behavior) So just get the following User-selected graph driver \"overlay\" overwritten by graph driver \"btrfs\" from database That is the observed error. But not expected error. The expected behavior is Podman follows man 5 containers-storage.conf. Prefer values from /etc/containers/storage.conf. After version upgrade from 4.3 to 4.4, no configuration required, no reset required. Faidon Liambotis 於 2023/7/15 02:02 寫道: Control: tags -1 moreinfo On Wed, Apr 19, 2023 at 09:24:21AM +0800, 鐘翊修 wrote: following man 5 containers-storage.conf, when a system have both /etc/containers/storage.conf and /usr/share/containers/storage.conf the values in /etc/containers/storage.conf overwrite the value in /usr/share/containers/storage.conf But in 4.4.0+ds1-1. with both files, podman takes the config from /usr/share/containers/stroage.conf To reproduce this Create podman graph database on podman 4.3.1 with btrfs (config in /etc/containers/storage.conf) upgrade from 4.3.1 to 4.4.0 run the following command sudo podman info expected error message User-selected graph driver \"overlay\" overwritten by graph driver \"btrfs\" from database I'm not sure I follow. Could you elaborate on the exact steps you took? Do you mean that you expected to get this error message but didn't, or that you got that error message even though you shouldn't have? Are you aware that you need to run "podman system reset" before changing storage.conf? See podman-system-reset(1). Thanks, Faidon
Bug#1041101: wireshark: CVE-2023-3649 CVE-2023-3648
Source: wireshark X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerabilities were published for wireshark. CVE-2023-3649[0]: | iSCSI dissector crash in Wireshark 4.0.0 to 4.0.6 allows denial of | service via packet injection or crafted capture file https://www.wireshark.org/security/wnpa-sec-2023-22.html CVE-2023-3648[1]: | Kafka dissector crash in Wireshark 4.0.0 to 4.0.6 and 3.6.0 to | 3.6.14 allows denial of service via packet injection or crafted | capture file https://www.wireshark.org/security/wnpa-sec-2023-21.html If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-3649 https://www.cve.org/CVERecord?id=CVE-2023-3649 [1] https://security-tracker.debian.org/tracker/CVE-2023-3648 https://www.cve.org/CVERecord?id=CVE-2023-3648 Please adjust the affected versions in the BTS as needed.
Bug#1041103: libjpeg: CVE-2023-37836 CVE-2023-37837
Source: libjpeg X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerabilities were published for libjpeg. CVE-2023-37836[0]: | libjpeg commit db33a6e was discovered to contain a reachable | assertion via BitMapHook::BitMapHook at bitmaphook.cpp. This | vulnerability allows attackers to cause a Denial of Service (DoS) | via a crafted file. https://github.com/thorfdbg/libjpeg/issues/87#BUG1 Fixed by: https://github.com/thorfdbg/libjpeg/commit/9e0cea29d7ba7a2c1e763865391bc94b336da25e CVE-2023-37837[1]: | libjpeg commit db33a6e was discovered to contain a heap buffer | overflow via LineBitmapRequester::EncodeRegion at | linebitmaprequester.cpp. This vulnerability allows attackers to | cause a Denial of Service (DoS) via a crafted file. https://github.com/thorfdbg/libjpeg/issues/87#BUG0 Fixed by: https://github.com/thorfdbg/libjpeg/commit/9e0cea29d7ba7a2c1e763865391bc94b336da25e If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-37836 https://www.cve.org/CVERecord?id=CVE-2023-37836 [1] https://security-tracker.debian.org/tracker/CVE-2023-37837 https://www.cve.org/CVERecord?id=CVE-2023-37837 Please adjust the affected versions in the BTS as needed.
Bug#1041102: qemu: CVE-2023-3019
Source: qemu X-Debbugs-CC: t...@security.debian.org Severity: normal Tags: security Hi, The following vulnerability was published for qemu. CVE-2023-3019[0]: e1000e: heap use-after-free in e1000e_write_packet_to_guest() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=59243 Proposed upstream patch: https://lists.nongnu.org/archive/html/qemu-devel/2023-05/msg08310.html 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-3019 https://www.cve.org/CVERecord?id=CVE-2023-3019 Please adjust the affected versions in the BTS as needed.
Bug#1041100: ruby-commonmarker: CVE-2023-37463
Source: ruby-commonmarker X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for ruby-commonmarker. CVE-2023-37463[0]: | cmark-gfm is an extended version of the C reference implementation | of CommonMark, a rationalized version of Markdown syntax with a | spec. Three polynomial time complexity issues in cmark-gfm may lead | to unbounded resource exhaustion and subsequent denial of service. | These vulnerabilities have been patched in 0.29.0.gfm.12. https://github.com/github/cmark-gfm/security/advisories/GHSA-w4qg-3vf7-m9x5 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-37463 https://www.cve.org/CVERecord?id=CVE-2023-37463 Please adjust the affected versions in the BTS as needed.
Bug#1041099: r-cran-commonmark: CVE-2023-37463
Source: r-cran-commonmark X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for r-cran-commonmark. CVE-2023-37463[0]: | cmark-gfm is an extended version of the C reference implementation | of CommonMark, a rationalized version of Markdown syntax with a | spec. Three polynomial time complexity issues in cmark-gfm may lead | to unbounded resource exhaustion and subsequent denial of service. | These vulnerabilities have been patched in 0.29.0.gfm.12. https://github.com/github/cmark-gfm/security/advisories/GHSA-w4qg-3vf7-m9x5 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-37463 https://www.cve.org/CVERecord?id=CVE-2023-37463 Please adjust the affected versions in the BTS as needed.
Bug#1041098: python-cmarkgfm: CVE-2023-37463
Source: python-cmarkgfm X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for python-cmarkgfm. CVE-2023-37463[0]: | cmark-gfm is an extended version of the C reference implementation | of CommonMark, a rationalized version of Markdown syntax with a | spec. Three polynomial time complexity issues in cmark-gfm may lead | to unbounded resource exhaustion and subsequent denial of service. | These vulnerabilities have been patched in 0.29.0.gfm.12. https://github.com/github/cmark-gfm/security/advisories/GHSA-w4qg-3vf7-m9x5 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-37463 https://www.cve.org/CVERecord?id=CVE-2023-37463 Please adjust the affected versions in the BTS as needed.
Bug#1041097: cmark-gfm: CVE-2023-37463
Source: cmark-gfm X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security Hi, The following vulnerability was published for cmark-gfm. CVE-2023-37463[0]: | cmark-gfm is an extended version of the C reference implementation | of CommonMark, a rationalized version of Markdown syntax with a | spec. Three polynomial time complexity issues in cmark-gfm may lead | to unbounded resource exhaustion and subsequent denial of service. | These vulnerabilities have been patched in 0.29.0.gfm.12. https://github.com/github/cmark-gfm/security/advisories/GHSA-w4qg-3vf7-m9x5 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-37463 https://www.cve.org/CVERecord?id=CVE-2023-37463 Please adjust the affected versions in the BTS as needed.
Bug#1041096: raspi-firmware: kernel removal can render raspi unbootable
Package: raspi-firmware Version: 1.20230405+ds-1 Severity: important Dear Maintainer, When removing a no-longer-in-use kernel recently, the raspi-firmware postrm script, presumably the fact that this line [1] is not executed on kernel removals, left me with a /boot/firmware/config.txt containing the line kernel=auto which in turn left the Raspi (Model 4B in case it matters) firmware very confused, and the machine unbootable. Andreas [1] https://salsa.debian.org/debian/raspi-firmware/-/blob/9cafcd85f8aed1ec0c0f609b98af591fae367ba2/debian/kernel/postinst.d/z50-raspi-firmware#L128 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages raspi-firmware depends on: ii dosfstools 4.2-1 ii dpkg1.21.22 raspi-firmware recommends no packages. Versions of packages raspi-firmware suggests: pn bluez-firmware pn firmware-brcm80211 ii firmware-misc-nonfree 20230515-3
Bug#1041095: Please drop installable-field-mirrors-source warning
Package: lintian Version: 2.116.3 Severity: normal Over the last couple of years I've received several MRs on salsa (via the Janitor) as a result of lintian's installable-field-mirrors-source. As an example see https://salsa.debian.org/utopia-team/libnma/-/merge_requests?scope=all=all I consider this behaviour of lintian wrong. If I have a src package that builds multiple binary packages and I'm looking at debian/contol, I do want to immediately see which section a package belongs too without having to skip back to the source package. This lintian warning is a false optimization. Please drop it or at least restrict it to packages building a singly binary package. Michael
Bug#1040955: linux-image-6.1.0-10-amd64 | drm/i915 Intel GFX Driver crashes kernel
Hi Víctor Thanks for your response. On Fri, Jul 14, 2023 at 11:16:04AM -0300, Victor A. Bettachini wrote: > Hi Salvatore, > > Sorry, but I'll not provide help following either of your > suggestions. > > Regarding testing in current or experimental branch, I need to keep this > machine sticked to the stable branch. The idea would have been to just install the linux-image-* package without other changes, and witouth removing the package from stable, then rolling back to the previous booted kernel and remove the image if desired. But I can understand. It would only have been helpful to further identify if the current stable versions up are affected or if the issue is resolved there. Regards, Salvatore
Bug#1041094: Xserver.1: some remarks and editorial fixes for the manual
Package: xserver-common
Version: 2:21.1.7-3
Severity: minor
Tags: patch
Dear Maintainer,
here are some notes and editrorial fixes for the man page.
The patch is in the attachment.
-.-.
The difference between the formatted outputs can be seen with:
nroff -man -t >
nroff -man -t >
diff -u
and for groff, using
"groff -man -t -Z" instead of "nroff -man"
Read the output of "diff -u" with "less -R" or similar.
-.-.
If "man" (man-db) is used to check the manual,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-.
Change '-' (\-) to '\(en' (en-dash) for a numeric range.
Xserver.1:121:sets key-click volume (allowable range: 0-100).
Xserver.1:165:sets beep (bell) volume (allowable range: 0-100).
Xserver.1:168:sets fake presenter screen default fps (allowable range: 1-600).
-.-.
Mark a full stop (.) and the exclamation mark (!) with "\&",
if it does not mean an end of a sentence.
This is a preventive action,
the paragraph could be reshaped, e.g., after changes.
When typing, one does not always notice when the line wraps after the
period.
There are too many examples of input lines in manual pages,
that end with an abbreviation point.
This marking is robust, and independent of the position on the line.
It corresponds to "\ " in TeX, and to "@:" in Texinfo.
57:devices (e.g. \fI/dev/mouse\fP) is restricted. Where applicable, the
81:sets pointer acceleration (i.e. the ratio of how much is reported to how much
106:May be useful for smooth transition with eg. fbdev driver.
266:sets pointer acceleration threshold in pixels (i.e. after how many pixels
406:X servers that support the XKEYBOARD (a.k.a. \*qXKB\*q) extension accept the
461:contain either an Internet hostname (e.g. expo.lcs.mit.edu)
-.-.
Change - to \- if it shall be printed as a minus sign.
Xserver.1:299:enables(+) or disables(-) the XINERAMA extension. The default
state is
Xserver.1:413:enables(+) or disables(-) AccessX key sequences.
-.-.
Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.
112:pattern. This is the default unless -retro or -wr is specified.
247:.B -retro
251:servers, this implies -zap.
-.-.
Strings longer than 3/4 of a standard line length (80)
527
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins
.
-.-.
Add a comma (or \&) after "e.g." and "i.e.", or use English words
(man-pages(7).
Abbreviation points should be protected against being interpreted as
an end of sentence, if they are not, and that independent of the
current place on the line.
57:devices (e.g. \fI/dev/mouse\fP) is restricted. Where applicable, the
81:sets pointer acceleration (i.e. the ratio of how much is reported to how much
266:sets pointer acceleration threshold in pixels (i.e. after how many pixels
461:contain either an Internet hostname (e.g. expo.lcs.mit.edu)
-.-.
Wrong distance between sentences.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
N.B
The number of lines affected is too large to be in the patch.
57:devices (e.g. \fI/dev/mouse\fP) is restricted. Where applicable, the
81:sets pointer acceleration (i.e. the ratio of how much is reported to how much
106:May be useful for smooth transition with eg. fbdev driver.
112:pattern. This is the default unless -retro or -wr is specified.
157:disables named extension. If an unknown extension name is specified,
161:enables named extension. If an unknown extension name is specified,
250:until the first time an application calls XDefineCursor(). For kdrive
260:seat to run on. Takes a string identifying a seat in a platform
261:specific syntax. On platforms which support this feature this may be
266:sets pointer acceleration threshold in pixels (i.e. after how many pixels
275:the delay. At the end of this grace period if no client is
406:X servers that support the XKEYBOARD (a.k.a. \*qXKB\*q) extension accept the
461:contain either an Internet hostname (e.g. expo.lcs.mit.edu)
530:prefix. Directories specified this way can contain symlinks pointing to the
531:real font directories. See the FONTPATH.D section for
Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user
Control: forwarded -1 https://lists.nongnu.org/archive/html/qemu-devel/2023-07/msg03138.html 14.07.2023 23:07, Thorsten Glaser wrote: Michael Tokarev dixit: commit 6fd5944980f4ccee728ce34bdaffc117db50b34d From the comment, it reserves 16 MiB after the main executable. In klibc/armhf, however, the main executable starts around 0x0001 whereas the interpreter starts after that, around 0x0038… Aren't it happens on all architectures, not just armhf? I had an impression it is not arch-specific. $subject mentions armhf only, but I think somewhere in the discussion it's been said all architectures are affected? Ok. Perhaps the fix here would be to see if the interpreter comes within 16 MiB past the main executable’s end, and if so, to move the break (I wasn’t aware stuff on GNU/Linux still uses that!) to start after the interpreter instead. The BSD manpage begins with… DESCRIPTION The brk() and sbrk() functions are historical curiosities left over from earlier days before the advent of virtual memory management. … so… oh well. That's lovely. There's another change for brk() pending in qemu right now (to make it page-aligned; and no, it does not fix this issue). I guess it is not just curiocities :) Anyway, while my proposed fix in theory moves the “end of the process’ data segment” to behind the interpreter instead of behind the main executable, processes are not supposed to use it in combination with _end, only the returned pointers. It’s something to at least consider. Will you forward this upstream? Yeah, already did, was just waiting for it to appear in the archives for the URL. Thank you! /mjt
Bug#1037437: From fresh bookworm install default sshd jail in fail2ban won’t work
Thank you José, I really appreciate you taking the time to confirm. Hope you have a great day! :) Regards, Jeremy On 14/7/23 08:45, José Miguel Gonçalves wrote: Hi Jeremy, On 13/07/23 23:01, Jeremy Davis wrote: Can you confirm that the current default bookworm fail2ban config/regex works with sshd with just this change (to 'backend' in /etc/fail2ban/jail.conf)? Or are further adjustments required? Yes, I can confirm that fail2ban sshd jail works fine using the default config and just changing the 'backend' to 'systemd'. Best regards, José Gonçalves OpenPGP_signature Description: OpenPGP digital signature
Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user
Michael Tokarev dixit: > commit 6fd5944980f4ccee728ce34bdaffc117db50b34d From the comment, it reserves 16 MiB after the main executable. In klibc/armhf, however, the main executable starts around 0x0001 whereas the interpreter starts after that, around 0x0038… Perhaps the fix here would be to see if the interpreter comes within 16 MiB past the main executable’s end, and if so, to move the break (I wasn’t aware stuff on GNU/Linux still uses that!) to start after the interpreter instead. The BSD manpage begins with… DESCRIPTION The brk() and sbrk() functions are historical curiosities left over from earlier days before the advent of virtual memory management. … so… oh well. Anyway, while my proposed fix in theory moves the “end of the process’ data segment” to behind the interpreter instead of behind the main executable, processes are not supposed to use it in combination with _end, only the returned pointers. It’s something to at least consider. Will you forward this upstream? Given how this both constraints executables’ sizes and perhaps has effects on other loaders, perhaps the klibc upstream could consider switching to using linker scripts or at least move the respective text basēs, on all architectures, so that the main executable comes after the interpreter. This will of course not help bookworm users but, perhaps, it is something, again, to consider, at least. bye, //mirabilos -- This space for rent. https://paypal.me/mirabilos to support my work.
Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user
14.07.2023 21:34, Thorsten Glaser wrote: .. And, indeed, the combination of klibc-sKNr1Fw-Rh9G1FYpGCXRnrwmP2A.so and fstype from 2.0.4-2 (jessie) also fails, so you have something that can reliably be used in bisect tests I think. Ok, this works. The bisection points to this commit between qemu v4.2.0 and v5.0.0: https://gitlab.com/qemu-project/qemu/-/commit/6fd5944980f4ccee728ce34bdaffc117db50b34d commit 6fd5944980f4ccee728ce34bdaffc117db50b34d Author: Richard Henderson Date: Fri Jan 17 13:02:45 2020 -1000 linux-user: Reserve space for brk With bad luck, we can wind up with no space at all for brk, which will generally cause the guest malloc to fail. This bad luck is easier to come by with ET_DYN (PIE) binaries, where either the stack or the interpreter (ld.so) gets placed immediately after the main executable. But there's nothing preventing this same thing from happening with ET_EXEC (normal) binaries, during probe_guest_base(). In both cases, reserve some extra space via mmap and release it back to the system after loading the interpreter and allocating the stack. The choice of 16MB is somewhat arbitrary. It's enough for libc to get going, but without being so large that 32-bit guests or 32-bit hosts are in danger of running out of virtual address space. It is expected that libc will be able to fall back to mmap arenas after the limited brk space is exhausted. Launchpad: https://bugs.launchpad.net/qemu/+bug/1749393 Signed-off-by: Richard Henderson Reviewed-by: Alex Bennée Tested-by: Alex Bennée Message-Id: <20200117230245.5040-1-richard.hender...@linaro.org> Signed-off-by: Laurent Vivier Does this ring any bells? Verified on armhf. I'll bug upstream. Thanks, /mjt
Bug#1036904: libreoffice 7.4.7-1 flagged for acceptance
package release.debian.org tags 1036904 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: libreoffice Version: 7.4.7-1 Explanation: new upstream bugfix release
Bug#1041093: ITP: golang-github-go-zookeeper-zk -- native ZooKeeper client for Go
Package: wnpp Severity: wishlist Owner: Daniel Swarbrick X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: golang-github-go-zookeeper-zk Version : 1.0.3-1 Upstream Contact: The Go-ZooKeeper Developers * URL : https://github.com/go-zookeeper/zk * License : BSD-3-clause Programming Lang: Go Description : native ZooKeeper client for Go Native Go ZooKeeper Client Library. This is (yet another) fork of the original g/samuel/go-zookeeper package, and is a build-dep of Prometheus (which currently uses a patch to build against the original g/samuel/go-zookeeper). Since the original g/samuel/go-zookeeper is now abandoned / archived, g-g-samuel-go-zookeeper-dev could eventually become a dummy transitional package for g-g-go-zookeeper-zk-dev, with symlinks. I will co-maintain this package as a member of the Debian Go Packaging Team.
Bug#1040953: bookworm-pu: package sra-sdk/3.0.3+dfsg-6~deb12u1
On Fri, 2023-07-14 at 15:09 -0400, Aaron M. Ucko wrote: > "Adam D. Barratt" writes: > > > FWIW the auto-generated debdiff disagrees - > > https://release.debian.org/proposed-updates/bookworm_diffs/sra-sdk_3.0.3+dfsg-6~deb12u1.debdiff > > Please clear the path for another 3.0.3+dfsg-6~deb12u1 upload, > thanks. > Thanks for the quick follow-up. I've flagged the current upload for rejection. Feel free to re-upload once that gets actioned. Regards, Adam
Bug#1041091: python3-virtualenv: re-execution of virtualenv command removes python-debian's debian directory
Package: python3-virtualenv Version: 20.17.1+ds-1 Severity: important Hi, as funny as the subject might sound, this took a while to track down. :) Reporting this, since this might bite other folks as well, and I also have STR. The behavior that was present until and incl. bullseye was as follows (newlines between command lines added by myself to make it easier to read/parse/follow): | % podman run --pull=always --rm -i -t debian:bullseye bash | root@9b5d718485de:/# cd | root@9b5d718485de:~# apt update ; apt -y install python3-virtualenv | [...] | root@9b5d718485de:~# virtualenv --python=python3 virtualenv | created virtual environment CPython3.9.2.final.0-64 in 162ms | creator CPython3Posix(dest=/root/virtualenv, clear=False, no_vcs_ignore=False, global=False) | seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv) | added seed packages: pip==20.3.4, pkg_resources==0.0.0, setuptools==44.1.1, wheel==0.34.2 | activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator | | root@9b5d718485de:~# . virtualenv/bin/activate | | (virtualenv) root@9b5d718485de:~# pip install python-debian | Collecting python-debian | Downloading python_debian-0.1.49-py3-none-any.whl (132 kB) | || 132 kB 5.9 MB/s | Collecting chardet | Downloading chardet-5.1.0-py3-none-any.whl (199 kB) | || 199 kB 18.4 MB/s | Installing collected packages: chardet, python-debian | Successfully installed chardet-5.1.0 python-debian-0.1.49 | | (virtualenv) root@9b5d718485de:~# python3 -c "from debian import deb822" | | (virtualenv) root@9b5d718485de:~# virtualenv --python=python3 virtualenv | created virtual environment CPython3.9.2.final.0-64 in 142ms | creator CPython3Posix(dest=/root/virtualenv, clear=False, no_vcs_ignore=False, global=False) | seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv) | added seed packages: chardet==5.1.0, pip==20.3.4, pkg_resources==0.0.0, python_debian==0.1.49, setuptools==44.1.1, wheel==0.34.2 | activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator | | (virtualenv) root@9b5d718485de:~# python3 -c "from debian import deb822" So everything fine, no problems. But on bookworm, this doesn't behave as such any longer: | % podman run --pull=always --rm -i -t debian:bookworm bash | root@491ed520fc26:/# cd | root@491ed520fc26:~# apt update ; apt -y install python3-virtualenv | [...] | root@491ed520fc26:~# virtualenv --python=python3 virtualenv | created virtual environment CPython3.11.2.final.0-64 in 439ms | creator CPython3Posix(dest=/root/virtualenv, clear=False, no_vcs_ignore=False, global=False) | seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv) | added seed packages: pip==23.0.1, setuptools==66.1.1, wheel==0.38.4 | activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator | | root@491ed520fc26:~# . virtualenv/bin/activate | | (virtualenv) root@491ed520fc26:~# pip install python-debian | Collecting python-debian | Downloading python_debian-0.1.49-py3-none-any.whl (132 kB) | 132.5/132.5 kB 3.7 MB/s eta 0:00:00 | Collecting chardet | Downloading chardet-5.1.0-py3-none-any.whl (199 kB) | 199.1/199.1 kB 6.5 MB/s eta 0:00:00 | Installing collected packages: chardet, python-debian | Successfully installed chardet-5.1.0 python-debian-0.1.49 | | (virtualenv) root@491ed520fc26:~# python3 -c "from debian import deb822" | | (virtualenv) root@491ed520fc26:~# virtualenv --python=python3 virtualenv | created virtual environment CPython3.11.2.final.0-64 in 341ms | creator CPython3Posix(dest=/root/virtualenv, clear=False, no_vcs_ignore=False, global=False) | seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv) | added seed packages: chardet==5.1.0, pip==23.0.1, python_debian==0.1.49, setuptools==66.1.1, wheel==0.38.4 | activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator | | (virtualenv) root@491ed520fc26:~# python3 -c "from debian import deb822" | Traceback (most recent call last): | File "", line 1, in | ModuleNotFoundError: No module named 'debian' So the re-execution of `virtualenv` for some reason removes the debian directory of python-debian on the filesystem. :-/ To highlight this from another run: | (virtualenv) root@b5d06fb7:~# ls virtualenv/lib/python3.11/site-packages/debian | __init__.py __pycache__ _arch_table.py _deb822_repro _util.py _version.py
Bug#1040841: texstudio: enable terminal build option
tags 1040841 + unreproducible thanks Hi Axel I remember your email and I've found it in my archive, it's from Oct 2021. I checked my git commits and found that I've activated the terminal with the upload of version 3.0.4+ds-2 in Oct 2021[1]. The internal terminal is still working for me with the current version in Bookworm (4.3.1+ds-2). I see the additional "Terminal" tab next to "Message", "Log", "Preview" and "Search Results" (as it is shown in your github pull request). When I start TeXstudio with a clean config, the Terminal tab is there as well. Sorry, I can't reproduce this. You say the tab is not visible when you start TeXstudio? And you don't see the config options if you enable advanced options? Kind regards Tom [1]: https://tracker.debian.org/news/1267252/accepted-texstudio-304ds-2-source-into-unstable/
Bug#1041092: cephadm: creates /etc/logrotate.d/cephadm leading to duplicate log entry
Package: cephadm
Version: 16.2.11+ds-2
Severity: normal
# systemctl status logrotate.service
systemd[1]: Starting logrotate.service - Rotate log files...
logrotate[90090]: error: ceph-common:1 duplicate log entry for
/var/log/ceph/cephadm.log
logrotate[90090]: error: found error in file ceph-common, skipping
systemd[1]: logrotate.service: Main process exited, code=exited,
status=1/FAILURE
systemd[1]: logrotate.service: Failed with result 'exit-code'.
systemd[1]: Failed to start logrotate.service - Rotate log files.
# grep -r ceph /etc/logrotate.d/
/etc/logrotate.d/cephadm:# created by cephadm
/etc/logrotate.d/cephadm:/var/log/ceph/cephadm.log {
/etc/logrotate.d/ceph-common:/var/log/ceph/*.log {
/etc/logrotate.d/ceph-common:killall -q -1 ceph-mon ceph-mgr ceph-mds
ceph-osd ceph-fuse radosgw rbd-mirror cephfs-mirror || pkill -1 -x
"ceph-mon|ceph-mgr|ceph-mds|ceph-osd|ceph-fuse|radosgw|rbd-mirror|cephfs-mirror"
|| true
/etc/logrotate.d/ceph-common:su root ceph
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (900, 'testing'), (900, 'stable'), (800, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cephadm depends on:
ii adduser 3.134
ii lvm2 2.03.16-2
ii python3 3.11.2-1+b1
Versions of packages cephadm recommends:
pn podman | docker.io
cephadm suggests no packages.
Bug#1040953: bookworm-pu: package sra-sdk/3.0.3+dfsg-6~deb12u1
"Adam D. Barratt" writes: > FWIW the auto-generated debdiff disagrees - > https://release.debian.org/proposed-updates/bookworm_diffs/sra-sdk_3.0.3+dfsg-6~deb12u1.debdiff Please clear the path for another 3.0.3+dfsg-6~deb12u1 upload, thanks. Sorry about that -- I'd compared against my -6 because that was handier on the relevant host, but my so-far customary workflow turned out to have yielded the same exclusion. I found a reasonably clean way of dropping the exclusion without needing a new tag: manually running dpkg-source -b . -Inonexistent I will look into adjusting my workflow to DTRT. -- 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#1040907: aerc: Freeze when pasting to body on email compose
On Fri, Jul 14, 2023 at 09:02:31PM +0200, Robin Jarry wrote: > Nilesh Patra, Jul 14, 2023 at 20:35: > > On Fri, Jul 14, 2023 at 08:13:16PM +0200, Robin Jarry wrote: > > > Nilesh Patra, Jul 14, 2023 at 19:59: > > > > There you go > > > > > > > > https://pb.envs.net/?816fb8c61575e2ba#4kD2xS4wJMGrsCd8tBhPfqHDJZ7qeM6qERaobgoYj46F > > > > > > Thanks a lot that helps. It looks like there is a deadlock due to two > > > goroutines trying to interact with the terminal: > > > > I'm going ahead with an upload in debian with this patch backported. > > From a distro pov I consider this a major breakeage. Given that aerc is > > designed to facilitate patch workflow as a goal, it makes it useless if > > I can't paste more than 4-5 lines in one go. > > > > If you disagree, feel free to revert the upload. You have the rights. > > Sure thing. It is certainly less risky than tagging a release in a rush. Thanks a lot for quick response and the patch! Best, Nilesh signature.asc Description: PGP signature
Bug#1040907: aerc: Freeze when pasting to body on email compose
On Fri Jul 14, 2023 at 1:35 PM CDT, Nilesh Patra wrote: > On Fri, Jul 14, 2023 at 08:13:16PM +0200, Robin Jarry wrote: > > Nilesh Patra, Jul 14, 2023 at 19:59: > > > There you go > > > > > > https://pb.envs.net/?816fb8c61575e2ba#4kD2xS4wJMGrsCd8tBhPfqHDJZ7qeM6qERaobgoYj46F > > > > Thanks a lot that helps. It looks like there is a deadlock due to two > > goroutines trying to interact with the terminal: > > I'm going ahead with an upload in debian with this patch backported. > From a distro pov I consider this a major breakeage. Given that aerc is > designed to facilitate patch workflow as a goal, it makes it useless if > I can't paste more than 4-5 lines in one go. I agree, this was a particularly bad breakage on this release. I think backporting this patch is a must. Thanks for backporting! -- Tim
Bug#1040907: aerc: Freeze when pasting to body on email compose
Nilesh Patra, Jul 14, 2023 at 20:35: > On Fri, Jul 14, 2023 at 08:13:16PM +0200, Robin Jarry wrote: > > Nilesh Patra, Jul 14, 2023 at 19:59: > > > There you go > > > > > > https://pb.envs.net/?816fb8c61575e2ba#4kD2xS4wJMGrsCd8tBhPfqHDJZ7qeM6qERaobgoYj46F > > > > Thanks a lot that helps. It looks like there is a deadlock due to two > > goroutines trying to interact with the terminal: > > I'm going ahead with an upload in debian with this patch backported. > From a distro pov I consider this a major breakeage. Given that aerc is > designed to facilitate patch workflow as a goal, it makes it useless if > I can't paste more than 4-5 lines in one go. > > If you disagree, feel free to revert the upload. You have the rights. Sure thing. It is certainly less risky than tagging a release in a rush.
Bug#1040854: tinyrpc autopkg test fail with setuptools 68
Package: python-tinyrpc
Version: 0.6-4
Followup-For: Bug #1040854
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
Control: tags -1 patch
Hi Ben,
Please find attached a patch that ports the tinyrpc autopkgtest from
pkg_resources to importlib.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru python-tinyrpc-0.6/debian/tests/smoke_test.py
python-tinyrpc-0.6/debian/tests/smoke_test.py
--- python-tinyrpc-0.6/debian/tests/smoke_test.py 2022-05-03
20:58:15.0 -0700
+++ python-tinyrpc-0.6/debian/tests/smoke_test.py 2023-07-14
11:44:59.0 -0700
@@ -21,7 +21,7 @@
import sys
import argparse
import importlib
-import pkg_resources
+from importlib.metadata import metadata
def emit_implementation():
@@ -40,7 +40,7 @@
:param name: Name of the distribution to retrieve.
:return: ``None``.
"""
-distribution = pkg_resources.get_distribution(name)
+distribution = metadata(name)['Name']
sys.stdout.write(
"Distribution ‘{name}’:\n\t{distribution!r}\n".format(
name=name, distribution=distribution))
Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user
Ben Hutchings dixit: >7.2. This introduced regressions for shared-library executables for I did notice the following: amd64: /lib/klibc-YUkGbOClhnaZRUUd4cUed0X2XZI.so: file format elf64-x86-64 /lib/klibc-YUkGbOClhnaZRUUd4cUed0X2XZI.so architecture: i386:x86-64, flags 0x0102: EXEC_P, D_PAGED start address 0x00201034 Program Header: LOAD off0x vaddr 0x0020 paddr 0x0020 align 2**12 filesz 0x01b4 memsz 0x01b4 flags r-- LOAD off0x1000 vaddr 0x00201000 paddr 0x00201000 align 2**12 filesz 0xcf07 memsz 0xcf07 flags r-x LOAD off0xe000 vaddr 0x0020e000 paddr 0x0020e000 align 2**12 filesz 0x3f6f memsz 0x3f6f flags r-- LOAD off0x00012000 vaddr 0x00212000 paddr 0x00212000 align 2**12 filesz 0x0140 memsz 0x4438 flags rw- NOTE off0x0190 vaddr 0x00200190 paddr 0x00200190 align 2**2 filesz 0x0024 memsz 0x0024 flags r-- STACK off0x vaddr 0x paddr 0x align 2**4 filesz 0x memsz 0x flags rwx Sections: Idx Name Size VMA LMA File off Algn 0 .note.gnu.build-id 0024 00200190 00200190 0190 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .text cf07 00201000 00201000 1000 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE […] Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x00 0x0020 0x0020 0x0001b4 0x0001b4 R 0x1000 LOAD 0x001000 0x00201000 0x00201000 0x00cf07 0x00cf07 R E 0x1000 LOAD 0x00e000 0x0020e000 0x0020e000 0x003f6f 0x003f6f R 0x1000 LOAD 0x012000 0x00212000 0x00212000 0x000140 0x004438 RW 0x1000 NOTE 0x000190 0x00200190 0x00200190 0x24 0x24 R 0x4 GNU_STACK 0x00 0x 0x 0x00 0x00 RWE 0x10 Section to Segment mapping: Segment Sections... 00 .note.gnu.build-id 01 .text 02 .rodata 03 .data .bss 04 .note.gnu.build-id armhf: /lib/klibc-m13AniKHUCMUNN8mXSUhIi8CUSA.so: file format elf32-littlearm /lib/klibc-m13AniKHUCMUNN8mXSUhIi8CUSA.so architecture: armv7, flags 0x0102: EXEC_P, D_PAGED start address 0x003800f9 Program Header: LOAD off0x vaddr 0x0038 paddr 0x0038 align 2**12 filesz 0xcecf memsz 0xcecf flags r-x LOAD off0xd000 vaddr 0x0038d000 paddr 0x0038d000 align 2**12 filesz 0x00b8 memsz 0x2254 flags rw- NOTE off0x00b4 vaddr 0x003800b4 paddr 0x003800b4 align 2**2 filesz 0x0024 memsz 0x0024 flags r-- STACK off0x vaddr 0x paddr 0x align 2**4 filesz 0x memsz 0x flags rw- private flags = 5000400: [Version5 EABI] [hard-float ABI] Sections: Idx Name Size VMA LMA File off Algn 0 .note.gnu.build-id 0024 003800b4 003800b4 00b4 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .text 9974 003800d8 003800d8 00d8 2**3 CONTENTS, ALLOC, LOAD, READONLY, CODE […] Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x00 0x0038 0x0038 0x0cecf 0x0cecf R E 0x1000 LOAD 0x00d000 0x0038d000 0x0038d000 0x000b8 0x02254 RW 0x1000 NOTE 0xb4 0x003800b4 0x003800b4 0x00024 0x00024 R 0x4 GNU_STACK 0x00 0x 0x 0x0 0x0 RW 0x10 Section to Segment mapping: Segment Sections... 00 .note.gnu.build-id .text .rodata 01 .data .bss 02 .note.gnu.build-id Specifically, what I noted is that, on amd64, the .text section inside the text segment, which here isn’t shared with the buildid section, has a page align increment from .note.gnu.build-id but the armhf one doesn’t. So I added -Ttext 0x381000 to the link command, to get… Sections: Idx Name Size VMA LMA File off Algn 0 .text 997c 00381000 00381000 1000 2**3 CONTENTS, ALLOC, LOAD, READONLY, CODE 1 .note.gnu.build-id 0024 003800b4 003800b4 00b4 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA […] … but the segfault persists, so maybe that’s not it, or that’s not yet enough and we have to use a linker script to put the buildid section inside its own segment like it does on amd64. The
Bug#1040907: aerc: Freeze when pasting to body on email compose
On Fri, Jul 14, 2023 at 08:13:16PM +0200, Robin Jarry wrote: > Nilesh Patra, Jul 14, 2023 at 19:59: > > There you go > > > > https://pb.envs.net/?816fb8c61575e2ba#4kD2xS4wJMGrsCd8tBhPfqHDJZ7qeM6qERaobgoYj46F > > Thanks a lot that helps. It looks like there is a deadlock due to two > goroutines trying to interact with the terminal: I'm going ahead with an upload in debian with this patch backported. From a distro pov I consider this a major breakeage. Given that aerc is designed to facilitate patch workflow as a goal, it makes it useless if I can't paste more than 4-5 lines in one go. If you disagree, feel free to revert the upload. You have the rights. Best, Nilesh signature.asc Description: PGP signature
Bug#1041090: valijson FTBFS with googletest 1.13.0
Source: valijson Version: 1.0+repack-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/valijson.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /build/1st/valijson-1.0+repack/tests/test_fetch_absolute_uri_document_callback.cpp:2: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing the two -std=c++11 to -std=c++14 in CMakeLists.txt
Bug#1040907: aerc: Freeze when pasting to body on email compose
On Fri, Jul 14, 2023 at 11:22:09PM +0530, Nilesh Patra wrote: > I fiddled a bit and noticed that it works OK on aerc 0.14.0 and I notice > the odd behavior on aerc 0.15.0. > > Something changed between these two which causes it to explode. I did a bisect meanwhile and found the commit that broke it. Didn't review the diff but probably some race condition sneeked in somewhere. c7b122f4c4a87cd54402c78465e1a5c882f37aeb is the first bad commit commit c7b122f4c4a87cd54402c78465e1a5c882f37aeb Author: Tim Culverhouse Date: Sun Apr 23 08:01:23 2023 -0500 tcell-term: upgrade to latest release Upgrade tcell-term to latest release. This is a complete rewrite of tcell-term, and includes many minor bug fixes and overall improvements. Notably: - Improved parsing - One fewer goroutine - Improved API - Improved redraw messaging - Improved key support - Improved mouse support Signed-off-by: Tim Culverhouse Acked-by: Robin Jarry go.mod | 6 +++--- go.sum | 10 +++--- widgets/terminal.go | 35 +++ 3 files changed, 29 insertions(+), 22 deletions(-) Best, Nilesh signature.asc Description: PGP signature
Bug#1041089: thin-provisioning-tools FTBFS with googletest 1.13.0
Source: thin-provisioning-tools Version: 0.9.0-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/thin-provisioning-tools.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /usr/src/googletest/googletest/src/gtest-all.cc:38: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing the two -std=c++11 to -std=c++14 in unit-tests/Makefile.in
Bug#1040907: aerc: Freeze when pasting to body on email compose
Nilesh Patra, Jul 14, 2023 at 19:59:
> There you go
>
> https://pb.envs.net/?816fb8c61575e2ba#4kD2xS4wJMGrsCd8tBhPfqHDJZ7qeM6qERaobgoYj46F
Thanks a lot that helps. It looks like there is a deadlock due to two
goroutines trying to interact with the terminal:
goroutine 1 [sync.Mutex.Lock]:
sync.(*Mutex).Lock(...)
sync/mutex.go:90
git.sr.ht/~rockorager/tcell-term.(*VT).HandleEvent(0xc000158c80, {0xc5ce80?,
0xc0007fff60?})
git.sr.ht/~rockorager/tcell-term@v0.7.1/vt.go:452 +0x6d fp=0xc000a2db40
sp=0xc000a2dad8 pc=0x9a72cd
git.sr.ht/~rjarry/aerc/widgets.(*Terminal).Event(0xc000b26280?, {0xc5ce80?,
0xc0007fff60?})
git.sr.ht/~rjarry/aerc/widgets/terminal.go:189 +0x72 fp=0xc000a2db68
sp=0xc000a2db40 pc=0x9e72d2
git.sr.ht/~rjarry/aerc/widgets.(*Composer).Event(0xc000a2dc48?, {0xc5ce80?,
0xc0007fff60?})
git.sr.ht/~rjarry/aerc/widgets/compose.go:669 +0xcf fp=0xc000a2dbb8
sp=0xc000a2db68 pc=0x9c43af
git.sr.ht/~rjarry/aerc/widgets.(*Aerc).Event(0xc062e8?, {0xc5ce80?,
0xc0007fff60?})
git.sr.ht/~rjarry/aerc/widgets/aerc.go:316 +0xc3 fp=0xc000a2dc30
sp=0xc000a2dbb8 pc=0x9ba1a3
git.sr.ht/~rjarry/aerc/lib/ui.(*UI).HandleEvent(0xc4a040, {0xc5ce80?,
0xc0007fff60})
git.sr.ht/~rjarry/aerc/lib/ui/ui.go:150 +0x162 fp=0xc000a2dc80
sp=0xc000a2dc30 pc=0x6a79c2
main.main()
git.sr.ht/~rjarry/aerc/main.go:266 +0xb45 fp=0xc000a2df80
sp=0xc000a2dc80 pc=0xa32fe5
goroutine 102 [chan send]:
git.sr.ht/~rjarry/aerc/lib/ui.QueueRedraw(...)
git.sr.ht/~rjarry/aerc/lib/ui/ui.go:30
git.sr.ht/~rjarry/aerc/widgets.(*Terminal).HandleEvent(0x8?, {0xc5c140?,
0xc00094e850?})
git.sr.ht/~rjarry/aerc/widgets/terminal.go:168 +0x9c fp=0xc000435e38
sp=0xc000435e10 pc=0x9e71bc
git.sr.ht/~rjarry/aerc/widgets.(*Terminal).HandleEvent-fm({0xc5c140?,
0xc00094e850?})
:1 +0x39 fp=0xc000435e60 sp=0xc000435e38 pc=0x9e9fb9
git.sr.ht/~rockorager/tcell-term.(*VT).postEvent(...)
git.sr.ht/~rockorager/tcell-term@v0.7.1/vt.go:414
git.sr.ht/~rockorager/tcell-term.(*VT).update(0xc000158c80, {0xb119c0?,
0xc000b24940?})
git.sr.ht/~rockorager/tcell-term@v0.7.1/vt.go:195 +0x489
fp=0xc000435f80 sp=0xc000435e60 pc=0x9a50e9
git.sr.ht/~rockorager/tcell-term.(*VT).Start.func1()
git.sr.ht/~rockorager/tcell-term@v0.7.1/vt.go:165 +0x2d fp=0xc000435fe0
sp=0xc000435f80 pc=0x9a4b2d
runtime.goexit()
runtime/asm_amd64.s:1598 +0x1 fp=0xc000435fe8 sp=0xc000435fe0
pc=0x469781
created by git.sr.ht/~rockorager/tcell-term.(*VT).Start
git.sr.ht/~rockorager/tcell-term@v0.7.1/vt.go:155 +0x33c
It looks like a known issue that has been fixed by this commit:
https://git.sr.ht/~rjarry/aerc/commit/916bca33ea6cf2530117071fdd9b7b15e00e2f29
Not released yet.
Bug#1040907: aerc: Freeze when pasting to body on email compose
On Fri Jul 14, 2023 at 7:59 PM CEST, Nilesh Patra wrote:
> On Fri, Jul 14, 2023 at 07:47:33PM +0200, Robin Jarry wrote:
> > After aerc has died, share the trace.log file contents. Ideally via
> > paste service, lists.sr.ht bounce emails that have attachments.
>
> There you go
>
> https://pb.envs.net/?816fb8c61575e2ba#4kD2xS4wJMGrsCd8tBhPfqHDJZ7qeM6qERaobgoYj46F
I can reproduce the issue on the released version (0.15.2). However, it
seems fixed on current master. I think commit 9a20640f ("ui: avoid races
with queue redraw") fixed this issue as well.
If I read your log correctly, you are running 0.15.0. Could you maybe
try the latest master?
Bug#1041088: lomiri-download-manager FTBFS with googletest 1.13.0
Source: lomiri-download-manager Version: 0.1.2-1 Severity: serious Tags: ftbfs trixie sid Forwarded: https://gitlab.com/ubports/development/core/lomiri-download-manager/-/commit/a6bc7ae80f2ff4c4743978c6c694149707d9d2e2 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lomiri-download-manager.html ... In file included from /usr/src/googletest/googlemock/include/gmock/internal/gmock-port.h:57, from /usr/src/googletest/googlemock/include/gmock/internal/gmock-internal-utils.h:49, from /usr/src/googletest/googlemock/include/gmock/gmock-actions.h:145, from /usr/src/googletest/googlemock/include/gmock/gmock.h:56, from /build/1st/lomiri-download-manager-0.1.2/obj-x86_64-linux-gnu/tests/common/lomiri-download-manager-test-lib_autogen/EWIEGA46WW/../../../../../tests/common/dbus_connection.h:23, from /build/1st/lomiri-download-manager-0.1.2/obj-x86_64-linux-gnu/tests/common/lomiri-download-manager-test-lib_autogen/EWIEGA46WW/moc_dbus_connection.cpp:10, from /build/1st/lomiri-download-manager-0.1.2/obj-x86_64-linux-gnu/tests/common/lomiri-download-manager-test-lib_autogen/mocs_compilation.cpp:4: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ...
Bug#1034590: precedence of /etc/containers/storage.conf should higher than /usr/share/containers/storage.conf
Control: tags -1 moreinfo On Wed, Apr 19, 2023 at 09:24:21AM +0800, 鐘翊修 wrote: > following man 5 containers-storage.conf, > when a system have both /etc/containers/storage.conf and > /usr/share/containers/storage.conf > > the values in /etc/containers/storage.conf overwrite the value in > /usr/share/containers/storage.conf > > But in 4.4.0+ds1-1. with both files, podman takes the config from > /usr/share/containers/stroage.conf > > To reproduce this > > Create podman graph database on podman 4.3.1 with btrfs (config in > /etc/containers/storage.conf) > > upgrade from 4.3.1 to 4.4.0 > > run the following command > > sudo podman info > > expected error message > > User-selected graph driver \"overlay\" overwritten by graph driver \"btrfs\" > from database I'm not sure I follow. Could you elaborate on the exact steps you took? Do you mean that you expected to get this error message but didn't, or that you got that error message even though you shouldn't have? Are you aware that you need to run "podman system reset" before changing storage.conf? See podman-system-reset(1). Thanks, Faidon
Bug#1041087: libqtdbusmock FTBFS with googletest 1.13.0
Source: libqtdbusmock Version: 0.7+bzr49+repack1-5 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libqtdbusmock.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /build/1st/libqtdbusmock-0.7+bzr49+repack1/tests/main.cpp:21: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=c++11 to -std=c++14 in CMakeLists.txt
Bug#1040907: aerc: Freeze when pasting to body on email compose
On Fri, Jul 14, 2023 at 07:47:33PM +0200, Robin Jarry wrote: > After aerc has died, share the trace.log file contents. Ideally via > paste service, lists.sr.ht bounce emails that have attachments. There you go https://pb.envs.net/?816fb8c61575e2ba#4kD2xS4wJMGrsCd8tBhPfqHDJZ7qeM6qERaobgoYj46F Best, Nilesh signature.asc Description: PGP signature
Bug#1037091: podman run fails because of missing ~/.config/docker/config.json
On Sun, Jun 04, 2023 at 02:52:56PM +0200, Felix Stupp wrote: > the current version of podman does not allow me to run any container due > to the following error message: > Error: stat /home/$USER/.config/docker/config.json: no such file or directory > > I can trigger this issue with a simple: podman run debian > However, what container I try to run seems not to matter. > > [...] > > However, it still seems at least weird to me, that podman requires (not > just reads optionally) a config file which is in Docker's config dir. That is indeed weird. Is there any config (either in your .config, or in /etc) that has been modified in your system? For example, do you perhaps have a registry configured, and one that requires a login? An unqualified "podman run debian" could try to resolve this to your local registry, which in turn may require a login, which implicitly calls "podman login", which in turn attempts to read from a variety of config paths, including $HOME/.docker/config.json. Regards, Faidon
Bug#1041086: orthanc-dicomweb FTBFS with googletest 1.13.0
Source: orthanc-dicomweb Version: 1.7+dfsg-6 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/orthanc-dicomweb.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /usr/src/gtest/src/gtest-all.cc:38: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ...
Bug#1041085: printer-driver-cups-pdf: /usr/lib/cups/backend/cups-pdf crashes with signal 11 and no additional information.
Package: printer-driver-cups-pdf
Version: 3.0.1-14
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Installed with apt.
Modified cups-pdf.conf to print to ${HOME}/tmp/cups-pdf
Attempt to print.
"Backend failed"
Increased cupsd.conf LogLevel to "debug"
Attempt to print.
"Backend failed"
Deleted PDF printer from cups
Forced reinstall of printer-driver-cups-pdf
Attempt to print.
"Backend failed"
Remove edit from cups-pdf.conf (e.g. back to default destination)
Attempt to print.
"Backend failed"
Attempt to find command line invocation in order to perhaps see a more useful
error message.
invoke:
# lpstat -p -d
printer isxerox-8145 is idle. enabled since Fri 14 Jul 2023 12:54:50 PM EDT
printer PDF is idle. enabled since Fri 14 Jul 2023 01:24:33 PM EDT
Backend failed
system default destination: PDF
Most information from /var/log/cups/error_log:
D [14/Jul/2023:12:59:27 -0400] [Job 7] PID 963955
(/usr/lib/cups/filter/pdftops) exited with no errors.
D [14/Jul/2023:12:59:27 -0400] [Job 7] PID 963956
(/usr/lib/cups/backend/cups-pdf) crashed on signal 11.
W [14/Jul/2023:12:59:27 -0400] [Job 7] Backend returned status -139 (crashed)
A little frustrating because there is so little information; but I will happily
execute anything you request.
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable'), (100,
'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages printer-driver-cups-pdf depends on:
ii cups2.4.2-3
ii cups-client 2.4.2-3
ii ghostscript 10.0.0~dfsg-11+deb12u1
ii libc6 2.36-9
ii libcups22.4.2-3
ii libpaper-utils 1.1.29
printer-driver-cups-pdf recommends no packages.
Versions of packages printer-driver-cups-pdf suggests:
ii system-config-printer 1.5.18-1
-- Configuration Files:
/etc/cups/cups-pdf.conf changed [not included]
-- no debconf information
Bug#1041084: zim-tools FTBFS with googletest 1.13.0
Source: zim-tools Version: 3.1.3-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zim-tools.html ... /tools-test.cpp.o.d -o test/tools-test.p/tools-test.cpp.o -c ../test/tools-test.cpp In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from ../test/tools-test.cpp:1: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing cpp_std=c++11 to cpp_std=c++14 in meson.build
Bug#1041083: libqtdbustest FTBFS with googletest 1.13.0
Source: libqtdbustest Version: 0.2+bzr42+repack1-14 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libqtdbustest.html ... In file included from /usr/src/googletest/googlemock/include/gmock/internal/gmock-port.h:57, from /usr/src/googletest/googlemock/include/gmock/internal/gmock-internal-utils.h:49, from /usr/src/googletest/googlemock/include/gmock/gmock-actions.h:145, from /usr/src/googletest/googlemock/include/gmock/gmock.h:56, from /build/1st/libqtdbustest-0.2+bzr42+repack1/tests/libqtdbustest/TestQProcessDBusService.cpp:22: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=c++11 to -std=c++14 in CMakeLists.txt
Bug#1040907: aerc: Freeze when pasting to body on email compose
I fiddled a bit and noticed that it works OK on aerc 0.14.0 and I notice the odd behavior on aerc 0.15.0. Something changed between these two which causes it to explode. Best, Nilesh signature.asc Description: PGP signature
Bug#1040907: aerc: Freeze when pasting to body on email compose
If you manage to reproduce this easily, could you try the following: 1) aerc >trace.log 2>&1 2) Compose a message reproduce the freeze. 3) From another terminal, kill aerc with SIGQUIT. After aerc has died, share the trace.log file contents. Ideally via paste service, lists.sr.ht bounce emails that have attachments. Thanks
Bug#1040907: aerc: Freeze when pasting to body on email compose
Nilesh Patra, Jul 14, 2023 at 19:14: > Are you using debian though? No, I am on Fedora 38. Linux ringo 6.3.11-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jul 2 13:17:31 UTC 2023 x86_64 GNU/Linux go version go1.20.5 linux/amd64 sway version 1.8.1 foot version: 1.14.0 -pgo +ime +graphemes -assertions aerc 0.15.2-96-gae07f640371e +notmuch (go1.20.5 amd64 linux) NVIM v0.9.1 Build type: RelWithDebInfo LuaJIT 2.1.0-beta3 Compilation: /usr/bin/gcc -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wvla -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -fno-common -Wno-unused-result -Wimplicit-fallthrough -fdiagnostics-color=auto -fstack-protector-strong -DUNIT_TESTING -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -I/usr/include/luajit-2.1 -I/usr/include -I/usr/include/luv -I/builddir/build/BUILD/neovim-0.9.1/redhat-linux-build/src/nvim/auto -I/builddir/build/BUILD/neovim-0.9.1/redhat-linux-build/include -I/builddir/build/BUILD/neovim-0.9.1/redhat-linux-build/cmake.config -I/builddir/build/BUILD/neovim-0.9.1/src -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include
