date:20240125

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#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12

2024-01-25 Thread Nicolas Haller


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#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12

2024-01-25 Thread Nicolas Haller


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#1061533: cmake: CMake doesn't find googletest

2024-01-25 Thread J . Neuschäfer

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#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#1061534: mirror submission for mirror.leitecastro.com

2024-01-25 Thread Tomas Leite Castro

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#1061533: cmake: CMake doesn't find googletest

2024-01-25 Thread Jonathan Neuschäfer

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#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#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#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#1018838: formiko: Switch to webkit2gtk 4.1

forwarded 1061526 https://github.com/astroidmail/astroid/issues/744

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#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#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#1061528: libpam-encfs: install PAM module into /usr

2024-01-25 Thread Michael Biebl

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#1061527: elogind: install files into /usr

2024-01-25 Thread Michael Biebl

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#995399: bluez: bluetooth disable after few seconds

2024-01-25 Thread Martin Tonusoo

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#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#1061487: bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1

2024-01-25 Thread Holger Levsen

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#1061509: closed by Bastian Germann (Re: RFS: compton/1-3 [ITA] -- compositor for X11, based on xcompmgr)

On Thu, 2024-01-25 at 21:45 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the sponsorship-requests package:
> 
> #1061509: RFS: compton/1-3 [ITA] -- compositor for X11, based on xcompmgr
> 
> It has been closed by Bastian Germann .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Bastian Germann 
> 
> by
> replying to this email.
> 
> 

Hi Bastian,

Thanks for sponsoring. 

I just did a dput -f fixing a couple more things as your email came through. :-)

I will get them in unstable soon.

Will you process my upload and salsa rights for the package also please.

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#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend

2024-01-25 Thread Antoine


On 1/25/24 22:08, Salvatore Bonaccorso wrote:

Is this a regression from 6.6.11-1


Yes


When you resume from suspend, do you get anything logged in the kernel log,
can you attach it here?


As it was mixed with other upgrades from testing (libc6, grub, polkit 
mainly),

for now I just rolled back from a backup, and did them incrementally
..to finish with only 6.6.13-1  which reproduced the issue.
I rolled back again so now I need to update my backup and will then try 
getting some logs

Bug#1055869: lxc-templates: need upgrade from upstream for templates issue

2024-01-25 Thread Sven Geuer

Package: lxc-templates
Version: 3.0.4.48.g4765da8-2
Followup-For: Bug #1055869

Dear Maintainer,

/usr/share/lxc/templates/lxc-debian contains two errors blocking the
creation of debian containers of archived debian releases per

lxc-create  -n -jessie-container -t debian --  
--mirror=http://archive.debian.org/debian 
--keyring=/usr/share/keyrings/debian-archive-removed-keys.gpg -a amd64 -r jessie

The errors are:

1) --keyring is not recognized as a valid option
2) --mirror is ignored

The latest upstream commit (74a6743) fixes both issues.

Please upgrade the debian package to this commit.

Sven

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lxc-templates depends on:
ii  lxc  1:5.0.3-2

Versions of packages lxc-templates recommends:
ii  bridge-utils   1.7.1-1
pn  busybox-static 
ii  cloud-image-utils  0.33-1
ii  debootstrap    1.0.134
ii  distro-info    1.7
ii  mmdebstrap 1.4.0-1
ii  openssl    3.1.4-2
ii  rsync  3.2.7-1+b1
ii  uuid-runtime   2.39.3-2
ii  xz-utils   5.4.5-0.3

Versions of packages lxc-templates suggests:
ii  qemu-user-static  1:8.1.2+ds-1

-- no debconf information

-- 
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585


signature.asc
Description: This is a digitally signed message part

Bug#1061525: does not boot from multi-device root filesystems

2024-01-25 Thread Steinar H. Gunderson

Package: bcachefs-tools
Version: 24+really1.3.4-2
Severity: normal

I have / as a multi-device bcachefs filesystem (two different SSDs,
with replicas=1). Booting from it was an, well, interesting endeavor :-)
It seems the following must be done in Debian before this Just Works(TM):

 - /etc/fstab must contain the UUID, not a colon-separated list of
   devices, or systemd will wait forever (because it doesn't understand
   the syntax; I believe this is an upstream issue).

 - Likewise, root= on the kernel command line must contain the UUID
   or the initramfs scripts will wait on some colon-separated device that does
   not (and will never) exist. grub-mkconfig must be updated to write root=
   _back_ from a colon-separated device list to a UUID; I don't know if there
   is already some kind of support for UUID-roots, but I think so.
   As of today, it fails with:

 /usr/sbin/grub-probe: error: failed to get canonical path of 
