Bug#1060894: marked as done (pylint broken due to version 3 of python3-astroid)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2024 07:34:28 +
with message-id 
and subject line Bug#1060894: fixed in pylint 3.0.3-1
has caused the Debian Bug report #1060894,
regarding pylint broken due to version 3 of python3-astroid
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.)


-- 
1060894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pylint
Version: 2.17.4-1
Severity: grave
Justification: renders package unusable

pylint dies when given anything, try with the simple program "a = 1", se
stacktrace below.
Downgrading python3-astroid from 3.0.2-1 to 2.15.6-1 fixes the problem.

I'm not sure if the problem lies in pylint or astroid so feel
free to move this report to python3-astroid if needed. :-)

-

Traceback (most recent call last):
  File "/bin/pylint", line 8, in 
sys.exit(run_pylint())
 
  File "/usr/lib/python3/dist-packages/pylint/__init__.py", line 36, in 
run_pylint
PylintRun(argv or sys.argv[1:])
  File "/usr/lib/python3/dist-packages/pylint/lint/run.py", line 157, in 
__init__
linter.load_default_plugins()
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 369, in 
load_default_plugins
checkers.initialize(self)
  File "/usr/lib/python3/dist-packages/pylint/checkers/__init__.py", line 136, 
in initialize
register_plugins(linter, __path__[0])
  File "/usr/lib/python3/dist-packages/pylint/utils/utils.py", line 204, in 
register_plugins
module = modutils.load_module_from_file(
 ^^^
  File "/usr/lib/python3/dist-packages/astroid/modutils.py", line 235, in 
load_module_from_file
return load_module_from_modpath(modpath)
   ^
  File "/usr/lib/python3/dist-packages/astroid/modutils.py", line 220, in 
load_module_from_modpath
return load_module_from_name(".".join(parts))
   ^^
  File "/usr/lib/python3/dist-packages/astroid/modutils.py", line 194, in 
load_module_from_name
module = importlib.import_module(dotted_name)
 
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1204, in _gcd_import
  File "", line 1176, in _find_and_load
  File "", line 1147, in _find_and_load_unlocked
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File 
"/usr/lib/python3/dist-packages/pylint/checkers/refactoring/__init__.py", line 
16, in 
from pylint.checkers.refactoring.refactoring_checker import 
RefactoringChecker
  File 
"/usr/lib/python3/dist-packages/pylint/checkers/refactoring/refactoring_checker.py",
 line 36, in 
nodes.TryExcept, nodes.TryFinally, nodes.While, nodes.For, nodes.If
^^^
AttributeError: module 'astroid.nodes' has no attribute 'TryExcept'



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

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

Versions of packages pylint depends on:
ii  python33.11.6-1
ii  python3-astroid3.0.2-1
ii  python3-dill   0.3.7-1
ii  python3-isort  5.6.4-1
ii  python3-logilab-common 1.9.8-1
ii  python3-mccabe 0.7.0-1
ii  python3-platformdirs   4.1.0-1
ii  python3-setuptools 68.1.2-2
ii  python3-tomli  2.0.1-2
ii  python3-tomlkit0.12.3-1
ii  python3-typing-extensions  4.7.1-2

Versions of packages pylint recommends:
ii  python3-tk  3.11.5-1

Versions of packages pylint suggests:
pn  pylint-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pylint
Source-Version: 3.0.3-1
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
pylint, 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 

Bug#1056439: marked as done (pylint's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2024 07:34:28 +
with message-id 
and subject line Bug#1056439: fixed in pylint 3.0.3-1
has caused the Debian Bug report #1056439,
regarding pylint'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.)


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

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

pylint's autopkg tests fail with Python 3.12, multiple failures.

complete build log at
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/p/pylint/20231118_183958_42d45@/log.gz
--- End Message ---
--- Begin Message ---
Source: pylint
Source-Version: 3.0.3-1
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
pylint, 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.
Sandro Tosi  (supplier of updated pylint 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: Wed, 17 Jan 2024 02:11:07 -0500
Source: pylint
Architecture: source
Version: 3.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 1032687 1056439 1058230 1058718 1060894
Changes:
 pylint (3.0.3-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release; Closes: #1058718, #1058230, #1056439
   * stop building the -doc package, and so drop patches too
   * debian/pylint.install
 - delete, no longer needed
   * debian/control
 - add git, platformdirs to b-d, needed by tests
 - bump deps on astroid to >= 3.0.1; Closes: #1060894
   * update github organization from PyCQA to pylint-dev
   * debian/rules
 - re-enable some tests now fixed upstream
 .
   [ Nicolas Boulenguez ]
   * debian/pylint.conffiles
 - remove emacs script on upgrade. Closes: #1032687
Checksums-Sha1:
 48cdd824397117b6ea9750784bf72b3741927327 2308 pylint_3.0.3-1.dsc
 0c47cb971ac9d1ae037dcf34b93bc548a97c8712 1046780 pylint_3.0.3.orig.tar.xz
 3f789f3eae34e9a0af845e6787ac02cab70a7d4e 21532 pylint_3.0.3-1.debian.tar.xz
 64f16b58c18dafb3813c2b60b98eaf0ea795b310 9615 pylint_3.0.3-1_source.buildinfo
Checksums-Sha256:
 ec593c57b1d24da346f0481073421516ae7326ce241db46120056e75b8cb423f 2308 
pylint_3.0.3-1.dsc
 af4872afcd02676bc25214dc2b583f8722e6adb844a96c72e91d5eef71acfae9 1046780 
pylint_3.0.3.orig.tar.xz
 840cf45b4b19bc8e5ac0c6953dcf49d78b5a7c6f2012459bf36b138dbee315cf 21532 
pylint_3.0.3-1.debian.tar.xz
 f633e2d9945f9c7054fa3c6fbdaebe7a17a60cd95a0c6295e29188f8e7c6ae0f 9615 
pylint_3.0.3-1_source.buildinfo
Files:
 491763b72929df5a26c7229e50cf15a0 2308 python optional pylint_3.0.3-1.dsc
 d1f84832a684d7885248a5ff3fe1102e 1046780 python optional 
pylint_3.0.3.orig.tar.xz
 757037a1a3ce3e444fe48dcbb8da144b 21532 python optional 
pylint_3.0.3-1.debian.tar.xz
 ac8675dcc7f4f1b2aed3aac22eee2e31 9615 python optional 
pylint_3.0.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmWnfagACgkQh588mTgB
qU/D4Q//Srp7E4PbJPnTU86cip8So6qNHNX06WE7e4Ig+tU1s3ku01eRcfTIVXPi
Ofb8WKhLxaFQ9C46/wEBsy7HwhlJWdBe04tcFqd+PkAgXPJ7oaBZf1XZ+ztI8vEi
gt/3hFNbkjyqzYvnXbGRCxWLCEVrogmUk/svoWvZUzWRnueN2P5xEJp8UaPLSN8P
OhlXLPWCBDZRnGPBWLfilGBXvD/y9np3MsNDB7AEuGSQi/5/yZNN+80f9tQnXPoq
XbONBbKA+StxjVkcevgYZYhSUV0A7FADv3cF9YUKQVTPkCtH8pdCSRXsEM6alHgx
rbLohskrSCXFfF2Ke66iOvOqDSDYVdCX03pip1DgGWsRAaMExK2+LPGImxCYVKXM
W2hckh+kCMCYRW0gkrvfTdS0ZkPw5Y3obtpFJYTL2jOUY7NJefodHqDc0M5oArMF
2pF/t6JBq/KI3DhrGICQFR5nOtAtiJ3iGABTkdndBkDA9SSX4oct6JGdn7rfaztn
oPZ+yvK1dFaFKjfbRMacGUgz0MjjVfA0zRgNVtaRIkFkE0jvmVkCx2HFOIuJsBAb
kl8j/hpnFHM4/3ivkUL7i3DeI4lMr9A5i756oaNP2zB996jMm3igu4eK/S2FBiVX
RLXiuEB21yc/3hiEegXIqKUplyW2+Vekjnqws7wyC0qqOmXX3nM=
=9rRj
-END PGP SIGNATURE End Message ---

Bug#1061049: libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6"

[Sébastien Villemot]

Hi Dima,

Le mardi 16 janvier 2024 à 15:06 -0800, Dima Kogan a écrit :
> Hi. I'm chasing down
> 
>   http://bugs.debian.org/1060986
> 
> The problem is that mrcal uses libdogleg, which contains
> 
>   typedef struct
>   {
> cholmod_common  common;
> 
>   } dogleg_solverContext_t;
> 
> The existing "libdogleg2" package was built against libsuitesparse-dev
> 7.3, so it must be linked with packages that use that ABI. But in
> suitesparse 7.4 the cholmod_common structure has a new member at the
> end:
> 
> FILE *blas_dump ;  // only used if CHOLMOD is compiled with -DBLAS_DUMP
> 
> This is in CHOLMOD/Include/cholmod.h
> 
> This extra member changes sizeof(cholmod_common), which changes the ABI,
> causing the crash. One way to fix this is to bump the SONAME of
> libcholmod.

I was indeed suspecting an ABI break in suitesparse, after having
noticed unexpected autopkgtest failures.

Thanks for investigating and finding the cause of the problem, you
saved me a lot of time!

I’ll report this upstream and fix it properly in Debian.

Best wishes,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Processed: limit source to pylint, tagging 1058230

[Debian Bug Tracking System]

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

> limit source pylint
Limiting to bugs with field 'source' containing at least one of 'pylint'
Limit currently set to 'source':'pylint'

> tags 1058230 + pending
Bug #1058230 [src:pylint] pylint: FTBFS: AttributeError: 'TreeRebuilder' object 
has no attribute 'visit_typealias'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1060751: marked as done (atril: CVE-2023-51698)

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2024 06:04:09 +
with message-id 
and subject line Bug#1060751: fixed in atril 1.26.1-4
has caused the Debian Bug report #1060751,
regarding atril: CVE-2023-51698
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.)


-- 
1060751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atril
Version: 1.26.1-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for atril.

CVE-2023-51698[0]:
| Atril is a simple multi-page document viewer. Atril is vulnerable to
| a critical Command Injection Vulnerability. This vulnerability gives
| the attacker immediate access to the target system when the target
| user opens a crafted document or clicks on a crafted link/URL using
| a maliciously crafted CBT document which is a TAR archive. A patch
| is available at commit ce41df6.


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-51698
https://www.cve.org/CVERecord?id=CVE-2023-51698
[1] 
https://github.com/mate-desktop/atril/security/advisories/GHSA-34rr-j8v9-v4p2
[2] 
https://github.com/mate-desktop/atril/commit/ce41df6467521ff9fd4f16514ae7d6ebb62eb1ed

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: atril
Source-Version: 1.26.1-4
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated atril 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: Wed, 17 Jan 2024 06:41:57 +0100
Source: atril
Architecture: source
Version: 1.26.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team 
Changed-By: Mike Gabriel 
Closes: 1060751
Changes:
 atril (1.26.1-4) unstable; urgency=medium
 .
   * debian/patches:
 + Add 0001-Use-a-blank-line-at-most.patch and 
0002-comics-Use-libarchive-to-
   unpack-documents.patch. Use libarchive instead of external command for
   extracing documents (CVE-2023-51698, closes: #1060751).
Checksums-Sha1:
 2d30824a2979a6f68fa2e93a1a881988acd310cf 3111 atril_1.26.1-4.dsc
 70e04897aa2903b422e931ca252fcf8b32bb52a8 45984 atril_1.26.1-4.debian.tar.xz
 14362fbb9b597dfb09d625b635e702c9cc0e559e 17679 atril_1.26.1-4_source.buildinfo
Checksums-Sha256:
 d1750be5de91a7b799ad609deac2c6aa5c33b08676927182a1c4a29a2142b1c1 3111 
atril_1.26.1-4.dsc
 5bf31bbcda9da334d3de7c41a9991f0f02daaead5a0ad27b20016688b02c12ae 45984 
atril_1.26.1-4.debian.tar.xz
 58ea333d7a51088d8e45a3643bf64f82edba7b9096152ac03269f3f6e068afce 17679 
atril_1.26.1-4_source.buildinfo
Files:
 42ce31ed16defdaea4e58a5fb6b967a6 3111 x11 optional atril_1.26.1-4.dsc
 c64258121ff1df6dc097484509abd2e8 45984 x11 optional 
atril_1.26.1-4.debian.tar.xz
 f8bacd72336eca5428e63022366265ce 17679 x11 optional 
atril_1.26.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmWnawoVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxhScP/jOEOnzww0zNr5MkPUhW3ILq22Ge
1S5qZmI9X/FQzjquw49LiumIKyhiOw5ELqLKRv7C90iGggtUTtDWvXvFoA556hLL
oH83GuCITUUAM09QdWfjkKL0n2Tp7l76b/EPIoH9GxI5isPXfG3CKEoL0R8+pDgp
yQqEpi1PVpiJG9HInv+0mcY08dW70XG/jCQbc8mDFuZvGMm6rpA/Xy6cED8UHH6O
ROzed4WfjXU1mKh4q5dB8W33AnMfQsT8FG5ZrfCLB6HcGhZlM/PDfMVnPg3GajZs
6Tj1OnJZjYarur2Z2ZsQo+9fiFRofOSAhE1WEdlbbF1tqmVdguTdbjlKIoRm7vc9
FsYz1JPgR4xpAX6L4BtqUfbodK4EiqfWf9d9bU04GfSezz0qOMXq5MuuOwEkDxo1
JGrbiihKPyU/nBMvDxe91UMFOQrvE4zaJYNWZdbbRTjfU+2a//41Y5mp7W3SZY2g
FS9WH3Bo3KbXt8iQb2nY0oe4mycdfnGcg+KxsTYL/H6T/HWn9gURMIgaG4Rdzhn/
qoKtbDZiO9CF8Kitykys28ga7Sl8FFnke4ehCRe3w/Awq87CwkTnGk7iDv4EFwt3
PqhlFV02idy6trPNxzcnW41CSV66I7sdfU/U7wLwDqB5i0VA/uTvrVZMUGeNrIqt
94lJV4zyEcK99Mp9
=HhS1
-END PGP 

Processed: Bug#1060751 marked as pending in atril

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1060751 [src:atril] atril: CVE-2023-51698
Added tag(s) pending.

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

Bug#1060751: marked as pending in atril

[Mike Gabriel]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-mate-team/atril/-/commit/7f623d75cf14ba506b43baaed99a1157b8cba80a


debian/patches: Add 0001-Use-a-blank-line-at-most.patch and 
0002-comics-Use-libarchive-to-unpack-documents.patch. Use libarchive instead of 
external command for extracing documents (CVE-2023-51698, closes: #1060751).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1060751

Processed: reassign 1060924 to klibc-utils, forcibly merging 1055694 1060924

[Debian Bug Tracking System]

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

> reassign 1060924 klibc-utils
Bug #1060924 [initramfs-tools] update-initramfs: cp: warning: behavior of -n is 
non-portable and may change in future
Bug reassigned from package 'initramfs-tools' to 'klibc-utils'.
No longer marked as found in versions initramfs-tools/0.142.
Ignoring request to alter fixed versions of bug #1060924 to the same values 
previously set
> forcemerge 1055694 1060924
Bug #1055694 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: 
warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
Bug #1056912 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: 
warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
Bug #1059936 [klibc-utils] initramfs-tools: update-initramfs yields "cp: 
warning: behavior of -n is non-portable and may change in future"
Bug #1060336 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: 
warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
Bug #1060924 [klibc-utils] update-initramfs: cp: warning: behavior of -n is 
non-portable and may change in future
1060924 was not blocked by any bugs.
1060924 was not blocking any bugs.
Added blocking bug(s) of 1060924: 1058752
Added indication that 1060924 affects initramfs-tools
Marked as found in versions klibc/2.0.13-2.
Bug #1056912 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: 
warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
Bug #1059936 [klibc-utils] initramfs-tools: update-initramfs yields "cp: 
warning: behavior of -n is non-portable and may change in future"
Bug #1060336 [klibc-utils] /usr/share/initramfs-tools/hooks/klibc-utils: cp: 
warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
Merged 1055694 1056912 1059936 1060336 1060924
> 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
1059936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059936
1060336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060336
1060924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1056439 marked as pending in pylint

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1056439 [src:pylint] pylint's autopkg tests fail with Python 3.12
Added tag(s) pending.

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

Processed: Bug#1060894 marked as pending in pylint

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1060894 [pylint] pylint broken due to version 3 of python3-astroid
Added tag(s) pending.

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

Bug#1060894: marked as pending in pylint

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/pylint/-/commit/0ab4bffee289b85f07912786fee55647fd057bb6


bump deps on astroid to >= 3.0.1; Closes: #1060894


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1060894

Bug#1056439: marked as pending in pylint

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/pylint/-/commit/a9f87948ad62cf32f04ec3a215c97146593c8a91


New upstream release; Closes: #1058718, #1058230, #1056439


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056439

Bug#1059829: Thank you

[Yadd]

On 1/16/24 20:36, Georges Khaznadar wrote:

Hello,

Javascript/Npm are not my cup of tea; so, please receive many thanks
about the help you provided to my poor packaging efforts.

If node-html5-qrcode happens to be dfsg-free, which should be the right
umbrella to host it on salsa.d.o? https://salsa.debian.org/js-team or
https://salsa.debian.org/georgesk ?


Hi,

yes I already push it on js-team/node-html5-qrcode. It is fixed now in 
it and ready to be pushed. Do you want I push it ?



I saw that you managed to let salsa's automaton pass 53 of the upstream
tests, and I would like to learn such magics. Please have you some
useful links about them?


Most of JS Team packages uses dh-sequence-nodejs. To start with it: 
https://wiki.debian.org/Javascript/Tutorial and then pkg-js-tools(7)


However, the changes I did here need a minimum knowledge of npm because 
the package doesn't follow exactly the common way (see dh_auto_install hook)



Best regards,   Georges.


Cheers,
Yadd

Bug#1060994: marked as done (libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir')

[Debian Bug Tracking System]

Your message dated Wed, 17 Jan 2024 02:34:17 +
with message-id 
and subject line Bug#1060994: fixed in libshumate 1.1.2-3
has caused the Debian Bug report #1060994,
regarding libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir'
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.)


-- 
1060994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libshumate
Version: 1.1.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 -- -Dauto_features=enabled
>   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 -Dauto_features=enabled
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: libshumate
> Project version: 1.1.2
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Library m found: YES
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Run-time dependency glib-2.0 found: YES 2.78.3
> Run-time dependency gobject-2.0 found: YES 2.78.3
> Run-time dependency gio-2.0 found: YES 2.78.3
> Run-time dependency cairo found: YES 1.18.0
> Run-time dependency sqlite3 found: YES 3.44.2
> Run-time dependency gtk4 found: YES 4.12.4
> Run-time dependency libsoup-3.0 found: YES 3.4.4
> Run-time dependency gobject-introspection-1.0 found: YES 1.78.1
> Run-time dependency vapigen found: YES 0.56.14
> Run-time dependency sysprof-capture-4 found: YES 45.1
> Build-time dependency gi-docgen found: YES 2023.3
> Program gi-docgen found: YES (/usr/bin/gi-docgen)
> Dependency gio-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-compile-resources found: YES 
> (/usr/bin/glib-compile-resources)
> Configuring shumate-version.h using configuration
> Dependency glib-2.0 found: YES 2.78.3 (cached)
> 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)
> ../shumate/meson.build:213: WARNING: Project targets '>= 0.53.0' but uses 
> feature introduced in '0.55.0': fatal_warnings arg in gnome.generate_gir.
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Program /usr/bin/x86_64-linux-gnu-g-ir-scanner found: YES 
> (/usr/bin/x86_64-linux-gnu-g-ir-scanner)
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Program /usr/bin/x86_64-linux-gnu-g-ir-compiler found: YES 
> (/usr/bin/x86_64-linux-gnu-g-ir-compiler)
> Program vapigen found: YES (/usr/bin/vapigen)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Configuring libshumate.toml using configuration
> Dependency gio-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-compile-resources found: YES 
> (/usr/bin/glib-compile-resources)
> Program valgrind found: NO
> Message: 
> --
> libshumate 1.1.2 (1.0)
> 
>  Demos: false
>  Documentation: true
>  Introspection: true
>   Vala API: true
> 
> Directories:
>prefix: /usr
>includedir: /usr/include
>libdir: /usr/lib/x86_64-linux-gnu
>   datadir: /usr/share
> --
> Build targets in project: 69
> WARNING: Project specifies a minimum meson_version '>= 0.53.0' but uses 
> features which were added in newer versions:
>  * 0.55.0: {'fatal_warnings arg in gnome.generate_gir'}
> 
> libshumate 1.1.2
> 
>   User defined options
> auto_features : enabled
> buildtype : plain
> libdir: lib/x86_64-linux-gnu
> localstatedir : /var
> prefix: /usr
> sysconfdir: /etc
> wrap_mode : nodownload
> python.bytecompile: -1
> 
> Found ninja-1.11.1 at /usr/bin/ninja
> 

Bug#1001643: Bug#1060913: Re: Bug#1060913: RFS: sdaps/1.9.11-0.1 [NMU] [RC] -- scripts for data acquisition with paper-based surveys

[Bo YU]

Hi!

On Tue, Jan 16, 2024 at 10:39 PM Dominik George  wrote:
>
> Hi,
>
> > Here I am not a member of DebianEdu team and told if am not a member
> > of one team there is no reason to do team upload.
> > Ideally, I should contact the team to join in or tell team I am going
> > to fix ftbfs issue.
>
> Whether the maintainer is a team doesn't matter here (it just means I am
> not responsible alone for the lack of updates on the package, haha ;)).
Ah, I just realized you are the maintainer of the package(as
uploader), many thanks for your work.
>
> In general, you always contact the maintainer for every upload before
> doing an NMU, through the address from the package meta-data or by
> sending your changes to the BTS into the bug you are fixing.

Thanks for reminding me about this.
Before submitting an NMU I basically will give it at a glance from
debian tracker to look at the care/upload frequency of this package is
used to determine if the NMU. Because for some packages that lack
care, there are bugs filed in time, but they may not be resolved for a
long time. But this is only from my experience. I should obey Debian
NMU guidance here.


>
> > But I got no response from there(not DebianEdu
> > team) in the past.
>
> Can you point me to message IDs where you requested changes to be
> uploaded?
Sorry, here I mean I asked for some help on IRC.  The package is here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060388

I will ping the maintainer of the package again and will fix some
issue like `UNRELEASE` here.
>
> Ideally, you should just send the changes to the BTS bug you are fixing,
> and tag it "patch".
OKay, no problem. Sometimes the debdiff for new upstream release is
very huge and BTS will drop this.:(

Many Thanks again, TIL.

BR,
Bo
>
> -nik

Processed: Re: Bug#1061004: guestfs-tools: FTBFS: make[6]: *** [Makefile:1723: test-suite.log] Error 1

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.52.0-2
Bug #1061004 [src:guestfs-tools] guestfs-tools: FTBFS: make[6]: *** 
[Makefile:1723: test-suite.log] Error 1
Marked as fixed in versions guestfs-tools/1.52.0-2.

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

Processed: block 1060986 with 1061049

[Debian Bug Tracking System]

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

> block 1060986 with 1061049
Bug #1060986 [src:mrcal] mrcal: FTBFS: make[2]: *** [Makefile.tests:85: 
test-nosampling] Error 1
1060986 was not blocked by any bugs.
1060986 was not blocking any bugs.
Added blocking bug(s) of 1060986: 1061049
> thanks
Stopping processing here.

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

Bug#1061004: guestfs-tools: FTBFS: make[6]: *** [Makefile:1723: test-suite.log] Error 1

[Hilko Bengen]

control: fixed -1 1.52.0-2

Bug#1060966: marked as done (openlp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jan 2024 23:35:36 +
with message-id 
and subject line Bug#1060966: fixed in openlp 3.1.0~rc4-1
has caused the Debian Bug report #1060966,
regarding openlp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 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.)


