Processed: reassign 1058265 to src:sqlalchemy, affects 1058265

[Debian Bug Tracking System]

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

> reassign 1058265 src:sqlalchemy
Bug #1058265 [src:python-flask-marshmallow] python-flask-marshmallow: FTBFS: 
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 
3.11" returned exit code 13
Bug reassigned from package 'src:python-flask-marshmallow' to 'src:sqlalchemy'.
No longer marked as found in versions python-flask-marshmallow/0.15.0-3.
Ignoring request to alter fixed versions of bug #1058265 to the same values 
previously set
> affects 1058265 src:python-flask-marshmallow
Bug #1058265 [src:sqlalchemy] python-flask-marshmallow: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Added indication that 1058265 affects src:python-flask-marshmallow
> thanks
Stopping processing here.

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

Bug#1058301: resampy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Antonio Valentino]

On Tue, 12 Dec 2023 09:24:48 +0100 Lucas Nussbaum  wrote:

Source: resampy
Version: 0.4.2+ds-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):
> make[1]: Entering directory '/<>'
> dh_auto_test
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_resampy/build; 
python3.12 -m pytest ""
> = test session starts 
==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> configfile: setup.cfg
> plugins: cov-4.1.0
> collected 0 items / 3 errors
> 
>  ERRORS 

> ___ ERROR collecting .pybuild/cpython3_3.12_resampy/build/tests/test_core.py 
___
> ImportError while importing test module 
'/<>/.pybuild/cpython3_3.12_resampy/build/tests/test_core.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3/dist-packages/numba/core/typeconv/typeconv.py:4: in 
> from numba.core.typeconv import _typeconv
> E   ImportError: cannot import name '_typeconv' from 'numba.core.typeconv' 
(/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)
> 
> During handling of the above exception, another exception occurred:

> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_core.py:8: in 
> import resampy
> resampy/__init__.py:7: in 
> from .core import *
> resampy/core.py:7: in 
> import numba
> /usr/lib/python3/dist-packages/numba/__init__.py:73: in 
> from numba.misc.special import (
> /usr/lib/python3/dist-packages/numba/misc/special.py:3: in 
> from numba.core.typing.typeof import typeof
> /usr/lib/python3/dist-packages/numba/core/typing/__init__.py:1: in 
> from .context import BaseContext, Context
> /usr/lib/python3/dist-packages/numba/core/typing/context.py:11: in 
> from numba.core.typeconv import Conversion, rules
> /usr/lib/python3/dist-packages/numba/core/typeconv/rules.py:2: in 
> from .typeconv import TypeManager, TypeCastingRules
> /usr/lib/python3/dist-packages/numba/core/typeconv/typeconv.py:16: in 
> raise ImportError(msg)
> E   ImportError: Numba could not be imported.
> E   

> E   If you are seeing this message and are undertaking Numba development 
work, you may need to rebuild Numba.
> E   Please see the development set up guide:
> E   


The issue seems to be related to the fact that the numba package still 
do not support python 12.


See also #1057461 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057461)



cheers
--
Antonio Valentino

Processed: reassign #1058301

[Debian Bug Tracking System]

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

> reassign 1058301 src:numba
Bug #1058301 [src:resampy] resampy: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Bug reassigned from package 'src:resampy' to 'src:numba'.
No longer marked as found in versions resampy/0.4.2+ds-3.
Ignoring request to alter fixed versions of bug #1058301 to the same values 
previously set
> found 1058301 numba/0.57.1+dfsg-1
Bug #1058301 [src:numba] resampy: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Marked as found in versions numba/0.57.1+dfsg-1.
> affects 1058301 + src:resampy
Bug #1058301 [src:numba] resampy: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added indication that 1058301 affects src:resampy
> thanks
Stopping processing here.

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

Bug#1058148: marked as done (bleachbit: FTBFS: ImportError: cannot import name 'SafeConfigParser' from 'configparser' (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfigParser'?)

[Debian Bug Tracking System]

Your message dated Sat, 16 Dec 2023 04:49:05 +
with message-id 
and subject line Bug#1058148: fixed in bleachbit 4.6.0-1
has caused the Debian Bug report #1058148,
regarding bleachbit: FTBFS: ImportError: cannot import name 'SafeConfigParser' 
from 'configparser' (/usr/lib/python3.12/configparser.py). Did you mean: 
'RawConfigParser'?
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.)