`/dev/nvme1n1p1:/dev/dm-2'.

 - initramfs must contain mount.bcachefs, since that is the only thing
   that knows how to probe a UUID into multiple devices. This means that
   the Rust parts needs to be built again, too (see #1060256).

 - The initramfs scripts attempt to rewrite UUID= _back_ to a
   single /dev device through probing, and give that to mount. It needs
   to avoid doing so for (multi-device) bcachefs filesystems, or they
   will never mount since they contain too few devices.

 - The GRUB command line must be rw, not ro; mounting with -o remount,rw
   gives: “bcachefs: bch2_parse_mount_opts() Invalid mount option errors:
   invalid selection”. I don't know if this is an upstream issue or if
   this is just considered a bug in our setup.

I don't have patches for any of this, unfortunately; I've just finagled
it by hand in my local system. But it's at least a laundry list :-)

/* Steinar */

Bug#1061524: tiff: CVE-2023-52356

Source: tiff
Version: 4.5.1+git230720-3
Severity: important
Tags: security upstream
Forwarded: https://gitlab.com/libtiff/libtiff/-/issues/622
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for tiff.

CVE-2023-52356[0]:
| A segment fault (SEGV) flaw was found in libtiff that could be
| triggered by passing a crafted tiff file to the
| TIFFReadRGBATileExt() API. This flaw allows a remote attacker to
| cause a heap-buffer overflow, leading to a denial of service.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-52356
https://www.cve.org/CVERecord?id=CVE-2023-52356
[1] https://gitlab.com/libtiff/libtiff/-/issues/622
[2] https://gitlab.com/libtiff/libtiff/-/merge_requests/546

https://gitlab.com/libtiff/libtiff/-/commit/51558511bdbbcffdce534db21dbaf5d54b31638a

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1061523: bookworm-pu: package tzdata/2023d-0+deb12u1

2024-01-25 Thread Aurelien Jarno

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: tzd...@packages.debian.org
Control: affects -1 + src:tzdata

[ Reason ]
A new upstream version of tzdata, 2023d, has been released with time
zone changes that might affect some of our users.

[ Impact ]
Some users might will have the wrong time on their system

[ Tests ]
There are no test for these changes.

[ Risks ]
The risk is quite low, importing new upstream version of tzdata has been
done many times in the past. In addition this new upstream version is in
testing/unstable for 3 weeks without any know issues.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
The new upstream version contains the following changes to past and
future timestamps:
- Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
- Vostok, Antarctica changed time zones on 2023-12-18.
- Casey, Antarctica changed time zones five times since 2020.
- Code and data fixes for Palestine timestamps starting in 2072.

In addition the leap second patch is dropped, as it is included in the
new upstream version.

[ Other info ]
I have already uploaded the package to the archive, thanks for
considering.
diff -Nru tzdata-2023c/africa tzdata-2023d/africa
--- tzdata-2023c/africa 2023-03-15 21:07:54.0 +0100
+++ tzdata-2023d/africa 2023-09-11 15:56:39.0 +0200
@@ -285,13 +285,6 @@
 # reproduced by other (more accessible) sites[, e.g.,]...
 # http://elgornal.net/news/news.aspx?id=4699258
 
-# From Paul Eggert (2014-06-04):
-# Sarah El Deeb and Lee Keath of AP report that the Egyptian government says
-# the change is because of blackouts in Cairo, even though Ahram Online (cited
-# above) says DST had no affect on electricity consumption.  There is
-# no information about when DST will end this fall.  See:
-# 
http://abcnews.go.com/International/wireStory/el-sissi-pushes-egyptians-line-23614833
-
 # From Steffen Thorsen (2015-04-08):
 # Egypt will start DST on midnight after Thursday, April 30, 2015.
 # This is based on a law (no 35) from May 15, 2014 saying it starts the last
diff -Nru tzdata-2023c/antarctica tzdata-2023d/antarctica
--- tzdata-2023c/antarctica 2023-01-24 08:20:36.0 +0100
+++ tzdata-2023d/antarctica 2023-12-20 18:26:39.0 +0100
@@ -80,6 +80,11 @@
 # - 2018 Oct  7 4:00 - 2019 Mar 17 3:00 - 2019 Oct  4 3:00 - 2020 Mar  8 3:00
 # and now - 2020 Oct  4 0:01
 
+# From Paul Eggert (2023-12-20):
+# Transitions from 2021 on are taken from:
+# https://www.timeanddate.com/time/zone/antarctica/casey
+# retrieved at various dates.
+
 # Zone NAMESTDOFF  RULES   FORMAT  [UNTIL]
 Zone Antarctica/Casey   0  -   -00 1969
 8:00   -   +08 2009 Oct 18  2:00
@@ -93,7 +98,12 @@
 8:00   -   +08 2019 Oct  4  3:00
11:00   -   +11 2020 Mar  8  3:00
 8:00   -   +08 2020 Oct  4  0:01
-   11:00   -   +11
+   11:00   -   +11 2021 Mar 14  0:00
+8:00   -   +08 2021 Oct  3  0:01
+   11:00   -   +11 2022 Mar 13  0:00
+8:00   -   +08 2022 Oct  2  0:01
+   11:00   -   +11 2023 Mar  9  3:00
+8:00   -   +08
 Zone Antarctica/Davis  0   -   -00 1957 Jan 13
7:00-   +07 1964 Nov
0   -   -00 1969 Feb
@@ -240,7 +250,50 @@
 #  year-round from 1960/61 to 1992
 
 # Vostok, since 1957-12-16, temporarily closed 1994-02/1994-11
-# See Asia/Urumqi.
+# From Craig Mundell (1994-12-15):
+# http://quest.arc.nasa.gov/antarctica/QA/computers/Directions,Time,ZIP
+# Vostok, which is one of the Russian stations, is set on the same
+# time as Moscow, Russia.
+#
+# From Lee Hotz (2001-03-08):
+# I queried the folks at Columbia who spent the summer at Vostok and this is
+# what they had to say about time there:
+# "in the US Camp (East Camp) we have been on New Zealand (McMurdo)
+# time, which is 12 hours ahead of GMT. The Russian Station Vostok was
+# 6 hours behind that (although only 2 miles away, i.e. 6 hours ahead
+# of GMT). This is a time zone I think two hours east of Moscow. The
+# natural time zone is in between the two: 8 hours ahead of GMT."
+#
+# From Paul Eggert (2001-05-04):
+# This seems to be hopelessly confusing, so I asked Lee Hotz about it
+# in person.  He said that some Antarctic locations set their local
+# time so that noon is the warmest part of the day, and that this
+# changes during the year and does not necessarily correspond to mean
+# solar noon.  So the Vostok time might have

Bug#1061522: atril: CVE-2023-52076

Source: atril
Version: 1.26.1-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 atril.

CVE-2023-52076[0]:
| Atril Document Viewer is the default document reader of the MATE
| desktop environment for Linux. A path traversal and arbitrary file
| write vulnerability exists in versions of Atril prior to 1.26.2.
| This vulnerability is capable of writing arbitrary files anywhere on
| the filesystem to which the user opening a crafted document has
| access. The only limitation is that this vulnerability cannot be
| exploited to overwrite existing files, but that doesn't stop an
| attacker from achieving Remote Command Execution on the target
| system. Version 1.26.2 of Atril contains a patch for this
| vulnerability.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-52076
https://www.cve.org/CVERecord?id=CVE-2023-52076
[1] 
https://github.com/mate-desktop/atril/security/advisories/GHSA-6mf6-mxpc-jc37
[2] 
https://github.com/mate-desktop/atril/commit/e70b21c815418a1e6ebedf6d8d31b8477c03ba50

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend

Control: tags -1 + moreinfo

On Thu, Jan 25, 2024 at 10:01:04PM +0100, r2rien wrote:
> Package: linux-image-6.6.13-amd64
> Version: 6.6.13-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: deb...@r2rien.net
> 
> Resuming from suspend keyboard totally unresponsive, thus no sysrq, no tty to
> the rescue, only power button.
> Stuck in gdm3 login screen,
> thus impossible to type password to unlock gnome-session
> I tagged it as grave so people with apt-listbugs could be informed

Please do provide some more information. Is this a regression from
6.6.11-1. In case yes, can you please try to bisect the changes in
upstreams 6.6.11 to 6.6.13 so we can isolate which change causes it?

When you resume from suspend, do you get anything logged in the kernel
log, can you attach it here?

Regards,
Salvatore

Bug#1061315: inn2 ftbfs with Python 3.12 as the default

2024-01-25 Thread Julien ÉLIE


Hi Matthias,

looking at m4/python.m4, this comes from getting the configuration out 
of the sysconfig module.


and _sysconfigdata_* has:

  'LOCALMODLIBS': '-lm  -lm   -lz -lm -lm   -lexpat  -lexpat '
  'Modules/_hacl/libHacl_Hash_SHA2.a -lz',


So, I'm not sure, how to better get the required information for 
linking, but this interface doesn't look very reliable.


maybe better use: python3-config --embed --libs


Oh, yes, your proposal to use python3-config is far better.
After testing, "python3-config --libs" is enough; there's no need in 
adding "--embed" as the "-lpython3.12" flag otherwise appears twice in 
PYTHON_LIBS.


Also, if python3-config (which may also be python2-config, python-config 
or any other variant) is not installed, I've kept the current check just 
to be sure we'll still have something.



I've opened a PR upstream:

https://github.com/rra/rra-c-util/pull/18/commits/63e4ddf8683c8c1dc429043ca8af7984eff21140

Thanks again.

--
Julien ÉLIE

« Le cercle est le plus long chemin d'un point au même point. » (Tom
  Stoppard, _Every Good Boy Deserves Favour_)

Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

2024-01-25 Thread Steev Klimaszewski

Does the cloud kernel even have wireless enabled?  My understanding
was the cloud kernels do not enable wireless.

Bug#1061521: linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend

2024-01-25 Thread r2rien

Package: linux-image-6.6.13-amd64
Version: 6.6.13-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: deb...@r2rien.net

Resuming from suspend keyboard totally unresponsive, thus no sysrq, no tty to
the rescue, only power button.
Stuck in gdm3 login screen,
thus impossible to type password to unlock gnome-session
I tagged it as grave so people with apt-listbugs could be informed


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (991, 'testing'), (990, 'unstable'), (600, 'stable'), (90, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.11-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-6.6.13-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod31-1
ii  linux-base  4.9

Versions of packages linux-image-6.6.13-amd64 recommends:
pn  apparmor 
ii  firmware-linux-free  20200122-2

Versions of packages linux-image-6.6.13-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.12-1
pn  linux-doc-6.6

Bug#1061520: mathtex: CVE-2023-51885 CVE-2023-51886 CVE-2023-51887 CVE-2023-51888 CVE-2023-51889 CVE-2023-51890

Source: mathtex
Version: 1.03-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for mathtex.

CVE-2023-51885[0]:
| Buffer Overflow vulnerability in Mathtex v.1.05 and before allows a
| remote attacker to execute arbitrary code via the length of the
| LaTeX string component.


CVE-2023-51886[1]:
| Buffer Overflow vulnerability in the main() function in Mathtex 1.05
| and before allows a remote attacker to cause a denial of service
| when using \convertpath.


CVE-2023-51887[2]:
| Command Injection vulnerability in Mathtex v.1.05 and before allows
| a remote attacker to execute arbitrary code via crafted string in
| application URL.


CVE-2023-51888[3]:
| Buffer Overflow vulnerability in the nomath() function in Mathtex
| v.1.05 and before allows a remote attacker to cause a denial of
| service via a crafted string in the application URL.


CVE-2023-51889[4]:
| Stack Overflow vulnerability in the validate() function in Mathtex
| v.1.05 and before allows a remote attacker to execute arbitrary code
| via crafted string in the application URL.


CVE-2023-51890[5]:
| An infinite loop issue discovered in Mathtex 1.05 and before allows
| a remote attackers to consume CPU resources via crafted string in
| the application URL.

[6] contains the "fuzzing mathtex" report.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-51885
https://www.cve.org/CVERecord?id=CVE-2023-51885
[1] https://security-tracker.debian.org/tracker/CVE-2023-51886
https://www.cve.org/CVERecord?id=CVE-2023-51886
[2] https://security-tracker.debian.org/tracker/CVE-2023-51887
https://www.cve.org/CVERecord?id=CVE-2023-51887
[3] https://security-tracker.debian.org/tracker/CVE-2023-51888
https://www.cve.org/CVERecord?id=CVE-2023-51888
[4] https://security-tracker.debian.org/tracker/CVE-2023-51889
https://www.cve.org/CVERecord?id=CVE-2023-51889
[5] https://security-tracker.debian.org/tracker/CVE-2023-51890
https://www.cve.org/CVERecord?id=CVE-2023-51890
[6] https://blog.yulun.ac.cn/posts/2023/fuzzing-mathtex/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1054214: gnome: caps-lock for upper case accented letters does not work anymore

Control: found -1 mutter/43.8-0+deb12u1

On Thu, Jan 25, 2024 at 3:16 PM  wrote:
> I found the cause of the error: the backports version of ibus. By
> restoring the affected packages to the official Debian 12 version,
> everything works perfectly again.

Ok, then a test case would look something like this:

Test Case
-
Install ibus from backports. Log out and log back in.
Open a terminal and install basic French support:
sudo dpkg-reconfigure locales
Select fr_FR.UTF-8 when prompted.

Open the Settings app. In the sidebar, click Keyboard
Click +, choose French (France), then choose the French (AZERTY) keyboard
Close the Settings app
In the top right of the screen, click en and switch the keyboard
layout to French (AZERTY)
In the text editor, type é (this is the number 2 key on a US English keyboard).
Now, press the Caps Lock key to enable Caps Lock.
Press the same key. You should get É

Fix

We just need to cherry-pick 6fe1b3145f8 for mutter.

Thank you,
Jeremy Bícha

Bug#1061519: shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551

Source: shim
Version: 15.7-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 15.7-1~deb11u1

Hi,

The following vulnerabilities were published for shim.

According to [6]:

* Various CVE fixes:
  CVE-2023-40546 mok: fix LogError() invocation
  CVE-2023-40547 - avoid incorrectly trusting HTTP headers
  CVE-2023-40548 Fix integer overflow on SBAT section size on 32-bit system
  CVE-2023-40549 Authenticode: verify that the signature header is in bounds.
  CVE-2023-40550 pe: Fix an out-of-bound read in verify_buffer_sbat()
  CVE-2023-40551: pe-relocate: Fix bounds check for MZ binaries

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40546
https://www.cve.org/CVERecord?id=CVE-2023-40546
[1] https://security-tracker.debian.org/tracker/CVE-2023-40547
https://www.cve.org/CVERecord?id=CVE-2023-40547
[2] https://security-tracker.debian.org/tracker/CVE-2023-40548
https://www.cve.org/CVERecord?id=CVE-2023-40548
[3] https://security-tracker.debian.org/tracker/CVE-2023-40549
https://www.cve.org/CVERecord?id=CVE-2023-40549
[4] https://security-tracker.debian.org/tracker/CVE-2023-40550
https://www.cve.org/CVERecord?id=CVE-2023-40550
[5] https://security-tracker.debian.org/tracker/CVE-2023-40551
https://www.cve.org/CVERecord?id=CVE-2023-40551
[6] https://github.com/rhboot/shim/releases/tag/15.8

Regards,
Salvatore

Bug#1057524:

Dear Maintainers,

 I apologise for the confusion, I have targeted the wrong fork with
the MR. The correct one is here[1]

Best Regards,
 Vladimir.

[1] https://salsa.debian.org/java-team/lombok/-/merge_requests/2

Bug#1054214: gnome: caps-lock for upper case accented letters does not work anymore

2024-01-25 Thread cufalo

Il giorno gio, 25/01/2024 alle 13.43 -0500, Jeremy Bícha ha scritto:
> 
> Perhaps the same patch from Mutter 45 would apply to Mutter 43. If
> so,
> this bug could be fixed for Debian 12.  It's a bit easier if the
> problem can be reproduced on a developer's computer though.
> 
> Thank you,
> Jeremy Bícha

I found the cause of the error: the backports version of ibus. By
restoring the affected packages to the official Debian 12 version,
everything works perfectly again.
I'll try to report it to the backports team.

Maybe this is the problem for Trixie/Sid too.

Many thanks,
Domenico Cufalo

P. S.: sorry for resending, but I forgot to reply to all.

Bug#1061258: rpm: enable read-only BerkeleyDB backend for bookworm?

2024-01-25 Thread Holger Levsen

On Thu, Jan 25, 2024 at 03:36:30PM +0200, Peter Pentchev wrote:
> FWIW, I just filed #1061487 with the proposed stable update.

awesome. and fwiw, the attached patch there looks sensible to me! ;)



-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Very hard to relate to those who think the first three years of the pandemic
were bad because they couldn’t go to bars for a while, as opposed to because
25 million people died, 400 million were disabled, and many more continue to
be unable to access public space.


signature.asc
Description: PGP signature

Bug#1061494: create a prosody-config package that will configure prosody with good xmpp compliance by default with debconf

2024-01-25 Thread Martin

Hi Praveen,

IMHO, that's a good idea!

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.

Using debconf sounds good to me, too.

What do other people (in the XMPP team or outside) think about it?

Cheers

Bug#1061518: (no subject)

2024-01-25 Thread other

Package: general
Severity: serious
X-Debbugs-Cc: a...@a.com, h...@test.com

Bug#1061517: shgfpuahgañsfgn

2024-01-25 Thread other

Package: asasasasasa
Severity: serious
X-Debbugs-Cc: a...@a.com, h...@test.com




-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
PT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1061516: Please add a sshd@.service template for socket activation

2024-01-25 Thread Marco d'Itri

Package: openssh-server
Version: 1:9.6p1-3
Severity: normal
Control: affects -1 systemd

The next release of systemd will contain support to connect to the 
system with SSH over an AF_VSOCK socket:
https://github.com/systemd/systemd/pull/30777/files

The server side of this uses what Ubuntu currently ships as 
ssh@.service, i.e. a template for socket activation of per-connection 
sshd daemons.

systemd currently expects the template to be named sshd@.service 
(because that is what Fedora uses), but if you prefer to keep the 
ssh@.service name then I suppose that we could patch systemd as well.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1061515: transition: ace

2024-01-25 Thread Sudip Mukherjee

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: sudipm.mukher...@gmail.com
Control: affects -1 + src:ace


Hi,

Small transition with only two affected packages: diagnostics, ivtools,
Both of them builds fine with ace 7.1.3+dfsg-1 in experimental.

The autogenerated ben tracker looks good. Please consider 'ace' for
transition.
Thanks in advance.


-- 
Regards
Sudip

Bug#897131: notify-osd: totally black bubble, unable to read any messages

2024-01-25 Thread Costin Chirvasuta

Works well when running a compositor:
sudo apt install compton
compton --backend glx --paint-on-overlay

Bug#1061514: php-zeta-console-tools: FTBFS with php 8.3

2024-01-25 Thread Athos Ribeiro

Source: php-zeta-console-tools
Version: 1.7.3-1
Severity: normal
Tags: patch
X-Debbugs-Cc: athos.ribe...@canonical.com

Dear Maintainer,

The package currently FTBFS with PHP 8.3 (in experimental).

This happens because, when incrementing booleans (which is a noop in
PHP8 < 8.4), PHP 8.3 emits a E_WARNING, leading to a phpunit test
failure.

This has been reported upstream in
https://github.com/zetacomponents/ConsoleTools/pull/25

I am also attaching a patch which should fix this.
Description: Do not increment boolean variables
 Before php8.3, incrementing/decrementing boolean variables have no effect. In
 php8.3, an E_WARNING is emitted to let users know about the lack of effect of
 the operation, which may cause test suite failures. Starting in php8.4, those
 operations will have a new effect over the variable. Let's avoid these output
 changes by not performing inc/dec operations over booleans. For further
 reference, please see https://wiki.php.net/rfc/saner-inc-dec-operators.
Author: Athos Ribeiro 
Forwarded: https://github.com/zetacomponents/ConsoleTools/pull/25
Last-Update: 2024-01-25
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/input/help_generators/standard.php
+++ b/src/input/help_generators/standard.php
@@ -318,7 +318,7 @@
 $synopsis = '';
 
 // Break after a nesting level of 2
-if ( $depth++ > 2 || ( in_array( $option->short, $usedOptions['short'] 
) && in_array( $option->long, $usedOptions['long'] ) ) ) return $synopsis;
+if ( (!is_bool($depth) && $depth++ > 2) || ( in_array( $option->short, 
$usedOptions['short'] ) && in_array( $option->long, $usedOptions['long'] ) ) ) 
return $synopsis;
 
 $usedOptions['short'][] = $option->short;
 $usedOptions['long'][]  = $option->long;

Bug#1017026: ITP: gnome-kiosk -- mutter based compositor for kiosks

Control: tags -1 +pending

On Thu, Jan 25, 2024 at 10:35 AM Mohammed Sadiq  wrote:
> On 2024-01-25 19:58, Jeremy Bícha wrote:
> > Please add a Lintian override for this one. There was a LIntian
> > override before you split the package:
> > W: gnome-kiosk-search-appliance: desktop-command-not-in-package
> > usr/bin/firefox
> > [usr/share/applications/org.gnome.Kiosk.SearchApp.desktop]
> I don't see this lintian warning. Can you check if it still shows up?

Yes, it is still there. I am using lintian 2.116.3. Is it possible
that you have not run  git add
debian/gnome-kiosk-search-appliance.lintian-overrides ?

But this is minor. I pushed a minor commit and then uploaded your
package to Experimental NEW now.

What do you think about lowering the Recommends to Suggests? If we use
Suggests, please add Enhances: gnome-kiosk to each package.

Thank you very much for finishing this packaging!

Jeremy Bícha

Bug#1061513: RFP: xwayland-run -- xwayland-run contains a set of small utilities revolving around running Xwayland

2024-01-25 Thread Matthias Geiger

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: werdah...@riseup.net, debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: xwayland-run
  Version : 0.0.2
  Upstream Contact: Oliver Fourdan
* URL : https://gitlab.freedesktop.org/ofourdan/xwayland-run
* License : MIT
  Programming Lang: Python
  Description : xwayland-run contains a set of small utilities revolving 
around running Xwayland

The source package contains the following utilities:

xwayland-run, to spawn an X11 client within its own dedicated Xwayland rootful 
instance,
wlheadless-run to run a Wayland client on a set of supported Wayland  headless 
compositors,
and xwfb-run, a combination of the two other tools above to be used as a direct 
replacement for xvfb-run specifically.

CC'ing d-devel because I believe some packages would need this
functionality.

best,

werdahias



-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmWytJIVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR11E8P/3DzGpDKBe2mrlknYb8qwmu6fcpL
HaOGXjdwFP1y7yPFE0cPkETHPPbqpVUqka+xvJb+iuEDm7Fsnu9J6Lq0+HbVNMiA
5YkBSscTgFjzFLQODaVLGd5SHhmfriU0t/Av9gxtn+eC7gF6t1z9RnvAZG3+F7nm
Paw69o18UTKmrHYDdLns1idp3KJImqxZg2gWhGvOS4ea5/LexDXDOM5wSUWbi1SU
ubJxZ2/n7Qu5dhJjM3n6DFtsS9BKrNxqQSpCTPXyxDMaxkIS+EqU4X1qxzjGF+xg
BbYyG6nlLypzKHRwYcKzO4gNuuS54fVBhz/2TDpAQYnu9fyBAU6OKzFXShCNwgjJ
tZMFuZYQuWTjR7K93Owfsw29u0tGRPxHrN0sxoTI06msFnUK6VIwxEs8U0JrfVWL
/xCX+GbMxz3Vhl/5a+3Dlm5FaobGnVDGlNs3fPWhqbc2yzDcvH5TUofiu8gMRQJG
uU3MF882TnJ91yc0UtB/3f5Fh680hH+/YMxbNE0U2+1soq8lviyBxBnk5Jqhmn1D
jKpQ1M/vDlJuKbFC9VGqakkR07PtaCcGf4sG8m2j1Zb8E7MKiYNs2tYIW2i07ZCp
F6SLCkIrQIN08LRKHNhm8Nd8RlwON/rgFondRhkU1mKR7Qknp9J07boi+0chRYL7
Ozl4x3UNZUaG0kYx
=t+az
-END PGP SIGNATURE-

Bug#1061512: 4

2024-01-25 Thread other

Package: general
Severity: important
X-Debbugs-Cc: h...@test.com

Bug#1054214: gnome: caps-lock for upper case accented letters does not work anymore

On Thu, Jan 25, 2024 at 1:40 PM  wrote:
> Il giorno gio, 25/01/2024 alle 13.17 -0500, Jeremy Bícha ha scritto:
> >
> > Hmm, I was unable to duplicate this issue with Debian 12 (which uses
> > GNOME 43), but I was able to duplicate it with Debian Testing.
> >
>
> I'm sorry, but could you please suggest me a way to fix this problem on
> my Debian 12 too? Or, at least, to identify the cause?
>
> In over twenty years, something like this had never happened to me.
>
> It's really annoying not being able to write those characters: AEIOU
> àèéìòù (all with active caps-lock).

Perhaps the same patch from Mutter 45 would apply to Mutter 43. If so,
this bug could be fixed for Debian 12.  It's a bit easier if the
problem can be reproduced on a developer's computer though.

Thank you,
Jeremy Bícha

Bug#1054214: gnome: caps-lock for upper case accented letters does not work anymore

2024-01-25 Thread cufalo

Il giorno gio, 25/01/2024 alle 13.17 -0500, Jeremy Bícha ha scritto:
> 
> Hmm, I was unable to duplicate this issue with Debian 12 (which uses
> GNOME 43), but I was able to duplicate it with Debian Testing.
> 

I'm sorry, but could you please suggest me a way to fix this problem on
my Debian 12 too? Or, at least, to identify the cause?

In over twenty years, something like this had never happened to me.

It's really annoying not being able to write those characters: AEIOU
àèéìòù (all with active caps-lock).

Many thanks in advance,
Domenico

Bug#1061511: gedit-source-code-browser-plugin: Upstream unmaintained for over a decade

2024-01-25 Thread Kip Warner

Package: gedit-source-code-browser-plugin
Version: 3.0.3-6
Severity: important
Tags: upstream
X-Debbugs-Cc: k...@thevertigo.com

Dear Maintainer,

Thank you for continuing to maintain the Debian gedit-source-code-
browser-plugin:

As you may be aware there has been no activity in more than a decade
upstream. Bit rot is making the plugin no longer usable with recent
versions of GEdit.

There is a fork that is maintained by ildar below:

   https://github.com/ildar/gedit-source-code-browser

Unfortunately I am advised by the maintainer that it too is currently
no longer compatible with the latest GEdit. 

   
https://github.com/MicahCarrick/gedit-source-code-browser/issues/40#issuecomment-1909725836

I have asked ildar if he intends to continue maintaining it. If he
does, then you you might want to consider switching from the old
upstream to ildar's release.

-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-proposed'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-14-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gedit-source-code-browser-plugin depends on:
ii  dconf-gsettings-backend [gsettings-backend]   0.40.0-4
ii  gedit 44.2-1
ii  python3   3.11.4-5
ii  universal-ctags [ctags]   5.9.20210829.0-1
ii  xfconf-gsettings-backend [gsettings-backend]  4.16.0-2vanir1~21.04

gedit-source-code-browser-plugin recommends no packages.

gedit-source-code-browser-plugin suggests no packages.

-- no debconf information

-- 
Kip Warner
OpenPGP signed/encrypted mail preferred
https://www.thevertigo.com


signature.asc
Description: This is a digitally signed message part

Bug#1061499: libgssglue: disable gsasl-dovecot-gssapi-heimdal autopkgtests on armhf, re-enable them on i386

2024-01-25 Thread Simon Josefsson

Thank you -- I am uploading a newly built package with your patch.

/Simon


signature.asc
Description: PGP signature

Bug#1054214: gnome: caps-lock for upper case accented letters does not work anymore

Control: reassign -1 src:mutter 44.8-1
Control: fixed -1 src:mutter 45.1-1
Control: affects -1 src:gnome-shell
Control: severity -1 important

On Thu, Jan 25, 2024 at 12:27 PM Domenico Cufalo  wrote:
> I'm sorry, but I would add that just recently I realized that the same problem
> is also present on Bookworm.
>
> I can write capital accented letters in Emacs or Telegram, but NOT in
> Libreoffice, not in Evolution, not in reportbug (where I write from), not in
> Gnome Text Editor, not in Geany etc.

Hmm, I was unable to duplicate this issue with Debian 12 (which uses
GNOME 43), but I was able to duplicate it with Debian Testing.

I believe the Debian Testing issue is fixed with mutter 45.1, but we
are stuck waiting for ftpmaster review before we can get that to
Debian Testing.

It's a bit surprising that the upstream issue I found was only
reported after GNOME 45 and not GNOME 44 (or GNOME 43).

https://gitlab.gnome.org/GNOME/mutter/-/commit/6fe1b3145
https://gitlab.gnome.org/GNOME/mutter/-/issues/3058

Thank you,
Jeremy Bícha

Bug#1061510: Engrampa fails to handle 7z and zip archives

2024-01-25 Thread Frank de Bruijn


Package: engrampa
Version: 1.26.1-2
Severity: Normal

Also: https://bugs.launchpad.net/ubuntu/+source/engrampa/+bug/2051014

After p7zip was replaced with 7zip, engrampa will no longer create or 
open 7z and zip archives. This is a known problem which has already been 
fixed upstream in version 1.27.


https://github.com/mate-desktop/engrampa/issues/433
https://github.com/mate-desktop/engrampa/pull/472


Using: Debian Testing 64-bit
Kernel: Linux asus 6.5.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.13-1 
(2023-11-29) x86_64 GNU/Linux

libc6: 2.37-13

Bug#1061497: msgpack-cxx: Please update to 6.1.0

2024-01-25 Thread James McCoy

On Thu, Jan 25, 2024 at 03:49:37PM +0100, Stephan Lachnit wrote:
> would it be possible to upload msgpack 6.1.0 to Debian unstable soon? It would
> be nice to have the v6 API in Ubuntu 24.04 LTS, for which the import freeze is
> on the 29th February.

Currently, this would break a number of packages.  The reverse
dependencies need to be updated to deal with both the msgpack-c /
msgpack-cxx split (which most have) and also to deal with the CMake
config renames that upstream did.

The former is tracked by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018679 and looks like
it's almost done.  I should raise the severity of the blocking issues
and double check others haven't crept in since I initially filed that.

Another round of checks is also needed to see what the impact is for the
CMake config rename.  I'll look into creating a tracking bug for that
and try to get some traction.

> I can also upload it as NMU if you want.

Please don't.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1061280: sysvinit crashes podman container on install

2024-01-25 Thread Mark Hindley

Control: tags -1 patch

On Mon, Jan 22, 2024 at 02:37:39PM -0700, Sam Hartman wrote:
> > "Mark" == Mark Hindley  writes:
> 
> Mark> Can you confirm?
> 
> I agree that should work.
> I have enough confidence and am busy enough today that I don't want to
> build just to apply the patch.

Thanks.

Mark

Bug#1054214: gnome: caps-lock for upper case accented letters does not work anymore

2024-01-25 Thread Domenico Cufalo

Package: gnome
Version: 1:43+1
Followup-For: Bug #1054214

Dear Maintainer,

I'm sorry, but I would add that just recently I realized that the same problem
is also present on Bookworm.

I can write capital accented letters in Emacs or Telegram, but NOT in
Libreoffice, not in Evolution, not in reportbug (where I write from), not in
Gnome Text Editor, not in Geany etc.

I hadn't noticed before when this problem started on Bookworm maybe because I
usually use Emacs.

Best regards,
Domenico


-- System Information:
Debian Release: 12.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome depends on:
ii  avahi-daemon 0.8-10
ii  cheese   43.0-1
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 12.0.6+nmu1~deb12u1
ii  evolution3.46.4-2
ii  evolution-plugins3.46.4-2
ii  file-roller  43.0-1
ii  gnome-calendar   43.1-2
ii  gnome-clocks 43.0-1
ii  gnome-color-manager  3.36.0-1+b1
ii  gnome-core   1:43+1
ii  gnome-maps   43.5-2~deb12u1
ii  gnome-music  42.1-1
ii  gnome-sound-recorder 43~beta-1
ii  gnome-tweaks 42~beta-4
ii  gnome-weather43.0-1
ii  gstreamer1.0-libav   1.22.0-2
ii  gstreamer1.0-plugins-ugly1.22.0-2+deb12u1
ii  libgsf-bin   1.14.50-1
ii  libproxy1-plugin-networkmanager  0.4.18-1.2
ii  libreoffice-calc 4:24.2.0~rc2-2~bpo12+1
ii  libreoffice-gnome4:24.2.0~rc2-2~bpo12+1
ii  libreoffice-impress  4:24.2.0~rc2-2~bpo12+1
ii  libreoffice-writer   4:24.2.0~rc2-2~bpo12+1
ii  network-manager-gnome1.30.0-2
ii  orca 45.2-1~bpo12+1
ii  rhythmbox3.4.6-2+b1
ii  rhythmbox-plugin-cdrecorder  3.4.6-2+b1
ii  rhythmbox-plugins3.4.6-2+b1
ii  rygel-playbin0.42.1-1
ii  rygel-tracker0.42.1-1
ii  seahorse 43.0-1
ii  shotwell 0.30.17-1+b1
ii  simple-scan  42.5-2
ii  totem-plugins43.0-2
ii  xdg-user-dirs-gtk0.11-1

Versions of packages gnome recommends:
ii  gnome-games   1:43+1
ii  gnome-initial-setup   43.2-6
ii  gnome-remote-desktop  43.3-1
ii  transmission-gtk  3.00-2.1+deb12u1

Versions of packages gnome suggests:
pn  alacarte  
pn  empathy   
pn  firefox-esr-l10n-all | firefox-l10n-all   
pn  goobox | sound-juicer 
pn  polari
pn  vinagre   
pn  webext-ublock-origin-firefox | webext-ublock-origin-chromium  

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme43-1
ii  at-spi2-core  2.50.0-1~bpo12+1
ii  baobab43.0-1
ii  dconf-cli 0.40.0-4
ii  dconf-gsettings-backend   0.40.0-4
ii  eog   43.2-1
ii  evince43.1-2+b1
ii  evolution-data-server 3.46.4-2
ii  fonts-cantarell   0.303.1-1
ii  gdm3  43.0-3
ii  gkbd-capplet  3.28.1-1
ii  glib-networking   2.74.0-4
ii  gnome-backgrounds 43.1-1
ii  gnome-bluetooth-sendto42.5-3
ii  gnome-calculator  1:43.0.1-2
ii  gnome-characters  43.1-1+deb12u1
ii  gnome-contacts43.1-1
ii  gnome-control-center  1:43.6-2~deb12u1
ii  gnome-disk-utility43.0-1
ii  gnome-font-viewer 43.0-1
ii  gnome-keyring 42.1-1+b2
ii  gnome-logs43.0-1
ii  gnome-menus   3.36.0-1.1
ii  gnome-online-accounts 3.46.0-1
ii  gnome-session 43.0-1+deb12u1
ii  gnome-settings-daemon 43.0-4
ii  gnome-shell   43.9-0+deb12u1
ii  gnome-shell-extensions43.1-1
ii  gnome-software43.5-1~deb12u1
ii  gnome-sushi   43.0-2
ii  gnome-system-monitor  42.0-2
ii  gnome-terminal3.46.8-1
ii  gnome-text-editor 43.2-1
ii  gnome-themes-extra3.28-2
ii  gnome-user-docs   43.0-2
ii  gnome-user-share  43.0-1

Bug#1061509: RFS: compton/1-3 [ITA] -- compositor for X11, based on xcompmgr

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "compton":

 * Package name : compton
   Version  : 1-3
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://github.com/chjj/compton
 * License  : Expat
 * Vcs  : https://salsa.debian.org/debian/compton
   Section  : x11

The source builds the following binary packages:

  compton - compositor for X11, based on xcompmgr

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/compton/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/c/compton/compton_1-3.dsc

Changes since the last upload:

 compton (1-3) unstable; urgency=medium
 .
   * New maintainer. (Closes: #960779)
   * Neither recommend or suggest picom. It is a fork of compton,
 so a separate product.
   * 'd/control': Move from transtional package libgl1-mesa-dev to libgl-dev.
   * 'd/control': Update 'Standards-Version' to 4.6.2, no changes required.
   * 'd/control': Remove ' Section: oldlibs'.
   * 'd/control': Remove message that compton is deprecated and to be removed
 and use the picom package instead.
 - Picom is a fork of compton, so different. Allow the user to decide which
   better suits their needs.
   * Removed 'd/watch' for now. Upstream compton redirects to picom.
   * Removed 'd/NEWS'. compton is still useful. Decision on removal can be
 taken at a later date, when it is no longer useful.

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#1060089: isc-dhcp: install dhclient into /usr/sbin, with DEP17 M18 diversions

2024-01-25 Thread Santiago Ruano Rincón

El 23/01/24 a las 10:34, Helmut Grohne escribió:
> On Tue, Jan 23, 2024 at 01:29:51AM +0100, Chris Hofstaedtler wrote:
> > Attached is an improved patch, that avoids the temporary file loss
> > that could occur in the old version. This is mostly based on work by
> > Helmut Grohne.
> 
> Thank you.
> 
> Reviewed-by: Helmut Grohne 
> 
> I could not identify issues. The begin-remove-after markup feels
> slightly inconsistent as it partially cleans up the mitigation, but
> cleaning up the part in -ddns using this simple markup is non-trivial
> and keeping those snippets a little longer shall not cause breakage, so
> while this isn't perfect, I think it's good to go as is.
> 
> I also locally built this change and performed bootstrap testing with
> debootstrap, cdebootstrap and mmebstrap (which include isc-dhcp-client
> in the larger variants).
> 
> > Please consider this version of the patch.
> 
> I second this request. I appreciate to have this resolved by the end of
> February. Preferrably, we have this change in experimental for a few
> days before transitioning to unstable to allow for more QA.
> 
> Helmut

Done. Thanks a lot to both of your for your work.


signature.asc
Description: PGP signature

Bug#1061508: Original tarball folder structure is 'picom-1' not 'compton-1'. Breaks gbp working.

Package: compton
Version: 1-2
Severity: normal

Maintainer tracking bug.

Original tarball folder structure is 'picom-1' not 'compton-1'. Breaks 'gbp' 
working due
to sha256sum etc.

Fix when have salsa maintainer/owner access after ITA complete.

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#1061507: [regression] rss-glx screensavers will not display on certain X11 windows

2024-01-25 Thread Timothy Pearson

Package: rss-glx
Version: 0.9.1-6.3+b1
Tags: patch

On certain hardware and with specific X11 windows (such as the TDE lock 
screen), the RSS-GLX hacks no longer display after upgrading to Bookworm from 
Bullseye.  This was traced to a missing glFinish() call prior to 
glXSwapBuffers(); likely the AMD GPU driver has not completed rendering prior 
to the Swap call, leading to the hack output not showing up on the target 
window.

I have attached a patch that is confirmed to fix the issue.  If desired, I can 
do an NMU to include this simple fix.  Ideally, this would also be backported 
to Bookworm, and I can handle the backport for that as well if desired.Index: rss-glx-0.9.1/src/driver.c
===
--- rss-glx-0.9.1.orig/src/driver.c
+++ rss-glx-0.9.1/src/driver.c
@@ -238,6 +238,7 @@
 
 		if (drawEnabled) {
 			hack_draw (XStuff, (double)now.tv_sec + now.tv_usec / 100.0f, frameTimeSoFar / 100.0f);
+			glFinish();
 
 			glXSwapBuffers (XStuff->display, XStuff->window);
 		}

Bug#1061478: apt: Internal Error, AutoRemover broke stuff, unmet dependencies: linux-headers-6.6.9-amd64

2024-01-25 Thread Wesley Schwengle




Hi,

TL;DR

One can currently reproduce this behavior on unstable by doing:

```
apt-get install linux-headers-6.6.9-amd64
dpkg -r --force-depends linux-image-6.6.9-amd64-unsigned
apt-get full-upgrade
```

You can fix it by either running:

```
apt-get remove linux-headers-6.6.9-amd64
# or
apt-mark auto linux-headers-6.6.9-amd64
# or but it doesn't make sense
apt --fix-broken install
```

I came across this scenario myself as well and on Reddit. This is my 
take on it.


Around the 11th, linux-image-6.6.9-amd64 was installed. And around the 
18th, linux-image-6.6.11-amd64. During the .9 install I saw similar 
things, I chose to keep everything as is. This caused me to keep running 
on the 6.6.8 kernel at the time.


I think something went wrong with the linux-headers-6.6.9-amd64 and/or 
linux-image-6.6.9-amd64 package. For instance, I didn't have the 
linux-headers-6.6.9-amd64 installed while I had 
linux-headers-6.6.8-amd64 and  linux-headers-6.6.11-amd64 installed. The 
package linux-image-6.6.9-amd64 isn't available in the repositories 
(anymore):


```
$ apt-cache policy linux-image-6.6.9-amd64
linux-image-6.6.9-amd64:
  Installed: (none)
  Candidate: (none)
  Version table:
 6.6.9-1 -1