-- 
1060966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openlp
Version: 3.0.2+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> QT_QPA_PLATFORM=offscreen dh_auto_test
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11_openlp/build; 
> python3.11 -m pytest -k 'not test_load_settings_position_invalid and not 
> test_get_directory_for_language_dir_from_source and not 
> test_get_ip_address_default'
> = test session starts 
> ==
> platform linux -- Python 3.11.7, pytest-7.4.4, pluggy-1.3.0
> PyQt5 5.15.10 -- Qt runtime 5.15.10 -- Qt compiled 5.15.10
> rootdir: /<>
> configfile: setup.cfg
> plugins: qt-4.3.1
> collected 2288 items / 3 deselected / 1 skipped / 2285 selected
> 
> tests/openlp_core/test_app.py ...[  
> 0%]
> tests/openlp_core/test_server.py .   [  
> 0%]
> tests/openlp_core/test_state.py ...  [  
> 1%]
> tests/openlp_core/test_threading.py .[  
> 1%]
> tests/openlp_core/test_version.py ...[  
> 2%]
> tests/openlp_core/api/test_deploy.py ... [  
> 2%]
> tests/openlp_core/api/test_main.py . [  
> 2%]
> tests/openlp_core/api/test_tab.py .  [  
> 3%]
> tests/openlp_core/api/test_websockets.py ..  [  
> 4%]
> tests/openlp_core/api/endpoint/test_controller.py    [  
> 4%]
> tests/openlp_core/api/http_server/test_http.py ..[  
> 4%]
> tests/openlp_core/api/http_server/test_init.py ...   [  
> 4%]
> tests/openlp_core/api/v2/test_controller.py ...FFFF. [  
> 6%]
>  [  
> 6%]
> tests/openlp_core/api/v2/test_core.py F. [  
> 6%]
> tests/openlp_core/api/v2/test_plugins.py ..F..   [  
> 7%]
> tests/openlp_core/api/v2/test_service.py [  
> 7%]
> tests/openlp_core/common/test_actions.py ..  [  
> 8%]
> tests/openlp_core/common/test_applocation.py [  
> 8%]
> tests/openlp_core/common/test_db.py ..   [  
> 8%]
> tests/openlp_core/common/test_handlers.py .  [  
> 8%]
> tests/openlp_core/common/test_httputils.py ..[  
> 9%]
> tests/openlp_core/common/test_i18n.py    [ 
> 10%]
> tests/openlp_core/common/test_init.py .. [ 
> 11%]
> ..   [ 
> 12%]
> tests/openlp_core/common/test_json.py .. [ 
> 13%]
> tests/openlp_core/common/test_mixins.py  [ 
> 13%]
> tests/openlp_core/common/test_network_interfaces.py ..   [ 
> 13%]
> tests/openlp_core/common/test_path.py .  [ 
> 14%]
> tests/openlp_core/common/test_platform.py .  [ 
> 14%]
> tests/openlp_core/common/test_registry.py .. [ 
> 14%]
> tests/openlp_core/common/test_settings.py ...[ 
> 15%]
> tests/openlp_core/common/test_utils.py ...   [ 
> 16%]
> tests/openlp_core/display/test_render.py ..  [ 
> 16%]
> tests/openlp_core/display/test_screens.py    [ 
> 17%]
> tests/openlp_core/display/test_window.py ... [ 
> 18%]
> ..   [ 
> 19%]
> tests/openlp_core/lib/test_db.py 

Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

[Scott Kitterman]

They accepted mariadb 10.11.6 as a proposed update and I rebuilt postfix again.

Updated packages (and the first ones also, note the slightly different revision 
number) at the same location:

https://kitterman.com/debian/

I'm not sure if you'll need to upgrade your mariadb packages.  If so, they can 
currently be found in incoming:

http://incoming.debian.org/debian-buildd/pool/main/m/mariadb/

After the next dinstall they will be available in the bookworm-proposed 
updates repository.  For incoming, you'll need to wget the binaries and use 
dpkg to install them.  For bookworm-proposed-updates, you can use apt with an 
appropriate entry in your sources.list.

Please test and let me know how it goes:

Thanks,

Scott K

On Tuesday, January 16, 2024 3:39:43 PM EST Richard Rosner wrote:
> Good to know. Thanks.
> 
> 
> Am Dienstag, 16. Januar 2024 21:00 CET, schrieb Scott Kitterman
> : So, the magic needed to build the new update
> exceeds my grasp, but it's debian/changelog discusses fixing regressions.
> On that basis, I think the thing to do is reassign the bug to mariadb and
> mark it as affecting postfix. I'll also bring it to the stable release
> manager's attention.
> 
> Scott K
> 
> On Tuesday, January 16, 2024 2:36:23 PM EST Scott Kitterman wrote:
> > Excellent. On that basis, I think blaming mariadb for the regression is
> > appropriate. I see there's another mariadb update pending. If would up for
> > another test, I'd like to see if that update solves the problem. I'll
> > build another set of packages against that and if that works, then we just
> > need to make sure we get that update accepted and rebuild postfix.
> > 
> > Scott K



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

Bug#1061049: libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6"

[Dima Kogan]

Package: libsuitesparse-dev
Version: 1:7.3.1+dfsg-2
Severity: serious
X-Debbugs-Cc: none, Dima Kogan 

Hi. I'm chasing down

  http://bugs.debian.org/1060986

The problem is that mrcal uses libdogleg, which contains

  typedef struct
  {
cholmod_common  common;

  } dogleg_solverContext_t;

The existing "libdogleg2" package was built against libsuitesparse-dev
7.3, so it must be linked with packages that use that ABI. But in
suitesparse 7.4 the cholmod_common structure has a new member at the
end:

FILE *blas_dump ;  // only used if CHOLMOD is compiled with -DBLAS_DUMP

This is in CHOLMOD/Include/cholmod.h

This extra member changes sizeof(cholmod_common), which changes the ABI,
causing the crash. One way to fix this is to bump the SONAME of
libcholmod.

Thanks.

Bug#1060946: closing 1060946

[David Prévot]

close 1060946 1.25.0-2
thanks

Processed: closing 1060946

[Debian Bug Tracking System]

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

> close 1060946 1.25.0-2
Bug #1060946 [src:php-phpstan-phpdoc-parser] php-phpstan-phpdoc-parser: FTBFS: 
TypeError: PhpParser\Lexer\Emulative::__construct(): Argument #1 ($phpVersion) 
must be of type ?PhpParser\PhpVersion, array given, called in 
/<>/tests/PHPStan/Printer/IntegrationPrinterWithPhpParserTest.php 
on line 69
Marked as fixed in versions php-phpstan-phpdoc-parser/1.25.0-2.
Bug #1060946 [src:php-phpstan-phpdoc-parser] php-phpstan-phpdoc-parser: FTBFS: 
TypeError: PhpParser\Lexer\Emulative::__construct(): Argument #1 ($phpVersion) 
must be of type ?PhpParser\PhpVersion, array given, called in 
/<>/tests/PHPStan/Printer/IntegrationPrinterWithPhpParserTest.php 
on line 69
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12

[Nicolas Haller]

Hello Mate,

Thanks for letting us know. I just tried with 2.12~rc1-13 and no luck.
I'll wait for 2.12 and let you know if it fixes my issue.

Thanks,

--
Nicolas Haller

On Mon, 15 Jan 2024 07:51:22 + Mate Kukri  
wrote:

Hello,

Just letting you know that the 2.12 merge is in progress, and GRUB
2.12 (non-rc1) will be available in Debian the (hopefully) not too
distant future.

Mate

On Fri, Jan 12, 2024 at 9:18 PM  wrote:
>
> Good day,
>
> does grub 2.12 (without rc1) help? There are a good pile of fixups
> between rc1 and release. E.g.
> 
https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12=1f5b180742ff2706bc3a696d115ddbc677ec75b9
> or
> 
https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12=67ae3981dc5113e5af3a0539174bcd7eab8f7722
> could help.
>
> Additionally, the ZFS fixes are needed to boot from volumes touched by
> ZFS 2.2 ( https://github.com/openzfs/zfs/issues/13873 ), so migrating to
> 2.12 is helpful in either case.
>
> Best regards,
> Michael Fritscher
>
> On Sat, 25 Nov 2023 17:36:41 -0500 Nicolas Haller
>  wrote:
> > Package: grub-efi-amd64
> > Version: 2.06-13
> > Severity: critical
> > Justification: breaks the whole system
> >
> > Dear Maintainer,
> >
> > My old laptop (Lenovo 11e) runs Sid and all was right before I updated
> > it the other day (I don't do that very often). After that upgrade, GRUB
> > wasn't able to load any kernel with the pretty much generic error
> > "Error: can't load image". The version of GRUB was 2.12~rc1-12.
> > If I try to boot again, GRUB tells me that I need to load the image
> > first (I guess it somehow ignores the linux command and sends that when
> > trying to load the initrd).
> >
> > I tried to reinstall grub, grub-install /dev/sda, update-grub, reinstall
> > the kernel, update-initramfs from the rescue mode but nothing worked.
> > The "file" command was able to read the vmlinuz file and none seemed
> > truncated. The system has one partition with both / and /boot and isn't
> > running out of space.
> > I did not see any error message during those operation besides GRUB
> > saying it wasn't able to update EFI parameters.
> >
> > I don't know if there is a way to get more logs or error message during
> > the boot explaining why it wasn't able to load the image.
> >
> > I tried to get the last version of GRUB from Bookworm, that is
> > 2.06-13, and now I'm able to boot. The kernel version did not change,
> >   the only change I did is to downgrade GRUB (and dependencies apt was
> >   asking for).
> >
> > I'm not sure which GRUB package I should use for reporting so I took the

Bug#1057843:

[Moutaz Elgamel]

moutaz

Bug#1055732: marked as done (fpylll ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jan 2024 22:04:18 +
with message-id 
and subject line Bug#1055732: fixed in fpylll 0.6.0-1
has caused the Debian Bug report #1055732,
regarding fpylll 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.)


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

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

fpylll ftbfs with Python 3.12:

[...]
[14/14] Cythonizing src/fpylll/util.pyx
build/src/fpylll/gmp/pylong.c: In function 
‘__pyx_f_6fpylll_3gmp_6pylong_mpz_get_pylong_large’:
build/src/fpylll/gmp/pylong.c:1281:13: warning: assignment to ‘PyObject 
*’ {aka ‘struct _object *’} from incompatible pointer type ‘PyLongObject 
*’ {aka ‘struct _longobject *’} [-Wincompatible-pointer-types]
 1281 |   __pyx_t_2 = _PyLong_New(__pyx_v_pylong_size); if 
(unlikely(!__pyx_t_2)) __PYX_ERR(0, 43, __pyx_L1_error)

  | ^
build/src/fpylll/gmp/pylong.c:1293:48: error: ‘PyLongObject’ {aka 
‘struct _longobject’} has no member named ‘ob_digit’
 1293 |   (void)(mpz_export(((PyLongObject *)__pyx_v_L)->ob_digit, 
NULL, -1, (sizeof(digit)), 0, __pyx_v_6fpylll_3gmp_6pylong_PyLong_nails, 
__pyx_v_z));

  |^~
build/src/fpylll/gmp/pylong.c: In function 
‘__pyx_f_6fpylll_3gmp_6pylong_mpz_set_pylong’:
build/src/fpylll/gmp/pylong.c:1584:140: error: ‘PyLongObject’ {aka 
‘struct _longobject’} has no member named ‘ob_digit’
 1584 |   mpz_import(__pyx_v_z, __pyx_v_pylong_size, -1, 
(sizeof(digit)), 0, __pyx_v_6fpylll_3gmp_6pylong_PyLong_nails, 
((PyLongObject *)__pyx_v_L)->ob_digit);
  | 


   ^~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:395: build: plugin distutils failed with: exit 
code=1: /usr/bin/python3.12 setup.py build

I: pybuild base:310: /usr/bin/python3 setup.py build
build/src/fpylll/gmp/pylong.c: In function 
‘__pyx_f_6fpylll_3gmp_6pylong_mpz_get_pylong_large’:
build/src/fpylll/gmp/pylong.c:1281:13: warning: assignment to ‘PyObject 
*’ {aka ‘struct _object *’} from incompatible pointer type ‘PyLongObject 
*’ {aka ‘struct _longobject *’} [-Wincompatible-pointer-types]
 1281 |   __pyx_t_2 = _PyLong_New(__pyx_v_pylong_size); if 
(unlikely(!__pyx_t_2)) __PYX_ERR(0, 43, __pyx_L1_error)

  | ^
In function ‘__Pyx_PyInt_From_int(int)’,
inlined from 
‘__pyx_pf_6fpylll_5fplll_3bkz_12BKZReduction_6__call__(__pyx_obj_6fpylll_5fplll_3bkz_BKZReduction*)’ 
at build/src/fpylll/fplll/bkz.cpp:4425:35:
build/src/fpylll/fplll/bkz.cpp:15230:34: warning: ‘__pyx_v_r’ may be 
used uninitialized [-Wmaybe-uninitialized]

15230 | return PyInt_FromLong((long) value);
  |  ^
build/src/fpylll/fplll/bkz.cpp: In function 
‘__pyx_pf_6fpylll_5fplll_3bkz_12BKZReduction_6__call__(__pyx_obj_6fpylll_5fplll_3bkz_BKZReduction*)’:

build/src/fpylll/fplll/bkz.cpp:4098:7: note: ‘__pyx_v_r’ was declared here
 4098 |   int __pyx_v_r;
  |   ^
build/src/fpylll/fplll/svpcvp.cpp: In function ‘PyObject* 
__pyx_pf_6fpylll_5fplll_6svpcvp_shortest_vector(PyObject*, 
__pyx_obj_6fpylll_5fplll_14integer_matrix_IntegerMatrix*, PyObject*, 
int, PyObject*, PyObject*, PyObject*)’:
build/src/fpylll/fplll/svpcvp.cpp:3921:37: warning: comparison of 
integer expressions of different signedness: 
‘std::vector, 
std::allocator > >::size_type’ {aka ‘long 
unsigned int’} and ‘Py_ssize_t’ {aka ‘long int’} [-Wsign-compare]

 3921 | for (__pyx_t_24 = 0; __pyx_t_24 < __pyx_t_23; __pyx_t_24+=1) {
  |  ~~~^~~~
build/src/fpylll/fplll/svpcvp.cpp: In function ‘PyObject* 
__pyx_pf_6fpylll_5fplll_6svpcvp_2closest_vector(PyObject*, 
__pyx_obj_6fpylll_5fplll_14integer_matrix_IntegerMatrix*, PyObject*, 
PyObject*, int)’:
build/src/fpylll/fplll/svpcvp.cpp:4740:33: warning: comparison of 
integer expressions of different signedness: 
‘std::vector, 
std::allocator > >::size_type’ {aka ‘long 
unsigned int’} and ‘Py_ssize_t’ {aka ‘long int’} [-Wsign-compare]

 4740 |   for (__pyx_t_7 = 0; __pyx_t_7 < __pyx_t_6; __pyx_t_7+=1) {
  |   ~~^~~
In file included from 
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1940,
 from 
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12,
 from 

Bug#1056800: marked as done (fpylll: ftbfs with cython 3.0.x)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jan 2024 22:04:18 +
with message-id 
and subject line Bug#1056800: fixed in fpylll 0.6.0-1
has caused the Debian Bug report #1056800,
regarding fpylll: ftbfs with cython 3.0.x
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.)


-- 
1056800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fpylll
Version: 0.5.9-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython3

[This bug is targeted to the upcoming trixie release]

The package fails to build in a test rebuild on at least arm64 with
cython 3.0.5, but succeeds to build with cython 0.29.36.  Please
update the package to build with cython 3.0.5 (available in experimental).

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.

Build logs building with cython 3.0.5 can be found at
https://people.debian.org/~stefanor/cython3/cython-3.0.5/

See also https://lists.debian.org/debian-python/2023/11/msg00034.html
--- End Message ---
--- Begin Message ---
Source: fpylll
Source-Version: 0.6.0-1
Done: Alexandre Detiste 

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

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

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

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated fpylll 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, 16 Jan 2024 22:52:13 +0100
Source: fpylll
Architecture: source
Version: 0.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
Changed-By: Alexandre Detiste 
Closes: 1044980 1055732 1056800
Changes:
 fpylll (0.6.0-1) unstable; urgency=medium
 .
   [ Julien Puydt ]
   * New upstream release (Closes: #1055732, #1056800).
   * Fix clean target (Closes: #1044980).
Checksums-Sha1:
 202342e78641c55ce62fffa9d50d3ad63d0fcf61 2457 fpylll_0.6.0-1.dsc
 8d17eeb93c0eb13029babdd08d2503f686c413cc 131057 fpylll_0.6.0.orig.tar.gz
 0430802ec574cbc0cbb600cc61b078e1a3e76962 5208 fpylll_0.6.0-1.debian.tar.xz
 ec1a118c258a68823a237bc9873830b37e0e855b 8369 fpylll_0.6.0-1_source.buildinfo
Checksums-Sha256:
 57e1a2aea90a910c16afb3ddf9fc1a03f5d623947e2681bb3ef7e6428d98a954 2457 
fpylll_0.6.0-1.dsc
 f7c212da16e943c4c684b7e0425eab89352517de1d7180befda56788096966ff 131057 
fpylll_0.6.0.orig.tar.gz
 fd7145835a5cda3c1c744698770084c9ce39c594a9e231c7831b871015ca0fe6 5208 
fpylll_0.6.0-1.debian.tar.xz
 22be346544295abf5c1ca1ceb50cb55fa8f3a1e3092c3b53b80af55c27782646 8369 
fpylll_0.6.0-1_source.buildinfo
Files:
 b05db8ca0304b2465cb5ad2028dbea1e 2457 python optional fpylll_0.6.0-1.dsc
 b90bdbe394741fe4e2ab50d65c3220d9 131057 python optional 
fpylll_0.6.0.orig.tar.gz
 4644b3a004ae8b6781310fe95ab1f875 5208 python optional 
fpylll_0.6.0-1.debian.tar.xz
 21148ba12df3cdd6a4c9e7737057961c 8369 python optional 
fpylll_0.6.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmWm+roRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBo9ABAAw55qTZ5/L9QUjYpwZyoxfTFEvV2y96kJ
JshGIzF+jij3rBl+CoTuh/Pr4fxuUtGEAlNrzEyvDImgUTdoUPoRigw8K6h5rlMH
GbLdJ5jP7HtptjY0RSO+5yzR+4oRjO8Jd0gPY4Xxravgvy80XpjQOPWUja5SARNd
f3pGuCPtR7yLV4ZcLRt1I1VVrUjrqNPja6VFQUFdv35vYHj5LNUcvhR1JuxqBknQ
7y5UW0FGPxiMx0A17682tNuEuy+M+wfYPjGOwZD0Hb3c1AkIhaJ/FJ19S9hRBpr0
/j60Oq+7lqlyHdQMrKy7jrpc+GHzFI8jN8WIJZs34zgkkgi1coviAqQGF3lRQwya
zT8yvjoiNSCyCMB4M0zFP8cs0JWiFgsYeiB+ton9ZKMq3ZsaChu6Cez617YxAGR0
Irx+lYxkv57VZ4YWNLkBF7ERgaPjk7BSWzi/o9m+DyY+14EdDQFfMdqzQdJ7Ru8a
UaFZosMbiTxlrvbShoF1O7mNHNVKJuIFkdsGcBg+ijc00iu+cXNdB/RIBqZIhcLP
VXjFI6GU+CcOXpmUvnCo59/cNeRNDQwCH8OgGHEY5hW9bZm6vWAgCW0bH2CehnA5
591tezDUGl8JaKnIhwI7PZtrCsq+hdib7m5Pe28F0X6oXZfpOznysEGMqEkgXecE
Ebkd1FTasBM=
=lIiy
-END PGP SIGNATURE End Message ---

Processed: fixed 1060962 in 0.7.7-2

[Debian Bug Tracking System]

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

> fixed 1060962 0.7.7-2
Bug #1060962 [src:bmusb] bmusb: FTBFS: dh_install: error: missing files, 
aborting
Marked as fixed in versions bmusb/0.7.7-2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1060994: libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir'

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir'
Bug #1060994 [src:libshumate] libshumate: FTBFS: make: *** [debian/rules:9: 
binary] Error 25
Changed Bug title to 'libshumate: FTBFS: Couldn't find include 
'GObject-2.0.gir'' from 'libshumate: FTBFS: make: *** [debian/rules:9: binary] 
Error 25'.

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

Bug#1060994: libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir'

[Simon McVittie]

Control: retitle -1 libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir'

On Tue, 16 Jan 2024 at 20:43:20 +0100, Lucas Nussbaum wrote:
> > Couldn't find include 'GObject-2.0.gir' (search path: 
> > '['/usr/share/gir-1.0', '/usr/lib/x86_64-linux-gnu/gir-1.0', 
> > '/<>/debian/.debhelper/generated/_source/home/.local/share/gir-1.0',
> >  'gir-1.0', '/usr/local/share/gir-1.0', '/usr/share/gir-1.0', 
> > '/usr/lib/x86_64-linux-gnu/gir-1.0', '/usr/share/gir-1.0', 
> > '/usr/share/gir-1.0']')

This is collateral damage from me removing an unnecessary dependency in
src:graphene, which previously pulled in an unwanted dependency chain
that included libgirepository1.0-dev.

Historically, packages that processed GIR XML needed to build-depend on
libgirepository1.0-dev. As of this week, it's better to build-depend on
gobject-introspection and the individual GIR XML packages that are needed,
which opens the way for being cross-compilable in future.

smcv

Bug#1055714: marked as done (python-jpype ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jan 2024 21:38:15 +
with message-id 
and subject line Bug#1055714: fixed in python-jpype 1.5.0-1
has caused the Debian Bug report #1055714,
regarding python-jpype 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.)


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

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

python-jpype ftbfs with Python 3.12:

[...]
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -Wall 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -fwrapv -g -O2 
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection 
-fdebug-prefix-map=/<>=/usr/src/python-jpype-1.4.1-1build2 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Inative/common/include 
-Inative/python/include -Inative/embedded/include 
-I/usr/lib/jvm/default-java/include 
-I/usr/lib/jvm/default-java/include/linux -I/usr/include/python3.12 -c 
native/common/jp_primitivetype.cpp -o 
build/temp.linux-x86_64-cpython-312/native/common/jp_primitivetype.o -g0 
-std=c++11 -O2
native/common/jp_primitivetype.cpp: In member function ‘PyObject* 
JPPrimitiveType::convertLong(PyTypeObject*, PyLongObject*)’:
native/common/jp_primitivetype.cpp:50:25: error: ‘PyLongObject’ {aka 
‘struct _longobject’} has no member named ‘ob_digit’

   50 | newobj->ob_digit[i] = tmp->ob_digit[i];
  | ^~~~
native/common/jp_primitivetype.cpp:50:44: error: ‘PyLongObject’ {aka 
‘struct _longobject’} has no member named ‘ob_digit’

   50 | newobj->ob_digit[i] = tmp->ob_digit[i];
  |^~~~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:395: build: plugin distutils failed with: exit 
code=1: /usr/bin/python3.12 setup.py build
--- End Message ---
--- Begin Message ---
Source: python-jpype
Source-Version: 1.5.0-1
Done: Alexandre Detiste 

We believe that the bug you reported is fixed in the latest version of
python-jpype, 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.
Alexandre Detiste  (supplier of updated python-jpype 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, 16 Jan 2024 22:01:49 +0100
Source: python-jpype
Architecture: source
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Alexandre Detiste 
Closes: 1055714
Changes:
 python-jpype (1.5.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.5.0 (Closes: #1055714)
Checksums-Sha1:
 71d69df809b5b04cb0d82fd0752056fbc0329236 2081 python-jpype_1.5.0-1.dsc
 3dc399d931add931b06b612569cd3caf88059ef1 710586 python-jpype_1.5.0.orig.tar.gz
 e094dfb5c4e4d939eef6098e7cc52a917d39ae12 3804 
python-jpype_1.5.0-1.debian.tar.xz
 f0f8b9d7e153fa80d91eb53f671b77e37130d728 15484 
python-jpype_1.5.0-1_source.buildinfo
Checksums-Sha256:
 7084099e1b8a26f5a6d190ddef291f98a6af4b2f0f4abdd3fd03900d48d03aa6 2081 
python-jpype_1.5.0-1.dsc
 324ca8b8c40a74d54afecf1612446d49b2113d552fba18092dd44cf196ce9152 710586 
python-jpype_1.5.0.orig.tar.gz
 d662ceb494ea02505ccffa6d3babac10216cc5ba9c52423548d620c44f94 3804 
python-jpype_1.5.0-1.debian.tar.xz
 8183500b30e862188230f59773cd4bcabb5272025a8e8379308a278068ce87c9 15484 
python-jpype_1.5.0-1_source.buildinfo
Files:
 ad9fdda44c21597afb045fa94c53d811 2081 python optional python-jpype_1.5.0-1.dsc
 4e2a2580d4896fc9a4e2f28ebe04d3aa 710586 python optional 
python-jpype_1.5.0.orig.tar.gz
 5b994e5685e38bf4eb3ac2af541561be 3804 python optional 
python-jpype_1.5.0-1.debian.tar.xz
 1131e9a49fb27ab5a7155ae5fa948de1 15484 python optional 
python-jpype_1.5.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: affects 1060687

[Debian Bug Tracking System]

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

> affects 1060687 + src:gnome-settings-daemon
Bug #1060687 [src:libwacom] libwacom-dev: Needs Depends: libevdev-dev
Added indication that 1060687 affects src:gnome-settings-daemon
> thanks
Stopping processing here.

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

Bug#1060950: cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file or directory

[Diederik de Haas]

Control: reassign 1058495 src:cage
Control: forcemerge -1 1058495



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

Processed: Re: Bug#1060950: cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> reassign 1058495 src:cage
Bug #1058495 [cage] cage: Please update to wlroots 0.17
Bug reassigned from package 'cage' to 'src:cage'.
Ignoring request to alter found versions of bug #1058495 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1058495 to the same values 
previously set
> forcemerge -1 1058495
Bug #1060950 [src:cage] cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: 
wlr/types/wlr_idle.h: No such file or directory
Bug #1058495 [src:cage] cage: Please update to wlroots 0.17
Unset Bug forwarded-to-address
Marked as found in versions cage/0.1.5-1.
Added tag(s) trixie and sid.
Bug #1060950 [src:cage] cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: 
wlr/types/wlr_idle.h: No such file or directory
Added tag(s) upstream.
Merged 1058495 1060950

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

Processed: adding some affected packages to libwacom bug

[Debian Bug Tracking System]

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

> affects 1061037 src:wacomtablet
Bug #1061037 {Done: Jeremy Bícha } 
[src:gnome-settings-daemon] gnome-settings-daemon: FTBFS: Package 'libevdev', 
required by 'libwacom', not found
Added indication that 1061037 affects src:wacomtablet
>
End of message, stopping processing here.

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

Bug#1061021: marked as done (cinnamon-control-center: FTBFS: Package 'libevdev', required by 'libwacom', not found)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jan 2024 16:03:10 -0500
with message-id 

and subject line Re: cinnamon-control-center: FTBFS: Package 'libevdev', 
required by 'libwacom', not found
has caused the Debian Bug report #1061021,
regarding cinnamon-control-center: FTBFS: Package 'libevdev', required by 
'libwacom', not found
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.)


-- 
1061021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cinnamon-control-center
Version: 5.8.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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=gnome
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   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
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: cinnamon-control-center
> Project version: 5.8.2
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Library m found: YES
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Run-time dependency cinnamon-desktop found: YES 5.8.0
> Run-time dependency libcinnamon-menu-3.0 found: YES 6.0.0
> Run-time dependency gtk+-3.0 found: YES 3.24.39
> Run-time dependency glib-2.0 found: YES 2.78.3
> Run-time dependency gio-unix-2.0 found: YES 2.78.3
> Run-time dependency gudev-1.0 found: YES 238
> Run-time dependency libgnomekbd found: YES 3.28.1
> Run-time dependency libgnomekbdui found: YES 3.28.1
> Run-time dependency libnotify found: YES 0.8.3
> Run-time dependency x11 found: YES 1.8.7
> Run-time dependency polkit-gobject-1 found: YES 123
> Run-time dependency libxklavier found: YES 5.4
> Run-time dependency upower-glib found: YES 1.90.2
> Has header "X11/extensions/XKB.h" : YES 
> Run-time dependency iso-codes found: YES 4.16.0
> Run-time dependency libnm found: YES 1.44.2
> Run-time dependency libnma found: YES 1.10.6
> Run-time dependency mm-glib found: YES 1.22.0
> Run-time dependency colord found: YES 1.4.6
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency libwacom found: NO 
> 
> ../meson.build:86:14: ERROR: Dependency lookup for libwacom with method 
> 'pkgconfig' failed: Could not generate cflags for libwacom:
> Package libevdev was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libevdev.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libevdev', required by 'libwacom', not found
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2024-01-15T20:22:22.141671
> Main binary: /usr/bin/python3
> Build Options: -Dpython.bytecompile=-1 -Dprefix=/usr 
> -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc 
> -Dbuildtype=plain -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: cinnamon-control-center
> Project version: 5.8.2
> ---
> Detecting compiler via: `cc --version` -> 0
> stdout:
> cc (Debian 13.2.0-9) 13.2.0
> Copyright (C) 2023 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> ---
> Running command: cc -E -dM -
> -
> ---
> Detecting linker via: `cc -Wl,--version -Wl,-z,relro -Wl,-z,now -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2` -> 0
> stdout:
> GNU ld (GNU Binutils for Debian) 2.41.50.20231227
> Copyright (C) 2023 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or (at your option) a later 

Processed (with 3 errors): adding some affected packages to libwacom bug

[Debian Bug Tracking System]

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

> affects 1061037 src:gnome-settings-daemon src:cinnamon-control-center
Bug #1061037 {Done: Jeremy Bícha } 
[src:gnome-settings-daemon] gnome-settings-daemon: FTBFS: Package 'libevdev', 
required by 'libwacom', not found
Added indication that 1061037 affects src:gnome-settings-daemon and 
src:cinnamon-control-center
> src:wacomtablet
Unknown command or malformed arguments to command.
> Thank you,
Unknown command or malformed arguments to command.
> Jeremy Bícha
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#1060990: wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2

[Jeremy Bícha]

This might be  https://bugs.debian.org/1060687

Thank you,
Jeremy Bícha

Processed (with 1 error): Re: Bug#1060950: cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 1058495
Bug #1060950 [src:cage] cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: 
wlr/types/wlr_idle.h: No such file or directory
Unable to merge bugs because:
package of #1058495 is 'cage' not 'src:cage'
Failed to forcibly merge 1060950: Did not alter merged bugs.


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

Bug#1061037: marked as done (gnome-settings-daemon: FTBFS: Package 'libevdev', required by 'libwacom', not found)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jan 2024 15:58:39 -0500
with message-id 

and subject line Re: Bug#1061037: gnome-settings-daemon: FTBFS: Package 
'libevdev', required by 'libwacom', not found
has caused the Debian Bug report #1061037,
regarding gnome-settings-daemon: FTBFS: Package 'libevdev', required by 
'libwacom', not found
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.)


-- 
1061037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-settings-daemon
Version: 45.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 -- \
>   --libdir=/usr/lib \
>   -Dgcr3=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 --libdir=/usr/lib -Dgcr3=true
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-settings-daemon
> Project version: 45.1
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> 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 glib-2.0 found: YES 2.78.3
> Run-time dependency geocode-glib-2.0 found: YES 3.26.3
> Run-time dependency gio-2.0 found: YES 2.78.3
> Run-time dependency gio-unix-2.0 found: YES 2.78.3
> Run-time dependency gnome-desktop-3.0 found: YES 44.0
> Run-time dependency gsettings-desktop-schemas found: YES 45.0
> Run-time dependency gtk+-3.0 found: YES 3.24.39
> Run-time dependency gtk+-x11-3.0 found: YES 3.24.39
> Run-time dependency gweather4 found: YES 4.4.0
> Run-time dependency libcanberra-gtk3 found: YES 0.30
> Run-time dependency libgeoclue-2.0 found: YES 2.7.1
> Run-time dependency libnotify found: YES 0.8.3
> Run-time dependency libpulse-mainloop-glib found: YES 16.1
> Run-time dependency pango found: YES 1.51.0
> Run-time dependency polkit-gobject-1 found: YES 123
> Run-time dependency upower-glib found: YES 1.90.2
> Run-time dependency x11 found: YES 1.8.7
> Run-time dependency xfixes found: YES 6.0.0
> Run-time dependency systemd found: YES 255
> ../meson.build:118: WARNING: Project targets '>= 0.57.0' but uses feature 
> deprecated since '0.56.0': dependency.get_pkgconfig_variable. use 
> dependency.get_variable(pkgconfig : ...) instead
> Library m found: YES
> 
> Executing subproject gvc 
> 
> gvc| Project name: gvc
> gvc| Project version: undefined
> gvc| C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 
> 13.2.0")
> gvc| C linker for the host machine: cc ld.bfd 2.41.50.20231227
> gvc| Dependency glib-2.0 found: YES 2.78.3 (cached)
> gvc| Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums)
> gvc| Dependency glib-2.0 found: YES 2.78.3 (cached)
> gvc| Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums)
> gvc| Dependency gio-2.0 found: YES 2.78.3 (cached)
> gvc| Run-time dependency gobject-2.0 found: YES 2.78.3
> gvc| Run-time dependency libpulse found: YES 16.1
> gvc| Dependency libpulse-mainloop-glib found: YES 16.1 (cached)
> gvc| Run-time dependency alsa found: YES 1.2.10
> gvc| Configuring config.h using configuration
> gvc| Build targets in project: 4
> gvc| Subproject gvc finished.
> 
> Run-time dependency gudev-1.0 found: YES 238
> Checking for function "timerfd_create" : YES 
> Run-time dependency wayland-client found: YES 1.22.0
> Run-time dependency gdk-wayland-3.0 found: YES 3.24.39
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency libwacom found: NO 
> 
> ../meson.build:163:17: ERROR: Dependency lookup for libwacom with method 
> 'pkgconfig' failed: Could not generate cflags for libwacom:
> Package libevdev was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libevdev.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libevdev', required by 'libwacom', not found
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> 

