Bug#1077098: marked as pending in ccrypt
Control: tag -1 pending Hello, Bug #1077098 in ccrypt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/ccrypt/-/commit/102694749767bc5d69b328b084a3ee35ccea7846 Rebuild against dh-elpa >=2.1.5 (Closes: #1077098). (this message was generated automatically) -- Greetings https://bugs.debian.org/1077098
Bug#1075573: tightvnc: ftbfs with GCC-14
Hello debian-gcc team, On Fri, 2024-07-05 at 23:48 +0200, Sven Geuer wrote: > On Wed, 2024-07-03 at 12:46 +, Matthias Klose wrote: > > > Package: src:tightvnc > > Version: 1:1.3.10-8 > > [...] > > Please keep the issue open until the package can be built in > > a follow-up test rebuild. I wonder when this test rebuild will happen. > > > > The package fails to build in a test rebuild on at least amd64 with > > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. > > [...] > > tightvnc 1:1.3.10-9 fixes the issue according to my tests. > > As requested above, I keep the bug open. As a reminder, tightvnc 1:1.3.10-9 fixes the issue. Best, Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#1074517: marked as pending in changeme
Control: tag -1 pending Hello, Bug #1074517 in changeme reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/changeme/-/commit/c29a3d1b51c60d4b3d8d154e59d88f162ab2b63e Replace python3-pysnmp4 by python3-pysnmp-lextudio (Closes: #1074517). The original pysnmp is not maintained upstream any longer and, thus, did not and will not adopt the changes Python 3.12 brought. Luckily there is a trustworthy fork available. See https://www.pysnmp.com/history for details. (this message was generated automatically) -- Greetings https://bugs.debian.org/1074517
Bug#1074500: marked as pending in pompem
Control: tag -1 pending Hello, Bug #1074500 in pompem reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/pompem/-/commit/503578cc4bea4940ff64f47da52a371953b643d1 Escape or replace backslashes in strings (Closes: #1074500). Python 3.12 throws syntax warnings regarding invalid escape sequences. In the case of pompem the invalid escape sequences were caused by unescaped or erroneous backslashes. (this message was generated automatically) -- Greetings https://bugs.debian.org/1074500
Bug#1066337: tightvnc: FTBFS: vncconnect.c:17:5: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration]
Hi Lucas, On Wed, 2024-03-13 at 12:45 +0100, Lucas Nussbaum wrote: > Source: tightvnc > Version: 1:1.3.10-7 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > This is most likely caused by a change in dpkg 1.22.6, that enabled > -Werror=implicit-function-declaration. For more information, see > https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration That is hard to correct, - this software is abandonware - there are about 250 warnings regarding implicit function declaration, - there is no generic way to get rid of them. I had a closer look revealing that there are many different cases to consider. I am afraid it will take weeks or even months to fix this bug. On the other hand I could override dpkg by injecting -Wno-error=implicit-function-declaration. Would that be acceptable? Cheers, Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#1034213: arno-iptables-firewall: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Unblock requested: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034621 -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#1034213: arno-iptables-firewall: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Hello Laurant, Hello Andreas, On Wed, 2023-04-12 at 13:43 +0200, Andreas Henriksson wrote: > On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > > Package: arno-iptables-firewall > > Version: 2.1.1-7 > > Severity: serious > > Tags: sid bookworm > > User: debhel...@packages.debian.org > > Usertags: systemd-files-in-usr-bookworm > > > > Dear Maintainer, > > > > It seems that your package arno-iptables-firewall is shipping files > > (.service, .socket or > > .timer) in /usr/lib/systemd/system. > [...] > > It seems the package has manually written maintainer scripts (instead > of > letting debhelper generating the proper code): > > ``` > arno-iptables-firewall-2.1.1> grep -R deb-systemd-helper debian/ > debian/postrm: # Remove deb-systemd-helper's state file > debian/postrm: deb-systemd-helper purge > arno-iptables-firewall.service > debian/postinst:deb-systemd-helper enable > arno-iptables-firewall.service > ``` > > So while I think manually written maintscript code should be frowned > upon (since it's a very common source of bugs), I guess this means > this bug is not RC severity?! > Laurent, as Andreas already pointed out arno-iptables-firewall (AIF) does not make use of dh_installsystemd but instead uses deb-systemd- helper with its maintainer scripts. A quick look into the source code of deb-systemd-helper [1] showed that this tools can deal with a service file stored in /usr/lib/systemd/system. This matches my observation that since arno-iptables-firewall 2.1.1-5 local debci runs using qemu as well as those at the Ubuntu site [2] were processed successfully. Debian's CI [3] unfortunately does not support the isolation-machine restriction, so there are no successful tests logged there. Therefore this bug against arno-iptables-firewall seems like a false negative to me, and I would like to ask you to check my arguments and close the bug eventually. Let me know if you still believe the service file should be moved back to /lib from /usr/lib. Andreas, I am not sure how it might be possible to have everything created automatically by debhelper, especially the part creating an initial configuration from user input might prevent this. If you have any suggestions how to simplify the maintainer scripts I am happy to adopt these. Best, Sven [1] https://sources.debian.org/src/init-system-helpers/1.65.2/script/deb-systemd-helper/#L153 [2] https://autopkgtest.ubuntu.com/packages/arno-iptables-firewall/jammy/amd64 [3] https://ci.debian.net/packages/a/arno-iptables-firewall/ -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#1001709: amule-daemon: amuled crashes with segmentation fault on startup
I cannot reproduce this bug any more. Connecting to the Kademlia network works again without any issues. No packages had been upgraded since the initial bug report. I suggest to reduce the bug's severity to normal. -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#1001709: amule-daemon: amuled crashes with segmentation fault on startup
Further observations: Setting ConnectToKad=0 in ~/.aMule/amule.conf lets amuled start up as expected, but of course without connecting to the Kademlia network. Activating Kademlia later on via amulegui > Preferences > Connection > Networks and bootstraping from known clients makes amuled crash again. -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#1001709: amule-daemon: amuled crashes with segmentation fault on startup
Package: amule-daemon Version: 1:2.3.3-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: debma...@g-e-u-e-r.de Dear Maintainer, amuled crashes on startup since my recent system upgrade. Here's what gdb reveals. (gdb) run Starting program: /usr/bin/amuled [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Detaching after vfork from child process 3950] 2021-12-14 18:42:31: Initialising aMuleD 2.3.3 compiled with wxBase(GTK2) v3.0.5 and Boost 1.74 2021-12-14 18:42:31: Checking if there is an instance already running... 2021-12-14 18:42:31: No other instances are running. [Detaching after vfork from child process 3952] [Detaching after vfork from child process 3954] [Detaching after vfork from child process 3956] [Detaching after vfork from child process 3958] [Detaching after vfork from child process 3960] [Detaching after vfork from child process 3965] [Detaching after vfork from child process 3970] [Detaching after vfork from child process 3975] 2021-12-14 18:42:33: ListenSocket: Ok. [New Thread 0x7721e640 (LWP 3980)] [New Thread 0x76a1d640 (LWP 3981)] [New Thread 0x7621c640 (LWP 3982)] [New Thread 0x75a1b640 (LWP 3983)] [New Thread 0x7521a640 (LWP 3984)] [New Thread 0x74a19640 (LWP 3985)] 2021-12-14 18:42:33: Loading temp files from /home/sg/.aMule/Temp. 2021-12-14 18:42:33: All PartFiles Loaded. 2021-12-14 18:42:33: amuled: OnInit - starting timer [New Thread 0x7fffd640 (LWP 3986)] 2021-12-14 18:42:33: Asio thread 1 started 2021-12-14 18:42:33: Asio thread 2 started 2021-12-14 18:42:33: Asio thread 3 started 2021-12-14 18:42:33: Asio thread 4 started [Thread 0x74a19640 (LWP 3985) exited] [Detaching after fork from child process 3987] Thread 1 "amuled" received signal SIGSEGV, Segmentation fault. 0x55679781 in Kademlia::CKademlia::ProcessPacket ( data=0x7fff8d10 "\344!\004\016\376TN\346\377\003\355j\261\245\006e:\003\331\"\241\311NU\001x\207\031\323\061\037\374\367@\217", lenData=lenData@entry=35, ip=ip@entry=1564980350, port=port@entry=51663, validReceiverKey=true, senderKey=...) at ../../src/kademlia/kademlia/Kademlia.cpp:303 303 ../../src/kademlia/kademlia/Kademlia.cpp: No such file or directory. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/2 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) LSM: AppArmor: enabled Versions of packages amule-daemon depends on: ii amule-common 1:2.3.3-2 ii libc6 2.32-5 ii libcrypto++8 8.6.0-2 ii libgcc-s1 11.2.0-12 ii libixml10 1:1.8.4-2 ii libpng16-16 1.6.37-3 ii libreadline8 8.1-2 ii libstdc++611.2.0-12 ii libupnp13 1:1.8.4-2 ii libwxbase3.0-0v5 3.0.5.1+dfsg-2+b1 ii lsb-base 11.1.0 ii zlib1g1:1.2.11.dfsg-2 Versions of packages amule-daemon recommends: ii amule-utils 1:2.3.3-2 ii unzip6.0-26 amule-daemon suggests no packages. -- Configuration Files: /etc/default/amule-daemon changed [not included] -- no debconf information
Bug#993184: Please switch upstream
Dear maintainer, I suggest to switch upstream to https://github.com/fer-moreira/floating-dock which is a fork of https://github.com/micheleg/dash-to-dock/. Floating-dock works perfectly fine for me in my bookworm installation. Cheers, Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#993187: gnome-shell-extension-hide-activities: does not declare compatibility with GNOME Shell 40
Please consider to switch upstream from https://github.com/shayelkin/gnome-hide-activities to https://github.com/nmingori/gnome-hide-actitivies-button. Cheers, Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#924042: Bug #924042 in tomb marked as pending
Control: tag -1 pending Hello, Bug #924042 in tomb reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/tomb/commit/670e61a7d47def1bdb29b92df4aaa3d1455e7e14 Add several missing Recommends and Suggests (Closes: #924042) (this message was generated automatically) -- Greetings https://bugs.debian.org/924042