-- 
1058148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bleachbit
Version: 4.4.2-2
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):
> make[1]: Entering directory '/<>'
> find po -name "*.mo" -delete
> dh_auto_clean
> I: pybuild base:310: python3.12 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 45, in 
> import bleachbit
>   File "/<>/bleachbit/__init__.py", line 33, in 
> from configparser import RawConfigParser, NoOptionError, SafeConfigParser
> ImportError: cannot import name 'SafeConfigParser' from 'configparser' 
> (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
> python3.12 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
> returned exit code 13
> make[1]: *** [debian/rules:10: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/bleachbit_4.4.2-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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: bleachbit
Source-Version: 4.6.0-1
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
bleachbit, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated bleachbit 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, 15 Dec 2023 23:11:35 -0500
Source: bleachbit
Architecture: source
Version: 4.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team ,
Changed-By: Boyuan Yang 
Closes: 1050264 1058148
Changes:
 bleachbit (4.6.0-1) unstable; urgency=medium
 .
   * New upstream release.
 + Fix compatibility with python3.11. (Closes: #1058148)
   * Update uploaders list. (Closes: #1050264)
   * debian/: Apply "wrap-and-sort -abst".
Checksums-Sha1:
 90eca58776fac205d0b58b061de0a2c6dbf5cc44 2028 bleachbit_4.6.0-1.dsc
 b653dcecdc2a13f9655bf2414c86a053960d8c4b 1369857 bleachbit_4.6.0.orig.tar.gz
 0ea4400efdeac4d9c98b3d33452c5d1642c9e35f 10348 bleachbit_4.6.0-1.debian.tar.xz
 99ea7a64edf7b67fee8dae0b44a5a4d2ff53a49c 6800 bleachbit_4.6.0-1_amd64.buildinfo
Checksums-Sha256:
 1aa28feada7edaac9569e046f0307bfa05fcb3822ebaedbf27034712e9cabcab 2028 
bleachbit_4.6.0-1.dsc
 b6e1d0157d672f7cdadde79fd687572b587a5febbf9a4c8eb5732338cf16fbc3 1369857 
bleachbit_4.6.0.orig.tar.gz
 9f70172465164ee0f0cab1b78df690a4c99c48e7f252ec0c664de1f3ab025f3d 10348 
bleachbit_4.6.0-1.debian.tar.xz
 ded8f38fcfd78b15adf3fe810966211b624091a3f7a6e336d6df2bc9c8c887c0 6800 
bleachbit_4.6.0-1_amd64.buildinfo
Files:
 d2e4baaf508c86cf7143575fcc91087d 2028 admin optional bleachbit_4.6.0-1.dsc
 6c09a3633f1d6a496a1f4165d5c0ed57 

Bug#1058336: visidata: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Anja]

Hello! Thanks for letting us know.

>  > self = , k = '_parts'
>
> def __getattr__(self, k):
> if hasattr(self.__dict__, k):
> r = getattr(self.__dict__, k)
> else:
> if self.__dict__.get('_path', None) is not None:
> >   r = getattr(self._path, k)
> E   AttributeError: 'PosixPath' object has no attribute
'_parts'. Did you mean: 'parts'?

Someone let us know much earlier on the repo, and we published a patch with
the fix: https://github.com/saulpw/visidata/issues/1934. We did not ship
that patch to Debian, since there was a planned major release very soon.

We are planning to release v3.0 in 2-4 weeks, and then that version will
then get packaged for Debian.

On Tue, 12 Dec 2023 at 01:18, Lucas Nussbaum  wrote:

> Source: visidata
> Version: 2.11-1
> 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):
> >  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
> >   pybuild --configure -i python{version} -p "3.12 3.11"
> > I: pybuild base:310: python3.12 setup.py config
> > running config
> > I: pybuild base:310: python3.11 setup.py config
> > running config
> >dh_auto_build -O--buildsystem=pybuild
> >   pybuild --build -i python{version} -p "3.12 3.11"
> > I: pybuild base:310: /usr/bin/python3.12 setup.py build
> > running build
> > running build_py
> > file visidata.py (for module visidata) not found
> > creating /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/fill.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/customdate.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/choose.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/utils.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/slide.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/shell.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/transpose.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/__init__.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/textsheet.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/path.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/macos.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/freqtbl.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/search.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/aggregators.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/metasheets.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/bezier.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/unfurl.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/help.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/_types.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/canvas.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/sheets.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/main.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/movement.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/menu.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/canvas_text.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/pyobj.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/form.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/selection.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/keys.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/macros.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/modify.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/memory.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/clipboard.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/color.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/regex.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > copying visidata/__main__.py ->
> /<>/.pybuild/cpython3_3.12_visidata/build/visidata
> > 

Bug#1052309: marked as done (lirc FTBFS when systemd.pc changes systemdsystemunitdir)

[Debian Bug Tracking System]

Your message dated Sat, 16 Dec 2023 01:04:40 +
with message-id 
and subject line Bug#1052309: fixed in lirc 0.10.1-7.3
has caused the Debian Bug report #1052309,
regarding lirc FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lirc
Version: 0.10.1-7.2
Severity: normal
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

systemd wants to change the value of systemdsystemunitdir in systemd.pc
to point to user. The lirc upstream code consumes this value to
determine the placement of systemd units. Unfortunately, the packaging
hard codes the current value, so when systemd changes it, lirc will
FTBFS. I'm attaching a patch to fix that.

Helmut
diff -Nru lirc-0.10.1/debian/changelog lirc-0.10.1/debian/changelog
--- lirc-0.10.1/debian/changelog2022-12-28 12:25:42.0 +0100
+++ lirc-0.10.1/debian/changelog2023-09-20 10:40:12.0 +0200
@@ -1,3 +1,11 @@
+lirc (0.10.1-7.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemdsystemunitdir changes in systemd.pc. (Closes: #-1)
+  * Also fix build vs host confusion.
+
+ -- Helmut Grohne   Wed, 20 Sep 2023 10:40:12 +0200
+
 lirc (0.10.1-7.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru lirc-0.10.1/debian/install lirc-0.10.1/debian/install
--- lirc-0.10.1/debian/install  2022-12-28 12:25:42.0 +0100
+++ lirc-0.10.1/debian/install  2023-09-20 10:40:12.0 +0200
@@ -1,7 +1,7 @@
 #! /usr/bin/dh-exec
 
 etc/lirc
-[linux-any] lib/systemd/*
+[linux-any] ${systemdsystemunitdir}
 [linux-any] usr/lib/tmpfiles.d/*
 [linux-any] usr/bin/lirc-make-devinput
 [linux-any] usr/bin/irpipe
diff -Nru lirc-0.10.1/debian/rules lirc-0.10.1/debian/rules
--- lirc-0.10.1/debian/rules2022-12-28 12:25:42.0 +0100
+++ lirc-0.10.1/debian/rules2023-09-20 10:40:12.0 +0200
@@ -5,6 +5,8 @@
 export DEB_BUILD_MAINT_OPTIONS  = hardening=+all
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
+export systemdsystemunitdir=$(shell pkg-config --variable=systemdsystemunitdir 
systemd | sed s,^/,,)
+
 %:
dh $@ --with python3
 
@@ -20,7 +22,7 @@
 
 override_dh_auto_configure: debian/lirc.preinst
 override_dh_auto_configure:
-ifeq ($(DEB_BUILD_ARCH_OS), linux)
+ifeq ($(DEB_HOST_ARCH_OS), linux)
dh_auto_configure -- \
SH_PATH=/bin/sh \
MODINFO=/sbin/modinfo \
@@ -44,7 +46,7 @@
find debian/tmp -name *.la -delete
rm -f debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/api-docs
chmod 755 debian/tmp/usr/share/lirc/python-pkg/lirc/lirctool
-ifeq ($(DEB_BUILD_ARCH_OS), linux)
+ifeq ($(DEB_HOST_ARCH_OS), linux)
mkdir -p debian/tmp/usr/lib/tmpfiles.d
echo "d /run/lirc  0755  root  root  10d" \
> debian/tmp/usr/lib/tmpfiles.d/lirc.conf
@@ -67,7 +69,7 @@
 endif
 
 override_dh_installsystemd:
-ifeq ($(DEB_BUILD_ARCH_OS), linux)
+ifeq ($(DEB_HOST_ARCH_OS), linux)
dh_installsystemd -p lirc lircd.socket
dh_installsystemd -p lirc --no-enable --no-start lircd.service
dh_installsystemd -p lirc --no-enable --no-start irexec.service
--- End Message ---
--- Begin Message ---
Source: lirc
Source-Version: 0.10.1-7.3
Done: Vagrant Cascadian 

We believe that the bug you reported is fixed in the latest version of
lirc, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated lirc 
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: Tue, 05 Dec 2023 15:52:45 -0800
Source: lirc
Architecture: source
Version: 0.10.1-7.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team 
Changed-By: Vagrant Cascadian 
Closes: 979019 979023 979024 988907 989304 1052309
Changes:
 lirc (0.10.1-7.3) unstable; urgency=medium
 .
   [ Vagrant Cascadian ]
   * Non-maintainer upload.
   * tools: Do not embed build date and kernel version in 

Bug#1058556: marked as done (binutils-or1k-elf: FTBFS: make[1]: *** [debian/rules:29: src] Error 1)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 23:04:32 +
with message-id 
and subject line Bug#1058556: fixed in binutils-or1k-elf 1.0.10
has caused the Debian Bug report #1058556,
regarding binutils-or1k-elf: FTBFS: make[1]: *** [debian/rules:29: src] 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.)


-- 
1058556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: binutils-or1k-elf
Version: 1.0.9
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):
>  debian/rules binary
> dh binary -Dsrc -Bbld
>debian/rules execute_before_dh_update_autotools_config
> make[1]: Entering directory '/<>'
> tar -xf /usr/src/binutils/binutils-*.tar.xz --transform='s|[^/]*|src|'
> patch -dsrc -p1 < 0001-readelf-typos-in-user-messages.patch
> patching file binutils/readelf.c
> Reversed (or previously applied) patch detected!  Assume -R? [n] 
> Apply anyway? [n] 
> Skipping patch.
> 2 out of 2 hunks ignored -- saving rejects to file binutils/readelf.c.rej
> make[1]: *** [debian/rules:29: src] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/binutils-or1k-elf_1.0.9_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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: binutils-or1k-elf
Source-Version: 1.0.10
Done: Nicolas Boulenguez 

We believe that the bug you reported is fixed in the latest version of
binutils-or1k-elf, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated binutils-or1k-elf 
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, 15 Dec 2023 22:16:45 +
Source: binutils-or1k-elf
Architecture: source
Version: 1.0.10
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Boulenguez 
Changed-By: Nicolas Boulenguez 
Closes: 1058556
Changes:
 binutils-or1k-elf (1.0.10) unstable; urgency=medium
 .
   * Rebuild against binutils 2.41.
   * Remove applied patches. Closes: #1058556.
Checksums-Sha1:
 ec2cf0c407f2a3a919c12a575b3f8525bc888c12 1894 binutils-or1k-elf_1.0.10.dsc
 c328e4ba91cf405ac1d918dbbab845fd78063da2 5124 binutils-or1k-elf_1.0.10.tar.xz
Checksums-Sha256:
 fc52aba3cd6f38f396690e876ced610fe81cc9d51db2d8b36124c17470129211 1894 
binutils-or1k-elf_1.0.10.dsc
 32cd347d97678814fa2f69a8efd47ab5f5630e69fb9544ec7ad5394b504c4e6c 5124 
binutils-or1k-elf_1.0.10.tar.xz
Files:
 e16b6529112030d826c274d337557ebb 1894 devel optional 
binutils-or1k-elf_1.0.10.dsc
 506c1b84ca92f39c766b176b5f14f9b8 5124 devel optional 
binutils-or1k-elf_1.0.10.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmV81zwTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRAUcprJmA8J0kguEACO9Z1yJt3oqaV8CplsSOGFr8Qm9tQe
ggtgOq6U3t4q1GELHAIIA5ZlYcys8RXXHOf1dzUMce/ZS9y8Wv0ek4ALCpZBEJJH
dMQ0vbapGKSIZHWcEXFYg8mU1ob4FFOos8n2lrqnhNAKgCCiyfdkx45YVUbm9sN/
RmP2CtSRypz0/t7chEN4wLk8kLLAiW9c+VFyswObxAG4D56bM1EU7JgsMmngr4aq
kW92vg4+OxnIDtURc7UEl/1xz7CWlKbqGWRczvgSiknv4NVLENi3Eeigal23OuIF
EaSRWX0sYwn/D3WWjg/6i+8hQyoU1NSEQLfAPU681+nyHPW21xP4F8y6y01cBYbJ
R4OPy4GsKxGNenT+Oopo6nAor0fj8CYqrI56wzkrycFfoIra7JLZmntcD2/8aaFU
/Zt7aPoBlp+7yg24VLo/ZqWtxAym8JH6ZqRsYctm0g6d+8Mluie4D8cdm7F1WE/I

Bug#1052983: Bug#1057914: Bug#1056996: bluez: diff for NMU version 5.70-1.1~exp0

[Nobuhiro Iwamatsu]

HI Salvatore,

2023年12月16日(土) 5:40 Salvatore Bonaccorso :
>
> Hi Nobuhiro,
>
> On Fri, Dec 15, 2023 at 05:38:17AM +0100, Salvatore Bonaccorso wrote:
> > Hi Nobuhiro
> >
> > On Fri, Dec 15, 2023 at 08:37:13AM +0900, Nobuhiro Iwamatsu wrote:
> > > Hi Salvatore,
> > >
> > > Thanks for your work.
> > > This patch looks good to me.
> > > Please upload without DELAYED/2 to unstable.
> >
> > Thanks for the confirmation, so I rescheduled it *but* note due to the
> > UsrMerge changes it goes first to experimental, so it can be tested by
> > the dumat tool from Helmut (Cc'ed).
>
> After the ack from Helmut and the dumat check I have now uploaded to
> unstable.

Got it. Thank you!

Best regards,
  Nobuhiro
-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org / kernel.org}
   GPG ID: 32247FBB40AD1FA6

Bug#1057329: marked as done (rust-rlp: autopkgtest failure on 32bit)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 22:25:21 +
with message-id 
and subject line re: rust-rlp: autopkgtest failure on 32bit
has caused the Debian Bug report #1057329,
regarding rust-rlp: autopkgtest failure on 32bit
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.)


-- 
1057329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rlp
Version: 0.5.2-1
Severity: serious

https://tracker.debian.org/pkg/rust-rlp

Issues preventing migration:
∙ ∙ autopkgtest for rust-rlp/0.5.2-1: amd64: Pass, arm64: Pass, armel: 
Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: 
Pass


...
843s failures:
4478
843s 
4479
843s  length_overflow stdout 
4480
843s thread 'length_overflow' panicked at 'assertion failed: `(left == right)`
4481
843s   left: `Err(RlpInvalidLength)`,
4482
843s  right: `Err(RlpIsTooBig)`', tests/tests.rs:27:5
4483
843s stack backtrace:
4484
843s0: rust_begin_unwind
4485
843s  at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
4486
843s1: core::panicking::panic_fmt
4487
843s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
4488
843s2: core::panicking::assert_failed_inner
4489
843s3: core::panicking::assert_failed
4490
843s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:228:5
4491
843s4: tests::length_overflow
4492
843s  at ./tests/tests.rs:27:2
4493
843s5: tests::length_overflow::{{closure}}
4494
843s  at ./tests/tests.rs:23:22
4495
843s6: core::ops::function::FnOnce::call_once
4496
843s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4497
843s7: core::ops::function::FnOnce::call_once
4498
843s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4499
843s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.
4500
843s 
4501
843s  test_rlp_list_length_overflow stdout 
4502
843s thread 'test_rlp_list_length_overflow' panicked at 'assertion failed: 
`(left == right)`
4503
843s   left: `Err(RlpIsTooShort)`,
4504
843s  right: `Err(RlpIsTooBig)`', tests/tests.rs:592:5
4505
843s stack backtrace:
4506
843s0: rust_begin_unwind
4507
843s  at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
4508
843s1: core::panicking::panic_fmt
4509
843s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
4510
843s2: core::panicking::assert_failed_inner
4511
843s3: core::panicking::assert_failed
4512
843s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:228:5
4513
843s4: tests::test_rlp_list_length_overflow
4514
843s  at ./tests/tests.rs:592:2
4515
843s5: tests::test_rlp_list_length_overflow::{{closure}}
4516
843s  at ./tests/tests.rs:588:36
4517
843s6: core::ops::function::FnOnce::call_once
4518
843s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4519
843s7: core::ops::function::FnOnce::call_once
4520
843s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4521
843s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.
4522
843s 
4523
843s 
4524
843s failures:
4525
843s length_overflow
4526
843s test_rlp_list_length_overflow
4527
843s 
4528
843s test result: FAILED. 42 passed; 2 failed; 0 ignored; 0 measured; 0 
filtered out; finished in 0.03s
4529
843s 
4530
843s error: test failed, to rerun pass `--test tests`
4531
844s autopkgtest [22:13:26]: test librust-rlp-dev:: ---]
▾ test librust-rlp-dev:: test results
4532
844s autopkgtest [22:13:26]: test librust-rlp-dev::  - - - - - - - - - - 
results - - - - - - - - - -
4533
844s librust-rlp-dev: FAIL non-zero exit status 101
▾ summary
4534
844s autopkgtest [22:13:26]:  summary
4535
844s rust-rlp:@   FAIL non-zero exit status 101
4536
844s librust-rlp-dev:default FAIL non-zero exit status 101
4537
844s librust-rlp-dev:derive FAIL non-zero exit status 101
4538
844s librust-rlp-dev:rlp-derive FAIL non-zero exit status 101
4539
844s librust-rlp-dev:std  FAIL non-zero exit status 101
4540
844s librust-rlp-dev: FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---

Version: 0.5.2-2

Autopkgtest has now passed on all 32-bit architectures where britney runs tests.--- End Message ---

Bug#1057760: marked as done (settle - upcoming rust-rusqlite update.)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 21:24:24 +
with message-id 
and subject line Bug#1057760: fixed in settle 0.40.1-2
has caused the Debian Bug report #1057760,
regarding settle - upcoming rust-rusqlite update.
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.)


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

Package: settle
Version: 0.40.1-1

I intend to update rust-rusqlite in unstable to 0.29 soon.
The cargo dependencies for settle already allow 0.29 but
the Debian dependencies will need updating.

I don't expect any issues as 0.29 is what upstream asks
for and I already tested this a while ago but I'm filing
this bug report to give you a heads up if you want to
do any further testing.
--- End Message ---
--- Begin Message ---
Source: settle
Source-Version: 0.40.1-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
settle, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated settle 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, 15 Dec 2023 21:59:15 +0100
Source: settle
Architecture: source
Version: 0.40.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1057760
Changes:
 settle (0.40.1-2) unstable; urgency=medium
 .
   * update patches; bump build-dependency for crate rusqlite;
 closes: bug#1057760, thanks to Peter Green
   * declare Built-Using and X-Cargo-Built-Using
Checksums-Sha1:
 4304a475bb36432404726f12ae74260161b7d66b 2361 settle_0.40.1-2.dsc
 b6570f1042a0a0ccc8c7e85efe89452fedb23363 15988 settle_0.40.1-2.debian.tar.xz
 75ac7741f2dd548848c04af1436f218de56a38ff 18769 settle_0.40.1-2_amd64.buildinfo
Checksums-Sha256:
 4926f64af4757ac61b8e7213457d8b94d72caebcd718dcf58eb176ea3d34edc8 2361 
settle_0.40.1-2.dsc
 73873f4a23f2c1f4414fbabd87757bfe7d4165074508e06f54ab7706901e2b1f 15988 
settle_0.40.1-2.debian.tar.xz
 3bebbada0eed6811a998b5cefc651d695d6abc3ea257038c98c369483886123a 18769 
settle_0.40.1-2_amd64.buildinfo
Files:
 9427f20409a20f551a6e8ff164359294 2361 text optional settle_0.40.1-2.dsc
 264543e9adeccd1b695abb0659b4137c 15988 text optional 
settle_0.40.1-2.debian.tar.xz
 50ed13a42e6daeccd1b05426786a438e 18769 text optional 
settle_0.40.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmV8v+YACgkQLHwxRsGg
ASEKYA//ebO5uoo0VWAZSXLBHhMtUadCverhnvb6VZ520YbpBOAxlL2lyIqYeChX
8xJY3nIsijbeNWLQKMxi3JMhtik83A8P4kq67KfcyF5Xq3YCjB2To6o7hrozpYzN
nm2rvmhxysTeIalwJPfUCmzVFs9dO/fvIsRFv3f+FaVl9UsQ3+hntPLo+/BG2BBn
oTzsFqJJpy3VKnC5zDwDD8hmfkpHp5qQe9kX9BVBiqgirD+bSaaPEIpG6ytI1lRR
kHezDHkLFcbszkaxzdEJ6oTL0Pop0+lvT/dtlMt5R3Fi3KmUn5lgqkNTiKEouIZc
Epqq4KQCUdM7wQJaorxkJVaKSwRsGg8ufZMw0sLhrd9xCaWFZbzFUdbs3LkNDr9t
12jUOpLsO5t2EEsFxVbtwa7pxf3TTj84GXeM6EuNux/R+7Ix32AA88t69ZZwK3vU
WBmpJ6XkTdP74pSVIyZuK4ds3GhqYK1wkTqToKDsMD4tGlArDzxBZE5a5ofdTuX2
D0/55A9/QFrEwyIyMdG6LINE3mtQn97dz7jRCrpmiMVdR2F9b8aa0NVVS+ctU/r7
QVtsZQxxUvl5Rqs7h7+tbrpzXfDJH6BFInYeGcz0nYjdMgOgieuWpC+yvHubZP6M
VoOLxuVhpRbOF1iEMz6SKkBCghDLtNfo8v24UzBSjbUw/cq8X+0=
=o1Wl
-END PGP SIGNATURE End Message ---

Bug#1058074: marked as done (rust-hyper-rustls - autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 21:06:14 +
with message-id 
and subject line Bug#1058074: fixed in rust-hyper-rustls 0.24.2-2
has caused the Debian Bug report #1058074,
regarding rust-hyper-rustls - autopkgtest failure
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.)


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

Package: rust-hyper-rustls
Version: 0.24.2-1
Severity: serious
Tags: patch

The autopkgtest for rust-hyper-rustls is failing, because the code in
test_alpn_http2 requires a runtime, but the feature requirements for
the test do not specify one.

A debdiff fixing this is attatched.diff -Nru rust-hyper-rustls-0.24.2/debian/changelog 
rust-hyper-rustls-0.24.2/debian/changelog
--- rust-hyper-rustls-0.24.2/debian/changelog   2023-12-02 20:25:28.0 
+
+++ rust-hyper-rustls-0.24.2/debian/changelog   2023-12-12 01:18:39.0 
+
@@ -1,3 +1,11 @@
+rust-hyper-rustls (0.24.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix feature requirements for test_alpn_http to prevent autopkgtest
+failure.
+
+ -- Peter Michael Green   Tue, 12 Dec 2023 01:18:39 +
+
 rust-hyper-rustls (0.24.2-1) unstable; urgency=medium
 
   * unfuzz patches
diff -Nru 
rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch 
rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
--- rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
1970-01-01 00:00:00.0 +
+++ rust-hyper-rustls-0.24.2/debian/patches/1002_test-requires-runtime.patch
2023-12-12 01:18:17.0 +
@@ -0,0 +1,20 @@
+Description: tests_alpn_http2 fails to build if no runtime is enabled
+ Add feature guards so it doesn't cause autopkgtest failure.
+Author: Peter Michael Green 
+Last-Update: 2023-12-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+Index: rust-hyper-rustls-0.24.2/src/connector/builder.rs
+===
+--- rust-hyper-rustls-0.24.2.orig/src/connector/builder.rs
 rust-hyper-rustls-0.24.2/src/connector/builder.rs
+@@ -353,7 +353,7 @@ mod tests {
+ }
+ 
+ #[test]
+-#[cfg(all(not(feature = "http1"), feature = "http2"))]
++#[cfg(all(not(feature = "http1"), feature = "http2", any(feature = 
"native-tokio", feature = "tokio-runtime")))]
+ fn test_alpn_http2() {
+ let roots = rustls::RootCertStore::empty();
+ let tls_config = rustls::ClientConfig::builder()
diff -Nru rust-hyper-rustls-0.24.2/debian/patches/series 
rust-hyper-rustls-0.24.2/debian/patches/series
--- rust-hyper-rustls-0.24.2/debian/patches/series  2022-12-06 
11:57:28.0 +
+++ rust-hyper-rustls-0.24.2/debian/patches/series  2023-12-12 
01:16:36.0 +
@@ -1,3 +1,4 @@
 1001_http1.patch
+1002_test-requires-runtime.patch
 2001_webpki-roots.patch
 2004_tests_broken.patch
--- End Message ---
--- Begin Message ---
Source: rust-hyper-rustls
Source-Version: 0.24.2-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
rust-hyper-rustls, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-hyper-rustls 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, 15 Dec 2023 21:50:56 +0100
Source: rust-hyper-rustls
Architecture: source
Version: 0.24.2-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1058074
Changes:
 rust-hyper-rustls (0.24.2-2) unstable; urgency=medium
 .
   * add patch 1002 to add feature guards ensuring runtime is available;
 closes: bug#1058074, thanks to Peter Green
Checksums-Sha1:
 68c68969bcad730d3420e4c02c31d9d423939744 3626 rust-hyper-rustls_0.24.2-2.dsc
 79aa9e6f8784ebc448e0e235b2e6391c4b775223 13928 
rust-hyper-rustls_0.24.2-2.debian.tar.xz
 a93193a75f6d3643e3c2dab18f81a91a8ed79456 13207 
rust-hyper-rustls_0.24.2-2_amd64.buildinfo

Bug#1058239: marked as done (onionbalance: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 20:55:13 +
with message-id 
and subject line Bug#1058239: fixed in onionbalance 0.2.2-1.2
has caused the Debian Bug report #1058239,
regarding onionbalance: FTBFS: AttributeError: module 'configparser' has no 
attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)


-- 
1058239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: onionbalance
Version: 0.2.2-1.1
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):
>  debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
>   pybuild --clean -i python{version} -p "3.12 3.11"
> I: pybuild base:310: python3.12 setup.py clean 
> /<>/versioneer.py:421: SyntaxWarning: invalid escape sequence 
> '\s'
>   LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
>   File "/<>/setup.py", line 65, in 
> version=versioneer.get_version(),
> 
>   File "/<>/versioneer.py", line 1480, in get_version
> return get_versions()["version"]
>^^
>   File "/<>/versioneer.py", line 1412, in get_versions
> cfg = get_config_from_root(root)
>   ^^
>   File "/<>/versioneer.py", line 342, in get_config_from_root
> parser = configparser.SafeConfigParser()
>  ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. 
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
> python3.12 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
> returned exit code 13
> make: *** [debian/rules:13: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/onionbalance_0.2.2-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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: onionbalance
Source-Version: 0.2.2-1.2
Done: Alexandre Detiste 

We believe that the bug you reported is fixed in the latest version of
onionbalance, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated onionbalance 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, 15 Dec 2023 19:50:14 +0100
Source: onionbalance
Architecture: source
Version: 0.2.2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Alexandre Detiste 
Closes: 1058239
Changes:
 onionbalance (0.2.2-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with Python3.12+ (Closes: #1058239)
   * Remove trivial usage of python3-future. (Applied upstream)
Checksums-Sha1:
 5c6248a42b46281289ffa1ffda89bb26432cc06f 2237 onionbalance_0.2.2-1.2.dsc
 7f802e60412099e74ab4814934984b8b0482f65d 11632 
onionbalance_0.2.2-1.2.debian.tar.xz
 e1ac788e03328cc50cfe50a3a07d88a62c39ba32 6258 
onionbalance_0.2.2-1.2_source.buildinfo
Checksums-Sha256:
 48940e439431c3f9d634524e396862b553d725db9a8a0f8919e11e2844e381e3 2237 
onionbalance_0.2.2-1.2.dsc
 

Bug#1058767: netplug: unmaintained

[Chris Hofstaedtler]

Source: netplug
Version: 1.2.9.2-3.2
Severity: serious

I'm filing this to get netplug removed from testing, with the goal
of removing it from unstable later, and before that happens, anyone
who wants to actually maintain this package can speak up.

As demonstrated today, having packages in stable that end up used in
downstream distros, and at the same time being completely
unmaintained in Debian for ~7 years is bad for everybody.

If you like to keep netplug in Debian, please start maintaining it
and then close this bug.

Otherwise I'll also file an RM bug for unstable later in this
development cycle.

Chris

Bug#1057403: marked as done (fq: Please upgrade to fq 0.9.0 (resolves FTBFS with latest golang-golang-x-exp-dev))

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 12:41:03 -0800
with message-id 

and subject line Fixed in 0.9.0-1
has caused the Debian Bug report #1057403,
regarding fq: Please upgrade to fq 0.9.0 (resolves FTBFS with latest 
golang-golang-x-exp-dev)
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.)


-- 
1057403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fq
Version: 0.3.0-1+b4
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: Daniel Milde , Anthony Fok 

Hi Daniel (and other fellow Debian Go Packaging Team members),

First of all, thank you for packaging fq, a very useful tool indeed.

There has been an API change to SortFunc (etc.) in golang.org/x/exp/slices,
(backported from "slices" in go1.21) which breaks fq << 0.8.0; please see:

  * slices: new standard library package based on x/exp/slices
https://github.com/golang/go/issues/57433 

  * x/exp/slices: "backport" slices.SortFunc
https://github.com/golang/go/issues/61374

So, after my recently upload of golang-golang-x-exp-dev, fq 0.3.0-1 now
fails to build from source (FTBFS).

Fortunately, the issue has been fixed upstream.  Please kindly package
fq 0.9.0, specifying these dependencies with explicit versions:

  * golang-github-burntsushi-toml-dev (>= 1.3.2)
  * golang-golang-x-exp-dev (>= 0.0~git20230725.302865e)

Many thanks!
Cheers,

Anthony Fok

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

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

Versions of packages fq depends on:
ii  libc6  2.37-12

fq recommends no packages.

fq suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Package: fq
Version: 0.9.0-1

This is fixed by uploading 0.9.0-1.
--- End Message ---

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

[Rafael Laboissière]

* Santiago Vila  [2023-12-15 18:15]:

The thing I don't understand here is why this problem in octave-vibes 
was diagnosed as an "unwritable $HOME" in the first place.


This is what I concluded after running some tests, but I do not 
remember the details. I will try to replicate it.


Best,

Rafael Laboissière

Bug#1052983: Bug#1057914: Bug#1056996: bluez: diff for NMU version 5.70-1.1~exp0

[Salvatore Bonaccorso]

Hi Nobuhiro,

On Fri, Dec 15, 2023 at 05:38:17AM +0100, Salvatore Bonaccorso wrote:
> Hi Nobuhiro
> 
> On Fri, Dec 15, 2023 at 08:37:13AM +0900, Nobuhiro Iwamatsu wrote:
> > Hi Salvatore,
> > 
> > Thanks for your work.
> > This patch looks good to me.
> > Please upload without DELAYED/2 to unstable.
> 
> Thanks for the confirmation, so I rescheduled it *but* note due to the
> UsrMerge changes it goes first to experimental, so it can be tested by
> the dumat tool from Helmut (Cc'ed).

After the ack from Helmut and the dumat check I have now uploaded to
unstable.

Regards,
Salvatore

Bug#1057914: marked as done (bluez: CVE-2023-45866)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 20:35:01 +
with message-id 
and subject line Bug#1057914: fixed in bluez 5.70-1.1
has caused the Debian Bug report #1057914,
regarding bluez: CVE-2023-45866
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.)


-- 
1057914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bluez
Version: 5.70-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for bluez.

CVE-2023-45866[0]:
| Bluetooth HID Hosts in BlueZ may permit an unauthenticated
| Peripheral role HID Device to initiate and establish an encrypted
| connection, and accept HID keyboard reports, potentially permitting
| injection of HID messages when no user interaction has occurred in
| the Central role to authorize such access. An example affected
| package is bluez 5.64-0ubuntu1 in Ubuntu 22.04LTS. NOTE: in some
| cases, a CVE-2020-0556 mitigation would have already addressed this
| Bluetooth HID Hosts issue.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-45866
https://www.cve.org/CVERecord?id=CVE-2023-45866
[1] 
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=25a471a83e02e1effb15d5a488b3f0085eaeb675

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bluez
Source-Version: 5.70-1.1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
bluez, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated bluez 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, 15 Dec 2023 20:57:14 +0100
Source: bluez
Architecture: source
Version: 5.70-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bluetooth Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 1052983 1056996 1057914
Changes:
 bluez (5.70-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upload to unstable.
 .
 bluez (5.70-1.1~exp0) experimental; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Fix FTBFS when systemd.pc changes systemdsystemunitdir (Closes: #1052983)
 .
   [ Chris Hofstaedtler ]
   * Defer udev file placement to udev's pkg-config data (Closes: #1056996)
   * Install hciconfig into /usr/bin instead of /bin
 .
   [ Salvatore Bonaccorso ]
   * input.conf: Change default of ClassicBondedOnly (CVE-2023-45866)
 (Closes: #1057914)
Checksums-Sha1: 
 416e174fe2ecfd863bd042d63152c84ea5659e6e 2911 bluez_5.70-1.1.dsc
 4ba1f274406fa09f9552fe33bc967b70db2c6d0c 40984 bluez_5.70-1.1.debian.tar.xz
Checksums-Sha256: 
 44307403a61d21fa46c0ffdb000d8905001960f40f2e463ea905a162144c7142 2911 
bluez_5.70-1.1.dsc
 54287ae0d36358238377f86537da00fa0cb0bb4615a99c3c7d8cb605ab350f84 40984 
bluez_5.70-1.1.debian.tar.xz
Files: 
 63bf2f4acf78ef42eab77049056657f9 2911 admin optional bluez_5.70-1.1.dsc
 2bbe02d6e6b37fedc84505faf8e35cf9 40984 admin optional 
bluez_5.70-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmV8sUFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E35YQAJGG0B9xidSFTR1d1IwsRNAB1qghU7YW
Glk0XPviC4+4UERNjmE2EjHnz1jiIeKB87BflGtmGofE4pWNCPcmHIluLnVjJnWk
59erMvL1A1T2fF7BLjoshAUtB0YlhkI9jP0eG+R0+l8+dp5nkybakxVr9M+n3rVH
vvPXibe0qhu33QkFF54O6Ob3v0W7mulwm/ji+uAN2W6Rs+HwZdbithK2fDKPnlmM
3ID5kmXX4aKLo8FO4VTdjnZAm721sFf9gd+AhXmV50Xv/XIJTriJqCKsFqlpmD1+
xSWso5+RvBLbZ8nTVKKsyvZMAO/vz3HAGYrpPcSB2oOdKViE8IyreGN3jE6c/tq0
cNhsrOW6ObisJOk40eDtiwut7tJrBNtsjgXCxbXuLKPGdiaY7awvN34kC86PPKQ2
JK7gRmHLRKhoBvdmSr6ie5mFlYTUlKwalVTlCtteep6bQb64nTY6zLR3FWASihaB

Bug#1052983: marked as done (bluez FTBFS when systemd.pc changes systemdsystemunitdir)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 20:35:01 +
with message-id 
and subject line Bug#1052983: fixed in bluez 5.70-1.1
has caused the Debian Bug report #1052983,
regarding bluez FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bluez
Version: 5.69-1
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. bluez' upstream build system consumes this variable
while the packaging hard codes its current value. As we change it, bluez
will FTBFS. Consider applying the attached patch to avoid this failure.

Helmut
diff -Nru bluez-5.69/debian/bluez-meshd.install 
bluez-5.69/debian/bluez-meshd.install
--- bluez-5.69/debian/bluez-meshd.install   2023-08-28 02:38:44.0 
+0200
+++ bluez-5.69/debian/bluez-meshd.install   2023-09-26 16:23:44.0 
+0200
@@ -1,5 +1,5 @@
 usr/share/dbus-1/system.d/bluetooth-mesh.conf
-lib/systemd/system/bluetooth-mesh.service
+${env:deb_systemdsystemunitdir}/bluetooth-mesh.service
 usr/bin/mesh-cfgclient
 usr/bin/mesh-cfgtest
 usr/bin/meshctl
diff -Nru bluez-5.69/debian/bluez.install bluez-5.69/debian/bluez.install
--- bluez-5.69/debian/bluez.install 2023-08-28 02:38:44.0 +0200
+++ bluez-5.69/debian/bluez.install 2023-09-26 16:24:10.0 +0200
@@ -24,7 +24,7 @@
 lib/udev/rules.d/97-hid2hci.rules
 attrib/gatttool usr/bin
 #-- for systemd
-lib/systemd/system/bluetooth.service
+${env:deb_systemdsystemunitdir}/bluetooth.service
 usr/share/dbus-1/system.d/bluetooth.conf
 usr/share/dbus-1/system-services/org.bluez.service
 usr/share/zsh/site-functions/_bluetoothctl
diff -Nru bluez-5.69/debian/changelog bluez-5.69/debian/changelog
--- bluez-5.69/debian/changelog 2023-08-28 02:38:44.0 +0200
+++ bluez-5.69/debian/changelog 2023-09-26 16:49:20.0 +0200
@@ -1,3 +1,10 @@
+bluez (5.69-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 26 Sep 2023 16:49:20 +0200
+
 bluez (5.69-1) unstable; urgency=medium
 
   * Update to 5.69.
diff -Nru bluez-5.69/debian/control bluez-5.69/debian/control
--- bluez-5.69/debian/control   2023-08-28 02:38:44.0 +0200
+++ bluez-5.69/debian/control   2023-09-26 16:22:48.0 +0200
@@ -18,7 +18,8 @@
python3-docutils,
udev,
check ,
-   systemd
+   systemd,
+   systemd-dev,
 Standards-Version: 4.6.1
 Rules-Requires-Root: no
 Vcs-Browser: https://salsa.debian.org/bluetooth-team/bluez
diff -Nru bluez-5.69/debian/rules bluez-5.69/debian/rules
--- bluez-5.69/debian/rules 2023-08-28 02:38:44.0 +0200
+++ bluez-5.69/debian/rules 2023-09-26 16:29:04.0 +0200
@@ -41,6 +41,8 @@
skip_packages = -Nbluez-cups
 endif
 
+export deb_systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 %:
dh $@ --exclude=.la
 
--- End Message ---
--- Begin Message ---
Source: bluez
Source-Version: 5.70-1.1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
bluez, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated bluez 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, 15 Dec 2023 20:57:14 +0100
Source: bluez
Architecture: source
Version: 5.70-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bluetooth Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 1052983 1056996 1057914
Changes:
 bluez (5.70-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upload to unstable.
 .
 bluez (5.70-1.1~exp0) experimental; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Fix FTBFS when systemd.pc changes 

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

[Michael Stone]

On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote:
Stlll, Pádraig gave a reasonable summary of why the change was made, 
despite its incompatibility with previous behavior. (One thing I'd add 
is that the FreeBSD behavior is inherently less race-prone.) It seemed 
like a good idea at the time all things considered, and to my mind 
still does.


I think you underestimate the value of maintaining compatibity with 
deployed versions. In the abstract it may have been a nice cleanup, but 
there are a lot of dumb things in the posix utilities that have been 
dumb for so long it's not worth the pain of changing them. Since this 
change hasn't yet hit mainstream debian, ubuntu, rhel, or suse users, I 
strongly suspect that this is a case where the absence of complaints is 
simply a sign that most of the people who'd be impacted haven't 
experienced the change yet.


Even if we tell people not to use -n at all, that doesn't mean we 
should revert to the coreutils 9.1 behavior.


It does, IMO, as it would be less likely to break scripts written by 
existing coreutils users.


The cat is to some extent out of the bag. Unless one insists on 
(FreeBSD | coreutils 9.2-9.4), or insist on coreutils 7.1-9.1, one 
should not rely on cp -n failing or silently succeeding when the 
destination already exists. This will remain true regardless of 
whether coreutils reverts to its 7.1-9.1 behavior.


Or you use a distribution that has to patch to maintain compatibility 
between versions. Ideally upstream would revert the behavior for now, 
deprecate as the long term fix, and all distributions would work the 
same. The other option is that each distribution decides whether to be 
compatible with upstream coreutils or their own previous release.

Processed: forcibly merging 1057564 1058116

[Debian Bug Tracking System]

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

> forcemerge 1057564 1058116
Bug #1057564 [src:gnome-bluetooth3] gnome-bluetooth3: FTBFS: failing tests
Bug #1057564 [src:gnome-bluetooth3] gnome-bluetooth3: FTBFS: failing tests
Added tag(s) sid and trixie.
Bug #1058116 [src:gnome-bluetooth3] gnome-bluetooth3: FTBFS: RuntimeError: 
Event loop is closed
Merged 1057564 1058116
> thanks
Stopping processing here.

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

Bug#1057604: marked as done (texext: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 19:49:37 +
with message-id 
and subject line Bug#1057604: fixed in texext 0.6.7-3
has caused the Debian Bug report #1057604,
regarding texext: FTBFS: AttributeError: module 'configparser' has no attribute 
'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)


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

Package: src:texext
Version: 0.6.7-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py clean
/<>/versioneer.py:418: SyntaxWarning: invalid escape sequence '\s'
  LONG_VERSION_PY['git'] = '''
Traceback (most recent call last):
  File "/<>/setup.py", line 20, in 
version=versioneer.get_version(),

  File "/<>/versioneer.py", line 1476, in get_version
return get_versions()["version"]
   ^^
  File "/<>/versioneer.py", line 1408, in get_versions
cfg = get_config_from_root(root)
  ^^
  File "/<>/versioneer.py", line 342, in get_config_from_root
parser = configparser.SafeConfigParser()
 ^
AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did 
you mean: 'RawConfigParser'?
E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
python3.12 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
returned exit code 13
make: *** [debian/rules:5: clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: texext
Source-Version: 0.6.7-3
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
texext, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated texext 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, 15 Dec 2023 20:26:59 +0100
Source: texext
Architecture: source
Version: 0.6.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1057604
Changes:
 texext (0.6.7-3) unstable; urgency=medium
 .
   * Team upload.
   * Set DPT as Maintainer
   * Python3.12 support
 Closes: #1057604
   * Standards-Version: 4.6.2 (routine-update)
   * Reorder sequence of d/control fields by cme (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Set upstream metadata fields: Repository.
   * Ignore test that fails with recent sphinx
Checksums-Sha1:
 699111212540bf5570cebd1bf945a50dd76b4157 2128 texext_0.6.7-3.dsc
 8e619ee38a90ff800a9895a47ec8e71f6a33ba58 3892 texext_0.6.7-3.debian.tar.xz
 e1e0f267e1345884c174e7c0a6175fda86e78185 10593 

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

[Paul Eggert]

On 2023-12-15 10:49, Michael Stone wrote:

There's no compelling reason to force this change


Well, certainly nobody compelled us at gunpoint

Stlll, Pádraig gave a reasonable summary of why the change was made, 
despite its incompatibility with previous behavior. (One thing I'd add 
is that the FreeBSD behavior is inherently less race-prone.) It seemed 
like a good idea at the time all things considered, and to my mind still 
does.




Essentially the current situation is that -n shouldn't be used if you expect a 
certain behavior for this case and you are writing a script for linux systems. 
Maybe in 10 years you'll be able to assume the new behavior. Better to just 
tell people to not use it at all, and leave the historic behavior alone until 
everyone has stopped using -n entirely.


Even if we tell people not to use -n at all, that doesn't mean we should 
revert to the coreutils 9.1 behavior.


The cat is to some extent out of the bag. Unless one insists on (FreeBSD 
| coreutils 9.2-9.4), or insist on coreutils 7.1-9.1, one should not 
rely on cp -n failing or silently succeeding when the destination 
already exists. This will remain true regardless of whether coreutils 
reverts to its 7.1-9.1 behavior.

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

[Michael Stone]

On Fri, Dec 15, 2023 at 06:33:00PM +, Pádraig Brady wrote:

Advantages of leaving as is:
We get consistency of "noclobber" behavior across systems / shells.


You don't, unless you ignore the coreutils/linux installed base 
entirely. Essentially the current situation is that -n shouldn't be used 
if you expect a certain behavior for this case and you are writing a 
script for linux systems. Maybe in 10 years you'll be able to assume 
the new behavior. Better to just tell people to not use it at all, and 
leave the historic behavior alone until everyone has stopped using -n 
entirely.



There is no potential for data loss etc.


There may not be, strictly speaking, if you look only at cp without 
context, but we have absolutely no idea what the impact is on the 
unknown number of existing scripts that depend on the historic behavior. 
This is causing breakages in practice.



so it just comes
down to how disruptive it is, or how often -n was used
with the "skip behavior" assumption.


IMO, it should come down to trying to avoid breaking changes in core 
system utilities. There's no compelling reason to force this change, so 
why break anything that depended on the historic behavior--especially 
without any notice or transition period--regardless of arguments over 
whether the historic behavior was right?



We've not had much push back as of yet,
and my current thinking is it's not that disruptive a change.


I suspect that's because it has not yet been widely deployed, which 
makes now the time to fix it.


Michael Stone

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

[Pádraig Brady]

On 15/12/2023 15:56, Michael Stone wrote:

I tend to think this was a serious mistake: it breaks the behavior of
existing scripts with no deprecation period. A stated advantage is
better compatibility with freebsd, but I don't understand why that is
more desirable than compatibility with all deployed gnu/linux systems? I
also don't think it's sufficient to try to lawyer out by saying that the
current behavior was undocumented: the previous documentation said that
-n would "silently do nothing" and that the return code would be zero on
success. Logically, unless cp fails to "do nothing", it should exit with
a zero code.

Such a drastic change in behavior demands a new flag, not a radical
repurposing of a widely used existing flag.

I was hoping to see more action on this bug, but that hasn't happened.
I'm not sure I see a way forward for debian other than reverting to the
old behavior. I am reluctant to do so as that will likely lead to
divergent behavior between distributions, but breaking scripts without a
compelling reason is also not good. I would encourage coreutils to
reconsider the change and finding a non-breaking way forward.


Yes it's a fair point.
It's an awkward case, and worth discussing.

To summarise:

  coreutils >= 7.1 had -n skip existing in dest (2009)
  coreutils >= 9.2 has -n immediately fail if existing in dest
  coreutils >= 9.3 has --update=none to skip existing in dest

  FreeBSD >= 4.7/macos has -n immediately fail if existing in dest

  bash has noclobber as a file protection mechanism,
  and fails immediately upon trying to overwrite a file.
  This is more consistent with the new coreutils behavior.

I see a reasonable amount of cp -n usage across github:
https://github.com/search?q=/cp+.*+-n+.*/+path:*.sh=code

Now it's not clear which behavior these github usages expect,
and the original docs didn't make it clear which behavior to expect.
A quick scan of the github usages also seem mainly to expect
a protection rather than an update use case, so failing
immediately would be the most appropriate action there too.
Also the original coreutils bug report here expected the new behaviour.

So we probably all agree that failing immediately is the
most appropriate / consistent -n behavior,
but GNU had diverged from that so there are about 10 years
of scripts that may expect the silent skip behavior.

Two options I see are:

- Leave as is and fix -n usages that expected the skip behavior
- Deprecate -n entirely and prompt to use --update={fail,none}

Advantages of leaving as is:
We get consistency of "noclobber" behavior across systems / shells.
We fix cases where previously scripts could have proceeded with
stale old files in place.

Disadvantages of leaving as is:
Users expecting the skip behavior, have to change to --update=none.

There is no potential for data loss etc. so it just comes
down to how disruptive it is, or how often -n was used
with the "skip behavior" assumption.

We've not had much push back as of yet,
and my current thinking is it's not that disruptive a change.
So I'd be 55:45 if favor of keeping things as is.

thanks,
Pádraig.

Bug#1058295: marked as done (python-markdown2: FTBFS: 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, 15 Dec 2023 18:22:47 +
with message-id 
and subject line Bug#1058295: fixed in python-markdown2 2.4.11-1
has caused the Debian Bug report #1058295,
regarding python-markdown2: FTBFS: 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.)


-- 
1058295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-markdown2
Version: 2.4.1-1
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):
>  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
>   pybuild --configure -i python{version} -p "3.12 3.11"
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p "3.12 3.11"
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> copying lib/markdown2.py -> 
> /<>/.pybuild/cpython3_3.12_markdown2/build
> running build_scripts
> creating build
> creating build/scripts-3.12
> copying and adjusting bin/markdown2 -> build/scripts-3.12
> changing mode of build/scripts-3.12/markdown2 from 644 to 755
> I: pybuild base:310: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying lib/markdown2.py -> 
> /<>/.pybuild/cpython3_3.11_markdown2/build
> running build_scripts
> creating build/scripts-3.11
> copying and adjusting bin/markdown2 -> build/scripts-3.11
> changing mode of build/scripts-3.11/markdown2 from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test --test-pytest -i python{version} -p "3.12 3.11"
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.12_markdown2/build; python3.12 -m pytest 
> test
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 0 items / 1 error
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.12_markdown2/build/test/test_markdown2.py _
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.12_markdown2/build/test/test_markdown2.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> test/test_markdown2.py:19: in 
> from testlib import TestError, TestSkipped, tag
> test/testlib.py:67: in 
> import imp
> E   ModuleNotFoundError: No module named 'imp'
> === short test summary info 
> 
> ERROR test/test_markdown2.py
>  Interrupted: 1 error during collection 
> 
> === 1 error in 0.17s 
> ===
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.12_markdown2/build; python3.12 -m pytest 
> test
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.11_markdown2/build; python3.11 -m pytest 
> test
> = test session starts 
> ==
> platform linux -- Python 3.11.7, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 8 items
> 
> test/test_markdown2.py ...x  
> [100%]
> 
> === warnings summary 
> ===
> test/testlib.py:67
>   /<>/.pybuild/cpython3_3.11_markdown2/build/test/testlib.py:67: 
> DeprecationWarning: the imp module is deprecated in favour of importlib and 
> slated for removal in Python 3.12; see the module's documentation for 
> alternative uses
> import imp
> 
> .pybuild/cpython3_3.11_markdown2/build/test/test_markdown2.py:586
>   .pybuild/cpython3_3.11_markdown2/build/test/test_markdown2.py:586: 
> PytestCollectionWarning: yield tests were removed in pytest 4.0 - test_cases 
> will be ignored
> 
> test/testlib.py:83
>   

Bug#1056480: marked as done (python-markdown2's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 18:22:47 +
with message-id 
and subject line Bug#1056480: fixed in python-markdown2 2.4.11-1
has caused the Debian Bug report #1056480,
regarding python-markdown2's autopkg tests fail with 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.)


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

Package: src:python-markdown2
Version: 2.4.1-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-markdown2's autopkg tests fail with Python 3.12:

[...]
258s autopkgtest [18:44:18]: test python3-markdown2: 
[---
258s = test session starts 
==

258s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
258s rootdir: /tmp/autopkgtest.996gQ7/autopkgtest_tmp
258s collected 0 items / 1 error
258s
258s  ERRORS 

258s ___ ERROR collecting test/test_markdown2.py 

258s ImportError while importing test module 
'/tmp/autopkgtest.996gQ7/autopkgtest_tmp/test/test_markdown2.py'.

258s Hint: make sure your test modules/packages have valid Python names.
258s Traceback:
258s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
258s return _bootstrap._gcd_import(name[level:], package, level)
258s test/test_markdown2.py:19: in 
258s from testlib import TestError, TestSkipped, tag
258s test/testlib.py:67: in 
258s import imp
258s E   ModuleNotFoundError: No module named 'imp'
258s === short test summary info 


258s ERROR test/test_markdown2.py
258s  Interrupted: 1 error during collection 

258s === 1 error in 0.12s 
===
--- End Message ---
--- Begin Message ---
Source: python-markdown2
Source-Version: 2.4.11-1
Done: Benjamin Drung 

We believe that the bug you reported is fixed in the latest version of
python-markdown2, 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.
Benjamin Drung  (supplier of updated python-markdown2 
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, 15 Dec 2023 18:51:46 +0100
Source: python-markdown2
Built-For-Profiles: noudeb
Architecture: source
Version: 2.4.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Benjamin Drung 
Closes: 1056480 1058295
Changes:
 python-markdown2 (2.4.11-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release (Closes: #1056480, #1058295)
   * Switch to autopkgtest-pkg-pybuild
   * Bump Standards-Version to 4.6.2
   * Override false positive lintian errors for source-is-missing
Checksums-Sha1:
 3caebc05ebf25e907dce5f44a95191d3239f9d79 2137 python-markdown2_2.4.11-1.dsc
 1d7c41d54cb72c852fdd7dc61ac1bf325ff556bd 1096864 
python-markdown2_2.4.11.orig.tar.gz
 549ccc193368563a259ac76faed65839ebe30f15 4828 
python-markdown2_2.4.11-1.debian.tar.xz
 6f915cfa822ac0fdce42ee51b43607dfb61aa210 7830 
python-markdown2_2.4.11-1_source.buildinfo
Checksums-Sha256:
 4c2d55a73cf5fc22b7f4447b3f823911b5562cabb012ec805c8b6c6a68006097 2137 
python-markdown2_2.4.11-1.dsc
 ebd2cf20f06bd28269e8bd0e5e70ac64b22fe2de1e72bbac2fcc9926889c4826 1096864 
python-markdown2_2.4.11.orig.tar.gz
 39f5b5754b78aaad8f73d71d2788e770602d58189eefdfac517fb64715959466 4828 
python-markdown2_2.4.11-1.debian.tar.xz
 81af811974f2591cd4a362f297cdb120b4a1b2d6b50e876ccfc5c602fe4ded17 7830 
python-markdown2_2.4.11-1_source.buildinfo
Files:
 f2b7eab93c2148cdd71a8a25a4ce659d 2137 python optional 
python-markdown2_2.4.11-1.dsc
 dcc7f5d4b24af117844e9fc75e82c362 1096864 python optional 
python-markdown2_2.4.11.orig.tar.gz
 cfd09de2fbbccc524bc598852f43658c 4828 python optional 
python-markdown2_2.4.11-1.debian.tar.xz
 36072e6e68d7ca0cdfdf472c5ce24665 7830 python optional 

Bug#996801: marked as done (db2twitter: unusable with tweepy version 4)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 18:15:19 +
with message-id 
and subject line Bug#1056611: Removed package(s) from unstable
has caused the Debian Bug report #996801,
regarding db2twitter: unusable with tweepy version 4
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.)


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

Package: db2twitter
Version: 0.6-1.1
Severity: grave
Tag: patch

Dear maintainer,

db2twitter has become unusable with the new python3-tweepy package
because of an backwards-incompatible API changes in version 4.
I think you'll need to remove the wait_on_rate_limit_notify=True
parameter from the tweepy.API() constructions in twresend.py:43
and twsend.py:46, but I'm not sure if that is enough.

Cheers
Timo

PS. You may also want to update d/watch to point to the new
upstream repository at https://gitlab.com/chaica/db2twitter

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.6-2+rm

Dear submitter,

as the package db2twitter has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1056611

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#984100: marked as done (libdjconsole: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 17:49:05 +
with message-id 
and subject line Bug#984100: fixed in libdjconsole 0.1.3-3.1
has caused the Debian Bug report #984100,
regarding libdjconsole: ftbfs with GCC-11
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.)


-- 
984100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libdjconsole
Version: 0.1.3-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libdjconsole_0.1.3-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
checking for libusb >= 0.1.11... yes
checking for pthread_create in -lpthread... yes
checking for ANSI C header files... (cached) no
checking for stdbool.h that conforms to C99... no
checking for _Bool... no
checking for an ANSI C-conforming const... yes
checking for error_at_line... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating libdjconsole.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating libdjconsole.pc
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
   dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
make -j1
make[1]: Entering directory '/<>'
make  all-am
make[2]: Entering directory '/<>'
/bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security   
-DDATADIR=\"/usr/share/libdjconsole\" -c -o djconsole.lo djconsole.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DDATADIR=\"/usr/share/libdjconsole\" -c djconsole.cpp  
-fPIC -DPIC -o .libs/djconsole.o
djconsole.cpp: In constructor ‘DJConsole::DJConsole(bool)’:
djconsole.cpp:110:18: error: ordered comparison of pointer with integer zero 
(‘usb_dev_handle*’ and ‘int’)
  110 | if(hdev1 < 0)
  |~~^~~
djconsole.cpp:118:18: error: ordered comparison of pointer with integer zero 
(‘usb_dev_handle*’ and ‘int’)
  118 | if(hdev2 < 0)
  |~~^~~
djconsole.cpp:137:24: warning: too many arguments for format 
[-Wformat-extra-args]
  137 | printf("Error claiming event interface, unload 
conflicting HID/joystick kernel driver\n", ret);
  |
^
djconsole.cpp:152:24: warning: too many arguments for format 
[-Wformat-extra-args]
  152 | printf("Error claiming mouse interface, unload 
conflicting mouse kernel driver\n", ret);
  |

Processed: block 1055694 with 1058752

[Debian Bug Tracking System]

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

> block 1055694 with 1058752
Bug #1055694 [klibc-utils] initramfs-tools: After updating coreutils cp: not 
replacing in console when running update-initramfs
Bug #1056912 [klibc-utils] initramfs-tools: update-initramfs - can't generate 
initramfs
1055694 was not blocked by any bugs.
1055694 was not blocking any bugs.
Added blocking bug(s) of 1055694: 1058752
1056912 was not blocked by any bugs.
1056912 was not blocking any bugs.
Added blocking bug(s) of 1056912: 1058752
> thanks
Stopping processing here.

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

Bug#1056510: marked as done (python-upsetplot's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 17:19:02 +
with message-id 
and subject line Bug#1056510: fixed in python-upsetplot 0.8.0-2
has caused the Debian Bug report #1056510,
regarding python-upsetplot's autopkg tests fail with 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.)


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

Package: src:python-upsetplot
Version: 0.8.0-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-upsetplot's autopkg tests fail with Python 3.12:

[...]
736s Testing with python3.12:
736s /usr/lib/python3/dist-packages/pytz/__init__.py:30: SyntaxWarning: 
invalid escape sequence '\s'

736s   match = re.match("^#\s*version\s*([0-9a-z]*)\s*$", line)
737s Traceback (most recent call last):
737s   File "", line 1, in 
737s   File "/usr/lib/python3/dist-packages/upsetplot/__init__.py", line 
7, in 
737s from .data import (generate_counts, generate_data, 
generate_samples,
737s   File "/usr/lib/python3/dist-packages/upsetplot/data.py", line 4, 
in 

737s from distutils.version import LooseVersion
737s ModuleNotFoundError: No module named 'distutils'
--- End Message ---
--- Begin Message ---
Source: python-upsetplot
Source-Version: 0.8.0-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
python-upsetplot, 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.
Andreas Tille  (supplier of updated python-upsetplot 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, 15 Dec 2023 17:53:08 +0100
Source: python-upsetplot
Architecture: source
Version: 0.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1056510
Changes:
 python-upsetplot (0.8.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Build-Depends: pybuild-plugin-pyproject
   * Standards-Version: 4.6.2 (routine-update)
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * Replace distutils by packaging to work with Python3.12
 Closes: #1056510
Checksums-Sha1:
 83310805d313db4c79a03cbf733b9df998b4b054 2316 python-upsetplot_0.8.0-2.dsc
 475753ae954be06d8775695946514ec4fba07c60 4088 
python-upsetplot_0.8.0-2.debian.tar.xz
 08a8e8a995a64c2da9dc89bca9c77f00214e4c2c 10481 
python-upsetplot_0.8.0-2_amd64.buildinfo
Checksums-Sha256:
 810aec8903a6f8c4985b8d28a3f56d1a4f8068ecc9f9e599954f01589a7b1537 2316 
python-upsetplot_0.8.0-2.dsc
 920b3df5b758f67937678cd49f94cb3c51d626c04928b86e630493337deb21f1 4088 
python-upsetplot_0.8.0-2.debian.tar.xz
 f18c39f9eb5aed971076c8b075557e58a90cb06648f6a55e207b1838353a4ef1 10481 
python-upsetplot_0.8.0-2_amd64.buildinfo
Files:
 21f5203a44ef05725ca87f6d49ae1c29 2316 python optional 
python-upsetplot_0.8.0-2.dsc
 f23f4f0b4ab6c94d4de90012b33e65a4 4088 python optional 
python-upsetplot_0.8.0-2.debian.tar.xz
 2c5889b8efc9ec0ea591f5bfbb586e9b 10481 python optional 
python-upsetplot_0.8.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmV8hr4RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFXnA//eVnUPL0hVK/vWDeYhjCiB7lY/W2EUYRh
ALp5KFRKScmp9ZOZz2cy9ktqnPB0lTTMcIUjSj9YXoV5rSCHv2rv9ORA7mvtqwf5
SIwB7mvdv2kXVp6GQt717XkxqBr3b9uWIqNzfQwP+79YEhTBEIAo5wHDgGqwrAz4
qI8EcuAT1FIbop+NBJGov80ZHbJsHJdkFJZ4pwRmGhc3FhM7FsQhhxAt6h/zGkYY
6stC1fZXHOjzwXEN4Vc3nCnZn7/x1vs2VDuWSOk0SNS5jb6DVLhwOBBIGcSWro52
901l7gZPnKYug5tek0LuEH6Uu6IH48CIgv2pqEjre3Wft5HK9apx6GudhPIOqZa/
n2PIQEQ6eA+qca3X/sXhps1Tx4WJ+I/0b13eR2vWDAh7sMOlPvsp+eiSYlRa4oI2
KTQaubE0K1ZdZWIPbFmSR0yrh4vmPsryrDi1ZHma2l8qBlozIBMpkwt89vB5e+a9
82nplUv8Uj1WSOMk+H4Ax9OdMpCH5jS+aaEJklfVV/HE5WaK/9tVVaYKb9ME5XSM
pfpT9D0Y50rjUNkH0Pe8tSGg8OzdTJ//HM4PkmK3OdTc2Pxoo3BDerXz3HqJx4H9
FXmSdiQFz1bRIl+F2zlottteZFtHOa3H+JqwLDp9xc76jJ3EGHp6rCnhm7FuqgjD
Q8YjdTshTQk=
=c5kG
-END PGP SIGNATURE End Message ---

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

[Santiago Vila]

El 15/12/23 a las 17:00, Rafael Laboissière escribió:

     […]
     HOME=/sbuild-nonexistent
     […]

It seems that your building system is setting HOME to an non-existent 
directory. How do you explain that ?


In this case, given its name, the variable is set by sbuild
before starting the build. This is the standard software used to
build packages by the official autobuilders and also by anybody
doing archive-rebuilds for QA purposes.

You can find such HOME=/sbuild-nonexistent line in any successful
build log as well:

https://buildd.debian.org/status/fetch.php?pkg=octave=amd64=8.4.0-1%2Bb1=1700257373=0

After sbuild sets HOME to an unwritable value, some debhelper tools,
it seems, may in turn set HOME to a temporary writable directory in certain
circumstances which I still have not studied carefully.

The thing I don't understand here is why this problem in octave-vibes
was diagnosed as an "unwritable $HOME" in the first place.

Thanks.

Processed: tagging 1058749

[Debian Bug Tracking System]

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

> tags 1058749 + sid trixie
Bug #1058749 [scanbd] scanbd: fails to upgrade from bookworm: mv: not replacing 
'/etc/scanbd/dll.conf'
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

[Rafael Laboissière]

Control: block -1 by 1058621
Control: merge -1 1057590

Trying again…

Processed: Re: Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1058621
Bug #1058281 [src:octave-netcdf] octave-ncarray: FTBFS: make: *** 
[debian/rules:5: binary] Error 139
1058281 was not blocked by any bugs.
1058281 was not blocking any bugs.
Added blocking bug(s) of 1058281: 1058621
> merge -1 1057590
Bug #1058281 [src:octave-netcdf] octave-ncarray: FTBFS: make: *** 
[debian/rules:5: binary] Error 139
Bug #1057589 [src:octave-netcdf] octave-ncarray: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Added tag(s) trixie and sid.
Added tag(s) trixie and sid.
Bug #1058281 [src:octave-netcdf] octave-ncarray: FTBFS: make: *** 
[debian/rules:5: binary] Error 139
Marked as found in versions octave-netcdf/1.0.17-1.
Added tag(s) upstream and confirmed.
Bug #1057590 [src:octave-netcdf] octave-netcdf: FTBFS: fatal: caught signal 
Segmentation fault -- stopping myself...
Merged 1057589 1057590 1058281

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

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

[Rafael Laboissière]

Rafael

* Santiago Vila  [2023-12-15 12:59]:


El 13/12/23 a las 9:27, Rafael Laboissière escribió:

i.e. you may rely on a writable $HOME if it's for a "good cause" (i.e. 
dh_auto_test).

So, the simple question: Should this not be also implemented in dh_octave_check 
as well, which is what octave-vibes was using?


Thanks for bringing this to my knowledge. However, I do not quite understand 
the text above. Does it mean that, when the package Build-Depends on 
debhelper-compat = 13, then $HOME will be set automatically to a writable 
directory? Well, octave-vibes that compatibility level of debhelper, but the 
autobuilders set HOME=/nonexistent/.


Sorry, I don't really know for sure.

I just remember this case where the debhelper feature allowed for an "easy" fix:

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


There is something that I definitively do not understand here. Let's 
take your build log for octave-vibes: 
https://people.debian.org/~sanvila/build-logs/202312/octave-vibes_0.2.0-8_amd64-20231205T162533.194Z


We see that debhelper-compat = 13 is used (line #76) in the build. 
However, we see the following in line #3199:


User Environment


[…]
HOME=/sbuild-nonexistent
[…]

It seems that your building system is setting HOME to an non-existent 
directory. How do you explain that ?


Best,

Rafael

Bug#1058752: cp --no-clobber behavior has changed

[Michael Stone]

I tend to think this was a serious mistake: it breaks the behavior of 
existing scripts with no deprecation period. A stated advantage is 
better compatibility with freebsd, but I don't understand why that is 
more desirable than compatibility with all deployed gnu/linux systems? I 
also don't think it's sufficient to try to lawyer out by saying that the 
current behavior was undocumented: the previous documentation said that 
-n would "silently do nothing" and that the return code would be zero on 
success. Logically, unless cp fails to "do nothing", it should exit with 
a zero code.


Such a drastic change in behavior demands a new flag, not a radical 
repurposing of a widely used existing flag.


I was hoping to see more action on this bug, but that hasn't happened. 
I'm not sure I see a way forward for debian other than reverting to the 
old behavior. I am reluctant to do so as that will likely lead to 
divergent behavior between distributions, but breaking scripts without a 
compelling reason is also not good. I would encourage coreutils to 
reconsider the change and finding a non-breaking way forward.


Michael Stone

Bug#1058124: marked as done (graphite-web: FTBFS: AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'?)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 15:50:26 +
with message-id 
and subject line Bug#1058124: fixed in graphite-web 1.1.10-2
has caused the Debian Bug report #1058124,
regarding graphite-web: FTBFS: AttributeError: 'ConfigParser' object has no 
attribute 'readfp'. Did you mean: 'read'?
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.)


-- 
1058124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: graphite-web
Version: 1.1.10-1
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):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 33, in 
> cf.readfp(StringIO(orig_setup_cfg), 'setup.cfg')
> ^
> AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you 
> mean: 'read'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
> python3.12 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
> returned exit code 13
> make: *** [debian/rules:7: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/graphite-web_1.1.10-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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: graphite-web
Source-Version: 1.1.10-2
Done: Alexandre Rossi 

We believe that the bug you reported is fixed in the latest version of
graphite-web, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Rossi  (supplier of updated graphite-web 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, 15 Dec 2023 16:30:39 +0100
Source: graphite-web
Architecture: source
Version: 1.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Graphite Group 
Changed-By: Alexandre Rossi 
Closes: 1058124
Changes:
 graphite-web (1.1.10-2) unstable; urgency=medium
 .
   * raise standards compliance to 4.6.2 (no change)
   * add forward info for CVE-2022-4728 CVE-2022-4729 CVE-2022-4730 patch
   * fix build with python 3.12 (Closes: #1058124)
Checksums-Sha1:
 0c45f5946065a2f8baa1fd1cf18110381dc1ecd3 2292 graphite-web_1.1.10-2.dsc
 b2e122b5911b865fe2ff8377cab2f567edcfd8ff 229440 
graphite-web_1.1.10-2.debian.tar.xz
 9626055fd98b0b1c2f331ed9e8df8314820eb374 8684 
graphite-web_1.1.10-2_amd64.buildinfo
Checksums-Sha256:
 bcf69453cfcf45319b12ad5f4ba2ba8c6f79476586b503d5e2a956c638d25b6a 2292 
graphite-web_1.1.10-2.dsc
 c6dd5661efaf55c5434e7f3b67748061586a6cd94c273e39b948ef7411991492 229440 
graphite-web_1.1.10-2.debian.tar.xz
 86d681e3c3b43234179abe341b4f09470c53aad8905731b557a4bdf9d9dee2b1 8684 
graphite-web_1.1.10-2_amd64.buildinfo
Files:
 035b437a039b5b1b4d039835033778b8 2292 web optional graphite-web_1.1.10-2.dsc
 2e622e86266a85da621ec253c95a425f 229440 web optional 
graphite-web_1.1.10-2.debian.tar.xz
 70af628038edc7f249c35ecda4f468ce 8684 web optional 
graphite-web_1.1.10-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEqURFrS/GV/h4cdpsWI+eupOKFo8FAmV8cX8ACgkQWI+eupOK

Processed: notfound 1058749 in scanbd/1.5.1-6+b1, found 1058749 in scanbd/1.5.1-6

[Debian Bug Tracking System]

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

> notfound 1058749 scanbd/1.5.1-6+b1
Bug #1058749 [scanbd] scanbd: fails to upgrade from bookworm: mv: not replacing 
'/etc/scanbd/dll.conf'
The source scanbd and version 1.5.1-6+b1 do not appear to match any binary 
packages
No longer marked as found in versions scanbd/1.5.1-6+b1.
> found 1058749 scanbd/1.5.1-6
Bug #1058749 [scanbd] scanbd: fails to upgrade from bookworm: mv: not replacing 
'/etc/scanbd/dll.conf'
Marked as found in versions scanbd/1.5.1-6.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'

[Debian Bug Tracking System]

Processing control commands:

> found -1 scanbd/1.5.1-6+b1
Bug #1058749 [scanbd] scanbd: fails to upgrade from bookworm: mv: not replacing 
'/etc/scanbd/dll.conf'
The source scanbd and version 1.5.1-6+b1 do not appear to match any binary 
packages
Marked as found in versions scanbd/1.5.1-6+b1.
> block -1 by 1058752
Bug #1058749 [scanbd] scanbd: fails to upgrade from bookworm: mv: not replacing 
'/etc/scanbd/dll.conf'
1058749 was not blocked by any bugs.
1058749 was not blocking any bugs.
Added blocking bug(s) of 1058749: 1058752

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

Bug#1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'

[Chris Hofstaedtler]

Control: found -1 scanbd/1.5.1-6+b1
Control: block -1 by 1058752

Hi Andreas,

I'm unsure what to do here. This problem is triggered by a behaviour
change in coreutils.

On Fri, Dec 15, 2023 at 03:17:18PM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'bookworm'.
> It installed fine in 'bookworm', then the upgrade to 'sid' fails.
[..]
>   Setting up scanbd (1.5.1-7) ...
>   mv: not replacing '/etc/scanbd/dll.conf'

With coreutils from unstable, scanbd from bookworm also fails to
install:

| Preparing to unpack .../scanbd_1.5.1-6+b1_arm64.deb ...
| Unpacking scanbd (1.5.1-6+b1) over (1.5.1-6+b1) ...
| Setting up scanbd (1.5.1-6+b1) ...
| mv: not replacing '/etc/scanbd/dll.conf'
| dpkg: error processing package scanbd (--configure):
|  installed scanbd package post-installation script subprocess returned error 
exit status 1
| Processing triggers for dbus (1.14.10-3) ...
| Errors were encountered while processing:
|  scanbd
| E: Sub-process /usr/bin/dpkg returned an error code (1)

I've marked this bug as found in the old version for now, and have
also opened #1058752 (but also see #1058630).
scanbd is not the only package affected by the coreutils change.

Chris

Processed: bug 1058752 is forwarded to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572

[Debian Bug Tracking System]

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

> forwarded 1058752 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572
Bug #1058752 [coreutils] coreutils: cp/mv changed return code in incompatible 
way
Set Bug forwarded-to-address to 
'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572'.
> thanks
Stopping processing here.

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

Bug#1058551: marked as done (git-buildpackage: FTBFS: make[2]: *** [Makefile:22: syntax-check] Error 1)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 15:19:40 +
with message-id 
and subject line Bug#1058551: fixed in git-buildpackage 0.9.33
has caused the Debian Bug report #1058551,
regarding git-buildpackage: FTBFS: make[2]: *** [Makefile:22: syntax-check] 
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.)


-- 
1058551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-buildpackage
Version: 0.9.32
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):
> make[1]: Entering directory '/<>'
> make
> make[2]: Entering directory '/<>'
> flake8 
> ./tests/02_test_upstream_source_tar_unpack.py:58:20: E721 do not compare 
> types, for exact checks use `is` / `is not`, for instance checks use 
> `isinstance()`
> make[2]: *** [Makefile:22: syntax-check] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/git-buildpackage_0.9.32_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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: git-buildpackage
Source-Version: 0.9.33
Done: Guido Günther 

We believe that the bug you reported is fixed in the latest version of
git-buildpackage, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated git-buildpackage 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, 15 Dec 2023 15:49:47 +0100
Source: git-buildpackage
Architecture: source
Version: 0.9.33
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Closes: 1058551
Changes:
 git-buildpackage (0.9.33) unstable; urgency=medium
 .
   [ Evangelos Ribeiro Tzaras ]
   * [f6d90d5] docs: gbp-clone: Fix small typo and fix metadata file name
 .
   [ Guido Günther ]
   * [6923df4] config: Catch DuplicateOption errors.
 Nicer than printing a stack trace
   * [8deb2e1] tests: Make flake8 happy (Closes: #1058551)
 .
   [ Taihsiang Ho (tai271828) ]
   * [d1a9745] d/control: Specify required git version as dependency.
 Explicitly specify the git version to facilitate easier backporting.
 Developers can align with this git version to reduce false alarms due
 to version inconsistencies.
Checksums-Sha1:
 d4e593c553652d21f84d955582521806d85ed188 2368 git-buildpackage_0.9.33.dsc
 1f94113b0c511f235e0c47ad3be8b288fd08e173 3140196 git-buildpackage_0.9.33.tar.xz
 4bfc5f0d1a9b9b9fac64592d1aa171de0a9a4054 13400 
git-buildpackage_0.9.33_amd64.buildinfo
Checksums-Sha256:
 e229b689831c0454b0e76df082c835bb752c7d9fb5647095814715b9c2755c7f 2368 
git-buildpackage_0.9.33.dsc
 2c76a8fa6a907e8e2d07b78f870aa755bbcb0a1d43204b4e3b67f4521c5b5b83 3140196 
git-buildpackage_0.9.33.tar.xz
 0ae5d5ed46cdd596ec9caea3bb25030cb791ef8efd2a19e59de07a482a4d1d3e 13400 
git-buildpackage_0.9.33_amd64.buildinfo
Files:
 4cc78bedf6bb2477e66f71fe0dd18ae1 2368 vcs optional git-buildpackage_0.9.33.dsc
 b094e4cf1bad8cb30878b778bc37ecf7 3140196 vcs optional 
git-buildpackage_0.9.33.tar.xz
 3e69b387e03341c6381fcb0691526ce4 13400 vcs optional 
git-buildpackage_0.9.33_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEY/bM35YinQkoayrDJb+GUkr8weMFAmV8a+AACgkQJb+GUkr8

Processed: user debian...@lists.debian.org, usertagging 1054931, affects 1054931, usertagging 1055511 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1054931 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1054931 + libghc-tidal-dev
Bug #1054931 [src:haskell-tidal] haskell-tidal: FTBFS: unsatisfiable 
build-dependencies: libghc-hosc-dev (< 0.20), libghc-primitive-dev (< 0.8)
Added indication that 1054931 affects libghc-tidal-dev
> usertags 1055511 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 1055511 20221002-10
Bug #1055511 [progress-linux-container] progress-linux-container: diversions 
need to be updated to deal with DEP17 P3
Marked as found in versions progress-linux-metapackages/20221002-10.
> affects 1055511 + progress-linux-server
Bug #1055511 [progress-linux-container] progress-linux-container: diversions 
need to be updated to deal with DEP17 P3
Added indication that 1055511 affects progress-linux-server
> found 1020284 1:2.43.0-1
Bug #1020284 [git-daemon-run] git-daemon-run: fails to purge: deluser -f:  
Unknown option: f
Marked as found in versions git/1:2.43.0-1.
> affects 1058353 - libadios2-mpi-c-libadios2-serial-c-dev + 
> libadios2-serial-c-dev libadios2-mpi-c-dev
Bug #1058353 [libadios2-mpi-c-dev] libadios2-mpi-c-dev: ships headers already 
shipped in libadios2-common-c-dev
Removed indication that 1058353 affects libadios2-mpi-c-libadios2-serial-c-dev
> thanks
Stopping processing here.

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

Processed: coreutils: cp/mv changed return code in incompatible way

[Debian Bug Tracking System]

Processing control commands:

> affects -1 initramfs-tools scanbd
Bug #1058752 [coreutils] coreutils: cp/mv changed return code in incompatible 
way
Added indication that 1058752 affects initramfs-tools and scanbd

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

Bug#1058752: coreutils: cp/mv changed return code in incompatible way

[Chris Hofstaedtler]

Package: coreutils
Version: 9.4-1
Severity: serious
Tags: upstream
Control: affects -1 initramfs-tools scanbd

Hi,

cp and mv -n changed their behaviour with regard to their exit code
when doing nothing, and also now write to stderr.

This causes a few problems in existing packages:

1) initramfs-tools autopkgtests fail, and it is unclear if
initramfs images with busybox actually work. Compare #1058630 and
[1]

2) scanbd now fails to install, see #1058749

And maybe other, so far unreported problems.


The upstream bug report appears to be stalled:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572

What will be done about this?


Should all affected packages (which are these?) workaround the
fallout?


Chris



[1] https://ci.debian.net/packages/i/initramfs-tools/testing/amd64/41037580/

Bug#1058297: marked as done (python-svg.path: FTBFS: 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, 15 Dec 2023 15:05:50 +
with message-id 
and subject line Bug#1058297: fixed in python-svg.path 6.3-2
has caused the Debian Bug report #1058297,
regarding python-svg.path: FTBFS: 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.)


-- 
1058297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-svg.path
Version: 6.3-1
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):
>  debian/rules build
> dh build --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_svg.path/build/svg
> copying src/svg/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_svg.path/build/svg
> creating /<>/.pybuild/cpython3_3.12_svg.path/build/svg/path
> copying src/svg/path/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_svg.path/build/svg/path
> copying src/svg/path/path.py -> 
> /<>/.pybuild/cpython3_3.12_svg.path/build/svg/path
> copying src/svg/path/parser.py -> 
> /<>/.pybuild/cpython3_3.12_svg.path/build/svg/path
> running egg_info
> creating src/svg.path.egg-info
> writing src/svg.path.egg-info/PKG-INFO
> writing dependency_links to src/svg.path.egg-info/dependency_links.txt
> writing requirements to src/svg.path.egg-info/requires.txt
> writing top-level names to src/svg.path.egg-info/top_level.txt
> writing manifest file 'src/svg.path.egg-info/SOURCES.txt'
> reading manifest file 'src/svg.path.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching 'Makefile'
> adding license file 'LICENSE.txt'
> writing manifest file 'src/svg.path.egg-info/SOURCES.txt'
> I: pybuild base:310: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_svg.path/build/svg
> copying src/svg/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_svg.path/build/svg
> creating /<>/.pybuild/cpython3_3.11_svg.path/build/svg/path
> copying src/svg/path/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_svg.path/build/svg/path
> copying src/svg/path/path.py -> 
> /<>/.pybuild/cpython3_3.11_svg.path/build/svg/path
> copying src/svg/path/parser.py -> 
> /<>/.pybuild/cpython3_3.11_svg.path/build/svg/path
> running egg_info
> writing src/svg.path.egg-info/PKG-INFO
> writing dependency_links to src/svg.path.egg-info/dependency_links.txt
> writing requirements to src/svg.path.egg-info/requires.txt
> writing top-level names to src/svg.path.egg-info/top_level.txt
> reading manifest file 'src/svg.path.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching 'Makefile'
> adding license file 'LICENSE.txt'
> writing manifest file 'src/svg.path.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.12_svg.path/build; python3.12 -m pytest 
> tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> configfile: setup.cfg
> plugins: cov-4.1.0
> collected 53 items
> 
> tests/test_boundingbox_image.py F[  
> 1%]
> tests/test_doc.py .  [  
> 3%]
> tests/test_generation.py .   [  
> 5%]
> tests/test_image.py F[  
> 7%]
> tests/test_parsing.py .  [ 
> 39%]
> tests/test_paths.py ..   [ 
> 88%]
> tests/test_tokenizer.py ..   
> [100%]
> 
> === FAILURES 
> ===
> ___ BoundingBoxImageTest.test_image 
> 
> 
> self =  

Bug#1058751: r-cran-rcppparallel: broken symlinks: /usr/lib/R/site-library/RcppParallel/lib/libtbb*.so.*.8 -> ../../../..//libtbb*.so.*.8

[Andreas Beckmann]

Package: r-cran-rcppparallel
Version: 5.1.7+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships
broken symlinks.

>From the attached log (scroll to the bottom...):

3m44.2s ERROR: FAIL: Broken symlinks:
  /usr/lib/R/site-library/RcppParallel/lib/libtbb.so.12.8 -> 
../../../../x86_64-linux-gnu/libtbb.so.12.8 (r-cran-rcppparallel)
  /usr/lib/R/site-library/RcppParallel/lib/libtbbbind_2_5.so.3.8 -> 
../../../../x86_64-linux-gnu/libtbbbind_2_5.so.3.8 (r-cran-rcppparallel)
  /usr/lib/R/site-library/RcppParallel/lib/libtbbmalloc.so.2.8 -> 
../../../../x86_64-linux-gnu/libtbbmalloc.so.2.8 (r-cran-rcppparallel)
  /usr/lib/R/site-library/RcppParallel/lib/libtbbmalloc_proxy.so.2.8 -> 
../../../../x86_64-linux-gnu/libtbbmalloc_proxy.so.2.8 (r-cran-rcppparallel)

I'm not sure whether these links are used at all (I didn't find any
obvious references in r-cran-rcppparallel, but then again I have no
experience with the R ecosystem).
If they are unused, they should be simply dropped from the package.

If you really need them, I'd suggest to only use the SONAME, i.e.
without the '.8' suffix.

(Currently the library files use a file version suffix of .11, but that
could change again in the next new upstream version upload.)


cheers,

Andreas


r-cran-rlang_1.1.2-1.log.gz
Description: application/gzip

Bug#1055159: marked as done (python-svg.path's autopkg tests fail with pillow 10.1.0)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 15:05:50 +
with message-id 
and subject line Bug#1055159: fixed in python-svg.path 6.3-2
has caused the Debian Bug report #1055159,
regarding python-svg.path's autopkg tests fail with pillow 10.1.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.)


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

Package: src:python-svg.path
Version: 6.3-1
Severity: serious
Tags: sid trixie

python-svg.path's autopkg tests fail with pillow 10.1.0.
see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-svg.path/39404032/log.gz


 27s ==
 27s FAIL: test_image (tests.test_image.ImageTest.test_image)
 27s --
 27s Traceback (most recent call last):
 27s   File 
"/tmp/autopkgtest-lxc.0vs2cq8a/downtmp/build.pRi/src/tests/test_image.py", line 
130, in test_image

 27s self.assertFalse(
 27s AssertionError: (10, 12, 403, 742) is not false : The resulting image is 
different from test_image.png

 27s
 27s ==
 27s FAIL: test_image 
(tests.test_boundingbox_image.BoundingBoxImageTest.test_image)

 27s --
 27s Traceback (most recent call last):
 27s   File 
"/tmp/autopkgtest-lxc.0vs2cq8a/downtmp/build.pRi/src/tests/test_boundingbox_image.py", 
line 139, in test_image

 27s self.assertFalse(
 27s AssertionError: (10, 12, 391, 742) is not false : The resulting image is 
different from test_boundingbox_image.png

 27s
 27s --
 27s Ran 46 tests in 0.751s
 27s
 27s FAILED (failures=2)
 27s Test failed: 
 27s error: Test failed: failures=2>
--- End Message ---
--- Begin Message ---
Source: python-svg.path
Source-Version: 6.3-2
Done: Benjamin Drung 

We believe that the bug you reported is fixed in the latest version of
python-svg.path, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated python-svg.path 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, 15 Dec 2023 15:37:14 +0100
Source: python-svg.path
Built-For-Profiles: noudeb
Architecture: source
Version: 6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Benjamin Drung 
Closes: 1055159 1058297
Changes:
 python-svg.path (6.3-2) unstable; urgency=medium
 .
   * QA upload.
   * tests: Use better than nothing font (Closes: #1055159, #1058297)
Checksums-Sha1:
 5ed06b2fffbba148c1b7a7059ef6c93be635fabc 2174 python-svg.path_6.3-2.dsc
 ba57066be7bc9f2f6f51a15bc8f47903023f7b3d 8256 
python-svg.path_6.3-2.debian.tar.xz
 58f23925fcfa9a258eaadabcddcf853ac79c5c48 9728 
python-svg.path_6.3-2_source.buildinfo
Checksums-Sha256:
 550895cd27f7f6815d30821df1a6a914cad1f467bc95e9fc40096391bff4b469 2174 
python-svg.path_6.3-2.dsc
 dde5d9d876f89d852aacd4d764e21e2a51e79617da93702887a08a5604a23c64 8256 
python-svg.path_6.3-2.debian.tar.xz
 e331efc8157f6b6d440b7712acba69b1223d8caddf183bde8dcd37d535c43a1f 9728 
python-svg.path_6.3-2_source.buildinfo
Files:
 8feedc6eb8d7a782159d011de5165801 2174 python optional python-svg.path_6.3-2.dsc
 d837b442557adad7b39e377ec8a3ec3f 8256 python optional 
python-svg.path_6.3-2.debian.tar.xz
 2670a002f181deae050c9d7e083ea9ee 9728 python optional 
python-svg.path_6.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmV8ZQIACgkQFZ61xO/I
d0wRxA/9F1OF7WZmy/2X21DVraE5+NbK6iouXEQq7sJauFYCuj87URAc7M9QG5eT
CjTmLdFej5EZy5ZnhGdVRMZjBG/iJpN3BnGjYMiobRGH2L+7PaQtpeVDc0SYvXJ3
QrTtsswU09DaPxVtz04xa9qOWFjKRfFWBoM6jOFeP7WA7I7pm/WzSnyKy2TFyCnL
0eWIrr9m8ehDuFEvqdslqD8xS8+Yc3dzKTdam6fbar7TlwI6q9/YYfK3bU/Ibx9T
OBPNljZCf9JLxPF8lJGdQTARVYnzKxo1hxlC8bFZH90/Khfw4DS9R0gmEBlO34LC
Jl13HJ8IyT/iCliErIAS4eWRP35qzmg5jbquU3gZPS1YwweH3t7SEwffL73hJrhx

Bug#1058516: marked as done (fiat-ecmwf: FTBFS: make[1]: *** [debian/rules:42: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 15:02:14 +
with message-id 
and subject line FIxed in last upload
has caused the Debian Bug report #1058516,
regarding fiat-ecmwf: FTBFS: make[1]: *** [debian/rules:42: 
override_dh_auto_configure] Error 2
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.)


-- 
1058516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fiat-ecmwf
Version: 1.0.0-4
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):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -DENABLE_DOCS=On -DENABLE_OMP=On -DENABLE_FORTRAN=On 
> -DENABLE_MPI=On 
>   cd debian/build && cmake -DCMAKE_MODULE_PATH=/usr/share/ecbuild/cmake 
> -DECBUILD_MACROS_DIR=/usr/share/ecbuild/cmake -DENABLE_BIT_REPRODUCIBLE=On 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release -DDISABLE_OS_CHECK=On 
> -DBUILD_SITE=debian -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
> -DECBUILD_LOG_LEVEL=DEBUG -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DENABLE_DOCS=On -DENABLE_OMP=On 
> -DENABLE_FORTRAN=On -DENABLE_MPI=On ../..
> -- DEBUG - ecbuild project(fiat) 
> CMake Deprecation Warning at 
> /usr/share/ecbuild/cmake/ecbuild_project.cmake:44 (cmake_minimum_required):
>   Compatibility with CMake < 3.5 will be removed from a future version of
>   CMake.
> 
>   Update the VERSION argument  value or use a ... suffix to tell
>   CMake that the project does not need compatibility with older versions.
> Call Stack (most recent call first):
>   CMakeLists.txt:12 (project)
> 
> 
> -- The Fortran compiler identification is GNU 13.2.0
> -- The C compiler identification is GNU 13.2.0
> -- The CXX compiler identification is GNU 13.2.0
> -- Detecting Fortran compiler ABI info
> -- Detecting Fortran compiler ABI info - done
> -- Check for working Fortran compiler: /usr/bin/f95 - skipped
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- DEBUG - -
> -- DEBUG - Environment:
> -- DEBUG - -
> SCHROOT_GID=1001
> DEB_HOST_MULTIARCH=x86_64-linux-gnu
> LC_ALL=C.UTF-8
> DEB_HOST_GNU_SYSTEM=linux-gnu
> DEB_BUILD_GNU_TYPE=x86_64-linux-gnu
> DEB_TARGET_ARCH_LIBC=gnu
> FFLAGS=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection 
> -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13
> DEB_BUILD_ARCH_ENDIAN=little
> DEB_BUILD_GNU_SYSTEM=linux-gnu
> CFLAGS_FOR_BUILD=-g -O2
> OBJCXXFLAGS_FOR_BUILD=-g -O2
> DEB_BUILD_ARCH_BITS=64
> DEB_BUILD_OPTIONS=parallel=8
> DEB_HOST_ARCH=amd64
> LDFLAGS_FOR_BUILD=
> DEB_TARGET_ARCH_ENDIAN=little
> SOURCE_DATE_EPOCH=1674416047
> OBJCFLAGS_FOR_BUILD=-g -O2
> OBJCXXFLAGS=-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection
> DEB_HOST_ARCH_BITS=64
> LANG=C.UTF-8
> MAKEFLAGS=
> SCHROOT_GROUP=user42
> DEB_TARGET_ARCH=amd64
> DH_INTERNAL_OPTIONS=-O--buildsystem=ecbuild-O--builddir=debian/build
> DEB_HOST_GNU_CPU=x86_64
> DEB_BUILD_ARCH_LIBC=gnu
> MFLAGS=-w
> DH_VERBOSE=1
> DEB_TARGET_ARCH_BITS=64
> CXXFLAGS_FOR_BUILD=-g -O2
> ASFLAGS=
> DEB_BUILD_ARCH_CPU=amd64
> LC_COLLATE=C.UTF-8
> SCHROOT_ALIAS_NAME=unstable
> DEB_HOST_ARCH_OS=linux
> SHELL=/bin/sh
> FCFLAGS=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection
> DEB_HOST_ARCH_CPU=amd64
> SCHROOT_USER=user42
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> DEB_BUILD_ARCH_ABI=base
> CPPFLAGS_FOR_BUILD=
> DEB_BUILD_ARCH=amd64
> FFLAGS_FOR_BUILD=-g -O2
> DEB_HOST_ARCH_LIBC=gnu
> SCHROOT_SESSION_ID=sid-amd64-sbuild-f6222330-0d99-4406-afce-a3fe3d1b5abe
> DEB_TARGET_ARCH_CPU=amd64
> DEB_HOST_GNU_TYPE=x86_64-linux-gnu
> DEB_BUILD_ARCH_OS=linux
> 

Bug#1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'

[Andreas Beckmann]

Package: scanbd
Version: 1.5.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
X-Debbugs-Cc: Chris Hofstaedtler 

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'bookworm'.
It installed fine in 'bookworm', then the upgrade to 'sid' fails.

This test intentionally skipped 'testing' to find problems before packages
migrate from 'unstable' to 'testing'.

>From the attached log (scroll to the bottom...):

  Setting up scanbd (1.5.1-7) ...
  mv: not replacing '/etc/scanbd/dll.conf'
  dpkg: error processing package scanbd (--configure):
   installed scanbd package post-installation script subprocess returned error 
exit status 1


cheers,

Andreas


scanbd_1.5.1-7.log.gz
Description: application/gzip

Bug#1058402: marked as done (spyder-kernels: FTBFS: 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, 15 Dec 2023 14:08:46 +
with message-id 
and subject line Re: Bug#1058402: spyder-kernels: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
has caused the Debian Bug report #1058402,
regarding spyder-kernels: FTBFS: 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.)


-- 
1058402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spyder-kernels
Version: 2.5.0-1
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):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/_version.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/py3compat.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels
> creating 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/spyderpdb.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/utils.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/namespace_manager.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/umr.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/spydercustomize.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> creating 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/dochelpers.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/mpl.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/test_utils.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/iofuncs.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/nsview.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/misc.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/lazymodules.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> creating 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/kernel.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/shell.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/outstream.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/__main__.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/start.py -> 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> creating 
> /<>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/comms
> copying spyder_kernels/comms/__init__.py -> 
> 

Processed: Re: Bug#1056531: cython 3.x (for Python 3.12)

[Debian Bug Tracking System]

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

> severity 1056531 important
Bug #1056531 [src:spyder-kernels] spyder-kernels autopkg tests fail with Python 
3.12
Severity set to 'important' from 'serious'
> retitle 1056531 spyder-kernels: cannot handle Cython files with Python 3.12
Bug #1056531 [src:spyder-kernels] spyder-kernels autopkg tests fail with Python 
3.12
Changed Bug title to 'spyder-kernels: cannot handle Cython files with Python 
3.12' from 'spyder-kernels autopkg tests fail with Python 3.12'.
> thanks
Stopping processing here.

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

Bug#1056531: cython 3.x (for Python 3.12)

[Julian Gilbey]

severity 1056531 important
retitle 1056531 spyder-kernels: cannot handle Cython files with Python 3.12
thanks

Update on this bug.  cython3-legacy and the current cython3 (which
I've just updated to not fail the autopkgtest tests with Python 3.12)
do not have working pyximport modules.  So I'm skipping the tests in
this package which depend on that for the time being.  When Cython 3.x
is in testing, I will re-enable those tests and depend on the new
version of cython3.  In the meantime, Spyder will have difficulties
with Cython source files if Python 3.12 is the default Python.  As
long as Python 3.11 is the default, it will be fine.

So I'm lowering the severity to important for now, and will close it
once I can depend on Cython 3.x.

Best wishes,

   Julian

Bug#1058532: golang-google-api: FTBFS: tests failed

[M Hickford]

> --- FAIL: TestTokenSource (0.00s)
> panic: cannot handle unexported field at {*google.Credentials}.universeDomain:
> "golang.org/x/oauth2/google".Credentials

This is fixed upstream
https://github.com/googleapis/google-api-go-client/commit/b3a71bda027d9ff92df3bf76b5ee9ffa55520dd9
so hopefully updating the package would fix the problem

Bug#1055554: marked as done (python-libais ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 13:51:00 +
with message-id 
and subject line Bug#104: fixed in python-libais 
0.17+git.20190917.master.e464cf8-4
has caused the Debian Bug report #104,
regarding python-libais ftbfs with 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.)


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

Package: src:python-libais
Version: 0.17+git.20190917.master.e464cf8-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

failing tests with Python 3.12:

[...]
==
ERROR: testMsg1 
(test.compatibility.gpsd_test.SingleMessageTestsTest.testMsg1)

--
Traceback (most recent call last):
  File "/<>/test/compatibility/gpsd_test.py", line 53, in 
testMsg1

self.assertDictContainsSubset(expected, mangled)
^
AttributeError: 'SingleMessageTestsTest' object has no attribute 
'assertDictContainsSubset'


==
ERROR: testMsg5LargeTypeAndCargo 
(test.compatibility.gpsd_test.SingleMessageTestsTest.testMsg5LargeTypeAndCargo)

--
Traceback (most recent call last):
  File "/<>/test/compatibility/gpsd_test.py", line 72, in 
testMsg5LargeTypeAndCargo

self.assertDictContainsSubset(expected, mangled)
^
AttributeError: 'SingleMessageTestsTest' object has no attribute 
'assertDictContainsSubset'


==
ERROR: testTimestamps 
(test.compatibility.gpsd_test.SingleMessageTestsTest.testTimestamps)

--
Traceback (most recent call last):
  File "/<>/test/compatibility/gpsd_test.py", line 92, in 
testTimestamps

self.assertDictContainsSubset(expected, mangled)
^
AttributeError: 'SingleMessageTestsTest' object has no attribute 
'assertDictContainsSubset'


==
ERROR: testDecodeUnknownMessage6 
(test.test_decode.Ais6Decoders.testDecodeUnknownMessage6)

--
Traceback (most recent call last):
  File "/<>/test/test_decode.py", line 36, in 
testDecodeUnknownMessage6

self.assertRaisesRegexp(ais.DecodeError, '6:669:11',
^^^
AttributeError: 'Ais6Decoders' object has no attribute 
'assertRaisesRegexp'. Did you mean: 'assertRaisesRegex'?


--
Ran 87 tests in 0.030s

FAILED (errors=4, skipped=2)
Test failed: 
error: Test failed: failures=0>
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
python3.12 setup.py test
--- End Message ---
--- Begin Message ---
Source: python-libais
Source-Version: 0.17+git.20190917.master.e464cf8-4
Done: Benjamin Drung 

We believe that the bug you reported is fixed in the latest version of
python-libais, 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 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated python-libais 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, 15 Dec 2023 14:32:02 +0100
Source: python-libais
Built-For-Profiles: noudeb
Architecture: source
Version: 0.17+git.20190917.master.e464cf8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Benjamin Drung 
Closes: 104
Changes:
 python-libais (0.17+git.20190917.master.e464cf8-4) unstable; urgency=medium
 .
   * Team upload
   * Fix logging line in TagQueue.put if no NMEA match is found
   * test: support Python 3.12 (Closes: #104)
   * Bump Standards-Version to 4.6.2
Checksums-Sha1:
 0a4b97b9cd26ddbc12da3c996c158beb416af2e0 2442 

Bug#1050097: Maintainers, please fix

[hardpenguin13]

Hi there. Installing the dependencies manually works. Please accept the
patch and rebuild the package and then close the bug ️.

Processed: Re: Bug#1056485: python-mpd asyncio tests fail with Python 3.12

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 python-mpd asyncio tests fail with Python 3.12
Bug #1056485 [src:python-mpd] python-mpd's autopkg tests fail with Python 3.12
Changed Bug title to 'python-mpd asyncio tests fail with Python 3.12' from 
'python-mpd's autopkg tests fail with Python 3.12'.
> severity -1 important
Bug #1056485 [src:python-mpd] python-mpd asyncio tests fail with Python 3.12
Severity set to 'important' from 'serious'

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

Bug#1056485: python-mpd asyncio tests fail with Python 3.12

[Simon McVittie]

Control: retitle -1 python-mpd asyncio tests fail with Python 3.12
Control: severity -1 important

On Sun, 10 Dec 2023 at 20:59:48 +, Simon McVittie wrote:
> On Wed, 22 Nov 2023 at 15:18:06 +0100, Matthias Klose wrote:
> > python-mpd's autopkg tests fail with Python 3.12:
> > [...]
> > 248s mpd.base.ConnectionError: Can not send command to disconnected client
> 
> Fedora opened an equivalent bug upstream. No fix is currently known -
> patches would be very much appreciated.

It looks as though the failing tests are for python-mpd's asyncio
interface, which is not actually used by any Debian package yet. In the
3.1.0-2 upload, I've marked those tests to be skipped, which mitigates
the bug.

It's still a valid bug, just not RC any more. If anyone is interested in
fixing the asyncio interface (or the test - it's not clear which one is
wrong), please revert d/p/Skip-asyncio-unit-tests-in-Python-3.12.patch
locally.

3.1.0-2 also sets up the package to run tests for all supported Python
versions at build time, which should make the failure with 3.12 easier
to reproduce: it will become a build failure, not just an autopkgtest
failure.

Thanks,
smcv

Bug#1056492: marked as done (python-pomegranate's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 13:22:02 +
with message-id 
and subject line Bug#1056492: fixed in python-pomegranate 0.14.8-4
has caused the Debian Bug report #1056492,
regarding python-pomegranate's autopkg tests fail with 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.)


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

Package: src:python-pomegranate
Version: 0.14.8-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-pomegranate's autopkg tests fail with Python 3.12:

[...]
700s autopkgtest [18:54:06]: test autodep8-python3: [---
700s Testing with python3.12:
701s Traceback (most recent call last):
701s   File "", line 1, in 
701s   File "/usr/lib/python3/dist-packages/pomegranate/__init__.py", 
line 12, in 

701s from .parallel import *
701s   File "pomegranate/parallel.pyx", line 7, in init pomegranate.parallel
701s   File "pomegranate/hmm.pyx", line 26, in init pomegranate.hmm
701s   File "pomegranate/kmeans.pyx", line 24, in init pomegranate.kmeans
701s   File "/usr/lib/python3/dist-packages/joblib/__init__.py", line 
113, in 

701s from .memory import Memory, MemorizedResult, register_store_backend
701s   File "/usr/lib/python3/dist-packages/joblib/memory.py", line 32, 
in 
701s from ._store_backends import StoreBackendBase, 
FileSystemStoreBackend
701s   File "/usr/lib/python3/dist-packages/joblib/_store_backends.py", 
line 15, in 

701s from .backports import concurrency_safe_rename
701s   File "/usr/lib/python3/dist-packages/joblib/backports.py", line 
22, in 

701s import distutils  # noqa
701s 
701s ModuleNotFoundError: No module named 'distutils'
--- End Message ---
--- Begin Message ---
Source: python-pomegranate
Source-Version: 0.14.8-4
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
python-pomegranate, 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.
Andreas Tille  (supplier of updated python-pomegranate 
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, 15 Dec 2023 12:06:50 +0100
Source: python-pomegranate
Architecture: source
Version: 0.14.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1056492 1056867
Changes:
 python-pomegranate (0.14.8-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Andreas Tille ]
   * Restrict upstream version to 0.14.8 series since this package has the
 only purpose to work with cnvkit which requires this version based on
 Cython and not on PyTorch
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * d/rules: call dh_numpy3
   * Verify test works properly
 Closes: #1056492
 .
   [ Bas Couwenberg ]
   * Switch to cython3-legacy
 Closes: #1056867
Checksums-Sha1:
 7ca2e06e6c8bc6a2d5bc1cff621facf5ab6745f9 2603 python-pomegranate_0.14.8-4.dsc
 745412157fe1257ffa4af4fe0f91507a6b552487 39168 
python-pomegranate_0.14.8-4.debian.tar.xz
 7315119671ede5ed75efe65581f419a319c82f94 9036 
python-pomegranate_0.14.8-4_amd64.buildinfo
Checksums-Sha256:
 47e7f19611a3227b74bdef8a623df55d5f0d0de14ab4e89b8eeb88833e926be2 2603 
python-pomegranate_0.14.8-4.dsc
 12247c9916689919391c3f864397e5cd725b40d57820f5f597f3de3bc9a22657 39168 
python-pomegranate_0.14.8-4.debian.tar.xz
 53b8fab4f52f9499115caf2f5b3385d31f08af888d15857aa9d83d1a8638 9036 
python-pomegranate_0.14.8-4_amd64.buildinfo
Files:
 251d6671f624c60dc72ed0837c69d740 2603 science optional 
python-pomegranate_0.14.8-4.dsc
 e5ae20e44491b0b349efc2bdd27657bb 39168 science optional 
python-pomegranate_0.14.8-4.debian.tar.xz
 1ffd97ef05dfc6a5b78394b4013356de 9036 science optional 
python-pomegranate_0.14.8-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmV8TNkRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF+nRAAhG7cuKn2ej7hUFNXPisLtZQSEAQuUB+s

Bug#1058746: libghc-swish-doc: Depends: haddock-interface-38 but it is not installable

[Sebastian Ramacher]

Package: libghc-swish-doc
Version: 0.10.4.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

libghc-swish-doc is currently not installable.

$ apt install libghc-swish-doc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libghc-swish-doc : Depends: haddock-interface-38 but it is not installable
Recommends: ghc-doc but it is not going to be installed
Recommends: libghc-hashable-doc but it is not going to be 
installed
Recommends: libghc-intern-doc but it is not going to be 
installed
Recommends: libghc-network-uri-doc but it is not going to 
be installed
Recommends: libghc-polyparse-doc but it is not going to be 
installed
Recommends: libghc-swish-dev but it is not going to be 
installed
Recommends: libjs-mathjax but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

Cheers
-- 
Sebastian Ramacher

Processed: affects 1058380

[Debian Bug Tracking System]

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

> affects 1058380 + src:ros2-ament-cmake-ros src:ros2-ament-index
Bug #1058380 [python3-ament-flake8] python3-ament-flake8: incompatible with 
flake8 version 6
Bug #1058418 [python3-ament-flake8] python3-ament-flake8: incompatible with 
flake8 version 6
Added indication that 1058380 affects src:ros2-ament-cmake-ros and 
src:ros2-ament-index
Added indication that 1058418 affects src:ros2-ament-cmake-ros and 
src:ros2-ament-index
> thanks
Stopping processing here.

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

Bug#1058744: dateparser's autopkg tests fail on 32bit platforms

[Matthias Klose]

Package: src:dateparser
Version: 1.2.0-1
Severity: serious
Tags: sid trixie

dateparser's autopkg tests fail on 32bit platforms:

[...]
151s === FAILURES 
===
151s _ TestLocalTZOffset.test_timezone_offset_calculation_1 
_

151s
151s a = (testMethod=test_timezone_offset_calculation_1>,)

151s
151s @wraps(func)
151s def standalone_func(*a):
151s >   return func(*(a + p.args), **p.kwargs)
151s
151s /usr/lib/python3/dist-packages/parameterized/parameterized.py:637:
151s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _
151s 
/tmp/autopkgtest-lxc.26ggv9gl/downtmp/autopkgtest_tmp/tests/test_timezone_parser.py:137: 
in test_timezone_offset_calculation

151s self.given_time(utc, local)
151s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _

151s
151s self = testMethod=test_timezone_offset_calculation_1>
151s utc_dt_string = '2052-01-02 11:07', local_dt_string = '2052-01-02 
10:07'

151s
151s def given_time(self, utc_dt_string, local_dt_string):
151s datetime_cls = dateparser.timezone_parser.datetime
151s if not isinstance(datetime_cls, Mock):
151s datetime_cls = Mock(wraps=datetime)
151s >   utc_dt_obj = datetime.strptime(utc_dt_string, "%Y-%m-%d 
%H:%M").astimezone(

151s dt.timezone.utc
151s )
151s E   OverflowError: timestamp out of range for platform time_t
151s
151s 
/tmp/autopkgtest-lxc.26ggv9gl/downtmp/autopkgtest_tmp/tests/test_timezone_parser.py:156: 
OverflowError
151s === short test summary info 

151s FAILED 
tests/test_timezone_parser.py::TestLocalTZOffset::test_timezone_offset_calculation_1
151s = 1 failed, 23916 passed, 1 skipped, 3 deselected in 78.40s 
(0:01:18) ==

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

[Santiago Vila]

El 13/12/23 a las 9:27, Rafael Laboissière escribió:

i.e. you may rely on a writable $HOME if it's for a "good cause" (i.e. 
dh_auto_test).

So, the simple question: Should this not be also implemented in dh_octave_check 
as well, which is what octave-vibes was using?


Thanks for bringing this to my knowledge. However, I do not quite understand 
the text above. Does it mean that, when the package Build-Depends on 
debhelper-compat = 13, then $HOME will be set automatically to a writable 
directory? Well, octave-vibes that compatibility level of debhelper, but the 
autobuilders set HOME=/nonexistent/.


Sorry, I don't really know for sure.

I just remember this case where the debhelper feature allowed for an "easy" fix:

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


Also, while we are at it, the Policy paragraph that you quoted:


The Debian autobuilders set HOME to /nonexistent so that packages which try to 
write to a home directory will fail to build.


would probably need to be reworded a little bit.


I agree. I think that a bug report should be filed against debian-policy on 
this issue.


Yes, I'll add that to my todo list.

Thanks a lot.

Bug#1058678: blt: disable jpeg support

[Adrian Bunk]

On Fri, Dec 15, 2023 at 11:20:09AM +0100, Helmut Grohne wrote:
>...
> The resulting artifacts
> still differed a lot from an unmodified build and in particular, the
> _uuid.so and _nis.so module went missing. The former probably is due to
> something from tk or blt issuing a dependency on uuid-dev and with those
> packages removed, uuid-dev was no longer pulled. I have not found a
> probably cause for the nis module.
>...

Missing build dependency on pkg-config.

> Helmut

cu
Adrian

Bug#1058743: libuv1: FTBFS on s390x on older kernels

[Simon Chopin]

Package: libuv1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: scho...@ubuntu.com

Hi!

If the buildd is using an older kernel version, such as 5.4 as is the
case in the Ubuntu s390x builders, the build fails on the following
tests:

not ok 147 - idle_starvation
not ok 366 - timer_from_check

In Ubuntu, the attached patch was applied to fix it.

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

Kernel: Linux 6.5.0-14-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
libuv1-1.46.0/debian/patches/lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
 
libuv1-1.46.0/debian/patches/lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
--- 
libuv1-1.46.0/debian/patches/lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
   1970-01-01 01:00:00.0 +0100
+++ 
libuv1-1.46.0/debian/patches/lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
   2023-12-15 12:44:07.0 +0100
@@ -0,0 +1,39 @@
+From 50b53cbd0db8d4e7be06939a0976ff520e791d31 Mon Sep 17 00:00:00 2001
+From: Ben Noordhuis 
+Date: Wed, 12 Jul 2023 23:33:49 +0200
+Subject: [PATCH] linux: don't use io_uring on pre-5.10.186 kernels (#4093)
+
+Those kernels have a known resource consumption bug where the sqpoll
+thread busy-loops.
+
+Fixes: https://github.com/libuv/libuv/issues/4089
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libuv1/+bug/2046442
+Origin: upstream, 
https://github.com/libuv/libuv/commit/50b53cbd0db8d4e7be06939a0976ff520e791d31
+Applied-Upstream: v1.47.0
+---
+ src/unix/linux.c | 8 +++-
+ 1 file changed, 7 insertions(+), 1 deletion(-)
+
+diff --git a/src/unix/linux.c b/src/unix/linux.c
+index 28803225..65fb847f 100644
+--- a/src/unix/linux.c
 b/src/unix/linux.c
+@@ -431,8 +431,14 @@ static int uv__use_io_uring(void) {
+   use = atomic_load_explicit(_io_uring, memory_order_relaxed);
+ 
+   if (use == 0) {
++/* Older kernels have a bug where the sqpoll thread uses 100% CPU. */
++use = uv__kernel_version() >= /* 5.10.186 */ 0x050ABA ? 1 : -1;
++
++/* But users can still enable it if they so desire. */
+ val = getenv("UV_USE_IO_URING");
+-use = val == NULL || atoi(val) ? 1 : -1;
++if (val != NULL)
++  use = atoi(val) ? 1 : -1;
++
+ atomic_store_explicit(_io_uring, use, memory_order_relaxed);
+   }
+ 
+-- 
+2.40.1
+
diff -Nru libuv1-1.46.0/debian/patches/series 
libuv1-1.46.0/debian/patches/series
--- libuv1-1.46.0/debian/patches/series 2023-10-15 16:37:48.0 +0200
+++ libuv1-1.46.0/debian/patches/series 2023-12-15 12:43:14.0 +0100
@@ -3,3 +3,4 @@
 disable_ipv6_test.patch
 path_max_zero_st_size
 skip-multicast-test
+lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch

Bug#1058521: marked as done (libhinoko: FTBFS: make: *** [debian/rules:8: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 11:50:50 +
with message-id 
and subject line Bug#1058521: fixed in libhinoko 1.0.1-1
has caused the Debian Bug report #1058521,
regarding libhinoko: FTBFS: make: *** [debian/rules:8: binary] 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.)


-- 
1058521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhinoko
Version: 1.0.0-1
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):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -Ddoc=true
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 
> meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr 
> --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu 
> -Dpython.bytecompile=-1 -Ddoc=true
> The Meson build system
> Version: 1.3.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: hinoko
> Project version: 1.0.0
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-8) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231206
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Run-time dependency hinawa found: YES 4.0.0
> Run-time dependency gobject-2.0 found: YES 2.78.3
> Build-time dependency glib-2.0 found: YES 2.78.3
> Program /usr/bin/glib-genmarshal found: YES (/usr/bin/glib-genmarshal)
> Dependency glib-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums)
> Dependency glib-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums)
> Run-time dependency gobject-introspection-1.0 found: YES 1.78.1
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Program /usr/bin/g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Program /usr/bin/g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
> Program hinoko-enum found: YES (/usr/bin/python3 
> /<>/tests/hinoko-enum)
> Program fw-iso-ctx found: YES (/usr/bin/python3 
> /<>/tests/fw-iso-ctx)
> Program fw-iso-ir-single found: YES (/<>/tests/fw-iso-ir-single)
> Program fw-iso-ir-multiple found: YES 
> (/<>/tests/fw-iso-ir-multiple)
> Program fw-iso-it found: YES (/<>/tests/fw-iso-it)
> Program fw-iso-resource found: YES (/usr/bin/python3 
> /<>/tests/fw-iso-resource)
> Program fw-iso-resource-auto found: YES (/usr/bin/python3 
> /<>/tests/fw-iso-resource-auto)
> Program fw-iso-resource-once found: YES (/usr/bin/python3 
> /<>/tests/fw-iso-resource-once)
> Program hinoko-functions found: YES (/usr/bin/python3 
> /<>/tests/hinoko-functions)
> Configuring hinoko.toml using configuration
> Run-time dependency gi-docgen found: YES 2023.3
> Program gi-docgen found: YES (/usr/bin/gi-docgen)
> Build targets in project: 8
> 
> hinoko 1.0.0
> 
>   User defined options
> buildtype : plain
> libdir: lib/x86_64-linux-gnu
> localstatedir : /var
> prefix: /usr
> sysconfdir: /etc
> wrap_mode : nodownload
> python.bytecompile: -1
> doc   : true
> 
> Found ninja-1.11.1 at /usr/bin/ninja
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=meson
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/19] /usr/bin/glib-genmarshal --prefix hinoko_sigs_marshal --stdinc 
> --output src/hinoko_sigs_marshal.h --header ../src/hinoko_sigs_marshal.list 
> --pragma-once
> INFO: Reading ../src/hinoko_sigs_marshal.list...
> [2/19] /usr/bin/glib-genmarshal --prefix hinoko_sigs_marshal --stdinc 
> --output src/hinoko_sigs_marshal.c --body ../src/hinoko_sigs_marshal.list 
> --include-header hinoko_sigs_marshal.h
> INFO: Reading ../src/hinoko_sigs_marshal.list...
> [3/19] /usr/bin/meson --internal exe --unpickle 
> /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_358aefc8a2d2e7e57b7937f58ed52edbb1e512ad.dat
> [4/19] /usr/bin/meson --internal exe --unpickle 
> /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_3897d4c04b1161abaabacfa321fbf0aa6805f8d0.dat
> [5/19] cc -Isrc/libhinoko.so.1.0.0.p -Isrc -I../src -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/hinawa 
> -fdiagnostics-color=always 

Bug#1058678: blt: disable jpeg support

[Adrian Bunk]

On Thu, Dec 14, 2023 at 06:22:45PM +0300, Sergei Golovan wrote:
>...
> Can someone investigate if blt is really necessary for Python now?
> It's a very old
> unmaintained piece of software, and I think that dependence of Python on it
> should be a bug.
>...

The src:python3.x packages build idle-python3.x packages.
IDLE is an IDE for Python.[1]

The idle-python3.x packages depend on python3-tk, which depends on blt.

There is a certain weirdness in Python shipping an IDE that is based
on Tcl/Tk, but that's an upstream issue.

The tk-dev/blt-dev build dependencies in src:python3.x:
- might be remnants from the times when python3-tk was built there, or
- might be test-only, or
- might be workaroundable with a noidle build profile

> Sergei Golovan

cu
Adrian

[1] https://docs.python.org/3/library/idle.html

Bug#1058360: marked as done (specreduce: FTBFS: 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, 15 Dec 2023 11:36:45 +
with message-id 
and subject line Bug#1058360: fixed in specreduce 1.3.0-2
has caused the Debian Bug report #1058360,
regarding specreduce: FTBFS: 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.)


-- 
1058360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: specreduce
Version: 1.3.0-1
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):
>  debian/rules build
> dh build --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:310: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> /usr/lib/python3/dist-packages/setuptools/installer.py:134: UserWarning: 
> Unbuilt egg for specreduce [unknown version] (/<>)
>   pkg_resources.get_distribution('wheel')
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
> I: pybuild base:310: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> 

Bug#1056583: kaidan: FTBFS with disabled network

[Gianfranco Costamagna]

control: tags -1 patch

https://patches.ubuntu.com/k/kaidan/kaidan_0.9.1-2ubuntu1.patch

this patch might do the trick.

+Description: Disable test requiring internet access
+Author: Gianfranco Costamagna 
+Bug-Debian: https://bugs.debian.org/1056583
+Last-Update: 2023-11-23
+
+--- kaidan-0.9.1.orig/tests/PublicGroupChatTest.cpp
 kaidan-0.9.1/tests/PublicGroupChatTest.cpp
+@@ -125,7 +125,7 @@ private Q_SLOTS:
+   QVERIFY(PublicGroupChat::toJson(groupChats) == 
QJsonArray({object1, object2}));
+   QVERIFY(groupChats == (PublicGroupChats {PublicGroupChat 
{object1}, PublicGroupChat {object2}}));
+   }
+-
++/*
+   void test_GroupChatSearchManager_GroupChatModel()
+   {
+   PublicGroupChatSearchManager manager;
+@@ -179,7 +179,7 @@ private Q_SLOTS:
+   QCOMPARE(groupChat.name(), index.data(Qt::DisplayRole));
+   QCOMPARE(groupChat.description(), index.data(Qt::ToolTipRole));
+   }
+-
++*/
+   void test_GroupChatProxyModel_data()
+   {
+   using Role = PublicGroupChatModel::CustomRole;


G.

On Thu, 23 Nov 2023 14:53:14 +0100 Gianfranco Costamagna 
 wrote:

Source: kaidan
Version: 0.9.1-2
Severity: serious


Hello, the package FTBFS trying to call search.jabber.network, something 
forbidden by policy.

6: QWARN  : GroupChatTest::test_GroupChatSearchManager_GroupChatModel() 
public-group-chat.search: Search request error: Host search.jabber.network not 
found
6: FAIL!  : GroupChatTest::test_GroupChatSearchManager_GroupChatModel() 
'spyError.isEmpty()' returned FALSE. ()

Full log available e.g. here: 
https://launchpadlibrarian.net/698369989/buildlog_ubuntu-noble-amd64.kaidan_0.9.1-2_BUILDING.txt.gz

I think disabling that test function should work as workaround.

G.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: kaidan: FTBFS with disabled network

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1056583 [src:kaidan] kaidan: FTBFS with disabled network
Bug #1058510 [src:kaidan] kaidan: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Added tag(s) patch.
Added tag(s) patch.

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

Bug#1058196: marked as done (swift-bench: FTBFS: AttributeError: 'TestUtils' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 11:21:01 +
with message-id 
and subject line Bug#1058196: fixed in swift-bench 1.2.0-7
has caused the Debian Bug report #1058196,
regarding swift-bench: FTBFS: AttributeError: 'TestUtils' object has no 
attribute 'assertEquals'. Did you mean: 'assertEqual'?
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.)