Bug#1060950: cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file or directory

[Diederik de Haas]

Control: forcemerge -1 1058495

On dinsdag 16 januari 2024 20:29:22 CET you wrote:
> Source: cage
> Version: 0.1.5-1
> Severity: serious
> Justification: FTBFS
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

It's a known problem, see https://bugs.debian.org/1058495

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

Bug#1060947: marked as done (pqmarble: FTBFS: make: *** [debian/rules:6: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Tue, 16 Jan 2024 20:40:48 +
with message-id 
and subject line Bug#1060947: fixed in pqmarble 1.3.0-5
has caused the Debian Bug report #1060947,
regarding pqmarble: FTBFS: make: *** [debian/rules:6: 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.)


-- 
1060947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pqmarble
Version: 1.3.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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=meson --with=gir
>dh_update_autotools_config -O--buildsystem=meson
>dh_autoreconf -O--buildsystem=meson
>dh_auto_configure -O--buildsystem=meson
>   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
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: pqmarble
> Project version: 2.0.0
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> Vala compiler for the host machine: valac (valac 0.56.14)
> 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 gio-2.0 found: YES 2.78.3
> Run-time dependency gtk4 found: YES 4.12.4
> Dependency gio-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-compile-resources found: YES 
> (/usr/bin/glib-compile-resources)
> Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Build targets in project: 7
> 
> pqmarble 2.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
> 
> Found ninja-1.11.1 at /usr/bin/ninja
>dh_auto_build -O--buildsystem=meson
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/8] /usr/bin/glib-compile-resources ../src/pqmarble.gresource.xml 
> --sourcedir ../src --c-name pqmarble --internal --generate --target 
> src/pqmarble-resources.h
> [2/8] /usr/bin/glib-compile-resources ../src/pqmarble.gresource.xml 
> --sourcedir ../src --c-name pqmarble --internal --generate --target 
> src/pqmarble-resources.c --dependency-file src/pqmarble-resources.c.d
> [3/8] valac -C --pkg gtk4 --pkg gio-2.0 --color=always --directory 
> src/libpqmarble.so.2.0.0.p --basedir ../src --library pqmarble --header 
> src/pqmarble.h --vapi ../pqmarble.vapi --gir ../PQMarble-2.gir 
> --gresources=../src/pqmarble.gresource.xml ../src/services/Settings.vala 
> ../src/utils/Utils.vala
> ../src/utils/Utils.vala:35.5-35.27: warning: `Gtk.CssProvider.load_from_data' 
> has been deprecated since 4.12
>35 | provider.load_from_data (data.data);
>   | ^~~ 
> ../src/utils/Utils.vala:55.15-55.38: warning: `Gtk.Widget.get_style_context' 
> has been deprecated since 4.10
>55 | var ctx = widget.get_style_context();
>   |   ^~~~   
> ../src/utils/Utils.vala:55.9-55.11: warning: `Gtk.StyleContext' has been 
> deprecated since 4.10
>55 | var ctx = widget.get_style_context();
>   | ^~~  
> ../src/utils/Utils.vala:74.5-74.20: warning: `Gtk.StyleContext' has been 
> deprecated since 4.10
>74 | Gtk.StyleContext.add_provider_for_display(display, provider, 
> priority);
>   | ^~~~  
>  
> Compilation succeeded - 4 warning(s)
> [4/8] cc -Isrc/libpqmarble.so.2.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/libmount 
> -I/usr/include/blkid -I/usr/include/gtk-4.0 -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/fribidi -I/usr/include/cairo 

Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

[Richard Rosner]

Good to know. Thanks.


Am Dienstag, 16. Januar 2024 21:00 CET, schrieb Scott Kitterman 
:
 So, the magic needed to build the new update exceeds my grasp, but it's
debian/changelog discusses fixing regressions. On that basis, I think the
thing to do is reassign the bug to mariadb and mark it as affecting postfix.
I'll also bring it to the stable release manager's attention.

Scott K

On Tuesday, January 16, 2024 2:36:23 PM EST Scott Kitterman wrote:
> Excellent. On that basis, I think blaming mariadb for the regression is
> appropriate. I see there's another mariadb update pending. If would up for
> another test, I'd like to see if that update solves the problem. I'll
> build another set of packages against that and if that works, then we just
> need to make sure we get that update accepted and rebuild postfix.
>
> Scott K


smime.p7s
Description: S/MIME cryptographic signature

Processed: Bug#1061013 marked as pending in pytest-twisted

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1061013 [src:pytest-twisted] pytest-twisted: FTBFS: FAILED 
test_async_fixture.py::test_succeed_blue[web] - RuntimeError: baz
Added tag(s) pending.

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

Bug#1061013: marked as pending in pytest-twisted

[Timo Röhling]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/pytest-twisted/-/commit/5b4d3902ad9e4b6c012558bce4327cf54810eb06


Relax location constraint of ignored DeprecationWarning

Closes: #1061013


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1061013

Bug#1061021: cinnamon-control-center: FTBFS: Package 'libevdev', required by 'libwacom', not found

[Fabio Fantoni]

Il 16/01/2024 20:29, Lucas Nussbaum ha scritto:

CMake binary for host machine is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Did not find CMake 'cmake'
Found CMake: NO
Dependency lookup for libwacom with method 'cmake' failed: CMake binary for 
machine host machine not found. Giving up.
Run-time dependency libwacom found: NO

../meson.build:86:14: ERROR: Dependency lookup for libwacom with method 
'pkgconfig' failed: Could not generate cflags for libwacom:
Package libevdev was not found in the pkg-config search path.
Perhaps you should add the directory containing `libevdev.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libevdev', required by 'libwacom', not found

dh_auto_configure: error: 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 returned exit code 1
make: *** [debian/rules:10: binary] Error 25


Thanks for your work about FTBFS reports.

libevdev seems don't required by cinnamon-control-center but by wacom, 
from a fast look I saw require it but don't have libevdev-dev dep.


anyway is already reported by 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060687


I don't think is a good thing add libevdev-dev build-dep. in 
cinnamon-control-center as temporary workaround and should wait fix in 
libwacom instead, or I'm wrong?




OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

[Scott Kitterman]

So, the magic needed to build the new update exceeds my grasp, but it's 
debian/changelog discusses fixing regressions.  On that basis, I think the 
thing to do is reassign the bug to mariadb and mark it as affecting postfix.  
I'll also bring it to the stable release manager's attention.

Scott K

On Tuesday, January 16, 2024 2:36:23 PM EST Scott Kitterman wrote:
> Excellent.  On that basis, I think blaming mariadb for the regression is
> appropriate.  I see there's another mariadb update pending.  If would up for
> another test, I'd like to see if that update solves the problem.  I'll
> build another set of packages against that and if that works, then we just
> need to make sure we get that update accepted and rebuild postfix.
> 
> Scott K
> 
> On Tuesday, January 16, 2024 2:25:13 PM EST Richard Rosner wrote:
> > These packages do work without a problem.
> > 
> > Am Dienstag, 16. Januar 2024 19:35 CET, schrieb Scott Kitterman
> > : Rebuild binaries are available (for the moment)
> > at:
> > 
> > https://kitterman.com/debian/
> > 
> > I'll remove them once we've done testing. That's all the binaries built by
> > postfix. You'll need to download and then use dpkg -i to install all the
> > ones you have on your system, not just postfix-mysql. At a minimum it will
> > be postfix and postfix-mysql.
> > 
> > Let me know how it goes.
> > 
> > Scott K



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

Processed: affects 1060917

[Debian Bug Tracking System]

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

> affects 1060917 postfix-mysql
Bug #1060917 [mariadb] postfix-mysql broken in 3.7.9, results in unsupported 
dictionary type
Added indication that 1060917 affects postfix-mysql
> thanks
Stopping processing here.

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

Processed: reassign 1060917 to mariadb

[Debian Bug Tracking System]

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

> reassign 1060917 mariadb
Bug #1060917 [postfix-mysql] postfix-mysql broken in 3.7.9, results in 
unsupported dictionary type
Bug reassigned from package 'postfix-mysql' to 'mariadb'.
No longer marked as found in versions postfix/3.7.9-0+deb12u1.
Ignoring request to alter fixed versions of bug #1060917 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1060942: marked as done (linux-signed-amd64: FTBFS: unsatisfiable build-dependencies: linux-image-6.6.9-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), linux-image-

[Debian Bug Tracking System]

Your message dated Tue, 16 Jan 2024 20:54:41 +0100
with message-id <20240116195441.l5oywod3hcuzi...@shell.thinkmo.de>
and subject line Re: Bug#1060942: linux-signed-amd64: FTBFS: unsatisfiable 
build-dependencies: linux-image-6.6.9-amd64-unsigned (= 6.6.9-1), 
linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), 
linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1)
has caused the Debian Bug report #1060942,
regarding linux-signed-amd64: FTBFS: unsatisfiable build-dependencies: 
linux-image-6.6.9-amd64-unsigned (= 6.6.9-1), 
linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), 
linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-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.)


-- 
1060942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux-signed-amd64
Version: 6.6.9+1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), dh-exec, python3:any, 
> sbsigntool, build-essential, fakeroot, linux-image-6.6.9-amd64-unsigned (= 
> 6.6.9-1), kernel-wedge (>= 2.105~), kmod, rsync, 
> linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), 
> linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1)
> Filtered Build-Depends: debhelper-compat (= 12), dh-exec, python3:any, 
> sbsigntool, build-essential, fakeroot, linux-image-6.6.9-amd64-unsigned (= 
> 6.6.9-1), kernel-wedge (>= 2.105~), kmod, rsync, 
> linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), 
> linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1)
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [612 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1089 B]
> Get:5 copy:/<>/apt_archive ./ Packages [869 B]
> Fetched 2570 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  sbuild-build-depends-main-dummy : Depends: linux-image-6.6.9-amd64-unsigned 
> (= 6.6.9-1) but it is not going to be installed
>Depends: 
> linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1) but it is not going to be 
> installed
>Depends: 
> linux-image-6.6.9-rt-amd64-unsigned (= 6.6.9-1) but it is not going to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/linux-signed-amd64_6.6.9+1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=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 ---
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Please blacklist the signed packages, this behaviour is a requirement of
the secure boot signing.

Nothing to see here.

Bastian

-- 
Most legends 

Bug#1060942: linux-signed-amd64: FTBFS: unsatisfiable build-dependencies: linux-image-6.6.9-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-cloud-amd64-unsigned (= 6.6.9-1), linux-image-6.6.9-rt-amd64-u

[Bastian Blank]

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

Please blacklist the signed packages, this behaviour is a requirement of
the secure boot signing.

Nothing to see here.

Bastian

-- 
Most legends have their basis in facts.
-- Kirk, "And The Children Shall Lead", stardate 5029.5

Bug#1061042: flask-mongoengine: FTBFS: tests failed

[Lucas Nussbaum]

Source: flask-mongoengine
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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:305: python3.12 setup.py config 
> running config
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine
> copying flask_mongoengine/operation_tracker.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine
> copying flask_mongoengine/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine
> copying flask_mongoengine/json.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine
> copying flask_mongoengine/pagination.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine
> copying flask_mongoengine/panels.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine
> copying flask_mongoengine/sessions.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine
> copying flask_mongoengine/connection.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine
> creating 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf
> copying flask_mongoengine/wtf/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf
> copying flask_mongoengine/wtf/models.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf
> copying flask_mongoengine/wtf/fields.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf
> copying flask_mongoengine/wtf/base.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf
> copying flask_mongoengine/wtf/orm.py -> 
> /<>/.pybuild/cpython3_3.12_flask-mongoengine/build/flask_mongoengine/wtf
> running egg_info
> creating flask_mongoengine.egg-info
> writing flask_mongoengine.egg-info/PKG-INFO
> writing dependency_links to flask_mongoengine.egg-info/dependency_links.txt
> writing requirements to flask_mongoengine.egg-info/requires.txt
> writing top-level names to flask_mongoengine.egg-info/top_level.txt
> writing manifest file 'flask_mongoengine.egg-info/SOURCES.txt'
> reading manifest file 'flask_mongoengine.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'docs'
> warning: no previously-included files matching '*.pyo' found under directory 
> 'docs'
> no previously-included directories found matching 'docs/_build'
> no previously-included directories found matching 'docs/_themes/.git'
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'flask_mongoengine.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: 
> Package 'flask_mongoengine.templates.panels' is absent from the `packages` 
> configuration.
> !!
> 
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'flask_mongoengine.templates.panels' as an 
> importable package[^1],
> but it is absent from setuptools' `packages` configuration.
> 
> This leads to an ambiguous overall configuration. If you want to 
> distribute this
> package, please make sure that 'flask_mongoengine.templates.panels' 
> is explicitly added
> to the `packages` configuration field.
> 
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" on setuptools 
> documentation page:
> 
> - 
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
> If you don't want 'flask_mongoengine.templates.panels' to be 
> distributed and are
> already explicitly excluding 'flask_mongoengine.templates.panels' via
> `find_namespace_packages(...)/find_namespace` or 
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or 
> `include-package-data=False` in
> combination with a more fine grained `package-data` configuration.
> 
> You can read more about "package data files" on setuptools 

Bug#1061041: syncthingtray: FTBFS: make[5]: *** [connector/CMakeFiles/check.dir/build.make:73: connector/CMakeFiles/check] Error 8

[Lucas Nussbaum]

Source: syncthingtray
Version: 1.3.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/debian/build'
> /usr/bin/ctest -V
> UpdateCTestConfiguration  from 
> :/<>/debian/build/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/debian/build/DartConfiguration.tcl
> Test project /<>/debian/build
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
> Start 1: syncthingconnector_run_tests
> 
> 1: Test command: 
> /<>/debian/build/connector/syncthingconnector_tests "-p" 
> "/<>/connector/testfiles" "-w" 
> "/<>/debian/build/connector/testworkingdir"
> 1: Working Directory: /<>/debian/build/connector
> 1: Test timeout computed to be: 1000
> 1: /<>/connector/testfiles/
> 1: /<>/connector/testfiles/
> 1: ./testfiles/
> 1: Directory used to store working copies:
> 1: /<>/debian/build/connector/testworkingdir/
> 1: Executing test cases ...
> 1: .
> 1:  - Setup configuration for Syncthing tests ...
> 1:  - No timeout factor set, defaulting to 1
> 1:(set environment variable SYNCTHING_TEST_TIMEOUT_FACTOR to specify a 
> factor to run tests on a slow machine)
> 1: 
> 1:  - Launching Syncthing: syncthing -gui-address=http://127.0.0.1:4001 
> -gui-apikey=syncthingtestinstance 
> -home=/<>/debian/build/connector/testworkingdir/testconfig 
> -no-browser -verbose
> 1: Info: Launched process, PID: 1655520
> 1: 
> 1:  - Preparing connection ...
> 1: 
> 1:  - Error handling in case of insufficient configuration ...
> 1:  - Connection error: Connection configuration is insufficient.
> 1:  - Connection status changed to: disconnected
> 1: 
> 1:  - Error handling in case of inavailability ...
> 1:  - Connection error: Unable to request Syncthing config: Connection refused
> 1:  - Connection error: Unable to request Syncthing status: Connection refused
> 1: [start] 2024/01/15 20:12:46 INFO: syncthing v1.27.2-ds4 "Gold Grasshopper" 
> (go1.21.5 linux-amd64) debian@debian 2024-01-06 14:38:16 UTC
> 1: [start] 2024/01/15 20:12:46 INFO: Generating ECDSA key and certificate for 
> syncthing...
> 1: [start] 2024/01/15 20:12:46 INFO: Archiving a copy of old config file 
> format at: 
> /<>/debian/build/connector/testworkingdir/testconfig/config.xml.v28
> 1: [GUZKE] 2024/01/15 20:12:46 INFO: My ID: 
> GUZKEQZ-NUIVT6O-EAK4SLK-PICXPBH-NRMSN67-NO2HK4C-KKZSBJF-DRNQKAX
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection error: Unable to request Syncthing config: Connection refused
> 1:  - Connection error: Unable to request Syncthing status: Connection refused
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection error: Unable to request Syncthing config: Connection refused
> 1:  - Connection error: Unable to request Syncthing status: Connection refused
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection error: Unable to request Syncthing config: Connection refused
> 1:  - Connection error: Unable to request Syncthing status: Connection refused
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection error: Unable to request Syncthing config: Connection refused
> 1:  - Connection error: Unable to request Syncthing status: Connection refused
> 1: [GUZKE] 2024/01/15 20:12:47 INFO: Single thread SHA256 performance is 347 
> MB/s using minio/sha256-simd (344 MB/s using crypto/sha256).
> 1: [GUZKE] 2024/01/15 20:12:47 VERBOSE: Starting up 
> (/<>/debian/build/connector/testworkingdir/testconfig)
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection error: Unable to request Syncthing config: Connection refused
> 1:  - Connection error: Unable to request Syncthing status: Connection refused
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: disconnected
> 1:  - Connection status changed to: 

Bug#1061037: gnome-settings-daemon: FTBFS: Package 'libevdev', required by 'libwacom', not found

[Lucas Nussbaum]

Source: gnome-settings-daemon
Version: 45.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 -- \
>   --libdir=/usr/lib \
>   -Dgcr3=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 --libdir=/usr/lib -Dgcr3=true
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-settings-daemon
> Project version: 45.1
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> 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 glib-2.0 found: YES 2.78.3
> Run-time dependency geocode-glib-2.0 found: YES 3.26.3
> Run-time dependency gio-2.0 found: YES 2.78.3
> Run-time dependency gio-unix-2.0 found: YES 2.78.3
> Run-time dependency gnome-desktop-3.0 found: YES 44.0
> Run-time dependency gsettings-desktop-schemas found: YES 45.0
> Run-time dependency gtk+-3.0 found: YES 3.24.39
> Run-time dependency gtk+-x11-3.0 found: YES 3.24.39
> Run-time dependency gweather4 found: YES 4.4.0
> Run-time dependency libcanberra-gtk3 found: YES 0.30
> Run-time dependency libgeoclue-2.0 found: YES 2.7.1
> Run-time dependency libnotify found: YES 0.8.3
> Run-time dependency libpulse-mainloop-glib found: YES 16.1
> Run-time dependency pango found: YES 1.51.0
> Run-time dependency polkit-gobject-1 found: YES 123
> Run-time dependency upower-glib found: YES 1.90.2
> Run-time dependency x11 found: YES 1.8.7
> Run-time dependency xfixes found: YES 6.0.0
> Run-time dependency systemd found: YES 255
> ../meson.build:118: WARNING: Project targets '>= 0.57.0' but uses feature 
> deprecated since '0.56.0': dependency.get_pkgconfig_variable. use 
> dependency.get_variable(pkgconfig : ...) instead
> Library m found: YES
> 
> Executing subproject gvc 
> 
> gvc| Project name: gvc
> gvc| Project version: undefined
> gvc| C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 
> 13.2.0")
> gvc| C linker for the host machine: cc ld.bfd 2.41.50.20231227
> gvc| Dependency glib-2.0 found: YES 2.78.3 (cached)
> gvc| Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums)
> gvc| Dependency glib-2.0 found: YES 2.78.3 (cached)
> gvc| Program /usr/bin/glib-mkenums found: YES (/usr/bin/glib-mkenums)
> gvc| Dependency gio-2.0 found: YES 2.78.3 (cached)
> gvc| Run-time dependency gobject-2.0 found: YES 2.78.3
> gvc| Run-time dependency libpulse found: YES 16.1
> gvc| Dependency libpulse-mainloop-glib found: YES 16.1 (cached)
> gvc| Run-time dependency alsa found: YES 1.2.10
> gvc| Configuring config.h using configuration
> gvc| Build targets in project: 4
> gvc| Subproject gvc finished.
> 
> Run-time dependency gudev-1.0 found: YES 238
> Checking for function "timerfd_create" : YES 
> Run-time dependency wayland-client found: YES 1.22.0
> Run-time dependency gdk-wayland-3.0 found: YES 3.24.39
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency libwacom found: NO 
> 
> ../meson.build:163:17: ERROR: Dependency lookup for libwacom with method 
> 'pkgconfig' failed: Could not generate cflags for libwacom:
> Package libevdev was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libevdev.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libevdev', required by 'libwacom', not found
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2024-01-15T20:21:32.69
> Main binary: /usr/bin/python3
> Build Options: -Dpython.bytecompile=-1 -Dgcr3=true -Dprefix=/usr 
> -Dlibdir=/usr/lib -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-settings-daemon
> Project version: 45.1
> ---
> Detecting compiler via: `cc --version` -> 0
> stdout:
> cc (Debian 13.2.0-9) 13.2.0
> Copyright (C) 2023 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> ---
> Running command: cc -E -dM -
> -
> ---
> Detecting linker via: `cc -Wl,--version -Wl,-z,relro -Wl,-z,now 

