Bug#1064265: openzwave: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: openzwave
Version: 1.6.1914+ds-1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
openzwave as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for openzwave
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru openzwave-1.6.1914+ds/debian/changelog 
openzwave-1.6.1914+ds/debian/changelog
--- openzwave-1.6.1914+ds/debian/changelog  2021-10-21 19:17:21.0 
+
+++ openzwave-1.6.1914+ds/debian/changelog  2024-02-19 07:30:55.0 
+
@@ -1,3 +1,12 @@
+openzwave (1.6.1914+ds-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+  * debian/libopenzwave1.6-dev.install: pkgconfig files now being installed
+in the multiarch path upstream, so fix the path lookup.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 07:30:55 +
+
 openzwave (1.6.1914+ds-1) unstable; urgency=medium
 
   * Team upload
diff -Nru openzwave-1.6.1914+ds/debian/control 
openzwave-1.6.1914+ds/debian/control
--- openzwave-1.6.1914+ds/debian/control2021-10-21 19:17:21.0 
+
+++ openzwave-1.6.1914+ds/debian/control2024-02-19 07:30:55.0 
+
@@ -14,9 +14,10 @@
 Vcs-Git: https://salsa.debian.org/debian-iot-team/openzwave.git
 Rules-Requires-Root: no
 
-Package: libopenzwave1.6
-Replaces: libopenzwave1.5
-Breaks: libopenzwave1.5
+Package: libopenzwave1.6t64
+Provides: ${t64:Provides}
+Replaces: libopenzwave1.6, libopenzwave1.5
+Breaks: libopenzwave1.6 (<< ${source:Version}), libopenzwave1.5
 Section: libs
 Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
@@ -31,7 +32,7 @@
 
 Package: libopenzwave1.6-dev
 Section: libdevel
-Depends: ${misc:Depends}, libopenzwave1.6 (= ${binary:Version})
+Depends: ${misc:Depends}, libopenzwave1.6t64 (= ${binary:Version})
 Suggests: libopenzwave-doc
 Architecture: any
 Description: header files for the openzwave library
@@ -57,7 +58,7 @@
 Package: openzwave
 Section: misc
 Architecture: any
-Depends: libopenzwave1.6 (>= ${binary:Version}), ${misc:Depends}, 
${shlibs:Depends}
+Depends: libopenzwave1.6t64 (>= ${binary:Version}), ${misc:Depends}, 
${shlibs:Depends}
 Description: Sample Program for libopenzwave
  OpenZWave is an open-source, cross-platform library designed to enable
  anyone to add support for Z-Wave home-automation devices to their
diff -Nru openzwave-1.6.1914+ds/debian/libopenzwave1.6-dev.install 
openzwave-1.6.1914+ds/debian/libopenzwave1.6-dev.install
--- openzwave-1.6.1914+ds/debian/libopenzwave1.6-dev.install2021-10-21 
19:17:21.0 +
+++ openzwave-1.6.1914+ds/debian/libopenzwave1.6-dev.install2024-02-19 
07:30:55.0 +
@@ -3,4 +3,4 @@
 usr/lib/*/libopenzwave.so
 usr/include/openzwave/*
 cpp/tinyxml/*.h usr/include/openzwave/tinyxml
-usr/lib/pkgconfig/* usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig/
+usr/lib/*/pkgconfig/*
diff -Nru openzwave-1.6.1914+ds/debian/libopenzwave1.6.install 
openzwave-1.6.1914+ds/debian/libopenzwave1.6.install
--- openzwave-1.6.1914+ds/debian/libopenzwave1.6.install2021-10-21 
19:17:21.0 +
+++ openzwave-1.6.1914+ds/debian/libopenzwave1.6.install1970-01-01

Bug#1051681: Hangs trying to boot from /boot on LVM+LUKS

[Mate Kukri]

Hi Michel,

There are a rather high number of variables to isolate here. If you
could provide the following information, it might help provide a
better guess at what's going on:
- Computer (or mainboard if white box desktop) model
- Firmware revision
- Is Secure Boot enabled?
- Description of your disk layout

Also if you could just try using the grub 2.12-1 binary to boot a
kernel+initrd from an ext4 volume directly (e.g. using a usb drive or
spare disk), that would also be very helpful, I wonder if this
regression has something to do with LVM.

Mate

On Sun, Feb 18, 2024 at 3:16 PM Michel Dänzer  wrote:
>
> On 2023-09-11 11:28, Michel Dänzer wrote:
> > Package: grub-efi
> > Version: 2.12~rc1-9
> > Severity: important
> >
> >
> > After upgrading to 2.12~rc1, any boot entry hangs after 'Loading initial 
> > ramdisk ...'. I'll attach a photo showing the debug=all output when it 
> > hangs.
> >
> > Downgrading to 2.06-13 avoids the issue.
>
> Still the same issue with 2.12-1.
>
> Is there any more information I can provide to help solve this? For the time 
> being I can keep the system booting with 2.06-14, I suspect that won't be a 
> reasonable option forever though.
>
>
> --
> Earthling Michel Dänzer|  https://redhat.com
> Libre software enthusiast  | Mesa and Xwayland developer
>
> ___
> Pkg-grub-devel mailing list
> pkg-grub-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grub-devel

Bug#1064264: openssl: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: openssl
Version: 3.1.5-1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
openssl as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for openssl
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru openssl-3.1.5/debian/changelog openssl-3.1.5/debian/changelog
--- openssl-3.1.5/debian/changelog  2024-02-03 16:11:24.0 +
+++ openssl-3.1.5/debian/changelog  2024-02-19 07:06:24.0 +
@@ -1,3 +1,10 @@
+openssl (3.1.5-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 07:06:24 +
+
 openssl (3.1.5-1) unstable; urgency=medium
 
   * Import 3.1.5
diff -Nru openssl-3.1.5/debian/control openssl-3.1.5/debian/control
--- openssl-3.1.5/debian/control2024-02-03 16:00:20.0 +
+++ openssl-3.1.5/debian/control2024-02-19 07:06:24.0 +
@@ -29,11 +29,13 @@
   * testing SSL/TLS clients and servers;
   * handling S/MIME signed or encrypted mail.
 
-Package: libssl3
+Package: libssl3t64
+Provides: ${t64:Provides}
+Replaces: libssl3
 Section: libs
 Architecture: any
 Multi-Arch: same
-Breaks: openssh-client (<< 1:9.4p1), openssh-server (<< 1:9.4p1), 
python3-m2crypto (<< 0.38.0-4)
+Breaks: libssl3 (<< ${source:Version}), openssh-client (<< 1:9.4p1), 
openssh-server (<< 1:9.4p1), python3-m2crypto (<< 0.38.0-4)
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Secure Sockets Layer toolkit - shared libraries
@@ -73,7 +75,7 @@
 Architecture: any
 Multi-Arch: same
 Suggests: libssl-doc
-Depends: libssl3 (= ${binary:Version}), ${misc:Depends}
+Depends: libssl3t64 (= ${binary:Version}), ${misc:Depends}
 Description: Secure Sockets Layer toolkit - development files
  This package is part of the OpenSSL project's implementation of the SSL
  and TLS cryptographic protocols for secure communication over the
diff -Nru openssl-3.1.5/debian/libssl3.NEWS openssl-3.1.5/debian/libssl3.NEWS
--- openssl-3.1.5/debian/libssl3.NEWS   2024-02-03 16:00:20.0 +
+++ openssl-3.1.5/debian/libssl3.NEWS   1970-01-01 00:00:00.0 +
@@ -1,8 +0,0 @@
-libssl3 (3.1.4-2) unstable; urgency=medium
-
-  TLSv1.0, TLSv1.1 and DTLS 1.0 work only at security level 0 (it was
-  previously allowed at security level 0). If you are still using them, you
-  need lower security level (via CipherString = DEFAULT:@SECLEVEL=0)
-  additionally to the MinProtocol setting.
-
- -- Sebastian Andrzej Siewior   Sat, 25 Nov 2023 
21:29:39 +0100
diff -Nru openssl-3.1.5/debian/libssl3.dirs openssl-3.1.5/debian/libssl3.dirs
--- openssl-3.1.5/debian/libssl3.dirs   2024-02-03 16:00:20.0 +
+++ openssl-3.1.5/debian/libssl3.dirs   1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/share/doc/libssl3
diff -Nru openssl-3.1.5/debian/libssl3.install 
openssl-3.1.5/debian/libssl3.install
--- openssl-3.1.5/debian/libssl3.install2024-02-03 16:00:20.0 
+
+++ openssl-3.1.5/debian/libssl3.install1970-01-01 00:00:00.0 
+
@@ -1,3 +0,0 @@
-usr/lib/*/*.so.*
-usr/lib/*/engin

Bug#1064263: openmpi: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: openmpi
Version: 4.1.6-5
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
openmpi as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for openmpi
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru openmpi-4.1.6/debian/changelog openmpi-4.1.6/debian/changelog
--- openmpi-4.1.6/debian/changelog  2024-01-01 17:14:56.0 +
+++ openmpi-4.1.6/debian/changelog  2024-02-19 06:50:54.0 +
@@ -1,3 +1,10 @@
+openmpi (4.1.6-5.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 06:50:54 +
+
 openmpi (4.1.6-5) unstable; urgency=medium
 
   * Ensure pkg-config is present for autopkgtests
diff -Nru openmpi-4.1.6/debian/control openmpi-4.1.6/debian/control
--- openmpi-4.1.6/debian/control2024-01-01 17:14:56.0 +
+++ openmpi-4.1.6/debian/control2024-02-19 06:50:54.0 +
@@ -66,7 +66,7 @@
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${fortran:Depends},
- libopenmpi3 (= ${binary:Version}), 
+ libopenmpi3t64 (= ${binary:Version}), 
  openmpi-common (>= ${source:Version}), 
  libibverbs-dev (>= 1.1.7) [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], 
libhwloc-dev,
  libevent-dev, 
@@ -91,12 +91,14 @@
  This package contains the header files and compiler wrappers which are needed
  to compile and link programs against libopenmpi.
 
-Package: libopenmpi3
+Package: libopenmpi3t64
+Provides: ${t64:Provides}
+Replaces: libopenmpi3
 Section: libs
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}, libhwloc-plugins, libpmix2
-Breaks: gromacs-openmpi (<< 2020~beta2-2), libeztrace0 (<< 1.1-8-5+b1), 
starpu-contrib-examples (<< 1.3.2+dfsg-2+b1), starpu-examples (<< 
1.3.2+dfsg-4+b1)
+Breaks: libopenmpi3 (<< ${source:Version}), gromacs-openmpi (<< 2020~beta2-2), 
libeztrace0 (<< 1.1-8-5+b1), starpu-contrib-examples (<< 1.3.2+dfsg-2+b1), 
starpu-examples (<< 1.3.2+dfsg-4+b1)
 Description: high performance message passing library -- shared library
  Open MPI is a project combining technologies and resources from several other
  projects (FT-MPI, LA-MPI, LAM/MPI, and PACX-MPI) in order to build the best
diff -Nru openmpi-4.1.6/debian/libopenmpi3.install 
openmpi-4.1.6/debian/libopenmpi3.install
--- openmpi-4.1.6/debian/libopenmpi3.install2024-01-01 17:14:56.0 
+
+++ openmpi-4.1.6/debian/libopenmpi3.install1970-01-01 00:00:00.0 
+
@@ -1,14 +0,0 @@
-# Shared libraries
-usr/lib/*/openmpi/lib/libmpi_mpifh*.so.*   
/usr/lib/${DEB_HOST_MULTIARCH}
-usr/lib/*/openmpi/lib/libmpi_usempif08*.so.*   
/usr/lib/${DEB_HOST_MULTIARCH}
-usr/lib/*/openmpi/lib/libmpi_usempi_ignore_tkr*.so.*   
/usr/lib/${DEB_HOST_MULTIARCH}
-usr/lib/*/openmpi/lib/libmca_common_sm.so.*
/usr/lib/${DEB_HOST_MULTIARCH}
-usr/lib/*/openmpi/lib/libmpi_cxx.so.*  
/usr/lib/${DEB_HOST_MULTIARCH}
-usr/lib/*/openmpi/lib/libmpi.so.*  
/usr/lib/${DEB_HOST_MULTIARCH}
-usr/lib/*/ope

Bug#1064262: python3-certbot-dns-standalone: please remove runtime dependency on python3-mock

[Alexandre Detiste]

Package: python3-certbot-dns-standalone
Version: 1.1-1
Severity: normal
X-Debbugs-Cc: Harlan Lieberman-Berg 

Hi,

python3-certbot-dns-standalone declares a runtime dependency on
(deprecated) python3-mock, which is kind weird and unsettling.

Please apply this patch to avoid generating such
runtime dep.

Greetings,


https://patch-diff.githubusercontent.com/raw/siilike/certbot-dns-standalone/pull/25.patch

--- a/certbot_dns_standalone/dns_standalone_test.py
+++ b/certbot_dns_standalone/dns_standalone_test.py
@@ -2,8 +2,7 @@
 
 import os
 import unittest
-
-import mock
+from unittest import mock
 
 from certbot import errors
 from certbot.plugins import dns_test_common
diff --git a/setup.py b/setup.py
index 652bfb7..7d311fb 100644
--- a/setup.py
+++ b/setup.py
@@ -12,7 +12,6 @@
 'acme>=0.21.1',
 'certbot>=2.1.0',
 'dnslib>=0.9.0',
-'mock',
 'setuptools',
 ]

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

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

Versions of packages python3-certbot-dns-standalone depends on:
pn  certbot
ii  python33.11.6-1
pn  python3-acme   
pn  python3-acme-abi-2 
pn  python3-certbot
pn  python3-certbot-abi-2  
pn  python3-dnslib 
ii  python3-mock   5.1.0-1
ii  python3-pkg-resources  68.1.2-2

python3-certbot-dns-standalone recommends no packages.

python3-certbot-dns-standalone suggests no packages.

Bug#1064261: ITP: python-sphinx-autodoc2 -- Sphinx extension to automatically generate API doc for Py packages

[Yogeswaran Umasankar]

Package: wnpp
Severity: wishlist
Owner: Yogeswaran Umasankar 
X-Debbugs-Cc: debian-de...@lists.debian.org, kd8...@gmail.com

* Package name: python-sphinx-autodoc2
  Version : 0.5.0
  Upstream Contact: Chris Sewell 
* URL : https://github.com/sphinx-extensions2/sphinx-autodoc2
* License : Expat
  Programming Lang: Python
  Description : Sphinx extension to automatically generate API doc for Py 
packages

There is no need to install your package to generate the
 documentation, and `sphinx-autodoc2` will correctly handle
 `if TYPE_CHECKING` blocks and other typing only features. You
 can even document packages from outside the project (via `git clone`).
 This is a depend for other packages in python and science. I planned
 to maintain it under DPT, and need sponsorship.

