Bug#1055441: ITP: golang-golang-x-telemetry -- Go Telemetry services and libraries

[Anthony Fok]

Package: wnpp
Severity: wishlist
Owner: Anthony Fok 

* Package name: golang-golang-x-telemetry
  Version : 0.0~git20231030.36630a2-1
  Upstream Author : The Go Authors
* URL : https://github.com/golang/telemetry
* License : BSD-3-Clause
  Programming Lang: Go
  Description : Go Telemetry services and libraries

 This package from the https://go.googlesource.com/telemetry repository 
 holds the Go Telemetry server code and libraries.

Reason for packaging: Needed by gopls (golang-golang-x-tools)

Bug#1033899: pipewire: Pipewire fails to sart, "Main process exited, code=killed, satus=31/SYS".

[Itai]

Got to looking at it again, and realized for some reason I had
pipewire-bin:i386 installed instead of the 64-bit version. After running
`sudo apt install pipewire-bin` and restarting - sound works again.
I have no idea how the i386 version came to be installed, or why the errors
were so cryptic.

On Sun, Jul 2, 2023 at 6:15 PM Itai  wrote:

> Thank you for the reply, attached is the output (log file).
>
>
> On Sat, Jul 1, 2023 at 11:17 PM Dylan Aïssi  wrote:
>
>> Le lun. 3 avr. 2023 à 18:54, Itai Shaked  a écrit :
>> >
>> > I am at a loss since there seems to be zero usable information in the
>> logs,
>> > just that the service is killed for some (unspecified?) reason.
>> >
>>
>> Can you manually start pipewire with an increased verbose level?
>> The following command should give us more details [1]:
>>
>> PIPEWIRE_LOG_SYSTEMD=false PIPEWIRE_DEBUG=5 pipewire 2>log
>>
>>
>> Dylan
>>
>> [1]
>> https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#pipewire-debugging-options
>>
>

Bug#1055440: libsfml-dev: Requesting libsfml-dev be upgraded to the latest release v2.6.1

[Chris Thrasher]

Package: libsfml-dev
Version: 2.5.1+dfsg-2
Severity: wishlist

Dear Maintainer,

My name is Chris Thrasher and I help maintain SFML. I'm requesting libsfml-dev 
be upgraded to the latest release of SFML, version 2.6.1. It was just released 
a few days ago and includes 5+ years worth of improvements to SFML since 2.5.1 
was released in 2018.

Thanks,

Chris

Bug#1054437: golang-ariga-atlas: website is build with Docusaurus not packaged for debian

[Cyril Brulebois]

Hi Bastien,

Bastien Roucariès  (2023-10-23):
> Source:  golang-ariga-atlas
> Version: 0.7.2-2
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS

This doesn't make any sense.

> Control: block -1 by 1054426
> 
> Dear Maintainer,
> 
> The documentation is build with docusaurus.
> 
> See website directory
> https://sources.debian.org/src/golang-ariga-atlas/0.7.2-2/doc/website/
> 
> You should repack or package docusaurus and rebuild

You're filing a serious bug report claiming this is about a failure to
build from source, then mention repacking, without describing any actual
issues.

Please be more considerate when filing serious bug reports.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Bug#1054438: golang-entgo-ent: website is build with Docusaurus not packaged for debian

[Cyril Brulebois]

Bastien Roucariès  (2023-10-23):
> Source:  golang-entgo-ent
> Version: 0.11.3-4
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS
> Control: block -1 by 1054426
> 
> Dear Maintainer,
> 
> The documentation is build with docusaurus.
> 
> See website directory
> https://sources.debian.org/data/main/g/golang-entgo-ent/0.11.3-4/doc/website
> 
> You should repack or package docusaurus and rebuild

That's bug report number 3 without any details…

-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Bug#1023047: wsjtx: No transmit audio

[tony mancill]

On Fri, Oct 13, 2023 at 08:57:38PM +0100, Christoph Berg wrote:
> Re: erebion
> > According to Pavucontrol there is no audio, as wsjtx does not show up. That
> > is while transmitting, haven't tried to receive last time as I did not have
> > the required cable with me.
> > 
> > I think input was broken as well, but to be sure I'd need to have another
> > look.
> 
> You don't need the radio connected, you can also let wsjtx record
> audio from the local mic and check if the ambient noise shows up on
> the waterfall. (Same for TX and local speaker of course.)
> 
> If wsjtx doesn't show up, I don't really know where to look further.
> (Frustratingly, I have the same issue atm with wfview. I currently
> blame pipewire, but I think it did work before.)

I'm not claiming that this thread from the wsjt-devel [1] list is
related, but perhaps it's a helpful hint?  (I still can't reproduce
the issue.)

[1] https://sourceforge.net/p/wsjt/mailman/message/51780237/

Bug#922021: Bug still present in Apt 1.4.10

[Christoph Franzen]

Hello,

I'm observing the same on Bullseye 11.6. This is an old i386
installation upgraded all the way from Etch 4.0 r3, but no complete
dist-upgrade.

Apt is version 1.4.10 from Stretch.

If I move those problematic symlinks out of the way, they are
re-created.

The bug breaks other things relying on "apt update" exiting without any
error (i.e. "pihole -up" here).

Christoph Franzen


pgpCZXqZ1YMtk.pgp
Description: Digitale Signatur von OpenPGP

Bug#1055439: RM: golang-github-docker-go-plugins-helpers [all] -- RoQA; NBS; renamed to golang-github-docker-go-plugins-helpers-dev

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

The badly named arch:all binary package has been renamed.

Andreas

Bug#1055438: kea: init-scripts not working

[Stefan Klein]

Package: kea-dhcp4-server
Version: 2.2.0-6
Severity: normal
File: kea
Tags: patch

Dear Maintainers,

thank you for your work to make Kea available on Debian.

I appreciate that you include init scripts and support init diversity.

Unfortunately those script don't work as expected. I fixed them and made
them mimic the behaviour of the Systemd service files as closely as
possible.

It would be nice if you could apply the attached patch to:

- set PIDFILE to the path used by Kea
- create the pid-directory if doesn't exist
- make the lock-directory match the one used in the Systemd service
- remove KEA_LOGGER_DESTINATION as it has no effect without an export
  and is not set in the service file either
- use start-stop-stop-daemon's exec parameter instead of name (as they
  exceed the 15 chars limit)