Bug#1061040: apertium-eu-en: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: apertium-eu-en
Version: 0.3.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> apertium-regtest test
> Corpus 1 of 1: eu-en-pending
>   1/59 (1.69%) tests pass (0/1 (0.0%) match gold)
> 
> There were changes! Rerun in interactive mode to update tests.
> Changed corpora: eu-en-pending
> make[1]: *** [Makefile:788: test] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/apertium-eu-en_0.3.3-1_unstable.log

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

Bug#1061035: libconfig-model-dpkg-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255

[Lucas Nussbaum]

Source: libconfig-model-dpkg-perl
Version: 3.002
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   /usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wl,-z,relro"
> Can't find dist packages without a MANIFEST file
> Run 'Build manifest' to generate one
> 
> WARNING: Possible missing or corrupt 'MANIFEST' file.
> Nothing to enter for 'provides' field in metafile.
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'Config-Model-Dpkg' version '0'
>dh_auto_build
>   /usr/bin/perl Build
> Checking doc for model Dpkg::Patch
> Wrote documentation in lib/Config/Model/models/Dpkg/Patch.pod
> Checking doc for model Dpkg
> Wrote documentation in lib/Config/Model/models/Dpkg.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/BugFiles.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/BugFiles/Control.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Control.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Control/Binary.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Control/Source.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Copyright.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/Content.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/FileLicense.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/FillBlanks.pod
> Wrote documentation in 
> lib/Config/Model/models/Dpkg/Copyright/FillBlanks/Pattern.pod
> Wrote documentation in 
> lib/Config/Model/models/Dpkg/Copyright/GlobalLicense.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/LicenseSpec.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Copyright/ScanPatterns.pod
> Wrote documentation in 
> lib/Config/Model/models/Dpkg/Copyright/ScanPatterns/Lists.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Install.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Meta.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/PackageScripts.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Source.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Source/Options.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Tests.pod
> Wrote documentation in lib/Config/Model/models/Dpkg/Tests/Control.pod
> Checking doc for model Dpkg::Copyright
> Checking doc for model Dpkg::Patches
> Wrote documentation in lib/Config/Model/models/Dpkg/Patches.pod
> Checking doc for model Dpkg::Control
> Building Config-Model-Dpkg
>dh_auto_test
>   /usr/bin/perl Build test --verbose 1
> when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 185.
> when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 188.
> when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 191.
> when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 196.
> when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 200.
> when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 203.
> when is deprecated at /usr/share/perl5/App/Cme/Command/run.pm line 207.
> t/cme-scripts.t .. 
> 
> Reading package lists... 0%
> 
> Reading package lists... 100%
> 
> Reading package lists... Done
> 
> 
> Building dependency tree... 0%
> 
> Building dependency tree... 0%
> 
> Building dependency tree... 50%
> 
> Building dependency tree... 50%
> 
> Building dependency tree... Done
> 
> 
> Reading state information... 0% 
> 
> Reading state information... 0%
> 
> Reading state information... Done
> 
> # Subtest: bump_dependency
> ok 1 - all went well
> ok 2 - check changes on stderr
> ok 3 - check: no message on stdout
> ok 4 - updated dependency in file
> 1..4
> ok 1 - bump_dependency
> # Subtest: update_my_copyright_year
> ok 1 - all went well
> ok 2 - check: no message on stdout
> ok 3 - updated copyright in file
> 1..3
> ok 2 - update_my_copyright_year
> 1..2
> ok
> t/copyright-from-scratch.t ... 
> ok 1 - compiled
> # Running tests in wr_root/copyright-from-scratch
> # Subtest: Creation of debian/copyright
> ok 1 - initial load is done
> ok 2 - check license text brought by Software::License
> ok 3 - check lic text
> ok 4 - check lic text
> ok 5 - check lic text
> 1..5
> ok 2 - Creation of debian/copyright
> # Subtest: Check "and/or" 

Bug#1061038: apertium-en-gl: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: apertium-en-gl
Version: 0.5.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> apertium-regtest test
> Corpus 1 of 1: en-gl-regression
>   0/1 (0.0%) tests pass
> 
> There were changes! Rerun in interactive mode to update tests.
> Changed corpora: en-gl-regression
> make[1]: *** [Makefile:806: test] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/apertium-en-gl_0.5.4-2_unstable.log

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

Bug#1061036: trash-cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: trash-cli
Version: 0.23.2.13.2-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:305: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11  
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/trashcli
> copying trashcli/__init__.py -> build/lib/trashcli
> copying trashcli/rm.py -> build/lib/trashcli
> copying trashcli/trash_dirs_scanner.py -> build/lib/trashcli
> copying trashcli/list.py -> build/lib/trashcli
> copying trashcli/py2compat.py -> build/lib/trashcli
> copying trashcli/trash.py -> build/lib/trashcli
> copying trashcli/list_mount_points.py -> build/lib/trashcli
> copying trashcli/super_enum.py -> build/lib/trashcli
> copying trashcli/fstab.py -> build/lib/trashcli
> copying trashcli/shell_completion.py -> build/lib/trashcli
> copying trashcli/fs.py -> build/lib/trashcli
> creating build/lib/trashcli/empty
> copying trashcli/empty/__init__.py -> build/lib/trashcli/empty
> copying trashcli/empty/print_version_action.py -> build/lib/trashcli/empty
> copying trashcli/empty/parser.py -> build/lib/trashcli/empty
> copying trashcli/empty/older_than.py -> build/lib/trashcli/empty
> copying trashcli/empty/empty_action.py -> build/lib/trashcli/empty
> copying trashcli/empty/delete_according_date.py -> build/lib/trashcli/empty
> copying trashcli/empty/main.py -> build/lib/trashcli/empty
> copying trashcli/empty/print_time_action.py -> build/lib/trashcli/empty
> copying trashcli/empty/description.py -> build/lib/trashcli/empty
> copying trashcli/empty/prepare_output_message.py -> build/lib/trashcli/empty
> copying trashcli/empty/emptier.py -> build/lib/trashcli/empty
> copying trashcli/empty/errors.py -> build/lib/trashcli/empty
> copying trashcli/empty/console.py -> build/lib/trashcli/empty
> copying trashcli/empty/empty_cmd.py -> build/lib/trashcli/empty
> copying trashcli/empty/user.py -> build/lib/trashcli/empty
> copying trashcli/empty/is_input_interactive.py -> build/lib/trashcli/empty
> copying trashcli/empty/actions.py -> build/lib/trashcli/empty
> copying trashcli/empty/guard.py -> build/lib/trashcli/empty
> copying trashcli/empty/parse_reply.py -> build/lib/trashcli/empty
> copying trashcli/empty/existing_file_remover.py -> build/lib/trashcli/empty
> creating build/lib/trashcli/lib
> copying trashcli/lib/__init__.py -> build/lib/trashcli/lib
> copying trashcli/lib/my_permission_error.py -> build/lib/trashcli/lib
> copying trashcli/lib/my_input.py -> build/lib/trashcli/lib
> creating build/lib/trashcli/put
> copying trashcli/put/class_name_meta.py -> build/lib/trashcli/put
> copying trashcli/put/trasher.py -> build/lib/trashcli/put
> copying trashcli/put/trash_directories_finder.py -> build/lib/trashcli/put
> copying trashcli/put/__init__.py -> build/lib/trashcli/put
> copying trashcli/put/trash_put_cmd.py -> build/lib/trashcli/put
> copying trashcli/put/trash_dir_volume_reader.py -> build/lib/trashcli/put
> copying trashcli/put/volume_message_formatter.py -> build/lib/trashcli/put
> copying trashcli/put/trash_all.py -> build/lib/trashcli/put
> copying trashcli/put/parser.py -> build/lib/trashcli/put
> copying trashcli/put/info_dir.py -> build/lib/trashcli/put
> copying trashcli/put/trash_result.py -> build/lib/trashcli/put
> copying trashcli/put/main.py -> build/lib/trashcli/put
> copying trashcli/put/candidate.py -> build/lib/trashcli/put
> copying trashcli/put/trashing_checker.py -> build/lib/trashcli/put
> copying trashcli/put/security_check.py -> build/lib/trashcli/put
> copying trashcli/put/reporter.py -> build/lib/trashcli/put
> copying trashcli/put/trashee.py -> build/lib/trashcli/put
> copying trashcli/put/suffix.py -> build/lib/trashcli/put
> copying trashcli/put/describer.py -> build/lib/trashcli/put
> copying trashcli/put/my_logger.py -> build/lib/trashcli/put
> copying trashcli/put/trash_directory_for_put.py -> build/lib/trashcli/put
> copying trashcli/put/file_trasher.py -> build/lib/trashcli/put
> copying trashcli/put/same_volume_gate.py -> build/lib/trashcli/put
> copying trashcli/put/gate.py -> build/lib/trashcli/put
> copying trashcli/put/original_location.py -> build/lib/trashcli/put
> copying trashcli/put/user.py -> build/lib/trashcli/put
> copying trashcli/put/format_trash_info.py -> build/lib/trashcli/put
> copying trashcli/put/clock.py -> build/lib/trashcli/put
> copying 

Bug#1061032: golang-github-go-kit-kit: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/go-kit/kit/auth/basic github.com/go-kit/kit/auth/casbin [...] returned

[Lucas Nussbaum]

Source: golang-github-go-kit-kit
Version: 0.10.0-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>   Copy go.mod -> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/go.mod
>   Copy go.sum -> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/go.sum
>   Copy transport/doc.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/doc.go
>   Copy transport/error_handler.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/error_handler.go
>   Copy transport/error_handler_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/error_handler_test.go
>   Copy transport/httprp/server.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/httprp/server.go
>   Copy transport/httprp/server_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/httprp/server_test.go
>   Copy transport/httprp/doc.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/httprp/doc.go
>   Copy transport/http/example_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/example_test.go
>   Copy transport/http/server.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/server.go
>   Copy transport/http/request_response_funcs_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/request_response_funcs_test.go
>   Copy transport/http/server_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/server_test.go
>   Copy transport/http/doc.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/doc.go
>   Copy transport/http/request_response_funcs.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/request_response_funcs.go
>   Copy transport/http/client_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/client_test.go
>   Copy transport/http/encode_decode.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/encode_decode.go
>   Copy transport/http/client.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/client.go
>   Copy transport/http/jsonrpc/request_response_types_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/request_response_types_test.go
>   Copy transport/http/jsonrpc/server.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/server.go
>   Copy transport/http/jsonrpc/error_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/error_test.go
>   Copy transport/http/jsonrpc/server_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/server_test.go
>   Copy transport/http/jsonrpc/doc.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/doc.go
>   Copy transport/http/jsonrpc/client_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/client_test.go
>   Copy transport/http/jsonrpc/request_response_types.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/request_response_types.go
>   Copy transport/http/jsonrpc/encode_decode.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/encode_decode.go
>   Copy transport/http/jsonrpc/error.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/error.go
>   Copy transport/http/jsonrpc/client.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/jsonrpc/client.go
>   Copy transport/http/proto/server.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/server.go
>   Copy transport/http/proto/proto_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/proto_test.go
>   Copy transport/http/proto/proto_pb_test.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/proto_pb_test.go
>   Copy transport/http/proto/proto_test.proto -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/proto_test.proto
>   Copy transport/http/proto/client.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/http/proto/client.go
>   Copy transport/grpc/server.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/grpc/server.go
>   Copy transport/grpc/doc.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/grpc/doc.go
>   Copy transport/grpc/request_response_funcs.go -> 
> obj-x86_64-linux-gnu/src/github.com/go-kit/kit/transport/grpc/request_response_funcs.go
>   

Bug#1061034: c-evo-dh: FTBFS: make[1]: *** [debian/rules:39: override_dh_auto_build] Error 2

[Lucas Nussbaum]

Source: c-evo-dh
Version: 1.10-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> # Show versions
> lazbuild -v
> 3.0
> echo 1.10-1
> 1.10-1
> # Show location of gcc support files
> grep gcc /etc/fpc.cfg
> # path to the gcclib
> -Fl/usr/lib/gcc/x86_64-linux-gnu/13
> -Fl/usr/lib/gcc/x86_64-linux-gnu/13
> dirname `gcc -print-libgcc-file-name`
> /usr/lib/gcc/x86_64-linux-gnu/13
> # Use custom fpc.cfg
> cp Pascal/Release.cfg fpc.cfg
> cp Pascal/Release.cfg AI/StdAI/fpc.cfg
> cp Pascal/Release.cfg Packages/CevoComponents/fpc.cfg
> cp Pascal/Release.cfg Packages/Common/fpc.cfg
> #
> # Build AI module (Peephole broken in fpc < 3.2.4)
> cd AI/StdAI && fpc -dRelease -Xc -B -O3 -OoNOPEEPHOLE -k-znoexecstack 
> -k-zseparate-code -olibstdai.so StdAI.lpr
> Compiling Release Version
> Compile Release Version
> Free Pascal Compiler version 3.2.2+dfsg-32 [2024/01/05] for x86_64
> Copyright (c) 1993-2021 by Florian Klaempfl and others
> (1002) Target OS: Linux for x86-64
> (3104) Compiling StdAI.lpr
> (3104) Compiling Protocol.pas
> (3104) Compiling CustomAI.pas
> (3104) Compiling ToolAI.pas
> (3104) Compiling Pile.pas
> (3104) Compiling AI.pas
> (3104) Compiling Barbarina.pas
> (9015) Linking libstdai.so
> (1008) 10306 lines compiled, 0.6 sec
> #
> # Build GTK2 program
> rm -fr tmphome
> rm -fr lib
> rm -fr Packages/CevoComponents/lib
> lazbuild --bm=Release -B --ws=gtk2 --no-write-project Integrated.lpi
> CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> 
> /<>/tmphome/.lazarus/environmentoptions.xml
> Note: (lazarus) Invalid Package Link: file 
> "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist.
> 
>   $563872B27B7A
>   $563872B22B65
>   $563872A7EF2E
>   $5638730D0713
>   $563872C32C83
>   $563872C1D1DE
>   $563872C1D0D8
>   $563872A8313D
>   $563872A80D64
>   $563872A7F3EB
>   $563872A84C93
>   $563872A87979
>   $563872AA975C
> Error: (lazbuild) Package file not found
> The package "IdeConfig" is installed but no valid package file (.lpk) was 
> found.
> A broken dummy package was created.
> lazbuild is non interactive, aborting now.
> make[1]: *** [debian/rules:39: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/c-evo-dh_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-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=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.

Bug#1061031: bdebstrap: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept'

[Lucas Nussbaum]

Source: bdebstrap
Version: 0.6.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running doc
> running command: pandoc -s -t man bdebstrap.1.md -o bdebstrap.1
> running build_scripts
> creating build
> creating build/scripts-3.11
> copying and adjusting bdebstrap -> build/scripts-3.11
> changing mode of build/scripts-3.11/bdebstrap from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m unittest discover -v -s /<>
> test_get_path_exists (tests.TestGetPath.test_get_path_exists)
> Test get_path(__file__). ... ok
> test_get_path_missing (tests.TestGetPath.test_get_path_missing)
> Test non-existing file for get_path(). ... ok
> test_get_path_pybuild (tests.TestGetPath.test_get_path_pybuild)
> Test changing current directory before calling get_path(). ... ok
> test_black (tests.test_black.BlackTestCase.test_black)
> Test: Run black code formatter on Python source code. ... Running following 
> command:
> black --check --diff -l 99 /<>/bdebstrap tests 
> /<>/setup.py
> ok
> test_debug (tests.test_config.TestArguments.test_debug)
> Test --debug argument parsing. ... ok
> test_empty_args (tests.test_config.TestArguments.test_empty_args)
> Test setting arguments to empty strings. ... ok
> test_malformed_env (tests.test_config.TestArguments.test_malformed_env)
> Test malformed --env parameter (missing equal sign). ... ok
> test_mirrors_with_spaces 
> (tests.test_config.TestArguments.test_mirrors_with_spaces)
> Test --mirrors with leading/trailing spaces. ... ok
> test_no_args (tests.test_config.TestArguments.test_no_args)
> Test calling bdebstrap without arguments. ... ok
> test_optional_args (tests.test_config.TestArguments.test_optional_args)
> Test optional arguments (which also have positional ones). ... ok
> test_parse_env (tests.test_config.TestArguments.test_parse_env)
> Test parsing --env parameters. ... ok
> test_positional_args (tests.test_config.TestArguments.test_positional_args)
> Test positional arguments (overwriting optional ones). ... ok
> test_split (tests.test_config.TestArguments.test_split)
> Test splitting comma and space separated values. ... ok
> test_add_command_line_arguments 
> (tests.test_config.TestConfig.test_add_command_line_arguments)
> Test Config.add_command_line_arguments(). ... ok
> test_add_command_line_arguments_no_config 
> (tests.test_config.TestConfig.test_add_command_line_arguments_no_config)
> Test Config.add_command_line_arguments() with no config file. ... ok
> test_check_example (tests.test_config.TestConfig.test_check_example)
> Test example unstable.yaml file. ... ok
> test_commented_packages (tests.test_config.TestConfig.test_commented_packages)
> Test commented-packages.yaml file. ... ok
> test_config_and_arguments 
> (tests.test_config.TestConfig.test_config_and_arguments)
> Test Config.add_command_line_arguments() with config file and arguments. ... 
> ok
> test_env_items (tests.test_config.TestConfig.test_env_items)
> Test environment variables for example unstable.yaml. ... ok
> test_loading (tests.test_config.TestConfig.test_loading)
> Test loading a YAML configuration file. ... ok
> test_sanitize_packages_debs 
> (tests.test_config.TestConfig.test_sanitize_packages_debs)
> Test sanitize_packages method: multiple local .debs ... ok
> test_sanitize_packages_duplicate_debs 
> (tests.test_config.TestConfig.test_sanitize_packages_duplicate_debs)
> Test sanitize_packages method: remove duplicate local .debs. ... ok
> test_sanitize_packages_duplicates 
> (tests.test_config.TestConfig.test_sanitize_packages_duplicates)
> Test sanitize_packages method: remove duplicates. ... ok
> test_sanitize_packages_pattern 
> (tests.test_config.TestConfig.test_sanitize_packages_pattern)
> Test sanitize_packages method: APT pattern ... ok
> test_source_date_epoch (tests.test_config.TestConfig.test_source_date_epoch)
> Test getting and setting SOURCE_DATE_EPOCH. ... ok
> test_wrong_element_type (tests.test_config.TestConfig.test_wrong_element_type)
> Test error message for wrong list element type. ... ok
> test_yaml_rendering (tests.test_config.TestConfig.test_yaml_rendering)
> Test that config.yaml is formatted correctly. ... ok
> test_merge_lists (tests.test_config.TestDictMerge.test_merge_lists)
> Test merging nested dicts. ... ok
> test_merge_nested_dicts 
> (tests.test_config.TestDictMerge.test_merge_nested_dicts)
> 

Bug#1061030: wavbreaker: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: scour:native

[Lucas Nussbaum]

Source: wavbreaker
Version: 0.16-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -sa
> dpkg-buildpackage: info: source package wavbreaker
> dpkg-buildpackage: info: source version 0.16-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Dennis Braun 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-checkbuilddeps: error: Unmet build dependencies: scour:native
> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
> dpkg-buildpackage: warning: (Use -d flag to override.)
> 
> Build finished at 2024-01-15T20:25:04Z


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/wavbreaker_0.16-2_unstable.log

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

Bug#1061029: lookatme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: lookatme
Version: 2.5.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> Running Sphinx v7.2.6
> making output directory... done
> Creating file /<>/docs/source/autodoc/lookatme.rst.
> Creating file /<>/docs/source/autodoc/lookatme.ascii_art.rst.
> Creating file /<>/docs/source/autodoc/lookatme.config.rst.
> Creating file /<>/docs/source/autodoc/lookatme.exceptions.rst.
> Creating file /<>/docs/source/autodoc/lookatme.log.rst.
> Creating file /<>/docs/source/autodoc/lookatme.parser.rst.
> Creating file /<>/docs/source/autodoc/lookatme.pres.rst.
> Creating file /<>/docs/source/autodoc/lookatme.prompt.rst.
> Creating file /<>/docs/source/autodoc/lookatme.schemas.rst.
> Creating file /<>/docs/source/autodoc/lookatme.slide.rst.
> Creating file /<>/docs/source/autodoc/lookatme.tui.rst.
> Creating file /<>/docs/source/autodoc/lookatme.tutorial.rst.
> Creating file /<>/docs/source/autodoc/lookatme.utils.rst.
> Creating file /<>/docs/source/autodoc/lookatme.contrib.rst.
> Creating file 
> /<>/docs/source/autodoc/lookatme.contrib.file_loader.rst.
> Creating file 
> /<>/docs/source/autodoc/lookatme.contrib.terminal.rst.
> Creating file /<>/docs/source/autodoc/lookatme.render.rst.
> Creating file 
> /<>/docs/source/autodoc/lookatme.render.asciinema.rst.
> Creating file 
> /<>/docs/source/autodoc/lookatme.render.markdown_block.rst.
> Creating file 
> /<>/docs/source/autodoc/lookatme.render.markdown_inline.rst.
> Creating file 
> /<>/docs/source/autodoc/lookatme.render.pygments.rst.
> Creating file /<>/docs/source/autodoc/lookatme.themes.rst.
> Creating file /<>/docs/source/autodoc/lookatme.themes.dark.rst.
> Creating file /<>/docs/source/autodoc/lookatme.themes.light.rst.
> Creating file /<>/docs/source/autodoc/lookatme.widgets.rst.
> Creating file 
> /<>/docs/source/autodoc/lookatme.widgets.clickable_text.rst.
> Creating file /<>/docs/source/autodoc/lookatme.widgets.table.rst.
> Creating file /<>/docs/source/autodoc/modules.rst.
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 12 source files that are out of date
> updating environment: [new config] 40 added, 0 changed, 0 removed
> reading sources... [  2%] autodoc/lookatme
> reading sources... [  5%] autodoc/lookatme.ascii_art
> reading sources... [  8%] autodoc/lookatme.config
> reading sources... [ 10%] autodoc/lookatme.contrib
> reading sources... [ 12%] autodoc/lookatme.contrib.file_loader
> reading sources... [ 15%] autodoc/lookatme.contrib.terminal
> reading sources... [ 18%] autodoc/lookatme.exceptions
> reading sources... [ 20%] autodoc/lookatme.log
> reading sources... [ 22%] autodoc/lookatme.parser
> reading sources... [ 25%] autodoc/lookatme.pres
> reading sources... [ 28%] autodoc/lookatme.prompt
> reading sources... [ 30%] autodoc/lookatme.render
> reading sources... [ 32%] autodoc/lookatme.render.asciinema
> reading sources... [ 35%] autodoc/lookatme.render.markdown_block
> reading sources... [ 38%] autodoc/lookatme.render.markdown_inline
> reading sources... [ 40%] autodoc/lookatme.render.pygments
> reading sources... [ 42%] autodoc/lookatme.schemas
> reading sources... [ 45%] autodoc/lookatme.slide
> reading sources... [ 48%] autodoc/lookatme.themes
> reading sources... [ 50%] autodoc/lookatme.themes.dark
> reading sources... [ 52%] autodoc/lookatme.themes.light
> reading sources... [ 55%] autodoc/lookatme.tui
> reading sources... [ 57%] autodoc/lookatme.tutorial
> reading sources... [ 60%] autodoc/lookatme.utils
> reading sources... [ 62%] autodoc/lookatme.widgets
> reading sources... [ 65%] autodoc/lookatme.widgets.clickable_text
> reading sources... [ 68%] autodoc/lookatme.widgets.table
> reading sources... [ 70%] autodoc/modules
> reading sources... [ 72%] builtin_extensions/file_loader
> reading sources... [ 75%] builtin_extensions/index
> reading sources... [ 78%] builtin_extensions/terminal
> reading sources... [ 80%] contrib_extensions
> reading sources... [ 82%] contrib_extensions_auto
> reading sources... [ 85%] dark_theme
> reading sources... [ 88%] getting_started
> reading sources... [ 90%] index
> reading sources... [ 92%] light_theme
> reading sources... [ 95%] slides
> reading sources... [ 98%] smart_splitting
> reading sources... [100%] style_precedence
> 
> /<>/docs/source/../../lookatme/contrib/__init__.py:docstring of 
> lookatme.contrib:7: WARNING: Inline emphasis start-string without end-string.
> /<>/docs/source/../../lookatme/contrib/__init__.py:docstring of 
> lookatme.contrib:7: WARNING: Inline strong start-string without end-string.
> 

Bug#1061026: python-watchgod: FTBFS: FAILED tests/test_watch.py::test_watch_log[trio] - RuntimeError: Already runn...

[Lucas Nussbaum]

Source: python-watchgod
Version: 0.8.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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
> I: pybuild base:305: python3.12 setup.py config 
> running config
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/version.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/main.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/watcher.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/__main__.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/cli.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/py.typed -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/version.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/main.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/watcher.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/cli.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/py.typed -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_watchgod/build; python3.12 -m pytest 
> -W ignore::trio.TrioDeprecationWarning
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> configfile: setup.cfg
> plugins: anyio-4.1.0, asyncio-0.20.3, toolbox-0.4, sugar-0.9.7, mock-3.12.0
> asyncio: mode=Mode.STRICT
> collected 162 items
> 
> tests/test_cli.py .. [ 
> 33%]
> ...  [ 
> 42%]
> tests/test_run_process.py F..[ 
> 51%]
> tests/test_watch.py  [ 
> 83%]
> ....F..F..   
> [100%]
> 
> === FAILURES 
> ===
> _ test_async_alive_terminates[asyncio+uvloop] 
> __
> 
> pyfuncitem = 
> 
> @pytest.hookimpl(tryfirst=True)
> def pytest_pyfunc_call(pyfuncitem: Any) -> bool | None:
> def run_with_hypothesis(**kwargs: Any) -> None:
> with get_runner(backend_name, backend_options) as runner:
> runner.run_test(original_func, kwargs)
> 
> backend = pyfuncitem.funcargs.get("anyio_backend")
> if backend:
> backend_name, backend_options = 
> extract_backend_and_options(backend)
> 
> if hasattr(pyfuncitem.obj, "hypothesis"):
> # Wrap the inner test function unless it's already wrapped
> original_func = pyfuncitem.obj.hypothesis.inner_test
> if original_func.__qualname__ != 
> run_with_hypothesis.__qualname__:
> if iscoroutinefunction(original_func):
> pyfuncitem.obj.hypothesis.inner_test = 
> run_with_hypothesis
> 
> return None
> 
> if iscoroutinefunction(pyfuncitem.obj):
> funcargs = pyfuncitem.funcargs
> testargs = {arg: funcargs[arg] for arg in 
> pyfuncitem._fixtureinfo.argnames}
> >   with get_runner(backend_name, backend_options) as runner:
> 
> /usr/lib/python3/dist-packages/anyio/pytest_plugin.py:123: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3.12/contextlib.py:137: in __enter__
> return next(self.gen)
> /usr/lib/python3/dist-packages/anyio/pytest_plugin.py:45: in get_runner
> asynclib.create_test_runner(backend_options)
> /usr/lib/python3/dist-packages/anyio/_backends/_asyncio.py:2431: in 
> create_test_runner
> 

Bug#1061028: flask-restful: FTBFS: intersphinx inventory 'six/objects.inv' not fetchable due to : [Errno 2] No such file or directory: '/<>/docs/six/objects.inv

[Lucas Nussbaum]

Source: flask-restful
Version: 0.3.9-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v7.2.6
> making output directory... done
> WARNING: The pre-Sphinx 1.0 'intersphinx_mapping' format is deprecated and 
> will be removed in Sphinx 8. Update to the current format as described in the 
> documentation. Hint: "intersphinx_mapping = {'': ('six', 
> None)}".https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
> loading intersphinx inventory from 
> /usr/share/doc/python-flask-doc/html/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory '/usr/share/doc/python-flask-doc/html/objects.inv' not 
> fetchable due to : [Errno 2] No such file or 
> directory: '/usr/share/doc/python-flask-doc/html/objects.inv'
> loading intersphinx inventory from 
> /usr/share/doc/python-werkzeug-doc/html/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory '/usr/share/doc/python-werkzeug-doc/html/objects.inv' 
> not fetchable due to : [Errno 2] No such file or 
> directory: '/usr/share/doc/python-werkzeug-doc/html/objects.inv'
> loading intersphinx inventory from 
> /usr/share/doc/python3-doc/html/objects.inv...
> loading intersphinx inventory from 
> /usr/share/doc/python3-doc/html/objects.inv...
> loading intersphinx inventory from six/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'six/objects.inv' not fetchable due to  'FileNotFoundError'>: [Errno 2] No such file or directory: 
> '/<>/docs/six/objects.inv'
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 9 source files that are out of date
> updating environment: [new config] 9 added, 0 changed, 0 removed
> reading sources... [ 11%] api
> reading sources... [ 22%] extending
> reading sources... [ 33%] fields
> reading sources... [ 44%] index
> reading sources... [ 56%] installation
> reading sources... [ 67%] intermediate-usage
> reading sources... [ 78%] quickstart
> reading sources... [ 89%] reqparse
> reading sources... [100%] testing
> 
> /<>/flask_restful/__init__.py:docstring of 
> flask_restful.Api.unauthorized:1: WARNING: duplicate object description of 
> flask_restful.Api.unauthorized, other instance in api, use :no-index: for one 
> of them
> /<>/docs/index.rst:6: WARNING: duplicate object description of 
> flask_restful, other instance in api, use :no-index: for one of them
> /<>/docs/reqparse.rst:217: WARNING: Explicit markup ends without 
> a blank line; unexpected unindent.
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> writing output... [ 11%] api
> writing output... [ 22%] extending
> writing output... [ 33%] fields
> writing output... [ 44%] index
> writing output... [ 56%] installation
> writing output... [ 67%] intermediate-usage
> writing output... [ 78%] quickstart
> writing output... [ 89%] reqparse
> writing output... [100%] testing
> 
> /<>/docs/intermediate-usage.rst:80: WARNING: undefined label: 
> 'blueprints'
> generating indices... genindex py-modindex done
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 8 warnings.
> 
> The HTML pages are in _build/html.
> 
> Build finished. The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/docs'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_flask-restful/build; python3.12 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> collected 318 items
> 
> tests/test_accept.py [  
> 3%]
> tests/test_api.py x.F... [ 
> 20%]
> ...FF... [ 
> 29%]
> tests/test_api_with_blueprint.py .   [ 
> 33%]
> tests/test_cors.py   [ 
> 34%]
> tests/test_fields.py ... [ 
> 50%]
>  [ 
> 57%]
> 