Bug#1064260: omniorb-dfsg: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: omniorb-dfsg
Version: 4.3.2+ds1-1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
omniorb-dfsg as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for omniorb-dfsg
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru omniorb-dfsg-4.3.2+ds1/debian/changelog 
omniorb-dfsg-4.3.2+ds1/debian/changelog
--- omniorb-dfsg-4.3.2+ds1/debian/changelog 2024-02-08 20:33:14.0 
+
+++ omniorb-dfsg-4.3.2+ds1/debian/changelog 2024-02-19 06:31:02.0 
+
@@ -1,3 +1,10 @@
+omniorb-dfsg (4.3.2+ds1-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 06:31:02 +
+
 omniorb-dfsg (4.3.2+ds1-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru omniorb-dfsg-4.3.2+ds1/debian/control 
omniorb-dfsg-4.3.2+ds1/debian/control
--- omniorb-dfsg-4.3.2+ds1/debian/control   2024-02-08 18:46:24.0 
+
+++ omniorb-dfsg-4.3.2+ds1/debian/control   2024-02-19 06:31:02.0 
+
@@ -95,13 +95,15 @@
  .
  This includes developer files for libcos4 and libcosdynamic4.
 
-Package: libomniorb4-3
+Package: libomniorb4-3t64
+Provides: ${t64:Provides}
+Breaks: libomniorb4-3 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libomniorb4-2
-Replaces: libomniorb4-2
+Replaces: libomniorb4-3, libomniorb4-2
 Description: omniORB core libraries
  omniORB4 is a freely available Common Object Request Broker
  Architecture (CORBA) 2.6 compliant object request broker (ORB)
@@ -115,7 +117,7 @@
 Package: libomniorb4-dev
 Architecture: any
 Section: libdevel
-Depends: libomniorb4-3 (= ${binary:Version}), libomnithread4-dev (= 
${binary:Version}), libssl-dev, pkgconf, ${misc:Depends}
+Depends: libomniorb4-3t64 (= ${binary:Version}), libomnithread4-dev (= 
${binary:Version}), libssl-dev, pkgconf, ${misc:Depends}
 Breaks: libomniorb3-dev
 Replaces: libomniorb3-dev
 Description: omniORB core libraries development files
diff -Nru omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3.dirs 
omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3.dirs
--- omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3.dirs2023-08-25 
18:49:22.0 +
+++ omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3.dirs1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-etc/
diff -Nru omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3.install 
omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3.install
--- omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3.install 2023-08-25 
18:49:22.0 +
+++ omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3.install 1970-01-01 
00:00:00.0 +
@@ -1,9 +0,0 @@
-usr/lib/*/libomniCodeSets4.so.*
-usr/lib/*/libomniConnectionMgmt4.so.*
-usr/lib/*/libomniDynamic4.so.*
-usr/lib/*/libomnihttpCrypto4.so.*
-usr/lib/*/libomnihttpTP4.so.*
-usr/lib/*/libomniORB4.so.*
-usr/lib/*/libomnisslTP4.so.*
-usr/lib/*/libomniZIOP4.so.*
-usr/lib/*/libomniZIOPDynamic4.so.*
diff -Nru omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3t64.dirs 
omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3t64.dirs
--- omniorb-dfsg-4.3.2+ds1/debian/libomniorb4-3

Bug#1064259: Remove spurious Depends: bubblewrap (it moved to libgnome-desktop-*)

[Trent W. Buck]

Package: nautilus
Version: 43.2-1
Severity: minor

Right now nautilus has Depends: bubblewrap, but it doesn't actually use 
bubblewrap.


https://salsa.debian.org/search?search=bubblewrap&nav_source=navbar&project_id=5329&group_id=2002&search_code=true&repository_ref=debian%2Flatest

This happened because nautilus used to contain an embedded copy of 
libgnome-desktop.
That was fixed, but the bubblewrap dependency was not removed.


https://salsa.debian.org/gnome-team/nautilus/-/commit/673c81cf9f1d68b71041220e6e44624dee44dbfc
 (libgnome-desktop embedded, bwrap required)

https://salsa.debian.org/gnome-team/nautilus/-/commit/4eb2d8705b7f799a16046b316a16ebde3af8dd0e
 (bwrap dependency documented)

https://salsa.debian.org/gnome-team/nautilus/-/commit/3862cf798039ccf3cb57d39400288314f04db25c
 (libgnome-desktop not embedded anymore, bwrap not directly required)

"libgnome-desktop* Depends: bubblewrap" provide this dependency already where 
it is still needed.


https://salsa.debian.org/search?search=bubblewrap&nav_source=navbar&project_id=5207&group_id=2002&search_code=true&repository_ref=debian%2Flatest


Boring context:
1. Can I use bwrap to harden XFCE's tumbler against the next
   https://security-tracker.debian.org/tracker/CVE-2023-4863 ?
2. Oh, nautilus Depends: bubblewrap directly.
   It's probably something simple (and steal-able!) like
   nautilus.desktop: TryExec=nautilus
   nautilus.desktop: Exec=bwrap ⋯ nautilus
3. Waitaminute, this isn't using bubblewrap *at all*?! >Confused<


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

Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 nautilus depends on:
ii  bubblewrap  0.8.0-2
ii  desktop-file-utils  0.26-1
ii  gsettings-desktop-schemas   43.0-1
ii  gvfs1.50.3-1
ii  libadwaita-1-0  1.2.2-1
ii  libc6   2.36-9+deb12u4
ii  libcairo2   1.16.0-7
ii  libcloudproviders0  0.3.1-2
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii  libgexiv2-2 0.14.0-1+b1
ii  libglib2.0-02.74.6-2
ii  libglib2.0-data 2.74.6-2
ii  libgnome-autoar-0-0 0.4.3-1
ii  libgnome-desktop-4-243.2-2
ii  libgstreamer-plugins-base1.0-0  1.22.0-3+deb12u1
ii  libgstreamer1.0-0   1.22.0-2
ii  libgtk-4-1  4.8.3+ds-2+deb12u1
ii  libnautilus-extension4  43.2-1
ii  libpango-1.0-0  1.50.12+ds-1
ii  libportal-gtk4-10.6-4
ii  libportal1  0.6-4
ii  libselinux1 3.4-1+b6
ii  libtracker-sparql-3.0-0 3.4.2-1
ii  nautilus-data   43.2-1
ii  shared-mime-info2.2-1
ii  tracker 3.4.2-1
ii  tracker-extract 3.4.3-1
ii  tracker-miner-fs3.4.3-1

Versions of packages nautilus recommends:
ii  gnome-sushi   43.0-2
ii  gvfs-backends 1.50.3-1
ii  libgdk-pixbuf2.0-bin  2.42.10+dfsg-1+b1
ii  librsvg2-common   2.54.7+dfsg-1~deb12u1

Versions of packages nautilus suggests:
ii  eog 43.2-1
ii  evince [pdf-viewer] 43.1-2+b1
pn  nautilus-extension-brasero  
pn  nautilus-sendto 
ii  totem   43.0-2
ii  vlc [mp3-decoder]   3.0.20-0+deb12u1
ii  xdg-user-dirs   0.18-1
ii  xpdf [pdf-viewer]   3.04+git20220601-1+b2

-- no debconf information

Bug#1064258: yad: Please update this package already

[Holmes]

Package: yad
Version: 0.40.0-1
Severity: important
X-Debbugs-Cc: 3a58f101-de75-4b85-b8fe-127896854...@simplelogin.com

Dear Maintainer,

yad hasn't seen any updates for years now.

Version 0.40.0-1 is so old that other applications depending on it are
complaining that the yad version is too old, which makes yad completely
unusable and forces user to compile their own yad version from source. This is
unacceptable.

Please update this package to a newer version. Thank you.


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

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

Versions of packages yad depends on:
ii  libc62.37-15
ii  libcairo21.18.0-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0 2.78.4-1
ii  libgtk-3-0   3.24.41-1
ii  libpango-1.0-0   1.51.0+ds-4
ii  libpangocairo-1.0-0  1.51.0+ds-4

yad recommends no packages.

yad suggests no packages.

Bug#1064257: ITP: rocm-tensile -- ROCm tool for generating and benchmarking assembly kernels

[Cordell Bloor]

Package: wnpp
Severity: wishlist
Owner: Cordell Bloor 
X-Debbugs-Cc: debian-de...@lists.debian.org, c...@slerp.xyz, 
debian...@lists.debian.org

* Package name: rocm-tensile
  Version : 6.0.2
* URL : https://github.com/ROCm/Tensile
* License : Expat
  Programming Lang: Python, HIP
  Description : ROCm tool for generating and benchmarking assembly kernels

 Tensile is a set of tools and libraries primarily for selecting
 parameters of GPU kernels implementing the general matrix multiply
 (GEMM) operation. There are three components that comprise Tensile:
 .
  1. A command-line tool for generating kernels, benchmarking them, and
 saving the parameters used for generating the best kernels (a.k.a.
 "solutions") in YAML files.
  2. A build system component that reads YAML solution files, generates
 kernel source files, and invokes the compiler to turn them into code
 object files. The kernels are indexed by their parameters in either
 YAML or MessagePack format within a TensileLibrary file.
  3. A runtime library for loading and executing the best available
 solution for a given set of GEMM input parameters (a.k.a. "a problem").

The rocm-tensile library sources are currently packaged as part of
rocblas in a multi-upstream tarball package, but they should be split
out so that the command-line tool can be packaged. Tensile kernels are a
vital part of the performance of the rocblas library. It is often
necessary to add tuned kernels for particular problem sizes to achieve
optimal performance in a new application or on a new hardware
architecture. This is therefore an important development tool for BLAS
performance on AMD GPUs.

A fork of the Tensile library is also used by hipblaslt. Splitting
Tensile out from the rocblas package may be helpful in preventing the
duplication of embedded copies. The Tensile library can also be used by
MIOpen.

This package is part of AMD's ROCm stack and will be maintained under
the Debian AI team umbrella.

Bug#1059223: reopen, stalls again migration

[Matthias Klose]

Control: reopen -1
Control: found -1  1.3.2-1

reopen, stalls again migration

Bug#1064256: nut: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: nut
Version: 2.8.1-3
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
nut as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for nut
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru nut-2.8.1/debian/changelog nut-2.8.1/debian/changelog
--- nut-2.8.1/debian/changelog  2024-01-11 16:01:16.0 +
+++ nut-2.8.1/debian/changelog  2024-02-19 03:12:25.0 +
@@ -1,3 +1,10 @@
+nut (2.8.1-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 03:12:25 +
+
 nut (2.8.1-3) unstable; urgency=medium
 
   * debian/control: Add missing Breaks/Replaces on nut-modbus (Closes:
diff -Nru nut-2.8.1/debian/control nut-2.8.1/debian/control
--- nut-2.8.1/debian/control2024-01-11 16:01:16.0 +
+++ nut-2.8.1/debian/control2024-02-19 03:12:25.0 +
@@ -200,7 +200,10 @@
  .
  This package contains FAQ, user, developer and packager documentation.
 
-Package: libupsclient6
+Package: libupsclient6t64
+Provides: ${t64:Provides}
+Replaces: libupsclient6
+Breaks: libupsclient6 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -219,7 +222,7 @@
 Section: libdevel
 Architecture: any
 Depends: libnss3-dev,
- libupsclient6 (= ${binary:Version}),
+ libupsclient6t64 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
 Multi-Arch: same
@@ -232,7 +235,10 @@
  .
  This package provides the development files.
 
-Package: libnutclient2
+Package: libnutclient2t64
+Provides: ${t64:Provides}
+Replaces: libnutclient2
+Breaks: libnutclient2 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -250,7 +256,7 @@
 Package: libnutclient-dev
 Section: libdevel
 Architecture: any
-Depends: libnutclient2 (= ${binary:Version}),
+Depends: libnutclient2t64 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
 Multi-Arch: same
@@ -263,7 +269,10 @@
  .
  This package provides the development files for the new client library.
 
-Package: libnutscan2
+Package: libnutscan2t64
+Provides: ${t64:Provides}
+Replaces: libnutscan2
+Breaks: libnutscan2 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -281,7 +290,7 @@
 Package: libnutscan-dev
 Section: libdevel
 Architecture: any
-Depends: libnutscan2 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: libnutscan2t64 (= ${binary:Version}), ${misc:Depends}, 
${shlibs:Depends}
 Breaks: libupsclient-dev (<< 2.7.4-9~)
 Replaces: libupsclient-dev (<< 2.7.4-9~)
 Multi-Arch: same
diff -Nru nut-2.8.1/debian/libnutclient2.install 
nut-2.8.1/debian/libnutclient2.install
--- nut-2.8.1/debian/libnutclient2.install  2024-01-11 16:01:16.0 
+
+++ nut-2.8.1/debian/libnutclient2.install  1970-01-01 00:00:00.0 
+
@@ -1,2 +0,0 @@
-lib/*/libnutclient.so.*
-lib/*/libnutclientstub.so.*
diff -Nru nut-2.8.1/debian/libnutclient2t64.install 
nut-2.8.1/debian/libnutclient2t64.instal

Bug#1064255: ITP: aemu -- This is an utility library for common functions used in the Android Emulator. External projects (gfxstream, QEMU) may use to perform C++ functions.

[Bo YU]

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

* Package name: aemu
  Version : 0.1.2 
  Upstream Contact: Google 
* URL : 
https://android.googlesource.com/platform/hardware/google/aemu/ 
* License : Apache-2.0 
  Programming Lang: C++ 
  Description : This is an utility library for common functions used in the 
Android Emulator. External projects (gfxstream, QEMU) may use to perform C++ 
functions.

AEMU development files, used by gfxstream to build against.

This is a blocker of #1059295 as above descriptions.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059295

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1028416: systemctl kexec doesn't shutdown system properly and corrupts mounted filesystems

[Miao Wang]

Dear maintainer,

I wonder if this fix can be backported to stable-pu and oldstable-pu,
since this bug may lead to data corruption. A possible approach might
be to mask the kexec init script in the systemd side, i.e. via
`systemctl mask kexec.service`, so that systemd users can get rid of
the kexec init script and other init system users can still enjoy
the provided kexec init script.

Cheers,

Miao Wang

Bug#1064254: /usr/bin/gpk-application: Crashes when searching

[Phil Calvin]

Package: gnome-packagekit
Version: 43.0-2
Severity: important
File: /usr/bin/gpk-application
X-Debbugs-Cc: p...@philcalvin.com

Dear Maintainer,

   * What led up to the situation?

   I recently did a `apt dist-upgrade` to get the latest packages for staging.
I reviewed the list of packages to be removed as is my practice, but none
seemed problematic. The full list of packages upgraded is below. I believe the
search feature was working fine prior to this upgrade.

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

   1. Open the GNOME PackageKit app by searching for "Packages."
   2. Enter a search string like "linux"
   3. Press enter

   * What was the outcome of this action?

   The application closes immediately without showing search results.

   When run from the command line (as `gpk-application`), the program logs the
following output when performing the steps above:

(gpk-application:9466): PackageKit-CRITICAL **: 22:53:54.382:
pk_client_generic_finish: assertion 'G_IS_TASK (res)' failed
zsh: segmentation fault  gpk-application

   * What outcome did you expect instead?

   The application should show a list of matching packages and not crash.

Most recent apt changes:

Start-Date: 2024-02-13  17:25:01 Commandline: apt-get dist-upgrade
Requested-By: eleos (1001) Install: libsvtav1enc1d1:amd64
(1.7.0+dfsg-2+b1, automatic), libsvtav1enc1d1:i386 (1.7.0+dfsg-2+b1,
automatic), libdleyna-core-1.0-6:amd64 (0.8.3-1+b1, automatic),
libgedit-gtksourceview-300-0:amd64 (299.0.4-3, automatic),
libperl5.38:amd64 (5.38.2-3, automatic), linux-image-6.6.13-amd64:amd64
(6.6.13-1, automatic), libqgis-server3.28.15:amd64
(3.28.15+dfsg-1, automatic), libgcc-14-dev:amd64 (14-20240201-3,
automatic), gcc-x86-64-linux-gnu:amd64 (4:13.2.0-7,
automatic), libqgis-analysis3.28.15:amd64 (3.28.15+dfsg-1,
automatic), libqgis-3d3.28.15:amd64 (3.28.15+dfsg-1,
automatic), cpp-x86-64-linux-gnu:amd64 (4:13.2.0-7,
automatic), linux-headers-6.6.13-common:amd64 (6.6.13-1,
automatic), gir1.2-gtksource-300:amd64 (299.0.4-3, automatic),
libqgis-native3.28.15:amd64 (3.28.15+dfsg-1, automatic), libwsutil15:amd64
(4.2.2-1, automatic), xtl-dev:amd64 (0.7.5-3, automatic),
libllvm17:i386 (1:17.0.6-5, automatic), g++-x86-64-linux-gnu:amd64
(4:13.2.0-7, automatic), cpp-13-x86-64-linux-gnu:amd64 (13.2.0-13,
automatic), libtss2-mu-4.0.1-0:amd64 (4.0.1-7, automatic),
libzxcvbn0:amd64 (2.5+dfsg-1+b1, automatic), libwiretap14:amd64
(4.2.2-1, automatic), libopenfec1:amd64 (1.4.2.9+dfsg-2,
automatic), libqgisgrass8-3.28.15:amd64 (3.28.15+dfsg-1, automatic),
libappstream5:amd64 (1.0.1-3, automatic), libwireshark17:amd64 (4.2.2-1,
automatic), gir1.2-girepository-2.0:amd64 (1.78.1-15, automatic),
libqt6multimedia6:amd64 (6.4.2-11, automatic), libnghttp3-3:amd64
(0.8.0-2, automatic), libpython3.12:amd64 (3.12.2-1, automatic),
libtepl-6-4:amd64 (6.8.0-2+b1, automatic), python3-zombie-imp:amd64
(0.0.2-2, automatic), linux-kbuild-6.6.13:amd64 (6.6.13-1, automatic),
libqgis-gui3.28.15:amd64 (3.28.15+dfsg-1, automatic), libqt6svg6:amd64
(6.4.2-4, automatic), libqgis-app3.28.15:amd64 (3.28.15+dfsg-1,
automatic), libavif16:amd64 (1.0.3-1, automatic), libavif16:i386
(1.0.3-1, automatic), libplacebo338:amd64 (6.338.2-1, automatic),
libplacebo338:i386 (6.338.2-1, automatic), libpython3.12-dev:amd64
(3.12.2-1, automatic), libgedit-gtksourceview-300-common:amd64 (299.0.4-3,
automatic), g++-13-x86-64-linux-gnu:amd64 (13.2.0-13, automatic),
libharfbuzz-gobject0:amd64 (8.3.0-2, automatic), python3.12-dev:amd64
(3.12.2-1, automatic), 7zip:amd64 (23.01+dfsg-8, automatic),
perl-modules-5.38:amd64 (5.38.2-3, automatic), libqgispython3.28.15:amd64
(3.28.15+dfsg-1, automatic), linux-headers-6.6.13-amd64:amd64
(6.6.13-1, automatic), gcc-13-x86-64-linux-gnu:amd64 (13.2.0-13,
automatic), libqgis-core3.28.15:amd64 (3.28.15+dfsg-1, automatic),
gcc-14-base:amd64 (14-20240201-3, automatic), gcc-14-base:i386
(14-20240201-3, automatic) Upgrade: dpkg:amd64 (1.22.2, 1.22.4),
fontconfig:amd64 (2.14.2-6, 2.14.2-6+b1), libvulkan1:amd64 (1.3.268.0-1,
1.3.275.0-1), libvulkan1:i386 (1.3.268.0-1, 1.3.275.0-1), reportbug:amd64
(12.0.0, 13.0.0), libgdal34:amd64 (3.8.2+dfsg-1, 3.8.3+dfsg-1),
graphicsmagick:amd64 (1.4+really1.3.42-1, 1.4+really1.3.42-1+b1),
libbox2d2:amd64 (2.4.1-3, 2.4.1-3+b2), lib32stdc++6:amd64 (13.2.0-7,
14-20240201-3), libgucharmap-2-90-7:amd64 (1:15.1.2-1, 1:15.1.2-1+b1),
libsphinxbase3:amd64 (0.8+5prealpha+1-16+b1, 0.8+5prealpha+1-16+b2),
libsphinxbase3:i386 (0.8+5prealpha+1-16+b1, 0.8+5prealpha+1-16+b2),
libcogl-path20:amd64 (1.22.8-4, 1.22.8-4+b1), libfreeimage3:amd64
(3.18.0+ds2-10, 3.18.0+ds2-10+b1), libssh2-1:amd64 (1.11.0-3,
1.11.0-4), libssh2-1:i386 (1.11.0-3, 1.11.0-4), libsynctex2:amd64
(2023.20230311.66589-8, 2023.20230311.66589-8+b1), openjdk-11-jdk:amd64
(11.0.21+9-1~deb11u1, 11.0.22+7-1~deb11u1), vlc-plugin-qt:amd64
(3.0.20-1+b1, 3.0.20-1+b2), libopenblas0:amd64 (0.3.25+ds-1, 0.3.25+ds-2),
openjdk-11-jre:amd64 (11.0.21+9-1~deb11u1

Bug#1061788: still fails autopkg tests

[Matthias Klose]

Control: reopen -1


almost succeeds ...

452s autopkgtest [23:18:04]: test integration:  - - - - - - - - - - 
results - - - - - - - - - -
452s integration  FAIL stderr: 
/tmp/autopkgtest.bA2TsA/build.5sQ/src/lib/bookletimposer/backend.py:87: 
SyntaxWarning: invalid escape sequence '\.'
452s autopkgtest [23:18:04]: test integration:  - - - - - - - - - - 
stderr - - - - - - - - - -
452s 
/tmp/autopkgtest.bA2TsA/build.5sQ/src/lib/bookletimposer/backend.py:87: 
SyntaxWarning: invalid escape sequence '\.'

452s   result = re.search("(.+)\.\w*$", value)
452s autopkgtest [23:18:04]:  summary
452s unittestsPASS
452s integration  FAIL stderr: 
/tmp/autopkgtest.bA2TsA/build.5sQ/src/lib/bookletimposer/backend.py:87: 
SyntaxWarning: invalid escape sequence '\.'

Bug#1064252: linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the default config "y"

[tomas k]

Package: src:linux
Version: 6.1.69-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: foren...@wi.rr.com

In the default config-6.1.0-17-amd64, there is a line: 
CONFIG_SYSTEM_TRUSTED_KEYS="y"

It is impossible to change it from y in menuconfig. Then, it creates 'error no 
rule to make y.  

-- Package-specific info:
** Version:
Linux version 6.1.0-17-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-17-amd64 
root=UUID=b8970480-c02f-4e13-83ea-99242beaa8c1 ro quiet

** Not tainted

** Kernel log:
[850617.148769]  sda: unable to read partition table
[850617.148860] sd 6:0:0:0: [sda] Attached SCSI disk
[850617.204217] sd 6:0:0:0: [sda] Synchronizing SCSI cache
[850617.444223] sd 6:0:0:0: [sda] Synchronize Cache(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850617.716182] usb 2-7.4: new high-speed USB device number 11 using xhci_hcd
[850617.888733] usb 2-7.4: New USB device found, idVendor=152d, idProduct=0562, 
bcdDevice= 2.09
[850617.888746] usb 2-7.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[850617.888748] usb 2-7.4: Product: SSK Storage
[850617.888750] usb 2-7.4: Manufacturer: SSK
[850617.888752] usb 2-7.4: SerialNumber: DD564198838B8
[850617.892008] scsi host6: uas
[850617.892602] scsi 6:0:0:0: Direct-Access SSK   0209 
PQ: 0 ANSI: 6
[850617.894762] sd 6:0:0:0: Attached scsi generic sg1 type 0
[850617.894982] sd 6:0:0:0: [sda] Spinning up disk...
[850618.428107] usb 2-7.4: USB disconnect, device number 11
[850618.924215] .ready
[850618.924291] sd 6:0:0:0: [sda] Read Capacity(16) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850618.924296] sd 6:0:0:0: [sda] Sense not available.
[850618.924302] sd 6:0:0:0: [sda] Read Capacity(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850618.924304] sd 6:0:0:0: [sda] Sense not available.
[850618.924314] sd 6:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[850618.924316] sd 6:0:0:0: [sda] 0-byte physical blocks
[850618.924321] sd 6:0:0:0: [sda] Write Protect is off
[850618.924324] sd 6:0:0:0: [sda] Mode Sense: 00 00 00 00
[850618.924328] sd 6:0:0:0: [sda] Asking for cache data failed
[850618.924333] sd 6:0:0:0: [sda] Assuming drive cache: write through
[850618.924342] sd 6:0:0:0: [sda] Preferred minimum I/O size 4096 bytes not a 
multiple of physical block size (0 bytes)
[850618.924345] sd 6:0:0:0: [sda] Optimal transfer size 33553920 bytes not a 
multiple of physical block size (0 bytes)
[850618.924995] sd 6:0:0:0: [sda] Attached SCSI disk
[854882.880440] usb 2-7.3: USB disconnect, device number 5
[854884.327593] usb 2-7.3: new low-speed USB device number 12 using xhci_hcd
[854884.457279] usb 2-7.3: New USB device found, idVendor=047d, idProduct=1020, 
bcdDevice= 1.08
[854884.457289] usb 2-7.3: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
[854884.457292] usb 2-7.3: Product: Kensington Expert Mouse
[854884.463747] input: Kensington Expert Mouse as 
/devices/pci:00/:00:14.0/usb2/2-7/2-7.3/2-7.3:1.0/0003:047D:1020.0004/input/input21
[854884.464101] hid-generic 0003:047D:1020.0004: input,hidraw2: USB HID v1.11 
Mouse [Kensington Expert Mouse] on usb-:00:14.0-7.3/input0
[860266.405755] audit: type=1400 audit(1707886801.612:37): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=178977 comm="cupsd" 
capability=12  capname="net_admin"
[880247.840603] wlp4s0: Connection to AP 00:90:7f:4a:10:b1 lost
[880459.847171] wlp4s0: authenticate with 00:90:7f:4a:10:b1
[880459.850240] wlp4s0: send auth to 00:90:7f:4a:10:b1 (try 1/3)
[880459.879928] wlp4s0: authenticated
[880459.881486] wlp4s0: associate with 00:90:7f:4a:10:b1 (try 1/3)
[880459.888498] wlp4s0: RX AssocResp from 00:90:7f:4a:10:b1 (capab=0x511 
status=0 aid=1)
[880459.893044] wlp4s0: associated
[880459.970372] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[880460.156234] wlp4s0: Limiting TX power to 21 (24 - 3) dBm as advertised by 
00:90:7f:4a:10:b1
[966628.811480] wlp4s0: Connection to AP 00:90:7f:4a:10:b1 lost
[966840.859629] wlp4s0: authenticate with 00:90:7f:4a:10:b1
[966840.862710] wlp4s0: send auth to 00:90:7f:4a:10:b1 (try 1/3)
[966840.891711] wlp4s0: authenticated
[966840.894718] wlp4s0: associate with 00:90:7f:4a:10:b1 (try 1/3)
[966840.898366] wlp4s0: RX AssocResp from 00:90:7f:4a:10:b1 (capab=0x511 
status=0 aid=1)
[966840.903409] wlp4s0: associated
[966840.943963] wlp4s0: Limiting TX power to 21 (24 - 3) dBm as advertised by 
00:90:7f:4a:10:b1
[966840.973030] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[1053031.509002] wlp4s0: deauthenticated from 00:90:7f:4a:10:b1 (Reason: 
3=DEAUTH_LEAVING)
[1053245.065573] wlp4s0: authenticate with 00:90:7f:4a:10:b1
[1053245.068633] wlp4s0: send auth to 00:90:7f:4a:10:b1 (try 1/3)
[1053245.0

Bug#1064253: new upstream release

[Antoine Beaupre]

Source: git-annex
Version: 10.20230126-3
Severity: wishlist

Upstream is now at 10.20240129 and we seem to be lagging behind a
little bit, is there a plan to sync up before trixie?

thanks!

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

Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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

-- no debconf information

Bug#864001: git-annex: Possible SHA-1 vulnerability: fixed in newer releases

[Antoine Beaupre]

Source: git-annex
Followup-For: Bug #864001

Control: fixed -1 7.20190129-3

Seems to me this should be closed; the fixed version has shipped in
Debian eons ago.


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

Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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

-- no debconf information

Bug#1064251: nodejs: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: nodejs
Version: 18.19.0+dfsg-6
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
nodejs as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for nodejs
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru nodejs-18.19.0+dfsg/debian/changelog 
nodejs-18.19.0+dfsg/debian/changelog
--- nodejs-18.19.0+dfsg/debian/changelog2023-12-03 21:41:14.0 
+
+++ nodejs-18.19.0+dfsg/debian/changelog2024-02-19 00:19:51.0 
+
@@ -1,3 +1,10 @@
+nodejs (18.19.0+dfsg-6.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 00:19:51 +
+
 nodejs (18.19.0+dfsg-6) unstable; urgency=medium
 
   * patch: remove useless and badly done icu_74 patch
diff -Nru nodejs-18.19.0+dfsg/debian/control nodejs-18.19.0+dfsg/debian/control
--- nodejs-18.19.0+dfsg/debian/control  2023-11-30 08:54:40.0 +
+++ nodejs-18.19.0+dfsg/debian/control  2024-02-19 00:19:51.0 +
@@ -55,7 +55,7 @@
 Depends: ${misc:Depends},
  libssl-dev (>= 1.1.1~),
  libuv1-dev (>= 1.33.0~),
- libnode108 (= ${binary:Version})
+ libnode108t64 (= ${binary:Version})
 Breaks: nodejs-dev (<< 10.0.0~dfsg1-3)
 Replaces: libv8-dev,
  nodejs-dev (<< 10.0.0~dfsg1-3)
@@ -68,7 +68,7 @@
  efficient, perfect for data-intensive real-time applications that run
  across distributed devices.
  .
- This package provides development headers for libnode108
+ This package provides development headers for libnode108t64
 
 Package: nodejs
 Architecture: amd64 arm64 armel armhf i386 kfreebsd-i386 kfreebsd-amd64 mips 
mips64el mips64r6el mipsel powerpc ppc64 ppc64el riscv64 s390x
@@ -78,7 +78,7 @@
  ${misc:Depends},
  sse2-support [i386],
  armv6k-support [armel], vfpv2-support [armel],
- libnode108 (= ${binary:Version})
+ libnode108t64 (= ${binary:Version})
 Recommends: ca-certificates,
  nodejs-doc
 Suggests: npm
@@ -105,7 +105,8 @@
  System, Events, Standard I/O, Modules, Timers, Child Processes, POSIX,
  HTTP, Multipart Parsing, TCP, DNS, Assert, Path, URL, Query Strings.
 
-Package: libnode108
+Package: libnode108t64
+Provides: ${t64:Provides}
 Section: libs
 Architecture: amd64 arm64 armel armhf i386 kfreebsd-i386 kfreebsd-amd64 mips 
mips64el mips64r6el mipsel powerpc ppc64 ppc64el riscv64 s390x
 Multi-Arch: same
@@ -116,10 +117,10 @@
  node-acorn (>= 6.2.1~) ,
  node-cjs-module-lexer (>= 1.2.2~) ,
  node-undici (>= 5.0.0~) 
-Breaks: node-modern-syslog (<< 1.1.4-2),
+Breaks: libnode108 (<< ${source:Version}), node-modern-syslog (<< 1.1.4-2),
  libnode64 (<< 10.24.1~),
  libnode72 (<< 13)
-Replaces: nodejs-legacy, libnode72, libnode83, libnode93
+Replaces: libnode108, nodejs-legacy, libnode72, libnode83, libnode93
 Conflicts: nodejs-legacy
 Description: evented I/O for V8 javascript - runtime library
  Node.js is a platform built on Chrome's JavaScript runtime for easily
diff -Nru nodejs-18.19.0+dfsg/debian/libnode108.install 
nodejs-18.19.0+dfsg/debian/libnode108.install
--- nodejs-18.19.0+dfsg/debian/libnode108.install   1970-01

Bug#1063422: [regression 6.1.y] f2fs: invalid zstd compress level: 6

[Chao Yu]

On 2024/2/9 4:19, Salvatore Bonaccorso wrote:

Hi Jaegeuk Kim, Chao Yu,

In Debian the following regression was reported after a Dhya updated
to 6.1.76:

On Wed, Feb 07, 2024 at 10:43:47PM -0500, Dhya wrote:

Package: src:linux
Version: 6.1.76-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

After upgrade to linux-image-6.1.0-18-amd64 6.1.76-1 F2FS filesystem
fails to mount rw.  Message in the boot journal:

   kernel: F2FS-fs (nvme0n1p6): invalid zstd compress level: 6

There was recently an f2fs patch to the 6.1 kernel tree which might be
related: https://www.spinics.net/lists/stable-commits/msg329957.html

Was able to recover the system by doing:

sudo mount -o 
remount,rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,compress_algorithm=lz4,compress_log_size=2,compress_mode=fs,atgc,discard_unit=block,memory=normal
 /dev/nvme0n1p6 /

under the running bad 6.1.0-18-amd64 kernel, then editing
/etc/default/grub:

   GRUB_DEFAULT="Advanced options for Debian GNU/Linux>Debian GNU/Linux, with Linux 
6.1.0-17-amd64"

and running 'update-grub' and rebooting to boot the 6.1.0-17-amd64
kernel.


The issue is easily reproducible by:

# dd if=/dev/zero of=test.img count=100 bs=1M
# mkfs.f2fs -f -O compression,extra_attr ./test.img
# mount -t f2fs -o 
compress_algorithm=zstd:6,compress_chksum,atgc,gc_merge,lazytime ./test.img /mnt

resulting in

[   60.789982] F2FS-fs (loop0): invalid zstd compress level: 6


Hi Salvatore,

Can you please try below fixes:

[PATCH 6.1] f2fs: add helper to check compression level
https://lore.kernel.org/linux-f2fs-devel/20240212160530.1017205-1-c...@kernel.org

[PATCH] f2fs: compress: fix to check zstd compress level correctly in mount 
option
https://lore.kernel.org/linux-f2fs-devel/20240212160818.1020903-1-c...@kernel.org

Thanks,



A bugzilla report has been submitted in
https://bugzilla.kernel.org/show_bug.cgi?id=218471

#regzbot introduced: v6.1.69..v6.1.76
#regzbot link: https://bugs.debian.org/1063422
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=218471

Regards,
Salvatore

Bug#1040416: linux-image-6.1.0-17-amd64: External log helps

[tomas k]

Package: src:linux
Followup-For: Bug #1040416
X-Debbugs-Cc: foren...@wi.rr.com

I had been having random loss of entire volumes of XFS, for 20 years. A 
compromise is to format with an external log on the same drive. 
I use 100MB log per 1TB data. So, in 'gdisk' (GPTFdisk) you can specify to make 
a partition of the entire drive (-) any amount, 
or + any amount. Or any size partition you wish +(-) any amount. I partiotion a 
2TB drive  the entire drive (-) 220mb. 

I make a partition for the remainder of the drive (-) 20mb, for a 200MB log. 
The last 20MB is superstition. XFS formats well using the defaults. 
For external log, it's 'mkfs.xfs -l logdev=/dev/nvme2n1p2 /dev/nvme2n1p1. 
Logdev= is a mount option, so be sure to include it. 
Also, don't permit XFS volumes to exceed 80% capacity.

Here's the tradeoff. Almost any problem with a XFS file system can be nuked by 
zeroing the log. Internal logs cause problems when zeroing. 
External logs zero every time. You lose some metadata, but that's not usually a 
big deal.

There are a few things to examine in formatting (mkfs.xfs). '-m crc=1' is the 
default. If you specify '-m crc=0', it's just insanity!
It's not designed to work without that. But, mechanical drives had their own 
crc checking. So, no one needed 2. 

Another thing is XFS is so fast it heats drives. So, you can look at the SMART 
data, with 'smartctl', or some Windows program,
and check the hottest temperature the drive has endured, and also its overall 
health.



-- Package-specific info:
** Version:
Linux version 6.1.0-17-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-17-amd64 
root=UUID=b8970480-c02f-4e13-83ea-99242beaa8c1 ro quiet

** Not tainted

** Kernel log:
[850617.148769]  sda: unable to read partition table
[850617.148860] sd 6:0:0:0: [sda] Attached SCSI disk
[850617.204217] sd 6:0:0:0: [sda] Synchronizing SCSI cache
[850617.444223] sd 6:0:0:0: [sda] Synchronize Cache(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850617.716182] usb 2-7.4: new high-speed USB device number 11 using xhci_hcd
[850617.888733] usb 2-7.4: New USB device found, idVendor=152d, idProduct=0562, 
bcdDevice= 2.09
[850617.888746] usb 2-7.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[850617.888748] usb 2-7.4: Product: SSK Storage
[850617.888750] usb 2-7.4: Manufacturer: SSK
[850617.888752] usb 2-7.4: SerialNumber: DD564198838B8
[850617.892008] scsi host6: uas
[850617.892602] scsi 6:0:0:0: Direct-Access SSK   0209 
PQ: 0 ANSI: 6
[850617.894762] sd 6:0:0:0: Attached scsi generic sg1 type 0
[850617.894982] sd 6:0:0:0: [sda] Spinning up disk...
[850618.428107] usb 2-7.4: USB disconnect, device number 11
[850618.924215] .ready
[850618.924291] sd 6:0:0:0: [sda] Read Capacity(16) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850618.924296] sd 6:0:0:0: [sda] Sense not available.
[850618.924302] sd 6:0:0:0: [sda] Read Capacity(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850618.924304] sd 6:0:0:0: [sda] Sense not available.
[850618.924314] sd 6:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[850618.924316] sd 6:0:0:0: [sda] 0-byte physical blocks
[850618.924321] sd 6:0:0:0: [sda] Write Protect is off
[850618.924324] sd 6:0:0:0: [sda] Mode Sense: 00 00 00 00
[850618.924328] sd 6:0:0:0: [sda] Asking for cache data failed
[850618.924333] sd 6:0:0:0: [sda] Assuming drive cache: write through
[850618.924342] sd 6:0:0:0: [sda] Preferred minimum I/O size 4096 bytes not a 
multiple of physical block size (0 bytes)
[850618.924345] sd 6:0:0:0: [sda] Optimal transfer size 33553920 bytes not a 
multiple of physical block size (0 bytes)
[850618.924995] sd 6:0:0:0: [sda] Attached SCSI disk
[854882.880440] usb 2-7.3: USB disconnect, device number 5
[854884.327593] usb 2-7.3: new low-speed USB device number 12 using xhci_hcd
[854884.457279] usb 2-7.3: New USB device found, idVendor=047d, idProduct=1020, 
bcdDevice= 1.08
[854884.457289] usb 2-7.3: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
[854884.457292] usb 2-7.3: Product: Kensington Expert Mouse
[854884.463747] input: Kensington Expert Mouse as 
/devices/pci:00/:00:14.0/usb2/2-7/2-7.3/2-7.3:1.0/0003:047D:1020.0004/input/input21
[854884.464101] hid-generic 0003:047D:1020.0004: input,hidraw2: USB HID v1.11 
Mouse [Kensington Expert Mouse] on usb-:00:14.0-7.3/input0
[860266.405755] audit: type=1400 audit(1707886801.612:37): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=178977 comm="cupsd" 
capability=12  capname="net_admin"
[880247.840603] wlp4s0: Connection to AP 00:90:7f:4a:10:b1 lost
[880459.847171] wlp4s0: authenticate with 00:90:7f:4a:10:b1
[880459.850240] wlp4s0: send auth to 00:90:7f:4a:10:b1 (try 1/3)
[880459.879928] wlp4s0: authenticated
[880459.881486] wlp4s0: associate with 00:90:7

Bug#1061806: lamassemble still fails autopkg tests with Python 3.12

[Matthias Klose]

Control: reopen -1

please see the tests triggered by python3-defaults. Not pasting these 
here in the bug report.


https://autopkgtest.ubuntu.com/packages/l/lamassemble/noble/amd64

Bug#854149: affected fonts

[Vincent Lefevre]

On 2018-03-16 21:40:56 +0100, Horst Schirmeier wrote:
> My test case: echo -e 'a\u0308a'
> 
> Correct rendering: äa
> (That's what I see with: Courier, Cousine, DejaVu Sans Mono, FreeMono)
> 
> Incorrect rendering: aä
> (That's what I see with: Andale Mono, Bitstream Vera Sans Mono, Courier
> 10 Pitch, Courier New, Hack Mono, Liberation Mono, Mitra Mono, Nimbus
> Mono L, Noto Mono, Oxygen Mono, Tlwg Mono, Tlwg Typo, Ubuntu Mono)

With libvte-2.91-0 0.75.91-2, I get äa as expected with DejaVu Sans Mono
and Liberation Mono.

But

echo -e '1\u03362'

is incorrect with both, though the result is different:
with DejaVu Sans Mono, I get a strikethrough 2, but with
Liberation Mono, the strikethrough is between 1 and 2.
And for

echo -e '...c\u20dd...'

the circle is after the c is both cases.

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

Bug#1061751: the autopkg test still fails

[Matthias Klose]

Control: reopen -1


 42s autopkgtest [02:05:28]: test testsuite: [---
 43s ln: failed to create symbolic link '/usr/bin/python3': Permission 
denied

 43s autopkgtest [02:05:29]: test testsuite: ---]
 43s autopkgtest [02:05:29]: test testsuite:  - - - - - - - - - - 
results - - - - - - - - - -

 43s testsuiteFAIL non-zero exit status 1
 43s autopkgtest [02:05:29]:  summary
 43s testsuiteFAIL non-zero exit status 1


either needs the needs-root restriction, or you manage the symlink in a 
writable path like $AUTOPKG_TEST/bin.

Bug#1052566: additional information

[Vladimir Petko]

Dear Maintainers,
Dear Maintainers,

  Would it be possible to consider a merge request[1] that addresses this issue?

Best Regards,
 Vladimir.

 [1] 
https://salsa.debian.org/java-team/libnative-platform-java/-/merge_requests/4

Bug#1064250: bbpager segfaults after a while of use

[C. Petersen]

Package: bbpager
Version: 0.4.7-10
Severity: important
X-Debbugs-Cc: c.peter...@firemail.de

Dear Maintainer,


bbpager, wether started seperately or from /home/me/.fluxbox/startup segfaults
after a while of not being idle. This is true for the package from the
repository or one built from debian source.


(gdb):
#0  std::_List_iterator::operator++ (this=0x7fffdac0)
at /usr/include/c++/12/bits/stl_list.h:297
__tmp = 
#1  0x55564ee6 in WMInterface::updateWindowList (this=0x555eb1c0)
at ./src/wminterface.cxx:84
it = 49
it_end = 49
pit = 
pit_end = 0x2
window_vect = std::vector of length 3, capacity 3 = {25165838,
27262990, 29360132}
pwindow = 0x555b0b30
#2  0x555653fc in WMInterface::propertyNotifyEvent
(this=0x555eb1c0, event=0x7fffdbc0)
at ./src/wminterface.cxx:185
No locals.
#3  0x77e465b0 in bt::Application::run() () from /lib/x86_64-linux-
gnu/libbt.so.0
No symbol table info available.
#4  0xe9a2 in main (argc=1, argv=0x7fffe168) at
./src/main.cxx:112
bbpager = { = {}, resource =
0x555e5620, desktop_nr = 4,
  wminterface = 0x555eb1c0, root_window = 963, pager_window_list =
std::__cxx11::list = {
[0] = 0x555b2950, [1] = 0x555b0b30}, desktop_window_list =
std::__cxx11::list = {
[0] = 0x555b0d40, [1] = 0x555ea1a0, [2] = 0x555ffa10,
[3] = 0x555ffc60},
  wm_init = false, number_of_desktops = 4, current_desktop_nr = 2,
iargv = 0x0, iargc = 0,
  row_last = 0, column_last = 0, _ewmh = 0x555b93d0,
xa_wm_delete_window = 338,
  xa_wm_state = 389, current_screen_info = @0x55587340,
current_screen = 0,
  frame_window = 0x555ef300, config = @0x7fffdda0}
i = 1
options = {withdrawn = false, decorated = false, shape = false, _argc =
1, _argv = 0x7fffe168,
  _geometry = "", rc_filename = "", blackbox_rc_filename = "", app_name
= "/usr/bin/bbpager",
  display_name = ""}

coredump:

Message: Process 140913 (bbpager) of user 1000 dumped core.

Stack trace of thread 140913:
#0  0x55f7f1d3c918
_ZNSt14_List_iteratorIP11PagerWindowEppEi (bbpager + 0x8918)
#1  0x55f7f1d44ee6 _ZN11WMInterface16updateWindowListEv
(bbpager + 0x10ee6)
#2  0x55f7f1d453fc
_ZN11WMInterface19propertyNotifyEventEPK14XPropertyEvent (bbpager + 0x113fc)
#3  0x7fabc86df5b0 _ZN2bt11Application3runEv (libbt.so.0 +
0x115b0)
#4  0x55f7f1d3e9a2 main (bbpager + 0xa9a2)
#5  0x7fabc824624a __libc_start_call_main (libc.so.6 +
0x2724a)
#6  0x7fabc8246305 __libc_start_main_impl (libc.so.6 +
0x27305)
#7  0x55f7f1d39791 _start (bbpager + 0x5791)
ELF object binary architecture: AMD x86-64

earlier strace (with the package from Debian):
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\24\0\6\0\303\3\0\0W\1\0\0!\0\0\0\0\0\0\0\1\0\0\0",
iov_len=24}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 24
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\1
7\n\1\0\0\0!\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=4096}],
msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 36
recvmsg(3, {msg_namelen=0}, 0)  = -1 EAGAIN (Die Ressource ist zur Zeit
nicht verfügbar)
recvmsg(3, {msg_namelen=0}, 0)  = -1 EAGAIN (Die Ressource ist zur Zeit
nicht verfügbar)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\16\0\2\0\3\0`\2", iov_len=8}, {iov_base=NULL,
iov_len=0}, {iov_base="", iov_len=0}], 3) = 8
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\0\t8\n\3\0`\2\0\0\16\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3,
[{iov_base="\f\0\7\0\232\0\0\2\17\0\0\0\21\0\0\0\21\0\0\0\23\0\0\0\4\0\0\0\f\0\4\0"...,
iov_len=112}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 112
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\f\09\n\232\0\0\2\0\0\0\0\23\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\f\0:\n\20\0\0\2$\0\21\0\2\0\4\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 132
recvmsg(3, {msg_namelen=0}, 0)  = -1 EAGAIN (Die Ress

Bug#1064249: net-snmp: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: net-snmp
Version: 44.8-3
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
net-snmp as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for net-snmp
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru net-snmp-5.9.4+dfsg/debian/changelog 
net-snmp-5.9.4+dfsg/debian/changelog
--- net-snmp-5.9.4+dfsg/debian/changelog2023-08-19 09:36:39.0 
+
+++ net-snmp-5.9.4+dfsg/debian/changelog2024-02-18 23:48:19.0 
+
@@ -1,3 +1,10 @@
+net-snmp (5.9.4+dfsg-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 23:48:19 +
+
 net-snmp (5.9.4+dfsg-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru net-snmp-5.9.4+dfsg/debian/control net-snmp-5.9.4+dfsg/debian/control
--- net-snmp-5.9.4+dfsg/debian/control  2023-08-19 09:36:39.0 +
+++ net-snmp-5.9.4+dfsg/debian/control  2024-02-18 23:48:18.0 +
@@ -74,7 +74,10 @@
  description, you need to activate the non-free repository and install the
  "snmp-mibs-downloader" package.
 
-Package: libsnmp40
+Package: libsnmp40t64
+Provides: ${t64:Provides}
+Replaces: libsnmp40
+Breaks: libsnmp40 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -89,14 +92,15 @@
  sending, receiving, decoding, and manipulation of the SNMP requests
  and responses.
 
-Package: libnetsnmptrapd40
+Package: libnetsnmptrapd40t64
+Provides: ${t64:Provides}
 Section: libs
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}, libsnmp-base
-Breaks: libsnmp40 (<= 5.9+dfsg-1)
-Replaces: libsnmp40 (<= 5.9+dfsg-1)
+Breaks: libnetsnmptrapd40 (<< ${source:Version}), libsnmp40t64 (<= 5.9+dfsg-1)
+Replaces: libnetsnmptrapd40, libsnmp40t64 (<= 5.9+dfsg-1)
 Description: SNMP (Simple Network Management Protocol) trap library
  The Simple Network Management Protocol (SNMP) provides a framework
  for the exchange of management information between agents (servers)
@@ -109,7 +113,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: no
-Depends: libc6-dev, libsnmp40 (=${binary:Version}), libnetsnmptrapd40 
(=${binary:Version}),
+Depends: libc6-dev, libsnmp40t64 (=${binary:Version}), libnetsnmptrapd40t64 
(=${binary:Version}),
  libwrap0-dev, libssl-dev, procps,
  libkvm-dev [kfreebsd-any], libsensors-dev [linux-any], 
${misc:Depends},
  libpci-dev
diff -Nru net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40.install 
net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40.install
--- net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40.install2023-08-19 
09:36:39.0 +
+++ net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40.install1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libnetsnmptrapd.so.*
diff -Nru net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40t64.install 
net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40t64.install
--- net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40t64.install 1970-01-01 
00:00:00.0 +
+++ net-sn

Bug#1064247: Update snakeyaml to v2.2 or later

[Jérôme Charaoui]

Package: puppetserver
Severity: normal
Version: 8.4.0-1~exp1
Owner: po...@debian.org

Hello,

The "puppetserver" CLI subcommands have evolved a bit between Puppet 
Server releases 7 and 8, so the manpages should be updated to reflect 
those changes.


Thanks!

-- Jérôme

Bug#1064246: neon27: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: neon27
Version: 0.33.0-1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
neon27 as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for neon27
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru neon27-0.33.0/debian/changelog neon27-0.33.0/debian/changelog
--- neon27-0.33.0/debian/changelog  2024-02-02 22:12:14.0 +
+++ neon27-0.33.0/debian/changelog  2024-02-18 23:41:28.0 +
@@ -1,3 +1,10 @@
+neon27 (0.33.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 23:41:28 +
+
 neon27 (0.33.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru neon27-0.33.0/debian/control neon27-0.33.0/debian/control
--- neon27-0.33.0/debian/control2023-10-03 21:27:50.0 +
+++ neon27-0.33.0/debian/control2024-02-18 23:41:27.0 +
@@ -7,7 +7,10 @@
 Rules-Requires-Root: no
 Homepage: https://notroj.github.io/neon/
 
-Package: libneon27
+Package: libneon27t64
+Provides: ${t64:Provides}
+Replaces: libneon27
+Breaks: libneon27 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -46,15 +49,19 @@
 Conflicts: libneon-dev, libneon24-doc (<= 0.24.5-1), libneon25-dev (<< 
0.28.2-5), libneon27-gnutls-dev
 Provides: libneon-dev
 Replaces: libneon-dev, libneon25-dev, libneon27-gnutls-dev
-Depends: ${misc:Depends}, libneon27 (= ${binary:Version}), libssl-dev, 
libxml2-dev, libkrb5-dev, pkgconf
-Description: Header and static library files for libneon27
+Depends: ${misc:Depends}, libneon27t64 (= ${binary:Version}), libssl-dev, 
libxml2-dev, libkrb5-dev, pkgconf
+Description: Header and static library files for libneon27t64
  This package contains the headers and the static library for libneon27.
  .
  Neon provides lower-level interfaces to directly implement new HTTP
  methods, and higher-level interfaces so that you don't have to
  worry about the lower-level stuff.
 
-Package: libneon27-gnutls
+Package: libneon27t64-gnutls
+Provides: ${t64:Provides}
+X-Time64-Compat: libneon27-gnutls
+Replaces: libneon27-gnutls
+Breaks: libneon27-gnutls (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -94,9 +101,9 @@
 Conflicts: libneon-dev, libneon24-doc (<= 0.24.5-1), libneon25-dev (<< 
0.28.2-5), libneon27-dev
 Provides: libneon-dev
 Replaces: libneon-dev, libneon25-dev, libneon27-dev
-Depends: ${misc:Depends}, libneon27-gnutls (= ${binary:Version}),
+Depends: ${misc:Depends}, libneon27t64-gnutls (= ${binary:Version}),
  libgnutls28-dev, libxml2-dev, libkrb5-dev, pkgconf
-Description: Header and static library files for libneon27 (GnuTLS enabled)
+Description: Header and static library files for libneon27t64 (GnuTLS enabled)
  This package contains the headers and the static library for
  libneon27-gnutls.
  .
diff -Nru neon27-0.33.0/debian/libneon27-gnutls.lintian-overrides 
neon27-0.33.0/debian/libneon27-gnutls.lintian-overrides
--- neon27-0.33.0/debian/libneon27-gnutls.lintian-overrides 2015-10-03 
19:

Bug#1064194: 535.86.05 breaks Xorg

[Andreas Beckmann]

On 18/02/2024 09.13, Harald Dunkel via pkg-nvidia-devel wrote:

Rebuilding the package using the installed libc6 and tools
did not help. log file is attached.


Rebuilding the package won't change anything since we are only repacking 
upstream provided binaries.


I didn't spot anything obvious in the upstream changelog for the newer 
releases so I'll just upload the next (not latest) upstream release 
(because that's the one I've ready right now) in the hope it improves 
things.


Andreas

Bug#1063717: NVIDIA packages in stable-updates fix module compilation for linux 6.1.76-1

[Andreas Beckmann]

On 18/02/2024 17.06, matte.mb2006.9...@gmail.com wrote:

https://lists.debian.org/debian-stable-announce/2024/02/msg2.html



The update is not yet available on my PC. I live in Italy.


Do you have bookworm-updates (or stable-updates) enabled in your 
sources.list(.d/)?

See detailed instructions in the announcement email linked above.


Andreas

Bug#1064070: RFP: cxxheaderparser -- python library for parsing C++ headers

[Christian Kastner]

Control: tag -1 pending

I've uploaded this to experimental, though with the Debian Python Team
as maintainer. Because although it is a dependency of the ROCm stack, it
seems to be a generally useful Python library.

Best,
Christian

On 2024-02-16 18:57, Cordell Bloor wrote:
> Package: wnpp
> Severity: wishlist
> X-Debbugs-Cc: c...@slerp.xyz, debian...@lists.debian.org
> 
> * Package name: cxxheaderparser
>   Version : 1.3.1
>   Upstream Contact: RobotPy Development Team 
> * URL : https://github.com/robotpy/cxxheaderparser
> * License : BSD-3-Clause
>   Programming Lang: Python
>   Description : Python library for parsing C++ headers
> 
> The cxxheaderparser library is used to parse syntactically valid C++
> code and operate on the results. It provides both a visitor-style
> interface to process the results as they are being parsed or the option
> of a single data structure containing all parsed information.
> 
> This library is a successor to CppHeaderParser, which is a build
> dependency of the AMD ROCm GPU profiling libraries used by PyTorch.
> Specifically, CppHeaderParser is required for roctracer and parts of
> rocm-hipamd. As CppHeaderParser has been deprecated by its authors,
> those libraries will need to be migrated to cxxheaderparser.
> 

Bug#1064181: binutils: libgprofng0: new symbol name version number is an unintended value

[Matthias Klose]

On 18.02.24 06:38, Hiroyuki YAMAMORI wrote:

Source: binutils
Version: 2.42-2
Severity: normal

Dear Maintainer,

Looking at libgprofng0's debian symbols file
"/var/lib/dpkg/info/libgprofng0\:amd64.symbols" line: 1170
  _ZN3Elf19get_funcname_in_pltEm@Base 2.42-2

As shown above, the version number should be 2.42, but it is 2.42-2.
When I tried to build the package, the following error message appeared.

```
dpkg-gensymbols -Pdebian/libgprofng0 -plibgprofng0 -ldebian/libbinutils
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libgprofng0/DEBIAN/symbols doesn't match 
completely debian/libgprofng0.symbols
--- debian/libgprofng0.symbols (libgprofng0_2.42-2_amd64)
+++ dpkg-gensymbolsx29YlY   2024-02-17 11:53:21.237584672 +0900
@@ -1222,7 +1222,8 @@
   _ZN3Elf15get_bfd_symbolsEv@Base 2.41.50.20231202
   _ZN3Elf16elf_getancillaryEP8Elf_DatajP17S_Elf64_Ancillary@Base 2.41
   _ZN3Elf16get_related_fileEPKcS1_@Base 2.41
- (subst)_ZN3Elf19get_funcname_in_pltE{uint64_t}@Base 2.42
+ _ZN3Elf19get_funcname_in_pltEm@Base 2.42-2
+#MISSING: 2.42-2# (subst)_ZN3Elf19get_funcname_in_pltE{uint64_t}@Base 2.42
   _ZN3Elf20find_ancillary_filesEPc@Base 2.41
   _ZN3Elf4dumpEv@Base 2.41
   _ZN3Elf8elf_initEv@Base 2.41
@@ -1339,9 +1340,11 @@
   (arch=!i386 !x32)_ZN6Disasm12set_addr_endEm@Base 2.41
   (arch=i386 x32)_ZN6Disasm12set_addr_endEy@Base 2.41
   _ZN6Disasm12set_img_nameEPc@Base 2.41
- (subst)_ZN6Disasm14map_PC_to_funcE{uint64_t}@Base 2.42
+ _ZN6Disasm14map_PC_to_funcEm@Base 2.42-2
+#MISSING: 2.42-2# (subst)_ZN6Disasm14map_PC_to_funcE{uint64_t}@Base 2.42
   _ZN6Disasm18remove_disasm_hndlEPv@Base 2.41
- (subst)_ZN6Disasm19get_funcname_in_pltE{uint64_t}@Base 2.42
+ _ZN6Disasm19get_funcname_in_pltEm@Base 2.42-2
+#MISSING: 2.42-2# (subst)_ZN6Disasm19get_funcname_in_pltE{uint64_t}@Base 2.42
   _ZN6DisasmC1E10Platform_tP5Stabs@Base 2.41
   _ZN6DisasmC1EPc@Base 2.41
   _ZN6DisasmC2E10Platform_tP5Stabs@Base 2.41
make: [debian/rules:1625: binary-native] Error 1 (ignored)
```
```
Now running lintian binutils_2.42-2_amd64.changes ...
E: libgprofng0: symbols-file-contains-current-version-with-debian-revision on 
symbol _ZN3Elf19get_funcname_in_pltEm@Base and 2 others (libgprofng.so.0) 
[symbols]
```

As you can see from the above, there are some bad parts in
`debian/libgprofng0.symbols`.
`man 5 deb-src-symbols` does not find `subst` tag.
One fix way is to write the following using `regex` tag.
```
  (regex)"^_ZN3Elf19get_funcname_in_pltE[my]@Base$" 2.42
```
When a function has two or more arguments, for example,
replace `[my]` with `[lmxy]+`, or more simply `.*`.
Another fix way is to write the following using `arch-bits`tag.
```
  (arch-bits=64)_ZN3Elf19get_funcname_in_pltEm@Base 2.42
  (arch-bits=32)_ZN3Elf19get_funcname_in_pltEy@Base 2.42
```

As a suggestion, the following is written in `debian/libgprofng0.symbols`,
but it is ambiguous to list negative types in `arch` tag specification,
so I think it should be avoided.
```
  (arch=!i386 !x32)_Z13dbeGetSamplesiill@Base 2.41
```


hmm, all these were generated with the pkg-symbolshelper. so probably a 
bug report there would be the right thing to do?

Bug#1064060: wsdd: Split to client and server packages?

[Matt Grant]

Hi!

As maintainer been investigating how wsdd is run by gvfs.  If wsdd is 
already running as a server to support smbd, gvfsd will not be able to 
start another wsdd due to the interface multicast socket(s) already 
being taken


I can set the default arguments for wsdd to listen on a socket in say 
/var/run/wsdd/wsdd.  Is it possible to tell gvfsd to talk to that socket 
instead of its one in /run/user//gvfsd/wsdd ??


Cheers,

Matt

On 18/02/24 23:20, Laurent Bigonville wrote:
On Fri, 16 Feb 2024 10:04:53 -0500 =?UTF-8?Q?Jeremy_B=C3=ADcha?= 
 wrote:


> gvfs 1.53.90-1 uses wsdd to find newer Windows network shares.
>
> My initial understanding is that wsdd can be used both to advertise
> network shares or to find network shares. gvfs only needs the "find"
> behavior and gvfs calls wsdd from $PATH directly when needed.
>
> I believe it is unwanted behavior for wsdd.service to be running for
> gvfs's use case.
>
> Therefore, please create a separate package for wsdd.service , perhaps
> named wsdd-server

Currently all machines installing wsdd start to advertise on the 
network and are automatically discoverable, this is less than optimal 
indeed.


And other alternative is to pass "--no-enable --no-start" to 
dh_installsystemd and add an After/Wants in the packages that really 
requires the "server" part to be running?


Not sure what other packages we are talking about here? There is 
currently on one rdep and it's gvfs


But I agree the "server" part shouldn't be running by default, at 
least without the "--no-host" option

Bug#1064191: openjdk-8: fails to install on i386 mantic, focal and jammy

[Thorsten Glaser]

Hi Vladimir,

> Would it be possible to consider the following changes:

>- d/JB-jre-headless.postinst.in: check that /usr/share/binfmts exists
>  before trying to delete it.

that’s fine, will be merged, thanks.

>- d/rules: build without atk bridge on i386 for Ubuntu versions that
>  do not have it.

Absolutely not. This is what causes installation failures
on i386 in the first place: the package is no longer M-A
coïnstallable.

Where is the problem of building against the bridge but
not enabling it? I mean, it built on i386, so the bridge
code clearly exists on i386.

The need here is that i386 and amd64, and really all other
arches but this double shows it the most, *cannot* install
different files.

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent

Bug#1063690: Segfault on table containing two sets

[Nina R.]

Having two sets in one table like this also causes a
segfault:

table inet filter {
  set blackhole_v4 {
type ipv4_addr
flags timeout, interval
  }
  set blackhole_v6 {
type ipv6_addr
flags timeout, interval
  }
}

In the meantime, I had to install 0.9.8-3.1 from
snapshot.debian.org.


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

Bug#1064244: med-fichier: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: med-fichier
Version: 4.1.0+repack-4
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
med-fichier as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for med-fichier
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru med-fichier-4.1.0+repack/debian/changelog 
med-fichier-4.1.0+repack/debian/changelog
--- med-fichier-4.1.0+repack/debian/changelog   2023-09-29 18:43:42.0 
+
+++ med-fichier-4.1.0+repack/debian/changelog   2024-02-18 21:36:18.0 
+
@@ -1,3 +1,10 @@
+med-fichier (4.1.0+repack-4.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 21:36:18 +
+
 med-fichier (4.1.0+repack-4) unstable; urgency=medium
 
   * Fix openmpi include dirs (closes: #1052753)
diff -Nru med-fichier-4.1.0+repack/debian/control 
med-fichier-4.1.0+repack/debian/control
--- med-fichier-4.1.0+repack/debian/control 2021-10-25 21:32:14.0 
+
+++ med-fichier-4.1.0+repack/debian/control 2024-02-18 21:36:18.0 
+
@@ -91,7 +91,7 @@
 Multi-Arch: same
 Section: libdevel
 Depends: libhdf5-mpi-dev,
- libmedc11 (= ${binary:Version}),
+ libmedc11t64 (= ${binary:Version}),
  ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
 Description: Development files for libmedc
@@ -102,7 +102,8 @@
  This package contains the header files and static library needed to
  compile applications that use libmedC.
 
-Package: libmedc11
+Package: libmedc11t64
+Provides: ${t64:Provides}
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -111,8 +112,8 @@
 Suggests: libmed-doc,
   libmed-tools
 Pre-Depends: ${misc:Pre-Depends}
-Breaks: libmedc1, libmedc1v5 (= 4.0.0+repack-1)
-Replaces: libmedc1, libmedc1v5 (= 4.0.0+repack-1)
+Breaks: libmedc11 (<< ${source:Version}), libmedc1, libmedc1v5 (= 
4.0.0+repack-1)
+Replaces: libmedc11, libmedc1, libmedc1v5 (= 4.0.0+repack-1)
 Description: Library to exchange meshed data (C version)
  MED-fichier (Modélisation et Echanges de Données, in English Modelisation
  and Data Exchange) is a library to store and exchange meshed data or
@@ -141,7 +142,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libs
-Depends: libmedc11,
+Depends: libmedc11t64,
  ${misc:Depends},
  ${shlibs:Depends}
 Suggests: libmed-doc,
diff -Nru med-fichier-4.1.0+repack/debian/libmedc11.install 
med-fichier-4.1.0+repack/debian/libmedc11.install
--- med-fichier-4.1.0+repack/debian/libmedc11.install   2021-10-25 
21:32:14.0 +
+++ med-fichier-4.1.0+repack/debian/libmedc11.install   1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libmedC.so.*
diff -Nru med-fichier-4.1.0+repack/debian/libmedc11t64.install 
med-fichier-4.1.0+repack/debian/libmedc11t64.install
--- med-fichier-4.1.0+repack/debian/libmedc11t64.install1970-01-01 
00:00:00.0 +
+++ med-fichier-4.1.0+repack/debian/libmedc11t64.install2021-10-25 
21:32:14.0 +
@@ -0,0 +1 @@
+usr/lib/*/libmedC.so.*
diff -Nru med-fichier-4.1.0+repa

Bug#1064243: rust-ahash: Fails to build, requires rustc 1.72

[Jeremy Bícha]

Source: rust-ahash
Version: 0.8.8-1
Severity: serious
Tags: ftbfs

rust-ahash fails to build because it wants rustc >= 1.72 but Debian
Unstable only has rustc 1.70.

https://buildd.debian.org/status/package.php?p=rust-ahash

Thank you,
Jeremy Bícha

Bug#1064242: ITP: golang-github-monochromegane-go-gitignore -- A fast gitignore matching library for Go.

[Arthur Diniz]

Package: wnpp
Severity: wishlist
Owner: Arthur Diniz 

* Package name: golang-github-monochromegane-go-gitignore
  Version : 0.0~git20200626.205db1a-1
  Upstream Author : monochromegane
* URL : https://github.com/monochromegane/go-gitignore
* License : Expat
  Programming Lang: Go
  Description : Fast gitignore matching library for Go.

 This library use simple tree index for matching, so keep fast if
 gitignore file has many pattern.

 Features
  * Support absolute path (/path/to/ignore)
  * Support relative path (path/to/ignore)
  * Support accept pattern (!path/to/accept)
  * Support directory pattern (path/to/directory/)
  * Support glob pattern (path/to/\*.txt)

Bug#1064219: net-snmp: NMU diff for 64-bit time_t transition

[Steve Langasek]

On Sun, Feb 18, 2024 at 01:10:19PM -0800, Steve Langasek wrote:
> Hi Craig,

> On Mon, Feb 19, 2024 at 07:17:08AM +1100, Craig Small wrote:
> > Hi Steve,
> >   Looks like you missed one:

> > dh_installdocs -plibsnmp-perl -ptkmib -plibsnmp-base -plibsnmp40
> > dh_installdocs: error: Requested unknown package libsnmp40 via
> > -p/--package, expected one of: snmpd snmptrapd snmp libsnmp-base
> > libsnmp40t64 libnetsnmptrapd40t64 libsnmp-dev libsnmp-perl tkmib
> > dh_installdocs: error: unknown option or error during option parsing; 
> > aborting

> Uhm.  I'm unclear how this could be, since we do test builds of the packages
> (dpkg-buildpackage -b) before filing any bugs.  I'll dig into this.

Got it.  Sorry, newly introduced bug in the uploader script.  Fixing up the
patch now.

> > On Mon, 19 Feb 2024 at 03:54, Steve Langasek  wrote:
> > 
> > > Source: net-snmp
> > > Version: 5.9.4+dfsg-1
> > > Severity: important
> > > Tags: patch pending sid trixie
> > > User: debian-...@lists.debian.org
> > > Usertags: time-t
> > >
> > > NOTICE: these changes must not be uploaded to unstable yet!
> > >
> > > Dear maintainer,
> > >
> > > As part of the 64-bit time_t transition required to support 32-bit
> > > architectures in 2038 and beyond
> > > (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> > > net-snmp as a source package shipping runtime libraries whose ABI
> > > either is affected by the change in size of time_t, or could not be
> > > analyzed via abi-compliance-checker (and therefore to be on the safe
> > > side we assume is affected).
> > >
> > > To ensure that inconsistent combinations of libraries with their
> > > reverse-dependencies are never installed together, it is necessary to
> > > have a library transition, which is most easily done by renaming the
> > > runtime library package.
> > >
> > > Since turning on 64-bit time_t is being handled centrally through a change
> > > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
> > > important that libraries affected by this ABI change all be uploaded close
> > > together in time.  Therefore I have prepared a 0-day NMU for net-snmp
> > > which will initially be uploaded to experimental if possible, then to
> > > unstable after packages have cleared binary NEW.
> > >
> > > Please find the patch for this NMU attached.
> > >
> > > If you have any concerns about this patch, please reach out ASAP.  
> > > Although
> > > this package will be uploaded to experimental immediately, there will be a
> > > period of several days before we begin uploads to unstable; so if
> > > information
> > > becomes available that your package should not be included in the
> > > transition,
> > > there is time for us to amend the planned uploads.
> > >
> > >
> > >
> > > -- System Information:
> > > Debian Release: trixie/sid
> > >   APT prefers unstable
> > >   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
> > > 'experimental')
> > > Architecture: amd64 (x86_64)
> > >
> > > Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
> > > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> > > 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)
> > >
> 
> -- 
> Steve Langasek   Give me a lever long enough and a Free OS
> Debian Developer   to set it on, and I can move the world.
> Ubuntu Developer   https://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1064241: tryton-server: please remove extraneous dependency on obsolete python3-mock

[Alexandre Detiste]

Source: tryton-server
Version: 6.0.39-1
Severity: normal

Hi,

python3-mock is an obsolete library that has been merged
into the standard library since Python3.3 as unittest.mock;
we are slowly trying to get the distribution rid of it.

Greetings,

Alexandre


$ grep mock -r
debian/control:   python3-mock,--->  
Please remove this one line
trytond/tests/test_bus.py:from unittest.mock import patch
trytond/tests/test_filestore.py:from unittest.mock import patch
trytond/tests/test_ir.py:from unittest.mock import Mock, patch, ANY
trytond/tests/test_modelsql.py:from unittest.mock import patch, call
trytond/tests/test_modelview.py:from unittest.mock import patch
trytond/tests/test_mptt.py:from unittest.mock import patch
trytond/tests/test_rpc.py:from unittest.mock import Mock, DEFAULT, call
trytond/tests/test_rpc.py:obj.reset_mock()
trytond/tests/test_rpc.py:obj.reset_mock()
trytond/tests/test_rpc.py:obj.reset_mock()
trytond/tests/test_sendmail.py:from unittest.mock import ANY, Mock, MagicMock, 
patch, call
trytond/tests/test_sendmail.py:server.reset_mock()
trytond/tests/test_transaction.py:from unittest.mock import Mock
trytond/tests/test_transaction.py:dm.reset_mock()
trytond/tests/test_transaction.py:dm.reset_mock()
trytond/tests/test_tryton.py:import unittest.mock
trytond/tests/test_tryton.py:unittest.mock.patch.stopall()
trytond/tests/test_user.py:from unittest.mock import patch, ANY, Mock
trytond/tests/test_wsgi.py:from unittest.mock import Mock, sentinel

Bug#1064240: toppler FTCBFS: multiple reasons

[Helmut Grohne]

Source: toppler
Version: 1.3-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

toppler fails to cross build from source. The immediate failure is that
it attempts to build using the build architecture toolchain and thus
fails locating required dependencies. Nothing is passing cross tools to
make here. Using dh_auto_build is the simplest way to fix that. Then, it
also builds some build tools for creating data files. SDL2_image is only
used for those build tools and therefore required for the build
architecture rather than the host architecture. The dependency needs to
be annotated with :native. I'm attaching a patch for your convenience.

Helmut
diff --minimal -Nru toppler-1.3/debian/changelog toppler-1.3/debian/changelog
--- toppler-1.3/debian/changelog2022-02-12 22:13:19.0 +0100
+++ toppler-1.3/debian/changelog2024-02-18 17:39:38.0 +0100
@@ -1,3 +1,12 @@
+toppler (1.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ SDL2_image is used for build tools only.
+
+ -- Helmut Grohne   Sun, 18 Feb 2024 17:39:38 +0100
+
 toppler (1.3-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru toppler-1.3/debian/control toppler-1.3/debian/control
--- toppler-1.3/debian/control  2022-02-12 22:13:19.0 +0100
+++ toppler-1.3/debian/control  2024-02-18 17:39:38.0 +0100
@@ -2,7 +2,7 @@
 Section: games
 Priority: optional
 Maintainer: Bill Allombert 
-Build-Depends: debhelper-compat (= 13), libsdl2-dev, libsdl2-mixer-dev, 
libsdl2-image-dev,  zlib1g-dev, libpng-dev
+Build-Depends: debhelper-compat (= 13), libsdl2-dev, libsdl2-mixer-dev, 
libsdl2-image-dev:native,  zlib1g-dev, libpng-dev
 Rules-Requires-Root: no
 Standards-Version: 4.6.0
 Homepage: https://gitlab.com/roever/toppler/
diff --minimal -Nru toppler-1.3/debian/rules toppler-1.3/debian/rules
--- toppler-1.3/debian/rules2022-02-12 22:13:19.0 +0100
+++ toppler-1.3/debian/rules2024-02-18 17:39:38.0 +0100
@@ -13,7 +13,7 @@
rm -rf _build locale toppler
 
 override_dh_auto_build:
-   $(MAKE) toppler DATADIR=/usr/share/games LOCALEDIR=/usr/share/locale
+   dh_auto_build -- toppler DATADIR=/usr/share/games 
LOCALEDIR=/usr/share/locale
 
 override_dh_auto_install:
$(MAKE) install BINDIR=/usr/games  LOCALEDIR=/usr/share/locale 
MANDIR=/usr/share/man \

Bug#1064239: gxr FTCBFS: attempts to run tests despite DEB_BUILD_OPTIONS=nocheck

[Helmut Grohne]

Source: gxr
Version: 0.15.1-4
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

gxr fails to cross build from source, because it attempts to run tests
and badly fails doing so (at the meson build step already). Usually
cross builds disable testing via DEB_BUILD_OPTIONS=nocheck. I'm
attaching a patch that makes gxr honour this option and using it makes
the cross build succeed (without testing). Please consider applying it.

Helmut
diff --minimal -Nru gxr-0.15.1/debian/changelog gxr-0.15.1/debian/changelog
--- gxr-0.15.1/debian/changelog 2022-08-03 12:38:08.0 +0200
+++ gxr-0.15.1/debian/changelog 2024-02-18 18:46:36.0 +0100
@@ -1,3 +1,10 @@
+gxr (0.15.1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Support DEB_BUILD_OPTIONS=nocheck. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 18 Feb 2024 18:46:36 +0100
+
 gxr (0.15.1-4) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru gxr-0.15.1/debian/rules gxr-0.15.1/debian/rules
--- gxr-0.15.1/debian/rules 2022-08-03 12:38:08.0 +0200
+++ gxr-0.15.1/debian/rules 2024-02-18 18:46:34.0 +0100
@@ -11,9 +11,10 @@
HOME=$(CURDIR)/debian/tmp-home XDG_CACHE_HOME=
 
 override_dh_auto_test:
+ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
install -d $(CURDIR)/debian/tmp-home/.cache/gxr
# Run tests without VR runtime
env $(test_env) meson build
env $(test_env) ninja -C build
env $(test_env) meson test -C build/ --no-suite gxr:xr --no-suite 
post-install
-
+endif

Bug#1064236: skalibs FTCBFS: multiple reasons

[Helmut Grohne]

Source: skalibs
Version: 2.14.0.0-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

skalibs fails to cross build from source for multiple reasons. The
immediate failure is during the clean override that runs a bare
configure. Being bare, it is a native configure, but the environment
contains host compiler flags and the amd64 gcc doesn't particularly like
e.g. -mbranch-protection=standard as given on arm64. Hence, compiler
flags should be unset for a native invocation. Then the real configure
invocation misses the important --build and --host flags and it also
fails unless one tells it whether posixspawn works as expected. I'm
attaching a patch fixing all of these and it makes skalibs cross
buildable. Please consider applying it.

Helmut
diff --minimal -Nru skalibs-2.14.0.0/debian/changelog 
skalibs-2.14.0.0/debian/changelog
--- skalibs-2.14.0.0/debian/changelog   2023-11-08 08:20:50.0 +0100
+++ skalibs-2.14.0.0/debian/changelog   2024-02-18 12:25:33.0 +0100
@@ -1,3 +1,13 @@
+skalibs (2.14.0.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Do not pass host compiler flags to native configure during clean.
++ Pass --build and --host to configure.
++ Seed result of posixspawnearlyreturn: We do not work with old glibc.
+
+ -- Helmut Grohne   Sun, 18 Feb 2024 12:25:33 +0100
+
 skalibs (2.14.0.0-3) unstable; urgency=medium
 
   * Fix building on arch:all
diff --minimal -Nru skalibs-2.14.0.0/debian/rules skalibs-2.14.0.0/debian/rules
--- skalibs-2.14.0.0/debian/rules   2023-11-08 08:20:50.0 +0100
+++ skalibs-2.14.0.0/debian/rules   2024-02-18 12:25:33.0 +0100
@@ -5,13 +5,14 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export LDFLAGS += -Wl,--fatal-warnings
 
+CONFIG_OPT += --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE)
 CONFIG_OPT += --dynlibdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
 CONFIG_OPT += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
 CONFIG_OPT += --includedir=\$${prefix}/include/$(DEB_HOST_MULTIARCH)
 CONFIG_OPT += --sysdepdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)/skalibs/sysdeps
 
 ifneq (,$(filter cross,$(DEB_BUILD_PROFILES)))
-CONFIG_OPT += --with-sysdep-devurandom=yes
+CONFIG_OPT += --with-sysdep-devurandom=yes 
--with-sysdep-posixspawnearlyreturn=no
 endif
 
 %:
@@ -19,7 +20,7 @@
 
 # `make distclean` needs config.mak file
 override_dh_auto_clean-arch:
-   ./configure
+   env -u CFLAGS -u CPPFLAGS -u CXXFLAGS -u LDFLAGS ./configure
dh_auto_clean
 
 override_dh_auto_configure-arch:

Bug#1064238: fuseext2: move aliased files from / to /usr (DEP17)

[Helmut Grohne]

Package: fuseext2
Version: 0.4-1.4
Tags: patch trixie sid
User: helm...@debian.org
Usertags: dep17m2

We want to finalize the /usr-merge transition by moving all aliased
files from / to /usr via DEP17 to avoid negative effects arising from
the use of aliased files. fuseext2 is involved, because it ships
programs in aliased locations. I'm sending a patch, because it cannot be
converted using dh-sequence-movetousr. Note that this patch must not be
uploaded to bookworm-backports or earlier as it would violate the file
move moratorium there.

Helmut
diff --minimal -Nru fuse-umfuse-ext2-0.4/debian/changelog 
fuse-umfuse-ext2-0.4/debian/changelog
--- fuse-umfuse-ext2-0.4/debian/changelog   2023-09-29 01:48:00.0 
+0200
+++ fuse-umfuse-ext2-0.4/debian/changelog   2024-02-18 12:10:55.0 
+0100
@@ -1,3 +1,10 @@
+fuse-umfuse-ext2 (0.4-1.5) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * DEP17: Move files to /usr. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 18 Feb 2024 12:10:55 +0100
+
 fuse-umfuse-ext2 (0.4-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru fuse-umfuse-ext2-0.4/debian/patches/series 
fuse-umfuse-ext2-0.4/debian/patches/series
--- fuse-umfuse-ext2-0.4/debian/patches/series  2023-09-29 01:48:00.0 
+0200
+++ fuse-umfuse-ext2-0.4/debian/patches/series  2024-02-18 12:10:55.0 
+0100
@@ -1 +1,2 @@
 fuse-ext2.h.patch
+usrmove.patch
diff --minimal -Nru fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch 
fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch
--- fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch   1970-01-01 
01:00:00.0 +0100
+++ fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch   2024-02-18 
12:10:55.0 +0100
@@ -0,0 +1,22 @@
+--- fuse-umfuse-ext2-0.4.orig/fuse-ext2/Makefile.am
 fuse-umfuse-ext2-0.4/fuse-ext2/Makefile.am
+@@ -283,7 +283,7 @@
+ if LINUX
+ install-exec-local:
+   $(INSTALL) -d "$(DESTDIR)/usr/sbin"
+-  $(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" 
"$(DESTDIR)/sbin/mount.fuse-ext2"
++  $(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" 
"$(DESTDIR)/$(sbindir)/mount.fuse-ext2"
+ endif
+ 
+ dist_man1_MANS = fuse-ext2.1
+--- fuse-umfuse-ext2-0.4.orig/fuse-ext2/Makefile.in
 fuse-umfuse-ext2-0.4/fuse-ext2/Makefile.in
+@@ -1884,7 +1884,7 @@
+ #endif
+ @LINUX_TRUE@install-exec-local:
+ @LINUX_TRUE@  $(INSTALL) -d "$(DESTDIR)/usr/sbin"
+-@LINUX_TRUE@  $(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" 
"$(DESTDIR)/sbin/mount.fuse-ext2"
++@LINUX_TRUE@  $(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" 
"$(DESTDIR)/$(sbindir)/mount.fuse-ext2"
+ 
+ # Tell versions [3.59,3.63) of GNU make to not export all variables.
+ # Otherwise a system limit (for SysV at least) may be exceeded.
diff --minimal -Nru fuse-umfuse-ext2-0.4/debian/rules 
fuse-umfuse-ext2-0.4/debian/rules
--- fuse-umfuse-ext2-0.4/debian/rules   2023-09-29 01:47:05.0 +0200
+++ fuse-umfuse-ext2-0.4/debian/rules   2024-02-18 12:10:55.0 +0100
@@ -3,15 +3,17 @@
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
 
+DEB_CONFIGURE_EXTRA_FLAGS=--exec-prefix='$${prefix}'
+
 common-install-prehook-arch common-install-prehook-indep::
-   mkdir -p debian/tmp/sbin
+   mkdir -p debian/tmp/usr/sbin
 
 install/fuseext2::
dh_link -pfuseext2 /usr/share/man/man1/fuse-ext2.1 
/usr/share/man/man8/mount.fuse-ext2.8
-   dh_link -pfuseext2 /usr/bin/fuse-ext2 /sbin/mount.fuse-ext2
+   dh_link -pfuseext2 /usr/bin/fuse-ext2 /usr/sbin/mount.fuse-ext2
# Compatibility symlinks for versions up to 0.3.
dh_link -pfuseext2 /usr/bin/fuse-ext2 /usr/bin/fuseext2
-   dh_link -pfuseext2 /sbin/mount.fuse-ext2 /sbin/mount.fuseext2
+   dh_link -pfuseext2 /usr/sbin/mount.fuse-ext2 /usr/sbin/mount.fuseext2
dh_link -pfuseext2 /usr/share/man/man1/fuse-ext2.1 
/usr/share/man/man1/fuseext2.1
dh_link -pfuseext2 /usr/share/man/man8/mount.fuse-ext2.8 
/usr/share/man/man8/mount.fuseext2.8
dh_compress -pfuseext2

Bug#1064237: netscript-2.4: move aliased files from / to /usr (DEP17)

[Helmut Grohne]

Package: netscript-2.4,netstcript-ipfilter
Version: 5.5.5+nmu1
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to finalize the /usr-merge transition via DEP17 by moving all
aliased files from / to /usr to avoid negative effects arising from
aliasing. netscript-2.4 is involved, because it installs multiple files
in aliased locations. As it uses debhelper for installing systemd units,
those will move automatically on the next upload. Programs and udev
files will not move automatically though and dh-sequence-movetousr does
not just work for netscript-2.4. Therefore, I am sending a patch to
perform the move. Note that this patch must not be uploaded to
bookworm-backports or earlier, because it would violate the file move
moratorium there.

Helmut
diff --minimal -Nru netscript-2.4-5.5.5+nmu1/debian/changelog 
netscript-2.4-5.5.5+nmu2/debian/changelog
--- netscript-2.4-5.5.5+nmu1/debian/changelog   2022-10-15 12:26:24.0 
+0200
+++ netscript-2.4-5.5.5+nmu2/debian/changelog   2024-02-18 12:00:53.0 
+0100
@@ -1,3 +1,10 @@
+netscript-2.4 (5.5.5+nmu2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * DEP17: Move files to /usr. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 18 Feb 2024 12:00:53 +0100
+
 netscript-2.4 (5.5.5+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru netscript-2.4-5.5.5+nmu1/debian/netscript-2.4.links 
netscript-2.4-5.5.5+nmu2/debian/netscript-2.4.links
--- netscript-2.4-5.5.5+nmu1/debian/netscript-2.4.links 2015-01-04 
04:54:23.0 +0100
+++ netscript-2.4-5.5.5+nmu2/debian/netscript-2.4.links 2024-02-18 
12:00:34.0 +0100
@@ -4,5 +4,5 @@
 usr/share/man/man5/netscript-2.4.conf.5.gz 
usr/share/man/man5/ipfilter.conf.5.gz
 usr/share/man/man8/netscript.8.gz usr/share/man/man8/ifup.8.gz
 usr/share/man/man8/netscript.8.gz usr/share/man/man8/ifdown.8.gz
-sbin/netscript sbin/ifup
-sbin/netscript sbin/ifdown
+usr/sbin/netscript usr/sbin/ifup
+usr/sbin/netscript usr/sbin/ifdown
diff --minimal -Nru netscript-2.4-5.5.5+nmu1/debian/rules 
netscript-2.4-5.5.5+nmu2/debian/rules
--- netscript-2.4-5.5.5+nmu1/debian/rules   2018-01-18 10:27:36.0 
+0100
+++ netscript-2.4-5.5.5+nmu2/debian/rules   2024-02-18 12:00:09.0 
+0100
@@ -33,8 +33,8 @@
dh_installdirs
 
# Add here commands to install the package into debian/.
-   $(MAKE) install DESTDIR=`pwd`/debian/netscript-2.4
-   $(MAKE) install-ipfilter DESTDIR=`pwd`/debian/netscript-ipfilter
+   $(MAKE) install DESTDIR=`pwd`/debian/netscript-2.4 
SBINDIR='$$(DESTDIR)/usr/sbin' UDEVLIBDIR='$$(DESTDIR)/usr/lib/udev'
+   $(MAKE) install-ipfilter DESTDIR=`pwd`/debian/netscript-ipfilter 
SBINDIR='$$(DESTDIR)/usr/sbin' UDEVLIBDIR='$$(DESTDIR)/usr/lib/udev'
 
 
 # Build architecture-independent files here.

Bug#1064219: net-snmp: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hi Craig,

On Mon, Feb 19, 2024 at 07:17:08AM +1100, Craig Small wrote:
> Hi Steve,
>   Looks like you missed one:

> dh_installdocs -plibsnmp-perl -ptkmib -plibsnmp-base -plibsnmp40
> dh_installdocs: error: Requested unknown package libsnmp40 via
> -p/--package, expected one of: snmpd snmptrapd snmp libsnmp-base
> libsnmp40t64 libnetsnmptrapd40t64 libsnmp-dev libsnmp-perl tkmib
> dh_installdocs: error: unknown option or error during option parsing; aborting

Uhm.  I'm unclear how this could be, since we do test builds of the packages
(dpkg-buildpackage -b) before filing any bugs.  I'll dig into this.

> On Mon, 19 Feb 2024 at 03:54, Steve Langasek  wrote:
> 
> > Source: net-snmp
> > Version: 5.9.4+dfsg-1
> > Severity: important
> > Tags: patch pending sid trixie
> > User: debian-...@lists.debian.org
> > Usertags: time-t
> >
> > NOTICE: these changes must not be uploaded to unstable yet!
> >
> > Dear maintainer,
> >
> > As part of the 64-bit time_t transition required to support 32-bit
> > architectures in 2038 and beyond
> > (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> > net-snmp as a source package shipping runtime libraries whose ABI
> > either is affected by the change in size of time_t, or could not be
> > analyzed via abi-compliance-checker (and therefore to be on the safe
> > side we assume is affected).
> >
> > To ensure that inconsistent combinations of libraries with their
> > reverse-dependencies are never installed together, it is necessary to
> > have a library transition, which is most easily done by renaming the
> > runtime library package.
> >
> > Since turning on 64-bit time_t is being handled centrally through a change
> > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
> > important that libraries affected by this ABI change all be uploaded close
> > together in time.  Therefore I have prepared a 0-day NMU for net-snmp
> > which will initially be uploaded to experimental if possible, then to
> > unstable after packages have cleared binary NEW.
> >
> > Please find the patch for this NMU attached.
> >
> > If you have any concerns about this patch, please reach out ASAP.  Although
> > this package will be uploaded to experimental immediately, there will be a
> > period of several days before we begin uploads to unstable; so if
> > information
> > becomes available that your package should not be included in the
> > transition,
> > there is time for us to amend the planned uploads.
> >
> >
> >
> > -- System Information:
> > Debian Release: trixie/sid
> >   APT prefers unstable
> >   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
> > 'experimental')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
> > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> > 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)
> >

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)

[Flavio Veloso Soares]

Package: cloud.debian.org
Severity: important
X-Debbugs-Cc: flavi...@magnux.com

Hello,

Bookworm's release notes clearly states that "systemd-resolved was
not, and still is not, the default DNS resolver in Debian"
(https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#systemd-resolved)

However apparently it is the default on the Debian provided AWS AMIs
-- at least that's what I got out-of-box on a few instances I
installed recently from the images in
https://wiki.debian.org/Cloud/AmazonEC2Image/Bookworm for the
us-east-2 and ca-west-1 regions.

Goals here is not to discuss systemd idiosyncrasies, but I've only got
headaches with systemd-resolved/-networkd to the point it's being
easier to install Bullseye and upgrade (no extra systemd-nonsensed
then, everything works).

So I just want to clarify what's the current status quo regarding
systemd-resolved/-networkd in cloud images so I can file bug reports
properly.

p.s.: same for polkitd -- not sure if we need a daemon "intended to be
used by privileged programs offering service to unprivileged programs
often through some form of inter-process communication mechanism"
installed NOT TO SAY RUNNING on a purposedly minimal network server
that virtually can only be acessed via ssh. I'm happy to file a bug
report/wishlist item if necessary.

Thank you,
FVS

Bug#1064234: rust-palette: Fails to build from source

[Jeremy Bícha]

Source: rust-palette
Version: 0.7.4.0+dfsg-2
Severity: serious
Tags: ftbfs

The latest upload of rust-palette fails to build from source due to
build test failures.

https://buildd.debian.org/status/package.php?p=rust-palette

Thank you,
Jeremy Bícha

Bug#1064233: RM: rust-axum-core -- RoM; superseded by rust-axum

[Jeremy Bícha]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Tags: moreinfo
X-Debbugs-Cc: rust-axum-c...@packages.debian.org
Control: affects -1 src:rust-axum-core
Control: block -1 by 1064232

Please remove rust-axum-core from Debian. Its binary package is built
by the rust-axum source package instead.

On behalf of the Debian Rust Maintainers,
Jeremy Bícha

Bug#1064232: rust-axum: Failing autopkgtests

[Jeremy Bícha]

Source: rust-axum
Version: 0.6.20-16
Severity: serious

rust-axum is unable to migrate to Testing because its autopkgtests are failing

https://qa.debian.org/excuses.php?package=rust-axum

Thank you,
Jeremy Bícha

Bug#1064227: ark: Ark cannot open 7z archives.

[cacin]

Source: ark
Version: 4:23.08.1-2
Followup-For: Bug #1064227

duplicate of #1055970, and #1063545 is related

Bug#1064219: net-snmp: NMU diff for 64-bit time_t transition

[Craig Small]

Hi Steve,
  Looks like you missed one:

dh_installdocs -plibsnmp-perl -ptkmib -plibsnmp-base -plibsnmp40
dh_installdocs: error: Requested unknown package libsnmp40 via
-p/--package, expected one of: snmpd snmptrapd snmp libsnmp-base
libsnmp40t64 libnetsnmptrapd40t64 libsnmp-dev libsnmp-perl tkmib
dh_installdocs: error: unknown option or error during option parsing; aborting


On Mon, 19 Feb 2024 at 03:54, Steve Langasek  wrote:

> Source: net-snmp
> Version: 5.9.4+dfsg-1
> Severity: important
> Tags: patch pending sid trixie
> User: debian-...@lists.debian.org
> Usertags: time-t
>
> NOTICE: these changes must not be uploaded to unstable yet!
>
> Dear maintainer,
>
> As part of the 64-bit time_t transition required to support 32-bit
> architectures in 2038 and beyond
> (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> net-snmp as a source package shipping runtime libraries whose ABI
> either is affected by the change in size of time_t, or could not be
> analyzed via abi-compliance-checker (and therefore to be on the safe
> side we assume is affected).
>
> To ensure that inconsistent combinations of libraries with their
> reverse-dependencies are never installed together, it is necessary to
> have a library transition, which is most easily done by renaming the
> runtime library package.
>
> Since turning on 64-bit time_t is being handled centrally through a change
> to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
> important that libraries affected by this ABI change all be uploaded close
> together in time.  Therefore I have prepared a 0-day NMU for net-snmp
> which will initially be uploaded to experimental if possible, then to
> unstable after packages have cleared binary NEW.
>
> Please find the patch for this NMU attached.
>
> If you have any concerns about this patch, please reach out ASAP.  Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if
> information
> becomes available that your package should not be included in the
> transition,
> there is time for us to amend the planned uploads.
>
>
>
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
> 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> 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)
>

Bug#1064231: ogre-1.12: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: ogre-1.12
Version: 1.12.10+dfsg2-3
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
ogre-1.12 as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for ogre-1.12
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru ogre-1.12-1.12.10+dfsg2/debian/changelog 
ogre-1.12-1.12.10+dfsg2/debian/changelog
--- ogre-1.12-1.12.10+dfsg2/debian/changelog2022-09-23 18:44:44.0 
+
+++ ogre-1.12-1.12.10+dfsg2/debian/changelog2024-02-18 18:55:47.0 
+
@@ -1,3 +1,10 @@
+ogre-1.12 (1.12.10+dfsg2-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 18:55:47 +
+
 ogre-1.12 (1.12.10+dfsg2-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru ogre-1.12-1.12.10+dfsg2/debian/control 
ogre-1.12-1.12.10+dfsg2/debian/control
--- ogre-1.12-1.12.10+dfsg2/debian/control  2022-09-23 18:42:10.0 
+
+++ ogre-1.12-1.12.10+dfsg2/debian/control  2024-02-18 18:55:47.0 
+
@@ -39,7 +39,7 @@
 Section: libdevel
 Architecture: any
 Depends: ${misc:Depends},
- libogre1.12.10 (= ${binary:Version})
+ libogre1.12.10t64 (= ${binary:Version})
 Conflicts: libogre-dev, libogre-1.8-dev, libogre-1.9-dev
 Suggests: ogre-1.12-doc
 Description: 3D Object-Oriented Graphics Rendering Engine (development files)
@@ -52,13 +52,14 @@
  .
  This package contains the headers needed to develop with OGRE.
 
-Package: libogre1.12.10
+Package: libogre1.12.10t64
+Provides: ${t64:Provides}
 Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends},
  ${shlibs:Depends}
-Breaks: libogre-1.12 (<<1.12.10+dfsg2-3)
-Replaces: libogre-1.12 (<<1.12.10+dfsg2-3)
+Breaks: libogre1.12.10 (<< ${source:Version}), libogre-1.12 (<<1.12.10+dfsg2-3)
+Replaces: libogre1.12.10, libogre-1.12 (<<1.12.10+dfsg2-3)
 Description: 3D Object-Oriented Graphics Rendering Engine (libraries)
  OGRE (Object-Oriented Graphics Rendering Engine) is a scene-oriented, flexible
  3D engine written in C++ designed to make it easier and more intuitive for
diff -Nru ogre-1.12-1.12.10+dfsg2/debian/libogre1.12.10t64.lintian-overrides 
ogre-1.12-1.12.10+dfsg2/debian/libogre1.12.10t64.lintian-overrides
--- ogre-1.12-1.12.10+dfsg2/debian/libogre1.12.10t64.lintian-overrides  
1970-01-01 00:00:00.0 +
+++ ogre-1.12-1.12.10+dfsg2/debian/libogre1.12.10t64.lintian-overrides  
2024-02-18 18:55:47.0 +
@@ -0,0 +1 @@
+libogre1.12.10t64: package-name-doesnt-match-sonames libogre1.12.10

Bug#1064230: dutch: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: dutch
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1064213: incus-agent: Incus Agent never starts due to ConditionPathExists

[stefanor]

Hi Mathias (2024.02.18_19:43:13_+)
>   I suspect you're seeing this on the host system running Incus? If so,
> that's expected behavior.

Nope, in a VM inside Incus.

>   Incus' default mode of operation when launching a VM is to
> dynamically inject the `incus-agent` binary into the VM's environment.

It does that if incus-agent-setup is in the image. This was an image
without incus-agent-setup, just your incus-agent package.

If the intention isn't to use the incus-agent package inside VMs, this
should be declared more clearly.

>   This setup covers the vast majority of regular Incus use. But,
> because there is an incus-agent package we also need to support someone
> creating a VM image that bakes in that package. Thus, there's a service
> definition in the incus-agent package. The ConditionPathExists check
> should ever only be true within a VM running under Incus.

That's was my use-case here, and it doesn't work, due to a race.

I've convinced myself that this isn't really the best way to go. And
instead of installing incus-agent in my images, I need the
incus-agent-setup unit that installs the agent over 9p.
Getting incus-agent from the host is likely to be much more reliable,
because the Incus upstream isn't expecting to have to support ancient
agents.

>   I've just verified that both use cases appear to work properly, so
> I've downgraded the bug's severity to normal.

Use a bare image without incus-agent-setup to reproduce the bug.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1064229: firmware-nonfree: CVE-2023-35061 CVE-2023-34983 CVE-2023-33875 CVE-2023-32651 CVE-2023-32644 CVE-2023-32642 CVE-2023-28720 CVE-2023-28374 CVE-2023-26586 CVE-2023-25951

[Salvatore Bonaccorso]

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

Hi,

The following vulnerabilities were published for firmware-nonfree.

They are addressed in the linux-firmware/20231211 upstream version.

CVE-2023-35061[0]:
| Improper initialization for some Intel(R) PROSet/Wireless and
| Intel(R) Killer(TM) Wi-Fi software before version 22.240 may allow
| an unauthenticated user to potentially enable information disclosure
| via adjacent access.


CVE-2023-34983[1]:
| Improper input validation for some Intel(R) PROSet/Wireless and
| Intel(R) Killer(TM) Wi-Fi software before version 22.240 may allow
| an unauthenticated user to potentially enable denial of service via
| adjacent access.


CVE-2023-33875[2]:
| Improper access control for some Intel(R) PROSet/Wireless and
| Intel(R) Killer(TM) Wi-Fi software before version 22.240 may allow
| an unauthenticated user to potentially enable denial of service via
| local access..


CVE-2023-32651[3]:
| Improper validation of specified type of input for some Intel(R)
| PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software before
| version 22.240 may allow an unauthenticated user to potentially
| enable denial of service via adjacent access.


CVE-2023-32644[4]:
| Protection mechanism failure for some Intel(R) PROSet/Wireless and
| Intel(R) Killer(TM) Wi-Fi software before version 22.240 may allow
| an unauthenticated user to potentially enable denial of service via
| adjacent access.


CVE-2023-32642[5]:
| Insufficient adherence to expected conventions for some Intel(R)
| PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software before
| version 22.240 may allow an unauthenticated user to potentially
| enable denial of service via adjacent access.


CVE-2023-28720[6]:
| Improper initialization for some Intel(R) PROSet/Wireless and
| Intel(R) Killer(TM) Wi-Fi software before version 22.240 may allow
| an unauthenticated user to potentially enable denial of service via
| adjacent access..


CVE-2023-28374[7]:
| Improper input validation for some Intel(R) PROSet/Wireless and
| Intel(R) Killer(TM) Wi-Fi software before version 22.240 may allow
| an unauthenticated user to potentially enable denial of service via
| adjacent access.


CVE-2023-26586[8]:
| Uncaught exception for some Intel(R) PROSet/Wireless and Intel(R)
| Killer(TM) Wi-Fi software before version 22.240 may allow an
| unauthenticated user to potentially enable denial of service via
| adjacent access.


CVE-2023-25951[9]:
| Improper input validation for some Intel(R) PROSet/Wireless and
| Intel(R) Killer(TM) Wi-Fi software before version 22.240 may allow a
| privileged user to potentially enable escalation of privilege via
| local access.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-35061
https://www.cve.org/CVERecord?id=CVE-2023-35061
[1] https://security-tracker.debian.org/tracker/CVE-2023-34983
https://www.cve.org/CVERecord?id=CVE-2023-34983
[2] https://security-tracker.debian.org/tracker/CVE-2023-33875
https://www.cve.org/CVERecord?id=CVE-2023-33875
[3] https://security-tracker.debian.org/tracker/CVE-2023-32651
https://www.cve.org/CVERecord?id=CVE-2023-32651
[4] https://security-tracker.debian.org/tracker/CVE-2023-32644
https://www.cve.org/CVERecord?id=CVE-2023-32644
[5] https://security-tracker.debian.org/tracker/CVE-2023-32642
https://www.cve.org/CVERecord?id=CVE-2023-32642
[6] https://security-tracker.debian.org/tracker/CVE-2023-28720
https://www.cve.org/CVERecord?id=CVE-2023-28720
[7] https://security-tracker.debian.org/tracker/CVE-2023-28374
https://www.cve.org/CVERecord?id=CVE-2023-28374
[8] https://security-tracker.debian.org/tracker/CVE-2023-26586
https://www.cve.org/CVERecord?id=CVE-2023-26586
[9] https://security-tracker.debian.org/tracker/CVE-2023-25951
https://www.cve.org/CVERecord?id=CVE-2023-25951

Regards,
Salvatore

Bug#1043152: dsh: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru dsh-0.25.10/ChangeLog.OLD dsh-0.25.10/ChangeLog.OLD
--- dsh-0.25.10/ChangeLog.OLD   2024-02-18 19:38:59.0 +
+++ dsh-0.25.10/ChangeLog.OLD   1970-01-01 00:00:00.0 +
@@ -1,17 +0,0 @@
-2001-05-14  Junichi Uekawa  
-
-   * dsh.1: added documentation for homedir configs.
-
-   * dsh.c (parse_options): added support for machines config.
-   (read_machinelist): The machines list support.
-   (parse_options): Configs in homedir too.
-
-2001-05-13  Junichi Uekawa  
-
-   * dsh.1: Created a manpage
-
-   * Makefile: Copied from other project. 
-
-   * dsh.c: Created / started, by
-   dancer@{debian.org,netfort.gr.jp,mikilab.doshisha.ac.jp} 
-
diff -Nru dsh-0.25.10/configure dsh-0.25.10/configure
--- dsh-0.25.10/configure   2024-02-18 19:38:59.0 +
+++ dsh-0.25.10/configure   2007-12-14 00:01:05.0 +
@@ -21245,7 +21245,7 @@
 fi
 
 
-ALL_LINGUAS="de ja"
+ALL_LINGUAS=ja
 
 MKINSTALLDIRS=
   if test -n "$ac_aux_dir"; then
diff -Nru dsh-0.25.10/configure.ac dsh-0.25.10/configure.ac
--- dsh-0.25.10/configure.ac2024-02-18 19:38:59.0 +
+++ dsh-0.25.10/configure.ac2007-12-14 00:00:49.0 +
@@ -17,7 +17,7 @@
 AM_PROG_LIBTOOL
 AC_C_CONST
 
-ALL_LINGUAS="de ja"
+ALL_LINGUAS=ja
 AM_GNU_GETTEXT([external])
 AC_CHECK_FUNC(gettext,,AC_CHECK_LIB(intl,gettext,,AC_MSG_WARN([Gettext not 
found])))
 localedir='${datadir}/locale'
diff -Nru dsh-0.25.10/dcp.sh dsh-0.25.10/dcp.sh
--- dsh-0.25.10/dcp.sh  2024-02-18 19:38:59.0 +
+++ dsh-0.25.10/dcp.sh  1970-01-01 00:00:00.0 +
@@ -1,6 +0,0 @@
-#! /bin/sh
-# script to distributedly copy files.
-
-PWD=`pwd`
-
-cat ${tempfile} | @bindir@/dsh "$@" -ic "test -x @libexecdir@/dcpd && ( cd 
${PWD}; cat > .tmp.f ;  tar xfz tmp.f; true) || @libexecdir@/dcpd ${PWD} 0"
\ No newline at end of file
diff -Nru dsh-0.25.10/debian/ChangeLog.OLD dsh-0.25.10/debian/ChangeLog.OLD
--- dsh-0.25.10/debian/ChangeLog.OLD1970-01-01 00:00:00.0 +
+++ dsh-0.25.10/debian/ChangeLog.OLD2024-02-18 18:55:04.0 +
@@ -0,0 +1,17 @@
+2001-05-14  Junichi Uekawa  
+
+   * dsh.1: added documentation for homedir configs.
+
+   * dsh.c (parse_options): added support for machines config.
+   (read_machinelist): The machines list support.
+   (parse_options): Configs in homedir too.
+
+2001-05-13  Junichi Uekawa  
+
+   * dsh.1: Created a manpage
+
+   * Makefile: Copied from other project. 
+
+   * dsh.c: Created / started, by
+   dancer@{debian.org,netfort.gr.jp,mikilab.doshisha.ac.jp} 
+
diff -Nru dsh-0.25.10/debian/README.Debian dsh-0.25.10/debian/README.Debian
--- dsh-0.25.10/debian/README.Debian2024-02-18 19:38:59.0 +
+++ dsh-0.25.10/debian/README.Debian2024-02-18 18:55:04.0 +
@@ -14,13 +14,6 @@
 the libc, through the NSS, i.e. it is possible to use NIS information
 in dsh.
 
-
-The author has a home page at 
-  http://www.netfort.gr.jp/~dancer/
-and the primary page for dsh is at 
-  http://www.netfort.gr.jp/~dancer/software/dsh.html
-
-
 enjoy.
 
  -- Junichi Uekawa , Tue Oct 15 22:52:28 2002
diff -Nru dsh-0.25.10/debian/changelog dsh-0.25.10/debian/changelog
--- dsh-0.25.10/debian/changelog2024-02-18 19:38:59.0 +
+++ dsh-0.25.10/debian/changelog2024-02-18 18:55:04.0 +
@@ -1,3 +1,21 @@
+dsh (0.25.10-1.6) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. (Closes: #1043152)
+  * d/copyright: Convert to machine-readable format.
+  * Record the homepage in the appropriate place.
+  * d/rules: Let build-stamp depend on configure-stamp. (Closes: #866363)
+  * Drop non-existing Suggest. (Closes: #921441)
+  * Replace old debhelper commands. (Closes: #1044630)
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: (Closes: #869478)
++ Let dh_auto_configure pass cross compilers to ./configure.
++ Let dh_auto_test honour DEB_BUILD_OPTIONS=nocheck.
++ Do not strip at install time, let dh_strip do it.
+
+ -- Bastian Germann   Sun, 18 Feb 2024 18:55:04 +
+
 dsh (0.25.10-1.5) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dsh-0.25.10/debian/control dsh-0.25.10/debian/control
--- dsh-0.25.10/debian/control  2024-02-18 19:38:59.0 +
+++ dsh-0.25.10/debian/control  2024-02-18 18:55:04.0 +
@@ -4,11 +4,11 @@
 Maintainer: Junichi Uekawa 
 Build-Depends: debhelper (>= 9), libdshconfig1-dev (>= 0.20.11-1), po4a, 
autotools-dev
 Standards-Version: 3.7.2
+Homepage: http://www.netfort.gr.jp/~dancer/software/dsh.html
 
 Package: dsh
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Suggests: update-cluster
 Description: dancer's shell, or distributed shell
  Executes specified command on a group of computers using remote shell
  methods such as rsh or ssh. 
@@ -20,6 +20,3 @@
  remote hosts.
  

Bug#1064213: incus-agent: Incus Agent never starts due to ConditionPathExists

[Mathias Gibbens]

Control: severity -1 normal

Hi Stefano,

  I suspect you're seeing this on the host system running Incus? If so,
that's expected behavior.

  Incus' default mode of operation when launching a VM is to
dynamically inject the `incus-agent` binary into the VM's environment.
(`incus-agent` should never actually run on the host itself.) To
accomplish this, it must copy the binary from the host system in
addition to automatically creating other config and service files for
the VM. Debian's packaging breaks out the `incus-agent` binary into its
own package that is Recommended, but not required if you're only
running containers.

  This setup covers the vast majority of regular Incus use. But,
because there is an incus-agent package we also need to support someone
creating a VM image that bakes in that package. Thus, there's a service
definition in the incus-agent package. The ConditionPathExists check
should ever only be true within a VM running under Incus.

  I've just verified that both use cases appear to work properly, so
I've downgraded the bug's severity to normal.

  If you know of a better way of making the systemd service not start
on the host machine, please let me know. Or if there might be some way
to make it more readily apparent that it's expected and normal
behavior.

Mathias


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

Bug#1063524: brltty: move aliased files to /usr (DEP17)

[Samuel Thibault]

Helmut Grohne, le dim. 18 févr. 2024 07:45:17 +0100, a ecrit:
> > > diff --minimal -Nru brltty-6.6/debian/brltty-udeb.dirs 
> > > brltty-6.6/debian/brltty-udeb.dirs
> > > --- brltty-6.6/debian/brltty-udeb.dirs2021-01-28 17:18:34.0 
> > > +0100
> > > +++ brltty-6.6/debian/brltty-udeb.dirs2024-02-08 17:59:12.0 
> > > +0100
> > > @@ -1,7 +1,7 @@
> > > -lib/debian-installer.d
> > > -lib/debian-installer-startup.d
> > > +usr/lib/debian-installer.d
> > > +usr/lib/debian-installer-startup.d
> > 
> > These are not currently read by the debian installer, so we mustn't move
> > these files for now.
> 
> I have moved such files elsewhere, so if this really causes problems
> still, I'd like to learn soon and handle it.

I have now tested it completely, it seems to be going fine indeed.

Samuel

Bug#1064228: lincity-ng: the install phase is rebuilding everything

[Alexandre Detiste]

Package: lincity-ng
Version: 2.9.0-1
Severity: normal

It looks like that 'jam install' is rebuilding everything _again_,
& this time in a non-verbose way that makes BLHC complains on Salsa.

This does not seems to affect end result.



This bug is similar to #1042506 for "ares".


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

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

Versions of packages lincity-ng depends on:
ii  libc62.37-15
ii  libgcc-s114-20240201-3
ii  libgl1   1.7.0-1
ii  libphysfs1   3.0.2-6
ii  libsdl2-2.0-02.30.0+dfsg-1
ii  libsdl2-gfx-1.0-01.0.4+dfsg-5
ii  libsdl2-image-2.0-0  2.8.2+dfsg-1
ii  libsdl2-mixer-2.0-0  2.8.0+dfsg-1
ii  libsdl2-ttf-2.0-02.22.0+dfsg-1
ii  libstdc++6   14-20240201-3
ii  libxml2  2.9.14+dfsg-1.3+b2
ii  lincity-ng-data  2.9.0-1
ii  zlib1g   1:1.3.dfsg-3+b1

lincity-ng recommends no packages.

lincity-ng suggests no packages.

-- no debconf information

Bug#1055036: crmsh 4.4.1-1+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: crmsh
Version: 4.4.1-1+deb12u1

Explanation: create log directory and file on installation

Bug#1064227: ark: Ark cannot open 7z archives.

[Holmes]

Package: ark
Version: 4:23.08.1-2
Severity: important
X-Debbugs-Cc: 3a58f101-de75-4b85-b8fe-127896854...@simplelogin.com

Dear Maintainer,

Ark is unable to open 7z archives. It says "The archive is empty or Ark cannot
open the content." It can compress files to 7z without any issues however.
Opening the same archive with another archive explorer shows the packed files.
The bug happens on both password encrypted 7z archives and unencrypted 7z
archives.


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

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

Versions of packages ark depends on:
ii  kinit  5.107.0-1
ii  kio5.107.0-1+b1
ii  libarchive13   3.7.2-1
ii  libc6  2.37-15
ii  libgcc-s1  14-20240201-3
ii  libkf5completion5  5.107.0-1+b1
ii  libkf5configcore5  5.107.0-1+b1
ii  libkf5configgui5   5.107.0-1+b1
ii  libkf5configwidgets5   5.107.0-2+b1
ii  libkf5coreaddons5  5.107.0-1+b1
ii  libkf5crash5   5.107.0-1+b1
ii  libkf5dbusaddons5  5.107.0-1+b1
ii  libkf5i18n55.107.0-1+b1
ii  libkf5jobwidgets5  5.107.0-1+b1
ii  libkf5kiocore5 5.107.0-1+b1
ii  libkf5kiofilewidgets5  5.107.0-1+b1
ii  libkf5kiogui5  5.107.0-1+b1
ii  libkf5kiowidgets5  5.107.0-1+b1
ii  libkf5parts5   5.107.0-1+b1
ii  libkf5pty5 5.107.0-1+b1
ii  libkf5service-bin  5.107.0-1+b1
ii  libkf5service5 5.107.0-1+b1
ii  libkf5widgetsaddons5   5.107.0-1+b1
ii  libkf5windowsystem55.107.0-1+b1
ii  libkf5xmlgui5  5.107.0-1+b1
ii  libqt5core5a   5.15.10+dfsg-7
ii  libqt5dbus55.15.10+dfsg-7
ii  libqt5gui5 5.15.10+dfsg-7
ii  libqt5widgets5 5.15.10+dfsg-7
ii  libstdc++6 14-20240201-3
ii  libzip41.7.3-1+b1
ii  zlib1g 1:1.3.dfsg-3+b1

Versions of packages ark recommends:
ii  7zip [p7zip-full]  23.01+dfsg-8
ii  bzip2  1.0.8-5+b2
ii  p7zip-full 16.02+transitional.1
ii  unar   1.10.7+ds1+really1.10.1-2+b3
ii  unzip  6.0-28
ii  zip3.0-13

Versions of packages ark suggests:
pn  rar 
pn  unrar | unrar-free  

-- no debconf information

Bug#1063524: brltty: move aliased files to /usr (DEP17)

[Samuel Thibault]

Helmut Grohne, le dim. 18 févr. 2024 07:45:17 +0100, a ecrit:
> > > diff --minimal -Nru brltty-6.6/debian/brltty-udeb.dirs 
> > > brltty-6.6/debian/brltty-udeb.dirs
> > > --- brltty-6.6/debian/brltty-udeb.dirs2021-01-28 17:18:34.0 
> > > +0100
> > > +++ brltty-6.6/debian/brltty-udeb.dirs2024-02-08 17:59:12.0 
> > > +0100
> > > @@ -1,7 +1,7 @@
> > > -lib/debian-installer.d
> > > -lib/debian-installer-startup.d
> > > +usr/lib/debian-installer.d
> > > +usr/lib/debian-installer-startup.d
> > 
> > These are not currently read by the debian installer, so we mustn't move
> > these files for now.
> 
> Keep in mind that the installer has been /usr-merged.

Oh, it has? I didn't know that.

Samuel

Bug#1064226: RFS: dia/0.98+git20240130-1 -- Diagram editor

[Philippe SWARTVAGHER]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name : dia
Version : 0.98+git20240130-1
Upstream contact : Zander Brown 
* URL : https://wiki.gnome.org/Apps/Dia/
* License : GPL-2+, GPL-2, GFDL-NIV-1.1+
* Vcs : https://salsa.debian.org/debian/dia
Section : graphics

The source builds the following binary packages:

dia-common - Diagram editor (common files)
dia - Diagram editor

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

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

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

dget -x
https://mentors.debian.net/debian/pool/main/d/dia/dia_0.98+git20240130-1.dsc

Changes since the last upload:

dia (0.98+git20240130-1) unstable; urgency=medium
.
* New upstream snapshot
- Closes: #1024834, #1025239, #1020531
- Drop poppler*.patch: applied upstream
- Adapt fix-libdia-install-dir.patch
- control: add libpoppler-cpp-dev to Build-Depends
- control: adapt to use GTK3 instead of GTK2 Closes: #967312
* rules: remove --no-parallel option
* rules: add FORCE_SOURCE_DATE=1 to have reproducible PDF
* copyright: update copyright year

Regards,

Philippe.

Bug#1064225: linux-headers-6.6.15-686-pae: dkms autoinstall on 6.6.15-686-pae/i686 failed for virtualbox

[Nicolas Patrois]

Package: linux-headers-6.6.15-686-pae
Version: 6.6.15-2
Severity: normal

Dear Maintainer,

dkms can’t build virtualbox, but acpi-call nvidia-legacy-390xx openrazer-driver
are OK.
Here are the logs from /var/lib/dkms/virtualbox/6.0.14/build/make.log:

DKMS make.log for virtualbox-6.0.14 for kernel 6.6.15-686-pae (i686)
dim. 18 févr. 2024 19:43:38 CET
make : on entre dans le répertoire « /usr/src/linux-headers-6.6.15-686-pae »
  CC [M]  /var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/SUPDrvGip.o
In file included from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/iprt/types.h:34,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/VBox/types.h:33,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/linux/../SUPDrvInternal.h:38,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/iprt/stdarg.h:47:12:
fatal error: stdarg.h: Aucun fichier ou dossier de ce type
   47 | #  include 
  |^~
compilation terminated.
make[3]: *** [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.build:248 :
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/linux/SUPDrv-linux.o] Erreur 1
make[3]: *** Attente des tâches non terminées
In file included from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/iprt/types.h:34,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/VBox/types.h:33,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/SUPDrvInternal.h:38,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/SUPDrv.c:33:
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/iprt/stdarg.h:47:12:
fatal error: stdarg.h: Aucun fichier ou dossier de ce type
   47 | #  include 
  |^~
compilation terminated.
make[3]: *** [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.build:248 :
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/SUPDrv.o] Erreur 1
In file included from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/iprt/types.h:34,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/VBox/types.h:33,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/SUPDrvInternal.h:38,
 from
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/SUPDrvGip.c:33:
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/include/iprt/stdarg.h:47:12:
fatal error: stdarg.h: Aucun fichier ou dossier de ce type
   47 | #  include 
  |^~
compilation terminated.
make[3]: *** [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.build:248 :
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv/SUPDrvGip.o] Erreur 1
make[2]: *** [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.build:485 :
/var/lib/dkms/virtualbox/6.0.14/build/vboxdrv] Erreur 2
make[1]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:1938 :
/var/lib/dkms/virtualbox/6.0.14/build] Erreur 2
make: *** [/usr/src/linux-headers-6.6.15-common/Makefile:246 : __sub-make]
Erreur 2
make : on quitte le répertoire « /usr/src/linux-headers-6.6.15-686-pae »

Yours,
n.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.16.0-6-686-pae (SMP w/3 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-headers-6.6.15-686-pae depends on:
ii  gcc-13   13.2.0-13
ii  linux-headers-6.6.15-common  6.6.15-2
ii  linux-image-6.6.15-686-pae   6.6.15-2
ii  linux-kbuild-6.6.15  6.6.15-2

linux-headers-6.6.15-686-pae recommends no packages.

linux-headers-6.6.15-686-pae suggests no packages.

-- no debconf information

Bug#1064224: python-hmmlearn: fails variational gaussian tests with sklearn 1.4

[Drew Parsons]

Source: python-hmmlearn
Version: 0.3.0-3
Severity: serious
Justification: debci

python-hmmlearn is failing variational_gaussian tests
(test_fit_mcgrory_titterington1d) with sklearn 1.4.

This comment upstream is relevant:
https://github.com/hmmlearn/hmmlearn/issues/539#issuecomment-1871436258

It's likely fixed in upstream PR#531
https://github.com/hmmlearn/hmmlearn/pull/531

If not, then I'd suggest skipping test_fit_mcgrory_titterington1d
until there's a better fix upstream.

PR#545 might also be generally helpful.

Bug#1043092: dictem: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru dictem-1.0.4/TODO dictem-1.0.4/TODO
--- dictem-1.0.4/TODO   2024-02-18 18:30:30.0 +
+++ dictem-1.0.4/TODO   2016-09-03 06:29:36.0 +
@@ -1 +1,6 @@
+- "er" dictionary + geek
+- antonym for "l". "n" and "p"?
+- keep p/n history in buffers with numbers.
+- does dictem-use-existing-buffer work properly?
+
 Do you have ideas, want new features, see bugs? Let me know ;-)
diff -Nru dictem-1.0.4/debian/changelog dictem-1.0.4/debian/changelog
--- dictem-1.0.4/debian/changelog   2024-02-18 18:30:30.0 +
+++ dictem-1.0.4/debian/changelog   2024-02-18 18:23:58.0 +
@@ -1,3 +1,12 @@
+dictem (1.0.4-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. Closes: #1043092
+  * d/copyright: Convert to machine-readable format.
+  * Remove trailing empty line from description.
+
+ -- Bastian Germann   Sun, 18 Feb 2024 18:23:58 +
+
 dictem (1.0.4-4.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru dictem-1.0.4/debian/control dictem-1.0.4/debian/control
--- dictem-1.0.4/debian/control 2024-02-18 18:30:30.0 +
+++ dictem-1.0.4/debian/control 2024-02-18 18:23:58.0 +
@@ -21,5 +21,3 @@
  It uses autocompletion that is used for selecting dictionary and 
  search strategy.  Moreover, DictEm provides several hooks which 
  may be used for buffer postprocessing.
- .
-
diff -Nru dictem-1.0.4/debian/copyright dictem-1.0.4/debian/copyright
--- dictem-1.0.4/debian/copyright   2024-02-18 18:30:30.0 +
+++ dictem-1.0.4/debian/copyright   2024-02-18 18:23:58.0 +
@@ -1,27 +1,29 @@
-This package was debianized by Zhenja Kaluta  on
-Fri, 24 Sep 2004 12:38:21 +0300.
-
-Downloaded From: http://www.mova.org/~cheusov/pub/dictem/
-
-Upstream Author: Aleksey Cheusov 
-
-Copyright (c) 2003, 2004 Aleksey Cheusov 
-
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This package was debianized by Zhenja Kaluta  on
+ Fri, 24 Sep 2004 12:38:21 +0300.
+Source:
+ http://www.mova.org/~cheusov/pub/dictem/
+Upstream-Contact:
+ Aleksey Cheusov 
+
+Files: *
+Copyright: (c) 2003, 2004 Aleksey Cheusov 
+License: GPL-2+
DictEm is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
-
+ .
DictEm is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.
-
+ .
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, 
USA
-
-On Debian systems, the complete text of the GNU General
-Public License can be found in `/usr/share/common-licenses/GPL-2'.
-
+Comment:
+ On Debian systems, the complete text of the GNU General
+ Public License can be found in `/usr/share/common-licenses/GPL-2'.
diff -Nru dictem-1.0.4/debian/patches/debian.patch 
dictem-1.0.4/debian/patches/debian.patch
--- dictem-1.0.4/debian/patches/debian.patch1970-01-01 00:00:00.0 
+
+++ dictem-1.0.4/debian/patches/debian.patch2024-02-18 18:23:58.0 
+
@@ -0,0 +1,462 @@
+--- dictem-1.0.4.orig/TODO
 dictem-1.0.4/TODO
+@@ -1,6 +1 @@
+-- "er" dictionary + geek
+-- antonym for "l". "n" and "p"?
+-- keep p/n history in buffers with numbers.
+-- does dictem-use-existing-buffer work properly?
+-
+ Do you have ideas, want new features, see bugs? Let me know ;-)
+--- dictem-1.0.4.orig/dictem.el
 dictem-1.0.4/dictem.el
+@@ -476,62 +476,82 @@ This variable is local to buffer")
+ (defun dictem-local-dict-basic-option (host port option-mime)
+   (let ((server-host (if host host (dictem-get-server
+ (append
+- (list "-P" "-")
++ (list "-P" "-" 
++ "--client" (dictem-client-text))
+  (if server-host
+(list "-h" server-host "-p" (dictem-get-port port)))
+  (if option-mime '("-M"))
+  dictem-client-prog-args-list
+  )))
+ 
+-(defun dictem-call-process (buffer host port args)
+-  (let (coding-system
+-  coding-system-for-read
+-  coding-system-for-write)
+-(if (and (functionp 'coding-system-list)
+-   (member 'utf-8 (coding-system-list)))
+-  (setq coding-system 'utf-8))
+-(setq coding-system-for-read coding-system)
+-(setq coding-system-for-write coding-system)
+-(apply 'call-process
+- `(,dictem-client-prog
+-   nil
+-   ,(dictem-get-buffer buffer)
+-   nil
+-   ,@(dictem-local-dict-basic-option host port nil)
+-   ,@args
+-   

Bug#1064223: imbalanced-learn: fails tests with sklearn 1.4: needs new versions

[Drew Parsons]

Source: imbalanced-learn
Version: 0.10.0-2
Severity: serious
Justification: debci

imbalanced-learn 0.10 fails tests with sklearn 1.4.

The problem is fixed upstrema with v0.12.

Bug#1064222: nut: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: nut
Version: 2.8.1-3
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
nut as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for nut
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru nut-2.8.1/debian/changelog nut-2.8.1/debian/changelog
--- nut-2.8.1/debian/changelog  2024-01-11 16:01:16.0 +
+++ nut-2.8.1/debian/changelog  2024-02-18 18:01:27.0 +
@@ -1,3 +1,10 @@
+nut (2.8.1-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 18:01:27 +
+
 nut (2.8.1-3) unstable; urgency=medium
 
   * debian/control: Add missing Breaks/Replaces on nut-modbus (Closes:
diff -Nru nut-2.8.1/debian/control nut-2.8.1/debian/control
--- nut-2.8.1/debian/control2024-01-11 16:01:16.0 +
+++ nut-2.8.1/debian/control2024-02-18 18:01:27.0 +
@@ -200,7 +200,10 @@
  .
  This package contains FAQ, user, developer and packager documentation.
 
-Package: libupsclient6
+Package: libupsclient6t64
+Provides: ${t64:Provides}
+Replaces: libupsclient6
+Breaks: libupsclient6 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -219,7 +222,7 @@
 Section: libdevel
 Architecture: any
 Depends: libnss3-dev,
- libupsclient6 (= ${binary:Version}),
+ libupsclient6t64 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
 Multi-Arch: same
@@ -232,7 +235,10 @@
  .
  This package provides the development files.
 
-Package: libnutclient2
+Package: libnutclient2t64
+Provides: ${t64:Provides}
+Replaces: libnutclient2
+Breaks: libnutclient2 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -250,7 +256,7 @@
 Package: libnutclient-dev
 Section: libdevel
 Architecture: any
-Depends: libnutclient2 (= ${binary:Version}),
+Depends: libnutclient2t64 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
 Multi-Arch: same
@@ -263,7 +269,10 @@
  .
  This package provides the development files for the new client library.
 
-Package: libnutscan2
+Package: libnutscan2t64
+Provides: ${t64:Provides}
+Replaces: libnutscan2
+Breaks: libnutscan2 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -281,7 +290,7 @@
 Package: libnutscan-dev
 Section: libdevel
 Architecture: any
-Depends: libnutscan2 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: libnutscan2t64 (= ${binary:Version}), ${misc:Depends}, 
${shlibs:Depends}
 Breaks: libupsclient-dev (<< 2.7.4-9~)
 Replaces: libupsclient-dev (<< 2.7.4-9~)
 Multi-Arch: same
diff -Nru nut-2.8.1/debian/libnutclient2.install 
nut-2.8.1/debian/libnutclient2.install
--- nut-2.8.1/debian/libnutclient2.install  2024-01-11 16:01:16.0 
+
+++ nut-2.8.1/debian/libnutclient2.install  1970-01-01 00:00:00.0 
+
@@ -1,2 +0,0 @@
-lib/*/libnutclient.so.*
-lib/*/libnutclientstub.so.*
diff -Nru nut-2.8.1/debian/libnutcli

Bug#1064221: nodejs: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: nodejs
Version: 18.19.0+dfsg-6
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
nodejs as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for nodejs
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru nodejs-18.19.0+dfsg/debian/changelog 
nodejs-18.19.0+dfsg/debian/changelog
--- nodejs-18.19.0+dfsg/debian/changelog2023-12-03 21:41:14.0 
+
+++ nodejs-18.19.0+dfsg/debian/changelog2024-02-18 16:49:53.0 
+
@@ -1,3 +1,10 @@
+nodejs (18.19.0+dfsg-6.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 16:49:53 +
+
 nodejs (18.19.0+dfsg-6) unstable; urgency=medium
 
   * patch: remove useless and badly done icu_74 patch
diff -Nru nodejs-18.19.0+dfsg/debian/control nodejs-18.19.0+dfsg/debian/control
--- nodejs-18.19.0+dfsg/debian/control  2023-11-30 08:54:40.0 +
+++ nodejs-18.19.0+dfsg/debian/control  2024-02-18 16:49:52.0 +
@@ -55,7 +55,7 @@
 Depends: ${misc:Depends},
  libssl-dev (>= 1.1.1~),
  libuv1-dev (>= 1.33.0~),
- libnode108 (= ${binary:Version})
+ libnode108t64 (= ${binary:Version})
 Breaks: nodejs-dev (<< 10.0.0~dfsg1-3)
 Replaces: libv8-dev,
  nodejs-dev (<< 10.0.0~dfsg1-3)
@@ -68,7 +68,7 @@
  efficient, perfect for data-intensive real-time applications that run
  across distributed devices.
  .
- This package provides development headers for libnode108
+ This package provides development headers for libnode108t64
 
 Package: nodejs
 Architecture: amd64 arm64 armel armhf i386 kfreebsd-i386 kfreebsd-amd64 mips 
mips64el mips64r6el mipsel powerpc ppc64 ppc64el riscv64 s390x
@@ -78,7 +78,7 @@
  ${misc:Depends},
  sse2-support [i386],
  armv6k-support [armel], vfpv2-support [armel],
- libnode108 (= ${binary:Version})
+ libnode108t64 (= ${binary:Version})
 Recommends: ca-certificates,
  nodejs-doc
 Suggests: npm
@@ -105,7 +105,8 @@
  System, Events, Standard I/O, Modules, Timers, Child Processes, POSIX,
  HTTP, Multipart Parsing, TCP, DNS, Assert, Path, URL, Query Strings.
 
-Package: libnode108
+Package: libnode108t64
+Provides: ${t64:Provides}
 Section: libs
 Architecture: amd64 arm64 armel armhf i386 kfreebsd-i386 kfreebsd-amd64 mips 
mips64el mips64r6el mipsel powerpc ppc64 ppc64el riscv64 s390x
 Multi-Arch: same
@@ -116,10 +117,10 @@
  node-acorn (>= 6.2.1~) ,
  node-cjs-module-lexer (>= 1.2.2~) ,
  node-undici (>= 5.0.0~) 
-Breaks: node-modern-syslog (<< 1.1.4-2),
+Breaks: libnode108 (<< ${source:Version}), node-modern-syslog (<< 1.1.4-2),
  libnode64 (<< 10.24.1~),
  libnode72 (<< 13)
-Replaces: nodejs-legacy, libnode72, libnode83, libnode93
+Replaces: libnode108, nodejs-legacy, libnode72, libnode83, libnode93
 Conflicts: nodejs-legacy
 Description: evented I/O for V8 javascript - runtime library
  Node.js is a platform built on Chrome's JavaScript runtime for easily
diff -Nru nodejs-18.19.0+dfsg/debian/libnode108t64.lintian-overrides 
nodejs-18.19.0+dfsg/debian/libnode108t64.lintian-overrides
--- nodejs-18.19.0+dfsg/debian/libnod

Bug#1062798: src:mumble: fails to migrate to testing for too long: autopkgtest failure

[Diederik de Haas]

On Sat, 3 Feb 2024 11:52:03 +0100 Paul Gevers  wrote:
> Source: mumble
> Version: 1.3.4-4
> Severity: serious
> Control: close -1 1.5.517-1
> Tags: sid trixie
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
> 
> Dear maintainer(s),
> 
> The Release Team considers packages that are out-of-sync between testing 
> and unstable for more than 30 days as having a Release Critical bug in 
> testing [1]. Your package src:mumble has been trying to migrate for 31 
> days [2]. Hence, I am filing this bug. The version in unstable fails its 
> own autopkgtest (thanks for adding one, it seems to just be missing a 
> test dependency). Please also annotate the test with the "superficial" 
> restriction as the name suggest you are not testing the package to great 
> extend. Please also help poco migrate, the package (build) depends on it.
> 
> [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
> [2] https://qa.debian.org/excuses.php?package=mumble

In https://bugs.debian.org/1063711 I added a "X-Debbugs-Cc" to this bug, but 
apparently that doesn't make it turn up in this bug.

In bug #1063711 I added some patches which made the autopkgtest succeed on my 
Salsa CI pipeline, but that's based on an older 'unreleased' version version 
of 1.5.517. Next to the missing test dependency, I also added a workaround for 
an upstream bug (https://github.com/mumble-voip/mumble/issues/6193) and a 
patch which fixed a script error (missing closing ')').

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

Bug#1064220: shim: Please consider packaging new release (15.8)

[Boyuan Yang]

Source: shim
Version: 15.7-1
Tags: sid trixie
Severity: important
X-Debbugs-CC: 93...@debian.org vor...@debian.org

Dear maintainers,

A new upstream release of shim is available at
https://github.com/rhboot/shim/releases/tag/15.8 . Please
consider fixing your debian/watch monitoring script and
get the new version packaged into Debian.

Thanks,
Boyuan Yang


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

Bug#829444: Use DEP14 branch layout by default

[Gioele Barabucci]

On Fri, 5 Jan 2024 16:44:03 +0100 Guido =?iso-8859-1?Q?G=FCnther?= 
 wrote:

What we need to figure out is a way to distinguish "old" style
repos (default upstream and master (or what gbp.conf provides) with
newly created ones (default debian/latest and upstream/latest or what
gbp.conf provides).

Likely the best way to do so is to add a `gbp.conf` option:

`layout = [legacy|dep14]`

defaulting to `legacy` if unset. 


Another possibility would be to check which branch exist and understand 
what is the intended layout. debian-janitor does that.


Pseudo-code:

if branches.include?("debian/latest", "upstream/latest"):
layout = dep14-2020
if branches.include?("debian/master"):
layout = dep14-2014
else:
layout = legacy

Obviously this must be tweaked to take into account branch names set via 
gbp.conf.


Regards,

--
Gioele Barabucci

Bug#1010062: RFA: autogen -- automated text file generator

[Andreas Metzler]

On 2022-04-23 Andreas Metzler  wrote:
> Package: wnpp
> Severity: normal
> X-Debbugs-Cc: auto...@packages.debian.org
> Control: affects -1 src:autogen

> I request an adopter for the autogen package.
[...]

Hello,

Please note that autogen is nearing EOL. It is also pretty complicated
internally (guile, C code, shell scripting). I will probably look into
submitting bug reports against rdeps so they know they need to move on.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1007614: crypt++el: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
Please find the debdiff attached.diff -Nru crypt++el-2.94/crypt++.el crypt++el-2.94/crypt++.el
--- crypt++el-2.94/crypt++.el   2024-02-18 17:39:09.0 +
+++ crypt++el-2.94/crypt++.el   2008-07-18 12:22:56.0 +
@@ -1570,7 +1570,7 @@
   (setq regexp (nth 3 elt))
   (if (and (stringp regexp)
(string-match regexp file))
-  (return (nth 0 elt))
+(return (nth 0 elt))
 
 (defun crypt-encryption-type-set ()
   "Set `crypt-encryption-type'"
diff -Nru crypt++el-2.94/debian/changelog crypt++el-2.94/debian/changelog
--- crypt++el-2.94/debian/changelog 2024-02-18 17:39:09.0 +
+++ crypt++el-2.94/debian/changelog 2024-02-18 17:14:28.0 +
@@ -1,3 +1,11 @@
+crypt++el (2.94-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Convert to source format 3.0 (closes: #1007614)
+  * d/copyright: Convert to machine-readable format.
+
+ -- Bastian Germann   Sun, 18 Feb 2024 17:14:28 +
+
 crypt++el (2.94-3.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru crypt++el-2.94/debian/copyright crypt++el-2.94/debian/copyright
--- crypt++el-2.94/debian/copyright 2024-02-18 17:39:09.0 +
+++ crypt++el-2.94/debian/copyright 2024-02-18 17:14:28.0 +
@@ -1,25 +1,26 @@
-This package was debianized by Christoph Martin mar...@verwaltung.uni-mainz.de 
on
-Fri, 11 Jul 1997 13:44:58 +0200.
-
-It was downloaded from
-http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/os-utils/crypt.el
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This package was debianized by Christoph Martin 
mar...@verwaltung.uni-mainz.de on
+ Fri, 11 Jul 1997 13:44:58 +0200.
+Source:
+ 
http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/os-utils/crypt.el
 
+Files: *
 Copyright:
-
  Copyright (C) 1998 Free Software Foundation, Inc.
  Copyright (C) 1994 Lawrence R. Dodd
  Copyright (C) 1993 Lawrence R. Dodd and Rod Whitby
  Copyright (C) 1988, 1989, 1990 Kyle E. Jones
-
+License: GPL-2+
  This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
  the Free Software Foundation; either version 2 of the License, or
  (at your option) any later version.
-
+ .
  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.
-
-On Debian systems, the complete text of the GNU General Public License
-can be found in `/usr/share/common-licenses/GPL'.
+Comment:
+ On Debian systems, the complete text of the GNU General Public License
+ version 2 can be found in `/usr/share/common-licenses/GPL-2'.
diff -Nru crypt++el-2.94/debian/patches/debian.patch 
crypt++el-2.94/debian/patches/debian.patch
--- crypt++el-2.94/debian/patches/debian.patch  1970-01-01 00:00:00.0 
+
+++ crypt++el-2.94/debian/patches/debian.patch  2024-02-18 17:14:28.0 
+
@@ -0,0 +1,13 @@
+Description: Fix indentation
+---
+--- crypt++el-2.94.orig/crypt++.el
 crypt++el-2.94/crypt++.el
+@@ -1570,7 +1570,7 @@ Derived from variable `crypt-encoding-al
+   (setq regexp (nth 3 elt))
+   (if (and (stringp regexp)
+(string-match regexp file))
+-(return (nth 0 elt))
++  (return (nth 0 elt))
+ 
+ (defun crypt-encryption-type-set ()
+   "Set `crypt-encryption-type'"
diff -Nru crypt++el-2.94/debian/patches/series 
crypt++el-2.94/debian/patches/series
--- crypt++el-2.94/debian/patches/series1970-01-01 00:00:00.0 
+
+++ crypt++el-2.94/debian/patches/series2024-02-18 17:14:28.0 
+
@@ -0,0 +1 @@
+debian.patch
diff -Nru crypt++el-2.94/debian/source/format 
crypt++el-2.94/debian/source/format
--- crypt++el-2.94/debian/source/format 2024-02-18 17:39:09.0 +
+++ crypt++el-2.94/debian/source/format 2024-02-18 17:14:04.0 +
@@ -1 +1 @@
-1.0
+3.0 (quilt)

Bug#446133: crypt++el has been removed from Debian, closing #446133

[Bastian Germann]

For the record, #481082 tells the story of the package removal and 
reintroduction.
The package upstream seems to be gone now. Maybe it is time to ask for removal 
again?

Bug#683640: cntlm: please upgrade to source format 3.0 (quilt)

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru cntlm-0.92.3/debian/changelog cntlm-0.92.3/debian/changelog
--- cntlm-0.92.3/debian/changelog   2024-02-18 17:09:07.0 +
+++ cntlm-0.92.3/debian/changelog   2024-02-18 16:59:48.0 +
@@ -1,3 +1,11 @@
+cntlm (0.92.3-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. Closes: #683640.
+  * d/copyright: Convert to machine-readable format.
+
+ -- Bastian Germann   Sun, 18 Feb 2024 16:59:48 +
+
 cntlm (0.92.3-1.2) unstable; urgency=medium
 
   [ Gianfranco Costamagna ]
@@ -61,7 +69,7 @@
 
  -- David Watson   Tue, 08 Jan 2008 23:34:29 +
 
-cntlm (0.35.1-1) unstable; urgency=low 
+cntlm (0.35.1-1) unstable; urgency=low
 
   [ David Kubicek ] 
   * New upstream release
@@ -147,4 +155,3 @@
   * Makefile adjustments regarding installation directories
 
  -- David Kubicek   Fri, 01 Jun 2007 17:36:34 +0200
-
diff -Nru cntlm-0.92.3/debian/copyright cntlm-0.92.3/debian/copyright
--- cntlm-0.92.3/debian/copyright   2024-02-18 17:09:07.0 +
+++ cntlm-0.92.3/debian/copyright   2024-02-18 16:59:48.0 +
@@ -1,32 +1,36 @@
-This package was debianized by David Kubicek  on
-Fri, 01 Jun 2007 10:46:26 +0200.
-
-The current Debian maintainer is David Watson 
-
-It was downloaded from 
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Comment:
+ This package was debianized by David Kubicek  on
+ Fri, 01 Jun 2007 10:46:26 +0200.
+ .
+ The current Debian maintainer is David Watson 
+Source:
+ 
 
+Files: *
 Copyright: 
-
 Copyright (C) 2007 David Kubicek
-
-License:
-
-This program is free software; you can redistribute it and/or modify
-it under the terms of the GNU General Public License (version 2) as published
-by the Free Software Foundation; either version 2 of the License.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License with
-the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL-2;
-if not, write to the Free Software Foundation, Inc., 51 Franklin St,
-Fifth Floor, Boston, MA 02110-1301, USA.
-
-On Debian systems, the complete text of the GNU General Public
-License, version 2, can be found in /usr/share/common-licenses/GPL-2.
-
-The Debian packaging is Copyright (C) 2007, David Kubicek  and
-is licensed under the GPL, see `/usr/share/common-licenses/GPL-2'.
+License: GPL-2+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License (version 2) as published
+ by the Free Software Foundation; either version 2 of the License,
+ or (at your option) any later version.
+ .
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License with
+ the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL-2;
+ if not, write to the Free Software Foundation, Inc., 51 Franklin St,
+ Fifth Floor, Boston, MA 02110-1301, USA.
+Comment:
+ On Debian systems, the complete text of the GNU General Public
+ License, version 2, can be found in /usr/share/common-licenses/GPL-2.
+
+Files: debian/*
+Copyright: (C) 2007, David Kubicek 
+License: GPL-2
+ The Debian packaging is licensed under the GPL,
+ see `/usr/share/common-licenses/GPL-2'.
diff -Nru cntlm-0.92.3/debian/patches/debian.patch 
cntlm-0.92.3/debian/patches/debian.patch
--- cntlm-0.92.3/debian/patches/debian.patch1970-01-01 00:00:00.0 
+
+++ cntlm-0.92.3/debian/patches/debian.patch2024-02-18 16:59:48.0 
+
@@ -0,0 +1,226 @@
+--- cntlm-0.92.3.orig/direct.c
 cntlm-0.92.3/direct.c
+@@ -282,8 +282,19 @@ rr_data_t direct_request(void *cdata, rr
+   data[0]->url = strdup(data[0]->rel_url);
+   }
+ 
+-  data[0]->headers = hlist_mod(data[0]->headers, 
"Connection", "keep-alive", 1);
+-  data[0]->headers = hlist_del(data[0]->headers, 
"Proxy-Authorization");
++  /*
++   * Force proxy keep-alive if the client can 
handle it (HTTP >= 1.1)
++   */
++  if (data[0]->http_version >= 11)
++  data[0]->headers = 
hlist_mod(data[0]->headers, "Connection", "keep-alive", 1);
++
++  /*
++ 

Bug#1007035: cl-regex: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru cl-regex-1/README cl-regex-1/README
--- cl-regex-1/README   2024-02-18 16:46:37.0 +
+++ cl-regex-1/README   1970-01-01 00:00:00.0 +
@@ -1,118 +0,0 @@
-(documentation from: http://www.geocities.com/mparker762/clawk.html>)
-
-REGEX package
-
-The regex engine is a pretty full-featured matcher, and thus is useful by
-itself. It was originally written as a prototype for a C++ matcher, though it
-has since diverged greatly.
-
-The regex compiler supports the following pattern syntax:
-
-* ^ matches the start of a string.
-* $ matches the end of a string.
-* [...] denotes a character class.
-* [^...] denotes a negated character class.
-* [:...:] denotes a special character class.
-  o [:alpha:] == [A-Za-z]
-  o [:upper:] == [A-Z]
-  o [:lower:] == [a-z]
-  o [:digit:] == [0-9]
-  o [:alnum:] == [A-Za-z0-9]
-  o [:xdigit:] == [A-Fa-f0-9]
-  o [:space:] == whitespace
-  o [:punct:] == punctuation marks
-  o [:graph:] == printable characters other than space
-  o [:cntrl:] == control characters
-  o [:word:] == wordlike characters
-  o [^:...:] denotes a negated special character class.
-* . matches any character.
-* (...) delimits a regex subexpression. Also denotes a register pattern.
-* (?...) denotes a regex subexpression that will not be captured in a 
register.
-* (?=...) denotes a regex subexpression that will be used as a forward
-   lookahead. If the subexpression matches, then the rest of the match will
-   continue as if the lookahead match had not occurred (i.e. it does not 
consume
-   the candidate string). It will not be captured in a register, though it 
can
-   contain subexpressions that may be captured.
-* (?!...) denotes a regex subexpression that will be used as a negative
-   forward lookahead (the match will continue only if the lookahead failed 
to
-   match). It will not be captured in a register, though it can contain
-   subexpressions that may be captured.
-* * denotes the kleene closure of the previous regex subexpression.
-* + denotes the positive closure of the previous regex subexpression.
-* *? denotes the non-greedy kleene closure of the previous regex 
subexpression.
-* +? denotes the non-greedy positive closure of the previous regex 
subexpression.
-* ? denotes the greedy match of 0 or 1 occurrences of the previous regex 
subexpression.
-* ?? denotes the non-greedy match of 0 or 1 occurrences of the previous
-   regex subexpression.
-* \nn denotes a back-match against the contents of a previously-matched 
register.
-* {nn,mm} denotes a bounded repetition.
-* {nn,mm}? denotes a non-greedy bounded repetition.
-* \n, \t, \r have their normal meanings.
-* \d matches any decimal character, \D matches any nondecimal character.
-* \w matches any wordlike character, \W matches any nonwordlike character.
-* \s matches any whitespace character, \S matches any nonspace character.
-* \< matches at the start of a word. \> matches at the end of a word.
-* \ that character (escapes an otherwise special meaning).
-* Special characters lose their specialness when escaped. There is a flag
-   to control this.
-* All other characters are matched literally.
-
-There are a variety of functions in the REGEX package that allow the programmer
-to adjust the allowable regular expression syntax:
-
-* The function ESCAPE-SPECIAL-CHARS allows you to change whether the
-   meta-characters have their magic meaning when escaped or unescaped. The 
default
-   behavior (per AWK syntax) is that special chars are unescaped.
-* The function ALLOW-BACKMATCH allows you to change whether or not the \nn
-   syntax is allowed. By default it is allowed.
-* The function ALLOW-RANGEMATCH allows you to change whether or not the the
-   {nn,mm} bounded repetition syntax is allowed. By default it is allowed.
-* The function ALLOW-NONGREEDY-QUANTIFIERS allows you to change whether or
-   not the *?, +?, ??, and {nn,mm}? quantifiers are recognized. By default 
they
-   are allowed.
-* The function ALLOW-NONREGISTER-GROUPS allows you to change whether or not
-   the (?...) syntax is recognized. By default it is allowed.
-* The function DOT-MATCHES-NEWLINE allows you to change whether '.' in a
-   pattern matches the newline character. This is false by default.
-
-Parenthesized expressions within the pattern are considered a register pattern,
-and will be recorded for use after the match. There is an implicit set of
-parentheses around the entire expression, so the bounds of the matched text
-itself will always occupy register 0.
-
-Extensions that will be coming soon include:
-
-   1. I am working on a second backend for the

Bug#1064219: net-snmp: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: net-snmp
Version: 5.9.4+dfsg-1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
net-snmp as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for net-snmp
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru net-snmp-5.9.4+dfsg/debian/changelog 
net-snmp-5.9.4+dfsg/debian/changelog
--- net-snmp-5.9.4+dfsg/debian/changelog2023-08-19 09:36:39.0 
+
+++ net-snmp-5.9.4+dfsg/debian/changelog2024-02-18 16:44:42.0 
+
@@ -1,3 +1,10 @@
+net-snmp (5.9.4+dfsg-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 16:44:42 +
+
 net-snmp (5.9.4+dfsg-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru net-snmp-5.9.4+dfsg/debian/control net-snmp-5.9.4+dfsg/debian/control
--- net-snmp-5.9.4+dfsg/debian/control  2023-08-19 09:36:39.0 +
+++ net-snmp-5.9.4+dfsg/debian/control  2024-02-18 16:44:42.0 +
@@ -74,7 +74,10 @@
  description, you need to activate the non-free repository and install the
  "snmp-mibs-downloader" package.
 
-Package: libsnmp40
+Package: libsnmp40t64
+Provides: ${t64:Provides}
+Replaces: libsnmp40
+Breaks: libsnmp40 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -89,14 +92,15 @@
  sending, receiving, decoding, and manipulation of the SNMP requests
  and responses.
 
-Package: libnetsnmptrapd40
+Package: libnetsnmptrapd40t64
+Provides: ${t64:Provides}
 Section: libs
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}, libsnmp-base
-Breaks: libsnmp40 (<= 5.9+dfsg-1)
-Replaces: libsnmp40 (<= 5.9+dfsg-1)
+Breaks: libnetsnmptrapd40 (<< ${source:Version}), libsnmp40t64 (<= 5.9+dfsg-1)
+Replaces: libnetsnmptrapd40, libsnmp40t64 (<= 5.9+dfsg-1)
 Description: SNMP (Simple Network Management Protocol) trap library
  The Simple Network Management Protocol (SNMP) provides a framework
  for the exchange of management information between agents (servers)
@@ -109,7 +113,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: no
-Depends: libc6-dev, libsnmp40 (=${binary:Version}), libnetsnmptrapd40 
(=${binary:Version}),
+Depends: libc6-dev, libsnmp40t64 (=${binary:Version}), libnetsnmptrapd40t64 
(=${binary:Version}),
  libwrap0-dev, libssl-dev, procps,
  libkvm-dev [kfreebsd-any], libsensors-dev [linux-any], 
${misc:Depends},
  libpci-dev
diff -Nru net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40.install 
net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40.install
--- net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40.install2023-08-19 
09:36:39.0 +
+++ net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40.install1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libnetsnmptrapd.so.*
diff -Nru net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40t64.install 
net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40t64.install
--- net-snmp-5.9.4+dfsg/debian/libnetsnmptrapd40t64.install 1970-01-01 
00:00:00.0 +
+++ 

Bug#1056364: borgmatic: please package documentation

[Dan Helfman]

Upstream dev here. Please let me know if there's anything I can do to 
make this easier. (Ideally in the form of a borgmatic ticket.) Today, 
the online documentation is "packaged" and served as a container image, 
but I realize that's not the most convenient way to consume offline 
documentation in Debian.


Dan

Bug#1064218: neon27: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: neon27
Version: 0.33.0-1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
neon27 as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for neon27
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
diff -Nru neon27-0.33.0/debian/changelog neon27-0.33.0/debian/changelog
--- neon27-0.33.0/debian/changelog  2024-02-02 22:12:14.0 +
+++ neon27-0.33.0/debian/changelog  2024-02-18 16:43:22.0 +
@@ -1,3 +1,10 @@
+neon27 (0.33.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 16:43:22 +
+
 neon27 (0.33.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru neon27-0.33.0/debian/control neon27-0.33.0/debian/control
--- neon27-0.33.0/debian/control2023-10-03 21:27:50.0 +
+++ neon27-0.33.0/debian/control2024-02-18 16:43:21.0 +
@@ -7,7 +7,10 @@
 Rules-Requires-Root: no
 Homepage: https://notroj.github.io/neon/
 
-Package: libneon27
+Package: libneon27t64
+Provides: ${t64:Provides}
+Replaces: libneon27
+Breaks: libneon27 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -46,15 +49,19 @@
 Conflicts: libneon-dev, libneon24-doc (<= 0.24.5-1), libneon25-dev (<< 
0.28.2-5), libneon27-gnutls-dev
 Provides: libneon-dev
 Replaces: libneon-dev, libneon25-dev, libneon27-gnutls-dev
-Depends: ${misc:Depends}, libneon27 (= ${binary:Version}), libssl-dev, 
libxml2-dev, libkrb5-dev, pkgconf
-Description: Header and static library files for libneon27
+Depends: ${misc:Depends}, libneon27t64 (= ${binary:Version}), libssl-dev, 
libxml2-dev, libkrb5-dev, pkgconf
+Description: Header and static library files for libneon27t64
  This package contains the headers and the static library for libneon27.
  .
  Neon provides lower-level interfaces to directly implement new HTTP
  methods, and higher-level interfaces so that you don't have to
  worry about the lower-level stuff.
 
-Package: libneon27-gnutls
+Package: libneon27t64-gnutls
+Provides: ${t64:Provides}
+X-Time64-Compat: libneon27-gnutls
+Replaces: libneon27-gnutls
+Breaks: libneon27-gnutls (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -94,9 +101,9 @@
 Conflicts: libneon-dev, libneon24-doc (<= 0.24.5-1), libneon25-dev (<< 
0.28.2-5), libneon27-dev
 Provides: libneon-dev
 Replaces: libneon-dev, libneon25-dev, libneon27-dev
-Depends: ${misc:Depends}, libneon27-gnutls (= ${binary:Version}),
+Depends: ${misc:Depends}, libneon27t64-gnutls (= ${binary:Version}),
  libgnutls28-dev, libxml2-dev, libkrb5-dev, pkgconf
-Description: Header and static library files for libneon27 (GnuTLS enabled)
+Description: Header and static library files for libneon27t64 (GnuTLS enabled)
  This package contains the headers and the static library for
  libneon27-gnutls.
  .
diff -Nru neon27-0.33.0/debian/libneon27-gnutls.lintian-overrides 
neon27-0.33.0/debian/libneon27-gnutls.lintian-overrides
--- neon27-0.33.0/debian/libneon27-gnutls.lintian-overrides 2015-10-03 
19:

Bug#1064159: ebook-speaker 6.2.0-4+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: ebook-speaker
Version: 6.2.0-4+deb12u1

Explanation: support username over 8 characters when enumerating groups

Bug#1064064: wayfire 0.7.4-3+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: wayfire
Version: 0.7.4-3+deb12u1

Explanation: add missing dependencies

Bug#1057874: archlinux-keyring 0~20231113-1~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: archlinux-keyring
Version: 0~20231113-1~deb12u1

Explanation: switch to pre-built keyrings; sync with upstream

Bug#1051466: ovn 23.03.1-1~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: ovn
Version: 23.03.1-1~deb12u1

Explanation: new upstream stable version

Bug#1064217: bitlbee: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: bitlbee
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1055036: bookworm-pu: package crmsh/4.4.1-1+deb12u1

[Jonathan Wiltshire]

Control: tag -1 = bookworm confirmed

On Sat, Feb 17, 2024 at 05:08:36PM +0100, Valentin Vidic wrote:
> On Mon, Feb 12, 2024 at 06:21:52PM +, Jonathan Wiltshire wrote:
> > This will happen on every package update, no? What if the local
> > administrator has set other properties on the log file (e.g. to allow other
> > users to read it)?
> 
> Thanks, I have updated the postinst to only make the changes if
> the logs don't exist. Updated debdiff attached below...

Please go ahead.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Bug#1007548: binstats: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.
diff -Nru binstats-1.08/Makefile binstats-1.08/Makefile
--- binstats-1.08/Makefile  2024-02-18 16:23:57.0 +
+++ binstats-1.08/Makefile  1999-12-06 19:36:05.0 +
@@ -12,8 +12,8 @@
 PREFIX= /usr/local
 # If you want to install derefsymlink in some place other than
 # /usr/local/bin then make sure PATH is set accordingly in binstats
-DESTBIN= $(DESTDIR)/$(PREFIX)/bin
-DESTMAN= $(DESTDIR)/$(PREFIX)/man/man1
+DESTBIN= $(PREFIX)/bin
+DESTMAN= $(PREFIX)/man/man1
 
 derefsymlink: derefsymlink.o
$(CC) -o $@ $(CFLAGS) $(LDFLAGS) derefsymlink.o
@@ -24,4 +24,4 @@
install -m 644 binstats.1 derefsymlink.1 $(DESTMAN)
 
 clean:
-   rm -f derefsymlink derefsymlink.o *~ *.00 bstats.log*
+   rm -f derefsymlink derefsymlink.o
diff -Nru binstats-1.08/binstats binstats-1.08/binstats
--- binstats-1.08/binstats  2024-02-18 16:23:57.0 +
+++ binstats-1.08/binstats  2001-01-18 12:31:38.0 +
@@ -100,7 +100,6 @@
 # your system or ignore if USEPATH=1)
 EXEDIR="/bin /usr/bin /usr/local/bin /sbin /usr/sbin /usr/local/sbin 
/usr/X11R6/bin /usr/games"
 
-USEMANPATH=1
 # the list of directories where your man pages reside
 MANDIR="/usr/man /usr/share/man /usr/X11R6/man /usr/local/man"
 
@@ -136,8 +135,6 @@
 DEBUG=0
 # another debugging option, set to 0 to reuse old temp files
 FILEOPS=1
-# Debian checks? Set to 1 to skip Debian-specific checks
-NODEBIAN=0
 
 #--process command line arguments---
 CLI_USAGE=\
@@ -146,7 +143,7 @@
[-l[ibraries]=\"/lib /usr/lib\"]
   [-m[anuals]=\"/usr/man /usr/local/man\"]
   [-p[ath]=\"/bin:/usr/bin:/usr/local/bin\"]
-   [-t[emp]=/tmp] [-s[kip-debian] [-v[ersion]]"
+   [-t[emp]=/tmp] [-v[ersion]]"
 
 for CLI_OPT
 do
@@ -165,11 +162,8 @@
   -l*=*) USELDSOCONF=0
  DLIBDIR="$CLI_ARG" ;;
   -m*=*) MANDIR="$CLI_ARG" ;;
-  -m*=*) USEMANPATH=0
- MANDIR="$CLI_ARG" ;;
   -p*=*) PATH="$CLI_ARG" ;;
   -t*=*) TMPDIR="$CLI_ARG" ;;
-  -s*=*) NODEBIAN=1 ;;
   -v*) echo "binstats-$BSVER"
exit 0 ;;
   *) echo "$CLI_USAGE"
@@ -183,23 +177,10 @@
  EXEDIR=`echo $OLDPATH | tr : ' ' | sed s:\~:$HOME:g`
 fi
 
-if [ $USEMANPATH -eq 1 ];then
- MANDIR=`manpath | tr : ' '`
-fi
-
 if [ $USELDSOCONF -eq 1 ]; then
 # use /etc/ld.so.conf plus the two "trusted" locations
- LDSOCONF=`cat /etc/ld.so.conf | grep -v '^#' | grep -v '^include ' | xargs 
echo`
+ LDSOCONF=`cat /etc/ld.so.conf | grep -v '^#' | xargs echo`
  DLIBDIR="/lib /usr/lib $LDSOCONF"
-
- # Handle includes in LDSOCONF
- LDSOCONF_INC=`cat /etc/ld.so.conf | grep -v '^#' | grep '^include ' | sed -e 
's/^include //' | xargs echo`
- for file in `ls $LDSOCONF_INC 2>/dev/null`; do
-if [ -e "$file" ]; then
-LDSOCONF=`cat $file | grep -v '^#' | grep -v '^include ' | xargs echo`
-DLIBDIR="$DLIBDIR $LDSOCONF"
-fi
-  done
 fi
 
 # ID number
@@ -207,107 +188,52 @@
 
 # name of temp log
 BSLOGTMP=$BSLOG.$PIDNO
-# Create the files we are going to use
-# backup old log file
-if [ -f $BSLOG ]; then mv -f $BSLOG $BSLOG~; fi
-{ umask 066; touch $BSLOG; [ -e $BSLOGTMP ] && rm -f $BSLOGTMP; touch 
$BSLOGTMP ; } 
 
 if [ $DEBUG -gt 0 ]; then
- BINSDIR=.
+ TMPDIR=.
  PIDNO=00
 else
- BINSDIR=`mktemp -t -d binstats.XX` || { echo "$0: Cannot create temporary 
directory!" >&2; exit 1; }
-fi
-# tidy up
-if [ $DEBUG -eq 0 ]; then
-   trap " [ -d \"$BINSDIR\" ] && /bin/rm -rf -- \"$BINSDIR\"" 0 1 2 3 13 15
+ TMPDIR=$TMPDIR/binstats.$PIDNO
+ mkdir -m 700 $TMPDIR || exit 1
 fi
 
+
 # list of executables
-EXELIST=$BINSDIR/exelist.$PIDNO
+EXELIST=$TMPDIR/exelist.$PIDNO
 # list of dynamic libraries
-DLIBLIST=$BINSDIR/dliblist.$PIDNO
+DLIBLIST=$TMPDIR/dliblist.$PIDNO
 # list of man pages
-MANLIST=$BINSDIR/manlist.$PIDNO
+MANLIST=$TMPDIR/manlist.$PIDNO
 # executable types
-EXEFILE=$BINSDIR/exefile.$PIDNO
+EXEFILE=$TMPDIR/exefile.$PIDNO
 # list of dependent (used) libraries
-EXELIB=$BINSDIR/exelib.$PIDNO
+EXELIB=$TMPDIR/exelib.$PIDNO
 # list of unused libraries
-DLIBUN=$BINSDIR/dlibun.$PIDNO
-# list of unused libraries with packages
-DLIBUNP=$BINSDIR/dlibunp.$PIDNO
-
-# Unused library packages
-LIBPUN=$BINSDIR/libpun.$PIDNO
-# Package list
-PACKLIST=$BINSDIR/packlist.$PIDNO
+DLIBUN=$TMPDIR/dlibun.$PIDNO
 
 # temporary storage
-DTEMPA=$BINSDIR/dtempa.$PIDNO # all dynamic libs in $DLIBDIR
-DTEMPB=$BINSDIR/dtempb.$PIDNO # missing dynamic libs in $EXELIB
-DTEMPC=$BINSDIR/dtempc.$PIDNO # dereferenced list of $DTEMPA
-
-ETEMPA=$BINSDIR/etempa.$PIDNO # all files in $EXEDIR
-ETEMPB=$BINSDIR/etempb.$PIDNO # output of ldd on files in $EXEFILE
-ETEMPC=$BINSDIR/etempc.$PIDNO # statically linked binaries in $ETEMPB
-ETEMPD=$BINSDIR/etempd.$PIDNO # duplicate executable names in $ETEMPA
-ETEMPE=$BINSDIR/etempe.$PIDNO # 'not stripped' binaries in $EXEFILE
-ETEMPF=$BINSDIR/etempf.$PIDNO # setuid binaries in $EXE

Bug#1007282: bindfs: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru bindfs-1.14.7/debian/changelog bindfs-1.14.7/debian/changelog
--- bindfs-1.14.7/debian/changelog  2024-02-18 16:17:24.0 +
+++ bindfs-1.14.7/debian/changelog  2024-02-18 16:16:20.0 +
@@ -1,3 +1,10 @@
+bindfs (1.14.7-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. (Closes: #1007282)
+
+ -- Bastian Germann   Sun, 18 Feb 2024 16:16:20 +
+
 bindfs (1.14.7-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #957041)
diff -Nru bindfs-1.14.7/debian/source/format bindfs-1.14.7/debian/source/format
--- bindfs-1.14.7/debian/source/format  2024-02-18 16:17:24.0 +
+++ bindfs-1.14.7/debian/source/format  2024-02-18 16:16:20.0 +
@@ -1 +1 @@
-1.0
+3.0 (quilt)

Bug#1044057: python-ulmo and pandas 2

[Rebecca N. Palmer]

Control: tags -1 patch

This should fix this (and as the filename suggests, also re-adds spme 
older fixes that seem to have been dropped by mistake between -1.1 and 
-2), but has not been tested: the relevant tests aren't run by default 
and there vaguely might be legal issues around ulmo's tests.Description: Don't fail on malformed or changed test data

CDEC has malformed lines that pandas 1.4+ errors out on
(I'm not sure why earlier pandas didn't do the same);
GHCN has simply changed at the source.

Author: Rebecca N. Palmer  (but upstream independently came up with the on_bad_lines part)
Bug-Debian: https://bugs.debian.org/1017573 https://bugs.debian.org/1044057
Forwarded: partly no, partly not-needed, partly https://github.com/ulmo-dev/ulmo/pull/214

--- a/test/cdec_historical_test.py
+++ b/test/cdec_historical_test.py
@@ -9,7 +9,7 @@ def test_get_stations():
 stations_file = 'cdec/historical/all_stations.csv'
 with test_util.mocked_urls(stations_file):
 stations = ulmo.cdec.historical.get_stations()
-assert 2000 < len(stations)
+assert 1900 < len(stations)
 assert u'PRA' in stations.index
 
 
--- a/test/ghcn_daily_test.py
+++ b/test/ghcn_daily_test.py
@@ -10,12 +10,12 @@ import test_util
 test_stations = [
 {
 'country': 'US',
-'elevation': 286.5,
+'elevation': 325.8,
 'gsn_flag': 'GSN',
 'hcn_flag': 'HCN',
 'id': 'USW3870',
-'latitude': 34.8831,
-'longitude': -82.2203,
+'latitude': 34.8833,
+'longitude': -82.2197,
 'name': 'GREER',
 'network': 'W',
 'network_id': '3870',
--- a/ulmo/cdec/historical/core.py
+++ b/ulmo/cdec/historical/core.py
@@ -74,9 +74,9 @@ def get_stations():
 # I haven't found a better list of stations, seems pretty janky
 # to just have them in a file, and not sure if/when it is updated.
 url = 'http://cdec.water.ca.gov/misc/all_stations.csv'
-# the csv is malformed, so some rows think there are 7 fields
-col_names = ['id','meta_url','name','num','lat','lon','junk']
-df = pd.read_csv(url, names=col_names, header=None, quotechar="'",index_col=0)
+# the csv is malformed, so some rows think there are 7-8 fields
+col_names = ['id','meta_url','name','num','lat','lon']
+df = pd.read_csv(url, names=col_names, header=None, quotechar="'",index_col=0,on_bad_lines='skip')
 
 return df
 
@@ -170,7 +170,7 @@ def get_station_sensors(station_ids=None, sensor_ids=None, resolutions=None):
 sensor_list.columns = ['sensor_id', 'variable', 'resolution','timerange']
 except:
 sensor_list.columns = ['variable', 'sensor_id', 'resolution', 'varcode', 'method', 'timerange']
-sensor_list[['variable', 'units']] = sensor_list.variable.str.split(',', 1, expand=True)
+sensor_list[['variable', 'units']] = sensor_list.variable.str.split(',', n=1, expand=True)
 sensor_list.resolution = sensor_list.resolution.str.strip('()')
 
 station_sensors[station_id] = _limit_sensor_list(sensor_list, sensor_ids, resolutions)

Bug#1064216: weex: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: weex
Version: 2.8.3
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1063717: NVIDIA packages in stable-updates fix module compilation for linux 6.1.76-1

[matte . mb2006 . 9990]

On Sun, 18 Feb 2024 01:24:02 +0100 Andreas Beckmann 
wrote:
> Hi,
> 
> NVIDIA driver packages that fix module compilation for linux 6.1.76-1
> (aka linux-image-6.1.0-18-*) are now available in stable-updates:
> 
> https://lists.debian.org/debian-stable-announce/2024/02/msg2.html
> 
> 
> Andreas
> 
> 
The update is not yet available on my PC. I live in Italy.

Bug#1060682: u-boot-sifive: Unable to boot from NVME via SPI on Hifive Unmatched Rev B

[Heinrich Schuchardt]

Related Launchpad bug:

HiFive Unmatched: __wrpll_calc_filter_range: post-divider reference freq 
out of range: 4294967295

https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054091

Bug#1007644: vde2: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
Please find the debdiff attached.diff -Nru vde2-2.3.2+r586/.git/COMMIT_EDITMSG 
vde2-2.3.2+r586/.git/COMMIT_EDITMSG
--- vde2-2.3.2+r586/.git/COMMIT_EDITMSG 2023-09-22 08:47:43.0 +
+++ vde2-2.3.2+r586/.git/COMMIT_EDITMSG 1970-01-01 00:00:00.0 +
@@ -1,46 +0,0 @@
-Add link to upstream sources in d/copyright
-
-Closes: #1051059
-Signed-off-by: Mattia Rizzolo 
-
-# Please enter the commit message for your changes. Lines starting
-# with '#' will be ignored, and an empty message aborts the commit.
-#
-# Date:  Fri Sep 22 10:49:40 2023 +0200
-#
-# On branch debian/sid
-# Your branch is ahead of 'origin/debian/sid' by 1 commit.
-#   (use "git push" to publish your local commits)
-#
-# Changes to be committed:
-#  modified:   debian/changelog
-#  modified:   debian/copyright
-#
-#  >8 
-# Do not modify or remove the line above.
-# Everything below it will be ignored.
-diff --git a/debian/changelog b/debian/changelog
-index 8e4ce2d..3a91bff 100644
 a/debian/changelog
-+++ b/debian/changelog
-@@ -1,3 +1,10 @@
-+vde2 (2.3.2+r586-9) unstable; urgency=medium
-+
-+  * Team upload.
-+  * Add link to upstream sources in d/copyright.  Closes: #1051059
-+
-+ -- Mattia Rizzolo   Fri, 22 Sep 2023 10:47:43 +0200
-+
- vde2 (2.3.2+r586-8) unstable; urgency=medium
- 
-   * do not generate vdeplug, libvdeplug* packages (Closes: #1000798)
-diff --git a/debian/copyright b/debian/copyright
-index aa32ee6..8dc0a99 100644
 a/debian/copyright
-+++ b/debian/copyright
-@@ -1,4 +1,5 @@
- Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
-+Source: https://sourceforge.net/projects/vde
- 
- Files: *
- Copyright: 2003-2020 Renzo Davoli
diff -Nru vde2-2.3.2+r586/.git/FETCH_HEAD vde2-2.3.2+r586/.git/FETCH_HEAD
--- vde2-2.3.2+r586/.git/FETCH_HEAD 2023-09-22 08:46:19.0 +
+++ vde2-2.3.2+r586/.git/FETCH_HEAD 1970-01-01 00:00:00.0 +
@@ -1,2 +0,0 @@
-07e68d4668a6329fc577fa190023ec628a5694b2   branch 'debian/sid' of 
salsa.debian.org:virtualsquare-team/vde2
-c6b68ab89e1dc8bb63a116b7096940a81c690843   not-for-merge   branch 
'upstream' of salsa.debian.org:virtualsquare-team/vde2
diff -Nru vde2-2.3.2+r586/.git/HEAD vde2-2.3.2+r586/.git/HEAD
--- vde2-2.3.2+r586/.git/HEAD   2020-01-30 11:43:23.0 +
+++ vde2-2.3.2+r586/.git/HEAD   1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-ref: refs/heads/debian/sid
diff -Nru vde2-2.3.2+r586/.git/ORIG_HEAD vde2-2.3.2+r586/.git/ORIG_HEAD
--- vde2-2.3.2+r586/.git/ORIG_HEAD  2023-09-22 08:46:19.0 +
+++ vde2-2.3.2+r586/.git/ORIG_HEAD  1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-07e68d4668a6329fc577fa190023ec628a5694b2
diff -Nru vde2-2.3.2+r586/.git/config vde2-2.3.2+r586/.git/config
--- vde2-2.3.2+r586/.git/config 2020-01-30 11:43:23.0 +
+++ vde2-2.3.2+r586/.git/config 1970-01-01 00:00:00.0 +
@@ -1,14 +0,0 @@
-[core]
-   repositoryformatversion = 0
-   filemode = true
-   bare = false
-   logallrefupdates = true
-[remote "origin"]
-   url = g...@salsa.debian.org:virtualsquare-team/vde2.git
-   fetch = +refs/heads/*:refs/remotes/origin/*
-[branch "upstream"]
-   remote = origin
-   merge = refs/heads/upstream
-[branch "debian/sid"]
-   remote = origin
-   merge = refs/heads/debian/sid
diff -Nru vde2-2.3.2+r586/.git/description vde2-2.3.2+r586/.git/description
--- vde2-2.3.2+r586/.git/description2020-01-30 11:42:47.0 +
+++ vde2-2.3.2+r586/.git/description1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-Unnamed repository; edit this file 'description' to name the repository.
diff -Nru vde2-2.3.2+r586/.git/hooks/applypatch-msg.sample 
vde2-2.3.2+r586/.git/hooks/applypatch-msg.sample
--- vde2-2.3.2+r586/.git/hooks/applypatch-msg.sample2020-01-30 
11:42:47.0 +
+++ vde2-2.3.2+r586/.git/hooks/applypatch-msg.sample1970-01-01 
00:00:00.0 +
@@ -1,15 +0,0 @@
-#!/bin/sh
-#
-# An example hook script to check the commit log message taken by
-# applypatch from an e-mail message.
-#
-# The hook should exit with non-zero status after issuing an
-# appropriate message if it wants to stop the commit.  The hook is
-# allowed to edit the commit message file.
-#
-# To enable this hook, rename this file to "applypatch-msg".
-
-. git-sh-setup
-commitmsg="$(git rev-parse --git-path hooks/commit-msg)"
-test -x "$commitmsg" && exec "$commitmsg" ${1+"$@"}
-:
diff -Nru vde2-2.3.2+r586/.git/hooks/commit-msg.sample 
vde2-2.3.2+r586/.git/hooks/commit-msg.sample
--- vde2-2.3.2+r586/.git/hooks/commit-msg.sample2020-01-30 
11:42:47.0 +
+++ vde2-2.3.2+r586/.git/hooks/commit-msg.sample1970-01-01 
00:00:00.0 +
@@ -1,24 +0,0 @@
-#!/bin/sh
-#
-# An example hook script to check the commit log message.
-# Called by "git commit" with one argument, the na

Bug#1060682: u-boot-sifive: Unable to boot from NVME via SPI on Hifive Unmatched Rev B

[Aurelien Jarno]

control: tag -1 + upstream

On 2024-01-12 23:26, Aurelien Jarno wrote:
> On 2024-01-12 13:32, Vagrant Cascadian wrote:
> > On 2024-01-12, Vagrant Cascadian wrote:
> > > On 2024-01-12, Vagrant Cascadian wrote:
> > >> On 2024-01-12, Michael Fladischer wrote:
> > >>> I was able to boot my Hifive Unmatched Rev B board via SPI from NVME 
> > >>> with
> > >>> u-boot-sifive-2023.07+dfsg-1. After upgrading to 2024.01+dfsg-1 u-boot 
> > >>> is no
> > >>> longer able to see any NVME drives:
> > > ...
> > >> I am getting this too. I had tested with a local build of
> > >> 2024.01~rc6-1~0 and that worked fine, so I am a bit surprised as none of
> > >> the very few commits between v2024.01-rc6 and v2024.01 seem relevent.
> > >
> > > I should also note that I am testing with u-boot on microSD, so it is
> > > not specific to u-boot from SPI.
> > >
> > >> I also wonder about opensbi, which was fairly recently upgraded,
> > >> although I *thought* I tested opensbi 1.4-1 with the ~rc6 build I had
> > >> done...
> > >
> > > I verified u-boot-sifive 2024.01~rc6+dfsg-2 (formerly in experimental)
> > > works, which was built with the same opensbi version. In fact, the only
> > > difference in the installed build-dependencies were perl related:
> > >
> > > - libperl5.36 (= 5.36.0-10+b1),
> > > + libperl5.38 (= 5.38.2-2),
> > > - perl (= 5.36.0-10+b1),
> > > - perl-base (= 5.36.0-10+b1),
> > > - perl-modules-5.36 (= 5.36.0-10),
> > > + perl (= 5.38.2-2),
> > > + perl-base (= 5.38.2-2),
> > > + perl-modules-5.38 (= 5.38.2-2),
> > >
> > > I am attempting a local rebuild, will see how that goes...
> > 
> > Well, rebuilding and just adding a new debian/changelog
> > entry... worked. both from a reboot and from a cold start.
> > 
> > That does not leave much to investigate, so is a bit worrying, but
> > perhaps a binNMU would "fix" it?
> 
> I tried to do a build from the sources using sbuild, and I ended up with
> exactly the same binaries, so unfortunately I doubt a binNMU would fix
> it.

I have spent some time on that, I haven't found the issue, but here are
my findings:

- Rebuilding the package with the current packages from sid, leads to a
  slightly different issue: reset_gpio is invalid

- The issue is reproducible building the upstream version 2024.01

- The actual error message changes with the value of
  CONFIG_LOCALVERSION:
  - If the final version is "2024.01", I get:
__wrpll_calc_filter_range: post-divider reference freq out of range: 
4294967295__wrpll_calc_filter_range: post-divider reference freq out of range: 
4294967295__wrpll_calc_filter_range: post-divider reference freq out of range: 
4294967295__wrpll_calc_filter_range: post-divider reference freq out of range: 
4294967295initcall failed at call fff5920e (err=-34)

  - If the final version is "2024.01+test-1", I get:
reset_gpio is invalid

  - If the final version is "2024.01+test-1+abc", I get:
pwren_gpio is invalid

- So far I have not been able to reproduce the issue with gcc-12, which
  doesn't mean that the bug is gcc-13 specific.

- This seems to be the same bug as: 
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054091

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net


signature.asc
Description: PGP signature

Bug#1064214: tracker-miners: update its homepage

[Patrice Duroux]

Source: tracker-miners
Severity: wishlist

Dear Maintainer,

With a patch for this.

Thanks,
Patrice


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

Kernel: Linux 6.7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/control b/debian/control
index 90865001f..dccb27791 100644
--- a/debian/control
+++ b/debian/control
@@ -52,7 +52,7 @@ Build-Depends: debhelper-compat (= 13),
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/gnome-team/tracker-miners
 Vcs-Git: https://salsa.debian.org/gnome-team/tracker-miners.git
-Homepage: https://wiki.gnome.org/Projects/Tracker
+Homepage: https://tracker.gnome.org/
 Rules-Requires-Root: no
 
 Package: tracker-extract

Bug#1007540: tmpreaper: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru tmpreaper-1.6.17/.cvsignore tmpreaper-1.6.17+nmu1/.cvsignore
--- tmpreaper-1.6.17/.cvsignore 1998-01-27 04:00:30.0 +
+++ tmpreaper-1.6.17+nmu1/.cvsignore1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-tmpreaper
diff -Nru tmpreaper-1.6.17/ChangeLog tmpreaper-1.6.17+nmu1/ChangeLog
--- tmpreaper-1.6.17/ChangeLog  2022-06-15 08:04:55.0 +
+++ tmpreaper-1.6.17+nmu1/ChangeLog 2024-02-18 15:28:13.0 +
@@ -1,3 +1,11 @@
+tmpreaper (1.6.17+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0.
+closes:#1007540
+
+ -- Bastian Germann   Sun, 18 Feb 2024 15:28:13 +
+
 tmpreaper (1.6.17) unstable; urgency=medium
 
   * Fix version in configure.ac and re-added some disappeared lines from rules
diff -Nru tmpreaper-1.6.17/debian/changelog 
tmpreaper-1.6.17+nmu1/debian/changelog
--- tmpreaper-1.6.17/debian/changelog   2022-06-15 08:04:55.0 +
+++ tmpreaper-1.6.17+nmu1/debian/changelog  2024-02-18 15:28:13.0 
+
@@ -1,3 +1,11 @@
+tmpreaper (1.6.17+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0.
+closes:#1007540
+
+ -- Bastian Germann   Sun, 18 Feb 2024 15:28:13 +
+
 tmpreaper (1.6.17) unstable; urgency=medium
 
   * Fix version in configure.ac and re-added some disappeared lines from rules
diff -Nru tmpreaper-1.6.17/debian/source/format 
tmpreaper-1.6.17+nmu1/debian/source/format
--- tmpreaper-1.6.17/debian/source/format   2021-12-14 11:15:22.0 
+
+++ tmpreaper-1.6.17+nmu1/debian/source/format  2024-02-18 15:28:13.0 
+
@@ -1 +1 @@
-1.0
+3.0 (native)

Bug#1064215: misses many dependencies

[Pierre Gruet]

Package: libgrpc-java
Version: 1.41.3+ds-2
Severity: normal

Dear Maintainer,

libgrpc-java should (at least) depend on libanimal-sniffer-java and
libperfmark-java, as its pom files declare a dependency on their artifacts.

Perhaps a general review of the dependencies would be useful.

Best,

-- 
Pierre