- run the daemons as non-root (default is _kea)
- make that user owner of the pid and lock directories
- give Kea access to raw sockets and privileged ports via setcap (this
  is not as nice as AmbientCapabilities in Systemd, but at least is
  what Kea's docs suggest)

Thank you in advance,
Stefan

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

Kernel: Linux 6.1.0-12-cloud-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages kea-dhcp4-server depends on:
ii  init-system-helpers  1.65.2
ii  kea-common   2.2.0-6
ii  libc62.36-9+deb12u1
ii  libgcc-s112.2.0-14
ii  libstdc++6   12.2.0-14

kea-dhcp4-server recommends no packages.

Versions of packages kea-dhcp4-server suggests:
pn  kea-doc  

-- Configuration Files:
/etc/init.d/kea-dhcp4-server changed [not included]
/etc/kea/kea-dhcp4.conf changed [not included]

-- no debconf information
diff --git a/debian/kea-ctrl-agent.init b/debian/kea-ctrl-agent.init
index 0dc99dd..3d1d5fa 100644
--- a/debian/kea-ctrl-agent.init
+++ b/debian/kea-ctrl-agent.init
@@ -6,9 +6,9 @@
 # Default-Start: 2 3 4 5
 # Default-Stop:  0 1 6
 # Short-Description: Kea DHCP Control Agent for REST Service
-# Description:   
-#<...>
-#<...>
+# Description:   Kea is an IPv4 and IPv6 DHCP server developed by Internet
+#Systems Consortium providing a very high-performance with
+#PostgreSQL, MySQL and memfile backends.
 ### END INIT INFO
 # Author: Jason Guy 
 # Do NOT "set -e"
@@ -19,11 +19,11 @@ DESC=kea-ctrl-agent
 NAME=kea-ctrl-agent
 DAEMON=/usr/sbin/kea-ctrl-agent
 DAEMON_ARGS="-c /etc/kea/kea-ctrl-agent.conf"
-PIDFILE=/run/$NAME.pid
+DAEMONUSER=_kea
+PIDFILE=/run/kea/kea-ctrl-agent.kea-ctrl-agent.pid
 SCRIPTNAME=/etc/init.d/$NAME
-KEA_PIDFILE_DIR=/run/
-KEA_LOCKFILE_DIR=/run/lock/kea/
-KEA_LOGGER_DESTINATION=/var/log/kea/
+KEA_PIDFILE_DIR=/run/kea
+KEA_LOCKFILE_DIR=/run/lock/kea
 
 # Exit if the package is not installed
 [ -x "$DAEMON" ] || exit 0
@@ -43,6 +43,15 @@ create_lockfile_dir()
 {
if [ ! -d "$KEA_LOCKFILE_DIR" ]; then
mkdir -m 0750 -p "$KEA_LOCKFILE_DIR"
+   chown "$DAEMONUSER:" "$KEA_LOCKFILE_DIR"
+   fi
+}
+
+create_pidfile_dir()
+{
+   if [ ! -d "$KEA_PIDFILE_DIR" ]; then
+   mkdir -m 0750 -p "$KEA_PIDFILE_DIR"
+   chown "$DAEMONUSER:" "$KEA_PIDFILE_DIR"
fi
 }
 
@@ -52,13 +61,15 @@ create_lockfile_dir()
 do_start()
 {
create_lockfile_dir
+   create_pidfile_dir
+   export KEA_LOCKFILE_DIR
# Return
#   0 if daemon has been started
#   1 if daemon was already running
#   2 if daemon could not be started
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON 
--test > /dev/null \
|| return 1
-   start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -b 
-- \
+   start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -b 
-c $DAEMONUSER -- \
$DAEMON_ARGS \
|| return 2
 }
@@ -73,7 +84,7 @@ do_stop()
#   1 if daemon was already stopped
#   2 if daemon could not be stopped
#   other if a failure occurred
-   start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile 
$PIDFILE --name $NAME
+   start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile 
$PIDFILE --exec $DAEMON --user $DAEMONUSER
RETVAL="$?"
[ "$RETVAL" = 2 ] && return 2
# Wait for children to finish too if this is a daemon that forks
@@ -82,7 +93,7 @@ do_stop()
# that waits for the process to drop all resources that could be
# needed by services started subsequently.  A last resort is to
# sleep for some time.
-   start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec 
$DAEMON
+  

Bug#1055437: gobject-introspection: Please provide a build profile to avoid build-dep loops through cairo

[Samuel Thibault]

Package: gobject-introspection
Version: 1.78.1-1
Severity: normal

Hello,

gobject-introspection currently build-depends on cairo, but various
build-dependencies of cairo build-depend on gobject-introspection, thus
creating various loops that makes bootstraping new Debian ports tricky.

It is however easy for gobject-introspection to break these loops by
making the cairo build-dependency optional and make gir1.2-freedesktop
not provide gir1.2-cairo-1.0.

Thanks,
Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 gobject-introspection depends on:
ii  build-essential 12.10
ii  libc6   2.37-12
ii  libdpkg-perl1.22.1
ii  libffi8 3.4.4-1
ii  libgirepository-1.0-1 [libgirepository-1.0-1-with-libffi8]  1.78.1-1
ii  libglib2.0-02.78.0-2
ii  python3 3.11.4-5+b1
ii  python3-distutils   3.11.5-1
ii  python3-mako1.2.4+ds-2
ii  python3-markdown3.4.4-1

gobject-introspection recommends no packages.

gobject-introspection suggests no packages.

-- no debconf information

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Bug#1055436: openjpeg2: openjpeg / apache build-dep loop

[Samuel Thibault]

Source: openjpeg2
Version: 2.5.0-2
Severity: normal
Tags: patch

Hello,

openjpeg2 currently depends on dh-apache2, which introduces build-dep
loops between openjpeg2, ghostscript, doxygen, apr, apr-util, apache2,
which makes bootstraping new Debian ports tricky.

It would be useful to introduce a pkg.openjpeg2.noapache build profile
that avoids the dependency, as the attached patch does, could you apply
it?

Thanks,
Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-06 02:26:51.969738191 +0100
+++ debian/control  2023-11-06 02:27:46.746128984 +0100
@@ -5,7 +5,7 @@
 Homepage: https://www.openjpeg.org
 Build-Depends: cmake (>= 2.8.2),
debhelper-compat (= 12),
-   dh-apache2,
+   dh-apache2 ,
help2man,
libcurl4-gnutls-dev | libcurl-ssl-dev,
libfcgi-dev,
@@ -88,6 +88,7 @@
 Package: libopenjpip-viewer
 Section: graphics
 Architecture: all
+Build-Profiles: 
 Depends: libopenjpip-dec-server, ${java:Depends}, ${misc:Depends}
 Suggests: libopenjp2-tools
 Conflicts: openjpip-viewer
--- debian/rules.original   2023-11-06 02:29:44.086963470 +0100
+++ debian/rules2023-11-06 02:30:35.419327426 +0100
@@ -17,8 +17,12 @@
   BUILDDOC = ON
 endif
 
+ifeq (,$(filter pkg.openjpeg2.noapache,$(DEB_BUILD_PROFILES)))
+DH_APACHE=--with=apache2
+endif
+
 %:
-   dh $@ --with apache2 $(DH_ADDONS) $(BUILD_PACKAGES)
+   dh $@ $(DH_APACHE) $(DH_ADDONS) $(BUILD_PACKAGES)
 build binary %-indep: DH_ADDONS=--with=javahelper
 
 CMAKE_EXTRA_FLAGS += -DCMAKE_SKIP_RPATH=ON \

Bug#1055435: numpy: dvisvgm build-dep not actually needed

[Samuel Thibault]

Source: numpy
Version: 1:1.24.2-1
Severity: normal

Hello,

numpy currently build-depends on dvisvgm, making it part of hairy
dependency loops through lerc/tiff/texlive. But the dependency is not
actually used, so could you try it to make boostraping new Debian ports
more seamless?

Thanks,
Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Bug#1055434: libwebp <-> tiff build-dep loop

[Samuel Thibault]

Source: libwebp
Version: 1.3.2-0.3
Severity: normal

Hello,

There is a direct build-depend loop between libwebp and tiff. Could you
introduce a notiff build profile in order to break this loop? Otherwise
one can't seamlessly bootstrap new Debian ports.

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Bug#1055433: key enrollment on non-EFI systems for `module.sig_enforce=1` kernel parameter

[Patrick Schleizer]

Package: src:linux
Severity: normal

Kernel module signature verification can be enabled using the 
`module.sig_enforce=1` kernel parameter on non-EFI systems.


On non-EFI systems, `mokutil` won't work. But then how could one enroll 
the key without needing to recompile grub or the kernel?


Can `/var/lib/dkms/mok.pub` be enrolled using `keyctl`? Probably not. As 
per kernel manual. [1]


> Note, however, that the kernel will only permit keys to be added to 
.builtin_trusted_keys if the new key's X.509 wrapper is validly signed 
by a key that is already resident in the .builtin_trusted_keys at the 
time the key was added.


Upstream DKMS thinks DKMS is the wrong place to do this.

Cheers,
Patrick

[1] https://www.kernel.org/doc/html/v6.6/admin-guide/module-signing.html

[2] https://github.com/dell/dkms/issues/359

Bug#1055432: kontact: Attaching file to email tries to mount filesystems

[Juha Jäykkä]

Package: kontact
Version: 4:22.12.3-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

Kontact email composition window "Attach file" should not try to mount 
filesystems that
aren't already mounted and the user does not explicitly try to enter.

Reproduce:

1. Set up an automounted filesystem, e.g. at /mnt/foobar
2. Mount it
3. Add /mnt/foobar to the sidebar either in Places, Recent Locations, or Remote,
   do not enter the directory (or come out of it after so it's not the last one
   you were in while the dialog is open)
4. Close the compose window
5. Umount /mnt/foobar
6. Compose another email and attach a file: /mnt/foobar gets mounted.

I appreciate this is an attempt to be helpful, gathering information about 
known mountpoints,
but the nature of autofs mountpoints is that they are not guaranteed to be 
always available
to be mounted so causing an attempt to mount them without user explicitly 
asking for it is
not good.

This is especially bad when the mountpoint is an NFS mount: kontact will hang 
until autofs
succeeds in mounting it. If the NFS server is never coming back, data loss 
follows as kontact
will never recover from an uninterruptible system call.

This is also highly annoying even when the server is available but /mnt/foobar 
is not yet
mounted: opening the file selection dialog takes as long as it takes for the 
mount to finish,
which is long enough to be annoying.

Kontact needs to be selective in its helpfulness: avoid causing autofs mounts 
to be triggered
if they are not yet mounted unless explicitly requested by the user.

Cheers,
Juha

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

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

Versions of packages kontact depends on:
ii  kdepim-runtime   4:22.12.3-2
ii  libc62.37-12
ii  libkf5configcore55.107.0-1
ii  libkf5configgui5 5.107.0-1
ii  libkf5configwidgets5 5.107.0-2
ii  libkf5coreaddons55.107.0-1
ii  libkf5crash5 5.107.0-1
ii  libkf5grantleetheme5 [libkf5grantleetheme5-22.12]22.12.3-2+b1
ii  libkf5guiaddons5 5.107.0-1
ii  libkf5i18n5  5.107.0-1+b1
ii  libkf5jobwidgets55.107.0-1
ii  libkf5kcmutils5  5.107.0-2
ii  libkf5kiogui55.107.0-1
ii  libkf5kontactinterface5 [libkf5kontactinterface5-22.12]  22.12.3-1
ii  libkf5libkdepim5 [libkf5libkdepim5-22.12]4:22.12.3-1
ii  libkf5parts5 5.107.0-1
ii  libkf5pimcommon5abi2 [libkf5pimcommon5-22.12]4:22.12.3-1
ii  libkf5service-bin5.107.0-1
ii  libkf5service5   5.107.0-1
ii  libkf5widgetsaddons5 5.107.0-1
ii  libkf5windowsystem5  5.107.0-1
ii  libkf5xmlgui55.107.0-1+b1
ii  libqt5core5a 5.15.10+dfsg-4
ii  libqt5dbus5  5.15.10+dfsg-4
ii  libqt5gui5   5.15.10+dfsg-4
ii  libqt5webengine5 5.15.15+dfsg-2+b1
ii  libqt5webenginecore5 5.15.15+dfsg-2+b1
ii  libqt5webenginewidgets5  5.15.15+dfsg-2+b1
ii  libqt5widgets5   5.15.10+dfsg-4
ii  libstdc++6   13.2.0-6

Versions of packages kontact recommends:
ii  accountwizard  4:22.12.3-1
ii  akregator  4:22.12.3-1
ii  kaddressbook   4:22.12.3-1
ii  kmail  4:22.12.3-1
ii  knotes 4:22.12.3-1
ii  korganizer 4:22.12.3-1

Versions of packages kontact suggests:
pn  gnokii  

-- no debconf information

Bug#1055431: RFS: scala-mode-el/1:1.1.0+git20221025.5d7cf21-1 [RC] [Team] -- transitional dummy package, scala-mode-el to elpa-scala-mode

[Xiyue Deng]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: debian-emac...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "scala-mode-el":

 * Package name : scala-mode-el
   Version  : 1:1.1.0+git20221025.5d7cf21-1
   Upstream contact : Heikki Vesalainen 
 * URL  : https://github.com/hvesalai/emacs-scala-mode
 * License  : SCALA-LICENSE, GPL-3+
 * Vcs  : https://salsa.debian.org/emacsen-team/scala-mode-el
   Section  : editors

The source builds the following binary packages:

  elpa-scala-mode - Emacs major mode for editing scala source code
  scala-mode-el - transitional dummy package, scala-mode-el to elpa-scala-mode

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

  https://mentors.debian.net/package/scala-mode-el/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/scala-mode-el/scala-mode-el_1.1.0+git20221025.5d7cf21-1.dsc

Changes since the last upload:

 scala-mode-el (1:1.1.0+git20221025.5d7cf21-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository-Browse.
   * Update standards version to 4.6.1, no changes needed.
   * Set upstream metadata fields: Repository.
   * Update standards version to 4.6.2, no changes needed.
 .
   [ Xiyue Deng ]
   * Sync to latest upstream head (5d7cf21).
   * Override clean rules in d/rules to fix building. (Closes: #1052917)
   * Modernize d/watch using special substitute strings.
   * Add more metadata in d/upstream/metadata.
   * Update year and Upstream-Contact and add myself in d/copyright.
   * Use xz compression in d/gbp.conf.

Regards,
-- 
  Xiyue Deng

Bug#1055372: btrfs-progs: new upstream version

[Christoph Anton Mitterer]

Hey.

Upstream has released 6.6.1, which contains an important fix.

6.6 should not be used, see:
https://lore.kernel.org/linux-btrfs/20231105222046.19483-1-dste...@suse.com/T/#u

Cheers,
Chris.

Bug#1055430: RFS: ruby-mdl/0.13.0-2 -- Markdown lint tool - transitional dummy package

[Norwid Behrnd]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "ruby-mdl":

 * Package name : ruby-mdl
   Version  : 0.13.0-2
   Upstream contact : ["p...@ipom.com"]
 * URL  : https://github.com/markdownlint/markdownlint
 * License  : MIT
 * Vcs  : https://salsa.debian.org/nbehrnd/ruby-mdl
   Section  : text

The source builds the following binary packages:

  markdownlint - Markdown lint tool
  ruby-mdl - Markdown lint tool - transitional dummy package

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

  https://mentors.debian.net/package/ruby-mdl/

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

  dget -x
  https://mentors.debian.net/debian/pool/main/r/ruby-mdl/ruby-mdl_0.13.0-2.dsc

Changes since the last upload:

 ruby-mdl (0.13.0-2) unstable; urgency=medium
 .
   * Source only upload for migration to testing

Regards,

Bug#1037020: xfce4-panel: workspace switcher extremely wide after bookworm upgrade

[Maxim Medvedev]

Hello,

There is a problem. It is very easy to reproduce it. Just install compiz
and specify Desktop size => Horizontal Virtual Size = 4 (for example).
After that, add the Workspace Switcher applet. After that, each cell of the
desktop will be equal to the virtual size.

--
Best regards,
Maxim Medvedev

Bug#1055429: bind9: iproute2 change ripples through bind9 sysvinit script preventing start

[Bob Proulx]

Package: bind9
Version: 1:9.19.17-1
Severity: normal
Tags: patch

A recent change in the iproute2 package moved the installed location
of the "ip" program from /bin/ip to /usr/bin/ip with the
iproute2-6.5.0-5 packaging.  That's all well and good of course.

On systems using sysvinit and not yet UsrMerged this snags a problem
in the sysvinit init script.  I know and understand that this is not a
combination that you or Debian is officially supporting.  But it would
help out interoperability if a one line fix were applied and your
kindness would be appreciated.

Here is the patch that corrects the problem.

--- named.original  2023-09-20 10:13:07.0 -0600
+++ named   2023-11-05 14:58:49.277781923 -0700
@@ -32,7 +32,7 @@
 if [ -x /usr/bin/uname ] && [ "X$(/usr/bin/uname -o)" = XSolaris ]; then
 LIST_NICS_IP=$(/sbin/ifconfig -au) || result=$?
 else
-LIST_NICS_IP=$(/bin/ip addr) || result=$?
+LIST_NICS_IP=$(ip addr) || result=$?
 fi
 if [ $result -ne 0 -o -z "${LIST_NICS_IP}" ]; then
#log_action_msg "No networks configured."

PATH is already set and there is no need to use a hard coded path for
that program.  Doing so results in this situation now where movement
of the program executable causes failure.  Better just to call it and
have it be found on PATH.

Thank you for maintaining bind9 in Debian!

Bob

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

Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Bug#1037440: kitty: Integrating golang parts of the package

[Nilesh Patra]

On Sun, Nov 05, 2023 at 10:09:44AM -0500, James McCoy wrote:
> The former is fine with me.  I took a quick look at what Fedora is
> doing, and it looks like they just patch setup.py to return from
> build_static_kittens() just before the “go build -v” line.
> 
> Adding a patch for that and then adapting the rest of the Debian side of
> the build to do it seems reasonable.

Right. So I have an update for you. I have attached a patch on top of
MR!3 [1] with this mail which gets the go parts (static kitten binary) building
for me \o/.
I wanted to commit directly but admittedly the non-gbp flow is
confusing for me so I left figuring this out for later.

I tried testing it locally and so far it does work as I expect it to.

I did the following changes:
* GO111MODULE should be turned off for debian specific builds otherwise
  it tries to fetch packages from the internet which is forbiden in
  build.
* Add dh_auto_configure for go counterpart as it'd initialize a _build
  directory with symlink to all packages. This saves us from some of the
  manual work which is done for example in[2].
* Added a corresponding clean directive too so as to cleanup _build
* I realised using dh_auto_build with go profiles is not something that
  works smoothly as it expects go files in 'kitty/' and it has none.
  There are a couple of other caveats too, so using 'go build '
  works better.
* Copied some generated header files in python counter part's build to
  _build directory
* Since some files did not get copied by go's dh_auto_configure they
  have been specified in DH_GOLANG_INSTALL_EXTRA
* Added a patch to ignore checking go version from go.mod as go list -m
  does not work with GO111MODULE set to off. This needs to be adjusted
  in d/control anyway
* Added kitten binary in d/kitten.install
* Add a XS-Go-Import-Path field in d/control in accordance with the
  package name in go.mod
* Update build deps and add versioned B-D on exp-dev

-> Note that exp-dev needs to be updated in debian. Since this is a key
package I have pinged the maintainer (on IRC) to do it. For this build,
I locally updated this and a couple other packages in the chain. You can
use the .debs for these from here[3]

-> I skipped the tests in d/rules as python specific stuff fails. I
leave the onus of fixing this on you :)

I hope this helps!

[1]: https://salsa.debian.org/debian/kitty/-/merge_requests/3
[2]: 
https://sources.debian.org/src/ncbi-entrez-direct/19.2.20230331+dfsg-3/debian/rules/
[3]: https://people.debian.org/~nilesh/kitty/

Best,
Nilesh
commit 281201ccddfee95a606d82e1860fa3ea73d355fd
Author: Nilesh Patra 
Date:   Mon Nov 6 03:05:17 2023 +0530

Changes to get kitten building

diff --git a/debian/control b/debian/control
index 3258bcc61..66ceda63c 100644
--- a/debian/control
+++ b/debian/control
@@ -4,6 +4,7 @@ Maintainer: James McCoy 
 Section: x11
 Standards-Version: 4.6.2
 Rules-Requires-Root: no
+XS-Go-Import-Path: kitty
 Homepage: https://sw.kovidgoyal.net/kitty/
 Vcs-Git: https://salsa.debian.org/debian/kitty.git
 Vcs-Browser: https://salsa.debian.org/debian/kitty
@@ -17,7 +18,7 @@ Build-Depends:
  furo ,
  golang-any,
  golang-github-altree-bigfloat-dev,
- golang-github-alecthomas-chroma-dev,
+ golang-github-alecthomas-chroma-v2-dev,
  golang-github-bmatcuk-doublestar-dev,
  golang-github-disintegration-imaging-dev,
  golang-github-dlclark-regexp2-dev,
@@ -26,7 +27,7 @@ Build-Depends:
  golang-github-seancfoley-ipaddress-go-dev,
  golang-github-shirou-gopsutil-dev,
  golang-github-zeebo-xxh3-dev,
- golang-golang-x-exp-dev,
+ golang-golang-x-exp-dev (>= 0.0~git20230801),
  golang-golang-x-image-dev,
  golang-golang-x-sys-dev,
  golang-howett-plist-dev,
diff --git a/debian/kitty.install b/debian/kitty.install
index fe49de93f..63b03ef63 100644
--- a/debian/kitty.install
+++ b/debian/kitty.install
@@ -1,4 +1,5 @@
 debian/tmp/usr/bin/kitty
+debian/tmp/usr/bin/kitten
 debian/tmp/usr/lib/
 debian/tmp/usr/share/applications/kitty.desktop
 debian/tmp/usr/share/icons/
diff --git a/debian/patches/fix-version.patch b/debian/patches/fix-version.patch
new file mode 100644
index 0..063c9d7d6
--- /dev/null
+++ b/debian/patches/fix-version.patch
@@ -0,0 +1,25 @@
+Description: "go list -m" does not work with GO111MODULE set to off. Disable version checking for now.
+ Also build the static kittens via debian buildsystem instead of the upstream one.
+Author: Nilesh Patra 
+Forwarded: not-needed
+Last-Update: 2023-11-06
+--- a/setup.py
 b/setup.py
+@@ -964,12 +964,13 @@
+ go = shutil.which('go')
+ if not go:
+ raise SystemExit('The go tool was not found on this system. Install Go')
+-required_go_version = subprocess.check_output([go] + 'list -f {{.GoVersion}} -m'.split()).decode().strip()
+-current_go_version = subprocess.check_output([go, 'version']).decode().strip().split()[2][2:]
+-if parse_go_version(required_go_version) > parse_go_version(current_go_version):
+-raise SystemExit(f'The version of go 

Bug#1053383: verilator version in testing is subject to upstream issue 4362

[Larry Doolittle]

On Mon, Oct 02, 2023 at 11:04:12PM -0700, Larry Doolittle wrote:
> [...] working versions are v5.014 and v5.016.

Verilator v5.018 was pushed to upstream git on Oct 31,
and I can confirm it also does not suffer from this bug.

  - Larry

Bug#237925: ITP: cdemu -- CD drive emulator for Linux

[Robert Ayrapetyan]

I've created a tutorial for installing cdemu in Debian (using a
Dockerfile), it can be easily adapted to the official Debian
package(s):
https://github.com/rayrapetyan/cdemu_debian_install/tree/main

Produces 7 independent deb packages:

vhba-dkms*.deb
libmirage_*.deb (required by cdemu-daemon and image-analyzer)
cdemu-daemon_*.deb
cdemu-client_*.deb
gcdemu*.deb
gir*.deb
image-analyzer*.deb

If no one replies, I can take ownership of these.

On Thu, 7 Jan 2021 14:54:59 +0200 Anya Annetova
 wrote:
> Any progress on this?

Bug#1055285: libseccomp misbehave on loong64

[Felix Geyer]

Hi,

On 03.11.23 15:39, Miao Wang wrote:

Package: libseccomp2
Version: 2.5.4-1+loong64
Severity: normal
Tags: patch

libseccomp2 in debian ports lonng64 cannot work properly because it is using a
wrong mapping between syscall numbers and names, which can be reproduced by
first installing package seccomp and then execute:

```
scmp_sys_resolver accept
```

The syscall number in the output is not correct, which should be 202 on loong64
architecture.


Please report this to debian-loonga...@lists.debian.org instead since
version 2.5.4-1+loong64 is not part of the Debian archive but added
by the loongarch porter team.

Felix

Bug#1055254: transition: dav1d

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2023-11-02 21:57:58 +0100, Dylan Aïssi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> Please schedule a transition slot for dav1d.
> 
> The auto-generated ben tracker looks good:
> https://release.debian.org/transitions/html/auto-dav1d.html
> 
> All reverse deps (ffmpeg, libavif, libheif, vlc and xine-lib-1.2) build fine
> with the new version in experimental.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1055428: ITP: python-pyrate-limiter -- The request rate limiter using Leaky-bucket algorithm

[Safir Secerovic]

Package: wnpp
Severity: wishlist
Owner: Safir Secerovic 
X-Debbugs-Cc: debian-de...@lists.debian.org, stephanlach...@debian.org

* Package name: python-pyrate-limiter
  Version : 2.10.0
  Upstream Contact: Vu Tran 
* URL : https://github.com/vutran1710/PyrateLimiter/
* License : MIT/X
  Programming Lang: Python
  Description : The request rate limiter using Leaky-bucket algorithm

Dependency of python-moddb (#1030392).
Will be maintained in Debian Games Team.
It should be temporarily held at 2.10.0 version.
As the package(s) that depend on it move forward so will the updates to this 
package.

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

[Markus Koschany]

Am Sonntag, dem 05.11.2023 um 20:35 + schrieb Adam D. Barratt:
> [...]
> After a bit of searching, I happened across a discussion of a similar
> change in a different product that mentioned the
> SslContextFactory$Server syntax, so gave that a try. The resulting
> package is now installed on handel.d.o and seems to work - at least,
> it's been running for 45 minutes now (whereas the broken versions
> lasted less than 5 minutes) and at least one client has successfully
> made a "puppet agent" run in the meantime.
> 
> I've attached a debdiff of the package we're now running, with the
> revised patch.

Great, thanks for the update. I feared the Java dot syntax couldn't be applied
one-to-one to Clojure. I suggest we wait another 24h to confirm it works and if
you don't see another regression then I'll release a new update tomorrow.

Regards,

Markus


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

Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found

[Faidon Liambotis]

Hi Paul,

On Sun, Nov 05, 2023 at 01:45:34PM +0100, Paul Gevers wrote:
> Source: wasmedge
> Version: 0.13.4+dfsg-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s),
> 
> Your package has an autopkgtest, great. However, it fails. Can you please
> investigate the situation and fix it? I copied some of the output at the
> bottom of this report.
> 
> The release team has announced [1] that failing autopkgtest on amd64 and
> arm64 are considered RC in testing.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> [...]
>
> 140s #   `clang++ --target=wasm32-wasi -o fibonacci.wasm
> -mexec-model=reactor script/fibonacci.cpp' failed
> 140s # In file included from script/fibonacci.cpp:1:
> 140s # script/fibonacci.h:3:10: fatal error: 'cstdint' file not found

Thank you for your report. This is caused #1052002, which I had marked
as affects: wasmedge previously.

Basically, the autopkgtest compiles a piece of code (with Clang) and
tries to run it (with WasmEdge). The Clang++ regression means the code
cannot be built.

I don't know how you'd like ot handle this w.r.t. the BTS, and testing
migrations. I'm inclined to just reassign/merge it to the bug above, but
I'll wait for your opinion first.

Also, I'm not sure I understand how clang migrated to testing when it
introduced an autopkgtest regression in another package. Isn't
autopkgtest integration in britney supposed to prevent this kind of
thing from happening?

Looking for your guidance,
Faidon

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

[Adam D. Barratt]

On Sun, 2023-11-05 at 19:18 +0100, Markus Koschany wrote:
> Am Sonntag, dem 05.11.2023 um 16:33 + schrieb Adam D. Barratt:
> > [...]
> > Do you have an idea how simple rebuilding the bullseye package on
> > buster would be? I'm happy to try that in general, but I've not
> > really
> > looked at the Java ecosystem in Debian much.
> 
> Sorry, I missed those new or updated dependencies. That complicates
> the matter a little. We also have to deal with clojure here, a LISP
> dialect of the Java language with a different build system
> (leiningen), but if all dependencies were in place a rebuild would be
> pretty simple. As a last resort I could bundle all those dependencies
> together with trapperkeeper-* the Java way TM but I hope we can avoid
> that.
> 
> The most ideal solution is a patch for the current version in Buster.
> I have uploaded a new revision to people.debian.org with minimal
> changes here:
> 
> https://people.debian.org/~apo/lts/buster/trapperkeeper-webserver-jetty9-clojure/
> 
> dget -x 
> https://people.debian.org/~apo/lts/buster/trapperkeeper-webserver-jetty9-clojure/trapperkeeper-webserver-jetty9-clojure_1.7.0-2+deb10u1.1.dsc
>  
> 
> should work as expected. I'm attaching the debdiff as well.
> 
> My solution is to replace the old SslContextFactory class with the
> new inner SslContextFactory.Server class but I don't know if this
> change has the desired effect because I couldn't test it.

Thanks for the patch.

Unfortunately it didn't work as-is:

Nov  5 18:39:14 handel/handel java[2393]: Exception in thread "main" 
java.lang.AssertionError: Assert failed: (keyword? kw)
Nov  5 18:39:14 handel/handel java[2393]:   at 
puppetlabs.kitchensink.core$without_ns.invokeStatic(core.clj:613)
Nov  5 18:39:14 handel/handel java[2393]:   at 
puppetlabs.kitchensink.core$without_ns.invoke(core.clj:613)
Nov  5 18:39:14 handel/handel java[2393]:   at 
puppetlabs.trapperkeeper.core$main.invokeStatic(core.clj:175)
Nov  5 18:39:14 handel/handel java[2393]:   at 
puppetlabs.trapperkeeper.core$main.doInvoke(core.clj:159)
Nov  5 18:39:14 handel/handel java[2393]:   at 
clojure.lang.RestFn.applyTo(RestFn.java:137)
Nov  5 18:39:14 handel/handel java[2393]:   at 
clojure.core$apply.invokeStatic(core.clj:665)
Nov  5 18:39:14 handel/handel java[2393]:   at 
clojure.core$apply.invoke(core.clj:660)
Nov  5 18:39:14 handel/handel java[2393]:   at 
puppetlabs.puppetdb.cli.services$provide_services.invokeStatic(services.clj:570)
Nov  5 18:39:14 handel/handel java[2393]:   at 
puppetlabs.puppetdb.cli.services$provide_services.invoke(services.clj:558)
Nov  5 18:39:14 handel/handel java[2393]:   at 
puppetlabs.puppetdb.cli.services$cli$fn__41585.invoke(services.clj:578)
...

After a bit of searching, I happened across a discussion of a similar
change in a different product that mentioned the
SslContextFactory$Server syntax, so gave that a try. The resulting
package is now installed on handel.d.o and seems to work - at least,
it's been running for 45 minutes now (whereas the broken versions
lasted less than 5 minutes) and at least one client has successfully
made a "puppet agent" run in the meantime.