Bug#1061027: moment-timezone.js: FTBFS: make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1

[Lucas Nussbaum]

Source: moment-timezone.js
Version: 0.5.43+dfsg-1+2023c
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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
>dh_update_autotools_config
>dh_autoreconf
>debian/rules execute_before_dh_auto_configure
> make[1]: Entering directory '/<>'
> # Fail the build if the tzdata package does not match TZVER.
> grep -q '^# version 2023c$' /usr/share/zoneinfo/tzdata.zi
> make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/moment-timezone.js_0.5.43+dfsg-1+2023c_unstable.log

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

Bug#1061024: transgui: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory

[Lucas Nussbaum]

Source: transgui
Version: 5.18.0+dfsg-3.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> lazbuild -B transgui.lpi --lazarusdir=/usr/lib/lazarus/default/
> CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> 
> /sbuild-nonexistent/.lazarus/environmentoptions.xml
> WARNING: unable to create primary config directory 
> "/sbuild-nonexistent/.lazarus"
> SetupCompilerFilename: Searching compiler ...
> SearchCompilerCandidates Value=/usr/bin/fpc File=/usr/bin/fpc
> SetupCompilerFilename: using /usr/bin/fpc
> Hint: (lazarus) storing Lazarus directory "/usr/lib/lazarus/default/" 
> Compiler path "/usr/bin/fpc" in 
> "/sbuild-nonexistent/.lazarus/environmentoptions.xml"
> Error: (lazarus) unable to edit file 
> /sbuild-nonexistent/.lazarus/environmentoptions.xml
> InitializeFppkg failed: Unable to create file 
> "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory
> Note: (lazarus) Invalid Package Link: file 
> "/usr/lib/lazarus/default/ide/packages/ideconfig/ideconfig.lpk" does not 
> exist.
> 
>   $55596A94CB7A
>   $55596A947B65
>   $55596A8A3F2E
>   $55596AEF5713
>   $55596AA57C83
>   $55596AA421DE
>   $55596AA420D8
>   $55596A8A813D
>   $55596A8A5D64
>   $55596A8A43EB
>   $55596A8A9C93
>   $55596A8AC979
>   $55596A8CE75C
> Error: (lazbuild) Package file not found
> The package "IdeConfig" is installed but no valid package file (.lpk) was 
> found.
> A broken dummy package was created.
> lazbuild is non interactive, aborting now.
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/transgui_5.18.0+dfsg-3.1_unstable.log

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

Bug#1061023: svtplay-dl: FTBFS: ModuleNotFoundError: No module named 'distutils.core'

[Lucas Nussbaum]

Source: svtplay-dl
Version: 3.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> argparse-manpage \
>   --project-name svtplay-dl \
>   --author 'Johan Andersson' \
>   --author-email 'j...@i19.se' \
>   --pyfile lib/svtplay_dl/utils/parser.py \
>   --function gen_parser \
>   --url https://svtplay-dl.se/ \
>   --output svtplay-dl.1
> Traceback (most recent call last):
>   File "/usr/bin/argparse-manpage", line 5, in 
> from build_manpages.cli import main
>   File "/usr/lib/python3/dist-packages/build_manpages/cli/__init__.py", line 
> 5, in 
> from build_manpages.build_manpage import ManPageWriter, get_parser
>   File "/usr/lib/python3/dist-packages/build_manpages/build_manpage.py", line 
> 10, in 
> from distutils.core import Command
> ModuleNotFoundError: No module named 'distutils.core'
> make[1]: *** [debian/rules:25: svtplay-dl.1] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/svtplay-dl_3.0-2_unstable.log

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

Bug#1061021: cinnamon-control-center: FTBFS: Package 'libevdev', required by 'libwacom', not found

[Lucas Nussbaum]

Source: cinnamon-control-center
Version: 5.8.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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=gnome
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   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
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: cinnamon-control-center
> Project version: 5.8.2
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Library m found: YES
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Run-time dependency cinnamon-desktop found: YES 5.8.0
> Run-time dependency libcinnamon-menu-3.0 found: YES 6.0.0
> Run-time dependency gtk+-3.0 found: YES 3.24.39
> Run-time dependency glib-2.0 found: YES 2.78.3
> Run-time dependency gio-unix-2.0 found: YES 2.78.3
> Run-time dependency gudev-1.0 found: YES 238
> Run-time dependency libgnomekbd found: YES 3.28.1
> Run-time dependency libgnomekbdui found: YES 3.28.1
> Run-time dependency libnotify found: YES 0.8.3
> Run-time dependency x11 found: YES 1.8.7
> Run-time dependency polkit-gobject-1 found: YES 123
> Run-time dependency libxklavier found: YES 5.4
> Run-time dependency upower-glib found: YES 1.90.2
> Has header "X11/extensions/XKB.h" : YES 
> Run-time dependency iso-codes found: YES 4.16.0
> Run-time dependency libnm found: YES 1.44.2
> Run-time dependency libnma found: YES 1.10.6
> Run-time dependency mm-glib found: YES 1.22.0
> Run-time dependency colord found: YES 1.4.6
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency libwacom found: NO 
> 
> ../meson.build:86:14: ERROR: Dependency lookup for libwacom with method 
> 'pkgconfig' failed: Could not generate cflags for libwacom:
> Package libevdev was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libevdev.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libevdev', required by 'libwacom', not found
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2024-01-15T20:22:22.141671
> Main binary: /usr/bin/python3
> Build Options: -Dpython.bytecompile=-1 -Dprefix=/usr 
> -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc 
> -Dbuildtype=plain -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: cinnamon-control-center
> Project version: 5.8.2
> ---
> Detecting compiler via: `cc --version` -> 0
> stdout:
> cc (Debian 13.2.0-9) 13.2.0
> Copyright (C) 2023 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> ---
> Running command: cc -E -dM -
> -
> ---
> Detecting linker via: `cc -Wl,--version -Wl,-z,relro -Wl,-z,now -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2` -> 0
> stdout:
> GNU ld (GNU Binutils for Debian) 2.41.50.20231227
> Copyright (C) 2023 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or (at your option) a later version.
> This program has absolutely no warranty.
> ---
> stderr:
> collect2 version 13.2.0
> /usr/bin/ld -plugin /usr/libexec/gcc/x86_64-linux-gnu/13/liblto_plugin.so 
> -plugin-opt=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper 
> -plugin-opt=-fresolution=/tmp/ccwNlt0l.res -plugin-opt=-pass-through=-lgcc 
> -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc 
> -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id 
> --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker 
> /lib64/ld-linux-x86-64.so.2 -pie 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/Scrt1.o 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/13/crtbeginS.o 
> -L/usr/lib/gcc/x86_64-linux-gnu/13 
> -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu 
> 

Bug#1061020: libervia-pubsub: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_install] Error 25

[Lucas Nussbaum]

Source: libervia-pubsub
Version: 0.4.0+hg488-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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_install --destdir=debian/tmp
> I: pybuild base:305: /usr/bin/python3.12 setup.py install --root 
> /<>/debian/tmp --install-lib=/usr/share/libervia 
> --install-scripts=/usr/share/libervia --verbose
> /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)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools_scm/_integration/setuptools.py:90: 
> UserWarning: version of sat_pubsub already set
>   warnings.warn(f"version of {dist_name} already set")
> /usr/lib/python3/dist-packages/setuptools/dist.py:509: 
> SetuptoolsDeprecationWarning: Invalid version: '0.5.0D'.
> !!
> 
> 
> 
> The version specified is not a valid version according to PEP 440.
> This may not work as expected with newer versions of
> setuptools, pip, and PyPI.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See https://peps.python.org/pep-0440/ for details.
> 
> 
> 
> !!
>   self._validate_version(self.metadata.version)
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running build
> running build_py
> running install_lib
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/share
> creating /<>/debian/tmp/usr/share/libervia
> creating /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/__init__.py 
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/error.py -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/container.py 
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying 
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/exceptions.py -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/const.py -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/iidavoll.py 
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/privilege.py 
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/mam.py -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/pam.py -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying 
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/pubsub_admin.py -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying 
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/pgsql_storage.py -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> creating /<>/debian/tmp/usr/share/libervia/sat_pubsub/test
> copying 
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/test/test_storage.py 
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub/test
> copying 
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/test/__init__.py -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub/test
> copying 
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/test/test_backend.py 
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub/test
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/backend.py 
> -> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying /<>/.pybuild/cpython3_3.12/build/sat_pubsub/VERSION -> 
> /<>/debian/tmp/usr/share/libervia/sat_pubsub
> copying 
> /<>/.pybuild/cpython3_3.12/build/sat_pubsub/delegation.py -> 
> 

Bug#1061016: sccache: FTBFS: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: sccache
Version: 0.7.4-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-cargo, help2man, 
> librust-anyhow-1+backtrace-dev, librust-anyhow-1+default-dev, 
> librust-ar-0.9+default-dev, librust-assert-cmd-2+default-dev, 
> librust-async-trait-0.1+default-dev (>= 0.1.52), 
> librust-atty-0.2+default-dev, librust-base64-0.21+default-dev, 
> librust-bincode-1+default-dev, librust-blake3-1+default-dev, 
> librust-byteorder-1+default-dev, librust-bytes-1+default-dev, 
> librust-chrono-0.4+default-dev, librust-clap-4+default-dev, 
> librust-counted-array-0.1+default-dev, librust-daemonize-0.5+default-dev, 
> librust-directories-5+default-dev, librust-encoding-0.2+default-dev, 
> librust-env-logger-0.10+default-dev, librust-filetime-0.2+default-dev, 
> librust-flate2-1+rust-backend-dev, librust-fs-err-2+default-dev, 
> librust-futures-0.3+default-dev, librust-futures-locks-0.7+default-dev, 
> librust-http-0.2+default-dev, librust-hyper-0.14+default-dev (>= 0.14.19), 
> librust-hyper-0.14+server-dev, librust-is-terminal-0.4+default-dev, 
> librust-itertools-0.10+default-dev, librust-jobserver-0.1+default-dev, 
> librust-libc-0.2+default-dev, librust-linked-hash-map-0.5+default-dev, 
> librust-log-0.4+default-dev, librust-memchr-2+default-dev, 
> librust-memmap2-0.9+default-dev, librust-mime-0.3+default-dev, 
> librust-num-cpus-1+default-dev, librust-number-prefix-0.4+default-dev, 
> librust-object-dev (<< 0.32), librust-once-cell-1+default-dev (>= 1.17), 
> librust-predicates-3+default-dev, librust-rand-0.8+default-dev, 
> librust-regex-1+default-dev, librust-reqwest-0.11+blocking-dev, 
> librust-reqwest-0.11+default-dev, librust-reqwest-0.11+json-dev, 
> librust-reqwest-0.11+rustls-tls-dev, librust-reqwest-0.11+stream-dev, 
> librust-reqwest-0.11+trust-dns-dev, librust-retry-2+default-dev, 
> librust-semver-1+default-dev, librust-serde-1+default-dev, 
> librust-serde-1+derive-dev, librust-serde-json-1+default-dev, 
> librust-serial-test-2+default-dev, librust-sha2-0.10+default-dev, 
> librust-strip-ansi-escapes-0.1+default-dev, librust-tar-0.4+default-dev, 
> librust-tempfile-3+default-dev, librust-test-case-3+default-dev, 
> librust-tokio-1+default-dev, librust-tokio-1+io-util-dev, 
> librust-tokio-1+macros-dev, librust-tokio-1+net-dev, 
> librust-tokio-1+process-dev, librust-tokio-1+rt-multi-thread-dev, 
> librust-tokio-1+time-dev, librust-tokio-serde-0.8+default-dev, 
> librust-tokio-util-0.7+codec-dev, librust-tokio-util-0.7+default-dev, 
> librust-tokio-util-0.7+io-dev, librust-toml-dev (<< 0.9), 
> librust-tower-0.4+default-dev, librust-trust-dns-resolver-0.22+default-dev, 
> librust-trust-dns-resolver-0.22+dns-over-https-rustls-dev, 
> librust-trust-dns-resolver-0.22+dns-over-rustls-dev, 
> librust-trust-dns-resolver-0.22+dnssec-ring-dev, librust-url-2+default-dev, 
> librust-uuid-1+default-dev, librust-uuid-1+v4-dev, 
> librust-walkdir-2+default-dev, librust-which-4-dev, librust-zip-0.6-dev, 
> librust-zstd-dev (<< 0.14), libstring-shellquote-perl, rustc (>= 1.65), 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-cargo, help2man, 
> librust-anyhow-1+backtrace-dev, librust-anyhow-1+default-dev, 
> librust-ar-0.9+default-dev, librust-assert-cmd-2+default-dev, 
> librust-async-trait-0.1+default-dev (>= 0.1.52), 
> librust-atty-0.2+default-dev, librust-base64-0.21+default-dev, 
> librust-bincode-1+default-dev, librust-blake3-1+default-dev, 
> librust-byteorder-1+default-dev, librust-bytes-1+default-dev, 
> librust-chrono-0.4+default-dev, librust-clap-4+default-dev, 
> librust-counted-array-0.1+default-dev, librust-daemonize-0.5+default-dev, 
> librust-directories-5+default-dev, librust-encoding-0.2+default-dev, 
> librust-env-logger-0.10+default-dev, librust-filetime-0.2+default-dev, 
> librust-flate2-1+rust-backend-dev, librust-fs-err-2+default-dev, 
> librust-futures-0.3+default-dev, librust-futures-locks-0.7+default-dev, 
> librust-http-0.2+default-dev, librust-hyper-0.14+default-dev (>= 0.14.19), 
> librust-hyper-0.14+server-dev, librust-is-terminal-0.4+default-dev, 
> librust-itertools-0.10+default-dev, librust-jobserver-0.1+default-dev, 
> librust-libc-0.2+default-dev, librust-linked-hash-map-0.5+default-dev, 
> librust-log-0.4+default-dev, librust-memchr-2+default-dev, 
> librust-memmap2-0.9+default-dev, librust-mime-0.3+default-dev, 
> librust-num-cpus-1+default-dev, librust-number-prefix-0.4+default-dev, 
> librust-object-dev 

Bug#1061018: octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134

[Lucas Nussbaum]