100 /var/lib/dpkg/status
```

The dependency tree is sorta broken of 6.6.9. The headers have these 
dependencies:


```
$ apt-cache depends linux-headers-6.6.9-amd64
linux-headers-6.6.9-amd64
  Depends: linux-headers-6.6.9-common
 |Depends: linux-image-6.6.9-amd64
  Depends: linux-image-6.6.9-amd64-unsigned
  Depends: linux-kbuild-6.6.9
  Depends: gcc-13
```

Your linux-image-amd64 package depends on:
```
$ apt-cache depends linux-image-amd64
linux-image-amd64
  Depends: linux-image-6.6.13-amd64
```

So now one of your packages is broken. I think it is warrants a look 
into your /var/log/apt/history.log to try to figure out what happened to 
your linux-{image,headers}-* packages around the 11th, 18th and later on.


Cheers,
Wesley

--
Wesley Schwengle
E: wes...@schwengle.net

Bug#1061506: ITP: r-cran-yulab.utils -- GNU R supporting functions for packages maintained by 'YuLab-SMU'

2024-01-25 Thread Andreas Tille

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-yulab.utils -- GNU R supporting functions for packages 
maintained by 'YuLab-SMU'
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-yulab.utils
  Version : 0.1.3
  Upstream Author : Guangchuang Yu
* URL : https://cran.r-project.org/package=yulab.utils
* License : Artistic-2.0
  Programming Lang: GNU R
  Description : GNU R supporting functions for packages maintained by 
'YuLab-SMU'
 This GNU R package contains miscellaneous functions commonly used by
 'YuLab-SMU'.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-yulab.utils

Bug#1061505: aerc: colorize broken for text/plain with dracula or nord stylesets

2024-01-25 Thread Jonathan Dowland

Package: aerc
Version: 0.16.0-1
Severity: normal

With

  [ui]
  styleset-name=dracula
  ...
  [filters]
  text/plain=colorize

text/plain emails are not colorized. This is reproducible outside
aerc. Where ~/tmp/thomas is a text/plain mail I dumped for testing,
For STYLE={solarized, default, blue}, the following works

  AERC_STYLESET=/usr/share/aerc/stylesets/$STYLE 
/usr/libexec/aerc/filters/colorize < ~/tmp/thomas

but for STYLE={nord, dracula}, it doesn't.

The issue is that those two have e.g.

  diff_add.fg=2
  diff_del.fg=1
  quote_*.fg=6

Whereas the ones that work use HTML e.g.

  quote_*.fg=#93a1a1 # bright cyan
  quote_1.fg=#268bd2 # blue
  quote_2.fg=#cb4b16 # bright red
  quote_3.fg=#d33682 # magenta
  quote_4.fg=#6c71c4 # bright magenta

My guess is they haven't been updated with some change to aerc.

-- System Information:
Debian Release: 12.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-15-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aerc depends on:
ii  libc62.36-9+deb12u3
ii  libnotmuch5  0.37-1+b1
ii  python3  3.11.2-1+b1

Versions of packages aerc recommends:
ii  dante-client  1.4.2+dfsg-7
ii  gnupg 2.2.40-1.1
ii  w3m   0.5.3+git20230121-2

Versions of packages aerc suggests:
ii  notmuch  0.37-1+b1
pn  python3-vobject  

-- no debconf information

-- 
  Jonathan Dowland
✎   j...@dow.land
   https://jmtd.net

Bug#1061504: Actual homepage of the compton project.

Package: compton
Version: 1-2
Severity: normal

Maintainer tracking bug.

Need to validate the actual homepage of compton.

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#1054124: dh-ada-library: dh_ada_library output causes /usr/share/ada/packaging.mk:81: *** missing separator error

2024-01-25 Thread Nicolas Boulenguez

Hello.

> debhelper  13.11.4
> dh-ada-library 8.6
> gnat-1010.2.1-6

> $ dh_ada_library --export-versions
> DEB_GNAT_VERSION:=GNATMAKE 10.2.1 20210110

I failed to reproduce your issue with
 debhelper  13.11.10
 dh-ada-library 8.6
 gnat-1010.5.0-2
That is, the output is
 DEB_GNAT_VERSION:=10

Can you reproduce the issue?
Which version of the 'gnat' package is involved, if any?

Also, in which source tree/commit are you executing dh_ada_library?
One could imagine a problem while parsing debian/control.

Bug#1060508: marked as done (gamemode: Please switch Build-Depends to systemd-dev)

2024-01-25 Thread Jonathan Carter


On 2024/01/25 17:46, Simon McVittie wrote:

libdbus-dev isn't systemd or udev?


Hmm... seems like that was quite a brainfart on my part.


The request was to replace the B-D on systemd with systemd-dev, without
altering the B-D on libdbus-1-dev or libsystemd-dev.


Fixed and uploaded!

-Jonathan

Bug#1061503: tex-common failed to configure

2024-01-25 Thread richarda

Package: tex-common
Version: 6.18
Severity: normal
Tags: patch

Dear Maintainer,

This report is written via my Rasperry Pi mailserver. 
The machine that had the problem is an AMD64 machine 
running Trixie/Bookworm/Sid

The problem seems to be similar to #994264 
where after every update via apt-get dist upgrade 
the configureation of tex common failed to complete, 
with reference to a file /tmp/updmap.

Typical content was : 
/quote
updmap will read the following updmap.cfg files (in precedence order):
  /usr/share/texmf/web2c/updmap.cfg
  /usr/share/texlive/texmf-dist/web2c/updmap.cfg
updmap may write changes to the following updmap.cfg file:
  /etc/texmf/web2c/updmap.cfg
dvips output dir: "/var/lib/texmf/fonts/map/dvips/updmap"
pdftex output dir: "/var/lib/texmf/fonts/map/pdftex/updmap"
dvipdfmx output dir: "/var/lib/texmf/fonts/map/dvipdfmx/updmap"
updmap [ERROR]: The following map file(s) couldn't be found:
updmap [ERROR]: epiolmec.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: esint.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: knitfont.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: scanpages.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: xypic.map (in 
/usr/share/texlive/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: Did you run mktexlsr?

You can disable non-existent map entries using the option
  --syncwithtrees.
/unquote

the missing *.map files were nowhere to be found on the system. 

I determined that texlive-latex-extra provided the missing files. 
I installed texlive-latex-extra and during that installation process, 
tex-common was configured. 

I will add that other suggested fixes suc as dpkg-reconfigure locales
failed to solve the configuration problem. 

regards

richarda

Bug#1061422: add patch

2024-01-25 Thread Matthias Klose


Control: tags -1 + patch

https://launchpadlibrarian.net/711104605/blender_4.0.2+dfsg-1ubuntu3_4.0.2+dfsg-1ubuntu4.diff.gz

Bug#1061502: virtaal: Please drop Build-Depends python3-libproxy

Source: virtaal
Version: 0.7.1+git20191021+ds1-2
Severity: serious
Tags: ftbfs sid trixie

virtaal Build-Depends on python3-libproxy, but this dependency is not
required for the build.

libproxy 0.5 no longer provides Python 3 bindings. Because it is
expected that Debian 13 will ship with libproxy 0.5, I am dropping the
python3-libproxy package now.

Thank you,
Jeremy Bícha

Bug#960779: ITA: compton -- compositor for X11, based on xcompmgr

On Thu, 2024-01-25 at 14:09 +, Tomas Janousek wrote:
> Hi Phil,
> On Thu, Jan 25, 2024 at 12:28:56PM +, Phil Wyett wrote:
> > I am interested in 'compton' and would like to adopt it and remove a small 
> > part of the
> > QA
> > Teams workload from them.
> > […]
> > I use this package now daily as an alternative to the in built XFCE 
> > compositor, so the
> > health of this package is important to me.
> I'm wondering whether you're aware of https://tracker.debian.org/pkg/picom, 
> which is an
> actively maintained fork of compton (although, IME, with a focus on being 
> pretty rather
> than on quality and performance).
> It's more or less a drop-in replacement for compton, so it should be super 
> easy for you
> to try it out for a few days. Personally I've had all sorts of trouble with 
> it in the
> past (memory leaks, flicker, and a massive performance degradation that still 
> hasn't
> been fixed despite being reported years ago 1), so I've been using
> https://github.com/liskin/compton/tree/debian/sid, which is a somewhat random 
> snapshot
> from a time where everything I need works and nothing is broken yet.
> Just thought it'd be useful to fill you in, in case you haven't heard about 
> picom.
> Regards,
> -- 
> 
> Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/  

Hi Tomas,

Yes, I am aware of picom because it is wrongly a 'Recommends' (installed when 
you install
compton) for compton.[1]

As you have experienced, it is flaky and has some weird bugs that I myself 
started to list
and then gave up. The final straw was when it came to picom on a basic 
configuration
triggered higher CPU usage and my fan to turn on and never turn off every time 
I started
vscode. Closing vscode left the fan running, but I was not interested in 
debugging it.

In my experience also, compton 1 is an easier and more stable package in Debian 
than
picom. For this reason I have decided to adopt it as it replaces the also flaky 
in-built
compositor of xfce for me.

The package will have the deprecation/removal warning in 'd/control' removed; 
and addition
to 'oldlibs' removed. Other updates will take place to the packaging to bring 
it up to
today's Debian. This package has value and will be maintained by myself 
accordingly.

If you have any bugs with Debian's compton. Please file bugs against the 
package and I
will look at them.

[1] The 'Recommends' will be removed. These are separate X11 compositors.

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#1060508: marked as done (gamemode: Please switch Build-Depends to systemd-dev)

2024-01-25 Thread Simon McVittie

Control: reopen -1
Control: found -1 1.8.1-1

mbiebl wrote:
> your package gamemode declares a Build-Depends on systemd and/or
> udev.

jcc replied:
> I tested this locally, it seems that gamemode really does need libdbus-dev,
> so I'm closing this bug.

libdbus-dev isn't systemd or udev?

The request was to replace the B-D on systemd with systemd-dev, without
altering the B-D on libdbus-1-dev or libsystemd-dev.

Thanks,
smcv

Bug#1017026: ITP: gnome-kiosk -- mutter based compositor for kiosks

2024-01-25 Thread Mohammed Sadiq

On 2024-01-25 19:58, Jeremy Bícha wrote:

Thank you!

It can make review easier if you push new commits instead of
force-pushing.

Sorry. I was doing so since the repo was not used anywhere.
Anyway new changes are pushed as new commits.

Please forward your bin/sh patch upstream. You can then add a
Forwarded: line to Debian's copy of the patch. This does not need to
be done before I sponsor your upload.

Shall do.

Please fix the below list of LIntian errors and warnings. You can
ignore other Lintian warnings here. You can get more explanation about
the issue by running a command like

lintian-explain-tags not-binnmuable-all-depends-any

For the copyright warning, use a Comment field like
https://salsa.debian.org/gnome-team/wike/-/blob/debian/latest/debian/copyright?ref_type=heads#L18-21
It is a long line so I would use two lines but indent the second line
by a space like was done with the Copyright and License fields.

done

W: gnome-kiosk source: debhelper-but-no-misc-depends
gnome-kiosk-search-appliance
W: gnome-kiosk source: syntax-error-in-dep5-copyright Cannot parse
line 5: Copyright info was added into README here:
https://gitlab.gnome.org/GNOME/gnome-kiosk/-/commit/9cf264d
[debian/copyright]

Please add a Lintian override for this one. There was a LIntian
override before you split the package:
W: gnome-kiosk-search-appliance: desktop-command-not-in-package
usr/bin/firefox
[usr/share/applications/org.gnome.Kiosk.SearchApp.desktop]

I don't see this lintian warning. Can you check if it still shows up?

cheers,
Mohammed Sadiq

Bug#1061501: libvorbis: Please disable test-coupling-segfault autopkgtest on armhf

2024-01-25 Thread Emanuele Rocca

Source: libvorbis
Version: 1.3.7-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Tags: patch

Hi,

the autopkgtest test-coupling-segfault currently fails on armhf due to
valgrind bug https://bugs.debian.org/1061496.

Please disable the test for now, it can be re-enabled once the valgrind
issue is fixed. Patch attached.

Thanks,
  Emanuele
diff -Nru libvorbis-1.3.7/debian/changelog libvorbis-1.3.7/debian/changelog
--- libvorbis-1.3.7/debian/changelog	2020-09-27 16:13:53.0 +0200
+++ libvorbis-1.3.7/debian/changelog	2024-01-25 16:25:09.0 +0100
@@ -1,3 +1,11 @@
+libvorbis (1.3.7-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable test-coupling-segfault on armhf due to valgrind bug #1061496.
+(Closes: #XXX)
+
+ -- Emanuele Rocca   Thu, 25 Jan 2024 16:25:09 +0100
+
 libvorbis (1.3.7-1) unstable; urgency=medium
 
   * Team upload
diff -Nru libvorbis-1.3.7/debian/tests/control libvorbis-1.3.7/debian/tests/control
--- libvorbis-1.3.7/debian/tests/control	2020-09-27 16:05:13.0 +0200
+++ libvorbis-1.3.7/debian/tests/control	2024-01-25 16:24:06.0 +0100
@@ -1,2 +1,6 @@
-Depends: @, vorbis-tools, build-essential, sound-theme-freedesktop, sound-icons, valgrind
-Tests: test-examples test-coupling-segfault
+Depends: @, vorbis-tools, build-essential, sound-theme-freedesktop
+Tests: test-examples
+
+Depends: @, vorbis-tools, sound-icons, valgrind
+Tests: test-coupling-segfault
+Architecture: !armhf

Bug#1061500: libfreerdp-server2-2: Connection from windows to gnome-remote-deskopt fails with the following error: [ERROR][com.winpr.sspi.NTLM] - Message Integrity Check (MIC) verification failed!

2024-01-25 Thread Patrick Winnertz

Package: libfreerdp-server2-2
Version: 2.10.0+dfsg1-1
Severity: important
Tags: patch

Dear Maintainer,

it's currently impossible to connect to a running gnome-remote-desktop
instance due to a issue in freerdp.

there is already a patch available in upstream for that issue, which
just needs to be backported to 2.10.

https://github.com/FreeRDP/FreeRDP/commit/a23a24fe068c37d20c254fe393d4fe5d4c6ab31d

You'll find additional information within this bug report: #1040395 and
at
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/86

It would be nice if the freerdp implementation in stable could be fixed,
so that rdp is again usable in a stable environment.

With best regards
Patrick

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-15-amd64 (SMP w/6 CPU threads; PREEMPT)
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 libfreerdp-server2-2 depends on:
ii  libc6  2.36-9+deb12u3
ii  libfreerdp2-2  2.10.0+dfsg1-1
ii  libwinpr2-22.10.0+dfsg1-1

libfreerdp-server2-2 recommends no packages.

libfreerdp-server2-2 suggests no packages.

-- no debconf information


--
Dr. Patrick Winnertz
Leostraße 26
68789 St. Leon-Rot
Tel: +49 163 253 636 9

Bug#1061315: inn2 ftbfs with Python 3.12 as the default

2024-01-25 Thread Matthias Klose


Control: tags -1 + patch

On 22.01.24 21:31, Julien ÉLIE wrote:

Hi Matthias,


Package: src:inn2
Version: 2.7.2~20231223-1
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

with python3-defaults from experimental:

[...]
checking for Python.h... yes
checking for Py_Initialize... no
configure: error: in `/<>/build':
configure: error: unable to link with Python library
See `config.log' for more details


Could you put the end of the config.log file? (the part showing the 
failure to find Py_Initialize)


Maybe a problem of Python not in the path?


FWIW, I do not run trixie, but building INN with a downloaded version of 
Python 3.12 on bookworm works for me:


checking for flags to link with Python... -L/home/news/work/py3.12.1/lib 
-lpython3.12 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic

checking Python.h usability... yes
checking Python.h presence... yes
checking for Python.h... yes
checking for Py_Initialize... yes


configure:15028: checking for Py_Initialize
configure:15028: gcc -o conftest -g -O2 
-I/home/news/work/py3.12.1/include/python3.12   conftest.c 
-L/home/news/work/py3.12.1/lib -lpython3.12 -lpthread -ldl -lutil -lm 
-Xlinker -export-dynamic   >&5


configure:15777: checking for Py_Initialize
configure:15777: gcc -o conftest -g -O2 -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer -ff
ile-prefix-map=/home/packages/tmp/inn2-2.7.2~20231223=. -flto=auto 
-ffat-lto-objects -fstack-pro
tector-strong -fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -fdebug-
prefix-map=/home/packages/tmp/inn2-2.7.2~20231223=/usr/src/inn2-2.7.2~20231223-1build2 
-I/usr/in
clude/python3.12 -Wdate-time -D_FORTIFY_SOURCE=3 
-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-o
bjects -Wl,-z,relro -Wl,-z,now conftest.c -L/usr/lib/x86_64-linux-gnu 
-lpython3.12 -ldl -lm -lm
-lm -lz -lm -lm -lexpat -lexpat Modules/_hacl/libHacl_Hash_SHA2.a -lz 
-Xlinker -export-dynamic -
Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -g -fwrapv -O2 
 >&5
/usr/bin/ld: cannot find Modules/_hacl/libHacl_Hash_SHA2.a: No such file 
or directory

collect2: error: ld returned 1 exit status
configure:15777: $? = 1


looking at m4/python.m4, this comes from getting the configuration out 
of the sysconfig module.


and _sysconfigdata_* has:

 'LOCALMODLIBS': '-lm  -lm   -lz -lm -lm   -lexpat  -lexpat '
 'Modules/_hacl/libHacl_Hash_SHA2.a -lz',


So, I'm not sure, how to better get the required information for 
linking, but this interface doesn't look very reliable.


maybe better use: python3-config --embed --libs

patch attached.

diff -Nru inn2-2.7.2~20231223/debian/changelog inn2-2.7.2~20231223/debian/changelog
--- inn2-2.7.2~20231223/debian/changelog	2024-01-19 20:41:48.0 +0100
+++ inn2-2.7.2~20231223/debian/changelog	2024-01-25 16:06:27.0 +0100
@@ -1,3 +1,9 @@
+inn2 (2.7.2~20231223-1ubuntu1) noble; urgency=medium
+
+  * Fix configury with Python 3.12.
+
+ -- Matthias Klose   Thu, 25 Jan 2024 16:06:27 +0100
+
 inn2 (2.7.2~20231223-1build2) noble; urgency=medium
 
   * No-change rebuild with Python 3.12 as default
diff -Nru inn2-2.7.2~20231223/debian/patches/python3.12.diff inn2-2.7.2~20231223/debian/patches/python3.12.diff
--- inn2-2.7.2~20231223/debian/patches/python3.12.diff	1970-01-01 01:00:00.0 +0100
+++ inn2-2.7.2~20231223/debian/patches/python3.12.diff	2024-01-25 16:06:27.0 +0100
@@ -0,0 +1,23 @@
+--- a/m4/python.m4
 b/m4/python.m4
+@@ -130,10 +130,7 @@ AC_DEFUN([INN_LIB_PYTHON],
+ print(" -L".join(sysconfig.get_config_vars("LIBDIR")))'`
+  py_ldlibrary=`$PYTHON -c 'import sysconfig; \
+ print(sysconfig.get_config_vars("LDLIBRARY")@<:@0@:>@)'`
+- py_linkage=`$PYTHON -c 'import sysconfig; \
+-print(" ".join(sysconfig.get_config_vars(  \
+-"LIBS", "LIBC", "LIBM", "LOCALMODLIBS", "BASEMODLIBS", \
+-"LINKFORSHARED", "LDFLAGS")))'`],
++ py_linkage=`${PYTHON}-config --embed --libs`],
+ [py_include=`$PYTHON -c 'import distutils.sysconfig; \
+ print(distutils.sysconfig.get_python_inc())'`
+  py_libdir=`$PYTHON -c 'import distutils.sysconfig; \
+@@ -142,7 +139,7 @@ AC_DEFUN([INN_LIB_PYTHON],
+ print(distutils.sysconfig.get_config_vars("LDLIBRARY")@<:@0@:>@)'`
+  py_linkage=`$PYTHON -c 'import distutils.sysconfig;   \
+ print(" ".join(distutils.sysconfig.get_config_vars(\
+-"LIBS", "LIBC", "LIBM", "LOCALMODLIBS", "BASEMODLIBS", \
++"LIBS", "LIBC", "LIBM", "MODLIBS", "BASEMODLIBS", \
+ "LINKFORSHARED", "LDFLAGS")))'`])
+  PYTHON_CPPFLAGS="-I$py_include"
+  py_libpython=`AS_ECHO(["$py_ldlibrary"]) \
diff -Nru inn2-2.7.2~20231223/debian/patches/series inn2-2.7.2~20231223/debian/patches/series
--- inn2-2.7.2~20231223/debian/patches/series	2023-09-06 21:47:32.0 +0200
+++

Bug#1061499: libgssglue: disable gsasl-dovecot-gssapi-heimdal autopkgtests on armhf, re-enable them on i386

2024-01-25 Thread Emanuele Rocca

Source: libgssglue
Version: 0.8-2
Severity: serious
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Tags: patch

Dear Maintainer,

Two of the libgssglue valgrind autopkgtests, namely
gsasl-dovecot-gssapi-heimdal and gsasl-dovecot-gssapi-heimdal-root,
currently fail on armhf due to valgrind bug
https://bugs.debian.org/1061496:

 libgssglue   PASS
 bad-configs  PASS
 bad-configs-root PASS
 gsasl-dovecot-gssapi PASS
 gsasl-dovecot-gssapi-heimdal FAIL non-zero exit status 1
 gsasl-dovecot-gssapi-heimdal-root FAIL non-zero exit status 1

Please consider disabling them.

On the other hand, all tests can be re-enabled on i386 now that #1057693
has been taken care of.

Patch attached.

Thanks,
  Emanuele
diff -Nru libgssglue-0.8/debian/changelog libgssglue-0.8/debian/changelog
--- libgssglue-0.8/debian/changelog	2023-12-07 09:17:26.0 +0100
+++ libgssglue-0.8/debian/changelog	2024-01-25 12:29:55.0 +0100
@@ -1,3 +1,12 @@
+libgssglue (0.8-2.1) UNRELEASED; urgency=medium
+
+  * Disable autopkgtests gsasl-dovecot-gssapi-heimdal and
+gsasl-dovecot-gssapi-heimdal-root on armhf due to valgrind
+bug #1061496.
+  * Re-enable valgrind on i386 now that #1057693 is fixed.
+
+ -- Emanuele Rocca   Thu, 25 Jan 2024 12:29:55 +0100
+
 libgssglue (0.8-2) unstable; urgency=medium
 
   * Disable valgrind in i386 due to #1057693.
diff -Nru libgssglue-0.8/debian/tests/control libgssglue-0.8/debian/tests/control
--- libgssglue-0.8/debian/tests/control	2023-12-07 08:40:56.0 +0100
+++ libgssglue-0.8/debian/tests/control	2024-01-25 12:29:55.0 +0100
@@ -10,13 +10,13 @@
 Restrictions: allow-stderr, needs-root
 
 Tests: gsasl-dovecot-gssapi
-Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!i386]
+Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available
 Restrictions: allow-stderr
 
 Tests: gsasl-dovecot-gssapi-heimdal
-Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!i386], libgssapi3-heimdal
+Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!armhf], libgssapi3-heimdal
 Restrictions: allow-stderr
 
 Tests: gsasl-dovecot-gssapi-heimdal-root
-Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!i386], libgssapi3-heimdal
+Depends: gsasl, dovecot-imapd, dovecot-gssapi, krb5-kdc, krb5-admin-server, valgrind-if-available [!armhf], libgssapi3-heimdal
 Restrictions: allow-stderr needs-root

Bug#1061498: newt: Please do not remove colour palettes

2024-01-25 Thread Vincent Blut

Package: newt
Version: 0.52.24-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Alastair,

Newt's colour palettes added into /etc/newt/ are going to end up removed
when upgrading or installing whiptail from Config-Files state due to the
following one-liner in the libnewt0.52.preinst file:

rm -f /etc/newt/palette*

This is quite harsh. Could you please drop it so that one can easily use a
system-wide palette?

Cheers,
Vincent

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQSRJQjHKbAUfuoc+DAQn1qAt/bgAQUCZbJ3ZgAKCRAQn1qAt/bg
AcYJAQDc83xNWal7cv/9IIkDCGWfjopIU4np43y0zUSLmD9NMAEAk0GiEVQ3G9DJ
9006w0xauvywUpfjNEhWP68TJUJ2Zw4=
=Ns0h
-END PGP SIGNATURE-

Bug#1061497: msgpack-cxx: Please update to 6.1.0

2024-01-25 Thread Stephan Lachnit

Package: msgpack-cxx
Severity: wishlist
X-Debbugs-Cc: james...@debian.org, stephanlach...@debian.org

Hi,

would it be possible to upload msgpack 6.1.0 to Debian unstable soon? It would
be nice to have the v6 API in Ubuntu 24.04 LTS, for which the import freeze is
on the 29th February. I can also upload it as NMU if you want.

Cheers,
Stephan


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1061496: valgrind: Segmentation fault on armhf checking programs built with -fstack-clash-protection or -fstack-check

2024-01-25 Thread Emanuele Rocca

Package: valgrind
Version: 1:3.20.0-2.1
Severity: important
User: debian-...@lists.debian.org
Usertags: 32bit-stackclash
Tags: upstream

On armhf, valgrind dies with a SIGSEGV when checking certain programs
built with either -fstack-clash-protection or -fstack-check.

The following example is a reproducer:

  // example.c
  void a_function() { char buf[8192]; }
  int main() { a_function(); }

The issue can be reproduced with:

  $ gcc -fstack-clash-protection example.c -o example && valgrind ./example
  ==2743356== Memcheck, a memory error detector
  ==2743356== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
  ==2743356== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
  ==2743356== Command: ./example
  ==2743356== 
  ==2743356== 
  ==2743356== Process terminating with default action of signal 11 (SIGSEGV)
  ==2743356==  Access not within mapped region at address 0xFEF0CB04
  ==2743356==at 0x1084EA: a_function (in /tmp/example)
  ==2743356==  If you believe this happened as a result of a stack
  ==2743356==  overflow in your program's main thread (unlikely but
  ==2743356==  possible), you can try to increase the size of the
  ==2743356==  main thread stack using the --main-stacksize= flag.
  ==2743356==  The main thread stack size used in this run was 8388608.
  ==2743356== 
  ==2743356== HEAP SUMMARY:
  ==2743356== in use at exit: 0 bytes in 0 blocks
  ==2743356==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
  ==2743356== 
  ==2743356== All heap blocks were freed -- no leaks are possible
  ==2743356== 
  ==2743356== For lists of detected and suppressed errors, rerun with: -s
  ==2743356== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 3)
  Segmentation fault

Bug#1061485: 7zip: The 7zip-standalone package isn't standalone

2024-01-25 Thread yokota

Hello,

> currently, the 7zip-standalone package has a hard dependency on the
> full-featured 7zip package, rendering it quite useless as a "light"
> standalone package.

This hard dependency is because 7zz requires SFX stub module
(/usr/lib/7zip/7zCon.sfx) for SFX archive creation.

I will re-consider this issue because SFX is not required in most usage.

--
YOKOTA Hiroshi

Bug#1061495: firefox: Firefox 122: webrtc broken (camera and screenshare can be seen locally but not on the other end)

2024-01-25 Thread Daniele Gobbetti

Package: firefox
Version: 122.0-1
Severity: important
X-Debbugs-Cc: daniele-...@gobbetti.name

Dear Maintainer,

as I updated to firefox 122 I could see that sending video in videoconferences 
does not work anymore.

The local sound can be heard on the other side of the connection, but the video 
stream is simply not visible,
this is true both for webcam as for screen sharing.
The local browser window shows everything correctly.

I could reproduce the issue also using janus "echo test" on their website 
( https://janus.conf.meetecho.com/demos/echotest.html ) and by starting firefox 
in "safe mode".
Additionally I tried changing the libavcodec60 package and installing the 
-extra version, to no avail.

I tried firefox 122 from mozilla ( from their tar.bzip2, not from their deb 
repository ) and it works.
Debian's packaged Firefox 121 wasn't affected by this problem.

Best Regards,
Daniele Gobbetti




-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils  5.16
ii  fontconfig   2.14.2-6+b1
ii  libasound2   1.2.10-3
ii  libatk1.0-0  2.50.0-1+b1
ii  libc62.37-14
ii  libcairo-gobject21.18.0-1+b1
ii  libcairo21.18.0-1+b1
ii  libdbus-1-3  1.14.10-4
ii  libevent-2.1-7   2.1.12-stable-8
ii  libffi8  3.4.4-2
ii  libfontconfig1   2.14.2-6+b1
ii  libfreetype6 2.13.2+dfsg-1+b1
ii  libgcc-s113.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3
ii  libglib2.0-0 2.78.3-2
ii  libgtk-3-0   3.24.40-2
ii  libnspr4 2:4.35-1.1
ii  libnss3  2:3.96.1-1
ii  libpango-1.0-0   1.51.0+ds-4
ii  libstdc++6   13.2.0-10
ii  libvpx8  1.13.1-2
ii  libx11-6 2:1.8.7-1
ii  libx11-xcb1  2:1.8.7-1
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  procps   2:4.0.4-2+b1
ii  zlib1g   1:1.3.dfsg-3+b1

Versions of packages firefox recommends:
ii  libavcodec-extra60 [libavcodec60]  7:6.1.1-1

Versions of packages firefox suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-11
ii  libgssapi-krb5-2   1.20.1-5
pn  pulseaudio 

-- no debconf information

Bug#1017026: ITP: gnome-kiosk -- mutter based compositor for kiosks