I've attached a debdiff of the package we're now running, with the
revised patch.

Regards,

Adam
diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog
--- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog	2019-09-13 10:00:50.0 +0100
+++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog	2023-11-05 19:28:22.0 +
@@ -1,3 +1,11 @@
+trapperkeeper-webserver-jetty9-clojure (1.7.0-2+deb10u1+dsa1) buster; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace deprecated class SslContextFactory with SslContextFactory.Server.
+Largely based on a patch by Markus Koschany. (Hopefully Closes:#1055348)
+
+ -- Adam D. Barratt   Sun, 05 Nov 2023 19:28:22 +
+
 trapperkeeper-webserver-jetty9-clojure (1.7.0-2+deb10u1) buster; urgency=medium
 
   [ Manfred Stock ]
diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series
--- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series	2019-09-13 09:54:48.0 +0100
+++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series	2023-11-05 19:28:22.0 +
@@ -3,3 +3,4 @@
 0003-TK-369-Add-LifeCycleImplementingRequestLogImpl.patch
 0004-Implement-LifeCycle-methods-missing-from-RequestLogI.patch
 0005-maint-Disable-EndpointIdentification.patch
+SslContextFactory.Server.patch
diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.Server.patch trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.Server.patch
--- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.Server.patch	1970-01-01 01:00:00.0 +0100
+++ 

Bug#915583: debian sphinx styling: second attempt

[Stéphane Blondon]

Le ven. 3 nov. 2023 à 15:43, Sam Hartman  a écrit :

> > "Sean" == Sean Whitton  writes:
>
> I'm happy to test with Orca on Firefox on Debian.
> Feel free to point me at a URL.
>


You can test it at:
http://stephane.yaal.fr/tmp/policy/

Regards

>

Bug#1055345: git-buildpackage: Please document how to build against a package from experimental

[Martin Quinson]

Le dimanche 05 novembre 2023 à 17:27 +0100, Guido Günther a écrit :
> Hi Martin,
> On Sat, Nov 04, 2023 at 04:43:10PM +0100, Martin Quinson wrote:
> > Package: git-buildpackage
> > Version: 0.9.32
> > Severity: wishlist
> > Tags: patch
> > 
> > Hello,
> > 
> > thanks a lot for this package, that very often saves my life when
> > packaging.
> > There is one thing however where gbp could be more helpful, it's when I
> > have to
> > build my package against a build-depend that comes from experimental.
> > 
> > I finally found a way to do it, and I propose the following patch for the
> > documentation for the next person looking for this information. I fully
> > acknowledge that this documentation is somehow suboptimal, and that the gbp
> > tool could be more helpful here, but the proposed documentation would
> > already
> > be great.
> 
> Thanks for taking the time to document this. Some minor nits below:
> 
> 
> > ---
> >  docs/chapters/special.xml |   25 +
> >  1 file changed, 25 insertions(+)
> > 
> > Index: b/docs/chapters/special.xml
> > ===
> > --- a/docs/chapters/special.xml
> > +++ b/docs/chapters/special.xml
> > @@ -40,6 +40,31 @@
> >  
> >  
> >  
> > +    
> > +    Using build-depends from experimental
> > +    
> 
> This should mention that one ought to use `gbp buildpackage
> --git-pbuilder` (as that is not the default).

Agreed.

> > +    To build your package against a build-depends taken from experimental,
> > you first need
> > +    to configure your pbuilder. To that extend, add the following to
> > +    ~/.pbuilderrc to instruct pbuilder to take build
> > depends from
> > +    experimental when they cannot be satisfied from unstable.
> > +    
> > +    
> > +PBUILDERSATISFYDEPENDSCMD=/usr/lib/pbuilder/pbuilder-satisfydepends-
> > experimental
> > +    
> 
> Wouldn't we want to make that conditional like:
> 
> if [ "$GBP_DIST" = "experimental" ]; then
>     echo "Using 'pbuilder-satisfydepends-experimental' for $GBP_DIST"
>     PBUILDERSATISFYDEPENDSCMD=/usr/lib/pbuilder/pbuilder-satisfydepends-
> experimental
> fi

Nice addition, thanks.

> but I *think* this is even the default nowadays for building against
> experimental.
> 
> > +    
> > +    You then need to add experimental to the apt configuration within the
> > chroot.
> > +    The simplest for that is to edit the config file from outside of the
> > chroot directly,
> > +    as follows:
> > +    
> > +sudo bash -c "echo 'deb http://deb.debian.org/debian experimental main' >>
> > /var/cache/pbuilder/base.cow/etc/apt/sources.list"
> > +    
> 
> What about suggesting to bootstrap a new environment instead via:
> 
>    DIST=experimental git-pbuilder create 
> 
> This also handles adding experimental to /etc/apt/sources.list (no extra
> setup needed). Maybe we can streamline things that way a bit?

This has the drawback of taking all dependencies from experimental, which may
not be what one wants.

I agree that things could be streamlined in the tool, but documenting how to
get around the corner with the current tools is already great, IMHO.

Thanks,
Mt


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

Bug#1055426: xorg-server: CVE-2023-5574

[Salvatore Bonaccorso]

Source: xorg-server
Version: 2:21.1.9-1
Severity: important
Tags: security upstream
Forwarded: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1189
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2:21.1.7-3
Control: found -1 2:21.1.7-3+deb12u2
Control: found -1 2:1.20.11-1
Control: found -1 2:1.20.11-1+deb11u8

Hi,

The following vulnerability was published for xorg-server.

Known already and this is the CVE which was last-minute backed out of
the last release. Filling the downstream bug to have a tracking of it
for us in Debian.

CVE-2023-5574[0]:
| A use-after-free flaw was found in xorg-x11-server-Xvfb. This issue
| occurs in Xvfb with a very specific and legacy configuration (a
| multi-screen setup with multiple protocol screens, also known as
| Zaphod mode). If the pointer is warped from a screen 1 to a screen
| 0, a use-after-free issue may be triggered during shutdown or reset
| of the Xvfb server, allowing for possible escalation of privileges
| or 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-5574
https://www.cve.org/CVERecord?id=CVE-2023-5574
[1] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1189
[2] https://lists.x.org/archives/xorg-announce/2023-October/003430.html

Regards,
Salvatore

Bug#1055424: ITP: python-sdbus -- modern Python D-Bus library

[Luca Boccassi]

Package: wnpp
Severity: wishlist
Owner: Luca Boccassi 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-sdbus
  Version : 0.11.1
  Upstream Author : various
* URL : https://github.com/python-sdbus/python-sdbus
* License : LGPL-2.1-or-later
  Programming Lang: python
  Description : python D-Bus library that aim to use the modern
features of python. It is based on libsystemd's sd-bus.

-- 
Kind regards,
Luca Boccassi


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

Bug#1055425: openmpi: Fix hurd-amd64 build

[Samuel Thibault]

Source: openmpi
Version: 4.1.6-1
Severity: important
Tags: patch

Hello,

hurd-amd64 has the same constraints as hurd-i386, could you apply the
attached patch?

Thanks,
Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-04 22:36:48.0 +
+++ debian/control  2023-11-05 14:57:00.0 +
@@ -13,12 +13,12 @@
  gfortran,
  libhwloc-dev,
  pkg-config,
- libibverbs-dev (>= 1.1.7) [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386],
- libfabric-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !sh4 !powerpc !x32],
- libnuma-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386],
+ libibverbs-dev (>= 1.1.7) [!kfreebsd-any !hurd-any],
+ libfabric-dev [!kfreebsd-any !hurd-any !sh4 !powerpc !x32],
+ libnuma-dev [!kfreebsd-any !hurd-any],
  libpsm-infinipath1-dev [amd64 i386],
  libpsm2-dev [amd64],