Source: octave-splines
Version: 1.3.5-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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=octave
>dh_update_autotools_config -O--buildsystem=octave
>dh_autoreconf -O--buildsystem=octave
>dh_octave_version -O--buildsystem=octave
> Checking the Octave version... ok
>dh_auto_configure -O--buildsystem=octave
>dh_auto_build -O--buildsystem=octave
>dh_auto_test -O--buildsystem=octave
>create-stamp debian/debhelper-build-stamp
>dh_testroot -O--buildsystem=octave
>dh_prep -O--buildsystem=octave
>dh_auto_install --destdir=debian/octave-splines/ -O--buildsystem=octave
>   octave --no-gui --no-history --silent --no-init-file --no-window-system 
> /usr/share/dh-octave/install-pkg.m 
> /<>/debian/octave-splines/usr/share/octave/packages 
> /<>/debian/octave-splines/usr/lib/x86_64-linux-gnu/octave/packages
> For information about changes from previous versions of the splines package, 
> run 'news splines'.
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Run the unit tests...
> Checking m files ...
> [inst/tps_val_der.m]
> > /<>/inst/tps_val_der.m
> * shared a,b,x,y,x1,x2,y1,c,dy,dy0
>  a = 2; b = -3; x = ([1:2:10 10.5 11.3])'; y = a*x;
>  c = tpaps(x,y,1);
> * assert (a*ones(size(x)), tps_val_der(x,c,x), 1E3*eps);
>  [x1 x2] = meshgrid(x, x);
>  y1 = a*x1+b*x2;
>  c = tpaps([x1(:) x2(:)],y1(:),0.5);
>  dy = tps_val_der([x1(:) x2(:)],c,[x1(:) x2(:)]);
>  dy0 = tps_val_der([x1(:) x2(:)],c,[x1(:) x2(:)],false);
> * assert (a*ones(size(x1(:))), dy(:, 1), 1E3*eps);
> * assert (b*ones(size(x2(:))), dy(:, 2), 1E3*eps); 
> * assert (dy0, dy, 1E3*eps);
> 4 tests, 4 passed, 0 known failure, 0 skipped
> [inst/bin_values.m]
> > /<>/inst/bin_values.m
> * shared x, y, x_bin, y_bin, w_bin, n_bin
>  x = [1; 2; 2; 3; 4];
>  y = [0 0; 1 1; 2 1; 3 4; 5 NaN];
>  [x_bin y_bin w_bin n_bin] = bin_values(x, y);
> * assert (x_bin, [1; 7/3]);
> * assert (y_bin, [0 0; 2 2]);
> * assert (!any(isfinite(w_bin(1, :;
> * assert (w_bin(2, :), [3 1]);
> * assert (n_bin, [1; 3]);
> 5 tests, 5 passed, 0 known failure, 0 skipped
> [inst/csaps_sel.m]
> > /<>/inst/csaps_sel.m
> * shared x,y,ret,p,sigma2,unc_y
>  x = [0:0.01:1]'; y = sin(x);
>  [ret,p,sigma2,unc_y] = csaps_sel(x,y,x);
> malloc(): invalid size (unsorted)
> fatal: caught signal Aborted -- stopping myself...
> Aborted
> make: *** [debian/rules:5: binary] Error 134


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/octave-splines_1.3.5-2_unstable.log

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

Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134

[Lucas Nussbaum]

Source: octave-divand
Version: 1.1.2+dfsg-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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=octave
>dh_update_autotools_config -O--buildsystem=octave
>dh_autoreconf -O--buildsystem=octave
>dh_octave_version -O--buildsystem=octave
> Checking the Octave version... ok
>dh_auto_configure -O--buildsystem=octave
>dh_auto_build -O--buildsystem=octave
>dh_auto_test -O--buildsystem=octave
>create-stamp debian/debhelper-build-stamp
>dh_testroot -O--buildsystem=octave
>dh_prep -O--buildsystem=octave
>dh_auto_install --destdir=debian/octave-divand/ -O--buildsystem=octave
>   octave --no-gui --no-history --silent --no-init-file --no-window-system 
> /usr/share/dh-octave/install-pkg.m 
> /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/share/octave/packages
>  
> /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/lib/x86_64-linux-gnu/octave/packages
> For information about changes from previous versions of the divand package, 
> run 'news divand'.
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Run the unit tests...
> Checking m files ...
> [inst/statevector_init.m]
> > /<>/inst/statevector_init.m
> * test
>  mask = rand(10,10) > .5;
>  mask_u = rand(9,10) > .5;
>  mask_v = rand(10,9) > .5;
>  sv = statevector_init(mask,mask_u,mask_v);
>  var = rand(10,10); 
>  var(mask==0) = 0;
>  var_u = rand(9,10);
>  var_u(mask_u==0) = 0;
>  var(mask==0) = 0;
>  var_v = rand(10,9);
>  var_v(mask_v==0) = 0;
>  [E] = statevector_pack(sv,var,var_u,var_v);
>  [Ezeta2,Eu2,Ev2] = statevector_unpack(sv,E);
>  assert(Ezeta2,var)
>  assert(Eu2,var_u)
>  assert(Ev2,var_v)
> 1 test, 1 passed, 0 known failure, 0 skipped
> Checking C++ files ...
> Run tests in debian/check.m
> [test_divand]
> run test_interp_1d: (max difference=2.77556e-16)   OK  
> run test_interp_2d: (max difference=2.22045e-16)   OK  
> run test_interp_regular: (max difference=2.22045e-16)   OK  
> run test_sparse_diff: (max difference=0)   OK  
> run test_1dvar: malloc(): invalid size (unsorted)
> fatal: caught signal Aborted -- stopping myself...
> Aborted
> make: *** [debian/rules:5: binary] Error 134


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/octave-divand_1.1.2+dfsg-6_unstable.log

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

Bug#1061015: pygame-sdl2: FTBFS: make: *** [debian/rules:6: binary] Error 25

[Lucas Nussbaum]

Source: pygame-sdl2
Version: 8.1.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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:305: python3.12 setup.py config 
> /<>/setuplib.py:269: SyntaxWarning: invalid escape sequence '\('
>   ccode = re.sub('Py_InitModule4\("([^"]+)"', 'Py_InitModule4("' + 
> parent_module + '.\\1"', ccode) # Py2
> 
> Error compiling Cython file:
> 
> ...
> sf.base = base
> sf.length = length
> sf.tell = 0
> 
> rv = SDL_AllocRW()
> rv.size = subfile_size
>   ^
> 
> 
> src/pygame_sdl2/rwobject.pyx:336:22: Cannot assign type 'Sint64 (SDL_RWops *) 
> except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'. Exception values are 
> incompatible. Suggest adding 'noexcept' to type 'Sint64 (SDL_RWops *) except? 
> -1 nogil'.
> 
> Error compiling Cython file:
> 
> ...
> sf.length = length
> sf.tell = 0
> 
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
>   ^
> 
> 
> src/pygame_sdl2/rwobject.pyx:337:22: Cannot assign type 'Sint64 (SDL_RWops *, 
> Sint64, int) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *, Sint64, int) 
> noexcept'. Exception values are incompatible. Suggest adding 'noexcept' to 
> type 'Sint64 (SDL_RWops *, Sint64, int) except? -1 nogil'.
> 
> Error compiling Cython file:
> 
> ...
> sf.tell = 0
> 
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
> rv.read = subfile_read
>   ^
> 
> 
> src/pygame_sdl2/rwobject.pyx:338:22: Cannot assign type 'size_t (SDL_RWops *, 
> void *, size_t, size_t) except? -1 nogil' to 'size_t (*)(SDL_RWops *, void *, 
> size_t, size_t) noexcept'. Exception values are incompatible. Suggest adding 
> 'noexcept' to type 'size_t (SDL_RWops *, void *, size_t, size_t) except? -1 
> nogil'.
> 
> Error compiling Cython file:
> 
> ...
> rv = SDL_AllocRW()
> rv.size = subfile_size
> rv.seek = subfile_seek
> rv.read = subfile_read
> rv.write = NULL
> rv.close = subfile_close
>^
> 
> 
> src/pygame_sdl2/rwobject.pyx:340:23: Cannot assign type 'int (SDL_RWops *) 
> except? -1 nogil' to 'int (*)(SDL_RWops *) noexcept'. Exception values are 
> incompatible. Suggest adding 'noexcept' to type 'int (SDL_RWops *) except? -1 
> nogil'.
> 
> Error compiling Cython file:
> 
> ...
> raise IOError("{!r} is not a filename or file-like 
> object.".format(filelike))
> 
> Py_INCREF(filelike)
> 
> rv = SDL_AllocRW()
> rv.size = python_size
>   ^
> 
> 
> src/pygame_sdl2/rwobject.pyx:367:14: Cannot assign type 'Sint64 (SDL_RWops *) 
> except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'. Exception values are 
> incompatible. Suggest adding 'noexcept' to type 'Sint64 (SDL_RWops *) except? 
> -1 nogil'.
> 
> Error compiling Cython file:
> 
> ...
> 
> Py_INCREF(filelike)
> 
> rv = SDL_AllocRW()
> rv.size = python_size
> rv.seek = python_seek
>   ^
> 
> 
> src/pygame_sdl2/rwobject.pyx:368:14: Cannot assign type 'Sint64 (SDL_RWops *, 
> Sint64, int) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *, Sint64, int) 
> noexcept'. Exception values are incompatible. Suggest adding 'noexcept' to 
> type 'Sint64 (SDL_RWops *, Sint64, int) except? -1 nogil'.
> 
> Error compiling Cython file:
> 
> ...
> Py_INCREF(filelike)
> 
> rv = SDL_AllocRW()
> rv.size = python_size
> rv.seek = python_seek
> rv.read = python_read
>   ^
> 
> 
> src/pygame_sdl2/rwobject.pyx:369:14: Cannot assign type 'size_t (SDL_RWops *, 
> void *, size_t, size_t) except? -1 nogil' to 

Bug#1061014: apertium-isl-eng: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: apertium-isl-eng
Version: 0.1.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> apertium-regtest test
> Corpus 1 of 2: isl-eng-pending
>   0/219 (0.0%) tests pass
> 
> Corpus 2 of 2: isl-eng-regression
>   0/201 (0.0%) tests pass
> 
> There were changes! Rerun in interactive mode to update tests.
> Changed corpora: isl-eng-pending, isl-eng-regression
> make[1]: *** [Makefile:788: test] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/apertium-isl-eng_0.1.2-1_unstable.log

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

Bug#1061010: click: FTBFS: tests failed

[Lucas Nussbaum]