-- 
1058196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift-bench
Version: 1.2.0-5
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):
>  debian/rules build
> make: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> dh build --buildsystem=pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_swift-bench/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_swift-bench/build/tests
> copying tests/test_utils.py -> 
> /<>/.pybuild/cpython3_3.12_swift-bench/build/tests
> copying tests/test_bench.py -> 
> /<>/.pybuild/cpython3_3.12_swift-bench/build/tests
> creating /<>/.pybuild/cpython3_3.12_swift-bench/build/swiftbench
> copying swiftbench/bench.py -> 
> /<>/.pybuild/cpython3_3.12_swift-bench/build/swiftbench
> copying swiftbench/utils.py -> 
> /<>/.pybuild/cpython3_3.12_swift-bench/build/swiftbench
> copying swiftbench/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_swift-bench/build/swiftbench
> running build_scripts
> creating build
> creating build/scripts-3.12
> copying and adjusting bin/swift-bench -> build/scripts-3.12
> copying and adjusting bin/swift-bench-client -> build/scripts-3.12
> changing mode of build/scripts-3.12/swift-bench from 644 to 755
> changing mode of build/scripts-3.12/swift-bench-client from 644 to 755
> I: pybuild base:310: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_swift-bench/build/tests
> copying tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_swift-bench/build/tests
> copying tests/test_utils.py -> 
> /<>/.pybuild/cpython3_3.11_swift-bench/build/tests
> copying tests/test_bench.py -> 
> /<>/.pybuild/cpython3_3.11_swift-bench/build/tests
> creating /<>/.pybuild/cpython3_3.11_swift-bench/build/swiftbench
> copying swiftbench/bench.py -> 
> /<>/.pybuild/cpython3_3.11_swift-bench/build/swiftbench
> copying swiftbench/utils.py -> 
> /<>/.pybuild/cpython3_3.11_swift-bench/build/swiftbench
> copying swiftbench/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_swift-bench/build/swiftbench
> running build_scripts
> creating build/scripts-3.11
> copying and adjusting bin/swift-bench -> build/scripts-3.11
> copying and adjusting bin/swift-bench-client -> build/scripts-3.11
> changing mode of build/scripts-3.11/swift-bench from 644 to 755
> changing mode of build/scripts-3.11/swift-bench-client from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.12_swift-bench/build; python3.12 -m nose 
> -v tests
> test_placeholder (tests.test_bench.TestBench.test_placeholder) ... 
> /usr/lib/python3.12/unittest/case.py:580: RuntimeWarning: TestResult has no 
> addDuration method
>   warnings.warn("TestResult has no addDuration method",
> ok
> test_config_true_value (tests.test_utils.TestUtils.test_config_true_value) 
> ... ok
> test_readconf (tests.test_utils.TestUtils.test_readconf) ... ERROR
> test_readconf_raw (tests.test_utils.TestUtils.test_readconf_raw) ... ERROR
> test_using_http_proxy (tests.test_utils.TestUtils.test_using_http_proxy) ... 
> ok
> 
> ==
> ERROR: test_readconf (tests.test_utils.TestUtils.test_readconf)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.12_swift-bench/build/tests/test_utils.py",
>  line 57, in test_readconf
> self.assertEquals(result, expected)
> ^
> 

Bug#1058739: lyskom-elisp-client: fails to install with Emacs 29: lyskom-elisp-client.el:17452:2: Error: Optimizer error: too much on the stack

[Andreas Beckmann]

Package: lyskom-elisp-client
Version: 0.48+git.20200923.ec349ff4-3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up emacs-gtk (1:29.1+1-5) ...
  update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs 
(emacs) in auto mode
  update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) 