- default-jdk [!hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !alpha !ppc64 
!sparc64] ,
+ default-jdk [!hppa !hurd-any !kfreebsd-any !alpha !ppc64 !sparc64] ,
  flex
 Build-Conflicts: libmpich-dev, libopenmpi-dev
 Standards-Version: 4.6.2
@@ -69,7 +69,7 @@
 Depends: ${shlibs:Depends}, ${misc:Depends}, 
  libopenmpi3 (= ${binary:Version}), 
  openmpi-common (>= ${source:Version}), 
- libibverbs-dev (>= 1.1.7) [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], 
libhwloc-dev,
+ libibverbs-dev (>= 1.1.7) [!kfreebsd-any !hurd-any], libhwloc-dev,
  libevent-dev, 
  libpmix-dev,
  libjs-jquery,
--- debian/rules.original   2023-11-05 01:21:44.0 +
+++ debian/rules2023-11-05 01:22:04.0 +
@@ -14,15 +14,15 @@
 
 ### Arch-specific stuff
 # No ibverbs support available on kFreeBSD, Hurd
-NO_VERBS_ARCH:= hurd-i386 kfreebsd-amd64 kfreebsd-i386 s390x 
-NO_FABRIC_ARCH:= hurd-i386 kfreebsd-amd64 kfreebsd-i386 s390x sh4 powerpc x32
+NO_VERBS_ARCH:= hurd-amd64 hurd-i386 kfreebsd-amd64 kfreebsd-i386 s390x 
+NO_FABRIC_ARCH:= hurd-amd64 hurd-i386 kfreebsd-amd64 kfreebsd-i386 s390x sh4 
powerpc x32
 PSM_ARCH:= amd64 i386
 PSM2_ARCH:= amd64
 UCX_ARCH:= amd64 ppc64el arm64
 ATOMICS_ARCH:= s390x riscv64
 NO_CMA_ARCH:= s390x mipsel hppa alpha armhf armel m68k sparc64
-NO_JAVA_ARCH:= hppa hurd-i386 kfreebsd-amd64 kfreebsd-i386 ppc64 alpha sparc64
-NO_TEST_ARCH:= hppa hurd-i386
+NO_JAVA_ARCH:= hppa hurd-amd64 hurd-i386 kfreebsd-amd64 kfreebsd-i386 ppc64 
alpha sparc64
+NO_TEST_ARCH:= hppa hurd-amd64 hurd-i386
 
 
 UCX:= $(if $(filter $(DEB_TARGET_ARCH), $(UCX_ARCH)),  --with-ucx,  )

Bug#1055415: Wrong order for the `resolve' option in nsswitch.conf

[Sylvain Garrigues]

Le dimanche 5 novembre 2023, Michael Biebl  a écrit :

>
> See https://salsa.debian.org/systemd-team/systemd/-/merge_requests/162
>
>
This is indeed related. Yet the changes (as of today) do not seem to fix
the order for `resolve'. This merge request seems to be waiting for a
consensus before it can make progress.

Bug#1055423: O: fbpanel -- lightweight X11 desktop panel

[Robert Ayrapetyan]

Package: wnpp
Severity: normal

FBPanel is a spinoff of the fspanel (f***ing small panel) with more
eye candy. It provides a taskbar (list of all opened windows), desktop
switcher, launchbar, clock, is EWMH/NETWM compliant, and has modest
resource usage.

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

[Markus Koschany]

Am Sonntag, dem 05.11.2023 um 16:33 + schrieb Adam D. Barratt:
> [...]
> Do you have an idea how simple rebuilding the bullseye package on
> buster would be? I'm happy to try that in general, but I've not really
> looked at the Java ecosystem in Debian much.

Sorry, I missed those new or updated dependencies. That complicates the matter
a little. We also have to deal with clojure here, a LISP dialect of the Java
language with a different build system (leiningen), but if all dependencies
were in place a rebuild would be pretty simple. As a last resort I could bundle
all those dependencies together with trapperkeeper-* the Java way TM but I hope
we can avoid that.

The most ideal solution is a patch for the current version in Buster. I have
uploaded a new revision to people.debian.org with minimal changes here:

https://people.debian.org/~apo/lts/buster/trapperkeeper-webserver-jetty9-clojure/

dget -
x 
https://people.debian.org/~apo/lts/buster/trapperkeeper-webserver-jetty9-clojure/
trapperkeeper-webserver-jetty9-clojure_1.7.0-2+deb10u1.1.dsc 

should work as expected. I'm attaching the debdiff as well.

My solution is to replace the old SslContextFactory class with the new inner
SslContextFactory.Server class but I don't know if this change has the desired
effect because I couldn't test it.

FTR, the already applied 0005-maint-Disable-EndpointIdentification.patch (new
in version +deb10u1) is related to the problem. Actually back then it did "fix"
the SSL problem and I'm a bit surprised it resurfaced now. 

There is also a third alternative. I could revert the split change in jetty9.

https://github.com/jetty/jetty.project/pull/3480/files#diff-58640db0f8f2cd84b7e653d1c1540913

If the new revision doesn't work for you, please send me your puppetdb config,
and I try to figure out a solution myself without the feedback loop delay.
Thanks in advance.

Regards,

Markus
diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog
--- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog	2019-09-13 11:00:50.0 +0200
+++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog	2023-11-05 18:06:31.0 +0100
@@ -1,3 +1,10 @@
+trapperkeeper-webserver-jetty9-clojure (1.7.0-2+deb10u1.1) buster-security; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace deprecated class SslContextFactory with SslContextFactory.Server.
+
+ -- Markus Koschany   Sun, 05 Nov 2023 18:06:31 +0100
+
 trapperkeeper-webserver-jetty9-clojure (1.7.0-2+deb10u1) buster; urgency=medium
 
   [ Manfred Stock ]
diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/0005-maint-Disable-EndpointIdentification.patch trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/0005-maint-Disable-EndpointIdentification.patch
--- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/0005-maint-Disable-EndpointIdentification.patch	2019-09-13 10:54:48.0 +0200
+++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/0005-maint-Disable-EndpointIdentification.patch	2023-11-05 18:06:31.0 +0100
@@ -1,4 +1,3 @@
-From 9db4170381e07165078e544340e12b38676c2613 Mon Sep 17 00:00:00 2001
 From: Justin Stoller 
 Date: Fri, 24 May 2019 16:10:44 -0700
 Subject: [PATCH] (maint) Disable EndpointIdentification
@@ -30,10 +29,10 @@
  1 file changed, 1 insertion(+)
 
 diff --git a/src/puppetlabs/trapperkeeper/services/webserver/jetty9_core.clj b/src/puppetlabs/trapperkeeper/services/webserver/jetty9_core.clj
-index 3a577bb..02e7c7d 100644
+index 99c9885..28cfef7 100644
 --- a/src/puppetlabs/trapperkeeper/services/webserver/jetty9_core.clj
 +++ b/src/puppetlabs/trapperkeeper/services/webserver/jetty9_core.clj
-@@ -197,6 +197,7 @@
+@@ -192,6 +192,7 @@
(.setKeyStore (:keystore keystore-config))
(.setKeyStorePassword (:key-password keystore-config))
(.setTrustStore (:truststore keystore-config))
@@ -41,6 +40,3 @@
;; Need to clear out the default cipher suite exclude list so
;; that Jetty doesn't potentially remove one or more ciphers
;; that we want to be included.
--- 
-2.20.1
-
diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series
--- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series	2019-09-13 10:54:48.0 +0200
+++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series	2023-11-05 18:06:31.0 +0100
@@ -3,3 +3,4 @@
 0003-TK-369-Add-LifeCycleImplementingRequestLogImpl.patch
 0004-Implement-LifeCycle-methods-missing-from-RequestLogI.patch
 0005-maint-Disable-EndpointIdentification.patch
+SslContextFactory.patch
diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.patch trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.patch

Bug#873186: please drop transitional package gnupg2

[Holger Levsen]

On Sun, Nov 05, 2023 at 02:24:44PM +0100, Andreas Metzler wrote:
> Control: block -1 by 1055395 1055397 1055398 1055399 1055400 1055401 1055402 
> 1055403 1055404 1055405 1055406 1055407
> This has to wait, I have just submitted bugs against rdeps.

great, thank you!


-- 
cheers,
Holger

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

If nothing saves us from death, may love at least save us from life.


signature.asc
Description: PGP signature

Bug#1055415: Wrong order for the `resolve' option in nsswitch.conf

[Michael Biebl]

Am 05.11.23 um 16:12 schrieb Sylvain Garrigues:

Package: libnss-resolve
Version: 252.17-1~deb12u1
X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org

The debian postinstall script for libnss-resolve inserts `resolve' in
the `hosts:' line of /etc/nsswitch.conf before `dns', therefore after
`files'. This does not seem optimal, as per `man nss-resolve', which
reads:
Specifically, it is recommended to place "resolve" early in
/etc/nsswitch.conf's "hosts:" line. It should be before the "files"
entry, since systemd-resolved supports /etc/hosts internally, but with
caching.



See https://salsa.debian.org/systemd-team/systemd/-/merge_requests/162



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1042597: python-amqp: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2

[s3v]

Dear Maintainer,

I can reproduce this issue with python3-sphinx 7.2.3-1 from snapshots.d.o
but not with python3-sphinx 7.2.6-1 just uploaded in sid.
I guess this upstream commit [1] fixed reported issue.

Anyway your package still FTBFS with this message:

Exception occurred:
  File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 112, in 
role
    title = caption % part

This is caused by sphinx-celery not compatible with newer Sphinx.
Please see this commit that fixes the problem [2]

Kind Regards

[1] https://github.com/sphinx-doc/sphinx/commit/2a631f97ef7f4b0edc247
[2] https://github.com/celery/sphinx_celery/commit/e2f88da7ad7c400dc5

Bug#1055422: please package 545.xx with open source kernel module

[Felix Zielcke]

Source: nvidia-graphics-drivers
Severity: wishlist


NVIDIA has released the 545 branch of their drivers.
And also says now in the README[1]:

  Use of the open kernel modules on GeForce and Workstation GPUs should be 
considered Beta quality in this release and no longer requires setting of the 
"NVreg_OpenRmEnableUnsupportedGpus" nvidia.ko kernel module parameter. The open 
kernel modules are suitable for broad usage, and NVIDIA requests feedback on 
any issues encountered that are specific to them.


Would be nice to have this avaible in experimental.

Thanks in advance

[1] 
https://download.nvidia.com/XFree86/Linux-x86_64/545.29.02/README/kernel_open.html

Bug#1050348: ITP: melonds -- nintendo DS emulator

[Tobias Frost]