Source: click
Version: 0.5.0-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> set -e; for python in python3.12 python3; do \
>   $python setup.py test; \
> done
> /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
> Normalizing '0.5.0-9' to '0.5.0.post9'
>   self.metadata.version = self._normalize_version(
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> /usr/lib/python3/dist-packages/setuptools/command/test.py:193: 
> _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`.
> 
> 
> 
> !!
>   ir_d = dist.fetch_build_eggs(dist.install_requires)
> /usr/lib/python3/dist-packages/setuptools/command/test.py:194: 
> _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`.
> 
> 
> 
> !!
>   tr_d = dist.fetch_build_eggs(dist.tests_require or [])
> /usr/lib/python3/dist-packages/setuptools/command/test.py:195: 
> _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`.
> 
> 
> 
> !!
>   er_d = dist.fetch_build_eggs(
> running egg_info
> creating click.egg-info
> writing click.egg-info/PKG-INFO
> writing dependency_links to click.egg-info/dependency_links.txt
> writing top-level names to click.egg-info/top_level.txt
> writing manifest file 'click.egg-info/SOURCES.txt'
> reading manifest file 'click.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'click.egg-info/SOURCES.txt'
> running build_ext
> /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
> Normalizing '0.5.0-9' to '0.5.0.post9'
>   self.metadata.version = self._normalize_version(
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> /usr/lib/python3/dist-packages/setuptools/command/test.py:193: 
> _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`.
> 
> 
> 
> !!
>   ir_d = dist.fetch_build_eggs(dist.install_requires)
> /usr/lib/python3/dist-packages/setuptools/command/test.py:194: 
> _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`.
> 
> 
> 
> !!
>   tr_d = dist.fetch_build_eggs(dist.tests_require or [])
> /usr/lib/python3/dist-packages/setuptools/command/test.py:195: 
> _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`.
> 
> 
> 
> !!
>   er_d = dist.fetch_build_eggs(
> running egg_info
> writing click.egg-info/PKG-INFO
> writing dependency_links to click.egg-info/dependency_links.txt
> 

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

[Lucas Nussbaum]

Source: aiohttp-jinja2
Version: 1.5.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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:305: python3.12 setup.py config 
> running config
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/typedefs.py -> 
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/helpers.py -> 
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> running egg_info
> creating aiohttp_jinja2.egg-info
> writing aiohttp_jinja2.egg-info/PKG-INFO
> writing dependency_links to aiohttp_jinja2.egg-info/dependency_links.txt
> writing requirements to aiohttp_jinja2.egg-info/requires.txt
> writing top-level names to aiohttp_jinja2.egg-info/top_level.txt
> writing manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> reading manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'pytest.ini'
> warning: no directories found matching 'examples'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> adding license file 'LICENSE'
> writing manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> copying aiohttp_jinja2/py.typed -> 
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build/aiohttp_jinja2
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/typedefs.py -> 
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
> copying aiohttp_jinja2/helpers.py -> 
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
> running egg_info
> writing aiohttp_jinja2.egg-info/PKG-INFO
> writing dependency_links to aiohttp_jinja2.egg-info/dependency_links.txt
> writing requirements to aiohttp_jinja2.egg-info/requires.txt
> writing top-level names to aiohttp_jinja2.egg-info/top_level.txt
> reading manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'pytest.ini'
> warning: no directories found matching 'examples'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> adding license file 'LICENSE'
> writing manifest file 'aiohttp_jinja2.egg-info/SOURCES.txt'
> copying aiohttp_jinja2/py.typed -> 
> /<>/.pybuild/cpython3_3.11_aiohttp-jinja2/build/aiohttp_jinja2
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_aiohttp-jinja2/build; python3.12 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> configfile: setup.cfg
> plugins: cov-4.1.0, anyio-4.1.0, asyncio-0.20.3, aiohttp-1.0.5
> asyncio: mode=Mode.AUTO
> collected 30 items
> 
> tests/test_context_processors.py F   [ 
> 16%]
> tests/test_jinja_filters.py F[ 
> 20%]
> tests/test_jinja_globals.py  [ 
> 46%]
> tests/test_simple_renderer.py F.FF   
> [100%]
> 
> === FAILURES 
> ===
> ___ test_context_processors 
> 
> 
> aiohttp_client = .go at 0x7fe063cbfa60>
> 
> async def test_context_processors(aiohttp_client):
> @aiohttp_jinja2.template("tmpl.jinja2")
> async def func(request):
> return {"bar": 2}
> 
> app = 
> web.Application(middlewares=[aiohttp_jinja2.context_processors_middleware])
> >   aiohttp_jinja2.setup(
> app,
> loader=jinja2.DictLoader(
> {"tmpl.jinja2": "foo: {{ foo }}, bar: {{ bar }}, path: {{ 
> request.path }}"}
> ),
> )
> 
> tests/test_context_processors.py:15: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> aiohttp_jinja2/__init__.py:82: in setup
> app[app_key] = env
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Bug#1061011: octave-zeromq: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1

[Lucas Nussbaum]

Source: octave-zeromq
Version: 1.5.6-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> ( cd doc ;\
>   texi2pdf -q zeromq.texi ;   \
>   makeinfo zeromq.texi )
> /usr/bin/texi2dvi: pdfetex exited with bad status, quitting.
> zeromq.texi:17: @include: could not find version.texi
> zeromq.texi:22: warning: undefined flag: VERSION
> zeromq.texi:119: warning: undefined flag: VERSION
> zeromq.texi:240: @include: could not find functions.texi
> make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/octave-zeromq_1.5.6-1_unstable.log

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

Bug#1061009: winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2

[Lucas Nussbaum]

Source: winff
Version: 1.6.2+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> lazbuild --widgetset=qt5 -B winff/winff.lpr
> CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> 
> /<>/tmphome/.lazarus/environmentoptions.xml
> Note: (lazarus) Invalid Package Link: file 
> "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist.
> 
>   $55A851D53B7A
>   $55A851D4EB65
>   $55A851CAAF2E
>   $55A8522FC713
>   $55A851E5EC83
>   $55A851E491DE
>   $55A851E490D8
>   $55A851CAF13D
>   $55A851CACD64
>   $55A851CAB454
>   $55A851CB0C93
>   $55A851CB3979
>   $55A851CD575C
> Error: (lazbuild) Package file not found
> The package "IdeConfig" is installed but no valid package file (.lpk) was 
> found.
> A broken dummy package was created.
> lazbuild is non interactive, aborting now.
> make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/winff_1.6.2+dfsg-2_unstable.log

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

Bug#1061007: xeus-python: FTBFS: ./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5bd): undefined reference to `xeus::make_xserver_shell_main(xeus::xcontext&, xeus::xconfiguration const&, nl

[Lucas Nussbaum]

Source: xeus-python
Version: 0.15.10+~0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/xpython.dir/src/main.cpp.o: in function `main':
> ./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5bd): undefined 
> reference to `xeus::make_xserver_shell_main(xeus::xcontext&, 
> xeus::xconfiguration const&, 
> nlohmann::json_abi_v3_11_3::detail::error_handler_t)'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5d7): 
> undefined reference to `xeus::xkernel::xkernel(xeus::xconfiguration const&, 
> std::__cxx11::basic_string, std::allocator 
> > const&, std::unique_ptr 
> >, std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete > (*)(xeus::xcontext&, 
> xeus::xconfiguration const&, 
> nlohmann::json_abi_v3_11_3::detail::error_handler_t), 
> std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete > (*)(xeus::xcontext&, 
> xeus::xconfiguration const&, std::__cxx11::basic_string std::char_traits, std::allocator > const&, 
> std::__cxx11::basic_string, std::allocator 
> > const&, nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator 
> >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void> const&), 
> nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator 
> >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, 
> nlohmann::json_abi_v3_11_3::detail::error_handler_t)'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/./src/main.cpp:166:(.text.startup+0x89b): 
> undefined reference to `xeus::make_xserver_shell_main(xeus::xcontext&, 
> xeus::xconfiguration const&, 
> nlohmann::json_abi_v3_11_3::detail::error_handler_t)'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/./src/main.cpp:166:(.text.startup+0x8d8): 
> undefined reference to 
> `xeus::xkernel::xkernel(std::__cxx11::basic_string std::char_traits, std::allocator > const&, 
> std::unique_ptr >, 
> std::unique_ptr 
> >, std::unique_ptr > 
> (*)(xeus::xcontext&, xeus::xconfiguration const&, 
> nlohmann::json_abi_v3_11_3::detail::error_handler_t), 
> std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete >, std::unique_ptr std::default_delete > (*)(xeus::xcontext&, 
> xeus::xconfiguration const&, std::__cxx11::basic_string std::char_traits, std::allocator > const&, 
> std::__cxx11::basic_string, std::allocator 
> > const&, nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator 
> >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void> const&), 
> nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator 
> >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, 
> nlohmann::json_abi_v3_11_3::detail::error_handler_t)'
> /usr/bin/ld: libxeus-python.so.0.15.10: undefined reference to 
> `xeus::xtarget::publish_message(std::__cxx11::basic_string std::char_traits, std::allocator > const&, 
> nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator 
> >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, 
> nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator 
> >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, std::vector std::allocator >, std::allocator 
> > > >) const'
> /usr/bin/ld: libxeus-python.so.0.15.10: undefined reference to 
> `xeus::xinterpreter::update_display_data(nlohmann::json_abi_v3_11_3::basic_json  std::vector, std::__cxx11::basic_string, 
> std::allocator >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, 
> nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator 
> >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>, 
> nlohmann::json_abi_v3_11_3::basic_json std::__cxx11::basic_string, std::allocator 
> >, bool, long, unsigned long, double, std::allocator, 
> nlohmann::json_abi_v3_11_3::adl_serializer, std::vector std::allocator >, void>)'
> /usr/bin/ld: libxeus-python.so.0.15.10: undefined reference to 
> `xeus::xdap_tcp_client::forward_event(nlohmann::json_abi_v3_11_3::basic_json  std::vector, std::__cxx11::basic_string, 
> std::allocator >, bool, long, unsigned long, double, 

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

[Lucas Nussbaum]

Source: sphinxcontrib-bibtex
Version: 2.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v7.2.6
> making output directory... done
> loading intersphinx inventory from 
> /usr/share/doc/python3-doc/html/objects.inv...
> loading intersphinx inventory from 
> /usr/share/doc/sphinx-doc/html/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 17 source files that are out of date
> updating environment: [new config] 17 added, 0 changed, 0 removed
> reading sources... [  6%] api
> reading sources... [ 12%] api/bibfile
> reading sources... [ 18%] api/directives
> reading sources... [ 24%] api/domains
> reading sources... [ 29%] api/interface
> reading sources... [ 35%] api/nodes
> reading sources... [ 41%] api/plugin
> reading sources... [ 47%] api/pybtex
> reading sources... [ 53%] api/referencing
> reading sources... [ 59%] api/roles
> reading sources... [ 65%] api/transforms
> reading sources... [ 71%] changes
> reading sources... [ 76%] index
> reading sources... [ 82%] license
> reading sources... [ 88%] quickstart
> reading sources... [ 94%] related
> reading sources... [100%] usage
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> writing output... [  6%] api
> writing output... [ 12%] api/bibfile
> writing output... [ 18%] api/directives
> writing output... [ 24%] api/domains
> writing output... [ 29%] api/interface
> writing output... [ 35%] api/nodes
> writing output... [ 41%] api/plugin
> writing output... [ 47%] api/pybtex
> writing output... [ 53%] api/referencing
> writing output... [ 59%] api/roles
> writing output... [ 65%] api/transforms
> writing output... [ 71%] changes
> writing output... [ 76%] index
> writing output... [ 82%] license
> writing output... [ 88%] quickstart
> writing output... [ 94%] related
> writing output... [100%] usage
> 
> generating indices... genindex py-modindex done
> highlighting module code... [  4%] pybtex.style.template
> highlighting module code... [  9%] sphinxcontrib.bibtex
> highlighting module code... [ 13%] sphinxcontrib.bibtex.bibfile
> highlighting module code... [ 17%] sphinxcontrib.bibtex.directives
> highlighting module code... [ 22%] sphinxcontrib.bibtex.domain
> highlighting module code... [ 26%] sphinxcontrib.bibtex.foot_directives
> highlighting module code... [ 30%] sphinxcontrib.bibtex.foot_domain
> highlighting module code... [ 35%] sphinxcontrib.bibtex.foot_roles
> highlighting module code... [ 39%] sphinxcontrib.bibtex.nodes
> highlighting module code... [ 43%] sphinxcontrib.bibtex.plugin
> highlighting module code... [ 48%] sphinxcontrib.bibtex.richtext
> highlighting module code... [ 52%] sphinxcontrib.bibtex.roles
> highlighting module code... [ 57%] sphinxcontrib.bibtex.style.names.last
> highlighting module code... [ 61%] sphinxcontrib.bibtex.style.referencing
> highlighting module code... [ 65%] 
> sphinxcontrib.bibtex.style.referencing.author_year
> highlighting module code... [ 70%] 
> sphinxcontrib.bibtex.style.referencing.basic_author_year
> highlighting module code... [ 74%] 
> sphinxcontrib.bibtex.style.referencing.basic_label
> highlighting module code... [ 78%] 
> sphinxcontrib.bibtex.style.referencing.extra_author
> highlighting module code... [ 83%] 
> sphinxcontrib.bibtex.style.referencing.extra_label
> highlighting module code... [ 87%] 
> sphinxcontrib.bibtex.style.referencing.extra_year
> highlighting module code... [ 91%] 
> sphinxcontrib.bibtex.style.referencing.label
> highlighting module code... [ 96%] sphinxcontrib.bibtex.style.template
> highlighting module code... [100%] sphinxcontrib.bibtex.transforms
> 
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded.
> 
> The HTML pages are in _build/html.
> 
> Build finished. The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/doc'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_sphinxcontrib.bibtex/build; 
> python3.12 -m pytest "-k not test_citation_rinoh"
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0

Bug#1061004: guestfs-tools: FTBFS: make[6]: *** [Makefile:1723: test-suite.log] Error 1

[Lucas Nussbaum]

Source: guestfs-tools
Version: 1.52.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[6]: Entering directory '/<>/builder'
> PASS: test-docs.sh
> FAIL: test-virt-builder-cacheall.sh
> FAIL: test-virt-builder-list.sh
> PASS: test-virt-index-validate.sh
> rm -f test-console-centos-7.2.sh test-console-centos-7.2.sh-t
> f=`echo "test-console-centos-7.2.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-centos-7.2.sh exec $srcdir/test-console.sh' "$f" > 
> test-console-centos-7.2.sh-t
> chmod 0755 test-console-centos-7.2.sh-t
> mv test-console-centos-7.2.sh-t test-console-centos-7.2.sh
> SKIP: test-console-centos-7.2.sh
> rm -f test-console-rhel-6.8.sh test-console-rhel-6.8.sh-t
> f=`echo "test-console-rhel-6.8.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-rhel-6.8.sh exec $srcdir/test-console.sh' "$f" > 
> test-console-rhel-6.8.sh-t
> chmod 0755 test-console-rhel-6.8.sh-t
> mv test-console-rhel-6.8.sh-t test-console-rhel-6.8.sh
> SKIP: test-console-rhel-6.8.sh
> rm -f test-console-rhel-7.2.sh test-console-rhel-7.2.sh-t
> f=`echo "test-console-rhel-7.2.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-rhel-7.2.sh exec $srcdir/test-console.sh' "$f" > 
> test-console-rhel-7.2.sh-t
> chmod 0755 test-console-rhel-7.2.sh-t
> mv test-console-rhel-7.2.sh-t test-console-rhel-7.2.sh
> SKIP: test-console-rhel-7.2.sh
> rm -f test-console-debian-7.sh test-console-debian-7.sh-t
> f=`echo "test-console-debian-7.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-debian-7.sh exec $srcdir/test-console.sh' "$f" > 
> test-console-debian-7.sh-t
> chmod 0755 test-console-debian-7.sh-t
> mv test-console-debian-7.sh-t test-console-debian-7.sh
> SKIP: test-console-debian-7.sh
> rm -f test-console-debian-8.sh test-console-debian-8.sh-t
> f=`echo "test-console-debian-8.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-debian-8.sh exec $srcdir/test-console.sh' "$f" > 
> test-console-debian-8.sh-t
> chmod 0755 test-console-debian-8.sh-t
> mv test-console-debian-8.sh-t test-console-debian-8.sh
> SKIP: test-console-debian-8.sh
> rm -f test-console-fedora-24.sh test-console-fedora-24.sh-t
> f=`echo "test-console-fedora-24.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-fedora-24.sh exec $srcdir/test-console.sh' "$f" > 
> test-console-fedora-24.sh-t
> chmod 0755 test-console-fedora-24.sh-t
> mv test-console-fedora-24.sh-t test-console-fedora-24.sh
> SKIP: test-console-fedora-24.sh
> rm -f test-console-ubuntu-12.04.sh test-console-ubuntu-12.04.sh-t
> f=`echo "test-console-ubuntu-12.04.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-ubuntu-12.04.sh exec $srcdir/test-console.sh' "$f" 
> > test-console-ubuntu-12.04.sh-t
> chmod 0755 test-console-ubuntu-12.04.sh-t
> mv test-console-ubuntu-12.04.sh-t test-console-ubuntu-12.04.sh
> SKIP: test-console-ubuntu-12.04.sh
> rm -f test-console-ubuntu-14.04.sh test-console-ubuntu-14.04.sh-t
> f=`echo "test-console-ubuntu-14.04.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-ubuntu-14.04.sh exec $srcdir/test-console.sh' "$f" 
> > test-console-ubuntu-14.04.sh-t
> chmod 0755 test-console-ubuntu-14.04.sh-t
> mv test-console-ubuntu-14.04.sh-t test-console-ubuntu-14.04.sh
> SKIP: test-console-ubuntu-14.04.sh
> rm -f test-console-ubuntu-16.04.sh test-console-ubuntu-16.04.sh-t
> f=`echo "test-console-ubuntu-16.04.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-ubuntu-16.04.sh exec $srcdir/test-console.sh' "$f" 
> > test-console-ubuntu-16.04.sh-t
> chmod 0755 test-console-ubuntu-16.04.sh-t
> mv test-console-ubuntu-16.04.sh-t test-console-ubuntu-16.04.sh
> SKIP: test-console-ubuntu-16.04.sh
> rm -f test-console-ubuntu-18.04.sh test-console-ubuntu-18.04.sh-t
> f=`echo "test-console-ubuntu-18.04.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-ubuntu-18.04.sh exec $srcdir/test-console.sh' "$f" 
> > test-console-ubuntu-18.04.sh-t
> chmod 0755 test-console-ubuntu-18.04.sh-t
> mv test-console-ubuntu-18.04.sh-t test-console-ubuntu-18.04.sh
> SKIP: test-console-ubuntu-18.04.sh
> rm -f test-console-ubuntu-20.04.sh test-console-ubuntu-20.04.sh-t
> f=`echo "test-console-ubuntu-20.04.sh" | /usr/bin/sed 
> 's/test-console-\(.*\).sh/\1/'`; \
> echo 'script=test-console-ubuntu-20.04.sh exec $srcdir/test-console.sh' "$f" 
> > test-console-ubuntu-20.04.sh-t
> chmod 0755 test-console-ubuntu-20.04.sh-t
> mv test-console-ubuntu-20.04.sh-t test-console-ubuntu-20.04.sh
> SKIP: test-console-ubuntu-20.04.sh
> SKIP: test-virt-builder-planner.sh
> SKIP: test-virt-builder-repository.sh
> 

Bug#1061001: scikit-fmm: FTBFS: avx512pfintrin.h:180:3: error: ‘base’ may be used uninitialized [-Werror=maybe-uninitialized]

[Lucas Nussbaum]

Source: scikit-fmm
Version: 2022.08.15-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> cython3 --cplus -3 /<>/skfmm/pheap.pyx
> dh_auto_configure
> I: pybuild base:305: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: 
> UserWarning: Unknown distribution option: 'configuration'
>   warnings.warn(msg)
> /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
> Normalizing '2022.08.15' to '2022.8.15'
>   self.metadata.version = self._normalize_version(
> running config
> I: pybuild base:305: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: 
> UserWarning: Unknown distribution option: 'configuration'
>   warnings.warn(msg)
> /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
> Normalizing '2022.08.15' to '2022.8.15'
>   self.metadata.version = self._normalize_version(
> running config
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> /<>/setup.py:116: DeprecationWarning: 
> 
>   `numpy.distutils` is deprecated since NumPy 1.23.0, as a result
>   of the deprecation of `distutils` itself. It will be removed for
>   Python >= 3.12. For older Python versions it will remain present.
>   It is recommended to use `setuptools < 60.0` for those Python versions.
>   For more details, see:
> https://numpy.org/devdocs/reference/distutils_status_migration.html 
> 
> 
>   from numpy.distutils.core import setup
> /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
> Normalizing '2022.08.15' to '2022.8.15'
>   self.metadata.version = self._normalize_version(
> running build
> running config_cc
> INFO: unifing config_cc, config, build_clib, build_ext, build commands 
> --compiler options
> running config_fc
> INFO: unifing config_fc, config, build_clib, build_ext, build commands 
> --fcompiler options
> running build_src
> INFO: build_src
> INFO: building extension "skfmm.cfmm" sources
> INFO: building extension "skfmm.pheap" sources
> INFO: build_src: building npy-pkg config files
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running build_py
> creating /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm
> copying skfmm/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm
> copying skfmm/setup.py -> 
> /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm
> copying skfmm/heap.py -> 
> /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm
> copying skfmm/pfmm.py -> 
> /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm
> running build_ext
> INFO: customize UnixCCompiler
> INFO: customize UnixCCompiler using build_ext
> INFO: CCompilerOpt.cc_test_flags[1077] : testing flags (-march=native)
> INFO: C compiler: x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare 
> -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 
> -I/usr/include/python3.11 -I/usr/include/python3.11 -Wsign-compare -g 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> 
> creating /tmp/tmp4j7s8560/usr
> creating /tmp/tmp4j7s8560/usr/lib
> creating /tmp/tmp4j7s8560/usr/lib/python3
> creating /tmp/tmp4j7s8560/usr/lib/python3/dist-packages
> creating /tmp/tmp4j7s8560/usr/lib/python3/dist-packages/numpy
> creating /tmp/tmp4j7s8560/usr/lib/python3/dist-packages/numpy/distutils
> creating /tmp/tmp4j7s8560/usr/lib/python3/dist-packages/numpy/distutils/checks
> INFO: compile options: '-I/usr/include/python3.12 -c'
> extra options: '-march=native'
> INFO: CCompilerOpt.cc_test_flags[1077] : testing flags (-O3)
> INFO: C compiler: x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare 
> -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection 
> -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 
> -I/usr/include/python3.11 -I/usr/include/python3.11 -Wsign-compare -g 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -DNDEBUG -g -fwrapv -O2 

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

[Lucas Nussbaum]

Source: python-flask-httpauth
Version: 4.5.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> copying src/flask_httpauth.py -> 
> /<>/.pybuild/cpython3_3.12_flask-httpauth/build
> running egg_info
> creating src/Flask_HTTPAuth.egg-info
> writing src/Flask_HTTPAuth.egg-info/PKG-INFO
> writing dependency_links to src/Flask_HTTPAuth.egg-info/dependency_links.txt
> writing requirements to src/Flask_HTTPAuth.egg-info/requires.txt
> writing top-level names to src/Flask_HTTPAuth.egg-info/top_level.txt
> writing manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> reading manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying src/flask_httpauth.py -> 
> /<>/.pybuild/cpython3_3.11_flask-httpauth/build
> running egg_info
> writing src/Flask_HTTPAuth.egg-info/PKG-INFO
> writing dependency_links to src/Flask_HTTPAuth.egg-info/dependency_links.txt
> writing requirements to src/Flask_HTTPAuth.egg-info/requires.txt
> writing top-level names to src/Flask_HTTPAuth.egg-info/top_level.txt
> reading manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'src/Flask_HTTPAuth.egg-info/SOURCES.txt'
> PYTHONPATH=. python3 -m sphinx -N -bhtml docs/ build/html # HTML generator
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> writing output... [100%] index
> 
> generating indices... genindex py-modindex done
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded.
> 
> The HTML pages are in build/html.
> PYTHONPATH=. python3 -m sphinx -N -bman docs/ build/man # Manpage generator
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [man]: all manpages
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> writing... flask-httpauth.3 { } done
> build succeeded.
> 
> The manual pages are in build/man.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_flask-httpauth/build; python3.12 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> collected 108 items
> 
> tests/test_basic_custom_realm.py ... [  
> 2%]
> tests/test_basic_get_password.py .   [  
> 7%]
> tests/test_basic_hashed_password.py ...  [ 
> 10%]
> tests/test_basic_verify_password.py  [ 
> 17%]
> tests/test_basic_verify_password_async.py    [ 
> 25%]
> tests/test_digest_custom_realm.py .. [ 
> 26%]
> tests/test_digest_get_password.py ...[ 
> 33%]
> tests/test_digest_ha1_password.py .  [ 
> 34%]
> tests/test_error_responses.py .  [ 
> 35%]
> tests/test_multi.py FF.. [ 
> 46%]
> tests/test_multi_async.py FF..   [ 
> 57%]
> tests/test_roles.py ..   [ 
> 66%]
> tests/test_roles_async.py .. [ 
> 75%]
> tests/test_token.py ..FF.[ 
> 87%]
> tests/test_token_async.py ..FF.  
> [100%]
> 
> === FAILURES 

Bug#1061000: dqlite: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: dqlite
Version: 1.16.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> PASS: unit-test
> FAIL: integration-test
> 
>libdqlite 1.16.0: ./test-suite.log
> 
> 
> # TOTAL: 2
> # PASS:  1
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: integration-test
> ==
> 
> Running test suite with seed 0x48146ffc...
> client/exec 
>   disk_mode=0   [ OK] [ 
> 0.00848620 / 0.00474892 CPU ]
>   disk_mode=1   [ OK] [ 
> 0.00903412 / 0.00310910 CPU ]
> client/execWithOneParam 
>   disk_mode=0   [ OK] [ 
> 0.01107855 / 0.00322604 CPU ]
>   disk_mode=1   [ OK] [ 
> 0.01084037 / 0.00271260 CPU ]
> client/execSql  
>   disk_mode=0   [ OK] [ 
> 0.00588297 / 0.00149010 CPU ]
>   disk_mode=1   [ OK] [ 
> 0.00743165 / 0.00155657 CPU ]
> client/query
>   disk_mode=0   [ OK] [ 
> 0.04957668 / 0.02712912 CPU ]
>   disk_mode=1   [ OK] [ 
> 0.02748792 / 0.01775024 CPU ]
> client/querySql 
>   disk_mode=0   [ OK] [ 
> 0.03543575 / 0.02319791 CPU ]
>   disk_mode=1   [ OK] [ 
> 0.03526996 / 0.01552904 CPU ]
> cluster/restart 
>   num_records=0, disk_mode=0[ OK] [ 
> 0.09370341 / 0.02169809 CPU ]
>   num_records=0, disk_mode=1[ OK] [ 
> 0.12578984 / 0.02156978 CPU ]
>   num_records=1, disk_mode=0[ OK] [ 
> 0.08911703 / 0.02158624 CPU ]
>   num_records=1, disk_mode=1[ OK] [ 
> 0.10179450 / 0.02262160 CPU ]
>   num_records=256, disk_mode=0  [ OK] [ 
> 1.33302500 / 0.36639435 CPU ]
>   num_records=256, disk_mode=1  [ OK] [ 
> 1.09571285 / 0.30773684 CPU ]
>   num_records=993, disk_mode=0  [ OK] [ 
> 4.43455608 / 1.49089326 CPU ]
>   num_records=993, disk_mode=1  [ OK] [ 
> 4.07793608 / 1.49977670 CPU ]
>   num_records=2200, disk_mode=0 [ OK] [ 
> 9.31523289 / 2.74274570 CPU ]
>   num_records=2200, disk_mode=1 [ OK] [ 
> 8.22212519 / 2.03489432 CPU ]
> cluster/dataOnNewNode   
>   num_records=0, disk_mode=0[ OK] [ 
> 1.02777129 / 0.01749712 CPU ]
>   num_records=0, disk_mode=1[ OK] [ 
> 1.02522202 / 0.01251844 CPU ]
>   num_records=1, disk_mode=0[ OK] [ 
> 1.04220156 / 0.01379738 CPU ]
>   num_records=1, disk_mode=1[ OK] [ 
> 1.02847857 / 0.01512479 CPU ]
>   num_records=256, disk_mode=0  [ OK] [ 
> 1.93572853 / 0.23575930 CPU ]
>   num_records=256, disk_mode=1  [ OK] [ 
> 2.27937617 / 0.42763899 CPU ]
>   num_records=993, disk_mode=0  [ ERROR ]
> Error: test/integration/test_cluster.c:165: assertion failed: rv_ == 0 (1 == 
> 0)
> Error: child killed by signal 6 (Aborted)
>   num_records=993, disk_mode=1  [ OK] [ 
> 5.01102442 / 1.52215910 CPU ]
>   num_records=2200, disk_mode=0 [ OK] [ 
> 9.22951190 / 2.42304560 CPU ]
>   num_records=2200, disk_mode=1 [ OK] [ 
> 9.26020030 / 2.42893808 CPU ]
> cluster/hugeRow [ OK] [ 
> 0.82882703 / 0.50905253 CPU ]
> cluster/modifyingQuery  
>   num_records=0, disk_mode=0[ OK] [ 
> 1.02560865 / 0.01266010 CPU ]
>   num_records=0, disk_mode=1[ OK] [ 
> 1.02765664 / 0.01314657 CPU ]
>   num_records=1, disk_mode=0[ OK] [ 
> 1.02474720 / 0.01152366 CPU ]
>   num_records=1, disk_mode=1

Bug#1060996: h5z-zfp: FTBFS: H5Dcreate failed at line 489, errno=2 (No such file or directory)

[Lucas Nussbaum]

Source: h5z-zfp
Version: 1.1.0+git20221021-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/src'
> make[3]: Nothing to be done for 'plugin'.
> make[3]: Leaving directory '/<>/src'
> x86_64-linux-gnu-gcc -c test_write.c -o test_write_plugin.o 
> -DH5Z_ZFP_USE_PLUGIN -DZFP_LIB_VERSION=0x1010 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I../src -I/usr/include 
> -I/usr/include/hdf5/serial
> x86_64-linux-gnu-gcc test_write_plugin.o -o test_write_plugin -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -Wl,-rpath,/usr/lib/x86_64-linux-gnu/hdf5/serial -Wl,-rpath,/usr/lib 
> -L/usr/lib/x86_64-linux-gnu/hdf5/serial -L/usr/lib -lhdf5 -lzfp -lm 
> -Wl,-z,relro
>  
> ./test_write_plugin zfpmode=1 rate=32 ...HDF5-DIAG: Error 
> detected in HDF5 (1.10.10) thread 1:
>   #000: ../../../src/H5D.c line 140 in H5Dcreate2(): unable to create dataset
> major: Dataset
> minor: Unable to initialize object
>   #001: ../../../src/H5Dint.c line 328 in H5D__create_named(): unable to 
> create and link to dataset
> major: Dataset
> minor: Unable to initialize object
>   #002: ../../../src/H5L.c line 1542 in H5L_link_object(): unable to create 
> new link to object
> major: Links
> minor: Unable to initialize object
>   #003: ../../../src/H5L.c line 1785 in H5L__create_real(): can't insert link
> major: Links
> minor: Unable to insert object
>   #004: ../../../src/H5Gtraverse.c line 830 in H5G_traverse(): internal path 
> traversal failed
> major: Symbol table
> minor: Object not found
>   #005: ../../../src/H5Gtraverse.c line 607 in H5G__traverse_real(): 
> traversal operator failed
> major: Symbol table
> minor: Callback failed
>   #006: ../../../src/H5L.c line 1590 in H5L__link_cb(): unable to create 
> object
> major: Links
> minor: Unable to initialize object
>   #007: ../../../src/H5Oint.c line 2459 in H5O_obj_create(): unable to open 
> object
> major: Object header
> minor: Can't open object
>   #008: ../../../src/H5Doh.c line 287 in H5O__dset_create(): unable to create 
> dataset
> major: Dataset
> minor: Unable to initialize object
>   #009: ../../../src/H5Dint.c line 1196 in H5D__create(): I/O filters can't 
> operate on this dataset
> major: Invalid arguments to routine
> minor: Unable to initialize object
>   #010: ../../../src/H5Z.c line 891 in H5Z_can_apply(): unable to apply filter
> major: Data filters
> minor: Error from filter 'can apply' callback
>   #011: ../../../src/H5Z.c line 852 in H5Z__prepare_prelude_callback_dcpl(): 
> unable to apply filter
> major: Data filters
> minor: Error from filter 'can apply' callback
>   #012: ../../../src/H5Z.c line 753 in H5Z__prelude_callback(): error during 
> user callback
> major: Data filters
> minor: Error from filter 'can apply' callback
>   #013: H5Zzfp.c line 158 in H5Z_zfp_can_apply(): ZFP lib not compiled with 
> -DBIT_STREAM_WORD_TYPE=uint8
> major: Data filters
> minor: Unable to initialize object
> H5Dcreate failed at line 489, errno=2 (No such file or directory)
>  [FAILED]
> ./test_write_plugin zfpmode=1 rate=16 ...HDF5-DIAG: Error 
> detected in HDF5 (1.10.10) thread 1:
>   #000: ../../../src/H5D.c line 140 in H5Dcreate2(): unable to create dataset
> major: Dataset
> minor: Unable to initialize object
>   #001: ../../../src/H5Dint.c line 328 in H5D__create_named(): unable to 
> create and link to dataset
> major: Dataset
> minor: Unable to initialize object
>   #002: ../../../src/H5L.c line 1542 in H5L_link_object(): unable to create 
> new link to object
> major: Links
> minor: Unable to initialize object
>   #003: ../../../src/H5L.c line 1785 in H5L__create_real(): can't insert link
> major: Links
> minor: Unable to insert object
>   #004: ../../../src/H5Gtraverse.c line 830 in H5G_traverse(): internal path 
> traversal failed
> major: Symbol table
> minor: Object not found
>   #005: ../../../src/H5Gtraverse.c line 607 in H5G__traverse_real(): 
> traversal operator failed
> major: Symbol table
> minor: Callback failed
>   #006: ../../../src/H5L.c line 1590 in H5L__link_cb(): unable to create 
> object
> major: Links
> minor: Unable to initialize object
>   #007: ../../../src/H5Oint.c line 2459 in H5O_obj_create(): unable to open 
> object
> major: Object header
> minor: Can't open object
>   #008: ../../../src/H5Doh.c line 287 in H5O__dset_create(): 

Bug#1060999: octave-sockets: FTBFS: make: *** [debian/rules:5: binary] Error 25

[Lucas Nussbaum]

Source: octave-sockets
Version: 1.4.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>/src'
> /usr/bin/mkoctfile --verbose socket.cc 
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave  
> -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protectionsocket.cc -o /tmp/oct-DW4tFF.o
> Extracting tests from socket.cc ...
> g++ -I/usr/include/octave-8.4.0/octave/.. -I/usr/include/octave-8.4.0/octave  
> -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection  -o socket.oct  /tmp/oct-DW4tFF.o   
> -shared -Wl,-Bsymbolic -Wl,-z,relro  -L/usr/lib/x86_64-linux-gnu -shared 
> -Wl,-Bsymbolic  -flto=auto -ffat-lto-objects -Wl,-z,relro 
> make[1]: Leaving directory '/<>/src'
> copyfile /<>/./src/socket.oct 
> /<>/./src/socket.cc-tst 
> /<>/./inst/x86_64-pc-linux-gnu-api-v58
> For information about changes from previous versions of the sockets package, 
> run 'news sockets'.
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Run the unit tests...
> Checking m files ...
> Checking C++ files ...
> [src/socket.cc]
> > /<>/src/socket.cc
> * test
>  ## Server socket
>  server = socket (AF_INET, SOCK_STREAM, 0);
>  assert (server >= 0);
> 
>  rc = bind (server, 9001);
>  assert (rc, 0);
> 
>  rc = listen (server, 1);
>  assert (rc, 0);
> 
>  ## Client socket
>  client = socket (AF_INET, SOCK_STREAM, 0);
>  assert (client >= 0);
> 
>  ## Create the connection and accept the connection
>  server_info = struct ("addr", "127.0.0.1", "port", 9001);
>  rc = connect (client, server_info);
>  assert (rc, 0);
> 
>  server_data = accept (server);
>  assert (server_data >= 0);
> 
>  ## Send and receive data
> 
>  ## Send as string from client
>  msg = "Hello socket-land!";
>  rc = send (client, msg);
>  assert (rc,length (msg));
> 
>  ## Receive at server
>  [msg_s, len_s] = recv (server_data, 100);
>  assert (msg_s != -1);
>  assert (len_s, length (msg));
> 
>  ## Send back out from server
>  rc = send (server_data, msg_s);
>  assert (rc, length (msg_s));
> 
>  ## Receive at client
>  [msg_c, len_c] = recv (client, 100);
>  assert (msg_c != -1);
>  assert (len_c, length (msg));
> 
>  ## Compare original string with recv string
>  assert (msg, num2str (msg_c, "%c"));
> 
>  assert (shutdown (client, SHUT_WR), 0);
>  assert (shutdown (client, SHUT_RD), 0);
>  assert (shutdown (client, SHUT_RDWR), 0);
> 
>  assert (disconnect (client), 0);
>  assert (disconnect (server_data), 0);
>  assert (disconnect (server), 0);
> * test
>  ## UDP
>  sock = socket (AF_INET, SOCK_DGRAM, 0);
>  assert (sock >= 0);
> 
>  rc = bind (sock, 9001);
>  assert (rc, 0);
> 
>  msg = "Hello socket-land!";
>  addrinfo = struct ("addr", "127.0.0.1", "port", 9001);
>  rc = sendto (sock, msg, 0, addrinfo);
>  assert (rc,length (msg));
> 
>  [msg_c, len_c, addr_c] = recvfrom (sock, 100);
>  assert (msg_c != -1);
>  assert (len_c, length (msg));
>  assert (addr_c.port, 9001);
> 
>  assert (msg, num2str (msg_c, "%c"));
> 
>  assert (disconnect (sock), 0);
> * test
>  assert (SOL_SOCKET != 0)
>  assert (MSG_WAITALL != 0)
>  assert (MSG_PEEK != 0)
>  assert (SO_REUSEADDR != 0)
>  assert (SO_KEEPALIVE != 0)
>  assert (SO_TYPE != 0)
>  assert (SHUT_RD, 0)
>  assert (SHUT_WR, 1)
>  assert (SHUT_RDWR, 2)
> * test
>  ## select
>  sock = socket (AF_INET, SOCK_DGRAM, 0);
>  assert (sock >= 0);
> 
>  rc = bind (sock, 9001);
>  assert (rc, 0);
> 
>  [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [sock], [sock], 1);
>  assert(ret, 1);
>  assert(rdfs, []);
>  # initial open
>  assert(wdfs, [sock]);
>  assert(edfs, []);
> 
>  msg = "Hello socket-land!";
>  addrinfo = struct ("addr", "127.0.0.1", "port", 9001);
>  rc = sendto (sock, msg, 0, addrinfo);
>  assert (rc,length (msg));
>  pause(1);
> 
>  [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [], [], .2);
>  assert(ret, 1);
>  assert(rdfs, [sock]);
>  assert(wdfs, []);
>  assert(edfs, []);
> 
>  [msg_c, len_c, addr_c] = recvfrom (sock, 100);
>  assert (msg_c != -1);
>  assert (len_c, length (msg));
>  assert (addr_c.port, 9001);
> 
>  [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [], [], .1);
>  assert(ret, 0);
>  assert(rdfs, []);
>  assert(wdfs, []);
>  assert(edfs, []);
> 
>  assert (disconnect (sock), 0);
> 
> * xtest
>  sock = socket (AF_INET, SOCK_DGRAM, 0);
>  assert (sock >= 0);
> 
>  start = tic;
>  [ret, rdfs, wdfs, edfs] = select(sock+1, [sock], [], [], 1);
>  timeout = toc(start);
>  assert(ret, 0);
>  assert(rdfs, []);
>  assert(wdfs, []);
>  assert(edfs, []);
>  assert(timeout, 1, 0.01);
> 

Bug#1060994: libshumate: FTBFS: make: *** [debian/rules:9: binary] Error 25

[Lucas Nussbaum]

Source: libshumate
Version: 1.1.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 -- -Dauto_features=enabled
>   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 -Dauto_features=enabled
> The Meson build system
> Version: 1.3.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: libshumate
> Project version: 1.1.2
> C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-9) 13.2.0")
> C linker for the host machine: cc ld.bfd 2.41.50.20231227
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Library m found: YES
> Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
> Run-time dependency glib-2.0 found: YES 2.78.3
> Run-time dependency gobject-2.0 found: YES 2.78.3
> Run-time dependency gio-2.0 found: YES 2.78.3
> Run-time dependency cairo found: YES 1.18.0
> Run-time dependency sqlite3 found: YES 3.44.2
> Run-time dependency gtk4 found: YES 4.12.4
> Run-time dependency libsoup-3.0 found: YES 3.4.4
> Run-time dependency gobject-introspection-1.0 found: YES 1.78.1
> Run-time dependency vapigen found: YES 0.56.14
> Run-time dependency sysprof-capture-4 found: YES 45.1
> Build-time dependency gi-docgen found: YES 2023.3
> Program gi-docgen found: YES (/usr/bin/gi-docgen)
> Dependency gio-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-compile-resources found: YES 
> (/usr/bin/glib-compile-resources)
> Configuring shumate-version.h using configuration
> Dependency glib-2.0 found: YES 2.78.3 (cached)
> 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)
> ../shumate/meson.build:213: WARNING: Project targets '>= 0.53.0' but uses 
> feature introduced in '0.55.0': fatal_warnings arg in gnome.generate_gir.
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Program /usr/bin/x86_64-linux-gnu-g-ir-scanner found: YES 
> (/usr/bin/x86_64-linux-gnu-g-ir-scanner)
> Dependency gobject-introspection-1.0 found: YES 1.78.1 (cached)
> Program /usr/bin/x86_64-linux-gnu-g-ir-compiler found: YES 
> (/usr/bin/x86_64-linux-gnu-g-ir-compiler)
> Program vapigen found: YES (/usr/bin/vapigen)
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Configuring libshumate.toml using configuration
> Dependency gio-2.0 found: YES 2.78.3 (cached)
> Program /usr/bin/glib-compile-resources found: YES 
> (/usr/bin/glib-compile-resources)
> Program valgrind found: NO
> Message: 
> --
> libshumate 1.1.2 (1.0)
> 
>  Demos: false
>  Documentation: true
>  Introspection: true
>   Vala API: true
> 
> Directories:
>prefix: /usr
>includedir: /usr/include
>libdir: /usr/lib/x86_64-linux-gnu
>   datadir: /usr/share
> --
> Build targets in project: 69
> WARNING: Project specifies a minimum meson_version '>= 0.53.0' but uses 
> features which were added in newer versions:
>  * 0.55.0: {'fatal_warnings arg in gnome.generate_gir'}
> 
> libshumate 1.1.2
> 
>   User defined options
> auto_features : enabled
> buildtype : plain
> libdir: lib/x86_64-linux-gnu
> localstatedir : /var
> prefix: /usr
> sysconfdir: /etc
> wrap_mode : nodownload
> python.bytecompile: -1
> 
> Found ninja-1.11.1 at /usr/bin/ninja
> make[1]: Leaving directory '/<>'
>dh_auto_build
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/124] /usr/bin/glib-compile-resources ../data/libshumate.gresource.xml 
> --sourcedir ../data --c-name shumate --internal --generate --target 
> data/shumate-resources.h
> xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint 
> is not in PATH
> [2/124] /usr/bin/glib-compile-resources ../data/libshumate.gresource.xml 
> --sourcedir ../data --c-name shumate --internal --generate --target 
> data/shumate-resources.c --dependency-file data/shumate-resources.c.d
> xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint 
> is not in PATH
> [3/124] /usr/bin/msgfmt -o po/ab/LC_MESSAGES/shumate1.mo ../po/ab.po
> [4/124] /usr/bin/msgfmt -o po/ca/LC_MESSAGES/shumate1.mo 

Bug#1060998: cthreadpool: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: cthreadpool
Version: 0.0+git20201207.b259a6e-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> 1/10
> 2/10
> 3/10
> 4/10
> 5/10
> 6/10
> 7/10
> 8/10
> 9/10
> 10/10
> 
> Testing multiple threads creation and destruction in pool(threads=3 times=20)
> 1/20
> 2/20
> 3/20
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/cthreadpool_0.0+git20201207.b259a6e-1_unstable.log

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

Bug#1060997: khard: FTBFS: make[2]: *** [Makefile:20: html] Error 2

[Lucas Nussbaum]

Source: khard
Version: 0.19.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> Running Sphinx v7.2.6
> making output directory... done
> /usr/lib/python3/dist-packages/autoapi/mappers/python/mapper.py:300: 
> RemovedInSphinx80Warning: The alias 'sphinx.util.status_iterator' is 
> deprecated, use 'sphinx.util.display.status_iterator' instead. Check CHANGES 
> for Sphinx API modifications.
>   for dir_root, path in sphinx.util.status_iterator(
> [AutoAPI] Reading files... [  7%] /<>/khard/__init__.py
> 
> Extension error (autoapi.extension):
> Handler  for event 'builder-inited' 
> threw an exception (exception: 'Module' object has no attribute 'doc')
> make[2]: *** [Makefile:20: html] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/khard_0.19.1-1_unstable.log

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

Bug#1060995: ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2

[Lucas Nussbaum]

Source: ddrescueview
Version: 0.4.5-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> lazbuild source/ddrescueview.lpi --bm="GNU/Linux Release" --no-write-project 
> --ws=qt5
> CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> 
> /<>/tmphome/.lazarus/environmentoptions.xml
> Note: (lazarus) Invalid Package Link: file 
> "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist.
> 
>   $55D5C4FD9B7A
>   $55D5C4FD4B65
>   $55D5C4F30F2E
>   $55D5C5582713
>   $55D5C50E4C83
>   $55D5C50CF1DE
>   $55D5C50CF0D8
>   $55D5C4F3513D
>   $55D5C4F32D64
>   $55D5C4F313EB
>   $55D5C4F36C93
>   $55D5C4F39979
>   $55D5C4F5B75C
> Error: (lazbuild) Package file not found
> The package "IdeConfig" is installed but no valid package file (.lpk) was 
> found.
> A broken dummy package was created.
> lazbuild is non interactive, aborting now.
> make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/ddrescueview_0.4.5-2_unstable.log

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

Bug#1060992: lomiri-system-settings: FTBFS: 12: QWARN : tst_notifications::ClickAppsVibrationsNotify::test_should_update_when_added() file:///<>/plugins/notifications/ClickAppsVibrations

[Lucas Nussbaum]

Source: lomiri-system-settings
Version: 1.0.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j1
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
>   Start  1: tst-plugins
> 
> 1: Test command: /<>/obj-x86_64-linux-gnu/tests/tst-plugins
> 1: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 1: Environment variables: 
> 1:  QT_QPA_PLATFORM=minimal
> 1:  XDG_DATA_DIRS=/<>/tests
> 1: Test timeout computed to be: 1000
> 1: * Start testing of PluginsTest *
> 1: Config: Using QtTest library 5.15.10, Qt 5.15.10 
> (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), 
> debian unknown
> 1: PASS   : PluginsTest::initTestCase()
> 1: PASS   : PluginsTest::testCategory()
> 1: PASS   : PluginsTest::testName()
> 1: PASS   : PluginsTest::testKeywords()
> 1: PASS   : PluginsTest::testSorting()
> 1: PASS   : PluginsTest::testReset()
> 1: PASS   : PluginsTest::testResetInPlugin()
> 1: PASS   : PluginsTest::cleanupTestCase()
> 1: Totals: 8 passed, 0 failed, 0 skipped, 0 blacklisted, 15ms
> 1: * Finished testing of PluginsTest *
>  1/12 Test  #1: tst-plugins ..   Passed0.03 sec
> test 2
>   Start  2: tst-arguments
> 
> 2: Test command: /<>/obj-x86_64-linux-gnu/tests/tst-arguments
> 2: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 2: Test timeout computed to be: 1000
> 2: * Start testing of ArgumentsTest *
> 2: Config: Using QtTest library 5.15.10, Qt 5.15.10 
> (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), 
> debian unknown
> 2: PASS   : ArgumentsTest::initTestCase()
> 2: PASS   : ArgumentsTest::testNull()
> 2: QWARN  : ArgumentsTest::testDefaultPlugin() could not locate map file
> 2: QWARN  : ArgumentsTest::testDefaultPlugin() could not locate map file
> 2: PASS   : ArgumentsTest::testDefaultPlugin()
> 2: QWARN  : ArgumentsTest::testPluginOptions() could not locate map file
> 2: PASS   : ArgumentsTest::testPluginOptions()
> 2: PASS   : ArgumentsTest::testObsoleted()
> 2: PASS   : ArgumentsTest::cleanupTestCase()
> 2: Totals: 6 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms
> 2: * Finished testing of ArgumentsTest *
>  2/12 Test  #2: tst-arguments    Passed0.01 sec
> test 3
>   Start  3: tst-systemimage
> 
> 3: Test command: /<>/obj-x86_64-linux-gnu/tests/tst-systemimage
> 3: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 3: Test timeout computed to be: 1000
> 3: * Start testing of TstSystemImage *
> 3: Config: Using QtTest library 5.15.10, Qt 5.15.10 
> (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), 
> debian unknown
> 3: PASS   : TstSystemImage::initTestCase()
> 3: 1705349587.298 Information
> 3: 1705349587.299 GetSetting "auto_download"
> 3: 1705349587.300 GetSetting "failures_before_warning"
> 3: QWARN  : TstSystemImage::testDetailedVersionDetails() Unable to locate 
> signal on s-i interface. Will not connect to s-i events.
> 3: PASS   : TstSystemImage::testDetailedVersionDetails()
> 3: 1705349587.422 Information
> 3: 1705349587.422 GetSetting "auto_download"
> 3: 1705349587.423 GetSetting "failures_before_warning"
> 3: QWARN  : TstSystemImage::testVersionTag() Unable to locate signal on s-i 
> interface. Will not connect to s-i events.
> 3: PASS   : TstSystemImage::testVersionTag()
> 3: 1705349587.546 Information
> 3: 1705349587.546 GetSetting "auto_download"
> 3: 1705349587.547 GetSetting "failures_before_warning"
> 3: QWARN  : TstSystemImage::testAvailableStatus(available, downloading) 
> Unable to locate signal on s-i interface. Will not connect to s-i events.
> 3: PASS   : TstSystemImage::testAvailableStatus(available, downloading)
> 3: 1705349587.682 Information
> 3: 1705349587.682 GetSetting "auto_download"
> 3: 1705349587.683 GetSetting "failures_before_warning"
> 3: QWARN  : TstSystemImage::testAvailableStatus(available, paused) Unable to 
> locate signal on s-i interface. Will not connect to s-i events.
> 3: PASS   : TstSystemImage::testAvailableStatus(available, paused)
> 3: 1705349587.811 Information
> 3: 1705349587.812 GetSetting "auto_download"
> 3: 1705349587.812 GetSetting "failures_before_warning"
> 3: QWARN  : TstSystemImage::testAvailableStatus(not available) Unable 

Bug#1060993: distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept'

[Lucas Nussbaum]

Source: distro-info
Version: 1.7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> ./test-debian-distro-info
> cd perl && ./test.pl
> testAlias
> py3versions: no X-Python3-Version in control file, using supported versions
> cd python && python3.12 setup.py test
> 1..35
> testAll
> ok 1 - unique: Matching lists
> ok 2 - symmetric_difference: Matching lists
> ok 3 - unique: 1 Unique Item
> ok 4 - unique: 1 Unique Item in the haystack
> ok 5 - symmetric_difference: 1 Unique Item
> ok 6 - Debian all
> ok 7 - Debian devel
> ok 8 - Debian oldstable
> ok 9 - Debian stable
> ok 10 - Debian testing
> ok 11 - Debian valid
> ok 12 - Debian valid
> ok 13 - Debian invalid
> ok 14 - Debian supported
> ok 15 - Debian LTS
> ok 16 - Debian ELTS
> ok 17 - Debian unsupported
> ok 18 - Debian codename, invalid
> ok 19 - Debian codename
> ok 20 - Debian version, invalid
> ok 21 - Debian version
> ok 22 - Ubuntu all
> ok 23 - Ubuntu version
> ok 24 - Ubuntu LTS version
> ok 25 - Ubuntu devel
> ok 26 - Ubuntu LTS
> ok 27 - Ubuntu stable
> ok 28 - Ubuntu valid
> ok 29 - Ubuntu invalid
> ok 30 - Ubuntu is_lts
> ok 31 - Ubuntu !is_lts
> ok 32 - Ubuntu !is_lts
> ok 33 - Ubuntu supported
> ok 34 - Ubuntu ESM
> ok 35 - Ubuntu unsupported
> testDevel
> testOldstable
> testStable
> testSupported
> testLTS
> testELTS
> testUnsupported
> testTesting
> testFullname
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> /usr/lib/python3/dist-packages/setuptools/command/test.py:193: 
> _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`.
> 
> 
> 
> !!
>   ir_d = dist.fetch_build_eggs(dist.install_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/command/test.py:194: 
> _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`.
> 
> 
> 
> !!
>   tr_d = dist.fetch_build_eggs(dist.tests_require or [])
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/command/test.py:195: 
> _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`.
> 
> 
> 
> !!
>   er_d = dist.fetch_build_eggs(
> WARNING: The wheel package is not available.
> running egg_info
> creating distro_info.egg-info
> writing distro_info.egg-info/PKG-INFO
> writing dependency_links to distro_info.egg-info/dependency_links.txt
> writing top-level names to distro_info.egg-info/top_level.txt
> writing manifest file 'distro_info.egg-info/SOURCES.txt'
> reading manifest file 'distro_info.egg-info/SOURCES.txt'
> writing manifest file 'distro_info.egg-info/SOURCES.txt'
> running build_ext
> test_all (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_all)
> Test: List all known Debian distributions. ... ok
> test_codename 
> (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_codename)
> Test: Codename decoding ... ok
> test_codename_result 
> (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_codename_result)
> Test: Check result set to codename. ... ok
> test_devel 
> (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_devel)
> Test: Get latest development Debian distribution. ... ok
> test_elts_supported 
> (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_elts_supported)
> Test: List all ELTS supported Debian distribution. ... ok
> test_fullname 
> (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_fullname)
> Test: Check result set to fullname. ... ok
> test_lts_supported 
> (distro_info_test.test_distro_info.DebianDistroInfoTestCase.test_lts_supported)
> Test: List all LTS supported Debian 

Bug#1060990: wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2

[Lucas Nussbaum]

Source: wacomtablet
Version: 3.2.0-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
> CMake Deprecation Warning at CMakeLists.txt:1 (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.
> 
> 
> -- The C compiler identification is GNU 13.2.0
> -- The CXX compiler identification is GNU 13.2.0
> -- 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
> -- Installing in the same prefix as Qt, adopting their path scheme.
> -- Could not set up the appstream test. appstreamcli is missing.
> -- Looking for __GLIBC__
> -- Looking for __GLIBC__ - found
> -- Performing Test _OFFT_IS_64BIT
> -- Performing Test _OFFT_IS_64BIT - Success
> -- Performing Test HAVE_DATE_TIME
> -- Performing Test HAVE_DATE_TIME - Success
> CMake Warning (dev) at /usr/share/ECM/modules/ECMFindModuleHelpers.cmake:113 
> (message):
>   Your project should require at least CMake 3.16.0 to use FindKF5.cmake
> Call Stack (most recent call first):
>   /usr/share/ECM/find-modules/FindKF5.cmake:30 
> (ecm_find_package_version_check)
>   CMakeLists.txt:25 (find_package)
> This warning is for project developers.  Use -Wno-dev to suppress it.
> 
> -- Found KF5CoreAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake 
> (found version "5.107.0") 
> -- Found Gettext: /usr/bin/msgmerge (found version "0.21") 
> -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake 
> (found version "5.107.0") 
> -- Found KF5GlobalAccel: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5GlobalAccel/KF5GlobalAccelConfig.cmake 
> (found version "5.107.0") 
> -- Found KF5Config: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found 
> version "5.107.0") 
> -- Found KF5XmlGui: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found 
> version "5.107.0") 
> -- Found KF5WidgetsAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5WidgetsAddons/KF5WidgetsAddonsConfig.cmake 
> (found version "5.107.0") 
> -- Found X11: /usr/include   
> -- Looking for XOpenDisplay in 
> /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so
> -- Looking for XOpenDisplay in 
> /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - 
> found
> -- Looking for gethostbyname
> -- Looking for gethostbyname - found
> -- Looking for connect
> -- Looking for connect - found
> -- Looking for remove
> -- Looking for remove - found
> -- Looking for shmat
> -- Looking for shmat - found
> -- Found KF5WindowSystem: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5WindowSystem/KF5WindowSystemConfig.cmake 
> (found version "5.107.0") 
> -- Found KF5Notifications: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Notifications/KF5NotificationsConfig.cmake 
> (found version "5.107.0") 
> -- Found KF5DBusAddons: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5DBusAddons/KF5DBusAddonsConfig.cmake 
> (found version "5.107.0") 
> -- Found KF5Plasma: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5Plasma/KF5PlasmaConfig.cmake (found 
> version "5.107.0") 
> -- Found KF5DocTools: 
> /usr/lib/x86_64-linux-gnu/cmake/KF5DocTools/KF5DocToolsConfig.cmake (found 
> version "5.107.0") 
> -- Found KF5: success (found version "5.107.0") found components: CoreAddons 
> I18n GlobalAccel Config XmlGui WidgetsAddons WindowSystem Notifications 
> DBusAddons Plasma DocTools 
> CMake Warning (dev) at /usr/share/ECM/modules/ECMFindModuleHelpers.cmake:113 
> (message):
>   Your project should require at least CMake 3.16.0 to use FindXCB.cmake
> Call Stack (most recent call first):
>   /usr/share/ECM/find-modules/FindXCB.cmake:67 
> (ecm_find_package_version_check)
>   CMakeLists.txt:26 

Bug#1060991: tuba: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1

[Lucas Nussbaum]

Source: tuba
Version: 0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> cd debian/build && ninja test
> [0/1] Running all tests.
> 1/9 BlurhashOK  0.03s
> 2/9 Celebrate   OK  0.03s
> 3/9 TrackingOK  0.02s
> 4/9 Units   OK  0.01s
> 5/9 WebApHandlerOK  0.01s
> 6/9 DateTimeFAIL0.03s   killed by signal 6 SIGABRT
> >>> MALLOC_PERTURB_=151 
> >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> >>>  ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
> >>> /<>/debian/build/tests/DateTime
> ― ✀  ―
> stdout:
> TAP version 13
> # random seed: R02S83fee4da4199330390e8ca34545512f3
> 1..5
> not ok /test_left - 
> Tuba:ERROR:tests/DateTime.p/DateTime.test.c:758:test_left: assertion failed 
> (_tmp7_ == _tmp9_): ("Aug 8, 2023" == "Aug 8")
> Bail out!
> stderr:
> **
> Tuba:ERROR:tests/DateTime.p/DateTime.test.c:758:test_left: assertion failed 
> (_tmp7_ == _tmp9_): ("Aug 8, 2023" == "Aug 8")
> ――
> 
> 7/9 HtmlOK  0.03s
> 8/9 Validate desktop file   OK  0.01s
> 9/9 Validate appstream file OK  0.04s
> 
> Summary of Failures:
> 
> 6/9 DateTimeFAIL0.03s   killed by signal 6 SIGABRT
> 
> Ok: 8   
> Expected Fail:  0   
> Fail:   1   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:0   
> 
> Full log written to /<>/debian/build/meson-logs/testlog.txt
> FAILED: meson-internal__test 
> /usr/bin/meson test --no-rebuild --print-errorlogs
> ninja: build stopped: subcommand failed.
> make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/tuba_0.6.1-1_unstable.log

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

Bug#1060987: q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: q2cli
Version: 2022.11.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/_version.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/__main__.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/commands.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli
> copying q2cli/util.py -> /<>/.pybuild/cpython3_3.11/build/q2cli
> creating /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_mystery_stew.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_cache_cli.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_dev.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_cli.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_core.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_usage.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> copying q2cli/tests/test_tools.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/tests
> creating /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/completion.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/state.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/usage.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/config.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> copying q2cli/core/cache.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/core
> creating /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> copying q2cli/builtin/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> copying q2cli/builtin/tools.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> copying q2cli/builtin/dev.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> copying q2cli/builtin/info.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/builtin
> creating /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/type.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/parser.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/command.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> copying q2cli/click/option.py -> 
> /<>/.pybuild/cpython3_3.11/build/q2cli/click
> running egg_info
> creating q2cli.egg-info
> writing q2cli.egg-info/PKG-INFO
> writing dependency_links to q2cli.egg-info/dependency_links.txt
> writing entry points to q2cli.egg-info/entry_points.txt
> writing top-level names to q2cli.egg-info/top_level.txt
> writing manifest file 'q2cli.egg-info/SOURCES.txt'
> reading manifest file 'q2cli.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'q2cli.egg-info/SOURCES.txt'
> UPDATING /<>/.pybuild/cpython3_3.11/build/q2cli/_version.py
> set /<>/.pybuild/cpython3_3.11/build/q2cli/_version.py to 
> '2022.11.1'
> running build_scripts
> creating build
> creating build/scripts-3.11
> copying bin/tab-qiime -> build/scripts-3.11
> changing mode of build/scripts-3.11/tab-qiime from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest --ignore=q2cli/tests/test_usage.py
> = test session starts 
> ==
> platform linux -- Python 3.11.7, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> collected 0 items / 6 errors
> 
>  ERRORS 
> 
> _ ERROR collecting .pybuild/cpython3_3.11/build/q2cli/tests/test_cache_cli.py 
> __
> q2cli/tests/test_cache_cli.py:15: in 
> from qiime2 import Artifact
> /usr/lib/python3/dist-packages/qiime2/__init__.py:23: in 
> __citations__ = tuple(Citations.load('citations.bib', package='qiime2'))
> /usr/lib/python3/dist-packages/qiime2/core/cite.py:26: in load
> parser = bp.bparser.BibTexParser()
> E   AttributeError: module 'bibtexparser' has no attribute 

Bug#1060989: astap: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2

[Lucas Nussbaum]

Source: astap
Version: 2022.12.09-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> lazbuild --widgetset=qt5 astap_linux.lpi
> CopySecondaryConfigFile /etc/lazarus/environmentoptions.xml -> 
> /<>/tmphome/.lazarus/environmentoptions.xml
> Note: (lazarus) Invalid Package Link: file 
> "/usr/lib/lazarus/3.0/ide/packages/ideconfig/ideconfig.lpk" does not exist.
> 
>   $55E0224A2B7A
>   $55E02249DB65
>   $55E0223F9F2E
>   $55E022A4B713
>   $55E0225ADC83
>   $55E0225981DE
>   $55E0225980D8
>   $55E0223FE13D
>   $55E0223FBD64
>   $55E0223FA3EB
>   $55E0223FFC93
>   $55E022402979
>   $55E02242475C
> Error: (lazbuild) Package file not found
> The package "IdeConfig" is installed but no valid package file (.lpk) was 
> found.
> A broken dummy package was created.
> lazbuild is non interactive, aborting now.
> make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/astap_2022.12.09-3_unstable.log

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

Bug#1060988: mathcomp-analysis: FTBFS: make[3]: *** [Makefile.coq:838: classical/mathcomp_extra.vo] Error 1

[Lucas Nussbaum]

Source: mathcomp-analysis
Version: 0.6.4-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> COQDEP VFILES
> COQC classical/boolp.v
> COQC classical/mathcomp_extra.v
> COQC theories/forms.v
> COQC theories/altreals/xfinmap.v
> File "./classical/mathcomp_extra.v", line 7, characters 9-28:
> Error: The reference choice.Choice.mixin was not found in the current
> environment.
> 
> make[3]: *** [Makefile.coq:838: classical/mathcomp_extra.vo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/mathcomp-analysis_0.6.4-3_unstable.log

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

Bug#1060985: prewikka: FTBFS: ModuleNotFoundError: No module named 'six'

[Lucas Nussbaum]

Source: prewikka
Version: 5.2.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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
> I: pybuild base:305: python3.12 setup.py config 
> /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)
> WARNING: The wheel package is not available.
> running config
> I: pybuild base:305: python3.11 setup.py config 
> /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)
> WARNING: The wheel package is not available.
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> /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)
> WARNING: The wheel package is not available.
> running build
> running compile_catalog
> compiling catalog prewikka/locale/en/LC_MESSAGES/prewikka.po to 
> prewikka/locale/en/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/ru/LC_MESSAGES/prewikka.po:168: unknown named 
> placeholder 'version'
> error: prewikka/locale/ru/LC_MESSAGES/prewikka.po:2793: placeholders are 
> incompatible
> compiling catalog prewikka/locale/ru/LC_MESSAGES/prewikka.po to 
> prewikka/locale/ru/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/pl/LC_MESSAGES/prewikka.po:2162: placeholders are 
> incompatible
> error: prewikka/locale/pl/LC_MESSAGES/prewikka.po:2854: placeholders are 
> incompatible
> compiling catalog prewikka/locale/pl/LC_MESSAGES/prewikka.po to 
> prewikka/locale/pl/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/de/LC_MESSAGES/prewikka.po:2804: placeholders are 
> incompatible
> compiling catalog prewikka/locale/de/LC_MESSAGES/prewikka.po to 
> prewikka/locale/de/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po:2397: placeholders are 
> incompatible
> error: prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po:2810: placeholders are 
> incompatible
> compiling catalog prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po to 
> prewikka/locale/pt_BR/LC_MESSAGES/prewikka.mo
> compiling catalog prewikka/locale/fr/LC_MESSAGES/prewikka.po to 
> prewikka/locale/fr/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/es/LC_MESSAGES/prewikka.po:2393: placeholders are 
> incompatible
> error: prewikka/locale/es/LC_MESSAGES/prewikka.po:2807: placeholders are 
> incompatible
> compiling catalog prewikka/locale/es/LC_MESSAGES/prewikka.po to 
> prewikka/locale/es/LC_MESSAGES/prewikka.mo
> compiling catalog prewikka/locale/it/LC_MESSAGES/prewikka.po to 
> prewikka/locale/it/LC_MESSAGES/prewikka.mo
> 9 errors encountered.
> running build_custom
> Traceback (most recent call last):
>   File "/usr/bin/lesscpy", line 33, in 
> sys.exit(load_entry_point('lesscpy==0.15.1', 'console_scripts', 
> 'lesscpy')())
>  ^
>   File "/usr/bin/lesscpy", line 25, in importlib_load_entry_point
> return next(matches).load()
>
>   File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
> module = import_module(match.group('module'))
>  
>   File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:], 

Bug#1060983: dwarf2sources: FTBFS: build-dependency not installable: librust-gimli-0+indexmap-dev (>= 0.26)

[Lucas Nussbaum]

Source: dwarf2sources
Version: 0.2.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), dh-cargo, 
> librust-anyhow-1-dev, librust-fallible-iterator-0-dev, 
> librust-gimli-0+indexmap-dev (>= 0.26), librust-memmap-0-dev (>= 0.7), 
> librust-object-0+default-dev (>= 0.29), librust-serde-1+derive-dev, 
> librust-serde-json-1-dev, librust-structopt-0+default-dev (>= 0.3), 
> librust-typed-arena-2-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), dh-cargo, 
> librust-anyhow-1-dev, librust-fallible-iterator-0-dev, 
> librust-gimli-0+indexmap-dev (>= 0.26), librust-memmap-0-dev (>= 0.7), 
> librust-object-0+default-dev (>= 0.29), librust-serde-1+derive-dev, 
> librust-serde-json-1-dev, librust-structopt-0+default-dev (>= 0.3), 
> librust-typed-arena-2-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [916 B]
> Get:5 copy:/<>/apt_archive ./ Packages [949 B]
> Fetched 2474 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  sbuild-build-depends-main-dummy : Depends: librust-gimli-0+indexmap-dev (>= 
> 0.26) but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/dwarf2sources_0.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-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=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.