Bug#1064337: samba: NMU diff for 64-bit time_t transition

[Andrew Bartlett]

Kia Ora Steve,
So long since we had a chance to work together, and I thank you for
your work on Debian.
Can we have a chat about this?
sssd does not, as I read it, use any time_t relevant parts of ldb, and
is the only external user of LDB in Debian that we know of.
Also, the debdiff changes the description of libsmbclient to
libsmbclient0 unintentionally in the free text.
I think therefore with some care we can reduce the impact of this
significantly, down to libsmbclient, which seems to use struct
timespec.
Andrew Bartlett
On Mon, 2024-02-19 at 22:30 -0800, Steve Langasek wrote:
> Source: sambaVersion: 2:4.20.0~rc2+dfsg-1Severity: importantTags:
> patch pending sid trixieUser: 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-
> bitarchitectures in 2038 and beyond(
> https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> sambaas a source package shipping runtime libraries whose ABI either
> is affectedby the change in size of time_t, or could not be analyzed
> viaabi-compliance-checker (and therefore to be on the safe side we
> assume isaffected).
> To ensure that inconsistent combinations of libraries with
> theirreverse-dependencies are never installed together, it is
> necessary tohave a library transition, which is most easily done by
> renaming theruntime library package.
> Since turning on 64-bit time_t is being handled centrally through a
> changeto the default dpkg-buildflags (https://bugs.debian.org/1037136
> ), it isimportant that libraries affected by this ABI change all be
> uploaded closetogether in time.  Therefore I have prepared a 0-day
> NMU for samba whichwill initially be uploaded to experimental if
> possible, then to unstableafter packages have cleared binary NEW.
> Please find the patch for this NMU attached.
> This NMU has not been uploaded to experimental yet because it is
> waiting onan update of the binary package override database from the
> ftp team forlibsmbclient, which was late identified as a package name
> requiring specialhandling.
> If you have any concerns about this patch, please reach out
> ASAP.  Therewill be a period of several days before we begin uploads
> to unstable; so ifinformation becomes available that your package
> should not be included inthe transition, there is time for us to
> amend the planned uploads.
-- 
Andrew Bartlett (he/him)   https://samba.org/~abartlet/Samba Team Member 
(since 2001) https://samba.orgSamba Team Lead
https://catalyst.net.nz/services/sambaCatalyst.Net Ltd
Proudly developing Samba for Catalyst.Net Ltd - a Catalyst IT group
company
Samba Development and Support: https://catalyst.net.nz/services/samba
Catalyst IT - Expert Open Source Solutions

Bug#1064337: [Pkg-samba-maint] Bug#1064337: samba: NMU diff for 64-bit time_t transition

[Michael Tokarev]

Control: tag -1 - patch pending

One more note: samba package in experimental is *not* yet intended for unstable,
it is a pre-release of next samba version and I don't plan to upload it to 
unstable
yet.  If any work is needed, it should be done on top of 4.19.  But I'm not sure
how to coordinate it all yet.  At the very least, I'm willing to help, can 
prepare
things with 4.19 and upload when needed.

/mjt

Bug#1064340: RFS: kylin-nm/4.0.0.0-1 -- Gui Applet tool for display and edit network simply

[xibowen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "kylin-nm":

 * Package name : kylin-nm
   Version  : 4.0.0.0-1
   Upstream contact : xibowen 
 * URL  : https://gitee.com/openkylin/kylin-nm
 * License  : GPL-2+, BSD-3-clause, GPL-3+
 * Vcs  : https://gitee.com/openkylin/kylin-nm
   Section  : utils

The source builds the following binary packages:

  kylin-nm - Gui Applet tool for display and edit network simply
  kylin-nm-plugin - Gui Applet plugin for display and edit network simply
  kylin-nm-plugin-dev - Gui Applet development for display and edit network 
simply
  libkylin-nm-base - Gui lib for display and edit network simply
  libkylin-nm-base-dev - Gui lib development for display and edit network simply

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

  https://mentors.debian.net/package/kylin-nm/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/k/kylin-nm/kylin-nm_4.0.0.0-1.dsc

Changes since the last upload:

 kylin-nm (4.0.0.0-1) unstable; urgency=medium
 .
   * New upstream release.

This package is depended on ukui-greeter and ukui-screensaver.

Regards,
-- 
  xibowen

Bug#1064337: [Pkg-samba-maint] Bug#1064337: samba: NMU diff for 64-bit time_t transition

[Michael Tokarev]

20.02.2024 09:30, Steve Langasek wrote:

Source: samba
Version: 2:4.20.0~rc2+dfsg-1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t



-Package: libsmbclient
+Package: libsmbclient0

Well.  Maybe this is ok.  I still haven't seen samba-libs analysis about
time_t abi, but smbclient never had a version in soname.

libsmbclient is definitely a public library.


-Package: libldb2
+Package: libldb2t64

And this one is definitely not needed.

libldb is an internal-to-samba library, which is used by exactly
one package in debian, sssd, for which you're adding Breaks.
I'm already adding the same Breaks in the next version of libldb,
because libldb has become incompatible with sssd *again* (the
new packages of samba 4.20 is in experimental, not yet with the
Breaks since I'm waiting for a rebuild of sssd).  Due the nature
of these libs (samba-libs and libldb), it is a stuff which is not
used outside, and it does not need time_t transition.

Where's the analysis of libsmbclient ABI?

Thanks,

/mjt

Bug#1063836: test l= tag dkim signature

[황병희]

On Tue, 2024-02-20 at 15:32 +0900, Byunghee HWANG wrote:
> Hi,
> 
> This is also test message of BTS. So please ignore.
> 
> especially i did insert l= tag of DKIM-Signarue.
> then i will check the result of all auth by return email.
> 
> 
> thanks;
> 

now this mail will be delivering via *bendel*.


Also i would like to see the result of all auth.


(please ignore this mail. it is just test...)

thanks;

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//


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

Bug#1042411: closed by Thomas Lange (found problem)

[Marc Lehmann]

On Sat, Feb 17, 2024 at 08:54:03PM +, Debian Bug Tracking System 
 wrote:
> the problem is that on your computer you have a directory /usr/etc.

Interesting bug.

> Then rinse uses this wrong path because it thinks a local rinse
> installation is available. Please remove this /usr/etc, which is not a
> usual directory.

I am not sure what you mean or why you closed this bug - asking me to
delete any "unusual" directories does not fix the bug in rinse. It's
completely legal in debian to have this directorxy, and some software
requires it - I cannot delete it without breaking other software.

The bug here is clearly in rinse - /usr/etc is not a debian-mandated
directory, so rinse must not rely on it being preesent or absent (see the
debian filesysytem heirarchy standard for example).

Asking users to delete random directories to work around a bug in your
package without fixing it is not acceptable.

Bug#1064339: qtscript-opensource-src: FTBFS: Please add support for loongarch64

[宋鼎]

Source: qtscript-opensource-src
Version: 5.15.10+dfsg-2
Severity: wishlist
Tags: ftbfs patch
User: debian-loonga...@lists.debian.org
Usertags: loong64


Dear maintainers,

We need to add architectural support for qtscript-opensource-src. 
Otherwise it will build failures .


Please consider the patch I have attached.
Would it be possible to include the support for LoongArch in the next
upload?
If you have any questions, you can contact me at any time.


/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |    ^~~~
../3rdparty/javascriptcore/JavaScriptCore/wtf/OwnPtr.h:61:25: warning: 
‘template class std::auto_ptr’ is deprecated: use 
'std::unique_ptr' instead [-Wdeprecated-declarations]
   61 | void adopt(std::auto_ptr autoPtr) { 
ASSERT(!autoPtr.get() || m_ptr != autoPtr.get()); deleteOwnedPtr(m_ptr); 
m_ptr = autoPtr.release(); }

  | ^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |    ^~~~
../3rdparty/javascriptcore/JavaScriptCore/wtf/VectorTraits.h:84:30: 
warning: ‘template class std::auto_ptr’ is deprecated: use 
'std::unique_ptr' instead [-Wdeprecated-declarations]
   84 | struct VectorTraits > : 
SimpleClassVectorTraits { };

  |  ^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |    ^~~~
In file included from 
../3rdparty/javascriptcore/JavaScriptCore/runtime/JSCell.h:28:
../3rdparty/javascriptcore/JavaScriptCore/runtime/JSValue.h: In 
constructor ‘QTJSC::JSValue::JSValue(QTJSC::JSCell*)’:
../3rdparty/javascriptcore/JavaScriptCore/runtime/JSValue.h:493:28: 
error: cast from ‘QTJSC::JSCell*’ to ‘int32_t’ {aka ‘int’} loses 
precision [-fpermissive]

  493 | u.asBits.payload = reinterpret_cast(ptr);
  |    ^~
../3rdparty/javascriptcore/JavaScriptCore/runtime/JSValue.h: In 
constructor ‘QTJSC::JSValue::JSValue(const QTJSC::JSCell*)’:
../3rdparty/javascriptcore/JavaScriptCore/runtime/JSValue.h:505:28: 
error: cast from ‘QTJSC::JSCell*’ to ‘int32_t’ {aka ‘int’} loses 
precision [-fpermissive]
  505 | u.asBits.payload = 
reinterpret_cast(const_cast(ptr));

  | ^~~
g++ -c -include .pch/Qt5Script -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-fno-strict-aliasing -Wall -Wreturn-type -Wcast-align -Wchar-subscripts 
-Wformat-security -Wreturn-type -Wno-unused-parameter -Wno-sign-compare 
-Wno-switch -Wno-switch-enum -Wundef -Wmissing-noreturn -Winit-self 
-fno-stack-protector -g -O2 
-ffile-prefix-map=/home/loongson/songd/qt/qtscript-opensource-src/qtscript-opensource-src-5.15.10+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++1y 
-fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions 
-D_REENTRANT -fPIC -DQT_NO_LINKED_LIST -DQT_NO_FOREACH 
-DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_LINKED_LIST -DJSC=QTJSC 
-Djscyyparse=qtjscyyparse -Djscyylex=qtjscyylex 
-Djscyyerror=qtjscyyerror -DWTF=QTWTF -DQT_NO_USING_NAMESPACE 
-DQLALR_NO_QSCRIPTGRAMMAR_DEBUG_INFO -DBUILDING_QT__=1 
-DWTF_USE_ACCELERATED_COMPOSITING -DNDEBUG -DLOG_DISABLED=1 
-DBUILDING_QT__ -DBUILDING_JavaScriptCore -DBUILDING_WTF 
-DWTF_USE_JAVASCRIPTCORE_BINDINGS=1 -DWTF_CHANGES=1 -DJS_NO_EXPORT 
-DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_BUILD_SCRIPT_LIB 
-DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS 
-DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS 
-DQT_DISABLE_DEPRECATED_BEFORE=0x05 
-DQT_DEPRECATED_WARNINGS_SINCE=0x06 -DQT_NO_EXCEPTIONS 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB 
-I. -I../3rdparty/javascriptcore/JavaScriptCore 
-I../3rdparty/javascriptcore 
-I../3rdparty/javascriptcore/JavaScriptCore/assembler 
-I../3rdparty/javascriptcore/JavaScriptCore/bytecode 
-I../3rdparty/javascriptcore/JavaScriptCore/bytecompiler 
-I../3rdparty/javascriptcore/JavaScriptCore/debugger 
-I../3rdparty/javascriptcore/JavaScriptCore/interpreter 
-I../3rdparty/javascriptcore/JavaScriptCore/jit 
-I../3rdparty/javascriptcore/JavaScriptCore/parser 
-I../3rdparty/javascriptcore/JavaScriptCore/pcre 
-I../3rdparty/javascriptcore/JavaScriptCore/profiler 
-I../3rdparty/javascriptcore/JavaScriptCore/runtime 
-I../3rdparty/javascriptcore/JavaScriptCore/wrec 
-I../3rdparty/javascriptcore/JavaScriptCore/wtf 
-I../3rdparty/javascriptcore/JavaScriptCore/wtf/symbian 
-I../3rdparty/javascriptcore/JavaScriptCore/wtf/unicode 
-I../3rdparty/javascriptcore/JavaScriptCore/yarr 
-I../3rdparty/javascriptcore/JavaScriptCore/API 
-I../3rdparty/javascriptcore/JavaScriptCore/ForwardingHeaders 

Bug#1064338: RFS: ukui-search/4.0.6.1-1 [ITP] -- User-wide desktop search of ukui

[xibowen]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "ukui-search":

 * Package name : ukui-search
   Version  : 4.0.6.1-1
   Upstream contact : zhangpengfei 
 * URL  : https://gitee.com/openkylin/ukui-search
 * License  : Expat, GPL-3+, BSD-2-clause, NTP, BSD-3-clause, GPL-2+
 * Vcs  : https://gitee.com/openkylin/ukui-search
   Section  : utils

The source builds the following binary packages:

  ukui-search - User-wide desktop search of ukui
  ukui-search-service - Data service for search function in UKUI desktop 
environment
  libchinese-segmentation1 - Libraries for natural language processing
  libchinese-segmentation-common - Extra files for libchinese-segmentation1
  libchinese-segmentation-dev - Development file for natural language processing
  libukui-search2 - Libraries for ukui-search
  libukui-search-common - Extra files for libukui-search
  libukui-search-dev - Development file  for ukui-search
  ukui-search-systemdbus - Systembus interface for ukui-search-service

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

  https://mentors.debian.net/package/ukui-search/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/u/ukui-search/ukui-search_4.0.6.1-1.dsc

Changes for the initial release:

 ukui-search (4.0.6.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1062977)

This package is depended on ukui-menu and ukui-notification-deamon.

Regards,
-- 
  xibowen

Bug#1052138: RFS: ukui-kwin/5.27.5-1 [ITP] -- UKUI window manager gl utils library

[MouseZhang]

Hi,

Thanks for your inquiry regarding the package.

> * Which version of the original kwin is used?
Based on version 5.27.5 of the original kwin.

> * What is missing from the original kwin and why is a fork needed?
The decision to fork the original kwin was driven by specific needs and 
requirements that were not fully met by the original project.
This fork allows us to tailor the window manager more closely to our specific 
features within the UKUI environment.
1. Tablet Mode Support: We have incorporated support for the UKUI tablet mode, 
which differs from the existing tablet mode mechanism in KWin. Therefore, 
corresponding modifications are required to adapt to our desktop environment.
2. Virtual Keyboard: We have developed a virtual keyboard, but the current 
window layering in KWin does not fully meet our needs. Particularly, when using 
the virtual keyboard for text input, pop-up windows such as QCompleter often 
obscure the virtual keyboard. To address this issue, we need to add a new 
window layer to ensure that the virtual keyboard always displays above popup 
windows.
3. Custom Protocols: To fulfill the application requirements in the UKUI 
environment, we have added or modified certain protocols, such as the blur 
effect with gradual intensity changes.
4. Window Snapping Functionality: We have implemented a window snapping feature 
similar to that in Windows 11, which allows users to manage windows more 
efficiently.
5. Global Gestures: We have replaced the original edge gestures in KWin with 
global gestures, such as using a four-finger swipe to invoke search.
6. Dependency Management: We aim to release UKUI without some of the 
dependencies associated with the Plasma desktop environment, while still using 
KWin as our window manager and Wayland compositor.
7. X11 Support: We require continued support for X11 and plan to develop new 
features to ensure flexibility and compatibility of UKUI across various systems.

> * What changes have been made based on the original kwin?
Currently, ukui-kwin only replaces the name and does not conflict with the 
original kwin.
In order to meet the Ubuntu DebianImportFreeze deadline, we hope to first 
introduce ukui-kwin into the Debian repository and then proceed with 
functionality transplantation. The existing kwin repository used by the UKUI 
desktop environment is located at https://gitee.com/openkylin/kwin, which 
includes the aforementioned functionality. However, this conflicts with the 
original kwin, so we need to fork ukui-kwin. Subsequently, the functionality 
will be transplanted into UKUI-Kwin (https://gitee.com/openkylin/ukui-kwin).

Bug#1064337: samba: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: samba
Version: 2:4.20.0~rc2+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 samba
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 samba 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.

This NMU has not been uploaded to experimental yet because it is waiting on
an update of the binary package override database from the ftp team for
libsmbclient, which was late identified as a package name requiring special
handling.

If you have any concerns about this patch, please reach out ASAP.  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.

-- 
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
diff -Nru samba-4.20.0~rc2+dfsg/debian/changelog 
samba-4.20.0~rc2+dfsg/debian/changelog
--- samba-4.20.0~rc2+dfsg/debian/changelog  2024-02-15 12:05:46.0 
-0800
+++ samba-4.20.0~rc2+dfsg/debian/changelog  2024-02-19 21:48:09.0 
-0800
@@ -1,3 +1,12 @@
+samba (2:4.20.0~rc2+dfsg-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+  * Add Breaks: from samba-libs to sssd, to provide a transition for this
+package which lacks a typical runtime library package name.
+
+ -- Steve Langasek   Tue, 20 Feb 2024 05:48:09 +
+
 samba (2:4.20.0~rc2+dfsg-1) experimental; urgency=medium
 
   * new upstream release candidate (4.20.0-rc2)
diff -Nru samba-4.20.0~rc2+dfsg/debian/control 
samba-4.20.0~rc2+dfsg/debian/control
--- samba-4.20.0~rc2+dfsg/debian/control2024-02-15 11:59:22.0 
-0800
+++ samba-4.20.0~rc2+dfsg/debian/control2024-02-19 19:55:43.0 
-0800
@@ -144,6 +144,9 @@
 Breaks:
  libwbclient0 (<< 2:4.16.1+dfsg-7~),
  samba (<< 2:4.17.0+dfsg-2~),
+ sssd-ad (<< 2.9.4-1+b1),
+ sssd-ad-common (<< 2.9.4-1+b1),
+ sssd-ipa (<< 2.9.4-1+b1),
 Description: Samba core libraries
  Samba is an implementation of the SMB/CIFS protocol for Unix systems,
  providing support for cross-platform file sharing with Microsoft Windows, OS 
X,
@@ -190,7 +193,7 @@
  .
  This package contains the common files that are used by both the server
  (provided in the samba package) and the client (provided in the smbclient
- libsmbclient packages).
+ libsmbclient0 packages).
 
 Package: samba-ad-dc
 Architecture: all
@@ -333,7 +336,7 @@
  ${ldb:Depends},
  ${misc:Depends},
  ${shlibs:Depends}
-Enhances: libldb2
+Enhances: libldb2t64
 Description: Samba Directory Services Database
  Samba is an implementation of the SMB/CIFS protocol for Unix systems,
  providing support for cross-platform file sharing with Microsoft Windows, OS 
X,
@@ -370,7 +373,10 @@
  Note: The runtime dependencies of vfs_ceph, vfs_glusterfs and vfs_snapper are
  moved to Recommends.
 
-Package: libsmbclient
+Package: libsmbclient0
+Provides: ${t64:Provides}
+Replaces: libsmbclient
+Breaks: libsmbclient (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -385,10 +391,10 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libsmbclient (= ${binary:Version}), ${misc:Depends}
-Description: development files for libsmbclient
+Depends: libsmbclient0 (= ${binary:Version}), ${misc:Depends}
+Description: development files for libsmbclient0
  This package provides the development files (static library and headers)
- required for building applications against libsmbclient, a library that
+ required for building applications against libsmbclient0, a library that
  enables client applications to talk 

Bug#1064336: python3.12: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: python3.12
Version: 3.12.2-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
python3.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 python3.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')
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 python3.12-3.12.2/debian/changelog python3.12-3.12.2/debian/changelog
--- python3.12-3.12.2/debian/changelog  2024-02-07 12:47:03.0 -0800
+++ python3.12-3.12.2/debian/changelog  2024-02-19 17:00:02.0 -0800
@@ -1,3 +1,10 @@
+python3.12 (3.12.2-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Tue, 20 Feb 2024 01:00:02 +
+
 python3.12 (3.12.2-1) unstable; urgency=medium
 
   * Python 3.12.2 release.
diff -Nru python3.12-3.12.2/debian/control python3.12-3.12.2/debian/control
--- python3.12-3.12.2/debian/control2023-12-08 11:28:58.0 -0800
+++ python3.12-3.12.2/debian/control2024-02-19 17:00:02.0 -0800
@@ -116,7 +116,10 @@
  This package contains some essential modules. It is normally not
  used on it's own, but as a dependency of python3.12-minimal.
 
-Package: libpython3.12
+Package: libpython3.12t64
+Provides: ${t64:Provides}
+Replaces: libpython3.12
+Breaks: libpython3.12 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -234,14 +237,15 @@
  .
  See the README.debug for more information.
 
-Package: libpython3.12-dbg
+Package: libpython3.12t64-dbg
+Provides: ${t64:Provides}
 Section: debug
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libpython3.12-stdlib (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}
-Breaks: python3-gdbm-dbg (<< 3.9.9-1~)
-Replaces: python3-gdbm-dbg (<< 3.9.9-1~)
+Breaks: libpython3.12-dbg (<< ${source:Version}), python3-gdbm-dbg (<< 
3.9.9-1~)
+Replaces: libpython3.12-dbg, python3-gdbm-dbg (<< 3.9.9-1~)
 Description: Debug Build of the Python Interpreter (version 3.12)
  The package holds two things:
  .
diff -Nru python3.12-3.12.2/debian/control.in 
python3.12-3.12.2/debian/control.in
--- python3.12-3.12.2/debian/control.in 2023-12-08 11:28:48.0 -0800
+++ python3.12-3.12.2/debian/control.in 2024-02-19 16:59:50.0 -0800
@@ -116,7 +116,10 @@
  This package contains some essential modules. It is normally not
  used on it's own, but as a dependency of @PVER@-minimal.
 
-Package: lib@PVER@
+Package: lib@PVER@t64
+Provides: ${t64:Provides}
+Replaces: lib@PVER@
+Breaks: lib@PVER@ (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -234,14 +237,15 @@
  .
  See the README.debug for more information.
 
-Package: lib@PVER@-dbg
+Package: lib@PVER@t64-dbg
+Provides: ${t64:Provides}
 Section: debug
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: lib@PVER@-stdlib (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}
-Breaks: python3-gdbm-dbg (<< 3.9.9-1~)
-Replaces: python3-gdbm-dbg (<< 3.9.9-1~)
+Breaks: lib@PVER@-dbg (<< ${source:Version}), python3-gdbm-dbg (<< 3.9.9-1~)
+Replaces: lib@PVER@-dbg, python3-gdbm-dbg (<< 3.9.9-1~)
 Description: Debug Build of the 

Bug#1058740: gtk4,librsvg: big-endian support is at risk of being removed

[Gayathri Berli]

Gentle Reminder...!

Thanks,
Gayathri.

Bug#1056354: python3-hinawa-utils depends on cruft gir1.2-hinawa-3.0

[Kentaro HAYASHI]

Control: fixed -1 0.4.0-1

This bug was fixed in hinawa-utils 0.4.0-1.


On Tue, 21 Nov 2023 17:09:35
+0200 Adrian Bunk  wrote:
> Package: python3-hinawa-utils
> Version: 0.3.0-3
> Severity: serious
> 
> src:libhinawa now builds gir1.2-hinawa-4.0 instead of
> gir1.2-hinawa-3.0
> 
> 

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

[Vladimir Petko]

Hi,

Thank you!!!

I will prepare the patch for Ubuntu stable releases/i386 and update the bug.

Best Regards,
 Vladimir.

Bug#1064333: passenger's autopkg tests fail with Python 3.12

[Matthias Klose]

Package: src:passenger
Version: 6.0.17+ds-1
Severity: important
Tags: sid trixie ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

this is fixed in upstream 6.0.20. I pulled these changes into the 6.0.17 
package. See

https://launchpadlibrarian.net/715180401/passenger_6.0.17+ds-1build2_6.0.17+ds-1ubuntu1.diff.gz

Bug#1064332: petsc: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: petsc
Version: 3.19.6+dfsg1-2
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
petsc 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 petsc
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 petsc-3.19.6+dfsg1/debian/changelog 
petsc-3.19.6+dfsg1/debian/changelog
--- petsc-3.19.6+dfsg1/debian/changelog 2024-01-21 06:41:21.0 +
+++ petsc-3.19.6+dfsg1/debian/changelog 2024-02-20 01:26:36.0 +
@@ -1,3 +1,10 @@
+petsc (3.19.6+dfsg1-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Tue, 20 Feb 2024 01:26:36 +
+
 petsc (3.19.6+dfsg1-2) unstable; urgency=medium
 
   * Update debian/patches/soname_extension to also add a define PETSC_LIB_EXT,
diff -Nru petsc-3.19.6+dfsg1/debian/control petsc-3.19.6+dfsg1/debian/control
--- petsc-3.19.6+dfsg1/debian/control   2024-01-21 06:41:21.0 +
+++ petsc-3.19.6+dfsg1/debian/control   2024-02-20 01:26:36.0 +
@@ -86,7 +86,7 @@
 Multi-Arch: same
 Architecture: any
 Section: libdevel
-Depends: libpetsc-real3.19 (= ${binary:Version}),
+Depends: libpetsc-real3.19t64 (= ${binary:Version}),
  libpetsc3.19-dev-common (= ${source:Version}),
  ${MPI:Depends},
  libhypre-dev (>= 2.15.1),
@@ -99,7 +99,7 @@
 Conflicts: libpetsc3.6.3-dev (<< 3.6.3.dfsg2-2), libpetsc-complex-3.6.3-dev 
(<< 3.6.3.dfsg2-2),
  libpetsc3.6.2-dev (<= 3.6.2.dfsg1-3), libpetsc-complex-3.6.2-dev (<= 
3.6.2.dfsg1-3)
 Recommends: libpetsc3.19-dev-examples, ksh | mksh | pdksh | zsh
-Suggests: petsc-dev, libpetsc-real3.19-dbg (= ${binary:Version}), 
petsc3.19-doc, libluminate-dev
+Suggests: petsc-dev, libpetsc-real3.19t64-dbg (= ${binary:Version}), 
petsc3.19-doc, libluminate-dev
 Description: Static libraries, shared links, header files for PETSc
  PETSc is the "Portable Extensible Toolkit for Scientific
  Computation", a suite of data structures and routines for the
@@ -112,16 +112,17 @@
  This package provides the development files for building applications
  using PETSc 3.19 with real numbers.
 
-Package: libpetsc-real3.19
+Package: libpetsc-real3.19t64
 Architecture: any
 Multi-Arch: same
 Section: libs
-Provides: libpetsc3.19
+X-Time64-Compat: libpetsc-complex3.19-dbg
+Provides: ${t64:Provides}, libpetsc3.19
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libpetsc3.6 (<< 3.6.2.dfsg1-4)
-Breaks: libpetsc-real3.10, libslepc-real3.10, libpetsc3.10-dev-common, 
libpetsc3.10-dev-examples
-Replaces: libpetsc3.6 (<< 3.6.2.dfsg1-4)
+Breaks: libpetsc-real3.19 (<< ${source:Version}), libpetsc-real3.10, 
libslepc-real3.10, libpetsc3.10-dev-common, libpetsc3.10-dev-examples
+Replaces: libpetsc-real3.19, libpetsc3.6 (<< 3.6.2.dfsg1-4)
 Description: Shared libraries for version 3.19 of PETSc
  PETSc is the "Portable Extensible Toolkit for Scientific
  Computation", a suite of data structures and routines for the
@@ -133,7 +134,7 @@
  .
  This package contains the PETSc 3.19 shared library for real numbers.
  .
- It provides soname libpetsc-real3.19
+ It provides soname libpetsc-real3.19t64
 
 

Bug#1064331: nodejs: FTBFS on riscv64: some test cases faileder: debian-riscv@lists.debian.orgertags: riscv64

[Bo YU]

Tags: ftbfs patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

On Tue, Feb 20, 2024 at 10:57:35AM +0800, Bo YU wrote:

Package: nodejs
Version: 18.19.1+dfsg-1
Severity: important

Dear Maintainer,

Nodejs 18.19.1+dfsg-1 has a ftbfs issue due to some test cases failed:

```
...
Failed tests:
./node /<>/test/parallel/test-runner-output.mjs
./node /<>/test/sequential/test-cpu-prof-dir-and-name.js
./node /<>/test/sequential/test-cpu-prof-name.js
...
```

Full buildd log see here:
https://buildd.debian.org/status/fetch.php?pkg=nodejs=riscv64=18.19.1%2Bdfsg-1=1708327149=0

I have flaged these tests with flaky status and confirmed it works.

So could we apply it on next upload?

BTW, there is some tests failed on mips64el, but I have no mips64el
machine to confirm if flag these tests with flaky is okay or not like on
riscv64. See #1064306.

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

--
Regards,
--
 Bo YU




diff -Nru nodejs-18.19.1+dfsg/debian/changelog 
nodejs-18.19.1+dfsg/debian/changelog
--- nodejs-18.19.1+dfsg/debian/changelog2024-02-19 01:12:23.0 
+0800
+++ nodejs-18.19.1+dfsg/debian/changelog2024-02-19 18:34:13.0 
+0800
@@ -1,3 +1,10 @@
+nodejs (18.19.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update riscv patch to fix ftbfs issue. (Closes: #-1)
+
+ -- Bo YU   Mon, 19 Feb 2024 18:34:13 +0800
+
nodejs (18.19.1+dfsg-1) unstable; urgency=medium

  * New upstream version 18.19.1. Closes: 1064055.
diff -Nru nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch 
nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch
--- nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch  2024-02-15 
06:11:51.0 +0800
+++ nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch  2024-02-19 
18:25:42.0 +0800
@@ -3,9 +3,11 @@
Author: J�r�my Lal , Bo YU 
Forwarded: not-yet

 a/test/sequential/sequential.status
-+++ b/test/sequential/sequential.status
-@@ -65,3 +65,19 @@
+Index: nodejs-18.19.1+dfsg/test/sequential/sequential.status
+===
+--- nodejs-18.19.1+dfsg.orig/test/sequential/sequential.status
 nodejs-18.19.1+dfsg/test/sequential/sequential.status
+@@ -65,3 +65,21 @@ test-watch-mode-inspect: PASS, FLAKY
 [$arch==s390x]
 # https://github.com/nodejs/node/issues/41286
 test-performance-eventloopdelay: PASS, FLAKY
@@ -13,8 +15,10 @@
+[$arch==riscv64]
+test-diagnostic-dir-cpu-prof: PASS, FLAKY
+test-cpu-prof-worker-argv: PASS, FLAKY
++test-cpu-prof-dir-and-name: PASS, FLAKY
+test-cpu-prof-exit: PASS, FLAKY
+test-cpu-prof-kill: PASS, FLAKY
++test-cpu-prof-name: PASS, FLAKY
+test-diagnostic-dir-cpu-prof: PASS, FLAKY
+test-debugger-auto-resume: PASS, FLAKY
+test-debugger-preserve-breaks: PASS, FLAKY
@@ -25,9 +29,11 @@
+test-cpu-prof-dir-absolute: PASS, FLAKY
+
+
 a/test/parallel/parallel.status
-+++ b/test/parallel/parallel.status
-@@ -150,6 +150,22 @@
+Index: nodejs-18.19.1+dfsg/test/parallel/parallel.status
+===
+--- nodejs-18.19.1+dfsg.orig/test/parallel/parallel.status
 nodejs-18.19.1+dfsg/test/parallel/parallel.status
+@@ -150,6 +150,23 @@ test-tls-write-error: PASS, FLAKY
 # https://github.com/nodejs/node/issues/48047
 test-http-pipeline-flood: SKIP

@@ -35,6 +41,7 @@
+test-fetch: PASS, FLAKY
+test-net-socket-connect-without-cb: PASS, FLAKY
+test-runner-inspect: PASS, FLAKY
++test-runner-output: PASS, FLAKY
+test-tcp-wrap-listen: PASS, FLAKY
+test-wasm-web-api: PASS, FLAKY
+test-vm-timeout-escape-promise-module: PASS, FLAKY





--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1064331: nodejs: FTBFS on riscv64: some test cases failed

[Bo YU]

Package: nodejs
Version: 18.19.1+dfsg-1
Severity: important

Dear Maintainer,

Nodejs 18.19.1+dfsg-1 has a ftbfs issue due to some test cases failed:

```
...
Failed tests:
./node /<>/test/parallel/test-runner-output.mjs
./node /<>/test/sequential/test-cpu-prof-dir-and-name.js
./node /<>/test/sequential/test-cpu-prof-name.js
...
```

Full buildd log see here:
https://buildd.debian.org/status/fetch.php?pkg=nodejs=riscv64=18.19.1%2Bdfsg-1=1708327149=0

I have flaged these tests with flaky status and confirmed it works.

So could we apply it on next upload?

BTW, there is some tests failed on mips64el, but I have no mips64el
machine to confirm if flag these tests with flaky is okay or not like on
riscv64. See #1064306.

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

-- 
Regards,
--
  Bo YU

diff -Nru nodejs-18.19.1+dfsg/debian/changelog 
nodejs-18.19.1+dfsg/debian/changelog
--- nodejs-18.19.1+dfsg/debian/changelog2024-02-19 01:12:23.0 
+0800
+++ nodejs-18.19.1+dfsg/debian/changelog2024-02-19 18:34:13.0 
+0800
@@ -1,3 +1,10 @@
+nodejs (18.19.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update riscv patch to fix ftbfs issue. (Closes: #-1)
+
+ -- Bo YU   Mon, 19 Feb 2024 18:34:13 +0800
+
 nodejs (18.19.1+dfsg-1) unstable; urgency=medium
 
   * New upstream version 18.19.1. Closes: 1064055.
diff -Nru nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch 
nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch
--- nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch  2024-02-15 
06:11:51.0 +0800
+++ nodejs-18.19.1+dfsg/debian/patches/riscv/flaky_tests.patch  2024-02-19 
18:25:42.0 +0800
@@ -3,9 +3,11 @@
 Author: Jérémy Lal , Bo YU 
 Forwarded: not-yet
 
 a/test/sequential/sequential.status
-+++ b/test/sequential/sequential.status
-@@ -65,3 +65,19 @@
+Index: nodejs-18.19.1+dfsg/test/sequential/sequential.status
+===
+--- nodejs-18.19.1+dfsg.orig/test/sequential/sequential.status
 nodejs-18.19.1+dfsg/test/sequential/sequential.status
+@@ -65,3 +65,21 @@ test-watch-mode-inspect: PASS, FLAKY
  [$arch==s390x]
  # https://github.com/nodejs/node/issues/41286
  test-performance-eventloopdelay: PASS, FLAKY
@@ -13,8 +15,10 @@
 +[$arch==riscv64]
 +test-diagnostic-dir-cpu-prof: PASS, FLAKY
 +test-cpu-prof-worker-argv: PASS, FLAKY
++test-cpu-prof-dir-and-name: PASS, FLAKY
 +test-cpu-prof-exit: PASS, FLAKY
 +test-cpu-prof-kill: PASS, FLAKY
++test-cpu-prof-name: PASS, FLAKY
 +test-diagnostic-dir-cpu-prof: PASS, FLAKY
 +test-debugger-auto-resume: PASS, FLAKY
 +test-debugger-preserve-breaks: PASS, FLAKY
@@ -25,9 +29,11 @@
 +test-cpu-prof-dir-absolute: PASS, FLAKY
 +
 +
 a/test/parallel/parallel.status
-+++ b/test/parallel/parallel.status
-@@ -150,6 +150,22 @@
+Index: nodejs-18.19.1+dfsg/test/parallel/parallel.status
+===
+--- nodejs-18.19.1+dfsg.orig/test/parallel/parallel.status
 nodejs-18.19.1+dfsg/test/parallel/parallel.status
+@@ -150,6 +150,23 @@ test-tls-write-error: PASS, FLAKY
  # https://github.com/nodejs/node/issues/48047
  test-http-pipeline-flood: SKIP
  
@@ -35,6 +41,7 @@
 +test-fetch: PASS, FLAKY
 +test-net-socket-connect-without-cb: PASS, FLAKY
 +test-runner-inspect: PASS, FLAKY
++test-runner-output: PASS, FLAKY
 +test-tcp-wrap-listen: PASS, FLAKY
 +test-wasm-web-api: PASS, FLAKY
 +test-vm-timeout-escape-promise-module: PASS, FLAKY


signature.asc
Description: PGP signature

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

[Chao Yu]

On 2024/2/20 3:54, Salvatore Bonaccorso wrote:

Hi,

On Mon, Feb 19, 2024 at 10:35:13AM +0800, Chao Yu wrote:

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


Confirmed that this fixes the reported issue as it was reported to us
in Debian in https://bugs.debian.org/1063422 . Thanks a lot!
(note just tested with the first commit as it landed in 6.1.78 to
confirm the immediate regression).

#regzbot fixed-by: cf3d57ad6ff8b566deba3544b9ad3384781fb604


Hi,

Thank you for confirmation.

Thanks,



Regards,
Salvatore

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

[Thorsten Glaser]

Hi Vladimir,

>Would it be possible to consider the alternative approach: add
>"do-not-throw-when-accesisibility-provider-not-found" patch on i386 in
>line with openjdk-11 +?

Sounds like a plan. For Ubuntu only, then?

>I had a chat on #ubuntu-release indicating that there is a little
>chance for me to argue for including the bridge into stable releases on
>i386.

OK.

>I can prepare this patch.

That would be great if you have the time.

Thanks,
//mirabilos
-- 
 exceptions: a truly awful implementation of quite a nice idea.
 just about the worst way you could do something like that, afaic.
 it's like anti-design.   that too… may I quote you on that?
 sure, tho i doubt anyone will listen ;)

Bug#1063302: libsingular4-dev: libsingular renders sagemath unusable

[Alexandre Lymberopoulos]

Thanks, Doug!

Hope this is fixed soon. My first guess is to call the installed version 
of singular and then see what happens. Sage team: if I can help in some 
way, just tell me.


Best, Alexandre

Em 19/02/2024 08:50, Torrance, Douglas escreveu:

Control: reassign -1 sagemath 9.5-6
Control: severity 1052051 grave
Control: merge -1 1052051

On Tue 06 Feb 2024 12:18:06 AM -03, Alexandre Lymberopoulos 
 wrote:

Package: libsingular4-dev
Version: 1:4.3.2-p10+ds-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

It seems that this version of the package (or other on the 
libsingular4 family) renders sagemath completelu unusable. In other 
systems, with the an older version of libsingular4* (4.3.1, if my 
memory isn't cheating me), sage runs perfectly.


Below is an output of sagemath running from the prompt:

~$ sage
┌┐
│ SageMath version 9.5, Release Date: 2022-01-30 │
│ Using Python 3.11.7. Type "help()" for help.   │
└┘
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3.11/pathlib.py", line 1251, in is_dir
    return S_ISDIR(self.stat().st_mode)
   ^

AttributeError: 'str' object has no attribute 'stat'
Original exception was:
Traceback (most recent call last):
  File "/usr/bin/sage-ipython", line 15, in 
    app.initialize()
  File 
"/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
110, in inner

    return method(app, *args, **kwargs)
   
  File "/usr/lib/python3/dist-packages/IPython/terminal/ipapp.py", 
line 278, in initialize

    self.init_shell()
  File "/usr/lib/python3/dist-packages/sage/repl/interpreter.py", line 
789, in init_shell

    self.shell.extension_manager.load_extension(SAGE_EXTENSION)
  File "/usr/lib/python3/dist-packages/IPython/core/extensions.py", 
line 76, in load_extension

    return self._load_extension(module_str)
   
  File "/usr/lib/python3/dist-packages/IPython/core/extensions.py", 
line 93, in _load_extension

    if self._call_load_ipython_extension(mod):
   ^^
  File "/usr/lib/python3/dist-packages/IPython/core/extensions.py", 
line 145, in _call_load_ipython_extension

    mod.load_ipython_extension(self.shell)
  File "/usr/lib/python3/dist-packages/sage/repl/__init__.py", line 5, 
in load_ipython_extension

    sage.repl.ipython_extension.load_ipython_extension(*args)
  File 
"/usr/lib/python3/dist-packages/sage/repl/ipython_extension.py", line 
617, in wrapper

    result = func(*args, **kwargs)
 ^
  File 
"/usr/lib/python3/dist-packages/sage/repl/ipython_extension.py", line 
630, in load_ipython_extension

    SageCustomizations(shell=ip)
  File 
"/usr/lib/python3/dist-packages/sage/repl/ipython_extension.py", line 
434, in __init__

    import sage.all # until sage's import hell is fixed
    ^^^
  File "/usr/lib/python3/dist-packages/sage/all.py", line 169, in 


    from sage.rings.all  import *
  File "/usr/lib/python3/dist-packages/sage/rings/all.py", line 87, in 


    from .qqbar import (AlgebraicRealField, AA,
  File "/usr/lib/python3/dist-packages/sage/rings/qqbar.py", line 
2810, in 

    QQxy = QQ['x', 'y']
   ~~^^
  File "sage/structure/parent.pyx", line 1276, in 
sage.structure.parent.Parent.__getitem__ 
(build/cythonized/sage/structure/parent.c:11543)
  File "/usr/lib/python3/dist-packages/sage/categories/rings.py", line 
1177, in __getitem__

    return PolynomialRing(self, elts)
   ^^
  File 
"/usr/lib/python3/dist-packages/sage/rings/polynomial/polynomial_ring_constructor.py", line 647, in PolynomialRing

    return _multi_variate(base_ring, names, **kwds)
   
  File 
"/usr/lib/python3/dist-packages/sage/rings/polynomial/polynomial_ring_constructor.py", line 775, in _multi_variate
    from sage.rings.polynomial.multi_polynomial_libsingular import 
MPolynomialRing_libsingular
ImportError: libsingular-Singular-4.3.1.so: cannot open shared object 
file: No such file or directory


It seems that sage calls previous version (4.3.1) of libsingular. I 
reported this bug before to sagemath package, but got no answer. I'let 
this filed here and report again on sage.


I may provide any further information needed to fix this.

Best, Alexandre

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

Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

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

Versions of 

Bug#682397: darktable: recommend opencl package

[David Bremner]

Tino Mettler via Pkg-phototools-devel
 writes:

>
> This is a general issue that the darktable package can not change.  So
> I propose to close this bug.
>
> Regards,
> Tino

I wonder if having the bug helps people see that there is no point in
filing more bugs on the same topic. I guess we can always leave the next
OpenCL bug open if that occurs.

Bug#1064330: efl: NMU diff for 64-bit time_t transition

[mwhudson]

Source: efl
Version: 1.27.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
efl 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 efl
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru efl-1.27.0/debian/changelog efl-1.27.0/debian/changelog
--- efl-1.27.0/debian/changelog 2024-01-03 05:36:10.0 +
+++ efl-1.27.0/debian/changelog 2024-02-20 01:04:28.0 +
@@ -1,3 +1,10 @@
+efl (1.27.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle   Tue, 20 Feb 2024 01:04:28 +
+
 efl (1.27.0-1) unstable; urgency=medium
 
   * Bump symbol versions for 1.27.0 release
diff -Nru efl-1.27.0/debian/control efl-1.27.0/debian/control
--- efl-1.27.0/debian/control   2024-01-03 05:34:32.0 +
+++ efl-1.27.0/debian/control   2024-02-20 01:04:28.0 +
@@ -315,7 +315,9 @@
  This package contains the Ecore wrapper and convenience functions for
  audio playback and recording.
 
-Package: libecore-con1
+Package: libecore-con1t64
+Provides: ${t64:Provides}
+Replaces: libecore-con1
 Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
@@ -323,7 +325,7 @@
  libecore-bin (>= ${source:Upstream-Version}),
  ${misc:Depends},
  ${shlibs:Depends},
-Breaks: libeina1a (<< ${source:Upstream-Version})
+Breaks: libecore-con1 (<< ${source:Version}), libeina1a (<< 
${source:Upstream-Version})
 Description: Ecore functions for network connections
  Ecore is a library of convenience functions. It provides abstractions
  for handling timers selections, Xdnd, event loops, and much
@@ -524,7 +526,7 @@
  libcurl4-openssl-dev,
  libdbus-1-dev,
  libecore-audio1 (= ${binary:Version}),
- libecore-con1 (= ${binary:Version}),
+ libecore-con1t64 (= ${binary:Version}),
  libecore-drm2-1 (= ${binary:Version}),
  libecore-evas1 (= ${binary:Version}),
  libecore-fb1 (= ${binary:Version}) [linux-any],
diff -Nru efl-1.27.0/debian/libecore-con1.install 
efl-1.27.0/debian/libecore-con1.install
--- efl-1.27.0/debian/libecore-con1.install 2024-01-03 05:33:48.0 
+
+++ efl-1.27.0/debian/libecore-con1.install 1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/libecore_con.so.*
diff -Nru efl-1.27.0/debian/libecore-con1.lintian-overrides 
efl-1.27.0/debian/libecore-con1.lintian-overrides
--- efl-1.27.0/debian/libecore-con1.lintian-overrides   2024-01-03 
05:33:48.0 +
+++ efl-1.27.0/debian/libecore-con1.lintian-overrides   1970-01-01 
00:00:00.0 +
@@ -1,2 +0,0 @@
-# Symbols generated by eolian; see note in README.source
-libecore-con1: symbols-file-contains-debian-revision
diff -Nru efl-1.27.0/debian/libecore-con1.symbols 
efl-1.27.0/debian/libecore-con1.symbols
--- efl-1.27.0/debian/libecore-con1.symbols 2024-01-03 05:33:48.0 
+
+++ efl-1.27.0/debian/libecore-con1.symbols 1970-01-01 00:00:00.0 
+
@@ -1,524 +0,0 @@
-libecore_con.so.1 libecore-con1 #MINVER#
-* Build-Depends-Package: libefl-all-dev
- ECORE_CON_EVENT_CLIENT_ADD@Base 1.27.0-0~eo
- 

Bug#1052051: sagemath: Confirm this on my installation

[Alexandre Lymberopoulos]

Package: sagemath
Version: 9.5-6
Followup-For: Bug #1052051

Dear Maintainer,

sagemath can't be run here. After many messages, the last one is:

ImportError: libsingular-Singular-4.3.1.so: cannot open shared object file: No 
such file or directory

Maybe it can be fixed by invoking the currently installed version of
libsingular. Or is it more complicated than that?

Best, Alexandre


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

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

Versions of packages sagemath depends on:
ii  python3   3.11.6-1
ii  python3-sage  9.5-6

Versions of packages sagemath recommends:
pn  sagemath-doc
ii  sagemath-jupyter9.5-6
pn  sagetex 
ii  texlive-latex-base  2023.20231207-1

Versions of packages sagemath suggests:
pn  dot2tex  
pn  gap-design   
pn  gap-factint  
pn  gap-grape
pn  gap-guava
pn  gap-laguna   
pn  gap-sonata   
pn  gap-toric

-- no debconf information

Bug#1064329: Micro stuttering when using a DisplayPort. Issue is not present when using HDMI

[Shawn Horvatic]

Package: Gnome
Version: 43.9
XOrg or Wayland: Wayland

*OS Information*

OS: Debian GNU/Linux
Version: 12.2.0-14
Kernel: Linux version 6.1.0-18-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.76-1 (2024-02-01)
Bug summary

When on Discord, Youtube, or any activity while using a DisplayPort as
primary output Gnome will micro-stutter. When a micro stutter occurs the
whole system will replay sounds, video, etc of the previous few frames. For
example Youtube will double play the same note during a micro stutter, or
if someone is speaking in discord their last word will repeat twice. I
tested this with HDMI, and none of these issues occurred.
Steps
to reproduce

   1. Plugin a DisplayPort Cable. This can be integrated, or video card
   2. Fresh install of Debian, selecting the Gnome desktop when installing
   3. In firefox or chrome play a youtube video, as it easy to see the
   stutter
   4. Micro stutter should occur within 5 - 15 mins. The video will repeat
   the last frames / sound


*Suggestions *
Upgrade Gnome to a version that can support Displayport

*Notes / Other Useful Info:*
- Ticket already made with Gnome:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7422
Gnome closed the ticket as Debian uses an unsupported version of Gnome

- KDE has a similar issue, but I have not tested it with HDMI to see if
that fixes the issue

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

[Vladimir Petko]

Hi,

Would it be possible to consider the alternative approach: add
"do-not-throw-when-accesisibility-provider-not-found" patch on i386 in
line with openjdk-11 +? I had a chat on #ubuntu-release indicating
that there is a little chance for me to argue for including the bridge
into stable releases on i386.
I can prepare this patch.

Best Regards,
 Vladimir.

Bug#1063719: More analysis and improved patch

[Bob Proulx]

George Robbert wrote:
> On an intel system, where uCode/AMD.pm was run before uCode/Intel.pm
>
> intel_sys1# needrestart -b
> NEEDRESTART-VER: 3.6
> NEEDRESTART-KCUR: 6.1.0-18-amd64
> NEEDRESTART-KEXP: 6.1.0-18-amd64
> NEEDRESTART-KSTA: 1
> NEEDRESTART-UCSTA: 1
> Use of uninitialized value $ucode_vars{"CURRENT"} in concatenation (.) or 
> string at /usr/sbin/needrestart line 940.
> NEEDRESTART-UCCUR:
> Use of uninitialized value $ucode_vars{"AVAIL"} in concatenation (.) or 
> string at /usr/sbin/needrestart line 941.
> NEEDRESTART-UCEXP:

I have been seeing these exact uninitialized value errors on my
machines too.  Very annoying as I am often using dsh to scan a large
collective of systems and the noise from these errors obscures the
information want to read.

> The attached patch fixes includes the previous patch and also fixes
> these 2 issues.

I have applied this second patch from George on my systems both Stable
and Unstable and it has solved the uninitialized value errors for me.
I saw no problems patching or running.  It is oh so very nice not to
be seeing those uninitialized value errors.

Example on an Debian Unstable Sid system.

root@clash:/# needrestart -b
NEEDRESTART-VER: 3.6
NEEDRESTART-KCUR: 6.4.0-4-amd64
NEEDRESTART-KEXP: 6.4.0-4-amd64
NEEDRESTART-KSTA: 1
NEEDRESTART-UCSTA: 1
Use of uninitialized value $ucode_vars{"CURRENT"} in concatenation (.) or 
string at /usr/sbin/needrestart line 940.
NEEDRESTART-UCCUR:
Use of uninitialized value $ucode_vars{"AVAIL"} in concatenation (.) or 
string at /usr/sbin/needrestart line 941.
NEEDRESTART-UCEXP:

root@clash:/# patch -p0 < /var/tmp/needrestart-ghr-2.patch
patching file /usr/share/perl5/NeedRestart/uCode.pm
Hunk #2 succeeded at 179 with fuzz 1.

root@clash:/# needrestart -b
NEEDRESTART-VER: 3.6
NEEDRESTART-KCUR: 6.4.0-4-amd64
NEEDRESTART-KEXP: 6.4.0-4-amd64
NEEDRESTART-KSTA: 1
NEEDRESTART-UCSTA: 0

Looks good to me! :-)

Bob

Bug#1063897: firefox: poor performance compared to vendor package

[Jeremy Davis]

Hi Laurent - and bug list,

On 20/2/24 02:26, Laurent Bigonville wrote:


AFACS, the packages provided by mozilla are only 
nightly/devedition/beta, but there is no stable release with the 
optimizations, or am I overlooking something?


I can confirm that the latest stable[1] is available via the Mozilla 
Debian apt repo[2]. nightly/devedition/beta builds are also available 
via the same repo for those that are interested.


[1] https://www.mozilla.org/en-US/firefox/122.0.1/releasenotes/
[2] 
https://support.mozilla.org/en-US/kb/install-firefox-linux#w_install-firefox-deb-package-for-debian-based-distributions


I.e.:

user@laptop ~$ apt policy firefox
firefox:
  Installed: (none)
  Candidate: 122.0.1~build1
  Version table:
 122.0.1~build1 900
900 https://packages.mozilla.org/apt mozilla/main amd64 Packages
 122.0~build2 900
900 https://packages.mozilla.org/apt mozilla/main amd64 Packages

FWIW obviously I haven't (yet) installed the latest upstream stable - 
but plan to in the near future.


Regards,
Jeremy


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064177: mozjs115: NMU diff for 64-bit time_t transition

[Jeremy Bícha]

Control: tags -1 -pending

On Sat, Feb 17, 2024 at 10:24 PM Steve Langasek  wrote:
> 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 mozjs115
> which will initially be uploaded to experimental if possible, then to
> unstable after packages have cleared binary NEW.

The NMU was automatically rejected because it was older than the
version currently in Unstable. I have uploaded mozjs115_115.8.0-2~exp1
to Experimental for you.

I can do the upload to Unstable when ready so I'm unsetting the pending tag.

Thank you,
Jeremy Bícha

Bug#1053923: Acknowledgement (gnome-keyring: After upgrade to Bookworm gnome-keyring-daemon shuts down and does not restart correctly)

[Nate Bargmann]

I do think this can be closed.  The cause was self inflicted with a cron
entry intended to kill 'rec' with pkill.  The pkill pattern included
'rec' which matched "directory" in the gnome-keyring-daemon command
line.

I offered a more complete write up on the debian-user mailing list:

https://lists.debian.org/debian-user/2024/02/msg00800.html

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Bug#1064328: snort: identified for time_t transition but no ABI in shlibs

[Steve Langasek]

Source: snort
Version: 2.9.15.1-6
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainers,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
snort as an affected package, on the basis that the headers could not be
compiled and analyzed out of the box using abi-compliance-checker[2], so we
have to assume it's affected.

However, snort's shlibs file declares a dependency on a library package name
that contains no ABI information:

$ cat DEBIAN/shlibs
libsf_sorules 0 snort-common-libraries (>= 2.9.15.1)
libsf_engine 0 snort-common-libraries (>= 2.9.15.1)
libsf_appid_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_dce2_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_dnp3_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_dns_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_ftptelnet_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_gtp_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_imap_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_modbus_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_pop_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_reputation_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_sdf_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_sip_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_smtp_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_ssh_preproc 0 snort-common-libraries (>= 2.9.15.1)
libsf_ssl_preproc 0 snort-common-libraries (>= 2.9.15.1)
$

It is not obvious that we should rename the package to
'snort-common-librariest64' as part of this transition.

Looking at the archive, there is a package that depends on this library,
snort.  Despite being built from the same source package, it does not have a
strict versioned dependency on snort-common-libraries but instead uses the
shlibs.

Since there is no self-evident thing to do with the library package name
here, we will not be handling this package as part of the mass NMUs. 
Instead I am filing a serious bug because partial upgrades from bookworm to
trixie on 32-bit architectures (upgrading snort-common-libraries without
also upgrading snort) will result in ABI skew and may result in broken
behavior.

Thanks,
-- 
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

[0] https://wiki.debian.org/ReleaseGoals/64bit-time
[1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
[2] 
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-16T21%3A19%3A00/logs/snort-common-libraries/base/log.txt


signature.asc
Description: PGP signature

Bug#1064327: spatialite: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: spatialite
Version: 5.1.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
spatialite 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 spatialite
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 spatialite-5.1.0/debian/changelog spatialite-5.1.0/debian/changelog
--- spatialite-5.1.0/debian/changelog   2023-08-05 13:52:11.0 +
+++ spatialite-5.1.0/debian/changelog   2024-02-19 23:10:36.0 +
@@ -1,3 +1,10 @@
+spatialite (5.1.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 23:10:36 +
+
 spatialite (5.1.0-1) unstable; urgency=medium
 
   * Move from experimental to unstable.
diff -Nru spatialite-5.1.0/debian/control spatialite-5.1.0/debian/control
--- spatialite-5.1.0/debian/control 2023-08-05 13:51:54.0 +
+++ spatialite-5.1.0/debian/control 2024-02-19 23:10:36.0 +
@@ -23,14 +23,16 @@
 Homepage: https://www.gaia-gis.it/fossil/libspatialite
 Rules-Requires-Root: no
 
-Package: libspatialite8
+Package: libspatialite8t64
+Provides: ${t64:Provides}
+Replaces: libspatialite8
 Architecture: any
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
-Breaks: spatialite-bin (<< 3.0.0-1~)
+Breaks: libspatialite8 (<< ${source:Version}), spatialite-bin (<< 3.0.0-1~)
 Description: Geospatial extension for SQLite - libraries
  The SpatiaLite extension enables SQLite to support spatial (geometry) data
  in a way conformant to OpenGis specifications, with both WKT and WKB formats.
@@ -44,7 +46,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libspatialite8 (= ${binary:Version}),
+Depends: libspatialite8t64 (= ${binary:Version}),
  libfreexl-dev,
  libgeos-dev,
  libminizip-dev,
diff -Nru spatialite-5.1.0/debian/libspatialite8.examples 
spatialite-5.1.0/debian/libspatialite8.examples
--- spatialite-5.1.0/debian/libspatialite8.examples 2023-08-05 
13:51:39.0 +
+++ spatialite-5.1.0/debian/libspatialite8.examples 1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-examples/*.c
diff -Nru spatialite-5.1.0/debian/libspatialite8.install 
spatialite-5.1.0/debian/libspatialite8.install
--- spatialite-5.1.0/debian/libspatialite8.install  2023-08-05 
13:51:39.0 +
+++ spatialite-5.1.0/debian/libspatialite8.install  1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libspatialite.so.*
diff -Nru spatialite-5.1.0/debian/libspatialite8.lintian-overrides 
spatialite-5.1.0/debian/libspatialite8.lintian-overrides
--- spatialite-5.1.0/debian/libspatialite8.lintian-overrides2023-08-05 
13:51:39.0 +
+++ spatialite-5.1.0/debian/libspatialite8.lintian-overrides1970-01-01 
00:00:00.0 +
@@ -1,15 +0,0 @@
-# Truncated changelog
-debian-news-entry-has-unknown-version *
-
-# Truncated string
-spelling-error-in-binary Syste System *
-
-# False positive, lat/lon
-spelling-error-in-binary Lon Long *
-
-# False positive, string not included 

Bug#1064326: python-xarray: intermittent hang in test_roundtrip_coordinates

[Rebecca N. Palmer]

Package: python3-xarray
Version: 2023.12.0-3

The xarray autopkgtest sometimes (~10% of the time) hangs in 
test_roundtrip_coordinates, and hence fails with a timeout.


Example failure log (but this is _not_ specific to pandas 2.x):
https://ci.debian.net/packages/p/python-xarray/testing/amd64/43065828/

Bug#1064325: rrdtool: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: rrdtool
Version: 1.7.2-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
rrdtool 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 rrdtool
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 rrdtool-1.7.2/debian/changelog rrdtool-1.7.2/debian/changelog
--- rrdtool-1.7.2/debian/changelog  2021-11-18 16:35:17.0 +
+++ rrdtool-1.7.2/debian/changelog  2024-02-19 23:07:48.0 +
@@ -1,3 +1,10 @@
+rrdtool (1.7.2-4.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 23:07:48 +
+
 rrdtool (1.7.2-4) unstable; urgency=medium
 
   [ Jean-Michel Vourgère ]
diff -Nru rrdtool-1.7.2/debian/control rrdtool-1.7.2/debian/control
--- rrdtool-1.7.2/debian/control2021-11-18 15:37:38.0 +
+++ rrdtool-1.7.2/debian/control2024-02-19 23:07:48.0 +
@@ -56,7 +56,10 @@
  Those setups usually run into I/O related problems. RRDCacheD's goal is to
  alleviate these problems.
 
-Package: librrd8
+Package: librrd8t64
+Provides: ${t64:Provides}
+Replaces: librrd8
+Breaks: librrd8 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -78,7 +81,7 @@
 Multi-Arch: same
 Section: libdevel
 Pre-Depends: ${misc:Pre-Depends}
-Depends: librrd8 (= ${binary:Version}), ${misc:Depends}
+Depends: librrd8t64 (= ${binary:Version}), ${misc:Depends}
 Description: time-series data storage and display system (development)
  The Round Robin Database Tool (RRDtool) is a system to store and display
  time-series data (e.g. network bandwidth, machine-room temperature,
diff -Nru rrdtool-1.7.2/debian/librrd8.install 
rrdtool-1.7.2/debian/librrd8.install
--- rrdtool-1.7.2/debian/librrd8.install2019-09-01 13:55:56.0 
+
+++ rrdtool-1.7.2/debian/librrd8.install1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/librrd.so.*
diff -Nru rrdtool-1.7.2/debian/librrd8.symbols 
rrdtool-1.7.2/debian/librrd8.symbols
--- rrdtool-1.7.2/debian/librrd8.symbols2019-10-19 20:38:16.0 
+
+++ rrdtool-1.7.2/debian/librrd8.symbols1970-01-01 00:00:00.0 
+
@@ -1,93 +0,0 @@
-librrd.so.8 librrd8 #MINVER#
-* Build-Depends-Package: librrd8-dev
- rrd_add_ptr@Base 1.4~rc2
- rrd_add_ptr_chunk@Base 1.5.3
- rrd_add_strdup@Base 1.4~rc2
- rrd_add_strdup_chunk@Base 1.5.3
- rrd_cf_conv@Base 1.7.0
- rrd_clear_error@Base 1.3.0
- rrd_close@Base 1.3.0
- rrd_create@Base 1.3.0
- rrd_create_r2@Base 1.5.3
- rrd_create_r@Base 1.3.0
- rrd_dontneed@Base 1.3.0
- rrd_dump@Base 1.3.0
- rrd_dump_cb_r@Base 1.4~rc2+20091004
- rrd_dump_opt_r@Base 1.7.1
- rrd_dump_r@Base 1.3.0
- rrd_fetch@Base 1.3.0
- rrd_fetch_cb_register@Base 1.5.3
- rrd_fetch_r@Base 1.3.0
- rrd_first@Base 1.3.0
- rrd_first_r@Base 1.3.0
- rrd_flush@Base 1.3.0
- rrd_flushcached@Base 1.4~rc2
- rrd_free@Base 1.3.0
- rrd_free_context@Base 1.3.0
- rrd_free_ptrs@Base 1.4~rc2
- rrd_freemem@Base 1.3.0
- rrd_get_context@Base 1.3.0
- rrd_get_error@Base 1.3.0
- rrd_graph@Base 1.3.0
- rrd_graph_v@Base 1.3.0
- rrd_info@Base 1.3.0
- 

Bug#1064323: sphinxbase: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: sphinxbase
Version: 0.8+5prealpha+1-16
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
sphinxbase 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 sphinxbase
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 sphinxbase-0.8+5prealpha+1/debian/changelog 
sphinxbase-0.8+5prealpha+1/debian/changelog
--- sphinxbase-0.8+5prealpha+1/debian/changelog 2023-02-25 18:13:43.0 
+
+++ sphinxbase-0.8+5prealpha+1/debian/changelog 2024-02-19 22:57:36.0 
+
@@ -1,3 +1,10 @@
+sphinxbase (0.8+5prealpha+1-16.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 22:57:36 +
+
 sphinxbase (0.8+5prealpha+1-16) unstable; urgency=medium
 
   * control: Drop ltrace dependency on mipsel (Closes: Bug#1031942)
diff -Nru sphinxbase-0.8+5prealpha+1/debian/control 
sphinxbase-0.8+5prealpha+1/debian/control
--- sphinxbase-0.8+5prealpha+1/debian/control   2023-02-25 18:13:05.0 
+
+++ sphinxbase-0.8+5prealpha+1/debian/control   2024-02-19 22:57:36.0 
+
@@ -30,7 +30,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libsphinxbase3 (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}, libpulse-dev
+Depends: libsphinxbase3t64 (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}, libpulse-dev
 Description: Speech recognition tool - development files
  CMU Sphinx is a large vocabulary, speaker-independent continuous speech
  recognition engine.
@@ -48,7 +48,10 @@
  .
  This package contains tools to manipulate Sphinx files.
 
-Package: libsphinxbase3
+Package: libsphinxbase3t64
+Provides: ${t64:Provides}
+Replaces: libsphinxbase3
+Breaks: libsphinxbase3 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
diff -Nru sphinxbase-0.8+5prealpha+1/debian/libsphinxbase3.install 
sphinxbase-0.8+5prealpha+1/debian/libsphinxbase3.install
--- sphinxbase-0.8+5prealpha+1/debian/libsphinxbase3.install2019-08-29 
08:07:43.0 +
+++ sphinxbase-0.8+5prealpha+1/debian/libsphinxbase3.install1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru sphinxbase-0.8+5prealpha+1/debian/libsphinxbase3.symbols 
sphinxbase-0.8+5prealpha+1/debian/libsphinxbase3.symbols
--- sphinxbase-0.8+5prealpha+1/debian/libsphinxbase3.symbols2019-08-29 
08:07:43.0 +
+++ sphinxbase-0.8+5prealpha+1/debian/libsphinxbase3.symbols1970-01-01 
00:00:00.0 +
@@ -1,542 +0,0 @@
-libsphinxad.so.3 libsphinxbase3 #MINVER#
- ad_close@Base 0.8+5prealpha
- ad_open@Base 0.8+5prealpha
- ad_open_dev@Base 0.8+5prealpha
- ad_open_sps@Base 0.8+5prealpha
- ad_read@Base 0.8+5prealpha
- ad_start_rec@Base 0.8+5prealpha
- ad_stop_rec@Base 0.8+5prealpha
-libsphinxbase.so.3 libsphinxbase3 #MINVER#
- __ckd_alloc_2d_ptr@Base 0.8+5prealpha
- __ckd_alloc_3d_ptr@Base 0.8+5prealpha
- __ckd_calloc_2d__@Base 0.8+5prealpha
- __ckd_calloc_3d__@Base 0.8+5prealpha
- __ckd_calloc_4d__@Base 0.8+5prealpha
- __ckd_calloc__@Base 0.8+5prealpha
- __ckd_malloc__@Base 0.8+5prealpha
- __ckd_realloc__@Base 

Bug#1064324: libnvme ftbfs on most release architectures

[Matthias Klose]

Package: src:libnvme
Version: 1.8-1
Severity: serious
Tags: sid trixie ftbfs

libnvme ftbfs on most release architectures, timeouts in the tests:

[...]
=== 24/24 


test: sysfs
start time:   11:13:43
duration: 30.05s
result:   killed by signal 15 SIGTERM
command: 
LIBNVME_SYSFS_PATH=/<>/obj-aarch64-linux-gnu/test/sysfs/nvme-sysfs-tw-carbon-6.8.0-rc1+ 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 
LIBNVME_HOSTNQN=nqn.2014-08.org.nvmexpress:uuid:ce4fee3e-c02c-11ee-8442-830d068a36c6 
LD_LIBRARY_PATH=/<>/obj-aarch64-linux-gnu/src 
MALLOC_PERTURB_=67 LIBNVME_HOSTID=ce4fee3e-c02c-11ee-8442-830d068a36c6 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
/<>/obj-aarch64-linux-gnu/test/sysfs/test-sysfs 
/<>/obj-aarch64-linux-gnu/test/sysfs/nvme-sysfs-tw-carbon-6.8.0-rc1+ 
nvme-sysfs-tw-carbon-6.8.0-rc1+.out 
/<>/obj-aarch64-linux-gnu/../test/sysfs/data/nvme-sysfs-tw-carbon-6.8.0-rc1+.out

==


Summary of Failures:

24/24 sysfs   TIMEOUT30.05s 
killed by signal 15 SIGTERM


Ok: 21
Expected Fail:  2
Fail:   0
Unexpected Pass:0
Skipped:0
Timeout:1
dh_auto_test: error: cd obj-aarch64-linux-gnu && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson 
test returned exit code 1

make: *** [debian/rules:6: binary-arch] Error 25

Bug#1064322: readline: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: readline
Version: 8.2-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
readline 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 readline
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 readline-8.2/debian/changelog readline-8.2/debian/changelog
--- readline-8.2/debian/changelog   2023-11-26 08:01:05.0 +
+++ readline-8.2/debian/changelog   2024-02-19 22:31:50.0 +
@@ -1,3 +1,10 @@
+readline (8.2-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 22:31:50 +
+
 readline (8.2-3) unstable; urgency=medium
 
   * Fix crash in rl_do_undo, taken from upstream. Closes: #1056314, #1037274.
diff -Nru readline-8.2/debian/control readline-8.2/debian/control
--- readline-8.2/debian/control 2023-11-25 10:37:26.0 +
+++ readline-8.2/debian/control 2024-02-19 22:31:50.0 +
@@ -10,7 +10,10 @@
   gcc-multilib [amd64 i386 kfreebsd-amd64 powerpc ppc64 s390 sparc] 
 Homepage: https://tiswww.case.edu/php/chet/readline/rltop.html
 
-Package: libreadline8
+Package: libreadline8t64
+Provides: ${t64:Provides}
+Replaces: libreadline8
+Breaks: libreadline8 (<< ${source:Version})
 Architecture: any
 Depends: readline-common, ${shlibs:Depends}, ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
@@ -85,7 +88,7 @@
 Package: libreadline-dev
 Architecture: any
 Section: libdevel
-Depends: libreadline8 (= ${binary:Version}), libncurses-dev, ${misc:Depends}
+Depends: libreadline8t64 (= ${binary:Version}), libncurses-dev, ${misc:Depends}
 Multi-Arch: same
 Conflicts: libreadline5-dev, libreadline6-dev, libreadline-gplv2-dev
 Suggests: readline-doc
diff -Nru readline-8.2/debian/lib32readline8.symbols 
readline-8.2/debian/lib32readline8.symbols
--- readline-8.2/debian/lib32readline8.symbols  2018-06-01 19:45:27.0 
+
+++ readline-8.2/debian/lib32readline8.symbols  2024-02-19 22:31:50.0 
+
@@ -1,4 +1,4 @@
 libhistory.so.8 #PACKAGE# #MINVER#
 #include "libhistory8.symbols.common"
 libreadline.so.8 #PACKAGE# #MINVER#
-#include "libreadline8.symbols.common"
+#include "libreadline8t64.symbols.common"
diff -Nru readline-8.2/debian/lib64readline8.symbols 
readline-8.2/debian/lib64readline8.symbols
--- readline-8.2/debian/lib64readline8.symbols  2018-06-01 19:45:37.0 
+
+++ readline-8.2/debian/lib64readline8.symbols  2024-02-19 22:31:50.0 
+
@@ -1,4 +1,4 @@
 libhistory.so.8 #PACKAGE# #MINVER#
 #include "libhistory8.symbols.common"
 libreadline.so.8 #PACKAGE# #MINVER#
-#include "libreadline8.symbols.common"
+#include "libreadline8t64.symbols.common"
diff -Nru readline-8.2/debian/libreadline8.symbols 
readline-8.2/debian/libreadline8.symbols
--- readline-8.2/debian/libreadline8.symbols2018-06-01 19:45:46.0 
+
+++ readline-8.2/debian/libreadline8.symbols1970-01-01 00:00:00.0 
+
@@ -1,4 +0,0 @@
-libhistory.so.8 #PACKAGE# #MINVER#
-#include "libhistory8.symbols.common"
-libreadline.so.8 #PACKAGE# #MINVER#
-#include "libreadline8.symbols.common"
diff -Nru 

Bug#1064302: enforcing time64 on 32-bit architectures is wrong for i386

[Matthias Klumpp]

Am Mo., 19. Feb. 2024 um 21:45 Uhr schrieb Matthias Klose :
>
> Package: src:ldc
> Version: 1:1.36.0-1
> Severity: serious
> Tags: sid trixie
>
> Just reading the changelog:
>
> * LDC should already work fine with 64-bit time on 32-bit
>   architectures, just to be on the safe side though, enforce
>   time64,lfs on 32-bit architectures for C code as well (Closes:
> #1064166)
>
> this is wrong for i386, which will keep the 32bit time_t.

You are right! I am pretty sure I've seen this approach in other
packages too though...
Anyway, it's adjusted now to follow the Debian wiki.

Thanks for the quick heads up!!
Best,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#1064321: elfutils: NMU diff for 64-bit time_t transition

[mwhudson]

Source: elfutils
Version: 0.190-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
elfutils 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 elfutils
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru elfutils-0.190/debian/changelog elfutils-0.190/debian/changelog
--- elfutils-0.190/debian/changelog 2023-11-16 13:54:07.0 +
+++ elfutils-0.190/debian/changelog 2024-02-19 22:38:02.0 +
@@ -1,3 +1,10 @@
+elfutils (0.190-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle   Mon, 19 Feb 2024 22:38:02 +
+
 elfutils (0.190-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru elfutils-0.190/debian/control elfutils-0.190/debian/control
--- elfutils-0.190/debian/control   2023-07-02 07:43:49.0 +
+++ elfutils-0.190/debian/control   2024-02-19 22:38:02.0 +
@@ -28,7 +28,7 @@
 Architecture: any
 Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends},
-  libelf1 (= ${binary:Version}), libdw1 (= ${binary:Version})
+  libelf1t64 (= ${binary:Version}), libdw1t64 (= ${binary:Version})
 Description: collection of utilities to handle ELF objects
  Elfutils is a collection of utilities, including eu-ld (a linker),
  eu-nm (for listing symbols from object files), eu-size (for listing the
@@ -36,13 +36,16 @@
  symbols), eu-readelf (to see the raw ELF file structures), and eu-elflint
  (to check for well-formed ELF files).
 
-Package: libelf1
+Package: libelf1t64
+Provides: ${t64:Provides}
+Replaces: libelf1
+Breaks: libelf1 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
 Description: library to read and write ELF files
- The libelf1 package provides a shared library which allows reading and
+ The libelf1t64 package provides a shared library which allows reading and
  writing ELF files on a high level.  Third party programs depend on
  this package to read internals of ELF files.  The programs of the
  elfutils package use it also to generate new ELF files.
@@ -53,11 +56,11 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libelf1 (= ${binary:Version}), ${misc:Depends},
+Depends: libelf1t64 (= ${binary:Version}), ${misc:Depends},
   zlib1g-dev, libzstd-dev
 Conflicts: libelfg0-dev
-Description: libelf1 development libraries and header files
- libelf1 provides a shared library which allows reading and writing of ELF
+Description: libelf1t64 development libraries and header files
+ libelf1t64 provides a shared library which allows reading and writing of ELF
  files on a high level.
  .
  This package contains development libraries and header files for libelf1.
@@ -66,10 +69,10 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libelf-dev, libdw1 (= ${binary:Version}), ${misc:Depends},
+Depends: libelf-dev, libdw1t64 (= ${binary:Version}), ${misc:Depends},
   zlib1g-dev, liblzma-dev
-Description: libdw1 development libraries and header files
- 

Bug#1064320: libeigen3-dev: linking objects compiled with different flags may cause crashes

[Dima Kogan]

Package: libeigen3-dev
Version: 3.4.0-4
Severity: normal
X-Debbugs-Cc: none, Dima Kogan 

Hello. I'm making this report to track the report in this mailing list
thread:

  https://www.mail-archive.com/debian-science@lists.debian.org/msg13666.html

In short: there's a known issue in Eigen that can create crashing
binaries when using a very reasonable workflow. A description of the
issue and minimized reproducer are here:

  https://www.mail-archive.com/debian-science@lists.debian.org/msg13710.html

I propose to patch this in Debian and/or talk to Eigen upstream to
eliminate the cause of the crash. A proposed patch appears here:

  https://www.mail-archive.com/debian-science@lists.debian.org/msg13857.html

In my view, a questionable design choice in C++ allows the user to
create crashing code, and Eigen expoloits this design choice to make
this crashing possible.

We cannot fix C++, but we can fix Eigen. The issue is that a templated
function defined in a header generates a (weak symbol) copy of this
function in EACH compile unit, and the linker then picks an arbitrary
copy from the many compile units it is given. It is thus imperative that
each copy is compatible with every other copy. Eigen breaks this
requirement by using the preprocessor to select incompatible behaviors
that might crash when linked together. The proposed patch eliminates
this preprocessor-based variability.

Bug#1063274: pydevd: autopkgtest-failing warning with pandas 2.1

[Rebecca N. Palmer]

Thank you for caring about not breaking other packages, and yes, that's 
a good reason to not upload that new upstream for now.


Does just the patch (not the new upstream) also break debugpy?  (It 
shouldn't be able to, since it only touches test code.)

Bug#1064319: dublin-traceroute: NMU diff for 64-bit time_t transition

[mwhudson]

Source: dublin-traceroute
Version: 0.4.2-2
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
dublin-traceroute 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 dublin-traceroute
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru dublin-traceroute-0.4.2/debian/changelog 
dublin-traceroute-0.4.2/debian/changelog
--- dublin-traceroute-0.4.2/debian/changelog2018-09-26 23:49:40.0 
+
+++ dublin-traceroute-0.4.2/debian/changelog2024-02-19 22:24:43.0 
+
@@ -1,3 +1,10 @@
+dublin-traceroute (0.4.2-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle   Mon, 19 Feb 2024 22:24:43 +
+
 dublin-traceroute (0.4.2-2) unstable; urgency=medium
 
   * Update dependencies (Closes: #894345)
diff -Nru dublin-traceroute-0.4.2/debian/control 
dublin-traceroute-0.4.2/debian/control
--- dublin-traceroute-0.4.2/debian/control  2018-09-26 23:49:40.0 
+
+++ dublin-traceroute-0.4.2/debian/control  2024-02-19 22:24:43.0 
+
@@ -16,7 +16,7 @@
 
 Package: dublin-traceroute
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libdublintraceroute0 (= 
${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, libdublintraceroute0t64 (= 
${binary:Version})
 Recommends: libcap2-bin
 Description: NAT-aware multipath tracerouting tool
  Dublin Traceroute uses the techniques invented by the authors of
@@ -25,7 +25,10 @@
  in the probe packet and analyzes the responses in order to detect all the
  encountered NATs.
 
-Package: libdublintraceroute0
+Package: libdublintraceroute0t64
+Provides: ${t64:Provides}
+Replaces: libdublintraceroute0
+Breaks: libdublintraceroute0 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -40,7 +43,7 @@
 Package: libdublintraceroute-dev
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends},
- libdublintraceroute0 (= ${binary:Version}),
+ libdublintraceroute0t64 (= ${binary:Version}),
  libjsoncpp-dev,
  libtins-dev
 Section: libdevel
diff -Nru dublin-traceroute-0.4.2/debian/libdublintraceroute0.install 
dublin-traceroute-0.4.2/debian/libdublintraceroute0.install
--- dublin-traceroute-0.4.2/debian/libdublintraceroute0.install 2018-09-26 
23:49:40.0 +
+++ dublin-traceroute-0.4.2/debian/libdublintraceroute0.install 1970-01-01 
00:00:00.0 +
@@ -1,2 +0,0 @@
-usr/lib/*/libdublintraceroute.so.0.*
-
diff -Nru dublin-traceroute-0.4.2/debian/libdublintraceroute0t64.install 
dublin-traceroute-0.4.2/debian/libdublintraceroute0t64.install
--- dublin-traceroute-0.4.2/debian/libdublintraceroute0t64.install  
1970-01-01 00:00:00.0 +
+++ dublin-traceroute-0.4.2/debian/libdublintraceroute0t64.install  
2018-09-26 23:49:40.0 +
@@ -0,0 +1,2 @@
+usr/lib/*/libdublintraceroute.so.0.*
+
diff -Nru 
dublin-traceroute-0.4.2/debian/libdublintraceroute0t64.lintian-overrides 
dublin-traceroute-0.4.2/debian/libdublintraceroute0t64.lintian-overrides
--- 

Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard

[Xavier G.]

Dear Maintainer,

I confirm this issue.
I experienced it with an AMD R7 240 graphics card[1] on a regular Debian
Sid host running kernel 6.6.15.
Booting with the previous kernel (6.6.13) did not change the situation
but I confirm "Accel" "no", as suggested by Grégory, is a suitable
workaround.

The machine that experiences this issue idles most of the time, so let
me know if I can do/provide anything that would help solving this.

Cheers,
-- 
Xavier G.

[1] lspci: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340 
/ Radeon 520]

Bug#1064318: bash: manpage lists incorrect filename (/etc/bash.bash.logout)

[T. Joseph Carter]

Package: bash
Version: 5.2.21-2
Severity: minor

Dear Maintainer,

The manpage for base states:

```
FILES
   /bin/bash
  The bash executable
   /etc/profile
  The systemwide initialization file, executed for login shells
   /etc/bash.bashrc
  The systemwide per-interactive-shell startup file
   /etc/bash.bash.logout
  The systemwide login shell cleanup file, executed when a login 
shell exits
```

This is incorrect, bash invokes /etc/bash.bash_logout.

Debian doesn't provide a bash.bash_logout so I know about this because I
was tinkering with adding stuff to these to find bash's config files in
XDG-standard locations, if they exist, since I keep ~/.config in git.

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

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

Versions of packages bash depends on:
ii  base-files   13
ii  debianutils  5.16
ii  libc62.37-15
ii  libtinfo66.4+20240113-1

Versions of packages bash recommends:
ii  bash-completion  1:2.11-8

Versions of packages bash suggests:
ii  bash-doc  5.2.21-2

-- Configuration Files:
/etc/bash.bashrc changed [not included]

-- no debconf information

Bug#1057548: cloud-init: FTBFS: failing tests

[Ross Vandegrift]

On Tue, Dec 05, 2023 at 11:04:12PM +0100, Santiago Vila wrote:
> During a rebuild of all packages in unstable, your package failed to build:

I started updating to the latest upstream release, which fixes this FTBFS.  But
I'm reluctant to push to the team repo, due to an issue with the network
nocloud datasource.

With a local webserver hosting cloud-init seed data, cloud-init 23.4.3 never
hits my local http server.  The same setup with 23.3.1 from sid works fine.
Disk based nocloud seeds work fine with 23.4.3.

So far, I haven't found any obvious failure - under 23.4.3,
DataSourceNoCloudNet either doesn't run or can't reach the http server.  In
case anyone has time to poke, the new release is pushed to my personal repo at
https://salsa.debian.org/rvandegrift/cloud-init

Ross

Bug#1064317: powertop: install systemd unit into /usr

[Michael Biebl]

Source: powertop
Version: 2.15-2
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to finalize the /usr-merge via DEP17 by moving all files to
/usr. powertop installs files into /lib; these should be moved into
the respective canonical locations in /usr/.

Please find a patch attached. It has been build-tested.

This should not be backported to bookworm. If you intend to
backport, please use dh_movetousr instead or defer the placement of the
unit files to systemd.pc.

If your package will change for the t64 transition or otherwise
rename/split/move its binaries (packages) during trixie, please
then upload to experimental and get in touch with the UsrMerge
driver, please see the wiki [1].

Michael

[1] https://wiki.debian.org/UsrMerge
diff -Nru powertop-2.15/debian/changelog powertop-2.15/debian/changelog
--- powertop-2.15/debian/changelog  2023-11-19 13:38:07.0 +0100
+++ powertop-2.15/debian/changelog  2024-02-19 23:11:13.0 +0100
@@ -1,3 +1,10 @@
+powertop (2.15-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd unit into /usr. (Closes: #-1)
+
+ -- Michael Biebl   Mon, 19 Feb 2024 23:11:13 +0100
+
 powertop (2.15-2) unstable; urgency=medium
 
   [ Rohan Jain ]
diff -Nru powertop-2.15/debian/powertop.install 
powertop-2.15/debian/powertop.install
--- powertop-2.15/debian/powertop.install   2023-11-19 13:24:54.0 
+0100
+++ powertop-2.15/debian/powertop.install   2024-02-19 23:11:11.0 
+0100
@@ -1 +1 @@
-powertop.service lib/systemd/system/
+powertop.service usr/lib/systemd/system/

Bug#1064316: rtkit: install systemd units into /usr

[Michael Biebl]

Source: rtkit
Version: 0.13-5
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to finalize the /usr-merge via DEP17 by moving all files to
/usr. rtkit installs files into /lib; these should be moved into
the respective canonical locations in /usr/.

Please find a patch attached. It has been build-tested.

This should not be backported to bookworm. If you intend to
backport, please use dh_movetousr instead or defer the placement of the
unit files to systemd.pc.

If your package will change for the t64 transition or otherwise
rename/split/move its binaries (packages) during trixie, please
then upload to experimental and get in touch with the UsrMerge
driver, please see the wiki [1].

Michael

[1] https://wiki.debian.org/UsrMerge
diff -Nru rtkit-0.13/debian/changelog rtkit-0.13/debian/changelog
--- rtkit-0.13/debian/changelog 2023-02-27 00:08:26.0 +0100
+++ rtkit-0.13/debian/changelog 2024-02-19 23:02:19.0 +0100
@@ -1,3 +1,10 @@
+rtkit (0.13-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd units into /usr. (Closes: #-1)
+
+ -- Michael Biebl   Mon, 19 Feb 2024 23:02:19 +0100
+
 rtkit (0.13-5) unstable; urgency=medium
 
   * Team upload
diff -Nru rtkit-0.13/debian/rules rtkit-0.13/debian/rules
--- rtkit-0.13/debian/rules 2023-02-27 00:07:20.0 +0100
+++ rtkit-0.13/debian/rules 2024-02-19 23:02:09.0 +0100
@@ -13,7 +13,7 @@
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   -Dsystemd_systemunitdir=/lib/systemd/system \
+   -Dsystemd_systemunitdir=/usr/lib/systemd/system \
-Dlibsystemd=enabled \
-Dinstalled_tests=true \
 

Bug#1064315: alsa-topology-conf: install firmware files into /usr

[Michael Biebl]

Source: alsa-topology-conf
Version: 1.2.5.1-2
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to finalize the /usr-merge via DEP17 by moving all files to
/usr. alsa-topology-conf installs files into /lib; these should be moved
into the respective canonical locations in /usr/.

Please find a patch attached. It has been build-tested.

This should not be backported to bookworm. If you intend to
backport, please use dh_movetousr instead.

If your package will change for the t64 transition or otherwise
rename/split/move its binaries (packages) during trixie, please
then upload to experimental and get in touch with the UsrMerge
driver, please see the wiki [1].

Michael

[1] https://wiki.debian.org/UsrMerge
diff -Nru alsa-topology-conf-1.2.5.1/debian/alsa-topology-conf.install 
alsa-topology-conf-1.2.5.1/debian/alsa-topology-conf.install
--- alsa-topology-conf-1.2.5.1/debian/alsa-topology-conf.install
2021-09-15 13:36:24.0 +0200
+++ alsa-topology-conf-1.2.5.1/debian/alsa-topology-conf.install
2024-02-18 08:52:54.0 +0100
@@ -1,2 +1,2 @@
-*.bin  lib/firmware
+*.bin usr/lib/firmware
 topology usr/share/alsa
diff -Nru alsa-topology-conf-1.2.5.1/debian/changelog 
alsa-topology-conf-1.2.5.1/debian/changelog
--- alsa-topology-conf-1.2.5.1/debian/changelog 2021-09-15 13:48:11.0 
+0200
+++ alsa-topology-conf-1.2.5.1/debian/changelog 2024-02-18 08:52:54.0 
+0100
@@ -1,3 +1,10 @@
+alsa-topology-conf (1.2.5.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install firmware files into /usr. (Closes: #-1)
+
+ -- Michael Biebl   Sun, 18 Feb 2024 08:52:54 +0100
+
 alsa-topology-conf (1.2.5.1-2) unstable; urgency=medium
 
   [ Jordi Mallach ]

Bug#1064314: Crash on NXDOMAIN in exempt_spf_addresses

[Jakob Haufe]

Package: postfix-policyd-spf-perl
Version: 2.011-2
Severity: normal

When /etc/postfix/exempt_spf_addresses contains a hostname that returns
NXDOMAIN, postfix-policyd-spf-perl crashes with

Can't call method "contains" on an undefined value at 
/usr/sbin/postfix-policyd-spf-perl line 296,  line 2.

This, however, doesn't seem to reach syslog. Postfix just logs:

warning: command /usr/sbin/postfix-policyd-spf-perl exit status 255
warning: premature end-of-input on private/spfcheck while reading input 
attribute name

This results in all mail being rejected with 451.

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

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

Versions of packages postfix-policyd-spf-perl depends on:
ii  adduser3.137
ii  libmail-spf-perl   3.20240206-1
ii  libnetaddr-ip-perl 4.079+dfsg-2+b2
ii  libsys-hostname-long-perl  1.5-3
ii  perl [libversion-perl] 5.38.2-3
ii  postfix3.8.5-1

postfix-policyd-spf-perl recommends no packages.

postfix-policyd-spf-perl suggests no packages.

-- no debconf information



-- 
ceterum censeo microsoftem esse delendam.


pgpxj6zcn9wwd.pgp
Description: OpenPGP digital signature

Bug#1064313: rdma-core: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: rdma-core
Version: 48.0-1.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
rdma-core 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 rdma-core
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 rdma-core-48.0/debian/changelog rdma-core-48.0/debian/changelog
--- rdma-core-48.0/debian/changelog 2024-01-22 15:08:10.0 +
+++ rdma-core-48.0/debian/changelog 2024-02-19 22:06:00.0 +
@@ -1,3 +1,10 @@
+rdma-core (48.0-1.2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 22:06:00 +
+
 rdma-core (48.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rdma-core-48.0/debian/control rdma-core-48.0/debian/control
--- rdma-core-48.0/debian/control   2024-01-22 15:08:10.0 +
+++ rdma-core-48.0/debian/control   2024-02-19 22:06:00.0 +
@@ -191,7 +191,7 @@
 Section: libdevel
 Architecture: linux-any
 Multi-Arch: same
-Depends: libibverbs-dev, librdmacm1 (= ${binary:Version}), ${misc:Depends}
+Depends: libibverbs-dev, librdmacm1t64 (= ${binary:Version}), ${misc:Depends}
 Description: Development files for the librdmacm library
  librdmacm is a library that allows applications to set up reliable
  connected and unreliable datagram transfers when using RDMA adapters.
@@ -210,7 +210,10 @@
  It contains the header files and static libraries (optionally)
  needed for compiling.
 
-Package: librdmacm1
+Package: librdmacm1t64
+Provides: ${t64:Provides}
+Replaces: librdmacm1
+Breaks: librdmacm1 (<< ${source:Version})
 Architecture: linux-any
 Multi-Arch: same
 Section: libs
@@ -249,7 +252,7 @@
  provided by libibverbs, which provides the interface used to actually
  transfer data.
  .
- This package contains useful librdmacm1 example programs such as
+ This package contains useful librdmacm1t64 example programs such as
  rping and udaddy.
 
 Package: srptools
@@ -280,7 +283,7 @@
 
 Package: infiniband-diags
 Architecture: linux-any
-Depends: libibnetdisc5 (= ${binary:Version}),
+Depends: libibnetdisc5t64 (= ${binary:Version}),
  ${misc:Depends},
  ${perl:Depends},
  ${shlibs:Depends}
@@ -322,7 +325,10 @@
  It contains the header files and static libraries (optionally)
  needed for compiling.
 
-Package: libibnetdisc5
+Package: libibnetdisc5t64
+Provides: ${t64:Provides}
+Replaces: libibnetdisc5
+Breaks: libibnetdisc5 (<< ${source:Version})
 Section: libs
 Architecture: linux-any
 Multi-Arch: same
@@ -341,7 +347,7 @@
 Section: libdevel
 Architecture: linux-any
 Multi-Arch: same
-Depends: libibnetdisc5 (= ${binary:Version}), ${misc:Depends}
+Depends: libibnetdisc5t64 (= ${binary:Version}), ${misc:Depends}
 Breaks: infiniband-diags (<< 2.0.0)
 Replaces: infiniband-diags (<< 2.0.0)
 Description: InfiniBand diagnostics library headers
@@ -351,5 +357,5 @@
  failover, and it is designed to be scalable.
  .
  This package provides development files required to build
- applications aginast the libibnetdisc5 InfiniBand diagnostic
+ applications aginast the libibnetdisc5t64 

Bug#684425: conky-std: please implement an alternative way to distinguish among hwmon devices

[Francesco Poli]

On Fri, 16 Feb 2024 20:22:58 +0100 (CET) Jmkr wrote:

> This bug could probably be closed as it is now possible to use device names 
> instead of numbers for "${hwmon ...}". I tested that it works when I did my 
> build of Conky 1.19.6-1 from Debian Sid. It was implemented in the Conky 
> commit "https://github.com/brndnmtthws/conky/commit/14e3b80c45254743e962f88d
> 027a7ea37bf59ee6".

Wow!
I was not aware that a feature (almost) identical to the one I
requested in 2012 (!) has been finally implemented.

I am really happy about it, thanks for the great news!

I am currently testing this new way to specify the hwmon device in
conky.conf, and it seems to work on one host (but I haven't yet
rebooted...). Let's see how it goes in the following weeks and on other
hosts...

Thanks again for the heads up!:-)

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpF9o5V_3HjY.pgp
Description: PGP signature

Bug#1064311: rdkit: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: rdkit
Version: 202309.3-2
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
rdkit 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 rdkit
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 rdkit-202309.3/debian/changelog rdkit-202309.3/debian/changelog
--- rdkit-202309.3/debian/changelog 2024-01-17 13:03:19.0 +
+++ rdkit-202309.3/debian/changelog 2024-02-19 20:49:34.0 +
@@ -1,3 +1,10 @@
+rdkit (202309.3-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 20:49:34 +
+
 rdkit (202309.3-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru rdkit-202309.3/debian/control rdkit-202309.3/debian/control
--- rdkit-202309.3/debian/control   2024-01-17 13:03:19.0 +
+++ rdkit-202309.3/debian/control   2024-02-19 20:49:33.0 +
@@ -102,7 +102,10 @@
  .
  This package contains data files.
 
-Package: librdkit1
+Package: librdkit1t64
+Provides: ${t64:Provides}
+Replaces: librdkit1
+Breaks: librdkit1 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -137,7 +140,7 @@
 Package: librdkit-dev
 Section: libdevel
 Architecture: any
-Depends: librdkit1 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: librdkit1t64 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
 Description: Collection of cheminformatics and machine-learning software 
(development files)
  RDKit is a Python/C++ based cheminformatics and machine-learning software
  environment.  Features Include:
diff -Nru rdkit-202309.3/debian/control.in rdkit-202309.3/debian/control.in
--- rdkit-202309.3/debian/control.in2023-09-20 14:24:08.0 +
+++ rdkit-202309.3/debian/control.in2024-02-19 20:49:33.0 +
@@ -102,7 +102,10 @@
  .
  This package contains data files.
 
-Package: librdkit1
+Package: librdkit1t64
+Provides: ${t64:Provides}
+Replaces: librdkit1
+Breaks: librdkit1 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -137,7 +140,7 @@
 Package: librdkit-dev
 Section: libdevel
 Architecture: any
-Depends: librdkit1 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: librdkit1t64 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
 Description: Collection of cheminformatics and machine-learning software 
(development files)
  RDKit is a Python/C++ based cheminformatics and machine-learning software
  environment.  Features Include:
diff -Nru rdkit-202309.3/debian/librdkit1.install 
rdkit-202309.3/debian/librdkit1.install
--- rdkit-202309.3/debian/librdkit1.install 2023-09-20 14:24:08.0 
+
+++ rdkit-202309.3/debian/librdkit1.install 1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/lib*.so.*
diff -Nru rdkit-202309.3/debian/librdkit1.lintian-overrides 
rdkit-202309.3/debian/librdkit1.lintian-overrides
--- rdkit-202309.3/debian/librdkit1.lintian-overrides   2023-09-20 
14:24:08.0 +
+++ 

Bug#1064312: node-undici: CVE-2024-24758

[Salvatore Bonaccorso]

Source: node-undici
Version: 5.28.2+dfsg1+~cs23.11.12.3-6
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for node-undici.

CVE-2024-24758[0]:
| Undici is an HTTP/1.1 client, written from scratch for Node.js.
| Undici already cleared Authorization headers on cross-origin
| redirects, but did not clear `Proxy-Authentication` headers. This
| issue has been patched in versions 5.28.3 and 6.6.1. Users are
| advised to upgrade. There are no known workarounds for this
| vulnerability.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-24758
https://www.cve.org/CVERecord?id=CVE-2024-24758
[1] https://github.com/nodejs/undici/security/advisories/GHSA-3787-6prv-h9w3
[2] 
https://github.com/nodejs/undici/commit/d3aa574b1259c1d8d329a0f0f495ee82882b1458

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1064310: dav1d: CVE-2024-1580

[Salvatore Bonaccorso]

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

Hi,

The following vulnerability was published for dav1d.

CVE-2024-1580[0]:
| An integer overflow in dav1d AV1 decoder that can occur when
| decoding videos with large frame size. This can lead to memory
| corruption within the AV1 decoder. We recommend upgrading past
| version 1.4.0 of dav1d.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-1580
https://www.cve.org/CVERecord?id=CVE-2024-1580
[1] 
https://code.videolan.org/videolan/dav1d/-/commit/2b475307dc11be9a1c3cc4358102c76a7f386a51

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1064309: src:python-pamqp: fails to migrate to testing for too long: autopkgtest failures on 32 bit

[Paul Gevers]

Source: python-pamqp
Version: 3.2.1-1
Severity: serious
Control: close -1 3.3.0-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:python-pamqp has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
fails its own autopkgtest on armel, armhf and i386 with what looks like 
a broken test for 32 bits architectures.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064308: libricohcamerasdk: identified for time_t transition but no ABI in shlibs

[Steve Langasek]

Source: libricohcamerasdk
Version: 1.1.0-4
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t

Hi Thorsten,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
libricohcamerasdk as an affected package, on the basis that the ABI of the
library references the time_t type.

However, libricohcamerasdk's shlibs file declares a dependency on a library
package name that contains no ABI information:

$ cat DEBIAN/shlibs
libmtpricoh 9 libricohcamerasdk (>= 1.1.0)
$

It is not obvious that we should rename the package to
'libricohcamerasdkt64' as part of this transition.

Looking at the archive, there is a package that depends on this library,
indi-pentax.

Since there is no self-evident thing to do with the library package name
here, we will not be handling this package as part of the mass NMUs. 
Instead I am filing a serious bug because partial upgrades from bookworm to
trixie on 32-bit architectures (upgrading libricohcamerasdk without also
upgrading indi-pentax, or vice versa) will result in ABI skew and may result
in broken behavior.

Thanks,
-- 
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

[0] https://wiki.debian.org/ReleaseGoals/64bit-time
[1] https://lists.debian.org/debian-devel/2024/01/msg00041.html


signature.asc
Description: PGP signature

Bug#1064307: awscli ftbfs with Python 3.12 as the default

[Matthias Klose]

Package: src:awscli
Version: 2.15.9-1
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

[...]
D: pybuild tools:231: invoking: python3.12 -m build 
--skip-dependency-check --no-isolation --wheel --outdir 
/<>/.pybuild/cpython3_3.12

* Building wheel...
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 353, in 

main()
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 335, in main

json_out['return_val'] = hook(**hook_input['kwargs'])
 
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 251, in build_wheel

return _build_backend().build_wheel(wheel_directory, config_settings,
   ^^
  File "/<>/backends/pep517.py", line 64, in build_wheel
_inject_wheel_extras(os.path.join(wheel_directory, whl_filename))
  File "/<>/backends/pep517.py", line 189, in 
_inject_wheel_extras

_build_and_inject_ac_index(BUILD_DIR, extracted_wheel_dir)
  File "/<>/backends/pep517.py", line 217, in 
_build_and_inject_ac_index

ac_index_build_name = _build_ac_index(build_dir)
  ^^
  File "/<>/backends/pep517.py", line 228, in _build_ac_index
from awscli.autocomplete.generator import generate_index
  File "/<>/awscli/autocomplete/generator.py", line 17, in 


from awscli.autocomplete.serverside.indexer import APICallIndexer
  File "/<>/awscli/autocomplete/serverside/indexer.py", 
line 18, in 

import awscli.clidriver
  File "/<>/awscli/clidriver.py", line 21, in 
import botocore.session
  File "/<>/awscli/botocore/session.py", line 27, in 
import botocore.client
  File "/<>/awscli/botocore/client.py", line 16, in 
from botocore import UNSIGNED, waiter, xform_name
  File "/<>/awscli/botocore/waiter.py", line 17, in 
from botocore.docs.docstring import WaiterDocstring
  File "/<>/awscli/botocore/docs/__init__.py", line 15, in 


from botocore.docs.service import ServiceDocumenter
  File "/<>/awscli/botocore/docs/service.py", line 13, in 


from botocore.docs.bcdoc.restdoc import DocumentStructure
  File "/<>/awscli/botocore/docs/bcdoc/restdoc.py", line 
15, in 

from botocore.compat import OrderedDict
  File "/<>/awscli/botocore/compat.py", line 36, in 
from botocore.vendored.six.moves import http_client
ModuleNotFoundError: No module named 'botocore.vendored.six.moves'

ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:391: build: plugin pyproject failed with: exit 
code=1: python3.12 -m build --skip-dependency-check --no-isolation 
--wheel --outdir /<>/.pybuild/cpython3_3.12

Traceback (most recent call last):
  File "/usr/bin/pybuild", line 389, in main
run(func, i, version, c)
  File "/usr/bin/pybuild", line 327, in run
result = func(context, args)
 ^^^
  File "/usr/share/dh-python/dhpython/build/plugin_pyproject.py", line 
108, in build

self.build_wheel(context, args)
  File "/usr/share/dh-python/dhpython/build/base.py", line 359, in 
wrapped_func

raise Exception(msg)
Exception: exit code=1: python3.12 -m build --skip-dependency-check 
--no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12
dh_auto_build: error: pybuild --build -i python{version} -p 3.12 
returned exit code 13

make: *** [debian/rules:11: binary] Error 25

Bug#1064306: nodejs: FTBFS on mips64el: failed tests

[Sebastian Ramacher]

Source: nodejs
Version: 18.19.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=18.19.1%2Bdfsg-1=1708294535=0

not ok 270 parallel/test-cli-node-options
  ---
  duration_ms: 8260.48900
  severity: fail
  exitcode: 1
  stack: |-
node:assert:991
throw newErr;
^

AssertionError [ERR_ASSERTION]: ifError got unwanted exception: Command 
failed: /<>/out/Release/node -e console.log("B")
Warning: disabling flag --expose_wasm due to conflicting flags

at /<>/test/parallel/test-cli-node-options.js:110:14
at /<>/test/common/index.js:453:15
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.exithandler (node:child_process:422:12)
at ChildProcess.emit (node:events:517:28)
at maybeClose (node:internal/child_process:1098:16)
at Socket. (node:internal/child_process:450:11)
at Socket.emit (node:events:517:28)
at Pipe. (node:net:351:12) {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: Error: Command failed: /<>/out/Release/node -e 
console.log("B")
  Warning: disabling flag --expose_wasm due to conflicting flags
  
  at ChildProcess.exithandler (node:child_process:422:12)
  at ChildProcess.emit (node:events:517:28)
  at maybeClose (node:internal/child_process:1098:16)
  at Socket. (node:internal/child_process:450:11)
  at Socket.emit (node:events:517:28)
  at Pipe. (node:net:351:12) {
code: null,
killed: false,
signal: 'SIGSEGV',
cmd: '/<>/out/Release/node -e console.log("B")'
  },
  expected: null,
  operator: 'ifError'
}

Node.js v18.19.1

...

not ok 475 parallel/test-crypto-sign-verify
  ---
  duration_ms: 715.73800
  severity: fail
  exitcode: 1
  stack: |-
node:assert:635
  throw err;
  ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

  Comparison {
+   message: 'error:1E08010C:DECODER routines::unsupported'
-   message: 'bye, bye, library'
  }
at Object. 
(/<>/test/parallel/test-crypto-sign-verify.js:42:10)
at Module._compile (node:internal/modules/cjs/loader:1356:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
at Module.load (node:internal/modules/cjs/loader:1197:32)
at Module._load (node:internal/modules/cjs/loader:1013:12)
at Function.executeUserEntryPoint [as runMain] 
(node:internal/modules/run_main:128:12)
at node:internal/main/run_main_module:28:49 {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: Error: error:1E08010C:DECODER routines::unsupported
  at Sign.sign (node:internal/crypto/sig:131:29)
  at assert.throws.message 
(/<>/test/parallel/test-crypto-sign-verify.js:43:31)
  at getActual (node:assert:756:5)
  at Function.throws (node:assert:902:24)
  at Object. 
(/<>/test/parallel/test-crypto-sign-verify.js:42:10)
  at Module._compile (node:internal/modules/cjs/loader:1356:14)
  at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
  at Module.load (node:internal/modules/cjs/loader:1197:32)
  at Module._load (node:internal/modules/cjs/loader:1013:12)
  at Function.executeUserEntryPoint [as runMain] 
(node:internal/modules/run_main:128:12) {
reason: 'unsupported',
code: 'ERR_OSSL_UNSUPPORTED'
  },
  expected: { message: 'bye, bye, library' },
  operator: 'throws'
}

...

not ok 579 parallel/test-debugger-preserve-breaks # TODO : Fix flaky test
  ---
  duration_ms: 26966.18100
  severity: flaky
  exitcode: 1
  stack: |-
/<>/test/common/debugger.js:90
  reject(new Error([
 ^

Error: Timeout (25000) while waiting for /(?:assert|break|break on 
start|debugCommand|exception|other|promiseRejection) in/i; found: debug> 
debug> 

< Waiting for the debugger to disconnect...
< 
debug> 
at Timeout. (/<>/test/common/debugger.js:90:18)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7)

Node.js v18.19.1

...

not ok 792 parallel/test-freeze-intrinsics
  ---
  duration_ms: 710.81600
  severity: fail
  exitcode: 1
  stack: |-
node:assert:125
  throw new AssertionError(obj);
  ^

AssertionError [ERR_ASSERTION]: Missing expected exception (TypeError).
at Object. 
(/<>/test/parallel/test-freeze-intrinsics.js:36:10)
at Module._compile (node:internal/modules/cjs/loader:1356:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
at Module.load 

Bug#1064305: fop: new upstream version 2.9

[tony mancill]

Source: fop
Version: 1:2.8-3
Severity: minor

This bug is for visibility; fop 2.9 is now available.
I am working on an update and will upload to experimental soon.

Bug#1064304: less: in PROMPTS section of doc, it's not at all clear that '.' characters get silently eaten

[Britton Kerin]

Package: less
Version: 590-1ubuntu0.22.04.1
Severity: normal
Tags: upstream

Dear Maintainer,

LESSEDIT expands the same things that are expanded in prompts, which
ends up meaning that this:

 (export LESSEDIT="bash --noprofile --norc -c 'echo ~/.bashrc'" && less 
some_file.c )

when you press v from less to fire it, ends up printing:

 /home/bkerin/bashrc

rather than:

 /home/bkerin/.bashrc

as expected.

It's entirely unclear from the docs that this is going to happen.  The
docs in the PROMPT section present a listof expansion beginning with %
and another list beginning with ?, and state that a period terminates
the true part of the conditional begun with ?.  The *do not* say that .
and : are metacharacters even if ? hasn't been used.  Either they should
not be treated as metacharacters in this case, or it should be clearly
documented that they are, so users know to escape them.

This is not an academic example since doing e.g.:

(export LESSEDIT="bash --noprofile --norc -i -c 'export SOME_MODE_VAR=def && 
source /etc/profile && source ~/.profile && some_func_from_profile'" && 
some_program_using_less_in_a_weird_way)

is a fairly obvious way to modally pull in stuff in ~/.profile for when
launching an editor from some_program_using_less_in_a_weird_way

Now that I know (after reading source) that the
very-common-in-file-names . character has to be escaped it all works
fine.

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

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

Versions of packages less depends on:
ii  libc6  2.35-0ubuntu3.6
ii  libtinfo6  6.3-2ubuntu0.1

less recommends no packages.

less suggests no packages.

-- no debconf information

Bug#1064303: authprogs: Program name is incorrect in description, "authrpogs" instead of "authprogs"

[Russell Jones]

Package: authprogs
Severity: minor
X-Debbugs-Cc: a1hg94...@mozmail.com

Dear Maintainer,

"authrpogs is invoked" in the description should say "authprogs is invoked"

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

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

Versions of packages authprogs depends on:
ii  python3   3.11.6-1
pn  python3-yaml  

authprogs recommends no packages.

authprogs suggests no packages.

Bug#1064067: libdemeter-perl: ships perl modules already packaged separately as libxray-scattering-perl, libxray-absorption-perl

[Andreas Beckmann]

Followup-For: Bug #1064067
Control: found -1 0.9.27+ds6-2
Control: retitle -1 libdemeter-perl: ships perl modules already packaged 
separately as libxray-scattering-perl, libxray-absorption-perl, 
libifeffit-perl, libchemistry-formula-perl

Hi,

there is another file conflict with libchemistry-formula-perl on
/usr/share/perl5/Chemistry/Formula.pm that was probably shadowed by the
other conflicts, otherwise I would have listed it in the initial report:

  Preparing to unpack .../libdemeter-perl_0.9.27+ds6-2_amd64.deb ...
  Unpacking libdemeter-perl (0.9.27+ds6-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libdemeter-perl_0.9.27+ds6-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/perl5/Chemistry/Formula.pm', which is also 
in package libchemistry-formula-perl 3.0.1-1.3
  Errors were encountered while processing:
   /var/cache/apt/archives/libdemeter-perl_0.9.27+ds6-2_amd64.deb


Looking at the file list, the following files are outside of the Demeter
namespace and potential future file conflict candidates. Ideally they
should be packaged separately.

/usr/share/perl5/Chemistry/Formula.pm  (currently in conflict)
/usr/share/perl5/Chemistry/MoreElements.pm
/usr/share/perl5/Larch.pm
/usr/share/perl5/LarchServer.pm
/usr/share/perl5/MooseX
/usr/share/perl5/MooseX/Quenchable.pm
/usr/share/perl5/MooseX/SetGet.pm
/usr/share/perl5/Xray
/usr/share/perl5/Xray/BondValence.pm
/usr/share/perl5/Xray/Crystal
/usr/share/perl5/Xray/Crystal/Cell.pm
/usr/share/perl5/Xray/Crystal/Site.pm
/usr/share/perl5/Xray/Crystal/SpaceGroup.pm
/usr/share/perl5/Xray/Crystal/share
/usr/share/perl5/Xray/Crystal/share/space_groups.db
/usr/share/perl5/Xray/Crystal.pm
/usr/share/perl5/Xray/data
/usr/share/perl5/Xray/data/bvparm2006.cif


Andreas

Bug#1064302: enforcing time64 on 32-bit architectures is wrong for i386

[Matthias Klose]

Package: src:ldc
Version: 1:1.36.0-1
Severity: serious
Tags: sid trixie

Just reading the changelog:

   * LDC should already work fine with 64-bit time on 32-bit
 architectures, just to be on the safe side though, enforce
 time64,lfs on 32-bit architectures for C code as well (Closes: 
#1064166)


this is wrong for i386, which will keep the 32bit time_t.

Bug#1064301: oss4: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: oss4
Version: 4.2-build2020-2
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 oss4
as a source package shipping runtime libraries whose ABI is affected by the
change in size of time_t.

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition.  Since the affected library is libasound2, the
actual library transition is in alsa-lib and oss4 only needs changes to its
Provides: to match.

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 oss4 which will
initially be uploaded to experimental, 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.

-- 
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
diff -Nru oss4-4.2-build2020/debian/changelog 
oss4-4.2-build2020/debian/changelog
--- oss4-4.2-build2020/debian/changelog 2023-08-04 17:12:47.0 -0700
+++ oss4-4.2-build2020/debian/changelog 2024-02-19 11:59:19.0 -0800
@@ -1,3 +1,13 @@
+oss4 (4.2-build2020-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Update libasound2 provides for 64-bit time_t transition.
+  * Use explicit Provides: for libasound2 compat on 64-bit archs since
+debhelper won't be able to work this out given 't64' is not in the
+package name.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 19:59:19 +
+
 oss4 (4.2-build2020-2) unstable; urgency=medium
 
   * control: Drop dependency on now-obsolete lsb-base.
diff -Nru oss4-4.2-build2020/debian/control oss4-4.2-build2020/debian/control
--- oss4-4.2-build2020/debian/control   2023-08-04 17:09:33.0 -0700
+++ oss4-4.2-build2020/debian/control   2024-02-19 11:59:19.0 -0800
@@ -96,8 +96,8 @@
 Package: liboss4-salsa-asound2
 Section: libs
 Architecture: any
-Provides: libasound2
-Conflicts: libasound2
+Provides: libasound2t64, libasound2 [amd64 arm64 mips64el ppc64el riscv64 
s390x]
+Conflicts: libasound2t64, libasound2
 Multi-Arch: same
 Depends: liboss4-salsa2, ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}


signature.asc
Description: PGP signature

Bug#890601: firmware-free: Source Package Doesn't Contain Source

[Bastian Germann]

On Tue, 5 Sep 2023 17:30:44 +0200 Bastian Germann  wrote:

Can you please drop carl9170-1.fw and the associated things from the package?
The carl9170fw package should be ready with revision 1.9.9-399-gcd480b9-1.1.
The only missing thing is a Breaks/Replaces which I would like to fill in as
soon as you have decided on the firmware-free revision that drops it.


Ping. There have been two firmware-free uploads since my request.
Would you please comment on this? I would like to get this into trixie.

Bug#1056284: nss: CVE-2023-5388

[Tobias Frost]

Control: tags -1 fixed-upstream patch

Upstream Patch:
https://hg.mozilla.org/projects/nss/rev/196716d8377ab427e326f20bff2d026e90ac69e2

Cheers,
-- 
tobi

Bug#1064288: Missing /skole directory.

[Mike Gabriel]

Control: found -1 2024.02.01.2~deb12u1
Control: found -1 2024.02.01.2
Control: tags -1 trixie
Control: tags -1 bookworm

Hi Daniel,

On  Mo 19 Feb 2024 19:48:37 CET, Daniel Teichmann wrote:


Package: debian-edu-fai
Version: bookworm

Dear Maintainers,

I've noticed that the /skole directory was missing, therefore no  
/home could be mounted for a user.

The user couldn't log into a workstation, because of that.


Thanks for the reminder/info. Will take a look.


I guess the missing dir should be created via puppet.


In vanilla Debian Edu, we don't use puppet. The fix needs to be  
applied to the FAI config space shipped in debian-edu-fai.


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpaM5sMCej_5.pgp
Description: Digitale PGP-Signatur

Bug#1064300: RFS: streamlink/6.6.1-1 -- CLI for extracting video streams from various websites to a video player

[Alexis Murzeau]

Package: sponsorship-requests
Severity: normal


Dear mentors,

I am looking for a sponsor for my package "streamlink" for a new
upstream version 6.6.1.

  * Package name: streamlink
Version : 6.6.1-1
Upstream Author : Streamlink Team
  * URL : https://streamlink.github.io/
  * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
  * Vcs : https://salsa.debian.org/amurzeau/streamlink/
Section : python

It builds those binary packages:
  python3-streamlink - Python module for extracting video streams from
various websites
  python3-streamlink-doc - CLI for extracting video streams from
various websites (documentation)
  streamlink - CLI for extracting video streams from various websites
to a video player


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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_6.6.1-1.dsc



Changes since the last upload to unstable:
streamlink (6.6.1-1) unstable; urgency=medium

  * New upstream version 6.6.1

 -- Alexis Murzeau   Mon, 19 Feb 2024 20:41:54 +0100

Regards,

--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F|


OpenPGP_0xE7BD1904F480937F.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064058: libxml-stream-perl: TLS/SSL broken with IO-Socket-SSL >= 2.078 when hostname verification is enabled

[Manfred Stock]

Hi gregor,

Am Sun, Feb 18, 2024 at 01:41:20AM +0100 schrieb gregor herrmann:
> On Fri, 16 Feb 2024 15:56:04 +0100, Manfred Stock wrote:
>
> > after upgrading to Debian Bookworm, we noticed that the sendxmpp command
> > line tool was not working anymore in our setup. [...] Eventually, I came
> > up with a pull request [1] containing a patch that fixed it for us -
> > [...]
>
> Oh wow -- thank you!

you're welcome, and thanks for your quick response!


> I remember looking at #1050336 in libnet-xmpp-perl and having the
> suspicion that the problem is actually in libxml-stream-perl, but
> never managed to nail it down.

It actually took me a while, too ;). I think I ended up in XML-Stream
because of the debug output, especially the binary part that was printed
in the output of a read operation. A few detours later, I found the
IO-Socket-SSL release where it stopped working and remembered that
start_SSL() was called in XML::Stream and that an example in the
documentation somewhere passed a hostname, which wasn't done in
XML::Stream. In conclusion, the error handling in XML::Stream (and maybe
Net::XMPP as well) seems to have some room for improvement, and I also
noticed that some messages in the debug output are quite misleading (the
"We are secure", for example, that was printed in TLSClientProceed(),
simply wasn't correct, at this point, upgrading the socket to SSL/TLS
had failed).


> > Since the upstream seems quite inactive, it might be worth considering
> > to add this or a similar patch to the package in Debian, as I came
> > across several other bug reports in the Debian BTS which might actually
> > be caused by this issue, like #986971 [2], #1032868 [3] and maybe also
> > #1050336 [4] - at least the error messages in the first two look very
> > similar to what I saw.
>
> I've uploaded libxml-stream-perl 1.24-5 to unstable right now.

Thanks! I quickly tested this package and can confirm that it works for
me.


> I'd like to invite the submitters of the other bugs to tests if there
> problems are fixed with libxml-stream-perl 1.24-5.
>
> If yes, I'm happy to
> - do some BTS manipulation
> - more relevant: get this fix into bookworm for the next point
>   release.

This would be great, thanks!


Cheers,
Manfred

Bug#1063338: dlm: cannot start dlm midcomms -97

[Salvatore Bonaccorso]

Control: tags -1 + pending confirmed

Hi,

The fix for this issue landed in v6.1.78 and is pending for a next
upload.

Regards,
Salvatore

Bug#1064299: console-setup: move files to /usr (DEP17)

[Helmut Grohne]

Source: console-setup
Version: 1.226
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
aliasing. console-setup is involved, because it ships quite a few
aliased files. I'm sending a patch, because it cannot be automatically
converted using dh-sequence-movetousr. I note that the Debian installer
is producing a merged-/usr filesystem since a few months. Also take 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 console-setup-1.226/debian/changelog 
console-setup-1.227/debian/changelog
--- console-setup-1.226/debian/changelog2024-02-09 15:45:38.0 
+0100
+++ console-setup-1.227/debian/changelog2024-02-18 13:51:52.0 
+0100
@@ -1,3 +1,10 @@
+console-setup (1.227) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * DEP17: Move aliased files to /usr. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 18 Feb 2024 13:51:52 +0100
+
 console-setup (1.226) unstable; urgency=medium
 
   * Team upload
diff --minimal -Nru console-setup-1.226/debian/console-setup-udeb.postinst 
console-setup-1.227/debian/console-setup-udeb.postinst
--- console-setup-1.226/debian/console-setup-udeb.postinst  2024-02-09 
15:45:38.0 +0100
+++ console-setup-1.227/debian/console-setup-udeb.postinst  2024-02-18 
13:51:52.0 +0100
@@ -96,7 +96,7 @@
 fi
 fi
 
-if ! [ -d /lib/debian-installer.d ]; then
+if ! [ -d /usr/lib/debian-installer.d ]; then
 dpkg-maintscript-helper rm_conffile \
 /etc/init.d/keyboard-setup 1.138~ -- "$@"
 dpkg-maintscript-helper rm_conffile \
diff --minimal -Nru console-setup-1.226/debian/console-setup.postrm 
console-setup-1.227/debian/console-setup.postrm
--- console-setup-1.226/debian/console-setup.postrm 2024-02-09 
15:45:38.0 +0100
+++ console-setup-1.227/debian/console-setup.postrm 2024-02-18 
13:51:52.0 +0100
@@ -7,7 +7,7 @@
 fi
 
 if [ remove = "$1" -o purge = "$1" ]; then
-if [ ! -f /bin/setupcon ]; then
+if [ ! -f /usr/bin/setupcon ]; then
 rm -f /etc/console-setup/cached_*
 fi
 fi
diff --minimal -Nru console-setup-1.226/debian/keyboard-configuration.postinst 
console-setup-1.227/debian/keyboard-configuration.postinst
--- console-setup-1.226/debian/keyboard-configuration.postinst  2024-02-09 
15:45:38.0 +0100
+++ console-setup-1.227/debian/keyboard-configuration.postinst  2024-02-18 
13:51:52.0 +0100
@@ -96,7 +96,7 @@
 fi
 fi
 
-if ! [ -d /lib/debian-installer.d ]; then
+if ! [ -d /usr/lib/debian-installer.d ]; then
 dpkg-maintscript-helper rm_conffile \
 /etc/init.d/keyboard-setup 1.138~ -- "$@"
 dpkg-maintscript-helper rm_conffile \
diff --minimal -Nru console-setup-1.226/debian/rules 
console-setup-1.227/debian/rules
--- console-setup-1.226/debian/rules2024-02-09 15:45:38.0 +0100
+++ console-setup-1.227/debian/rules2024-02-18 13:51:52.0 +0100
@@ -110,11 +110,11 @@
$(MAKE) etcdir=debian/console-setup-linux/etc \
prefix=debian/console-setup-linux/usr install-common-linux
dh_install -p console-setup-linux \
-   init/90-console-setup.rules lib/udev/rules.d/
+   init/90-console-setup.rules usr/lib/udev/rules.d/
dh_install -p console-setup-linux \
-   init/keyboard-setup.sh lib/console-setup/
+   init/keyboard-setup.sh usr/lib/console-setup/
dh_install -p console-setup-linux \
-   init/console-setup.sh lib/console-setup/
+   init/console-setup.sh usr/lib/console-setup/
dh_systemd_enable -p console-setup-linux \
--name keyboard-setup
dh_systemd_enable -p console-setup-linux \
@@ -138,9 +138,9 @@
$(MAKE) etcdir=debian/console-setup-freebsd/etc \
prefix=debian/console-setup-freebsd/usr install-common-freebsd
dh_install -p console-setup-freebsd \
-   init/keyboard-setup.sh lib/console-setup/
+   init/keyboard-setup.sh usr/lib/console-setup/
dh_install -p console-setup-freebsd \
-   init/console-setup.sh lib/console-setup/
+   init/console-setup.sh usr/lib/console-setup/
dh_systemd_enable -p console-setup-freebsd \
--name keyboard-setup
dh_systemd_enable -p console-setup-freebsd \
@@ -164,14 +164,16 @@
dh_prep -p console-setup
dh_prep -p console-setup-mini
$(MAKE) etcdir=debian/console-setup/etc \
-   prefix=debian/console-setup/usr install-common
+   prefix=debian/console-setup/usr \
+   bootprefix=debian/console-setup/usr install-common
$(MAKE) etcdir=debian/console-setup/etc \

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

[Salvatore Bonaccorso]

Hi,

On Mon, Feb 19, 2024 at 10:35:13AM +0800, Chao Yu wrote:
> 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

Confirmed that this fixes the reported issue as it was reported to us
in Debian in https://bugs.debian.org/1063422 . Thanks a lot!
(note just tested with the first commit as it landed in 6.1.78 to
confirm the immediate regression).

#regzbot fixed-by: cf3d57ad6ff8b566deba3544b9ad3384781fb604

Regards,
Salvatore

Bug#1064298: libhamlib4t64: ineffective replaces due to /usr-move

[Helmut Grohne]

Package: libhamlib4t64
Version: 4.5.5-3.1~exp1
Severity: serious
Tags: patch
User: helm...@debian.org
Usertags: dep17p1
Control: affects -1 + libhamlib4
X-Debbugs-Cc: vor...@debian.org, mwhud...@debian.org

libhamlib4t64 introduced Replaces for libhamlib4 to take over its files
and in that process it also takes over
/usr/lib/udev/rules.d/60-libhamlib4.rules. This file also is in
libhamlib4 in an aliased location. Moving a file from / to /usr and
between packages causes file loss (DEP17 P1). Hence, I'm extending the
existing mitigation for DEP17 P7 (M-A:same shared file loss) to cover
the new P1 problem introduced by time64. See my attched patch. The
protective diversion will be kept beyond postinst and stay around. Since
the earlier diversion in libhamlib4 was removed in postinst, there
cannot be any conflict on diversions. I tested the upgrade using
piuparts.

Helmut
diff --minimal -Nru hamlib-4.5.5/debian/changelog hamlib-4.5.5/debian/changelog
--- hamlib-4.5.5/debian/changelog   2024-02-17 04:43:05.0 +0100
+++ hamlib-4.5.5/debian/changelog   2024-02-19 19:50:40.0 +0100
@@ -1,3 +1,11 @@
+hamlib (4.5.5-3.1~exp1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Extend DEP17 P7 mitigation (protective diversion for udev rules) to also
+cover P1 (package rename). (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 19 Feb 2024 19:50:40 +0100
+
 hamlib (4.5.5-3.1~exp1) experimental; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru hamlib-4.5.5/debian/libhamlib4t64.lintian-overrides 
hamlib-4.5.5/debian/libhamlib4t64.lintian-overrides
--- hamlib-4.5.5/debian/libhamlib4t64.lintian-overrides 2024-02-17 
04:43:05.0 +0100
+++ hamlib-4.5.5/debian/libhamlib4t64.lintian-overrides 2024-02-19 
19:50:40.0 +0100
@@ -1,4 +1,4 @@
 # protective diversion for upgrades of files moved from / to /usr
 # see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056692
-libhamlib4t64: diversion-for-unknown-file 
lib/udev/rules.d/60-libhamlib4t64.rules [preinst:14]
+libhamlib4t64: diversion-for-unknown-file lib/udev/rules.d/60-libhamlib4.rules 
[preinst:*]
 libhamlib4t64: package-name-doesnt-match-sonames libhamlib4
diff --minimal -Nru hamlib-4.5.5/debian/libhamlib4t64.postinst 
hamlib-4.5.5/debian/libhamlib4t64.postinst
--- hamlib-4.5.5/debian/libhamlib4t64.postinst  2024-02-17 04:43:05.0 
+0100
+++ hamlib-4.5.5/debian/libhamlib4t64.postinst  2024-02-19 13:56:14.0 
+0100
@@ -7,17 +7,6 @@
 
 rm -f /etc/udev/rules.d/60-libhamlib4.rules
 
-# begin-remove-after: released:forky
-# protective diversion of files moved from / to /usr, to avoid file loss.
-# Only for upgrades.
-if [ "$1" = "configure" ]; then
-# At this point, the package will have installed the same file in */usr*.
-dpkg-divert --package usr-is-merged --no-rename \
---divert /lib/udev/rules.d/60-libhamlib4.rules.usr-is-merged \
---remove /lib/udev/rules.d/60-libhamlib4.rules
-fi
-# end-remove-after
-
 #DEBHELPER#
 
 exit 0
diff --minimal -Nru hamlib-4.5.5/debian/libhamlib4t64.postrm 
hamlib-4.5.5/debian/libhamlib4t64.postrm
--- hamlib-4.5.5/debian/libhamlib4t64.postrm2024-02-17 04:43:05.0 
+0100
+++ hamlib-4.5.5/debian/libhamlib4t64.postrm2024-02-19 13:56:50.0 
+0100
@@ -5,16 +5,13 @@
 
 dpkg-maintscript-helper rm_conffile /etc/udev/60-libhamlib4.rules -- "$@"
 
-# begin-remove-after: released:forky
 # protective diversion of files moved from / to /usr, to avoid file loss.
 # Only for upgrades.
 if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
-# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
 dpkg-divert --package usr-is-merged --no-rename \
 --divert /lib/udev/rules.d/60-libhamlib4.rules.usr-is-merged \
 --remove /lib/udev/rules.d/60-libhamlib4.rules
 fi
-# end-remove-after
 
 #DEBHELPER#
 
diff --minimal -Nru hamlib-4.5.5/debian/libhamlib4t64.preinst 
hamlib-4.5.5/debian/libhamlib4t64.preinst
--- hamlib-4.5.5/debian/libhamlib4t64.preinst   2024-02-17 04:43:05.0 
+0100
+++ hamlib-4.5.5/debian/libhamlib4t64.preinst   2024-02-19 13:55:31.0 
+0100
@@ -5,15 +5,13 @@
 
 dpkg-maintscript-helper rm_conffile /etc/udev/60-libhamlib4.rules -- "$@"
 
-# begin-remove-after: released:forky
 # protective diversion of files moved from / to /usr, to avoid file loss.
-# Only for upgrades.
-if [ "$1" = "upgrade" ]; then
+if [ "$1" = upgrade ] || [ "$1" = install ]; then
+# The diversion should be removed after trixie is released.
 dpkg-divert --package usr-is-merged --no-rename \
 --divert /lib/udev/rules.d/60-libhamlib4.rules.usr-is-merged \
 --add /lib/udev/rules.d/60-libhamlib4.rules
 fi
-# end-remove-after
 
 #DEBHELPER#
 

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Lucas Castro]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name : foolsm
   Version  : 1.0.21-1
   Upstream contact : [fill in name and email of upstream]
 * URL  :http://lsm.foobar.fi/
 * License  : GPL-2
 * Vcs  : [fill in URL of packaging vcs]
   Section  : utils

The source builds the following binary packages:

  foolsm - Link connectivity monitor tool
  lsm - Link connectivity monitor tool - transitional package

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

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

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

  dget 
-xhttps://mentors.debian.net/debian/pool/main/f/foolsm/foolsm_1.0.21-1.dsc

Changes for the initial release:

 foolsm (1.0.21-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/watch updated
   * debian/patches/ cleaned out

Regards,
--
  Lucas Castro



OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064295: puppet-agent: ununsatisfiable dependencies: depends on ruby-concurrent (< 1.2.0)

[Aurelien Jarno]

Package: puppet-agent
Version: 7.23.0-1
Severity: serious
X-Debbugs-Cc: d...@debian.org

Dear maintainer,

puppet-agent in unstable is not installable anymore as it depends on
ruby-concurrent (< 1.2.0), while the version in unstable is now 1.2.3-2.

Regards
Aurelien

Bug#1064294: bind-dyndb-ldap: FTBFS: error: Install BIND9 development files

[Aurelien Jarno]

Source: bind-dyndb-ldap
Version: 11.10-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

bind-dyndb-ldap fails to build from source, from my build log on amd64:

| checking for -fvisibility=hidden compiler flag... yes
| checking for -fno-delete-null-pointer-checks compiler flag... yes
| checking for -std=gnu11 compiler flag... yes
| checking for isc-config.sh... no
| checking for working isc-config... no
| configure: WARNING:
|   Could not detect script isc-config.sh. Compilation may fail.
|   Defining variable BIND9_CFLAGS will fix this problem.
|   
| checking for isc_dir_open in -lisc... yes
| checking for dns_name_init in -ldns... no
| configure: error: Install BIND9 development files
|   cd build && tail -v -n \+0 config.log

A full build log is also available on riscv64:
https://buildd.debian.org/status/fetch.php?pkg=bind-dyndb-ldap=riscv64=11.10-6%2Bb2=1703783350=0

The issue is also visible on the reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/bind-dyndb-ldap_11.10-6.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/bind-dyndb-ldap_11.10-6.rbuild.log.gz

Regards
Aurelien

Bug#1064293: less: CVE-2022-48624

[Salvatore Bonaccorso]

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

Hi,

The following vulnerability was published for less.

CVE-2022-48624[0]:
| close_altfile in filename.c in less before 606 omits shell_quote
| calls for LESSCLOSE.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-48624
https://www.cve.org/CVERecord?id=CVE-2022-48624
[1] https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1064292: pyside2: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: pyside2
Version: 5.15.12-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
pyside2 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 pyside2
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 pyside2-5.15.12/debian/changelog pyside2-5.15.12/debian/changelog
--- pyside2-5.15.12/debian/changelog2024-02-08 08:13:11.0 +
+++ pyside2-5.15.12/debian/changelog2024-02-19 18:32:19.0 +
@@ -1,3 +1,10 @@
+pyside2 (5.15.12-6.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 18:32:19 +
+
 pyside2 (5.15.12-6) unstable; urgency=medium
 
   * Team upload.
diff -Nru pyside2-5.15.12/debian/control pyside2-5.15.12/debian/control
--- pyside2-5.15.12/debian/control  2024-02-08 08:13:11.0 +
+++ pyside2-5.15.12/debian/control  2024-02-19 18:32:19.0 +
@@ -76,13 +76,14 @@
  .
  This package contains the common documentation package.
 
-Package: libpyside2-py3-5.15
+Package: libpyside2-py3-5.15t64
+Breaks: libpyside2-py3-5.15 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
 Conflicts: libpyside2-py3-5.11, libpyside2-py3-5.13, libpyside2-py3-5.14
-Replaces: libpyside2-py3-5.11, libpyside2-py3-5.13, libpyside2-py3-5.14
-Provides: libpyside2-py3
+Replaces: libpyside2-py3-5.15, libpyside2-py3-5.11, libpyside2-py3-5.13, 
libpyside2-py3-5.14
+Provides: ${t64:Provides}, libpyside2-py3
 Description: Python 3 bindings for Qt5 (base files)
  pyside2 provides Python bindings for Qt 5.x framework.
  .
@@ -94,7 +95,7 @@
 Package: libpyside2-dev
 Section: libdevel
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, libpyside2-py3-5.15 (= 
${binary:Version})
+Depends: ${misc:Depends}, ${shlibs:Depends}, libpyside2-py3-5.15t64 (= 
${binary:Version})
 Description: Python bindings for Qt5 (development files)
  pyside2 provides Python bindings for Qt 5.x framework.
  .
@@ -127,13 +128,14 @@
  .
  Shiboken2 is the binding generator used to create the PySide2 bindings.
 
-Package: libshiboken2-py3-5.15
+Package: libshiboken2-py3-5.15t64
+Breaks: libshiboken2-py3-5.15 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
 Conflicts: libshiboken2-py3-5.11, libshiboken2-py3-5.13, libshiboken2-py3-5.14
-Replaces: libshiboken2-py3-5.11, libshiboken2-py3-5.13, libshiboken2-py3-5.14
-Provides: libshiboken2-py3
+Replaces: libshiboken2-py3-5.15, libshiboken2-py3-5.11, libshiboken2-py3-5.13, 
libshiboken2-py3-5.14
+Provides: ${t64:Provides}, libshiboken2-py3
 Description: CPython bindings generator for C++ libraries (Python3 shared 
library)
  Shiboken2 is a bindings generator for C++ libraries that outputs CPython
  source code. It collects information from library headers, and then
@@ -148,7 +150,7 @@
 Section: libdevel
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends},
- libshiboken2-py3-5.15 (= ${binary:Version}), shiboken2 (= ${binary:Version}), 
python3-dev
+ 

Bug#1064291: ITP: python-awkward -- manipulate JSON-like data with NumPy-like idioms

[Sascha Steinbiss]

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

* Package name: python-awkward
  Version : 2.6.1
  Upstream Contact: Jim Pivarski 
* URL : https://github.com/scikit-hep/awkward
* License : BSD-3-clause
  Programming Lang: Python,  C++
  Description : manipulate JSON-like data with NumPy-like idioms

Awkward Array is a library for nested, variable-sized data, including
arbitrary-length lists, records, mixed types, and missing data, using
NumPy-like idioms. Arrays are dynamically typed, but operations on them
are compiled and fast. Their behavior coincides with NumPy when array
dimensions are regular and generalizes when they're not.

This is packaged as a dependency for another package under the umbrella
of the Debian Med packaging team.

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

[Steve Langasek]

Sorry, somehow it happens that if I DIDN'T change pkgconfig path handling
the package FTBFS for me locally, but since I DID change this in the NMU it
FTBFS in experimental.

Here's a follow-on NMU patch with that part reverted.


On Mon, Feb 19, 2024 at 07:38:45AM +, Steve Langasek wrote:
> 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/changelog2021-10-21 19:17:21.0 
> +
> +++ openzwave-1.6.1914+ds/debian/changelog2024-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/control  2021-10-21 19:17:21.0 
> +
> +++ openzwave-1.6.1914+ds/debian/control  2024-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.install  2021-10-21 
> 19:17:21.0 +
> +++ openzwave-1.6.1914+ds/debian/libopenzwave1.6-dev.install  2024-02-19 
> 

Bug#1064290: mirror listing update for elmirror.cl

[Jonathan Gutierrez]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: elmirror.cl
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd-amd64 i386 
mips mips64el mipsel powerpc ppc64el riscv64 s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Jonathan Gutierrez 
Country: CL Chile
Location: Santiago
Sponsor: ElMirror.cl team https://elmirror.cl




Trace Url: http://elmirror.cl/debian/project/trace/
Trace Url: http://elmirror.cl/debian/project/trace/ftp-master.debian.org
Trace Url: http://elmirror.cl/debian/project/trace/elmirror.cl

Bug#1064289: mirror submission for elmirror.cl

[https://elmirror.cl]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: elmirror.cl
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd-amd64 i386 
mips mips64el mipsel powerpc ppc64el riscv64 s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: https://elmirror.cl 
Country: CL Chile
Location: Santiago
Sponsor: ElMirror.cl team https://elmirror.cl




Trace Url: http://elmirror.cl/debian/project/trace/
Trace Url: http://elmirror.cl/debian/project/trace/ftp-master.debian.org
Trace Url: http://elmirror.cl/debian/project/trace/elmirror.cl

Bug#1064288: Missing /skole directory.

[Daniel Teichmann]

Package: debian-edu-fai
Version: bookworm

Dear Maintainers,

I've noticed that the /skole directory was missing, therefore no /home 
could be mounted for a user.

The user couldn't log into a workstation, because of that.

I guess the missing dir should be created via puppet.

Greetings

Daniel Teichmann
DAS-NETZWERKTEAM
Telefon: 0176 322 774 51
GnuPG Key ID: 0x8100A778
daniel.teichm...@das-netzwerkteam.de, https://das-netzwerkteam.de

Bug#1063746: Upload request for golang-github-katalix-go-l2tp 0.1.7-1

[Tom Parkin]

Hi folks,

Would someone mind please reviewing and uploading
golang-github-katalix-go-l2tp 0.1.7-1?

https://salsa.debian.org/go-team/packages/golang-github-katalix-go-l2tp

The package is updated to remove the L2TPIP6 transport test, which is
failing due to the backport of an upstream kernel regression to the
stable kernel which at least Debian Bookworm is running.

Once we have a fix for the kernel regression we can re-enable the unit
test, but for the time being removing the test is the most direct
approach for addressing the CI failures captured by #1063746.

Thanks and best regards,
Tom
-- 
Tom Parkin
Katalix Systems Ltd
https://katalix.com
Catalysts for your Embedded Linux software development


signature.asc
Description: PGP signature

Bug#1060898: apfs-dkms: fails to build module: super.c:17:10: fatal error: version.h: No such file or directory

[Gürkan Myczko]

Hi Andreas,


attached you can find an overhaul of the package installation that also
fixes the missing version.h

Having the Debian revision included in the dkms module version is very
unusual, now this only uses the upstream version.


Looks good except it didn't install/build for me, maybe I did something 
wrong...


The Vcs-* URLs in the package point to an empty repository ... 
otherwise

you could have gotten a MR with a sequence of commits.


So sorry, moved to bananas team, but never filled it, now it's there and 
ready.

Feel free to go ahead with a team upload...

Best,
Alex


Andreas

Bug#1064287: RFS: winff/1.6.3+dfsg-1 -- graphical video and audio batch converter using ffmpeg or avconv

[Peter B]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : winff
   Version  : 1.6.3+dfsg-1
   Upstream contact : Matthew Weatherford 
 * URL  : https://github.com/WinFF/winff
 * License  : GFDL-1.3+, GPL-2+, GPL-3+
 * Vcs  : https://salsa.debian.org/pascal-team/winff
   Section  : video

The source builds the following binary packages:

  winff - graphical video and audio batch converter using ffmpeg or avconv
  winff-qt - Qt variant of winff
  winff-data - winff data files
  winff-doc - winff documentation

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/w/winff/winff_1.6.3+dfsg-1.dsc


Changes since the last upload:

 winff (1.6.3+dfsg-1) unstable; urgency=medium
 .
   * New Upstream release (Closes: #1053373) (Closes: #1061586)
   * Drop patch adopted upstream
   * Update copyright date

Regards,
--
  Peter Blackman

Bug#1064267: fontconfig 2.15 breaks color emoji

[Markus Koller]

Found the upstream bug: 
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/400

> It seems the font is considered as a bitmap font now (wasn't the case in 
> 2.14.x) and because of no-bitmap.conf, the emoji font wouldn't load. Removing 
> this conf file makes the emoji font load fine. I am unsure whether to 
> consider this as a regression, but for now I will close this issue.

After running "dpkg-reconfigure fontconfig-config" and enabling bitmap fonts 
the color emoji indeed work again.

Greetings,
Markus

Bug#1063746: (no subject)

[Tom Parkin]

I believe the root cause of this issue is this backported kernel
commit:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/net/l2tp/l2tp_ip6.c?h=linux-6.1.y=f6a7182179c0ed788e3755ee2ed18c888ddcc33f

The commit is present from Linux v6.6 onwards and has been backported
to at least the linux-6.1.y series stable kernels.

I will work on a kernel fix, but in the meantime the go-l2tp package
will have to remove the testcase in order to address this bug.


signature.asc
Description: PGP signature

Bug#1064286: puppet-lint: please backport v4 to bookworm

[Louis-Philippe Véronneau]

Package: puppet-lint
Version: 4.2.4-1
Severity: wishlist

Dear maintainers,

Would it be possible to backport this package to bookworm? v4 introduces 
the `legacy_facts` check, which is very important, since the 
puppet-agent 7 to 8 transition deprecates those.


Having puppet-lint v4 backported would ease this transition a lot, since 
people could lint their existing code base with this new check before 
migrating to Trixie.


Cheers, and thanks for maintaining this package,

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#1064285: dante: NMU diff for 64-bit time_t transition

[Michael Hudson-Doyle]

Source: dante
Version: 1.4.2+dfsg-7build8
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
dante 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 $src
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 was uploaded to experimental last week (apologies, somehow
filing the bug failed), 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 mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru dante-1.4.2+dfsg/debian/changelog dante-1.4.2+dfsg/debian/changelog
--- dante-1.4.2+dfsg/debian/changelog   2019-09-12 11:17:28.0 +
+++ dante-1.4.2+dfsg/debian/changelog   2024-02-05 02:19:17.0 +
@@ -1,3 +1,10 @@
+dante (1.4.2+dfsg-7.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle   Mon, 05 Feb 2024 02:19:17 +
+
 dante (1.4.2+dfsg-7) unstable; urgency=medium
 
   * Run dpkg-gensymbols with -c4 for more stringent checks.
diff -Nru dante-1.4.2+dfsg/debian/control dante-1.4.2+dfsg/debian/control
--- dante-1.4.2+dfsg/debian/control 2019-09-12 11:17:28.0 +
+++ dante-1.4.2+dfsg/debian/control 2024-02-05 02:19:17.0 +
@@ -10,7 +10,10 @@
 Vcs-Browser: https://gitlab.com/dante/pkg-debian-full
 Rules-Requires-Root: no
 
-Package: libsocksd0
+Package: libsocksd0t64
+Provides: ${t64:Provides}
+Replaces: libsocksd0
+Breaks: libsocksd0 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -28,7 +31,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libsocksd0 (= ${binary:Version}), ${misc:Depends}
+Depends: libsocksd0t64 (= ${binary:Version}), ${misc:Depends}
 Description: Development files for compiling programs with SOCKS support
  Dante is a circuit-level firewall/proxy that can be used to provide
  convenient and secure network connectivity to a wide range of hosts
@@ -38,7 +41,10 @@
  This package provides header files and instructions for compiling programs
  with SOCKS support.
 
-Package: libdsocksd0
+Package: libdsocksd0t64
+Provides: ${t64:Provides}
+Replaces: libdsocksd0
+Breaks: libdsocksd0 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -56,7 +62,7 @@
 Architecture: all
 Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${perl:Depends},
- libdsocksd0 (>= ${source:Version}), libfile-which-perl
+ libdsocksd0t64 (>= ${source:Version}), libfile-which-perl
 Description: SOCKS wrapper for users behind a firewall
  Dante is a circuit-level firewall/proxy that can be used to provide
  convenient and secure network connectivity to a wide range of hosts
diff -Nru dante-1.4.2+dfsg/debian/libdsocksd0.install 
dante-1.4.2+dfsg/debian/libdsocksd0.install
--- dante-1.4.2+dfsg/debian/libdsocksd0.install 2019-09-12 11:17:28.0 
+
+++ dante-1.4.2+dfsg/debian/libdsocksd0.install 1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/libdsocksd.so.*
diff -Nru dante-1.4.2+dfsg/debian/libdsocksd0.lintian-overrides 
dante-1.4.2+dfsg/debian/libdsocksd0.lintian-overrides
--- dante-1.4.2+dfsg/debian/libdsocksd0.lintian-overrides   

Bug#1064284: pcp: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: pcp
Version: 6.2.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
pcp 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 pcp
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 pcp-6.2.0/debian/changelog pcp-6.2.0/debian/changelog
--- pcp-6.2.0/debian/changelog  2024-02-11 22:18:37.0 +
+++ pcp-6.2.0/debian/changelog  2024-02-19 16:49:15.0 +
@@ -1,3 +1,10 @@
+pcp (6.2.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 19 Feb 2024 16:49:15 +
+
 pcp (6.2.0-1) unstable; urgency=low
 
   * New release (full details in CHANGELOG).
diff -Nru pcp-6.2.0/debian/control pcp-6.2.0/debian/control
--- pcp-6.2.0/debian/control2024-02-11 22:18:37.0 +
+++ pcp-6.2.0/debian/control2024-02-19 16:49:14.0 +
@@ -9,7 +9,7 @@
 X-Python3-Version: >= 3.3
 
 Package: pcp
-Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, python3-pcp, 
python3, libpcp-pmda3 (= ${binary:Version}), libpcp-mmv1 (= ${binary:Version}), 
libpcp-web1 (= ${binary:Version}), libpcp-archive1 (= ${binary:Version}), 
libpcp3 (= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, python3-pcp, 
python3, libpcp-pmda3t64 (= ${binary:Version}), libpcp-mmv1t64 (= 
${binary:Version}), libpcp-web1t64 (= ${binary:Version}), libpcp-archive1t64 (= 
${binary:Version}), libpcp3t64 (= ${binary:Version})
 Recommends: libpcp-pmda-perl
 Conflicts: pgpool2, dstat, pcp-webapi, pcp-manager
 Suggests: pcp-gui, libpcp-import-perl, bpftrace (>= 0.9.2) [amd64 arm64 
ppc64el], python3-bpfcc [amd64 arm64 armhf ppc64el s390x ppc64], redis-server
@@ -28,7 +28,7 @@
 
 Package: pcp-conf
 Depends: ${misc:Depends}
-Breaks: libpcp3 (<< 3.9.0), pcp (<< 4.0.1)
+Breaks: libpcp3t64 (<< 3.9.0), pcp (<< 4.0.1)
 Section: libs
 Architecture: any
 Description: Performance Co-Pilot runtime configuration
@@ -43,7 +43,7 @@
 
 Package: libpcp3-dev
 Section: libdevel
-Depends: ${misc:Depends}, libpcp3 (= ${binary:Version}), libc6-dev | libc-dev
+Depends: ${misc:Depends}, libpcp3t64 (= ${binary:Version}), libc6-dev | 
libc-dev
 Breaks: pcp (<< 4.3.4), libpcp-gui2-dev (<< 3.11.10~), pcp-webapi (<< 5.0.0), 
pcp-manager (<< 5.2.0)
 Replaces: libpcp-gui2-dev (<< 3.11.10~), pcp-webapi (<< 5.0.0), pcp-manager 
(<< 5.2.0)
 Architecture: any
@@ -57,10 +57,12 @@
  client applications to easily retrieve and process any subset of
  that data.
 
-Package: libpcp3
+Package: libpcp3t64
+Provides: ${t64:Provides}
+Replaces: libpcp3
 Depends: ${shlibs:Depends}, ${misc:Depends}, pcp-conf (= ${binary:Version})
 Conflicts: pgpool2
-Breaks: pcp (<< 2.8.0), libpcp3-dev (<< 2.8.5)
+Breaks: libpcp3 (<< ${source:Version}), pcp (<< 2.8.0), libpcp3-dev (<< 2.8.5)
 Section: libs
 Architecture: any
 Description: Performance Co-Pilot library
@@ -74,7 +76,7 @@
 
 Package: libpcp-gui2-dev
 Section: libdevel
-Depends: ${misc:Depends}, libpcp-gui2 (= ${binary:Version}), libpcp3 (= 
${binary:Version})
+Depends: ${misc:Depends}, libpcp-gui2t64 (= ${binary:Version}), libpcp3t64 (= 
${binary:Version})

Bug#1052566: additional information

[tony mancill]

On Mon, Feb 19, 2024 at 03:10:09PM +1300, Vladimir Petko wrote:
>  [1] 
> https://salsa.debian.org/java-team/libnative-platform-java/-/merge_requests/4

Merged and uploaded.

Cheers,
tony

Bug#1064194: 535.86.05 breaks Xorg

[Harald Dunkel]

On 2024-02-19 00:29:15, Andreas Beckmann wrote:


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.



Its still broken. I tried Debian's linux-image-6.6.15-amd64 kernel and
upstream's kernel version 6.7.5.

Upstream provides version 535.154.05. Is there some script to create an
nvidia-graphics-drivers source package from it?


Regards

Harri

Bug#1064283: nftlb: Upstream has moved

[Tj]

Source: nftlb
Version: 1.0.7-1
Severity: important
Tags: upstream

The upstream repo was archived read-only in January 2024. From a
netfilter-devel mailing-list post in September 2023 it appears the
upstream moved:

https://lore.kernel.org/netfilter-devel/CAF90-Wg4NTjfUE7pomw8VnQAjSQC2OXa5FQFH_XwK=zf1no...@mail.gmail.com/

to

https://github.com/relianoid/nftlb

Bug#1018795: dh-dlang: support for mapping dpkg-buildflags for ldc but it's not used

[Jeremy Bícha]

The meson bug https://bugs.debian.org/1017087 has been marked done for
a while. Can we close this bug too?

Thank you,
Jeremy Bícha

Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition

[Fabio Fantoni]

Il 18/02/2024 01:20, Steve Langasek ha scritto:

Hi,

It is easiest for us to include cinnamon in the batch NMUs to unstable.

Thanks,


ok, thanks, only small reminder to include the missed Breaks 
(https://salsa.debian.org/cinnamon-team/cinnamon-desktop/-/commit/b06e59910a83b2252b866d051ffe7c5ea6f6742f) 
in the NMU patch




OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064281: ghdl: Building ghdl fails if LLVM and Clang versions are not provided explicitly

[Heinrich Schuchardt]

Package: ghdl
Version: 3.0.0+dfsg2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch

Dear Maintainer,

the 3.0.0+dfsg2 packaging requires that LLVM < 17 should be installed.
As this is already the LLVM default we must explicitely install the
LLVM 16 and Clang 16 packages for building.

  * Explicitely use llvm-16, clang-16 (LP: #2047298)

Thanks for considering the patch.


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

Kernel: Linux 6.6.0-14-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ghdl-3.0.0+dfsg2/debian/control ghdl-3.0.0+dfsg2/debian/control
--- ghdl-3.0.0+dfsg2/debian/control 2023-10-01 01:16:46.0 +0200
+++ ghdl-3.0.0+dfsg2/debian/control 2024-02-19 12:49:34.0 +0100
@@ -12,8 +12,8 @@
libmpfr-dev (>= 3.0.0-9~) ,
libgmp-dev (>= 2:5.0.1~) ,
texinfo ,
-   llvm-dev (<< 1:17~) ,
-   clang (>= 1:3.5) ,
+   llvm-16-dev ,
+   clang-16 ,
zlib1g-dev
 Standards-Version: 4.6.2
 Homepage: https://github.com/ghdl/ghdl
diff -Nru ghdl-3.0.0+dfsg2/debian/rules ghdl-3.0.0+dfsg2/debian/rules
--- ghdl-3.0.0+dfsg2/debian/rules   2023-10-01 01:16:46.0 +0200
+++ ghdl-3.0.0+dfsg2/debian/rules   2024-02-19 12:49:34.0 +0100
@@ -4,6 +4,8 @@
 # for Ada code anyway
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-format
 
+export PATH:=$(PATH):/usr/lib/llvm-16/bin
+
 #export DH_VERBOSE = 1
 
 include /usr/share/dpkg/default.mk

Bug#1063897: firefox: poor performance compared to vendor package

[Laurent Bigonville]

On Wed, 14 Feb 2024 16:49:59 +0100 Sylvestre Ledru 
 wrote:

>
> Le 14/02/2024 à 13:00, Lorenzo Bertini a écrit :
> > Dear Maintainer,
> >
> > Firefox on debian (both ESR and sid versions) is performing poorly. 
Here are the

> > results on one of my machines, but it's consistent with all the others:
> >
> > Test: Browserbench Speedometer 2.1 
(https://browserbench.org/Speedometer2.1)

> >
> > Gentoo: 290 (+65%)
> > Debian sid with vendor package: 260 (+50%)
> > Debian sid firefox: 175 (-)
> > Debian sid firefox-esr: 160 (-10%)
> >
> > Upon inspection, I think the cause is the optimization flags, 
including LTO, PGO, O3.
> > Please take this report in consideration, as the performance 
increase is massive.

>

> it is expected and why Mozilla is providing a Debian package now

AFACS, the packages provided by mozilla are only 
nightly/devedition/beta, but there is no stable release with the 
optimizations, or am I overlooking something?

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

[matte . mb2006 . 9990]

On Mon, 19 Feb 2024 00:18:29 +0100 Andreas Beckmann 
wrote:
> 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
> 
> 
Yes.
# deb cdrom:[Debian GNU/Linux 12.4.0 _Bookworm_ - Official amd64 DVD Binary-1 with firmware 20231210-17:57]/ bookworm main non-free-firmware

deb http://deb.debian.org/debian/ bookworm main non-free-firmware contrib non-free
deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware contrib non-free

deb http://security.debian.org/debian-security bookworm-security main non-free-firmware contrib non-free
deb-src http://security.debian.org/debian-security bookworm-security main non-free-firmware contrib non-free

# bookworm-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.debian.org/debian/ bookworm-updates main non-free-firmware contrib non-free
deb-src http://deb.debian.org/debian/ bookworm-updates main non-free-firmware contrib non-free

Bug#1064280: scikit-learn: armhf tests failing: not giving expected divide-by-zero warning

[Drew Parsons]

Source: scikit-learn
Version: 1.4.1.post1+dfsg-1
Severity: normal

sklearn 1.4 is passing most tests but two remain "failing" on armhf.

test_tfidf_no_smoothing and test_qda_regularization are "expected to
fail" by emitting a divide-by-zero warning, but they emit no such
exception.

I guess it's a particularity of the way armhf handles floating point
calculations.  I'd suggest just skipping these two tests on armhf,
unless upstream wants to inspect more deeply to fix it.

armhf was already failing tests so this will not prevent migration to
testing (i.e. no need for severity: serious).