Bug#1068035: marked as done (FTBFS: wrong --link-doc target)

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 05:50:29 +
with message-id 
and subject line Bug#1068035: fixed in mdbtools 1.0.0+dfsg-1.3
has caused the Debian Bug report #1068035,
regarding FTBFS: wrong --link-doc target
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdbtools
Version: 1.0.0+dfsg-1.2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=mdbtools=arm64=1.0.0%2Bdfsg-1.2%2Bb2=1711715505=0

dh_installdocs --no-package=mdbtools-doc --link-doc=libmdb3
dh_installdocs: error: Requested unknown package libmdb3 via --link-doc,
expected one of: mdbtools mdbtools-dev libmdb3t64 libmdbsql3t64 odbc-mdbtools
mdbtools-doc

It should be changed to libmdb3t64.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: mdbtools
Source-Version: 1.0.0+dfsg-1.3
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
mdbtools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated mdbtools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 27 Apr 2024 05:11:37 +
Source: mdbtools
Architecture: source
Version: 1.0.0+dfsg-1.3
Distribution: unstable
Urgency: medium
Maintainer: Jean-Michel Vourgère 
Changed-By: Steve Langasek 
Closes: 1068035
Changes:
 mdbtools (1.0.0+dfsg-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use correct package for doc target.  Closes: #1068035.
Checksums-Sha1:
 c28355eb9bcb795abe129bc575484bedc66c6ca6 2393 mdbtools_1.0.0+dfsg-1.3.dsc
 f13693086712c9c566ed8a24ad3a0923269fee4b 15516 
mdbtools_1.0.0+dfsg-1.3.debian.tar.xz
 468bbd728b36904c0f1085d78a89a1fb80cb0ed1 7043 
mdbtools_1.0.0+dfsg-1.3_source.buildinfo
Checksums-Sha256:
 f333ff256e20a373f65baa1ca639ff33950f384e4bda60af81aa5f260b8e6bf3 2393 
mdbtools_1.0.0+dfsg-1.3.dsc
 c59c9dc40b30e89f193e51ce76daddf9a55881e14019f57a321221dafb13392a 15516 
mdbtools_1.0.0+dfsg-1.3.debian.tar.xz
 9869fa47be5676661973cf9b990e306c11b8eb1579f41675bff5da2f8e2e0588 7043 
mdbtools_1.0.0+dfsg-1.3_source.buildinfo
Files:
 116f58b4591787b8b67affd0f57313da 2393 database optional 
mdbtools_1.0.0+dfsg-1.3.dsc
 013af2d96dc151173e882f2c5740ed56 15516 database optional 
mdbtools_1.0.0+dfsg-1.3.debian.tar.xz
 58e70298b59652776b59279383f7a8af 7043 database optional 
mdbtools_1.0.0+dfsg-1.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmYsi3sSHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9oWwP/i2Y3Lyd4RICDfDZ+QaNo1vCkjpgkKrU
iAlKEOV+VjDdzB8m6gK343xyaOE0C3BPrWqINL92A2o8YkFmDfjzcNIcXVtsVv13
3lsfwijGBhaK2euNZMxzz15v/ru+CLmOBKPcxWJ/2sATGay7m8Nn7JIUlphtn0f4
JvDh1qTBVFvkmXz67WAXEwkBSaa5E+0AXaLmc8nxfAhSrVDCQOqtkldRk04cAbxh
nOdJES+h9hDsjxGTKn1Q+q+qqFJy3E+ZFeHQ2F8YvPDRbHxenTwHONepstr0xa+H
SoViiLZat5P66/LK6TDQvFlvpwTesnzIVEkpJ/tw3DJ8NLFiJURQx4IIFdotrojd
8L5KMlPOp75XLGEVKqT8DoHl40MBGTIiKzyz9tev94Hh6hcxtSEjudGeEPxZLaOX
8wkkOb9ujAxdSaDRiUAYGMn2W6UeGRkoL/Jx8CQKgESAwZVi9xleBfZXiGoypBtp
DhYE/RbNOv4cnweLTKEnd7NHNSDK8sJf/wED8/UsfSmHLT6ta30BKT0ukmAU2r+x
ST6tK8IxIUEtvNylNztEy5EDq+t21vvInfrDY2hKllwHU4RhfnfFjHVCommmr7ul
LYUk3BwhcZ+fJ4a/snrituL5RIcPN0SaElmBrs5tjLIT6e4ilNplx/TtujSRqxpA
TXltnku8oXqM
=Evgx
-END PGP SIGNATURE-



pgplpkRMoQk9m.pgp
Description: PGP signature
--- End Message ---

Bug#1069888: marked as done (node-bunyan: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 05:36:27 +
with message-id 
and subject line Bug#1069888: fixed in node-bunyan 2.0.5+~cs4.4.3-3
has caused the Debian Bug report #1069888,
regarding node-bunyan: FTBFS: failing tests
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:node-bunyan
Version: 2.0.5+~cs4.4.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link node_modules/exeunt -> ../exeunt
Link node_modules/mv -> ../mv
Link node_modules/safe-json-stringify -> ../safejsonstringify
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/bunyan
/bin/sh -ex debian/tests/pkg-js/test
+ tap -R tap -J --no-cov test/add-stream.test.js test/buffer.test.js 
test/child-behaviour.test.js test/cli-client-req.test.js test/cli-res.test.js 
test/cli.test.js test/ctor.test.js test/cycles.test.js test/error-event.test.js 
test/level.test.js test/log.test.js test/other-api.test.js 
test/process-exit.test.js test/raw-stream.test.js test/ringbuffer.test.js 
test/safe-json-stringify.test.js test/serializers.test.js test/src.test.js 
test/stream-levels.test.js
TAP version 13
# Subtest: test/add-stream.test.js
# Subtest: non-writables passed as stream
ok 1 - "stream" stream is not writable
ok 2 - "stream" stream is not writable
1..2
ok 1 - non-writables passed as stream # time=18.713ms

# Subtest: proper stream

ok 1 - expect truthy value
1..1
ok 2 - proper stream # time=4.908ms

1..2

# time=46.964ms
ok 1 - test/add-stream.test.js # time=46.964ms

# Subtest: test/buffer.test.js
# Subtest: log.info(BUFFER)
ok 1 - log.trace msg is inspect(BUFFER)
ok 2 - no "0" array index key in record: undefined
ok 3 - no "parent" array index key in record: undefined
ok 4 - log.trace(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 5 - log.debug msg is inspect(BUFFER)
ok 6 - no "0" array index key in record: undefined
ok 7 - no "parent" array index key in record: undefined
ok 8 - log.debug(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 9 - log.info msg is inspect(BUFFER)
ok 10 - no "0" array index key in record: undefined
ok 11 - no "parent" array index key in record: undefined
ok 12 - log.info(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 13 - log.warn msg is inspect(BUFFER)
ok 14 - no "0" array index key in record: undefined
ok 15 - no "parent" array index key in record: undefined
ok 16 - log.warn(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 17 - log.error msg is inspect(BUFFER)
ok 18 - no "0" array index key in record: undefined
ok 19 - no "parent" array index key in record: undefined
ok 20 - log.error(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 21 - log.fatal msg is inspect(BUFFER)
ok 22 - no "0" array index key in record: undefined
ok 23 - no "parent" array index key in record: undefined
ok 24 - log.fatal(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
1..24
ok 1 - log.info(BUFFER) # time=15.595ms

1..1

# time=36.998ms
ok 2 - test/buffer.test.js # time=36.998ms

# Subtest: test/child-behaviour.test.js
# Subtest: child can add stream
ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
1..4
ok 1 - child can add stream # time=8.798ms

# Subtest: child can set level of inherited streams

ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
1..3
ok 2 - child can set level of inherited streams # time=2.496ms

# Subtest: child can set level of inherited streams and add streams

ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
ok 5 - should be 

Processed: Re: FTBFS: wrong --link-doc target

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1068035 [src:mdbtools] FTBFS: wrong --link-doc target
Added tag(s) patch.

-- 
1068035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068035: FTBFS: wrong --link-doc target

[Steve Langasek]

Package: mdbtools
Version: 1.0.0+dfsg-1.2
Followup-For: Bug #1068035
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Hi Jean-Michel,

I am unclear how there are binaries in the archive for mdbtools
1.0.0+dfsg-1.2, given this bug is present there and affects all
architectures.  Nevertheless, the fix for the problem is attached.  As this
is fallout from the time_t transition, I am uploading a 0-day NMU to correct
the issue.

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
diff -Nru mdbtools-1.0.0+dfsg/debian/rules mdbtools-1.0.0+dfsg/debian/rules
--- mdbtools-1.0.0+dfsg/debian/rules2023-04-03 05:46:44.0 -0700
+++ mdbtools-1.0.0+dfsg/debian/rules2024-04-22 22:55:55.0 -0700
@@ -8,5 +8,5 @@
dh_auto_configure -- --with-unixodbc=/usr
 
 override_dh_installdocs:
-   dh_installdocs --no-package=mdbtools-doc --link-doc=libmdb3
+   dh_installdocs --no-package=mdbtools-doc --link-doc=libmdb3t64
dh_installdocs --package=mdbtools-doc

Processed: Bug#1069888 marked as pending in node-bunyan

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1069888 [src:node-bunyan] node-bunyan: FTBFS: failing tests
Added tag(s) pending.

-- 
1069888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069888: marked as pending in node-bunyan

[Yadd]

Control: tag -1 pending

Hello,

Bug #1069888 in node-bunyan reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-bunyan/-/commit/67134e3efbb67ddfc7cd9d33a0223b02d3e56893


Drop one unstable test

Closes: #1069888


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069888

Processed: found 1057581 in 8.0.1-1, fixed 1057581 in 8.0.1-11

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1057581 8.0.1-1
Bug #1057581 {Done: Yadd } [node-get-stream] node-clipanion: 
FTBFS: error TS2307: Cannot find module 'get-stream' or its corresponding type 
declarations.
Marked as found in versions node-get-stream/8.0.1-1 and reopened.
> fixed 1057581 8.0.1-11
Bug #1057581 [node-get-stream] node-clipanion: FTBFS: error TS2307: Cannot find 
module 'get-stream' or its corresponding type declarations.
Marked as fixed in versions node-get-stream/8.0.1-11.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1057581 to node-get-stream, affects 1057581

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1057581 node-get-stream
Bug #1057581 {Done: Yadd } [src:node-clipanion] 
node-clipanion: FTBFS: error TS2307: Cannot find module 'get-stream' or its 
corresponding type declarations.
Bug reassigned from package 'src:node-clipanion' to 'node-get-stream'.
No longer marked as found in versions node-clipanion/3.2.1+dfsg-1.
No longer marked as fixed in versions node-get-stream/8.0.1-11.
> affects 1057581 node-clipanion
Bug #1057581 {Done: Yadd } [node-get-stream] node-clipanion: 
FTBFS: error TS2307: Cannot find module 'get-stream' or its corresponding type 
declarations.
Added indication that 1057581 affects node-clipanion
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069518: marked as done (projecteur: FTBFS on armhf: deviceinput.cc:697:64: error: narrowing conversion of ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’ {aka ‘short u

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 02:36:37 +
with message-id 
and subject line Bug#1069518: fixed in projecteur 0.10-3
has caused the Debian Bug report #1069518,
regarding projecteur: FTBFS on armhf: deviceinput.cc:697:64: error: narrowing 
conversion of ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} 
to ‘__u16’ {aka ‘short unsigned int’} [-Werror=narrowing]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: projecteur
Version: 0.10-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -DCXX_COMPILER_ID=GNU -DCXX_COMPILER_VERSION=13.2.0 
> -DHAS_Qt_DBus=1 -DHAS_Qt_X11Extras=1 -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB 
> -I/<>/obj-arm-linux-gnueabihf/projecteur_autogen/include 
> -I/<>/src 
> -I/<>/obj-arm-linux-gnueabihf/version/projecteur -isystem 
> /usr/include/arm-linux-gnueabihf/qt5 -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtCore -isystem 
> /usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQuick -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQmlModels -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQml -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtX11Extras -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtDBus -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -std=gnu++14 -Wall -Wextra -Werror -fPIC -MD -MT 
> CMakeFiles/projecteur.dir/src/devicescan.cc.o -MF 
> CMakeFiles/projecteur.dir/src/devicescan.cc.o.d -o 
> CMakeFiles/projecteur.dir/src/devicescan.cc.o -c 
> /<>/src/devicescan.cc
> /<>/src/deviceinput.cc: In member function ‘void 
> InputMapper::Impl::emitNativeKeySequence(const NativeKeySequence&)’:
> /<>/src/deviceinput.cc:697:64: error: narrowing conversion of 
> ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’ 
> {aka ‘short unsigned int’} [-Werror=narrowing]
>   697 |   events.emplace_back(input_event{{}, ie.type, ie.code, 
> ie.value});
>   | ~~~^
> /<>/src/deviceinput.cc:697:69: error: missing initializer for 
> member ‘input_event::value’ [-Werror=missing-field-initializers]
>   697 |   events.emplace_back(input_event{{}, ie.type, ie.code, 
> ie.value});
>   | ^
> /<>/src/deviceinput.cc: In lambda function:
> /<>/src/deviceinput.cc:893:55: error: narrowing conversion of 
> ‘(int32_t)de.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’ 
> {aka ‘short unsigned int’} [-Werror=narrowing]
>   893 | struct input_event ie = {{}, de.type, de.code, de.value};
>   |~~~^
> /<>/src/deviceinput.cc:893:60: error: missing initializer for 
> member ‘input_event::value’ [-Werror=missing-field-initializers]
>   893 | struct input_event ie = {{}, de.type, de.code, de.value};
>   |^
> /<>/src/deviceinput.cc: In member function ‘void 
> InputMapper::addEvents(const KeyEvent&)’:
> /<>/src/deviceinput.cc:906:79: error: missing initializer for 
> member ‘input_event::value’ [-Werror=missing-field-initializers]
>   906 |   if (!hasLastSYN) { events.emplace_back(input_event{{}, EV_SYN, 
> SYN_REPORT, 0}); }
>   |   
> ^
> [ 44%] Building CXX object CMakeFiles/projecteur.dir/src/deviceswidget.cc.o
> /usr/bin/c++ -DCXX_COMPILER_ID=GNU -DCXX_COMPILER_VERSION=13.2.0 
> -DHAS_Qt_DBus=1 -DHAS_Qt_X11Extras=1 -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB 
> -I/<>/obj-arm-linux-gnueabihf/projecteur_autogen/include 

Bug#1067622: marked as done (FTBFS: error: missing initializer for member ‘input_event::value’)

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 02:36:36 +
with message-id 
and subject line Bug#1067622: fixed in projecteur 0.10-3
has caused the Debian Bug report #1067622,
regarding FTBFS: error: missing initializer for member ‘input_event::value’
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: projecteur
Version: 0.10-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=projecteur=armel=0.10-2%2Bb2=1711185228=0

/<>/src/deviceinput.cc: In member function ‘void
InputMapper::Impl::emitNativeKeySequence(const NativeKeySequence&)’:
/<>/src/deviceinput.cc:697:64: error: narrowing conversion of
‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
{aka ‘short unsigned int’} [-Werror=narrowing]
  697 |   events.emplace_back(input_event{{}, ie.type, ie.code, ie.value});
  | ~~~^
/<>/src/deviceinput.cc:697:69: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
  697 |   events.emplace_back(input_event{{}, ie.type, ie.code, ie.value});
  | ^
/<>/src/deviceinput.cc: In lambda function:
/<>/src/deviceinput.cc:893:55: error: narrowing conversion of
‘(int32_t)de.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
{aka ‘short unsigned int’} [-Werror=narrowing]
  893 | struct input_event ie = {{}, de.type, de.code, de.value};
  |~~~^
/<>/src/deviceinput.cc:893:60: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
  893 | struct input_event ie = {{}, de.type, de.code, de.value};
  |^
/<>/src/deviceinput.cc: In member function ‘void
InputMapper::addEvents(const KeyEvent&)’:
/<>/src/deviceinput.cc:906:79: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
  906 |   if (!hasLastSYN) { events.emplace_back(input_event{{}, EV_SYN,
SYN_REPORT, 0}); }
  |
^



Note that this package enables -Werror.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: projecteur
Source-Version: 0.10-3
Done: Stuart Prescott 

We believe that the bug you reported is fixed in the latest version of
projecteur, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated projecteur package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 27 Apr 2024 11:43:27 +1000
Source: projecteur
Architecture: source
Version: 0.10-3
Distribution: experimental
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Stuart Prescott 
Closes: 1067622 1069518
Changes:
 projecteur (0.10-3) experimental; urgency=medium
 .
   * Fix FTBFS caused by t64 transition with local patch to change the
 input_event struct at compile time (Closes: #1067622, #1069518)
   * Update Standards-Version to 4.7.0 (no changes required).
Checksums-Sha1:
 65862ffb69d7ec01bc97edece06a371fc0568124 2143 projecteur_0.10-3.dsc
 089ff391137b3ea9ff37f0209ccd15a265f183a6 4188 projecteur_0.10-3.debian.tar.xz
 3488530d3f449432bb246c254f9febf80d8cd6f3 12258 
projecteur_0.10-3_amd64.buildinfo
Checksums-Sha256:
 

Bug#1065976: marked as done (python-levenshtein: FTBFS on arm{el,hf}: Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function ‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 02:36:45 +
with message-id 
and subject line Bug#1065976: fixed in python-levenshtein 0.25.1-3
has caused the Debian Bug report #1065976,
regarding python-levenshtein: FTBFS on arm{el,hf}: 
Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function 
‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’? 
[-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-levenshtein
Version: 0.12.2-3
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=python-levenshtein=armel=0.12.2-3=1709900271=0

arm-linux-gnueabi-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall 
-g -Werror=implicit-function-declaration -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12 
-c Levenshtein/_levenshtein.c -o 
build/temp.linux-armv8l-cpython-312/Levenshtein/_levenshtein.o
Levenshtein/_levenshtein.c: In function ‘levenshtein_common’:
Levenshtein/_levenshtein.c:731:13: warning: pointer targets in assignment from 
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness 
[-Wpointer-sign]
  731 | string1 = PyString_AS_STRING(arg1);
  | ^
Levenshtein/_levenshtein.c:732:13: warning: pointer targets in assignment from 
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness 
[-Wpointer-sign]
  732 | string2 = PyString_AS_STRING(arg2);
  | ^
Levenshtein/_levenshtein.c:746:12: error: implicit declaration of function 
‘PyUnicode_GET_SIZE’; did you mean ‘PyDict_GET_SIZE’? 
[-Werror=implicit-function-declaration]
  746 | len1 = PyUnicode_GET_SIZE(arg1);
  |^~
  |PyDict_GET_SIZE
Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function 
‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’? 
[-Werror=implicit-function-declaration]
  749 | string1 = PyUnicode_AS_UNICODE(arg1);
  |   ^~~~
  |   PyUnicode_AsUCS4
Levenshtein/_levenshtein.c:749:13: warning: assignment to ‘Py_UNICODE *’ {aka 
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
  749 | string1 = PyUnicode_AS_UNICODE(arg1);
  | ^
Levenshtein/_levenshtein.c:750:13: warning: assignment to ‘Py_UNICODE *’ {aka 
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
  750 | string2 = PyUnicode_AS_UNICODE(arg2);
  | ^
Levenshtein/_levenshtein.c: In function ‘hamming_py’:
Levenshtein/_levenshtein.c:816:13: warning: pointer targets in assignment from 
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness 
[-Wpointer-sign]
  816 | string1 = PyString_AS_STRING(arg1);
  | ^
Levenshtein/_levenshtein.c:817:13: warning: pointer targets in assignment from 
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness 
[-Wpointer-sign]
  817 | string2 = PyString_AS_STRING(arg2);
  | ^
Levenshtein/_levenshtein.c:832:13: warning: assignment to ‘Py_UNICODE *’ {aka 
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
  832 | string1 = PyUnicode_AS_UNICODE(arg1);
  | ^
Levenshtein/_levenshtein.c:833:13: warning: assignment to ‘Py_UNICODE *’ {aka 
‘unsigned int *’} from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
  833 | string2 = PyUnicode_AS_UNICODE(arg2);
  | ^
Levenshtein/_levenshtein.c: In function ‘jaro_py’:
Levenshtein/_levenshtein.c:860:13: warning: pointer targets in assignment from 
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness 
[-Wpointer-sign]
  860 | string1 = PyString_AS_STRING(arg1);
  | ^
Levenshtein/_levenshtein.c:861:13: warning: pointer targets in assignment from 
‘char *’ to ‘lev_byte *’ {aka ‘unsigned char *’} differ in signedness 
[-Wpointer-sign]
  861 | string2 = PyString_AS_STRING(arg2);
  | ^
Levenshtein/_levenshtein.c:870:13: warning: assignment 

Bug#1061434: marked as done (python 3.12 extension not working)

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 02:36:45 +
with message-id 
and subject line Bug#1061434: fixed in python-levenshtein 0.25.1-3
has caused the Debian Bug report #1061434,
regarding python 3.12 extension not working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1061434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: python3-levenshtein
Version: 0.12.2-2+b5
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12


the python 3.12 extension is not working:

$ python3.12 -c 'import Levenshtein'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/Levenshtein/__init__.py", line 
1, in 

from Levenshtein import _levenshtein
ImportError: 
/usr/lib/python3/dist-packages/Levenshtein/_levenshtein.cpython-312-x86_64-linux-gnu.so: 
undefined symbol: PyUnicode_AS_UNICODE
--- End Message ---
--- Begin Message ---
Source: python-levenshtein
Source-Version: 0.25.1-3
Done: Stuart Prescott 

We believe that the bug you reported is fixed in the latest version of
python-levenshtein, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated python-levenshtein 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 27 Apr 2024 11:45:48 +1000
Source: python-levenshtein
Architecture: source
Version: 0.25.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team ,
Changed-By: Stuart Prescott 
Closes: 1061434 1065976
Changes:
 python-levenshtein (0.25.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Upload to unstable.
   * Fix compilation with Python 3.12 (Closes: #1061434, #1065976)
Checksums-Sha1:
 e4fc2dfede970145e68d3a9eb060f6ced925a43a 2297 python-levenshtein_0.25.1-3.dsc
 eb0466b2b7d7cd2cc323d49dbcfe53f07be25a9c 3940 
python-levenshtein_0.25.1-3.debian.tar.xz
 26a5c8845fff0dc2d43bb185658831706833ee96 10326 
python-levenshtein_0.25.1-3_amd64.buildinfo
Checksums-Sha256:
 7efb1ca2ea32973030dd607c920c6237884bb5469d4d71570daa0b8c895015cf 2297 
python-levenshtein_0.25.1-3.dsc
 215302622d09516d909a53a7e1627a783b7a955318230c0b40714a20e948de2f 3940 
python-levenshtein_0.25.1-3.debian.tar.xz
 e810f71d1cf9ad8678a0816d6b1d5c02189989b42e02d7984e3f2943f2aa5cc0 10326 
python-levenshtein_0.25.1-3_amd64.buildinfo
Files:
 2f6a87198286d4515f529dc505f5bb9b 2297 python optional 
python-levenshtein_0.25.1-3.dsc
 635cc5a73ce1afa3491159d6214a8675 3940 python optional 
python-levenshtein_0.25.1-3.debian.tar.xz
 7281f80fd73a123655cb4b5039c3aa4a 10326 python optional 
python-levenshtein_0.25.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAmYsWmAACgkQu8F+uxOW
8vfa4w//fyKawiyXV18HhuPT87QS9U3IPgMXPF7Fe+z0QDm85dYsgYZqDNbivNYD
5PocU97Fyg27rNsBzSvXujlCcXFClJrBhrIOyT6cF3C3b2sfrqCUv3CRJ3344mwc
+uB+aDwl9a66jDUT9WjWSswqAG40Abag6YqVaMskrL88tI4hhxAMwXpCef16YO6C
CKGRUQoohjgAQ1GoJ+mrWg8Qec9SzuTkLE7KxmX0aYoa7Lg0OV5y7Yyv64Ruk7WA
+RG1ucvDPS90TQLBa6QxVADly64l4tM5Fl6VH5guSHl1Hp9HOVCRFElPCJViYXU6
03/3TsXWinf/RbzjNWYJ8Ev6hcApuNhc5rEzCvyTKMB+4OvB3Hlt1LLIjYlNkR6m
u8ilm0loDFwoYs+5677Mtkwu+hWunleZ7pR/5X8AEnkWB2++X9KgJjsggbU4K4Sf
f3HK1EHutCDazug3Cl1yMtcxog3AyJQU91U/ErgYwbXU9yLOze1q7lvZoopcD+RJ
LYH6AmpgpOeqnUHNEw1s+6STP3CrEzn0E4rqI8uZ7iuqcRO2uik4bh3bs2D7RZ/k
DPgmPfT94aZrTP8n6dUNRhW9qyMlvZy3Zzo6/kqQAw47mZih0SRkWaQhnAxu2Tlh
2YkjPs84zQ1+La55dN0DN6Oyh+cf4FiQvdmyrvPuklbuvYIHbaA=
=XJXQ
-END PGP SIGNATURE-



pgpeeHSFV2GLl.pgp
Description: PGP signature
--- End Message ---

Bug#1069518: marked as pending in projecteur

[Stuart Prescott]

Control: tag -1 pending

Hello,

Bug #1069518 in projecteur reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/qt-kde-team/extras/projecteur/-/commit/642a0c5b8de2a41e9c1ca4326a750d7410267a3c


Add patch to handle t64 changes to input_event struct

Fixes FTBFS caused by t64 transition with local patch to change the
input_event struct at compile time

Closes: #1067622, #1069518


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069518

Bug#1067622: marked as pending in projecteur

[Stuart Prescott]

Control: tag -1 pending

Hello,

Bug #1067622 in projecteur reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/qt-kde-team/extras/projecteur/-/commit/642a0c5b8de2a41e9c1ca4326a750d7410267a3c


Add patch to handle t64 changes to input_event struct

Fixes FTBFS caused by t64 transition with local patch to change the
input_event struct at compile time

Closes: #1067622, #1069518


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067622

Processed: Bug#1069518 marked as pending in projecteur

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1069518 [src:projecteur] projecteur: FTBFS on armhf: 
deviceinput.cc:697:64: error: narrowing conversion of 
‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’ 
{aka ‘short unsigned int’} [-Werror=narrowing]
Added tag(s) pending.

-- 
1069518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1067622 marked as pending in projecteur

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067622 [src:projecteur] FTBFS: error: missing initializer for member 
‘input_event::value’
Added tag(s) pending.

-- 
1067622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069805: marked as done (scikit-build tries pip install during build)

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 01:49:47 +
with message-id 
and subject line Bug#1069805: fixed in scikit-build 0.17.6-2
has caused the Debian Bug report #1069805,
regarding scikit-build tries pip install during build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-build
Version: 0.17.6-1
Severity: serious
Tags: trixie sid ftbfs

scikit-build accesses network resources during the build:

process = 
stdout = None, stderr = None, retcode = 1

def run(*popenargs,
input=None, capture_output=False, timeout=None, check=False, 
**kwargs):
"""Run command with arguments and return a CompletedProcess instance.

The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those 
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture 
them,
or pass capture_output=True to capture both.

If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return 
code
in the returncode attribute, and output & stderr attributes if those 
streams
were captured.

If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.

There is an optional argument "input", allowing you to
pass bytes or a string to the subprocess's stdin.  If you use this 
argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.

By default, all communication is in bytes, and therefore any "input" 
should
be bytes, and the stdout and stderr will be bytes. If in text mode, any
"input" should be a string, and stdout and stderr will be strings 
decoded
according to locale encoding, or by "encoding" if set. Text mode is
triggered by setting any of text, encoding, errors or 
universal_newlines.

The other arguments are the same as for the Popen constructor.
"""
if input is not None:
if kwargs.get('stdin') is not None:
raise ValueError('stdin and input arguments may not both be 
used.')
kwargs['stdin'] = PIPE

if capture_output:
if kwargs.get('stdout') is not None or kwargs.get('stderr') is not 
None:
raise ValueError('stdout and stderr arguments may not be used '
 'with capture_output.')
kwargs['stdout'] = PIPE
kwargs['stderr'] = PIPE

with Popen(*popenargs, **kwargs) as process:
try:
stdout, stderr = process.communicate(input, timeout=timeout)
except TimeoutExpired as exc:
process.kill()
if _mswindows:
# Windows accumulates the output in a single blocking
# read() call run on child threads, with the timeout
# being done in a join() on those threads.  communicate()
# _after_ kill() is required to collect that and add it
# to the exception.
exc.stdout, exc.stderr = process.communicate()
else:
# POSIX _communicate already populated the output so
# far into the TimeoutExpired exception.
process.wait()
raise
except:  # Including KeyboardInterrupt, communicate handled that.
process.kill()
# We don't call process.wait() as .__exit__ does that for us.
raise
retcode = process.poll()
if check and retcode:
>   raise CalledProcessError(retcode, process.args,
 output=stdout, stderr=stderr)
E   subprocess.CalledProcessError: Command '['/usr/bin/python3.12', 
'-m', 'pip', 'wheel', '--wheel-dir', 
'/tmp/pytest-of-jspricke/pytest-21/wheelhouse0', '/build/package/package']' 
returned non-zero exit status 1.
--- End Message ---
--- Begin Message ---
Source: scikit-build
Source-Version: 0.17.6-2
Done: Emmanuel Arias 

We believe that the bug you reported is fixed in the latest version of
scikit-build, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

[Christoph Anton Mitterer]

On Sat, 2024-04-27 at 03:15 +0200, Guilhem Moulin wrote:
> Yup that'd make sense to me (and I see you did that already), thanks!

:-)

Unfortunately I doubt it will be possibly to do some fully generic
solution.

So best we'll get is probably either an unconditional inclusion or some
simpler copy_* function.


Thanks for your help with the hint on the 2.34 change... I had already
been at my wits end, why pthread didn't show up at ldd ^^

Best wishes,
Chris.

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

[Guilhem Moulin]

On Sat, 27 Apr 2024 at 02:07:21 +0200, Christoph Anton Mitterer wrote:
> So you say it's a glibc thingy, that this doesn't show up anymore?

Yup, that's what I wrote https://bugs.debian.org/1032235#97

| It was intentional, see the article
| 
https://developers.redhat.com/articles/2021/12/17/why-glibc-234-removed-libpthread
 .
| Unfortunately that change broke initramfs-tools' fix for 
https://bugs.debian.org/950254
| which we (src:cryptsetup maintainers) relied on for cryptsetup-initramfs.
| Until last week src:argon2 had never been rebuilt with the newer glibc,
| so it's just unfortunate that we missed that at the time.

On the one hand it was unfortunate to find such a severe RC bug
(unbootable system with the default config) so late in the freeze, on
the other hand it would have been even worse if src:argon2 would have
been uploaded to bookworm-security or -pu after the stable release :-)

> $ ldd /usr/bin/argon2
>   linux-vdso.so.1 (0x7ffcc67d4000)
>   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1a1ee48000)
>   /lib64/ld-linux-x86-64.so.2 (0x7f1a1f058000)
>
> I should use libc for determination?

Don't know if that's the best or most robust solution but that's what
I'd do as workaround at least.

> Would you recommend me to reassign #1069912 to initramfs-tools, asking
> for a more user-friendly solution?

Yup that'd make sense to me (and I see you did that already), thanks!

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1069374: marked as done (python-grpc-tools: FTBFS: aborting due to unexpected upstream changes in grpc_tools/_protoc_compiler.cpp (generated by cython))

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 00:49:36 +
with message-id 
and subject line Bug#1069374: fixed in python-grpc-tools 1.14.1-7
has caused the Debian Bug report #1069374,
regarding python-grpc-tools: FTBFS: aborting due to unexpected upstream changes 
in grpc_tools/_protoc_compiler.cpp (generated by cython)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-grpc-tools
Version: 1.14.1-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean  --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py clean 
> /<>/setup.py:18: DeprecationWarning: pkg_resources is deprecated 
> as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
>   import pkg_resources
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:381: FutureWarning: 
> Cython directive 'language_level' not set, using '3str' for now (Py3). This 
> has changed from earlier releases! File: 
> /<>/grpc_tools/_protoc_compiler.pyx
>   tree = Parsing.p_module(s, pxd, full_module_name)
> Compiling grpc_tools/_protoc_compiler.pyx because it changed.
> [1/1] Cythonizing grpc_tools/_protoc_compiler.pyx
> running clean
> removing '/<>/.pybuild/cpython3_3.12_grpcio-tools/build' (and 
> everything under it)
> 'build/bdist.linux-aarch64' does not exist -- can't clean it
> 'build/scripts-3.12' does not exist -- can't clean it
> I: pybuild base:311: python3.11 setup.py clean 
> /<>/setup.py:18: DeprecationWarning: pkg_resources is deprecated 
> as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
>   import pkg_resources
> running clean
> removing '/<>/.pybuild/cpython3_3.11_grpcio-tools/build' (and 
> everything under it)
> 'build/bdist.linux-aarch64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-grpc-tools using existing 
> ./python-grpc-tools_1.14.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of directory grpcio_tools.egg-info
> dpkg-source: warning: ignoring deletion of file 
> grpcio_tools.egg-info/SOURCES.txt, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file 
> grpcio_tools.egg-info/PKG-INFO, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file 
> grpcio_tools.egg-info/top_level.txt, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file 
> grpcio_tools.egg-info/requires.txt, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file 
> grpcio_tools.egg-info/dependency_links.txt, use --include-removal to override
> dpkg-source: info: local changes detected, the modified files are:
>  python-grpc-tools-1.14.1/grpc_tools/_protoc_compiler.cpp
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/python-grpc-tools_1.14.1-6.diff.silkQD
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2024-04-20T03:15:38Z


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/python-grpc-tools_1.14.1-6_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a 

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

[Christoph Anton Mitterer]

On Sat, 2024-04-27 at 01:48 +0200, Guilhem Moulin wrote:
> built using glibc ≥2.34.  AFAICT the “if the ldd output includes
> libpthread then run copy_libgcc()” logic from initramfs-tools is
> mostly moot
> now

Ah, I just realised glibc "merged" libpthread ^^

Therefore...

> but despite what I promised elbrus in
> https://bugs.debian.org/1032235#87 it
> looks like I didn't file a bug.

... I helped you fulfilling your promise and re-assigned my #1069912,
making it the bug that asks for some more generic solution :-)


Thanks,
Chris.

Bug#1064089: marked as done (gutenprint: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 00:19:32 +
with message-id 
and subject line Bug#1064089: fixed in gutenprint 5.3.4.20220624T01008808d602-2
has caused the Debian Bug report #1064089,
regarding gutenprint: NMU diff for 64-bit time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gutenprint
Version: 5.3.4.20220624T01008808d602-1
Severity: important
Tags: patch
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
gutenprint 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 gutenprint.

Please find the patch for this NMU attached.

Unfortunately, due to unrelated bugs (bug #1064088), your package fails to
build in unstable and therefore we will not be uploading an NMU for this.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gutenprint
Source-Version: 5.3.4.20220624T01008808d602-2
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
gutenprint, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated gutenprint package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Apr 2024 23:10:00 +0200
Source: gutenprint
Architecture: source
Version: 5.3.4.20220624T01008808d602-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Group 
Changed-By: Thorsten Alteholz 
Closes: 1064088 1064089
Changes:
 gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium
 .
   * do not build this package on 32bit architectures anymore
 Closes: #1064088
 Closes: #1064089
 There was no patch attached to #1064089, so I can not reproduce the
 problems mentioned in #1064088. I am fed up with this poorly done
 transition, so I won't spend more time with this. Sorry 32bit people.
Checksums-Sha1:
 263f3b632560f12513538b513e696e0db53eb8da 3210 
gutenprint_5.3.4.20220624T01008808d602-2.dsc
 f070be098b05810df047571faa521c7cec690b54 95036 
gutenprint_5.3.4.20220624T01008808d602-2.debian.tar.xz
 a8e143047c6f88a82d89d031ccff7acd64497c0a 20798 
gutenprint_5.3.4.20220624T01008808d602-2_amd64.buildinfo
Checksums-Sha256:
 6661d2a2c7a9c6615c188217c93ddb7db4635d24474cd61e2f7ac144e8fd7174 3210 
gutenprint_5.3.4.20220624T01008808d602-2.dsc
 858c4091f2d9418f9e35cb37b0d2bfe181a819ddd4a08c00eedfae8a1816bf68 95036 
gutenprint_5.3.4.20220624T01008808d602-2.debian.tar.xz
 4e06c6331a979761b6d018a5cd9862099f92da2c2146ec6fb49de6501b07c7ca 20798 
gutenprint_5.3.4.20220624T01008808d602-2_amd64.buildinfo
Files:
 ea7ac1f5ff28e39aeaeb7108783a112a 3210 graphics optional 
gutenprint_5.3.4.20220624T01008808d602-2.dsc
 51151ed4e4d37c3ee58d2a49eb1bf9ff 95036 graphics optional 

Bug#1064088: marked as done (gutenprint: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 00:19:32 +
with message-id 
and subject line Bug#1064088: fixed in gutenprint 5.3.4.20220624T01008808d602-2
has caused the Debian Bug report #1064088,
regarding gutenprint: FTBFS in unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gutenprint
Version: 5.3.4.20220624T01008808d602-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble

Dear maintainers,

gutenprint now fails to build from source in unstable.  Initially, it fails
to build because debian/libgutenprintui2-2.symbols expects symbols to be
present that are not part of this library's API but only a result of using
yacc internally.  Marking these symbols optional gets past this issue:

 (optional)yy_create_buffer@Base 5.3.0~pre1
 (optional)yy_delete_buffer@Base 5.3.0~pre1
 (optional)yy_flex_debug@Base 5.3.0~pre1
 (optional)yy_flush_buffer@Base 5.3.0~pre1
 (optional)yy_scan_buffer@Base 5.3.0~pre1
 (optional)yy_scan_bytes@Base 5.3.0~pre1
 (optional)yy_scan_string@Base 5.3.0~pre1
 (optional)yy_switch_to_buffer@Base 5.3.0~pre1
 (optional)yyalloc@Base 5.3.0~pre1
 (optional)yychar@Base 5.3.0~pre1
 (optional)yydebug@Base 5.3.1
[...]

But then the package fails because dh_missing complains about files
installed into debian/tmp not being included in any package:

[...]
make[1]: Leaving directory '/tmp/time-t/gutenprint-5.3.4.20220624T01008808d602'
   dh_missing
dh_missing: warning: usr/share/gutenprint/doc/reference-html/a2128.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/a2128.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/c1723.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/c1723.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/c193.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/c193.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/c1974.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/c1974.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/c199.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/c199.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/c38.html exists in 
debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/c38.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/c463.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/c463.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/c47.html exists in 
debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/c47.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/f14.html exists in 
debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/f14.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/index.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/index.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/x1675.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/x1675.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/x1740.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/x1740.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/x2159.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/x2159.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/x270.html exists 
in debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/x270.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/x66.html exists in 
debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/x66.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/x78.html exists in 
debian/tmp but is not installed to anywhere (related file: 
"doc/developer/reference-html/x78.html")
dh_missing: warning: usr/share/gutenprint/doc/reference-html/x961.html exists 
in 

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

[Christoph Anton Mitterer]

Hey Guilhem

On Sat, 2024-04-27 at 01:48 +0200, Guilhem Moulin wrote:
> Even it weren't, libpthread wouldn't show up since src:argon2 from
> bookworm
> and later is built using glibc ≥2.34.

When argon2 builds, it uses -pthread ... not really sure what that does
exactly, the manpage merely says it links against pthread, but
statically? Dynamically?

Anyway, when building it manually and even with -lpthread, it doesn't
show up - just as you say.

Tried now for an hour or so to make it show up (eventually gave up and
filed #1069912).

So you say it's a glibc thingy, that this doesn't show up anymore?


>   AFAICT the “if the ldd output includes
> libpthread then run copy_libgcc()” logic from initramfs-tools is
> mostly moot
> now, see https://bugs.debian.org/1032235#97 .

Shouldn't initramfstools then not simply generally include libgcc?



> We used the following workaround to manually call copy_libgcc()
> 
>    
> https://salsa.debian.org/cryptsetup-team/cryptsetup/-/commit/4cade1eae57abd93e0d6491eebce5f5f163ef186#a630d04e2df57150e6a092fc23f955c6ea0ce412
>    
> https://salsa.debian.org/cryptsetup-team/cryptsetup/-/commit/369cb651abad11a3844fa38ea86ece40f4f40078

As a workaround I've used now:
copy_libgcc /lib/x86_64-linux-gnu

with the libpath hardcoded... but I have no idea how I should get that
path properly.
As far as I can see from your commit, you simply used the path that
libargon2 was using?

But I don't have that since argon2 doesn't link against it ;-)
Any idea what would be the best solution in my case?


> for Bookworm, but removed it with 2:2.7.2-1 since src:cryptsetup no
> longer uses libargon.  There is no stability guaranty for transitive
> dependencies so I'd indeed argue the regression is not
> src:cryptsetup's
> fault :-)  Adapting the above workarounds to your custom hookfile
> should
> solve the issue, though.

Hmm yes, but I'm not sure if that would be a more proper solution than
mine (with the hardcoded path), cause:

In principle, my argon2 binary tool, might be from another arch as the
installed libargon2 (if it's installed at all, which isn't necessarily
the case).
So not sure, but maybe:

$ ldd /usr/bin/argon2
linux-vdso.so.1 (0x7ffcc67d4000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1a1ee48000)
/lib64/ld-linux-x86-64.so.2 (0x7f1a1f058000)

I should use libc for determination?

> 



> > Did anyone of your report this issue anywhere else?
> 
> Some years ago I asked the initramfs-tools maintainers to
> inconditionally copy
> libgcc_s to the initramfs image, but IIRC Ben argued it was too
> seldom used to
> justify the cost in size and impemented the libpthread detection
> logic +
> copy_libgcc() instead.
> 
> I don't know if the detection logic can be improved/fixed in
> initramfs-tools,
> but despite what I promised elbrus in
> https://bugs.debian.org/1032235#87 it
> looks like I didn't file a bug.

So... I assume the change in glibc is proper then... and a fix (if at
all) would rather need to go to initramfs-tools?
Would you recommend me to reassign #1069912 to initramfs-tools, asking
for a more user-friendly solution?


Thanks,
Chris.

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

[Guilhem Moulin]

Hi,

On Sat, 27 Apr 2024 at 00:33:51 +0200, Christoph Anton Mitterer wrote:
> Now the problem is that argon2 is statically linked, so there's no
> libpthread showing up in its ldd, and thus copy_exec doesn't realise it
> needs to invoke copy_libgcc.

Even it weren't, libpthread wouldn't show up since src:argon2 from bookworm
and later is built using glibc ≥2.34.  AFAICT the “if the ldd output includes
libpthread then run copy_libgcc()” logic from initramfs-tools is mostly moot
now, see https://bugs.debian.org/1032235#97 .

We used the following workaround to manually call copy_libgcc()


https://salsa.debian.org/cryptsetup-team/cryptsetup/-/commit/4cade1eae57abd93e0d6491eebce5f5f163ef186#a630d04e2df57150e6a092fc23f955c6ea0ce412

https://salsa.debian.org/cryptsetup-team/cryptsetup/-/commit/369cb651abad11a3844fa38ea86ece40f4f40078

for Bookworm, but removed it with 2:2.7.2-1 since src:cryptsetup no
longer uses libargon.  There is no stability guaranty for transitive
dependencies so I'd indeed argue the regression is not src:cryptsetup's
fault :-)  Adapting the above workarounds to your custom hookfile should
solve the issue, though.

> Did anyone of your report this issue anywhere else?

Some years ago I asked the initramfs-tools maintainers to inconditionally copy
libgcc_s to the initramfs image, but IIRC Ben argued it was too seldom used to
justify the cost in size and impemented the libpthread detection logic +
copy_libgcc() instead.

I don't know if the detection logic can be improved/fixed in initramfs-tools,
but despite what I promised elbrus in https://bugs.debian.org/1032235#87 it
looks like I didn't file a bug.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1066348: marked as done (hplip: FTBFS: scan/sane/hpaio.c:364:12: error: implicit declaration of function ‘orblite_init’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 23:35:05 +
with message-id 
and subject line Bug#1066348: fixed in hplip 3.22.10+dfsg0-5
has caused the Debian Bug report #1066348,
regarding hplip: FTBFS: scan/sane/hpaio.c:364:12: error: implicit declaration 
of function ‘orblite_init’ [-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hplip
Version: 3.22.10+dfsg0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"HP\ 
> Linux\ Imaging\ and\ Printing\" -DPACKAGE_TARNAME=\"hplip\" 
> -DPACKAGE_VERSION=\"3.22.10\" -DPACKAGE_STRING=\"HP\ Linux\ Imaging\ and\ 
> Printing\ 3.22.10\" -DPACKAGE_BUGREPORT=\"3.22.10\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"hplip\" -DVERSION=\"3.22.10\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBDL=1 -DHAVE_PTHREAD_H=1 
> -DHAVE_JPEGLIB_H=1 -DHAVE_UINT32_T=1 -DHAVE_LIBHPIP=1 -DHAVE_LIBHPIP=1 
> -DDISABLE_IMAGEPROCESSOR=1 -DHAVE_LIBCRYPTO=1 -DHAVE_LIBNETSNMP=1 
> -DHAVE_NET_SNMP_NET_SNMP_CONFIG_H=1 -DHAVE_LIBAVAHI=1 
> -DHAVE_LIBAVAHI_CLIENT=1 -DHAVE_LIBAVAHI_COMMON=1 
> -DHAVE_AVAHI_CLIENT_CLIENT_H=1 -DHAVE_AVAHI_COMMON_MALLOC_H=1 
> -DHAVE_CUPS_CUPS_H=1 -DHAVE_CUPS_PPD_H=1 -DHAVE_LIBUSB_1_0_LIBUSB_H=1 
> -DHAVE_PYTHON_H=1 -DHAVE_DBUS=1 -I. -Iip -Iio/hpmud -Iscan/sane -Iprnt/hpijs 
> -Icommon/ -Iprotocol  -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include  -Iprotocol -Iprotocol/discovery 
> -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -I/usr/include/python3.11 -I/usr/include/python3.11 -DCONFDIR=\"/etc/hp\" -c 
> -o libsane_hpaio_la-pml.lo `test -f 'scan/sane/pml.c' || echo 
> './'`scan/sane/pml.c
> In file included from scan/sane/mfpdtf.c:28:
> scan/sane/common.h:191:1: warning: ‘visibility’ attribute ignored on 
> non-class types [-Wattributes]
>   191 | char* __attribute__ ((visibility ("hidden"))) itoa(int value, char* 
> str, int radix);
>   | ^~~~
> scan/sane/mfpdtf.c: In function ‘MfpdtfReadInnerBlock’:
> scan/sane/mfpdtf.c:476:13: warning: ignoring return value of ‘write’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   476 | write( mfpdtf->fdLog, buffer, r );  /* log raw rgb data, 
> use imagemagick to display */
>   | ^
> In file included from scan/sane/hpaio.h:32,
>  from scan/sane/hpaio.c:48:
> scan/sane/common.h:191:1: warning: ‘visibility’ attribute ignored on 
> non-class types [-Wattributes]
>   191 | char* __attribute__ ((visibility ("hidden"))) itoa(int value, char* 
> str, int radix);
>   | ^~~~
> In file included from scan/sane/hpaio.c:57:
> scan/sane/sanei_debug.h:167: warning: "DBG" redefined
>   167 | # define DBGDBG_LOCAL
>   | 
> In file included from scan/sane/hpaio.c:41:
> protocol/discovery/avahiDiscovery.h:79: note: this is the location of the 
> previous definition
>79 |#define DBG(args...)
>   | 
> scan/sane/hpaio.c: In function ‘GetCupsPrinters’:
> scan/sane/hpaio.c:202:4: warning: ‘httpConnectEncrypt’ is deprecated: Use 
> httpConnect2 instead. [-Wdeprecated-declarations]
>   202 |if ((http = httpConnectEncrypt(cupsServer(), ippPort(), 
> cupsEncryption())) == NULL)
>   |^~
> In file included from /usr/include/cups/ipp.h:18,
>  from /usr/include/cups/cups.h:28,
>  from scan/sane/hpaio.c:37:
> /usr/include/cups/http.h:477:26: note: declared here
>   477 | extern http_t   *httpConnectEncrypt(const char *host, int 
> port, http_encryption_t encryption) _CUPS_DEPRECATED_1_7_MSG("Use 
> httpConnect2 instead.");
>   |   

Processed: tagging 1064282, reassign 1069433 to src:openmpi, tagging 1069433, tagging 1069840 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1064282 + experimental
Bug #1064282 [src:poppler] poppler: NMU diff for 64-bit time_t transition
Added tag(s) experimental.
> reassign 1069433 src:openmpi 4.1.6-3
Bug #1069433 [openmpi] gtg-trace: FTBFS on armhf: tests fail
Bug reassigned from package 'openmpi' to 'src:openmpi'.
No longer marked as found in versions 4.1.6-5.
Ignoring request to alter fixed versions of bug #1069433 to the same values 
previously set
Bug #1069433 [src:openmpi] gtg-trace: FTBFS on armhf: tests fail
Marked as found in versions openmpi/4.1.6-3.
> tags 1069433 - sid trixie
Bug #1069433 [src:openmpi] gtg-trace: FTBFS on armhf: tests fail
Removed tag(s) sid and trixie.
> tags 1069840 + sid trixie
Bug #1069840 [src:maven-dependency-analyzer] maven-dependency-analyzer: FTBFS: 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile 
(default-testCompile) on project maven-dependency-analyzer: Compilation failure
Added tag(s) trixie and sid.
> retitle 1069374 python-grpc-tools: FTBFS: aborting due to unexpected upstream 
> changes in grpc_tools/_protoc_compiler.cpp (generated by cython)
Bug #1069374 [src:python-grpc-tools] python-grpc-tools: FTBFS on arm64: 
aborting due to unexpected upstream changes in grpc_tools/_protoc_compiler.cpp
Changed Bug title to 'python-grpc-tools: FTBFS: aborting due to unexpected 
upstream changes in grpc_tools/_protoc_compiler.cpp (generated by cython)' from 
'python-grpc-tools: FTBFS on arm64: aborting due to unexpected upstream changes 
in grpc_tools/_protoc_compiler.cpp'.
> retitle 1069370 shasta: FTBFS: dpkg-shlibdeps: error: cannot find library 
> shasta.cpython-311-aarch64-linux-gnu.so needed by debian/shasta/usr/bin/shasta
Bug #1069370 [src:shasta] shasta: FTBFS: dpkg-shlibdeps: error: cannot continue 
due to the error above
Changed Bug title to 'shasta: FTBFS: dpkg-shlibdeps: error: cannot find library 
shasta.cpython-311-aarch64-linux-gnu.so needed by debian/shasta/usr/bin/shasta' 
from 'shasta: FTBFS: dpkg-shlibdeps: error: cannot continue due to the error 
above'.
> found 1061025 1.3.0-1
Bug #1061025 [src:libcommons-logging-java] httpcomponents-client: FTBFS: make: 
*** [debian/rules:4: build] Error 25
Marked as found in versions libcommons-logging-java/1.3.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1061025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061025
1064282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064282
1069370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069370
1069374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069374
1069433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069433
1069840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068849: [pkg-cryptsetup-devel] Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

[Christoph Anton Mitterer]

Hey guys.

I kinda ran into a similar issue.

I use my own OpenPGP keyscript which is highly improved upon that
("decrypt_gnupg") shipped by the package.

One thing that I do is offer optionally feeding the entered passphrase
trough argon2 (the standalone tool from the package of the same name)
which I copy via copy_exec.

Now the problem is that argon2 is statically linked, so there's no
libpthread showing up in its ldd, and thus copy_exec doesn't realise it
needs to invoke copy_libgcc.


Did anyone of your report this issue anywhere else? I mean it's
obviously not crypsetup.
But I cannot really blame argon2 either, nor can I really blame update-
initramfs.


Cheers,
Chris.

Bug#1069703: marked as done (dynamips: requires rebuild for t64 transition)

[Debian Bug Tracking System]

Your message dated Sat, 27 Apr 2024 00:03:29 +0200
with message-id 
and subject line Re: dynamips: requires rebuild for t64 transition
has caused the Debian Bug report #1069703,
regarding dynamips: requires rebuild for t64 transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dynamips
Version: 0.2.14-1
Severity: serious
Tags: sid trixie
X-Debbugs-Cc: sramac...@debian.org

dynamips is in non-free without auto build support. Please rebuild the
package against the t64 packages in unstable.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
On Tue, 23 Apr 2024 08:29:23 +0200 Sebastian Ramacher 
 wrote:

dynamips is in non-free without auto build support. Please rebuild the
package against the t64 packages in unstable.


Uploaded manually built binNMUs for amd64 and i386.
In case there are more packages in non-free or contrib in need of a 
manual binNMU, please let me know.



Andreas--- End Message ---

Bug#1069545: [Pkg-erlang-devel] Bug#1069545: erlang: FTBFS on armel: make[4]: *** [/<>/make/arm-unknown-linux-gnueabi/otp.mk:325: ../pdf/wx-2.2.2.1.pdf] Error 1

[Sergei Golovan]

notfound 1069545 1:25.3.2.11+dfsg-1
thanks

Hi Lucas,

Java throwing an out-of-memory exception on armel doesn't count as a
bug, I reckon.

On the other hand, my previous thought about sufficient memory size on
builds is irrelevant because builds build only architecture dependent
packages, and erlang-doc is architecture independent.

On Tue, Apr 23, 2024 at 10:02 AM Sergei Golovan  wrote:
>
> Version: 1:25.3.2.11+dfsg-1
>
> Hi Lukas,
>
> On Sat, Apr 20, 2024 at 4:27 PM Lucas Nussbaum  wrote:
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on armel.
>
> > > [INFO] FOUserAgent - Rendered page #871.
> > > Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
>
> It's an intermittent out-of-memory error. It never occurs on buildds
> (I guess they just have more memory available then in the setup you're
> using for the archive rebuild). Therefore, I'm closing this bugreport.
>
> Cheers!
> --
> Sergei Golovan



-- 
Sergei Golovan

Processed: Re: [Pkg-erlang-devel] Bug#1069545: erlang: FTBFS on armel: make[4]: *** [/<>/make/arm-unknown-linux-gnueabi/otp.mk:325: ../pdf/wx-2.2.2.1.pdf] Error 1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 1069545 1:25.3.2.11+dfsg-1
Bug #1069545 {Done: Sergei Golovan } [src:erlang] erlang: 
FTBFS on armel: make[4]: *** 
[/<>/make/arm-unknown-linux-gnueabi/otp.mk:325: 
../pdf/wx-2.2.2.1.pdf] Error 1
No longer marked as found in versions erlang/1:25.3.2.11+dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1069374 marked as pending in python-grpc-tools

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1069374 [src:python-grpc-tools] python-grpc-tools: FTBFS on arm64: 
aborting due to unexpected upstream changes in grpc_tools/_protoc_compiler.cpp
Added tag(s) pending.

-- 
1069374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069374: marked as pending in python-grpc-tools

[Andreas Beckmann]

Control: tag -1 pending

Hello,

Bug #1069374 in python-grpc-tools reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-grpc-tools/-/commit/46f7b74bd24ace348a6a4fd27a681b907f7f91af


clean grpc_tools/_protoc_compiler.cpp, generated by cython

Closes: #1069374


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069374

Bug#1069904: Autopkgtests failed

[Andrey Rakhmatullin]

Package: python3-gnupg
Version: 0.5.2-1
Severity: serious

https://ci.debian.net/packages/p/python-gnupg/unstable/amd64/45884087/

277s + python3.11 test_gnupg.py
493s ...F...
493s ==
493s FAIL: test_search_keys (__main__.GPGTestCase.test_search_keys)
493s Test that searching for keys works
493s --
493s Traceback (most recent call last):
493s   File "/tmp/autopkgtest-
lxc.s9943af9/downtmp/build.Ev1/src/test_gnupg.py", line 1252, in
test_search_keys
493s self.assertEqual(0, r.returncode, 'Non-zero return code')
493s AssertionError: 0 != 2 : Non-zero return code


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 python3-gnupg depends on:
ii  gnupg2.2.40-3
ii  python3  3.11.8-1

python3-gnupg recommends no packages.

python3-gnupg suggests no packages.

Bug#1067616: marked as done (FTBFS: error: ‘struct input_event’ has no member named ‘time’)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 18:49:41 +
with message-id 
and subject line Bug#1067616: fixed in clanlib 1.0~svn3827-11.2
has caused the Debian Bug report #1067616,
regarding FTBFS: error: ‘struct input_event’ has no member named ‘time’
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clanlib
Version: 1.0~svn3827-11.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=clanlib=armel=1.0%7Esvn3827-11.1=1711185366=0

GLX/input_device_linuxevent.cpp: In member function ‘virtual void
CL_InputDevice_LinuxEvent::keep_alive()’:
GLX/input_device_linuxevent.cpp:269:72: error: ‘struct input_event’ has no
member named ‘time’
  269 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].code ? "Config Sync" : "Report
Sync" );
  |
^~~~
GLX/input_device_linuxevent.cpp:269:91: error: ‘struct input_event’ has no
member named ‘time’
  269 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].code ? "Config Sync" : "Report
Sync" );
  |
^~~~
GLX/input_device_linuxevent.cpp:274:72: error: ‘struct input_event’ has no
member named ‘time’
  274 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
  |
^~~~
GLX/input_device_linuxevent.cpp:274:91: error: ‘struct input_event’ has no
member named ‘time’
  274 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
  |
^~~~
GLX/input_device_linuxevent.cpp:283:72: error: ‘struct input_event’ has no
member named ‘time’
  283 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
  |
^~~~
GLX/input_device_linuxevent.cpp:283:91: error: ‘struct input_event’ has no
member named ‘time’
  283 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: clanlib
Source-Version: 1.0~svn3827-11.2
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
clanlib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated clanlib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Apr 2024 21:29:44 +
Source: clanlib
Architecture: source
Version: 1.0~svn3827-11.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Steve Langasek 
Closes: 1067616 1069385
Changes:
 clanlib (1.0~svn3827-11.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix dep from -dev package to point to current runtime lib name.
 Closes: #1069385.
   * debian/patches/64-bit-time-t-compat.patch: compatibility with 64-bit
 time_t.  Closes: #1067616.
Checksums-Sha1:
 73c4490a8aa6952bfe1e8db507a338fc53dcdb93 2395 clanlib_1.0~svn3827-11.2.dsc
 fd7ba9b0c52627f8932553e6ec12d02b6f89463f 130488 
clanlib_1.0~svn3827-11.2.debian.tar.xz
 393aed6f50eb343579e4bf19388955e1e6fd9221 5268 
clanlib_1.0~svn3827-11.2_source.buildinfo
Checksums-Sha256:
 314060999cb0ad3a0bd6a50ef8f73c1a4c1211cdee2cd05da596b88b03109f6e 2395 
clanlib_1.0~svn3827-11.2.dsc
 feebb45876f330995ef1e632e666346af0a0b1cda00338cff2b1144728308cf1 130488 
clanlib_1.0~svn3827-11.2.debian.tar.xz
 430b8e03ca2ebc350bc21e66e993bc7fd7c773de62322f3cfaed23a1160b3130 5268 
clanlib_1.0~svn3827-11.2_source.buildinfo
Files:
 5ace6f4667a97d0162b072531d99fc91 2395 libs optional 
clanlib_1.0~svn3827-11.2.dsc
 d692cde148c56a9ba119144ffe72714d 130488 libs optional 
clanlib_1.0~svn3827-11.2.debian.tar.xz
 eab5787ab0a4aef8f744caa56ceeac4f 

Bug#1069385: marked as done (FTBFS: dh_installdocs: error: Requested unknown package libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ...)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 18:49:41 +
with message-id 
and subject line Bug#1069385: fixed in clanlib 1.0~svn3827-11.2
has caused the Debian Bug report #1069385,
regarding FTBFS: dh_installdocs: error: Requested unknown package 
libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ...
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clanlib
Version: 1.0~svn3827-11.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: Nothing to be done for 'install-exec-am'.
> make[3]: Nothing to be done for 'install-data-am'.
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_install
>debian/rules override_dh_installdocs-arch
> make[1]: Entering directory '/<>'
> dh_installdocs --link-doc=libclanapp-1.0v5
> dh_installdocs: error: Requested unknown package libclanapp-1.0v5 via 
> --link-doc, expected one of: libclanapp-1.0t64 libclanlib-dev clanlib-doc
> make[1]: *** [debian/rules:49: override_dh_installdocs-arch] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/clanlib_1.0~svn3827-11.1_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: clanlib
Source-Version: 1.0~svn3827-11.2
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
clanlib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated clanlib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Apr 2024 21:29:44 +
Source: clanlib
Architecture: source
Version: 1.0~svn3827-11.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Steve Langasek 
Closes: 1067616 1069385
Changes:
 clanlib (1.0~svn3827-11.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix dep from -dev package to point to current runtime lib name.
 Closes: #1069385.
   * debian/patches/64-bit-time-t-compat.patch: compatibility with 64-bit
 time_t.  Closes: #1067616.
Checksums-Sha1:
 73c4490a8aa6952bfe1e8db507a338fc53dcdb93 2395 clanlib_1.0~svn3827-11.2.dsc
 fd7ba9b0c52627f8932553e6ec12d02b6f89463f 130488 
clanlib_1.0~svn3827-11.2.debian.tar.xz
 393aed6f50eb343579e4bf19388955e1e6fd9221 5268 
clanlib_1.0~svn3827-11.2_source.buildinfo
Checksums-Sha256:
 314060999cb0ad3a0bd6a50ef8f73c1a4c1211cdee2cd05da596b88b03109f6e 2395 
clanlib_1.0~svn3827-11.2.dsc
 feebb45876f330995ef1e632e666346af0a0b1cda00338cff2b1144728308cf1 130488 
clanlib_1.0~svn3827-11.2.debian.tar.xz
 430b8e03ca2ebc350bc21e66e993bc7fd7c773de62322f3cfaed23a1160b3130 5268 
clanlib_1.0~svn3827-11.2_source.buildinfo
Files:
 5ace6f4667a97d0162b072531d99fc91 2395 libs optional 
clanlib_1.0~svn3827-11.2.dsc
 d692cde148c56a9ba119144ffe72714d 130488 libs optional 
clanlib_1.0~svn3827-11.2.debian.tar.xz
 eab5787ab0a4aef8f744caa56ceeac4f 5268 libs optional 
clanlib_1.0~svn3827-11.2_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: clanlib FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags 1069385 patch
Bug #1069385 [src:clanlib] FTBFS: dh_installdocs: error: Requested unknown 
package libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ...
Ignoring request to alter tags of bug #1069385 to the same tags previously set

-- 
1069385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1067616: clanlib FTBFS

[Steve Langasek]

Control: tags 1069385 patch

Please find attached a comprehensive NMU patch for both the time_t
conversion and the FTBFS errors.

I am uploading this now as a 0-day NMU.

-- 
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 clanlib-1.0~svn3827/debian/changelog 
clanlib-1.0~svn3827/debian/changelog
--- clanlib-1.0~svn3827/debian/changelog2023-09-15 13:49:45.0 
-0700
+++ clanlib-1.0~svn3827/debian/changelog2024-04-25 14:29:44.0 
-0700
@@ -1,3 +1,20 @@
+clanlib (1.0~svn3827-11.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix dep from -dev package to point to current runtime lib name.
+Closes: #1069385.
+  * debian/patches/64-bit-time-t-compat.patch: compatibility with 64-bit
+time_t.  Closes: #1067616.
+
+ -- Steve Langasek   Thu, 25 Apr 2024 21:29:44 +
+
+clanlib (1.0~svn3827-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.  Closes: #1062074
+
+ -- Steve Langasek   Wed, 28 Feb 2024 15:52:37 +
+
 clanlib (1.0~svn3827-11) unstable; urgency=medium
 
   * Team upload.
diff -Nru clanlib-1.0~svn3827/debian/control clanlib-1.0~svn3827/debian/control
--- clanlib-1.0~svn3827/debian/control  2023-09-15 13:49:45.0 -0700
+++ clanlib-1.0~svn3827/debian/control  2024-04-25 14:29:44.0 -0700
@@ -4,7 +4,7 @@
  Barry deFreese 
 Section: libs
 Priority: optional
-Build-Depends:
+Build-Depends: dpkg-dev (>= 1.22.5),
  bzip2,
  debhelper-compat (= 12),
  libasound2-dev [linux-any],
@@ -28,14 +28,17 @@
 Vcs-Git: https://salsa.debian.org/games-team/clanlib.git
 Homepage: https://github.com/sphair/ClanLib
 
-Package: libclanapp-1.0v5
+Package: libclanapp-1.0t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libclanapp-1.0v5
+Breaks: libclanapp-1.0v5 (<< ${source:Version})
 Architecture: any
 Depends:
  ${misc:Depends},
  ${shlibs:Depends}
 Conflicts:
  libclanapp-1.0
-Replaces:
+Replaces:libclanapp-1.0v5, 
  libclanapp-1.0
 Multi-Arch: same
 Description: ClanLib game SDK runtime
@@ -60,7 +63,7 @@
 Architecture: any
 Section: libdevel
 Depends:
- libclanapp-1.0v5 (= ${binary:Version}),
+ libclanapp-1.0t64 (= ${binary:Version}),
  ${misc:Depends}
 Recommends:
  libfreetype-dev,
diff -Nru clanlib-1.0~svn3827/debian/libclanapp-1.0t64.install 
clanlib-1.0~svn3827/debian/libclanapp-1.0t64.install
--- clanlib-1.0~svn3827/debian/libclanapp-1.0t64.install1969-12-31 
16:00:00.0 -0800
+++ clanlib-1.0~svn3827/debian/libclanapp-1.0t64.install2023-09-15 
13:49:45.0 -0700
@@ -0,0 +1,11 @@
+usr/lib/*/libclanApp*.so.*
+usr/lib/*/libclanCore*.so.*
+usr/lib/*/libclanDisplay*.so.*
+usr/lib/*/libclanGL*.so.*
+usr/lib/*/libclanGUI*.so.*
+usr/lib/*/libclanGUIStyleSilver*.so.*
+usr/lib/*/libclanMikMod*.so.*
+usr/lib/*/libclanNetwork*.so.*
+usr/lib/*/libclanSignals*.so.*
+usr/lib/*/libclanSound*.so.*
+usr/lib/*/libclanVorbis*.so.*
diff -Nru clanlib-1.0~svn3827/debian/libclanapp-1.0t64.lintian-overrides 
clanlib-1.0~svn3827/debian/libclanapp-1.0t64.lintian-overrides
--- clanlib-1.0~svn3827/debian/libclanapp-1.0t64.lintian-overrides  
1969-12-31 16:00:00.0 -0800
+++ clanlib-1.0~svn3827/debian/libclanapp-1.0t64.lintian-overrides  
2024-02-28 07:52:20.0 -0800
@@ -0,0 +1 @@
+libclanapp-1.0t64: package-name-doesnt-match-sonames libclanapp-1.0v5
diff -Nru clanlib-1.0~svn3827/debian/libclanapp-1.0v5.install 
clanlib-1.0~svn3827/debian/libclanapp-1.0v5.install
--- clanlib-1.0~svn3827/debian/libclanapp-1.0v5.install 2023-09-15 
13:49:45.0 -0700
+++ clanlib-1.0~svn3827/debian/libclanapp-1.0v5.install 1969-12-31 
16:00:00.0 -0800
@@ -1,11 +0,0 @@
-usr/lib/*/libclanApp*.so.*
-usr/lib/*/libclanCore*.so.*
-usr/lib/*/libclanDisplay*.so.*
-usr/lib/*/libclanGL*.so.*
-usr/lib/*/libclanGUI*.so.*
-usr/lib/*/libclanGUIStyleSilver*.so.*
-usr/lib/*/libclanMikMod*.so.*
-usr/lib/*/libclanNetwork*.so.*
-usr/lib/*/libclanSignals*.so.*
-usr/lib/*/libclanSound*.so.*
-usr/lib/*/libclanVorbis*.so.*
diff -Nru clanlib-1.0~svn3827/debian/patches/64-bit-time-t-compat.patch 
clanlib-1.0~svn3827/debian/patches/64-bit-time-t-compat.patch
--- clanlib-1.0~svn3827/debian/patches/64-bit-time-t-compat.patch   
1969-12-31 16:00:00.0 -0800
+++ clanlib-1.0~svn3827/debian/patches/64-bit-time-t-compat.patch   
2024-04-25 14:29:44.0 -0700
@@ -0,0 +1,53 @@
+Description: compatibility with 64-bit time_t
+ linux/input.h uses a different structure when time_t is 64-bit, so
+ patch around this.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1067616
+Last-Update: 2024-04-25
+Forwarded: no
+
+Index: clanlib-1.0~svn3827/Sources/GL/GLX/input_device_linuxevent.cpp

Processed: clanlib FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags 1069385 patch
Bug #1069385 [src:clanlib] FTBFS: dh_installdocs: error: Requested unknown 
package libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ...
Ignoring request to alter tags of bug #1069385 to the same tags previously set

-- 
1067616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067616
1069385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: clanlib FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags 1069385 patch
Bug #1069385 [src:clanlib] FTBFS: dh_installdocs: error: Requested unknown 
package libclanapp-1.0v5 via --link-doc, expected one of: libclanapp-1.0t64 ...
Added tag(s) patch.

-- 
1062074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062074
1069385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1069878, tagging 1069350, tagging 1069549, found 1069433 in 4.1.6-5, affects 1069433 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1069878 + sid trixie
Bug #1069878 [dm-writeboost-dkms] dm-writeboost-dkms: kernel module fails to 
build for Linux 6.7.12: error: too few arguments to function ‘dm_io’
Added tag(s) sid and trixie.
> tags 1069350 - sid trixie
Bug #1069350 [src:netavark] netavark: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo build returned exit code 101
Removed tag(s) trixie and sid.
> tags 1069549 - sid trixie
Bug #1069549 [src:racket] racket: FTBFS on armel: dh_install: error: missing 
files, aborting
Removed tag(s) sid and trixie.
> found 1069433 4.1.6-5
Bug #1069433 [openmpi] gtg-trace: FTBFS on armhf: tests fail
There is no source info for the package 'openmpi' at version '4.1.6-5' with 
architecture ''
Unable to make a source version for version '4.1.6-5'
Marked as found in versions 4.1.6-5.
> affects 1069433 = src:gtg-trace
Bug #1069433 [openmpi] gtg-trace: FTBFS on armhf: tests fail
Removed indication that 1069433 affects gtg-trace
Added indication that 1069433 affects src:gtg-trace
> tags 1069542 - sid trixie
Bug #1069542 [src:octave] octave: FTBFS on armel: make[1]: *** 
[debian/rules:59: override_dh_auto_build-indep] Error 1
Removed tag(s) sid and trixie.
> tags 1069424 - sid trixie
Bug #1069424 [src:yosys] yosys: FTBFS on armhf: make[3]: *** [Makefile:32: 
011/submod_dots.pdf] Error 1
Removed tag(s) sid and trixie.
> notfound 1064282 24.02.0-1
Bug #1064282 [src:poppler] poppler: NMU diff for 64-bit time_t transition
No longer marked as found in versions poppler/24.02.0-1.
> fixed 1064282 24.02.0-1
Bug #1064282 [src:poppler] poppler: NMU diff for 64-bit time_t transition
Marked as fixed in versions poppler/24.02.0-1.
> reassign 969907 src:poppler 20.09.0-2
Bug #969907 {Done: Amin Bandali } [libpoppler-glib8] 
inkscape, etc. crashing with mismatched libpoppler102 and libpoppler-glib8
Bug #1012532 {Done: Amin Bandali } [libpoppler-glib8] 
inkscape: PDF import no longer works
Bug reassigned from package 'libpoppler-glib8' to 'src:poppler'.
Bug reassigned from package 'libpoppler-glib8' to 'src:poppler'.
No longer marked as found in versions poppler/20.09.0-2.
No longer marked as found in versions poppler/20.09.0-2.
No longer marked as fixed in versions poppler/23.08.0-1.
No longer marked as fixed in versions poppler/23.08.0-1.
Bug #969907 {Done: Amin Bandali } [src:poppler] inkscape, 
etc. crashing with mismatched libpoppler102 and libpoppler-glib8
Bug #1012532 {Done: Amin Bandali } [src:poppler] inkscape: 
PDF import no longer works
Marked as found in versions poppler/20.09.0-2.
Marked as found in versions poppler/20.09.0-2.
> fixed 969907 23.08.0-1
Bug #969907 {Done: Amin Bandali } [src:poppler] inkscape, 
etc. crashing with mismatched libpoppler102 and libpoppler-glib8
Bug #1012532 {Done: Amin Bandali } [src:poppler] inkscape: 
PDF import no longer works
Marked as fixed in versions poppler/23.08.0-1.
Marked as fixed in versions poppler/23.08.0-1.
> tags 1069469 - sid trixie
Bug #1069469 [libahven-dev] libahven-dev not installable on armhf
Removed tag(s) trixie and sid.
> tags 1069468 - sid trixie
Bug #1069468 [src:pcscada] pcscada: FTBFS on armhf: build-dependency not 
installable: libahven-dev
Removed tag(s) trixie and sid.
> found 1069468 0.7.7-5
Bug #1069468 [src:pcscada] pcscada: FTBFS on armhf: build-dependency not 
installable: libahven-dev
Marked as found in versions pcscada/0.7.7-5.
> tags 1069468 - sid trixie
Bug #1069468 [src:pcscada] pcscada: FTBFS on armhf: build-dependency not 
installable: libahven-dev
Ignoring request to alter tags of bug #1069468 to the same tags previously set
> found 1069454 0.6.2-4
Bug #1069454 [src:libalog] libalog: FTBFS on armhf: build-dependency not 
installable: libahven-dev
Marked as found in versions libalog/0.6.2-4.
> tags 1069454 - sid trixie
Bug #1069454 [src:libalog] libalog: FTBFS on armhf: build-dependency not 
installable: libahven-dev
Removed tag(s) trixie and sid.
> tags 1069421 - sid trixie
Bug #1069421 [src:dbusada] dbusada: FTBFS on armhf: build-dependency not 
installable: libahven-dev
Removed tag(s) sid and trixie.
> found 1069421 0.6.2-5
Bug #1069421 [src:dbusada] dbusada: FTBFS on armhf: build-dependency not 
installable: libahven-dev
Marked as found in versions dbusada/0.6.2-5.
> found 1067616 1.0~svn3827-11
Bug #1067616 [src:clanlib] FTBFS: error: ‘struct input_event’ has no member 
named ‘time’
Marked as found in versions clanlib/1.0~svn3827-11.
> found 1069216 0.24.0-1
Bug #1069216 [src:rust-futures-rustls] rust-futures-rustls: Fails to build from 
source
Marked as found in versions rust-futures-rustls/0.24.0-1.
> notfixed 1069545 1:25.3.2.11+dfsg-1
Bug #1069545 {Done: Sergei Golovan } [src:erlang] erlang: 
FTBFS on armel: make[4]: *** 
[/<>/make/arm-unknown-linux-gnueabi/otp.mk:325: 
../pdf/wx-2.2.2.1.pdf] Error 1
No longer marked as fixed in versions 1:25.3.2.11+dfsg-1.
> found 1069476 2.1.0-27
Bug #1069476 [src:libtexttools] libtexttools: FTBFS on armhf: make[1]: *** 

Bug#1056196: marked as done (python3-onelogin-saml2: Please package new version 1.16.0, as current version will FTBFS soon)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 18:20:41 +
with message-id 
and subject line Bug#1056196: fixed in python3-onelogin-saml2 1.16.0-1
has caused the Debian Bug report #1056196,
regarding python3-onelogin-saml2: Please package new version 1.16.0, as current 
version will FTBFS soon
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:python3-onelogin-saml2
Version: 1.12.0-3
Severity: important

I've recently fixed a build error related to expired certificates
used in the tests. However, I see that the current package in unstable
will FTBFS in the future:

https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/python3-onelogin-saml2_1.12.0-3.rbuild.log.gz

This is from the build log:

Current time: Fri Dec 20 10:52:08 -12 2024

and I can reproduce the error by using the "libfaketime" package
in this way:

LD_PRELOAD=/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1 FAKETIME="+1y" 
dpkg-buildpackage -uc -us -b

So, before bothering upstream and telling them that the tests still fail,
I'd like to see a more recent version in unstable, then I will be able to see
if there are more things to backport for stable or not.

Thanks.
--- End Message ---
--- Begin Message ---
Source: python3-onelogin-saml2
Source-Version: 1.16.0-1
Done: Alexandre Detiste 

We believe that the bug you reported is fixed in the latest version of
python3-onelogin-saml2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated 
python3-onelogin-saml2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Apr 2024 19:56:00 +0200
Source: python3-onelogin-saml2
Architecture: source
Version: 1.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Alexandre Detiste 
Closes: 1056196
Changes:
 python3-onelogin-saml2 (1.16.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.16.0 (Closes: #1056196)
   * remove old extraneous dependencies on python3-mock & python3-six
   * use new dh-sequence-python3
   * run test with pytest like upstream does
   * set Rules-Requires-Root: no
 .
   [ Colin Watson ]
   * Apply patch from https://github.com/SAML-Toolkits/python3-saml/pull/399
 to fix failing testValidateTimestamps.
Checksums-Sha1:
 5b8e965f0684a261043c0756e573f839f35010c2 2338 
python3-onelogin-saml2_1.16.0-1.dsc
 6641e973546be3df3db89254b74fbac56bb3ddda 3578998 
python3-onelogin-saml2_1.16.0.orig.tar.gz
 f3aa9c2995df74e2e87479ff46f698532b915971 5504 
python3-onelogin-saml2_1.16.0-1.debian.tar.xz
 ca423bd69362e10f1c1905a5309f606567f6d2dc 7311 
python3-onelogin-saml2_1.16.0-1_source.buildinfo
Checksums-Sha256:
 69cf796ff0f07253b01a8ab7dfec8e0f77cb9e0643b9e955c2c942a6a494fb01 2338 
python3-onelogin-saml2_1.16.0-1.dsc
 41c41d986b0ef66635aa53abe51dfe0e09b1fb07a8803cbbdc861c3f82b6d15a 3578998 
python3-onelogin-saml2_1.16.0.orig.tar.gz
 1c25a269e97e9a7b46fb744a7356d5c66214e9715bfb2fa0a2266aa45e0717e3 5504 
python3-onelogin-saml2_1.16.0-1.debian.tar.xz
 e76c2c8c4499e3a144857a26683bdf8f73e92745d56d30d7ada10a73fb76237b 7311 
python3-onelogin-saml2_1.16.0-1_source.buildinfo
Files:
 2f2b24ebbc91e2ec7cf239c4cbe98e61 2338 python optional 
python3-onelogin-saml2_1.16.0-1.dsc
 9857f093e6b860e51138010aa01ca31a 3578998 python optional 
python3-onelogin-saml2_1.16.0.orig.tar.gz
 57f15537ffba670433aa9f47255ff813 5504 python optional 
python3-onelogin-saml2_1.16.0-1.debian.tar.xz
 b272396163c1c99f4060a62a9434d531 7311 python optional 
python3-onelogin-saml2_1.16.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmYr63IRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBpNIA/+Jn6CdR4dwnRmtGlrx1kSn/WcF2DGeV91
Ji72bKq2prAosjSflZMTetFl5Cmua+W3+tgSNU4KzUnedh3AV58CINjfK1Nex7tP
FHI89yENRcSCAQ0nOn2xig+JJTOsPkCrFjm/45IVHeyID0tBmJE8GCoEYXq6mTE5
hMHyDgWQl0yhf+7hqE00hCt3F4/35F+LR/8mSjuc9Fy9GssLSdSM/4Vz6W0j+frU

Bug#1067474: gxr-openvr: package Build-Depends on libgxr-0.15-0 whic is no longer built

[Andreas Beckmann]

Followup-For: Bug #1067474
Control: tag -1 pending

Hi,

I've just uploaded a NMU (diff attached) to DELAYED/2 fixing this issue,
a followup issue (from Ubuntu) and cleaning up some cruft.
Please let me know if I should delay it longer.

Andreas

PS: the Vcs-* variables point to the repository of a different package.
You probably need to append '-b debian/master-openvr' (if that is the
correct branch) to Vcs-Git.
diff -Nru gxr-openvr-0.15.1/debian/changelog gxr-openvr-0.15.1/debian/changelog
--- gxr-openvr-0.15.1/debian/changelog  2020-08-08 07:22:29.0 +0200
+++ gxr-openvr-0.15.1/debian/changelog  2024-04-26 20:00:15.0 +0200
@@ -1,3 +1,19 @@
+gxr-openvr (0.15.1-2.1) unstable; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Non-maintainer upload.
+  * Fix building twice in a row.
+  * Switch B-D from pkg-config to pkgconf.
+
+  [ Michael Hudson-Doyle ]
+  * s/libgxr-0.15-0/libgxr-dev/ in Build-Depends.  (Closes: #1067474)
+
+  [ Julian Andres Klode ]
+  * Remove libgxr-0.15-0, libsdl-2.0-0 depends. They are taken care of by
+shlibs and break time_t.
+
+ -- Andreas Beckmann   Fri, 26 Apr 2024 20:00:15 +0200
+
 gxr-openvr (0.15.1-2) unstable; urgency=medium
 
   * Source only upload.
diff -Nru gxr-openvr-0.15.1/debian/clean gxr-openvr-0.15.1/debian/clean
--- gxr-openvr-0.15.1/debian/clean  1970-01-01 01:00:00.0 +0100
+++ gxr-openvr-0.15.1/debian/clean  2024-04-26 19:36:45.0 +0200
@@ -0,0 +1,2 @@
+build/
+examples/cube/shaders/*.spv
diff -Nru gxr-openvr-0.15.1/debian/control gxr-openvr-0.15.1/debian/control
--- gxr-openvr-0.15.1/debian/control2020-08-08 07:22:12.0 +0200
+++ gxr-openvr-0.15.1/debian/control2024-04-26 19:58:51.0 +0200
@@ -11,25 +11,22 @@
  gtk-doc-tools,
  libgtk-3-dev (>= 3.22),
  libgulkan-dev (>= 0.15.0),
- libgxr-0.15-0,
+ libgxr-dev,
  libjson-glib-dev,
  libopenvr-dev,
  mesa-common-dev,
  meson (>= 0.45.1),
- pkg-config,
+ pkgconf,
 Standards-Version: 4.5.0
 Homepage: https://gitlab.freedesktop.org/xrdesktop/gxr
 Vcs-Browser: https://salsa.debian.org/xrdesktop-team/gxr
 Vcs-Git: https://salsa.debian.org/xrdesktop-team/gxr.git
 
 Package: libgxr-openvr-0.15-0
-Section: contrib/libs
 Architecture: linux-any
 Depends:
  ${misc:Depends},
  ${shlibs:Depends},
- libgxr-0.15-0,
- libsdl2-2.0-0,
 Breaks: libgxr-0.14-0 (<< 0.15)
 Replaces: libgxr-0.14-0 (<< 0.15)
 Description: gxr backend for nonfree OpenVR libraries
diff -Nru gxr-openvr-0.15.1/debian/rules gxr-openvr-0.15.1/debian/rules
--- gxr-openvr-0.15.1/debian/rules  2020-08-08 07:22:12.0 +0200
+++ gxr-openvr-0.15.1/debian/rules  2024-04-26 19:55:16.0 +0200
@@ -25,4 +25,3 @@
env $(test_env) meson build
env $(test_env) ninja -C build
env $(test_env) meson test -C build/ --no-suite gxr:xr --no-suite 
post-install
-

Processed: Re: gxr-openvr: package Build-Depends on libgxr-0.15-0 whic is no longer built

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067474 [src:gxr-openvr] gxr-openvr: package Build-Depends on 
libgxr-0.15-0 whic is no longer built
Added tag(s) pending.

-- 
1067474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069756: readability: build time test error: lxml.html.clean module is now a separate project lxml_html_clean

[Étienne Mollier]

Hi Colin,

Colin Watson, on 2024-04-26:
> Based on https://github.com/buriy/python-readability/issues/179, it
> looks as though upstream intends to switch to bleach; I think we can
> just patch setup.py in Debian in the meantime though.  I'll do that.

Looks good to me, thanks for tackling this!

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/3, please excuse my verbosity
   `-on air: Saga - Give 'Em The Money


signature.asc
Description: PGP signature

Bug#1065777: marked as done (clblas: FTBFS on arm{el,hf}: /<>/src/library/blas/gens/symv.c:955:29: error: implicit declaration of function ‘abs’; did you mean ‘fabs’? [-Werror=implicit-fu

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 17:19:20 +
with message-id 
and subject line Bug#1065777: fixed in clblas 2.12-5
has caused the Debian Bug report #1065777,
regarding clblas: FTBFS on arm{el,hf}: 
/<>/src/library/blas/gens/symv.c:955:29: error: implicit 
declaration of function ‘abs’; did you mean ‘fabs’? 
[-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clblas
Version: 2.12-4.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=clblas=armel=2.12-4.1=1709170039=0

cd /<>/obj-arm-linux-gnueabi/library/tools/tune && /usr/bin/cc 
-DCLBLAS_BONAIRE_DYNAMIC_KERNEL -DCLBLAS_HAWAII_DYNAMIC_KERNEL 
-DCLBLAS_TAHITI_DYNAMIC_KERNEL -DCL_USE_DEPRECATED_OPENCL_1_1_APIS 
-DCL_USE_DEPRECATED_OPENCL_2_0_APIS -D_POSIX_C_SOURCE=199309L 
-D_XOPEN_SOURCE=500 -I/<>/src -I/<>/src/include 
-I/<>/src/library/blas/include 
-I/<>/src/library/blas/gens 
-I/<>/obj-arm-linux-gnueabi/include 
-I/<>/src/library/tools/tune -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -pedantic -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 
-Wstrict-prototypes -fno-builtin -MD -MT 
library/tools/tune/CMakeFiles/tune.dir/__/__/blas/gens/symv.c.o -MF 
CMakeFiles/tune.dir/__/__/blas/gens/symv.c.o.d -o 
CMakeFiles/tune.dir/__/__/blas/gens/symv.c.o -c 
/<>/src/library/blas/gens/symv.c
[ 14%] Building C object 
library/tools/tune/CMakeFiles/tune.dir/__/__/blas/gens/gemm.c.o
cd /<>/obj-arm-linux-gnueabi/library/tools/tune && /usr/bin/cc 
-DCLBLAS_BONAIRE_DYNAMIC_KERNEL -DCLBLAS_HAWAII_DYNAMIC_KERNEL 
-DCLBLAS_TAHITI_DYNAMIC_KERNEL -DCL_USE_DEPRECATED_OPENCL_1_1_APIS 
-DCL_USE_DEPRECATED_OPENCL_2_0_APIS -D_POSIX_C_SOURCE=199309L 
-D_XOPEN_SOURCE=500 -I/<>/src -I/<>/src/include 
-I/<>/src/library/blas/include 
-I/<>/src/library/blas/gens 
-I/<>/obj-arm-linux-gnueabi/include 
-I/<>/src/library/tools/tune -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -pedantic -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 
-Wstrict-prototypes -fno-builtin -MD -MT 
library/tools/tune/CMakeFiles/tune.dir/__/__/blas/gens/gemm.c.o -MF 
CMakeFiles/tune.dir/__/__/blas/gens/gemm.c.o.d -o 
CMakeFiles/tune.dir/__/__/blas/gens/gemm.c.o -c 
/<>/src/library/blas/gens/gemm.c
In file included from /usr/include/CL/cl.h:20,
 from /<>/src/clBLAS.h:35,
 from /<>/src/library/blas/gens/symv.c:27:
/usr/include/CL/cl_version.h:22:9: note: ‘#pragma message: cl_version.h: 
CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)’
   22 | #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. 
Defaulting to 300 (OpenCL 3.0)")
  | ^~~
In file included from /usr/include/CL/cl.h:20,
 from /<>/src/clBLAS.h:35,
 from /<>/src/library/blas/gens/gemm.c:28:
/usr/include/CL/cl_version.h:22:9: note: ‘#pragma message: cl_version.h: 
CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)’
   22 | #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. 
Defaulting to 300 (OpenCL 3.0)")
  | ^~~
/<>/src/library/blas/gens/symv.c: In function ‘fixupArgs’:
/<>/src/library/blas/gens/symv.c:955:29: error: implicit 
declaration of function ‘abs’; did you mean ‘fabs’? 
[-Werror=implicit-function-declaration]
  955 | abs(kargs->ldc.Vector);
  | ^~~
  | fabs
cc1: some warnings being treated as errors
make[3]: *** [library/tools/tune/CMakeFiles/tune.dir/build.make:443: 
library/tools/tune/CMakeFiles/tune.dir/__/__/blas/gens/gemv.c.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: clblas
Source-Version: 2.12-5
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
clblas, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which 

Bug#1021924: networking-mlnx: FTBFS test failures: sqlalchemy.exc.InvalidRequestError: A transaction is already begun on this Session.

[Santiago Vila]

El 17/10/22 a las 14:04, Michael Biebl escribió:

Source: networking-mlnx
Version: 1:16.0.0-3
Severity: serious
Tags: ftbfs

networking-mlnx FTBFS in unstable

It appears to be trigger lots of test suite failures and is killed
eventually


I think it's even worse than that: The test suite seems to enter an endless 
loop,
producing a bigger and bigger build log, and the build needs to be killed by 
hand
because otherwise the build log would take all available disk space.

The last log I got grew to 6 GB until I decided to kill it:

-rw-r--r-- 1 master master 6002644863 abr 26 14:40 
networking-mlnx_16.0.0-3.1_amd64-20240426T144020.998Z

No surprise that the state of this package in Reproducible Builds is "banned":

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/networking-mlnx.html

For such reason, I believe this package should be removed from unstable and
uploaded to experimental instead, at the very minimum.

Cc:ing all relevant parties.

Thanks.

Bug#1069842: marked as done (rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 16:52:48 +
with message-id 
and subject line Bug#1069842: fixed in r-base 4.4.0-2
has caused the Debian Bug report #1069842,
regarding rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or 
directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:rjava
Version: 1.0-11-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build --buildsystem R
   dh_update_autotools_config -O--buildsystem=R
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
   dh_autoreconf -O--buildsystem=R
   dh_auto_configure -O--buildsystem=R
   dh_auto_build -O--buildsystem=R
   dh_auto_test -O--buildsystem=R
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary
dh binary --buildsystem R
   dh_testroot -O--buildsystem=R
   dh_prep -O--buildsystem=R
   dh_auto_install --destdir=debian/r-cran-rjava/ -O--buildsystem=R
I: R Package: rJava Version: 1.0-11
I: Building using R version 4.4.0-1
I: R API version: r-api-4.0
I: Using built-time from d/changelog: Fri, 26 Jan 2024 11:10:09 -0600
mkdir -p /<>/debian/r-cran-rjava/usr/lib/R/site-library
R CMD INSTALL -l /<>/debian/r-cran-rjava/usr/lib/R/site-library 
--clean . "--built-timestamp='Fri, 26 Jan 2024 11:10:09 -0600'"
* installing *source* package ‘rJava’ ...
files ‘configure’, ‘jri/tools/config.guess’, ‘jri/tools/config.sub’, 
‘src/config.h.in’ have the wrong MD5 checksums
** using staged installation
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for string.h... (cached) yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
configure: checking whether gcc supports static inline...
yes
checking whether setjmp.h is POSIX.1 compatible... yes
checking for gcc options needed to detect all undeclared functions... none 
needed
checking whether sigsetjmp is declared... yes
checking whether siglongjmp is declared... yes
checking Java support in R... present:
interpreter : '/usr/lib/jvm/default-java/bin/java'
archiver: '/usr/lib/jvm/default-java/bin/jar'
compiler: '/usr/lib/jvm/default-java/bin/javac'
header prep.: ''
cpp flags   : '-I/usr/lib/jvm/default-java/include 
-I/usr/lib/jvm/default-java/include/linux'
java libs   : '-L/usr/lib/jvm/default-java/lib/server -ljvm'
checking whether Java run-time works... yes
checking whether -Xrs is supported... yes
checking whether -Xrs will be used... yes
checking whether JVM will be loaded dynamically... no
checking whether JNI programs can be compiled... yes
checking whether JNI programs run... yes
checking JNI data types... ok
checking whether JRI should be compiled (autodetect)... yes
checking whether debugging output should be enabled... no
checking whether memory profiling is desired... no
checking whether threads support is requested... no
checking whether callbacks support is requested... no
checking whether JNI cache support is requested... no
checking whether headless init is enabled... no
checking whether JRI is requested... yes
configure: creating ./config.status
config.status: creating src/Makevars
config.status: creating R/zzz.R
config.status: creating src/config.h
=== configuring in jri (/<>/jri)
configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr/local'  
'CC=gcc' 'CFLAGS=-g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat 

Bug#1069756: marked as done (readability: build time test error: lxml.html.clean module is now a separate project lxml_html_clean)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 16:25:48 +
with message-id 
and subject line Bug#1069756: fixed in readability 0.8.1+dfsg1-4
has caused the Debian Bug report #1069756,
regarding readability: build time test error: lxml.html.clean module is now a 
separate project lxml_html_clean
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: readability
Version: 0.8.1+dfsg1-3
Severity: serious
Tags: ftbfs
Justification: ftbfs

Dear Maintainer,

Attempt to run readability tests at build time results in the
following error:

==
ERROR: readability (unittest.loader._FailedTest.readability)
--
ImportError: Failed to import test module: readability
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 452, in 
_find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 362, in 
_get_module_from_name
__import__(name)
  File 
"/<>/.pybuild/cpython3_3.11/build/readability/__init__.py", line 
3, in 
from .readability import Document
  File 
"/<>/.pybuild/cpython3_3.11/build/readability/readability.py", 
line 11, in 
from .cleaners import clean_attributes
  File 
"/<>/.pybuild/cpython3_3.11/build/readability/cleaners.py", line 
3, in 
from lxml.html.clean import Cleaner
  File "/usr/lib/python3/dist-packages/lxml/html/clean.py", line 18, in 

raise ImportError(
ImportError: lxml.html.clean module is now a separate project 
lxml_html_clean.
Install lxml[html_clean] or lxml_html_clean directly.

As far as I could witness, replacing the python3-lxml build
dependency by python3-lxml-html-clean resolved the issue at
least for the bulid time test.  The package is subject to
autodep8 python3 test, which raises that the binary package will
also need it dependencies adjusted; this suggests the setup.py
would probably need patching so this is addressed appropriately
at a larger scale than Debian's.  The missing dependency on
python3-lxml-html-clean is also causing a regression in offpunk
autopkgtest[1], although that could be easily worked around by
pulling the missing dependency there.

[1]: https://ci.debian.net/packages/o/offpunk/unstable/amd64/44684161/

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/4, please excuse my verbosity
   `-on air: Mike Oldfield - Lion


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: readability
Source-Version: 0.8.1+dfsg1-4
Done: Colin Watson 

We believe that the bug you reported is fixed in the latest version of
readability, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated readability package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Apr 2024 16:39:16 +0100
Source: readability
Architecture: source
Version: 0.8.1+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Colin Watson 
Closes: 1069756
Changes:
 readability (0.8.1+dfsg1-4) unstable; urgency=medium
 .
   * Team upload.
   * Add (build-)dependency on python3-lxml-html-clean (closes: #1069756).
Checksums-Sha1:
 049a8bee60f5060f890863a598a85c7c8c695a20 2171 readability_0.8.1+dfsg1-4.dsc
 529099c836815b069c5dd5e9b1945c23a91d0720 3640 
readability_0.8.1+dfsg1-4.debian.tar.xz
 d4ed330a0e25aac01fb73894fa62715642c7234d 6805 
readability_0.8.1+dfsg1-4_source.buildinfo
Checksums-Sha256:
 b03cd45477452068afb0e51a5becc9c8f6989b42c75a5367963aa977ae784b5c 2171 
readability_0.8.1+dfsg1-4.dsc
 

Bug#1069844: More debug info

[Alex Bennée]

On Fri, 26 Apr 2024 at 16:48, Julian Andres Klode <
julian.kl...@canonical.com> wrote:

> On Thu, Apr 25, 2024 at 09:10:08PM +0100, Alex Bennée wrote:
> > Alex Bennée  writes:
> >
> > > Julian Andres Klode  writes:
> > >
> > >> On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote:
> > >>>
> > >>> Continuing to debug on QEMU it seems there is an incompatibility with
> > >>> the images and the peloader (which overrides the normal efi loader):
> > >>>
> > 
> > >
> > >> In the error case you can see though, that one of the section
> > >> addresses in the Xen binary to be relocated points into the (PE)
> > >> header of the binary, which obviously seems wrong.
> > >>
> > >> So go check your PE sections and check which one is wrong?
> > >
> > > Is there any tooling for examining PE sections?
> >
> > Nothing really jumps out from objdump:
> >
> > 1:08:50 [root@debian-arm64:~] # objdump -h /boot/xen
> >
> >   /boot/xen: file format pei-aarch64-little
> >
> >   Sections:
> >   Idx Name  Size  VMA   LMA   File
> off  Algn
> > 0 .reloc    
>   2**0
> > ALLOC, LOAD, READONLY, DATA
>
>
> This looks suspicious. Yes it's 0 size but it's address is 0 which
> clearly points into the header, and we don't skip 0 size sections when
> loading the PE binary for later relocation, and we don't use any .reloc
> section.
>

It does get skipped in the reloc code:

  if (!info->reloc || !(info->reloc->size))
{
  grub_dprintf ("linux", "no relocations\n");
  return GRUB_EFI_SUCCESS;
}

Although the x86_64 build of Xen uses reloc sections (which Xen itself
deals with) we don't actually need them for Arm. However the way the PE
binary is built is a little funky:

make

  UPD include/xen/compile.h


 Xen 4.19-unstable

make[1]: Nothing to be done for 'include'.

make[1]: 'arch/arm/include/asm/asm-offsets.h' is up to date.

  CC  common/version.o

  LD  common/built_in.o

  CC  arch/arm/acpi/domain_build.o

  INIT_O  arch/arm/acpi/domain_build.init.o


  LD  arch/arm/acpi/built_in.o

  CC  arch/arm/domain_build.o

  INIT_O  arch/arm/domain_build.init.o

  CC  arch/arm/efi/boot.o

  INIT_O  arch/arm/efi/boot.init.o

  LD  arch/arm/efi/built_in.o

  CC  arch/arm/setup.o


  LD  arch/arm/built_in.o

  LD  prelink.o

ld-EL --no-warn-rwx-segments --fix-cortex-a53-843419 -T
arch/arm/xen.lds -N prelink.o \

./common/symbols-dummy.o -o ./.xen-syms.0

nm -pa --format=sysv ./.xen-syms.0 \

| ./tools/symbols  --sysv --sort \

> ./.xen-syms.0.S

make -f ./Rules.mk obj=. ./.xen-syms.0.o

  CC  .xen-syms.0.o

ld-EL --no-warn-rwx-segments --fix-cortex-a53-843419 -T
arch/arm/xen.lds -N prelink.o \
./.xen-syms.0.o -o ./.xen-syms.1

nm -pa --format=sysv ./.xen-syms.1 \

| ./tools/symbols  --sysv --sort \


> ./.xen-syms.1.S

make -f ./Rules.mk obj=. ./.xen-syms.1.o


  CC  .xen-syms.1.o

ld-EL --no-warn-rwx-segments --fix-cortex-a53-843419 -T
arch/arm/xen.lds -N prelink.o --build-id=sha1 \
./.xen-syms.1.o -o xen-syms

nm -pa --format=sysv xen-syms \

| ./tools/symbols --all-symbols --xensyms --sysv --sort \

> xen-syms.map

rm -f ./.xen-syms.[0-9]*

objcopy -O binary -S xen-syms xen

ln -sf xen xen.efi

I can't work out how to build without the reloc section and trying to
remove the .reloc section after the fact results in something where the
file-offset is ahead of the VMA position:

➜  objcopy --remove-section=.reloc -O binary -S xen-syms xen-test

17:03:23 alex@gwenyn:xen.git/xen  on  testing/new-attempt:new-attempt
[!?]
➜  objdump -h xen-test




xen-test: file format pei-aarch64-little



Sections:


Idx Name  Size  VMA   LMA   File off
 Algn
  0 .reloc      
 2**0

  ALLOC, LOAD, READONLY, DATA

  1 .text 00127ea8  0160  0160  0160
 2**4

  CONTENTS, ALLOC, LOAD, CODE

17:03:25 alex@gwenyn:xen.git/xen  on  testing/new-attempt:new-attempt
[!?]
➜  objcopy --remove-section=.reloc xen-test


17:03:37 alex@gwenyn:xen.git/xen  on  testing/new-attempt:new-attempt
[!?]
➜  objdump -h xen-test



xen-test: file format pei-aarch64-little



Sections:

Idx Name  Size  VMA   LMA   File off
 Algn

  0 .text 00127ea8  0160  0160  01b0
 2**2
  CONTENTS, ALLOC, LOAD, CODE



>
> > 1 .text 00107ea8  0160  0160
> 0160  2**4
> > CONTENTS, ALLOC, LOAD, CODE
> >   21:08:53 [root@debian-arm64:~] # objdump -h /boot/vmlinuz
>
>
> I suppose the header is smaller than 0x160 bytes and this is ok.
>
> My colleague Heinrich has written a nice PE analyser tool too:
>
> 

Bug#1058322: marked as done (supertuxkart: FTBFS: SpirvIntrinsics.h:120:10: error: ‘variant’ in namespace ‘std’ does not name a template type)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 15:52:05 +
with message-id 
and subject line Bug#1057463: fixed in supertuxkart 1.4+dfsg-4
has caused the Debian Bug report #1057463,
regarding supertuxkart: FTBFS: SpirvIntrinsics.h:120:10: error: ‘variant’ in 
namespace ‘std’ does not name a template type
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: supertuxkart
Version: 1.4+dfsg-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/lib/tinygettext && /usr/bin/c++ 
> -DDISABLE_ICONV -DENABLE_IPV6 -DSUPERTUXKART_VERSION=\"1.4\" -DVERSION=0.1.0 
> -I/<>/lib/graphics_utils 
> -I/<>/lib/graphics_engine/include 
> -I/<>/lib/shaderc/libshaderc/include 
> -I/<>/lib/enet/include -I/<>/lib/bullet/src 
> -I/<>/lib/tinygettext/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++0x -O2 -DNDEBUG -MD -MT 
> lib/tinygettext/CMakeFiles/tinygettext.dir/src/dictionary.o -MF 
> CMakeFiles/tinygettext.dir/src/dictionary.o.d -o 
> CMakeFiles/tinygettext.dir/src/dictionary.o -c 
> /<>/lib/tinygettext/src/dictionary.cpp
> In file included from /usr/include/glslang/Include/Types.h:47,
>  from /usr/include/glslang/Include/intermediate.h:57,
>  from 
> /usr/include/glslang/MachineIndependent/localintermediate.h:42,
>  from /usr/include/glslang/SPIRV/SpvTools.h:50,
>  from /usr/include/glslang/SPIRV/GlslangToSpv.h:42,
>  from 
> /<>/lib/shaderc/libshaderc_util/src/compiler.cc:23:
> /usr/include/glslang/Include/SpirvIntrinsics.h:120:10: error: ‘variant’ in 
> namespace ‘std’ does not name a template type
>   120 | std::variant value;
>   |  ^~~
> /usr/include/glslang/Include/SpirvIntrinsics.h:120:5: note: ‘std::variant’ is 
> only available from C++17 onwards
>   120 | std::variant value;
>   | ^~~
> /usr/include/glslang/Include/SpirvIntrinsics.h: In constructor 
> ‘glslang::TSpirvTypeParameter::TSpirvTypeParameter(const 
> glslang::TIntermConstantUnion*)’:
> /usr/include/glslang/Include/SpirvIntrinsics.h:100:60: error: ‘value’ was not 
> declared in this scope
>   100 | TSpirvTypeParameter(const TIntermConstantUnion* arg) { value = 
> arg; }
>   |^
> /usr/include/glslang/Include/SpirvIntrinsics.h: In constructor 
> ‘glslang::TSpirvTypeParameter::TSpirvTypeParameter(const glslang::TType*)’:
> /usr/include/glslang/Include/SpirvIntrinsics.h:101:45: error: ‘value’ was not 
> declared in this scope
>   101 | TSpirvTypeParameter(const TType* arg) { value = arg; }
>   | ^
> /usr/include/glslang/Include/SpirvIntrinsics.h: In member function ‘const 
> glslang::TIntermConstantUnion* glslang::TSpirvTypeParameter::getAsConstant() 
> const’:
> /usr/include/glslang/Include/SpirvIntrinsics.h:105:13: error: ‘value’ was not 
> declared in this scope
>   105 | if (value.index() == 0)
>   | ^
> /usr/include/glslang/Include/SpirvIntrinsics.h: In member function ‘const 
> glslang::TType* glslang::TSpirvTypeParameter::getAsType() const’:
> /usr/include/glslang/Include/SpirvIntrinsics.h:111:13: error: ‘value’ was not 
> declared in this scope
>   111 | if (value.index() == 1)
>   | ^
> [  2%] Building CXX object 
> lib/bullet/CMakeFiles/bulletcollision.dir/src/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp.o
> cd /<>/obj-x86_64-linux-gnu/lib/bullet && /usr/bin/c++ 
> -DSUPERTUXKART_VERSION=\"1.4\" -I/<>/lib/bullet/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -DNDEBUG -MD -MT 
> lib/bullet/CMakeFiles/bulletcollision.dir/src/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp.o
>  -MF 
> CMakeFiles/bulletcollision.dir/src/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp.o.d
>  -o 
> CMakeFiles/bulletcollision.dir/src/BulletCollision/BroadphaseCollision/btCollisionAlgorithm.cpp.o
>  -c 
> 

Bug#1068805: marked as done (python3-pywt: distutils not available in Python 3.12)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 15:50:21 +
with message-id 
and subject line Bug#1068805: fixed in pywavelets 1.4.1-1
has caused the Debian Bug report #1068805,
regarding python3-pywt: distutils not available in Python 3.12
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: python3-pywt
Version: 1.1.1-3
Severity: serious

Dear maintainer,

pywt directly depends on distutils, which is no longer available on 
Python 3.12. in pywt/__init__.py:


---8<--
from __future__ import division, print_function, absolute_import
from distutils.version import LooseVersion
---8<--

This makes the current version of pywt unusable on Python 3.12.

Best

Ole
--- End Message ---
--- Begin Message ---
Source: pywavelets
Source-Version: 1.4.1-1
Done: Colin Watson 

We believe that the bug you reported is fixed in the latest version of
pywavelets, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated pywavelets package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Apr 2024 16:12:54 +0100
Source: pywavelets
Architecture: source
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Colin Watson 
Closes: 1000232 1068805
Changes:
 pywavelets (1.4.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release:
 - Remove distutils dependency (closes: #1068805).
   * Remove misspelled override_dh_fixperms_indep and
 override_dh_fixperms_arch targets from debian/rules; they're no longer
 needed anyway.
   * Build-depend on dh-sequence-numpy3 (closes: #1000232).
   * Fix handling of SOURCE_DATE_EPOCH in debian/rules.
Checksums-Sha1:
 7488b13c9529f53e7a91ccbc6605c473a4b468a1 2300 pywavelets_1.4.1-1.dsc
 952c8f17a899f91642c2a4c9a212a30ab952135a 4589677 pywavelets_1.4.1.orig.tar.gz
 68675d2782024b573cd6fd75543b69d1352ead28 8632 pywavelets_1.4.1-1.debian.tar.xz
Checksums-Sha256:
 6320f99d98b5ca744a61a120d39eb1c1b62fbfa03aa82f65c99058df82c94bce 2300 
pywavelets_1.4.1-1.dsc
 6437af3ddf083118c26d8f97ab43b0724b956c9f958e9ea788659f6a2834ba93 4589677 
pywavelets_1.4.1.orig.tar.gz
 a4926079db63626cc5bbfeb6a0ccc680093e444dccdea7e6eb8963fb5cb72785 8632 
pywavelets_1.4.1-1.debian.tar.xz
Files:
 82c3e2d0603008f3b1a9eb6b8048135b 2300 python optional pywavelets_1.4.1-1.dsc
 6e487b2c3418fc0a1acf3be53bfbb0c3 4589677 python optional 
pywavelets_1.4.1.orig.tar.gz
 407b2ae49defcbf4d44957c27033fdeb 8632 python optional 
pywavelets_1.4.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrxLkACgkQOTWH2X2G
UAt98BAAjN7VkB7Bs2miVjOuRW8XDxP7paGxeRX5jMCe17Eqjyot3nRgGBg4qBLp
Df7IMqCkwOcfYqHCd2zQQPfqMUcUx1SPM9oDuFizd7M627RSvXis3MFiUU3piJRJ
BBOZ9cJrr3KxS5tYggweGVMVCojC8XBrs92rAN8ygKq3TDLI+KYxGSqU3XV7iAvY
vyVH853n+mBS3HPvJOMM1PfwQx9r3kXg+IK+ACH/UN2Y5+BM1Fe6TzGzF3BlRqVq
wjrrgmd49Y7gCnNyqJSbMfqudcoaN7n3oA+92pumCYYBwDsE8yfdplzxvPXViA80
pKPIEtTdHcWXgbgroJAOVFPPwbR6g4b2ZvYVCTDDxVd8TC8nT0u/yYUJcUYkkBKH
FcOlH3VZkAXHVhGuewaKZ6mlGuGQ/R6pK8VK76o4SCqZHYWimAZEqpFH3RXny1uV
SN0nM4p51B61BPgke1BOmMJ0PCVqxtT6JY2a4GTSHveDHCgqrCG2ZlTgdtxayOKf
UJc1ABII1E8hmCafqrnKxSv0APGoPFuGsyiIw4KIPi2Qkz1XbBQIYrstIxUQMZHO
5nprmpOqsAYi9cWcopkuJ4voijIbb+74GfcEoDtw7zzFqlT98FRbCup4FfaHZ32b
Mxa2lF3l6AXERJCZ16FIhLZLbG4HpumfJvmnn4SHINAZ4V3b+0I=
=L08w
-END PGP SIGNATURE-



pgp26i_Vhi0wY.pgp
Description: PGP signature
--- End Message ---

Bug#1066357: marked as done (ldapvi: FTBFS: diff.c:218:9: error: implicit declaration of function ‘ldap_bv2dn_x’; did you mean ‘ldap_bv2dn’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 15:47:46 +
with message-id 
and subject line Bug#1066357: fixed in ldapvi 1.7-11
has caused the Debian Bug report #1066357,
regarding ldapvi: FTBFS: diff.c:218:9: error: implicit declaration of function 
‘ldap_bv2dn_x’; did you mean ‘ldap_bv2dn’? 
[-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldapvi
Version: 1.7-10
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -o diff.o diff.c
> diff.c: In function ‘safe_str2dn’:
> diff.c:218:9: error: implicit declaration of function ‘ldap_bv2dn_x’; did you 
> mean ‘ldap_bv2dn’? [-Werror=implicit-function-declaration]
>   218 | ldap_bv2dn_x(, out, flags);
>   | ^~~~
>   | ldap_bv2dn
> cc1: some warnings being treated as errors
> make[1]: *** [GNUmakefile:16: diff.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/ldapvi_1.7-10_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ldapvi
Source-Version: 1.7-11
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
ldapvi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated ldapvi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Apr 2024 11:15:30 -0400
Source: ldapvi
Architecture: source
Version: 1.7-11
Distribution: unstable
Urgency: medium
Maintainer: Rhonda D'Vine 
Changed-By: Boyuan Yang 
Closes: 1066357
Changes:
 ldapvi (1.7-11) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Avoid using transitional package names.
   * debian/control: Add missing dependency sensible-utils (lintian).
   * debian/patches/07,08: Add patch to fix FTBFS caused by
 Werror=implicit-function-declaration. (Closes: #1066357)
Checksums-Sha1:
 ad00b7931db71fd5f8a91518475626e1ba621021 1777 ldapvi_1.7-11.dsc
 d1cde4cbb618180f9ae0e77c56a1520b8ad61c9a 119503 ldapvi_1.7.orig.tar.gz
 707c8d4bd18f8dc8f0a93dd641a3b6c2a4fdd377 9592 ldapvi_1.7-11.debian.tar.xz
 99fb0011f9d98d283e87820a6819cb2bb4330454 7756 ldapvi_1.7-11_amd64.buildinfo
Checksums-Sha256:
 da7985a246d9274b0b68f6145e07dd5489f6c081346f06d5e88201bcf4b49e1f 1777 
ldapvi_1.7-11.dsc
 6f62e92d20ff2ac0d06125024a914b8622e5b8a0a0c2d390bf3e7990cbd2e153 119503 
ldapvi_1.7.orig.tar.gz
 bba97940aa50f74e72a67a6b710e0847f018064a5f053c69033cb46890786b17 9592 
ldapvi_1.7-11.debian.tar.xz
 

Bug#1057581: marked as done (node-clipanion: FTBFS: error TS2307: Cannot find module 'get-stream' or its corresponding type declarations.)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 15:49:10 +
with message-id 
and subject line Bug#1057581: fixed in node-get-stream 8.0.1-11
has caused the Debian Bug report #1057581,
regarding node-clipanion: FTBFS: error TS2307: Cannot find module 'get-stream' 
or its corresponding type declarations.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:node-clipanion
Version: 3.2.1+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with nodejs
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
/!\ website/package.json not found
Unable to load website
workspaces field found in package.json

Found debian/nodejs/additional_components
Link ./node_modules/tslib -> /usr/share/nodejs/tslib
Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha
Link ./node_modules/typescript -> /usr/share/nodejs/typescript
Link ./node_modules/@rollup/plugin-typescript -> 
/usr/share/nodejs/@rollup/plugin-typescript
Link ./node_modules/@types/chai -> /usr/share/nodejs/@types/chai
Link ./node_modules/ts-node -> /usr/share/nodejs/ts-node
Link ./node_modules/@types/chai-as-promised -> 
/usr/share/nodejs/@types/chai-as-promised
Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
Link ./node_modules/get-stream -> /usr/share/nodejs/get-stream
/!\ website/package.json not found
Unable to load website
Link ./node_modules/typanion -> /usr/share/nodejs/typanion
Found debian/nodejs/additional_components
   dh_auto_build --buildsystem=nodejs
/!\ website/package.json not found
Unable to load website
workspaces field found in package.json

Found debian/nodejs/additional_components
Found debian/nodejs/./build
cd ./. && sh -ex debian/nodejs/./build
+ rollup -c --bundleConfigAsCjs

/<>/sources/advanced/builtins/definitions.ts, /<>/sources/advanced/builtins/help.ts, /<>/sources/advanced/builtins/index.ts, /<>/sources/advanced/builtins/version.ts, /<>/sources/advanced/Cli.ts, 
/<>/sources/advanced/Command.ts, /<>/sources/advanced/HelpCommand.ts, /<>/sources/advanced/index.ts, /<>/sources/advanced/options/Array.ts, /<>/sources/advanced/options/Boolean.ts, 
/<>/sources/advanced/options/Counter.ts, /<>/sources/advanced/options/index.ts, /<>/sources/advanced/options/Proxy.ts, /<>/sources/advanced/options/Rest.ts, /<>/sources/advanced/options/String.ts, 
/<>/sources/advanced/options/utils.ts, /<>/sources/constants.ts, /<>/sources/core.ts, /<>/sources/errors.ts, /<>/sources/format.ts, /<>/sources/platform/browser.ts, 
/<>/sources/platform/node.ts → lib, lib...
(!) The "preserveModules" option is deprecated. Use the 
"output.preserveModules" option instead.
https://rollupjs.org/https://rollupjs.org/configuration-options/#output-preservemodules
created lib, lib in 3.7s
+ cp -a sources/platform/package.json lib/platform/
+ debian/apply-publish-config ./package.json
   dh_auto_test --buildsystem=nodejs
/!\ website/package.json not found
Unable to load website
workspaces field found in package.json

Found debian/nodejs/additional_components
ln -s ../. node_modules/clipanion
/bin/sh -ex debian/tests/pkg-js/test
+ FORCE_COLOR=1 mocha --require ts-node/register --extension ts tests/specs 
--exclude tests/specs/browser.test.ts --exclude tests/specs/treeshake.test.ts

TSError: ⨯ Unable to compile TypeScript:
tests/tools.ts(1,54): error TS2307: Cannot find module 'get-stream' or its 
corresponding type declarations.

at createTSError (/usr/share/nodejs/ts-node/src/index.ts:865:12)
at reportTSError (/usr/share/nodejs/ts-node/src/index.ts:869:19)
at getOutput (/usr/share/nodejs/ts-node/src/index.ts:1083:36)
at Object.compile (/usr/share/nodejs/ts-node/src/index.ts:1439:41)
at Module.m._compile (/usr/share/nodejs/ts-node/src/index.ts:1623:30)
at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
at Object.require.extensions. [as .ts] 
(/usr/share/nodejs/ts-node/src/index.ts:1627:12)
at Module.load (node:internal/modules/cjs/loader:1197:32)
at Function.Module._load (node:internal/modules/cjs/loader:1013:12)
at Module.require (node:internal/modules/cjs/loader:1225:19)
at require 

Bug#1069844: More debug info

[Julian Andres Klode]

On Thu, Apr 25, 2024 at 09:10:08PM +0100, Alex Bennée wrote:
> Alex Bennée  writes:
> 
> > Julian Andres Klode  writes:
> >
> >> On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote:
> >>> 
> >>> Continuing to debug on QEMU it seems there is an incompatibility with
> >>> the images and the peloader (which overrides the normal efi loader):
> >>> 
> 
> >
> >> In the error case you can see though, that one of the section
> >> addresses in the Xen binary to be relocated points into the (PE)
> >> header of the binary, which obviously seems wrong.
> >>
> >> So go check your PE sections and check which one is wrong?
> >
> > Is there any tooling for examining PE sections?
> 
> Nothing really jumps out from objdump:
> 
> 1:08:50 [root@debian-arm64:~] # objdump -h /boot/xen
> 
>   /boot/xen: file format pei-aarch64-little
> 
>   Sections:
>   Idx Name  Size  VMA   LMA   File off  
> Algn
> 0 .reloc        
> 2**0
> ALLOC, LOAD, READONLY, DATA


This looks suspicious. Yes it's 0 size but it's address is 0 which
clearly points into the header, and we don't skip 0 size sections when
loading the PE binary for later relocation, and we don't use any .reloc
section.


> 1 .text 00107ea8  0160  0160  0160  
> 2**4
> CONTENTS, ALLOC, LOAD, CODE
>   21:08:53 [root@debian-arm64:~] # objdump -h /boot/vmlinuz


I suppose the header is smaller than 0x160 bytes and this is ok.

My colleague Heinrich has written a nice PE analyser tool too:

https://github.com/xypron/efi_analyzer


-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1069756: marked as pending in readability

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1069756 in readability reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/readability/-/commit/8c36e8dac6b5aa7b09c55840971a988b36f6f77c


Add (build-)dependency on python3-lxml-html-clean

Closes: #1069756


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069756

Processed: Bug#1069756 marked as pending in readability

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1069756 [src:readability] readability: build time test error: 
lxml.html.clean module is now a separate project lxml_html_clean
Added tag(s) pending.

-- 
1069756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069756: readability: build time test error: lxml.html.clean module is now a separate project lxml_html_clean

[Colin Watson]

On Wed, Apr 24, 2024 at 11:16:17AM +0200, Étienne Mollier wrote:
> As far as I could witness, replacing the python3-lxml build
> dependency by python3-lxml-html-clean resolved the issue at
> least for the bulid time test.  The package is subject to
> autodep8 python3 test, which raises that the binary package will
> also need it dependencies adjusted; this suggests the setup.py
> would probably need patching so this is addressed appropriately
> at a larger scale than Debian's.

Based on https://github.com/buriy/python-readability/issues/179, it
looks as though upstream intends to switch to bleach; I think we can
just patch setup.py in Debian in the meantime though.  I'll do that.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Processed: ldapvi: diff for NMU version 1.7-11

[Debian Bug Tracking System]

Processing control commands:

> tags 1066357 + patch
Bug #1066357 [src:ldapvi] ldapvi: FTBFS: diff.c:218:9: error: implicit 
declaration of function ‘ldap_bv2dn_x’; did you mean ‘ldap_bv2dn’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.
> tags 1066357 + pending
Bug #1066357 [src:ldapvi] ldapvi: FTBFS: diff.c:218:9: error: implicit 
declaration of function ‘ldap_bv2dn_x’; did you mean ‘ldap_bv2dn’? 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

-- 
1066357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1066357: ldapvi: diff for NMU version 1.7-11

[Boyuan Yang]

Control: tags 1066357 + patch
Control: tags 1066357 + pending

Dear maintainer,

I've prepared an NMU for ldapvi (versioned as 1.7-11) and
uploaded it to DELAYED/0. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru ldapvi-1.7/debian/changelog ldapvi-1.7/debian/changelog
--- ldapvi-1.7/debian/changelog 2016-01-12 16:14:50.0 -0500
+++ ldapvi-1.7/debian/changelog 2024-04-26 11:15:30.0 -0400
@@ -1,3 +1,13 @@
+ldapvi (1.7-11) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Avoid using transitional package names.
+  * debian/control: Add missing dependency sensible-utils (lintian).
+  * debian/patches/07,08: Add patch to fix FTBFS caused by
+Werror=implicit-function-declaration. (Closes: #1066357)
+
+ -- Boyuan Yang   Fri, 26 Apr 2024 11:15:30 -0400
+
 ldapvi (1.7-10) unstable; urgency=medium
 
   * Update my name/email address.
diff -Nru ldapvi-1.7/debian/control ldapvi-1.7/debian/control
--- ldapvi-1.7/debian/control   2016-01-12 10:36:14.0 -0500
+++ ldapvi-1.7/debian/control   2024-04-26 11:15:15.0 -0400
@@ -2,13 +2,13 @@
 Section: text
 Priority: optional
 Maintainer: Rhonda D'Vine 
-Build-Depends: debhelper (>= 9~), libldap2-dev, libglib2.0-dev, libpopt-
dev, libncurses5-dev, libsasl2-dev, libreadline-dev, xsltproc
+Build-Depends: debhelper (>= 9~), libldap-dev, libglib2.0-dev, libpopt-
dev, libncurses-dev, libsasl2-dev, libreadline-dev, xsltproc
 Standards-Version: 3.9.6
 Homepage: http://www.lichteblau.com/ldapvi/
 
 Package: ldapvi
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, sensible-utils
 Description: perform an LDAP search and update results using a text
editor
  From a first glance ldapvi looks like ldapsearch: You search for
entries in
  the ldap database. But the results get opened in your preferred editor,
and
diff -Nru ldapvi-1.7/debian/patches/07_diff.c-Use-public-interface-
ldap_bv2dn-instead-of-ld.patch ldapvi-1.7/debian/patches/07_diff.c-Use-
public-interface-ldap_bv2dn-instead-of-ld.patch
--- ldapvi-1.7/debian/patches/07_diff.c-Use-public-interface-ldap_bv2dn-
instead-of-ld.patch 1969-12-31 19:00:00.0 -0500
+++ ldapvi-1.7/debian/patches/07_diff.c-Use-public-interface-ldap_bv2dn-
instead-of-ld.patch 2024-04-26 11:13:02.0 -0400
@@ -0,0 +1,28 @@
+From: Boyuan Yang 
+Date: Fri, 26 Apr 2024 10:41:33 -0400
+Subject: diff.c: Use public interface ldap_bv2dn instead of ldap_bv2dn_x
+
+The current openldap ldap_bv2dn_x() function is a private
implementation.
+The public interface ldap_bv2dn() share almost the same function
parameters
+except for the context. As a result, it is safe to use the public
interface
+as a replacement. This solves the FTBFS caused by
+-Werror=implicit-function-declaration.
+
+Bug-Debian: https://bugs.debian.org/1066357
+---
+ diff.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/diff.c b/diff.c
+index bb000fc..4596662 100644
+--- a/diff.c
 b/diff.c
+@@ -215,7 +215,7 @@ safe_str2dn(char *str, LDAPDN *out, int flags)
+ struct berval bv;
+ bv.bv_val = str;
+ bv.bv_len = strlen(str);
+-ldap_bv2dn_x(, out, flags);
++ldap_bv2dn(, out, flags);
+ }
+ #else
+ #error oops
diff -Nru ldapvi-1.7/debian/patches/08_ftbfs-implicit-function-
declaration.patch ldapvi-1.7/debian/patches/08_ftbfs-implicit-function-
declaration.patch
--- ldapvi-1.7/debian/patches/08_ftbfs-implicit-function-
declaration.patch   1969-12-31 19:00:00.0 -0500
+++ ldapvi-1.7/debian/patches/08_ftbfs-implicit-function-
declaration.patch   2024-04-26 11:15:30.0 -0400
@@ -0,0 +1,70 @@
+From: Boyuan Yang 
+Date: Fri, 26 Apr 2024 10:51:32 -0400
+Subject: Fix ftbfs implicit function declaration
+
+Also include common.h for error.c for definition of error.c. Needed
+for deprecated LDAP function of ldap_perror.
+
+Bug-Debian: https://bugs.debian.org/1066357
+---
+ common.h| 1 +
+ error.c | 3 +++
+ parse.c | 3 +++
+ parseldif.c | 2 ++
+ 4 files changed, 9 insertions(+)
+
+diff --git a/common.h b/common.h
+index f731e62..714b112 100644
+--- a/common.h
 b/common.h
+@@ -282,6 +282,7 @@ int adjoin_str(GPtrArray *, char *);
+ int adjoin_ptr(GPtrArray *, void *);
+ void init_dialog(tdialog *, enum dialog_mode, char *, char *);
+ void dialog(char *header, tdialog *, int, int);
++void fdcp(int fdsrc, int fddst);
+ 
+ /*
+  * schema.c
+diff --git a/error.c b/error.c
+index 5924868..345a2bf 100644
+--- a/error.c
 b/error.c
+@@ -14,6 +14,9 @@
+  * along with this program; if not, write to the Free Software
+  * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307
USA
+  */
++
++#include "common.h"
++
+ #include 
+ #include 
+ #include 
+diff --git a/parse.c b/parse.c
+index e171f53..0c6b0ec 100644
+--- a/parse.c
 b/parse.c
+@@ -16,7 +16,10 @@
+  * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307
USA
+  */
+ 

Bug#1069608: marked as done (topplot: missing test-depends on python3-all)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 15:05:23 +
with message-id 
and subject line Bug#1069608: fixed in topplot 0.2.2+repack-2
has caused the Debian Bug report #1069608,
regarding topplot: missing test-depends on python3-all
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

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

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


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


Adding python3-all to the Depends in debian/*tests*/control should fix 
this bug, but I have not actually tested this.
--- End Message ---
--- Begin Message ---
Source: topplot
Source-Version: 0.2.2+repack-2
Done: Colin Watson 

We believe that the bug you reported is fixed in the latest version of
topplot, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated topplot package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Apr 2024 15:08:01 +0100
Source: topplot
Architecture: source
Version: 0.2.2+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Colin Watson 
Closes: 1069608
Changes:
 topplot (0.2.2+repack-2) unstable; urgency=medium
 .
   * Team upload.
   * Add python3-all to autopkgtest Depends (closes: #1069608).
Checksums-Sha1:
 cdbe6d4f0279b6dad30b863bbfb71de70a17f9d7 2402 topplot_0.2.2+repack-2.dsc
 3d82f6b2eff6e1edea62939b8e4655bb1bcb00f4 3472 
topplot_0.2.2+repack-2.debian.tar.xz
Checksums-Sha256:
 103efd5cfaf1f3310beaae8ce60061303e1b50078a41043756d9d741af2dcf90 2402 
topplot_0.2.2+repack-2.dsc
 9833f2101df35241e326f912d61ab19fac29a81c0f5c45106ca9cc663ffe8975 3472 
topplot_0.2.2+repack-2.debian.tar.xz
Files:
 c7cd2265112964282d785f24b1382389 2402 utils optional topplot_0.2.2+repack-2.dsc
 732739539cf9a29b67753e6b9dda5c82 3472 utils optional 
topplot_0.2.2+repack-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrtY0ACgkQOTWH2X2G
UAumnBAAiY90VUC3I+Mmafxv7qFyaMTaFtW0dtR2FO/TfKKM4TC7cDqR73Qrln0o
g2OgzYTeFpK6X31nSGg59wic7vDAIF1knPxNiBrildMLFVgKaJpWxFc90KvD5+N/
KajTBq2WnemMBB7ZUuTxjNNKzDLeftGaZlNvLuS+G4xyaU02iLElFBVMRKx4MMvi
jfw7qgi7xiFRXXkVgPPnIlFDQcMQVhX9ww5fJNeJgkLADTxFM9nsjITIJkBrK2T4
bwYeobe2VUIEkEQbWEIspw/4zMuCuOJjyzrHnZ+PJeioWGSDXg0TIPYVVliS+RH9
gupMpgwmK+ETjHJ5YqFGe/ghuCjTgzNLSGjzZU8WKWo4jcDIJMMcMGFSFWpnpKiz
JMsEYAGpjlIBT0hoPIMNoPwrQ5pgY6vtsHif9tSfRuJ0GdaECJVCx/mV79/b0cGS
PByWnxucNLTlkEK5N7tk9DbZYQY8tmGY3Ig/lK0zInM4Qtj2Gqh8YvpoEfZZttBK
XIUFbP4FRczqYdIGdFBK5YlU7yeaag1h5KyRJBkk48rila3ZNrb900iNZLM8dTs+
jwOWYaclvXQq4hzjd+z9fgeVQH8CyncORgGm6g+K9IofQ3q6ehRh7BnJmRQjvbek
0ta+KIhdcxc8kq6eNRFXBGfHTnKCpJlBuaWmH45+cgKe++cR8zA=
=h6OC
-END PGP SIGNATURE-



pgpnQ1aOocLG3.pgp
Description: PGP signature
--- End Message ---

Bug#1069360: marked as done (python-cytoolz: FTBFS on arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 15:03:18 +
with message-id 
and subject line Bug#1069360: fixed in python-cytoolz 0.12.2-2
has caused the Debian Bug report #1069360,
regarding python-cytoolz: FTBFS on arm64: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cytoolz
Version: 0.12.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config 
> [1/5] Cythonizing cytoolz/dicttoolz.pyx
> [2/5] Cythonizing cytoolz/functoolz.pyx
> [3/5] Cythonizing cytoolz/itertoolz.pyx
> [4/5] Cythonizing cytoolz/recipes.pyx
> [5/5] Cythonizing cytoolz/utils.pyx
> running config
> I: pybuild base:311: python3.11 setup.py config 
> [1/5] Cythonizing cytoolz/utils.pyx
> [2/5] Cythonizing cytoolz/dicttoolz.pyx
> [3/5] Cythonizing cytoolz/functoolz.pyx
> [4/5] Cythonizing cytoolz/itertoolz.pyx
> [5/5] Cythonizing cytoolz/recipes.pyx
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3.12 setup.py build 
> [1/5] Cythonizing cytoolz/utils.pyx
> [2/5] Cythonizing cytoolz/dicttoolz.pyx
> [3/5] Cythonizing cytoolz/functoolz.pyx
> [4/5] Cythonizing cytoolz/itertoolz.pyx
> [5/5] Cythonizing cytoolz/recipes.pyx
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/_signatures.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/_version.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/compatibility.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> creating /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/curried
> copying cytoolz/curried/operator.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/curried
> copying cytoolz/curried/exceptions.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/curried
> copying cytoolz/curried/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/curried
> copying cytoolz/itertoolz.pyx -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/recipes.pyx -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/utils.pyx -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/dicttoolz.pyx -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/functoolz.pyx -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/itertoolz.pxd -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/cpython.pxd -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/__init__.pxd -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/dicttoolz.pxd -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/utils.pxd -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/functoolz.pxd -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> copying cytoolz/recipes.pxd -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz
> creating /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_functoolz.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_serialization.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_doctests.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_embedded_sigs.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_tlz.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_dev_skip_test.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_dicttoolz.py -> 
> /<>/.pybuild/cpython3_3.12_cytoolz/build/cytoolz/tests
> copying cytoolz/tests/test_none_safe.py -> 
> 

Bug#1067366: marked as done (mirrorbits: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_build] Error 25)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 15:01:29 +
with message-id 
and subject line Bug#1067366: fixed in mirrorbits 
0.5.1+git20240203.4e34d9b+ds1-2
has caused the Debian Bug report #1067366,
regarding mirrorbits: FTBFS: make[1]: *** [debian/rules:22: 
override_dh_auto_build] Error 25
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mirrorbits
Version: 0.5.1+git20240203.4e34d9b+ds1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- -buildmode=pie -ldflags '-X 
> github.com/etix/mirrorbits/core.VERSION=v0.5.1+git20240203.4e34d9b+ds1 -X 
> github.com/etix/mirrorbits/core.BUILD=0.5.1+git20240203.4e34d9b+ds1-1 -X 
> github.com/etix/mirrorbits/config.TEMPLATES_PATH=/usr/share/mirrorbits/templates/'
>   cd _build && go install -trimpath -v -p 8 -buildmode=pie -ldflags "-X 
> github.com/etix/mirrorbits/core.VERSION=v0.5.1+git20240203.4e34d9b+ds1 -X 
> github.com/etix/mirrorbits/core.BUILD=0.5.1+git20240203.4e34d9b+ds1-1 -X 
> github.com/etix/mirrorbits/config.TEMPLATES_PATH=/usr/share/mirrorbits/templates/"
>  github.com/etix/mirrorbits github.com/etix/mirrorbits/cli 
> github.com/etix/mirrorbits/config github.com/etix/mirrorbits/core 
> github.com/etix/mirrorbits/daemon github.com/etix/mirrorbits/database 
> github.com/etix/mirrorbits/database/interfaces 
> github.com/etix/mirrorbits/database/upgrader 
> github.com/etix/mirrorbits/database/v1 github.com/etix/mirrorbits/filesystem 
> github.com/etix/mirrorbits/http github.com/etix/mirrorbits/logs 
> github.com/etix/mirrorbits/mirrors github.com/etix/mirrorbits/network 
> github.com/etix/mirrorbits/process github.com/etix/mirrorbits/rpc 
> github.com/etix/mirrorbits/scan github.com/etix/mirrorbits/testing 
> github.com/etix/mirrorbits/utils
> internal/goexperiment
> internal/coverage/rtcov
> internal/unsafeheader
> internal/godebugs
> internal/goos
> internal/cpu
> internal/goarch
> internal/itoa
> runtime/internal/atomic
> runtime/internal/syscall
> math/bits
> unicode/utf8
> internal/race
> internal/abi
> internal/chacha8rand
> runtime/internal/math
> runtime/internal/sys
> sync/atomic
> unicode
> cmp
> encoding
> crypto/internal/alias
> slices
> crypto/subtle
> internal/bytealg
> math
> crypto/internal/boring/sig
> log/internal
> internal/nettrace
> container/list
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/alias
> google.golang.org/grpc/serviceconfig
> runtime
> internal/reflectlite
> sync
> internal/testlog
> google.golang.org/grpc/internal/buffer
> google.golang.org/grpc/internal/grpcsync
> internal/bisect
> internal/singleflight
> runtime/cgo
> errors
> internal/godebug
> sort
> strconv
> path
> io
> internal/oserror
> internal/safefilepath
> vendor/golang.org/x/net/dns/dnsmessage
> internal/intern
> syscall
> math/rand
> crypto/internal/nistec/fiat
> bytes
> strings
> hash
> reflect
> crypto
> net/netip
> crypto/internal/randutil
> bufio
> regexp/syntax
> crypto/rc4
> hash/crc32
> vendor/golang.org/x/text/transform
> net/http/internal/ascii
> html
> text/tabwriter
> google.golang.org/grpc/encoding
> golang.org/x/text/transform
> time
> internal/syscall/execenv
> internal/syscall/unix
> regexp
> internal/fmtsort
> encoding/binary
> google.golang.org/grpc/backoff
> google.golang.org/grpc/internal/grpcrand
> context
> io/fs
> internal/poll
> google.golang.org/grpc/keepalive
> google.golang.org/grpc/internal/backoff
> golang.org/x/net/context
> google.golang.org/grpc/tap
> embed
> crypto/md5
> crypto/cipher
> crypto/internal/edwards25519/field
> encoding/base64
> vendor/golang.org/x/crypto/internal/poly1305
> crypto/internal/nistec
> os
> crypto/internal/edwards25519
> golang.org/x/sys/unix
> crypto/internal/boring
> crypto/des
> encoding/pem
> crypto/sha1
> crypto/sha256
> crypto/aes
> crypto/sha512
> crypto/hmac
> vendor/golang.org/x/crypto/chacha20
> vendor/golang.org/x/crypto/hkdf
> crypto/ecdh
> fmt
> path/filepath
> io/ioutil
> net
> vendor/golang.org/x/sys/cpu
> google.golang.org/grpc/internal/envconfig
> os/signal
> vendor/golang.org/x/crypto/chacha20poly1305
> os/exec
> encoding/hex
> log
> flag
> encoding/json
> gopkg.in/yaml.v3
> math/big
> net/url
> github.com/pkg/errors
> github.com/etix/mirrorbits/core
> 

Processed: Bug#1069608 marked as pending in topplot

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1069608 [src:topplot] topplot: missing test-depends on python3-all
Added tag(s) pending.

-- 
1069608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069608: marked as pending in topplot

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1069608 in topplot reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/topplot/-/commit/3b37e8bd6872c31e18cac5f8fd54039ca9919942


Add python3-all to autopkgtest Depends

Closes: #1069608


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069608

Processed: retitle 1069367 to qemu: FTBFS: arch:all packages can only be built on amd64 ..., tagging 1069367

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1069367 qemu: FTBFS: arch:all packages can only be built on amd64
Bug #1069367 [src:qemu] qemu: FTBFS on arm64: build-dependency not installable: 
gcc-powerpc64-linux-gnu
Changed Bug title to 'qemu: FTBFS: arch:all packages can only be built on 
amd64' from 'qemu: FTBFS on arm64: build-dependency not installable: 
gcc-powerpc64-linux-gnu'.
> severity 1069367 wishlist
Bug #1069367 [src:qemu] qemu: FTBFS: arch:all packages can only be built on 
amd64
Severity set to 'wishlist' from 'serious'
> tags 1069367 + wontfix - moreinfo sid trixie
Bug #1069367 [src:qemu] qemu: FTBFS: arch:all packages can only be built on 
amd64
Added tag(s) wontfix.
Bug #1069367 [src:qemu] qemu: FTBFS: arch:all packages can only be built on 
amd64
Removed tag(s) trixie, moreinfo, and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069815: marked as done (wesnoth-1.8-server: new package installs systemd unit in aliased location)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 13:57:54 +
with message-id 
and subject line Bug#1069815: fixed in wesnoth-1.18 1:1.18.0-2
has caused the Debian Bug report #1069815,
regarding wesnoth-1.8-server: new package installs systemd unit in aliased 
location
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wesnoth-1.18-server
Version: 1:1.17.26-1
Severity: serious
Justification: do not introduce aliased files into Debian

Hi,

I noticed that wesnoth-1.18-server is a new package and installs a file
below /lib, which is an aliased location that we try to empty to
complete the /usr-move transition via DEP17. I am filing this bug at
RC-severity to stop it from migrating to trixie and hope you agree with
this. Please downgrade if you disagree though note that this kind of
issue will become an RC-bug for all packages later in the trixie cycle.

The simplest fix to this problem is changing

SYSTEMD_SERVICE = 
debian/wesnoth-$(BRANCH_VERSION)-server/lib/systemd/system/wesnoth-$(BRANCH_VERSION)-server.service

in debian/rules and move the file to /usr/lib. This is mostly safe for
backports, except that bookworm's debhelper will fail to generate
necessary maintainer scripts. Please bump your debhelper dependency to
13.11.6 (available in bookworm-backports).

Alternatively, adding dh-sequence-movetousr to Build-Depends should also
resolve the matter, but for a new package I'd prefer to fix this right
from the start.

Both solutions are likely applicable to other wesnoth versions as well,
though we don't consider those RC-bugs yet.

Helmut
--- End Message ---
--- Begin Message ---
Source: wesnoth-1.18
Source-Version: 1:1.18.0-2
Done: Vincent Cheng 

We believe that the bug you reported is fixed in the latest version of
wesnoth-1.18, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Cheng  (supplier of updated wesnoth-1.18 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Apr 2024 06:07:52 -0700
Source: wesnoth-1.18
Built-For-Profiles: noudeb
Architecture: source
Version: 1:1.18.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Vincent Cheng 
Closes: 1069815
Changes:
 wesnoth-1.18 (1:1.18.0-2) unstable; urgency=medium
 .
   * Install systemd unit file in UsrMerge-allowed location. (Closes: #1069815)
 - Declare build-dep on debhelper (>= 13.11.6~).
Checksums-Sha1:
 d7373f7bff0ff3cd8e5e1881c2202b71b439ab03 4333 wesnoth-1.18_1.18.0-2.dsc
 3219fa87680fc6b77e553ddee6e78766e7891943 179812 
wesnoth-1.18_1.18.0-2.debian.tar.xz
Checksums-Sha256:
 0d1688a326a09b611c39779e20bad7fec0f0306603e768272515a5fd22db7d68 4333 
wesnoth-1.18_1.18.0-2.dsc
 a433444dc008c18f9e8a6104fe243d764c79309678ebef8cb846d9a71bf0c0f4 179812 
wesnoth-1.18_1.18.0-2.debian.tar.xz
Files:
 e090205140738c026e374b7513308e7e 4333 games optional wesnoth-1.18_1.18.0-2.dsc
 9b2d390259ad51de5834e2fd82e14e32 179812 games optional 
wesnoth-1.18_1.18.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE1TqBWjy3ZZr4guOVju3MG6ofMv8FAmYrqwoACgkQju3MG6of
Mv8d2Q//VCB812zD+EcTVz/dCEZV5kRpQofg+r2g08CxkLuNXu/K8Wt0qwdySPJc
4a2SlGTQxKn6T/HcXZ4y7rR5JeadPpUAGFN2gCo98CnoGFtwfOLL5LyJuzUaihwX
KkCPJlMuS+BTJ8XfcAOP1SsAvLGfM2XT9X0L0eEz3SqKwUEgWTdimaETz6tX5k+a
Xdt+ihGSiGErbH+w3DdfwykYMWfU62iuoGfLyRrDPaUF9DlNyealGfPJSHQSYiYT
fWVFmtyMSwIHXFZ/xc6D9ANOY3Uj8Iqqz7Xz6HVqtOLYMqhSA9Qm45OSkeQ2hOzv
CpZhY8n3GgaD3D2rRbEKdMwSpkqlPHfjg4iksJcKFV3HlQIQ2HPSwPwaPXFjcPDK
6Q6sqLQZnD8VzlWTbtPyracSjL60G9IbENq+KL5gZyCrU9ZgsDtLJQNcXT1u9fXr
p4izRD1QMknmI2l5pQ17oMaEVdvYSrKS1ZIEP7PnvBMGYJDAC7Y+/xwGmySXaC89
AAfiP+A02IUQmDy7tDyv0mN8s7Lv49JQqxAhPW/0f1p9FTTAATk6eblZH4fbkm8H
pREZ5yUGLeau/B407m7YsrDon+CRN3PM3IHffgGDP16SScfhBFDk+XUaHv8k+bBH
qgWOc4T8y/9s5IUAmktZSxKOBeKzDnkQiQOmPrNtL9LbuqixFoM=
=NiDI
-END PGP SIGNATURE-



pgpKkRh1t7Ftm.pgp
Description: PGP signature
--- End Message ---

Processed: Re: testing: MISSING ARCHS on debian mirrors: amd64 arm64 i386 mips64el ppc64el riscv64 s390x

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:gnutls28 3.8.3-1
Bug #1069882 [libgnutls30] testing: MISSING ARCHS on debian mirrors: amd64 
arm64 i386 mips64el ppc64el riscv64 s390x
Bug reassigned from package 'libgnutls30' to 'src:gnutls28'.
No longer marked as found in versions gnutls28/3.8.3-1.
Ignoring request to alter fixed versions of bug #1069882 to the same values 
previously set
Bug #1069882 [src:gnutls28] testing: MISSING ARCHS on debian mirrors: amd64 
arm64 i386 mips64el ppc64el riscv64 s390x
Marked as found in versions gnutls28/3.8.3-1.
> severity -1 normal
Bug #1069882 [src:gnutls28] testing: MISSING ARCHS on debian mirrors: amd64 
arm64 i386 mips64el ppc64el riscv64 s390x
Severity set to 'normal' from 'critical'
> tag -1 moreinfo
Bug #1069882 [src:gnutls28] testing: MISSING ARCHS on debian mirrors: amd64 
arm64 i386 mips64el ppc64el riscv64 s390x
Added tag(s) moreinfo.

-- 
1069882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1069360 marked as pending in python-cytoolz

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1069360 [src:python-cytoolz] python-cytoolz: FTBFS on arm64: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Added tag(s) pending.

-- 
1069360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069360: marked as pending in python-cytoolz

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1069360 in python-cytoolz reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-cytoolz/-/commit/3f462fede0bcd4468c9dd27b6b9f23c033fb611b


Fix test failure on Python 3.11.9/3.12.3/main

Closes: #1069360


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069360

Bug#1069882: testing: MISSING ARCHS on debian mirrors: amd64 arm64 i386 mips64el ppc64el riscv64 s390x

[Andreas Beckmann]

Control: reassign -1 src:gnutls28 3.8.3-1
Control: severity -1 normal
Control: tag -1 moreinfo

On Fri, 26 Apr 2024 12:41:45 +0200 Dirk Lehmann  wrote:

Package: libgnutls30
Version: 3.8.3-1



since yesterday the .deb files for the architectures
  * amd64 arm64 i386 mips64el ppc64el riscv64 s390x
on the Debian Apt mirrors are not listed/available anymore:


since they have been superseded by libgnutls30t64 for the 64-bit time_t 
transition.


In a minimal up-to-date testing chroot:

# apt-get install exim4-daemon-light
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  cron cron-daemon-common dmsetup exim4-base exim4-config libapparmor1 
libargon2-1 libcryptsetup12 libdevmapper1.02.1 libevent-2.1-7t64 
libfdisk1 libgnutls-dane0t64 libidn12 libjson-c5 libkmod2 
libsystemd-shared libunbound8 netbase systemd systemd-dev

Suggested packages:
  anacron logrotate checksecurity supercat bat exim4-doc-html | 
exim4-doc-info eximon4 file mail-reader spf-tools-perl swaks 
dns-root-data systemd-container systemd-homed systemd-userdbd 
systemd-boot systemd-resolved libfido2-1 libip4tc2 libqrencode4
  libtss2-esys-3.0.2-0 libtss2-mu-4.0.1-0 libtss2-rc0 
libtss2-tcti-device0 polkitd

Recommended packages:
  bsd-mailx | mailx psmisc default-dbus-system-bus | dbus-system-bus 
systemd-timesyncd | time-daemon

The following NEW packages will be installed:
  cron cron-daemon-common dmsetup exim4-base exim4-config 
exim4-daemon-light libapparmor1 libargon2-1 libcryptsetup12 
libdevmapper1.02.1 libevent-2.1-7t64 libfdisk1 libgnutls-dane0t64 
libidn12 libjson-c5 libkmod2 libsystemd-shared libunbound8 netbase

  systemd systemd-dev
0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
Need to get 86.0 kB/9704 kB of archives.
After this operation, 27.8 MB of additional disk space will be used.
Do you want to continue? [Y/n]

which looks fine, therefore downgrading the severity.

The t64 transition has started migrating packages to testing
 a few days ago, so maybe you experienced the failure at an unfortunate 
moment.


Andreas

Bug#1057463: marked as pending in supertuxkart

[Reiner Herrmann]

Hi Vincent,

On Fri, Apr 26, 2024 at 06:03:51AM -0700, Vincent Cheng wrote:
> Hi Reiner,
> 
> On Sat, Jan 6, 2024 at 1:03 PM Reiner Herrmann  
> wrote:
> > 
> > Use system shaderc instead of embedded copy
> >
> > Closes: #1057463, #1031387
> > 
> 
> Just wanted to sanity check before uploading, is it ok for me to
> upload what's currently in salsa to close out #1057463 (and #995771),
> or are there other blockers / were you waiting on something else?
> Either way, thanks for fixing these bugs in supertuxkart!

at the time when I fixed it, there were still some strange linking
errors. But I just did another test build and it was successful.
The reason is probably the new version of shaderc (which mentions
linking fixes in the changelog).
So I don't see any blocker, please upload it. Thanks!

Kind regards,
  Reiner

Bug#1069195: librust-prost-build-dev: FTBFS

[Peter Green]

Unsatisfiable build-dependency on librust-heck-0.5+default-dev



There seems to be an error here. the version of librust-prost-dev in sid
(build-)depends on librust-heck-0.4+default-dev.

The version in experimental does depend on librust-heck-0.5+default-dev
as it's first choice, but that's fine because version 0.5 of rust-heck
is available in experimental.

Bug#1069817: marked as done (Autopkgtests fail)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 13:12:20 +
with message-id 
and subject line Bug#1069817: fixed in python-exceptiongroup 1.2.1-1
has caused the Debian Bug report #1069817,
regarding Autopkgtests fail
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-exceptiongroup
Version: 1.2.0-1
Severity: serious

https://ci.debian.net/packages/p/python-exceptiongroup/unstable/amd64/45886580/

 47s === FAILURES
===
 47s ___ DeepRecursionInSplitAndSubgroup.test_deep_split

 47s tests/test_exceptions.py:375: in test_deep_split
 47s with self.assertRaises(RecursionError):
 47s E   AssertionError: RecursionError not raised
 47s __ DeepRecursionInSplitAndSubgroup.test_deep_subgroup
__
 47s tests/test_exceptions.py:380: in test_deep_subgroup
 47s with self.assertRaises(RecursionError):
 47s E   AssertionError: RecursionError not raised


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 python3-exceptiongroup depends on:
ii  python3  3.11.8-1

python3-exceptiongroup recommends no packages.

python3-exceptiongroup suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: python-exceptiongroup
Source-Version: 1.2.1-1
Done: Colin Watson 

We believe that the bug you reported is fixed in the latest version of
python-exceptiongroup, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated python-exceptiongroup 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Apr 2024 13:42:11 +0100
Source: python-exceptiongroup
Architecture: source
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Colin Watson 
Closes: 1069817
Changes:
 python-exceptiongroup (1.2.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release:
 - Fix test failure on Python 3.12.3 (closes: #1069817).
Checksums-Sha1:
 5152d02cfc98caef06db8e6a7a9fbb17fb938f4f 2220 python-exceptiongroup_1.2.1-1.dsc
 6a82af27b1b1b0b4a2159d7f91f852543a04573f 28203 
python-exceptiongroup_1.2.1.orig.tar.gz
 10fb12a032882f81a4356368cf1a17f909590717 3856 
python-exceptiongroup_1.2.1-1.debian.tar.xz
 2cb8b006a87eb4306f830999c44ea2cbfa3d6e0a 6970 
python-exceptiongroup_1.2.1-1_source.buildinfo
Checksums-Sha256:
 bcbce2a4d0078a7edf7d7114f73ee773786887e68642de52e7588221a43af4db 2220 
python-exceptiongroup_1.2.1-1.dsc
 b59b2c0cee4423a01ca6dba773efac4dd6390e3908e36ed222d683ce827c8f3b 28203 
python-exceptiongroup_1.2.1.orig.tar.gz
 682be05f009cb8bf4031e616beab4eb6c21ff06bab4beb9187ed406a8fc02f03 3856 
python-exceptiongroup_1.2.1-1.debian.tar.xz
 c0aeda428a06f398b5d01cae9a979745024fed4a0d2626c7e6e25accedde68da 6970 
python-exceptiongroup_1.2.1-1_source.buildinfo
Files:
 9723f3bda1dff420cf016405235d7dd7 2220 python optional 
python-exceptiongroup_1.2.1-1.dsc
 7c9f0f77ee6cbe4c5cb33662b4d59889 28203 python optional 
python-exceptiongroup_1.2.1.orig.tar.gz
 0744e3d73104ca225f480cbf07b00d89 3856 python optional 
python-exceptiongroup_1.2.1-1.debian.tar.xz
 4c74c0cd636cef63185335778d2cb69f 6970 python optional 
python-exceptiongroup_1.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrohoACgkQOTWH2X2G

Bug#1057463: marked as pending in supertuxkart

[Vincent Cheng]

Hi Reiner,

On Sat, Jan 6, 2024 at 1:03 PM Reiner Herrmann  wrote:
>
> Control: tag -1 pending
>
> Hello,
>
> Bug #1057463 in supertuxkart reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
>
> https://salsa.debian.org/games-team/supertuxkart/-/commit/68a3bec7900d9921cb7f0428123db0eda945742a
>
> 
> Use system shaderc instead of embedded copy
>
> Closes: #1057463, #1031387
> 
>
> (this message was generated automatically)
> --
> Greetings
>
> https://bugs.debian.org/1057463

Just wanted to sanity check before uploading, is it ok for me to
upload what's currently in salsa to close out #1057463 (and #995771),
or are there other blockers / were you waiting on something else?
Either way, thanks for fixing these bugs in supertuxkart!

Regards,
Vincent

Bug#1069816: marked as done (Autopkgtests fail)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 12:52:07 +
with message-id 
and subject line Bug#1069816: fixed in python-argcomplete 3.3.0-1
has caused the Debian Bug report #1069816,
regarding Autopkgtests fail
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-argcomplete
Version: 3.1.4-1
Severity: serious

https://ci.debian.net/packages/p/python-argcomplete/unstable/amd64/45886560/

102s ==
102s ERROR: test_repl_parse_after_complete
(__main__.TestArgcompleteREPL.test_repl_parse_after_complete)
102s --
102s Traceback (most recent call last):
102s   File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 925, in
test_repl_parse_after_complete
102s args = p.parse_args(["--foo", "spam", "bar"])
102s^^
102s   File "/usr/lib/python3.12/argparse.py", line 1908, in parse_args
102s args, argv = self.parse_known_args(args, namespace)
102s  ^^
102s   File "/usr/lib/python3.12/argparse.py", line 1941, in parse_known_args
102s namespace, args = self._parse_known_args(args, namespace)
102s   ^^^
102s   File "/usr/lib/python3/dist-packages/argcomplete/packages/_argparse.py",
line 299, in _parse_known_args
102s start_index = consume_optional(start_index)
102s   ^
102s   File "/usr/lib/python3/dist-packages/argcomplete/packages/_argparse.py",
line 165, in consume_optional
102s action, option_string, explicit_arg = option_tuple
102s ^^^
102s ValueError: too many values to unpack (expected 3)
102s
102s ==
102s FAIL: test_choices (__main__.TestArgcomplete.test_choices)
102s --
102s Traceback (most recent call last):
102s   File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 170, in test_choices
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '-h'
102s '--help'
102s '--ship'
102s Items in the second set but not the first:
102s 'speedboat'
102s 'submarine'
102s
102s ==
102s FAIL: test_completers (__main__.TestArgcomplete.test_completers)
102s --
102s Traceback (most recent call last):
102s   File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 291, in
test_completers
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '--url'
102s '--email'
102s '-h'
102s '--help'
102s Items in the second set but not the first:
102s 'http://url1'
102s 'http://url2'
102s
102s ==
102s FAIL: test_default_completer
(__main__.TestArgcomplete.test_default_completer)
102s --
102s Traceback (most recent call last):
102s   File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 415, in
test_default_completer
102s self.assertEqual(set(self.run_completer(make_parser(), cmd)),
set(output))
102s AssertionError: Items in the first set but not the second:
102s '--one'
102s '--many'
102s Items in the second set but not the first:
102s 'test/'
102s
102s ==
102s FAIL: test_escape_special_chars
(__main__.TestArgcomplete.test_escape_special_chars)
102s --
102s Traceback (most recent call last):
102s   File "/tmp/autopkgtest-
lxc.q4aft1il/downtmp/autopkgtest_tmp/test/test.py", line 823, in
test_escape_special_chars
102s self.assertEqual(set(self.run_completer(make_parser(), "prog -1 ")),
{r"bar\<\$\>baz "})
102s AssertionError: Items in the first set but not the second:
102s '-1'
102s '-2'
102s '-3'
102s Items in the second set but not the first:
102s 'bar\\<\\$\\>baz '
102s
102s 

Bug#1060134: kmod-udeb vs busybox-udeb: agree on who ships depmod

[Cyril Brulebois]

Marco d'Itri  (2024-04-26):
> On Apr 26, Michael Tokarev  wrote:
> 
> > So, should I disable module utils in busybox-udeb now?
> I think so.

I haven't gotten any requests / seen any reasons to keep it; so, yes,
please feel free to remove it whenever is convenient for you.

> > Is kmod udeb ready and used in d-i already, or does it need some
> > prep first?
> AFAIK it works.

Absolutely, that's been working since the small xz-utils tweak (the udeb
addition, not the backdoor thing).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1069888: node-bunyan: FTBFS: failing tests

[Santiago Vila]

Package: src:node-bunyan
Version: 2.0.5+~cs4.4.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link node_modules/exeunt -> ../exeunt
Link node_modules/mv -> ../mv
Link node_modules/safe-json-stringify -> ../safejsonstringify
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/bunyan
/bin/sh -ex debian/tests/pkg-js/test
+ tap -R tap -J --no-cov test/add-stream.test.js test/buffer.test.js 
test/child-behaviour.test.js test/cli-client-req.test.js test/cli-res.test.js 
test/cli.test.js test/ctor.test.js test/cycles.test.js test/error-event.test.js 
test/level.test.js test/log.test.js test/other-api.test.js 
test/process-exit.test.js test/raw-stream.test.js test/ringbuffer.test.js 
test/safe-json-stringify.test.js test/serializers.test.js test/src.test.js 
test/stream-levels.test.js
TAP version 13
# Subtest: test/add-stream.test.js
# Subtest: non-writables passed as stream
ok 1 - "stream" stream is not writable
ok 2 - "stream" stream is not writable
1..2
ok 1 - non-writables passed as stream # time=18.713ms

# Subtest: proper stream

ok 1 - expect truthy value
1..1
ok 2 - proper stream # time=4.908ms

1..2

# time=46.964ms
ok 1 - test/add-stream.test.js # time=46.964ms

# Subtest: test/buffer.test.js
# Subtest: log.info(BUFFER)
ok 1 - log.trace msg is inspect(BUFFER)
ok 2 - no "0" array index key in record: undefined
ok 3 - no "parent" array index key in record: undefined
ok 4 - log.trace(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 5 - log.debug msg is inspect(BUFFER)
ok 6 - no "0" array index key in record: undefined
ok 7 - no "parent" array index key in record: undefined
ok 8 - log.debug(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 9 - log.info msg is inspect(BUFFER)
ok 10 - no "0" array index key in record: undefined
ok 11 - no "parent" array index key in record: undefined
ok 12 - log.info(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 13 - log.warn msg is inspect(BUFFER)
ok 14 - no "0" array index key in record: undefined
ok 15 - no "parent" array index key in record: undefined
ok 16 - log.warn(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 17 - log.error msg is inspect(BUFFER)
ok 18 - no "0" array index key in record: undefined
ok 19 - no "parent" array index key in record: undefined
ok 20 - log.error(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
ok 21 - log.fatal msg is inspect(BUFFER)
ok 22 - no "0" array index key in record: undefined
ok 23 - no "parent" array index key in record: undefined
ok 24 - log.fatal(BUFFER, "bar") msg is inspect(BUFFER) + " bar"
1..24
ok 1 - log.info(BUFFER) # time=15.595ms

1..1

# time=36.998ms
ok 2 - test/buffer.test.js # time=36.998ms

# Subtest: test/child-behaviour.test.js
# Subtest: child can add stream
ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
1..4
ok 1 - child can add stream # time=8.798ms

# Subtest: child can set level of inherited streams

ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
1..3
ok 2 - child can set level of inherited streams # time=2.496ms

# Subtest: child can set level of inherited streams and add streams

ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
ok 5 - should be equal
ok 6 - should be equal
1..6
ok 3 - child can set level of inherited streams and add streams # 
time=5.594ms

# Subtest: child should not lose parent "hostname"

ok 1 - should be equal
ok 2 - should be equal
ok 3 - should be equal
ok 4 - should be equal
1..4
ok 4 - child should not lose parent "hostname" # time=1.888ms

1..4

# time=43.011ms
ok 3 - test/child-behaviour.test.js # time=43.011ms

(node:558561) DeprecationWarning: ifError() is deprecated, use error() instead
(Use `node --trace-deprecation ...` to show where the warning was created)
# Subtest: test/cli-client-req.test.js
# Subtest: client_req extra newlines, client_res={} (pull \#252)
ok 1 - should not error
ok 2 - should be equal

Bug#1067316: marked as done (gnucash-docs: FTBFS: Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: cannot open sha

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 12:35:18 +
with message-id 
and subject line Bug#1067316: fixed in gnucash-docs 5.6-1
has caused the Debian Bug report #1067316,
regarding gnucash-docs: FTBFS: Exception in thread "main" 
java.lang.UnsatisfiedLinkError: 
/usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: 
cannot open shared object file: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnucash-docs
Version: 5.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/build'
> [  0%] Generating gnucash-guide.fo
> cd /<>/build/zh/guide && /usr/bin/cmake -E make_directory 
> /<>/build/share/doc//zh
> cd /<>/build/zh/guide && /usr/bin/xsltproc --path 
> /<>/docbook --xinclude --nonet -o 
> /<>/build/zh/guide/gnucash-guide.fo --stringparam 
> fop1.extensions 1 --stringparam variablelist.as.blocks 1 --stringparam 
> glosslist.as.blocks 1 /<>/zh/guide/../xsl/zh-fo.xsl 
> /<>/zh/guide/index.docbook
> Making portrait pages on USletter paper (8.5inx11in)
> [  3%] Generating ../../share/doc/zh/gnucash-guide.pdf
> cd /<>/build/zh/guide && /usr/bin/fop -l zh -c 
> /<>/build/zh/guide/fop.xconf -fo 
> /<>/build/zh/guide/gnucash-guide.fo -pdf 
> /<>/build/share/doc//zh/gnucash-guide.pdf
> [warning] /usr/bin/fop: JVM flavor 'sun' not understood
> [warning] /usr/bin/fop: Unable to locate serializer in /usr/share/java
> [warning] /usr/bin/fop: Unable to locate xalan2 in /usr/share/java
> [warning] /usr/bin/fop: Unable to locate xercesImpl in /usr/share/java
> [WARN] FOUserAgent - Font "Symbol,normal,700" not found. Substituting with 
> "Symbol,normal,400".
> [WARN] FOUserAgent - Font "ZapfDingbats,normal,700" not found. Substituting 
> with "ZapfDingbats,normal,400".
> [WARN] FOUserAgent - Hyphenation pattern not found. URI: zh.
> [INFO] FOUserAgent - Rendered page #1.
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 14384 millipoints. (See position 
> 18:448)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 15080 millipoints. (See position 
> 28:235)
> [INFO] TTFFile - This is a TrueType collection file with 4 fonts
> [INFO] TTFFile - Containing the following fonts: 
> [INFO] TTFFile - AR PL UKai CN <-- selected
> [INFO] TTFFile - AR PL UKai HK
> [INFO] TTFFile - AR PL UKai TW
> [INFO] TTFFile - AR PL UKai TW MBE
> [INFO] FOUserAgent - Rendered page #2.
> [INFO] FOUserAgent - Rendered page #3.
> [INFO] FOUserAgent - Rendered page #4.
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 98:462)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 100:237)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 102:237)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 104:299)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 105:241)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 106:241)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 107:303)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 108:237)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 109:237)
> [WARN] FOUserAgent - The contents of fo:block line 1 exceed the available 
> area in the inline-progression direction by 2000 millipoints. (See position 
> 

Processed: Bug#1067316 marked as pending in gnucash-docs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067316 [src:gnucash-docs] gnucash-docs: FTBFS: Exception in thread "main" 
java.lang.UnsatisfiedLinkError: 
/usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: 
cannot open shared object file: No such file or directory
Added tag(s) pending.

-- 
1067316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069818: marked as done (FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 12:05:31 +
with message-id 
and subject line Bug#1069818: fixed in toolz 0.12.1-1
has caused the Debian Bug report #1069818,
regarding FTBFS: tests failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: toolz
Version: 0.12.0-2
Severity: serious
Tags: ftbfs

=== FAILURES
===
 test_inspect_wrapped_property
_

def test_inspect_wrapped_property():
class Wrapped(object):
def __init__(self, func):
self.func = func

def __call__(self, *args, **kwargs):
return self.func(*args, **kwargs)

@property
def __wrapped__(self):
return self.func

func = lambda x: x
wrapped = Wrapped(func)
assert inspect.signature(func) == inspect.signature(wrapped)

>   assert num_required_args(Wrapped) is None
E   AssertionError: assert 1 is None
E+  where 1 = num_required_args(.Wrapped'>)

toolz/tests/test_inspect_args.py:485: AssertionError


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: toolz
Source-Version: 0.12.1-1
Done: Colin Watson 

We believe that the bug you reported is fixed in the latest version of
toolz, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated toolz package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Apr 2024 12:47:29 +0100
Source: toolz
Architecture: source
Version: 0.12.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Colin Watson 
Closes: 1069818
Changes:
 toolz (0.12.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release:
 - Minimal maintenance to support Python 3.12.
   * Fix test failure on Python 3.11.9/3.12.3/main (closes: #1069818).
Checksums-Sha1:
 157cef3c60b2e193053cdf5d8f13d87b710ed967 2234 toolz_0.12.1-1.dsc
 63a52090028bf5c16f7087f5ccaeb3fdea0014d9 94974 toolz_0.12.1.orig.tar.gz
 eb85426482979be65373159a663b84de16dbfb62 4500 toolz_0.12.1-1.debian.tar.xz
Checksums-Sha256:
 f2e979a9834380b9b6a84f933c29ce2e4830f69de49894a8cd04552bd63c6f99 2234 
toolz_0.12.1-1.dsc
 c2207d17a773209c50ae4038f2523ce9435b2fc43c5a8d69a0d96dd1967426c0 94974 
toolz_0.12.1.orig.tar.gz
 2e2e43535db1ce630adc3f2a0c0ad258e323aed288640507515a830102efadfc 4500 
toolz_0.12.1-1.debian.tar.xz
Files:
 ad9c5d7732b8c83fa39bac5512f2eadf 2234 python optional toolz_0.12.1-1.dsc
 79dff938a0cb1cac59c2f67591d0c86a 94974 python optional toolz_0.12.1.orig.tar.gz
 c83402c5a142b85c831dadcc3c4ef579 4500 python optional 
toolz_0.12.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYrlQYACgkQOTWH2X2G
UAuB9hAAsgAr+F7oT0r6XEEJ0yn3awOfG9GczvZy50iDMMn26KAtGNkAN2zM+UWL
jihekL9I9NmZagmqAVdaz4q+jmKapnehRRfGri/U6xxgrp9hDlyQR07Kdqgfk7M9
nAPjAZAjzh5acjP1UI/L2tUI2BsLVI3kou9NvtVd125WSfCXlPHmbxQsbwJdNhta
jyjSBcsXPuJ2VmSQhNYdz3eT/Kf3LPmfsAmVwf9vyIgQAQuNE8eDqo7gYNUS1VCB
4Ovgjyk5se1WyC39ye7AprUlQO0QMfW4JSuLiXYjUo/PEqLV7ywy2pQl8OeLb2NP
XObL/1B2OQQ6nSgQOL9rqbiJNtkmD0Qz9BvWiAtBSXfUdmzPK/xY4ALTmvE8Yg5r
47PXmZAoB6vK/g+8v4nCTW9VYsHpillJNCCUhzMPFDNlHVthM9z0W9H4W12LbJEg
0ybwESkLjVRgDIDfvqh8dsbm81b7/Vd8Yb0OffXBTVVz6kQxCrF7MnHQyo7/HczB

Bug#1067316: marked as pending in gnucash-docs

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #1067316 in gnucash-docs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/gnucash-docs/-/commit/a6789346f3c0833e0de782c38098e92c51ab20d5


Build-Depends += "libharfbuzz-dev" (Closes: #1067316).

This is indirect dependency that is weakly expressed in OpenJDK's 
libfontmanager.

Thanks, Vincent Lefevre.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067316

Processed: Re: Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1069835 [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB 
shares
Severity set to 'important' from 'grave'

-- 
1069835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069818: marked as pending in toolz

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1069818 in toolz reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/toolz/-/commit/59155505e05c393226e55cad4e0e5de690df3d07


Fix test failure on Python 3.11.9/3.12.3/main

Closes: #1069818


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069818

Processed: Bug#1069818 marked as pending in toolz

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1069818 [src:toolz] FTBFS: tests failed
Added tag(s) pending.

-- 
1069818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: antlr4-maven-plugin: please provide debian-versioned maven coordinates

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1065660 [antlr4-maven-plugin] antlr4-maven-plugin: please provide 
debian-versioned maven coordinates
Severity set to 'important' from 'serious'
> tags -1 - ftbfs
Bug #1065660 [antlr4-maven-plugin] antlr4-maven-plugin: please provide 
debian-versioned maven coordinates
Removed tag(s) ftbfs.

-- 
1065660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065660: antlr4-maven-plugin: please provide debian-versioned maven coordinates

[Andrius Merkys]

Control: severity -1 important
Control: tags -1 - ftbfs

Hi,

On 2024-04-25 19:12, Santiago Vila wrote:

I noticed that chemicaltagger currently FTBFS and I believe it is because
of this problem, so to avoid duplicate reports, I'm raising this one to 
serious.


A build log for chemicaltagger is available here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/chemicaltagger.html


I have just fixed the FTBFS bug in chemicaltagger/1.6.2-4, it was a 
separate issue, unrelated to antlr4-maven-plugin.


Best,
Andrius

Bug#1069882: testing: MISSING ARCHS on debian mirrors: amd64 arm64 i386 mips64el ppc64el riscv64 s390x

[Dirk Lehmann]

Package: libgnutls30
Version: 3.8.3-1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

since yesterday the .deb files for the architectures

  * amd64 arm64 i386 mips64el ppc64el riscv64 s390x

on the Debian Apt mirrors are not listed/available anymore:

  * MISSING:  testing   libgnutls30   3.8.3-1
  * MISSING:  testing   libgnutls-dane0   3.8.3-1

At yesterday I guess that's an security issue and will be available
via `testing-security` in some hours.  But currently it seems not be
resolved.

The CRITICAL IMPACT of this issue is that `exim4-daemon-light` is
depending on `libgnutls-dane0`.  And `reportbug` is depending on
`exim4`.  Since exim4 is the default MTA in Debian it is currently not
possible to report bugs anymore in testing, as I am currently doing!

Please fix fast.  Maybe possible to just "held back" libgnutls30 and
libgnutls-dane0?

Best regards,
Dirk =)


-- 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/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.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 libgnutls30 depends on:
ii  libc6  2.37-18
ii  libgmp10   2:6.3.0+dfsg-2+b1
ii  libhogweed63.9.1-2+b1
ii  libidn2-0  2.3.7-2
ii  libnettle8 3.9.1-2+b1
ii  libp11-kit00.25.3-4
ii  libtasn1-6 4.19.0-3+b2
ii  libunistring5  1.2-1

libgnutls30 recommends no packages.

Versions of packages libgnutls30 suggests:
pn  gnutls-bin  

-- no debconf information

Bug#1069064: marked as done (util-linux-extra: insufficient Replaces for util-linux due to /usr-move)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 10:44:03 +
with message-id 
and subject line Bug#1069064: fixed in util-linux 2.40-7
has caused the Debian Bug report #1069064,
regarding util-linux-extra: insufficient Replaces for util-linux due to 
/usr-move
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-linux-extra
Version: 2.40-6
Severity: serious
User: helm...@debian.org
Usertags: dep17p1
Control: affects -1 + util-linux

Hi Chris,

I think I mentioned this on IRC already and you intended to revert, but
nothing happened, so lets turn this into a bug for tracking purposes at
least.

util-linux-extra gained the utils ctrlaltdel, fsck.cramfs, fsck.minix,
mkfs.bfs, mkfs.cramfs, and mkfs.minix. In util-linux-extra, these now
reside below /usr/sbin while they used to reside in /sbin in util-linux
in bookworm and earlier. Hence upgrading from bookworm to sid can cause
these files to be lost.

I think we have three ways to address this:

 1. Revert the move and retry after trixie. I think you favoured this?
 2. Upgrade Breaks to Conflicts and issue a temporary protective
diversion from u-l-e.preinst to u-l-e.postinst. In theory, apt can
first unpack u-l, then unpack u-l-e and then configure both, so
there is a safe solution. However, there is a risk that apt could
decide to temporarily remove u-l and that would be really bad.
 3. Keep Breaks and issue temporary diversions to be removed in forky's
u-l-e.postinst.

Please let me know your choice and I can do a patch.

Helmut
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.40-7
Done: Chris Hofstaedtler 

We believe that the bug you reported is fixed in the latest version of
util-linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated util-linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 26 Apr 2024 11:41:02 +0200
Source: util-linux
Architecture: source
Version: 2.40-7
Distribution: unstable
Urgency: medium
Maintainer: util-linux packagers 
Changed-By: Chris Hofstaedtler 
Closes: 1069064 1069634
Changes:
 util-linux (2.40-7) unstable; urgency=medium
 .
   [ Chris Hofstaedtler ]
   * Import upstream stable/v2.40 up to a8aa0b5f154a44557f5bae5a4027bdbfe42b0323
 * lsns: fix netns use
 * libmount: fix comment typo for mnt_fs_get_comment()
 * libmount: Fix access check for utab in context
 * lsblk: simplify SOURCES code
 * findmnt: always zero-terminate SOURCES data
 * agetty: Don't override TERM passed by the user
 * libsmartcols: reset wrap after calculation
 * lslocks: remove a unused local variable
 * lslocks: don't abort gathering per-process information even if
   opening a /proc/[0-9]* fails
 * lsns: tolerate lsns_ioctl(fd, NS_GET_{PARENT,USERNS}) failing with ENOSYS
 * lsns: report with warnx if a namespace related ioctl fails with ENOSYS
 * Fix misplaced else in mnt_update_already_done
 * findmnt: revise the code for -I and -D option (Closes: #1069634)
 * libblkid: topology/ioctl: simplify ioctl handling
 * libblkid: topology/ioctl: correctly handle kernel types
 * pam_lastlog2: link against liblastlog
 * libblkid: Fix segfault when blkid.conf doesn't exist (Closes: #1069634)
 .
   [ Helmut Grohne ]
   * Fix /usr-move mitigation (Closes: #1069064).
 Thanks!
Checksums-Sha1:
 033ee23eb0abc00aa70357509d8acecc55aac653 4643 util-linux_2.40-7.dsc
 732696cfce190b5f507a9c26cc8a0db919153e1c 08 util-linux_2.40-7.debian.tar.xz
 b709e3e2a6f447e08ba8804bdb41999d8ce4f799 19579 
util-linux_2.40-7_arm64.buildinfo
Checksums-Sha256:
 c1a8aac385de4e93e2f71ec641652bdf89ff2c898e9cc7799eaf5076c2078220 4643 
util-linux_2.40-7.dsc
 fe7a854ac6659c5a668d4afad5e72ab87d3aeb0f0c313b3c07b8087294215291 08 
util-linux_2.40-7.debian.tar.xz
 90bd27ee0991db95b358726e96f215c143d19d8f70175298648fc4248afb2b54 19579 

Bug#1064715: marked as done (zabbix: FTBFS: make[4]: *** [Makefile:623: zabbix.com/cmd/zabbix_agent2] Error 1)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 10:45:13 +
with message-id 
and subject line Bug#1064715: fixed in zabbix 1:6.0.29+dfsg-1
has caused the Debian Bug report #1064715,
regarding zabbix: FTBFS: make[4]: *** [Makefile:623: 
zabbix.com/cmd/zabbix_agent2] Error 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zabbix
Version: 1:6.0.25+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/debian/tmp-build-AGENT2/src/go'
> CGO_CFLAGS="-I/usr/include  " CGO_LDFLAGS="-L/usr/lib -Wl,--start-group   
> 
> /<>/debian/tmp-build-AGENT2/src/zabbix_agent/logfiles/libzbxlogfiles.a
>  
> /<>/debian/tmp-build-AGENT2/src/libs/zbxcomms/libzbxcomms.a  
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxcommon/libzbxcommon.a
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxcrypto/libzbxcrypto.a
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxsys/libzbxsys.a  
>   /<>/debian/tmp-build-AGENT2/src/libs/zbxprof/libzbxprof.a  
> /<>/debian/tmp-build-AGENT2/src/libs/zbxnix/libzbxnix.a  
>   /<>/debian/tmp-build-AGENT2/src/libs/zbxconf/libzbxconf.a  
> 
> /<>/debian/tmp-build-AGENT2/src/libs/zbxhttp/libzbxhttp.a
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxcompress/libzbxcompress.a
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxregexp/libzbxregexp.a
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/libzbxagent2sysinfo.a
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/common/libcommonsysinfo.a
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/simple/libsimplesysinfo.a
>   
> /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/linux/libspechostnamesysinfo.a
>  
> /<>/debian/tmp-build-AGENT2/src/libs/zbxsysinfo/linux/libspecsysinfo.a
>  
> /<>/debian/tmp-build-AGENT2/src/libs/zbxexec/libzbxexec.a
>   /<>/debian/tmp-build-AGENT2/src/libs/zbxalgo/libzbxalgo.a  
> /<>/debian/tmp-build-AGENT2/src/libs/zbxjson/libzbxjson.a
>   -lm   -lmodbus  -lpcre2-8-lz -lpthread -lssl -lcrypto 
> -Wl,--end-group" go build -v -tags="pcre2" -ldflags="-X 
> 'zabbix.com/pkg/version.compileDate=`date +"%b %_d %Y"`' -X 
> zabbix.com/pkg/version.compileTime=`date +%H:%M:%S` -X 
> zabbix.com/pkg/version.compileOs=`go env GOOS` -X 
> zabbix.com/pkg/version.compileArch=`go env GOARCH` -X 
> main.confDefault=/etc/zabbix/zabbix_agent2.conf -X 
> main.applicationName=zabbix_agent2" -o bin zabbix.com/cmd/zabbix_agent2
> go build -v -ldflags="-X 'zabbix.com/pkg/version.compileDate=`date +"%b %_d 
> %Y"`' -X zabbix.com/pkg/version.compileTime=`date +%H:%M:%S` -X 
> zabbix.com/pkg/version.compileOs=`go env GOOS` -X 
> zabbix.com/pkg/version.compileArch=`go env GOARCH` -X 
> main.applicationName=zabbix_web_service" -o bin 
> zabbix.com/cmd/zabbix_web_service
> internal/goarch
> internal/coverage/rtcov
> internal/godebugs
> internal/goexperiment
> internal/unsafeheader
> internal/goos
> runtime/internal/atomic
> runtime/internal/syscall
> internal/abi
> internal/cpu
> runtime/internal/math
> runtime/internal/sys
> internal/race
> sync/atomic
> internal/itoa
> unicode/utf8
> container/list
> unicode
> runtime/internal/syscall
> encoding
> math/bits
> unicode/utf8
> runtime/internal/atomic
> sync/atomic
> math/bits
> crypto/internal/alias
> unicode
> internal/abi
> internal/cpu
> crypto/subtle
> internal/bytealg
> crypto/internal/boring/sig
> log/internal
> internal/nettrace
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> unicode/utf16
> internal/nettrace
> crypto/subtle
> crypto/internal/boring/sig
> vendor/golang.org/x/crypto/internal/alias
> github.com/chromedp/chromedp/device
> math
> github.com/gobwas/pool/internal/pmath
> golang.org/x/net/internal/iana
> golang.org/x/net/html/atom
> golang.org/x/text/encoding/internal/identifier
> golang.org/x/text/internal/utf8internal
> golang.org/x/xerrors/internal
> internal/bytealg
> math
> runtime
> runtime
> sync
> internal/reflectlite
> internal/reflectlite
> sync
> internal/singleflight
> internal/bisect
> zabbix.com/internal/monitor
> internal/testlog
> internal/bisect
> internal/singleflight
> github.com/josharian/intern
> 

Processed: Re: reassign 1067188 to src:gcc-mingw-w64, found 1067188 in 25.2, fixed 1067188 in 26.1, affects 1067188

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1067188
Bug #1067188 [src:gcc-mingw-w64] gdb-mingw-w64: FTBFS in trixie
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1067188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069064: marked as pending in util-linux

[Chris Hofstaedtler]

Control: tag -1 pending

Hello,

Bug #1069064 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/util-linux/-/commit/e7b4b439820d215cc81e1b37d1950216378a2289


Fix /usr-move mitigation

Closes: #1069064


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069064

Processed: Bug#1069064 marked as pending in util-linux

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1069064 [util-linux-extra] util-linux-extra: insufficient Replaces for 
util-linux due to /usr-move
Added tag(s) pending.

-- 
1069064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bullseye-pu: package cpu/1.4.3-14~deb11u1

[Debian Bug Tracking System]

Processing control commands:

> block 1067439 with -1
Bug #1067439 {Done: Andreas Beckmann } [cpu] cpu: undefined 
symbol globalLdap in libcpu_ldap.so on Debian 12
1067439 was not blocked by any bugs.
1067439 was not blocking any bugs.
Added blocking bug(s) of 1067439: 1069880
> affects -1 + src:cpu
Bug #1069880 [release.debian.org] bullseye-pu: package cpu/1.4.3-14~deb11u1
Added indication that 1069880 affects src:cpu

-- 
1067439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067439
1069880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1060134

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1060134 + pending
Bug #1060134 [kmod-udeb,busybox-udeb] kmod-udeb vs busybox-udeb: agree on who 
ships depmod
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1060134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1060134: kmod-udeb vs busybox-udeb: agree on who ships depmod

[Michael Tokarev]

Ok,

I'm removing whole modutils from busybox udeb (besides depmod, this is
lsmod, insmod, rmmod, and modprobe).  All these are provided by
kmod-udeb as far as I can see (as symlinks to kod).

--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 
ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 
8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

Bug#1060134: kmod-udeb vs busybox-udeb: agree on who ships depmod

[Marco d'Itri]

On Apr 26, Michael Tokarev  wrote:

> So, should I disable module utils in busybox-udeb now?
I think so.

> Is kmod udeb ready and used in d-i already, or does it need some
> prep first?
AFAIK it works.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1068490: marked as done (netperf: Netserver remove /dev/null in some cases, breaking many things)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 09:24:46 +
with message-id 
and subject line Bug#1068490: fixed in netperf 2.7.0-0.3
has caused the Debian Bug report #1068490,
regarding netperf: Netserver remove /dev/null in some cases, breaking many 
things
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netperf
Version: 2.7.0-0.2
Severity: critical
Tags: patch upstream
Justification: breaks unrelated software
X-Debbugs-Cc: tourrilhes@gmail.com

This bug is hard to reproduce, as the condition that lead to
Netserver deleting /dev/null are quite mysterious. I was getting my
/dev/null removed over the years at very rare occurences, until
I managed to track it down to Netserver.

The issue is not present in the tarball for version 2.7.0. It
was introduced in patch :
02018-02-07T17:21:57-08:00~5380b1f.patch
In particular, this line :
+FileName = NETPERF_NULL;
This patch is part of the Netperf GitHub, which is why I added
the upstream tag.
I will report this bug upstream, unfortunately I don't expect
much action :-(

A quick look at the source code show that the code is wrong in
very obvious way. The fix is quite simple and obvious, and I provide
a patch (included below).
Note that my patch replace
11_no_change_perms_on_dev-null.patch, so please remove that patch
before applying mine.
Thanks in advance !

Jean


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

Kernel: Linux 5.10.0-28-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages netperf depends on:
ii  libc6  2.31-13+deb11u8

netperf recommends no packages.

netperf suggests no packages.

-- no debconf information

diff --git a/src/netserver.c b/src/netserver.c
index 2e6b567..ae4ad61 100644
--- a/src/netserver.c
+++ b/src/netserver.c
@@ -220,7 +220,7 @@ unlink_empty_debug_file() {
 #if !defined(WIN32)
   struct stat buf;
 
-  if (stat(FileName,)== 0) {
+  if ( (! suppress_debug) && (stat(FileName,)== 0) ) {
 
 if (buf.st_size == 0)
   unlink(FileName);
@@ -239,6 +239,7 @@ open_debug_file()
   if (where != NULL) fflush(where);
   if (suppress_debug) {
 strncpy(FileName, NETPERF_NULL, sizeof(FileName));
+FileName[sizeof(FileName) - 1] = '\0';
 where = fopen(FileName, "w");
   } else {
 int fd;
@@ -260,7 +261,8 @@ open_debug_file()
 
 #if !defined(WIN32)
 
-  chmod(FileName,0644);
+  if (! suppress_debug)
+chmod(FileName,0644);
 
   /* redirect stdin to "/dev/null" */
   rd_null_fp = fopen(NETPERF_NULL,"r");
diff --git a/src/netserver.c b/src/netserver.c
index 2e6b567..ae4ad61 100644
--- a/src/netserver.c
+++ b/src/netserver.c
@@ -220,7 +220,7 @@ unlink_empty_debug_file() {
 #if !defined(WIN32)
   struct stat buf;
 
-  if (stat(FileName,)== 0) {
+  if ( (! suppress_debug) && (stat(FileName,)== 0) ) {
 
 if (buf.st_size == 0)
   unlink(FileName);
@@ -239,6 +239,7 @@ open_debug_file()
   if (where != NULL) fflush(where);
   if (suppress_debug) {
 strncpy(FileName, NETPERF_NULL, sizeof(FileName));
+FileName[sizeof(FileName) - 1] = '\0';
 where = fopen(FileName, "w");
   } else {
 int fd;
@@ -260,7 +261,8 @@ open_debug_file()
 
 #if !defined(WIN32)
 
-  chmod(FileName,0644);
+  if (! suppress_debug)
+chmod(FileName,0644);
 
   /* redirect stdin to "/dev/null" */
   rd_null_fp = fopen(NETPERF_NULL,"r");
diff --git a/src/netserver.c b/src/netserver.c
index 2e6b567..ae4ad61 100644
--- a/src/netserver.c
+++ b/src/netserver.c
@@ -220,7 +220,7 @@ unlink_empty_debug_file() {
 #if !defined(WIN32)
   struct stat buf;
 
-  if (stat(FileName,)== 0) {
+  if ( (! suppress_debug) && (stat(FileName,)== 0) ) {
 
 if (buf.st_size == 0)
   unlink(FileName);
@@ -239,6 +239,7 @@ open_debug_file()
   if (where != NULL) fflush(where);
   if (suppress_debug) {
 strncpy(FileName, NETPERF_NULL, sizeof(FileName));
+FileName[sizeof(FileName) - 1] = '\0';
 where = fopen(FileName, "w");
   } else {
 int fd;
@@ -260,7 

Bug#1069876: libsbml: autopkgtest regression

[Andreas Tille]

Hi,

Am Fri, Apr 26, 2024 at 09:27:55AM +0200 schrieb Sebastian Ramacher:
>  95s autopkgtest [21:29:51]: test autodep8-python3: [---
>  95s Testing with python3.12:

Short note:  If I understood upstream correctly they currently support
Python3.11 only.  In any case they support only *one* Python3 version at
the same time.  It might be sensible to reach out to upstream for an
update but that's currently out of my scope.

Kind regards
   Andreas.

-- 
https://fam-tille.de

Bug#1068936: marked as done (libcanberra-gtk3-module: hard-coded dependency on libgtk-3-0)

[Debian Bug Tracking System]

Your message dated Fri, 26 Apr 2024 09:10:11 +
with message-id 
and subject line Bug#1068936: fixed in libcanberra 0.30-13
has caused the Debian Bug report #1068936,
regarding libcanberra-gtk3-module: hard-coded dependency on libgtk-3-0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcanberra-gtk3-module
Version: 0.30-12
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

This package has a hard-coded dependency on libgtk-3-0. Since libgtk-3-0
was renamed for the time_t transition, the dependency needs to be
updated or simply removed. Even oldstable has a recent enough version of
GTK 3.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libcanberra
Source-Version: 0.30-13
Done: Michael Biebl 

We believe that the bug you reported is fixed in the latest version of
libcanberra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated libcanberra package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 25 Apr 2024 21:18:44 +0200
Source: libcanberra
Binary: gnome-session-canberra gnome-session-canberra-dbgsym libcanberra-dev 
libcanberra-doc libcanberra-gstreamer libcanberra-gstreamer-dbgsym 
libcanberra-gtk-common-dev libcanberra-gtk3-0 libcanberra-gtk3-0-dbgsym 
libcanberra-gtk3-dev libcanberra-gtk3-module libcanberra-gtk3-module-dbgsym 
libcanberra-pulse libcanberra-pulse-dbgsym libcanberra0 libcanberra0-dbgsym
Architecture: source amd64 all
Version: 0.30-13
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 gnome-session-canberra - GNOME session log in and log out sound events
 libcanberra-dev - simple interface for playing event sounds (development files)
 libcanberra-doc - simple abstract interface for playing event sounds - doc
 libcanberra-gstreamer - GStreamer backend for libcanberra
 libcanberra-gtk-common-dev - simple interface for playing event sounds (GTK+ 
shared developmen
 libcanberra-gtk3-0 - GTK+ 3.0 helper for playing widget event sounds with 
libcanberra
 libcanberra-gtk3-dev - simple interface for playing event sounds (GTK+ 3 
development fil
 libcanberra-gtk3-module - translates GTK3 widgets signals to event sounds
 libcanberra-pulse - PulseAudio backend for libcanberra
 libcanberra0 - simple abstract interface for playing event sounds
Closes: 1065454 1068936
Changes:
 libcanberra (0.30-13) unstable; urgency=medium
 .
   * Team upload
   * Revert time_t related changes.
 Those changes appear to not be necessary. time_t is not exposed in the
 API/ABI and a-c-c did not detect any issues.
 This reverts commit 04a6b5de59db6a0832b1d31f287bf7afa76e11c3.
 (Closes: #1065454)
   * Drop hard-coded dependency on libgtk-3-0 (>= 3.2.2-3) (Closes: #1068936)
   * Add versioned Provides for libcanberra0t64 and libcanberra-gtk3-0t64.
 This simplifies compatibility with Ubuntu 24.04.
 Thanks to Jeremy Bicha
   * Bump Standards-Version to 4.7.0
Checksums-Sha1:
 21fecf599971d299f4a7f867ec4561ec625d2f30 2970 libcanberra_0.30-13.dsc
 b6402d7337f7d3e25cf45e33a3c151f03494fe09 14616 
libcanberra_0.30-13.debian.tar.xz
 96ecc3d5a904a034bec77fd9d21a2f524147e63a 8252 
gnome-session-canberra-dbgsym_0.30-13_amd64.deb
 b897e4438c8936f88c6aa6d6d947c4a190b609ab 8208 
gnome-session-canberra_0.30-13_amd64.deb
 6f55851ca1808350e227e99dcd4d555fa5e4bc27 8488 libcanberra-dev_0.30-13_amd64.deb
 9bcbac09b1cf8ae7f7af897316c2c26b86bb83aa 21056 libcanberra-doc_0.30-13_all.deb
 64ff7efe2ded964d2a6287c2e88a3730b5cfaa64 24956 
libcanberra-gstreamer-dbgsym_0.30-13_amd64.deb
 b888a11e306fb4a546241722911eab5b1d569907 9696 
libcanberra-gstreamer_0.30-13_amd64.deb
 302a4ef5b4cb203386cddfdb78cdb6e69599513d 4388 
libcanberra-gtk-common-dev_0.30-13_all.deb
 f0f7b1304a288dd65b96d4607b444ab7c3544086 20508 
libcanberra-gtk3-0-dbgsym_0.30-13_amd64.deb
 6b175e1635fb1711b5d8953e42cd6b8cd56d4b38 9456