On Wed, 23 Aug 2023 19:54:22 +0100 Jonathan Dowland 
wrote:
> On Wed, Aug 23, 2023 at 03:07:15PM +, Mae Miller wrote:
> >I'm going to be packaging this as my first package partially because
> >it's a program I use and care about and partially in order to learn
how
> >the system works and to make my first contribution to debian.
> 
> Those are great reasons!
> 
> Can melonDS be usefully used without a BIOS/firmware dump from a DS?

According to the upstream FAQ, it needs them:

First of all, melonDS requires BIOS and firmware dumps from a DS or if
you want to emulate the DSi, melonDS requires the BIOS, firmware and
NAND image. We haven't gotten around to making alternate BIOS/firmware
yet. So, you will need to obtain those:
 
> -- 
> Please do not CC me for listmail.
> 
> Jonathan Dowland
> ✎  j...@debian.org
>  https://jmtd.net
> 
> 

Bug#1055241: crun 1.8.1-1+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1055241 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: crun
Version: 1.8.1-1+deb12u1

Explanation: fix containers with systemd as their init system, when using newer 
kernel versions

Bug#1055086: libmateweather 1.26.0-1.1+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1055086 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: libmateweather
Version: 1.26.0-1.1+deb12u1

Explanation: locations: add San Miguel de Tucuman (Argentina); update forecast 
zones for Chicago; update data server URL; fix some location names

Bug#1055031: mda-lv2 1.2.10-1+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1055031 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: mda-lv2
Version: 1.2.10-1+deb12u1

Explanation: fix LV2 plugin installation location

Bug#1055009: distro-info-data 0.58+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1055009 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: distro-info-data
Version: 0.58+deb12u1

Explanation: add Ubuntu 24.04 LTS Noble Numbat; fix several End Of Life dates

Bug#1055009: distro-info 1.5+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1055009 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: distro-info
Version: 1.5+deb12u1

Explanation: update tests for distro-info-data 0.58+deb12u1, which adjusted 
Debian 7's EoL date

Bug#1054470: wormhole-william 1.0.6-2+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1054470 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: wormhole-william
Version: 1.0.6-2+deb12u1

Explanation: disable flaky tests, fixing build failures

Bug#1054589: libapache2-mod-python 3.5.0+git20211031.e6458ec-1+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1054589 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: libapache2-mod-python
Version: 3.5.0+git20211031.e6458ec-1+deb12u1

Explanation: ensure binNMU versions are PEP-440-compliant

Bug#1054122: axis 1.4-28+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1054122 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: axis
Version: 1.4-28+deb12u1

Explanation: filter out unsupported protocols in the client class 
ServiceFactory [CVE-2023-40743]

Bug#1054119: qpdf 11.3.0-1+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1054119 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: qpdf
Version: 11.3.0-1+deb12u1

Explanation: fix data loss issue with some quoted octal strings

Bug#1052229: gnome-shell 43.9-0+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1052229 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: gnome-shell
Version: 43.9-0+deb12u1

Explanation: new upstream stable release; allow notifications to be dismissed 
with backspace key in addition to the delete key; fix duplicate devices shown 
when reconnecting to PulseAudio; fix possible use-after-free crashes on 
PulseAudio/Pipewire restart; avoid sliders in quick settings (volume, etc.) 
being reported to accessibility tools as their own parent object; align 
scrolled viewports to the pixel grid to avoid jitter visible during scrolling

Bug#1050384: awstats 7.8-3+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1050384 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: awstats
Version: 7.8-3+deb12u1

Explanation: avoid prompts on upgrade due to logrotate configuration cleanup

Bug#1052227: mutter 43.8-0+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1052227 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: mutter
Version: 43.8-0+deb12u1

Explanation: new upstream stable release; fix the ability to drag libdecor 
windows by their title bar on touchscreens; fix flickering and rendering 
artifacts when using software rendering; improve GNOME Shell app grid 
performance by avoiding repainting monitors other than the one it is displayed 
on

Bug#1055421: roundcube: cross-site scripting (XSS) vulnerability in setting Content-Type/Content-Disposition for attachment preview/download

[Guilhem Moulin]

Source: roundcube
Version: 1.6.4+dfsg-1
Severity: important
Control: found -1 1.6.4+dfsg-1~deb12u1
Tags: security upstream

Roundcube webmail upstream has recently released 1.6.5 which fixes the
following vulnerability:

 * Fix cross-site scripting (XSS) vulnerability in setting
   Content-Type/Content-Disposition for attachment preview/download.
   
https://github.com/roundcube/roundcubemail/commit/81ac3c342a4f288deb275590895b52ec3785cf8a

AFAICT no CVE-ID has been published for this issue.
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1055380: kio-gdrive: Unable to log in to the account, probably due to the old version of the signon-ui library

[Jesse Rhodes]

Control: merge 1055380 1054919
thanks

This is a duplicate of #1054919 which has a workaround listed.

On Sun, Nov 5, 2023 at 4:39 AM trb  wrote:
>
> Package: kio-gdrive
> Version: 22.12.3-1
> Severity: important
> X-Debbugs-Cc: tere...@gmail.com
>
> Dear Maintainer,
> an attempt to log in to a Google account always fails. After entering your 
> Google account login, the process never proceeds to the password entry stage. 
> From what I found, this is probably related to an old version of the 
> signon-ui library - https://bugs.kde.org/show_bug.cgi?id=420280.
>
> Best regards
> Peter
>
>
> -- System Information:
> Debian Release: 12.2
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT)
> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 kio-gdrive depends on:
> ii  kaccounts-integration  4:22.12.3-1
> ii  kio5.103.0-1
> ii  libaccounts-qt5-1  1.16-2
> ii  libc6  2.36-9+deb12u3
> ii  libkaccounts2  4:22.12.3-1
> ii  libkf5coreaddons5  5.103.0-1
> ii  libkf5i18n55.103.0-1
> ii  libkf5kiocore5 5.103.0-1
> ii  libkf5kiogui5  5.103.0-1
> ii  libkf5kiowidgets5  5.103.0-1
> ii  libkf5notifications5   5.103.0-1
> ii  libkf5widgetsaddons5   5.103.0-1
> ii  libkpimgapicore5abi1 [libkpimgapicore5-22.12]  22.12.3-1
> ii  libkpimgapidrive5 [libkpimgapidrive5-22.12]22.12.3-1
> ii  libqt5core5a   5.15.8+dfsg-11
> ii  libqt5gui5 5.15.8+dfsg-11
> ii  libqt5widgets5 5.15.8+dfsg-11
> ii  libstdc++6 12.2.0-14
>
> kio-gdrive recommends no packages.
>
> kio-gdrive suggests no packages.
>
> -- no debconf information
>

Bug#1055420: libxi: Separate out documentation build

[Samuel Thibault]

Source: libxi
Version: 1.8-1
Severity: normal
Tags: patch

Hello,

libxi currently build-depends on w3m, which makes it part of a long
build dependency through imlib and whatnot image libraries. The w3m
dependency is actually only for building documentation. The attached
patch adds a nodoc build profile. This makes bootstraping a new Debian
port much easier.

Note that

chmod +x debian/libxi-dev.install

needs to be done to complete the patch.

Also, the patch is not working yet because the package has not been
converted to the quilt source format yet, and thus the +x is lost in the
.diff.gz format, but I guess there is no reason left for keeping using
the native source format?

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
--- debian/control.original 2023-11-05 02:54:27.0 +
+++ debian/control  2023-11-05 16:55:42.0 +
@@ -4,6 +4,7 @@
 Maintainer: Debian X Strike Force 
 Build-Depends:
  debhelper-compat (= 12),
+ dh-exec,
  quilt,
  x11proto-dev (>= 2021.5),
  libx11-dev (>= 2:1.4.99.1),
@@ -15,10 +16,10 @@
  quilt,
  xutils-dev (>= 1:7.6+2),
 # specs
- xmlto,
- xorg-sgml-doctools (>= 1:1.8),
- xsltproc,
- w3m,
+ xmlto ,
+ xorg-sgml-doctools (>= 1:1.8) ,
+ xsltproc ,
+ w3m ,
 Standards-Version: 4.5.0
 Vcs-Git: https://salsa.debian.org/xorg-team/lib/libxi.git
 Vcs-Browser: https://salsa.debian.org/xorg-team/lib/libxi
--- debian/rules.original   2023-11-05 02:54:35.0 +
+++ debian/rules2023-11-05 16:53:05.0 +
@@ -10,12 +10,18 @@
 # set this to the name of the main shlib's binary package
 PACKAGE = libxi6
 
+ifeq (,$(filter nodoc,$(DEB_BUILD_PROFILES)))
+DOC = --with-xmlto
+else
+DOC = --disable-specs
+endif
+
 %:
dh $@ --with quilt --builddirectory=build/
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   --with-xmlto \
+   $(DOC) \
--without-fop
 
 override_dh_install:
