Bug#945092: Security: tcpxtract crash (heap-buffer-overflow) on Buster/Stretch/Jessie

[Vladimir Petko]

Dear Maintainers,

It seems that the crash was caused by the uninitialized pointer
'srch_machine'. The code checks it for NULL before initializing it
properly. Since the pointer was not initialized to NULL occasionally
the initialization did not happen and the code tried to access
uninitialized memory.

I was wondering if the attached patch could be accepted as a solution
for this issue?

Best Regards,
 Vladimir.


tcpxtract.debdiff
Description: Binary data

Bug#1068136: Bug#1069368: Updating golang-github-golang-protobuf-1-5 to fix FTBFS

[Anthony Fok]

On Sun, Apr 21, 2024 at 10:03 AM Mathias Gibbens  wrote:
>
> On Sat, 2024-04-20 at 22:40 +0800, Shengjing Zhu wrote:
> > On Sat, Apr 20, 2024 at 10:28 PM Mathias Gibbens  wrote:
> > >
> > > Hi Anthony,
> > >
> > >   A few weeks ago you uploaded a new version of golang-google-protobuf
> > > to unstable which caused a FTBFS in golang-github-golang-protobuf-1-5
> > > v1.5.3 [1,2,3]. This has been blocking the transition of various golang
> > > packages from unstable to testing.
> > >
> > >   I've verified that v1.5.4 of golang-github-golang-protobuf-1-5 builds
> > > fine on my amd64 system. `build-rdeps golang-github-golang-protobuf-1-
> > > 5-dev` identifies 219 rdeps in main, so I haven't kicked off a `ratt`
> > > run testing for any build regressions with the newer version yet.
> > >
> >
> > This is a known regression in 1.5.3, see
> > https://github.com/golang/protobuf/issues/1596#issuecomment-1981208282
>
>   Since that appears to be the only change in v1.5.4, would there be
> any concerns with uploading that version to unstable? This breakage is
> starting to cause FTBFS bugs to be filed against affected packages,
> such as hugo (#1069371).
>
> Mathias

Hi Reinhard, Mathias and Shengjing,

Thank you for bringing this to my attention, and sorry for my late response!
Thank you also for your detailed investigation!  Very much appreciated!

I don't see any concern uploading v1.5.4 especially how it fixes the
regression and FTBFS
with v1.5.3, and I'll be uploading golang-github-golang-protobuf-1-5
1.5.4-1 very shortly.

Cheers,
Anthony

Bug#1050393: Unneeded dependency on "dconf-gsettings-backend | gsettings-backend"?

[Xiyue Deng]

Xiyue Deng  writes:

> Sean Whitton  writes:
>
>> Hello,
>>
>> On Wed 27 Mar 2024 at 11:40pm -07, Xiyue Deng wrote:
>>
>>> Sean Whitton  writes:
>>>
 Hello,

 Rob, can you review the implementation in d/rules for Xiyue's patch to
 this bug, please?  I'm not sure it's the straightforward way to do it.

 Xiyue, I think it would make sense to use emacs-common (<< 1:29.3+2-2),
 for the relationships.
>>>
>>> Ah indeed, I should update the versions after the Emacs 29.3 upload,
>>> though I think you meant "1:29.3+1-2".  Also, as we are just moving
>>> files from emacs-common to emacs-pgtk, breaks/replaces is only needed
>>> from emacs-pgtk to emacs-common but no the other way around, so I
>>> dropped the breaks on emacs-pgtk from emacs-common.
>>>
>>> I have updated the patch accordingly and attached here.  PTAL.
>>
>> Thanks.
>>
>>> (BTW, I'm always curious about the "+1" part of the version number.  I
>>> would expect something like "+dfsg" or "+ds" as we are dropping some
>>> of the non-DFSG conformant files, but why "+1"? :)
>>
>> It's just in case the DFSG split is done incorrectly and another attempt
>> is required -- given how complex it is.
>
> Ack, totally understandable.
>
> With the release of Emacs 1:29.3+1-2, I have rebased the patch onto it
> and bumped the breaks/replaces version.  PTAL.

Rob suggested on IRC to be a bit more conservative by removing the file
and remove the directories upwards recursively so that we can catch
future addition to the directories more easily.  The patch has been
adjusted accordingly.  PTAL.

-- 
Xiyue Deng

>From 400a3efac8f0d2ab02ba18ac4cb5ee2324bf7c23 Mon Sep 17 00:00:00 2001
From: Xiyue Deng 
Date: Wed, 13 Mar 2024 10:22:46 -0700
Subject: [PATCH] Install GSettings schema in pgtk build only (Closes:
 #1050393)

* In PGTK build it generates the GSettings schema file
"/usr/share/glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml" which
is not needed in other variant.
* Move the file from emacs-common to emacs-pgtk, and adds proper
breaks/replaces to ensure a smooth upgrade.
---
 debian/changelog |  7 +++
 debian/control   | 11 +--
 debian/rules | 12 +++-
 3 files changed, 27 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 5d4e9f050ae..e2a31a36fcb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+emacs (1:29.3+1-3) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Install GSettings schema in pgtk build only (Closes: #1050393)
+
+ -- Xiyue Deng   Wed, 13 Mar 2024 10:22:10 -0700
+
 emacs (1:29.3+1-2) unstable; urgency=medium
 
   * Change native-comp-async-report-warnings-errors to `silent'.
diff --git a/debian/control b/debian/control
index e168717089f..3c04652c769 100644
--- a/debian/control
+++ b/debian/control
@@ -138,8 +138,15 @@ Provides: editor, emacs, emacsen, info-browser, mail-reader, news-reader
 Recommends: fonts-noto-color-emoji
 Suggests: emacs-common-non-dfsg
 Conflicts: emacs-gtk, emacs-lucid, emacs-nox
-Replaces: emacs-gtk, emacs-lucid, emacs-nox, emacs-bin-common (<< 1:29.2)
-Breaks: emacs-bin-common (<< 1:29.2)
+Replaces:
+ emacs-gtk,
+ emacs-lucid,
+ emacs-nox,
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.3+1-3~),
+Breaks:
+ emacs-bin-common (<< 1:29.2),
+ emacs-common (<< 1:29.3+1-3~),
 Description: GNU Emacs editor (with GTK+ Wayland GUI support)
  GNU Emacs is the extensible self-documenting text editor.  This
  package contains a version of Emacs with a graphical user interface
diff --git a/debian/rules b/debian/rules
index 6250f60ea9b..1262e568c80 100755
--- a/debian/rules
+++ b/debian/rules
@@ -489,6 +489,12 @@ override_dh_auto_install: $(autogen_install_files)
 	  rm -f $(pkgdir_common)/usr/share/info/emacs/dir.old
 
 	  install -d $(pkgdir_common)/usr/local/share/emacs/site-lisp
+
+	  # PGTK builds a GSettings schema that is PGTK specific and
+	  # should not be shipped in emacs-common
+	  cd $(pkgdir_common)/usr/share \
+	&& rm glib-2.0/schemas/org.gnu.emacs.defaults.gschema.xml \
+	&& rmdir --parents glib-2.0/schemas
 endif
 
 ##
@@ -548,7 +554,7 @@ override_dh_auto_install: $(autogen_install_files)
 
 ##
 # emacs-pgtk
-ifneq (,$(findstring emacs, $(shell dh_listpackages)))
+ifneq (,$(findstring emacs-pgtk, $(shell dh_listpackages)))
 	  $(call install_common_binpkg_bits,$(install_dir_pgtk),$(pkgdir_pgtk),emacs-pgtk,pgtk)
 
   # install desktop entries
@@ -557,6 +563,10 @@ override_dh_auto_install: $(autogen_install_files)
 	debian/emacs.desktop \
 	debian/emacs-term.desktop \
 	$(pkgdir_pgtk)/usr/share/applications/
+	  # install GSettings schema
+	  install -d $(pkgdir_pgtk)/usr/share/glib-2.0
+	  cp -a $(install_dir_pgtk)/usr/share/glib-2.0/* \
+	$(pkgdir_pgtk)/usr/share/glib-2.0
 endif
 
 

Bug#1069638: blender: crashes on startup (SIGSEGV)

[Marcus Better]

Package: blender
Version: 4.0.2+dfsg-1+b2
Severity: important

Dear Maintainer,

Starting blender crashes immediately, before any window is shown.

Stack trace:

(gdb) bt
#0  wm_window_set_drawable (activate=false, win=0x0, wm=0x7fff8fd68c08) at 
./source/blender/windowmanager/intern/wm_window.cc:1235
#1  wm_window_ghostwindow_add (title=0x58d0e545 "Blender", 
is_dialog=, win=0x7fff8fd44088, wm=0x7fff8fd68c08) at 
./source/blender/windowmanager/intern/wm_window.cc:785
#2  wm_window_ghostwindow_ensure(wmWindowManager*, wmWindow*, bool) 
(wm=0x7fff8fd68c08, win=0x7fff8fd44088, is_dialog=) at 
./source/blender/windowmanager/intern/wm_window.cc:817
#3  0x565087f5 in wm_window_ghostwindows_ensure(wmWindowManager*) 
(wm=wm@entry=0x7fff8fd68c08) at 
./source/blender/windowmanager/intern/wm_window.cc:874
#4  0x564d18f8 in WM_check(bContext*) (C=C@entry=0x7fff9436f788) at 
./source/blender/windowmanager/intern/wm.cc:483
#5  0x564e793e in wm_homefile_read_ex(bContext*, wmHomeFileRead_Params 
const*, ReportList*, wmFileReadPost_Params**)
(C=C@entry=0x7fff9436f788, 
params_homefile=params_homefile@entry=0x7fffd940, 
reports=reports@entry=0x0, 
r_params_file_read_post=r_params_file_read_post@entry=0x7fffd938)
at ./source/blender/windowmanager/intern/wm_files.cc:1476
#6  0x564ed1b8 in WM_init(bContext*, int, char const**) 
(C=C@entry=0x7fff9436f788, argc=argc@entry=1, argv=argv@entry=0x7fffdb18)
at ./source/blender/windowmanager/intern/wm_init_exit.cc:302
#7  0x55d67568 in main(int, char const**) (argc=1, argv=0x7fffdb18) 
at ./source/creator/creator.cc:537


With --debug::

> blender --debug 
Switching to fully guarded memory allocator.
Blender 4.0.2
argv[0] = blender
argv[1] = --debug
Writing: /tmp/blender.crash.txt
fish: Job 1, 'blender --debug' terminated by signal SIGSEGV (Address boundary 
error)

> cat /tmp/blender.crash.txt
# Blender 4.0.2, Unknown revision

# backtrace
blender(+0xf6d517) [0x55e4d22e6517]
blender(+0x83db0d) [0x55e4d1bb6b0d]
/lib/x86_64-linux-gnu/libc.so.6(+0x3c510) [0x7f3c00c5a510]
blender(+0xfb478c) [0x55e4d232d78c]
blender(+0xfb47f5) [0x55e4d232d7f5]
blender(+0xf7d8f8) [0x55e4d22f68f8]
blender(+0xf9393e) [0x55e4d230c93e]
blender(+0xf991b8) [0x55e4d23121b8]
blender(+0x813568) [0x55e4d1b8c568]
/lib/x86_64-linux-gnu/libc.so.6(+0x276ca) [0x7f3c00c456ca]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f3c00c45785]
blender(+0x839421) [0x55e4d1bb2421]

# Python backtrace

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

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

Versions of packages blender depends on:
ii  blender-data  4.0.2+dfsg-1
ii  fonts-dejavu  2.37-8
ii  libavcodec60  7:6.1.1-1
ii  libavdevice60 7:6.1.1-1
ii  libavformat60 7:6.1.1-1
ii  libavutil58   7:6.1.1-1
ii  libboost-locale1.83.0 1.83.0-2+b2
ii  libc6 2.37-15
ii  libembree4-4  4.3.0+dfsg-2
ii  libepoxy0 1.5.10-1+b2
ii  libfftw3-double3  3.3.10-1+b1
ii  libfftw3-single3  3.3.10-1+b1
ii  libfreetype6  2.13.2+dfsg-1+b1
ii  libgcc-s1 14-20240201-3
ii  libgmp10  2:6.3.0+dfsg-2+b1
ii  libgomp1  14-20240201-3
ii  libimath-3-1-29t643.1.9-3.1+b1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3+b1
ii  libjemalloc2  5.3.0-2+b1
ii  libjpeg62-turbo   1:2.1.5-2+b2
ii  libopenal11:1.23.1-4+b1
ii  libopencolorio2.1t64  2.1.3+dfsg-1.1+b1
ii  libopenexr-3-1-30 3.1.5-5.1+b1
ii  libopenimageio2.4t64  2.4.17.0+dfsg-1.1+b1
ii  libopenjp2-7  2.5.0-2+b2
ii  libopenvdb10.0t64 10.0.1-2.1+b1
ii  libosdcpu3.5.0t64 3.5.0-2.1
ii  libosdgpu3.5.0t64 3.5.0-2.1
ii  libpng16-16t641.6.43-5
ii  libpotrace0   1.16-2+b1
ii  libpugixml1v5 1.14-0.1+b1
ii  libpulse0 16.1+dfsg1-3
ii  libpython3.11t64  3.11.9-1
ii  libsdl2-2.0-0 2.30.1+dfsg-4
ii  libsndfile1   1.2.2-1
ii  libspnav0 1.1-2
ii  libstdc++614-20240201-3
ii  libswscale7   7:6.1.1-1
ii  

Bug#1055190: apt: autoremove forgets a package

[Vincent Lefevre]

On 2024-04-22 03:19:36 +0200, Vincent Lefevre wrote:
> On 2024-04-21 12:03:05 +0200, David Kalnischkies wrote:
> > Controlling autoremoval behaviour is `APT::AutoRemove::SuggestsImportant`
> > which defaults to `true` as the autoremover could potentially break some
> > usecase for you that the suggests enabled and you have grown attached to
> > even through the suggests was once installed for another reason.
> 
> OK, I had actually that on my old machines, but for some reason,
> I didn't remember that and didn't notice that this was missing on
> new machines (and there was a bug in my script that checked the
> consistency of the config between machines).

I meant that I had

  APT::AutoRemove::SuggestsImportant "false";

in a config file on old machines (added 6 years ago), but this
file was missing on the new machines, and I did not remember of
the existence of this setting because:

> But the fact that this is a hidden setting did not help, i.e. it is
> not mentioned in the documentation (apt(8), apt-get(8), apt.conf(5),
> apt-config(8) man pages, APT User's Guide), while the description of
> "apt autoremove" is misleading ("dependencies" is used twice in the
> same sentence with 2 different meanings!).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1069637: hd-idle: version 1.21+ds-1 hangs the upgrade process

[Arthur Marsh]

Package: hd-idle
Version: 1.21+ds-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

Setting up hd-idle (1.21+ds-1) ...
Installing new version of config file /etc/default/hd-idle ...
Installing new version of config file /etc/logrotate.d/hd-idle ...
Stopping the hd-idle daemon: hd-idle.
Starting the hd-idle daemon: hd-idlesymlinkPolicy=0, defaultIdle=600, 
defaultCommand=scsi, defaultPowerCondition=0, debug=false, logFile=, devices=

process just hung at this point.

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

Had to kill hd-idle process then downgrade hd-idle.
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

Kernel: Linux 6.9.0-rc4+ (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages hd-idle depends on:
ii  init-system-helpers1.66devuan1
ii  libc6  2.38-6
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.09-1devuan1

hd-idle recommends no packages.

hd-idle suggests no packages.

-- no debconf information

Bug#1058834: ponyprog: diff for NMU version 3.1.3+ds-1.1

[Chris Hofstaedtler]

Control: tags 1058834 + patch
Control: tags 1058834 + pending


Dear maintainer,

I've prepared an NMU for ponyprog (versioned as 3.1.3+ds-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru ponyprog-3.1.3+ds/debian/changelog ponyprog-3.1.3+ds/debian/changelog
--- ponyprog-3.1.3+ds/debian/changelog	2022-03-10 16:33:58.0 +0100
+++ ponyprog-3.1.3+ds/debian/changelog	2024-04-22 03:18:43.0 +0200
@@ -1,3 +1,10 @@
+ponyprog (3.1.3+ds-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use udev.pc to place udev files. (Closes: #1058834)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 03:18:43 +0200
+
 ponyprog (3.1.3+ds-1) unstable; urgency=medium
 
   * [6909f06] d/gbp.conf: Update content to filter out
diff -Nru ponyprog-3.1.3+ds/debian/control ponyprog-3.1.3+ds/debian/control
--- ponyprog-3.1.3+ds/debian/control	2022-03-10 16:33:58.0 +0100
+++ ponyprog-3.1.3+ds/debian/control	2024-04-22 03:18:41.0 +0200
@@ -11,8 +11,10 @@
  libftdi1-dev,
  libftdipp1-dev,
  libusb-dev,
+ pkgconf,
  qtbase5-dev,
  qtmultimedia5-dev,
+ systemd-dev,
 Rules-Requires-Root: binary-targets
 Standards-Version: 4.6.0
 Homepage: https://github.com/lancos/ponyprog
diff -Nru ponyprog-3.1.3+ds/debian/ponyprog.install ponyprog-3.1.3+ds/debian/ponyprog.install
--- ponyprog-3.1.3+ds/debian/ponyprog.install	2022-03-10 16:17:22.0 +0100
+++ ponyprog-3.1.3+ds/debian/ponyprog.install	2024-04-22 03:18:41.0 +0200
@@ -1,3 +1,3 @@
 icons/ponyprog.svg usr/share/icons/hicolor/scalable/apps
-lib/udev/rules.d/90-ponyprog.rules
+${env:deb_udevdir}/rules.d/90-ponyprog.rules
 usr
diff -Nru ponyprog-3.1.3+ds/debian/rules ponyprog-3.1.3+ds/debian/rules
--- ponyprog-3.1.3+ds/debian/rules	2022-03-10 16:33:58.0 +0100
+++ ponyprog-3.1.3+ds/debian/rules	2024-04-22 03:18:41.0 +0200
@@ -15,6 +15,8 @@
 CFLAGS+=$(CPPFLAGS)
 CXXFLAGS+=$(CPPFLAGS)
 
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
 ICON_SIZES=128x128 64x64 48x48 32x32 24x24 16x16
 
 # detect the encoding of the file ponyprog.html
@@ -27,6 +29,7 @@
 DEB_PONYPROG_CMAKE_OPTS := \
 	-DCMAKE_INSTALL_PREFIX=/usr \
 	-DCMAKE_SHARED_LINKER_FLAGS_RELEASE="$(LDFLAGS)" \
+	-DUDEV_INSTALL_DIR="/$(deb_udevdir)/rules.d" \
 	-DUSE_DEBUGGER=ON \
 	-DUSE_QT5=ON \
 	$(NULL)

Bug#981454: fuse-zip: version 0.7.2 is out

[Alexander Galanin]

I'm planning to NMU it. Version would be "0.7.2-0.1"

Glad to hear it!

--
Alexander Galanin

Bug#1058773: caddy: diff for NMU version 2.6.2-6.1

[Chris Hofstaedtler]

Control: tags 1058773 + patch
Control: tags 1058773 + pending


Dear maintainer,

I've prepared an NMU for caddy (versioned as 2.6.2-6.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru caddy-2.6.2/debian/caddy.install caddy-2.6.2/debian/caddy.install
--- caddy-2.6.2/debian/caddy.install	2023-08-23 13:28:40.0 +0200
+++ caddy-2.6.2/debian/caddy.install	2024-04-22 03:13:07.0 +0200
@@ -1,6 +1,6 @@
 dist/config/Caddyfile   etc/caddy/
-dist/init/caddy.service lib/systemd/system
-dist/init/caddy-api.service lib/systemd/system
+dist/init/caddy.service ${env:deb_systemdsystemunitdir}/
+dist/init/caddy-api.service ${env:deb_systemdsystemunitdir}/
 debian/missing-sources/caddy/welcome/index.html usr/share/caddy/
 debian/generated/completions/caddy  usr/share/bash-completion/completions/
 debian/generated/completions/_caddy usr/share/zsh/vendor-completions/
diff -Nru caddy-2.6.2/debian/changelog caddy-2.6.2/debian/changelog
--- caddy-2.6.2/debian/changelog	2023-08-23 13:28:40.0 +0200
+++ caddy-2.6.2/debian/changelog	2024-04-22 03:13:10.0 +0200
@@ -1,3 +1,10 @@
+caddy (2.6.2-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use systemd.pc to place systemd units. (Closes: #1058773)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 03:13:10 +0200
+
 caddy (2.6.2-6) unstable; urgency=medium
 
   * Team upload
diff -Nru caddy-2.6.2/debian/control caddy-2.6.2/debian/control
--- caddy-2.6.2/debian/control	2023-08-23 13:28:40.0 +0200
+++ caddy-2.6.2/debian/control	2024-04-22 03:13:07.0 +0200
@@ -39,6 +39,8 @@
golang-glog-dev,
golang-golang-x-text-dev,
golang-github-stoewer-go-strcase-dev,
+   pkgconf,
+   systemd-dev,
 Standards-Version: 4.6.1.0
 Vcs-Browser: https://salsa.debian.org/go-team/packages/caddy
 Vcs-Git: https://salsa.debian.org/go-team/packages/caddy.git
diff -Nru caddy-2.6.2/debian/rules caddy-2.6.2/debian/rules
--- caddy-2.6.2/debian/rules	2023-08-23 13:28:40.0 +0200
+++ caddy-2.6.2/debian/rules	2024-04-22 03:13:07.0 +0200
@@ -7,6 +7,8 @@
 export DH_GOLANG_EXCLUDES := integration tracing
 export BUILDDIR := build
 
+export deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 include /usr/share/dpkg/pkg-info.mk
 LDFLAGS := -ldflags '-X $(DH_GOPKG).CustomVersion=$(DEB_VERSION_UPSTREAM) -X $(DH_GOPKG)/cmd.CustomDate="$(SOURCE_DATE_EPOCH)"'
 

Bug#1055190: apt: autoremove forgets a package

[Vincent Lefevre]

On 2024-04-21 12:03:05 +0200, David Kalnischkies wrote:
> On Sun, Apr 21, 2024 at 03:35:28AM +0200, Vincent Lefevre wrote:
> > > root@qaa:~# dpkg -s libtest-fatal-perl:amd64
> > > dpkg-query: package 'libtest-fatal-perl' is not installed and no 
> > > information is available
> > > Use dpkg --info (= dpkg-deb --info) to examine archive files.
[...]
> > Well, this isn't really the right explanation. This is due to an
> > output bug in apt, which should have output "libtest-fatal-perl:all"
> > instead of "libtest-fatal-perl:amd64".
> 
> That might be your preference (now), but it would be wrong in terms of
> apt and I am sure if you think a bit more about it you will agree:
> 
> A package is not arch:all. People say that all the time, but only
> because they mean that "this version of the package is arch:all" as we
> tend to talk about a *.deb file as a package and that contains
> a specific version.
> 
> If apt were to display "libtest-fatal-perl:all" it would mean that if
> that package becomes arch:any in the next version apt would need
> to show "removing: libtest-fatal-perl:all" and "new install:
> libtest-fatal-perl:amd64" instead of as an "upgrade" among many other
> very annoying things around architectures.
> 
> So, for apt, "libtest-fatal-perl:all" is treated like
> "libtest-fatal-perl:native" aka "libtest-fatal-perl:amd64" for you, so
> that if a binary package is arch:any or arch:all is an implementation
> detail for a user – as it should be – as that changes over time.
> The native architecture does not change as often, if at all.
> 
> So, in other words, for apt a "package" is usually a set of versions
> which can have different architectures, while for dpkg a package is
> a single version (except if it is not, like in that same arch:all to
> arch:any flip; but users don't speak to dpkg that often and especially
> not in that moment. apt does for them…).
> 
> In a way, you could complain that dpkg is so anal about the arch
> instead, but in its own world and context, it makes sense.

But here, "apt install ..." outputs libtest-fatal-perl:amd64, which is
a particular version of this package. And just after the installation,
"dpkg -s ..." refers to exactly the same version. So one should expect
that both tools use a common name to designate the package.

> > So, there's only a "Suggests", and note that I do not install
> > "Suggests" by default.
> 
> While you don't install Suggests via `APT::Install-Suggests` which is
> `false` by default, that has no bearing on the autoremoval.
> 
> Controlling autoremoval behaviour is `APT::AutoRemove::SuggestsImportant`
> which defaults to `true` as the autoremover could potentially break some
> usecase for you that the suggests enabled and you have grown attached to
> even through the suggests was once installed for another reason.

OK, I had actually that on my old machines, but for some reason,
I didn't remember that and didn't notice that this was missing on
new machines (and there was a bug in my script that checked the
consistency of the config between machines).

But the fact that this is a hidden setting did not help, i.e. it is
not mentioned in the documentation (apt(8), apt-get(8), apt.conf(5),
apt-config(8) man pages, APT User's Guide), while the description of
"apt autoremove" is misleading ("dependencies" is used twice in the
same sentence with 2 different meanings!).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1060343: duo-unix: diff for NMU version 1.11.3-1.2

[Chris Hofstaedtler]

Control: tags 1063523 + pending
Control: tags 1060343 + pending

Dear maintainer,

I've prepared an NMU for duo-unix (versioned as 1.11.3-1.2) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru duo-unix-1.11.3/debian/changelog duo-unix-1.11.3/debian/changelog
--- duo-unix-1.11.3/debian/changelog	2024-02-28 03:30:53.0 +0100
+++ duo-unix-1.11.3/debian/changelog	2024-04-22 02:52:25.0 +0200
@@ -1,3 +1,13 @@
+duo-unix (1.11.3-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install aliased files into /usr (DEP17 M2) (Closes: #1060343)
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS (Closes: #1063523)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 02:52:25 +0200
+
 duo-unix (1.11.3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru duo-unix-1.11.3/debian/libpam-duo.install duo-unix-1.11.3/debian/libpam-duo.install
--- duo-unix-1.11.3/debian/libpam-duo.install	2011-09-02 22:21:02.0 +0200
+++ duo-unix-1.11.3/debian/libpam-duo.install	2024-04-22 02:50:44.0 +0200
@@ -1,3 +1,3 @@
-lib/*/security/pam_duo.so
+usr/lib/*/security/pam_duo.so
 debian/pam-configs/* usr/share/pam-configs/
 debian/pam_duo.conf etc/security/
diff -Nru duo-unix-1.11.3/debian/not-installed duo-unix-1.11.3/debian/not-installed
--- duo-unix-1.11.3/debian/not-installed	2020-03-14 18:08:43.0 +0100
+++ duo-unix-1.11.3/debian/not-installed	2024-04-22 02:50:44.0 +0200
@@ -1,7 +1,7 @@
 # We use the debian-specific version from debian/pam_duo.conf instead.
 etc/security/pam_duo.conf
 # We don't need .la files for linking
-lib/x86_64-linux-gnu/security/pam_duo.la
+usr/lib/x86_64-linux-gnu/security/pam_duo.la
 usr/lib/x86_64-linux-gnu/libduo.la
 # We do not support static linking.
 usr/lib/x86_64-linux-gnu/libduo.a
diff -Nru duo-unix-1.11.3/debian/patches/cross.patch duo-unix-1.11.3/debian/patches/cross.patch
--- duo-unix-1.11.3/debian/patches/cross.patch	1970-01-01 01:00:00.0 +0100
+++ duo-unix-1.11.3/debian/patches/cross.patch	2024-04-22 02:52:25.0 +0200
@@ -0,0 +1,24 @@
+--- duo-unix-1.11.3.orig/autotools/ax_check_x509.m4
 duo-unix-1.11.3/autotools/ax_check_x509.m4
+@@ -14,20 +14,16 @@
+ 
+ AU_ALIAS([CHECK_X509], [AX_CHECK_X509])
+ AC_DEFUN([AX_CHECK_X509],[
+-AC_MSG_CHECKING([whether X509_TEA_set_state runs])
+ save_LIBS="$LIBS"
+ save_LDFLAGS="$LDFLAGS"
+ save_CPPFLAGS="$CPPFLAGS"
+ LDFLAGS="$LDFLAGS $OPENSSL_LDFLAGS"
+ LIBS="$OPENSSL_LIBS $LIBS"
+ CPPFLAGS="$OPENSSL_INCLUDES $CPPFLAGS"
+-AC_RUN_IFELSE(
+-[AC_LANG_PROGRAM([void X509_TEA_set_state(int change);], [X509_TEA_set_state(0);])],
++AC_CHECK_FUNC([X509_TEA_set_state],
+ [
+-AC_MSG_RESULT([yes])
+ $1
+ ], [
+-AC_MSG_RESULT([no])
+ $2
+ ])
+ CPPFLAGS="$save_CPPFLAGS"
diff -Nru duo-unix-1.11.3/debian/patches/series duo-unix-1.11.3/debian/patches/series
--- duo-unix-1.11.3/debian/patches/series	2020-03-14 18:08:43.0 +0100
+++ duo-unix-1.11.3/debian/patches/series	2024-04-22 02:52:25.0 +0200
@@ -4,3 +4,4 @@
 libduo-install.patch
 pam_duo-ldflags.patch
 lib-strncpy.patch
+cross.patch
diff -Nru duo-unix-1.11.3/debian/rules duo-unix-1.11.3/debian/rules
--- duo-unix-1.11.3/debian/rules	2020-03-14 18:08:43.0 +0100
+++ duo-unix-1.11.3/debian/rules	2024-04-22 02:50:44.0 +0200
@@ -11,7 +11,7 @@
 	dh $@
 
 override_dh_auto_configure:
-	dh_auto_configure -- --with-pam=/lib/$(DEB_HOST_MULTIARCH)/security \
+	dh_auto_configure -- --with-pam=/usr/lib/$(DEB_HOST_MULTIARCH)/security \
 			 --sysconfdir=/etc/security \
 			 --includedir=\$${prefix}/include/duo
 

Bug#1057850: libnss-db: Uses db5.3, no replacement in sight

[Chris Hofstaedtler]

On Thu, Apr 04, 2024 at 07:16:34PM -0300, Paulo Henrique de Lima Santana wrote:
> Would be possible reintroduce libnss-db to testing?
> 
> I'm asking because I'm maintainer of the pglistener package and I know there
> aren't plans to update the sofwtare with another database solution.

Well what's your plan forward? db5.3 is supposed to be removed.

Chris

Bug#1069585: apt: autoremoval forgets transitional packages in a OR dependency

[Vincent Lefevre]

Control: retitle -1 synaptic: should not depend on the transitional package 
policykit-1

On 2024-04-21 12:25:45 +0200, David Kalnischkies wrote:
> synaptics could drop the or on policykit-1 – or if for some reason
> keeping it is desirable make it a versioned on, like:
> |   pkexec | policykit-1 (<< first-transitional-version~)

OK. I've also reported a bug against network-manager, which has the
same issue.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1060769: foo2zjs: diff for NMU version 20200505dfsg0-2.1

[Chris Hofstaedtler]

Control: tags 1060769 + pending


Dear maintainer,

I've prepared an NMU for foo2zjs (versioned as 20200505dfsg0-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris
diff -Nru foo2zjs-20200505dfsg0/debian/changelog foo2zjs-20200505dfsg0/debian/changelog
--- foo2zjs-20200505dfsg0/debian/changelog	2021-09-02 14:45:45.0 +0200
+++ foo2zjs-20200505dfsg0/debian/changelog	2024-04-22 02:32:30.0 +0200
@@ -1,3 +1,12 @@
+foo2zjs (20200505dfsg0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * DEP17: Move all aliased files to /usr. (Closes: #1060769)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 02:32:30 +0200
+
 foo2zjs (20200505dfsg0-2) unstable; urgency=medium
 
   * Remove myself from Uploaders
diff -Nru foo2zjs-20200505dfsg0/debian/NEWS foo2zjs-20200505dfsg0/debian/NEWS
--- foo2zjs-20200505dfsg0/debian/NEWS	2021-09-02 14:45:45.0 +0200
+++ foo2zjs-20200505dfsg0/debian/NEWS	2024-04-22 02:32:25.0 +0200
@@ -1,7 +1,7 @@
 foo2zjs (20090908dfsg-2) unstable; urgency=low
 
   Starting with this version all HP firmwares are looked for into
-  /lib/firmware/hp/ instead of upstream /usr/share/foo2zjs/firmware/
+  /usr/lib/firmware/hp/ instead of upstream /usr/share/foo2zjs/firmware/
   (thus solving bug #517957).
 
   The upstream /usr/bin/getweb and /lib/udev/hplj1000 scripts have
diff -Nru foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs-common.install foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs-common.install
--- foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs-common.install	2021-09-02 14:45:45.0 +0200
+++ foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs-common.install	2024-04-22 02:32:25.0 +0200
@@ -1,7 +1,7 @@
 PPD/* usr/share/ppd/foo2zjs/
 debian/printer-driver-foo2zjs-common.ppd-updater /usr/share/cups/ppd-updaters/
 getweb usr/sbin
-hplj1000 lib/udev
+hplj1000 usr/lib/udev
 hplj1020.desktop usr/share/applications/
 hplj1020_icon.png usr/share/pixmaps
 usr/bin/foo2ddst-wrapper
diff -Nru foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.dirs foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.dirs
--- foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.dirs	2021-09-02 14:45:45.0 +0200
+++ foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.dirs	2024-04-22 02:32:25.0 +0200
@@ -1 +1 @@
-/lib/firmware/hp/
+/usr/lib/firmware/hp/
diff -Nru foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.links foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.links
--- foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.links	2021-09-02 14:45:45.0 +0200
+++ foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.links	2024-04-22 02:32:25.0 +0200
@@ -1,10 +1,10 @@
-lib/udev/hplj1000 lib/udev/hplj1005
-lib/udev/hplj1000 lib/udev/hplj1018
-lib/udev/hplj1000 lib/udev/hplj1020
-lib/udev/hplj1000 lib/udev/hpljP1005
-lib/udev/hplj1000 lib/udev/hpljP1006
-lib/udev/hplj1000 lib/udev/hpljP1007
-lib/udev/hplj1000 lib/udev/hpljP1008
-lib/udev/hplj1000 lib/udev/hpljP1505
-lib/udev/hplj1000 lib/udev/hpljP1505n
+usr/lib/udev/hplj1000 usr/lib/udev/hplj1005
+usr/lib/udev/hplj1000 usr/lib/udev/hplj1018
+usr/lib/udev/hplj1000 usr/lib/udev/hplj1020
+usr/lib/udev/hplj1000 usr/lib/udev/hpljP1005
+usr/lib/udev/hplj1000 usr/lib/udev/hpljP1006
+usr/lib/udev/hplj1000 usr/lib/udev/hpljP1007
+usr/lib/udev/hplj1000 usr/lib/udev/hpljP1008
+usr/lib/udev/hplj1000 usr/lib/udev/hpljP1505
+usr/lib/udev/hplj1000 usr/lib/udev/hpljP1505n
 usr/bin/psicc usr/bin/foo2zjs-icc2ps
diff -Nru foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.lintian-overrides foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.lintian-overrides
--- foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.lintian-overrides	2021-09-02 14:45:45.0 +0200
+++ foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.lintian-overrides	2024-04-22 02:32:25.0 +0200
@@ -1,5 +1,5 @@
 # That's on purpose, getweb can go fetch these from the web
-package-contains-empty-directory lib/firmware/hp/
+package-contains-empty-directory usr/lib/firmware/hp/
 
 # Manpages are shipped in printer-driver-foo2zjs-common
 no-manual-page usr/bin/arm2hpdl
diff -Nru foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.postinst foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.postinst
--- foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.postinst	2021-09-02 14:45:45.0 +0200
+++ foo2zjs-20200505dfsg0/debian/printer-driver-foo2zjs.postinst	2024-04-22 02:32:25.0 +0200
@@ -3,9 +3,13 @@
 set -e
 
 if [ "$1" = configure ]; then
+# begin-remove-after: released:trixie
+# Mitigate empty directory loss in upgrade DEP17 P6.
+mkdir -p /usr/lib/firmware/hp
+# end-remove-after
 # Move user-downloaded firmware files
 if ls /usr/share/foo2zjs/firmware/*.dl >/dev/null 2>/dev/null; then
-	mv /usr/share/foo2zjs/firmware/*.dl /lib/firmware/hp/ 2>/dev/null
+	mv /usr/share/foo2zjs/firmware/*.dl /usr/lib/firmware/hp/ 

Bug#1069636: network-manager: should not depend on the transitional package policykit-1

[Vincent Lefevre]

Package: network-manager
Version: 1.46.0-1+b2
Severity: normal

network-manager currently has

  Depends: [...] polkitd | policykit-1

policykit-1 is now a transitional package. network-manager should not
depend on it (even in an OR dependency), otherwise apt or aptitude
cannot propose its removal.

This is even more important now that deborphan has been removed from
Debian.

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 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

Versions of packages network-manager depends on:
ii  adduser 3.137
ii  dbus [default-dbus-system-bus]  1.14.10-4+b1
ii  libaudit1   1:3.1.2-2.1
ii  libbluetooth3   5.73-1
ii  libc6   2.37-18
ii  libcurl3t64-gnutls  8.7.1-3
ii  libglib2.0-0t64 2.78.4-6
ii  libgnutls30t64  3.8.5-2
ii  libjansson4 2.14-2+b2
ii  libmm-glib0 1.22.0-3+b1
ii  libndp0 1.8-1
ii  libnewt0.52 0.52.24-2
ii  libnm0  1.46.0-1+b2
ii  libpsl5t64  0.21.2-1.1
ii  libreadline8t64 8.2-4
ii  libselinux1 3.5-2+b2
ii  libsystemd0 255.4-1+b1
ii  libteamdctl01.31-1
ii  libudev1255.4-1+b1
ii  policykit-1 124-2
ii  polkitd 124-2
ii  udev255.4-1+b1

Versions of packages network-manager recommends:
ii  dnsmasq-base [dnsmasq-base]  2.90-3
ii  libpam-systemd   255.4-1+b1
ii  modemmanager 1.22.0-3+b1
ii  ppp  2.5.0-1+2
ii  wireless-regdb   2022.06.06-1
ii  wpasupplicant2:2.10-21+b1

Versions of packages network-manager suggests:
ii  iptables   1.8.10-3
pn  libteam-utils  

Versions of packages network-manager is related to:
ii  isc-dhcp-client  4.4.3-P1-5

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1059515: mdns-reflector: diff for NMU version 0.0.1+git20230914.4b4cd3b-2.1

[Chris Hofstaedtler]

Control: tags 1059515 + patch
Control: tags 1059515 + pending


Dear maintainer,

I've prepared an NMU for mdns-reflector (versioned as 
0.0.1+git20230914.4b4cd3b-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru mdns-reflector-0.0.1+git20230914.4b4cd3b/debian/changelog mdns-reflector-0.0.1+git20230914.4b4cd3b/debian/changelog
--- mdns-reflector-0.0.1+git20230914.4b4cd3b/debian/changelog	2024-02-01 22:16:11.0 +0100
+++ mdns-reflector-0.0.1+git20230914.4b4cd3b/debian/changelog	2024-04-22 02:24:48.0 +0200
@@ -1,3 +1,10 @@
+mdns-reflector (0.0.1+git20230914.4b4cd3b-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd units into /usr (DEP17 M2) (Closes: #1059515)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 02:24:48 +0200
+
 mdns-reflector (0.0.1+git20230914.4b4cd3b-2) unstable; urgency=medium
 
   * debian/control:
diff -Nru mdns-reflector-0.0.1+git20230914.4b4cd3b/debian/install mdns-reflector-0.0.1+git20230914.4b4cd3b/debian/install
--- mdns-reflector-0.0.1+git20230914.4b4cd3b/debian/install	2023-03-21 18:38:11.0 +0100
+++ mdns-reflector-0.0.1+git20230914.4b4cd3b/debian/install	2024-04-22 02:24:46.0 +0200
@@ -1,3 +1,3 @@
 misc/mdns-reflector etc/
-misc/mdns-reflector.service lib/systemd/system
-misc/mdns-reflector@.service lib/systemd/system
+misc/mdns-reflector.service usr/lib/systemd/system
+misc/mdns-reflector@.service usr/lib/systemd/system

Bug#966288: [Pkg-puppet-devel] Bug#966288: mcollective - RM for bullseye?

[Chris Hofstaedtler]

Control: clone -1 -2
Control: severity -1 serious
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: mcollective -- ROQA; dead upstream, alternatives exist
Control: tags -2 = moreinfo

On Mon, Apr 01, 2024 at 12:21:57PM -0700, Matt Taggart wrote:
> The last mcollective release was v.3.1.2 tagged on Oct 14, 2018, and zero
> commits after that, so is effectively dead upstream.
> 
> Here are the popcon stats
>   https://qa.debian.org/popcon.php?package=mcollective
> 
> I think it could probably be removed from debian now.
> 
> This bug mentioned "bolt" as a possible replacement, that seems to be this:
>   https://www.puppet.com/docs/bolt/latest/bolt.html

I've cloned this bug to request RM for trixie. While bolt is not
packaged in Debian, it seems mcollective has no users and whoever
was running it has very likely replaced it by now with something
else. I know a number of sites now using Puppet + ansible instead
of Puppet + mcollective.

AFAIK the old mcollective doesn't work with current Puppet, but I
haven't looked since 2018 either :-)

Chris

Bug#1060083: cgroupfs-mount: diff for NMU version 1.4+nmu1

[Chris Hofstaedtler]

Control: tags 1060083 + patch
Control: tags 1060083 + pending


Dear maintainer,

I've prepared an NMU for cgroupfs-mount (versioned as 1.4+nmu1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru cgroupfs-mount-1.4/debian/changelog cgroupfs-mount-1.4+nmu1/debian/changelog
--- cgroupfs-mount-1.4/debian/changelog	2017-03-08 23:05:14.0 +0100
+++ cgroupfs-mount-1.4+nmu1/debian/changelog	2024-04-22 01:59:39.0 +0200
@@ -1,3 +1,10 @@
+cgroupfs-mount (1.4+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install initscript mask into /usr/lib (DEP17 M2). (Closes: #1060083)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:59:39 +0200
+
 cgroupfs-mount (1.4) unstable; urgency=medium
 
   * Add a short blurb about installation in README.md
diff -Nru cgroupfs-mount-1.4/debian/links cgroupfs-mount-1.4+nmu1/debian/links
--- cgroupfs-mount-1.4/debian/links	2017-03-08 22:53:04.0 +0100
+++ cgroupfs-mount-1.4+nmu1/debian/links	2024-04-22 01:59:35.0 +0200
@@ -2,4 +2,4 @@
 
 # http://0pointer.de/blog/projects/three-levels-of-off
 # "mask" the cgroupfs-mount service in systemd
-/dev/null lib/systemd/system/cgroupfs-mount.service
+/dev/null usr/lib/systemd/system/cgroupfs-mount.service

Bug#1059409: net-tools: diff for NMU version 2.10-1.1

[Chris Hofstaedtler]

Control: tags 1059409 + patch
Control: tags 1059409 + pending


Dear maintainer,

I've prepared an NMU for net-tools (versioned as 2.10-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru net-tools-2.10/debian/changelog net-tools-2.10/debian/changelog
--- net-tools-2.10/debian/changelog	2023-11-23 15:41:07.0 +0100
+++ net-tools-2.10/debian/changelog	2024-04-22 01:55:29.0 +0200
@@ -1,3 +1,10 @@
+net-tools (2.10-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Release to unstable. (Closes: #1059409)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:55:29 +0200
+
 net-tools (2.10-1) experimental; urgency=medium
 
   * Move to /usr-merge (DEP17).

Bug#1061239: pam-tmpdir: diff for NMU version 0.09+nmu1

[Chris Hofstaedtler]

Control: tags 1061239 + patch
Control: tags 1061239 + pending


Dear maintainer,

I've prepared an NMU for pam-tmpdir (versioned as 0.09+nmu1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru pam-tmpdir-0.09/debian/changelog pam-tmpdir-0.09+nmu1/debian/changelog
--- pam-tmpdir-0.09/debian/changelog	2012-03-08 23:43:05.0 +0100
+++ pam-tmpdir-0.09+nmu1/debian/changelog	2024-04-22 01:48:11.0 +0200
@@ -1,3 +1,11 @@
+pam-tmpdir (0.09+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install into /usr (DEP17 M2) (Closes: #1061239)
+  * Update lintian override to currently correct tag and format.
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:48:11 +0200
+
 pam-tmpdir (0.09) unstable; urgency=low
 
   * Add README.Debian explaining a bit about how pam-tmpdir works.
diff -Nru pam-tmpdir-0.09/debian/lintian-overrides/libpam-tmpdir pam-tmpdir-0.09+nmu1/debian/lintian-overrides/libpam-tmpdir
--- pam-tmpdir-0.09/debian/lintian-overrides/libpam-tmpdir	2012-03-08 23:18:29.0 +0100
+++ pam-tmpdir-0.09+nmu1/debian/lintian-overrides/libpam-tmpdir	2024-04-22 01:48:11.0 +0200
@@ -1 +1 @@
-libpam-tmpdir: setuid-binary sbin/pam-tmpdir-helper 4755 root/root
+libpam-tmpdir: elevated-privileges 4755 root/root [usr/sbin/pam-tmpdir-helper]
diff -Nru pam-tmpdir-0.09/debian/rules pam-tmpdir-0.09+nmu1/debian/rules
--- pam-tmpdir-0.09/debian/rules	2012-03-08 23:47:58.0 +0100
+++ pam-tmpdir-0.09+nmu1/debian/rules	2024-04-22 01:48:06.0 +0200
@@ -8,9 +8,9 @@
 	dh $@ --with autoreconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --exec-prefix=/ --with-pam-dir=/lib/$(DEB_HOST_MULTIARCH)/security 
+	dh_auto_configure -- --with-pam-dir=/usr/lib/$(DEB_HOST_MULTIARCH)/security
 
 
 override_dh_fixperms:
 	dh_fixperms
-	chmod u+s debian/libpam-tmpdir/sbin/pam-tmpdir-helper
+	chmod u+s debian/libpam-tmpdir/usr/sbin/pam-tmpdir-helper

Bug#1060351: vlan: diff for NMU version 2.0.5+nmu1

[Chris Hofstaedtler]

Control: tags 1060351 + patch
Control: tags 1060351 + pending


Dear maintainer,

I've prepared an NMU for vlan (versioned as 2.0.5+nmu1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru vlan-2.0.5/debian/changelog vlan-2.0.5+nmu1/debian/changelog
--- vlan-2.0.5/debian/changelog	2019-02-21 08:29:59.0 +0100
+++ vlan-2.0.5+nmu1/debian/changelog	2024-04-22 01:44:32.0 +0200
@@ -1,3 +1,10 @@
+vlan (2.0.5+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install into /usr for DEP17 M2. (Closes: #1060351)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:44:32 +0200
+
 vlan (2.0.5) unstable; urgency=medium
 
   * debian/network/if-pre-up.d/vlan: add missing biosdevname (Closes: #922801).
diff -Nru vlan-2.0.5/debian/vlan.install vlan-2.0.5+nmu1/debian/vlan.install
--- vlan-2.0.5/debian/vlan.install	2019-02-04 12:11:29.0 +0100
+++ vlan-2.0.5+nmu1/debian/vlan.install	2024-04-22 01:44:27.0 +0200
@@ -1,2 +1,2 @@
 debian/network  etc
-vconfig sbin
+vconfig usr/sbin

Bug#1059412: netcat-openbsd: diff for NMU version 1.226-1.1

[Chris Hofstaedtler]

Control: tags 1059412 + patch
Control: tags 1059412 + pending


Dear maintainer,

I've prepared an NMU for netcat-openbsd (versioned as 1.226-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru netcat-openbsd-1.226/debian/changelog netcat-openbsd-1.226/debian/changelog
--- netcat-openbsd-1.226/debian/changelog	2023-10-16 19:31:08.0 +0200
+++ netcat-openbsd-1.226/debian/changelog	2024-04-22 01:39:53.0 +0200
@@ -1,3 +1,12 @@
+netcat-openbsd (1.226-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install nc.openbsd into /usr/bin. (Closes: #1059412)
+Keep update-alternatives calls unchanged to preserve pre-existing
+user/admin configuration.
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:39:53 +0200
+
 netcat-openbsd (1.226-1) unstable; urgency=medium
 
   [ Guilhem Moulin ]
diff -Nru netcat-openbsd-1.226/debian/netcat-openbsd.install netcat-openbsd-1.226/debian/netcat-openbsd.install
--- netcat-openbsd-1.226/debian/netcat-openbsd.install	2023-10-16 19:31:08.0 +0200
+++ netcat-openbsd-1.226/debian/netcat-openbsd.install	2024-04-22 01:39:51.0 +0200
@@ -1 +1 @@
-nc bin/
+nc usr/bin/
diff -Nru netcat-openbsd-1.226/debian/rules netcat-openbsd-1.226/debian/rules
--- netcat-openbsd-1.226/debian/rules	2023-10-16 19:31:08.0 +0200
+++ netcat-openbsd-1.226/debian/rules	2024-04-22 01:39:51.0 +0200
@@ -39,7 +39,7 @@
 endif
 
 execute_after_dh_install:
-	mv -T $(prefix)/bin/nc $(prefix)/bin/nc.openbsd
+	mv -T $(prefix)/usr/bin/nc $(prefix)/usr/bin/nc.openbsd
 
 execute_after_dh_installman:
 	mv -T $(man1dir)/nc.1 $(man1dir)/nc_openbsd.1

Bug#1059189: quota: diff for NMU version 4.06-1.1

[Chris Hofstaedtler]

Control: tags 1059189 + patch
Control: tags 1059189 + pending


Dear maintainer,

I've prepared an NMU for quota (versioned as 4.06-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru quota-4.06/debian/changelog quota-4.06/debian/changelog
--- quota-4.06/debian/changelog	2021-02-09 13:22:57.0 +0100
+++ quota-4.06/debian/changelog	2024-04-22 01:36:54.0 +0200
@@ -1,3 +1,11 @@
+quota (4.06-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install binary programs into /usr/sbin. (Closes: #1059189)
+  * Update paths to /usr/sbin in (init) scripts, systemd service.
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:36:54 +0200
+
 quota (4.06-1) unstable; urgency=medium
 
   * New upstream version 4.06
diff -Nru quota-4.06/debian/dirs quota-4.06/debian/dirs
--- quota-4.06/debian/dirs	2021-02-09 13:05:00.0 +0100
+++ quota-4.06/debian/dirs	2024-04-22 01:36:52.0 +0200
@@ -1,6 +1,5 @@
 usr/bin
 usr/sbin
-sbin
 etc/init.d
 usr/share/man/man1
 usr/share/man/man2
diff -Nru quota-4.06/debian/quota.init quota-4.06/debian/quota.init
--- quota-4.06/debian/quota.init	2021-02-09 13:05:00.0 +0100
+++ quota-4.06/debian/quota.init	2024-04-22 01:36:52.0 +0200
@@ -13,7 +13,7 @@
 DESC="quota service"
 
 # names of binaries
-on=/sbin/quotaon
+on=/usr/sbin/quotaon
 
 set -e
 
diff -Nru quota-4.06/debian/quota-initial-check.sh quota-4.06/debian/quota-initial-check.sh
--- quota-4.06/debian/quota-initial-check.sh	2021-02-09 13:05:00.0 +0100
+++ quota-4.06/debian/quota-initial-check.sh	2024-04-22 01:36:52.0 +0200
@@ -1,8 +1,8 @@
 #!/bin/sh
 
 # names of binaries
-check=/sbin/quotacheck
-on=/sbin/quotaon
+check=/usr/sbin/quotacheck
+on=/usr/sbin/quotaon
 quotaisnew=/var/lib/quota/new
 
 ALLFLAGS=-aug
diff -Nru quota-4.06/debian/quotaoff.sh quota-4.06/debian/quotaoff.sh
--- quota-4.06/debian/quotaoff.sh	2021-02-09 13:05:00.0 +0100
+++ quota-4.06/debian/quotaoff.sh	2024-04-22 01:36:52.0 +0200
@@ -1,7 +1,7 @@
 #!/bin/sh
 
 # names of binaries
-off=/sbin/quotaoff
+off=/usr/sbin/quotaoff
 quotaisoff=/var/lib/quota/off
 ALLFLAGS=-aug
 
diff -Nru quota-4.06/debian/quotaon.sh quota-4.06/debian/quotaon.sh
--- quota-4.06/debian/quotaon.sh	2021-02-09 13:05:00.0 +0100
+++ quota-4.06/debian/quotaon.sh	2024-04-22 01:36:52.0 +0200
@@ -1,8 +1,8 @@
 #!/bin/sh
 
 # names of binaries
-check=/sbin/quotacheck
-on=/sbin/quotaon
+check=/usr/sbin/quotacheck
+on=/usr/sbin/quotaon
 quotaisoff=/var/lib/quota/off
 quotaisnew=/var/lib/quota/new
 forcequotacheck=/forcequotacheck
diff -Nru quota-4.06/debian/quotarpc.service quota-4.06/debian/quotarpc.service
--- quota-4.06/debian/quotarpc.service	2021-02-09 13:05:00.0 +0100
+++ quota-4.06/debian/quotarpc.service	2024-04-22 01:36:52.0 +0200
@@ -5,7 +5,7 @@
 PartOf=nfs-server.target
 After=rpcbind.service
 Before=nfs-server.target
-ConditionFileIsExecutable=/sbin/rpcbind
+ConditionFileIsExecutable=/usr/sbin/rpcbind
  
 [Service]
 Type=forking
diff -Nru quota-4.06/debian/rules quota-4.06/debian/rules
--- quota-4.06/debian/rules	2021-02-09 13:05:00.0 +0100
+++ quota-4.06/debian/rules	2024-04-22 01:36:52.0 +0200
@@ -57,10 +57,6 @@
 	# Add here commands to install the package into debian/quota.
 	$(MAKE) DESTDIR=`pwd`/debian/quota install
 
-	-mv `pwd`/debian/quota/usr/sbin/quotacheck `pwd`/debian/quota/sbin
-	-mv `pwd`/debian/quota/usr/sbin/quotaon `pwd`/debian/quota/sbin
-	-mv `pwd`/debian/quota/usr/sbin/quotaoff `pwd`/debian/quota/sbin
-
 # Build architecture-independent files here.
 binary-indep: build install
 # We have nothing to do by default.

Bug#1059178: approx: diff for NMU version 5.12-2.1

[Chris Hofstaedtler]

Control: tags 1059178 + patch
Control: tags 1059178 + pending

Dear maintainer,

I've prepared an NMU for approx (versioned as 5.12-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru approx-5.12/debian/approx.install approx-5.12/debian/approx.install
--- approx-5.12/debian/approx.install	2023-09-10 06:10:50.0 +0200
+++ approx-5.12/debian/approx.install	2024-04-22 01:33:12.0 +0200
@@ -1,5 +1,5 @@
 approx		usr/sbin
 approx-import	usr/sbin
 etc/approx.conf	etc/approx
-etc/approx.socket	lib/systemd/system
-etc/approx@.service	lib/systemd/system
+etc/approx.socket	usr/lib/systemd/system
+etc/approx@.service	usr/lib/systemd/system
diff -Nru approx-5.12/debian/changelog approx-5.12/debian/changelog
--- approx-5.12/debian/changelog	2023-09-10 06:10:50.0 +0200
+++ approx-5.12/debian/changelog	2024-04-22 01:33:25.0 +0200
@@ -1,3 +1,11 @@
+approx (5.12-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd units into /usr/lib/systemd/system.
+(Closes: #1059178)
+
+ -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:33:25 +0200
+
 approx (5.12-2) unstable; urgency=medium
 
   * Team upload

Bug#1069634: /usr/bin/findmnt: util-linux: findmnt -D produces incorrect output

[Lane Jennison]

Package: util-linux
Version: 2.40-6
Severity: normal
File: /usr/bin/findmnt
X-Debbugs-Cc: l...@lane-fu.com

Dear Maintainer,

Known Bug resolved in upstream package.

findmnt -D returns inode output instead of human-readable byte output.

Upstream commit aa0c45e8686df509c169121473d2cfb4fe18c3ea should resolve
issue.   

See https://github.com/util-linux/util-linux/pull/2915

Thank you!

lane

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

Kernel: Linux 6.8.7-edge-rockchip-rk3588 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages util-linux depends on:
ii  libblkid1  2.40-6
ii  libc6  2.37-18
ii  libcap-ng0 0.8.5-1
ii  libcrypt1  1:4.4.36-4
ii  libmount1  2.40-6
ii  libpam0g   1.5.3-7
ii  libselinux13.5-2+b2
ii  libsmartcols1  2.40-6
ii  libsystemd0255.4-1+b1
ii  libtinfo6  6.4+20240414-1
ii  libudev1   255.4-1+b1
ii  libuuid1   2.40-6

Versions of packages util-linux recommends:
ii  sensible-utils  0.0.22

Versions of packages util-linux suggests:
ii  dosfstools  4.2-1.1
ii  kbd 2.6.4-2
pn  util-linux-extra
pn  util-linux-locales  

-- no debconf information

Bug#1058697: fonts-fork-awesome: expected files missing?

[Nicholas D Steeves]

Hi Paul,

Paul Gevers  writes:

> For src:cacti (of which I'm de-facto the only maintainer) I received a 
> bug report in Ubuntu (#2046431) about missing files. As cacti doesn't 
> ship these files, but Depends on fonts-fork-awesome I was wondering if 
> cacti upstream is shipping "weird" files or if the files are reasonable 
> to be expected and are just missing to be build/shipped in 
> fonts-fork-awesome.
>
> We're at least talking about ./webfonts/fa-solid-900.woff2 and 
> ./css/all.css.

As far as I can tell the above are copies of FontAwesome webfonts.

apt-file list fonts-fork-awesome | grep css
https://github.com/ForkAwesome/Fork-Awesome/tree/master/css

It looks like we're not installing the "min" variant, which wouldn't
solve this cacti bug.

> See below for my reply to the Ubuntu bug report.
>
> Paul
>
> On 14-12-2023 10:13, Francis Greaves wrote:
[snip]
>> I setup everything, added the Gexport Plugin from here
>> https://github.com/Cacti/plugin_gexport, but in the log I had 4 PHP
>> errors relating to missing files:
>> 
>> /usr/share/cacti/site/include/fa/webfonts/fa-solid-900.woff2
>> /usr/share/cacti/site/include/fa/css/all.css

These look like FontAwesome assets to me.

> Did this error only occur after you added the plugin?
>
>> Looking at the folder structure compared with the official download from
>> the Cacti site:

Here is the official download of ForkAwesome, which doesn't contain
these files:

  https://github.com/ForkAwesome/Fork-Awesome/archive/1.2.0.zip

> In Debian (and hence in Ubuntu) we try to depend on packages providing 
> functionality instead of embedding other projects in source packages. 
> For cacti in Ubuntu, the Awesome Font is delivered by the 
> fonts-fork-awesome package. You'll see that include/fa is a soft-link.
>
>> the include/fa/css folder only had two items fork-awesome.css and
>> v5-compat.css when it should have 16 items
>> 
>> the include/fa/ folder only has 5 items when it should have 10 and in
>> particular has NO webfonts at all.
>> 
>> Just as a test before moving to the official download I copied the
>> include/fa/webfonts folder and the contents of the include/fa/css folder
>> to the Ubuntu install

I don't understand what fonts-fork-awesome is supposed to do about
this.  Isn't this a vendoring issue?

> So, I wonder if we should request changes to the fonts-fork-awesome 
> package. Unfortunately, I'm not experience in how webfonts work.
>

I confess that I'm not either, but I suspect that src:cacti might need
integration work to cope with unvendoring ForkAwesome--if that's the
cause of this.  My primary hypothesis is that this is upstream src:cacti
FontAwesome cruft.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1069633: Time to remove yasm from Debian?

[Petter Reinholdtsen]

Package: yasm
Version: 1.3.0-4

In https://github.com/yasm/yasm/issues/164 >, the upstream
developer of yasm states "I'm still alive, but have moved on to other
projects. If someone else wants to take on maintainership, I'd be happy
to give them the access to this repo do so (presumably with some kind of
transitional period where I would review/approve PRs).".  The many open
security issues listed on
https://security-tracker.debian.org/tracker/source-package/yasm >
are all unsolved, and bsed on the statement above and the time duration
since it was expressed it seem unlikely that this will change any time
soon.

Perhaps it is time to remove yasm from Debian and move all reverse build
dependencies to use a different assembler?

-- 
Happy hacking
Petter Reinholdtsen

Bug#1069632: viking: ruler tool makes viking hang due to uninitialized value

[Vincent Lefevre]

Package: viking
Version: 1.10-3
Severity: important
Tags: upstream fixed-upstream patch

The ruler tool makes viking hang due to an uninitialized value.

Until now I was using the attached patch fixing this problem, from

https://github.com/viking-gps/viking/pull/175/commits/a68acdedbe7421e9980b6611229f92f5be2b65fb

See https://github.com/viking-gps/viking/pull/175

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 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

Versions of packages viking depends on:
ii  gpsbabel 1.9.0+ds-2+b2
ii  libbz2-1.0   1.0.8-5.1
ii  libc62.37-18
ii  libcairo21.18.0-3+b1
ii  libcurl3t64-gnutls   8.7.1-3
ii  libexpat12.6.2-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b3
ii  libgeoclue-2-0   2.7.1-2+b1
ii  libgexiv2-2  0.14.2-2+b2
ii  libglib2.0-0t64  2.78.4-6
ii  libgps30t64  3.25-3+b1
ii  libgtk-3-0t643.24.41-4
ii  libjson-glib-1.0-0   1.8.0-2+b1
ii  libmagic1t64 1:5.45-3
ii  libnettle8t643.9.1-2.2
ii  liboauth01.0.3-5+b1
hi  libpango-1.0-0   1.51.0+ds-4
hi  libpangocairo-1.0-0  1.51.0+ds-4
ii  libsqlite3-0 3.45.3-1
ii  libx11-6 2:1.8.7-1
ii  libzip4t64   1.7.3-1.1+b1
ii  zlib1g   1:1.3.dfsg-3.1

Versions of packages viking recommends:
ii  expect [expect-dev]  5.45.4-3

Versions of packages viking suggests:
pn  gpsd  
ii  yelp  42.2-1+b2

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
diff --git a/src/vikviewport.c b/src/vikviewport.c
index 85adb891..3f696ab2 100644
--- a/src/vikviewport.c
+++ b/src/vikviewport.c
@@ -2026,6 +2026,7 @@ void vik_viewport_compute_bearing ( VikViewport *vp, gint 
x1, gint y1, gint x2,
 *baseangle = M_PI - atan2(tx-x1, ty-y1);
 *angle -= *baseangle;
   } else{
+*baseangle = 0;
 *angle = atan2((y2-y1), (x2-x1)) + M_PI_2;
   }
 

Bug#1062007: notfound 1062007 in 3.0.0-alpha5-1, closing 1062007

[Andreas Beckmann]

On 21/04/2024 18.28, Sebastian Ramacher wrote:

# changes SONAME in experimental, so a transition to libdaq3 would also
# provide the required changes for time_t


OK. In that case maybe the package should be binNMUed in experimental 
and then the bug could be closed with the version in experimental, too.



Andreas

Bug#1063936: xxdiff is blind to differences between process substitution inputs

[Florian Schlichting]

Hi Kingsley,

> Please allow me to draw your attention to
> a way I think it may be improved.

> $ xxdiff <( echo a ) <( echo b )
> 
> Screen shots of what I saw are attached.
> 
> As you can see in them, replacing
> 
> process substitution
> 
> with
> 
> files
> 
> works.
> 
> So does diff
> 
> $ diff <( echo a ) <( echo b )
> 1c1
> < a
> ---
> > b
> 
> 
> My humble suggestion:
> 
> Improve xxdiff to work with process substitution.

I think that's an interesting idea, however I'm not sure how easy it is
to implement that, and who would have the time to try their hand on
this.

I notice that using process substitution only works when both inputs are
of that kind; comparing process substitution with a regular file results
in an Internal error referencing src/buffer.inline.h:76

Florian

Bug#1069631: loki-ecmwf: Unsatisfiable dependency: python3-loki etc

[Jeremy Bícha]

Source: loki-ecmwf
Version: 0.2.0-1
Severity: serious

After https://salsa.debian.org/science-team/loki-ecmwf/-/commit/fd228e81dcb,
python3-loki-ecmwf-lint-rules has Depends: python3-loki but that
package is not available in Debian.

https://qa.debian.org/excuses.php?package=loki-ecmwf complains about
other uninstallable packages but I did not check them.

Thank you,
Jeremy Bícha

Bug#1068101: RFS ping mini-httpd/1.30-10 -- Small HTTP server

[Alexandru Mihail]

Hi, thanks for your considerations !

>   It looks like you've been maintaining this package for a while now.
> Have you considered applying to become a Debian Maintainer[1]? That
> would allow you to eventually be given upload permissions on the
> mini-
> httpd package, so you wouldn't need to keep filing RFS bugs. :)
> 
Yes, I've been thinking about applying for a long time, my first
sponsor ( who helped me with the first 2-3 versions ) suggested it as
well, but I was not yet sure how long I should wait as a non-uploading
maintainer before applying. I do need a DD to "vouch" for me, don't I ?
I don't know how busy my first (and only regular) sponsor is, he's been
away for a few releases..I hope he'll reply if I ask for some help.
Thanks for the idea :)
>   Also, I suspect people might be more hesitant to sponsor packages
> after the actions of "Jia Tan" and the xz backdoor. Going through the
> process to become a DM can help demonstrate your commitment to good
> packaging and the Debian project as a whole. (I'm not in any way
> trying
> to suggest you might be a malicious actor, just that there's recently
> been [rightfully] a lot of scrutiny of how easy it can be for someone
> to mess with packages shipped by a distribution.)

Yes you,re right, perhaps that is a cause as well. Usually, RFS were
closed in a matter of days before for this package. Jia's actions did
produce some shockwaves in the FOSS/Linux world for sure..

Have a great day, I'll look into starting the new member process !
Alexandru Mihail
> 
> Mathias
> 
> [1] -- https://nm.debian.org/public/newnm


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

Bug#1064459: refining DEP17 patches for glibc and base-files

[Helmut Grohne]

Hi Santiago,

On Fri, Apr 19, 2024 at 07:24:15PM +0200, Santiago Vila wrote:
> I've added two commits, one to create symlinks with a "shell" for, and the 
> last
> one for a sample changelog (because this is really a "team upload" or a 
> "guest upload"
> more than a NMU). I think for simplicity it's ok if you skip the changelog 
> part
> in your repo.

I've updated my demo repository with your patch.

https://salsa.debian.org/helmutg/bootstrap-usrmerge-demo/-/commit/6425c8cde53596199cd37bb1625d1dfb2a4b74d0

I'm happy to call it guest upload while I find team upload slightly
misleading.

I avoid patching changelogs in the demo to avoid the need for
unnecessary rebasing. It's a functional demo.

For util-linux, I think Chris will send me an encrypted version of a
signed .changes file such that I only perform the upload not even the
signing. Please let me know if you prefer that approach.

Helmut

Bug#1069630: libcupsfilters-dev and libcupsfilters2-dev have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, /usr/lib/x86_64-linux-gnu/libcupsfilters.so and /usr/lib/x86_64-

[Helmut Grohne]

Package: libcupsfilters2-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libcupsfilters-dev

The files
 * /usr/lib/x86_64-linux-gnu/libcupsfilters.a
 * /usr/lib/x86_64-linux-gnu/libcupsfilters.so
 * /usr/lib/x86_64-linux-gnu/pkgconfig/libcupsfilters.pc
are contained in the packages
 * libcupsfilters-dev/1.28.17-4 as present in unstable
 * libcupsfilters2-dev/2.0.0-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Please figure out which of these packages should properly own the
affected files and reassign the bug as appropriate. When doing so,
please add the other package to the set of affected packages using
"Control: affects -1 + " to avoid the filing of duplicates.

The other package should stop installing the files. In case the files
are being moved between packages, Breaks and Replaces should be
declared. In this case, please refer to policy section 7.6 for details.
Another useful resource is https://wiki.debian.org/PackageTransition.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Bug#1069625: Acknowledgement (gstreamer1.0: Don't build ptp-helper on hppa)

[John David Anglin]

Updated patch to fix install.

Dave

--
John David Anglin  dave.ang...@bell.net
--- control.save2024-04-21 15:25:15.368645225 +
+++ control 2024-04-21 15:14:58.183856344 +
@@ -18,7 +18,7 @@
libdw-dev [i386 amd64 armel armhf arm64 powerpc ppc64 ppc64el 
mipsel mips64el riscv64],
bison,
flex,
-   rustc,
+   rustc [!hppa],
libgirepository1.0-dev,
gir1.2-glib-2.0,
gir1.2-freedesktop,
--- libgstreamer1.0-0.install.save  2024-04-21 16:38:07.810032050 +
+++ libgstreamer1.0-0.install   2024-04-21 16:38:17.922110631 +
@@ -1,5 +1,4 @@
 usr/lib/*/gstreamer-1.0/*.so
 usr/lib/*/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
-usr/lib/*/gstreamer1.0/gstreamer-1.0/gst-ptp-helper
 usr/lib/*/*.so.*
 usr/share/locale
--- rules.save  2024-04-21 15:25:23.96877 +
+++ rules   2024-04-21 16:40:18.347048541 +
@@ -44,6 +44,10 @@
 conf_flags += -Dlibunwind=disabled -Dlibdw=disabled
 endif
 
+ifneq (,$(filter $(DEB_HOST_ARCH),hppa))
+conf_flags += -Dptp-helper=disabled
+endif
+
 infiles := \
libgstreamer1.0-0.postinst
 
--- libgstreamer1.0-0.postinst.in.save  2024-04-21 19:15:04.053817208 +
+++ libgstreamer1.0-0.postinst.in   2024-04-21 19:15:41.034100581 +
@@ -2,7 +2,7 @@
 
 set -e
 
-if [ "$1" = configure ]; then
+if [ "$1" = configure && test -f 
/usr/lib/@MULTIARCH@/gstreamer1.0/gstreamer-1.0/gst-ptp-helper ]; then
 # If we have setcap is installed, try setting 
cap_net_bind_service,cap_net_admin+ep,
 # which allows us to install our helper binary without the setuid bit.
 if command -v setcap > /dev/null; then

Bug#1067628: cctools: diff for NMU version 9.9-4.1

[Sebastian Ramacher]

Control: tags 1067628 + patch


Dear maintainer,

I've prepared an NMU for cctools (versioned as 9.9-4.1). The diff
is attached to this message.

Regards.


-- 
Sebastian Ramacher
diff -Nru cctools-9.9/debian/changelog cctools-9.9/debian/changelog
--- cctools-9.9/debian/changelog	2023-12-06 11:26:18.0 +0100
+++ cctools-9.9/debian/changelog	2024-04-21 22:18:03.0 +0200
@@ -1,3 +1,13 @@
+cctools (9.9-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Michael Hudson-Doyle ]
+  * Undefine _FILE_OFFSET_BITS and _TIME_BITS in rmonitor_helper.c so the library's
+interposition of open/open64 still works. (Closes: #1067628)
+
+ -- Sebastian Ramacher   Sun, 21 Apr 2024 22:18:03 +0200
+
 cctools (9.9-4) unstable; urgency=medium
 
   * Fix to build to correct globus configuration, enable broken
diff -Nru cctools-9.9/debian/patches/globus-flags.patch cctools-9.9/debian/patches/globus-flags.patch
--- cctools-9.9/debian/patches/globus-flags.patch	2023-12-06 11:26:18.0 +0100
+++ cctools-9.9/debian/patches/globus-flags.patch	2024-03-20 03:59:10.0 +0100
@@ -15,3 +15,17 @@
  CCTOOLS_GLOBUS_CCFLAGS=${globus_ccflags}
  
  export CCTOOLS_TEST_CCFLAGS=${test_ccflags}
+--- a/resource_monitor/src/rmonitor_helper.c
 b/resource_monitor/src/rmonitor_helper.c
+@@ -13,6 +13,11 @@
+ #define _GNU_SOURCE // Aah!!
+ #endif
+ 
++/* Building with these macros defines interferes with this files attempt to
++   interpose both open and open64 */
++#undef _FILE_OFFSET_BITS
++#undef _TIME_BITS
++
+ #include 
+ #include 
+ #include 

Bug#1069629: ITP: python-paginate -- Python module that helps dividing large lists of items into pages

[Boyuan Yang]

Package: wnpp
Owner: Boyuan Yang 
Severity: wishlist

* Package name: python-paginate
  Version : 0.5.6
  Upstream Contact: Christoph Haas 
* URL : https://github.com/Pylons/paginate
* License : Expat
  Programming Lang: Python
  Description :  Python module that helps dividing large lists of items 
into pages

 This module helps dividing large lists of items into pages.
 The user is shown one page at a time and can navigate to other pages.

This package is a dependency to mkdocs-material package.

This package will be maintained under Debian Python Team umbrella.

Thanks,
Boyuan Yang


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

Bug#1068818: sngrep: CVE-2024-3119 CVE-2024-3120

[Moritz Muehlenhoff]

On Sun, Apr 21, 2024 at 07:35:43PM +, Victor Seva wrote:
> Hi,
> 
> 
> I've just uploaded sngrep 1.8.1-1 to sid and prepared 1.6.0-1+deb12u1 for 
> bookworms-security [0].
> 
> Attached debdiff file.
> 
> Waiting for you reply,
> Victor
> 
> [0] 
> https://salsa.debian.org/pkg-voip-team/sngrep/-/tags/debian%2F1.6.0-1+deb12u1

Hi Victor,
diff looks fine, but I don't believe this really needs a DSA; it's rather 
obscure attack vector.
I think addressing this via the next Bookworm point release is perfectly fine, 
what do you think?

Procedure is outlined at
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions

Cheers,
Moritz

Bug#1069267: 2.1.2-59 preinst script fails

[Jamie Heilman]

> > ln -s /etc/runit/runsvdir/current "$T/service"

Note this should have read:

ln -s runit/runsvdir/current "$T/service"

> Overall it seems that if do that automatically too many things can
> go wrong.  However the code can be used as an example in the NEWS,
> so thanks for sharing and test it!

If there's no appetite to attempt the migration automatically then
the preinst script will need to continue to support the case where
/etc/service is a directory.  


--- runit.preinst.orig  2024-03-22 23:18:48.0 +
+++ runit.preinst   2024-04-21 19:16:18.011931776 +
@@ -14,7 +14,7 @@
 
 if [ ! -e /etc/service ]; then #new install
ln -s /etc/runit/runsvdir/current /etc/service
-else
+elif [ -h /etc/service ]; then
servlink=$(readlink /etc/service) # should be 
/etc/runit/runsvdir/current
if [ "$servlink" != '/etc/runit/runsvdir/current' ]; then
# transition to enable runsvchdir, started in 2.1.2-28, to be 
removed in future:


Should do the trick.

-- 
Jamie Heilman http://audible.transient.net/~jamie/

Bug#1066672: httest: diff for NMU version 2.4.23-1.6

[Sebastian Ramacher]

Dear maintainer,

I've prepared an NMU for httest (versioned as 2.4.23-1.6). The diff
is attached to this message.

Regards.


-- 
Sebastian Ramacher
diff -Nru httest-2.4.23/debian/changelog httest-2.4.23/debian/changelog
--- httest-2.4.23/debian/changelog	2023-12-12 10:52:16.0 +0100
+++ httest-2.4.23/debian/changelog	2024-04-21 21:15:11.0 +0200
@@ -1,3 +1,12 @@
+httest (2.4.23-1.6) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Steve Langasek ]
+  * debian/patches: Fix implicit definitions (Closes: #1066672)
+
+ -- Sebastian Ramacher   Sun, 21 Apr 2024 21:15:11 +0200
+
 httest (2.4.23-1.5) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru httest-2.4.23/debian/patches/no-implicit-declarations.patch httest-2.4.23/debian/patches/no-implicit-declarations.patch
--- httest-2.4.23/debian/patches/no-implicit-declarations.patch	1970-01-01 01:00:00.0 +0100
+++ httest-2.4.23/debian/patches/no-implicit-declarations.patch	2024-04-21 21:14:30.0 +0200
@@ -0,0 +1,43 @@
+Description: add missing includes
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066672
+Last-Update: 2024-04-10
+Forwarded: no
+
+Index: httest-2.4.23/src/socks_module.c
+===
+--- httest-2.4.23.orig/src/socks_module.c
 httest-2.4.23/src/socks_module.c
+@@ -25,6 +25,8 @@
+ /
+  * Includes
+  ***/
++#include 
++
+ #include "module.h"
+ #ifndef HAVE_NO_NETINET
+   #include 
+Index: httest-2.4.23/src/annotation_module.c
+===
+--- httest-2.4.23.orig/src/annotation_module.c
 httest-2.4.23/src/annotation_module.c
+@@ -25,6 +25,7 @@
+ /
+  * Includes
+  ***/
++#include 
+ #include "module.h"
+ 
+ /
+Index: httest-2.4.23/src/dbg_module.c
+===
+--- httest-2.4.23.orig/src/dbg_module.c
 httest-2.4.23/src/dbg_module.c
+@@ -24,6 +24,7 @@
+ /
+  * Includes
+  ***/
++#include 
+ #include "store.h"
+ #include "module.h"
+ 
diff -Nru httest-2.4.23/debian/patches/series httest-2.4.23/debian/patches/series
--- httest-2.4.23/debian/patches/series	2023-12-12 10:52:16.0 +0100
+++ httest-2.4.23/debian/patches/series	2024-04-21 21:14:30.0 +0200
@@ -4,3 +4,4 @@
 fix-gcc-10.patch
 autoconf-2.70.patch
 pcre2.patch
+no-implicit-declarations.patch

Bug#1069628: trantor: diff for NMU version 1.5.12+ds-1.2

[Sebastian Ramacher]

Package: trantor
Version: 1.5.12+ds-1.1
Severity: normal
Tags: patch  pending


Dear maintainer,

I've prepared an NMU for trantor (versioned as 1.5.12+ds-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru trantor-1.5.12+ds/debian/changelog trantor-1.5.12+ds/debian/changelog
--- trantor-1.5.12+ds/debian/changelog	2024-04-21 12:04:17.0 +0200
+++ trantor-1.5.12+ds/debian/changelog	2024-04-21 21:11:56.0 +0200
@@ -1,3 +1,12 @@
+trantor (1.5.12+ds-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control:
+- Drop hard-coded dependency on lib-cares2
+- Add libc-ares-dev to Build-Depends
+
+ -- Sebastian Ramacher   Sun, 21 Apr 2024 21:11:56 +0200
+
 trantor (1.5.12+ds-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru trantor-1.5.12+ds/debian/control trantor-1.5.12+ds/debian/control
--- trantor-1.5.12+ds/debian/control	2024-04-21 12:04:17.0 +0200
+++ trantor-1.5.12+ds/debian/control	2024-04-21 21:08:16.0 +0200
@@ -2,7 +2,7 @@
 Maintainer: Pierre-Elliott Bécue 
 Section: web
 Priority: optional
-Build-Depends: cmake, debhelper-compat (=13), dh-cmake, dh-cmake-compat (=1)
+Build-Depends: cmake, debhelper-compat (=13), dh-cmake, dh-cmake-compat (=1), libc-ares-dev
 Standards-Version: 4.6.1
 Vcs-Browser: https://salsa.debian.org/debian/trantor
 Vcs-Git: https://salsa.debian.org/debian/trantor.git
@@ -11,7 +11,7 @@
 
 Package: libtrantor1
 Architecture: any
-Depends: libc-ares2, ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: Non-blocking I/O cross-platform TCP network library
  Trantor is a non-blocking I/O cross-platform TCP network library, using C++14.
  Drawing on the design of Muduo Library

Bug#1069627: libapache2-mod-security2: Homepage in package details points to a non-existent GitHub repository

[Ville Lehtinen]

Package: libapache2-mod-security2
Version: 2.9.7-1+b1
Severity: minor
X-Debbugs-Cc: vee.lehti...@gmail.com

Dear Maintainer,

Homepage has a typo:
https://github.com/SpiderLapbs/ModSecurity

"/SpiderLapbs" should be "/SpiderLabs", although the repository has moved:
https://github.com/SpiderLabs/ModSecurity

Fixed address redirects here:
https://github.com/owasp-modsecurity/ModSecurity

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

Kernel: Linux 6.1.0-20-cloud-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to C.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 libapache2-mod-security2 depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.59-1~deb12u1
ii  libapr1 1.7.2-3
ii  libaprutil1 1.6.3-1
ii  libc6   2.36-9+deb12u4
ii  libcurl3-gnutls 7.88.1-10+deb12u5
pn  liblua5.1-0 
ii  libpcre2-8-010.42-1
ii  libxml2 2.9.14+dfsg-1.3~deb12u1
ii  libyajl22.1.0-3+deb12u2

Versions of packages libapache2-mod-security2 recommends:
pn  modsecurity-crs  

libapache2-mod-security2 suggests no packages.

Bug#1069549: racket: FTBFS on armel: dh_install: error: missing files, aborting

[David Bremner]

Control: tag -1 confirmed

Lucas Nussbaum  writes:

> Source: racket
> Version: 8.12+dfsg1-7
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on armel.

Thanks for the report. I don't know why it wasn't triggered previously,
but I can confirm the problem is not architecture specific, and I can
replicate it on amd64 with

CONFIG_ARGS_amd64 := --disable-docs --enable-bc

Rather than being architecture specific it seems related to the
configuration options that happen to only be used for armel at the
moment.

Bug#1069624: rapidfuzz: Fails to build on arch: all

[Julian Gilbey]

Hi Jeremy,

On Sun, Apr 21, 2024 at 02:01:26PM -0400, Jeremy Bícha wrote:
> Source: rapidfuzz
> Version: 3.6.2+ds-2
> Severity: serious
> Tags: ftbfs
> 
> The arch: all build for rapidfuzz is failing:
> 
> https://buildd.debian.org/status/package.php?p=rapidfuzz
> 
> If you use sbuild, I believe you can test this with
> sbuild -arch-all --no-arch-any

Thanks for flagging this.  I've only just fixed taskflow, and will be
able to look at rapidfuzz later this week, all being well.  It's
surprising how many issues new packages can throw up when they're
first build on the multiple archs by the buildds!

Best wishes,

   Julian

Bug#1068101: RFS ping mini-httpd/1.30-10 -- Small HTTP server

[Mathias Gibbens]

Hi Alexandru,

  I haven't reviewed your package, however:

On Sun, 2024-04-21 at 19:42 +0300, Alexandru Mihail wrote:
> Thanks a lot and have a nice day,
> Alexandru Mihail
> mini-httpd maintainer

  It looks like you've been maintaining this package for a while now.
Have you considered applying to become a Debian Maintainer[1]? That
would allow you to eventually be given upload permissions on the mini-
httpd package, so you wouldn't need to keep filing RFS bugs. :)

  Also, I suspect people might be more hesitant to sponsor packages
after the actions of "Jia Tan" and the xz backdoor. Going through the
process to become a DM can help demonstrate your commitment to good
packaging and the Debian project as a whole. (I'm not in any way trying
to suggest you might be a malicious actor, just that there's recently
been [rightfully] a lot of scrutiny of how easy it can be for someone
to mess with packages shipped by a distribution.)

Mathias

[1] -- https://nm.debian.org/public/newnm


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

Bug#1069626: fuse-zip: isolation-machine autopkgtest fails: times out without any logging

[Paul Gevers]

Source: fuse-zip
Version: 0.5.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine

Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for 
isolation-machine tests on ci.debian.net for amd64 and added your 
package to the list to use that. However, it fails. Can you please 
investigate the situation and fix it? I copied some of the output at the 
bottom of this report, albeit there is nothing to see as the test 
doesn't log anything.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing, but because machine-isolation 
support by ci.debian.net is new I have not marked this bug as serious (yet).


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/packages/f/fuse-zip/testing/amd64/45706859/

46s autopkgtest [15:26:31]: test blackbox: [---
10046s autopkgtest [18:13:11]: ERROR: timed out on command "su -s 
/bin/bash debci -c set -e; exec /tmp/autopkgtest.aZzNr9/wrapper.sh 
--artifacts=/tmp/autopkgtest.aZzNr9/blackbox-artifacts 
--chdir=/tmp/autopkgtest.aZzNr9/build.mtV/src 
--env=DEB_BUILD_OPTIONS=parallel=2 --env=DEBIAN_FRONTEND=noninteractive 
--env=LANG=C.UTF-8 --unset-env=LANGUAGE --unset-env=LC_ADDRESS 
--unset-env=LC_ALL --unset-env=LC_COLLATE --unset-env=LC_CTYPE 
--unset-env=LC_IDENTIFICATION --unset-env=LC_MEASUREMENT 
--unset-env=LC_MESSAGES --unset-env=LC_MONETARY --unset-env=LC_NAME 
--unset-env=LC_NUMERIC --unset-env=LC_PAPER --unset-env=LC_TELEPHONE 
--unset-env=LC_TIME --script-pid-file=/tmp/autopkgtest_script_pid 
--source-profile --stderr=/tmp/autopkgtest.aZzNr9/blackbox-stderr 
--stdout=/tmp/autopkgtest.aZzNr9/blackbox-stdout 
--tmp=/tmp/autopkgtest.aZzNr9/autopkgtest_tmp 
--make-executable=/tmp/autopkgtest.aZzNr9/build.mtV/src/debian/tests/blackbox 
-- /tmp/autopkgtest.aZzNr9/build.mtV/src/debian/tests/blackbox" (kind: test)

10047s autopkgtest [18:13:12]: test blackbox: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069596: xscreensaver does not ask password on first key hit

[Alessandro Vesely]

Hi,

I'm afraid I won't try next screensaver version.  The bug has been 
showing on a server which I don't want to reboot.  After the logged 
event I'm using slock.


Best
Ale

On 21/04/2024 16:52, Tormod Volden wrote:

Thanks for your report. It would be worthwhile to check if this is a
bug that is already fixed in the newer version of xscreensaver 6.08
that is available in Debian unstable. Can you please try installing
the 6.08 version from Debian unstable? If the binaries don't install
as-is, the package can be safely rebuilt without changes on your
Debian stable system. (Hopefully we can get 6.08 into
bookworm-backports later.)

Regards,
Tormod

Bug#1069102: linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares

[Mark Ullmann]

Package: src:linux
Version: 6.1.85-1
Followup-For: Bug #1069102
X-Debbugs-Cc: email4deb...@gmx.net

Dear Maintainer,

I noticed the same issue.

I have a mount:
mount -t cifs //XXX/Backups/borg-backup /mnt/backups -o
noserverino,credentials=/etc/xxx,file_mode=0777,dir_mode=0777  -vvv

In the mounted directory, a folder is missing. I can see the folder
when I connect to the share via Dolphin.
(This is a backup-drive and I noticed because borg-backup threw errors.)

This is reproducible: after a reboot and mounting the share again, the same
folder is missing and the other folders are shown.


I build a kernel with the patch from #26, which I am running right now. The
problem seems to be gone: borg-backup now runs cleanly. So I assume the mount
is fine with the patch from #26.

I could probably test a kernel if it installs on stable.

Best, Mark.


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

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

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


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: TUXEDO
product_name: N24_25BU
product_version: Not Applicable  
chassis_vendor: TUXEDO
chassis_version: N/A 
bios_vendor: American Megatrends Inc.
bios_version: 5.12
board_vendor: TUXEDO
board_name: N24_25BU
board_version: Not Applicable  

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1558:2410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer HD Graphics 620 [1558:2410]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th/8th Gen Core Processor Gaussian Mixture Model [1558:2410]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: CLEVO/KAPOK Computer Sunrise Point-LP USB 3.0 xHCI 
Controller [1558:2410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Thermal subsystem [8086:9d31] (rev 21)
Subsystem: CLEVO/KAPOK Computer Sunrise Point-LP Thermal subsystem 
[1558:2410]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: CLEVO/KAPOK Computer Sunrise Point-LP CSME HECI [1558:2410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA 
Controller [AHCI mode] [8086:9d03] (rev 21) (prog-if 01 [AHCI 1.0])
Subsystem: CLEVO/KAPOK Computer Sunrise Point-LP SATA Controller [AHCI 
mode] [1558:2410]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ 

Bug#1069625: gstreamer1.0: Don't build ptp-helper on hppa

[John David Anglin]

Source: gstreamer1.0
Version: 1.24.2-1
Severity: normal
Tags: ftbfs patch

Dear Maintainer,

The standalone ptp-helper application in gstreamer1.0 1.24.2-1 requires
the rust compiler to build.  rustc is not available on hppa, alpha,
hurd-amd64, hurd-i386, ia64, m68k and sh4.  The current dependence on
rustc blocks the entire package from being built.  This indirectly
blocks hundreds of packages from being built.

I do not believe the ptp-helper is useful on hppa.  PTP support
requires hardware time stamping.  None of the Ethernet hardware
commonly used in PA-RISC machines have this capability.

gstreamer1.0 builds successfully with the attached patch on hppa.
Work is needed to add other architectures without rustc and to adjust
the installation files.

Regards,
Dave Anglin

-- System Information:
Debian Release: trixie/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 6.8.7 (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- control.save2024-04-21 15:25:15.368645225 +
+++ control 2024-04-21 15:14:58.183856344 +
@@ -18,7 +18,7 @@
libdw-dev [i386 amd64 armel armhf arm64 powerpc ppc64 ppc64el 
mipsel mips64el riscv64],
bison,
flex,
-   rustc,
+   rustc [!hppa],
libgirepository1.0-dev,
gir1.2-glib-2.0,
gir1.2-freedesktop,
--- libgstreamer1.0-0.install.save  2024-04-21 16:38:07.810032050 +
+++ libgstreamer1.0-0.install   2024-04-21 16:38:17.922110631 +
@@ -1,5 +1,4 @@
 usr/lib/*/gstreamer-1.0/*.so
 usr/lib/*/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
-usr/lib/*/gstreamer1.0/gstreamer-1.0/gst-ptp-helper
 usr/lib/*/*.so.*
 usr/share/locale
--- rules.save  2024-04-21 15:25:23.96877 +
+++ rules   2024-04-21 16:40:18.347048541 +
@@ -44,6 +44,10 @@
 conf_flags += -Dlibunwind=disabled -Dlibdw=disabled
 endif
 
+ifneq (,$(filter $(DEB_HOST_ARCH),hppa))
+conf_flags += -Dptp-helper=disabled
+endif
+
 infiles := \
libgstreamer1.0-0.postinst
 

Bug#1069574: age-old and insecure webkit package

[Dmitry Shachnev]

Hi again Hadmut,

On Sun, Apr 21, 2024 at 08:25:23PM +0300, Hadmut Danisch wrote:
> Hi Dmitry,
>
>
> even their own website
>
> https://wkhtmltopdf.org/status.html
>
> says:
>
>*Do not use wkhtmltopdf with any untrusted HTML* – be sure to
>sanitize any user-supplied HTML/JS, otherwise it can lead to
>complete takeover of the server it is running on! Please consider
>using a Mandatory Access Control system like AppArmor or SELinux,
>see recommended AppArmor policy .
>
> Wouldn't it be more than enough or a reason to throw this out of
> debian/ubuntu, until they fixed this?

First, I am the wrong person to ask about this. I am CCing the wkhtmltopdf
maintainer.

Second, wkhtmltopdf is not a leaf package, there are other packages depending
on it:

  Reverse-Recommends
  ==
  * civicrm-common
  * python3-a38

  Reverse-Depends
  ===
  * odoo-16
  * python3-django-wkhtmltopdf
  * python3-pdfkit

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1069624: rapidfuzz: Fails to build on arch: all

[Jeremy Bícha]

Source: rapidfuzz
Version: 3.6.2+ds-2
Severity: serious
Tags: ftbfs

The arch: all build for rapidfuzz is failing:

https://buildd.debian.org/status/package.php?p=rapidfuzz

If you use sbuild, I believe you can test this with
sbuild -arch-all --no-arch-any

Thank you,
Jeremy Bícha

Bug#1069623: ganeti-instance-debootstrap: isolation-machine autopkgtest fails: http://deb.debian.org/debian/dists/jessie doesn't exist

[Paul Gevers]

Source: ganeti-instance-debootstrap
Version: 0.16-8
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine

Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for 
isolation-machine tests on ci.debian.net for amd64 and added your 
package to the list to use that. 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, but because machine-isolation 
support by ci.debian.net is new I have not marked this bug as serious (yet).


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/packages/g/ganeti-instance-debootstrap/testing/amd64/45709257/

 27s autopkgtest [17:54:41]: test install-export-import: 
[---

 28s 512+0 records in
 28s 512+0 records out
 28s 536870912 bytes (537 MB, 512 MiB) copied, 0.487683 s, 1.1 GB/s
 28s Installing instance...
 29s Re-reading the partition table failed.: Invalid argument
 29s I: Retrieving InRelease
 29s I: Retrieving Release
 29s E: Failed getting release file 
http://deb.debian.org/debian/dists/jessie/Release
 30s autopkgtest [17:54:44]: test install-export-import: 
---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Jeremy Bícha]

Simple patch attached.

Thank you,
Jeremy Bícha
From: Jeremy Bicha 
Date: Sun, 21 Apr 2024 13:37:18 -0400
Subject: [PATCH] Mark no-default-features autopkgtest as flaky

Closes: #1069621
---
 debian/tests/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/tests/control b/debian/tests/control
index e97cdaa..e5008bc 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -18,7 +18,7 @@ Depends:
  librust-futures-lite-1+default-dev,
  librust-try-lock-0.2+default-dev,
  librust-waker-fn-1+default-dev,
-Restrictions: allow-stderr
+Restrictions: allow-stderr, flaky
 
 Test-Command: /usr/share/cargo/bin/cargo-auto-test event-listener 5.3.0
  --all-targets

Bug#1069622: firejail: isolation-machine autopkgtest fails: firefox doesn't exist in testing

[Paul Gevers]

Source: firejail
Version: 0.9.72-2
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine

Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for 
isolation-machine tests on ci.debian.net for amd64 and added your 
package to the list to use that. However, it fails if the test runs in 
testing; it passes when run in unstable. Can you please investigate the 
situation and fix it? I copied some of the output at the bottom of this 
report. It looks like the test Depends on packages that aren't available 
in testing. thunderbird and transmission-gtk should be temporarily, but 
firefox isn't going to migrate by design.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing, but because machine-isolation 
support by ci.debian.net is new I have not marked this bug as serious (yet).


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/f/firejail/45706858/log.gz

616s The following packages have unmet dependencies:
616s  autopkgtest-satdep : Depends: thunderbird but it is not installable
616s   Depends: firefox but it is not installable
616s   Depends: transmission-gtk but it is not 
installable


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Jeremy Bícha]

Source: rust-event-listener
Version: 5.3.0-2
Severity: serious
Tags: experimental patch
X-Debbugs-CC: werdah...@riseup.net

rust-event-listener's --no-default-features autopkgtest is failing:

https://ci.debian.net/packages/r/rust-event-listener/unstable/amd64/

This issue will block the rust-event-listener transition. I suggest
marking the autopkgtest as flaky and reporting the issue upstream.

Thank you,
Jeremy Bícha

Bug#1069574: age-old and insecure webkit package

[Hadmut Danisch]

Hi Dmitry,


even their own website

https://wkhtmltopdf.org/status.html

says:

   *Do not use wkhtmltopdf with any untrusted HTML* – be sure to
   sanitize any user-supplied HTML/JS, otherwise it can lead to
   complete takeover of the server it is running on! Please consider
   using a Mandatory Access Control system like AppArmor or SELinux,
   see recommended AppArmor policy .

Wouldn't it be more than enough or a reason to throw this out of 
debian/ubuntu, until they fixed this?



regards

Hadmut

Bug#1069603: [Pkg-openssl-devel] Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

[Paul Gevers]

Hi

On 21-04-2024 5:56 p.m., Sebastian Andrzej Siewior wrote:

The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0.
This was solved by the Perl team with their 0.29 upload. This and 0.30
didn't migrate to testing and in the meantime we got OpenSSL into
unstable which relies on that fix.
The migration was delayed by the time_t transition.


Ack. I figured that out too.


Could britney be hinted to migrate both at the same time? This should
solve the issue you pointed out.


There is no "please test together" knob if that's what you mean (is that 
what you mean?). I have triggered the test manually, so for now the 
lights are green. Because those expire, I have added a hint to ignore 
the failure of the old version in testing.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069574: age-old and insecure webkit package

[Dmitry Shachnev]

Hi Hadmut!

On Sat, Apr 20, 2024 at 09:23:37PM +0300, Hadmut Danisch wrote:
> Package: libqt5webkit5
>
> Version: 5.212.0~alpha4-30
>
>
> Hi,
>
> this was originally a bug report against Ubuntu 24.04 as 2061191, but since
> the package is community maintained and not by Ubuntu, they asked me to
> report it "upstreams".
>
>
> Ubuntu 24.04 beta / Debian bookworm still use libqt5webkit5.
>
> It is not obvious, where it comes from, but the version is still an alpha4,
> and the link in the README seems to suggest, that it still comes from
> https://github.com/annulen/webkit, which redirects to
> https://github.com/qtwebkit/qtwebkit, where the alpha4 tag is over 4 years
> old.
>
> There, the latest README tells:
>
> Code in this repository is obsolete. If you are looking for up-to-date
> QtWebKit use this fork: https://github.com/movableink/webkit
>
> https://github.com/movableink/webkit seems to be still maintained – more or
> less. And calls itself "inofficial mirror"

Unfortunately, movableink/webkit seems to be even less stable or ready than
qtwebkit/qtwebkit. For example, it is known that PyQt5 cannot be built
against it [1], and there are packages in Debian which need it:

  $ reverse-depends python3-pyqt5.qtwebkit
  Reverse-Recommends
  ==
  * linuxcnc-uspace [amd64 arm64 armel armhf i386 mips64el ppc64el s390x]
  * python3-ginga

  Reverse-Depends
  ===
  * frescobaldi [amd64 arm64 armel armhf i386 mips64el ppc64el s390x]
  * manuskript
  * openshot-qt
  * python3-pyface
  * python3-qgis [amd64 arm64 armel armhf i386 mips64el ppc64el s390x]
  * python3-qtpy
  * qutebrowser-qtwebkit
  * yade [amd64 arm64]

> Have a look at
>
> https://blogs.gnome.org/mcatanzaro/2022/11/04/stop-using-qtwebkit/
>
> which calls qtwebkit insecure, poorly maintained, and cites CVEs about
> remote code execution (some of them would have to be fixed in the fork, but
> probably not in the version here in ubuntu).
>
> The problem is, that tools like wkhtmltopdf do use this library and are
> typically used to pull contents from a given URL, i.e. from foreign
> websites.
>
> Processing foreign HTML and Javascript code in conjunction with
> vulnerabilities to remote code execution, this is highly dangerous.

I absolutely agree. Projects like wkhtmltopdf should stop using Qt WebKit
and should be ported to Qt WebEngine or other alternatives [2]. Once they do
that, we will be able to remove Qt WebKit from Debian.

Any help with filing bugs, both upstream and here in Debian, is welcome.

It is also worth noting that our Release Notes explicitly mention [3] that
Qt WebKit is not covered by security support, thus anyone who uses it with
untrusted input data does so on their own risk.

[1]: https://github.com/movableink/webkit/issues/16
[2]: ideally, they should be also ported from Qt 5 to Qt 6
[3]: 
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#browser-security

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1069620: RFS: lua-mode/20231023~git-1 -- Emacs major-mode for editing Lua programs

[Xiyue Deng]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : lua-mode
   Version  : 20231023~git-1
   Upstream contact : immerrr 
 * URL  : https://github.com/immerrr/lua-mode
 * License  : GPL-3+
 * Vcs  : https://salsa.debian.org/emacsen-team/lua-mode
   Section  : lisp

The source builds the following binary packages:

  elpa-lua-mode - Emacs major-mode for editing Lua programs

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

  https://mentors.debian.net/package/lua-mode/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lua-mode/lua-mode_20231023~git-1.dsc

Changes since the last upload:

 lua-mode (20231023~git-1) unstable; urgency=medium
 .
   * Sync to latest upstream snapshot (d074e41)
   * Drop the patch applied upstream and reorder the remaining patch
   * Update upstream license to GPL-3+ following upstream change
   * Add a missing upstream copyright holder

Regards,
-- 
Xiyue Deng

Bug#1063900: gstreamer1.0-plugins-good: missing Breaks+Replaces: gstreamer1.0-plugins-ugly (<< 1.23)

[Jean-Marc]

On Wed, 14 Feb 2024 14:58:16 +0100 Andreas Beckmann  wrote:

Package: gstreamer1.0-plugins-good
Version: 1.23.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,
[...]


Current version in sid are the following ones:

$ apt policy gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly
gstreamer1.0-plugins-good:
 Table de version :
 1.24.2-1 500
500 https://deb.debian.org/debian unstable/main amd64 Packages

gstreamer1.0-plugins-ugly:
 Table de version :
 1.24.2-1+b1 500
500 https://deb.debian.org/debian unstable/main amd64 Packages


The following files are in conflict:

/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so
/usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs


Files mentioned here in the bug report are not present in 
gstreamer1.0-plugins-ugly:1.24.2-1+b1 anymore.


Can you confirm I am not wrong and update the bug report accordingly ?


cheers,


Regards,


Andreas


--
Jean-Marc

(*)
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so
/usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1068101: RFS ping mini-httpd/1.30-10 -- Small HTTP server

[Alexandru Mihail]

Pinging about the RFS - mini-httpd/1.30-10.
If anyone can help with the upload, that would be a huge help. It's
been a month since opening the RFS and some people that proposed
patches for this release are really looking forward to using it.
Mentors page:

  https://mentors.debian.net/package/mini-httpd/

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

  dget -x
https://mentors.debian.net/debian/pool/main/m/mini-httpd/mini-httpd_1.30-10.dsc

Thanks a lot and have a nice day,
Alexandru Mihail
mini-httpd maintainer



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

Bug#1052714: firmware-amd-graphics: Missing firmware for AMD Radeon RX 7000 series cards

[Richard]

I'd also like to support this. The current firmware-amd-graphics is getting
close to being a year old. While of course the Stable branch won't get
up-to-date firmware as that's not the point of firmware, I don't see a
reason at least sid or an experimental branch shouldn't be kept more
up-to-date. And I don't really see a reason why that shouldn't be the case
for testing and stable-updates or stable-backports too.

E.g., a Ryzen 7040's iGPU can't be handled by the 06/2023 firmware package,
it will complain that "amdgpu/gc_11_0_1_me" couldn't be loaded. With at
least the 09/2023 firmware that's not an issue anymore.

Greetings,
Richard

Bug#1069619: RM: ruby-sigar -- ROM; rc-buggy, not needed anymore

[Praveen Arimbrathodiyil]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: ruby-si...@packages.debian.org
Control: affects -1 + src:ruby-sigar
User: ftp.debian@packages.debian.org
Usertags: remove
Control: block -1 by 1069616
Control: block 1067084 by -1

Affected by rc bug #1067084 (blocks t64 transition), not needed anymore 
(its only reverse dependency already has an RM request).


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069618: rust-process-viewer: Fails to build with rust-gtk4 0.8

[Jeremy Bícha]

Source: rust-process-viewer
Version: 0.5.8-4
Severity: important
Forwarded: https://github.com/GuillaumeGomez/process-viewer/pull/206
Tags: ftbfs

The Debian Rust team will update rust-gtk4 from 0.7 to 0.8 soon.
rust-process-viewer is not yet compatible with rust-gtk4 0.8. I
started on the porting but I don't expect to work on this more.

Thank you,
Jeremy Bícha

Bug#1059643: RFS: wstroke/2.1-1 [ITP] -- Mouse gesture plugin for Wayfire.

[Daniel Kondor]

Control: tags -1 - moreinfo


Thank you for the review! I've addressed the issues and lintian warnings 
mentioned. Let me know if there are more issues.


Best,

Daniel

Bug#1069247: libconfig-model-dpkg-perl: test failures

[Julian Andres Klode]

On Sun, Apr 21, 2024 at 04:32:48PM +0300, Niko Tyni wrote:
> [Copying Julian as the apt maintainer.]
> 
> On Sat, Apr 20, 2024 at 09:02:35PM +0300, Niko Tyni wrote:
> > On Sat, Apr 20, 2024 at 11:09:17AM +0200, Dominique Dumont wrote:
> > > On Thursday, 18 April 2024 19:21:55 CEST you wrote:
> > > > Source: libconfig-model-dpkg-perl
> > > > Version: 3.004
> > > > Severity: serious
> > > > Tags: ftbfs
> > > > Justification: fails to build from source
> > > 
> > > This really looks like a bug with prove:
> > > 
> > > $ perl t/reorder.t 
> > > ok 1 -  test re-ordered list
> > > 1..1
> > 
> > > I can't see what's wrong with the output of reorder test...
> > 
> > Looks like something is injecting apt progress messages to stdout with
> > CR characters hiding it on the terminal but obviously not from `prove`.
> > 
> > $ perl t/reorder.t |od -c
> 
> > 460   f   o   r   m   a   t   i   o   n   .   .   .   0   %  \r
> > 500
> > *
> > 540  \r   o   k   1   -   t   e   s   t   r   e
> > 560   -   o   r   d   e   r   e   d   l   i   s   t  \n   1   .
> > 600   .   1  \n
> 
> These come from apt, via libapt-pkg-perl which I don't think has ever
> filtered them away. The thing that broke this is surely output changes
> in apt 2.9.
> 
> The crucial difference wrt. at least bookworm seems to be that the
> apt messages used to end with a line feed "\n" before the actual TAP
> format started.  Now it only has a carriage return "\r" there. Apparently
> `prove` ignores unknown lines, but now interprets all the apt output to
> be part of the first line that ends with the 'ok 1' part. So that gets
> ignored as well.
> 
> I see the TAP format spec says at
> 
>   https://testanything.org/tap-version-14-specification.html
> 
>   A Harness should normalize line endings by replacing any instances of
>   \r\n or \r in the TAP document with \n.
> 
> so I suppose this might be a normal/wishlist bug in `prove`. In that case,
> please note that it needs to be fixed in libtest-harness-perl first as
> src:perl just bundles an older version of it.
> 
> Not sure if apt should go back to ending its output with a line
> feed. Julian, what do you think?
> -- 
> Niko

This should be fixed in apt git already, just needs an upload,
which is waiting-ish for some more merges
-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#963872: RFP: automx2 - Email client configuration made easy (replaces "automx")

[Jakob Haufe]

(cc'ing Jérôme as he expressed interest)
(cc'ing Juri as he started packaging at [1])

I recently learned about automx2 and would love to see it packaged in
Debian as well.

Does either of you still plan to maintain it? Is there anything I can
help with?

Cheers,
sur5r

[1] https://salsa.debian.org/python-team/packages/automx2

-- 
ceterum censeo microsoftem esse delendam.


pgpZqVwN2NQH8.pgp
Description: OpenPGP digital signature

Bug#1068136: Updating golang-github-golang-protobuf-1-5 to fix FTBFS

[Mathias Gibbens]

On Sat, 2024-04-20 at 22:40 +0800, Shengjing Zhu wrote:
> On Sat, Apr 20, 2024 at 10:28 PM Mathias Gibbens  wrote:
> > 
> > Hi Anthony,
> > 
> >   A few weeks ago you uploaded a new version of golang-google-protobuf
> > to unstable which caused a FTBFS in golang-github-golang-protobuf-1-5
> > v1.5.3 [1,2,3]. This has been blocking the transition of various golang
> > packages from unstable to testing.
> > 
> >   I've verified that v1.5.4 of golang-github-golang-protobuf-1-5 builds
> > fine on my amd64 system. `build-rdeps golang-github-golang-protobuf-1-
> > 5-dev` identifies 219 rdeps in main, so I haven't kicked off a `ratt`
> > run testing for any build regressions with the newer version yet.
> > 
> 
> This is a known regression in 1.5.3, see
> https://github.com/golang/protobuf/issues/1596#issuecomment-1981208282

  Since that appears to be the only change in v1.5.4, would there be
any concerns with uploading that version to unstable? This breakage is
starting to cause FTBFS bugs to be filed against affected packages,
such as hugo (#1069371).

Mathias


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

Bug#1069603: [Pkg-openssl-devel] Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

[Sebastian Andrzej Siewior]

On 2024-04-21 13:42:03 [+0200], Paul Gevers wrote:

> opensslfrom testing3.2.1-3
> libcrypt-smime-perlfrom testing0.28-1
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration of openssl to testing
> [1]. Due to the nature of this issue, I filed this bug report against both
> packages. Can you please investigate the situation and reassign the bug to
> the right package?

The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0. 
This was solved by the Perl team with their 0.29 upload. This and 0.30
didn't migrate to testing and in the meantime we got OpenSSL into
unstable which relies on that fix.
The migration was delayed by the time_t transition.

Could britney be hinted to migrate both at the same time? This should
solve the issue you pointed out.

Sebastian

Bug#964214: libdebhelper-perl: dh_auto_configure cannot do out-of-tree builds for qmake buildsystem

[Jiri Palecek]

On Sat, 4 Jul 2020 00:01:15 +0200 Niels Thykier wrote:
> Thorsten Glaser:
> > Package: libdebhelper-perl
> > Version: 13.1
> > Severity: normal
> >
> > Apparently, dh7 fails to tell qmake the location of the source
directory
> > when attempting an out-of-tree build:
> >
> >
> > […]
> >
> >
> > The qmake invocation syntax error message is somewhat misleading,
> > but looking at the invocation command line it becomes somewhat clearer.
> >
>
> Interesting. I am not sure out of source builds have ever been
> supported by qmake (at least not correctly at any rate). If you know
> how to do it, then I am happy to look at fixing it.

Qmake does indeed support out of source builds (and for a long time -
you can find questions about it on the forums from 2010). You can check
a possible implementation of debhelper support for it in MR 125.

Regards

    Jiri Palecek

Bug#1061421: Fails to start after an upgrade

[Jeremy Bícha]

On Sun, Apr 21, 2024 at 2:36 AM Arto Jantunen  wrote:
>
> Jeremy Bícha  writes:
> > Please verify whether wlgreet is working for you now.
>
> Was something changed somewhere? What, where?
>
> On trixie the issue reproduces exactly the same (even with sway upgraded
> to the binNMU'd version from sid).

There have been a huge amount of changes, but most of those changes
were in Unstable and haven't reached Testing yet.

Marc, there is a fix for sway 1.9 in wlgreet 0.5. Do you want to try
if that improves anything here?

Thank you,
Jeremy Bícha

Bug#1066224: radvd_2.19-2_amd64.changes REJECTED

[Geert Stappers]

tags 1066224 pending
stop

On Sun, Apr 21, 2024 at 10:19:31AM +, Debian FTP Masters wrote:
> radvd_2.19-2_amd64.deb: trying to install to unstable, but could not find 
> source (radvd 1:2.19-2)

Oops.  On the upside: an opportunity to add an tag


Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#1069596: xscreensaver does not ask password on first key hit

[Tormod Volden]

Thanks for your report. It would be worthwhile to check if this is a
bug that is already fixed in the newer version of xscreensaver 6.08
that is available in Debian unstable. Can you please try installing
the 6.08 version from Debian unstable? If the binaries don't install
as-is, the package can be safely rebuilt without changes on your
Debian stable system. (Hopefully we can get 6.08 into
bookworm-backports later.)

Regards,
Tormod

Bug#1067691: FTBFS: double free or corruption

[Bernhard Übelacker]

Hello,
I found this one interesting and tried to reproduce it,
and hit this issue quite reliable with an unstable armel chroot,
inside an armhf unstable qemu VM,
or with a Android/LineageOS with real arm CPU.

Unfortunately valgrind is no longer built for armel, and a local armel rebuild
shows issues with latest "-fstack-protector-strong -fstack-clash-protection".

Finally I found this issue leads not to a crash at amd64, but
valgrind uncovers it there reliable [1].

dpkg-buildpackage with valgrind installed uses it automatically.
Therefore the change in [2] might be an improvement?


Increasing the allocation of the input buffer like in [3]
makes the valgrind errors go away.
Unfortunately I don't know what exact size this buffer is expected to have.

Kind regards,
Bernhard




[1]
...
fft const
==1105453== Invalid write of size 4
==1105453==at 0x60BFC25: ??? (in 
/usr/lib/x86_64-linux-gnu/libavutil.so.58.29.100)
==1105453==by 0x4CE1880: av_rdft_calc (in 
/usr/lib/x86_64-linux-gnu/libavcodec.so.60.31.102)
==1105453==by 0x11246F: FFTPlanImpl::execute() (spek-fft.cc:38)
==1105453==by 0x110A76: test_const() (test-fft.cc:21)
==1105453==by 0x1105F5: test_fft() (test-fft.cc:77)
==1105453==by 0x10BF5C: main (test.cc:11)
==1105453==  Address 0x11a828c4 is 4 bytes after a block of size 64 alloc'd
==1105453==at 0x4845DA0: memalign (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==1105453==by 0x4845F01: posix_memalign (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==1105453==by 0x608CC14: av_malloc (in 
/usr/lib/x86_64-linux-gnu/libavutil.so.58.29.100)
==1105453==by 0x1126A0: FFTPlan (spek-fft.h:29)
==1105453==by 0x1126A0: FFTPlanImpl::FFTPlanImpl(int) (spek-fft.cc:27)
==1105453==by 0x112745: FFT::create(int) (spek-fft.cc:24)
==1105453==by 0x1109AE: test_const() (test-fft.cc:13)
==1105453==by 0x1105F5: test_fft() (test-fft.cc:77)
==1105453==by 0x10BF5C: main (test.cc:11)
...


[2]
--- debian/control.orig 2023-01-11 07:25:51.0 +0100
+++ debian/control  2024-04-21 16:30:57.545576734 +0200
@@ -11,3 +11,4 @@ Build-Depends: debhelper-compat (= 13),
libwxgtk3.2-dev,
-   wx-common
+   wx-common,
+   valgrind-if-available
 Standards-Version: 4.6.2


[3]
--- src/spek-fft.h.orig 2023-01-10 05:00:39.0 +0100
+++ src/spek-fft.h  2024-04-21 16:28:07.0 +0200
@@ -28,3 +28,3 @@ public:
 // input data to be aligned by up to 32 bytes (e.g. AVX)
-this->input = (float*) av_malloc(sizeof(float) * input_size);
+this->input = (float*) av_malloc(sizeof(float) * (input_size + 2));
 }

Bug#1069576: blhc: False positive NONVERBOSE BUILD in src:fim

[Simon Ruderich]

Hi Rafael,

On Sat, Apr 20, 2024 at 09:13:58PM +0200, Rafael Laboissière wrote:
> Dear Maintainer,
>
> blhc triggers a NONVERBOSE BUILD error in src:fim
>
> https://salsa.debian.org/debian/fim/-/jobs/5618524
>
>   [snip]
>   $ blhc --debian --line-numbers --color ${SALSA_CI_BLHC_ARGS} 
> ${WORKING_DIR}/*.build || [ $? -eq 1 ]
>   338:NONVERBOSE BUILD: CXX  : g++
>   [snip]
>
> blhc is complaining about the output of the upstream configure script,
> which indicates to the user which C++ compiler will be used.

should be fixed in [1].

> The patch attached to this bug report fixes the problem for me.
> Hopefully, it will not introduce false negatives.

Thanks for the patch. I've fixed it slightly differently to
reduce the chance of false negatives.

Best,
Simon

[1] 
https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=5d2c33804eade9a6b1463d4cb46d7cac0018274c
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#1037521: (no subject)

[Simon Ruderich]

Hi,

On Fri, Apr 05, 2024 at 12:48:19AM -0400, Yogeswaran Umasankar wrote:
> eribe...@debian.org, Matthias Geiger 
> Bcc: Subject: Re: false positive NONVERBOSE BUILD for rust code in Python
> modules
> Reply-To: Hi,
>
> I am having similar issue in another package 'python-cotengrust' [0].
> The link for buildlog [1].
>
> [0] https://salsa.debian.org/python-team/packages/python-cotengrust/
> [1] 
> https://salsa.debian.org/python-team/packages/python-cotengrust/-/jobs/5519541

as discussed in IRC the problem is that blhc cannot detect that
this is a rust package. In regular buildd logs the "Filtered
Build-Depends:" lines contain the build dependencies. This gives
blhc a way to enable special handling for certain situations (in
this case if a rust compiler is used).

I couldn't find a way to get this information from the salsa
build logs. If they could be modified to show the build
dependencies then I'll adapt blhc to detect this case.

Best,
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#1068773: Subject: blhc: Stack clash and branch protection flag issues in Debian Bookworm and older releases

[Simon Ruderich]

Hi,

On Wed, Apr 10, 2024 at 09:09:13PM +, aquilamac...@riseup.net wrote:
> The ${RELEASE} variable in the context of this issue refers to the
> specific Debian release being used during the Salsa CI process. One
> potential solution that has been considered is to ensure that
> blhc:${RELEASE} correctly handles the flags for each release. This
> approach could alleviate the compilation errors and ensure consistency
> across different Debian releases.
>
> For more details, you can check the issue in the Salsa CI repository at
> https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/340
>
> Before proceeding with any changes, I would appreciate your input on
> this matter. Specifically, do you think it would be sensible to use blhc
> from each release? Your insights would be greatly appreciated.

I think the best solution is to use the blhc version from the
corresponding release (i.e. blhc:${RELEASE}). Otherwise each
change to flags in blhc will require manual work for earlier
releases as carnil mentioned.

The blhc version in each release should be able to handle the
flags for that release (otherwise it's a bug which should be
fixed). So the suggested first approach should work fine and
cause the less additional maintenance overhead.

Best,
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#1067084: ruby-sigar: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

[Praveen Arimbrathodiyil]

On Mon, 18 Mar 2024 09:13:47 +0100 Sebastian Ramacher 
 wrote:

Justification: fails to build from source (but built successfully in the past)
This packaged can be removed once ruby-eye is removed. RM request filed 
for its only reverse dependency ruby-eye.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069616: rc-buggy, not needed anymore

[Pirate Praveen]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: ruby-...@packages.debian.org
Control: affects -1 + src:ruby-eye
User: ftp.debian@packages.debian.org
Control: block -1 by 1069615

rc buggy #1031479 and originally packaged as dependency of diaspora 
which is now requested to be removed.

Bug#1069613: systemd: Startup fails after apt full-upgrade

[Bud Heal]

Package: systemd
Version: 252.22-1~deb12u1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: budheal...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?
A couple of non-Debian packages needed libc > 2.31, so I upgraded this
laptop.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I changed sources.list to point to bullseye, apt-get update, apt-get
upgrade --without-new-pkgs, apt-get full-update. Reboot at each upgrade.
I changed sources.list to point to bookworm, including non-free and
non-free-firmware, apt-get update, apt-get upgrade --without-new-pkgs,
reboot, noted that GLIB (libc) had budged to 2.36 and debian_version was
12.5, so time for apt-get full-upgrade. Things were still working fine, 
but not after another reboot.
   * What was the outcome of this action?
Now startup does not complete to login. After I enter the disk password,
a long list of messages come up as usual and the first error was that
apache could not be started. Later boots add a line, Error ucsi_acpi
USBC000:00 PPM init failed (-110)
I used a Bookworm RC3 disk (DLBD) for triage, and tail var/log/syslog
informs that gnome crashed.
I then did apt-get update, upgrade --without-new-pkgs, full-upgrade on a
laptop (installed from Bookworm RC3 and set aside because I had work to
do) and those steps worked fine.
Now, this HP Omen 6-core has been problematic, or at least difficult, in
the past, but I was able to find its firmware and I think Debian now
includes them.
When time allows, I can compare the config and binary files to see what
is different but that startup goes into an endless loop is peculiar.
   * What outcome did you expect instead?
Obviously, init should proceed to login.


-- Package-specific info:

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages systemd depends on:
ii  libacl12.3.1-3
ii  libaudit1  1:3.0.9-1
ii  libblkid1  2.38.1-5+deb12u1
ii  libc6  2.36-9+deb12u4
ii  libcap21:2.66-4
ii  libcryptsetup122:2.6.1-4~deb12u2
ii  libfdisk1  2.38.1-5+deb12u1
ii  libgcrypt201.10.1-3
ii  libkmod2   30+20221128-1
ii  liblz4-1   1.9.4-1
ii  liblzma5   5.4.1-0.2
ii  libmount1  2.38.1-5+deb12u1
ii  libp11-kit00.24.1-2
ii  libseccomp22.5.4-1+b3
ii  libselinux13.4-1+b6
ii  libssl33.0.11-1~deb12u2
ii  libsystemd-shared  252.22-1~deb12u1
ii  libsystemd0252.22-1~deb12u1
ii  libzstd1   1.5.4+dfsg2-5
ii  mount  2.38.1-5+deb12u1

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]  1.14.10-1~deb12u1
ii  ntpsec [time-daemon]1.2.2+dfsg1-1+deb12u1

Versions of packages systemd suggests:
ii  libfido2-11.12.0-2+b1
ii  libqrencode4  4.1.1-1
ii  libtss2-esys-3.0.2-0  3.2.1-3
ii  libtss2-mu0   3.2.1-3
ii  libtss2-rc0   3.2.1-3
ii  policykit-1   122-3
ii  polkitd   122-3
pn  systemd-boot  
pn  systemd-container 
pn  systemd-homed 
pn  systemd-resolved  
pn  systemd-userdbd   

Versions of packages systemd is related to:
ii  dbus-user-session  1.14.10-1~deb12u1
pn  dracut 
ii  initramfs-tools0.142
ii  libnss-systemd 252.22-1~deb12u1
ii  libpam-systemd 252.22-1~deb12u1
ii  udev   252.22-1~deb12u1

-- no debconf information
[EQUIVALENT] /etc/systemd/system/mysql.service -> 
/usr/lib/systemd/system/mysql.service
[EQUIVALENT] /etc/systemd/system/mysqld.service -> 
/usr/lib/systemd/system/mysqld.service
[EXTENDED]   /usr/lib/systemd/system/rc-local.service -> 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED]   /usr/lib/systemd/system/systemd-localed.service -> 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
[EXTENDED]   /usr/lib/systemd/system/user@.service -> 
/usr/lib/systemd/system/user@.service.d/10-login-barrier.conf

5 overridden configuration files found.
==> /var/lib/systemd/deb-systemd-helper-enabled/fstrim.timer.dsh-also <==
/etc/systemd/system/timers.target.wants/fstrim.timer

==> /var/lib/systemd/deb-systemd-helper-enabled/sysstat-collect.timer.dsh-also 
<==
/etc/systemd/system/sysstat.service.wants/sysstat-collect.timer

==> /var/lib/systemd/deb-systemd-helper-enabled/e2scrub_all.timer.dsh-also <==
/etc/systemd/system/timers.target.wants/e2scrub_all.timer

==> /var/lib/systemd/deb-systemd-helper-enabled/mysql.service <==

==> 

Bug#1069614: erfs: isolation-machine autopkgtest fails: sshfs failed

[Paul Gevers]

Source: erfs
Version: 1.4-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine

Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for 
isolation-machine tests on ci.debian.net for amd64 and added your 
package to the list to use that. 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, but because machine-isolation 
support by ci.debian.net is new I have not marked this bug as serious (yet).


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/packages/e/erfs/testing/amd64/45706002/

 49s autopkgtest [13:48:31]: test upstream-tests: [---
 50s read: Connection reset by peer
 50s ERROR: sshfs failed.
 50s 1. The volume is already mounted.
 50s 2. Wrong SHARE-SECRET.
 50s 3. The server can not be reached.
 50s autopkgtest [13:48:32]: test upstream-tests: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069615: RM: diaspora -- ROM; unmaintained, rc-buggy

[Pirate Praveen]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: diasp...@packages.debian.org
Control: affects -1 + src:diaspora
User: ftp.debian@packages.debian.org
Usertags: remove

I was hoping to come back to updating diaspora, but I don't think I will 
be able to find time. It is affected by rc bugs #924109, #974014 and 
also blocking removal of its unmaintained dependencies.

Bug#1069612: drm-info: isolation-machine autopkgtest fails: /dev/dri/card0: Permission denied

[Paul Gevers]

Source: drm-info
Version: 2.6.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine

Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for 
isolation-machine tests on ci.debian.net for amd64 and added your 
package to the list to use that. 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, but because machine-isolation 
support by ci.debian.net is new I have not marked this bug as serious (yet).


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/packages/d/drm-info/testing/amd64/45706001/

 33s autopkgtest [13:47:33]: test command1: [---
 33s /dev/dri/card0: Permission denied
 33s Failed to retrieve information from /dev/dri/card0
 34s autopkgtest [13:47:34]: test command1: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069611: dpdk-kmods: isolation-machine autopkgtest fails: tar: Cowardly refusing to create an empty archive

[Paul Gevers]

Source: dpdk-kmods
Version: 0~20230205+git-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine

Dear maintainer(s),

Your package has an autopkgtest, great. I recently added support for 
isolation-machine tests on ci.debian.net for amd64 and added your 
package to the list to use that. 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, but because machine-isolation 
support by ci.debian.net is new I have not marked this bug as serious (yet).


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/packages/d/dpdk-kmods/testing/amd64/45706000/

 28s autopkgtest [13:45:23]: test test-dkms: [---
 28s tar: Cowardly refusing to create an empty archive
 28s Try 'tar --help' or 'tar --usage' for more information.
 29s autopkgtest [13:45:24]: test test-dkms: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069610: RFS: modernizr/3.13.0-0.1 [NMU] -- JavaScript library to detect HTML5 and CSS3 features in the user's browser

[Fab Stz]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

It's an NMU and the changes of this NMU have already been approved and merged 
in salsa at https://salsa.debian.org/js-team/modernizr

 * Package name : modernizr
   Version  : 3.13.0-0.1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://modernizr.com/
 * License  : MIT
 * Vcs  : https://salsa.debian.org/js-team/modernizr
   Section  : javascript

The source builds the following binary packages:

  libjs-modernizr - JavaScript library to detect HTML5 and CSS3 features in 
the user's browser

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/m/modernizr/
modernizr_3.13.0-0.1.dsc

Changes since the last upload:

 modernizr (3.13.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release Closes: #1001203, #1067130
   * d/control:
  - update Build-Depends
  - update standards version to 4.6.2, no changes needed.
   * d/copyright:
  - add/update entries for the new version
  - remove now useless Files-Excluded (file is not shipped anymore)
   * d/install: don't install feature-detects/* anymore
   * d/rules:
  - build modernizr.js with upstream's new build script
  - remove repack suffix (not needed anymore) and add it to d/watch
   * d/s/lintian-overrides: add lintian-overrides for 'source-is-missing'
 errors (files contain test data)
   * d/watch: update URL & methodology, add repacksuffix here instead of
 d/rules (but not used because there is no Files-Excluded in d/copyright)
   * add missing source file 'file.js' and add patch to use it.

Regards,

Bug#979617: tcplay: VeraCrypt support

[GCS]

Hi,

On Sun, Apr 21, 2024 at 9:06 AM Daniel Kahn Gillmor  wrote:
> I've just confirmed what Johannes said about tcplay 3.3 building easily
> on debian.  I uploaded 3.3-0.1 to unstable as an NMU to DELAYED/15,
> after cleaning up the packaging a little bit.
[...]
> Hopefully this NMU is welcomed in the helpful spirit i intended with it!
> But if you think it's a bad idea, I don't mind it being NACK'ed.  In the
> course of doing the cleanup i noticed a few weird things about the
> packaging for libtcplay, that i wasn't sure how to best fix, so i just
> recorded them in the BTS.
 I prefer communication first. :) Currently I'm travelling so I can
only check it on Tuesday.

> I've also tested a backported version of 3.3-0.1 to debian stable, and
> it seems to work fine to create an interoperable VeraCrypt volume
> (methodology described below).
 There were some license problems in the past at least, which
prevented packaging. I will check the current situation.

Regards,
Laszlo/GCS

Bug#1069247: libconfig-model-dpkg-perl: test failures

[Niko Tyni]

[Copying Julian as the apt maintainer.]

On Sat, Apr 20, 2024 at 09:02:35PM +0300, Niko Tyni wrote:
> On Sat, Apr 20, 2024 at 11:09:17AM +0200, Dominique Dumont wrote:
> > On Thursday, 18 April 2024 19:21:55 CEST you wrote:
> > > Source: libconfig-model-dpkg-perl
> > > Version: 3.004
> > > Severity: serious
> > > Tags: ftbfs
> > > Justification: fails to build from source
> > 
> > This really looks like a bug with prove:
> > 
> > $ perl t/reorder.t 
> > ok 1 -  test re-ordered list
> > 1..1
> 
> > I can't see what's wrong with the output of reorder test...
> 
> Looks like something is injecting apt progress messages to stdout with
> CR characters hiding it on the terminal but obviously not from `prove`.
> 
> $ perl t/reorder.t |od -c

> 460   f   o   r   m   a   t   i   o   n   .   .   .   0   %  \r
> 500
> *
> 540  \r   o   k   1   -   t   e   s   t   r   e
> 560   -   o   r   d   e   r   e   d   l   i   s   t  \n   1   .
> 600   .   1  \n

These come from apt, via libapt-pkg-perl which I don't think has ever
filtered them away. The thing that broke this is surely output changes
in apt 2.9.

The crucial difference wrt. at least bookworm seems to be that the
apt messages used to end with a line feed "\n" before the actual TAP
format started.  Now it only has a carriage return "\r" there. Apparently
`prove` ignores unknown lines, but now interprets all the apt output to
be part of the first line that ends with the 'ok 1' part. So that gets
ignored as well.

I see the TAP format spec says at

  https://testanything.org/tap-version-14-specification.html

  A Harness should normalize line endings by replacing any instances of
  \r\n or \r in the TAP document with \n.

so I suppose this might be a normal/wishlist bug in `prove`. In that case,
please note that it needs to be fixed in libtest-harness-perl first as
src:perl just bundles an older version of it.

Not sure if apt should go back to ending its output with a line
feed. Julian, what do you think?
-- 
Niko

Bug#1041027: rapidjson: diff for NMU version 1.1.0+dfsg2-7.2

[Micha Lenk]

Dear maintainer,

On Sun, 21 Apr 2024 15:23:27 +0200 Micha Lenk  wrote:

I've prepared an NMU for rapidjson (versioned as 1.1.0+dfsg2-7.2). The diff
is attached to this message.


I forgot to mention, I've pushed my changes to salsa on branch 
'NMU_fix_for_debbug_1041027':

https://salsa.debian.org/debian/rapidjson/-/commits/NMU_fix_for_debbug_1041027?ref_type=heads

Regards,
Micha

Bug#1041027: rapidjson: diff for NMU version 1.1.0+dfsg2-7.2

[Micha Lenk]

Dear maintainer,

I've prepared an NMU for rapidjson (versioned as 1.1.0+dfsg2-7.2). The diff
is attached to this message.

Regards,
Micha
diff -Nru rapidjson-1.1.0+dfsg2/debian/changelog rapidjson-1.1.0+dfsg2/debian/changelog
--- rapidjson-1.1.0+dfsg2/debian/changelog	2022-10-15 18:10:14.0 +0200
+++ rapidjson-1.1.0+dfsg2/debian/changelog	2024-04-21 15:12:21.0 +0200
@@ -1,3 +1,11 @@
+rapidjson (1.1.0+dfsg2-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/rules: Switch to C++ 14 to fix FTBFS with googletest >= 1.13.0
+(Closes: #1041027)
+
+ -- Micha Lenk   Sun, 21 Apr 2024 15:12:21 +0200
+
 rapidjson (1.1.0+dfsg2-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rapidjson-1.1.0+dfsg2/debian/rules rapidjson-1.1.0+dfsg2/debian/rules
--- rapidjson-1.1.0+dfsg2/debian/rules	2019-01-31 21:17:42.0 +0100
+++ rapidjson-1.1.0+dfsg2/debian/rules	2024-04-21 15:10:49.0 +0200
@@ -3,6 +3,12 @@
 # output every command that modifies files on the build system.
 #DH_VERBOSE = 1
 
+# Needed since googletest 1.13.0 (see #1041027)
+export DEB_CXXFLAGS_MAINT_APPEND = -std=c++14
+
 %:
 	dh $@
 
+override_dh_auto_configure:
+	# Needed since googletest 1.13.0 (see #1041027)
+	dh_auto_configure -- -DRAPIDJSON_BUILD_CXX11=OFF

Bug#1068174: Debian FPGA toolchain update and testing (Was: Bug#1068174: yosys: Please package the latest upstream release)

[Philipp Klaus Krause]

Am 20.04.24 um 16:15 schrieb Daniel Gröber:

On Mon, Apr 01, 2024 at 11:48:16AM +0200, Philipp Klaus Krause wrote:

I use yosys to synthesize for the iCE40UP and GateMate FPGAs. IMO, the
current upstream release 0.38 has substantial improvements over the 0.33
release currently in Debian.


Neat, are the GateMates finally available on the open market then? I'd love
to get my hands on some dev hardware.


Yes, I got the GateMateA1-EVB board from Olimex, since it is
substantially cheaper than the official CologneChips one, and I have no
use for most of the extra features of the CologneChips board:
https://www.olimex.com/Products/FPGA/GateMate/GateMateA1-EVB/open-source-hardware


Are you open to doing some testing for the new package version once I get
around to putting it together? I can do end-to-end testing on ICE40(HX) and
(probably) GW1N (if I can figure out how to flash this thing) maybe
@Jonathan (in CC) can cover ECP5 and you could do ICE40UP and GateMate?


I can do some testing on iCE40UP5 (iCEBreaker board) and GateMateA1
(GateMateA1-EVB board). I run Debian on amd64, arm64, and ppc64 (but so
far used yosys on amd64 only).


I've been meaning to look into what we could use for testing beyond simple
blinkies. Perhaps some CPU? I'd like to have something that can run
internal consistency checks. If anyone has any ideas let me know.


My use-case is basically that: the experimental f8 CPU
(https://sourceforge.net/p/sdcc/code/HEAD/tree/branches/f8/f8/). I
actually use "simple blinkies" for testing": a basic f8-based SoC, that
runs a program on the CPU that does the blinking. However, I write
System Verilog, so I use sv2v (not yet in Debian) as a preprocessor
before feeding my code into yosys.

Philipp

P.S.: I saw that yosys 0.40 was just released. I'll do a quick test of
the upstream release in the next few days.

Bug#1069609: RFS: mount-zip/1.0.14-1 [RFP] -- Read-only FUSE file system for ZIP archives

[Fab Stz]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "mount-zip":

 * Package name : mount-zip
   Version  : 1.0.14-1
   Upstream contact : François Degros 
 * URL  : https://github.com/google/mount-zip
 * License  : GPL-3.0-or-later
 * Vcs  : https://salsa.debian.org/bastif/mount-zip
   Section  : utils

The source builds the following binary packages:

  mount-zip - Read-only FUSE file system for ZIP archives

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

  https://mentors.debian.net/package/mount-zip/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/m/mount-zip/mount-zip_1.0.14-1.dsc

Changes for the initial release:

 mount-zip (1.0.14-1) unstable; urgency=medium
 .
   * Initial release. Closes: #1068638

Regards,

Bug#1069608: topplot: missing test-depends on python3-all

[Rebecca N. Palmer]

Source: topplot
Version: 0.2.2+repack-1
Tags: patch
Severity: serious
Justification: blocks testing migration of other packages

topplot tries to run its autopkgtest in all versions of Python (which is 
good), but does not test-depend on all those versions of Python.


This previously worked because numpy depended on them.  However, this 
has now been removed (see #945824), causing topplot's autopkgtests to fail.


Adding python3-all to the Depends in debian/*tests*/control should fix 
this bug, but I have not actually tested this.

Bug#1069558: lomiri-ui-toolkit: FTBFS on armel: QWARN : components::UnknownTestFunc() file:///usr/lib/arm-linux-gnueabi/qt5/qml/QtTest/SignalSpy.qml:258: Error: Invalid write to global property "qtest

[Mike Gabriel]

Control: severity -1 important
Control: tags -1 moreinfo

Hi Lucas,

On  Sa 20 Apr 2024 15:21:10 CEST, Lucas Nussbaum wrote:


Source: lomiri-ui-toolkit
Version: 1.3.5100+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

During a rebuild of all packages in sid, your package failed to build
on armel.


Relevant part (hopefully):



[...]


The bug title seems misleading. Causes of the FTBFS are these test  
failures of the following kind:


QWARN  : components::AbstractButtonAPI::test_sensing_area(zero size,  
no margins, tap in visual) "No touch device registered. Register one  
using registerTouchDevice() before using touchClick"
FAIL!  : components::AbstractButtonAPI::test_sensing_area(zero size,  
no margins, tap in visual) 'wait for signal clicked' returned FALSE.  
()


Can this be related to a slightly different test bed? A VM without  
evdev device? (Not sure if a PC-like hardware is required for  
successfully running those tests).


Mike


--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgprC6PQ3W8Yx.pgp
Description: Digitale PGP-Signatur

Bug#1067915: veusz: diff for NMU version 3.6.2-1.1

[Andreas Metzler]

Control: tags 1067915 + patch
Control: tags 1067915 + pending

Dear maintainer,

I've prepared an NMU for veusz (versioned as 3.6.2-1.1) and
uploaded it to DELAYED/00.

kind regards Andreas
diff -Nru veusz-3.6.2/debian/changelog veusz-3.6.2/debian/changelog
--- veusz-3.6.2/debian/changelog	2023-03-20 07:10:18.0 +0100
+++ veusz-3.6.2/debian/changelog	2024-04-21 14:19:21.0 +0200
@@ -1,3 +1,10 @@
+veusz (3.6.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop runtime library packages (not -dev) from b-d. Closes: #1067915
+
+ -- Andreas Metzler   Sun, 21 Apr 2024 14:19:21 +0200
+
 veusz (3.6.2-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru veusz-3.6.2/debian/control veusz-3.6.2/debian/control
--- veusz-3.6.2/debian/control	2023-03-20 07:10:18.0 +0100
+++ veusz-3.6.2/debian/control	2024-04-21 14:18:16.0 +0200
@@ -6,12 +6,6 @@
 Build-Depends: debhelper-compat (= 13),
dh-exec,
dh-python,
-   libqt5core5a,
-   libqt5dbus5,
-   libqt5gui5,
-   libqt5svg5,
-   libqt5widgets5,
-   libqt5xml5,
python3-all,
python3-all-dev,
python3-astropy,


signature.asc
Description: PGP signature

Bug#1069599: dhcpcd: isolation-machine autopkgtest fails: Unit systemd-timesyncd.service not found.

[Paul Gevers]

Hi,

On 21-04-2024 1:59 p.m., Martin-Éric Racine wrote:

That service unit is provided by systemd-timesyncd, which systemd
recommends. Basically, unless your testing environment explicitly
installs another package providing time-daemon, this shouldn't happen,
since systemd would have pulled systemd-timesyncd by default.


In autopkgtest context, recommends are not installed (to avoid issues 
where recommends are (sometimes) not installable). If your test needs 
it, you'll need to Depends on it explicitly in your test stanza.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069599: dhcpcd: isolation-machine autopkgtest fails: Unit systemd-timesyncd.service not found.

[Martin-Éric Racine]

su 21. huhtik. 2024 klo 14.59 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> su 21. huhtik. 2024 klo 14.12 Paul Gevers (elb...@debian.org) kirjoitti:
> >
> > Source: dhcpcd
> > Version: 1:10.0.6-1
> > Severity: important
> > User: debian...@lists.debian.org
> > Usertags: isolation-machine
> >
> > Dear maintainer(s),
> >
> > Your package has an autopkgtest, great. I recently added support for
> > isolation-machine tests on ci.debian.net for amd64 and added your
> > package to the list to use that. However, it fails. Can you please
> > investigate the situation and fix it? I copied some of the output at the
> > bottom of this report.
>
> [...]
>
> >   29s autopkgtest [11:03:42]: test timesyncd-ntp-servers-from-dhcp:
> > [---
> >   30s Preparing virtual interfaces...
> >   30s Actual changes:
> >   30s tx-checksum-ip-generic: off
> >   30s tx-tcp-segmentation: off [not requested]
> >   30s tx-tcp-ecn-segmentation: off [not requested]
> >   30s tx-tcp-mangleid-segmentation: off [not requested]
> >   30s tx-tcp6-segmentation: off [not requested]
> >   30s tx-checksum-sctp: off
> >   30s Preparing dnsmasq configuration...
> >   35s Obtaining network configuration for veth1 via dhcp...
> >   37s RA from non local address fdae:9322:f1cc::1
> >   43s Failed to reload-or-try-restart systemd-timesyncd.service: Unit
> > systemd-timesyncd.service not found.
> >   43s Failed to reload-or-try-restart systemd-timesyncd.service: Unit
> > systemd-timesyncd.service not found.
> >   48s Check if the NTP server is made available to daemon...Failed to
> > parse bus message: No route to host
> >   49s autopkgtest [11:04:02]: test timesyncd-ntp-servers-from-dhcp:
> > ---]
>
> That service unit is provided by systemd-timesyncd, which systemd
> recommends. Basically, unless your testing environment explicitly
> installs another package providing time-daemon, this shouldn't happen,
> since systemd would have pulled systemd-timesyncd by default.

Anyhow, no harm done. The following commit should fix it:

https://salsa.debian.org/debian/dhcpcd/-/commit/55e588b0d7561c697f3fedfddef3feeb6c8b34b9

Martin-Éric

Bug#1069106: openmpi: 32 bit pmix_init:startup:internal-failure: help-pmix-runtime.txt: No such file

[Drew Parsons]

Source: openmpi
Version: 4.1.6-12
Followup-For: Bug #1069106
Control: reopen 1069106

4.1.6-12 was intended to fix this bug, but it's still occuring

e.g.
https://ci.debian.net/packages/o/openmpi/unstable/i386/45630865/
https://ci.debian.net/packages/o/openmpi/unstable/armhf/45630866/

Bug#1068422: possibly caused by python 3.12.3 Re: Bug#1068422: can't import dask.dataframe - TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object

[Rebecca N. Palmer]

This bug is not *obviously* known to dask upstream, but their CI is 
failing and I haven't checked why.


It happens only in Python 3.12, not 3.11:
https://ci.debian.net/packages/d/dask/unstable/amd64/45013666/
and still doesn't happen in testing, but does happen in mostly-testing 
with 
src:python3-defaults,src:db5.3,src:keras,src:nodejs,src:openssl,src:python3-stdlib-extensions,src:python3.11,src:python3.12,src:readline,src:udisks2,src:viagee 
from unstable:

https://ci.debian.net/packages/d/dask/testing/amd64/45564690/

This suggests that the trigger may be the upgrade of Python itself 
(3.12.2-1 in testing -> 3.12.3-1 in unstable).


*Possibly* related items from the upstream Python changelog:
https://github.com/python/cpython/issues/101293
https://github.com/python/cpython/issues/117110

Bug#1069607: retroarch is built without optimization

[Adrian Bunk]

Package: retroarch
Version: 1.18.0+dfsg-1
Severity: important
Tags: ftbfs
X-Debbugs-Cc: Jonathan McDowell 

debian/rules:export DEB_CXXFLAGS_MAINT_STRIP=-O2
debian/rules:export DEB_CFLAGS_MAINT_STRIP=-O2

Building without optimization makes binaries
both slower and bigger.

The latter is likely also the root cause of the FTBFS
on m68k and powerpc.

Bug#1069599: dhcpcd: isolation-machine autopkgtest fails: Unit systemd-timesyncd.service not found.

[Martin-Éric Racine]

su 21. huhtik. 2024 klo 14.12 Paul Gevers (elb...@debian.org) kirjoitti:
>
> Source: dhcpcd
> Version: 1:10.0.6-1
> Severity: important
> User: debian...@lists.debian.org
> Usertags: isolation-machine
>
> Dear maintainer(s),
>
> Your package has an autopkgtest, great. I recently added support for
> isolation-machine tests on ci.debian.net for amd64 and added your
> package to the list to use that. However, it fails. Can you please
> investigate the situation and fix it? I copied some of the output at the
> bottom of this report.

[...]

>   29s autopkgtest [11:03:42]: test timesyncd-ntp-servers-from-dhcp:
> [---
>   30s Preparing virtual interfaces...
>   30s Actual changes:
>   30s tx-checksum-ip-generic: off
>   30s tx-tcp-segmentation: off [not requested]
>   30s tx-tcp-ecn-segmentation: off [not requested]
>   30s tx-tcp-mangleid-segmentation: off [not requested]
>   30s tx-tcp6-segmentation: off [not requested]
>   30s tx-checksum-sctp: off
>   30s Preparing dnsmasq configuration...
>   35s Obtaining network configuration for veth1 via dhcp...
>   37s RA from non local address fdae:9322:f1cc::1
>   43s Failed to reload-or-try-restart systemd-timesyncd.service: Unit
> systemd-timesyncd.service not found.
>   43s Failed to reload-or-try-restart systemd-timesyncd.service: Unit
> systemd-timesyncd.service not found.
>   48s Check if the NTP server is made available to daemon...Failed to
> parse bus message: No route to host
>   49s autopkgtest [11:04:02]: test timesyncd-ntp-servers-from-dhcp:
> ---]

That service unit is provided by systemd-timesyncd, which systemd
recommends. Basically, unless your testing environment explicitly
installs another package providing time-daemon, this shouldn't happen,
since systemd would have pulled systemd-timesyncd by default.

Martin-Éric