Bug#1061487: bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1
On Thu, Jan 25, 2024 at 02:39:03PM +0200, Peter Pentchev wrote: > [ Impact ] > Users who upgrade from RPM 4.16.0 or earlier to 4.18.0 cannot use > their database of packages already installed via RPM. IOW, qubes 4.x users: https://github.com/QubesOS/qubes-issues/issues/8482 "Dom0 updates fail when update qube is based on Debian 12 or Whonix 17" -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Bananas are berries. signature.asc Description: PGP signature
Bug#1061526: astroidmail: Stop using webkit2gtk 4.0
Source: astroidmail Version: 0.16-2 Severity: serious Tags: trixie sid User: pkg-webkit-maintain...@lists.alioth.debian.org Usertags: webkit-4.0 The webkit2gtk maintainers intend to stop building the 4.0 API soon. Please switch to using the 4.1 API which is the same as the 4.0 API except that it uses libsoup3 instead of libsoup2.4. Unfortunately, astroidmail uses libsoup directly so it is necessary to port it from libsopu2.4 to libsoup3 to fix this issue. There is some documentation and many examples at https://gitlab.gnome.org/GNOME/libsoup/-/issues/218 On behalf of the webkit2gtk maintainers, Jeremy Bícha
Bug#995399: bluez: bluetooth disable after few seconds
Package: bluez Version: 5.71-1 Followup-For: Bug #995399 X-Debbugs-Cc: mar...@tonusoo.ee I observed pretty much the identical behavior described by Flavio Amieiro after upgrading to 5.71-1. The bluetooth speaker connected for ~5 seconds, after which the bluetoothd segfaulted: [Thu Jan 25 23:37:29 2024] input: Bedroom speaker (AVRCP) as /devices/virtual/input/input36 [Thu Jan 25 23:37:36 2024] bluetoothd[8904]: segfault at 5621e0155f79 ip 562480a64375 sp 7ffd9e9c66e0 error 4 in bluetoothd[562480a42000+ec000] likely on CPU 0 (core 0, socket 0) [Thu Jan 25 23:37:36 2024] Code: 00 31 c0 e9 54 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 41 55 41 54 55 53 48 83 ec 08 48 8b 2a 48 8b 7a 08 <48> 8b 45 20 4c 8b ad 88 00 00 00 4c 8b 20 48 85 ff 74 19 c7 47 08 Upgrading to 5.72 from the upstream fixed this issue. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bluez depends on: ii dbus [default-dbus-system-bus] 1.14.10-4 ii init-system-helpers 1.66 ii kmod31-1 ii libasound2 1.2.10-3 ii libc6 2.37-14 ii libdbus-1-3 1.14.10-4 ii libdw1 0.190-1+b1 ii libglib2.0-02.78.3-2 ii libreadline88.2-3 ii libudev1255.3-1 ii udev255.3-1 bluez recommends no packages. Versions of packages bluez suggests: ii pulseaudio-module-bluetooth 16.1+dfsg1-3 -- Configuration Files: /etc/bluetooth/main.conf changed [not included] -- no debconf information
Bug#1061527: elogind: install files into /usr
Source: elogind
Version: 252.9-1debian3
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2
We want to finalize the /usr-merge via DEP17 by moving all files to
/usr. elogind installs files into /lib and /bin; these should be moved
into the respective canonical locations in /usr/.
Please find a patch attached. It has been build-tested.
Note: this should not be backported to bookworm. If you intend to
backport, please use dh_movetousr instead.
If your package will change for the t64 transition or otherwise
rename/split/move its binaries (packages) during trixie, please
then upload to experimental and get in touch with the UsrMerge
driver, please see the wiki [1].
Michael
[1] https://wiki.debian.org/UsrMerge
diff -Nru elogind-252.9/debian/changelog elogind-252.9/debian/changelog
--- elogind-252.9/debian/changelog 2023-12-26 18:26:30.0 +0100
+++ elogind-252.9/debian/changelog 2024-01-25 23:27:16.0 +0100
@@ -1,3 +1,10 @@
+elogind (252.9-1debian3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Install files into their canonical location in /usr. (Closes: #-1)
+
+ -- Michael Biebl Thu, 25 Jan 2024 23:27:16 +0100
+
elogind (252.9-1debian3) unstable; urgency=medium
* d/control: add Build-Depends: libmount-dev to fix nocheck build.
diff -Nru elogind-252.9/debian/elogind.install
elogind-252.9/debian/elogind.install
--- elogind-252.9/debian/elogind.install2023-12-26 18:26:30.0
+0100
+++ elogind-252.9/debian/elogind.install2024-01-25 23:27:16.0
+0100
@@ -1,11 +1,10 @@
-bin/
usr/bin
etc/elogind/*.conf
-lib/elogind/
-lib/*/elogind/
-lib/udev/rules.d/70-uaccess.rules
-lib/udev/rules.d/71-seat.rules
-lib/udev/rules.d/73-seat-late.rules
+usr/lib/elogind/
+usr/lib/*/elogind/
+usr/lib/udev/rules.d/70-uaccess.rules
+usr/lib/udev/rules.d/71-seat.rules
+usr/lib/udev/rules.d/73-seat-late.rules
usr/share/bash-completion/
usr/share/dbus-1/
usr/share/locale/
diff -Nru elogind-252.9/debian/libelogind0.install
elogind-252.9/debian/libelogind0.install
--- elogind-252.9/debian/libelogind0.install2023-12-26 18:26:30.0
+0100
+++ elogind-252.9/debian/libelogind0.install2024-01-25 23:23:29.0
+0100
@@ -1 +1 @@
-lib/*/libelogind.so.*
+usr/lib/*/libelogind.so.*
diff -Nru elogind-252.9/debian/libelogind0.links
elogind-252.9/debian/libelogind0.links
--- elogind-252.9/debian/libelogind0.links 2023-12-26 18:26:30.0
+0100
+++ elogind-252.9/debian/libelogind0.links 2024-01-25 23:23:53.0
+0100
@@ -1,2 +1,2 @@
#! /usr/bin/dh-exec
-lib/${DEB_HOST_MULTIARCH}/libelogind.so.0
lib/${DEB_HOST_MULTIARCH}/libsystemd.so.0
+usr/lib/${DEB_HOST_MULTIARCH}/libelogind.so.0
usr/lib/${DEB_HOST_MULTIARCH}/libsystemd.so.0
diff -Nru elogind-252.9/debian/libelogind-dev-doc.install
elogind-252.9/debian/libelogind-dev-doc.install
--- elogind-252.9/debian/libelogind-dev-doc.install 2023-12-26
18:26:30.0 +0100
+++ elogind-252.9/debian/libelogind-dev-doc.install 2024-01-25
23:26:26.0 +0100
@@ -1,2 +1,3 @@
usr/share/doc/elogind/ usr/share/doc/libelogind-dev-doc/
usr/share/man/man3/*
+usr/lib/*/libelogind.so
diff -Nru elogind-252.9/debian/libelogind-dev.links
elogind-252.9/debian/libelogind-dev.links
--- elogind-252.9/debian/libelogind-dev.links 2023-12-26 18:26:30.0
+0100
+++ elogind-252.9/debian/libelogind-dev.links 1970-01-01 01:00:00.0
+0100
@@ -1,2 +0,0 @@
-#! /usr/bin/dh-exec
-lib/${DEB_HOST_MULTIARCH}/libelogind.so.0
usr/lib/${DEB_HOST_MULTIARCH}/libelogind.so
diff -Nru elogind-252.9/debian/libpam-elogind.install
elogind-252.9/debian/libpam-elogind.install
--- elogind-252.9/debian/libpam-elogind.install 2023-12-26 18:26:30.0
+0100
+++ elogind-252.9/debian/libpam-elogind.install 2024-01-25 23:23:39.0
+0100
@@ -1,4 +1,4 @@
debian/extra/pam.d/ /etc
-lib/*/security/pam_elogind.so
+usr/lib/*/security/pam_elogind.so
usr/share/man/man8/pam_elogind.8
debian/extra/pam-configs/ /usr/share/
diff -Nru elogind-252.9/debian/rules elogind-252.9/debian/rules
--- elogind-252.9/debian/rules 2023-12-26 18:26:30.0 +0100
+++ elogind-252.9/debian/rules 2024-01-25 23:27:16.0 +0100
@@ -7,12 +7,12 @@
# behaviour
CONFFLAGS = \
- -Dpamlibdir=/lib/$(DEB_HOST_MULTIARCH)/security \
- -Drootlibdir=/lib/$(DEB_HOST_MULTIARCH) \
- -Dsplit-usr=true \
+ -Dpamlibdir=/usr/lib/$(DEB_HOST_MULTIARCH)/security \
+ -Drootlibdir=/usr/lib/$(DEB_HOST_MULTIARCH) \
+ -Dsplit-usr=false \
-Ddocdir=/usr/share/doc/elogind \
-Dman=true \
- -Dudevrulesdir=/lib/udev/rules.d \
+ -Dudevrulesdir=/usr/lib/udev/rules.d \
-Ddefault-kill-user-processes=false \
-Dtests=true \
-Dmode=release
Bug#1061528: libpam-encfs: install PAM module into /usr
Source: libpam-encfs Version: 0.1.4.4-15 Severity: normal Tags: patch User: helm...@debian.org Usertags: dep17m2 We want to finalize the /usr-merge via DEP17 by moving all files to /usr. libpam-encfs installs files into /lib; these should be moved into the respective canonical locations in /usr/. Please find a patch attached. It has been build-tested. Note: this should not be backported to bookworm. If you intend to backport, please use dh_movetousr instead. If your package will change for the t64 transition or otherwise rename/split/move its binaries (packages) during trixie, please then upload to experimental and get in touch with the UsrMerge driver, please see the wiki [1]. Michael [1] https://wiki.debian.org/UsrMerge diff -Nru libpam-encfs-0.1.4.4/debian/changelog libpam-encfs-0.1.4.4/debian/changelog --- libpam-encfs-0.1.4.4/debian/changelog 2023-01-19 18:43:33.0 +0100 +++ libpam-encfs-0.1.4.4/debian/changelog 2024-01-25 23:37:36.0 +0100 @@ -1,3 +1,10 @@ +libpam-encfs (0.1.4.4-15.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install PAM module into /usr. (Closes: #-1) + + -- Michael Biebl Thu, 25 Jan 2024 23:37:36 +0100 + libpam-encfs (0.1.4.4-15) unstable; urgency=medium [ Debian Janitor ] diff -Nru libpam-encfs-0.1.4.4/debian/patches/03_install_into_usr.patch libpam-encfs-0.1.4.4/debian/patches/03_install_into_usr.patch --- libpam-encfs-0.1.4.4/debian/patches/03_install_into_usr.patch 1970-01-01 01:00:00.0 +0100 +++ libpam-encfs-0.1.4.4/debian/patches/03_install_into_usr.patch 2024-01-25 23:37:34.0 +0100 @@ -0,0 +1,10 @@ +Index: libpam-encfs-0.1.4.4/Makefile +=== +--- libpam-encfs-0.1.4.4.orig/Makefile 2024-01-25 23:36:19.0 +0100 libpam-encfs-0.1.4.4/Makefile 2024-01-25 23:37:32.673299975 +0100 +@@ -1,4 +1,4 @@ +-PAM_LIB_DIR = $(DESTDIR)/lib/$(DEB_HOST_MULTIARCH)/security ++PAM_LIB_DIR = $(DESTDIR)/usr/lib/$(DEB_HOST_MULTIARCH)/security + CC = gcc + LD = ld + INSTALL = /usr/bin/install diff -Nru libpam-encfs-0.1.4.4/debian/patches/series libpam-encfs-0.1.4.4/debian/patches/series --- libpam-encfs-0.1.4.4/debian/patches/series 2021-02-24 23:08:46.0 +0100 +++ libpam-encfs-0.1.4.4/debian/patches/series 2024-01-25 23:37:20.0 +0100 @@ -1,2 +1,3 @@ 01_pam_encfs.c_hint-console-login-on-error.patch 02_Makefile_Debian-build-stuff.diff +03_install_into_usr.patch
Bug#1057511: Additional information
Dear Maintainers, Would it be possible to consider a merge request[1] that addresses this issue? Best Regards, Vladimir. [1] https://salsa.debian.org/java-team/jtreg/-/merge_requests/3
Bug#764684: ITA: splash -- Visualisation tool for Smoothed Particle Hydrodynamics simulation
retitle 764684 ITA: splash -- Visualisation tool for Smoothed Particle Hydrodynamics simulation owner 764684 ! thanks Hi all, I am interested in 'splash' and would like to adopt it. I am the Debian Maintainer (DM) of rednotebook, filezilla and libfilezilla, bglibs, librepfunc, w-scan-cpp, compton, so maintaining similar package types is familiar to me. Regards Phil -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram: https://www.instagram.com/kathenasorg/ signature.asc Description: This is a digitally signed message part
Bug#1061529: jline3 ftbfs with Java 21 due to this-escape warning
Source: jline3 Version: 3.3.1-3 Severity: important Tags: ftbfs User: debian-j...@lists.debian.org Usertags: default-java21 Dear Maintainers, The package fails to build with Java 21 default to do this-escape warning: [WARNING] COMPILATION WARNING : [INFO] - [WARNING] /<>/builtins/src/main/java/org/jline/builtins/Nano.java:[949,16] [this-escape] possible 'this' escape before subclass is fully initialized [INFO] 1 warning [INFO] - [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] error: warnings found and -Werror specified [INFO] 1 error [INFO] --- Best Regards, Vladimir -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-14-generic (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1018838: formiko: Switch to webkit2gtk 4.1
forwarded 1061526 https://github.com/astroidmail/astroid/issues/744
Bug#1061530: sugar-browse-activity: Stop using webkit2gtk 4.0
Source: sugar-browse-activity Version: 207-2 Severity: serious Tags: patch trixie sid User: pkg-webkit-maintain...@lists.alioth.debian.org Usertags: webkit-4.0 Forwarded: https://salsa.debian.org/jbicha/sugar-browse-activity/-/commits/webkit The webkit2gtk maintainers intend to stop building the 4.0 API soon. Please switch to using the 4.1 API which is the same as the 4.0 API except that it uses libsoup3 instead of libsoup2.4. My colleague has submitted a patch for this issue. It works for me even though Sugar itself is still using libsoup2.4 and webkit2gtk 4.0. I have cherry-picked the patch to my fork of your repo in the webkit branch. https://salsa.debian.org/jbicha/sugar-browse-activity/-/commits/webkit On behalf of the webkit2gtk maintainers, Jeremy Bícha
Bug#1061531: sugar: Stop using webkit2gtk 4.0
Source: sugar Version: 0.120-1 Severity: serious Tags: trixie sid User: pkg-webkit-maintain...@lists.alioth.debian.org Usertags: webkit-4.0 The webkit2gtk maintainers intend to stop building the 4.0 API soon. Please switch to using the 4.1 API which is the same as the 4.0 API except that it uses libsoup3 instead of libsoup2.4. There is some documentation and many examples of libsoup2.4 porting at https://gitlab.gnome.org/GNOME/libsoup/-/issues/218 By the way, it is not possible to use libsoup2.4 and libsoup3 in the same process. I don't think this is a problem in the Debian archive for Sugar beyond sugar-browse-activity. And in that case, sugar-browse-activity was ported to libsoup3 first and appears to still work fine. On behalf of the webkit2gtk maintainers, Jeremy Bícha
Bug#1061532: cinnamon: Update to 6.0
Source: cinnamon Version: 5.8.4-4 Severity: wishlist Please package cinnamon 6.0. I am especially interested in seeing Cinnamon switch from libsoup2.4 to libsoup3. Thank you, Jeremy Bícha
Bug#1061533: cmake: CMake doesn't find googletest
Package: cmake
Version: 3.28.1-1
Severity: normal
X-Debbugs-Cc: s...@debian.org, hal...@debian.org
Hello, I have installed cmake 3.28.1-1 and googletest 1.14.0-1 from
Debian testing, and I'm trying to use GTest with CMake as follows:
```
# CMakeLists.txt
cmake_minimum_required(VERSION 3.14)
project(foo)
enable_testing()
find_package(GTest REQUIRED)
add_executable(foo foo.cc)
target_link_libraries(foo GTest::gtest GTest::gtest_main)
add_test(AllTestsInFoo foo)
```
```
// foo.cc
TEST(Foo, foo) {
EXPECT_EQ(1 + 2, 3);
}
```
This is very close to the example provided in
/usr/share/cmake-3.28/Modules/FindGTest.cmake,
but it fails:
```
$ cmake .
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/lib/ccache/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/lib/ccache/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at
/usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR
GTEST_MAIN_LIBRARY)
Call Stack (most recent call first):
/usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:600
(_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.28/Modules/FindGTest.cmake:270
(FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:5 (find_package)
-- Configuring incomplete, errors occurred!
```
This usecase doesn't seem to unusual, so I suspect a bug somewhere in
FindGTest.cmake or maybe a missing file somewhere.
Best regards.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cmake depends on:
ii cmake-data3.28.1-1
ii libarchive13 3.7.2-1
ii libc6 2.37-13
ii libcurl4 8.5.0-2
ii libexpat1 2.5.0-2+b2
ii libgcc-s1 13.2.0-10
ii libjsoncpp25 1.9.5-6+b2
ii librhash0 1.4.3-3
ii libstdc++613.2.0-10
ii libuv11.46.0-3
ii procps2:4.0.4-2+b1
ii zlib1g1:1.3.dfsg-3+b1
Versions of packages cmake recommends:
ii gcc 4:13.2.0-2
ii make 4.3-4.1
Versions of packages cmake suggests:
pn cmake-doc
pn cmake-format
pn elpa-cmake-mode
ii ninja-build 1.11.1-2
-- no debconf information
Bug#1061534: mirror submission for mirror.leitecastro.com
Package: mirrors Severity: wishlist User: mirr...@packages.debian.org Usertags: mirror-submission Submission-Type: new Site: mirror.leitecastro.com Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd-amd64 i386 mips mips64el mipsel powerpc ppc64el riscv64 s390x Archive-http: /debian/ Archive-rsync: debian/ Maintainer: Tomas Leite Castro Country: PT Portugal Location: Lisbon Comment: I'm hosting /debian and /debian-cd. Would it be possible to get push syncs from debian directly? I also have space for /debian-backports and /debian-archive. Unfortunately I could not find a working mirror here in Portugal that supports rsync and has these mirrors. Best regards, Tomás Trace Url: http://mirror.leitecastro.com/debian/project/trace/ Trace Url: http://mirror.leitecastro.com/debian/project/trace/ftp-master.debian.org Trace Url: http://mirror.leitecastro.com/debian/project/trace/mirror.leitecastro.com
Bug#1061535: wayland-protocols: Please update to 1.33
Source: wayland-protocols Version: 1.32-1 Severity: wishlist wayland-protocols 1.33 has been released and the next version of mutter will be using it. Please package the new version. Thank you, Jeremy Bícha
Bug#1061533: cmake: CMake doesn't find googletest
On Fri, Jan 26, 2024 at 01:20:03AM +0100, Jonathan Neuschäfer wrote: > Package: cmake > Version: 3.28.1-1 > Severity: normal > X-Debbugs-Cc: s...@debian.org, hal...@debian.org > > > Hello, I have installed cmake 3.28.1-1 and googletest 1.14.0-1 from > Debian testing, and I'm trying to use GTest with CMake as follows: Sorry for the noise, I found the problem: For this to work, I need to install libgtest-dev. Perhaps the googletest package could include a hint to that effect in the description.
Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12
Hi Jeremy, Thanks for the suggestions. I was able to update my BIOS/UEFI but it didn't solve the issue unfortunately. So I change the type of my UEFI partition to BIOS boot partition, install grub-pc 2.12-1, run a grub-install and change the BIOS setting to "legacy BIOS only" as you mentioned and I'm able to boot now. I'm not sure of the consequences of switching from UEFI to BIOS, but at least, I have a GRUB I don't need to pin to 2.06. :-) Thanks again for your help. -- Nicolas Haller On 2024-01-24 00:49, Jeremy Davis wrote: Hi Nicolas, It might be worth double checking you have the latest BIOS/UEFI? If it's not the latest, then updating is worth a try IMO. FWIW I recently updated mine to resolve some (completely unrelated) issues on my Lenovo Gen 1 X1 Carbon on Bookworm. With no optical drive and no Windows, it initially seemed like a PITA, but ended up pretty easy. Process went something like this: - download relevant BIOS/UEFI update ISO specific to your model from Lenovo - extract IMG from ISO (using 'geteltorito' tool in 'genisoimage' pkg) - write IMG to USB (e.g. using 'dd') - boot from USB - update...! :) If you are already running latest, updating doesn't help, or you want to try a workaround, perhaps try disabling UEFI (i.e. disable secure boot and enable "legacy BIOS only" mode) and install the non-uefi grub (i.e. 'grub-pc')? Good luck. Cheers, Jeremy
Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12
Hello Mate, As per Jeremy suggestion, I switched to BIOS/grub-pc and I'm now able to boot my system. I guess this is not super ideal so I'll let you decide if you want to keep this bug open or not. If you need a tester for your idea, I can revert my system to UEFI and give it a try whenever it's ready. Thanks, -- Nicolas Haller On 2024-01-25 03:22, Mate Kukri wrote: Hello all, An idea for a workaround I have on such machines is to add an environment variable (or some other option) to GRUB that let's GRUB use the legacy-x86 kernel entry point even if the EFI stub appears supported (of course only with UEFI Secure Boot disabled). Based on previous discussion, it unfortunately seems that this isn't strictly a GRUB issue, and the problem comes from GRUB switching to booting the kernel using the method now preferred by upstream. Mate On Thu, Jan 25, 2024 at 2:21 AM Nicolas Haller wrote: On 2024-01-23 08:15, Julian Andres Klode wrote: Control: severity -1 important On Sat, Nov 25, 2023 at 05:36:41PM -0500, Nicolas Haller wrote: Package: grub-efi-amd64 Version: 2.06-13 Severity: critical Justification: breaks the whole system Dear Maintainer, My old laptop (Lenovo 11e) runs Sid and all was right before I updated it the other day (I don't do that very often). After that upgrade, GRUB wasn't able to load any kernel with the pretty much generic error "Error: can't load image". The version of GRUB was 2.12~rc1-12. If I try to boot again, GRUB tells me that I need to load the image first (I guess it somehow ignores the linux command and sends that when trying to load the initrd). I'm downgrading this bug severity, as a single system regressing in boot ability is not release critical. It is not possible for us to ensure that grub continues working on every single device out there, this grub will work for more hardware than previous grubs, and blocking the transition to testing because it doesn't work on your 11e is not helping anyone. We have now also uploaded 2.12-1 and of course we welcome any patches, but an old Lenovo 11e is not a priority, and we don't have any to test ourselves. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en Hello Julian, I'm not sure why the aggressive tone here, I was asked if this bug breaks my system and it does. How you want to handle this is up to you. I think GRUB is a critical piece of a Linux system and I thought it was worth to report the issue I encounter. As I mentioned, my Lenovo isn't the newest one but it's not an esoteric hardware either. It's a pretty regular amd64 laptop. To be honest, I'm a bit concerned that GRUB failed where it wasn't before (I would called that a regression) but also that it fails without giving any error message or any kind of clue that could help to debug this. I'm not a debian or ubuntu core developer and I don't know the first thing about how to develop or debug a boot loader. Asking me for patches isn't helping anyone. If you have any suggestion in order to fix or just to diagnose the issue, feel free to share that with me. Meanwhile, I'll try 2.12.1 and look for an upgrade as Jeremy suggested. Have a nice day, -- Nicolas Haller ___ Pkg-grub-devel mailing list pkg-grub-de...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grub-devel
Bug#1061529: jline3 ftbfs with Java 21 due to this-escape warning
Dear Maintainers, Would it be possible to consider a merge request[1] that addresses this issue? Best Regards, Vladimir. [1] https://salsa.debian.org/java-team/jline3/-/merge_requests/2
Bug#1061536: php-doctrine-deprecations: FTBFS for PHP 8.3
Source: php-doctrine-deprecations
Version: 1.1.2-1
Severity: normal
Tags: patch
X-Debbugs-Cc: athos.ribe...@canonical.com
Dear Maintainer,
This package FTBFS with PHP 8.3 (in experimental) due to the deprecation
mentioned in
https://www.php.net/manual/en/reflectionproperty.setvalue.php.
I am attaching a patch to fix the issue, which was also forwarded
upstream at https://github.com/doctrine/deprecations/pull/64.
Description: adjust tests for PHP 8.3
As of PHP 8.3.0, calling ReflectionProperty::setValue with a single argument
is deprecated.
See https://www.php.net/manual/en/reflectionproperty.setvalue.php for further
reference.
Author: Athos Ribeiro
Forwarded: https://github.com/doctrine/deprecations/pull/64
Last-Update: 2024-01-25
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/tests/Doctrine/Deprecations/DeprecationTest.php
+++ b/tests/Doctrine/Deprecations/DeprecationTest.php
@@ -28,11 +28,11 @@
// reset the global state of Deprecation class across tests
$reflectionProperty = new ReflectionProperty(Deprecation::class,
'ignoredPackages');
$reflectionProperty->setAccessible(true);
-$reflectionProperty->setValue([]);
+$reflectionProperty->setValue(null, []);
$reflectionProperty = new ReflectionProperty(Deprecation::class,
'triggeredDeprecations');
$reflectionProperty->setAccessible(true);
-$reflectionProperty->setValue([]);
+$reflectionProperty->setValue(null, []);
Deprecation::disable();
@@ -277,12 +277,12 @@
{
$reflectionProperty = new ReflectionProperty(Deprecation::class,
'type');
$reflectionProperty->setAccessible(true);
-$reflectionProperty->setValue(null);
+$reflectionProperty->setValue(null, null);
Deprecation::trigger('Foo', 'link', 'message');
$this->assertSame(0,
Deprecation::getUniqueTriggeredDeprecationsCount());
-$reflectionProperty->setValue(null);
+$reflectionProperty->setValue(null, null);
$_SERVER['DOCTRINE_DEPRECATIONS'] = 'track';
Deprecation::trigger('Foo', __METHOD__, 'message');
@@ -293,7 +293,7 @@
{
$reflectionProperty = new ReflectionProperty(Deprecation::class,
'type');
$reflectionProperty->setAccessible(true);
-$reflectionProperty->setValue(null);
+$reflectionProperty->setValue(null, null);
$_ENV['DOCTRINE_DEPRECATIONS'] = 'trigger';
$this->expectErrorHandler(
Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12
Hi Nicholas, On 26/1/24 11:40, Nicolas Haller wrote: Thanks for the suggestions. I was able to update my BIOS/UEFI but it didn't solve the issue unfortunately. :( If you haven't already, it may be worth reporting upstream (i.e. to grub devs) - they might have more ideas on troubleshooting, etc? So I change the type of my UEFI partition to BIOS boot partition, install grub-pc 2.12-1, run a grub-install and change the BIOS setting to "legacy BIOS only" as you mentioned and I'm able to boot now. Yay! I'm not sure of the consequences of switching from UEFI to BIOS, but at least, I have a GRUB I don't need to pin to 2.06. :-) AFAIK, it just means that you aren't using secureboot/UEFI so the risk of rootkits is potentially higher. TBH, I'm not sure how much risk there really is in practice though? FWIW, my laptop (a couple of years older than yours AFAIT) first had Debian 6/Squeeze installed - about ~11-12 years ago & upgraded since - has always been like that. IIRC I had to, to install Debian back then? It's always been rock solid reliable and I've never had any issues (beyond the odd Debian bug - at least to the best of my knowledge). I'm always a bit paranoid though, so super careful - daily automated aide scans, thunderbird with html disabled for email and firefox locked down for web browsing - always careful with what links I click, etc. So YMMV!? Thanks again for your help. You're most welcome. Have an awesome day! :) Cheers, Jeremy OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061537: kexec-tools: non-text error output
Package: kexec-tools
Version: 1:2.0.27-1
Severity: normal
Dear Maintainer,
root@chwast:/tmp# zcat /media/Image.gz | kexec -l -t Image /dev/stdin
--reuse-cmdline --dtb /usr/local/src/mt8173-elm-hana.dtb
Cannot read /dev/stdinroot@chwast:/tmp#
As evident from this transcript, the output isn't a text file.
(Also, it doesn't say why it couldn't read it; strace disagrees:
openat(AT_FDCWD, "/dev/stdin", O_RDONLY) = 4
lseek(4, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
read(4,
"MZ@\372\377?\0\24\0\0\0\0\0\0\0\0\0\0\333\33\0\0\0\0\n\0\0\0\0\0\0\0"...,
8192) = 8192
close(4)= 0
openat(AT_FDCWD, "/dev/stdin", O_RDONLY) = 4
newfstatat(4, "", {st_mode=S_IFIFO|0600, st_size=0, ...}, AT_EMPTY_PATH) = 0
close(4)= 0
write(2, "Cannot read /dev/stdin", 22Cannot read /dev/stdin) = 22
exit_group(1) = ?
it's a bizarre success, but a success nonetheless.)
Best,
наб
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.6.11 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages kexec-tools depends on:
ii debconf [debconf-2.0] 1.5.83
ii dpkg 1.22.2
ii libc6 2.37-13
ii libxenmisc4.17 4.17.2+76-ge1f9cb16e2-1
ii zlib1g 1:1.3.dfsg-3+b1
kexec-tools recommends no packages.
kexec-tools suggests no packages.
-- debconf information:
kexec-tools/use_grub_config: false
signature.asc
Description: PGP signature
Bug#1041723:
Just a request to bump this bug. While the original submitter's request (at 4.2, requesting an upgrade to 4.4 in July 2023) has been addressed with the present version (4.4), darktable has moved on to 4.6, as of December 2023. See: https://www.darktable.org/news/ At maintainers' convenience, please update the package :)! Thank you! Charlie
Bug#1061538: Old package separator "'" deprecated
Package: linklint Version: 2.3.5-7 File: /usr/bin/linklint Old package separator "'" deprecated at /usr/bin/linklint line 987...
Bug#1061539: wlrctl: missing arm64 version
Package: wlrctl Please also provide arm64 versions of this package! Might as well make the other missing versions too.
Bug#1061540: python3-qgis: upgrade warnings: SyntaxWarning: invalid escape sequence '\s' '\d'
Package: python3-qgis Version: 3.28.15+dfsg-1 Severity: minor Usertags: warnings Upgrading python3-qgis gives some syntax warnings: Setting up python3-qgis (3.28.15+dfsg-1) ... /usr/lib/python3/dist-packages/qgis/3d/__init__.py:70: SyntaxWarning: invalid escape sequence '\s' QgsAbstractMaterialSettings.TrianglesDataDefined.__doc__ = "Triangle based rendering with possibility of datadefined color \since QGIS 3.18" /usr/lib/python3/dist-packages/qgis/core/__init__.py:435: SyntaxWarning: invalid escape sequence '\d' QgsDataItem.SetCrs.__doc__ = "Can set CRS on layer or group of layers. \deprecated since QGIS 3.6 -- no longer used by QGIS and will be removed in QGIS 4.0" Since these are docstrings there is probably no consequence. -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-qgis depends on: hi libc62.37-12 ii libgcc-s113.2.0-10 ii libpython3.113.11.7-2 ii libqca-qt5-2 2.3.8-1 ii libqgis-3d3.28.153.28.15+dfsg-1 ii libqgis-analysis3.28.15 3.28.15+dfsg-1 ii libqgis-core3.28.15 3.28.15+dfsg-1 ii libqgis-gui3.28.15 3.28.15+dfsg-1 ii libqgis-server3.28.153.28.15+dfsg-1 ii libqgispython3.28.15 3.28.15+dfsg-1 ii libqscintilla2-qt5-152.14.1+dfsg-1 ii libqt5core5a 5.15.10+dfsg-6 ii libqt5gui5 5.15.10+dfsg-6 ii libqt5network5 5.15.10+dfsg-6 ii libqt5positioning5 5.15.10+dfsg-3 ii libqt5svg5 5.15.10-2 ii libqt5webkit55.212.0~alpha4-33 ii libqt5widgets5 5.15.10+dfsg-6 ii libqt5xml5 5.15.10+dfsg-6 ii libsqlite3-mod-spatialite5.1.0-1 ii libstdc++6 13.2.0-10 ii python3 3.11.6-1 ii python3-dateutil 2.8.2-3 ii python3-httplib2 0.20.4-3 ii python3-jinja2 3.1.2-1 ii python3-lxml 5.1.0-1 ii python3-markupsafe 2.1.3-1+b1 ii python3-owslib 0.29.3-1 ii python3-plotly 5.15.0+dfsg1-1 ii python3-psycopg2 2.9.9-1+b1 ii python3-pygments 2.15.1+dfsg-1 ii python3-pyproj 3.6.1-2+b1 ii python3-pyqt55.15.10+dfsg-1 ii python3-pyqt5.qsci 2.14.1+dfsg-1 ii python3-pyqt5.qtpositioning 5.15.10+dfsg-1 ii python3-pyqt5.qtsql 5.15.10+dfsg-1 ii python3-pyqt5.qtsvg 5.15.10+dfsg-1 ii python3-pyqt5.qtwebkit 5.15.10+dfsg-1 ii python3-qgis-common 3.28.15+dfsg-1 ii python3-requests 2.31.0+dfsg-1 ii python3-tz 2023.3.post1-2 ii python3-yaml 6.0.1-2 ii qgis-providers 3.28.15+dfsg-1 python3-qgis recommends no packages. python3-qgis suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1057511: Additional information
On Fri, Jan 26, 2024 at 11:48:23AM +1300, Vladimir Petko wrote: > [1] https://salsa.debian.org/java-team/jtreg/-/merge_requests/3 Merged and uploaded. Thank you for the patch!
Bug#1061541: ITP: ruby-redis-client -- redis-client is a simple, low-level, client for Redis 6+.
Package: wnpp Severity: wishlist Owner: Vivek K J X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: ruby-redis-client Version : 0.19.1 Upstream Contact: jean.bouss...@gmail.com * URL : https://github.com/redis-rb/redis-client * License : Expat Programming Lang: Ruby Description : redis-client is a simple, low-level, client for Redis 6+. Contrary to the redis gem, redis-client doesn't try to map all Redis commands to Ruby constructs, it merely is a thin wrapper on top of the RESP3 protocol. This package is a dependency of gitlab. This package will be maintained by Debian ruby team.
Bug#1043240: transition: pandas 1.5 -> 2.1
Hi On Tue, 23 Jan 2024 at 14:38, Julian Gilbey wrote: > We're nearly there (the transition page says it's 99% done), and when > this transition is complete, then python3-defaults 3.11.6+ will be > able to migrate to testing. python3-defaults/3.11.6-1 with Python 3.12 as a supported version is now in testing [1]. > Yes - please don't upload it to unstable yet. Uploading to > experimental is fine. Uploading to unstable now should be fine, but maybe wait for pandas/1.5.3+dfsg-12 to migrate first (in about four hours). Regards Graham [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055085#29
Bug#1061542: tracker-miners: FTBFS on amd64, arm64, loong64 and so on
Source: tracker-miners Version: 3.4.6-2 Severity: wishlist Tags: ftbfs patch User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, The package tracker-miners failed to compile on amd64, arm64, loong64 and other architectures in the Debian Package Auto-Building environment. The error messages are as follows, ``` .. === 54/54 test: tracker-miners:examples / query-sync start time: 21:21:01 duration: 1.68s result: exit status 0 command: ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/usr/lib/loongarch64-linux-gnu TRACKER_EXAMPLES_AUTOMATED_TEST=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 TEST_ONTOLOGIES_DIR=/usr/share/tracker3/ontologies/nepomuk MALLOC_PERTURB_=224 /usr/bin/python3 /<>/obj-loongarch64-linux-gnu/run-uninstalled --store-tmpdir /<>/examples/python/query-sync.py --- stdout --- Music albums: --- stderr --- (tracker-miner-fs-3:1266574): Tracker-WARNING **: 21:21:01.850: Locale 'LANG' is not set, defaulting to C locale (tracker-miner-fs-3:1266574): libupower-glib-WARNING **: 21:21:02.093: Couldn't connect to proxy: Could not connect: No such file or directory (tracker-miner-fs-3:1266574): Tracker-WARNING **: 21:21:02.093: Unable to connect to UPower == Summary of Failures: 21/54 tracker-miners:extractor+audio / mp3-id3v2.4-1 FAIL 0.20s exit status 1 22/54 tracker-miners:extractor+audio / mp3-id3v2.3-empty-artist-album FAIL 0.18s exit status 1 23/54 tracker-miners:extractor+audio / mp3-id3v2.4-2 FAIL 0.18s exit status 1 24/54 tracker-miners:extractor+desktop / application FAIL 0.18s exit status 1 25/54 tracker-miners:extractor+desktop / link-wikipedia-tracker FAIL 0.18s exit status 1 26/54 tracker-miners:extractor+audio / flac-musicbrainz FAIL 0.18s exit status 1 27/54 tracker-miners:extractor+audio / vorbis-musicbrainz FAIL 0.18s exit status 1 28/54 tracker-miners:extractor+images / jpeg-basic FAIL 0.18s exit status 1 29/54 tracker-miners:extractor+images / jpeg-region-of-interest FAIL 0.18s exit status 1 30/54 tracker-miners:extractor+images / jpeg-gps-location FAIL 0.18s exit status 1 31/54 tracker-miners:extractor+images / jpeg-iptc-tags FAIL 0.18s exit status 1 32/54 tracker-miners:extractor+images / jpeg-iptcdata-records FAIL 0.18s exit status 1 33/54 tracker-miners:extractor+images / gif-comment-extension-block FAIL 0.18s exit status 1 35/54 tracker-miners:extractor+images / gif-xmp FAIL 0.18s exit status 1 36/54 tracker-miners:extractor+images / png-basic FAIL 0.18s exit status 1 37/54 tracker-miners:extractor+images / png-region-of-interest FAIL 0.18s exit status 1 38/54 tracker-miners:extractor+images / raw-cr2 FAIL 0.18s exit status 1 39/54 tracker-miners:extractor+images / tiff-basic FAIL 0.18s exit status 1 40/54 tracker-miners:extractor+playlists / playlist-test-1 FAIL 0.18s exit status 1 42/54 tracker-miners:extractor+office / oasis-doc FAIL 0.18s exit status 1 43/54 tracker-miners:extractor+office / office-doc FAIL 0.18s exit status 1 44/54 tracker-miners:extractor+office / powerpoint FAIL 0.18s exit status 1 45/54 tracker-miners:extractor+office / pdf-doc FAIL 0.18s exit status 1 46/54 tracker-miners:extractor+office / ps-doc FAIL 0.18s exit status 1 47/54 tracker-miners:extractor+office / ps-doc-atend FAIL 0.18s exit status 1 48/54 tracker-miners:extractor+office / psgz-doc FAIL 0.18s exit status 1 49/54 tracker-miners:extractor+video / mkv-basic FAIL 0.18s exit status 1 50/54 tracker-miners:extractor+video / mov-basic FAIL 0.18s exit status 1 51/54 tracker-miners:extractor+video / mp4-basic FAIL 0.18s exit status 1 52/54 tracker-miners:extractor+video / mp4-video-without-audio FAIL 0.18s exit status 1 Ok: 24 Expected Fail: 0 Fail: 30 Unexpected Pass:
Bug#1061348: [debian-mysql] Bug#1061348: mariadb: install PAM modules and systemd unit files into /usr
I opened an MR about this one at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/65 to get CI validation. I will do some more testing over the weekend and then merge both. Thanks for your contribution!
Bug#1042858: promod3: unable to install on arm64
Hi, On Tue, 1 Aug 2023 23:23:39 +0200 Sebastian Ramacher wrote: $ apt-get install promod3 Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: promod3 : Depends: python3-ost but it is not installable Depends: python3-promod3 but it is not installable E: Unable to correct problems, you have held broken packages. promod3 is arch:all, but it depends on arch:any packages which build on amd64 only. Is it necessary to limit the architecture list for promod3? I am reluctant to do so as there will be the need to manually update the list every time a new architecture becomes supported by its arch:any dependencies. Andrius
Bug#1061511: gedit-source-code-browser-plugin: Upstream unmaintained for over a decade
Dear Kip, thanks for your mail and references. I have asked ildar, in the bug you referred to, additional details on what broke in the last Gedit versions. If anybody is able to fix his fork, or produce another one and make some minimal commitment to update it (or accept contributions for it) over time, I will be happy to switch the Debian package to it. The best thing would clearly be having an up to date fork owned by a project, rather than an individual who (legitimately) writes "I personally don't plan to maintain this regularly". I would be happy to be in such a project and occasionally contribute - while I would not want to simply package my personal fork. Pietro
Bug#1043240: transition: pandas 1.5 -> 2.1
On Fri, Jan 26, 2024 at 08:43:03AM +0200, Graham Inggs wrote: > Hi > > On Tue, 23 Jan 2024 at 14:38, Julian Gilbey wrote: > > We're nearly there (the transition page says it's 99% done), and when > > this transition is complete, then python3-defaults 3.11.6+ will be > > able to migrate to testing. > > python3-defaults/3.11.6-1 with Python 3.12 as a supported version is > now in testing [1]. Wonderful news! Congratulations to everyone who helped to make this happen! Best wishes, Julian
Bug#1061494: [Pkg-xmpp-devel] Bug#1061494: create a prosody-config package that will configure prosody with good xmpp compliance by default with debconf
Hi On 25/1/24 20:59, Martin wrote: > Hi Praveen, > > IMHO, that's a good idea! Yes, sounds nice. > Esp. I like to have a config that is as similar as possible to Snikket, > for those, who like to selfhost, but want to avoid docker. > > I'm not sure, if that package should be part of prosody itself or if it > should be a separate source package with a binary package, that depends > on both prosody and prosody-modules. another source package sounds too much. It can be included in prosody source. Cheers -- - | ,''`. Victor Seva | | : :' : linuxman...@torreviejawireless.org | | `. `' PGP: 8F19 CADC D42A 42D4 5563 730C 51A0 9B18 CF5A 5068 | |`- Debian Developer | - OpenPGP_signature.asc Description: PGP signature OpenPGP_0x7D7B65C42A0EC8B2.asc Description: application/pgp-keys
Bug#1054574: adminer seems dead upstream, switch to adminerevo ?
Hi, Status update: the work is done. src:adminerevo and packaged dependency are awaiting sponsorship. https://mentors.debian.net/package/libjs-jush/ https://mentors.debian.net/package/adminerevo/ Thanks, Alex
Bug#1061543: indent: CVE-2024-0911
Source: indent X-Debbugs-CC: t...@security.debian.org Severity: normal Tags: security Hi, This was assigned CVE-2024-0911: https://lists.gnu.org/archive/html/bug-indent/2024-01/msg1.html If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-0911 https://www.cve.org/CVERecord?id=CVE-2024-0911 Please adjust the affected versions in the BTS as needed.
Bug#1055329: Offer of support/assistance
Hi, > My name is Jeremy and I'd like to offer you my support and assistance in > your efforts to package and maintain AdminerEvo if that's of any use to you? Many thanks for your offer and your are welcome to help for this. I had forgotten to post a status update on this particular work item: the work is essentially done, I'm just seeking a Debian developper (I'm not) to upload the new package to the Debian archive and grant me access for further uploads. Thanks, Alex