--- debian/libxi-dev.install.original   2023-11-05 16:54:25.0 +
+++ debian/libxi-dev.install2023-11-05 16:57:28.0 +
@@ -1,7 +1,8 @@
+#! /usr/bin/dh-exec
 usr/lib/*/libXi.a
 usr/lib/*/libXi.so
 usr/lib/*/pkgconfig/xi.pc
 usr/include/X11/extensions/
-usr/share/doc/libXi/*.html usr/share/doc/libxi-dev
-usr/share/doc/libXi/*.txt  usr/share/doc/libxi-dev
+ usr/share/doc/libXi/*.html usr/share/doc/libxi-dev
+ usr/share/doc/libXi/*.txt  usr/share/doc/libxi-dev
 usr/share/man/man3

Bug#1042837: Acknowledgement (signify-openbsd: Embedding signature in gz header does not work)

[Tomasz Buchert]

On 05/11/23 14:46, Nikolaus Rath wrote:
> Hi Thomas,
> 
> On Sun, 5 Nov 2023, at 14:19, Tomasz Buchert wrote:
> > On 01/08/23 17:15, Nikolaus Rath wrote:
> >> Using -x instead of -m when verifying gives "interesting" output:
> >> 
> >> $ signify-openbsd -Vz -p s3ql-5.0.pub -x signed.gz
> >> untrusted comment: verify with s3ql-5.0.pub
> >> RWSKPEtoJRYfrolP1xcoVCAxdIGvBp+I600+z5r4Ckcknx45J4pGrYvhlrWn6WTtwom7mTyjT7epM/oQyhfn/UbuKTR7pjN+0g0=
> >> date=2023-08-01T16:10:04Z
> >> key=s3ql-5.0.sec
> >> algorithm=SHA512/256
> >> blocksize=65536
> >> 
> >> 05b894ec8534324eda46e2c71b2e9cd8c3e6f89432d222d06949076bc5236998
> >> Ke2~⏎  
> >>  
> >> 
> >> This terminates with exit code 0... but somehow I'm not convinced that 
> >> signify did the right thing here.
> >> 
> >
> > I checked that signify puts the FCOMMENT section (from RFC) with 
> > the signature and a bunch of other things at the preamble of the
> > signed gz file. The comment ends just after what looks like SHA256,
> > which is then followed by the binary data. The binary data is
> > identical to the main compressed data of the original file.
> >
> > In fact, it seems that the verification of gz files actually just
> > passes through the whole file. The man page implies that:
> >
> >   Verify a gzip pipeline:
> >  $ ftp url | signify-openbsd -Vz -t arc | tar ztf -
> >
> > The behavior seems then intended, but maybe it's not documented enough?
> 
> Sorry, I don't quite follow. The behavior of printing binary garbage to 
> stdout is intended?
> 
> 
> Best,
> -Niko

Hey,

the "binary garbage" you see is actually the exact contents of the gz file for 
which you verify. See:

[ ~/test ] $ cat out.gz | signify-openbsd -Vz -p ~/.ssh/signify.pub | cat > x
[ ~/test ] $ diff x out.gz 

(i.e., out.gz and the output of signify are exactly the same)

This allows to use it cleanly in the shell pipelines as is shown in the manpage.

I think the request in this bug could be to have an option to verify the
signify-signed gz file WITHOUT printing out the gz file to stdout?

Does it make sense?

Tomasz


signature.asc
Description: PGP signature

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

[Adam D. Barratt]

On Sat, 2023-11-04 at 20:33 +0100, Markus Koschany wrote:
> Could you install the version of trapperkeeper-webserver-jetty9-
> clojure from Bullseye and reinstall the jetty9 security update and
> report back if this solves your problem?

Doing that directly doesn't "just work":

 libtrapperkeeper-webserver-jetty9-clojure : Depends: libkitchensink-clojure 
(>= 3.1.1-2) but 2.3.0-2 is to be installed
 Depends: 
libprismatic-schema-clojure (>= 1.1.12) but 1.1.6-1 is to be installed
 Depends: 
libpuppetlabs-i18n-clojure (>= 0.9.0-2) but 0.8.0-1 is to be installed
 Depends: libring-codec-clojure (>= 
1.1.2) but 1.0.1-1 is to be installed
 Depends: libssl-utils-clojure (>= 
3.1.0) but 0.8.3-2 is to be installed
 Depends: libtrapperkeeper-clojure 
(>= 3.1.0) but 1.5.2-2 is to be installed
 Depends: 
libtrapperkeeper-filesystem-watcher-clojure (>= 1.2.2-2) but it is not 
installable
 Depends: libordered-clojure but it 
is not installable

Adding a bullseye APT source ends up at "19 upgraded, 5 newly
installed".

Do you have an idea how simple rebuilding the bullseye package on
buster would be? I'm happy to try that in general, but I've not really
looked at the Java ecosystem in Debian much.

Regards,

Adam

Bug#1055345: git-buildpackage: Please document how to build against a package from experimental

[Guido Günther]

Hi Martin,
On Sat, Nov 04, 2023 at 04:43:10PM +0100, Martin Quinson wrote:
> Package: git-buildpackage
> Version: 0.9.32
> Severity: wishlist
> Tags: patch
> 
> Hello,
> 
> thanks a lot for this package, that very often saves my life when packaging.
> There is one thing however where gbp could be more helpful, it's when I have 
> to
> build my package against a build-depend that comes from experimental.
> 
> I finally found a way to do it, and I propose the following patch for the
> documentation for the next person looking for this information. I fully
> acknowledge that this documentation is somehow suboptimal, and that the gbp
> tool could be more helpful here, but the proposed documentation would already
> be great.

Thanks for taking the time to document this. Some minor nits below:

> 
> Again, thanks for this great tool and for your time.
> Mt
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (90, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.4.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 git-buildpackage depends on:
> ii  devscripts 2.23.6
> ii  git    1:2.40.1-1
> ii  man-db 2.11.2-3
> ii  python3    3.11.4-5+b1
> ii  python3-dateutil   2.8.2-3
> ii  python3-pkg-resources  68.1.2-1
> ii  python3-yaml   6.0.1-1
> ii  sensible-utils 0.0.20
> 
> Versions of packages git-buildpackage recommends:
> ii  cowbuilder    0.89
> ii  pbuilder  0.231
> ii  pristine-tar  1.50
> ii  python3-requests  2.31.0+dfsg-1
> 
> Versions of packages git-buildpackage suggests:
> ii  python3-notify2  0.3-5
> ii  sudo 1.9.14p2-1
> ii  unzip    6.0-28
> 
> -- no debconf information
> 

> ---
>  docs/chapters/special.xml |   25 +
>  1 file changed, 25 insertions(+)
> 
> Index: b/docs/chapters/special.xml
> ===
> --- a/docs/chapters/special.xml
> +++ b/docs/chapters/special.xml
> @@ -40,6 +40,31 @@
>  
>  
>  
> +
> +Using build-depends from experimental
> +

This should mention that one ought to use `gbp buildpackage
--git-pbuilder` (as that is not the default).

> +To build your package against a build-depends taken from experimental, 
> you first need
> +to configure your pbuilder. To that extend, add the following to
> +~/.pbuilderrc to instruct pbuilder to take build 
> depends from
> +experimental when they cannot be satisfied from unstable.
> +
> +
> +PBUILDERSATISFYDEPENDSCMD=/usr/lib/pbuilder/pbuilder-satisfydepends-experimental
> +

Wouldn't we want to make that conditional like:

if [ "$GBP_DIST" = "experimental" ]; then
echo "Using 'pbuilder-satisfydepends-experimental' for $GBP_DIST"

PBUILDERSATISFYDEPENDSCMD=/usr/lib/pbuilder/pbuilder-satisfydepends-experimental
fi

but I *think* this is even the default nowadays for building against 
experimental.

> +
> +You then need to add experimental to the apt configuration within the 
> chroot.
> +The simplest for that is to edit the config file from outside of the 
> chroot directly,
> +as follows:
> +
> +sudo bash -c "echo 'deb http://deb.debian.org/debian experimental main' >> 
> /var/cache/pbuilder/base.cow/etc/apt/sources.list"
> +

What about suggesting to bootstrap a new environment instead via:

   DIST=experimental git-pbuilder create 

This also handles adding experimental to /etc/apt/sources.list (no extra
setup needed). Maybe we can streamline things that way a bit?

Cheers,
 -- Guido

> +
> +Once everything is setup (and once you updated apt cache files with
> +git-pbuilder update), you can force the build of your 
> package against
> +a given package from experimental by specifying the relevant version in 
> the
> +debian/control.
> +
> +
>  
>  Importing NMUs
>  

Bug#1055419: bookworm-pu: package pcs/0.11.5-1+deb12u1

[Valentin Vidic]

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

[ Reason ]
Running the 'crm resource move' command results in a Python
stack trace due to missing arguments in a function call. The
bug was introduced in version 0.11.5 and fixed upstream in
0.11.6.

[ Impact ]
'crm resource move' command does not work correctly.

[ Tests ]
Package tests pass for the updated package and also manual
test confirm the move command works correctly now.

[ Risks ]
The code change is simple (adding the missing function argument),
so the risk should be low.

[ 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 ]
Function calls to tools.get_tmp_file() are replaced with
tools.get_tmp_file(None) to avoid the error:

TypeError: get_tmp_file() missing 1 required positional argument: 'data'


diff -Nru pcs-0.11.5/debian/changelog pcs-0.11.5/debian/changelog
--- pcs-0.11.5/debian/changelog 2023-03-03 08:57:59.0 +0100
+++ pcs-0.11.5/debian/changelog 2023-11-05 16:27:07.0 +0100
@@ -1,3 +1,9 @@
+pcs (0.11.5-1+deb12u1) bookworm; urgency=medium
+
+  * d/patches: add fix for resource move (Closes: #1042893)
+
+ -- Valentin Vidic   Sun, 05 Nov 2023 16:27:07 +0100
+
 pcs (0.11.5-1) unstable; urgency=medium
 
   * New upstream version 0.11.5
diff -Nru pcs-0.11.5/debian/patches/Fix-resource-move.patch 
pcs-0.11.5/debian/patches/Fix-resource-move.patch
--- pcs-0.11.5/debian/patches/Fix-resource-move.patch   1970-01-01 
01:00:00.0 +0100
+++ pcs-0.11.5/debian/patches/Fix-resource-move.patch   2023-11-05 
16:27:07.0 +0100
@@ -0,0 +1,25 @@
+--- a/pcs/lib/pacemaker/live.py
 b/pcs/lib/pacemaker/live.py
+@@ -384,7 +384,10 @@
+ string cib_xml -- CIB XML to simulate
+ """
+ try:
+-with tools.get_tmp_file() as new_cib_file, tools.get_tmp_file() as 
transitions_file:
++with (
++tools.get_tmp_file(None) as new_cib_file,
++tools.get_tmp_file(None) as transitions_file,
++):
+ cmd = [
+ __exec("crm_simulate"),
+ "--simulate",
+--- a/pcs_test/tools/custom_mock.py
 b/pcs_test/tools/custom_mock.py
+@@ -98,7 +98,7 @@
+ except StopIteration:
+ pass
+ 
+-def _mock_side_effect(self, data=None, binary=False):
++def _mock_side_effect(self, data, binary=False):
+ def _seek_callback(offset):
+ if offset != 0:
+ raise AssertionError(
diff -Nru pcs-0.11.5/debian/patches/series pcs-0.11.5/debian/patches/series
--- pcs-0.11.5/debian/patches/series1970-01-01 01:00:00.0 +0100
+++ pcs-0.11.5/debian/patches/series2023-11-05 16:27:07.0 +0100
@@ -0,0 +1 @@
+Fix-resource-move.patch

Bug#1039883: The issue impacts SSD disks as well

[Hervé Werner]

Hello

I'm sorry for the delay.

> Are you able to reliably preoeduce the issue and can bisect it to the 
> introducing commit?
I faced this issue on real data but I struggled to find a reliable scenario to 
reproduce it. Here is what I just came up with:
  sudo mkfs -t ext4 -O fast_commit,inline_data /dev/sdb
  sudo mount /dev/sdb /mnt/
  sudo install -d -o myuser /mnt/annex
  cd /mnt/annex
  git init && git annex init
  for i in {1..2}; do
for i in {1..1}; do
  dd if=/dev/urandom of=file-${i} bs=1K count=1 2>/dev/null
done
git annex add -J cpus . >/dev/null && git annex sync -J cpus && git annex 
fsck -J cpus >/dev/null
git rm * && git annex sync  && git annex dropunused all
  done

Then at some point the following error appears:
  EXT4-fs error (device sdb): ext4_map_blocks:577: inode #3942343: block 4: 
comm git-annex:w: lblock 1 mapped to illegal pblock 4 (length 1)

Some observations:
  - Contrary to what I implied in my first message, using the option 
inline_data alone doesn't seem to trigger the error.
  - Working with less than 10K files doesn't seem to trigger the error
  - Sometimes the commands just run fine that's why I run the whole thing twice
  - I also tried with various file size, in particular 1B, but it does not seem 
to have any impact
  - The disk I was using is a 5400RPM HDD

I'm running the kernel 6.5.0-3-amd64.
I'm also getting this issue on Debian stable's kernel (6.1.0-13-amd64) so I'm 
not aware of any working kernel version.

Regards
Hervé

Bug#1055418: systemtap: autopkgtest regression: Pass 4: compilation failed. [man error::pass4]

[Paul Gevers]

Source: systemtap
Version: 4.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since a couple 
of months. Can you please investigate the situation and fix it? I copied 
some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemtap/39374282/log.gz

223s /usr/share/systemtap/runtime/linux/print.c:367:46: error: ‘struct 
module’ has no member named ‘core_text_size’; did you mean 
‘kprobes_text_size’?
223s   367 |(unsigned long) 
(THIS_MODULE->core_text_size)/1024,

223s   |  ^~
223s 
/usr/src/linux-headers-6.5.0-3-common/include/linux/printk.h:427:33: 
note: in definition of macro ‘printk_index_wrap’
223s   427 | _p_func(_fmt, ##__VA_ARGS__); 
\

223s   | ^~~
223s /usr/share/systemtap/runtime/linux/print.c:348:9: note: in 
expansion of macro ‘printk’

223s   348 | printk(KERN_DEBUG
223s   | ^~
223s cc1: all warnings being treated as errors
223s make[1]: *** 
[/usr/src/linux-headers-6.5.0-3-common/scripts/Makefile.build:248: 
/tmp/stapUiwpzl/hello_src.o] Error 1
223s make: *** [/usr/src/linux-headers-6.5.0-3-common/Makefile:2059: 
/tmp/stapUiwpzl] Error 2

223s WARNING: kbuild exited with status: 2
223s Pass 4: compiled C into "hello.ko" in 35730usr/7150sys/22477real ms.
223s Pass 4: compilation failed.  [man error::pass4]
223s Tip: /usr/share/doc/systemtap/README.Debian should help you get 
started.

224s autopkgtest [08:12:49]: test build-hello: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055417: ITP: golang-github-tdewolff-argp -- GNU command line argument parser (Go library)

[Anthony Fok]

Package: wnpp
Severity: wishlist
Owner: Anthony Fok 

* Package name: golang-github-tdewolff-argp
  Version : 0.0~git20231030.fa6c548-1
  Upstream Author : Taco de Wolff
* URL : https://github.com/tdewolff/argp
* License : Expat
  Programming Lang: Go
  Description : GNU command line argument parser (Go library)
 The argp Go package provides a command-line argument parser
 following the GNU standard.
 .
   ./test -vo out.png --size 256 input.txt
 .
 with the following features:
 .
  * build-in help (-h and --help) message
  * scan arguments into struct fields with configuration in tags
  * scan into composite field types (arrays, slices, structs)
  * allow for nested sub commands
 .
 GNU command line argument rules:
 .
  * arguments are options when they begin with a hyphen -
  * multiple options can be combined: -abc is the same as -a -b -c
  * long options start with two hyphens: --abc is one option
  * option names are alphanumeric characters
  * options can have a value: -a 1 means that a has value 1
  * option values can be separated by a space, equal sign, or nothing: -a1 -
a=1 -a 1 are all equal
  * options and non-options can be interleaved
  * the argument -- terminates all options so that all following arguments
are treated as non-options
  * a single - argument is a non-option usually used to mean standard in or
out streams
  * options may be specified multiple times, only the last one determines
its value
  * options can have multiple values: -a 1 2 3 means that a is an
array/slice/struct of three numbers of value [1,2,3]
 .
 See also github.com/tdewolff/prompt for a command-line prompter.

Reason for packaging: Needed by golang-github-tdewolff-minify >= 2.20.5

Bug#1054433: node-puppeteer: website is build with Docusaurus not packaged for debian

[Kentaro HAYASHI]

Control: severity -1 important

Hi,

It seems that already repacked.

Surely regenerating omitted content (website and docs) may be
recommended
in the future, so marked as important.

Regards,

Bug#1055416: nodejs: Testsuite failure in test-crypto-dh since OpenSSL 3.0.12/3.1.4.

[Sebastian Andrzej Siewior]

Package: nodejs
Version: 18.13.0+dfsg1-1
Severity: Serious
Tags: patch
control: affects -1 src:openssl

OpenSSL 3.0.12 and 3.1.4 changed the error response resulting a failure
in test parallel/test-crypto-dh.
This has been addressed in the master branch in commit
8eea2d3709090 ("test: fix crypto-dh error message for OpenSSL 3.x")

An additional problem is that the check compares OpenSSL from compile
time not runtime. Which means I couldn't test upstream's version as-is.
The attached version takes always the 3.0.12/3.1.4 variant. Given that
the new upload picks up the new OpenSSL vesion then it should be okay to
apply the original commit.

Sebastian
From: Sebastian Andrzej Siewior 
Date: Sun, 5 Nov 2023 13:08:23 +0100
Subject: [PATCH] test: Alter error message.

This is variant of upstream's commit
	8eea2d3709090 ("test: fix crypto-dh error message for OpenSSL 3.x")

It does not work as-is in Debian because the testsuite may run against a
different version than the compiled once and the constant version check
does not apply.

Signed-off-by: Sebastian Andrzej Siewior 
---
 test/parallel/test-crypto-dh.js  |   4 +---
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/test/parallel/test-crypto-dh.js b/test/parallel/test-crypto-dh.js
index 18721fcf289e..506780db4cbe 100644
--- a/test/parallel/test-crypto-dh.js
+++ b/test/parallel/test-crypto-dh.js
@@ -165,9 +165,7 @@ if (common.hasOpenSSL3) {
 
 assert.throws(() => {
   dh3.computeSecret('');
-}, { message: common.hasOpenSSL3 ?
-  'error:02800080:Diffie-Hellman routines::invalid secret' :
-  'Supplied key is too small' });
+}, { message: 'Supplied key is too small' });
 
 // Invalid test: curve argument is undefined
 assert.throws(
-- 
2.42.0

Bug#1053575: RFS: ruby-mdl/0.13.0-1 -- Markdown lint tool

[Leandro Cunha]

I remember that I opened an RFS as a bug for a Ruby package and the
Kanashiro caught my attention.
I had forgotten that the recommendation is to open in mailing list of the
team.

Em dom., 5 de nov. de 2023 10:39, Norwid Behrnd 
escreveu:

> On Sat, 4 Nov 2023 19:02:02 +0100
> Tobias Frost  wrote:
>
> > Am Wed, Nov 01, 2023 at 11:55:29PM +0100 schrieb Norwid Behrnd:
> >
> > Your transitional package needs to Depends: on the new package.
> >
>
> Thank you for spotting my omission.  The current upload to
>
> https://mentors.debian.net/package/ruby-mdl/#upload-5
>
> by time stamp 2023-11-05 13:24 now equally mentions `markdownlint` as
> dependency for the transitional dummy package `ruby-mdl`.
>
>

Bug#1037440: kitty: Integrating golang parts of the package

[James McCoy]

Switched to the "New upstream" bug, since that seems more relevant.

On Sun, Nov 05, 2023 at 02:09:20AM +0530, Nilesh Patra wrote:
> On Sat, Nov 04, 2023 at 02:25:47PM -0400, James McCoy wrote:
> > We can try that for the now, but it would probably be good for someone
> > else to eventually take over primary maintenance of the package.
> > 
> > https://salsa.debian.org/debian/kitty/-/merge_requests/3 is what I have
> > so far for the new upstream version.  Feel free to hack around with
> > that.
> 
> Cool. I have one question though: how do you sync the repo to new
> upstream? It does not seem to use gbp layout so wanted to know how
> exactly you're tracking/pulling the commits?

I just merge the upstream tags directly and use “git deborig” to produce
the orig tarball (c.f. dgit-maint-merge(7)).

> OTOH, I did take a look at the errors and I see two ways. Either patch
> out all the go build related code and use debian's go build toolchain
> (which takes care of a bunch of things) or hack around the way upstream
> builds to somehow fit out usecase (this is consuming quite some cycles).
> Definitely complicated since a bunch of different functionalities have
> been mixed with different languages.

The former is fine with me.  I took a quick look at what Fedora is
doing, and it looks like they just patch setup.py to return from
build_static_kittens() just before the “go build -v” line.

Adding a patch for that and then adapting the rest of the Debian side of
the build to do it seems reasonable.

This sounds like the packaging will be carrying around a patch for a
while, so I would normally switch to dgit-maint-debrebase(7) here.
However, maybe it's better to align with gbp if that's what you're more
comfortable with.

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

Bug#1055415: Wrong order for the `resolve' option in nsswitch.conf

[Sylvain Garrigues]

Package: libnss-resolve
Version: 252.17-1~deb12u1
X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org

The debian postinstall script for libnss-resolve inserts `resolve' in
the `hosts:' line of /etc/nsswitch.conf before `dns', therefore after
`files'. This does not seem optimal, as per `man nss-resolve', which
reads:
Specifically, it is recommended to place "resolve" early in
/etc/nsswitch.conf's "hosts:" line. It should be before the "files"
entry, since systemd-resolved supports /etc/hosts internally, but with
caching.

Bug#1042837: Acknowledgement (signify-openbsd: Embedding signature in gz header does not work)

[Nikolaus Rath]

Hi Thomas,

On Sun, 5 Nov 2023, at 14:19, Tomasz Buchert wrote:
> On 01/08/23 17:15, Nikolaus Rath wrote:
>> Using -x instead of -m when verifying gives "interesting" output:
>> 
>> $ signify-openbsd -Vz -p s3ql-5.0.pub -x signed.gz
>> untrusted comment: verify with s3ql-5.0.pub
>> RWSKPEtoJRYfrolP1xcoVCAxdIGvBp+I600+z5r4Ckcknx45J4pGrYvhlrWn6WTtwom7mTyjT7epM/oQyhfn/UbuKTR7pjN+0g0=
>> date=2023-08-01T16:10:04Z
>> key=s3ql-5.0.sec
>> algorithm=SHA512/256
>> blocksize=65536
>> 
>> 05b894ec8534324eda46e2c71b2e9cd8c3e6f89432d222d06949076bc5236998
>> Ke2~⏎
>>
>> 
>> This terminates with exit code 0... but somehow I'm not convinced that 
>> signify did the right thing here.
>> 
>
> I checked that signify puts the FCOMMENT section (from RFC) with 
> the signature and a bunch of other things at the preamble of the
> signed gz file. The comment ends just after what looks like SHA256,
> which is then followed by the binary data. The binary data is
> identical to the main compressed data of the original file.
>
> In fact, it seems that the verification of gz files actually just
> passes through the whole file. The man page implies that:
>
>   Verify a gzip pipeline:
>  $ ftp url | signify-openbsd -Vz -t arc | tar ztf -
>
> The behavior seems then intended, but maybe it's not documented enough?

Sorry, I don't quite follow. The behavior of printing binary garbage to stdout 
is intended?


Best,
-Niko

Bug#1054401: bookworm-pu: package nagios-plugins-contrib/42.20230308+deb12u1

[Jan Wagner]

Hi there,

Am 23.10.23 um 19:43 schrieb Holger Levsen:

On Mon, Oct 23, 2023 at 01:19:25PM +0200, Jan Wagner wrote:

[ Reason ]
As reported in #1033791, check_running_kernel fails to find version on
bookworm/(arm64|armhf).

[ Impact ]
check_running_kernel doesn't work on arm64 and armhf as expected, this is a
regression.

[ Tests ]
The patch was verified to work in #1033791

I've rebuild the package on arm64 and can confirm 
/usr/lib/nagios/plugins/check_running_kernel
now works on those arm64 systems where the version currently in bookworm does
not work.


is there anything I can do to get the package into bookworm?

Cheers, Jan

Bug#1055414: bedtools: FTBFS on i386: "intersect" tool failure

[Étienne Mollier]

Source: bedtools
Version: 2.31.0+dfsg-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

Dear Maintainer,

While making a routine metadata update on a Debian patch against
bedtools, Salsa CI caught a build failure on i386[1] which I
could reproduce multiple times in sid and in testing with the
unmodified version of the package.

[1]: https://salsa.debian.org/med-team/bedtools/-/jobs/4891166

The relevant part of the build log shows the following
differences in the test suite of the "intersect" tool:

intersect.t22.p...0a1
> chr1  0   30  one_block_one_exon_30bp 40  -   0   
30  0,0,0   1   30, 0,  chr1  0  100 exon1   1  
 +   30
fail
intersect.t22.q...1a2
> chr1  80  110 one_block_one_exon_20bp 40  -   80  
110 0,0,0   1   30, 0,  chr1  0  100 exon1   1  
 +   20
fail

The tests are started from test/intersect/test-intersect.sh.
I'm not sure what change caused the build failure to appear.
The issue is not affecting amd64, nor armhf, which suggest
something very i386 specific.  I have not checked closely the
other CPU architectures yet.  The relevant upstream change that
introduced this code begins to date back from quite some time
ago[2] and the package builds with -ffloat-store for a while, so
this may be caused by a dependency, or a compiler change.

[2]: 
https://github.com/arq5x/bedtools2/commit/9d22ccb24f258553b0eff31e689b09563227331b

Hope this helps pinpointing what's up,
Étienne.


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

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

-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/7, please excuse my verbosity
   `-on air: Condition Red - Let It All Come Out


signature.asc
Description: PGP signature

Bug#1055413: Upgrade ignores /etc/unsupported-skip-usrmerge-conversion

[Chris Carr]

Package: usr-is-merged
Version: 38
Severity: normal

Dear Maintainer,



   * What led up to the situation?



Upgrading my schroot



   * What exactly did you do (or not do) that was effective (or

 ineffective)?



sudo sbuild-update -udcar -u



   * What was the outcome of this action?



Preparing to unpack .../usr-is-merged_38_all.deb ...





**

*

*The usr-is-merged package cannot be installed because this system does

*not have a merged /usr.

*

*Please install the usrmerge package to convert this system to merged-/usr.

*

*For more information please read https://wiki.debian.org/UsrMerge.

*

**





dpkg: error processing archive
/var/cache/apt/archives/usr-is-merged_38_all.deb (--unpack):

new usr-is-merged package pre-installation script subprocess returned error
exit status 1

Errors were encountered while processing:

/var/cache/apt/archives/usr-is-merged_38_all.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)

E: apt-get dist-upgrade failed





   * What outcome did you expect instead?



A silent upgrade of usr-is-merged from v37 to v38.



I have been using sbuild and schroot for ~3 months and this is the first
time I have had this error – so I assume it is related to the new v38
package. My schroot contains the file
/etc/unsupported-skip-usrmerge-conversion – presumably because it uses
overlayfs. This prevents me installing usrmerge manually and fixing the
broken upgrade. I assume what is supposed to happen is that usr-is-merged
is supposed to upgrade silently, having clocked the /etc/unsupported- file
and accepted that this system is not going to do the merge.



Grateful for any tips that will allow me to resume using sbuild and
schroot.



Thanks



Chris





-- System Information:

Debian Release: trixie/sid

  APT prefers unstable

  APT policy: (500, 'unstable')

merged-usr: no

Architecture: amd64 (x86_64)



Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)

Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to C.UTF-8), LANGUAGE not set

Shell: /bin/sh linked to /bin/dash

Init: unable to detect



-- no debconf information

Bug#1042837: Acknowledgement (signify-openbsd: Embedding signature in gz header does not work)

[Tomasz Buchert]

On 01/08/23 17:15, Nikolaus Rath wrote:
> Using -x instead of -m when verifying gives "interesting" output:
> 
> $ signify-openbsd -Vz -p s3ql-5.0.pub -x signed.gz
> untrusted comment: verify with s3ql-5.0.pub
> RWSKPEtoJRYfrolP1xcoVCAxdIGvBp+I600+z5r4Ckcknx45J4pGrYvhlrWn6WTtwom7mTyjT7epM/oQyhfn/UbuKTR7pjN+0g0=
> date=2023-08-01T16:10:04Z
> key=s3ql-5.0.sec
> algorithm=SHA512/256
> blocksize=65536
> 
> 05b894ec8534324eda46e2c71b2e9cd8c3e6f89432d222d06949076bc5236998
> Ke2~⏎ 
>   
> 
> This terminates with exit code 0... but somehow I'm not convinced that 
> signify did the right thing here.
> 
> Best,
> -Nikolaus
> 

Hey Nikolaus,

I checked that signify puts the FCOMMENT section (from RFC) with 
the signature and a bunch of other things at the preamble of the
signed gz file. The comment ends just after what looks like SHA256,
which is then followed by the binary data. The binary data is
identical to the main compressed data of the original file.

In fact, it seems that the verification of gz files actually just
passes through the whole file. The man page implies that:

  Verify a gzip pipeline:
 $ ftp url | signify-openbsd -Vz -t arc | tar ztf -

The behavior seems then intended, but maybe it's not documented enough?

Cheers,
Tomasz

Bug#1055412: xorg-server: Fix hurd-amd64 build

[Samuel Thibault]

Source: xorg-server
Version: 2:21.1.9-1
Severity: important
Tags: patch

Hello,

hurd-amd64 has the same constraint as hurd-i386, could you please apply
the attached patch?

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-05 10:38:47.0 +
+++ debian/control  2023-11-05 10:38:52.0 +
@@ -25,7 +25,7 @@
  libudev-dev (>= 151-3) [linux-any],
  libselinux1-dev (>= 2.0.80) [linux-any],
  libaudit-dev [linux-any],
- libdrm-dev (>= 2.4.107-5~) [!hurd-i386],
+ libdrm-dev (>= 2.4.107-5~) [!hurd-any],
  libgl1-mesa-dev (>= 9.2),
  mesa-common-dev,
  libunwind-dev [amd64 arm64 armel armhf hppa i386 ia64 mips64 mips64el mipsel 
powerpc powerpcspe ppc64 ppc64el sh4],
@@ -43,7 +43,7 @@
  libxfixes-dev (>= 1:3.0.0),
  libxv-dev,
  libxinerama-dev,
- libxshmfence-dev (>= 1.1) [!hurd-i386],
+ libxshmfence-dev (>= 1.1) [!hurd-any],
 # glamor
  libepoxy-dev [linux-any kfreebsd-any],
  libegl1-mesa-dev [linux-any kfreebsd-any],

Bug#1055411: kubernetes: Verison 1.20 has reached EOL (maintenance support)

[Reinhard Tartler]

Source: kubernetes
Severity: important
X-Debbugs-Cc: debian-rele...@lists.debian.org

Dear maintainer,

The version of kubectl as currently packaged in Debian has reached EOL.

Looking at https://endoflife.date/kubernetes, the date for the maintenance
period expiered on 28 Feb 2022, which is way beyond a full year.

I don't think such old packages should be in the next stable debian release,
but I'll leave it to the release team about deciding on that.

Please upgrade to a newer version. Also, please consider commenting on the
many existing open bugs on the package


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

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

Bug#1055410: RFS: scite/5.3.9-1 -- Lightweight GTK-based programming editor

[Andreas Rönnquist]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "scite":
(I am a DD, but I don't have access to my gpg-key currently, I am
working on getting signatures on a new key).

 * Package name : scite
   Version  : 5.3.9-1
   Upstream contact : Neil Hodgson 
 * URL  : https://scintilla.org/SciTE.html
 * License  : scintilla, Expat, BSL-1.0, LGPL-2.1
 * Vcs  : https://salsa.debian.org/debian/scite
   Section  : editors

The source builds the following binary packages:

  scite - Lightweight GTK-based programming editor

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/s/scite/scite_5.3.9-1.dsc

Changes since the last upload:

 scite (5.3.9-1) unstable; urgency=medium
 .
   * New upstream version 5.3.9

Regards,
-- 
  Andreas Rönnquist
gus...@debian.org

Bug#1055409: /usr/bin/dpkg-deb: dpkg-deb goes defunct and has to be killed during apt dist-upgrade

[Simon John]

Package: dpkg
Version: 1.22.1
Severity: important
File: /usr/bin/dpkg-deb

Dear Maintainer,

3 times in the last month or so I have had apt dist-upgrade stall.

The culprit appears to be dpkg-deb which goes defunct. Once I kill it, 
the transaction seems to continue although I have to run "apt-get -f 
install" or "dpkg reconfigure -a" to finish it.


It appears to be at the unpack stage where we see the problem.

Another Sid user on social media also has a quite powerful machine (we 
both have 32 cores, nvme and 64gb+ ecc ram) and has the same problem, so 
maybe its a threading thing? Obviously not a memory/disk issue.


Logs from today's occurrence:

# ps auxw|grep dpkg
root 1324970 91.0  0.2 151484 145108 pts/2   Rs+  13:04   6:12
/usr/bin/dpkg --status-fd 25 --no-triggers --unpack --auto-deconfigure
--recursive /tmp/apt-dpkg-install-ilDw1k
root 1328162  0.0  0.0   7364  2048 pts/2S+   13:08   0:00 
dpkg-deb --fsys-tarfile 
/tmp/apt-dpkg-install-ilDw1k/081-libgtk-4-doc_4.12.3+ds-2_all.deb
root 1328163  0.0  0.0  0 0 pts/2Z+   13:08   0:00 
[dpkg-deb]


root 1328164  0.3  0.1 153632 115056 pts/2   Sl+  13:08   0:00 
dpkg-deb --fsys-tarfile 
/tmp/apt-dpkg-install-ilDw1k/081-libgtk-4-doc_4.12.3+ds-2_all.deb

simon1329047  0.0  0.0   6348  2048 pts/3S+   13:11   0:00 grep
--color=auto dpkg

"pkill dpkg-deb" resulted in:

dpkg: error processing archive /tmp/apt-dpkg-install-
ilDw1k/081-libgtk-4-doc_4.12.3+ds-2_all.deb (--unpack):
 dpkg-deb --fsys-tarfile subprocess was killed by signal (Terminated)

For the rest of the dist-upgrade i keep seeing defunct dpkg-debs:

# ps auxw|grep defunct
root 1331212  0.0  0.0  0 0 pts/2Z+   13:14   0:00 
[dpkg-deb]


root 1331276  0.0  0.0   6348  2048 pts/3S+   13:14   0:00 grep 
defunct


killing them off seems to just spawn a new instance:

# kill -9 1331212
-bash: kill: (1331212) - No such process

# ps auxw|grep defunct
root 1331368  0.0  0.0  0 0 pts/2Z+   13:14   0:00 
[dpkg-deb]


root 1331426  0.0  0.0   6348  2048 pts/3S+   13:14   0:00 grep 
defunct


At the end of the operation i get:

Errors were encountered while processing:
 /tmp/apt-dpkg-install-ilDw1k/081-libgtk-4-doc_4.12.3+ds-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish

"apt-get -f install" allows the transaction to complete.

I had same problem before with: 
/tmp/apt-dpkg-install-PdxOu1/1-texlive-fonts-
extra_2023.20231007-1_all.deb and another package I can't quite remember 
before

that.



-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

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

Kernel: Linux 6.5.0-3-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.37-12
ii  liblzma5 5.4.4-0.1
ii  libmd0   1.1.0-1
ii  libselinux1  3.5-1
ii  libzstd1 1.5.5+dfsg2-2
ii  tar  1.34+dfsg-1.2
ii  zlib1g   1:1.2.13.dfsg-3

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.7.6
pn  debsig-verify  

-- no debconf information

--
Simon John

Bug#873186: please drop transitional package gnupg2

[Andreas Metzler]

On 2023-11-04 Bastian Germann  wrote:
[...]
> Please also drop gpgv2, which can be done now because the only reverse
> dependency only has an alternative dependency on it.

I have done this in debian/experimental GIT.

cu Andreas

Bug#1053575: RFS: ruby-mdl/0.13.0-1 -- Markdown lint tool

[Norwid Behrnd]

On Sat, 4 Nov 2023 19:02:02 +0100
Tobias Frost  wrote:

> Am Wed, Nov 01, 2023 at 11:55:29PM +0100 schrieb Norwid Behrnd:
> 
> Your transitional package needs to Depends: on the new package.
> 

Thank you for spotting my omission.  The current upload to

https://mentors.debian.net/package/ruby-mdl/#upload-5

by time stamp 2023-11-05 13:24 now equally mentions `markdownlint` as
dependency for the transitional dummy package `ruby-mdl`.

Bug#873186: please drop transitional package gnupg2

[Andreas Metzler]

Control: block -1 by 1055395 1055397 1055398 1055399 1055400 1055401 1055402 
1055403 1055404 1055405 1055406 1055407

On 2017-08-25 Holger Levsen  wrote:
> Package: gnupg2
> Version: 2.1.18-6
> Severity: normal
> user: qa.debian@packages.debian.org
> usertags: transitional

> Please drop transitional package gnupg2 for Buster, as it has been released 
> with Stretch.

> Thanks for maintaining gnupg2!

Hello,

This has to wait, I have just submitted bugs against rdeps.

https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gnupg2-rdep;users=pkg-gnupg-ma...@lists.alioth.debian.org

cu Andreas

Bug#1055222: fuse: backport unprivileged usage via /dev/fd/N to support usage in namespaces

[GCS]

Hi Helmut,

On Thu, Nov 2, 2023 at 12:15 PM Helmut Grohne  wrote:
> I have a slightly unusual request. I know libfuse 2.x is a legacy in
> maintenance mode slated for removal eventually. Unfortunately, 2/3 of
> fuse users still use the 2.x branch so it seems like we will have to
> support it a bit longer than expected.
 I think distributions should do the opposite, somehow enforce
projects to migrate to the new, supported FUSE version. Basically it
is deprecated since 2018 and as 2024 is approaching it means for six
years.

> Unfortunately, this currently requires fuse >= 3.3 and e.g. fuse2fs from
> e2fsprogs still uses fuse 2.x. Last time Ted Ts'o was inquired about
> porting to 3.x, he was unenthusiastic and when I spent a look, it is
> quite non-trivial as the API changed a lot. It's not just fuse2fs that
> is affected but still 2/3 of drivers.
[...]
> So I think we should backport this into fuse 2.x. This is not to say
> that we should stop porting drivers to the 3.x API. It also slightly
> improves compatibility between 2.x and 3.x, so that seems like a sane
> trade-off to me. Do you agree?
 Yes, it makes upstreams more easily staying with the FUSE 2 API.
Making the switch to the FUSE 3 API more difficult. But OK, let it go.
I'm preparing the upload.

Regards,
Laszlo/GCS

Bug#1055407: python3-securesystemslib: recommends transition package gnupg2

[Andreas Metzler]

Package: python3-securesystemslib
Version: 0.26.0-1
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package recommends gnupg2 which has been a transitional package
depending on gnupg since 2016. Please refer to gnupg instead.

cu Andreas

Bug#1055406: pass-extension-tail: Depends on transition package gnupg2

[Andreas Metzler]

Package: pass-extension-tail
Version: 1.1.1-2.1
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055405: openstack-cluster-installer-utils: Depends on transition package gnupg2

[Andreas Metzler]

Package: openstack-cluster-installer-utils
Version: 42.3.1
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055403: neurodebian-archive-keyring: Depends on transition package gnupg2

[Andreas Metzler]

Package: neurodebian-archive-keyring
Version: 0.42.1
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055404: obs-server: Depends on transition package gnupg2

[Andreas Metzler]

Package: obs-server
Version: 2.9.4-9
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055402: mandos: Depends on transition package gnupg2

[Andreas Metzler]

Package: mandos
Version: 1.8.16-1
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055399: gnupg-pkcs11-scd: suggests transition package gnupg2

[Andreas Metzler]

Package: gnupg-pkcs11-scd
Version: 0.10.0-2
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package suggests gnupg2 which has been a transitional package
depending on gnupg since 2016. Please refer to gnupg instead.

cu Andreas

Bug#1055401: in-toto: recommends transition package gnupg2

[Andreas Metzler]

Package: in-toto
Version: 1.3.1-1
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package recommends gnupg2 which has been a transitional package
depending on gnupg since 2016. Please refer to gnupg instead.

cu Andreas

Bug#1055400: gopass: Depends on transition package gnupg2

[Andreas Metzler]

Package: gopass
Version: 1.5.0-1
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055398: debdelta: Depends on transition package gnupg2

[Andreas Metzler]

Package: debdelta
Version: 0.67
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055396: libxaw: Separate out documentation build

[Samuel Thibault]

Source: libxaw
Version: 2:1.0.14-1
Severity: normal
Tags: patch

Hello,

libxaw currently build-depends on w3m, which makes it part of a long
build dependency through imlib and whatnot image libraries. The w3m
dependency is actually only for building documentation, which is already
separated into an arch:all binary package. The attached patch completes
the separation by separating out the build dependencies. This makes
bootstraping a new Debian port much easier.

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/control.original 2023-11-05 13:00:42.0 +
+++ debian/control  2023-11-05 13:00:47.0 +
@@ -14,7 +14,7 @@
  quilt,
  dpkg-dev (>= 1.13.19),
  xutils-dev (>= 1:7.5+4),
-# specs:
+Build-Depends-Indep:
  xmlto, xorg-sgml-doctools (>= 1:1.5), w3m,
 Standards-Version: 4.6.0
 Vcs-Git: https://salsa.debian.org/xorg-team/lib/libxaw.git
--- debian/rules.original   2023-11-05 13:01:47.0 +
+++ debian/rules2023-11-05 13:02:06.0 +
@@ -15,11 +15,12 @@
 docflags = --enable-specs
 
 override_dh_auto_configure-arch: docflags = --disable-specs
+override_dh_auto_configure-indep: docflags = --with-xmlto
 override_dh_auto_configure-arch override_dh_auto_configure-indep:
dh_auto_configure -- \
--docdir=\$${datadir}/doc/libxaw7-dev \
--disable-xaw6 \
-   --with-xmlto --without-fop \
+   --without-fop \
--disable-silent-rules \
$(docflags)
 

Bug#1055397: apt-transport-in-toto: Depends on transition package gnupg2

[Andreas Metzler]

Package: apt-transport-in-toto
Version: 0.1.1-3
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055395: acetoneiso: Depends on transition package gnupg2

[Andreas Metzler]

Package: acetoneiso
Version: 2.4-4
Severity: normal
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gnupg2-rdep

Hello,

this package depends on gnupg2 which has been a transitional package
depending on gnupg since 2016. Please depend on gnupg instead.

cu Andreas

Bug#1055394: src:python-pymemcache: fails to migrate to testing for too long: autopkgtest regression on 32 bits

[Paul Gevers]

Source: python-pymemcache
Version: 3.5.2-2
Severity: serious
Control: close -1 4.0.0-5
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:python-pymemcache has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug. The version in 
unstable fails its own autopkgtest on 32 bit architectures: armel, armhf 
and i386. armhf and i386 also fail on reproducible-builds.org with the 
same test error.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=python-pymemcache



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055393: undertime: autopkgtest regression: 'NoneType' object has no attribute 'utcoffset'

[Paul Gevers]

Source: undertime
Version: 3.2.0
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/u/undertime/39061593/log.gz

 31s **
 31s File "/usr/bin/undertime", line 1079, in __main__.uniq_zones
 31s Failed example:
 31s list(uniq_zones(zones, now))
 31s Exception raised:
 31s Traceback (most recent call last):
 31s   File "/usr/lib/python3.11/doctest.py", line 1351, in __run
 31s exec(compile(example.source, filename, "single",
 31s   File "", line 1, in 
 31s list(uniq_zones(zones, now))
 31s   File "/usr/bin/undertime", line 1086, in uniq_zones
 31s offset = zone.utcoffset(now)
 31s  ^^
 31s AttributeError: 'NoneType' object has no attribute 'utcoffset'
 31s **


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found

[Paul Gevers]

Source: wasmedge
Version: 0.13.4+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/w/wasmedge/39560218/log.gz

140s autopkgtest [15:12:57]: test embed-cxx: [---
140s 1..4
140s not ok 1 build fibonacci.cpp to wasm
140s # (in test file debian/tests/embed-cxx, line 12)
140s #   `clang++ --target=wasm32-wasi -o fibonacci.wasm 
-mexec-model=reactor script/fibonacci.cpp' failed

140s # In file included from script/fibonacci.cpp:1:
140s # script/fibonacci.h:3:10: fatal error: 'cstdint' file not found
140s # #include 
140s #  ^
140s # 1 error generated.
140s ok 2 build fibonacci/cpp to native
141s ok 3 build embed_cxx
141s not ok 4 run embed_cxx and test for valid output
141s # (in test file debian/tests/embed-cxx, line 27)
141s #   `assert_line --index 2 --partial "3524578"' failed
141s #
141s # -- line does not contain substring --
141s # index : 2
141s # substring : 3524578
141s # line  : [2023-11-04 15:12:58.648] [error] loading failed: 
invalid path, Code: 0x20

141s # --
141s #
141s autopkgtest [15:12:58]: test embed-cxx: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055391: willow: autopkgtest regression: test_save_webp_quality

[Paul Gevers]

Source: willow
Version: 1.6.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it recently started
to fail in testing.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/w/willow/39598331/log.gz

 44s autopkgtest [12:34:41]: test runtests: [---
 55s 
s...sssx..x.x...s...x.sssxxx.x.x.s.s..x..x.ss..F...

 55s ==
 55s FAIL: test_save_webp_quality 
(tests.test_wand.TestWandOperations.test_save_webp_quality)

 55s --
 55s Traceback (most recent call last):
 55s   File 
"/tmp/autopkgtest-lxc.exbm9v5i/downtmp/autopkgtest_tmp/tests/test_wand.py", 
line 333, in test_save_webp_quality

 55s self.assertTrue(low_quality.f.tell() < high_quality.f.tell())
 55s AssertionError: False is not true
 55s
 55s --
 55s Ran 219 tests in 10.791s
 55s
 55s FAILED (failures=1, skipped=28, expected failures=11)
 56s autopkgtest [12:34:53]: test runtests: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055353: Debian installer not setting locale in Trixie daily builds

[Brandon Werner]

On Sat, Nov 4, 2023, at 2:27 PM, Brandon Werner wrote:
> 
> 
> Hi,
> After installing via the daily images, my locale isn't set. I took a brief 
> look, and my best guess is the trouble is being caused in the file 
> post-base-installer.d/05localechooser. There, I noticed
> "DESTFILE="/target/etc/default/locale"".
> I believe this file was retired recently in Debian.
I tried a reinstall, changing the above line to
"DESTFILE="/target/etc/locale.conf""
in the installer after I booted the daily netinst, and my locale was set in the 
installed system