Bug#989029: info: scroll-backward is buggy
Am 24.05.2021 um 01:36 teilte Vincent Lefevre mit: Hi, The info manual says: ('scroll-backward') Shift the text in this window down. The inverse of 'scroll-forward'. If you are at the start of a node, takes you to the "previous" node, so that you can read an entire manual from finish to start by repeating . The default scroll size can be changed by invoking the ('scroll-backward-page-only-set-window') command with a numeric argument. [...] Did the situation improve in 6.8? Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Bug#1003924: indi: reproducible-builds: BuildId differences triggered by RPATH
Source: indi Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/indi.html The attached patch to debian/rules passes -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override, which should use a relative path for RPATH. Alternately, updating the packaging to debhelper compat level 14 should fix this, although it is currently an experimental compat level. With this patch applied, indi should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining indi! live well, vagrant From c917fc3f34b19883752b7894f9f2219ff1e52e83 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Tue, 18 Jan 2022 06:54:57 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index bd1224a..3cfe5e7 100755 --- a/debian/rules +++ b/debian/rules @@ -8,3 +8,6 @@ include /usr/share/pkg-kde-tools/qt-kde-team/2/library-packages.mk override_dh_gencontrol-arch: libpkgs_gen_strict_local_shlibs dh_gencontrol -a + +override_dh_auto_configure: + dh_auto_configure -- -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON -- 2.34.1 signature.asc Description: PGP signature
Bug#1003923: soundkonverter: reproducible-builds: BuildId differences triggered by RPATH
Source: soundkonverter Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/soundkonverter.html The attached patch to debian/rules passes -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override, which should use a relative path for RPATH. Alternately, updating the packaging to debhelper compat level 14 should fix this, although it is currently an experimental compat level. With this patch applied, soundkonverter should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining soundkonverter! live well, vagrant From e47199bb76454355ee880bd4c98e53fae3a4fd66 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Tue, 18 Jan 2022 06:39:05 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index 1735662..eeb8510 100755 --- a/debian/rules +++ b/debian/rules @@ -8,3 +8,6 @@ execute_after_dh_auto_install: override_dh_installchangelogs: dh_installchangelogs src/CHANGELOG + +override_dh_auto_configure: + dh_auto_configure -- -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON -- 2.34.1 signature.asc Description: PGP signature
Bug#996540: Post install fails when run as non-root user and does not respect PKG_ROOT
On Mon, 17 Jan 2022 09:10:52 +0100 Johannes Schauer Marin Rodrigues wrote: > Quoting Glenn Washburn (2022-01-17 08:42:24) > > I'll restate my use case briefly here. The use case is installing packages > > as > > an unprivileged user to a user writable location (I don't have privileges on > > this machine and can't chroot). This can be done by invoking the dpkg binary > > with the "--force-script-chrootless" option and works, but the post install > > fails. > > And just as I told you in that other bug, you can achieve that same thing > without being root by using either fakechroot or by unsharing the user > namespace. But you definitely have privileges for the former. Chroot is a semantic I'e been trying to avoid because I'm wanting to use the main filesystem as much as possible (ie only install what's not already installed on the main system). I believe unprivileged overlayfs is what I want. I could use overlayfs in UML, but so far trying to avoid that as a dependency. I believe Ubuntu has a patch for this, but I don't think its been accepted to mainline yet. So here I am. > We don't need to put support allowing maintainer scripts to be run as another > user as the root user if there are mechanisms that can fake the root user. For > good reasons package maintainers are cautious when it's about increasing the > complexity of their maintainer scripts and it should only be done when it's > absolutely necessary. Yes, I've heard this before. Probably at a minimum this should be documented in the dpkg debian man page, perhaps under script-chrootless or DPKG_ROOT, noting that that not all distro packages honor this method of package install. > The final decision of course lies with the texinfo maintainers and not me. I'm > just explaining for you (again) why this is not needed. Just have a look at > the > mmdebstrap code and how it fakes being root to create chroot tarballs without > any root privileges. Take that code and use it for your own project and you > will not have to file another of these bugs as all packages will just > magically > work without any changes. If you need help understanding how mmdebstrap does > what it does I (again) offer you my help. Thank you Josch. I don't believe this can help me because of the afore mentioned issue with chroot. Am I mistaken? You can take this discussion off the bug list if you like. It seems to be venturing into irrelevant territory. Glenn
Bug#1003922: recastnavigation: reproducible-builds: BuildId differences triggered by RPATH
Source: recastnavigation Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/recastnavigation.html The attached patch to debian/rules passes -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override, which should use a relative path for RPATH. Alternately, updating the packaging to debhelper compat level 14 should fix this, although it is currently an experimental compat level. With this patch applied, recastnavigation should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining recastnavigation! live well, vagrant From 4b8a78935baaffeb65671f36fe1a1695a34ada4b Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Tue, 18 Jan 2022 05:58:20 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 1 + 1 file changed, 1 insertion(+) diff --git a/debian/rules b/debian/rules index 1bc7077..afb14dc 100755 --- a/debian/rules +++ b/debian/rules @@ -25,6 +25,7 @@ DEB_CMAKE_OPTIONS ?= -DCMAKE_VERBOSE_MAKEFILE=ON \ -DRECASTNAVIGATION_DEMO=OFF \ -DRECASTNAVIGATION_TESTS=OFF \ -DRECASTNAVIGATION_EXAMPLES=OFF \ + -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \ .. override_dh_auto_configure: -- 2.34.1 signature.asc Description: PGP signature
Bug#1003921: firmware-realtek: firmware does not load if intel_idle.max_cstate=1 is entered on the command line
Package: firmware-realtek Version: 20161130-5~deb8u1 Severity: important Dear Maintainer, I have been trying to debug a problem with my Intel GPU. My Intel GPU performs badly unless intel_idle.max_cstate=1 is set as a grub command line option. However, several reboots later, I can prove that that option is incompatible (in my environment at least) with the firmware-realtek package in Buster (version 20210315-3). When I upgraded to the version of firmware-realtek in buster and rebooted, the realtek firmware that I need for my Gigabit Ethernet card failed to load. Here are the relevant book logs from this successful boot: [8.789508] r8169 :02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168e-2.fw [8.790229] RTL8211DN Gigabit Ethernet r8169-0-200:00: attached PHY driver [RTL8211DN Gigabit Ethernet] (mii_bus:phy_addr=r8169-0-200:00, irq=IGNORE) Here is my relevant install of the Bullseye version of firmware-realtek: Start-Date: 2022-01-17 19:27:36 Commandline: /usr/bin/apt-get -q install firmware-realtek Requested-By: lfcjf (110) Upgrade: firmware-realtek:amd64 (20161130-5~deb8u1, 20210315-3) End-Date: 2022-01-17 19:28:01 In order to make the system boot properly, I had to remove the firmware-realtek and install a copy of firmware-realtek_20161130-5~deb8u1_all.deb (using dpkg -i) which I had from a few years ago. That older firmware package has the identical file rtl_nic/rtl8168e-2.fw with the Bullseye version (I used dpkg-deb -x to extract the two files and ran an md5sum to compare them). So the problem is not with the firmware file that I need itself. The problem is with getting the firmware to load if I have set the grub command line option intel_idle.max_cstate=1. In the Bullseye version of the firmware-realtek package the firmware does not load and I end up with NO network. That is a show stopper. Here is dmesg output from this successfull boot (with the 20161130-5~deb8u1 version of the package): Rebooted Tue Jan 18 00:05:06 EST 2022. [0.00] Linux version 5.10.0-10-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.84-1 (2021-12-08) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-10-amd64 root=/dev/mapper/precession-root ro quiet i915.enable_dc=0 i915.disable_power_well=1 intel_idle.max_cstate=1 [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable [0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable [0.00] BIOS-e820: [mem 0x2000-0x201f] reserved [0.00] BIOS-e820: [mem 0x2020-0x3fff] usable [0.00] BIOS-e820: [mem 0x4000-0x401f] reserved [0.00] BIOS-e820: [mem 0x4020-0xbad92fff] usable [0.00] BIOS-e820: [mem 0xbad93000-0xbadd9fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbadda000-0xbade0fff] ACPI data [0.00] BIOS-e820: [mem 0xbade1000-0xbade1fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbade2000-0xbae04fff] reserved [0.00] BIOS-e820: [mem 0xbae05000-0xbae05fff] usable [0.00] BIOS-e820: [mem 0xbae06000-0xbae17fff] reserved [0.00] BIOS-e820: [mem 0xbae18000-0xbae24fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbae25000-0xbae48fff] reserved [0.00] BIOS-e820: [mem 0xbae49000-0xbae8bfff] ACPI NVS [0.00] BIOS-e820: [mem 0xbae8c000-0xbaff] usable [0.00] BIOS-e820: [mem 0xbb80-0xbf9f] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00023fdf] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: BIOSTAR Group H61MU3/H61MU3, BIOS 4.6.4 04/07/2011 [0.00] tsc: Fast TSC calibration using PIT [0.00] tsc: Detected 2394.353 MHz processor [0.000832] e820: update [mem 0x-0x0fff] usable ==> reserved [0.000835] e820: remove [mem 0x000a-0x000f] usable [0.000843] last_pfn = 0x23fe00 max_arch_pfn = 0x4 [0.000848] MTRR default type: uncachable [0.000849] MTRR fixed ranges enabled: [0.000850] 0-9F
Bug#1003920: akonadi: reproducible-builds: BuildId differences triggered by RPATH
Source: akonadi Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/akonadi.html The attached patch to debian/rules passes -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override, which should use a relative path for RPATH. Alternately, updating the packaging to debhelper compat level 14 should fix this, although it is currently an experimental compat level. With this patch applied, akonadi should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining akonadi! live well, vagrant From 91a269b1608d2ed3393a1d304947c7f3125e09a0 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Tue, 18 Jan 2022 05:15:45 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 1 + 1 file changed, 1 insertion(+) diff --git a/debian/rules b/debian/rules index 7d57e79..093dca1 100755 --- a/debian/rules +++ b/debian/rules @@ -19,6 +19,7 @@ override_dh_auto_configure: dh_auto_configure -- \ -DINSTALL_QSQLITE_IN_QT_PREFIX=ON \ -DBUILD_TOOLS=ON \ + -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \ -DBUILD_DESIGNERPLUGIN=ON execute_after_dh_install: -- 2.34.1 signature.asc Description: PGP signature
Bug#1003919: apulse: reproducible-builds: BuildId differences triggered by RPATH
Source: apulse Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apulse.html The attached patch to debian/rules passes -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override, which should use a relative path for RPATH. Alternately, updating the packaging to debhelper compat level 14 should fix this, although it is currently an experimental compat level. With this patch applied, apulse should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining apulse! live well, vagrant From eb60043b8fabdf52639e816ef888fdbbb72eee43 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Tue, 18 Jan 2022 05:01:38 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index 9fd8e1a..81d0cbb 100755 --- a/debian/rules +++ b/debian/rules @@ -16,3 +16,6 @@ override_dh_makeshlibs: # defaulted by debhelper for cmake. override_dh_shlibdeps: dh_shlibdeps -l/usr/lib/${DEB_HOST_MULTIARCH}/apulse + +override_dh_auto_configure: + dh_auto_configure -- -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON -- 2.34.1 signature.asc Description: PGP signature
Bug#1003918: bats: new upstream version
Source: bats Version: 1.2.1-3 Severity: wishlist Hey. There's a newer upstream version out (1.5.0)... and much more in git. btw: would it be possible to also include: https://github.com/bats-core/bats-support https://github.com/bats-core/bats-assert https://github.com/bats-core/bats-file ? Thanks, Chris.
Bug#1002976: Debian 11
I just tried the mini iso again, the error about firmware was about the installer language question, it then asked me if I had a disk with firmware and if so to install it. This looks normal to me. I have since learned hot to download all the firmware and put it on my usb stick in a folder named 'firmware", when I do this, the mini.iso is able to see my wifi card and asks me the network ID number and password for my wifi and it will connect. Best regards, David On Mon, Jan 17, 2022 at 3:33 AM Samuel Thibault wrote: > D.J.J. Ring, Jr., le dim. 16 janv. 2022 21:44:55 -0500, a ecrit: > > The mini iso just gave me an error that firmware was missing for my wifi > - I > > found the instructions on how to load firmware and put it in a FAT > partition on > > USB stick in a directory named /firmware. No more error. > > That was not the question. Please *exactly* answer the question I am > asking: > > *When* was this error precisely? Before or after the installer language > question? > > That's the information I need, if you don't provide it we'll be unused > what works and what doesn't work, and won't be able to fix the bug. > > Samuel >
Bug#726542: RE: ITA: pngphoon -- Creates a png file with the current phase of the moon
Hi, I did contact upstream, after this the package now has a git repository. Upstream will sign tarballs, and probably a new version soon. Nice, isn't it? kretcheu :x On Mon, 17 Jan 2022 11:19:24 -0300 Leandro Cunha wrote: Hi, The package should be without updates to ever and in the situation it is worthy for orphaned packages. The update I worked on should be the last one for this package. Edit leaving the package orphaned in case you change your mind. Leandro OpenPGP_signature Description: OpenPGP digital signature
Bug#1003917: ITP: xmrig -- High performance, open source CPU/GPU miner, RandomX benchmark, and stratum proxy.
Package: wnpp X-Debbugs-Cc: debian-de...@lists.debian.org Owner: Ben Westover X-Debbugs-Cc: kwestover...@gmail.com Severity: wishlist * Package name: xmrig Version : 6.16.2 Upstream Author : XMRig * URL : http://xmrig.com * License : GPL-3 Programming Lang: C, C++ Description : High performance, open source CPU/GPU miner, RandomX benchmark, and stratum proxy. XMRig is a high performance, open source, cross platform RandomX, KawPow, CryptoNight and AstroBWT unified CPU/GPU miner and RandomX benchmark. One thing to note about XMRig is that it only supports x86 and ARM, so the package will only support a subset of the available Debian architectures. I do not plan to maintain this package inside a team. I am not looking for co-maintainers, but I will need a sponsor. OpenPGP_0xC311C5F54E89B698.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1003916: hledger: please update to latest upstream release
Package: hledger Severity: wishlist Dear maintainers, Please update this package to the latest upstream release (currently 1.24.1). I'm trying to migrate from ledger to hledger because of the included CSV rules parsing, but it seems the current docs online include commands currently not available in Debian. This makes my life harder :( Cheers, and thanks for maintaining this package. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
On Mon, Jan 17, 2022 at 4:55 AM Samuel Thibault wrote: > Hello, > > Thanks for the information. > > D.J.J. Ring, Jr., le dim. 16 janv. 2022 22:12:29 -0500, a ecrit: > > I already noticed something, in Buster, my digital card isn't listed > > with the cat /proc/asound/cards command. > > Yes, that's because in the bullseye case you have used the mini.iso. As > I wrote, please rather use the netinst bullseye iso image. The mini.iso > image was only to check whether the presence of the i915 driver would > help. > > > ## Output of amixer -c 0 scontents and amixer -c 1 scontents for the > Bullseys > > mini_amixer1contents > > > > > > ## Output of amixer -c 0 scontents amixer -c 1 scontents and amixer -c 1 > > 10.11.0_amixer1contents > > One thing I notice is this: > > Simple mixer control 'IEC958',0 > Capabilities: pswitch pswitch-joined > Playback channels: Mono > Mono: Playback [off] > > It's off in the Buster case and on in the Bullseye case. I guess you are > not using the IEC958 output. > > Could you try running this inside the bullseye installer: > > amixer -c 0 sset IEC958,0 off > > samuel > Hello Samuel, I'm trying to be very careful to do whatever you tell me, but I will probably make a mistake, but not on purpose, just because I misunderstood. Here's what I did. Using firmware-10.11.0-amd64 installer, I gave this command: amixer -c 0 set IEC958,0 off I didn't get a response because my sound cards were renumbered. So I changed the command to: amixer -c 1 set IEC958,0 off This is the response I received. Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] About the firmware error, it's right after language selection saying that some of my hardware requires firmware and that I should insert a disk with firmware on it. That looks normal to me. While my computer has a digital sound output, I don't use it, I use the small speaker 3.5mm TRS (tip, ring, sleeve) plug like music players use to go to an amplified speaker. Regards, David
Bug#1003907: Acknowledgement (fails to successfully associate)
Hardware: 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6205 (802.11a/b/g/n) Flags: bus master, fast devsel, latency 0, IRQ 35, IOMMU group 13 Memory at f250 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 08-11-96-ff-ff-8d-d4-90 Kernel driver in use: iwlwifi Kernel modules: iwlwifi OpenPGP_signature Description: OpenPGP digital signature
Bug#918854: Disabling libgit2
Hi, Thanks Jelmer! Others - This is just to confirm that I can reproduce the issue on a Pi4 (with no pending updates) and that I was able to move forward with jelmer's workaround. pi@raspberrypi:~/proj/pgx-extns/test2 $ uname -a Linux raspberrypi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux pi@raspberrypi:~/proj/pgx-extns/test2 $ ldconfig -v 2>/dev/null | grep libgit2 libgit2.so.27 -> libgit2.so.0.27.7 - robins
Bug#881626: busybox: enable telnetd
On Tuesday, 18 January 2022 01:17:38 CET Jonathan Rubenstein wrote: > Maybe this is an indication that busybox-static needs to be audited, or > that all 3 configurations should be audited to make sure something isn't > missing that has no reason to be. IIUC, that is planned: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998803#25 signature.asc Description: This is a digitally signed message part.
Bug#1003915: mathgl: reproducible-builds: BuildId differences triggered by RPATH
Source: mathgl Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mathgl.html The attached patch to debian/rules passes -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override, which should use a relative path for RPATH. Alternately, updating the packaging to debhelper compat level 14 should fix this, although it is currently an experimental compat level. With this patch applied, mathgl should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining mathgl! live well, vagrant From c5f7530ed115ef9be65861e69271185c423ffe0a Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Tue, 18 Jan 2022 00:52:33 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 1 + 1 file changed, 1 insertion(+) diff --git a/debian/rules b/debian/rules index c4570b9..66929a7 100755 --- a/debian/rules +++ b/debian/rules @@ -43,6 +43,7 @@ override_dh_auto_configure: -Denable-qt5asqt=ON \ -Denable-json-sample=ON \ -Denable-json-sample-we=ON \ +-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \ -Denable-python=ON override_dh_python3: -- 2.34.1 signature.asc Description: PGP signature
Bug#1003914: kget: reproducible-builds: BuildId differences triggered by RPATH
Source: kget Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kget.html The attached patch to debian/rules passes -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override, which should use a relative path for RPATH. Alternately, updating the packaging to debhelper compat level 14 should fix this, although it is currently an experimental compat level. With this patch applied, kget should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining kget! live well, vagrant From 73003d74730ae01d17a8e7f94ce84fe0346ce1c3 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Tue, 18 Jan 2022 00:21:29 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 5c9fac1..3c95cbe 100755 --- a/debian/rules +++ b/debian/rules @@ -9,7 +9,7 @@ include /usr/share/pkg-kde-tools/qt-kde-team/2/l10n-packages.mk dh $@ --with kf5 override_dh_auto_configure: - dh_auto_configure -Skf5 -- -DBUILD_TESTING=OFF + dh_auto_configure -Skf5 -- -DBUILD_TESTING=OFF -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON override_dh_auto_test: : -- 2.34.1 signature.asc Description: PGP signature
Bug#993161: pam: some remaining changes for DPKG_ROOT
> "Johannes" == Johannes Schauer Marin Rodrigues writes: Johannes> Hi Steve, Quoting Johannes Schauer Marin Rodrigues Johannes> (2021-12-08 10:00:31) Johannes> Since it has been more than a month without any reply I Johannes> just uploaded a NMU of pam with the attached debdiff to Johannes> DELAYED/10. Those are the same changes as from Johannes> https://salsa.debian.org/vorlon/pam/-/merge_requests/7 and Johannes> our CI passes with those changes to pam Johannes> https://salsa.debian.org/helmutg/dpkg-root-demo/-/jobs I have attempted to cancel this NMU. I've tried to explicitly nack this change without feedback from Steve, and I stand behind this. This change adds a maintenance burden that I'm not entirely comfortable accepting either as an NMU or as a co-maintainer without full authority. I'm guessing my previous statement on this was insufficiently clear. Please wait for feedback from Steve before integrating this change. Thanks, --Sam signature.asc Description: PGP signature
Bug#1002978: Another GPU hang
OK, now we know the i915 driver, in my environment is NOT fixed with just the microcode. I get GPU hangs whether the microcode is up-to-date or not. This boot had NO kernel command line options (besides Debian defaults): GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=force" I don't remember if I added pcie_aspm=force or if Debian did. I've had that forever. I will try removing it next, but I probably need it for my Realtek Ethernet that uses the 8168 driver. Currently, I have: $ cat /sys/module/pcie_aspm/parameters/policy [default] performance powersave powersupersave Here is the output of /sys/class/drm/card0/error: GPU HANG: ecode 6:2:bb86, in systemd-logind [662] Kernel: 5.10.0-10-amd64 x86_64 Driver: 20200917 Time: 1642463910 s 885852 us Boottime: 7195 s 975866 us Uptime: 7189 s 236627 us Capture: 4296691264 jiffies; 543240 ms ago Active process (on ring bcs0): systemd-logind [662] Reset count: 0 Suspend count: 0 Platform: SANDYBRIDGE Subplatform: 0x0 PCI ID: 0x0102 PCI Revision: 0x09 PCI Subsystem: 1565:110d IOMMU enabled?: 0 RPM wakelock: yes PM suspended: no GT awake: yes EIR: 0x IER: 0x82bc8585 GTIER[0]: 0x00401001 PGTBL_ER: 0x FORCEWAKE: 0x DERRMR: 0x fence[0] = fde03b007f6001 fence[1] = 122600701127003 fence[2] = fence[3] = fence[4] = fence[5] = fence[6] = fence[7] = fence[8] = fence[9] = fence[10] = fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = ERROR: 0x DONE_REG: 0x bcs0 command stream: CCID: 0x START: 0x5000 HEAD: 0x0fe034d0 [0x3458] TAIL: 0x36f8 [0x34d0, 0x34e0] CTL: 0x3001 MODE: 0x HWS: 0x7fffb000 ACTHD: 0x 7fff3ee8 IPEIR: 0x0008 IPEHR: 0x4477 ESR: 0x INSTDONE: 0xfff1 batch: [0x_7fff3000, 0x_7fff7000] BBADDR: 0x_7fff3ee3 BB_STATE: 0x INSTPS: 0x INSTPM: 0x FADDR: 0x 7fff3f80 RC PSMI: 0x0010 FAULT_REG: 0x GFX_MODE: 0x PP_DIR_BASE: 0x engine reset count: 0 Active context: systemd-logind[662] prio 0, guilty 0 active 0, runtime total 0ns, avg 0ns bcs0 --- HW Status = 0x 7fffb000 :cL%-H!!!Tc0;&FRS,4aK&eK-$Fk6JP^IKP"K!4)Z. bcs0 --- batch = 0x 7fff3000 :=m_`(+@[H9*1>F@9kb_ZL,tUu]nJ#WN6g$ROq$#UUsrA'--e$d_R^0)luEdKiJD?%4+2TScP/afS7MKb-!')6*QmkM"Blk<@4s1<;EjkJ#1.f"Jfpej!qVZa!XN-KA[pR`*rg0HQ5T%GpPsj+--CS"%=$jQ6kk;s1f^q.Lo'!^l]kiSj8M4Fpl!m3?ri7jfXZH[J]1gY4)\@FT%>S]p_nQEd7.q"nNW"9#LIO!8f2Y>V`Jhe43XiCr++i\Q2=(BsA+ZA/pcS]Z=Ym?gVZd/E`ZT&_2+3=(L'/[WV<0?.F3NSo2Oj9Cg([C?<5#tprrmU]Zng5G_:V_--7.X#hjfBhpDhh/bZ]+CY_C'XBK6%TZe2aK!L\UF%0cWmV_Fo48LFmI8%_9+8])9De%WAP:P4Etm-\s!sB7#I,r0L5G?uhuUQ1(uT"5Vg6^mt.DBZb?qq+mUQhiIBR$%i:B(*7-N4s<^:N!dt0cQ0s5s+k0m$jtCU4,i)BB41=kiWo?S!jlZkY92ou0D;o2B[Qju>l!LcIsr@W&,T%9=u7&TPZe*=HVitpV_`;n'2/baJ85fK^o\Lm<[=F;%./##ZtX0k1t5G*nI%E`?ri7fg%PrgQW.=8TNbZO07Bbl9n`NK0q=S1U%Y;lIt9ZX9tOb`e^&oNkdoaEl4%N(2--N-[ISbgeH9pu:cDKWggP-@,8@f"=jhqQW,C/LBgIZZp]`dKMO3QiYh(dsMIgI==2lY6)lu$H#3R`]N#9.[!KO-CR/!RC[1CM\'Y1J_6+Y3C$t)7T!";cr0l`'F2P-:3]"o[p[CE\'(:/^WTT/o&m<:#Zq.%`RH[RiaNd@g)P\C0=^al!DC.Tegj)\_2A5Q2>o#$MBn1WqElTkF:]'JXff4gP1@1Rqn/%ab**p1GI$cQBcCm.^G<:MT5?jpBSX-i4pr>C=C`c+;r@Gf%a0Ni$0"(k-nHI#(>;*/+ikG<4+CA?5HoRCs2gHkbUs9YN?IYr:r_1qS^AOT_#[We7Gck_IH?BItbqE?EGdslc-UZ?!b'QhsmeU^0mIp\1d1Pf=lSh.;`C,H'B8O3fC_35KF&uLtQbNS.3Hn;7"[MU?QUqa\BP3fDM^cJ,)RZ?h8iTN.:D`2\Z4Y+Pm#^s'd'&^ZP\m?JjigR=ECTngA4o7D+F;+qia#f9%M#6f$flnfY'qh0BW6OUkbdXlN.,'%ZUshF)d;6Z4/peY]C_rF*AR+s%n:F[h"t(NW&Df5hJE%Zjm,.anGi74SYLL99tc"!j?pWAC#l>.12;=cB!o;^S(9!eslWhor%+O,@u2Mhl#AEp\C./^\d!up5K%&MjC@?n2CK.hNi?'FjCEpV$$BlWg]$97gC]_!VMK700nM4@Bk02k50MGt:;(0Zj=hC@OU-KN/4*M[2a05D<0NV:u0Xc^Wkd>4@EYr\)ti8,hH$KiZPPn")qI/UMkf0Uk.g*XU*saY>akni+,Nq:?^us*f`5O7u4VE=B\->WQCt9WJY1d8Ra!\r\?]BcKI8`&^C"fPpqSLeNgOaPmRP+EBGr,VFE'o>s+U%S1u-'ORXS*J^dgLdI/#'QF/k&B,VTH/o9%;<3E_6^2QpUPMYbKW*l3NZb>]"iH.2*'i"n*Cg[KE=YpbN>t2?`"PWPZuHN%&?Qp;IUjBfiT,aY%aj?gOoqK$8!4[D"jt79*(+gf01QR:E:`!!',7 available engines: 7 slice total: 0, mask= subslice total: 0 EU total: 0 EU per subslice: 0 has slice power gating: no has subslice power gating: no has EU power gating: no Unavailable Num Pipes: 2 Pipe [0]: Power: on SRC: 077f0437 STAT: Plane [0]: CNTR: d8004400 STRIDE: 1e00 ADDR: SURF: 007f6000 TILEOFF: Cursor [0]: CNTR: 04004027 POS: 0277047e BASE: 00fdf000 Pipe [1]: Power: on SRC: STAT: Plane [1]: CNTR: 4000 STRIDE: ADDR: SURF: TILEOFF: Cursor [1]: CNTR: POS: BASE: CPU transcoder: A Power: on CONF: c000 HTOTAL: 0897077f HBLANK: 0897077f HSYNC: 080307d7 VTOTAL: 04640437 VBLANK: 04640437 VSYNC: 0440043b CPU transcoder: B Power: on CONF: H
Bug#881626: busybox: enable telnetd
busybox-stable Pardon me, I need to proofread. I mean busybox-static. Best Regards, Jonathan Rubenstein
Bug#881626: busybox: enable telnetd
We will not enable telnetd in any of the flavours of busybox that we currently package. Respectfully, telnetd has been enabled for busybox-stable since 2010, so you can install busybox-stable. Maybe this is an indication that busybox-stable needs to be audited, or that all 3 configurations should be audited to make sure something isn't missing that has no reason to be. (I have a few in mind already, but they deserve their own bugs) Best Regards, Jonathan Rubenstein
Bug#1003913: lintian: False positive: package-contains-documentation-outside-usr-share-doc
Package: lintian Version: 2.114.0 Severity: normal For the current (from experimental, but will be in unstable shortly) build for python-nacl I get the following from lintian: I: python3-nacl: package-contains-documentation-outside-usr-share-doc usr/lib/python3/dist-packages/PyNaCl-1.5.0.dist-info/top_level.txt Thinks in Python package dist-info directories aren't documentation and should not be considered for this check. These are relatively rare, but will be increasingly common as more packages switch to newer Python build systems. Scott K
Bug#1003912: vdeplug4: reproducible-builds: BuildId differences triggered by RPATH
Source: vdeplug4 Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The RPATH contains the build path resulting in different buildid: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdeplug4.html The attached patch to debian/rules passes -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via a dh_auto_configure override, which should use a relative path for RPATH. Alternately, updating the packaging to debhelper compat level 14 should fix this, although it is currently an experimental compat level. With this patch applied, vdeplug4 should build reproducibly on tests.reproducible-builds.org! Thanks for maintaining vdeplug4! live well, vagrant From 319872b658057cfb572b7adfa7d4c3fdb73da6a4 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Mon, 17 Jan 2022 23:49:59 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index c61a937..35c765b 100755 --- a/debian/rules +++ b/debian/rules @@ -17,3 +17,6 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed override_dh_auto_install: dh_auto_install --destdir=debian/tmp + +override_dh_auto_configure: + dh_auto_configure -- -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON -- 2.34.1 signature.asc Description: PGP signature
Bug#1003324: RFP: fragments -- a easy to use BitTorrent client
Hi, Everyone uses transmission which is installed on Debian with Gnome through the package[1] with task-gnome-desktop[2] a task package to install the desktop environment as defined in description. I'll leave it to whoever wants it or in the future if I change my mind. If this bug is still open. [1] https://packages.debian.org/sid/gnome [2] https://packages.debian.org/sid/task-gnome-desktop -- Cheers, Leandro Cunha Software Engineer and Debian Contributor ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄ -BEGIN PGP PUBLIC KEY BLOCK- mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh 0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7 ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3 k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx /m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C +DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4 hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08 iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X 7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00 4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9 WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O +SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW fNdY6Ns= =rdCA -END PGP PUBLIC KEY BLOCK-
Bug#1003911: RFA: xplanet -- planetary body renderer
Package: wnpp Severity: normal I request an adopter for the xplanet package. I've not had any time to work on the package for quite a while, so I'm hoping somebody else will pick it up. The package description is: Xplanet renders an image of a planet into an X window or a file. All of the major planets and most satellites can be drawn, and different map projections are also supported, including azimuthal, hemisphere, Lambert, Mercator, Mollweide, Peters, polyconic, and rectangular. . In order to run xplanet, you'll need at least one map file. Some maps are included in the xplanet-images package. Xplanet renders an image of a planet into an X window or a file. All of the major planets and most satellites can be drawn, and different map projections are also supported, including azimuthal, hemisphere, Lambert, Mercator, Mollweide, Peters, polyconic, and rectangular. . In order to run xplanet, you'll need at least one map file. Some maps are included in the xplanet-images package.
Bug#1003910: O: xmix -- X11-based interface to the Linux sound driver mixer
Package: wnpp Severity: normal I intend to orphan the xmix package. It's way behind the times and likely not very useful for most current systems. I stopped using it myself some time ago, so it's time I let it go. The package description is: This interface to the sound driver mixer allows easy adjustment of the sound card's input and output levels, and selection of sound source for recording.
Bug#1003909: RFA: nas -- Network Audio System - local server
Package: wnpp Severity: normal I request an adopter for the nas package. I haven't really done much with nas in a while, and it's quiet upstream too. I've no time to work on it any more. The package description is: The Network Audio System (NAS) was developed by NCD for playing, recording, and manipulating audio data over a network. Like the X Window System, it uses the client/server model to separate applications from the specific drivers that control audio input and output devices. . This package contains the NAS daemon (nasd), needed for local output from NAS. The Network Audio System (NAS) was developed by NCD for playing, recording, and manipulating audio data over a network. Like the X Window System, it uses the client/server model to separate applications from the specific drivers that control audio input and output devices. . This package contains the NAS daemon (nasd), needed for local output from NAS.
Bug#1003908: RFA: dvdtape -- Create DVD master filesystems on DLT media
Package: wnpp Severity: normal I request an adopter for the dvdtape package. I haven't had a need for this package in a very long time, and I've no time to work on it any more. The package description is: This tool will create the control files needed when mastering DVDs for manufacturing (DDP information, DDPMS information, "lead in") and output them to DLT tape(s) or disk files as desired.
Bug#1003907: fails to successfully associate
Package: wpasupplicant Version: 2:2.10-1 Severity: grave Hi, during todays upgrade of wpasupplicant 2:2.9.0-23 to 2:2.10-1 my network connection was killed (I'm using NetworkManager 1.34.0) and I wasn't able to successfully connect again, even after a reboot. Only a downgrade to 2:2.9.0-23 helped. Attached is the journal log for wpasupplicant.service and a dmesg output. Marking as RC so the package doesn't migrate until this has been investigated. Regards, Michael -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wpasupplicant depends on: ii adduser3.118 ii libc6 2.33-2 ii libdbus-1-31.12.20-3 ii libnl-3-2003.4.0-1+b1 ii libnl-genl-3-200 3.4.0-1+b1 ii libnl-route-3-200 3.4.0-1+b1 ii libpcsclite1 1.9.5-1 ii libreadline8 8.1.2-1 ii libssl1.1 1.1.1m-1 ii lsb-base 11.1.0 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl pn wpagui -- Configuration Files: /etc/wpa_supplicant/ifupdown.sh changed [not included] -- no debconf information dmesg Description: application/json Jan 18 00:17:02 pluto systemd[1]: Starting WPA supplicant... Jan 18 00:17:03 pluto systemd[1]: Started WPA supplicant. Jan 18 00:17:03 pluto wpa_supplicant[664]: Successfully initialized wpa_supplicant Jan 18 00:17:04 pluto wpa_supplicant[664]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed Jan 18 00:17:07 pluto wpa_supplicant[664]: wlp3s0: WPS-CANCEL Jan 18 00:17:07 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED 38:10:d5:8f:38:e2 0 Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=38:10:d5:8f:38:e2 status_code=40 Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Deauth request to the driver failed Jan 18 00:17:08 pluto wpa_supplicant[664]: BSSID 38:10:d5:8f:38:e2 ignore list count incremented to 2, ignoring for 10 seconds Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz) Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz) Jan 18 00:17:09 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED 38:10:d5:8f:38:e1 0 Jan 18 00:17:09 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz) Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=38:10:d5:8f:38:e2 status_code=40 Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-REMOVED 38:10:d5:8f:38:e2 0 Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-REMOVED 38:10:d5:8f:38:e1 0 Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED 38:10:d5:8f:38:e2 0 Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=38:10:d5:8f:38:e2 status_code=40 Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: SME: Deauth request to the driver failed Jan 18 00:17:13 pluto wpa_supplicant[664]: BSSID 38:10:d5:8f:38:e2 ignore list count incremented to 2, ignoring for 10 seconds Jan 18 00:17:14 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz) Jan 18 00:17:16 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38
Bug#1003871: [LA-Mirroring] Bug#1003871: Bug#1003871: Acknowledgement (mirror listing update for mirror.linux.org.au)
Hi Thanks for that, we have just run a manual sync and that is working again now. We should be back to up to date mirror shortly. Steve On Mon, Jan 17, 2022 at 10:25:47PM +, Adam D. Barratt wrote: > Hi, > > I think I've spotted and fixed the rsync issue on the syncproxy side, > which was also related to the change Julien mentioned. > > Let us know how things look from your side. > > Regards, > > Adam > > > On Mon, 2022-01-17 at 15:47 +0100, Julien Cristau wrote: > > Hi Steven, > > > > there was an issue on syncproxy.au.debian.org which caused (ssh) > > triggers to mirror.linux.org.au to not work since the change, however > > I > > don't have an explanation for rsync not working :( > > > > Cheers, > > Julien > > > > On Mon, Jan 17, 2022 at 09:56:15PM +1100, Steven Hanley wrote: > > > More details from the email I sent on Saturday > > > > > > Hi > > > > > > We have just moved our mirror.linux.org.au to a new machine, on a > > > new ip > > > address. > > > > > > I have kept the credentials for our sync the same > > > > > > username > > > > > > mirror.linux.org.au > > > > > > Getting > > > > > > rsync: failed to connect to syncproxy.au.debian.org > > > (2400:a4c0::27): > > > Connection timed out (110) > > > rsync: failed to connect to syncproxy.au.debian.org > > > (103.84.224.39): > > > Connection timed out (110) > > > rsync error: error in socket IO (code 10) at clientserver.c(127) > > > [Receiver=3.1.3] > > > > > > Is there a modification oon your end needed? > > > > > > The new ip addresses are > > > > > > ipv4 103.84.224.37 > > > ipv6 2400:a4c0::25 > > > > > > Cheers > > > > > > Steve > > > > > > > > > On Mon, Jan 17, 2022 at 10:27:03AM +, Debian Bug Tracking > > > System wrote: > > > > Thank you for filing a new Bug report with Debian. > > > > > > > > You can follow progress on this Bug here: 1003871: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003871. > > > > > > > > This is an automatically generated reply to let you know your > > > > message > > > > has been received. > > > > > > > > Your message is being forwarded to the package maintainers and > > > > other > > > > interested parties for their attention; they will reply in due > > > > course. > > > > > > > > Your message has been sent to the package maintainer(s): > > > > Debian Mirrors Team > > > > > > > > If you wish to submit further information on this problem, please > > > > send it to 1003...@bugs.debian.org. > > > > > > > > Please do not send mail to ow...@bugs.debian.org unless you wish > > > > to report a problem with the Bug-tracking system. > > > > > > > > -- > > > > 1003871: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003871 > > > > Debian Bug Tracking System > > > > Contact ow...@bugs.debian.org with problems > > > > ___ > > > > mirroring mailing list > > > > mirror...@lists.linux.org.au > > > > http://lists.linux.org.au/mailman/listinfo/mirroring > > > > > > -- > > > Steven Hanley s...@svana.org http://svana.org/sjh/diary > > > did the hate filled want to build bunkers, in your beautiful red > > > earth > > > they want to build them in our shiny white snow > > >Hello Birmingham - To The Teeth - Ani > > > > > > > > > > ___ > mirroring mailing list > mirror...@lists.linux.org.au > http://lists.linux.org.au/mailman/listinfo/mirroring -- Steven Hanley s...@svana.org http://svana.org/sjh/diary do you split the rent there with all your secrets or do you just pretend to all your friends they're uninvited guests Shrug - Evolve - Ani
Bug#1002978: Another GPU hang
I rebooted with these grub config options: GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=force intel_idle.max_cstate=1" In addition to an almost immediate GPU hang, my r8169 driver Ethernet card failed to load its firmware causing a full network outage. I rebooted to see if it was a fluke, but no: evidently, removing two boot options (i915.disable_power_well=1 i915.enable_dc=0) plus the new microcode is incompatible with the intel_idle.max_cstate=1 with my r8169 Ethernet card. I know that because I fixed it by removing intel_idle.max_cstate=1 in grub. My strategy is to explore if the microcode is enough to fix the problem. But because intel_idle.max_cstate=1 doesn't cause a tainted kernel warning, I wrongly thought it was an innocuous option. Hence the learning experience described above. So far this configuration is stable. The Ethernet is working and No GPU hangs though I have experienced a few small hiccups that might be GPU performance related. These were not too bad and nothing has appeared in the error logs. But I only have 45 minutes of uptime. I'll report back when I have more confidence. After that no network GPU hang here is the output of /sys/class/drm/card0/error: GPU HANG: ecode 6:0: Kernel: 5.10.0-10-amd64 x86_64 Driver: 20200917 Time: 1642455365 s 522631 us Boottime: 40 s 7750 us Uptime: 33 s 557210 us Capture: 4294902272 jiffies; 149072 ms ago Reset count: 0 Suspend count: 0 Platform: SANDYBRIDGE Subplatform: 0x0 PCI ID: 0x0102 PCI Revision: 0x09 PCI Subsystem: 1565:110d IOMMU enabled?: 0 RPM wakelock: yes PM suspended: no GT awake: yes EIR: 0x IER: 0x82bc8585 GTIER[0]: 0x00401001 PGTBL_ER: 0x FORCEWAKE: 0x DERRMR: 0x fence[0] = fde03b007f6001 fence[1] = 11f8007010f9003 fence[2] = fence[3] = fence[4] = fence[5] = fence[6] = fence[7] = fence[8] = fence[9] = fence[10] = fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = ERROR: 0x DONE_REG: 0x available engines: 7 slice total: 0, mask= subslice total: 0 EU total: 0 EU per subslice: 0 has slice power gating: no has subslice power gating: no has EU power gating: no Unavailable Num Pipes: 2 Pipe [0]: Power: on SRC: 077f0437 STAT: Plane [0]: CNTR: d8004400 STRIDE: 1e00 ADDR: SURF: 007f6000 TILEOFF: Cursor [0]: CNTR: 04004027 POS: 02db0452 BASE: 00fdf000 Pipe [1]: Power: on SRC: STAT: Plane [1]: CNTR: 4000 STRIDE: ADDR: SURF: TILEOFF: Cursor [1]: CNTR: POS: BASE: CPU transcoder: A Power: on CONF: c000 HTOTAL: 0897077f HBLANK: 0897077f HSYNC: 080307d7 VTOTAL: 04640437 VBLANK: 04640437 VSYNC: 0440043b CPU transcoder: B Power: on CONF: HTOTAL: HBLANK: HSYNC: VTOTAL: VBLANK: VSYNC: gen: 6 gt: 1 iommu: disabled memory-regions: 5 page-sizes: 1000 platform: SANDYBRIDGE ppgtt-size: 31 ppgtt-type: 1 dma_mask_size: 40 is_mobile: no is_lp: no require_force_probe: no is_dgfx: no has_64bit_reloc: no gpu_reset_clobbers_display: no has_reset_engine: no has_fpga_dbg: no has_global_mocs: no has_gt_uc: no has_l3_dpf: no has_llc: yes has_logical_ring_contexts: no has_logical_ring_elsq: no has_logical_ring_preemption: no has_master_unit_irq: no has_pooled_eu: no has_rc6: yes has_rc6p: yes has_rps: yes has_runtime_pm: no has_snoop: no has_coherent_ggtt: yes unfenced_needs_alignment: no hws_needs_physical: no cursor_needs_physical: no has_csr: no has_ddi: no has_dp_mst: no has_dsb: no has_dsc: no has_fbc: yes has_gmch: no has_hdcp: no has_hotplug: yes has_hti: no has_ipc: no has_modular_fia: no has_overlay: no has_psr: no has_psr_hw_tracking: no overlay_needs_physical: no supports_tv: no rawclk rate: 125000 kHz CS timestamp frequency: 1250 Hz Has logical contexts? yes scheduler: 0 i915.vbt_firmware=(null) i915.modeset=-1 i915.lvds_channel_mode=0 i915.panel_use_ssc=-1 i915.vbt_sdvo_panel_type=-1 i915.enable_dc=-1 i915.enable_fbc=0 i915.enable_psr=-1 i915.psr_safest_params=no i915.enable_psr2_sel_fetch=no i915.disable_power_well=1 i915.enable_ips=1 i915.invert_brightness=0 i915.enable_guc=0 i915.guc_log_level=-1 i915.guc_firmware_path=(null) i915.huc_firmware_path=(null) i915.dmc_firmware_path=(null) i915.mmio_debug=0 i915.edp_vswing=0 i915.reset=3 i915.inject_probe_failure=0 i915.fastboot=-1 i915.enable_dpcd_backlight=-1 i915.force_probe= i915.fake_lmem_start=0 i915.enable_hangcheck=yes i915.load_detect_test=no i915.force_reset_modeset_test=no i915.error_capture=yes i915.disable_display=no i915.verbose_state_checks=yes i915.nuclear_pageflip=no i915.enable_dp_mst=yes i915.enable_gvt=no Here are the full logs from dmesg: [0.00] microcode: microcode updated early to revision 0x2f,
Bug#1003089: man-db has become prohibitively slow
On Mon, Jan 17, 2022 at 09:15:14PM +0100, Steinar H. Gunderson wrote: > On Mon, Jan 17, 2022 at 04:10:02AM +, Colin Watson wrote: > > We definitely do need to sort out encoding conversion, though. Although > > UTF-8 has been recommended for many years, policy still allows "the > > usual legacy encoding" and we've never got round to mandating UTF-8: > > > > $ w3m -dump https://lintian.debian.org/tags/national-encoding | grep > > --count usr/share/man > > 502 > > I tried looking at this, but TBH I don't think the man-db path _ever_ > inserts a conversion. The parameter to the lexer path is simply always NULL > in all calls, except for from a test. Am I missing something? test_manfile (which despite the name is not a test function) calls find_name with file!="-" and encoding=NULL; that causes find_name to call get_page_encoding, which always returns something non-NULL ("ISO-8859-1" for English pages), and then call add_manconv from that to UTF-8. > > Would you care to have a look at this? > > > > https://gitlab.com/cjwatson/man-db/-/merge_requests/2 > > Thanks! I'll have a go at a review, but it might need to wait until the end > of the week. I'll try to get it done earlier, though. How would you like any > review comments? Email or somehow in Gitlab? Mild preference for GitLab MR comments, but I'm not that fussy. > > There's probably still room for improvement, but unlikely to be much > > more than a factor of two or so at this point, and I think this should > > get us comfortably back to the point where it's no longer annoying > > people during upgrades. > > Someone else suggested an idea I thought of throwing around: In addition > to optimizing the code, perhaps the postinst trigger should simply launch the > man-db timer in the background? At least for systemd users, this should be > pretty straightforward, and give the control back to the installation > process. (Given that dpkg is very much single-threaded, we're not generally > throughput-bound, so using up a core shouldn't be a big problem.) I suppose that's an option; apt-xapian-index.postinst seems to be precedent for doing things in the background, albeit in a non-systemd way. Unlike the postinst, man-db.service omits -p/--no-purge, but maybe that would be OK, especially after this round of optimization. I'll consider that once I get to packaging these changes. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#1003905: python-cryptography 3.4.8-1 regression vs upstream 3.4.8
Package: python-cryptography Version: 3.4.8-1 Severity: normal Dear Maintainer, dump_certificate_request() for an unsigned CSR is failing on 3.4.8-1 in distro but is successful against upstream 3.4.8. I have a test here that can be run against upstream as well as distro packages. https://github.com/coreycb/cryptography-regression-test Thank you, Corey
Bug#1003871: [LA-Mirroring] Bug#1003871: Acknowledgement (mirror listing update for mirror.linux.org.au)
Hi, I think I've spotted and fixed the rsync issue on the syncproxy side, which was also related to the change Julien mentioned. Let us know how things look from your side. Regards, Adam On Mon, 2022-01-17 at 15:47 +0100, Julien Cristau wrote: > Hi Steven, > > there was an issue on syncproxy.au.debian.org which caused (ssh) > triggers to mirror.linux.org.au to not work since the change, however > I > don't have an explanation for rsync not working :( > > Cheers, > Julien > > On Mon, Jan 17, 2022 at 09:56:15PM +1100, Steven Hanley wrote: > > More details from the email I sent on Saturday > > > > Hi > > > > We have just moved our mirror.linux.org.au to a new machine, on a > > new ip > > address. > > > > I have kept the credentials for our sync the same > > > > username > > > > mirror.linux.org.au > > > > Getting > > > > rsync: failed to connect to syncproxy.au.debian.org > > (2400:a4c0::27): > > Connection timed out (110) > > rsync: failed to connect to syncproxy.au.debian.org > > (103.84.224.39): > > Connection timed out (110) > > rsync error: error in socket IO (code 10) at clientserver.c(127) > > [Receiver=3.1.3] > > > > Is there a modification oon your end needed? > > > > The new ip addresses are > > > > ipv4 103.84.224.37 > > ipv6 2400:a4c0::25 > > > > Cheers > > > > Steve > > > > > > On Mon, Jan 17, 2022 at 10:27:03AM +, Debian Bug Tracking > > System wrote: > > > Thank you for filing a new Bug report with Debian. > > > > > > You can follow progress on this Bug here: 1003871: > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003871. > > > > > > This is an automatically generated reply to let you know your > > > message > > > has been received. > > > > > > Your message is being forwarded to the package maintainers and > > > other > > > interested parties for their attention; they will reply in due > > > course. > > > > > > Your message has been sent to the package maintainer(s): > > > Debian Mirrors Team > > > > > > If you wish to submit further information on this problem, please > > > send it to 1003...@bugs.debian.org. > > > > > > Please do not send mail to ow...@bugs.debian.org unless you wish > > > to report a problem with the Bug-tracking system. > > > > > > -- > > > 1003871: > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003871 > > > Debian Bug Tracking System > > > Contact ow...@bugs.debian.org with problems > > > ___ > > > mirroring mailing list > > > mirror...@lists.linux.org.au > > > http://lists.linux.org.au/mailman/listinfo/mirroring > > > > -- > > Steven Hanley s...@svana.org http://svana.org/sjh/diary > > did the hate filled want to build bunkers, in your beautiful red > > earth > > they want to build them in our shiny white snow > >Hello Birmingham - To The Teeth - Ani > > > >
Bug#1003904: lsp-plugins 1.1.31-1 FTBFS on armhf
Package: lsp-plugins Version: 1.1.31-1 Severity: serious Justification: Policy 5.6.8 Dear Maintainer, lsp-plugins 1.1.31 FTBFS on armhf and therefore cannot migrate from proposed to release on ubuntu Jammy (future 20.04). Please specify architectures to build for in debian/control. Thanks, Erich Eickmeyer Ubuntu MOTU -- System Information: Debian Release: bullseye/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-17-lowlatency (SMP w/12 CPU cores; 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= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lsp-plugins depends on: ii lsp-plugins-jack1.1.31-1 ii lsp-plugins-ladspa 1.1.31-1 ii lsp-plugins-lv2 1.1.31-1 ii lsp-plugins-vst 1.1.31-1 lsp-plugins recommends no packages. Versions of packages lsp-plugins suggests: ii dgedit 0.10.0-1build1 -- no debconf information
Bug#1003903: RM: crda -- ROM; obsolete due to kernel changes
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: debian-ker...@lists.debian.org crda is used to load the data from wireless-regdb into the Linux kernel. Linux 4.15 implemented direct loading of the data by the kernel, and this is not an optional feature (whereas continued support for crda is). In our linux package we deferred that change until 5.5 as it required changes to data signing in wireless-regdb. Since bullseye released with Linux 5.10, I think we can expect that bookworm/unstable users will have at least that kernel version and will no longer need crda. Ben.
Bug#1002978: Another experiment, another GPU hang
My last experiment used these settings in /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=force intel_idle.max_cstate=1 i915.disable_power_well=1 i915.enable_dc=0" Although I had the GPU hang previously reported, the behavior wasn't too bad after that early blowup. So I didn't bother rebooting until today to try those options again, but with the intel-microcode package installed to see if microcode revision 0x2f, date = 2019-02-17 would help with the problem. About 25 minutes after rebooting, the GPU hung. Here is the output of /sys/class/drm/card0/error: GPU HANG: ecode 6:1:8500cfb9, in systemd-logind [659] Kernel: 5.10.0-10-amd64 x86_64 Driver: 20200917 Time: 1642445556 s 917357 us Boottime: 1393 s 992264 us Uptime: 1387 s 183171 us Capture: 4295240768 jiffies; 8157112 ms ago Active process (on ring rcs0): systemd-logind [659] Reset count: 0 Suspend count: 0 Platform: SANDYBRIDGE Subplatform: 0x0 PCI ID: 0x0102 PCI Revision: 0x09 PCI Subsystem: 1565:110d IOMMU enabled?: 0 RPM wakelock: yes PM suspended: no GT awake: yes EIR: 0x IER: 0x82bc8585 GTIER[0]: 0x00401001 PGTBL_ER: 0x FORCEWAKE: 0x DERRMR: 0x fence[0] = fde03b007f6001 fence[1] = 123400701135003 fence[2] = fence[3] = fence[4] = 39c501303570001 fence[5] = fence[6] = fence[7] = fence[8] = fence[9] = fence[10] = fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = ERROR: 0x DONE_REG: 0x rcs0 command stream: CCID: 0x7fff810d START: 0x1000 HEAD: 0x19201100 [0x0fb8] TAIL: 0x12b0 [0x1100, 0x1138] CTL: 0x3001 MODE: 0x4040 HWS: 0x7fffe000 ACTHD: 0x 7fff2358 IPEIR: 0x IPEHR: 0x7a02 ESR: 0x INSTDONE: 0xff00cfbb SC_INSTDONE: 0x03300c27 batch: [0x_7fff2000, 0x_7fff6000] BBADDR: 0x_7fff2359 BB_STATE: 0x0020 INSTPS: 0x820b INSTPM: 0x0280 FADDR: 0x 7fff2500 RC PSMI: 0x0010 FAULT_REG: 0x GFX_MODE: 0x7a800a05 PP_DIR_BASE: 0x7fdf engine reset count: 0 Active context: systemd-logind[659] prio 0, guilty 0 active 0, runtime total 0ns, avg 0ns rcs0 --- HW Status = 0x 7fffe000 :cL%-H!!!TsU+cQM'X4[[@$\^U?$3n"0X8q-c!4DlM rcs0 --- batch = 0x 7fff2000 :RcU&a<>97pRD6NS$Z!3,)[.h!Pbg&V7$4EI1(Y^jbPYff0m$gQi-:#Fe4LqtP[gc56&W?2+&*]\`PSGL?M%/TEIZ?;!eAW&=Tbhr]R5P.#n_Y]D[oi6Y\4!RD52G'_KR,D7+II)](gZ5Q6qn,2np?b!45hm&.C9b)s?Lb?8M?^PWfKY0Y9%UWE+J1_6m5/[.59OIO@SFd,i;W<1u8)HPgQrDKtP6B5A=cD&*/pLs=#>rL4]A%VUs7g-Iq3k"2dK[7J)@QRJ]Y*S)Ao-aNDK[bNB*V+Gp4]P1c7,O!>sUX9G#>[=@e@k5cG_&Rm7&HBRj,igZ3rjUF,M@r1OAC^Bpc0EL!L'l8opDf[nF%^0bZMTj]CMY0DmU\Gjk/Z`#>+"ZQH2`b&2Z7?dWKh"PnkYf^e0T1X=(t],jVj],ujGKD!m[E"e`KHAD9b$t>-PR$dem6=H"hFNdEp6+N0r0a?c6AB4#(I.H(KR/BFZZA,o#k@Df(??C=bZ\hrU'%adA6c!UBl?bj:Rj!\\Outb?$kp&-#_6MB:#WWee%A"T>S_71)`j%03;EO:LmF./h#1d!ee/MP-*5ubjIlM]F'91%.2Y?$V(DDdpCLbZr_:9%=bo7VT(S?'_^HC)sA'ak@+.20\Ndt_oQa@U>LOhJ1m1=KnhjEAdA_9q1s44;1^i-K=[g@,Bj?%*WZ(m_Mfrp?hNfgBU\ChbN?5rI,)k%/Ik2!+"DpJ'.W(A7R<1DT6,>_Cf]]M+0X?8EDVCYF^*`782Mjo@[?oF6Omc_n";,@;j4X6ctPem!Pj2MB(A)r:?4mY*[$$KX@?CEqk>I[J8G4GeqiOS'F0@kOsubcg>69lmK!tT(rq=J*%XK0o?Q;!r9h.XST9G_WJL@(B'(V.6-4kCZ>q`16CgGV_`36?Pm"c7^)L&T,9Z_0GjDZbmsDqs$9?/rd4FmML6TYg;\'cI(69hA@9OKFn/22W#ad`T4T^*b96CGiWIJ']s"U]ErK_]5#eETob)DSXj>Nd^\*WjrDWZ$DR!VWi+m.Qq)HlV5L(tFcaNq_I?O@pIQWG+;?&$PG5GD=dG3;I=i%3!5F4Kt^>9=khei_^1B3T^'A)/#/auEG;tf5.lBo?RVt\=5rqF04?E`3R;#)em*'\G6$N7sZ&]0n+?&6+bmkUPc46[A<)=K>R9+:FT>++^G\D6nfYF!QTrVd-%LF87f8tbSs@GD-[\.['j6T>fFr)9==N@>o$7o?S%R:N,jQ3U6$nj6Xn/,X2-958h's*u[eOh\`uNK88b[f*20[S+T.@O'2K"Ccpql(u+[P?07'[o9B965=li,@5gPeRtc.A)SM_n8WPSl2-Tk`*@?^T<<"H$sS#fn4S??QbX>*+p*JP)&Za=\dd*]`%rXlpF+8l?[nsNFQ:EkrR)U5`]qIcMj6*hnL@o%8jC<2r\/Q^!In8bq9mmT,C[^FBSZE!#Pc0mpqbg#OC'h%mscnZg7Rp^5s)i2N+>T\PJ@$RGWXgGd.YZ^M[+_l(;GtrO@l^r4+A+I)ur7M%@rOFibOTYC8/oQ6caXA*6s$7sG1:PqtgDBY$bS%BLX$!2-IOTE*_ScA/s.V.@[I`HEhd$I]S<*X0eIi$72Z'/lAE4O3VMPV5Q:;MLBIHt!4HMY rcs0 --- ring = 0x 1000 :fBo)Q5f6>WBCWtUMGamF:f(!i7Q@A,28MNfKs8&=I=qpG8\kdi#2hEOYUgc+,Ci*G;uV;qH20SI=S(eQelp:XV*=3!kXH;DYB,9\6a+T(MiJm#*?XN0Y?u`#3r(j<9:1cRDa,q>?TTpGf$!M.Q"LE2X>r,Xj7[T.?daCP0fSUo;U*f1=S]6e,X/7lHA4;.P-/rXI3NmK`]elG$T]s);1kk$QI#IjCZbr$hYD2"1=WIGA,df)<-Ifj?^Ig^b*r[.ZEr%7qHptPeEn9=h(pa>p)ptPa?3kt\f^[k+nJ(25kJ#Ro.s/CJan'_2!oKU1\ELI)]!!$O& rcs0 --- HW context = 0x 7fff8000 :R-gDgk>P=fp]L'6)gj,UVGeRuh#$"]$8&H3gGX/5-Zi7A2uP:f*HHAR`6XDdq4bB5O13F2&YUIJ`Jro)&IEF-!k[P[G=-d+Lf/%1J.+W81Ma%1H"@\'W>RpP<7lINW!]U$39LIf3=ipXNZq"GO*bs$]s2I0f51_'D&(;oCsDrlR]VcO]Kn:;YA56OTUK!8f$'3V)/&h:P<6\aAm/_j1=BH[t#c++^ZnSZZ,0#GY_$rPr7#MQfb'q\[EjuY_!X*]+JK/RoD.ReeDZ,e"N)%`Q&*sV@,@EZ>rSP*Om@3:E3Ua#HiVtq`<\%8=m,u"I]UUXY$H7;ho_1N'E'%q6dH"@%;5_,MTFf$_<)+5&R7#O%:IZO!Km;sRJH/_7/oDUsaXS]-EFukb613SK.G#Y_5!lVs'RF5Yhia?s]Y5gWFPA/tbGA@W7+)o6R1G9OM%ra!QKGj2X\@tQ9!PDR84V#6_A8J][=eAq,5g45AbuHua[BkB[..dIre#+T.*]U8f,KS2
Bug#1003902: RFP: grafana-dashboard-manager -- Import and export Grafana dashboards for backup and dynamic provisioning
Package: wnpp Severity: wishlist * Package name: grafana-dashboard-manager Version : N/A (no official release) Upstream Author : https://github.com/Beam-Connectivity * URL : https://github.com/Beam-Connectivity/grafana-dashboard-manager * License : MIT Programming Lang: Python Description : Import and export Grafana dashboards for backup and dynamic provisioning A simple cli utility for importing or exporting dashboard json definitions using the Grafana HTTP API. This may be useful for: * Backing up your dashboards that already exist within your Grafana instance, e.g. if you are migrating from the internal sqlite database to MySQL. * Updating dashboard files for your Infrastructure-as-Code, for use with Grafana dashboard provisioning. * Making tweaks to dashboard JSON files directly and updating Grafana with one command. Notable features: * Mirrors the folder structure between a local set of dashboards and Grafana, creating folders where necessary. * Ensures links to dashboards folders in a dashlist Panel are consistent with the Folder IDs - useful for deploying one set of dashboards across mulitple Grafana instances, e.g. for dev, test, prod environments. --- Grafana itself is not packaged in Debian (http://bugs.debian.org/923872) but we should still be able to package tools like this that make it easier to operate the service. This package doesn't, as far as I can tell, depend on Grafana itself. I might eventually get tired of our system for maintaining dashboards and package this, but for now this is just a RFP. I will change the title and owner when / if I do start working on this.
Bug#976811: [pkg-php-pear] Bug#976811: transition: php8.1
Hi, On 17-01-2022 06:49, Kunal Mehta wrote: I don't have any i386 hardware, I tried pulling down a i386 Debian unstable Docker container on my amd64 laptop and installing the mediawiki+php8.1 packages on that but it didn't trigger the test failure. Do you have any other suggestions/tips on how I could debug this? The test is flaky, did you run it multiple times? And did you install php-defaults/92? I don't know how to use Docker, I create i386 lxc for these [1] (but I think Docker does the same), that's also how they are created on the ci.d.n infrastructure. As an alternative I just committed [4] which would hopefully dump the underlying error message upon failure. Please let me know if it's OK for me to upload that without it being disruptive. That works. Personally I would copy them to the artifacts folder instead of dumping them in the log (to not pollute the log), but whatever. If we raise confidence in php itself (and can blame mediawiki for these failures), I'm all for it. Paul [1] sudo autopkgtest-build-lxc debian unstable i386 OpenPGP_signature Description: OpenPGP digital signature
Bug#1003901: librsync: New upstream release (2.3.2, 2021 Apr 10)
Source: librsync Severity: wishlist Hello there, https://github.com/librsync/librsync/releases/tag/v2.3.2 lists: | This is a patch release that fixes some minor bugs, tidies the code for | many compiler warnings, and improves windows compatibility. Upgrading | from v2.3.1 is recommended for most people, and essential for people | using platforms experiencing bugs #214 or #207. | [...] | The debian package configs are still very out of date. Please update the package when you think it is due time. Cheers, Flo signature.asc Description: PGP signature
Bug#986294: New upstream 0.45.1 available
retitle 986294 New upstream 0.45.2 available thanks On Sat, Jun 05, 2021 at 09:39:19PM -0300, Leandro Doctors wrote: > Please check https://github.com/hanslub42/rlwrap/releases/latest FWIW, this now lists v0.45.2 as the latest. Cheers, Flo signature.asc Description: PGP signature
Bug#1003900: linux-image-5.10.0-10-amd64: After upgrade to bullseye: DMA Read .. Request device ... PASID ffffffff fault addr ... DRHD: handling fault status reg 2
Package: src:linux Version: 5.10.84-1 Severity: normal X-Debbugs-Cc: les...@dubiel.pl After upgrading from bullseye to buster there is huge amount of errors: [10122.779046] dmar_fault: 842 callbacks suppressed [10122.779047] DMAR: DRHD: handling fault status reg 2 [10122.779060] DMAR: [DMA Read] Request device [05:00.0] PASID fault addr ff8ed000 [fault reason 06] PTE Read access is not set [10122.900275] DMAR: DRHD: handling fault status reg 2 [10122.900287] DMAR: [DMA Read] Request device [05:00.0] PASID fault addr ff891000 [fault reason 06] PTE Read access is not set [10122.923105] DMAR: DRHD: handling fault status reg 3 [10122.923118] DMAR: [DMA Read] Request device [05:00.0] PASID fault addr ff8ab000 [fault reason 06] PTE Read access is not set [10122.926187] DMAR: DRHD: handling fault status reg 2 [10133.964234] dmar_fault: 371 callbacks suppressed #lspci -vv: 05:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 18 IOMMU group: 14 Region 0: I/O ports at c000 [size=256] Region 1: Memory at f782 (32-bit, non-prefetchable) [size=256] Expansion ROM at f780 [disabled] [size=128K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: r8169 Kernel modules: r8169 # dmesg | grep 'Read access' -C50 | head -n70 [ 36.918796] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card0/input6 [ 36.918847] input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.0/sound/card0/input7 [ 36.91] input: HDA Intel HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.0/sound/card0/input8 [ 36.925864] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card2/input9 [ 36.926842] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card2/input10 [ 36.926970] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card2/input11 [ 36.927694] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card2/input12 [ 37.081772] snd_hda_codec_realtek hdaudioC1D2: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [ 37.081774] snd_hda_codec_realtek hdaudioC1D2: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 37.081775] snd_hda_codec_realtek hdaudioC1D2: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [ 37.081776] snd_hda_codec_realtek hdaudioC1D2: mono: mono_out=0x0 [ 37.081776] snd_hda_codec_realtek hdaudioC1D2: dig-out=0x11/0x0 [ 37.081777] snd_hda_codec_realtek hdaudioC1D2: inputs: [ 37.081778] snd_hda_codec_realtek hdaudioC1D2: Rear Mic=0x18 [ 37.081779] snd_hda_codec_realtek hdaudioC1D2: Front Mic=0x19 [ 37.081779] snd_hda_codec_realtek hdaudioC1D2: Line=0x1a [ 37.081780] snd_hda_codec_realtek hdaudioC1D2: CD=0x1c [ 37.081780] snd_hda_codec_realtek hdaudioC1D2: dig-in=0x1f [ 37.097665] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/sound/card1/input13 [ 37.097709] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card1/input14 [ 37.098126] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card1/input15 [ 37.098162] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input16 [ 37.098197] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1b.0/sound/card1/input17 [ 37.098618] snd_hda_intel :00:1b.0: device 1458:a002 is on the power_save denylist, forcing power_save to 0 [ 37.160844] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 37.351840] [TTM] Zone kernel: Available graphics memory: 8134362 KiB [ 37.351842] [TTM] Zone dma32: Available graphics memory: 2097152 KiB [ 37.351843] [TTM] Initializing pool allocator [ 37.351846] [TTM] Initializing DMA pool allocator [ 37.351879] nouveau :01:00.0: DRM: VRAM: 1024 MiB [ 37.351880] nouveau :01:00.0: DRM: GART: 1048576 MiB [ 37.351883] nouveau :01:00.0: DRM: TMDS table version 2.0 [ 37.351884] nouveau :01:00.0: DRM: DCB version 4.0 [ 37.351885] nouveau :01:00.0: DRM: DCB outp 00: 02000300 [ 37.351886] nouveau :01:00.0: DRM: DCB outp 01: 01000302 00020030 [ 37.351887] nouveau :01:00.0: DRM: DCB outp 02: 02021362 00020010 [ 37.351887] nouvea
Bug#1003899: wavemon: New upstream release (v0.9.4, 2021 Sep 18)
Package: src:wavemon Severity: wishlist Hello there, there are some new upstream releases available, the latest is v0.9.4 from 2021 Sep 18, as also noticed by uscan. Please update when you think it is due time. Cheers, Flo signature.asc Description: PGP signature
Bug#1003895: [Pkg-pascal-devel] Bug#1003895: lazarus: undefined reference to QLCLOpenGLWidget
Hi Stephan, On Mon, 2022-01-17 at 20:50 +0100, Stephan Lachnit wrote: > ... > Dear maintainer, > > it looks like the update to 2.2.0 broke the Qt OpenGL Widget. I tried to > compile goverlay [1] with the new version, but it fails with the following > error message: There are more things broken unfortunately. I'm fixing them one by one and I hope I can fix them all soon. Help is welcome of course. > ... > > Maybe this is because libqtpas has not been updated for 2.2.0? This is possible. I'll upload a new qt5 soon. > If so, maybe it makes sense to rethink the decision of #922296 again to > prevent > this happening again in the future. I'll check this again to refresh my memory and we can talk about it. > > [1] https://salsa.debian.org/games-team/goverlay Nice tool, glad to see tools like that written with FPC+Lazarus. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#913794: qpdfview document "focus"
tags 913794 moreinfo unreproducible thanks Hello, I've tried to reproduce this issue on the latest version in Debian (0.4.18-6) and have been unsuccessful. I tried a bunch of things, enabled auto-refresh and even tried to update a PDF generated with pandoc, but I always get a proper focus. I'm on openbox though... I'd be curious to know what Desktop environment you are using, and if you can reproduce this bug in another one. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#1003898: pseudo: fakeroot wrapper script doesn't handle multiple concurrent pseudo instances
Package: pseudo Version: 1.9.0+git2021+300d7570720b-1 Severity: normal This may be problematic: fakeroot cat /dev/random | fakeroot tee /tmp/foobar This is not supposed to happen often, but at the moment it’s not handled at all. -- Cheers, Andrej
Bug#1003089: man-db has become prohibitively slow
On Mon, Jan 17, 2022 at 04:10:02AM +, Colin Watson wrote: > Significant progress! See the end of this email. Thanks for dealing with this. I'm deleting most of your text, but be sure that I've read it :-) And I understand most of it (although I of course disagree at some points, I think those are beside the discussion). > We definitely do need to sort out encoding conversion, though. Although > UTF-8 has been recommended for many years, policy still allows "the > usual legacy encoding" and we've never got round to mandating UTF-8: > > $ w3m -dump https://lintian.debian.org/tags/national-encoding | grep > --count usr/share/man > 502 I tried looking at this, but TBH I don't think the man-db path _ever_ inserts a conversion. The parameter to the lexer path is simply always NULL in all calls, except for from a test. Am I missing something? > I've been experimenting with a few things, and I think the most elegant > way to do this is in fact to add another layer of abstraction! This is > a much cheaper one, though. If instead of returning a pipeline we have > decompress_open return a new tagged union type, we can clone the simple > pipeline_{read,peek}* functions on top of that, and convert everything > over to use those rather than talking to libpipeline directly; the > functions that specifically need pipeline support (mainly in man(1), but > also things like the cat page case in lexgrog.l) can ask to drop down to > a lower level. This sounds fine to me. It's not something I would pick if I maintained the code myself, but I'm obviously not doing that, and I don't see anything in it that would preclude optimization. :-) > Would you care to have a look at this? > > https://gitlab.com/cjwatson/man-db/-/merge_requests/2 Thanks! I'll have a go at a review, but it might need to wait until the end of the week. I'll try to get it done earlier, though. How would you like any review comments? Email or somehow in Gitlab? > There's probably still room for improvement, but unlikely to be much > more than a factor of two or so at this point, and I think this should > get us comfortably back to the point where it's no longer annoying > people during upgrades. Someone else suggested an idea I thought of throwing around: In addition to optimizing the code, perhaps the postinst trigger should simply launch the man-db timer in the background? At least for systemd users, this should be pretty straightforward, and give the control back to the installation process. (Given that dpkg is very much single-threaded, we're not generally throughput-bound, so using up a core shouldn't be a big problem.) /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#827566: qpdfview: search option 'whole words' doesn't work
found 827566 0.4.18-6 thanks I can reproduce this issue on the current Debian Sid, using an obviously more recent version of Poppler: PDF support using Poppler 20.09.0 PS support using libspectre 0.2.9 DjVu support using DjVuLibre 3.5.28 PDF support using Fitz Printing support using CUPS 2.3.3op2 There's currently no upstream bug about this. I'm still looking at the Debian patches / how we build this package, but if I don't find anything, I'll forward this and try to get help :) -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#1003897: acpi: ACPI errors at startup
Package: acpi Version: 1.7-1.1 Severity: grave Justification: causes non-serious data loss X-Debbugs-Cc: garraudmag...@hotmail.fr Dear Maintainer, I have moved some weeks ago from Windows to Debian. I'm almost happy with that but i still face an issue during the boot with ACPI. I have updated the Bios with latest Dell firmware without any change. Could anyone help me understanding the error bug message and how to fix it please ? Here is my config : Dell Inc. Latitude 5424 Rugged Memory : 31.2 GiB Processor : Intel® Core™ i7-8650U CPU @ 1.90GHz × 8 Graphics : AMD® Radeon 500 series / Mesa Intel® UHD Graphics 620 (KBL GT2) Disk : 1.0 TB NVME OS : Debian GNU/Linux bookworm/sid version testing OS type : 64 bits Gnome : 41.2 And here are the dmesg | grep error messages : [ 0.317572] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.317623] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.317672] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.349328] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.349375] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.349419] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.401925] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.401949] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.401969] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.542739] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.542846] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.542945] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.571399] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.575373] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.579438] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.657970] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.660572] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.663228] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Thanks in advance, -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages acpi depends on: ii libc6 2.33-2 acpi recommends no packages. acpi suggests no packages. -- no debconf information
Bug#1003896: FTBFS: t/1.t: Failed 2/6 subtests
Source: libclass-dbi-plugin-type-perl Version: 0.02-7 Severity: serious Tags: upstream ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As noted by ci.debian.net, libclass-dbi-plugin-type-perl fails its testuite, also reproducibly during build: dh_auto_test make -j4 test TEST_VERBOSE=1 make[1]: Entering directory '/build/libclass-dbi-plugin-type-perl-0.02' PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t # Failed test 'notes is text' # at t/1.t line 28. # 'TEXT' # doesn't match '(?^:text|blob)' # Failed test 'id is integer' # at t/1.t line 31. # 'INT' # doesn't match '(?^:^int)' # Looks like you failed 2 tests of 6. t/1.t .. 1..6 ok 1 - use Class::DBI::Plugin::Type; not ok 2 - notes is text ok 3 - tasted is a date ok 4 - price is decimal not ok 5 - id is integer ok 6 - name is varchar Dubious, test returned 2 (wstat 512, 0x200) Failed 2/6 subtests Test Summary Report - --- t/1.t (Wstat: 512 Tests: 6 Failed: 2) Failed tests: 2, 5 Non-zero exit status: 2 Files=1, Tests=6, 0 wallclock secs ( 0.01 usr 0.01 sys + 0.08 cusr 0.00 csys = 0.10 CPU) Result: FAIL Failed 1/1 test programs. 2/6 subtests failed. make[1]: *** [Makefile:825: test_dynamic] Error 2 There are some old but similar upstream tickets: https://rt.cpan.org/Public/Bug/Display.html?id=130055 https://rt.cpan.org/Public/Bug/Display.html?id=128135 which point to (DBD::)SQLite as a possible reason, and libdbd-sqlite3-perl indeed had a new upload to unstable ~2 weeks ago. Cheers, gregor - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmHlyt5fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbEng/8DNe4lwPjQbFgbPbxc8ArhM5ewnzXkQVT6rpAG47m8VlRTrifP1SF1wJs vOL9HhXV8MRoFmt0zZISeM1XVwAUVnQbXl1yp0lItFMtuIfYIL3u5cnBtC+KtLGf D/RvaGq++FJSMAg44nxApNXgyJP+ssVE4s5oRrWuDG+V7Yih4vU7PMbwosa8vcxM FL2Ybe8QiOa6LBjEki4kgj5R3C6xEk2z+YtyOiphm2Yb+71L+gTd9O6SIo1u+vIC fN50/9g9IclQxajzFc0rwlMf7cWw+DCbOzKsPiNGlnT2ir50NTHK87NngIcu9fOi 4Fn/HOfV8EtmxjSQleyMSmcjOpmfk3PRh/wnzg24LsrLTlsiU/yGtoDCaVXBUds5 ump5r0iv0fOW4ybO7MWEeb8YX8stqweuIcJP4Z29R5OGOC9i9QX6+11E6LknXz3S bWRNfclsoa6xZxKkAX7z9NKhpRmsLGqtJLtiSjLGOYhyHpzLUGwZQywyYOT56u9Y WWE09pDBljNmPCGiBzteQPA7c6wKLIygydtBdeGmBPSomFpOLyBIp89vH/i3LYjb hpqQua9gY55d/GXYdGPijN2iYxx6Iy6wdgcJxPlrML1Prhxla84ZlFJyCWC0Qp0G BmvtnuExvwsDT1h/yuiNa+LuC+wsi1X1aO7B/YnjTKynYt/vIOc= =/mGQ -END PGP SIGNATURE-
Bug#990887: tig: Please update to 2.5.4
retitle 990887 tig: Please update to 2.5.5 thanks On Sat, Jul 10, 2021 at 04:12:40PM +0200, Elimar Riesebieter wrote: > there is a new release available: Now there is https://github.com/jonas/tig/releases/tag/tig-2.5.5, and I can confirm that the current packaging still allows to build a .deb from it. Cheers, Flo signature.asc Description: PGP signature
Bug#918180: man page SYNOPSIS should reflect -c, -i are required
Control: tag -1 wontfix On Fri, 04 Jan 2019 08:58:26 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: So please change the man page: wpa_supplicant [ -BddfhKLqqsTtuvW ] -iifname -cconfig file [ -Ddriver ] [ -PPID_file ] [ -foutput file ] Because -c and -i are not "optional" but required. Neither -c nor -i are required. -- Cheers, Andrej
Bug#1003860: RFS: makemkv-oss/1.16.5-1 [ITP] -- Convert video that you own into free format that can be played everywhere
Hello, Mathias! It looks like you're basing your packaging work off of the packages I've created and made available; that's wonderful, and I'm glad they were a good starting point. However, I think it would be appropriate (at a minimum) to provide credit in d/copyright. Here's the story: I was planning to package MakeMKV, so I checked for ITPs to see if there was anyone else working on it. Since there were none, I believed I was the first to try. I was almost done packaging, then I found your packages while searching for a resolution to a specific problem. Since my attempt wasn't very good, I took the best parts of both of ours and put them together into a better package. I fully intended to credit you at the end, but I forgot by the time I was ready to upload to put that in. I will now add a credit to d/copyright. The d/rules file I created for the makemkv-bin package is quite hacky, and work should probably be done to get that into nicer shape if the package is going to be included in the archive. Yes, I agree, but debian/rules etiquette isn't my forte, so I'm not sure of the best way to improve/rewrite it. Suggestions are always welcome. The makemkv-oss package has a lot of vendored libraries. I've tried in the past to remove them, and found that some (like libmatroska) are sufficiently different from the versions in bullseye that they cannot be easily replaced with system libraries. (For instance, see this thread where the libmatroska issue was found: https://forum.makemkv.com/forum/viewtopic.php?p=111826) I foresee this as the largest hurdle to actually getting packages accepted into Debian. Since this package is for sid/bookworm and not bullseye, the system libmatroska should be newer, and I haven't seen any significant problems with using it yet, though I admit I haven't thoroughly tested the finished package yet. Is there a particular reason why you're using debhelper-compat version 12, rather than 13? I'm not sure, I meant to use 13. I'll fix that as well. Mathias, thank you so much for both your original packaging and the help here. I really appreciate it, as I'm new to Debian packaging and not as familiar with the source code of MakeMKV as you seem to be. Now I can see the fact that I might not be the best maintainer of this package and there are others that could do a better job than me. Would you like to be co-maintainer of this package? You contributed the majority of the actual package contents and you seem to be a lot better at this than me. -- Ben Westover OpenPGP_0xC311C5F54E89B698.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1003859: libtest-spelling-perl: library prefers hunspell, but that is listed last in package dependencies
On Mon, 17 Jan 2022 20:44:35 +0100, Jonas Smedegaard wrote: > Quoting gregor herrmann (2022-01-17 20:33:47) > > On Mon, 17 Jan 2022 01:31:50 +0100, Jonas Smedegaard wrote: > > > Test::Spelling documents that it picks hunspell if available. > > I've made some changes in git, maybe you want to take a look if this > > matches your ideas? > > Looks good to me. Thanks! Thanks for checking! Uploaded. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1003895: lazarus: undefined reference to QLCLOpenGLWidget
Source: lazarus Version: 2.2.0+dfsg-2 Severity: important X-Debbugs-Cc: stephanlach...@debian.org, abou.almonta...@sfr.fr Control: affects -1 src:goverlay Dear maintainer, it looks like the update to 2.2.0 broke the Qt OpenGL Widget. I tried to compile goverlay [1] with the new version, but it fails with the following error message: (9015) Linking /<>/goverlay /usr/bin/ld.bfd: ./debian/.debhelper/generated/_source/home/.lazarus/lib/LazOpenGLContext/lib/x86_64-linux/qt5/qlclopenglwidget.o: in function `CREATEWIDGET': /usr/lib/lazarus/2.2.0/components/opengl//qlclopenglwidget.pas:58: undefined reference to `QLCLOpenGLWidget_Create' /usr/bin/ld.bfd: ./debian/.debhelper/generated/_source/home/.lazarus/lib/LazOpenGLContext/lib/x86_64-linux/qt5/qlclopenglwidget.o: in function `PAINTGL': /usr/lib/lazarus/2.2.0/components/opengl//qlclopenglwidget.pas:65: undefined reference to `QLCLOpenGLWidget_InheritedPaintGL' /usr/bin/ld.bfd: ./debian/.debhelper/generated/_source/home/.lazarus/lib/LazOpenGLContext/lib/x86_64-linux/qt5/qlclopenglwidget.o: in function `ATTACHEVENTS': /usr/lib/lazarus/2.2.0/components/opengl//qlclopenglwidget.pas:75: undefined reference to `QLCLOpenGLWidget_override_paintGL' /usr/bin/ld.bfd: ./debian/.debhelper/generated/_source/home/.lazarus/lib/LazOpenGLContext/lib/x86_64-linux/qt5/qlclopenglwidget.o: in function `DETACHEVENTS': /usr/lib/lazarus/2.2.0/components/opengl//qlclopenglwidget.pas:83: undefined reference to `QLCLOpenGLWidget_override_paintGL' /<>/goverlay.lpr(27,1) Error: (9013) Error while linking Maybe this is because libqtpas has not been updated for 2.2.0? If so, maybe it makes sense to rethink the decision of #922296 again to prevent this happening again in the future. Regards, Stephan [1] https://salsa.debian.org/games-team/goverlay -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: 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) LSM: AppArmor: enabled
Bug#1003859: libtest-spelling-perl: library prefers hunspell, but that is listed last in package dependencies
Quoting gregor herrmann (2022-01-17 20:33:47) > On Mon, 17 Jan 2022 01:31:50 +0100, Jonas Smedegaard wrote: > > > Test::Spelling documents that it picks hunspell if available. > > I've made some changes in git, maybe you want to take a look if this > matches your ideas? > > If you'd like to cut down the list of spell checkers and dictionaries > to just hunspell and hunspell-en-us and/or move them from Recommends > to Depends, that also works for me (although in pratice any of the > spell checkers probably work just fine). Looks good to me. Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#807115: qpdfview: Screen jumps when scrolling via touchpad
forwarded 807115 https://bugs.launchpad.net/qpdfview/+bug/1696116 thanks Hello, Looking at the upstream bugs, this seems to be the issue: https://bugs.launchpad.net/qpdfview/+bug/1696116 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#1003894: h2database: CVE-2021-42392
Source: h2database Version: 1.4.197-4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for h2database. CVE-2021-42392[0]: | The org.h2.util.JdbcUtils.getConnection method of the H2 database | takes as parameters the class name of the driver and URL of the | database. An attacker may pass a JNDI driver name and a URL leading to | a LDAP or RMI servers, causing remote code execution. This can be | exploited through various attack vectors, most notably through the H2 | Console which leads to unauthenticated remote code execution. 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-2021-42392 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42392 [1] https://github.com/h2database/h2database/security/advisories/GHSA-h376-j262-vhq6 [2] https://jfrog.com/blog/the-jndi-strikes-back-unauthenticated-rce-in-h2-database-console/ Regards, Salvatore
Bug#1003864: libreoffice-help-it: Libreoffice help depends from Firefox-esr package
severity 1003864 wishlist retitle 1003864 please don' t depend on browsers thanks Am 17.01.22 um 08:57 schrieb Antonio: Severity: normal Why? It's doing that it is intended to do. If I try to install the LibreOffice help, the Firefox-esr package is automatically installed. That is not new. That is there since ~ 3.5 years... Just because it is the first alternative. As the reportbug info you posted said itself: pn firefox-esr | epiphany-browser | konqueror | chromium | fire firefox-esr OR epiphany-browser OR konqueror OR chromium OR firefox (thought that list probably should be reordered?) Why is this? Becuase the help DOES need a X (well, JavaScript-capable, and the nongui browsers can't) browser. Without that there would be an error (or even worse: nothing happen) when opening the help. One might argue it can be a Recommends: (then only people who don't install recommends per default don't get it, but) Regards, Rene
Bug#1003859: libtest-spelling-perl: library prefers hunspell, but that is listed last in package dependencies
On Mon, 17 Jan 2022 01:31:50 +0100, Jonas Smedegaard wrote: > Test::Spelling documents that it picks hunspell if available. I've made some changes in git, maybe you want to take a look if this matches your ideas? If you'd like to cut down the list of spell checkers and dictionaries to just hunspell and hunspell-en-us and/or move them from Recommends to Depends, that also works for me (although in pratice any of the spell checkers probably work just fine). Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1003892: src:python-dropbox: fails to migrate to testing for too long: depends on new binary with unresolved RC bug
Hi, On Mon, 17 Jan 2022 19:58:27 +0100 Paul Gevers wrote: Source: python-dropbox You can ignore this report (I hope). The RC bug was resolved, but the bts isn't perfect in handling bugs assigned to two packages. I (hopefully) fixed that. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1003808: libvcflib: reproducible-builds: BuildId differences triggered by RPATH
On 2022-01-17, Andreas Tille wrote: > are you sure you picked the right code to patch? The code in Git[1] > is very different from the chunk your patch claims to replace. While > I could easily add -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON to dh_auto_configure > but I wanted to make sure that there is no other package you intended > to fix that way. Oops, must have gotten the patch mixed up with another package! The originally intended patch should be attached. live well, vagrant From b7e78e09b4c2f4589f33f987718640a49d5f719f Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Sun, 16 Jan 2022 01:44:10 + Subject: [PATCH] debian/rules: Pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON via dh_auto_configure override. This avoids embedding the full path in RPATH, which triggers BuildId differences. https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index f8da7b8..1e87b1f 100755 --- a/debian/rules +++ b/debian/rules @@ -20,7 +20,7 @@ override_dh_auto_clean: dh_auto_clean || true override_dh_auto_configure: - dh_auto_configure -- -DOPENMP=ON + dh_auto_configure -- -DOPENMP=ON -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON override_dh_auto_build: dh_auto_build -- 2.34.1 signature.asc Description: PGP signature
Bug#878399: qpdfview: some documents can make it crash with SIGPIPE
severity 878399 normal tags 878399 moreinfo unreproducible thanks Hi, Thanks for reporting this bug. I understand it's been five years; I'm the new qpdfview maintainer in Debian. I cannot download the PDF in question, as the link you gave end ups in "You cannot access this document". Could you please check if this still happens on the latest version of qpdfview (0.4.18-6) ? Until then, I'll downgrade the severity of this bug and mark is as unreproducible. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#927673: new upstream version
Just for the records: It seems that the build dependencies listed by current ZK 3.7.0’s README_packaging.md would be as follows: libcppunit-dev python-setuptools python2.7-dev openssl libssl-dev libsasl2-modules-gssapi-mit libsasl2-modules libsasl2-dev But python2.7-dev didn't really seem to be necessary. Instead I had to install the following unlisted to make everything build: libtool pkg-config (contains some automake makro that is used) autoconf automake But I guess these are only needed when building the C client. Cheers, Chris.
Bug#1003313: [pkg-gnupg-maint] Bug#1003313: closed by Debian FTP Masters (reply to Daniel Kahn Gillmor ) (Bug#1003313: fixed in libgpg-error 1
On Sat 2022-01-15 10:43:13 +0100, Helmut Grohne wrote: > I disagree. The version proposed by me was: > >> -*-*-linux-gnu*) >> +*-*-linux-*) > > The version that actually ended up upstream was: > > +*-*-linux-gnu* | *-*-linux-musl) > > The thing that it doesn't match is: > > arm-linux-musleabihf Thanks for this followup, Helmut, and for your persistence. I've re-opened the upstream bug report with this information. If upstream agrees that this makes sense, i'm happy to update the patch for the debian package. i appreciate your work on getting (and keeping) alternate debian architectures in healthy shape! This is an important backstop for f/loss ecosystem health. --dkg signature.asc Description: PGP signature
Bug#1003893: pseudo breaks tar and thereby building python2.7
Package: pseudo Version: 1.9.0+git2021+300d7570720b-1 Severity: critical Justification: unrelated packages are broken by pseudo Control: affects -1 + tar I was faced with a very strange python2.7 build failure: | (cd debian/tmp && tar cf - .) | (cd debian/python2.7 && tar xpf -) | abort()ing pseudo client by server request. See https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this. | Check logfile: /tmp/pseudo.1000/2734893/pseudo.log | /bin/bash: line 1: 2753698 Aborted (core dumped) tar xpf - | make: *** [debian/rules:908: stamps/stamp-install] Error 134 | dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 It took me a while to figure that pseudo provides fakeroot and fakeroot was selected for installation instead of fakeroot. No clue why, but this happens. So the actual issue is that pseudo makes tar segfault. I have not figure why that happens, but I crafted a reproducer: | mmdebstrap --verbose --variant=apt --format=null --include=pseudo --customize-hook='chroot $1 sh -c "fakeroot tar -C lib -c -f - . | fakeroot tar -C /tmp/ -xv"' unstable /dev/null Running this ends with: | I: running --customize-hook in shell: sh -c 'chroot $1 sh -c "fakeroot tar -C lib -c -f - . | fakeroot tar -C /tmp/ -xv"' exec /tmp/mmdebstrap.0uWKm7mGmi | ./ | ./lsb/ | ./lsb/init-functions | ./lsb/init-functions.d/ | ./lsb/init-functions.d/00-verbose | ./init/ | abort()ing pseudo client by server request. See https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this. | Check logfile: /tmp/pseudo.0/1728/pseudo.log | Aborted (core dumped) | umount: /tmp/mmdebstrap.0uWKm7mGmi/dev/null: target is busy. | umount ./dev/null failed: 8192 at /usr/bin/mmdebstrap line 1067. | cannot unlink ./dev/null: Device or resource busy at /usr/bin/mmdebstrap line 1070. | E: run_chroot failed: E: command failed: chroot $1 sh -c "fakeroot tar -C lib -c -f - . | fakeroot tar -C /tmp/ -xv" | W: listening on child socket failed: | I: removing tempdir /tmp/mmdebstrap.0uWKm7mGmi... Any of the following actions resolve this bug: * Removing pseudo from the archive. * Having pseudo stop providing fakeroot. * Having pseudo stop making tar segfault. Helmut
Bug#1003892: src:python-dropbox: fails to migrate to testing for too long: depends on new binary with unresolved RC bug
Source: python-dropbox Version: 10.10.0-1 Severity: serious Control: close -1 11.25.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:python-dropbox has been trying to migrate for 72 days [2]. Hence, I am filing this bug. Your package grew a new dependency on src:python-stone which fails to migrate due to an unresolved RC bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=python-dropbox OpenPGP_signature Description: OpenPGP digital signature
Bug#1003706: ITS: sofia-sip
Hi, On Fri, 14 Jan 2022 01:24:23 +0100 Jonas Smedegaard wrote: > Source: sofia-sip > Version: 1.12.11+20110422.1-2.1 > Severity: important > X-Debbugs-Cc: Ron Lee > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Dear Ron, > > It seems sofia-sip is not actively maintained, and I hereby request to > salvage the package. > > The package has seen no uploads from you for 8 years, an NMU was made 5 > years ago seemingly uncommented by you, and several important bugs have > been open for several years with no comment from you. > > Point is not to point fingers, only to elaborate on why I propose that > salvation is needed and I thereby initiate that process. If you prefer > to maintain the package yourself then that's great - please do. > > As per the salvaging process, I now give you some some time to respond, > and otherwise will issue a delayed NMU which effectuates my salvation. > > (I will most likely salvage as part of the VoIP team, and maintain it > together with Evangelos, in case someone wonders about how this might > collide/relate with the discussion in bug#965829). Happy to be working with you in case this package gets salvaged. > > > Kind regards, > > - Jonas > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHgwrIACgkQLHwxRsGg > ASHuXg/+N35mRC4wIB8X0nrnYr13PNSMuAZTxNJ7i2r3ew5rvTidCVJD7iGHx60z > uzocaTriKF7EhFH8HfRzoZ8gjyeGq35JLip/WgDnGKgmysl5GeMk7mfV3s1Glp3o > +IoJw9M37lBfljyCleHzV0CTE6fk+0xdVC/ZW257xOn8LYjuYc3GWj0JRmsAK7+q > MtWckVLwsFN4zz+bUWXgiUiWnLvh/jaFBUrxHIW8iw1iECW5FD2IVRY4l6LcdBM0 > ZRUJoDpy/A79LGcsa1kELz1TrN2adwXnUHu4RgHuPRrJHvKcTgMqKdYLI1S65sgE > UDy+CuFo2mW9KVP+VilxNC+q65JODdnQVzXaxttjHnzx7XsxHEqP5XnMaqOJWuei > SdXkPvP4pA5w8xV1rx80khojEcprGjuY1eVLqMNulGkpaLe3rkuLQ6YSOkYI8CZ4 > bOLWXvoPFLVbx57ciImvbdbM8mP2GERHwYROvuy64hTvxSg//v7CIkgnQbQ1xo60 > irKh2UQ23qNCiabWLIdcxjFKi8zARYQZHB1f5lRRrIw7e7ugNk2633dinfXceMXg > 6gyr98TGwEWAiEMA5GpU4j2Ueb3pD5Q16Dzioqh3io0fFI//mqYdcXjc0C6nzgo3 > 4r+7O0SBpxRK20AC8Vnmu56jsk+wivphpiz0P+Q6YudFAQuzEVo= > =gIB5 > -END PGP SIGNATURE- > > Cheers -- Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1003890: ceph-mgr won't start when backported to Bullseye
Package: ceph-mgr Version: 16.2.7+ds-4 Severity: wishlist Hi, I downloaded ceph sources from unsable, and compiled sucessfully on Bullseye. However once installed/upgraded over from bullseye version of the packages I can not start ceph-mgr on any node. At first I was getting an error about the pg_autoscaler module: Jan 17 12:10:45 pyre systemd[1]: Started Ceph cluster manager daemon. Jan 17 12:10:47 pyre ceph-mgr[63427]: context.c:56: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second time Jan 17 12:10:47 pyre ceph-mgr[63427]: context.c:56: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second time Jan 17 12:10:47 pyre ceph-mgr[63427]: context.c:56: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second time Jan 17 12:10:48 pyre ceph-mgr[63427]: context.c:56: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second time Jan 17 12:10:54 pyre ceph-mgr[63427]: 2022-01-17T12:10:54.556-0500 7fa9217fa700 -1 log_channel(cluster) log [ERR] : Unhandled exception from module 'pg_autoscaler' while running on mgr.pyre: (-18,) Jan 17 12:10:54 pyre ceph-mgr[63427]: 2022-01-17T12:10:54.556-0500 7fa9217fa700 -1 pg_autoscaler.serve: Jan 17 12:10:54 pyre ceph-mgr[63427]: 2022-01-17T12:10:54.556-0500 7fa9217fa700 -1 Traceback (most recent call last): Jan 17 12:10:54 pyre ceph-mgr[63427]: File "/usr/share/ceph/mgr/pg_autoscaler/module.py", line 272, in serve Jan 17 12:10:54 pyre ceph-mgr[63427]: self._maybe_adjust() Jan 17 12:10:54 pyre ceph-mgr[63427]: File "/usr/share/ceph/mgr/pg_autoscaler/module.py", line 608, in _maybe_adjust Jan 17 12:10:54 pyre ceph-mgr[63427]: ps, root_map = self._get_pool_status(osdmap, pools, profile) Jan 17 12:10:54 pyre ceph-mgr[63427]: File "/usr/share/ceph/mgr/pg_autoscaler/module.py", line 565, in _get_pool_status Jan 17 12:10:54 pyre ceph-mgr[63427]: root_map, overlapped_roots = self.get_subtree_resource_status(osdmap, crush_map) Jan 17 12:10:54 pyre ceph-mgr[63427]: File "/usr/share/ceph/mgr/pg_autoscaler/module.py", line 341, in get_subtree_resource_status Jan 17 12:10:54 pyre ceph-mgr[63427]: roots, overlapped_roots = self.identify_subtrees_and_overlaps(osdmap, Jan 17 12:10:54 pyre ceph-mgr[63427]: File "/usr/share/ceph/mgr/pg_autoscaler/module.py", line 296, in identify_subtrees_and_overlaps Jan 17 12:10:54 pyre ceph-mgr[63427]: osds = set(crush.get_osds_under(root_id)) Jan 17 12:10:54 pyre ceph-mgr[63427]: File "/usr/share/ceph/mgr/mgr_module.py", line 292, in get_osds_under Jan 17 12:10:54 pyre ceph-mgr[63427]: accumulate(buckets[root_id]) Jan 17 12:10:54 pyre ceph-mgr[63427]: KeyError: -18 However still not having any luck after disabling that module. Now I get this: Jan 17 12:24:45 pyre ceph-mgr[67556]: ceph version 16.2.7 (dd0603118f56ab514f133c8d2e3adfc983942503) pacific (stable) Jan 17 12:24:45 pyre ceph-mgr[67556]: 1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x124) [0x7efebab0d120] Jan 17 12:24:45 pyre ceph-mgr[67556]: 2: /usr/lib/x86_64-linux-gnu/ceph/libceph-common.so.2(+0x24a2ab) [0x7efebab0d2ab] Jan 17 12:24:45 pyre ceph-mgr[67556]: 3: (CrushWrapper::_get_take_weight_osd_map(int, std::map, std::allocator > >*) const+0x201) [0x7efebb097b11] Jan 17 12:24:45 pyre ceph-mgr[67556]: 4: (CrushWrapper::get_rule_weight_osd_map(unsigned int, std::map, std::allocator > >*) const+0x15b) [0x7efebb097d3b] Jan 17 12:24:45 pyre ceph-mgr[67556]: 5: (PGMap::get_rule_avail(OSDMap const&, int) const+0x66) [0x555fc9c84166] Jan 17 12:24:45 pyre ceph-mgr[67556]: 6: (PGMap::get_rules_avail(OSDMap const&, std::map, std::allocator > >*) const+0x1cd) [0x555fc9c8461d] Jan 17 12:24:45 pyre ceph-mgr[67556]: 7: (PGMap::encode_digest(OSDMap const&, ceph::buffer::v15_2_0::list&, unsigned long)+0x20) [0x555fc9c84730] Jan 17 12:24:45 pyre ceph-mgr[67556]: 8: (DaemonServer::send_report()+0x616) [0x555fc9d2f656] Jan 17 12:24:45 pyre ceph-mgr[67556]: 9: (DaemonServer::maybe_ready(int)+0x633) [0x555fc9d308e3] Jan 17 12:24:45 pyre ceph-mgr[67556]: 10: (DaemonServer::ms_dispatch2(boost::intrusive_ptr const&)+0xef) [0x555fc9d4165f] Jan 17 12:24:45 pyre ceph-mgr[67556]: 11: (Messenger::ms_deliver_dispatch(boost::intrusive_ptr const&)+0x468) [0x7efebad2f518] Jan 17 12:24:45 pyre ceph-mgr[67556]: 12: (DispatchQueue::entry()+0x5ef) [0x7efebad2cc3f] Jan 17 12:24:45 pyre ceph-mgr[67556]: 13: (DispatchQueue::DispatchThread::entry()+0xd) [0x7efebadec21d] Jan 17 12:24:45 pyre ceph-mgr[67556]: 14: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8ea7) [0x7efeba4feea7] Jan 17 12:24:45 pyre ceph-mgr[67556]: 15: clone() Jan 17 12:24:45 pyre ceph-mgr[67556]: 0> 2022-01-17T12:24:45.814-0500 7efe8b1ee700 -1 *** Caught signal (Aborted) ** Jan 17 12:24:45 pyre ceph-mgr[67556]: in thread 7efe8b1ee700 thread_name:ms_dispatch Jan 17 12:24:45 pyre ceph-mgr[67556]: ceph version 16.2.7 (dd0603118f56ab514f133c8d2e3adfc983942503) pacific (stable)
Bug#987787: libdebuginfod-common: wrong permissions on /etc/profile.d/debuginfod.{c,}sh (and odd content)
On Sun, Aug 22, 2021 at 12:17:59PM +0800, Paul Wise wrote: > I think this approach is pretty convoluted, personally I would just > make the files in /etc either not exist when disabled, or symlinks into > /usr/share when enabled. I don't disagree, but /e/p.d/* can't be symlinks to /u/s. However, please consider new, simplified, patch below, applying to current Salsa HEAD (4ff688068d05a82039f7cbf88ae99e4d6a4bc327, 0.186-1). Thanks, наб From 868e5606b4c22ac84fafeff2028a1c74f710728f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= Date: Mon, 17 Jan 2022 18:26:42 +0100 Subject: [PATCH] d/libdebuginfod-common.post{inst,rm}: install conffiles 644, use /bin/sh shebang, remove /e/p.d/dd.*sh if libdebuginfod/usedebiandebuginfod unset --- debian/libdebuginfod-common.postinst | 115 +-- debian/libdebuginfod-common.postrm | 31 2 files changed, 35 insertions(+), 111 deletions(-) diff --git a/debian/libdebuginfod-common.postinst b/debian/libdebuginfod-common.postinst index a482967..93f5fa3 100644 --- a/debian/libdebuginfod-common.postinst +++ b/debian/libdebuginfod-common.postinst @@ -1,4 +1,4 @@ -#!/bin/bash +#!/bin/sh set -e @@ -6,101 +6,28 @@ set -e CONFTEMPLATEPATH="/usr/share/libdebuginfod-common" -# Change a "generic" shell file according to enable/disable -# DEBUGINFOD_URLS according. -# -# - $1 is the shell file name -# -# - $2 is the pattern that we will look for when changing the file. -# This pattern will also be used to perform the substitution. -# -# - $3 is the action we will perform: set the DEBUGINFOD_URLS -# variable, or unset it. -# -# By the end of it, the specified shell file will have an extra line -# which either sets DEBUGINFOD_URLS to have its own value, or sets -# DEBUGINFOD_URLS to be empty (i.e., unsets any value). -change_shell_file () -{ -file="$1" -pattern="$2" - -if [ "$3" = "set" ]; then - finalvar='$DEBUGINFOD_URLS' -else - finalvar="" -fi - -# Check whether the last line of the file already starts with -# ${pattern}. If it does, then we will perform a sed to replace -# it according to the action specified. Otherwise, we will append -# a last line containing the set/unset. -if tail -n1 "$file" | grep -q "^$pattern"; then - sed -i "\$s@${pattern}.*@${pattern}\"${finalvar}\"@" "${file}" -else - echo "${pattern}\"${finalvar}\"" >> "${file}" -fi -} - -# Change the .sh file according to an action specified by $1. It can -# be either "set" (meaning that we will be setting DEBUGINFOD_URLS to -# a valid value), or "unset" (which means that DEBUGINFOD_URLS will be -# empty). -change_sh_file () -{ -shfile="$1" -shaction="$2" - -change_shell_file \ - "$shfile" \ - "export DEBUGINFOD_URLS=" \ - "$shaction" -} - -# Change the .csh file according to an action specified by $1. The -# explanation for change_sh_file also applies here. -change_csh_file () -{ -cshfile="$1" -cshaction="$2" - -change_shell_file \ - "$cshfile" \ - "setenv DEBUGINFOD_URLS " \ - "$cshaction" -} - case "$1" in configure) - GOT_DEBCONF_ANSWER=0 - - for ext in sh csh; do - if [ -f "${CONFTEMPLATEPATH}"/debuginfod."${ext}" ]; then - if [ "$GOT_DEBCONF_ANSWER" -eq 0 ]; then - RET="false" - if grep -qFx "ID=debian" /etc/os-release; then - db_get libdebuginfod/usedebiandebuginfod || RET="false" - fi - - if [ "$RET" = "true" ]; then - action="set" - else - action="unset" - fi - GOT_DEBCONF_ANSWER=1 - fi - - tmpfile=$(mktemp) - cat "${CONFTEMPLATEPATH}"/debuginfod."${ext}" > "$tmpfile" - change_"${ext}"_file "$tmpfile" "$action" - - ucf --three-way --debconf-ok \ - "$tmpfile" \ - /etc/profile.d/debuginfod."${ext}" - ucfr libdebuginfod-common /etc/profile.d/debuginfod."${ext}" - rm -f "${tmpfile}" - fi - done + GOT_DEBCONF_ANSWER=0 + for ext in sh csh; do + [ -f "${CONFTEMPLATEPATH}/debuginfod.${ext}" ] || continue + + if [ "$GOT_DEBCONF_ANSWER" -eq 0 ]; then +grep -qFx "ID=debian" /etc/os-release && db_get libdebuginfod/usedebiandebuginfod || RET="false" +GOT_DEBCONF_ANSWER=1 + fi + + if [ "$RET" = "true" ]; then +UCF_FORCE_CONFFMISS=1 ucf --three-way --debconf-ok "${CONFTEMPLATEPATH}/debuginfod.${ext}" "/etc/profile.d/debuginfod.${ext}" +if [ "$(stat -c%a "/etc/profile.d/debuginfod.${ext}")" = 600 ]; then + chmod 644 "/etc/profile.d/debuginfod.${ext}" # Correct permissions created by previous versions (<=0.186-1) +fi + else +rm -f "/etc/profile.d/debuginfod.${ext}" + fi + ucfr libdebuginfod-common "/etc/profile.d/debuginfod.${ext}" + done + rm -rf "${tmpdir}" ;; abort-upgrade|abort-remove|abort-deconfigure) diff --git a/debian/libdebuginfod-common.postrm b/debian/libdebuginfod-common.postrm index 62a92ca..250ab6c 100644 --- a/debian/libdebuginfod-common.postrm +++ b/debian/libdebuginfod-common.postrm @@ -1,27 +1,24 @@ -#!/bin/bash +#!/bin/sh set -e case "$1
Bug#1003889: RFS: tapecalc/20220117-1 -- full-screen tape editor that lets the user edit a calculation
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "tapecalc": * Package name: tapecalc Version : 20220117-1 Upstream Author : Thomas E. Dickey * URL : https://invisible-island.net/add/add.html * License : MIT-old, X11 * Vcs : https://salsa.debian.org/debian/tapecalc Section : math It builds those binary packages: tapecalc - full-screen tape editor that lets the user edit a calculation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/tapecalc/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/t/tapecalc/tapecalc_20220117-1.dsc Changes since the last upload: tapecalc (20220117-1) unstable; urgency=medium . * New upstream version 20220117. (LP: #1771671) * Drop upstreamed patch. * Add debian/upstream/metadata file. * Update copyright years. Regards, Victor Westerhuis OpenPGP_signature Description: OpenPGP digital signature
Bug#1003888: mrtg: [INTL:de] updated German debconf translation
Package: mrtg Severity: wishlist Tags: patch l10n Please find the updated German debconf translation for mrtg attached. Please place this file in debian/po/ as de.po for your next upload. If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. Greetings Helge # Debconf file for MRTG # Copyright (C) 2021 Joao Eriberto Mota Filho # This file is distributed under the same license as the mrtg package. # Helge Kreutzmann , 2021, 2022. # msgid "" msgstr "" "Project-Id-Version: mrtg 2.17.8+git20211022.f52e91e-1\n" "Report-Msgid-Bugs-To: m...@packages.debian.org\n" "POT-Creation-Date: 2022-01-08 15:02-0300\n" "PO-Revision-Date: 2022-01-17 18:30+0100\n" "Last-Translator: Helge Kreutzmann \n" "Language-Team: German \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../mrtg.templates:1001 msgid "Fix owner, group and permissions for /var/www/html/mrtg?" msgstr "" "Eigentümer, Gruppe und Berechtigungen für /var/www/html/mrtg korrigieren?" #. Type: boolean #. Description #: ../mrtg.templates:1001 msgid "" "By default MRTG writes all graphics in /var/www/html/mrtg/ directory. This " "directory is present at this moment, but it is insecure. Is needed to make " "this directory owned by 'mrtg' user and 'www-data' group. The recommended " "permission is 0750." msgstr "" "Standardmäßig schreibt MRTG alle Graphiken in das Verzeichnis /var/www/html/" "mrtg/. Dieses Verzeichnis existiert derzeit, aber es ist unsicher. Es ist " "notwendig, dass dieses Verzeichnis dem Benutzer »mrtg« und der Gruppe »www-" "data« gehört. Die empfohlene Berechtigung ist 0750." #. Type: boolean #. Description #: ../mrtg.templates:2001 msgid "Create /var/www/html/mrtg?" msgstr "/var/www/html/mrtg erstellen?" #. Type: boolean #. Description #: ../mrtg.templates:2001 msgid "" "By default MRTG writes all graphics in /var/www/html/mrtg/ directory. " "However, at this moment, this directory doesn't exist. Is also needed to " "make this directory owned by 'mrtg' user and 'www-data' group. The " "recommended permission is 0750." msgstr "" "Standardmäßig schreibt MRTG alle Graphiken in das Verzeichnis /var/www/html/" "mrtg/. Dieses Verzeichnis existiert momentan nicht. Es ist notwendig, dass " "dieses Verzeichnis dem Benutzer »mrtg« und der Gruppe »www-data« gehört. Die " "empfohlene Berechtigung ist 0750." #. Type: boolean #. Description #: ../mrtg.templates:2001 msgid "" "Alternatively, you can use another path for generated graphics. Note that " "keeping this directory empty when using another path is not a problem." msgstr "" "Alternativ können Sie einen anderen Pfad für die erstellten Graphiken " "verwenden. Beachten Sie, dass es kein Problem ist, wenn dieses Verzeichnis " "bei der Verwendung eines anderen Pfades leerbleibt." #. Type: boolean #. Description #: ../mrtg.templates:3001 msgid "Remove old and conflicting file /etc/cron.d/mrtg?" msgstr "Die alte und einen Konflikt auslösende Datei entfernen?" #. Type: boolean #. Description #: ../mrtg.templates:3001 msgid "" "MRTG no longer needs to use cron because it is starting on Debian via " "systemd/init.d scripts." msgstr "" "MRTG benötigt Cron nicht mehr, da es unter Debian durch Systemd/init.d-" "Skripte gestartet wird." #. Type: boolean #. Description #: ../mrtg.templates:3001 msgid "" "Was found a file called /etc/cron.d/mrtg, that was installed from an old " "version of the MRTG. If kept, this file will make a duplicate work because " "MRTG now runs as a daemon, coordinated by systemd/init.d. Consequently, is " "strongly recommended to remove the cron file." msgstr "" "Es wurde eine Datei Namens /etc/cron.d/mrtg gefunden, die von einer " "alten Version von MRTG installiert wurde. Falls diese erhalten bleibt, führt " "dies zu doppelter Arbeit, diese Datei zu doppelter Arbeit führen, da MRTG " "jetzt als Dämon ausgeführt wird, der durch Systemd/init.d koordiniert wird. " "Daher empfehlen wir mit Nachdruck diese Cron-Datei zu entfernen." #. Type: boolean #. Description #: ../mrtg.templates:3001 msgid "" "If this cron job is needed, consider to rename the file /etc/cron.d/mrtg (e." "g. from /etc/cron.d/mrtg to /etc/cron.d/mrtg-custom) to avoid future " "warnings." msgstr "" "Falls dieser Cron-Auftrag benötigt wird, könnten Sie die Datei " "umbenennen (z.B. von /etc/cron.d/mrtg in /etc/cron.d/mrtg-custom), um " "zukünftige Warnungen zu vermeiden."
Bug#1003887: terminology: outputs error on start: Could not fetch a node located at 0x40000004529e
Package: terminology Version: 1.9.0-2 Severity: minor When starting terminology I see: ``` ERR<148513>:elementary ../src/lib/elementary/efl_ui_focus_manager_calc.c:1529 _efl_ui_focus_manager_calc_efl_ui_focus_manager_manager_focus_set() Could not fetch a node located at 0x4004529e ## Copy & Paste the below (until EOF) into a terminal, then hit Enter eina_btlog << EOF /lib/x86_64-linux-gnu/libeina.so.1 0x7f2e06086ebc 0x7f2e0605a000 /lib/x86_64-linux-gnu/libeina.so.1 0x7f2e060880c1 0x7f2e0605a000 /lib/x86_64-linux-gnu/libeina.so.1 0x7f2e060896f3 0x7f2e0605a000 /lib/x86_64-linux-gnu/libelementary.so.1 0x7f2e05ebe24e 0x7f2e05b61000 /lib/x86_64-linux-gnu/libelementary.so.1 0x7f2e05eb8552 0x7f2e05b61000 /lib/x86_64-linux-gnu/libelementary.so.1 0x7f2e05ebb925 0x7f2e05b61000 /lib/x86_64-linux-gnu/libelementary.so.1 0x7f2e05eb915a 0x7f2e05b61000 /usr/bin/terminology 0x55cc71f83d73 0x55cc71f2c000 /usr/bin/terminology 0x55cc71f878bd 0x55cc71f2c000 /lib/x86_64-linux-gnu/libeo.so.1 0x7f2e057b28e2 0x7f2e0579b000 /lib/x86_64-linux-gnu/libeo.so.1 0x7f2e057ad090 0x7f2e0579b000 /lib/x86_64-linux-gnu/libelementary.so.1 0x7f2e05e8cd45 0x7f2e05b61000 /lib/x86_64-linux-gnu/libecore_evas.so.1 0x7f2e05b405b9 0x7f2e05b2d000 /lib/x86_64-linux-gnu/ecore_evas/engines/x/v-1.25/module.so 0x7f2e00fb3429 0x7f2e00fa7000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e06120480 0x7f2e060fa000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e06129642 0x7f2e060fa000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e06122439 0x7f2e060fa000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e0612130c 0x7f2e060fa000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e0611bef6 0x7f2e060fa000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e0611c6e5 0x7f2e060fa000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e06122295 0x7f2e060fa000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e061215cc 0x7f2e060fa000 /lib/x86_64-linux-gnu/libecore.so.1 0x7f2e0611c7d7 0x7f2e060fa000 /usr/bin/terminology 0x55cc71f4d16e 0x55cc71f2c000 /usr/bin/terminology 0x55cc71f4169d 0x55cc71f2c000 /lib/x86_64-linux-gnu/libc.so.6 0x7f2e057e9d0a 0x7f2e057c3000 /usr/bin/terminology 0x55cc71f416da 0x55cc71f2c000 EOF ``` This is not very nice, but terminology still works. Thus I'm assigning a severitfy of "minor". Piping that to eina_btlog gives: ``` /lib/x86_64-linux-gnu/libeina.so.1 | ??/?? : 32655 @ _eina_semaphore_free() /lib/x86_64-linux-gnu/libeina.so.1 | ??/?? : 32655 @ eina_log_print_cb_stdout() /lib/x86_64-linux-gnu/libeina.so.1 | ??/?? : 32655 @ eina_log_print() /lib/x86_64-linux-gnu/libelementary.so.1| ??/?? : 32655 @ efl_ui_focus_manager_calc_update_order() y/lib/x86_64-linux-gnu/libelementary.so.1| ??/?? : 32655 @ efl_ui_focus_manager_focus_set() /lib/x86_64-linux-gnu/libelementary.so.1| ??/?? : 32655 @ efl_ui_focus_manager_calc_update_order() /lib/x86_64-linux-gnu/libelementary.so.1| ??/?? : 32655 @ efl_ui_focus_manager_pop_history_stack() /usr/bin/terminology | ??/?? : 32655 @ MD5Final() /usr/bin/terminology | ??/?? : 32655 @ MD5Final() /lib/x86_64-linux-gnu/libeo.so.1| ??/?? : 32655 @ efl_provider_unregister() /lib/x86_64-linux-gnu/libeo.so.1| ??/?? : 32655 @ efl_event_callback_legacy_call() /lib/x86_64-linux-gnu/libelementary.so.1| ??/?? : 32655 @ elm_win_rotation_with_resize_set() /lib/x86_64-linux-gnu/libecore_evas.so.1| ??/?? : 32655 @ _ecore_evas_focus_device_set() /lib/x86_64-linux-gnu/ecore_evas/engines/x/v-1.25/module.so | /: 0 @ () /lib/x86_64-linux-gnu/libecore.so.1 | ??/?? : 0 @ ecore_main_fd_handler_active_set() /lib/x86_64-linux-gnu/libecore.so.1 | ??/?? : 0 @ efl_loop_message_handler_message_call() /lib/x86_64-linux-gnu/libecore.so.1 | ??/?? : 0 @ efl_loop_timeout() /lib/x86_64-linux-gnu/libecore.so.1 | ??/?? : 0 @ efl_loop_message_process() /lib/x86_64-linux-gnu/libecore.so.1 | ??/??
Bug#1003738: tech-ctte: Call for votes on TC membership of Matthew Vernon
On Fri, 14 Jan 2022 at 11:56:20 -0700, Sean Whitton wrote: > ===BEGIN > The Technical Committee recommends that Matthew Vernon be > appointed by the Debian Project Leader to the Technical Committee. > > H: Recommend to Appoint Matthew Vernon > F: Further Discussion > ===END I vote H > F. smcv signature.asc Description: PGP signature
Bug#1003737: tech-ctte: Call for votes on TC membership of Helmut Grohne
On Fri, 14 Jan 2022 at 11:55:17 -0700, Sean Whitton wrote: > ===BEGIN > The Technical Committee recommends that Helmut Grohne be > appointed by the Debian Project Leader to the Technical Committee. > > H: Recommend to Appoint Helmut Grohne > F: Further Discussion > ===END I vote H > F. smcv signature.asc Description: PGP signature
Bug#1003886: New upstream version
Hello Gregwar, I notice that you released a new version but it's not in Debian yet. Can I help you to maintain your program fatcat in the Debian archive? My name is kretcheu I'm DM. I want to help, so if you think that is appropriate, we could co-maintain. Thanks. kretcheu :x On Mon, 17 Jan 2022 13:57:37 -0300 "Paulo Roberto Alves de Oliveira (aka kretcheu)" wrote: Source: fatcat Version: 1.0.5-1 Severity: wishlist Dear Maintainer, Package: fatcat Version: 1.0.5 There is a new upstream version, 1.1.0, available at: https://github.com/Gregwar/fatcat/tags -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.1-gnu (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled OpenPGP_signature Description: OpenPGP digital signature
Bug#956012: chromium: use DuckDuckGo as Chromium's default search provider
Hi, What do you think, Andres? This idea is good. I use duckduckgo as my default search engine. I don't know if your idea is to continue with browser maintenance. -BEGIN PGP PUBLIC KEY BLOCK- mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh 0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7 ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3 k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx /m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C +DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4 hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08 iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X 7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00 4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9 WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O +SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW fNdY6Ns= =rdCA -END PGP PUBLIC KEY BLOCK-
Bug#1003886: New upstream version
Source: fatcat Version: 1.0.5-1 Severity: wishlist Dear Maintainer, Package: fatcat Version: 1.0.5 There is a new upstream version, 1.1.0, available at: https://github.com/Gregwar/fatcat/tags -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.1-gnu (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1003835: udev: XEN domU: Guest RX stalled, unreachable due to nw device naming change
Am 17.01.22 um 08:20 schrieb Michael Biebl: Am 17.01.22 um 08:15 schrieb Michael Biebl: I don't think we want to get into the business of mangling other packages configuration files (which would be a policy violation anyway). Also keep in mind that ifupdown is by no means the only network configuration scheme. At most we could let postinst generate a warning message. That said, I have no idea if such a script would be feasible and how reliable the detection would be. I'm happy to take suggestions how this could be implemented. Even better, if you have an idea, please submit a MR. Another alternative could be to add a udev.NEWS entry. I'm tossing out another idea: debian-installer, when installing the system initially, could write a config for grub which appends net.naming-scheme=system was installed with> So, once the system is installed, the net-naming-scheme would no longer change. Haven't yet made up my mind, whether this is a good idea or not. Would welcome feedback! Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#951331: hexchat apparmor profile
Control: tag -1 -pending On Sun, Jan 16, 2022 at 09:40:12AM +0100, Mattia Rizzolo wrote: > On Sat, Jan 15, 2022 at 06:05:14PM +, Patrick Schleizer wrote: > > Mattia Rizzolo: > > > Could you please revise your patch following their suggestions? > > > > > > https://bugs.debian.org/951331#23 > > > > > > This has been done. Please check. Also pull requests welcome. > > I'm asking friends for testing (since I don't use it). Unfortunately, that testing showed some issues. [329190.993264] audit: type=1400 audit(1642420765.354:126): apparmor="DENIED" operation="connect" profile="/usr/bin/hexchat" pid=967103 comm="hexchat" family="unix" sock_type="stream" protocol=0 requested_mask="send receive connect" denied_mask="send connect" addr=none peer_addr="@/tmp/dbus-0fDmto1XGK" peer="unconfined" [329191.029276] audit: type=1400 audit(1642420765.390:127): apparmor="DENIED" operation="open" profile="/usr/bin/hexchat" name="/usr/share/enchant-2/enchant.ordering" pid=967103 comm="hexchat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [329191.033456] audit: type=1400 audit(1642420765.394:128): apparmor="DENIED" operation="open" profile="/usr/bin/hexchat" name="/etc/machine-id" pid=967103 comm="hexchat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [329191.033463] audit: type=1400 audit(1642420765.394:129): apparmor="DENIED" operation="open" profile="/usr/bin/hexchat" name="/etc/machine-id" pid=967103 comm="hexchat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [329191.034635] audit: type=1400 audit(1642420765.394:130): apparmor="DENIED" operation="connect" profile="/usr/bin/hexchat" name="/run/user/1000/bus" pid=967103 comm="hexchat" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [329191.035041] audit: type=1400 audit(1642420765.398:131): apparmor="DENIED" operation="connect" profile="/usr/bin/hexchat" name="/run/user/1000/bus" pid=967103 comm="pool-hexchat" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [329191.090387] audit: type=1400 audit(1642420765.450:132): apparmor="DENIED" operation="open" profile="/usr/bin/hexchat" name="/usr/share/enchant-2/enchant.ordering" pid=967103 comm="hexchat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [329191.248574] audit: type=1400 audit(1642420765.610:133): apparmor="DENIED" operation="open" profile="/usr/bin/hexchat" name="/home/user/.local/lib/python3.8/site-packages/" pid=967103 comm="hexchat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [329191.248637] audit: type=1400 audit(1642420765.610:134): apparmor="DENIED" operation="open" profile="/usr/bin/hexchat" name="/usr/local/lib/python3.8/dist-packages/" pid=967103 comm="hexchat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [329191.260383] audit: type=1400 audit(1642420765.622:135): apparmor="DENIED" operation="open" profile="/usr/bin/hexchat" name="/home/user/.local/lib/python3.8/site-packages/" pid=967103 comm="hexchat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 So, in particular, it seems that: * file transfer is not working anymore * loading of plugins seems have some issues -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1003874: falkon: Package falkon is not in repository although it is available for armhf on Debian
Dear Adolf, I suspect some misconfiguration on your machine? The package for armhf does exist in Debian space, please check it at https://packages.debian.org/bullseye/armhf/falkon/download Best regards, Georges. Adolf Winterer a écrit : > Package: falkon > Severity: normal > Tags: a11y > X-Debbugs-Cc: adolf.j.winte...@inn-salzach.de > > Dear Maintainer, > > ng to install the web browser Falkon failed due to non-existence of the > package in the repository. > >* What led up to the situation? > Tried to install a few well liked KDE applications on my Raspberry Pi 4 > 4GB, > which worked mostly well (e.g. with Dolphin, Konsole, Okular), but > failed > to install the Falkon web browser due to non-existence in the repository. >* What exactly did you do (or not do) that was effective (or > ineffective)? > Looked up the package with apt search and found the package to not be > existent > in the repository. > Checked with Debian package directory and found that the package exists > also > for the armhf architecture. Therefore there seems to be no fundamental > problem > building and packaging for armhf. > https://packages.debian.org/bullseye/falkon >* What was the outcome of this action? > Currently using different browser as workaround as long as Falkon is not > available (yet). >* What outcome did you expect instead? > Expected the package to be existent in the repository and a successful > install. > > Content of my sources.list file: > deb tor://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free > rpi > # Uncomment line below then 'apt-get update' to enable 'apt-get source' > # deb-src tor://raspbian.raspberrypi.org/raspbian/ bullseye main contrib > non-free rpi > > Are there plans to include packages like Falkon into the repository? Are > there > any technical issues which block the package from inclusion? > > Best Regards, > Adolf > > -- System Information: > Distributor ID: Raspbian > Description: Raspbian GNU/Linux 11 (bullseye) > Release: 11 > Codename: bullseye > Architecture: armv7l > > Kernel: Linux 5.10.63-v7l+ (SMP w/4 CPU threads) > Kernel taint flags: TAINT_CRAP > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: PGP signature
Bug#874116: octave-tisean FTBFS on !amd64: test failure
Control: severity -1 serious Control: block 1003599 by -1 On Sun, 03 Sep 2017 16:10:20 +0300 Adrian Bunk wrote: > Source: octave-tisean > Version: 0.2.3-1 > Severity: important > > https://buildd.debian.org/status/package.php?p=octave-tisean&suite=sid > > ... > Summary: 162 tests, 125 passed, 0 known failures, 0 skipped > /usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' > failed > make: *** [check-pkg] Error 1 Raising the severity of this bug to serious. Actually the failures on some non-amd64 architectures are random, so that binaries sometimes get built but then it becomes difficult to update them. In particular, I cannot get the s390x binary rebuilt for the Octave 6.4 transition (even after trying 5 times). -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#1003879: systemd-coredump - No longer any relation with libdw1 for backtraces
On Mon, 2022-01-17 at 16:17 +0100, Michael Biebl wrote: > Am 17.01.22 um 15:19 schrieb Bastian Blank: > > Package: systemd-coredump > > Version: 250.2-3 > > Severity: normal > > > > systemd 250 started to use libdw1 via dlopen instead of direct linking. > > So systemd-coredump should at least add a Recommends for it. > > Luca, what was your goal here? > Did you want to have libdw1 installed by default (in which case a > Recommends would be fine) or should this an explicit opt-in (i.e. at > most a Suggests) This should be a Recommends for a generalist distro like Debian, where in the vast majority of cases having backtraces and such things is useful for users (while still allowing to easily opt out when building minimalist images or container runtimes). -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#1003722: jupyter-notebook: blank page in firefox
This happened to me, but uninstalling and re-installing fixed it: see below. I also got a blank page with the same "exports is not defined" error after upgrading jupyter to 6.4.5-3. Next, I uninstalled the debian package and installed jupyter from pip: pip3 install jupyter ... and still had the same problem. So, I removed the pip version (`pip3 uninstall jupyter`) and re-installed it from debian... and now it works. Here's the versions of packages I have now: ``` $ apt list --installed | grep jupyter jupyter-core/unstable,now 4.9.1-1 all [installed,automatic] jupyter-nbextension-jupyter-js-widgets/unstable,now 6.0.0-8 all [installed,automatic] jupyter-notebook/unstable,now 6.4.5-3 all [installed] python3-jupyter-client/unstable,now 7.1.0-1 all [installed,automatic] python3-jupyter-core/unstable,now 4.9.1-1 all [installed,automatic] python3-jupyterlab-pygments/unstable,now 0.1.2-8 all [installed,automatic] ``` and here are the versions of all the packages that got installed when I re-installed jupyter-notebook: ``` jupyter-core/unstable,now 4.9.1-1 all [installed,automatic] jupyter-nbextension-jupyter-js-widgets/unstable,now 6.0.0-8 all [installed,automatic] libjs-backbone/unstable,now 1.4.0~dfsg+~1.4.5-2 all [installed,automatic] libjs-bootstrap-tour/unstable,now 0.12.0+dfsg-3 all [installed,automatic] libjs-codemirror/unstable,now 5.63.3+~cs5.83.9-1 all [installed,automatic] libjs-es6-promise/unstable,now 4.2.8-9 all [installed,automatic] libjs-jed/unstable,now 1.1.1-3 all [installed,automatic] libjs-jquery-typeahead/unstable,now 2.11.0+dfsg1-3 all [installed,automatic] libjs-marked/unstable,now 4.0.9+ds+~4.0.1-2 all [installed,automatic] libjs-moment/unstable,now 2.29.1+ds-3 all [installed,automatic] libjs-requirejs-text/unstable,now 2.0.12-1.1 all [installed,automatic] libjs-requirejs/unstable,now 2.3.6+ds-1 all [installed,automatic] libjs-text-encoding/unstable,now 0.7.0-4 all [installed,automatic] libjs-xterm/unstable,now 3.8.1+~cs0.9.0-1 all [installed,automatic] node-jed/unstable,now 1.1.1-3 all [installed,automatic] python3-argon2/unstable,now 21.1.0-1+b1 amd64 [installed,automatic] python3-bleach/unstable,now 4.1.0-1 all [installed,automatic] python3-entrypoints/unstable,now 0.3-10 all [installed,automatic] python3-ipykernel/unstable,now 6.6.1-1 all [installed,automatic] python3-ipywidgets/unstable,now 6.0.0-8 all [installed,automatic] python3-jupyter-client/unstable,now 7.1.0-1 all [installed,automatic] python3-jupyterlab-pygments/unstable,now 0.1.2-8 all [installed,automatic] python3-nbclient/unstable,now 0.5.6-2 all [installed,automatic] python3-nbconvert/unstable,now 6.3.0-1 all [installed,automatic] python3-nest-asyncio/unstable,now 1.5.4-1 all [installed,automatic] python3-notebook/unstable,now 6.4.5-3 all [installed,automatic] python3-pandocfilters/unstable,now 1.5.0-1 all [installed,automatic] python3-prometheus-client/unstable,now 0.9.0-1 all [installed,automatic] python3-send2trash/unstable,now 1.6.0~b1+git20210122.2eb3242-1 all [installed,automatic] python3-terminado/unstable,now 0.12.1-1 all [installed,automatic] python3-testpath/unstable,now 0.5.0+dfsg-1 all [installed,automatic] python3-widgetsnbextension/unstable,now 6.0.0-8 all [installed,automatic] python3-zmq/unstable,now 22.3.0-1+b1 amd64 [installed,automatic] ``` Hope this helps, and let me know if I can provide more information. - peter > I can confirm I get a JS error upon starting 'jupyter notebook' from the > CLI using either Firefox: > > Uncaught ReferenceError: exports is not defined > > http://localhost:/static/tree/js/main.min.js?v=1165e50a1bd56de1d3cb2eb1f607c410d26e4dc418d1e016a4a3721ca5d697af4ef59e61b3be7082890269c3728083992695ad6156881a27d4b45d88802a4e8b:13852
Bug#1003574: segfault in libc-2.33.so during i386 boot ofde QEMU VM
Am 2022-01-15 11:26, schrieb Aurelien Jarno: control: reopen -1 control: merge 1003610 -1 control: severity -1 serious control: found -1 glibc/2.33-1 control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=28784 On 2022-01-12 14:08, Christian Kastner wrote: Hi Aurelien, thank you for the quick reply. On 2022-01-12 11:45, Aurelien Jarno wrote: >> # Boot image. -enable-kvm assumes that this is being tested on amd64 >> # Optionally use -nographic for terminal output instead of GUI >> $ qemu-system-i386 \ >>-machine q35 \ >>-enable-kvm \ > > You might also want to try without -enable-kvm Indeed, this fixed the issue. So sorry for the noise. I was 120% sure that I had tried that. My turn to be sorry, it appears to be a genuine issue on the GNU libc side, and changing the CPU definition in QEMU, either with -cpu or by disabling kvm) just hide the bug. I was not able to reproduce the issue as you need a non-Intel CPU to get the issue with the command line your provided. This bug also affects via C7 CPUs. I have reported the issue upstream and provided a patch, currently waiting for review. Regards, Aurelien I built the libc6 deb-package for i386 with your patch applied. It fixes the problem for VIA C7 and VIA Eden. Thanks a lot for your help. I hope upstream will include this fix soon. Regards, -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts
Bug#1003885: ldb: FTBFS on kfreebsd
Source: ldb Version: 2:2.2.3-2 Severity: important Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, Could you please fix the build on src:ldb like you did on the other libraries? Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#1003879: systemd-coredump - No longer any relation with libdw1 for backtraces
Am 17.01.22 um 15:19 schrieb Bastian Blank: Package: systemd-coredump Version: 250.2-3 Severity: normal systemd 250 started to use libdw1 via dlopen instead of direct linking. So systemd-coredump should at least add a Recommends for it. Luca, what was your goal here? Did you want to have libdw1 installed by default (in which case a Recommends would be fine) or should this an explicit opt-in (i.e. at most a Suggests) OpenPGP_signature Description: OpenPGP digital signature
Bug#1003873: [Pkg-javascript-devel] Bug#1003873: marked as done (emscripten: emcc search for /usr/bin/clang (and other binaries) which doesn't exist)
Yadd wrote: > I didn't know that emscripten generated local config. It should have > been update during package upgrade. I did mention this in a previous post to this bugreport: > Beware that on first use of emscripten it stores a config file in > $HOME (and very explicitly notifies about that) - or if run as root > then a config file is stored at /usr/share/emscripten/.emscripten so > NEVER EVER execute emscripten tools as root! It is also mentioned in README.Debian for the package. If you have ideas for ways you could have better been aware, then I am interested - I can imagine you not being the only one caught by this. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1003884: lumino: FTBFS with webpack 5: Not found, setimmediate is required by debian/nodejs/./extlinks but not available
Source: lumino Version: 2021.12.13-1 Severity: important Tags: ftbfs User: pkg-javascript-de...@alioth-lists.debian.net Usertags: webpack5 Hi, We are starting to build against webpack5 in experimental and the package needed for local build is webpack and node-webpack-source from experimental. During a test rebuild, lumino was found to fail to build in that situation. Relevant part (hopefully): Found debian/nodejs/additional_components Adding component(s): packages/algorithm, packages/application, packages/collections, packages/commands, packages/coreutils, packages/datagrid, packages/datastore, packages/default-theme, packages/disposable, packages/domutils, packages/dragdrop, packages/keyboard, packages/messaging, packages/polling, packages/properties, packages/signaling, packages/virtualdom, packages/widgets Not found ### setimmediate is required by debian/nodejs/./extlinks but not available make: *** [debian/rules:4: binary] Error 1 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2022-01-17T10:12:52Z Finished The full log is attached to this mail. sbuild (Debian sbuild) 0.81.2 (31 January 2021) on debian +==+ | lumino 2021.12.13-1 (amd64) Mon, 17 Jan 2022 14:29:10 + | +==+ Package: lumino Version: 2021.12.13-1 Source Version: 2021.12.13-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-103a53e2-d3f1-4b81-b08c-150e2e7aecfe' with '<>' W: ../webpack_5.65.0+dfsg+~cs9.20.9-3_all.deb is neither a regular file nor a directory. Skipping... I: NOTICE: Log filtering will replace 'build/lumino-cRAxzs/resolver-Rk4U25' with '<>' +--+ | Update chroot| +--+ Get:1 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ InRelease Ign:1 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ InRelease Get:2 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Release [951 B] Get:2 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Release [951 B] Get:3 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Release.gpg Ign:3 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Release.gpg Get:4 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Packages [807 B] Err:4 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Packages Could not open file /build/lumino-cRAxzs/resolver-OA3Elp/apt_archive/./Packages - open (13: Permission denied) Get:4 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Packages [1405 B] Get:5 http://deb.debian.org/debian unstable InRelease [165 kB] Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB] Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:9 http://deb.debian.org/debian unstable/main Sources T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [6783 B] Get:10 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 kB] Get:9 http://deb.debian.org/debian unstable/main Sources T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [6783 B] Get:11 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index [63.3 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [6743 B] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [1644 B] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [900 B] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [6743 B] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [900 B] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [1644 B] Fetched 510 kB in 6s (85.3 kB/s) Reading package lists... W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4
Bug#1003883: Tests aren't part of the package build
Package: suitesparse-graphblas Version: 6.0.0+dfsg-3 Hey, The source includes a Test directory but those aren't run as part of the build, it would be nice to do so and also to add some autopkgtest. Cheers,
Bug#1003877: libblis3-openmp: i386 triggers segfault in scipy arpack test (test_hermitian_modes))
If I read scipy correctly, self._arpack_extract is defined at https://github.com/scipy/scipy/blob/cd9a2597b7ee399bf9dbdead0115607d442feced/scipy/sparse/linalg/_eigen/arpack/arpack.py#L706 as Fneupd or Dneupd The prefix type F or D is set at test_arpack.py#L426
Bug#1003882: RM: node-jquery.waitforimages -- ROM; Broken and useless
Package: ftp.debian.org Severity: normal Hi, node-jquery.waitforimages is broken for a while and useless in Debian. Iy should be removed from archive. Cheers, Yadd
Bug#1003871: [LA-Mirroring] Bug#1003871: Acknowledgement (mirror listing update for mirror.linux.org.au)
Hi Steven, there was an issue on syncproxy.au.debian.org which caused (ssh) triggers to mirror.linux.org.au to not work since the change, however I don't have an explanation for rsync not working :( Cheers, Julien On Mon, Jan 17, 2022 at 09:56:15PM +1100, Steven Hanley wrote: > More details from the email I sent on Saturday > > Hi > > We have just moved our mirror.linux.org.au to a new machine, on a new ip > address. > > I have kept the credentials for our sync the same > > username > > mirror.linux.org.au > > Getting > > rsync: failed to connect to syncproxy.au.debian.org (2400:a4c0::27): > Connection timed out (110) > rsync: failed to connect to syncproxy.au.debian.org (103.84.224.39): > Connection timed out (110) > rsync error: error in socket IO (code 10) at clientserver.c(127) > [Receiver=3.1.3] > > Is there a modification oon your end needed? > > The new ip addresses are > > ipv4 103.84.224.37 > ipv6 2400:a4c0::25 > > Cheers > > Steve > > > On Mon, Jan 17, 2022 at 10:27:03AM +, Debian Bug Tracking System wrote: > > Thank you for filing a new Bug report with Debian. > > > > You can follow progress on this Bug here: 1003871: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003871. > > > > This is an automatically generated reply to let you know your message > > has been received. > > > > Your message is being forwarded to the package maintainers and other > > interested parties for their attention; they will reply in due course. > > > > Your message has been sent to the package maintainer(s): > > Debian Mirrors Team > > > > If you wish to submit further information on this problem, please > > send it to 1003...@bugs.debian.org. > > > > Please do not send mail to ow...@bugs.debian.org unless you wish > > to report a problem with the Bug-tracking system. > > > > -- > > 1003871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003871 > > Debian Bug Tracking System > > Contact ow...@bugs.debian.org with problems > > ___ > > mirroring mailing list > > mirror...@lists.linux.org.au > > http://lists.linux.org.au/mailman/listinfo/mirroring > > -- > Steven Hanley s...@svana.org http://svana.org/sjh/diary > did the hate filled want to build bunkers, in your beautiful red earth > they want to build them in our shiny white snow >Hello Birmingham - To The Teeth - Ani >
Bug#1003881: js error on home page
Package: jupyter-notebook Version: 6.4.5-3 Severity: serious When starting `jupyter-notebook`, a browser is spawned to land (after some redirects) on http://localhost:/tree but the page stays blank. The browser console reports some javascript error: Uncaught ReferenceError: exports is not defined marked.js:14 marked.js:14 marked.js:14 So jupyter is basically unusable because nothing can be accessed.
Bug#1003873: [Pkg-javascript-devel] Bug#1003873: Bug#1003873: Bug#1003873: emscripten: emcc search for /usr/bin/clang (and other binaries) which doesn't exist
Quoting Yadd (2022-01-17 14:02:55) > On 17/01/2022 13:55, Jonas Smedegaard wrote: > > Quoting Yadd (2022-01-17 13:40:44) > >> On 17/01/2022 13:30, Jonas Smedegaard wrote: > >>> Control: tags -1 unreproducible > > > when trying to build a WASM file from a C file, emcc fails because > it doesn't find /usr/bin/clang (and other clang binaries). > > > > [...] > > > >>> In a clone of https://salsa.debian.org/js-team/node-jest.git running > >>> above command - on a clean Debian testing system - I get this > >>> failure (after some time of compiling with clang -13): > >>> > >>> error: undefined symbol: main (referenced by top-level compiled C/C++ > >>> code) > >>> warning: Link with `-s LLD_REPORT_UNDEFINED` to get more information on > >>> undefined symbols > >>> warning: To disable errors for undefined symbols use `-s > >>> ERROR_ON_UNDEFINED_SYMBOLS=0` > >>> warning: _main may need to be added to EXPORTED_FUNCTIONS if it arrives > >>> from a system library > >>> warning: To build in STANDALONE_WASM mode without a main(), use emcc > >>> --no-entry > >>> Error: Aborting compilation due to previous errors > >>> emcc: error: '/usr/bin/node /usr/share/emscripten/src/compiler.js > >>> /tmp/tmp4byge9ba.json' failed (returned 1) > > > > [...] > > > >> I'm using emscripten 3.1.1~dfsg+~1.39.6-3 with a clean Debian testing > >> (this is probably the last version available when `apt upgrade`). > >> > >> Yes, I got same error after fixing paths. This is another problem, > >> upstream uses a custom clang (from wasi-sdk) > > > > I don't understand how "pristine system" and "after fixing paths" fit > > together. > > I manually linked /usr/bin/clang-13 to /usr/bin/clang (and other binaries) > > > Please provide a full build log (as attached file, not inline), so it is > > possible to see (and therefore replicate) the exact commands executed on > > the prisitne Debian testing system leading to the reported state. > > This is just a manual test, before doing these manual links, I got: > >$ emcc src/lexer.c -s WASM=1 -I include-wasm -o lib/lexer.wasm >emcc: error: clang executable not found at `/usr/bin/clang` > > No more logs, just one command that returned one error Sorry, I cannot work with that limited information. As a notable example, I would like to see where exactly during the use of the pristine system emscripten emits its initial notice that it has created a configuration file. Until reproducible I am most likely to ignore this bugreport, considering it "a case of fly-by UFOs bit-flipping the data storage of the system". - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1003878: SOGo package README.Debian states built with GnuTLS while it is being built with openssl
Hi! El dl. 17 de 01 de 2022 a les 14:10 +0100, en/na Bernhard Dick va escriure: > > The README.Debian file of the SOGo package states there is no S/MIME > support in the webinterface due to the package being built using > GnuTLS > instead of openssl while a switch to openssl has been done in commit > f2d148cd Oh, thanks for that! It's now fixed in git. -- Jordi Mallach
Bug#726542: ITA: pngphoon -- Creates a png file with the current phase of the moon
Hi, The package should be without updates to ever and in the situation it is worthy for orphaned packages. The update I worked on should be the last one for this package. Edit leaving the package orphaned in case you change your mind. Leandro
Bug#1003879: systemd-coredump - No longer any relation with libdw1 for backtraces
Package: systemd-coredump Version: 250.2-3 Severity: normal systemd 250 started to use libdw1 via dlopen instead of direct linking. So systemd-coredump should at least add a Recommends for it. Bastian -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)