in auto mode
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install lyskom-elisp-client for emacs
  install/lyskom-elisp-client: Handling install of emacsen flavor emacs
  install/lyskom-elisp-client: byte-compiling for emacs
  Please wait...
  
  In toplevel form:
  lyskom-elisp-client.el:1119:2: Warning: defvar 
`kom-pick-text-no-strategy-alist' docstring wider than 80 characters
  lyskom-elisp-client.el:3039:2: Warning: defvar `lyskom-text-buttons' 
docstring wider than 80 characters
  lyskom-elisp-client.el:4385:2: Warning: defconst `lyskom-server-features' 
docstring has wrong usage of unescaped single quotes (use \= or different 
quoting)
  lyskom-elisp-client.el:6158:2: Warning: `string-make-unibyte' is an obsolete 
function (as of 26.1); use `encode-coding-string'.
  lyskom-elisp-client.el:6333:2: Warning: More than one doc string
  
  In lyskom-get-menu-string:
  lyskom-elisp-client.el:6919:2: Warning: docstring has wrong usage of 
unescaped single quotes (use \= or different quoting)
  lyskom-elisp-client.el:17452:2: Error: Optimizer error: too much on the stack
  ERROR: install script from lyskom-elisp-client package failed
  dpkg: error processing package emacs-gtk (--configure):
   installed emacs-gtk package post-installation script subprocess returned 
error exit status 1
  dpkg: dependency problems prevent configuration of emacs:
   emacs depends on emacs-gtk (>= 1:27.1) | emacs-pgtk (>= 1:27.1) | 
emacs-lucid (>= 1:27.1) | emacs-nox (>= 1:27.1); however:
Package emacs-gtk is not configured yet.
Package emacs-pgtk is not installed.
Package emacs-lucid is not installed.
Package emacs-nox is not installed.
  
  dpkg: error processing package emacs (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of lyskom-elisp-client:
   lyskom-elisp-client depends on emacs; however:
Package emacs is not configured yet.
Package emacs-gtk which provides emacs is not configured yet.
  
  dpkg: error processing package lyskom-elisp-client (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-13) ...
  Processing triggers for install-info (7.1-2) ...
  Errors were encountered while processing:
   emacs-gtk
   emacs
   lyskom-elisp-client


cheers,

Andreas


lyskom-elisp-client_0.48+git.20200923.ec349ff4-3.log.gz
Description: application/gzip

Processed: Bug#1058196 marked as pending in swift-bench

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058196 [src:swift-bench] swift-bench: FTBFS: AttributeError: 'TestUtils' 
object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?
Added tag(s) pending.

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

Bug#1058196: marked as pending in swift-bench

[Philippe Seraphin]

Control: tag -1 pending

Hello,

Bug #1058196 in swift-bench 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/openstack-team/services/swift-bench/-/commit/422e8a2f8b3bc76e2708c219f339c1010aab98c8


* Add python 3.12 patches (Closes: #1058196):
- py3.12-fix-AssertEquals.patch
- py3.12-fix-readfp.path


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058196

Bug#1058678: blt: disable jpeg support

[Helmut Grohne]

Hi Sergei,

On Thu, Dec 14, 2023 at 06:22:45PM +0300, Sergei Golovan wrote:
> I'm sorry, I wasn't aware about these implications. Meanwhile, I'm
> setting this bug
> severity to serious and will fix it as soon as possible.

Thank you. I agree that this is surprising at times. Hence, I'm looking
after this. :)

> > I suggest that you temporarily revert this change in unstable to restore
> > the ability to bootstrap Debian from source.
> 
> I'll do that.

Thank you.

> Can someone investigate if blt is really necessary for Python now?

This is a very difficult question I fear. A very common approach for
dropping dependencies is using reproducible builds as a QA tool: If the
package builds and has the same output artifact with a dependency
removed, it probably isn't used during build (but maybe used for
testing). Please keep in mind that any build dependency annotated
 is irrelevant to bootstrapping problems, so this is quite
powerful normally.

Unfortunately, Python is not very reproducible. It embeds the build path
into lots of places. It uses profile guided optimization and even if you
build with DEB_BUILD_OPTIONS=nopgo, you still get lots of variations.

The python$VER package used to contain tk, but since a while we have
python3-stdlib-extensions. It feels fairly natural that python$VER
should no longer need tk and blt. I went a head and tried reproducing
this. On the good side, that build succeeded. The resulting artifacts
still differed a lot from an unmodified build and in particular, the
_uuid.so and _nis.so module went missing. The former probably is due to
something from tk or blt issuing a dependency on uuid-dev and with those
packages removed, uuid-dev was no longer pulled. I have not found a
probably cause for the nis module.

So from the outset it seems that breaking the cycle at Python is
plausible, but it needs more validation work. Possibly, blt is still
being used for testing the build and that's fine as long as it is
annotated . (Do note that a failure to build from source with
the nocheck profile enabled is considered to be an rc bug since trixie.)

> Again, I'll revert the change shortly, but is there any way I can help
> with untangling Python from blt?

If you are up for doing that work, I definitely appreciate that. As
detailed earlier, this probably involves changing python's Build-Depends
only. Adding uuid-dev and probably other packages that currently are
implied and then dropping or annotating blt-dev and probably also
tk-dev. That validation work is what takes time. At a bare minimum, one
needs to fix a build path and use DEB_BUILD_OPTIONS=nopgo, but I suspect
that even that isn't enough to get variations down to a manageable
level.

I'm all for removing blt from the bootstrap set in general. Though keep
in mind that you won't be removing it from python3-stdlib-extensions and
python3-tk has 500+ build-rdeps, so your luck with being removed from
bootstrap may vary.

Helmut

Bug#1058252: marked as done (pynn: FTBFS: AttributeError: 'SpaceTest' object has no attribute 'assert_'. Did you mean: 'assertIn'?)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 10:35:18 +
with message-id 
and subject line Bug#1058252: fixed in pynn 0.10.1-3
has caused the Debian Bug report #1058252,
regarding pynn: FTBFS: AttributeError: 'SpaceTest' object has no attribute 
'assert_'. Did you mean: 'assertIn'?
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.)


-- 
1058252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pynn
Version: 0.10.1-2
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):
> make[1]: Entering directory '/<>'
> cp -a test test_save
> rm -f \
> test/system/scenarios/__init__.py \
> test/unittests/test_brian.py \
> test/system/test_brian.py \
> test/system/test_brian2.py \
> test/system/test_hardware_brainscales.py \
> test/system/test_moose.py \
> test/system/scenarios/registry.py \
> test/system/test_serialization.py \
> test/system/test_nest.py \
> test/system/test_neuroml.py \
> test/system/test_neuron.py \
> test/unittests/test_random.py \
> test/unittests/test_neuron.py
> dh_auto_test
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_pynn/build; 
> python3.12 -m nose -v test
> test__add__assembly 
> (unittests.test_assembly.AssemblyTest.test__add__assembly) ... 
> /usr/lib/python3.12/unittest/case.py:580: RuntimeWarning: TestResult has no 
> addDuration method
>   warnings.warn("TestResult has no addDuration method",
> ok
> test__add__population 
> (unittests.test_assembly.AssemblyTest.test__add__population) ... ok
> test__homogeneous_synapses 
> (unittests.test_assembly.AssemblyTest.test__homogeneous_synapses) ... ok
> test__len__ (unittests.test_assembly.AssemblyTest.test__len__) ... ok
> test__non_homogeneous_synapses 
> (unittests.test_assembly.AssemblyTest.test__non_homogeneous_synapses) ... ok
> test_add_inplace_assembly 
> (unittests.test_assembly.AssemblyTest.test_add_inplace_assembly) ... ok
> test_add_inplace_population 
> (unittests.test_assembly.AssemblyTest.test_add_inplace_population) ... ok
> test_add_invalid_object 
> (unittests.test_assembly.AssemblyTest.test_add_invalid_object) ... ok
> test_all_cells (unittests.test_assembly.AssemblyTest.test_all_cells) ... ok
> test_all_iterator (unittests.test_assembly.AssemblyTest.test_all_iterator) 
> ... ok
> test_conductance_based 
> (unittests.test_assembly.AssemblyTest.test_conductance_based) ... ok
> test_create_with_non_population_should_raise_Exception 
> (unittests.test_assembly.AssemblyTest.test_create_with_non_population_should_raise_Exception)
>  ... ok
> test_create_with_one_population 
> (unittests.test_assembly.AssemblyTest.test_create_with_one_population) ... ok
> test_create_with_two_populations 
> (unittests.test_assembly.AssemblyTest.test_create_with_two_populations) ... ok
> test_create_with_zero_populations 
> (unittests.test_assembly.AssemblyTest.test_create_with_zero_populations) ... 
> ok
> test_describe (unittests.test_assembly.AssemblyTest.test_describe) ... ok
> test_first_and_last_id 
> (unittests.test_assembly.AssemblyTest.test_first_and_last_id) ... ok
> test_getSpikes (unittests.test_assembly.AssemblyTest.test_getSpikes) ... ok
> test_get_data_with_gather 
> (unittests.test_assembly.AssemblyTest.test_get_data_with_gather) ... ok
> test_get_gsyn (unittests.test_assembly.AssemblyTest.test_get_gsyn) ... ok
> test_get_multiple_homogeneous_params_with_gather 
> (unittests.test_assembly.AssemblyTest.test_get_multiple_homogeneous_params_with_gather)
>  ... ok
> test_get_multiple_inhomogeneous_params_with_gather 
> (unittests.test_assembly.AssemblyTest.test_get_multiple_inhomogeneous_params_with_gather)
>  ... ok
> test_get_multiple_params_no_gather 
> (unittests.test_assembly.AssemblyTest.test_get_multiple_params_no_gather) ... 
> ok
> test_get_population 
> (unittests.test_assembly.AssemblyTest.test_get_population) ... ok
> test_get_sequence_param 
> (unittests.test_assembly.AssemblyTest.test_get_sequence_param) ... ok
> test_get_single_param_with_gather 
> (unittests.test_assembly.AssemblyTest.test_get_single_param_with_gather) ... 
> ok
> test_get_v (unittests.test_assembly.AssemblyTest.test_get_v) ... ok
> test_getitem_array (unittests.test_assembly.AssemblyTest.test_getitem_array) 
> ... ok
> test_getitem_int (unittests.test_assembly.AssemblyTest.test_getitem_int) ... 
> ok
> test_getitem_slice 

Bug#1058678: marked as done (blt: disable jpeg support)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 10:34:13 +
with message-id 
and subject line Bug#1058678: fixed in blt 2.5.3+dfsg-7
has caused the Debian Bug report #1058678,
regarding blt: disable jpeg support
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.)


-- 
1058678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blt
Version: 2.5.3+dfsg-6
Severity: important
User: helm...@debian.org
Usertags: rebootstrap

Hi Sergei,

did you know that blt participates in architecture bootstrap? It's
required for building the Python interpreter for instance and thus far,
this has all worked out well, but now you added a build dependency on
libjpeg-dev. libjpeg-turbo in turn Build-Depends on default-jdk and
while it builds its -java package as an Arch:all package, the jdk
actually is being used as it stuffs jni symbols into the main library,
so really the Arch:any package already requires default-jdk. So now we
have a path from Python to Java. We also have a path from Java to Python
already, so your blt upload introduces a bootstrap dependency cycle and
this is bad.

I suggest that you temporarily revert this change in unstable to restore
the ability to bootstrap Debian from source.

Then let's figure out the best way to break the cycle before re-enabling
jpeg support. This has mostly worked earlier, because libjpeg-turbo was
not part of the bootstrap set. Even adding libjpeg-turbo seems fine in
principle, but Java less so. As explained earlier, breaking the cycle
between libjpeg-turbo and Java is harder, because there are
Java-specific symbols in the main library. Making jpeg support optional
in blt seems similarly impractical to me. This is definitely more work
than just enabling jpeg support unfortunately. Do you have more ideas?

Helmut
--- End Message ---
--- Begin Message ---
Source: blt
Source-Version: 2.5.3+dfsg-7
Done: Sergei Golovan 

We believe that the bug you reported is fixed in the latest version of
blt, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated blt 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, 15 Dec 2023 13:10:25 +0300
Source: blt
Architecture: source
Version: 2.5.3+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Sergei Golovan 
Changed-By: Sergei Golovan 
Closes: 1058678
Changes:
 blt (2.5.3+dfsg-7) unstable; urgency=medium
 .
   * Disable JPEG support because enabling it interferences with Debian
 bootstrap procedure by adding new dependency on jpeg-turbo
 (closes: #1058678).
Checksums-Sha1:
 871063eccf3ffcfa41401343d31db03670a6387f 1997 blt_2.5.3+dfsg-7.dsc
 49b75798d640adc2a5ba73ec1dfc94a73c185cd6 58176 blt_2.5.3+dfsg-7.debian.tar.xz
 13800fb229e406d8b3ddce9b6915601c1fa090b3 8483 blt_2.5.3+dfsg-7_amd64.buildinfo
Checksums-Sha256:
 94b29778632cebbbc676cdf90345e94419c9b3b806c31c87405ad4ecc5e96e56 1997 
blt_2.5.3+dfsg-7.dsc
 4289a0d394ed707d9a2a38864e359eee880009c114c19ab4b07b0ed77232a51a 58176 
blt_2.5.3+dfsg-7.debian.tar.xz
 c96ac20c246792f8bc04c187c83d613552f0311748b23313d906d04c024479ab 8483 
blt_2.5.3+dfsg-7_amd64.buildinfo
Files:
 5865def35a306c67b5eff65aeb562d23 1997 devel optional blt_2.5.3+dfsg-7.dsc
 d73247d388a91d0b76f9d170c3878017 58176 devel optional 
blt_2.5.3+dfsg-7.debian.tar.xz
 02bad634d882f4c1f0fe91eb3a8654e0 8483 devel optional 
blt_2.5.3+dfsg-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAmV8JucACgkQTyrk60tj
54ftEA//XQv9kGn0BTHeYCfgri/Csl/8MdliUc7aIA1rmKsd3jLB95+ugSUY+Tfa
KGkHfDW3yolTw5Ju7AVksyxXu69Twg08ul/Qiv0icenzy80FyuwRe+UBMBZ4cwB5
RBe92Xi3hMTfTwMu8pQpdxmTMRhDmGuDLAR+XqpswOoRSAPH7hhJdtcvnKpC/2Oe
7uDJ/sydWFyLIszAoO7SCxgj58KkPmVu09Q2VyL3mHFOGFpy8dLjWhOePK0syrXZ
P+mkTBc9Hc8PV+mjz8OEczAKCOJkKdQ09DP5N0QSOLS7izr7nTiGvyvEz/+Cvb6s
+JgRxWCGa4MW/amYC7XFC6Wh6SS57hERgHCqzaeS/P14Bt0kje0n1A3pBgNHHj+b
+kG1AmCrdAWtjq70ROOs+Sd8c62xTwuzGEiXwXcYaoo010qwS/9GUzH8w5JSPnYx
bv/Wyrgem4ciqnvYZCJ6Bif2tWrUaqnQRhNyxX0aA7Uhdvzwfxa4pGu4pcwRjdyv

Processed: Bug#1058323 marked as pending in python-magnumclient

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058323 [src:python-magnumclient] python-magnumclient: FTBFS: TypeError: 
HTTPSConnection.__init__() got an unexpected keyword argument 'key_file'
Added tag(s) pending.

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

Bug#1058323: marked as pending in python-magnumclient

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1058323 in python-magnumclient 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/openstack-team/clients/python-magnumclient/-/commit/4df7db233712e77e73fd1fd0bf07b4ef5fc4b9ec


* Add py3.12-key_file-and-cert_file-must-use-context.patch
(Closes: #1058323).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058323

Bug#1058252: marked as pending in pynn

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1058252 in pynn 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/med-team/pynn/-/commit/ea997cc5c80af982868d15c07a3076f76c1d2b6d


python3.12.patch: new: fix test with python3.12.

Closes: #1058252


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058252

Processed: Bug#1058252 marked as pending in pynn

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058252 [src:pynn] pynn: FTBFS: AttributeError: 'SpaceTest' object has no 
attribute 'assert_'. Did you mean: 'assertIn'?
Ignoring request to alter tags of bug #1058252 to the same tags previously set

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

Processed: Bug#1058252 marked as pending in pynn

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058252 [src:pynn] pynn: FTBFS: AttributeError: 'SpaceTest' object has no 
attribute 'assert_'. Did you mean: 'assertIn'?
Added tag(s) pending.

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

Bug#1058252: marked as pending in pynn

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1058252 in pynn 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/med-team/pynn/-/commit/ea997cc5c80af982868d15c07a3076f76c1d2b6d


python3.12.patch: new: fix test with python3.12.

Closes: #1058252


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058252

Processed (with 2 errors): Re: Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

[Debian Bug Tracking System]

Processing control commands:

> blocked -1 by 1058621
Unknown command or malformed arguments to command.

> merge -1 1057590
Bug #1058281 [src:octave-netcdf] octave-ncarray: FTBFS: make: *** 
[debian/rules:5: binary] Error 139
Unable to merge bugs because:
blockedby of #1057589 is '1058621' not ''
blockedby of #1057590 is '1058621' not ''
Failed to merge 1058281: Did not alter merged bugs.


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

Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

[Rafael Laboissière]

Control: blocked -1 by 1058621
Control: merge -1 1057590

I hope that the merge goes well this time.

Best,

Rafael Laboissière

Bug#1055692: marked as done (macs ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 08:55:06 -0100
with message-id 

and subject line macs ftbfs with Python 3.12
has caused the Debian Bug report #1055692,
regarding macs ftbfs with 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.)


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

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

macs ftbfs with Python 3.12 (note that also cython 3.0.5 was used)

[...]
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py config

Error compiling Cython file:

...
crick_right = right_sum(crick, search_start, window_size)

wtd_list = np.zeros( search_end - search_start + 1, dtype="float32")
i = 0
for j in range(search_start, search_end+1):
wtd_list[i] = max((2 * (watson_left * crick_right)**0.5 - 
watson_right - crick_left),0) # minimum score is 0


 ^


MACS2/IO/CallPeakUnit.pyx:200:93: complex types are unordered
Compiling MACS2/Prob.pyx because it changed.
Compiling MACS2/IO/Parser.pyx because it changed.
Compiling MACS2/Pileup.pyx because it changed.
Compiling MACS2/PeakModel.pyx because it changed.
Compiling MACS2/PeakDetect.pyx because it changed.
Compiling MACS2/Signal.pyx because it changed.
Compiling MACS2/IO/PeakIO.pyx because it changed.
Compiling MACS2/IO/BedGraphIO.pyx because it changed.
Compiling MACS2/IO/FixWidthTrack.pyx because it changed.
Compiling MACS2/IO/PairedEndTrack.pyx because it changed.
Compiling MACS2/IO/BedGraph.pyx because it changed.
Compiling MACS2/IO/ScoreTrack.pyx because it changed.
Compiling MACS2/IO/CallPeakUnit.pyx because it changed.
[ 1/13] Cythonizing MACS2/IO/BedGraph.pyx
[ 2/13] Cythonizing MACS2/IO/BedGraphIO.pyx
[ 3/13] Cythonizing MACS2/IO/CallPeakUnit.pyx
Traceback (most recent call last):
  File "/<>/setup.py", line 102, in 
main()
  File "/<>/setup.py", line 98, in main
ext_modules = cythonize( ext_modules ),
  
  File "/usr/lib/python3/dist-packages/Cython/Build/Dependencies.py", 
line 1154, in cythonize

cythonize_one(*args)
  File "/usr/lib/python3/dist-packages/Cython/Build/Dependencies.py", 
line 1321, in cythonize_one

raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: MACS2/IO/CallPeakUnit.pyx
E: pybuild pybuild:395: configure: plugin distutils failed with: exit 
code=1: python3.12 setup.py config
dh_auto_configure: error: pybuild --configure -i python{version} -p 
"3.12 3.11" returned exit code 13

make: *** [debian/rules:14: binary] Error 25
--- End Message ---
--- Begin Message ---
As noted above, macs 2.2.9.1-1+b1 built successfully with cython3 0.29.36-3.1.
The build failure with cython 3.0.x is #1056813.--- End Message ---

Processed: Re: astroquery: FTBFS: ModuleNotFoundError: No module named 'imp'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #1057543 [src:astroquery] astroquery: FTBFS: ModuleNotFoundError: No module 
named 'imp'
Added tag(s) fixed-upstream.

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

Bug#1057543: astroquery: FTBFS: ModuleNotFoundError: No module named 'imp'

[Ole Streicher]

Control: tags -1 fixed-upstream

The problem here is that the python3-astropy-helpers package is not 
ready for Python 3.12, see #1058104.


https://bugs.debian.org/1058104

Astropy-helpers is EOL upstream, therefore I think we should no longer 
rely on that package.


For astroquery, there is a merged Pull Request for Python 3.12 compatibility

https://github.com/astropy/astroquery/pull/2838

This includes switching astropy-helpers to a personally-maintained 
version. IMO the best way would be to include that directly in the 
astroquery package until astroquery gets rid of astropy-helpers completely.


Cheers

Ole

Bug#1058698: mozilla-devscripts should be removed from testing/unstable

[Carsten Schoenert]

Hello Mechtilde,

Am Thu, Dec 14, 2023 at 07:09:16PM +0100 schrieb Mechtilde:
> Hello Mathias,
> 
> thanks for the hint,
> 
> At this time mozilla-devscript is needed when you want to build
> Mozilla-AddOns from the *.xpi.
> 
> So we need to elaborate another way to do it.

I've dropped mozilla-devscripts as an dependency for thunderbird long
ago.
To get the l10n XPI files creatable I picked up the main part of
mozilla-devscripts, the shell script xpi-pack.sh, and placed it within
the debian/ folder.

https://salsa.debian.org/mozilla-team/thunderbird/-/commit/b31360b05e048826571245a2fda26d56592da435

We call this shell script then directly in debian/rules, it's quite
simple and straight forward to use.

https://salsa.debian.org/mozilla-team/thunderbird/-/blob/debian/sid/debian/rules#L134

I think shipping this shell script now in only a few source packages is
acceptable, otherwise we would need to fix mozilla-devscripts with a bit
effort for not really big gain.

Another option could be to move the XPI package build functionaliy into
some debhelper package, but I haven't looked really seriously into any
option.

Regards
Carsten

Bug#1058150: marked as done (sixer: FTBFS: AssertionError: '/<>/sixer.py:44[104 chars]")\n' != '')

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2023 09:20:02 +
with message-id 
and subject line Bug#1058150: fixed in sixer 1.6-5
has caused the Debian Bug report #1058150,
regarding sixer: FTBFS: AssertionError: '/<>/sixer.py:44[104 
chars]")\n' != ''
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.)


-- 
1058150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sixer
Version: 1.6-4
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):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; for pyvers in 3.12 3.11; do \
>   python$pyvers tests.py ; \
> done
> /<>/sixer.py:445: SyntaxWarning: invalid escape sequence '\.'
>   XRANGE_REGEX = re.compile("(? ...F.FF.
> ==
> FAIL: test_nonexistent_operation 
> (__main__.TestProgram.test_nonexistent_operation)
> --
> Traceback (most recent call last):
>   File "/<>/tests.py", line 1396, in test_nonexistent_operation
> self.assertEqual(stderr, '')
> AssertionError: '/<>/sixer.py:44[104 chars]")\n' != ''
> - /<>/sixer.py:445: SyntaxWarning: invalid escape sequence '\.'
> -   XRANGE_REGEX = re.compile("(? 
> 
> ==
> FAIL: test_patch_dir (__main__.TestProgram.test_patch_dir)
> --
> Traceback (most recent call last):
>   File "/<>/tests.py", line 1357, in test_patch_dir
> stdout = self.run_sixer(2, path)
>  ^^^
>   File "/<>/tests.py", line 1328, in run_sixer
> self.assertEqual(stderr, '')
> AssertionError: '/<>/sixer.py:44[104 chars]")\n' != ''
> - /<>/sixer.py:445: SyntaxWarning: invalid escape sequence '\.'
> -   XRANGE_REGEX = re.compile("(? 
> 
> ==
> FAIL: test_patch_file (__main__.TestProgram.test_patch_file)
> --
> Traceback (most recent call last):
>   File "/<>/tests.py", line 1336, in test_patch_file
> stdout = self.run_sixer(1, tmp.name)
>  ^^^
>   File "/<>/tests.py", line 1328, in run_sixer
> self.assertEqual(stderr, '')
> AssertionError: '/<>/sixer.py:44[104 chars]")\n' != ''
> - /<>/sixer.py:445: SyntaxWarning: invalid escape sequence '\.'
> -   XRANGE_REGEX = re.compile("(? 
> 
> --
> Ran 44 tests in 7.738s
> 
> FAILED (failures=3)
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/sixer_1.6-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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: sixer
Source-Version: 1.6-5
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
sixer, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated sixer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it 

Processed: Bug #1055697: forwarded to upstream commit that fix the FTBFS

[Debian Bug Tracking System]

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

> forwarded 1055697 
> https://github.com/coin3d/pivy/commit/d3faf04b8770c60ca9b2186059ee82201e3620ad
Bug #1055697 [src:pivy] pivy ftbfs with Python 3.12
Set Bug forwarded-to-address to 
'https://github.com/coin3d/pivy/commit/d3faf04b8770c60ca9b2186059ee82201e3620ad'.
> thanks
Stopping processing here.

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

Processed: 1058441 is forwarded

[Debian Bug Tracking System]

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

> forwarded 1058441 https://github.com/python-openxml/python-docx/issues/1300
Bug #1058441 [src:python-docx] python-docx: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/python-openxml/python-docx/issues/1300'.
>
End of message, stopping processing here.

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