date:20240524

Processing control commands:

> tags -1 patch
Bug #1070649 [src:libvmod-re2] libvmod-re2: FTBFS with libre2-11 (experimental)
Added tag(s) patch.

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

Bug#1070649: libvmod-re2: FTBFS with libre2-11 (experimental)

2024-05-24 Thread Gianfranco Costamagna


control: tags -1 patch

Hello, bumping c++11 to c++17 works to make the build succeed.
Please also see Ubuntu build with the patch
https://launchpad.net/ubuntu/+source/libvmod-re2/2.0.0-2ubuntu1


thanks for considering it.

Gianfranco

diff -Nru libvmod-re2-2.0.0/debian/changelog libvmod-re2-2.0.0/debian/changelog
--- libvmod-re2-2.0.0/debian/changelog  2022-10-23 16:36:29.0 +0200
+++ libvmod-re2-2.0.0/debian/changelog  2024-05-25 07:27:43.0 +0200
@@ -1,3 +1,10 @@
+libvmod-re2 (2.0.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build failure by using std=c++17 (Closes: #1070649)
+
+ -- Gianfranco Costamagna   Sat, 25 May 2024 
07:27:43 +0200
+
 libvmod-re2 (2.0.0-2) unstable; urgency=medium

   * Add debian/gbp.conf.
diff -Nru libvmod-re2-2.0.0/debian/patches/series 
libvmod-re2-2.0.0/debian/patches/series
--- libvmod-re2-2.0.0/debian/patches/series 2022-10-23 16:36:29.0 
+0200
+++ libvmod-re2-2.0.0/debian/patches/series 2024-05-25 07:26:24.0 
+0200
@@ -5,3 +5,4 @@
 0005-Fix-expected-test-output-for-missing-subroutine.patch
 0006-Increase-test-timeout.patch
 0007-Fix-typo-in-documentation.patch
+std-c++17.patch
diff -Nru libvmod-re2-2.0.0/debian/patches/std-c++17.patch 
libvmod-re2-2.0.0/debian/patches/std-c++17.patch
--- libvmod-re2-2.0.0/debian/patches/std-c++17.patch1970-01-01 
01:00:00.0 +0100
+++ libvmod-re2-2.0.0/debian/patches/std-c++17.patch2024-05-25 
07:27:43.0 +0200
@@ -0,0 +1,29 @@
+Description: New absl/re2 requires at least std=c++17
+/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than 
C++14 are not supported."
+
+Author: Gianfranco Costamagna 
+Bug-Debian: https://bugs.debian.org/1070649
+Last-Update: 2024-05-25
+
+--- libvmod-re2-2.0.0.orig/configure.ac
 libvmod-re2-2.0.0/configure.ac
+@@ -98,7 +98,7 @@ AC_CHECK_HEADER_STDBOOL
+ AC_LANG(C++)
+ SAVE_CXXFLAGS="$CXXFLAGS"
+ SAVE_LDFLAGS="$LDFLAGS"
+-CXXFLAGS+=" -std=c++11"
++CXXFLAGS+=" -std=c++17"
+ LDFLAGS+=" -lre2"
+ # Check if the Set::Match() method supports error reporting, to notify
+ # if a match failed due to the DFA hitting the max_mem
+--- libvmod-re2-2.0.0.orig/src/Makefile.am 2024-05-25 07:25:25.0 
+0200
 libvmod-re2-2.0.0/src/Makefile.am  2024-05-25 07:29:41.798272339 +0200
+@@ -2,7 +2,7 @@ AUTOMAKE_OPTIONS = subdir-objects
+
+ AM_CFLAGS = $(VARNISHAPI_CFLAGS) -Wall -Werror -Wextra -std=c99
+ AM_LDFLAGS = $(VARNISHAPI_LIBS) $(VMOD_LDFLAGS)
+-AM_CXXFLAGS = -Wall -Werror -Wextra -std=c++11 @RE2_CFLAGS@
++AM_CXXFLAGS = -Wall -Werror -Wextra -std=c++17 @RE2_CFLAGS@
+
+ vmod_LTLIBRARIES = libvmod_re2.la
+


On Mon, 6 May 2024 11:26:43 -0400 Stefano Rivera  wrote:

Source: libvmod-re2
Version: 2.0.0-2
Severity: important
Tags: ftbfs
Control: affects -1 src:re2

libvmod-re2 fails to build with re2 from experimental:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/varnish -Wall -Werror -Wextra -std=c99 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -pthread -fstack-protector -c vmod_re2.c  -fPIC -DPIC -o .libs/vmod_re2.o
In file included from /usr/include/absl/base/config.h:86,
 from /usr/include/absl/base/internal/invoke.h:40,
 from /usr/include/absl/base/call_once.h:34,
 from /usr/include/re2/re2.h:222,
 from vre2/vre2set.h:43,
 from vre2/vre2set.cpp:34:
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than 
C++14 are not supported."

Full build log: 
https://debusine.debian.net/artifact/66531/libvmod-re2_2.0.0-2_amd64-2024-05-06T15:18:37Z.build

It looks like it needs to set a higher C++ std version.

Stefano




OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071622: marked as done (falcosecurity-scap-dkms: missing dependency on adduser)

Your message dated Sat, 25 May 2024 04:49:16 +
with message-id 
and subject line Bug#1071622: fixed in falcosecurity-libs 0.15.1-4
has caused the Debian Bug report #1071622,
regarding falcosecurity-scap-dkms: missing dependency on adduser
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.)


-- 
1071622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: falcosecurity-scap-dkms
Version: 0.15.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Setting up falcosecurity-scap-dkms (0.15.1-3) ...
  /var/lib/dpkg/info/falcosecurity-scap-dkms.postinst: 9: addgroup: not found
  dpkg: error processing package falcosecurity-scap-dkms (--configure):
   installed falcosecurity-scap-dkms package post-installation script 
subprocess returned error exit status 1
  Processing triggers for libc-bin (2.38-11) ...
  Errors were encountered while processing:
   falcosecurity-scap-dkms

adduser no longer gets installed transitively.


cheers,

Andreas


falcosecurity-scap-dkms_0.15.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: falcosecurity-libs
Source-Version: 0.15.1-4
Done: Dima Kogan 

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

Debian distribution maintenance software
pp.
Dima Kogan  (supplier of updated falcosecurity-libs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 24 May 2024 21:32:53 -0700
Source: falcosecurity-libs
Architecture: source
Version: 0.15.1-4
Distribution: unstable
Urgency: medium
Maintainer: Dima Kogan 
Changed-By: Dima Kogan 
Closes: 1071622
Changes:
 falcosecurity-libs (0.15.1-4) unstable; urgency=medium
 .
   * Reverted the use-group-to-access-scap-device patches.
 Because they didn't work properly. (Reopens: #745706)
 (Closes: #1071622)
Checksums-Sha1:
 09ec34bd59d5d9d1c5f545f2006ca321cc80584b 2613 falcosecurity-libs_0.15.1-4.dsc
 d02f04dd6ee7b64fb1280457f0f7a9383ff4c55d 9316 
falcosecurity-libs_0.15.1-4.debian.tar.xz
 1d4375a94f8cf07ece2acc258be5b4f75964713d 14549 
falcosecurity-libs_0.15.1-4_source.buildinfo
Checksums-Sha256:
 c0a0b64be5980bde406185a2c595a494db15ee3b6baca52a921684f684d04fb8 2613 
falcosecurity-libs_0.15.1-4.dsc
 8c0bf8640bdd3cc6ee53de8e128988494e0d6bc5e30da16b8e9479a98286c3bd 9316 
falcosecurity-libs_0.15.1-4.debian.tar.xz
 f0741c04afa48f394bed1253d13e9cbd17e7833febdacefd9424e3dba3bc1520 14549 
falcosecurity-libs_0.15.1-4_source.buildinfo
Files:
 d73c383918ed54909ab90e783a47591b 2613 libdevel optional 
falcosecurity-libs_0.15.1-4.dsc
 2455db0d413613d309159574448faac5 9316 libdevel optional 
falcosecurity-libs_0.15.1-4.debian.tar.xz
 34b86c71de043d66d4ac3f8d008c1072 14549 libdevel optional 
falcosecurity-libs_0.15.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmZRaigSHGRrb2dhbkBk
ZWJpYW4ub3JnAAoJEKzHws8wlBGI84oQAJ+llkhvRl9IBNYPjsEK6A4uk2LKZpIP
MJyGCkzT04zkKHrDxMKk1IREVvQqcOnDYnofPueu+4UcNihxD44M8J4tTZCV+M0q
vSrJqPLZKFc7v7MDiKGsAt3JDeGM4EtFDHvLaB7utXjNzY/DLvAC+sRgho5w8MUF
tktkEeyMVpckKQ5+47TRK5cGntZC40i/7gD7konACQsHpbime15EscVEBVz72cJD
fxcPT8sJrGQPjmTrk0LpiVJC4h0qSI5AhCfAfT1FVqZjvQlkuBsqKnh3oq1pI8Yz
D4oOx8aqcfhr+di8RMlCVvabzL/SYZRI56zO4GxMWwqrdSqvxAwmgbpFJj4j60I7
Jdu0TK4o+SW0BtkdnUBDFwsgJTxOMSXIiDmHlSaRTeIpVeIT6GwcED3/AyRtv2Ty
Za3pQbPhIdqk0C7ybUr1LaDvzZ2R31Pz3ZHSL0Cv62Rk1uy0KFF1zvOfMnUfo9lp
X3a+MyfAlpfM1boep5Z5KgFeBIp3IgBwcnEMYZ5JbButSihixJkitIo1Vw4hcSDS
9DnAJHnO2scqLrrlIKJ0WjZ0gscRR7scU4DVbJG0eFBvVsxlLiS+UZfY1GS2Ts+V
3f2wB3QuuAcZ0GeF7CuRY1FGwMBAEeD+oQGw+ts+HmJYBGjekV1W6qyWadG7rCVf
sVOfVe27BzG0
=4JyD
-END PGP SIGNATURE-



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

Bug#1071362: rpy2: FTBFS: rpy2/tests/rinterface/test_embedded_r.py s.......Fatal Python error: Segmentation fault

2024-05-24 Thread Bo YU


Hi,
On Sat, May 18, 2024 at 06:41:53AM -0500, Dirk Eddelbuettel wrote:


On 17 May 2024 at 23:05, Santiago Vila wrote:
| Dirk Eddelbuettel wrote:
| > Is there a chance this could be spurious?
|
| Unlikely because it also happens here:
|
| https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rpy2.html

Ok, I will get in touch with Laurent.


hmm, the failure will not happen on riscv64 real hardware when I am
trying to get below diff file.

--
Regards,
--
  Bo YU

diff -Nru rpy2-3.5.16/debian/changelog rpy2-3.5.16/debian/changelog
--- rpy2-3.5.16/debian/changelog2024-04-05 04:42:35.0 +0800
+++ rpy2-3.5.16/debian/changelog2024-05-19 22:32:19.0 +0800
@@ -1,3 +1,10 @@
+rpy2 (3.5.16-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Skip some tests on riscv64. (Closes: #-1) 
+
+ -- BO YU   Sun, 19 May 2024 22:32:19 +0800
+
 rpy2 (3.5.16-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru rpy2-3.5.16/debian/patches/series rpy2-3.5.16/debian/patches/series
--- rpy2-3.5.16/debian/patches/series   2023-08-27 00:04:33.0 +0800
+++ rpy2-3.5.16/debian/patches/series   2024-05-19 22:30:46.0 +0800
@@ -1,3 +1,3 @@
 #relax_cffi_version_requirement
 #comment_out_one_test
-skip_complex_tests_on_mips64el
+skip_complex_tests_on_mips64el_and_riscv64
diff -Nru rpy2-3.5.16/debian/patches/skip_complex_tests_on_mips64el 
rpy2-3.5.16/debian/patches/skip_complex_tests_on_mips64el
--- rpy2-3.5.16/debian/patches/skip_complex_tests_on_mips64el   2023-08-27 
00:59:57.0 +0800
+++ rpy2-3.5.16/debian/patches/skip_complex_tests_on_mips64el   1970-01-01 
08:00:00.0 +0800
@@ -1,148 +0,0 @@
-Description: Skip complex-valued tests on mips64el
-Bug-Debian: https://bugs.debian.org/1050432
-Reviewed-By: Dirk Eddelbuettel 
-Last-Update: 2023-08-26
-
 rpy2-3.5.13.orig/rpy2/tests/rinterface/test_na.py
-+++ rpy2-3.5.13/rpy2/tests/rinterface/test_na.py
-@@ -1,6 +1,8 @@
- import pytest
- import math
- import rpy2.rinterface as ri
-+import sys
-+import platform
- 
- ri.initr()
- 
-@@ -147,7 +149,8 @@ def test_NACharacter_in_vector():
- assert x.get_charsxp(1).rid == na_str.rid
- assert x[2] == 'cd'
- 
--
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_R_to_NAComplex():
- r_na_complex = ri.evalr('NA_complex_')[0]
- assert math.isnan(r_na_complex.real)
 rpy2-3.5.13.orig/rpy2/tests/rinterface/test_vector_complex.py
-+++ rpy2-3.5.13/rpy2/tests/rinterface/test_vector_complex.py
-@@ -1,9 +1,13 @@
- import pytest
- import rpy2.rinterface as ri
-+import sys
-+import platform
- 
- ri.initr()
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_init_from_seqr():
- seq = [1+2j, 5+7j, 0+1j]
- v = ri.ComplexSexpVector(seq)
-@@ -18,17 +22,23 @@ def test_init_from_seq_invalid_item():
- ri.ComplexSexpVector(seq)
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_getitem():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- assert vec[1] == 5+7j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_setitem():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec[1] = 100+3j
- assert vec[1] == 100+3j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_getslice():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec_s = vec[0:2]
-@@ -37,6 +47,8 @@ def test_getslice():
- assert vec_s[1] == 5+7j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_getslice_negative():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec_s = vec[-2:-1]
-@@ -44,6 +56,8 @@ def test_getslice_negative():
- assert vec_s[0] == 5+7j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_setslice():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec[0:2] = ri.ComplexSexpVector([100+3j, 5-5j])
-@@ -52,6 +66,8 @@ def test_setslice():
- assert vec[1] == 5-5j
- 
- 
-+@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 
'little',
-+reason="Complex tests fail for 'mips64el'.")
- def test_setslice_negative():
- vec = ri.ComplexSexpVector([1+2j, 5+7j, 0+1j])
- vec[-2:-1] = ri.ComplexSexpVector([100+3j, ])
-@@ -59,6 +75,8 @@ def test_setslice_negative():
-

Bug#1071813: spyder-memory-profiler: FTBFS: E ImportError: cannot import name 'get_icon' from 'spyder.utils.qthelpers' (/usr/lib/python3/dist-packages/spyder/utils/qthelpers.py)

2024-05-24 Thread Jitse Niesen


Hello,

This is the former upstream maintainer of spyder-memory-profiler. I 
decided to stop maintaining the plugin, because it depends on 
python-memory-profiler which is also no longer maintained. As a result, 
spyder-memory-profiler is no longer compatible with recent versions of 
Spyder and that probably explains the error.


Let me know if you need more information.

All the best,
Jitse Niesen


On 25/05/2024 01:33, Santiago Vila wrote:

Package: src:spyder-memory-profiler
Version: 0.2.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


 


[...]
 debian/rules build
dh build --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler
copying spyder_memory_profiler/memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler
copying spyder_memory_profiler/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example
copying spyder_memory_profiler/example/profiling_test_script.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example
copying spyder_memory_profiler/example/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data
copying spyder_memory_profiler/data/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets
copying spyder_memory_profiler/widgets/memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets
copying spyder_memory_profiler/widgets/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir
copying 
spyder_memory_profiler/example/subdir/profiling_test_script2.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir
copying spyder_memory_profiler/example/subdir/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images
copying spyder_memory_profiler/data/images/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests
copying spyder_memory_profiler/widgets/tests/test_memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests 

copying spyder_memory_profiler/widgets/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests
copying spyder_memory_profiler/data/images/spyder.memory_profiler.png 
-> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images

I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler
copying spyder_memory_profiler/memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler
copying spyder_memory_profiler/__init__.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example
copying spyder_memory_profiler/example/profiling_test_script.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example
copying spyder_memory_profiler/example/__init__.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/data
copying spyder_memory_profiler/data/__init__.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/data
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/widgets
copying

Bug#1070677: fail2ban fails: "Failed during configuration: Have not found any log file for sshd jail"

2024-05-24 Thread Vincent Lefevre

On 2024-05-24 14:52:08 +0200, Sylvestre Ledru wrote:
> Could you please propose a PR ? I didn't find the time to fix this lately
> (and i don't use fail2ban anymore).

https://salsa.debian.org/python-team/packages/fail2ban/-/merge_requests/9

This restores the use of nftables and selects the systemd backend
for the same set of jails as Fedora and Arch (openSUSE also has
mysql, but this is probably a mistake because Fedora and Arch had
it initially but it got removed because "mysqld does not log login
attempts to the journal" -- I did not check whether this is still
the case or the Fedora and Arch settings are out-of-date).

Note that the setting for sshd is necessary. For the other jails,
this may also be needed if the user has enabled other jails but has
not set the backend explicitly (not needed with fail2ban 1.0.2-3 in
testing). For instance, in my case, I had enabled the postfix jail,
and without this setting, after the upgrade from testing, fail2ban
was failing for the same reason as with sshd.

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

Bug#1071817: xavs2: FTBFS: source/common/vec/intrinsic_intra-pred.c:775:13: error: implicit declaration of function ‘memcpy’


Package: src:xavs2
Version: 1.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --sourcedirectory=build/linux
   dh_update_autotools_config -O--sourcedirectory=build/linux
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
   dh_autoreconf -O--sourcedirectory=build/linux
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
VER_SHA="unstable" dh_auto_configure -- \
--enable-shared \
--enable-pic \
--extra-cflags="-Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
-DXAVS2_EXPORTS"
cd build/linux && ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info 
--sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode 
--disable-dependency-tracking --enable-shared --enable-pic "--extra-cflags=-Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility=hidden -DXAVS2_EXPORTS"
Unknown option --build=x86_64-linux-gnu, ignored
Unknown option --mandir=${prefix}/share/man, ignored
Unknown option --infodir=${prefix}/share/info, ignored
Unknown option --sysconfdir=/etc, ignored
Unknown option --localstatedir=/var, ignored
Unknown option --disable-option-checking, ignored
Unknown option --disable-silent-rules, ignored
Unknown option --runstatedir=/run, ignored
Unknown option --disable-maintainer-mode, ignored
Unknown option --disable-dependency-tracking, ignored
platform:  X86_64
byte order:little-endian
system:LINUX
cli:   yes
libxavs2:  internal
shared:yes
static:yes
asm:   yes
interlaced:yes
avs:   no
lavf:  no
ffms:  no
mp4:   no
gpl:   yes
thread:posix
opencl:no
filters:   crop select_every
lto:   no
debug: no
gprof: no
strip: no
PIC:   yes
bit depth: 8
chroma format: all

You can run 'make' or 'make fprofiled' now.
make[1]: Leaving directory '/<>'
   dh_auto_build -O--sourcedirectory=build/linux
cd build/linux && make -j2
make[1]: Entering directory '/<>/build/linux'
[33m dependency file generation... [0m
[33m [Compiling]: /<>/source/test/test.c [0m
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -I. -I/<>/source -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
-DXAVS2_EXPORTS -DARCH_X86_64=1 -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5 -fPIC -fomit-frame-pointer -fno-tree-vectorize -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -I. 
-I/<>/source -I/<>/source/common -I/<>/source/common/x86 -I/<>/source/common/vec 
-I/<>/source/encoder -I/<>/source/test -mmmx -msse -msse2 -msse3 -mssse3 -msse4 -msse4.1 -msse4.2 -msse4a -c -o test/test.o 
/<>/source/test/test.c
[33m [Compiling]: /<>/source/common/block_info.c [0m
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -I. -I/<>/source -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
-DXAVS2_EXPORTS -DARCH_X86_64=1 -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5 -fPIC -fomit-frame-pointer -fno-tree-vectorize -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -I. 
-I/<>/source -I/<>/source/common -I/<>/source/common/x86 -I/<>/source/common/vec 
-I/<>/source/encoder -I/<>/source/test -mmmx -msse -msse2 -msse3 -mssse3 -msse4 -msse4.1 -msse4.2 -msse4a -c -o common/block_info.o 
/<>/source/common/block_info.c
[33m [Compiling]: /<>/source/common/common.c [0m
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -I. -I/<>/source -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
-DXAVS2_EXPORTS -DARCH_X86_64=1 -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5 -fPIC -fomit-frame-pointer -fno-tree-vectorize -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -I. 
-I/<>/source -I/<>/source/common -I/<>/source/common/x86 -I/<>/source/common/vec 
-I/<>/source/encoder -I/<>/source/test -mmmx -msse -msse2 -msse3 -mssse3 -msse4 -msse4.1 -msse4.2 -msse4a -c -o common/common.o 
/<>/source/common/common.c
[33m [Compiling]: /<>/source/common/cpu.c [0m
gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64 -g -O2

Bug#1071816: umap-learn: FTBFS: E TypeError: exceptions must be derived from Warning, not


Package: src:umap-learn
Version: 0.5.4+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.11/build/umap
copying umap/plot.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/sparse.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/aligned_umap.py -> 
/<>/.pybuild/cpython3_3.11/build/umap
copying umap/layouts.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/utils.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/umap_.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/parametric_umap.py -> 
/<>/.pybuild/cpython3_3.11/build/umap
copying umap/validation.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/spectral.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/distances.py -> /<>/.pybuild/cpython3_3.11/build/umap
copying umap/__init__.py -> /<>/.pybuild/cpython3_3.11/build/umap
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dh_auto_test -- --system=custom --test-args="PYTHONPATH={build_dir} {interpreter} -m 
pytest"
I: pybuild base:311: PYTHONPATH=/<>/.pybuild/cpython3_3.11/build 
python3.11 -m pytest
= test session starts ==
platform linux -- Python 3.11.9, pytest-8.1.2, pluggy-1.5.0
rootdir: /<>
collected 209 items

umap/tests/test_aligned_umap.py s[  2%]
umap/tests/test_chunked_parallel_spatial_metric.py s [ 12%]
s[ 22%]
umap/tests/test_composite_models.py .s.. [ 24%]
umap/tests/test_data_input.py .  [ 24%]
umap/tests/test_densmap.py .s..  [ 26%]
umap/tests/test_parametric_umap.py sss   [ 30%]
umap/tests/test_plot.py s[ 30%]
umap/tests/test_spectral.py ..   [ 31%]
umap/tests/test_umap_get_feature_names_out.py    [ 33%]
umap/tests/test_umap_metrics.py s.s. [ 52%]
..   [ 53%]
umap/tests/test_umap_nn.py ..sss..   [ 58%]
umap/tests/test_umap_on_iris.py  [ 64%]
umap/tests/test_umap_ops.py ....F..  [ 73%]
umap/tests/test_umap_repeated_data.py .  [ 77%]
umap/tests/test_umap_trustworthiness.py ..   [ 82%]
umap/tests/test_umap_validation_params.py .. [ 97%]
..   [100%]

=== FAILURES ===
 test_disconnected_data[True-jaccard-1] 

num_isolates = 1, metric = 'jaccard', force_approximation = True

@pytest.mark.parametrize("num_isolates", [1, 5])
@pytest.mark.parametrize("metric", ["jaccard", "hellinger"])
@pytest.mark.parametrize("force_approximation", [True, False])
def test_disconnected_data(num_isolates, metric, force_approximation):
options = [False, True]
disconnected_data = np.random.choice(a=options, size=(10, 30), p=[0.6, 
1 - 0.6])
# Add some disconnected data for the corner case test
disconnected_data = np.vstack(
[disconnected_data, np.zeros((num_isolates, 30), dtype="bool")]
)
new_columns = np.zeros((num_isolates + 10, num_isolates), dtype="bool")
for i in range(num_isolates):
new_columns[10 + i, i] = True
disconnected_data = np.hstack([disconnected_data, new_columns])


  with pytest.warns(None) as w:


umap/tests/test_umap_ops.py:119:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = WarningsChecker(record=True), expected_warning = None, match_expr = None

def __init__(
self,
expected_warning: Union[Type[Warning], Tuple[Type[Warning], ...]] = 
Warning,
match_expr: Optional[Union[str, Pattern[str]]] = None,
*,
_ispytest: bool = False,
) -> None:
check_ispytest(_ispytest)
super().__init__(_ispytest=True)

msg = "exceptions must be derived

Bug#1071814: tpot: FTBFS: ERROR: Failure: AttributeError (module 'numpy' has no attribute 'float'.


Package: src:tpot
Version: 0.11.7+dfsg-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3,mkdocs --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build

[... snipped ...]

The aliases was originally deprecated in NumPy 1.20; for more details and 
guidance see the original release note at:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in 
loadTestsFromName
module = self.importer.importFromPath(
 ^
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
   
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  
  File "/usr/lib/python3.11/imp.py", line 235, in load_module
return load_source(name, filename, file)
   ^
  File "/usr/lib/python3.11/imp.py", line 172, in load_source
module = _load(spec)
 ^^^
  File "", line 721, in _load
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File 
"/<>/.pybuild/cpython3_3.11_tpot/build/tests/feature_transformers_tests.py",
 line 2, in 
from tpot.builtins import CategoricalSelector, ContinuousSelector
  File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/__init__.py", line 
27, in 
from .tpot import TPOTClassifier, TPOTRegressor
  File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/tpot.py", line 31, in 

from .base import TPOTBase
  File "/<>/.pybuild/cpython3_3.11_tpot/build/tpot/base.py", line 68, in 

from .builtins import CombineDFs, StackingEstimator
  File 
"/<>/.pybuild/cpython3_3.11_tpot/build/tpot/builtins/__init__.py", line 
29, in 
from .one_hot_encoder import OneHotEncoder, 
auto_select_categorical_features, _transform_selected
  File 
"/<>/.pybuild/cpython3_3.11_tpot/build/tpot/builtins/one_hot_encoder.py",
 line 136, in 
class OneHotEncoder(BaseEstimator, TransformerMixin):
  File 
"/<>/.pybuild/cpython3_3.11_tpot/build/tpot/builtins/one_hot_encoder.py",
 line 216, in OneHotEncoder
def __init__(self, categorical_features='auto', dtype=np.float,
  
  File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 324, in 
__getattr__
raise AttributeError(__former_attrs__[attr])
AttributeError: module 'numpy' has no attribute 'float'.
`np.float` was a deprecated alias for the builtin `float`. To avoid this error 
in existing code, use `float` by itself. Doing this will not modify any 
behavior and is safe. If you specifically wanted the numpy scalar type, use 
`np.float64` here.
The aliases was originally deprecated in NumPy 1.20; for more details and 
guidance see the original release note at:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

==
ERROR: Failure: ImportError (
`load_boston` has been removed from scikit-learn since version 1.2.

The Boston housing prices dataset has an ethical problem: as
investigated in [1], the authors of this dataset engineered a
non-invertible variable "B" assuming that racial self-segregation had a
positive impact on house prices [2]. Furthermore the goal of the
research that led to the creation of this dataset was to study the
impact of air quality but it did not give adequate demonstration of the
validity of this assumption.

The scikit-learn maintainers therefore strongly discourage the use of
this dataset unless the purpose of the code is to study and educate
about ethical issues in data science and machine learning.

In this special case, you can fetch the dataset from the original
source::

import pandas as pd
import numpy as np

data_url = "http://lib.stat.cmu.edu/datasets/boston;
raw_df = pd.read_csv(data_url, sep="\s+", skiprows=22, header=None)
data =

Bug#1071815: troffcvt: FTBFS: fd.c:24:17: error: implicit declaration of function ‘getdtablesize’


Package: src:troffcvt
Version: 1.04+repack1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh_testdir
/usr/bin/make -f debian/rules _b_
make[1]: Entering directory '/<>'
mkdir -p debian/build
touch debian/build/_x_
sed imboot/imboot.pl > debian/build/imboot \
-e "s#\$(PERLPATH)#`which perl`#" \
-e "s#\$(CONFIGROOTDIR)#`pwd`/config#"
chmod a+x debian/build/imboot
touch imboot/_b_
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wl,-z,relro 
msub/msub.c -o debian/build/msub
msub/msub.c: In function ‘Substitute’:
msub/msub.c:602:32: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  602 | (void) write (1, p, (int) refInitIdx);
  |^~
msub/msub.c:606:40: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  606 | (void) write (1, vp->value, (int) strlen 
(vp->value));
  |
^~
msub/msub.c:609:24: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  609 | (void) write (1, p, (int) strlen (p));
  |^~
touch msub/_b_
sed WRPRC/config/site.def > WRPRC/config/site.def.temp \
-e "s%^#define ConfigRootDir .*\$%#define ConfigRootDir 
\"`pwd`/config\"%"
mv WRPRC/config/site.def.temp WRPRC/config/site.def
(set -e; cd WRPRC; make World; make install)
make[2]: Entering directory '/<>/WRPRC'

Building WRPRC 2.11 imake configuration file distribution

Fri May 24 23:46:14 UTC 2024

make -w Makefile
make[3]: Entering directory '/<>/WRPRC'
imboot -C WRPRC2  . .
rm Makefile.bak
mv Makefile Makefile.bak
imake  -DUseInstalled -I./config -I/<>/config/WRPRC2 -DTOPDIR=. 
-DCURDIR=.
make[3]: Leaving directory '/<>/WRPRC'
make -w Makefiles
make[3]: Entering directory '/<>/WRPRC'
making Makefiles in ./config...
rm Makefile.bak
mv Makefile Makefile.bak
imake  -DUseInstalled -I.././config -I/<>/config/WRPRC2 
-DTOPDIR=../. -DCURDIR=./config
make[4]: Entering directory '/<>/WRPRC/config'
make[4]: Nothing to be done for 'Makefiles'.
make[4]: Leaving directory '/<>/WRPRC/config'
making Makefiles in ./R1-docs...
rm Makefile.bak
mv Makefile Makefile.bak
imake  -DUseInstalled -I.././config -I/<>/config/WRPRC2 
-DTOPDIR=../. -DCURDIR=./R1-docs
make[4]: Entering directory '/<>/WRPRC/R1-docs'
make[4]: Nothing to be done for 'Makefiles'.
make[4]: Leaving directory '/<>/WRPRC/R1-docs'
make[3]: Leaving directory '/<>/WRPRC'
make -w clean
make[3]: Entering directory '/<>/WRPRC'
rm -f WRPRC-2.11.tar.gz
rm -f -r WRPRC-2.11
rm -f tutorial.ps
rm -f reference.ps
rm -f p-s.ps
rm -f limits.ps
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *.a .emacs_* tags TAGS make.log MakeOut 
"#"*
cleaning in ./config...
make[4]: Entering directory '/<>/WRPRC/config'
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *.a .emacs_* tags TAGS make.log MakeOut 
"#"*
make[4]: Leaving directory '/<>/WRPRC/config'
cleaning in ./R1-docs...
make[4]: Entering directory '/<>/WRPRC/R1-docs'
rm -f config-WRPRC.ps
rm -f installation.ps
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *.a .emacs_* tags TAGS make.log MakeOut 
"#"*
make[4]: Leaving directory '/<>/WRPRC/R1-docs'
make[3]: Leaving directory '/<>/WRPRC'

Fri May 24 23:46:14 UTC 2024

Build of WRPRC2 configuration distribution complete.
Now you can run 'make install'

make[2]: Leaving directory '/<>/WRPRC'
make[2]: Entering directory '/<>/WRPRC'
installing in ./config...
make[3]: Entering directory '/<>/WRPRC/config'
+ mkdir -p /<>/config/WRPRC2
+ install -c -m 0444 README /<>/config/WRPRC2/README
+ install -c -m 0444 Imake.tmpl /<>/config/WRPRC2/Imake.tmpl
+ install -c -m 0444 Imake.params /<>/config/WRPRC2/Imake.params
+ install -c -m 0444 Imake.p-params 
/<>/config/WRPRC2/Imake.p-params
+ install -c -m 0444 Imake.rules /<>/config/WRPRC2/Imake.rules
+ install -c -m 0444 Imake.p-rules /<>/config/WRPRC2/Imake.p-rules
+ install -c -m 0444 site.def /<>/config/WRPRC2/site.def
+ install -c -m 0444 site.p-def /<>/config/WRPRC2/site.p-def
+ install -c -m 0444 FreeBSD.cf /<>/config/WRPRC2/FreeBSD.cf
+ install -c -m 0444 Imake.cf /<>/config/WRPRC2/Imake.cf
+ install -c -m 0444 Mips.cf /<>/config/WRPRC2/Mips.cf
+ install -c -m 0444 NetBSD.cf /<>/config/WRPRC2/NetBSD.cf
+ install -c -m 0444 Next.cf /<>/config/WRPRC2/Next.cf
+ install -c -m 0444 cray.cf /<>/config/WRPRC2/cray.cf
+ install -c -m 0444 generic.cf /<>/config/WRPRC2/generic.cf
+

Bug#1071813: spyder-memory-profiler: FTBFS: E ImportError: cannot import name 'get_icon' from 'spyder.utils.qthelpers' (/usr/lib/python3/dist-packages/spyder/utils/qthelpers.py)


Package: src:spyder-memory-profiler
Version: 0.2.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler
copying spyder_memory_profiler/memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler
copying spyder_memory_profiler/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example
copying spyder_memory_profiler/example/profiling_test_script.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example
copying spyder_memory_profiler/example/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data
copying spyder_memory_profiler/data/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets
copying spyder_memory_profiler/widgets/memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets
copying spyder_memory_profiler/widgets/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir
copying spyder_memory_profiler/example/subdir/profiling_test_script2.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir
copying spyder_memory_profiler/example/subdir/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images
copying spyder_memory_profiler/data/images/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images
creating 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests
copying spyder_memory_profiler/widgets/tests/test_memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests
copying spyder_memory_profiler/widgets/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/widgets/tests
copying spyder_memory_profiler/data/images/spyder.memory_profiler.png -> 
/<>/.pybuild/cpython3_3.12_spyder-memory-profiler/build/spyder_memory_profiler/data/images
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler
copying spyder_memory_profiler/memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler
copying spyder_memory_profiler/__init__.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example
copying spyder_memory_profiler/example/profiling_test_script.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example
copying spyder_memory_profiler/example/__init__.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/data
copying spyder_memory_profiler/data/__init__.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/data
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/widgets
copying spyder_memory_profiler/widgets/memoryprofiler.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/widgets
copying spyder_memory_profiler/widgets/__init__.py -> 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/widgets
creating 
/<>/.pybuild/cpython3_3.11_spyder-memory-profiler/build/spyder_memory_profiler/example/subdir
copying spyder_memory_profiler/example/subdir/profiling_test_script2.py ->

Bug#1071812: qiskit-ibmq-provider: FTBFS: E AttributeError: module 'numpy' has no attribute 'float'.


Package: src:qiskit-ibmq-provider
Version: 0.4.6-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.12_qiskit-ibmq-provider/build/qiskit

[... snipped ...]

raise AttributeError(__former_attrs__[attr])
E   AttributeError: module 'numpy' has no attribute 'float'.
E   `np.float` was a deprecated alias for the builtin `float`. To avoid this 
error in existing code, use `float` by itself. Doing this will not modify any 
behavior and is safe. If you specifically wanted the numpy scalar type, use 
`np.float64` here.
E   The aliases was originally deprecated in NumPy 1.20; for more details and 
guidance see the original release note at:
E   https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations. Did 
you mean: 'cfloat'?
_ ERROR collecting 
.pybuild/cpython3_3.12_qiskit-ibmq-provider/build/test/ibmq/test_registration.py
 _
test/ibmq/test_registration.py:27: in 
from qiskit.providers.ibmq import IBMQ, IBMQFactory
/usr/lib/python3/dist-packages/qiskit/__init__.py:31: in 
from qiskit.circuit import ClassicalRegister
/usr/lib/python3/dist-packages/qiskit/circuit/__init__.py:58: in 
from .quantumcircuit import QuantumCircuit
/usr/lib/python3/dist-packages/qiskit/circuit/quantumcircuit.py:24: in 
from qiskit.circuit.instruction import Instruction
/usr/lib/python3/dist-packages/qiskit/circuit/instruction.py:45: in 
from qiskit.qobj.models.qasm import QasmQobjInstruction
/usr/lib/python3/dist-packages/qiskit/qobj/models/qasm.py:20: in 
from qiskit.validation.fields import List, Integer, InstructionParameter, 
Nested
/usr/lib/python3/dist-packages/qiskit/validation/fields/__init__.py:43: in 

from .custom import Complex, InstructionParameter, DictParameters
/usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:61: in 

class InstructionParameter(ModelTypeValidator):
/usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:76: in 
InstructionParameter
numpy.integer, numpy.float,
/usr/lib/python3/dist-packages/numpy/__init__.py:324: in __getattr__
raise AttributeError(__former_attrs__[attr])
E   AttributeError: module 'numpy' has no attribute 'float'.
E   `np.float` was a deprecated alias for the builtin `float`. To avoid this 
error in existing code, use `float` by itself. Doing this will not modify any 
behavior and is safe. If you specifically wanted the numpy scalar type, use 
`np.float64` here.
E   The aliases was originally deprecated in NumPy 1.20; for more details and 
guidance see the original release note at:
E   https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations. Did 
you mean: 'cfloat'?
_ ERROR collecting 
.pybuild/cpython3_3.12_qiskit-ibmq-provider/build/test/ibmq/websocket/test_websocket_integration.py
 _
test/ibmq/websocket/test_websocket_integration.py:21: in 
from qiskit import ClassicalRegister, QuantumCircuit, QuantumRegister
/usr/lib/python3/dist-packages/qiskit/__init__.py:31: in 
from qiskit.circuit import ClassicalRegister
/usr/lib/python3/dist-packages/qiskit/circuit/__init__.py:58: in 
from .quantumcircuit import QuantumCircuit
/usr/lib/python3/dist-packages/qiskit/circuit/quantumcircuit.py:24: in 
from qiskit.circuit.instruction import Instruction
/usr/lib/python3/dist-packages/qiskit/circuit/instruction.py:45: in 
from qiskit.qobj.models.qasm import QasmQobjInstruction
/usr/lib/python3/dist-packages/qiskit/qobj/models/qasm.py:20: in 
from qiskit.validation.fields import List, Integer, InstructionParameter, 
Nested
/usr/lib/python3/dist-packages/qiskit/validation/fields/__init__.py:43: in 

from .custom import Complex, InstructionParameter, DictParameters
/usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:61: in 

class InstructionParameter(ModelTypeValidator):
/usr/lib/python3/dist-packages/qiskit/validation/fields/custom.py:76: in 
InstructionParameter
numpy.integer, numpy.float,
/usr/lib/python3/dist-packages/numpy/__init__.py:324: in __getattr__
raise AttributeError(__former_attrs__[attr])
E   AttributeError: module 'numpy' has no attribute 'float'.
E   `np.float` was a deprecated alias for the builtin `float`. To avoid this 
error in existing code, use `float` by itself. Doing this will not modify any 
behavior and is safe. If you specifically wanted the numpy scalar type, use 
`np.float64` here.

Bug#1071811: python-sparse: FTBFS: INTERNALERROR> pluggy._manager.PluginValidationError: unknown hook 'pytest_cmdline_preparse' in plugin >/.pybuild/cpyth


Package: src:python-sparse
Version: 0.15.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --buildsystem=pybuild --test-pytest
   dh_update_autotools_config -O--buildsystem=pybuild -O--test-pytest
   dh_autoreconf -O--buildsystem=pybuild -O--test-pytest
   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<>'
touch sparse/tests/__init__.py
make[1]: Leaving directory '/<>'
   dh_auto_configure -O--buildsystem=pybuild -O--test-pytest
   dh_auto_build -O--buildsystem=pybuild -O--test-pytest
I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_sparse
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/sparse
copying sparse/_utils.py -> build/lib/sparse
copying sparse/_umath.py -> build/lib/sparse
copying sparse/_dok.py -> build/lib/sparse
copying sparse/_sparse_array.py -> build/lib/sparse
copying sparse/_slicing.py -> build/lib/sparse
copying sparse/_io.py -> build/lib/sparse
copying sparse/_settings.py -> build/lib/sparse
copying sparse/_version.py -> build/lib/sparse
copying sparse/_numba_extension.py -> build/lib/sparse
copying sparse/_common.py -> build/lib/sparse
copying sparse/__init__.py -> build/lib/sparse
creating build/lib/sparse/_coo
copying sparse/_coo/indexing.py -> build/lib/sparse/_coo
copying sparse/_coo/common.py -> build/lib/sparse/_coo
copying sparse/_coo/numba_extension.py -> build/lib/sparse/_coo
copying sparse/_coo/core.py -> build/lib/sparse/_coo
copying sparse/_coo/__init__.py -> build/lib/sparse/_coo
creating build/lib/sparse/tests
copying sparse/tests/test_dot.py -> build/lib/sparse/tests
copying sparse/tests/test_compressed.py -> build/lib/sparse/tests
copying sparse/tests/test_einsum.py -> build/lib/sparse/tests
copying sparse/tests/test_compressed_convert.py -> build/lib/sparse/tests
copying sparse/tests/test_io.py -> build/lib/sparse/tests
copying sparse/tests/conftest.py -> build/lib/sparse/tests
copying sparse/tests/test_compressed_2d.py -> build/lib/sparse/tests
copying sparse/tests/test_conversion.py -> build/lib/sparse/tests
copying sparse/tests/test_array_function.py -> build/lib/sparse/tests
copying sparse/tests/test_coo.py -> build/lib/sparse/tests
copying sparse/tests/test_dok.py -> build/lib/sparse/tests
copying sparse/tests/test_dask_interop.py -> build/lib/sparse/tests
copying sparse/tests/test_coo_numba.py -> build/lib/sparse/tests
copying sparse/tests/__init__.py -> build/lib/sparse/tests
copying sparse/tests/test_elemwise.py -> build/lib/sparse/tests
creating build/lib/sparse/_compressed
copying sparse/_compressed/compressed.py -> build/lib/sparse/_compressed
copying sparse/_compressed/indexing.py -> build/lib/sparse/_compressed
copying sparse/_compressed/common.py -> build/lib/sparse/_compressed
copying sparse/_compressed/convert.py -> build/lib/sparse/_compressed
copying sparse/_compressed/__init__.py -> build/lib/sparse/_compressed
running egg_info
creating sparse.egg-info
writing sparse.egg-info/PKG-INFO
writing dependency_links to sparse.egg-info/dependency_links.txt
writing entry points to sparse.egg-info/entry_points.txt
writing requirements to sparse.egg-info/requires.txt
writing top-level names to sparse.egg-info/top_level.txt
writing manifest file 'sparse.egg-info/SOURCES.txt'
reading manifest file 'sparse.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.html' under directory 'sparse'
warning: no files found matching 'setup.py'
warning: no files found matching 'requirements.txt'
warning: no files found matching '*.txt' under directory 'requirements'
no previously-included directories found matching 'docs/_build'
warning: no files found matching 'versioneer.py'
adding license file 'LICENSE'
writing manifest file 'sparse.egg-info/SOURCES.txt'
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/sparse
copying build/lib/sparse/_utils.py -> build/bdist.linux-x86_64/wheel/sparse
copying build/lib/sparse/_umath.py -> build/bdist.linux-x86_64/wheel/sparse
copying build/lib/sparse/_dok.py -> build/bdist.linux-x86_64/wheel/sparse
copying build/lib/sparse/_sparse_array.py -> 
build/bdist.linux-x86_64/wheel/sparse
copying build/lib/sparse/_slicing.py -> build/bdist.linux-x86_64/wheel/sparse
copying build/lib/sparse/_io.py -> build/bdist.linux-x86_64/wheel/sparse
copying build/lib/sparse/_settings.py -> build/bdist.linux-x86_64/wheel/sparse
copying build/lib/sparse/_version.py -> build/bdist.linux-x86_64/wheel/sparse
creating

Bug#1071808: prospector: FTBFS: Failure: ImportError (cannot import name 'find_pylintrc' from 'pylint.config' (/usr/lib/python3/dist-packages/pylint/config/init.py)) ... ERROR


Package: src:prospector
Version: 1.1.7-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.11 setup.py config
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m nose -v tests/" 
dh_auto_test
I: pybuild base:311: python3.11 -m nose -v tests/
Failure: ImportError (cannot import name 'find_pylintrc' from 'pylint.config' 
(/usr/lib/python3/dist-packages/pylint/config/__init__.py)) ... ERROR
test1 (tests.finder.test_file_finder.TestSysPath.test1) ... ok
test2 (tests.finder.test_file_finder.TestSysPath.test2) ... ok
test3 (tests.finder.test_file_finder.TestSysPath.test3) ... ok
test_is_a_venv 
(tests.finder.test_file_finder.TestVirtualenvDetection.test_is_a_venv) ... ok
Windows doesn't allow extremely long paths. This unit test has to be ... ok
test_not_a_venv 
(tests.finder.test_file_finder.TestVirtualenvDetection.test_not_a_venv) ... ok
Failure: ImportError (cannot import name 'find_pylintrc' from 'pylint.config' 
(/usr/lib/python3/dist-packages/pylint/config/__init__.py)) ... ERROR
test_ignore_file 
(tests.suppression.test_suppression.SuppressionTest.test_ignore_file) ... ok
test_ignore_lines 
(tests.suppression.test_suppression.SuppressionTest.test_ignore_lines) ... ok
Failure: SkipTest () ... SKIP
Failure: ImportError (cannot import name 'find_pylintrc' from 'pylint.config' 
(/usr/lib/python3/dist-packages/pylint/config/__init__.py)) ... ERROR
Failure: ImportError (cannot import name 'find_pylintrc' from 'pylint.config' 
(/usr/lib/python3/dist-packages/pylint/config/__init__.py)) ... ERROR
test_multiple_lines (tests.test_blender.TestBlend.test_multiple_lines) ... ok
test_blend_line (tests.test_blender.TestBlendLine.test_blend_line) ... ok
Ensures that the blending works fine when there are no messages to blend ... ok
Verifies that messages pass through if there is nothing to blend ... ok
test_single_blend (tests.test_blender.TestBlendLine.test_single_blend) ... ok
Failure: ImportError (cannot import name 'find_pylintrc' from 'pylint.config' 
(/usr/lib/python3/dist-packages/pylint/config/__init__.py)) ... ERROR
test_char_order (tests.test_message.LocationOrderTest.test_char_order) ... ok
test_line_order (tests.test_message.LocationOrderTest.test_line_order) ... ok
test_path_order (tests.test_message.LocationOrderTest.test_path_order) ... ok
test_sort_between_none_chars 
(tests.test_message.LocationOrderTest.test_sort_between_none_chars) ... ok
test_sort_between_none_lines 
(tests.test_message.LocationOrderTest.test_sort_between_none_lines) ... ok

==
ERROR: Failure: ImportError (cannot import name 'find_pylintrc' from 
'pylint.config' (/usr/lib/python3/dist-packages/pylint/config/__init__.py))
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in 
loadTestsFromName
module = self.importer.importFromPath(
 ^
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
   
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  
  File "/usr/lib/python3.11/imp.py", line 235, in load_module
return load_source(name, filename, file)
   ^
  File "/usr/lib/python3.11/imp.py", line 172, in load_source
module = _load(spec)
 ^^^
  File "", line 721, in _load
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/<>/tests/config/test_datatype.py", line 4, in 
from prospector.config.datatype import OutputChoice
  File "/<>/prospector/config/__init__.py", line 6, in 
from prospector import tools
  File "/<>/prospector/tools/__init__.py", line 7, in 
from prospector.tools.pylint import PylintTool
  File "/<>/prospector/tools/pylint/__init__.py", line 6, in 

from pylint.config import find_pylintrc
ImportError: cannot import name 'find_pylintrc' from 'pylint.config' 
(/usr/lib/python3/dist-packages/pylint/config/__init__.py)

Bug#1071809: protontricks: FTBFS: E assert 'Your system locale is incapable of displaying all characters' in "Using 'zenity' as GUI provider"


Package: src:protontricks
Version: 1.10.5-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --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.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/protontricks
copying src/protontricks/util.py -> build/lib/protontricks
copying src/protontricks/gui.py -> build/lib/protontricks
copying src/protontricks/_version.py -> build/lib/protontricks
copying src/protontricks/config.py -> build/lib/protontricks
copying src/protontricks/winetricks.py -> build/lib/protontricks
copying src/protontricks/flatpak.py -> build/lib/protontricks
copying src/protontricks/steam.py -> build/lib/protontricks
copying src/protontricks/__init__.py -> build/lib/protontricks
creating build/lib/protontricks/cli
copying src/protontricks/cli/desktop_install.py -> build/lib/protontricks/cli
copying src/protontricks/cli/launch.py -> build/lib/protontricks/cli
copying src/protontricks/cli/main.py -> build/lib/protontricks/cli
copying src/protontricks/cli/util.py -> build/lib/protontricks/cli
copying src/protontricks/cli/__init__.py -> build/lib/protontricks/cli
running egg_info
creating src/protontricks.egg-info
writing src/protontricks.egg-info/PKG-INFO
writing dependency_links to src/protontricks.egg-info/dependency_links.txt
writing entry points to src/protontricks.egg-info/entry_points.txt
writing requirements to src/protontricks.egg-info/requires.txt
writing top-level names to src/protontricks.egg-info/top_level.txt
writing manifest file 'src/protontricks.egg-info/SOURCES.txt'
reading manifest file 'src/protontricks.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files found matching '*.yml'
warning: no previously-included files matching '*.py[cod]' found anywhere in 
distribution
warning: no previously-included files matching '__pycache__' found anywhere in 
distribution
adding license file 'LICENSE'
writing manifest file 'src/protontricks.egg-info/SOURCES.txt'
creating build/lib/protontricks/data
creating build/lib/protontricks/data/data
copying src/protontricks/data/data/icon_placeholder.png -> 
build/lib/protontricks/data/data
creating build/lib/protontricks/data/scripts
copying src/protontricks/data/scripts/bwrap_launcher.sh -> 
build/lib/protontricks/data/scripts
copying src/protontricks/data/scripts/wine_launch.sh -> 
build/lib/protontricks/data/scripts
copying src/protontricks/data/scripts/wineserver_keepalive.bat -> 
build/lib/protontricks/data/scripts
copying src/protontricks/data/scripts/wineserver_keepalive.sh -> 
build/lib/protontricks/data/scripts
creating build/lib/protontricks/data/share
creating build/lib/protontricks/data/share/applications
copying src/protontricks/data/share/applications/protontricks-launch.desktop -> 
build/lib/protontricks/data/share/applications
copying src/protontricks/data/share/applications/protontricks.desktop -> 
build/lib/protontricks/data/share/applications
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/protontricks
copying build/lib/protontricks/util.py -> 
build/bdist.linux-x86_64/wheel/protontricks
copying build/lib/protontricks/gui.py -> 
build/bdist.linux-x86_64/wheel/protontricks
copying build/lib/protontricks/_version.py -> 
build/bdist.linux-x86_64/wheel/protontricks
creating build/bdist.linux-x86_64/wheel/protontricks/data
creating build/bdist.linux-x86_64/wheel/protontricks/data/data
copying build/lib/protontricks/data/data/icon_placeholder.png -> 
build/bdist.linux-x86_64/wheel/protontricks/data/data
creating build/bdist.linux-x86_64/wheel/protontricks/data/scripts
copying build/lib/protontricks/data/scripts/bwrap_launcher.sh -> 
build/bdist.linux-x86_64/wheel/protontricks/data/scripts
copying build/lib/protontricks/data/scripts/wineserver_keepalive.sh -> 
build/bdist.linux-x86_64/wheel/protontricks/data/scripts
copying build/lib/protontricks/data/scripts/wine_launch.sh -> 
build/bdist.linux-x86_64/wheel/protontricks/data/scripts
copying build/lib/protontricks/data/scripts/wineserver_keepalive.bat -> 
build/bdist.linux-x86_64/wheel/protontricks/data/scripts
creating build/bdist.linux-x86_64/wheel/protontricks/data/share
creating build/bdist.linux-x86_64/wheel/protontricks/data/share/applications
copying

Bug#1071810: pyfftw: FTBFS: /tmp/pyfftw-l6u29tyw/fftw_plan_dft.c:2:17: error: implicit declaration of function ‘fftw_plan_dft’


Package: src:pyfftw
Version: 0.13.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with sphinxdoc --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 pybuild:308: find -name "*.c" -delete
I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_pyfftw
* Building wheel...
:46: DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html
/<>/versioneer.py:421: SyntaxWarning: invalid escape sequence '\s'
  LONG_VERSION_PY['git'] = '''
INFO:root:running bdist_wheel
INFO:root:running build
INFO:root:running build_py
INFO:root:creating build
INFO:root:creating build/lib.linux-x86_64-cpython-312
INFO:root:creating build/lib.linux-x86_64-cpython-312/pyfftw
INFO:root:copying pyfftw/_version.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw
INFO:root:copying pyfftw/config.py -> build/lib.linux-x86_64-cpython-312/pyfftw
INFO:root:copying pyfftw/__init__.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw
INFO:root:creating build/lib.linux-x86_64-cpython-312/pyfftw/builders
INFO:root:copying pyfftw/builders/_utils.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/builders
INFO:root:copying pyfftw/builders/builders.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/builders
INFO:root:copying pyfftw/builders/__init__.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/builders
INFO:root:creating build/lib.linux-x86_64-cpython-312/pyfftw/interfaces
INFO:root:copying pyfftw/interfaces/_utils.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/interfaces
INFO:root:copying pyfftw/interfaces/cache.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/interfaces
INFO:root:copying pyfftw/interfaces/dask_fft.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/interfaces
INFO:root:copying pyfftw/interfaces/numpy_fft.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/interfaces
INFO:root:copying pyfftw/interfaces/scipy_fftpack.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/interfaces
INFO:root:copying pyfftw/interfaces/__init__.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/interfaces
INFO:root:copying pyfftw/interfaces/scipy_fft.py -> 
build/lib.linux-x86_64-cpython-312/pyfftw/interfaces
INFO:root:running build_ext
INFO:root:x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/<>/include -I/<>/pyfftw 
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include -I/usr/include -I/usr/include/python3.12 -c 
/tmp/pyfftw-em5b20w6/None.c -o /tmp/pyfftw-em5b20w6/None.o
INFO:root:x86_64-linux-gnu-gcc /tmp/pyfftw-em5b20w6/None.o -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu -lm -o /tmp/pyfftw-em5b20w6/a.out
INFO:root:x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/<>/include -I/<>/pyfftw 
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include -I/usr/include -I/usr/include/python3.12 -c 
/tmp/pyfftw-l6u29tyw/fftw_plan_dft.c -o /tmp/pyfftw-l6u29tyw/fftw_plan_dft.o
/tmp/pyfftw-l6u29tyw/fftw_plan_dft.c: In function ‘main’:
/tmp/pyfftw-l6u29tyw/fftw_plan_dft.c:2:17: error: implicit declaration of 
function ‘fftw_plan_dft’ [-Werror=implicit-function-declaration]
2 | fftw_plan_dft();
  | ^
cc1: some warnings being treated as errors
WARNING:__main__:Compilation error: command '/usr/bin/x86_64-linux-gnu-gcc' 
failed with exit code 1
INFO:root:x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/<>/include -I/<>/pyfftw 
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include -I/usr/include -I/usr/include/python3.12 -c 
/tmp/pyfftw-r_m1h4sa/fftwf_plan_dft.c -o /tmp/pyfftw-r_m1h4sa/fftwf_plan_dft.o
/tmp/pyfftw-r_m1h4sa/fftwf_plan_dft.c: In function ‘main’:
/tmp/pyfftw-r_m1h4sa/fftwf_plan_dft.c:2:17: error: implicit declaration of 
function ‘fftwf_plan_dft’ [-Werror=implicit-function-declaration]
2 |

Bug#1071807: prody: FTBFS: ModuleNotFoundError: No module named 'numpy.testing.decorators'


Package: src:prody
Version: 2.4.1+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --buildsystem pybuild --with numpy3,python3
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_prody/build/prody

[... snipped ...]

testPBCCoordArgumentSwitching 
(prody.tests.measure.test_contacts.TestNeighbors.testPBCCoordArgumentSwitching) 
... ok
testCenter (prody.tests.measure.test_measure.TestCenter.testCenter) ... ok
testCenterWithWeights 
(prody.tests.measure.test_measure.TestCenter.testCenterWithWeights) ... ok
testMultiCoordsets 
(prody.tests.measure.test_measure.TestCenter.testMultiCoordsets) ... ok
testMultiCoordsetsWithWeights 
(prody.tests.measure.test_measure.TestCenter.testMultiCoordsetsWithWeights) ... 
ok
testCTerPhi (prody.tests.measure.test_measure.TestDihedrals.testCTerPhi) ... ok
testCTerPsi (prody.tests.measure.test_measure.TestDihedrals.testCTerPsi) ... ok
testCalcPhi (prody.tests.measure.test_measure.TestDihedrals.testCalcPhi) ... ok
testCalcPsi (prody.tests.measure.test_measure.TestDihedrals.testCalcPsi) ... ok
testNTerPhi (prody.tests.measure.test_measure.TestDihedrals.testNTerPhi) ... ok
testNTerPsi (prody.tests.measure.test_measure.TestDihedrals.testNTerPsi) ... ok
testPBC (prody.tests.measure.test_measure.TestDistances.testPBC) ... ok
testPBCSymmetry 
(prody.tests.measure.test_measure.TestDistances.testPBCSymmetry) ... ok
testMSF (prody.tests.measure.test_measure.TestMSF.testMSF) ... 
/<>/.pybuild/cpython3_3.11_prody/build/prody/trajectory/dcdfile.py:273:
 DeprecationWarning: The binary mode of fromstring is deprecated, as it behaves 
surprisingly on unicode inputs. Use frombuffer instead
  xyz = fromstring(self._file.read(self._itemsize * n_floats),
/<>/.pybuild/cpython3_3.11_prody/build/prody/trajectory/dcdfile.py:320:
 DeprecationWarning: The binary mode of fromstring is deprecated, as it behaves 
surprisingly on unicode inputs. Use frombuffer instead
  data = fromstring(data, self._dtype)
/<>/.pybuild/cpython3_3.11_prody/build/prody/trajectory/dcdfile.py:294:
 DeprecationWarning: The binary mode of fromstring is deprecated, as it behaves 
surprisingly on unicode inputs. Use frombuffer instead
  unitcell = fromstring(self._file.read(48), dtype=np.float64)
ok
testMSFfloat (prody.tests.measure.test_measure.TestMSF.testMSFfloat) ... ok
testByArgument 
(prody.tests.measure.test_transform.TestMoveAtoms.testByArgument) ... ok
testToArgument 
(prody.tests.measure.test_transform.TestMoveAtoms.testToArgument) ... ok
testTransformation 
(prody.tests.measure.test_transform.TestMoveAtoms.testTransformation) ... ok
testWrap (prody.tests.measure.test_transform.TestWrapAtoms.testWrap) ... ok
prody.tests.proteins.test_ciffile 
(unittest.loader._FailedTest.prody.tests.proteins.test_ciffile) ... ERROR
prody.tests.proteins.test_dssp 
(unittest.loader._FailedTest.prody.tests.proteins.test_dssp) ... ERROR
testHeaderContent 
(prody.tests.proteins.test_header.TestParsePDBHeaderOnly.testHeaderContent) ... 
ok
testHeaderType 
(prody.tests.proteins.test_header.TestParsePDBHeaderOnly.testHeaderType) ... ok
prody.tests.proteins.test_localpdb 
(unittest.loader._FailedTest.prody.tests.proteins.test_localpdb) ... ERROR
prody.tests.proteins.test_pdbfile 
(unittest.loader._FailedTest.prody.tests.proteins.test_pdbfile) ... ERROR
prody.tests.proteins.test_wwpdb 
(unittest.loader._FailedTest.prody.tests.proteins.test_wwpdb) ... ERROR
testBuildMSAlocal 
(prody.tests.sequence.test_analysis.TestBuildMSA.testBuildMSAlocal) ... ok
testResidueCount 
(prody.tests.sequence.test_analysis.TestCalcMSAOccupancy.testResidueCount) ... 
ok
testResidueOccupancy 
(prody.tests.sequence.test_analysis.TestCalcMSAOccupancy.testResidueOccupancy) 
... ok
testSequenceCount 
(prody.tests.sequence.test_analysis.TestCalcMSAOccupancy.testSequenceCount) ... 
ok
testSequenceOccupancy 
(prody.tests.sequence.test_analysis.TestCalcMSAOccupancy.testSequenceOccupancy) 
... ok
testMATLAB (prody.tests.sequence.test_analysis.TestCalcMeff.testMATLAB) ... ok
testTwenty (prody.tests.sequence.test_analysis.TestCalcMeff.testTwenty) ... ok
testTwentyReversed 
(prody.tests.sequence.test_analysis.TestCalcMeff.testTwentyReversed) ... ok
testZero1 (prody.tests.sequence.test_analysis.TestCalcMeff.testZero1) ... ok
testZero2 (prody.tests.sequence.test_analysis.TestCalcMeff.testZero2) ... ok
testAmbiguity 
(prody.tests.sequence.test_analysis.TestCalcMutualInfo.testAmbiguity) ... ok
testAmbiguity2

Bug#1071806: powermock: FTBFS: core/src/main/java/org/powermock/core/ClassReplicaCreator.java:[99,36] incompatible types: java.lang.Class cannot be converted to java.lang.Class


Package: src:powermock
Version: 1.6.6-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
mh_patchpoms -plibpowermock-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar 
-Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
deprecated in JDK 13 and will likely be removed in a future release.
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO]
[INFO] powermock  [pom]
[INFO] powermock-reflect  [jar]
[INFO] powermock-core [jar]
[INFO] powermock-api  [pom]
[INFO] powermock-api-support  [jar]
[INFO] powermock-api-easymock [jar]
[INFO] powermock-api-mockito-common   [jar]
[INFO] powermock-api-mockito  [jar]
[INFO] powermock-modules  [pom]
[INFO] powermock-module-junit4-common [jar]
[INFO] powermock-module-junit4[jar]
[INFO] powermock-classloading-base[jar]
[INFO] powermock-module-junit4-rule   [jar]
[INFO] powermock-module-javaagent [jar]
[INFO] powermock-module-junit4-rule-agent [jar]
[INFO] powermock-module-testng-common [jar]
[INFO] powermock-module-testng[jar]
[INFO] powermock-module-testng-agent  [jar]
[INFO] powermock-modules-impl [pom]
[INFO] powermock-classloading-module  [pom]
[INFO] powermock-classloading-objenesis   [jar]
[INFO] powermock-classloading-xstream [jar]
[INFO]
[INFO] --< org.powermock:powermock >---
[INFO] Building powermock 1.6.6  [1/22]
[INFO] [ pom ]-
[INFO]
[INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ powermock ---
[WARNING] Ignoring project type pom - supportedProjectTypes = [jar, bundle]
[INFO]
[INFO] --< org.powermock:powermock-reflect >---
[INFO] Building powermock-reflect 1.6.6  [2/22]
[INFO] [ jar ]-
[WARNING] The artifact org.apache.maven.plugins:maven-resources-plugin:jar:2.6 
has been relocated to org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0
[INFO]
[INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ 
powermock-reflect ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, 
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory 
/<>/reflect/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ 
powermock-reflect ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
build is platform dependent!
[INFO] Compiling 27 source files to /<>/reflect/target/classes
Use of target 1.6 is no longer supported, switching to 7
Use of source 1.6 is no longer supported, switching to 7
[INFO] 
/<>/reflect/src/main/java/org/powermock/reflect/internal/WhiteboxImpl.java: 
/<>/reflect/src/main/java/org/powermock/reflect/internal/WhiteboxImpl.java 
uses or overrides a deprecated API.
[INFO] 
/<>/reflect/src/main/java/org/powermock/reflect/internal/WhiteboxImpl.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
/<>/reflect/src/main/java/org/powermock/reflect/internal/WhiteboxImpl.java:

Bug#1071805: pam-pgsql: FTBFS: src/backend_pgsql.c:282:44: error: implicit declaration of function ‘crypt’


Package: src:pam-pgsql
Version: 0.7.3.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --with autotools_dev
dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
dh: warning: The autotools-dev sequence is deprecated and replaced by dh in 
debhelper (>= 9.20160115)
dh: warning: This feature will be removed in compat 12.
   dh_update_autotools_config
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
   dh_autotools-dev_updateconfig
dh_autotools-dev_updateconfig: warning: Compatibility levels before 10 are 
deprecated (level 7 in use)
dh_autotools-dev_updateconfig: warning: dh_autotools-dev_updateconfig is 
deprecated; please see dh_autotools-dev_updateconfig(1) for a replacement
dh_autotools-dev_updateconfig: warning: This feature will be removed in compat 
12.
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
autoreconf -vfi
autoreconf: export WARNINGS=
autoreconf: Entering directory '.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf: configure.ac: not using Intltool
autoreconf: configure.ac: not using Gtkdoc
autoreconf: running: aclocal --force -I m4
autoreconf: running: /usr/bin/autoconf --force
configure.ac:21: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
./lib/autoconf/lang.m4:199: AC_LANG_CONFTEST is expanded from...
./lib/autoconf/general.m4:2894: _AC_LINK_IFELSE is expanded from...
./lib/autoconf/general.m4:2911: AC_LINK_IFELSE is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
m4/attributes.m4:87: CC_CHECK_LDFLAGS is expanded from...
m4/attributes.m4:104: CC_NOUNDEFINED is expanded from...
configure.ac:21: the top level
configure.ac:23: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
./lib/autoconf/lang.m4:199: AC_LANG_CONFTEST is expanded from...
./lib/autoconf/general.m4:2823: _AC_COMPILE_IFELSE is expanded from...
./lib/autoconf/general.m4:2839: AC_COMPILE_IFELSE is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
m4/attributes.m4:38: CC_CHECK_CFLAGS_SILENT is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
m4/attributes.m4:135: CC_CHECK_WERROR is expanded from...
m4/attributes.m4:144: CC_CHECK_ATTRIBUTE is expanded from...
m4/attributes.m4:186: CC_ATTRIBUTE_VISIBILITY is expanded from...
configure.ac:23: the top level
configure.ac:23: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
./lib/autoconf/lang.m4:199: AC_LANG_CONFTEST is expanded from...
./lib/autoconf/general.m4:2823: _AC_COMPILE_IFELSE is expanded from...
./lib/autoconf/general.m4:2839: AC_COMPILE_IFELSE is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
m4/attributes.m4:38: CC_CHECK_CFLAGS_SILENT is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
m4/attributes.m4:38: CC_CHECK_CFLAGS_SILENT is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
m4/attributes.m4:135: CC_CHECK_WERROR is expanded from...
m4/attributes.m4:144: CC_CHECK_ATTRIBUTE is expanded from...
m4/attributes.m4:186: CC_ATTRIBUTE_VISIBILITY is expanded from...
configure.ac:23: the top level
configure.ac:23: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
./lib/autoconf/lang.m4:199: AC_LANG_CONFTEST is expanded from...
./lib/autoconf/general.m4:2823:

Bug#1071804: ognibuild: FTBFS: ImportError: Failed to import test module: ognibuild.resolver


Package: src:ognibuild
Version: 0.0.18+git20230208.1.9b890a2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/clean.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/vcs.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/install.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/__main__.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/fix_build.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/test.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/logs.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/requirements.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/buildlog.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/fixers.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/buildsystem.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/dist_catcher.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/buildlog_converters.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/dist.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/dep_server.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/upstream.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/outputs.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/__init__.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/info.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
copying ognibuild/build.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
creating /<>/.pybuild/cpython3_3.12/build/ognibuild/debian
copying ognibuild/debian/upstream_deps.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/debian
copying ognibuild/debian/fix_build.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/debian
copying ognibuild/debian/apt.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/debian
copying ognibuild/debian/build_deps.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/debian
copying ognibuild/debian/file_search.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/debian
copying ognibuild/debian/udd.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/debian
copying ognibuild/debian/__init__.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/debian
copying ognibuild/debian/build.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/debian
creating /<>/.pybuild/cpython3_3.12/build/ognibuild/resolver
copying ognibuild/resolver/apt.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/resolver
copying ognibuild/resolver/dep_server.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/resolver
copying ognibuild/resolver/__init__.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/resolver
creating /<>/.pybuild/cpython3_3.12/build/ognibuild/session
copying ognibuild/session/plain.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/session
copying ognibuild/session/__init__.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/session
copying ognibuild/session/schroot.py -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild/session
copying ognibuild/py.typed -> 
/<>/.pybuild/cpython3_3.12/build/ognibuild
running build_scripts
creating build
creating build/scripts-3.12
copying and adjusting scripts/report-apt-deps-status -> build/scripts-3.12
changing mode of build/scripts-3.12/report-apt-deps-status from 644 to 755
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/clean.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/vcs.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/install.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/__main__.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/fix_build.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/test.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/logs.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/requirements.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/buildlog.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/fixers.py -> 
/<>/.pybuild/cpython3_3.11/build/ognibuild
copying ognibuild/buildsystem.py ->

Bug#1071802: node-puppeteer: FTBFS: src/node/BrowserFetcher.ts(572,13): error TS2314: Generic type 'HttpsProxyAgent' requires 1 type argument(s).


Package: src:node-puppeteer
Version: 13.4.1+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
Link ./node_modules/cross-fetch -> /usr/share/nodejs/cross-fetch
Link ./node_modules/pkg-dir -> /usr/share/nodejs/pkg-dir
Link ./node_modules/progress -> /usr/share/nodejs/progress
Link ./node_modules/proxy-from-env -> /usr/share/nodejs/proxy-from-env
Link ./node_modules/rimraf -> /usr/share/nodejs/rimraf
Link ./node_modules/ws -> /usr/share/nodejs/ws
Link ./node_modules/agent-base -> /usr/share/nodejs/agent-base
Link ./node_modules/yauzl -> /usr/share/nodejs/yauzl
Copy /usr/share/nodejs/extract-zip -> ./node_modules/
Copy /usr/share/nodejs/https-proxy-agent -> ./node_modules/
Link node_modules/devtools-protocol -> ../devtools-protocol
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
tsc -b src/tsconfig.cjs.json
src/node/BrowserFetcher.ts(572,13): error TS2314: Generic type 
'HttpsProxyAgent' requires 1 type argument(s).
src/node/BrowserFetcher.ts(596,12): error TS2314: Generic type 
'HttpsProxyAgentOptions' requires 1 type argument(s).
src/node/BrowserFetcher.ts(598,23): error TS2349: This expression is not 
callable.
  Type 'typeof 
import("/<>/node_modules/https-proxy-agent/dist/index")' has no 
call signatures.
src/node/install.ts(177,12): error TS2314: Generic type 
'HttpsProxyAgentOptions' requires 1 type argument(s).
src/node/install.ts(179,30): error TS2349: This expression is not callable.
  Type 'typeof 
import("/<>/node_modules/https-proxy-agent/dist/index")' has no 
call signatures.
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

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

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

Thanks.

Bug#1071803: node-solid-keychain: FTBFS: Exception during run: Error: Cannot find module '@trust/webcrypto'


Package: src:node-solid-keychain
Version: 0.1.3-3.1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pandoc --from gfm-raw_html --to html --standalone --output README.html README.md
[WARNING] This document format requires a nonempty  element.
  Defaulting to 'README' as the title.
  To specify a title, use 'title' in metadata or --metadata title="...".
pandoc --from gfm-raw_html --to plain --output README.txt README.md
dh override_dh_auto_build
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
NODE_ENV=test prove \
--exec "mocha --reporter=tap" \
test/NotSupportedErrorSpec.js test/RsaKeyPairSpec.js 
test/SupportedAlgorithmsSpec.js \

test/NotSupportedErrorSpec.js  ok

 Exception during run: Error: Cannot find module '@trust/webcrypto'
Require stack:
- /<>/src/algorithms/RsaKeyPair.js
- /<>/test/RsaKeyPairSpec.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1145:15)
at Module._load (node:internal/modules/cjs/loader:986:27)
at Module.require (node:internal/modules/cjs/loader:1233:19)
at require (node:internal/modules/helpers:179:18)
at Object. (/<>/src/algorithms/RsaKeyPair.js:4:16)
at Module._compile (node:internal/modules/cjs/loader:1358:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
at Module.load (node:internal/modules/cjs/loader:1208:32)
at Module._load (node:internal/modules/cjs/loader:1024:12)
at Module.require (node:internal/modules/cjs/loader:1233:19)
at require (node:internal/modules/helpers:179:18)
at Object. (/<>/test/RsaKeyPairSpec.js:17:20)
at Module._compile (node:internal/modules/cjs/loader:1358:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
at Module.load (node:internal/modules/cjs/loader:1208:32)
at Module._load (node:internal/modules/cjs/loader:1024:12)
at cjsLoader (node:internal/modules/esm/translators:348:17)
at ModuleWrap. (node:internal/modules/esm/translators:297:7)
at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
at async formattedImport 
(/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:9:14)
at async exports.requireOrImport 
(/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:42:28)
at async exports.loadFilesAsync 
(/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:100:20)
at async singleRun (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:125:3)
at async exports.handler (/usr/share/nodejs/mocha/lib/cli/run.js:370:5) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
'/<>/src/algorithms/RsaKeyPair.js',
'/<>/test/RsaKeyPairSpec.js'
  ]
}
test/RsaKeyPairSpec.js ...
Dubious, test returned 1 (wstat 256, 0x100)
No subtests run
test/SupportedAlgorithmsSpec.js .. ok

Test Summary Report
---
test/RsaKeyPairSpec.js (Wstat: 256 (exited 1) Tests: 0 Failed: 0)
  Non-zero exit status: 1
  Parse errors: No plan found in TAP output
Files=3, Tests=5,  1 wallclock secs ( 0.02 usr  0.01 sys +  0.97 cusr  0.13 
csys =  1.13 CPU)
Result: FAIL
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:34: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

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

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

Thanks.

Bug#1071800: mdanalysis: FTBFS: MDAnalysis/lib/src/transformations/transformations.c:2122:35: error: implicit declaration of function ‘PyUnicode_GetSize’


Package: src:mdanalysis
Version: 2.5.0+dfsg1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --with python3,sphinxdoc --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.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_mdanalysis
* Building wheel...
performance hint: MDAnalysis/lib/c_distances.pyx:301:5: Exception check on 
'_minimum_image_orthogonal' will always require the GIL to be acquired.
Possible solutions:
1. Declare '_minimum_image_orthogonal' as 'noexcept' if you control the 
definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on '_minimum_image_orthogonal' to allow an 
error code to be returned.
performance hint: MDAnalysis/lib/c_distances.pyx:328:5: Exception check on 
'_minimum_image_triclinic' will always require the GIL to be acquired.

[... snipped ...]

copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/contacts.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
creating build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/data
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/data/filenames.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/data
copying 
build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/data/janin_ref_data.npy 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/data
copying 
build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/data/rama_ref_data.npy 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/data
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/data/__init__.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/data
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/polymer.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/waterdynamics.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/lineardensity.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/atomicdistances.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/align.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/rms.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/bat.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/nucleicacids.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
creating build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/hydrogenbonds
copying 
build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/hydrogenbonds/hbond_analysis.py
 -> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/hydrogenbonds
copying 
build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/hydrogenbonds/hbond_autocorrel.py
 -> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/hydrogenbonds
copying 
build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/hydrogenbonds/__init__.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/hydrogenbonds
copying 
build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/hydrogenbonds/wbridge_analysis.py
 -> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/hydrogenbonds
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/diffusionmap.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
creating build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/legacy
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/legacy/x3dna.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/legacy
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/legacy/__init__.py 
-> build/bdist.linux-x86_64/wheel/MDAnalysis/analysis/legacy
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/gnm.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/msd.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/leaflet.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/density.py -> 
build/bdist.linux-x86_64/wheel/MDAnalysis/analysis
copying build/lib.linux-x86_64-cpython-311/MDAnalysis/analysis/psa.py ->

Bug#1071801: myhdl: FTBFS: There is a syntax error in your configuration file: (unicode error) 'unicodeescape' codec can't decode bytes in position 0-1: truncated uXXXX escape (conf.py, line 189)


Package: src:myhdl
Version: 0.11-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_simulator.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_join.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_intbv.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_resolverefs.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_misc.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_always.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_getcellvars.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_enum.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_tristate.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_modbv.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_getHierarchy.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_Cosimulation.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_delay.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_util.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_traceSignals.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_always_seq.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_instance.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_always_comb.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_ShadowSignal.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_bin.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_Simulation.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_Signal.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_compat.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/debug.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_extractHierarchy.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_Waiter.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/__init__.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_visitors.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_concat.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
copying myhdl/_block.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl
creating /<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
copying myhdl/conversion/_analyze.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
copying myhdl/conversion/_misc.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
copying myhdl/conversion/_toVHDL.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
copying myhdl/conversion/_toVHDLPackage.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
copying myhdl/conversion/_VHDLNameValidation.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
copying myhdl/conversion/_toVerilog.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
copying myhdl/conversion/_verify.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
copying myhdl/conversion/__init__.py -> 
/<>/.pybuild/cpython3_3.12_myhdl/build/myhdl/conversion
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_simulator.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_join.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_intbv.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_resolverefs.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_misc.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_always.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_getcellvars.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_enum.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_tristate.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_modbv.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_getHierarchy.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying myhdl/_Cosimulation.py -> 
/<>/.pybuild/cpython3_3.11_myhdl/build/myhdl
copying

Bug#1071798: maradns: FTBFS: dh_install: warning: Compatibility levels before 10 are deprecated (level 9 in use)


Package: src:maradns
Version: 2.0.13-1.6
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
make: 'build' is up to date.
 fakeroot debian/rules binary
dh binary --with python3
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
System: Linux
Version: 2.0.13
Makefile: build/Makefile.linux
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp  /<>/deadwood-*/src/DwRandPrime.h 
/<>/debian/DwRandPrime.h
cp rng/rng-32bit-tables.h rng/rng-32bit-tables.h.bak
make -f build/Makefile.linux all COMPILED=\""Linux system at Sat, 09 Dec 2023 17:16:39 
+0100"\" VERSION=\"2.0.13\"
make[2]: Entering directory '/<>'
cd libs ; make "CC=cc `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM -DIPV6 
`dpkg-buildflags --get CPPFLAGS` `dpkg-buildflags --get LDFLAGS`" ; cd ../dns ; make 
"CC=cc `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM -DIPV6 `dpkg-buildflags --get 
CPPFLAGS` `dpkg-buildflags --get LDFLAGS`" ; \
cd ../rng ; make "CC=cc `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM -DIPV6 
`dpkg-buildflags --get CPPFLAGS` `dpkg-buildflags --get LDFLAGS`" ; cd ../parse ; make 
"CC=cc `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM -DIPV6 `dpkg-buildflags --get 
CPPFLAGS` `dpkg-buildflags --get LDFLAGS`" ; \
cd ../qual ; make "CC=cc `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM 
-DIPV6 `dpkg-buildflags --get CPPFLAGS` `dpkg-buildflags --get LDFLAGS`" ; cd 
../server ; \
make "CC=cc `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM -DIPV6 `dpkg-buildflags --get CPPFLAGS` `dpkg-buildflags 
--get LDFLAGS`" "VERSION="2.0.13"" COMPILED=\""Linux system at Sat, 09 Dec 2023 17:16:39 
+0100"\" ; \
cd ../tools ; make "CC=cc `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM 
-DIPV6 `dpkg-buildflags --get CPPFLAGS` `dpkg-buildflags --get LDFLAGS`" ; \
echo "FLAGS: `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM -DIPV6 
`dpkg-buildflags --get CPPFLAGS` `dpkg-buildflags --get LDFLAGS`"; \
cd ../deadwood-*/src/ ; make FLAGS="`dpkg-buildflags --get CFLAGS` -Wall 
-DSELECT_PROBLEM -DIPV6 `dpkg-buildflags --get CPPFLAGS` `dpkg-buildflags --get 
LDFLAGS`"; \
cd ../../tcp ; make "CC=cc `dpkg-buildflags --get CFLAGS` -Wall -DSELECT_PROBLEM -DIPV6 `dpkg-buildflags 
--get CPPFLAGS` `dpkg-buildflags --get LDFLAGS`" "VERSION="2.0.13"" ; cat 
../00README.FIRST
make[3]: Entering directory '/<>/libs'
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/libs=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DSELECT_PROBLEM -DIPV6 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -c  -o JsStr.o JsStr.c
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/libs=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DSELECT_PROBLEM -DIPV6 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -c  -o JsStrOS.o 
JsStrOS.c
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/libs=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DSELECT_PROBLEM -DIPV6 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -c  -o JsStrCP.o 
JsStrCP.c
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/libs=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DSELECT_PROBLEM -DIPV6 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -c  -o MaraHash.o 
MaraHash.c
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/libs=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DSELECT_PROBLEM -DIPV6 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro  -o tests tests.c 
JsStr.o JsStrOS.o JsStrCP.o MaraHash.o
tests.c: In function ‘main’:
tests.c:81:15: warning: variable ‘nowarn’ set but not used 
[-Wunused-but-set-variable]
   81 | char *nowarn;
  |   ^~
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/libs=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall 
-DSELECT_PROBLEM -DIPV6 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro  -o mtest mtest.c 
JsStr.o JsStrOS.o JsStrCP.o MaraHash.o
mtest.c: In function ‘main’:
mtest.c:19:11: warning: variable ‘nowarn’ set but not used 
[-Wunused-but-set-variable]
   19 | char *nowarn;
  |   ^~
make[3]: Leaving directory '/<>/libs'
make[3]: Entering directory '/<>/dns'
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/dns=. -fstack-protector-strong

Bug#1071799: matrix-sydent: FTBFS: ModuleNotFoundError: No module named 'typing_extensions'


Package: src:matrix-sydent
Version: 2.5.1-1.1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent
copying sydent/types.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent
copying sydent/sydent.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent
copying sydent/__init__.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent
creating /<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_util.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_auth.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_invites.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_email.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_replication.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_casefold_migration.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_threepidunbind.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_register.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_blacklisting.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/utils.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_start.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_jinja_templates.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_msisdn.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/test_store_invite.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
copying tests/__init__.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/tests
creating 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/matrix_is_test
copying matrix_is_test/launcher.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/matrix_is_test
copying matrix_is_test/__init__.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/matrix_is_test
creating 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/validators
copying sydent/validators/emailvalidator.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/validators
copying sydent/validators/common.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/validators
copying sydent/validators/msisdnvalidator.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/validators
copying sydent/validators/__init__.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/validators
creating /<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/sms
copying sydent/sms/types.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/sms
copying sydent/sms/openmarket.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/sms
copying sydent/sms/__init__.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/sms
creating 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/users
copying sydent/users/tokens.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/users
copying sydent/users/accounts.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/users
copying sydent/users/__init__.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/users
creating /<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/threepid_associations.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/hashing_metadata.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/terms.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/peers.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/invite_tokens.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/accounts.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/sqlitedb.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/valsession.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
copying sydent/db/__init__.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/db
creating 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/terms
copying sydent/terms/terms.py -> 
/<>/.pybuild/cpython3_3.12_matrix-sydent/build/sydent/terms
copying

Bug#1071797: jodd: FTBFS: Could not resolve all files for configuration ':jodd-log:compileClasspath'.


Package: src:jodd
Version: 3.8.6-1.1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --buildsystem=gradle --with maven-repo-helper
   dh_update_autotools_config -O--buildsystem=gradle
   dh_autoreconf -O--buildsystem=gradle
   dh_auto_configure -O--buildsystem=gradle
   dh_auto_build -O--buildsystem=gradle
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=jodd -Dfile.encoding=UTF-8 --parallel 
--max-workers=2 jar
openjdk version "17.0.11" 2024-04-16
OpenJDK Runtime Environment (build 17.0.11+9-Debian-1)
OpenJDK 64-Bit Server VM (build 17.0.11+9-Debian-1, mixed mode, sharing)
Initialized native services in: /<>/.gradle/native
To honour the JVM settings for this build a new JVM will be forked. Please 
consider using the daemon: 
https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
Starting process 'Gradle build daemon'. Working directory: 
/<>/.gradle/daemon/4.4.1 Command: 
/usr/lib/jvm/java-17-openjdk-amd64/bin/java --add-opens java.base/java.lang=ALL-UNNAMED 
-Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
 -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp 
/usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
Successfully started process 'Gradle build daemon'
An attempt to start the daemon took 0.801 secs.
The client will now receive all logging from the daemon (pid: 18915). The daemon log file: 
/<>/.gradle/daemon/4.4.1/daemon-18915.out.log
Daemon will be stopped at the end of the build stopping after processing
Closing daemon's stdin at end of input.
The daemon will no longer process any standard input.
Using 2 worker leases.
Creating new cache for fileHashes, path 
/<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
org.gradle.cache.internal.DefaultCacheAccess@17efbc7
Creating new cache for resourceHashesCache, path 
/<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
access org.gradle.cache.internal.DefaultCacheAccess@17efbc7
Creating new cache for fileHashes, path 
/<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
org.gradle.cache.internal.DefaultCacheAccess@4d51ad05
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.
Creating new cache for metadata-1.1/results, path 
/<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
org.gradle.cache.internal.DefaultCacheAccess@5a1f7b77
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using BuildScriptTransformer.
Generating JAR file: 
/<>/.gradle/caches/4.4.1/generated-gradle-jars/gradle-api-4.4.1.jar
Generating JAR file 'gradle-api-4.4.1.jar'
Keep-alive timer started
Adding Debian repository to project 'buildSrc'
Parallel execution is an incubating feature.
Evaluating project ':buildSrc' using build file 
'/<>/buildSrc/build.gradle'.
Compiling build file '/<>/buildSrc/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/buildSrc/build.gradle' using 
BuildScriptTransformer.
Adding Maven pom generation to project 'buildSrc'
Linking the generated javadoc to the system JDK API documentation
Creating new cache for metadata-2.36/module-metadata, path 
/<>/.gradle/caches/modules-2/metadata-2.36/module-metadata.bin, 
access org.gradle.cache.internal.DefaultCacheAccess@465b0002
Loading the Maven rules...
Replacing org.codehaus.groovy:groovy-all:jar:2.4.10  ->  
org.codehaus.groovy:groovy-all:jar:debian
Replacing org.yaml:snakeyaml:jar:1.13  ->  org.yaml:snakeyaml:jar:1.x
Ignoring org.codehaus.groovy.modules.http-builder:http-builder:jar:0.7.1
Replacing org.apache.httpcomponents:httpmime:jar:4.3  ->  
org.apache.httpcomponents:httpmime:jar:debian
Passing through 
org.apache.httpcomponents:httpcomponents-client:jar:debian
Passing through org.apache.httpcomponents:httpclient:jar:debian
Passing through org.apache.httpcomponents:httpcore:jar:debian
Passing through org.apache.httpcomponents:httpcomponents-core:jar:debian
Passing through commons-logging:commons-logging:jar:debian
Passing through org.apache.commons:commons-parent:jar:debian
Passing through org.apache:apache:jar:debian
Passing through commons-codec:commons-codec:jar:debian
Selected primary task 'clean' from project :
Selected primary task 'build' from project :
Creating new cache for annotation-processors, path 
/<>/buildSrc/.gradle/4.4.1/fileContent/annotation-processors.bin, 
access

Bug#1071795: fava: FTBFS: help2man: can't get `--help' info from PYTHONPATH="/<>/src" python3 -m fava.cli


Package: src:fava
Version: 1.23.1+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_fava
* Building wheel...
running bdist_wheel
running build
running build_py

[... snipped ...]

You can read more about "package data files" on setuptools 
documentation page:

- https://setuptools.pypa.io/en/latest/userguide/datafiles.html


[^1]: For Python, any directory (with suitable naming) can be imported,
  even if it does not contain any `.py` files.
  On the other hand, currently there is no concept of package data
  directory, all directories are treated like packages.



!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: 
Package 'fava.translations.zh.LC_MESSAGES' is absent from the `packages` 
configuration.
!!




# Package would be ignored #

Python recognizes 'fava.translations.zh.LC_MESSAGES' 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 'fava.translations.zh.LC_MESSAGES' 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 'fava.translations.zh.LC_MESSAGES' to be distributed 
and are
already explicitly excluding 'fava.translations.zh.LC_MESSAGES' 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 
documentation page:

- https://setuptools.pypa.io/en/latest/userguide/datafiles.html


[^1]: For Python, any directory (with suitable naming) can be imported,
  even if it does not contain any `.py` files.
  On the other hand, currently there is no concept of package data
  directory, all directories are treated like packages.



!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: 
Package 'fava.translations.zh_Hant_TW.LC_MESSAGES' is absent from the 
`packages` configuration.
!!




# Package would be ignored #

Python recognizes 'fava.translations.zh_Hant_TW.LC_MESSAGES' 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 
'fava.translations.zh_Hant_TW.LC_MESSAGES' 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 'fava.translations.zh_Hant_TW.LC_MESSAGES' to be 
distributed and are
already explicitly excluding 'fava.translations.zh_Hant_TW.LC_MESSAGES' 
via
`find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
you can try to use

Bug#1071796: jajuk: FTBFS: src/main/java/org/jajuk/ui/helpers/PlaylistRepositoryTableModel.java:101: error: is not abstract and does not


Package: src:jajuk
Version: 1:1.10.9+dfsg2-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --buildsystem=ant
   dh_update_autotools_config -O--buildsystem=ant
   dh_autoreconf -O--buildsystem=ant
   dh_auto_configure -O--buildsystem=ant
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- -f build_enduser.xml package_jar  -Dbuild.time='Wed, 29 Nov 
2017 13:09:42 +0100'
ant -propertyfile ./debian/ant.properties -Duser.name debian -f build_enduser.xml 
package_jar "-Dbuild.time=Wed, 29 Nov 2017 13:09:42 +0100"
Buildfile: /<>/build_enduser.xml

clean:
[mkdir] Created dir: /<>/bin
[mkdir] Created dir: /<>/test-reports

compile:
 [echo] Compile the code
[javac] /<>/build_enduser.xml:23: warning: 'includeantruntime' 
was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 448 source files to /<>/bin
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 7
[javac] warning: [options] source value 7 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 7 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/<>/src/main/java/org/jajuk/ui/helpers/PlaylistRepositoryTableModel.java:101:
 error:  is not abstract and 
does not override abstract method test(Playlist) in Predicate
[javac]   alToShow = new ArrayList(Collections2.filter(alToShow, 
new Predicate() {
[javac] 
 ^
[javac] 
/<>/src/main/java/org/jajuk/ui/helpers/PlaylistRepositoryTableModel.java:110:
 error:  is not abstract and 
does not override abstract method test(Playlist) in Predicate
[javac]   alToShow = new ArrayList(Collections2.filter(alToShow, 
new Predicate() {
[javac] 
 ^
[javac] 
/<>/src/main/java/org/jajuk/ui/helpers/PlaylistRepositoryTableModel.java:118:
 error:  is not abstract and 
does not override abstract method test(Playlist) in Predicate
[javac]   alToShow = new ArrayList(Collections2.filter(alToShow, 
new Predicate() {
[javac] 
 ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 3 errors
[javac] 4 warnings

BUILD FAILED
/<>/build_enduser.xml:23: Compile failed; see the compiler error 
output for details.

Total time: 7 seconds
dh_auto_build: error: ant -propertyfile ./debian/ant.properties -Duser.name debian -f 
build_enduser.xml package_jar "-Dbuild.time=Wed, 29 Nov 2017 13:09:42 +0100" 
returned exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

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

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

Thanks.

Bug#1071794: dcmstack: FTBFS: AttributeError: 'TestDcmstackCli' object has no attribute 'out_dir'


Package: src:dcmstack
Version: 0.9-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
pybuild --configure -i python{version} -p "3.12 3.11"
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
pybuild --build -i python{version} -p "3.12 3.11"
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
copying src/dcmstack/extract.py -> 
/<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
copying src/dcmstack/dcmstack.py -> 
/<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
copying src/dcmstack/utils.py -> 
/<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
copying src/dcmstack/nitool_cli.py -> 
/<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
copying src/dcmstack/dcmmeta.py -> 
/<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
copying src/dcmstack/dcmstack_cli.py -> 
/<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
copying src/dcmstack/__init__.py -> 
/<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
copying src/dcmstack/info.py -> 
/<>/.pybuild/cpython3_3.12_dcmstack/build/dcmstack
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
copying src/dcmstack/extract.py -> 
/<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
copying src/dcmstack/dcmstack.py -> 
/<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
copying src/dcmstack/utils.py -> 
/<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
copying src/dcmstack/nitool_cli.py -> 
/<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
copying src/dcmstack/dcmmeta.py -> 
/<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
copying src/dcmstack/dcmstack_cli.py -> 
/<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
copying src/dcmstack/__init__.py -> 
/<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
copying src/dcmstack/info.py -> 
/<>/.pybuild/cpython3_3.11_dcmstack/build/dcmstack
   dh_auto_test -O--buildsystem=pybuild
pybuild --test --test-pytest -i python{version} -p "3.12 3.11"
I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_dcmstack/build; 
python3.12 -m pytest test
= test session starts ==
platform linux -- Python 3.12.3, pytest-8.1.2, pluggy-1.5.0
rootdir: /<>
collected 131 items

test/test_cli.py FFF [  2%]
test/test_dcmmeta.py ... [ 41%]
...  [ 58%]
test/test_dcmstack.py .  [ 93%]
test/test_extract.py .   [100%]

=== FAILURES ===
__ TestDcmstackCli.test_basic __

self = 

def test_basic(self):

  nii_paths = make_niftis(self.out_dir)

E   AttributeError: 'TestDcmstackCli' object has no attribute 'out_dir'

test/test_cli.py:55: AttributeError
__ TestDcmstackCli.test_embed __

self = 

def test_embed(self):

  nii_paths = make_niftis(self.out_dir, ['--embed'])

E   AttributeError: 'TestDcmstackCli' object has no attribute 'out_dir'

test/test_cli.py:59: AttributeError
___ TestNitoolCli.test_basic ___

self = 

def test_basic(self):

  nii_path = make_niftis(self.out_dir, ['--embed'])[0]

E   AttributeError: 'TestNitoolCli' object has no attribute 'out_dir'

test/test_cli.py:65: AttributeError
=== warnings summary ===
.pybuild/cpython3_3.12_dcmstack/build/test/test_dcmstack.py::TestToNifti::test_single_vol
.pybuild/cpython3_3.12_dcmstack/build/test/test_dcmstack.py::TestToNifti::test_slice_dim_reorient
.pybuild/cpython3_3.12_dcmstack/build/test/test_dcmstack.py::TestToNifti::test_two_time_vol
.pybuild/cpython3_3.12_dcmstack/build/test/test_dcmstack.py::TestToNifti::test_two_vector_vol
  /usr/lib/python3/dist-packages/nibabel/nifti1.py:1646: UserWarning: Multiple 
slice orders satisfy: sequential decreasing, alternating decreasing, 
alternating increasing 2. Choosing the first one
warnings.warn(

.pybuild/cpython3_3.12_dcmstack/build/test/test_dcmstack.py::test_fsl_hack
.pybuild/cpython3_3.12_dcmstack/build/test/test_dcmstack.py::test_pix_overflow

Bug#1071793: cider: FTBFS: Eager macro-expansion failure: (buttercup-dynamic-binding-error . "buttercup requires `lexical-binding' to be t"


Package: src:cider
Version: 0.19.0+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --with elpa --with mkdocs
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
LANG=C.UTF-8 LC_ALL=C.UTF-8 mkdocs build --clean
WARNING -  Config value 'site_favicon': Unrecognised configuration name: 
site_favicon
INFO-  Cleaning site directory
INFO-  Building documentation to directory: /<>/html
WARNING -  Doc file 'about/contributing.md' contains a relative link 
'readthedocs.org', but the target 'about/readthedocs.org' is not found among 
documentation files.
INFO-  Documentation built in 0.31 seconds
make[1]: Leaving directory '/<>'
   dh_elpa_test
buttercup -L . -L test/utils
Loading /etc/emacs/site-start.d/00debian.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
cider-popup.el: Warning: Use keywords rather than deprecated positional 
arguments to `define-minor-mode'
nrepl-client.el: Warning: Use keywords rather than deprecated positional 
arguments to `define-minor-mode'
Interactive forms not supported in generic functions: (interactive "P")
cider-test.el: Warning: Use keywords rather than deprecated positional 
arguments to `define-minor-mode'
cider-mode.el: Warning: Missing format argument
cider-mode.el: Warning: Use keywords rather than deprecated positional 
arguments to `define-minor-mode'
cider-debug.el: Warning: Use keywords rather than deprecated positional 
arguments to `define-minor-mode'
cider-test.el: Warning: Use keywords rather than deprecated positional 
arguments to `define-minor-mode'
Running 38 specs.

cider--test-unless-local
  returns the given argument if text at point is not a clojure local
[32m  returns the given argument if text at point is not a clojure local[0m 
(3.08ms)

cider--read-locals-from-next-sexp
  respects cursor position
[32m  respects cursor position[0m (0.23ms)
  understands clojure destructuring
[32m  understands clojure destructuring[0m (0.22ms)
  handles clojure type-hints
[32m  handles clojure type-hints[0m (0.21ms)

cider--read-locals-from-bindings-vector
  understands clojure destructuring
[32m  understands clojure destructuring[0m (0.43ms)
  handles clojure type-hints
[32m  handles clojure type-hints[0m (0.28ms)
  handles newlines
[32m  handles newlines[0m (0.30ms)

cider--read-locals-from-arglist
  handles whitespace
[32m  handles whitespace[0m (0.26ms)
  handles clojure docstrings, meta-data, type-hints
[32m  handles clojure docstrings, meta-data, type-hints[0m (0.25ms)
  understands clojure destructuring
[32m  understands clojure destructuring[0m (0.36ms)
  understands clojure multi-arity functons
[32m  understands clojure multi-arity functons[0m (0.24ms)
  understands lambda functions
[32m  understands lambda functions[0m (0.23ms)

cider--make-result-overlay
  can create overlays
[32m  can create overlays[0m (0.13ms)
  when overlay duration is `command`
erases overlays after the next command is executed
[32merases overlays after the next command is executed[0m (0.19ms)
  when overlay duration is given in secs
erases overlays after that duration
[32merases overlays after that duration[0m (2.00s)

cider--delete-overlay
  deletes overlays
[32m  deletes overlays[0m (0.19ms)

File failed to load correctly:
  ./test/cider-apropos-tests.el
[31m  ./test/cider-apropos-tests.el[0m[31m  Eager macro-expansion failure: 
(buttercup-dynamic-binding-error . "buttercup requires `lexical-binding' to be 
t")[0m (0.04ms)
  ./test/cider-browse-ns-tests.el
[31m  ./test/cider-browse-ns-tests.el[0m[31m  Eager macro-expansion failure: 
(buttercup-dynamic-binding-error . "buttercup requires `lexical-binding' to be 
t")[0m (0.04ms)
  ./test/cider-classpath-tests.el
[31m  ./test/cider-classpath-tests.el[0m[31m  Eager macro-expansion failure: 
(buttercup-dynamic-binding-error . "buttercup requires `lexical-binding' to be 
t")[0m (0.04ms)
  ./test/cider-client-tests.el
[31m  ./test/cider-client-tests.el[0m[31m  Eager macro-expansion failure: 
(buttercup-dynamic-binding-error . "buttercup requires `lexical-binding' to be 
t")[0m (0.03ms)
  ./test/cider-common-tests.el
[31m  ./test/cider-common-tests.el[0m[31m  Eager macro-expansion failure: 
(buttercup-dynamic-binding-error . "buttercup requires `lexical-binding' to be 
t")[0m (0.03ms)
  ./test/cider-connection-tests.el
[31m  ./test/cider-connection-tests.el[0m[31m  Eager macro-expansion 
failure: (wrong-number-of-arguments (3 . 4) 2)[0m (0.03ms)
  ./test/cider-debug-tests.el
[31m  ./test/cider-debug-tests.el[0m[31m  Eager macro-expansion failure: 
(buttercup-dynamic-binding-error . "buttercup requires `lexical-binding' to be 
t")[0m (0.02ms)

Bug#1071792: check-all-the-things: FTBFS: /bin/sh: 1: register-python-argcomplete3: not found


Package: src:check-all-the-things
Version: 2017.05.20+nmu1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --parallel --with bash-completion
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config -O--parallel
   dh_auto_configure -O--parallel
dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
(level 9 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
help2man \
--version-string=2017.05.20+nmu1 \
--no-info \
--name="Check all of the things!" \
./check-all-the-things \
> check-all-the-things.1
register-python-argcomplete3 check-all-the-things > 
debian/check-all-the-things.bash-completion
/bin/sh: 1: register-python-argcomplete3: not found
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 127
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

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

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

Thanks.

Bug#1071791: bing: FTBFS: bing_probes.c:259:17: error: implicit declaration of function ‘memcpy’


Package: src:bing
Version: 1.3.5-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with autoreconf
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   dh_auto_build
make -j2 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time 
-D_FORTIFY_SOURCE=2 -I.   -g -Wall -D_DEBUG -o bing.o -c bing.c
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time 
-D_FORTIFY_SOURCE=2 -I.   -g -Wall -D_DEBUG -o bing_misc.o -c bing_misc.c
bing.c:186:27: warning: missing braces around initializer [-Wmissing-braces]
  186 | struct sockaddr addr_none={PF_INET,0,0};
  |   ^
  |{  }
cc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time 
-D_FORTIFY_SOURCE=2 -I.   -g -Wall -D_DEBUG -o bing_probes.o -c bing_probes.c
bing.c: In function ‘main’:
bing.c:1422:5: warning: ignoring return value of ‘setgid’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
 1422 | setgid(getgid());
  | ^~~~
bing.c:1423:5: warning: ignoring return value of ‘setuid’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
 1423 | setuid(getuid());
  | ^~~~
bing.c: At top level:
bing.c:98:13: warning: ‘rcsid’ defined but not used [-Wunused-variable]
   98 | static char rcsid[] = "$Id: bing.c,v 1.12 1999/10/24 22:45:03 fgouget Exp 
$";
  | ^
bing_probes.c: In function ‘generate_data’:
bing_probes.c:259:17: error: implicit declaration of function ‘memcpy’ 
[-Werror=implicit-function-declaration]
  259 | memcpy(packet_data+i,state->pattern,
  | ^~
bing_probes.c:31:1: note: include ‘’ or provide a declaration of 
‘memcpy’
   30 | #include "mod_icmp.h"
  +++ |+#include 
   31 |
bing_probes.c:259:17: warning: incompatible implicit declaration of built-in 
function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
  259 | memcpy(packet_data+i,state->pattern,
  | ^~
bing_probes.c:259:17: note: include ‘’ or provide a declaration of 
‘memcpy’
bing_probes.c: In function ‘probe_set_option’:
bing_probes.c:370:9: warning: incompatible implicit declaration of built-in 
function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
  370 | memcpy(state->pattern,(char*)optval,state->pattern_size);
  | ^~
bing_probes.c:370:9: note: include ‘’ or provide a declaration of 
‘memcpy’
bing_probes.c:381:40: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  381 | handle2state(handle)->udp_port=(int)optval;
  |^
bing_probes.c: In function ‘do_probe’:
bing_probes.c:472:17: warning: incompatible implicit declaration of built-in 
function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
  472 | memcpy(&((struct 
sockaddr_in*)(>dst_addr))->sin_addr,>ip_dst,4);
  | ^~
bing_probes.c:472:17: note: include ‘’ or provide a declaration of 
‘memcpy’
cc1: some warnings being treated as errors
make[1]: *** [Makefile:112: bing_probes.o] Error 1
make[1]: *** Waiting for unfinished jobs
bing.c: In function ‘traceroute’:
bing.c:701:16: warning: ‘probe_res’ may be used uninitialized 
[-Wmaybe-uninitialized]
  701 | if (probe_res!=BP_RES_TIMEOUT) {
  |^
bing.c:605:9: note: ‘probe_res’ was declared here
  605 | int probe_res;
  | ^
bing.c: In function ‘print_host_statistics’:
bing.c:1205:8: warning: ‘corr’ may be used uninitialized [-Wmaybe-uninitialized]
 1205 | if (corr==0.0) {
  |^
bing.c:1174:12: note: ‘corr’ was declared here
 1174 | double corr;
  |^~~~
bing.c: In function ‘main’:
bing.c:1604:29: warning: ‘c1’ may be used uninitialized [-Wmaybe-uninitialized]
 1604 | printf("%c%7.3f%c ",c1,rtt,c2);
  | ^~
bing.c:1580:34: note: ‘c1’ was declared here
 1580 | char c1,c2;
  |  ^~
bing.c:1604:29: warning: ‘c2’ may be used uninitialized [-Wmaybe-uninitialized]
 1604 | printf("%c%7.3f%c ",c1,rtt,c2);
  | ^~
bing.c:1580:37: note:

Bug#1065966: marked as done (gsocket: FTBFS on arm{el,hf}: /tmp/ccmyiWuJ.s:4004: Error: symbol `__lstat64_time64' is already defined)

Your message dated Sat, 25 May 2024 00:11:32 +
with message-id 
and subject line Bug#1065966: fixed in gsocket 1.4.43-1
has caused the Debian Bug report #1065966,
regarding gsocket: FTBFS on arm{el,hf}: /tmp/ccmyiWuJ.s:4004: Error: symbol 
`__lstat64_time64' is already defined
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.)


-- 
1065966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsocket
Version: 1.4.41-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=gsocket=armhf=1.4.41-1%2Bb1=1709989725=0

gcc -DHAVE_CONFIG_H -I. -I..   -I./../include  -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -shared 
-fPIC -O2 -Wall -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -c -o 
gsocket_uchroot_dso_so_0-gsocket_uchroot_dso.o `test -f 'gsocket_uchroot_dso.c' 
|| echo './'`gsocket_uchroot_dso.c
gcc  -O2 -Wall -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security  -Wl,-z,relro 
-Wl,-z,now -o gs-netcat gs_netcat-4_gs-netcat.o gs_netcat-utils.o 
gs_netcat-socks.o gs_netcat-console.o gs_netcat-ids.o gs_netcat-event_mgr.o 
gs_netcat-pkt_mgr.o gs_netcat-console_display.o gs_netcat-filetransfer.o 
gs_netcat-globbing.o gs_netcat-filetransfer_mgr.o gs_netcat-gsocket_dso-lib.o 
../lib/libgsocket.a  -lssl -lcrypto -ldl -lutil 
gcc  -O2 -Wall -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security  -Wl,-z,relro 
-Wl,-z,now -o gs-helloworld gs_helloworld-1_gs-helloworld.o 
gs_helloworld-utils.o gs_helloworld-gsocket_dso-lib.o ../lib/libgsocket.a  
-lssl -lcrypto -ldl -lutil 
gcc -shared -fPIC -O2 -Wall -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -ldl 
-Wl,-soname=gsocket_dso.so.0 -Wl,-z,relro -Wl,-z,now -o gsocket_dso.so.0 
gsocket_dso_so_0-gsocket_dso.o gsocket_dso_so_0-gsocket_dso-lib.o  -lssl 
-lcrypto -ldl -lutil 
gcc  -O2 -Wall -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security  -Wl,-z,relro 
-Wl,-z,now -o gs-pipe gs_pipe-2_gs-pipe.o gs_pipe-utils.o 
gs_pipe-gsocket_dso-lib.o ../lib/libgsocket.a  -lssl -lcrypto -ldl -lutil 
/tmp/ccmyiWuJ.s: Assembler messages:
/tmp/ccmyiWuJ.s:3773: Error: symbol `__stat64_time64' is already defined
/tmp/ccmyiWuJ.s:4004: Error: symbol `__lstat64_time64' is already defined
make[3]: *** [Makefile:959: gsocket_uchroot_dso_so_0-gsocket_uchroot_dso.o] 
Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/<>/tools'
make[2]: *** [Makefile:387: all-recursive] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gsocket
Source-Version: 1.4.43-1
Done: Daniel Echeverri 

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

Debian distribution maintenance software
pp.
Daniel Echeverri  (supplier of updated gsocket package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 24 May 2024 17:54:48 -0500
Source: gsocket
Architecture: source
Version: 1.4.43-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverri 
Changed-By: Daniel Echeverri 
Closes: 1065966
Changes:
 gsocket (1.4.43-1) unstable; urgency=medium
 .
   * New upstream version 1.4.43 (Closes: #1065966)
   * debian/copyright
 + Extend debian copyright holders years.
   * debian/control
 + Bump Standards-Version to 4.7.0 (no changes).
   * Update debian/gsocket.symbols file.
Checksums-Sha1:

Processed: metadata

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

> tags 1058997 + ftbfs
Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12
Added tag(s) ftbfs.
> tags 1060492 + ftbfs
Bug #1060492 [src:freeipa] freeipa: Please switch Build-Depends to systemd-dev
Added tag(s) ftbfs.
> severity 1058473 serious
Bug #1058473 [src:genx] genx: please (temporarily) drop python3-numba 
dependencies
Severity set to 'serious' from 'important'
> tags 1058473 + ftbfs
Bug #1058473 [src:genx] genx: please (temporarily) drop python3-numba 
dependencies
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1071451: marked as done (src:gmsh: FTBFS with new opencascade 7.8.1)

Your message dated Fri, 24 May 2024 22:21:06 +
with message-id 
and subject line Bug#1071451: fixed in gmsh 4.12.2+ds1-2
has caused the Debian Bug report #1071451,
regarding src:gmsh: FTBFS with new opencascade 7.8.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.)


-- 
1071451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmsh
Severity: important
Tags: patch ftbfs

Dear maintainer,

gmsh FTBFS with the new opencascade 7.8.1 as the CMakeLists.txt missed to list 
one library,
and therefore many symbols are not resolved at build time:

Excerpt of build log:

/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`STEPCAFControl_Reader::STEPCAFControl_Reader()'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`STEPCAFControl_Reader::ChangeReader()'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`HeaderSection_FileDescription::SetImplementationLevel(opencascade::handle
 const&)'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`APIHeaderSection_MakeHeader::FdValue() const'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`HeaderSection_FileName::SetTimeStamp(opencascade::handle
 const&)'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`APIHeaderSection_MakeHeader::APIHeaderSection_MakeHeader(int)'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`HeaderSection_FileName::SetOriginatingSystem(opencascade::handle
 const&)'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`StepData_StepModel::AddHeaderEntity(opencascade::handle 
const&)'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`HeaderSection_FileName::SetPreprocessorVersion(opencascade::handle
 const&)'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`StepData_StepModel::Header() const'
collect2: error: ld returned 1 exit status
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`STEPCAFControl_Reader::Transfer(opencascade::handle const&, 
Message_ProgressRange const&)'
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`HeaderSection_FileName::SetName(opencascade::handle 
const&)'
collect2: error: ld returned 1 exit status
/usr/bin/ld: libgmsh.so.4.12.2: undefined reference to 
`STEPControl_Writer::Write(char const*)'
make[4]: *** [CMakeFiles/t13_cpp.dir/build.make:190: t13_cpp] Error 1
make[4]: Leaving directory '/build/gmsh-4.12.2+ds1/debian/build'
make[3]: *** [CMakeFiles/Makefile2:1759: CMakeFiles/t13_cpp.dir/all] Error 2
make[4]: *** [CMakeFiles/t14_cpp.dir/build.make:190: t14_cpp] Error 1
make[4]: Leaving directory '/build/gmsh-4.12.2+ds1/debian/build'


The attached patch makes the packages compile here locally - the patch *should*
be backward compatible with the older opencascade currently in sid.

-- 
tobi

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

Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -1331,7 +1331,7 @@
 if(FREETYPE_FOUND)
   if(OCC_VERSION AND OCC_VERSION VERSION_GREATER_EQUAL "7.8.0")
 set(OCC_CAF_LIBS_REQUIRED
-TKXCAF TKLCAF TKVCAF TKCAF TKV3d TKService TKCDF)
+TKXCAF TKLCAF TKVCAF TKCAF TKV3d TKService TKCDF TKDESTEP )
   else()
 set(OCC_CAF_LIBS_REQUIRED
 TKXDESTEP TKXDEIGES TKXCAF TKLCAF TKVCAF TKCAF TKV3d TKService 
TKCDF)
--- End Message ---
--- Begin Message ---
Source: gmsh
Source-Version: 4.12.2+ds1-2
Done: Tobias Frost 

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated gmsh 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

Processed: slic3r-prusa: diff for NMU version 2.7.4+dfsg-1.1

Processing control commands:

> tags 1071470 + pending
Bug #1071470 [src:slic3r-prusa] src:slic3r-prusa: FTBFS with opencasacade 7.8.1
Added tag(s) pending.

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

Bug#1071470: slic3r-prusa: diff for NMU version 2.7.4+dfsg-1.1

Control: tags 1071470 + pending


Dear maintainer,

I've prepared an NMU for slic3r-prusa (versioned as 2.7.4+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru slic3r-prusa-2.7.4+dfsg/debian/changelog slic3r-prusa-2.7.4+dfsg/debian/changelog
--- slic3r-prusa-2.7.4+dfsg/debian/changelog	2024-04-18 07:26:21.0 +0200
+++ slic3r-prusa-2.7.4+dfsg/debian/changelog	2024-05-24 22:12:57.0 +0200
@@ -1,3 +1,11 @@
+slic3r-prusa (2.7.4+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with opencasacade 7.8.1 (Closes: #1071470) and
+add a versioned B-D on it.
+
+ -- Tobias Frost   Fri, 24 May 2024 22:12:57 +0200
+
 slic3r-prusa (2.7.4+dfsg-1) unstable; urgency=medium
 
   * [3cddded] New upstream version 2.7.4+dfsg
diff -Nru slic3r-prusa-2.7.4+dfsg/debian/control slic3r-prusa-2.7.4+dfsg/debian/control
--- slic3r-prusa-2.7.4+dfsg/debian/control	2024-04-18 07:26:21.0 +0200
+++ slic3r-prusa-2.7.4+dfsg/debian/control	2024-05-24 22:12:57.0 +0200
@@ -20,11 +20,11 @@
libheatshrink-dev,
libnanosvg-dev,
libnlopt-cxx-dev | libnlopt-dev (<< 2.4.2+dfsg-5~),
-   libocct-data-exchange-dev,
-   libocct-draw-dev,
-   libocct-foundation-dev,
-   libocct-modeling-algorithms-dev,
-   libocct-visualization-dev,
+   libocct-data-exchange-dev (>=7.8.1+dfsg1),
+   libocct-draw-dev (>=7.8.1+dfsg1),
+   libocct-foundation-dev (>=7.8.1+dfsg1),
+   libocct-modeling-algorithms-dev (>=7.8.1+dfsg1),
+   libocct-visualization-dev (>=7.8.1+dfsg1),
libopenvdb-dev (>= 5.0),
libopenvdb-tools,
libpng-dev,
diff -Nru slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch
--- slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch	1970-01-01 01:00:00.0 +0100
+++ slic3r-prusa-2.7.4+dfsg/debian/patches/occt-7.8.patch	2024-05-24 22:12:57.0 +0200
@@ -0,0 +1,18 @@
+diff --git a/src/occt_wrapper/CMakeLists.txt b/src/occt_wrapper/CMakeLists.txt
+index d8dd8e1..d27055f 100644
+--- a/src/occt_wrapper/CMakeLists.txt
 b/src/occt_wrapper/CMakeLists.txt
+@@ -22,11 +22,8 @@ generate_export_header(OCCTWrapper)
+ find_package(OpenCASCADE REQUIRED)
+ 
+ set(OCCT_LIBS
+-TKXDESTEP
+-TKSTEP
+-TKSTEP209
+-TKSTEPAttr
+-TKSTEPBase
++TKDESTEP
++TKDESTL
+ TKXCAF
+ TKXSBase
+ TKVCAF
diff -Nru slic3r-prusa-2.7.4+dfsg/debian/patches/series slic3r-prusa-2.7.4+dfsg/debian/patches/series
--- slic3r-prusa-2.7.4+dfsg/debian/patches/series	2024-04-18 07:26:21.0 +0200
+++ slic3r-prusa-2.7.4+dfsg/debian/patches/series	2024-05-24 22:12:57.0 +0200
@@ -8,3 +8,4 @@
 Disable-preset-update-and-version-check-by-default.patch
 Patch-tests-for-Catch2-v3-compatibility.patch
 Explicit-wxWidgets-initializers.patch
+occt-7.8.patch


signature.asc
Description: PGP signature

Bug#1071223: marked as done (negen: Will FTBFS with next opencascade version 7.8.1)

Your message dated Fri, 24 May 2024 21:02:12 +
with message-id 
and subject line Bug#1071223: fixed in netgen 6.2.2401+dfsg1-2
has caused the Debian Bug report #1071223,
regarding negen: Will FTBFS with next opencascade version 7.8.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.)


-- 
1071223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netgen
Severity: important
Tags: ftbfs

Dear maintainers,

I've just uploaded opencascade 7.8.1 to experimental (currently sitting in NEW
waiting for ftp master approval)

Unfortunatly, netgen fails with the new version, as there are ABI changes (e.g
dropped header files.)

[ 48%] Building CXX object 
CMakeFiles/nglib.dir/libsrc/occ/Partition_Loop3d.cxx.o
/usr/bin/c++ -DFFMPEG -DHAVE_DLFCN_H -DHAVE_FREEIMAGE -DHAVE_FREETYPE 
-DHAVE_OPENGL_EXT -DHAVE_RAPIDJSON -DHAVE_TBB -DHAVE_TK -DHAVE_XLIB -DJPEGLIB 
-DMETIS -DNETGEN_PYTHON -DNG_MPI4PY -DNG_PYTHON -DOCCGEOMETRY 
-DOCC_CONVERT_SIGNALS -DPARALLEL -DPYBIND11_SIMPLE_GIL_MANAGEMENT 
-D__STDC_CONSTANT_MACROS -Dnglib_EXPORTS 
-I/build/netgen-6.2.2401+dfsg1/obj-x86_64-linux-gnu 
-I/build/netgen-6.2.2401+dfsg1 -I/build/netgen-6.2.2401+dfsg1/include 
-I/build/netgen-6.2.2401+dfsg1/libsrc 
-I/build/netgen-6.2.2401+dfsg1/libsrc/include -I/usr/include/python3.11 
-I/usr/lib/python3/dist-packages/mpi4py/include/mpi4py 
-I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem 
/usr/include/opencascade -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/build/netgen-6.2.2401+dfsg1=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -std=gnu++17 -fPIC 
-fvisibility=hidden -MD -MT 
CMakeFiles/nglib.dir/libsrc/occ/Partition_Loop3d.cxx.o -MF 
CMakeFiles/nglib.dir/libsrc/occ/Partition_Loop3d.cxx.o.d -o 
CMakeFiles/nglib.dir/libsrc/occ/Partition_Loop3d.cxx.o -c 
/build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.cxx
In file included from 
/build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.jxx:29,
 from 
/build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.ixx:10,
 from 
/build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.cxx:14:
/build/netgen-6.2.2401+dfsg1/libsrc/occ/Partition_Loop3d.hxx:32:13: fatal 
error: TopTools_OrientedShapeMapHasher.hxx: No such file or directory
   32 |#include 
  | ^
compilation terminated.

-- 
tobi

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

Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: netgen
Source-Version: 6.2.2401+dfsg1-2
Done: Tobias Frost 

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated netgen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 24 May 2024 21:57:58 +0200
Source: netgen
Architecture: source
Version: 6.2.2401+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Tobias Frost 
Closes: 1071223
Changes:
 netgen (6.2.2401+dfsg1-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to support opencascade 7.8.1 (Closes: #1071223)
 and add a versioned B-D constraint on it.
Checksums-Sha1:
 b2e0f7ef123cb4806b7d292c4d3ee36208bd4d56 2983 netgen_6.2.2401+dfsg1-2.dsc
 d479715f8cfc639ff5a93daf2406c57ab544686c 25284

Bug#1071007: marked as done (sherlock: Must not ship /usr/lib/python3/dist-packages/init.py)

Your message dated Fri, 24 May 2024 22:01:51 +0100
with message-id 

and subject line sherlock: Must not ship 
/usr/lib/python3/dist-packages/__init__.py
has caused the Debian Bug report #1071007,
regarding sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
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.)


-- 
1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sherlock
Version: 0.14.3+git20240511.b83f5be-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + pycrc

sherlock has an undeclared file conflict. This may result in an unpack
error from dpkg.

The file /usr/lib/python3/dist-packages/__init__.py is contained in the
packages
 * pycrc/0.10.0-2 as present in trixie|unstable
 * sherlock/0.14.3+git20240511.b83f5be-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
I have read the other replies to the bug, which I missed previously.

It's not upstream's intention to ship the modules in dist-packages.

Closing.

Regards,

-- 
Samuel Henrique --- End Message ---

Bug#1071283: marked as done (src:freecad: FTBFS with opencascade 7.8.1)

Your message dated Fri, 24 May 2024 20:55:05 +
with message-id 
and subject line Bug#1071283: fixed in freecad 0.21.2+dfsg1-2
has caused the Debian Bug report #1071283,
regarding src:freecad: FTBFS with opencascade 7.8.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.)


-- 
1071283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freecad
Version: 0.21.2+dfsg1-1
Severity: important
Tags: ftbfs

freecad fails to build with opencascade 7.8.1, which is now in experimental.

(Once the transistion starts, this bug will become RC.)

snippet attached:

[  0%] Linking CXX shared library ../../../lib/libSMDS.so
cd /build/freecad-0.21.2+dfsg1/debian/build-py3/src/3rdParty/salomesmesh && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/SMDS.dir/link.txt --verbose=1
/usr/lib/ccache/c++ -fPIC  -Wall -Wextra -Wno-write-strings -g -O2 
-ffile-prefix-map=/build/freecad-0.21.2+dfsg1=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -fpermissive -I/usr/include/python3.11 
-flto -Wno-sign-compare -Wno-reorder -Wno-switch -Wno-unused-variable 
-Wno-unused-but-set-variable -Wno-comment -Wno-unused-parameter -Wno-empty-body 
-Wno-pedantic -Wno-unused-result -Wno-cast-function-type 
-Wno-maybe-uninitialized -Wno-missing-field-initializers -O2 -g -DNDEBUG 
-L/usr/lib/x86_64-linux-gnu/openmpi/lib -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-Wl,-flto -shared -Wl,-soname,libSMDS.so -o ../../../lib/libSMDS.so 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_BallElement.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_Downward.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_EdgePosition.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_FaceOfEdges.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_FaceOfNodes.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_FacePosition.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_IteratorOfElements.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_LinearEdge.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_Mesh.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_Mesh0DElement.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshCell.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshEdge.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshElement.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshElementIDFactory.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshFace.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshGroup.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshIDFactory.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshNode.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshNodeIDFactory.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshObject.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_MeshVolume.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_PolygonalFaceOfNodes.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_PolyhedralVolumeOfNodes.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_Position.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_QuadraticEdge.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_QuadraticFaceOfNodes.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_QuadraticVolumeOfNodes.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_SpacePosition.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_UnstructuredGrid.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_VertexPosition.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_VolumeOfFaces.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_VolumeOfNodes.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_VolumeTool.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_VtkCellIterator.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_VtkEdge.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_VtkFace.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/SMDS_VtkVolume.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/Utils_SALOME_Exception.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/chrono.cpp.o 
CMakeFiles/SMDS.dir/src/SMDS/duplicate.cpp.o   
-L/usr/lib/x86_64-linux-gnu/hdf5/serial  
-L/usr/lib/x86_64-linux-gnu/openmpi/lib  
-Wl,-rpath,/usr/lib/x86_64-linux-gnu/hdf5/serial:/usr/lib/x86_64-linux-gnu/openmpi/lib:
 -lhdf5 -lmpi_cxx -lmpi -lTKIGES -lTKSTL 
/usr/lib/x86_64-linux-gnu/libTKXSBase.so.7.8.1 
/usr/lib/x86_64-linux-gnu/libTKOffset.so.7.8.1 -lTKSTEPBase -lTKSTEPAttr 
-lTKSTEP209 -lTKSTEP /usr/lib/x86_64-linux-gnu/libTKFeat.so.7.8.1 
/usr/lib/x86_64-linux-gnu/libTKBin.so.7.8.1 
/usr/lib/x86_64-linux-gnu/libTKBinL.so.7.8.1 -lTKXDESTEP -lTKXDEIGES 
/usr/lib/x86_64-linux-gnu/libTKMeshVS.so.7.8.1 
/usr/lib/x86_64-linux-gnu/libTKRWMesh.so.7.8.1 
/usr/lib/x86_64-linux-gnu/libvtkFiltersVerdict-9.1.so.9.1.0 
/usr/lib/x86_64-linux-gnu/libvtkIOMPIParallel-9.1.so.9.1.0 
/usr/lib/x86_64-linux-gnu/libvtkInteractionStyle-9.1.so.9.1.0

Processed: sherlock: Must not ship /usr/lib/python3/dist-packages/init.py

Processing control commands:

> reopen -1 =
Bug #1071007 {Done: Josenilson Ferreira da Silva } 
[sherlock] sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions sherlock/0.14.3+git20240522.ab5fcbb-1.

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

Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/init.py

2024-05-24 Thread Samuel Henrique

Control: reopen -1 =

The latest upload broke the package, this time by mis-placing the files in
/usr/share/:
https://salsa.debian.org/pkg-security-team/sherlock/-/commit/58dacca3117b66341a4371431d6f38a1d35b08c9
https://salsa.debian.org/pkg-security-team/sherlock/-/commit/00a20c5cc3a9c42a295e886dee1db49472338c4e

The commit "58dacca3117b66341a4371431d6f38a1d35b08c" is also doing more than
what's described in its message. I'm not sure dh_link is the right place to
remove test files, but I haven't looked into that deeply.

This breaks the ability to import sherlock into other python scripts, since
it's not under dist-packages anymore.

The original proposed solution to the issue still stands: we just need to not
ship files at the root of dist-packages.

Regards,

-- 
Samuel Henrique

Bug#1071782: skimage: autopkgtest needs update for new version of pytest on s390x


Source: skimage
Version: 0.22.0-3
Severity: serious
X-Debbugs-CC: pyt...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pytest

Dear maintainer(s),

With a recent upload of pytest the autopkgtest of skimage fails in 
testing on s390x when that autopkgtest is run with the binary packages 
of pytest from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
pytest from testing8.1.2-1
skimagefrom testing0.22.0-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. I'll note that 
s390x is our only big endian architecture with autopgktest.


Currently this regression is blocking the migration of pytest to testing 
[1]. Of course, pytest shouldn't just break your autopkgtest (or even 
worse, your package), but due to the nature of the package pytest I 
suspect that your package just needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from pytest should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=pytest

https://ci.debian.net/data/autopkgtest/testing/s390x/s/skimage/46978110/log.gz

=== FAILURES 
===
300s __ test_imread_handle 
__

300s 300s def test_imread_handle():
300s expected = np.load(fetch('data/chessboard_GRAY_U8.npy'))
300s with open(fetch('data/chessboard_GRAY_U16.tif'), 'rb') as fh:
300s img = imread(fh)
300s >   assert img.dtype == np.uint16
300s E   AssertionError: assert dtype('
300s E+  where dtype('0,   0],\n   [255, 255, 255, ...,   0,   0,   0],\n   [255, 255, 
255, ...,   0,   0,   0],\n   ...,\n   [  0,   0,   0, ..., 255, 
255, 255],\n   [  0,   0,   0, ..., 255, 255, 255],\n   [  0, 
0,   0, ..., 255, 255, 255]], dtype='
300s E+  and= np.uint16
300s 300s 
/usr/lib/python3/dist-packages/skimage/io/tests/test_tifffile.py:48: 
AssertionError
300s === warnings summary 
===

300s filters/tests/test_unsharp_mask.py: 480 warnings
300s 
/usr/lib/python3/dist-packages/skimage/filters/tests/test_unsharp_mask.py:26: 
RuntimeWarning: invalid value encountered in cast

300s array = ((array + offset) * 128).astype(dtype)
300s 300s io/tests/test_pil.py::test_png_round_trip
300s io/tests/test_pil.py::test_imsave_filelike
300s 
/usr/lib/python3/dist-packages/skimage/io/_plugins/pil_plugin.py:105: 
DeprecationWarning: The binary mode of fromstring is deprecated, as it 
behaves surprisingly on unicode inputs. Use frombuffer instead

300s frame = np.fromstring(frame.tobytes(), dtype)
300s 300s measure/tests/test_fit.py::test_ellipse_parameter_stability
300s   /usr/lib/python3/dist-packages/skimage/measure/fit.py:526: 
RuntimeWarning: divide by zero encountered in scalar divide

300s phi = 0.5 * np.arctan((2. * b) / (a - c))
300s 300s 
transform/tests/test_pyramids.py::test_pyramid_dtype_support[pyramid_gaussian-uint8]
300s 
transform/tests/test_pyramids.py::test_pyramid_dtype_support[pyramid_laplacian-uint8]
300s 
/usr/lib/python3/dist-packages/skimage/transform/tests/test_pyramids.py:208: 
RuntimeWarning: invalid value encountered in cast

300s img = np.random.randn(32, 8).astype(dtype)
300s 300s 
../../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:446
300s   /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:446: 
PytestCacheWarning: could not create cache path 
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/nodeids: 
[Errno 13] Permission denied: 
'/usr/lib/python3/dist-packages/skimage/.pytest_cache'

300s config.cache.set("cache/nodeids", sorted(self.cached_nodeids))
300s 300s 
../../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:398
300s   /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:398: 
PytestCacheWarning: could not create cache path 
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/lastfailed: 
[Errno 13] Permission denied: 
'/usr/lib/python3/dist-packages/skimage/.pytest_cache'

300s config.cache.set("cache/lastfailed", self.lastfailed)
300s 300s ../../../../usr/lib/python3/dist-packages/_pytest/stepwise.py:57
300s   /usr/lib/python3/dist-packages/_pytest/stepwise.py:57: 
PytestCacheWarning: could not create cache path

Processed: skimage: autopkgtest needs update for new version of pytest on s390x

Processing control commands:

> affects -1 src:pytest
Bug #1071782 [src:skimage] skimage: autopkgtest needs update for new version of 
pytest on s390x
Added indication that 1071782 affects src:pytest

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

Bug#1061743: Gramps in Debian

2024-05-24 Thread Ross Gammon


Hi Tobias,

There are no blockers other than real life getting in the way. I did
start working on 5.2.0 in the experimental branch on Salsa. From memory,
there was a problem with fuzzy patches, and the tedious checking of
copyrights still to do. But I should probably merge the changes into
master, and then import 5.2.2.

If you have some spare cycles you are welcome to help move things along.
I use gbp + quilt.

Regards,

Ross

On 28.04.2024 17.40, Dr. Tobias Quathamer wrote:

Hi Ross,

I'd like to get gramps back into Debian, and from my (very limited)
research it seems that gramps v5.2.1 fixed the build failure on Debian.

Are you planning to update the package? Or is there another blocker
which I didn't spot?

Thanks for taking care of gramps in Debian!

Regards,
Tobias

Bug#1071780: sepp: FTBFS: ImportError: cannot import name '_convert_node_to_root_polytomy' from 'dendropy.datamodel.treemodel'


Package: src:sepp
Version: 4.5.1+really4.5.1+dfsg-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
mkdir -p tools/bundled/Linux
mkdir -p tools/merge/lib
# Building the jar for sepp.
cd tools/merge && \
CLASSPATH=/usr/share/java/jenkins-json-lib.jar:/usr/share/java/gson.jar ant
Buildfile: /<>/tools/merge/build.xml

clean:

compile:
[mkdir] Created dir: /<>/tools/merge/classes
[javac] /<>/tools/merge/build.xml:32: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for 
repeatable builds
[javac] Compiling 23 source files to /<>/tools/merge/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 
/<>/tools/merge/src/edu/rice/cs/bioinfo/programs/phylonet/structs/tree/util/Trees.java:32:
 warning: SunGraphicsEnvironment is internal proprietary API and may be removed in a future 
release
[javac] import sun.java2d.SunGraphicsEnvironment;
[javac]  ^
[javac] 
/<>/tools/merge/src/edu/rice/cs/bioinfo/programs/phylonet/algos/lca/SchieberVishkinLCA.java:188:
 warning: [removal] Integer(int) in Integer has been deprecated and marked for removal
[javac] _tnode_idx_lookup.put(n, new Integer(i++));
[javac]  ^
[javac] 
/<>/tools/merge/src/edu/rice/cs/bioinfo/programs/phylonet/structs/tree/io/NewickReader.java:341:
 warning: [removal] Double(double) in Double has been deprecated and marked for removal
[javac] node.setData(new Double(0));
[javac]  ^
[javac] 
/<>/tools/merge/src/edu/rice/cs/bioinfo/programs/phylonet/structs/tree/model/sti/STITree.java:221:
 warning: [removal] Integer(int) in Integer has been deprecated and marked for removal
[javac] return _nodes.get(new Integer(id));
[javac]   ^
[javac] 
/<>/tools/merge/src/phylolab/taxonamic/JSONMerger.java:264: 
warning: [removal] Integer(String) in Integer has been deprecated and marked for removal
[javac]   newRecord.set(locEdgeNum, new Integer(newLab));
[javac] ^
[javac] 
/<>/tools/merge/src/phylolab/taxonamic/JSONMerger.java:275: 
warning: [removal] Double(double) in Double has been deprecated and marked for removal
[javac]   Double newLWR = new Double(prior * precord.getDouble(2));
[javac]   ^
[javac] 
/<>/tools/merge/src/phylolab/taxonamic/JSONMerger.java:519: 
warning: [removal] Double(String) in Double has been deprecated and marked for removal
[javac]   mainEdgeLen.put(edgeLenMatcher.group(2), new 
Double(edgeLenMatcher.group(1)));
[javac]^
[javac] 
/<>/tools/merge/src/phylolab/taxonamic/JSONMerger.java:616: 
warning: [removal] Double(String) in Double has been deprecated and marked for removal
[javac] cutoff = new Double(args[i]);
[javac]  ^
[javac] 
/<>/tools/merge/src/phylolab/taxonamic/JSONMerger.java:656: 
warning: [removal] Double(String) in Double has been deprecated and marked for removal
[javac] threshold = new Double(args[i]);
[javac] ^
[javac] 
/<>/tools/merge/src/phylolab/taxonamic/PPlacerJSONMerger.java:177: 
warning: [removal] Integer(String) in Integer has been deprecated and marked for removal
[javac] pr.set(locEdgeNum, new Integer(newLab));
[javac]^
[javac] 
/<>/tools/merge/src/phylolab/taxonamic/PPlacerJSONMerger.java:269: 
warning: [removal] Double(String) in Double has been deprecated and marked for removal
[javac] Double len = new 
Double(matcher.group(1));
[javac]  ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 12 warnings

jar:
  [jar] Building jar: /<>/tools/merge/seppJsonMerger.jar

BUILD SUCCESSFUL
Total time: 2 seconds
dh_auto_configure
I: pybuild base:311: python3.11 setup.py config

Creating main sepp config file at /<>/.pybuild/cpython3_3.11/.sepp/main.config 
and tools at /<>/.pybuild/cpython3_3.11/.sepp
# dh_auto_configure only calls the config for

Bug#1071781: smlsharp: FTBFS: configure: error: Specify --with-incompatible-llvm if you really want to build SML# with it.

Package: src:smlsharp
Version: 4.0.0+git20211227.5af5945b-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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

[...]
debian/rules binary
dh binary
dh_update_autotools_config
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
dh_autoreconf
configure.ac:6: warning: The macro `AC_CONFIG_HEADER' is obsolete.
configure.ac:6: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:6: the top level
configure.ac:14: warning: The macro `AC_PROG_CC_C99' is obsolete.
configure.ac:14: You should run autoupdate.
./lib/autoconf/c.m4:1659: AC_PROG_CC_C99 is expanded from...
configure.ac:14: the top level
configure.ac:246: warning: The macro `AC_ERROR' is obsolete.
configure.ac:246: You should run autoupdate.
./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.ac:246: the top level
configure.ac:246: warning: The macro `AC_ERROR' is obsolete.
configure.ac:246: You should run autoupdate.
./lib/autoconf/oldnames.m4:34: AC_ERROR is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:1553: AC_ARG_WITH is expanded from...
configure.ac:246: the top level
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
CFLAGS="-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection"
LDFLAGS="-Wl,-z,relro -Wl,-z,now" \
./configure --prefix=/usr
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for wchar.h... yes
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether _XOPEN_SOURCE should be defined... no
checking for stdatomic.h... yes
checking for alignof... yes
checking for _Thread_local storage class... yes
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for find... /usr/bin/find
checking for ranlib... ranlib
checking for ld... ld
checking for ar... ar
checking that RDYNAMIC_LDFLAGS works... yes
checking that RUNLOOP_DLDFLAGS works... yes
checking for llvm-config... /usr/bin/llvm-config
checking for LLVM bindir... /usr/lib/llvm-16/bin
checking for LLVM cxxflags... -I/usr/lib/llvm-16/include -std=c++17
-fno-exceptions -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
-D__STDC_LIMIT_MACROS
checking for LLVM version... 16.0.6
checking for llc... /usr/lib/llvm-16/bin/llc
checking for opt... /usr/lib/llvm-16/bin/opt
checking for llvm-dis... /usr/lib/llvm-16/bin/llvm-dis
checking for llvm-as... /usr/lib/llvm-16/bin/llvm-as
checking for LLVM compatibility... no
configure: WARNING: SML# does not support LLVM 16.0. Build may fail due to
incompatibility.
configure: error: Specify --with-incompatible-llvm if you really want to build
SML# with it.
make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact

Bug#1071778: python-django-ca: FTBFS: failing tests


Package: src:python-django-ca
Version: 1.25.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3,sphinxdoc --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.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_django-ca
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib

[... snipped ...]

E   SystemExit: 1

/usr/lib/python3/dist-packages/django/core/management/base.py:422: SystemExit

During handling of the above exception, another exception occurred:

self = 

@override_tmpcadir(CA_MIN_KEY_SIZE=1024)
def test_multiple_ocsp_and_ca_issuers(self) -> None:
"""Test using multiple OCSP responders and CA issuers."""
root = self.load_ca("root")
name = self._testMethodName[:32]

ocsp_uri_one = "http://ocsp.example.com/one;

ocsp_uri_two = "http://ocsp.example.net/two;
issuer_uri_one = "http://issuer.example.com/one;
issuer_uri_two = "http://issuer.example.com/two;

  ca = self.init_ca_e2e(

name,
f"/CN={name}",
f"--parent={root.serial}",
# NOTE: mixing the order of arguments here. This way we make sure 
that the values are properly
# sorted (by method) in the assertion for the extension.
f"--ca-ocsp-url={ocsp_uri_one}",
f"--ca-issuer-url={issuer_uri_one}",
f"--ca-ocsp-url={ocsp_uri_two}",
f"--ca-issuer-url={issuer_uri_two}",
chain=[root],
)

django_ca/tests/commands/test_init_ca.py:1027:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
django_ca/tests/commands/test_init_ca.py:71: in init_ca_e2e
with self.assertCreateCASignals() as (pre, post):
/usr/lib/python3.11/contextlib.py:158: in __exit__
self.gen.throw(typ, value, traceback)
django_ca/tests/base/mixins.py:291: in assertCreateCASignals
self.assertTrue(post_sig.called is post)
E   AssertionError: False is not true
__ ViewCATestCase.test_acme_disabled ___

self = 

@override_tmpcadir(CA_ENABLE_ACME=False)
def test_acme_disabled(self) -> None:
"""Test viewing when ACME is disabled."""
stdout, stderr = self.cmd("view_ca", self.cas["root"].serial, 
wrap=False)
self.assertEqual(stderr, "")
data = self.get_cert_context("root")

  self.assertMultiLineEqual(stdout, 
expected["root-acme-disabled"].format(**data))

E   AssertionError: '* Na[250 chars]tus: Expired\n* HPKP pin: 
OfMQVNzWUTEbiU4y6hBS[2504 chars]--\n' != '* Na[250 chars]tus: Valid\n* HPKP 
pin: OfMQVNzWUTEbiU4y6hBSbq[2502 chars]--\n'
E   Diff is 2920 characters long. Set self.maxDiff to None to see it.

django_ca/tests/commands/test_view_ca.py:1457: AssertionError
_ ViewCATestCase.test_all_cas __

self = 

@override_tmpcadir()
def test_all_cas(self) -> None:
"""Test viewing all CAs."""
for name, ca in sorted(self.cas.items(), key=lambda t: t[0]):
stdout, stderr = self.cmd("view_ca", ca.serial, wrap=False)
data = self.get_cert_context(name)

  self.assertMultiLineEqual(stdout, expected[name].format(**data), name)

E   AssertionError: '* Na[252 chars]tus: Expired\n* HPKP pin: 
47J9/gQZ1KaXn1TGcQeu[3391 chars]--\n' != '* Na[252 chars]tus: Valid\n* HPKP 
pin: 47J9/gQZ1KaXn1TGcQeurg[3389 chars]--\n'
E   Diff is 3827 characters long. Set self.maxDiff to None to see it. : 
child

django_ca/tests/commands/test_view_ca.py:1411: AssertionError
__ ViewCATestCase.test_no_extensions ___

self = 

@override_tmpcadir()
def test_no_extensions(self) -> None:
"""Test viewing a CA without extensions."""
stdout, stderr = self.cmd("view_ca", self.cas["root"].serial, 
extensions=False, wrap=False)
self.assertEqual(stderr, "")
data = self.get_cert_context("root")

  self.assertMultiLineEqual(stdout, 
expected["root-no-extensions"].format(**data))

E   AssertionError: '* Na[250 chars]tus: Expired\n* HPKP pin: 
OfMQVNzWUTEbiU4y6hBS[2224 chars]--\n' != '* Na[250 chars]tus: Valid\n* HPKP 
pin: OfMQVNzWUTEbiU4y6hBSbq[ chars]--\n'
E   Diff is 2632 characters long. Set self.maxDiff to None to see it.

django_ca/tests/commands/test_view_ca.py:1465: AssertionError
 ViewCATestCase.test_no_no_private_key

Bug#1071777: python-array-api-compat: FTBFS: ImportError: Failed to load PyTorch C extensions


Package: src:python-array-api-compat
Version: 1.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.12_array_api_compat/build/array_api_compat

[... snipped ...]

# 
https://github.com/pytorch/multipy/blob/d60f34ad38c371e441fe7ffdb77a3c3dda5a5d19/multipy/runtime/interpreter/interpreter_impl.cpp#L134-L137
def _running_with_deploy():
return sys.modules.get("torch._meta_registrations", None) is object

from ._utils import _import_dotted_name, classproperty

from ._utils_internal import get_file_path, 
prepare_multiprocessing_environment, \
USE_RTLD_GLOBAL_WITH_LIBTORCH, USE_GLOBAL_DEPS

# TODO(torch_deploy) figure out how to freeze version.py in fbcode build

if _running_with_deploy():
__version__ = "torch-deploy-1.8"
else:
from .torch_version import __version__ as __version__

from typing import Any, Callable, Dict, Optional, Set, Tuple, Type, TYPE_CHECKING, Union, List

import builtins

__all__ = [

'typename', 'is_tensor', 'is_storage',
'set_default_tensor_type', 'set_default_device',
'set_rng_state', 'get_rng_state', 'manual_seed', 'initial_seed', 'seed',
'save', 'load', 'set_printoptions', 'chunk', 'split', 'stack', 'matmul',
'no_grad', 'enable_grad', 'rand', 'randn', 'inference_mode',
'DoubleStorage', 'FloatStorage', 'LongStorage', 'IntStorage',
'ShortStorage', 'CharStorage', 'ByteStorage', 'BoolStorage',
'TypedStorage', 'UntypedStorage',
'DoubleTensor', 'FloatTensor', 'LongTensor', 'IntTensor',
'ShortTensor', 'CharTensor', 'ByteTensor', 'BoolTensor', 'Tensor',
'lobpcg', 'use_deterministic_algorithms',
'are_deterministic_algorithms_enabled',
'is_deterministic_algorithms_warn_only_enabled',
'set_deterministic_debug_mode', 'get_deterministic_debug_mode',
'set_float32_matmul_precision', 'get_float32_matmul_precision',
'set_warn_always', 'is_warn_always_enabled', 'SymInt', 'SymFloat',
'SymBool', 'sym_not',
'sym_int', 'sym_float', 'sym_max', 'sym_min', 'compile', 'vmap',
'export',
]



# Load the extension module



if sys.platform == 'win32':

pfiles_path = os.getenv('ProgramFiles', 'C:\\Program Files')
py_dll_path = os.path.join(sys.exec_prefix, 'Library', 'bin')
th_dll_path = os.path.join(os.path.dirname(__file__), 'lib')

# When users create a virtualenv that inherits the base environment,

# we will need to add the corresponding library directory into
# DLL search directories. Otherwise, it will rely on `PATH` which
# is dependent on user settings.
if sys.exec_prefix != sys.base_exec_prefix:
base_py_dll_path = os.path.join(sys.base_exec_prefix, 'Library', 
'bin')
else:
base_py_dll_path = ''

dll_paths = list(filter(os.path.exists, [th_dll_path, py_dll_path, base_py_dll_path]))

if all(not os.path.exists(os.path.join(p, 'nvToolsExt64_1.dll')) for p in dll_paths):

nvtoolsext_dll_path = os.path.join(
os.getenv('NVTOOLSEXT_PATH', os.path.join(pfiles_path, 'NVIDIA 
Corporation', 'NvToolsExt')), 'bin', 'x64')
else:
nvtoolsext_dll_path = ''

from .version import cuda as cuda_version

import glob
if cuda_version and all(not glob.glob(os.path.join(p, 'cudart64*.dll')) 
for p in dll_paths):
cuda_version_1 = cuda_version.replace('.', '_')
cuda_path_var = 'CUDA_PATH_V' + cuda_version_1
default_path = os.path.join(pfiles_path, 'NVIDIA GPU Computing 
Toolkit', 'CUDA', 'v' + cuda_version)
cuda_path = os.path.join(os.getenv(cuda_path_var, default_path), 
'bin')
else:
cuda_path = ''

dll_paths.extend(filter(os.path.exists, [nvtoolsext_dll_path, cuda_path]))

kernel32 = ctypes.WinDLL('kernel32.dll', use_last_error=True)

with_load_library_flags = hasattr(kernel32, 'AddDllDirectory')
prev_error_mode = kernel32.SetErrorMode(0x0001)

Bug#1071779: ruby-diaspora-federation-rails: FTBFS: Could not find 'faraday' (~> 1.0) among 123 total gem(s)


Package: src:ruby-diaspora-federation-rails
Version: 0.2.7-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --buildsystem=ruby --with ruby
   dh_update_autotools_config -O--buildsystem=ruby
   dh_autoreconf -O--buildsystem=ruby
   dh_auto_configure -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -O--buildsystem=ruby
   dh_prep -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-diaspora-federation-rails/ 
-O--buildsystem=ruby
dh_ruby --install /<>/debian/ruby-diaspora-federation-rails
/usr/bin/ruby3.1 -S gem build --config-file /dev/null --verbose 
/tmp/d20240524-19334-fq2iq/gemspec
Failed to load /dev/null because it doesn't contain valid YAML hash
  Successfully built RubyGem
  Name: diaspora_federation-rails
  Version: 0.2.7
  File: diaspora_federation-rails-0.2.7.gem
/usr/bin/ruby3.1 -S gem install --config-file /dev/null --verbose --local 
--verbose --no-document --ignore-dependencies --install-dir 
debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all 
/tmp/d20240524-19334-fq2iq/diaspora_federation-rails-0.2.7.gem
Failed to load /dev/null because it doesn't contain valid YAML hash
/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all/gems/diaspora_federation-rails-0.2.7/config/initializers/filter_parameter_logging.rb
/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all/gems/diaspora_federation-rails-0.2.7/config/initializers/mime_types.rb
/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all/gems/diaspora_federation-rails-0.2.7/config/routes.rb
/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all/gems/diaspora_federation-rails-0.2.7/lib/diaspora_federation/engine.rb
/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all/gems/diaspora_federation-rails-0.2.7/lib/diaspora_federation/rails.rb
Successfully installed diaspora_federation-rails-0.2.7
1 gem installed
cd debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all
rm -rf bin
rm -rf build_info
rm -rf cache
rm -rf doc
rm -rf extensions
rmdir plugins
cd gems/diaspora_federation-rails-0.2.7
rm -f
chmod 644 lib/diaspora_federation/engine.rb lib/diaspora_federation/rails.rb
find lib/ -type d -empty -delete
cd -
cd -
/usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby3.1   │
└──┘

RUBYLIB=. 
GEM_PATH=/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
 ruby3.1 -e gem\ \"diaspora_federation-rails\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1477:in `rescue in block in 
activate_dependencies': Could not find 'faraday' (~> 1.0) among 123 total 
gem(s) (Gem::MissingSpecError)
Checked in 
'GEM_PATH=/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
 at: /usr/share/rubygems-integration/all/specifications/diaspora_federation-0.2.7.gemspec, execute `gem 
env` for more information
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1474:in `block 
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1463:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1463:in 
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1445:in 
`activate'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1481:in `block 
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1463:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1463:in 
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1445:in 
`activate'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:63:in 
`block in gem'
from

Bug#1071776: pytest-services: FTBFS: ERROR tests/test_plugin.py::test_mysql - ValueError: . is not a normalized an...


Package: src:pytest-services
Version: 2.2.1+ds-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
/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/_distutils/dist.py:265: UserWarning: 
Unknown distribution option: 'extras'
  warnings.warn(msg)
running config
I: pybuild base:311: 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.
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: UserWarning: 
Unknown distribution option: 'extras'
  warnings.warn(msg)
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /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.
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: UserWarning: 
Unknown distribution option: 'extras'
  warnings.warn(msg)
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/django_settings.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/plugin.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/process.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/folders.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/locks.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/memcached.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/mysql.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/log.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/__init__.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/xvfb.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
copying pytest_services/service.py -> 
/<>/.pybuild/cpython3_3.12_pytest-services/build/pytest_services
I: pybuild base:311: /usr/bin/python3 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.
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: UserWarning: 
Unknown distribution option: 'extras'
  warnings.warn(msg)
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.11_pytest-services/build/pytest_services
copying pytest_services/django_settings.py -> 
/<>/.pybuild/cpython3_3.11_pytest-services/build/pytest_services
copying

Bug#1071774: orange3: FTBFS: Orange/classification/_simple_tree.c:63:9: error: implicit declaration of function ‘qsort_r’


Package: src:orange3
Version: 3.35.0+ds1-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 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.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_orange3
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-312

[... snipped ...]

creating build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/tests
copying Orange/widgets/data/utils/tests/test_tableview.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/tests
copying Orange/widgets/data/utils/tests/__init__.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/tests
creating 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_rectangular_selection.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/base.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_bracket_highlighter.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_draw_whitespace.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_api.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_edit.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_indent.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/test_vim.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/run_all.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
copying Orange/widgets/data/utils/pythoneditor/tests/__init__.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests
creating 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests/test_indenter
copying Orange/widgets/data/utils/pythoneditor/tests/test_indenter/test_python.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests/test_indenter
copying Orange/widgets/data/utils/pythoneditor/tests/test_indenter/indenttest.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests/test_indenter
copying Orange/widgets/data/utils/pythoneditor/tests/test_indenter/__init__.py 
-> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/data/utils/pythoneditor/tests/test_indenter
creating build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owdistancefile.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owpca.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owlouvain.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owsavedistances.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owmanifoldlearning.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owtsne.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owdbscan.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owcorrespondence.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owdistancematrix.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owsom.py -> 
build/lib.linux-x86_64-cpython-311/Orange/widgets/unsupervised/tests
copying Orange/widgets/unsupervised/tests/test_owhierarchicalclustering.py ->

Bug#1071775: plotpy: FTBFS: plotpy/tests/benchmarks/test_benchmarks.py Fatal Python error: Aborted


Package: src:plotpy
Version: 2.2.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with=python3 --with=numpy3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
[05/24/24 19:15:06] WARNING  pyproject.toml does not contain a setuptools.py:119
 tool.setuptools_scm section
WARNING  pyproject.toml does not contain a setuptools.py:119
 tool.setuptools_scm section
I: pybuild base:311: python3.11 setup.py config
[05/24/24 19:15:08] WARNING  pyproject.toml does not contain a setuptools.py:119
 tool.setuptools_scm section
WARNING  pyproject.toml does not contain a setuptools.py:119
 tool.setuptools_scm section
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
[05/24/24 19:15:10] WARNING  pyproject.toml does not contain a setuptools.py:119
 tool.setuptools_scm section
WARNING  pyproject.toml does not contain a setuptools.py:119
 tool.setuptools_scm section
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
is not valid for C++
In file included from ./src/pcolor.cpp:23:
./src/arrays.hpp:50:34: warning: ‘template struct std::iterator’ is deprecated 
[-Wdeprecated-declarations]
   50 | class iterator : public std::iterator
  |  ^~~~
In file included from /usr/include/c++/13/bits/stl_algobase.h:65,
 from /usr/include/c++/13/bits/specfun.h:43,
 from /usr/include/c++/13/cmath:3699,
 from /usr/include/c++/13/math.h:36,
 from /usr/include/python3.12/pyport.h:195,
 from /usr/include/python3.12/Python.h:38,
 from ./src/pcolor.cpp:6:
/usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here
  127 | struct _GLIBCXX17_DEPRECATED iterator
  |  ^~~~
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
is not valid for C++
In file included from ./src/scaler.cpp:37:
./src/arrays.hpp:50:34: warning: ‘template struct std::iterator’ is deprecated 
[-Wdeprecated-declarations]
   50 | class iterator : public std::iterator
  |  ^~~~
In file included from /usr/include/c++/13/bits/stl_algobase.h:65,
 from /usr/include/c++/13/bits/specfun.h:43,
 from /usr/include/c++/13/cmath:3699,
 from /usr/include/c++/13/math.h:36,
 from /usr/include/python3.12/pyport.h:195,
 from /usr/include/python3.12/Python.h:38,
 from ./src/scaler.cpp:6:
/usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here
  127 | struct _GLIBCXX17_DEPRECATED iterator
  |  ^~~~
I: pybuild base:311: /usr/bin/python3 setup.py build
[05/24/24 19:15:31] WARNING  pyproject.toml does not contain a setuptools.py:119
 tool.setuptools_scm section
[05/24/24 19:15:32] WARNING  pyproject.toml does not contain a setuptools.py:119
 tool.setuptools_scm section
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
is not valid for C++
In file included from ./src/pcolor.cpp:23:
./src/arrays.hpp:50:34: warning: ‘template struct std::iterator’ is deprecated 
[-Wdeprecated-declarations]
   50 | class iterator : public std::iterator
  |  ^~~~
In file included from /usr/include/c++/13/bits/stl_algobase.h:65,
 from /usr/include/c++/13/bits/specfun.h:43,
 from /usr/include/c++/13/cmath:3699,
 from /usr/include/c++/13/math.h:36,
 from /usr/include/python3.11/pyport.h:218,
 from /usr/include/python3.11/Python.h:38,
 from ./src/pcolor.cpp:6:
/usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here
  127 | struct _GLIBCXX17_DEPRECATED iterator
  |  ^~~~
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ 
is not valid for C++
In file included from ./src/scaler.cpp:37:
./src/arrays.hpp:50:34: warning: ‘template struct

Bug#1071773: node-socks-proxy-agent: FTBFS: error TS2305: Module '"agent-base"' has no exported member 'ClientRequest'.


Package: src:node-socks-proxy-agent
Version: 7.0.0+dfsg+~cs2.0.11-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
Link ./node_modules/agent-base -> /usr/share/nodejs/agent-base
Link ./node_modules/@types/debug -> /usr/share/nodejs/@types/debug
Link ./node_modules/socks -> /usr/share/nodejs/socks
Link node_modules/dns2 -> ../dns2
Link node_modules/socksv5 -> ../socksv5
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
Found debian/nodejs/./build
cd ./. && sh -ex debian/nodejs/./build
+ tsc
src/index.ts(2,17): error TS2305: Module '"agent-base"' has no exported member 
'ClientRequest'.
src/index.ts(2,32): error TS2305: Module '"agent-base"' has no exported member 
'RequestOptions'.
src/index.ts(3,10): error TS2305: Module '"agent-base"' has no exported member 
'AgentOptions'.
src/index.ts(121,14): error TS2515: Non-abstract class 'SocksProxyAgent' does 
not implement inherited abstract member 'connect' from class 'Agent'.
src/index.ts(129,11): error TS2345: Argument of type 'SocksProxyAgentOptions' 
is not assignable to parameter of type 'AgentOptions'.
  Types of property 'port' are incompatible.
Type 'string | number | null | undefined' is not assignable to type 'number 
| undefined'.
  Type 'null' is not assignable to type 'number | undefined'.
src/index.ts(159,30): error TS7006: Parameter 'err' implicitly has an 'any' 
type.
src/index.ts(159,35): error TS7006: Parameter 'res' implicitly has an 'any' 
type.
dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 
2
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

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

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

Thanks.

Bug#1071772: ktx: FTBFS: include/q_shared.h:101:8: error: conflicting types for ‘strlcpy’


Package: src:ktx
Version: 1.42+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --buildsystem=cmake
   dh_update_autotools_config -O--buildsystem=cmake
   dh_autoreconf -O--buildsystem=cmake
   dh_auto_configure -O--buildsystem=cmake
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 ..
-- The C 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
-- /<>/obj-x86_64-linux-gnu/game.q3asm
-- Configuring done (0.2s)
-- Generating done (0.0s)
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_FIND_USE_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_RUNSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
FETCHCONTENT_FULLY_DISCONNECTED


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
   dh_auto_build -O--buildsystem=cmake
cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install 
--strip-program=true" VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/qwprogs.dir/build.make CMakeFiles/qwprogs.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/qwprogs.dir/DependInfo.cmake "--color="
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/qwprogs.dir/build.make CMakeFiles/qwprogs.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  2%] Building C object CMakeFiles/qwprogs.dir/src/g_main.c.o
[  2%] Building C object CMakeFiles/qwprogs.dir/src/admin.c.o
/usr/bin/cc -DBOT_SUPPORT=1 -Dqwprogs_EXPORTS -I/<>/include -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -Wall -MD -MT CMakeFiles/qwprogs.dir/src/admin.c.o -MF CMakeFiles/qwprogs.dir/src/admin.c.o.d 
-o CMakeFiles/qwprogs.dir/src/admin.c.o -c /<>/src/admin.c
/usr/bin/cc -DBOT_SUPPORT=1 -Dqwprogs_EXPORTS -I/<>/include -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -Wall -MD -MT CMakeFiles/qwprogs.dir/src/g_main.c.o -MF CMakeFiles/qwprogs.dir/src/g_main.c.o.d 
-o CMakeFiles/qwprogs.dir/src/g_main.c.o -c /<>/src/g_main.c
In file included from /<>/include/g_local.h:31,
 from /<>/src/g_main.c:26:
/<>/include/q_shared.h:101:8: error: conflicting types for 
‘strlcpy’; have ‘size_t(char *, char *, size_t)’ {aka ‘long unsigned int(char *, char *, 
long unsigned int)’}
  101 | size_t strlcpy(char *dst, char *src, size_t siz);
  |^~~
In file included from /<>/include/g_local.h:31,
 from /<>/src/admin.c:2:
/<>/include/q_shared.h:101:8: error: conflicting types for 
‘strlcpy’; have ‘size_t(char *, char *, size_t)’ {aka ‘long unsigned int(char *, char *, 
long unsigned int)’}
  101 | size_t strlcpy(char *dst, char *src, size_t siz);
  |^~~
In file included from /usr/include/features.h:502,
 from /usr/include/assert.h:35,
 from /<>/include/q_shared.h:80:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:150:1: note: previous 
definition of ‘strlcpy’ with type ‘size_t(char * restrict,  const char * 
restrict,  size_t)’ {aka ‘long unsigned int(char * restrict,  const char * 
restrict,  long unsigned int)’}
  150 | __NTH (strlcpy (char *__restrict __dest, const char *__restrict __src,
  | ^
/<>/include/q_shared.h:102:8: error: conflicting types for

Bug#1071770: golang-github-protonmail-gluon: FTBFS: failing tests


Package: src:golang-github-protonmail-gluon
Version: 0.17.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --builddirectory=_build --buildsystem=golang
   dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
   dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
cp -r \
/usr/share/gocode/src/github.com/emersion/go-mbox \
/<>/_build/src/github.com/ProtonMail/go-mbox
while IFS="" read -r p || [ -n "$p" ]; do \
patch -uN -d /<>/_build/src/github.com/ProtonMail/go-mbox < 
/<>/debian/go-mbox-patches/"$p"; \
done < /<>/debian/go-mbox-patches/series
patching file reader.go

[... snipped ...]

=== RUN   TestParseDateTimeRejected
=== RUN   TestParseDateTimeRejected/Mon,_25_Sep_2017_5:25:40_+02
--- PASS: TestParseDateTimeRejected (0.00s)
--- PASS: TestParseDateTimeRejected/Mon,_25_Sep_2017_5:25:40_+02 (0.00s)
=== RUN   TestParseWord
--- PASS: TestParseWord (0.00s)
=== RUN   TestParsePhrase
--- PASS: TestParsePhrase (0.00s)
=== RUN   TestParseAddress
=== RUN   TestParseAddress/u...@example.com
=== RUN   TestParseAddress/John_Doe_
=== RUN   TestParseAddress/Mary_Smith_
=== RUN   TestParseAddress/"Joe_Q._Public"_
=== RUN   TestParseAddress/Mary_Smith_
=== RUN   TestParseAddress/j...@example.org
=== RUN   TestParseAddress/Who?_
=== RUN   TestParseAddress/
=== RUN   TestParseAddress/"Giant;_\"Big\"_Box"_
=== RUN   TestParseAddress/Pete_
=== RUN   TestParseAddress/"Mary_Smith:_Personal_Account"_
=== RUN   
TestParseAddress/Pete(A_nice_\)_chap)_
=== RUN   TestParseAddress/Gogh_Fir_
=== RUN   TestParseAddress/normal_name__
=== RUN   TestParseAddress/"comma,_name"__
=== RUN   TestParseAddress/name___(ignore_comment)
=== RUN   TestParseAddress/"Mail_Robot"_<>
=== RUN   TestParseAddress/Michal_Hořejšek_
=== RUN   TestParseAddress/First_Last_
=== RUN   TestParseAddress/First_Last_
=== RUN   TestParseAddress/First_Last_
=== RUN   TestParseAddress/First_Last_
=== RUN   TestParseAddress/First_Last_
=== RUN   TestParseAddress/
=== RUN   TestParseAddress/First_Last_<_u...@domain.com>
=== RUN   TestParseAddress/u...@domain.com,
=== RUN   TestParseAddress/First_Middle_"Last"_
=== RUN   TestParseAddress/First_Middle_Last_
=== RUN   TestParseAddress/First_Middle"Last"_
=== RUN   TestParseAddress/First_Middle_"Last"
=== RUN   TestParseAddress/First_"Middle"_"Last"_
=== RUN   TestParseAddress/First_"Middle""Last"_
=== RUN   TestParseAddress/first.last_
=== RUN   TestParseAddress/first_._last_
--- PASS: TestParseAddress (0.00s)
--- PASS: TestParseAddress/u...@example.com (0.00s)
--- PASS: TestParseAddress/John_Doe_ (0.00s)
--- PASS: TestParseAddress/Mary_Smith_ (0.00s)
--- PASS: TestParseAddress/"Joe_Q._Public"_ 
(0.00s)
--- PASS: TestParseAddress/Mary_Smith_ (0.00s)
--- PASS: TestParseAddress/j...@example.org (0.00s)
--- PASS: TestParseAddress/Who?_ (0.00s)
--- PASS: TestParseAddress/ (0.00s)
--- PASS: TestParseAddress/"Giant;_\"Big\"_Box"_ 
(0.00s)
--- PASS: TestParseAddress/Pete_ (0.00s)
--- PASS: 
TestParseAddress/"Mary_Smith:_Personal_Account"_ (0.00s)
--- PASS: 
TestParseAddress/Pete(A_nice_\)_chap)_ 
(0.00s)
--- PASS: TestParseAddress/Gogh_Fir_ (0.00s)
--- PASS: TestParseAddress/normal_name__ (0.00s)
--- PASS: TestParseAddress/"comma,_name"__ (0.00s)
--- PASS: TestParseAddress/name___(ignore_comment) 
(0.00s)
--- PASS: TestParseAddress/"Mail_Robot"_<> (0.00s)
--- PASS: TestParseAddress/Michal_Hořejšek_ (0.00s)
--- PASS: TestParseAddress/First_Last_ (0.00s)
--- PASS: TestParseAddress/First_Last_ (0.00s)
--- PASS: TestParseAddress/First_Last_ (0.00s)
--- PASS: TestParseAddress/First_Last_ (0.00s)
--- PASS: TestParseAddress/First_Last_ (0.00s)
--- PASS: TestParseAddress/ (0.00s)
--- PASS: TestParseAddress/First_Last_<_u...@domain.com> (0.00s)
--- PASS: TestParseAddress/u...@domain.com, (0.00s)
--- PASS: TestParseAddress/First_Middle_"Last"_ (0.00s)
--- PASS: TestParseAddress/First_Middle_Last_ (0.00s)
--- PASS: TestParseAddress/First_Middle"Last"_ (0.00s)
--- PASS: TestParseAddress/First_Middle_"Last" (0.00s)
--- PASS: TestParseAddress/First_"Middle"_"Last"_ (0.00s)
--- PASS: TestParseAddress/First_"Middle""Last"_ (0.00s)
--- PASS: TestParseAddress/first.last_ (0.00s)
--- PASS: TestParseAddress/first_._last_ (0.00s)
=== RUN   TestParseAddressList
=== RUN   
TestParseAddressList/Alice_,_Bob_,_Eve_
=== RUN   
TestParseAddressList/Alice_;_Bob_;_Eve_
=== RUN   
TestParseAddressList/Ed_Jones_,j...@where.test,John_
=== RUN

Bug#1071771: jupyter-ydoc: FTBFS: ImportError: Failed to import test module: jupyter_ydoc


Package: src:jupyter-ydoc
Version: 1.0.2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --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.12 with "build" 
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.12_jupyter-ydoc
* Building wheel...
Successfully built jupyter_ydoc-1.0.2-py3-none-any.whl
I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with 
"installer" module
I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" 
module
I: pybuild base:311: python3.11 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.11_jupyter-ydoc
* Building wheel...
Successfully built jupyter_ydoc-1.0.2-py3-none-any.whl
I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with 
"installer" module
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd 
/<>/.pybuild/cpython3_3.12_jupyter-ydoc/build; python3.12 -m 
unittest discover -v
jupyter_ydoc (unittest.loader._FailedTest.jupyter_ydoc) ... ERROR

==
ERROR: jupyter_ydoc (unittest.loader._FailedTest.jupyter_ydoc)
--
ImportError: Failed to import test module: jupyter_ydoc
Traceback (most recent call last):
  File "/usr/lib/python3.12/unittest/loader.py", line 427, in _find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
_get_module_from_name
__import__(name)
  File 
"/<>/.pybuild/cpython3_3.12_jupyter-ydoc/build/jupyter_ydoc/__init__.py",
 line 7, in 
from .yblob import YBlob  # noqa

  File 
"/<>/.pybuild/cpython3_3.12_jupyter-ydoc/build/jupyter_ydoc/yblob.py", 
line 8, in 
import y_py as Y
  File "/usr/lib/python3/dist-packages/y_py/__init__.py", line 1, in 
from .y_py import *
ModuleNotFoundError: No module named 'y_py.y_py'


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.12_jupyter-ydoc/build; python3.12 -m 
unittest discover -v
I: pybuild base:311: cd 
/<>/.pybuild/cpython3_3.11_jupyter-ydoc/build; python3.11 -m 
unittest discover -v

--
Ran 0 tests in 0.000s

OK
dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned 
exit code 13
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


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

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

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

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

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

Thanks.

Bug#1071769: golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.Err, not types.Bool


Package: src:golang-github-google-cel-go
Version: 0.12.5+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --builddirectory=build --buildsystem=golang --with=golang
   dh_update_autotools_config -O--builddirectory=build -O--buildsystem=golang
   dh_autoreconf -O--builddirectory=build -O--buildsystem=golang
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
mkdir -p -v build/src/github.com/google/cel-go/vendor
mkdir: created directory 'build'
mkdir: created directory 'build/src'
mkdir: created directory 'build/src/github.com'
mkdir: created directory 'build/src/github.com/google'
mkdir: created directory 'build/src/github.com/google/cel-go'
mkdir: created directory 'build/src/github.com/google/cel-go/vendor'
cp -v -a debian/missing-sources/* build/src/github.com/google/cel-go/vendor

[... snipped ...]

--- PASS: TestParse/135_? (0.00s)
--- PASS: TestParse/134_-- (0.00s)
--- PASS: TestParse/133_ind[a{b}] (0.00s)
--- PASS: TestParse/132_{:a} (0.00s)
--- PASS: TestParse/131_{a} (0.00s)
--- PASS: TestParse/130_msg{:a} (0.00s)
--- PASS: TestParse/129_func{{a}} (0.00s)
--- PASS: TestParse/128_[1,_2,_3].map(var,_var_*_var) (0.00s)
--- PASS: TestParse/127_while (0.00s)
--- PASS: TestParse/126_void (0.00s)
--- PASS: TestParse/125_var (0.00s)
--- PASS: TestParse/124_return (0.00s)
--- PASS: TestParse/123_namespace (0.00s)
--- PASS: TestParse/122_package (0.00s)
--- PASS: TestParse/121_loop (0.00s)
--- PASS: TestParse/120_let (0.00s)
--- PASS: TestParse/119_in (0.00s)
--- PASS: TestParse/118_import (0.00s)
--- PASS: TestParse/117_if (0.00s)
--- PASS: TestParse/116_function (0.00s)
--- PASS: TestParse/115_for (0.00s)
--- PASS: TestParse/114_else (0.00s)
--- PASS: TestParse/113_continue (0.00s)
--- PASS: TestParse/112_const (0.00s)
--- PASS: TestParse/93_x["a"].single_int32_==_23 (0.00s)
--- PASS: TestParse/110_as (0.00s)
--- PASS: TestParse/109___''_in_['',_'',_'']&&_in. (0.00s)
--- PASS: TestParse/108_""_in_["",_"",_""] (0.00s)
--- PASS: TestParse/107_"\a\b\f\n\r\t\v\'\"\\\?_Illegal_escape_\>" (0.00s)
--- PASS: TestParse/106_"\xFh" (0.00s)
--- PASS: TestParse/105_"\a\b\f\n\r\t\v'\"\\\?_Legal_escapes" (0.00s)
--- PASS: TestParse/104_"\U03A8\?" (0.00s)
--- PASS: TestParse/103_"hi\u263A_\u263Athere" (0.00s)
--- PASS: TestParse/102_"\303\277" (0.00s)
--- PASS: TestParse/101_"\xC3\XBF" (0.00s)
--- PASS: TestParse/100_{"a":_1}."a" (0.00s)
--- PASS: TestParse/99_"abc"_+_"def" (0.00s)
--- PASS: TestParse/98_1_+_+ (0.00s)
--- PASS: TestParse/97_1_+_2_*_3_-_1_/_2_==_6_%_1 (0.00s)
--- PASS: TestParse/96_b"abc"_+_B"def" (0.00s)
--- PASS: TestParse/95_false_&&_!true_||_false_?_2_:_3 (0.00s)
--- PASS: TestParse/94_x.single_nested_message_!=_null (0.00s)
--- PASS: TestParse/84_{1:2u,_2:3u} (0.00s)
--- PASS: TestParse/92_1.all(2,_3) (0.00s)
--- PASS: TestParse/91_[1,3,4][0] (0.00s)
--- PASS: TestParse/90_"\"" (0.00s)
--- PASS: TestParse/89_1_+_2_3_+ (0.00s)
--- PASS: TestParse/88_1_+_$ (0.00s)
--- PASS: TestParse/87_size(x)_==_x.size() (0.00s)
--- PASS: TestParse/86_TestAllTypes(){single_int32:_1,_single_int64:_2} 
(0.00s)
--- PASS: TestParse/85_TestAllTypes{single_int32:_1,_single_int64:_2} 
(0.00s)
--- PASS: TestParse/79_{foo:_5,_bar:_"xyz",_} (0.00s)
--- PASS: TestParse/83_[]_+_[1,2,3,]_+_[4] (0.00s)
--- PASS: TestParse/82_{ (0.00s)
--- PASS: TestParse/81_a_<_5_||_a_>_10 (0.00s)
--- PASS: TestParse/80_a_>_5_&&_a_<_10 (0.00s)
--- PASS: TestParse/77_[3,_4,_5,] (0.01s)
--- PASS: TestParse/78_{foo:_5,_bar:_"xyz"} (0.00s)
--- PASS: TestParse/76_[3,_4,_5] (0.00s)
--- PASS: TestParse/75_SomeMessage{foo:_5,_bar:_"xyz"} (0.00s)
--- PASS:

Bug#1071768: golang-github-github-smimesign: FTBFS: fakeca_test.go:178: exec: "openssl": executable file not found in $PATH


Package: src:golang-github-github-smimesign
Version: 0.2.0+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --builddirectory=_build --buildsystem=golang --with=golang
   dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
   dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
cd _build && go install -trimpath -v -p 2 
github.com/github/smimesign/ietf-cms github.com/github/smimesign/fakeca
internal/unsafeheader
internal/goarch
internal/cpu
internal/abi
internal/bytealg
internal/chacha8rand
internal/coverage/rtcov
internal/godebugs
internal/goexperiment
internal/goos
runtime/internal/atomic
runtime/internal/math
runtime/internal/sys
runtime/internal/syscall
internal/race
sync/atomic
runtime
unicode
unicode/utf8
math/bits
math
crypto/internal/alias
crypto/subtle
internal/itoa
crypto/internal/boring/sig
cmp
slices
unicode/utf16
vendor/golang.org/x/crypto/cryptobyte/asn1
internal/nettrace
container/list
vendor/golang.org/x/crypto/internal/alias
log/internal
internal/reflectlite
sync
internal/testlog
internal/bisect
errors
sort
io
bytes
hash
strconv
crypto/internal/randutil
internal/oserror
syscall
crypto
reflect
internal/syscall/unix
time
internal/poll
encoding/binary
internal/fmtsort
crypto/cipher
internal/safefilepath
internal/syscall/execenv
path
crypto/internal/boring
crypto/aes
crypto/des
io/fs
internal/godebug
math/rand
os
strings
crypto/internal/edwards25519/field
crypto/internal/nistec/fiat
fmt
math/big
embed
crypto/internal/nistec
crypto/ecdh
crypto/sha512
crypto/internal/edwards25519
crypto/dsa
crypto/elliptic
crypto/internal/bigmod
crypto/internal/boring/bbig
encoding/asn1
crypto/rand
crypto/ed25519
crypto/md5
crypto/rsa
vendor/golang.org/x/crypto/cryptobyte
crypto/sha1
crypto/ecdsa
crypto/sha256
encoding/hex
encoding/base64
crypto/x509/pkix
context
encoding/pem
vendor/golang.org/x/net/dns/dnsmessage
internal/singleflight
internal/intern
net/netip
runtime/cgo
net/url
path/filepath
bufio
compress/flate
hash/crc32
compress/gzip
crypto/hmac
crypto/rc4
vendor/golang.org/x/crypto/chacha20
vendor/golang.org/x/crypto/internal/poly1305
vendor/golang.org/x/sys/cpu
vendor/golang.org/x/crypto/chacha20poly1305
vendor/golang.org/x/crypto/hkdf
net
vendor/golang.org/x/text/transform
log
vendor/golang.org/x/text/unicode/bidi
vendor/golang.org/x/text/secure/bidirule
vendor/golang.org/x/text/unicode/norm
vendor/golang.org/x/net/idna
vendor/golang.org/x/net/http2/hpack
mime
mime/quotedprintable
net/http/internal
net/http/internal/ascii
os/exec
net/textproto
crypto/x509
vendor/golang.org/x/net/http/httpguts
vendor/golang.org/x/net/http/httpproxy
mime/multipart
github.com/github/smimesign/ietf-cms/oid
crypto/tls
github.com/github/smimesign/ietf-cms/protocol
github.com/github/smimesign/fakeca
net/http/httptrace
net/http
github.com/github/smimesign/ietf-cms/timestamp
github.com/github/smimesign/ietf-cms
   dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 2 
github.com/github/smimesign/ietf-cms github.com/github/smimesign/fakeca
=== RUN   TestSign
--- PASS: TestSign (0.00s)
=== RUN   TestSignDetached
--- PASS: TestSignDetached (0.00s)
=== RUN   TestSignDetachedWithOpenSSL
sign_test.go:110: could not find openssl in path
--- SKIP: TestSignDetachedWithOpenSSL (0.00s)
=== RUN   TestSignRemoveHeaders
--- PASS: TestSignRemoveHeaders (0.00s)
=== RUN   TestAddTimestamps
--- PASS: TestAddTimestamps (0.02s)
=== RUN   TestTimestampsVerifications
--- PASS: TestTimestampsVerifications (0.34s)
=== RUN   TestVerify
--- PASS: TestVerify (0.00s)
=== RUN   TestVerifyGPGSMAttached
--- PASS: TestVerifyGPGSMAttached (0.00s)
=== RUN   TestVerifyGPGSMDetached
--- PASS: TestVerifyGPGSMDetached (0.00s)
=== RUN   TestVerifyGPGSMNoCerts
--- PASS: TestVerifyGPGSMNoCerts (0.00s)
=== RUN   TestVerifyOpenSSLAttached
--- PASS: TestVerifyOpenSSLAttached (0.00s)
=== RUN   TestVerifyOpenSSLDetached
--- PASS: TestVerifyOpenSSLDetached (0.00s)
=== RUN   TestVerifyOutlookDetached
verify_test.go:142: x509: certificate signed by unknown authority
--- FAIL: TestVerifyOutlookDetached (0.00s)
=== RUN   TestVerifySmimesignAttachedWithTimestamp
verify_test.go:159: x509: certificate signed by unknown authority
--- FAIL: TestVerifySmimesignAttachedWithTimestamp (0.00s)
=== RUN   TestVerifyChain
--- PASS: TestVerifyChain (0.00s)
=== RUN   TestVerifyDSAWithSHA1
--- PASS: TestVerifyDSAWithSHA1 (0.00s)
FAIL
FAILgithub.com/github/smimesign/ietf-cms1.090s
=== RUN   TestDefaults
--- PASS: TestDefaults (0.19s)
=== RUN   TestIntermediate
--- PASS: TestIntermediate (0.47s)
=== RUN   TestSubject
--- PASS: TestSubject (0.18s)
===

Bug#1071082: Bug#1048703: NMU pushed to DELAYED/10

2024-05-24 Thread Pierre Gruet


Hello Martin,

Le 24/05/2024 à 15:58, Martin Quinson a écrit :

Hello Pierre,

many many thanks for the upload. You just did what I was supposed to do, thanks
for that. If you still have your PLM tree around, I'd appreciate if you could
push them to the salsa git too. If you don't have that, that's not a problem.
I'll try to fulfill my role at some point.


You're welcome! Glad I could help :)

I just pushed the changes to the Salsa repo!



Thanks again for your good work,
Mt


Have a great weekend,

--
Pierre


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071767: fpdf2: autopkgtest needs update for new version of pytest


Source: fpdf2
Version: 2.7.9-1
Severity: serious
X-Debbugs-CC: pyt...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pytest

Dear maintainer(s),

With a recent upload of pytest the autopkgtest of fpdf2 fails in testing 
when that autopkgtest is run with the binary packages of pytest from 
unstable. It passes when run with only packages from testing. In tabular 
form:


   passfail
pytest from testing8.1.2-1
fpdf2  from testing2.7.9-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of pytest to testing 
[1]. Of course, pytest shouldn't just break your autopkgtest (or even 
worse, your package), but given the nature of the package pytest, I 
suspect your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from pytest should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=pytest

https://ci.debian.net/data/autopkgtest/testing/amd64/f/fpdf2/46966995/log.gz

=== FAILURES 
===
263s __ test_multi_cell_split_only 
__

263s 263s def test_multi_cell_split_only():  # discussion 314
263s pdf = FPDF()
263s pdf.add_page()
263s pdf.set_font("Helvetica", size=TEXT_SIZE)
263s text = "Lorem ipsum Ut nostrud irure reprehenderit anim 
nostrud dolore sed ut"

263s expected = [
263s "Lorem ipsum Ut nostrud irure",
263s "reprehenderit anim nostrud",
263s "dolore sed ut",
263s ]
263s with pytest.warns(
263s DeprecationWarning, match='The parameter "split_only" 
is deprecated.'

263s ) as record:
263s assert (
263s pdf.multi_cell(w=0, h=LINE_HEIGHT, text=text, 
split_only=True) == expected

263s )
263s >   assert len(record) == 1
263s E   assert 2 == 1
263s E+  where 2 = len(WarningsChecker(record=True))
263s 263s test/text/test_multi_cell.py:267: AssertionError
263s === warnings summary 
===

263s test/image/test_vector_image.py::test_svg_image_no_viewbox
263s 
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:45: 
UserWarning:  has no "viewBox", using its "width" & "height" as 
default "viewBox"

263s img = pdf.image(SVG_SRCDIR / "simple_rect_no_viewbox.svg")
263s 263s 
test/image/test_vector_image.py::test_svg_image_with_custom_width_and_no_viewbox
263s 
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:75: 
UserWarning:  has no "viewBox", using its "width" & "height" as 
default "viewBox"

263s img = pdf.image(SVG_SRCDIR / "simple_rect_no_viewbox.svg", w=60)
263s 263s 
test/image/test_vector_image.py::test_svg_image_with_custom_size_and_no_viewbox
263s 
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:106: 
UserWarning:  has no "viewBox", using its "width" & "height" as 
default "viewBox"
263s img = pdf.image(SVG_SRCDIR / "simple_rect_no_viewbox.svg", 
x=50, y=50, w=30, h=60)
263s 263s 
test/image/test_vector_image.py::test_svg_image_style_inherited_from_fpdf
263s 
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:132: 
UserWarning:  has no "viewBox", using its "width" & "height" as 
default "viewBox"

263s pdf.image(
263s 263s test/image/test_vector_image.py::test_svg_image_from_bytesio
263s 
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:145: 
UserWarning:  has no "viewBox", using its "width" & "height" as 
default "viewBox"

263s pdf.image(
263s 263s test/image/test_vector_image.py::test_svg_image_from_bytes
263s 
/tmp/autopkgtest-lxc.vf1cnias/downtmp/build.w5B/src/test/image/test_vector_image.py:158: 
UserWarning:  has no "viewBox", using its "width" & "height" as 
default "viewBox"

263s pdf.image(
263s 263s 
test/table/test_table_extraction.py::test_camelot_extract_simple_table[table_simple.pdf-lattice]
263s 
test/table/test_table_extraction.py::test_camelot_extract_simple_table[table_with_images.pdf-lattice]
263s 
test/table/test_table_extraction.py::test_camelot_extract_simple_table[table_with_images_and_img_fill_width.pdf-lattice]
263s

Processed: fpdf2: autopkgtest needs update for new version of pytest

Processing control commands:

> affects -1 src:pytest
Bug #1071767 [src:fpdf2] fpdf2: autopkgtest needs update for new version of 
pytest
Added indication that 1071767 affects src:pytest

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

Processed: src:sccache: fails to migrate to testing for too long: FTBFS

Processing control commands:

> close -1 0.8.0-3
Bug #1071766 [src:sccache] src:sccache: fails to migrate to testing for too 
long: FTBFS
The source 'sccache' and version '0.8.0-3' do not appear to match any binary 
packages
Marked as fixed in versions sccache/0.8.0-3.
Bug #1071766 [src:sccache] src:sccache: fails to migrate to testing for too 
long: FTBFS
Marked Bug as done

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

Bug#1071766: src:sccache: fails to migrate to testing for too long: FTBFS


Source: sccache
Version: 0.7.7-1
Severity: serious
Control: close -1 0.8.0-3
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:sccache has been trying to migrate for 81 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build.


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Bug#1071283 marked as pending in freecad

Processing control commands:

> tag -1 pending
Bug #1071283 [freecad] src:freecad: FTBFS with opencascade 7.8.1
Ignoring request to alter tags of bug #1071283 to the same tags previously set

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

Bug#1071283: marked as pending in freecad

Control: tag -1 pending

Hello,

Bug #1071283 in freecad 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/science-team/freecad/-/commit/0c11c3043707dc5706bcfe1733796f7112e8c783


Fix FTBFS with opencascade 7.8.1 (Closes: #1071283), and B-D on new opencascade.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071283

Processed: src:kmod: fails to migrate to testing for too long: unresolved RC bug

Processing control commands:

> close -1 32-1
Bug #1071764 [src:kmod] src:kmod: fails to migrate to testing for too long: 
unresolved RC bug
Marked as fixed in versions kmod/32-1.
Bug #1071764 [src:kmod] src:kmod: fails to migrate to testing for too long: 
unresolved RC bug
Marked Bug as done

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

Bug#1071764: src:kmod: fails to migrate to testing for too long: unresolved RC bug


Source: kmod
Version: 31+20240202-2
Severity: serious
Control: close -1 32-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:kmod has been trying to migrate for 76 
days [2]. Hence, I am filing this bug. The version in unstable has an 
unresolved RC bug (it failed to build on buildds for armel and armhf).


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071643: horizon-eda: diff for NMU version 2.6.0-2.1

Control: tags 1071643 + pending


Dear maintainer,

I've prepared an NMU for horizon-eda (versioned as 2.6.0-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

(note: the previous patch was by accident reversed.)

Regards.

diff -Nru horizon-eda-2.6.0/debian/changelog horizon-eda-2.6.0/debian/changelog
--- horizon-eda-2.6.0/debian/changelog	2024-05-22 17:31:22.0 +0200
+++ horizon-eda-2.6.0/debian/changelog	2024-05-24 20:52:05.0 +0200
@@ -1,3 +1,10 @@
+horizon-eda (2.6.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS, add missing B-D on cppzmq-dev. Closes: #1071643
+
+ -- Tobias Frost   Fri, 24 May 2024 20:52:05 +0200
+
 horizon-eda (2.6.0-2) unstable; urgency=medium
 
   * Fix build depend
diff -Nru horizon-eda-2.6.0/debian/control horizon-eda-2.6.0/debian/control
--- horizon-eda-2.6.0/debian/control	2024-05-22 17:30:29.0 +0200
+++ horizon-eda-2.6.0/debian/control	2024-05-24 20:52:01.0 +0200
@@ -9,7 +9,7 @@
  libglm-dev, libgit2-dev, libcurl4-gnutls-dev, libocct-data-exchange-dev,
  libdxflib-dev (>> 3.17.0), libarchive-dev,
  libzip-dev, libglib2.0-dev, libpodofo-dev, python3-cairo-dev, libosmesa6-dev,
- dh-python
+ dh-python, cppzmq-dev
 Standards-Version: 4.4.0
 Homepage: https://horizon-eda.org/
 Rules-Requires-Root: no


signature.asc
Description: PGP signature

Processed: horizon-eda: diff for NMU version 2.6.0-2.1

Processing control commands:

> tags 1071643 + pending
Bug #1071643 [src:horizon-eda] horizon-eda: Missing build dependency on 
cppzmq-dev
Added tag(s) pending.

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

Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev

Source: horizon-eda
Followup-For: Bug #1071643

(patch attached now)


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

Kernel: Linux 6.8.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Naur horizon-eda-2.6.0/debian/control horizon-eda-2.6.0-bak/debian/control
--- horizon-eda-2.6.0/debian/control2024-05-24 20:14:57.641114565 +0200
+++ horizon-eda-2.6.0-bak/debian/control2024-05-24 20:14:28.444689829 
+0200
@@ -9,7 +9,7 @@
  libglm-dev, libgit2-dev, libcurl4-gnutls-dev, libocct-data-exchange-dev,
  libdxflib-dev (>> 3.17.0), libarchive-dev,
  libzip-dev, libglib2.0-dev, libpodofo-dev, python3-cairo-dev, libosmesa6-dev,
- dh-python, cppzmq-dev
+ dh-python
 Standards-Version: 4.4.0
 Homepage: https://horizon-eda.org/
 Rules-Requires-Root: no

Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev

Source: horizon-eda
Followup-For: Bug #1071643
Control: tags -1 patch

I can confirm that the version in sid FTBFS, and all that needs is adding
the B.D. (Trivial) patch attached.

To speed up the opencascade transistion, I'll NMU this in DELAYED/2.

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

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

Processed: Re: horizon-eda: Missing build dependency on cppzmq-dev

Processing control commands:

> tags -1 patch
Bug #1071643 [src:horizon-eda] horizon-eda: Missing build dependency on 
cppzmq-dev
Added tag(s) patch.

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

Processed: metadata

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

> # these bugs should not affect bookworm
> found 1071471 9.5.1-2
Bug #1071471 [src:deal.ii] src:deal.ii: FTBFS with opencascade 7.8
Marked as found in versions deal.ii/9.5.1-2.
> found 1071451 4.12.2+ds1-1
Bug #1071451 [src:gmsh] src:gmsh: FTBFS with new opencascade 7.8.1
Marked as found in versions gmsh/4.12.2+ds1-1.
> found 1071223 6.2.2401+dfsg1-1.1
Bug #1071223 [src:netgen] negen: Will FTBFS with next opencascade version 7.8.1
Marked as found in versions netgen/6.2.2401+dfsg1-1.1.
> found 1071470 2.6.1+dfsg-3
Bug #1071470 [src:slic3r-prusa] src:slic3r-prusa: FTBFS with opencasacade 7.8.1
Marked as found in versions slic3r-prusa/2.6.1+dfsg-3.
> thanks
Stopping processing here.

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

Bug#1071728: vzlogger: FTBFS: failing tests

2024-05-24 Thread Joachim Zobel

Am Freitag, dem 24.05.2024 um 12:29 +0200 schrieb Santiago Vila:
> 
>s0:Reading S0 - returning 2 readings (n=0 n_neg = 0)
> 
>s0:Reading S0 - returning 4 readings (n=0 n_neg = 0)
> ./tests/mocks/mock_MeterS0.cpp:174: Failure
> Value of: tdist >= 900 && tdist <= 1100
>Actual: false
> Expected: true
> tdist=5097
> 

This checks a duration, which is questionable in a test anyway.

I'll remove the assert.

Sincerely,
Joachim

Bug#1071759: firebird4.0 FTBFS with libre2-dev 20240501

2024-05-24 Thread Adrian Bunk

Source: firebird4.0
Version: 4.0.4.3010.ds6-3
Severity: serious
Tags: ftbfs patch
Forwarded: 
https://github.com/FirebirdSQL/firebird/commit/936e045d50f4f6632017e1cb0edea6ef960fc80c

https://buildd.debian.org/status/logs.php?pkg=firebird4.0=4.0.4.3010.ds6-3%2Bb1

...
In file included from /usr/include/absl/base/config.h:86,
 from /usr/include/absl/base/internal/invoke.h:40,
 from /usr/include/absl/base/call_once.h:34,
 from /usr/include/re2/re2.h:222,
 from /<>/src/common/../common/SimilarToRegex.h:25,
 from /<>/src/common/SimilarToRegex.cpp:22:
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less 
than C++14 are not supported."
   79 | #error "C++ versions less than C++14 are not supported."
  |  ^
...

Bug#1064492: marked as done (libdemeter-perl: Use of wxTB_3DBUTTONS crashes the Artemis GUI)

Your message dated Fri, 24 May 2024 16:50:11 +
with message-id 
and subject line Bug#1064492: fixed in libdemeter-perl 0.9.27+ds6-6
has caused the Debian Bug report #1064492,
regarding libdemeter-perl: Use of wxTB_3DBUTTONS crashes the Artemis GUI
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.)


-- 
1064492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdemeter-perl
Version: 0.9.27
Severity: grave
Tags: patch upstream
Justification: renders package unusable

when invoking the "dartemis" executable, it fails when trying to use
wxTB_3DBUTTONS from Wx::ToolBar.  This is in line 174 of the GDS.pm script.
Removal of wxTB_3DBUTTONS from line 174 allows dartemis to run correctly.

I think there is a more serious problem.  The most recent official release
is
0.9.26, not 0.9.27.  The fix suggested above reverts to the code in 0.9.26.
Perhaps, 0.9.26 should be the version used in the Debian package.

There is also an error in executing "dhephaestus".  It crashes with the
following error:

$ dhephaestus
Can't use an undefined value as an ARRAY reference at
/usr/share/perl5/Demeter/UI/Hephaestus/LineFinder.pm line 46.
Compilation failed in require at /usr/share/perl5/Demeter/UI/Hephaestus.pm
line
298.

As far as I can tell, there is no difference in either Hephaestus.pm or
LineFinder.pm in the two versions so the problem is more subtle.  In any
case,
version 0.9.26 runs without errors in trixie with the same version of libwx-
perl.

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

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

Versions of packages libdemeter-perl depends on:
ii  libarchive-zip-perl 1.68-1
ii  libcapture-tiny-perl0.48-2
ii  libchemistry-elements-perl  1.077-1
ii  libchemistry-formula-perl   3.0.1-1.3
ii  libconfig-ini-perl  1:0.029-1
ii  libconst-fast-perl  0.014-2
ii  libdatetime-perl2:1.59-1+b1
ii  libdigest-sha-perl  6.04-1+b1
ii  libencoding-fixlatin-perl   1.04-3
ii  libfile-copy-recursive-perl 0.45-4
ii  libfile-countlines-perl 0.0.3-4
ii  libfile-touch-perl  0.12-2
ii  libfile-which-perl  1.27-2
ii  libgraph-perl   1:0.9727-1
ii  libgraphics-gnuplotif-perl  1.8-2
ii  libheap-perl0.80-5
ii  libifeffit-perl 2:1.2.11d-12.5+b1
ii  libjson-perl4.1-1
ii  liblist-moreutils-perl  0.430-2
ii  libmath-combinatorics-perl  0.09-6
ii  libmath-derivative-perl 1.01-3
ii  libmath-random-free-perl0.2.0-2
ii  libmath-random-perl 0.72-2+b3
ii  libmath-round-perl  0.08-1
ii  libmath-spline-perl 0.02-4
ii  libmoose-perl   2.2207-1
ii  libmoosex-aliases-perl  0.11-2
ii  libmoosex-types-laxnum-perl 0.04-2
ii  libmoosex-types-perl0.50-2
ii  libpdl-stats-perl   0.83-1+b1
ii  libpod-pom-perl 2.01-4
ii  libregexp-assemble-perl 0.38-2
ii  libregexp-common-perl   2017060201-3
ii  librpc-xml-perl 0.82-1
ii  libspreadsheet-writeexcel-perl  2.40-4
ii  libstar-parser-perl 0.59-4
ii  libstatistics-descriptive-perl  3.0801-1
ii  libtext-template-perl   1.61-1
ii  libtext-unidecode-perl  1.30-3
ii  libtree-simple-perl 1.34-2
ii  libwant-perl0.29-2+b2
ii  libxmlrpc-lite-perl 0.717-5
ii  libxray-absorption-perl 3.0.1-4
ii  libxray-scattering-perl 3.0.1-3
ii  libyaml-tiny-perl   1.74-1
ii  pdl 1:2.085-1
ii  perl [libdigest-sha-perl]   5.38.2-3

libdemeter-perl recommends no packages.

libdemeter-perl suggests no packages.

-- no debconf information


-- 
Carlo U. Segre (he/him) -- Duchossois Leadership Professor of Physics
Professor of Materials Science & Engineering
Director, Center for Synchrotron Radiation Research and Instrumentation
Illinois Institute of Technology
Phone: 312.567.3498
se...@iit.edu   http://phys.iit.edu/~segre   se...@debian.org
--- End Message ---
--- Begin Message ---
Source: libdemeter-perl
Source-Version: 0.9.27+ds6-6

Bug#1071315: Partial patch

2024-05-24 Thread Roland Mas

Here's a partial patch that fixes the compilation-- but not the linking. 
I didn't manage to get the linking to work, but I'm sharing what I 
currently have.

Roland.
From: Roland Mas 
Date: Fri, 24 May 2024 16:01:50 +0200
Subject: Remove -pthread from hsc2hs invocation

---
 binoculars-ng/Makefile.am | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/binoculars-ng/Makefile.am b/binoculars-ng/Makefile.am
index ca255c1..5b2c5c7 100644
--- a/binoculars-ng/Makefile.am
+++ b/binoculars-ng/Makefile.am
@@ -18,7 +18,7 @@ AM_GHCFLAGS=\
 	-outputdir=$(builddir)/src

 .hsc.hs:
-	$(HSC2HS) $$(echo "$(AM_CFLAGS)" | sed "s%-ftrack-macro-expansion=0%%") -o $@ $<
+	$(HSC2HS) $$(echo "$(AM_CFLAGS)" | sed -e "s%-ftrack-macro-expansion=0%%" -e "s%-pthread%%") -o $@ $<

 .hs.o:
 	$(GHC) --make $(AM_GHCFLAGS) -c -o $@ $<

Bug#1071749: bidentd: Cannot work with current kernels - remove?

2024-05-24 Thread Chris Hofstaedtler

Source: bidentd
Version: 1.1.4-1.2
Severity: serious

Inspection of the source reveals bidentd uses /proc/net/ip_conntrack
and/or /proc/net_ip_masquerade to identify connections.
These files have long been removed from Linux.

I believe bidentd thus cannot work at all and propose its removal.

I'm filing with sev: serious, because it's been a really really long
time already since when bidentd could have become useful, and IMO we
should not have it in trixie.

Chris

Bug#1071365: marked as done (srpc: FTBFS: src/compress/rpc_compress_snappy.cc:112:37: error: call of overloaded ‘Compress(srpc::RPCSnappySource, srpc::RPCSnappySink)’ is ambiguous)

Your message dated Fri, 24 May 2024 14:45:05 +
with message-id 
and subject line Bug#1071365: fixed in srpc 0.10.2-2
has caused the Debian Bug report #1071365,
regarding srpc: FTBFS: src/compress/rpc_compress_snappy.cc:112:37: error: call 
of overloaded ‘Compress(srpc::RPCSnappySource*, srpc::RPCSnappySink*)’ is 
ambiguous
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.)


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

Package: src:srpc
Version: 0.10.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary  --buildsystem=cmake
   dh_update_autotools_config -O--buildsystem=cmake
   dh_autoreconf -O--buildsystem=cmake
   dh_auto_configure -O--buildsystem=cmake
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 ..
-- 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
-- Looking for lz4.h
-- Looking for lz4.h - found
-- Looking for C++ include snappy.h
-- Looking for C++ include snappy.h - found
-- Looking for C++ include workflow/Workflow.h
-- Looking for C++ include workflow/Workflow.h - found
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "3.2.2")
-- Found Protobuf: /usr/lib/x86_64-linux-gnu/libprotobuf.so (found suitable version 
"3.21.12", minimum required is "3.5.0")
-- Configuring done (1.1s)
-- Generating done (0.0s)
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
FETCHCONTENT_FULLY_DISCONNECTED


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
   dh_auto_build -O--buildsystem=cmake
cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install 
--strip-program=true" VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/LINK_HEADERS.dir/build.make 
CMakeFiles/LINK_HEADERS.dir/depend
make  -f src/generator/CMakeFiles/srpc_generator.dir/build.make 
src/generator/CMakeFiles/srpc_generator.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/LINK_HEADERS.dir/DependInfo.cmake "--color="
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/src/generator /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src/generator 
/<>/obj-x86_64-linux-gnu/src/generator/CMakeFiles/srpc_generator.dir/DependInfo.cmake "--color="
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/LINK_HEADERS.dir/build.make 
CMakeFiles/LINK_HEADERS.dir/build
make  -f src/generator/CMakeFiles/srpc_generator.dir/build.make 
src/generator/CMakeFiles/srpc_generator.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -E make_directory /<>/_include/srpc
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  2%] Building CXX object 
src/generator/CMakeFiles/srpc_generator.dir/compiler.cc.o
/usr/bin/cmake -E

Bug#1071082: Bug#1048703: NMU pushed to DELAYED/10

2024-05-24 Thread Martin Quinson

Hello Pierre,

many many thanks for the upload. You just did what I was supposed to do, thanks
for that. If you still have your PLM tree around, I'd appreciate if you could
push them to the salsa git too. If you don't have that, that's not a problem.
I'll try to fulfill my role at some point.

Thanks again for your good work,
Mt

Le mercredi 22 mai 2024 à 23:08 +0200, Pierre Gruet a écrit :
> Dear Maintainer,
> 
> I have just uploaded fixes for bugs 1048703 and 1071082 to DELAYED/10.
> This is to prevent testing autoremoval of plm on June, 11th.
> 
> Enclosed is the source debdiff of this NMU. It is strictly based upon 
> the patches I submitted in the two bug logs.
> 
> Please tell me if I should delay or cancel the foreseen NMU.
> 
> Best wishes,
> 
> -- 
> Pierre



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

Processed: Bug#1071283 marked as pending in freecad

Processing control commands:

> tag -1 pending
Bug #1071283 [freecad] src:freecad: FTBFS with opencascade 7.8.1
Added tag(s) pending.

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

Bug#1071283: marked as pending in freecad

Control: tag -1 pending

Hello,

Bug #1071283 in freecad 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/science-team/freecad/-/commit/767e64b8eebe4765b134cd2c294b9db541c5bf32


Add patch for opencascade 7.8.x

Gbp-Dch: Closes: #1071283


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071283

Processed: Bug#1071723 marked as pending in pam-p11

Processing control commands:

> tag -1 pending
Bug #1071723 [src:pam-p11] pam-p11: FTBFS: configure.ac:70: error: possibly 
undefined macro: AC_MSG_ERROR
Added tag(s) pending.

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

Bug#1071723: marked as pending in pam-p11

2024-05-24 Thread Bastian Germann

Control: tag -1 pending

Hello,

Bug #1071723 in pam-p11 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/opensc-team/pam-p11/-/commit/10dcbd98f1f40acf4b69a21d24bbdba9d6f1285a


Add Build-Depends: pkgconf (Closes: #1071723)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071723

Processed: Opencascade transition starts now

Processing control commands:

> severity -1 serious
Bug #1071471 [src:deal.ii] src:deal.ii: FTBFS with opencascade 7.8
Severity set to 'serious' from 'important'

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

Processed: Opencascade transition starts now

Processing control commands:

> severity -1 serious
Bug #1071470 [src:slic3r-prusa] src:slic3r-prusa: FTBFS with opencasacade 7.8.1
Severity set to 'serious' from 'important'

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

Processed: Opencascade transition starts now

Processing control commands:

> severity -1 serious
Bug #1071451 [src:gmsh] src:gmsh: FTBFS with new opencascade 7.8.1
Severity set to 'serious' from 'important'

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

Processed: Opencascade transition starts now

Processing control commands:

> severity -1 serious
Bug #1071223 [src:netgen] negen: Will FTBFS with next opencascade version 7.8.1
Severity set to 'serious' from 'important'

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

Bug#1070677: fail2ban fails: "Failed during configuration: Have not found any log file for sshd jail"

2024-05-24 Thread Sylvestre Ledru

Le 24/05/2024 à 14:25, Vincent Lefevre a écrit :

On 2024-05-07 08:35:28 +0200, Sylvestre Ledru wrote:

Le 07/05/2024 à 03:57, Vincent Lefevre a écrit :

On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:

May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban
[557228]: ERROR Failed during configuration: Have not found any
log file for sshd jail

I suppose that this is because sshd no longer uses the systemd
backend. This is wrong. If I understand correctly, the point of

https://github.com/fail2ban/fail2ban/issues/3292#issuecomment-2078361360

is to no longer use the systemd backend for all jails, but for
sshd only. So "backend = systemd" has been removed from DEFAULT,
but the above comment also points to

https://github.com/fail2ban/fail2ban/commit/85a4881a9a818b6a746109f74980919296eedad0

which adds for DEFAULT in paths-debian.conf:

banaction = nftables
banaction_allports = nftables[type=allports]

sshd_backend = systemd

But paths-debian.conf has not changed in the fail2ban 1.1.0-1 package.

ok, thanks.

Any idea what the fix should be? I am a bit lost in this conversation :/

For the sshd issue (mainly this bug), upstream changed 2 visible
things in the above commit:

* It changed default's "backend = systemd" to "sshd_backend = systemd"
with the reason:

remove default backend (systemd) - too dangerous for all jails,
because it's hardly to find an error if some jail mistakenly start
to monitor journal instead of logfile (even if it exists), but will
silently find nothing

Indeed, using systemd as the backend for all jails by default may
yield silent breakage for services that do not use syslog for logging
(this is not like this had already been the default backend).

* It disabled the sshd jail by default.

What you did in

https://salsa.debian.org/python-team/packages/fail2ban/-/commit/c03b1a832132f8033a6c698650daba9c48e22c62

is that the following lines are removed.

[DEFAULT]
banaction = nftables
banaction_allports = nftables[type=allports]
backend = systemd

(leaving the sshd jail enabled, contrary to upstream's Debian files).

Since the sshd jail is still enabled but its backend is now the
default backend, it will use a syslog log file (/var/log/auth.log
if this has not changed), which doesn't exist if rsyslog is not
installed. Said otherwise, the following bugs are back:

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

(you fixed them in

https://salsa.debian.org/python-team/packages/fail2ban/-/commit/e634fa863e2d8035181e9e03476ae6dd56044fe6

on 2024-01-02 by the "backend = systemd", but reverted them
in c03b1a832132f8033a6c698650daba9c48e22c62).

There are several (non-exclusive) solutions:

1. Do not enable the sshd jail by default, following upstream's
decision, and let the user decide whether he should change the
backend for sshd when he enables the sshd jail.

The side effects after an upgrade:
* The sshd jail may no longer be enabled (i.e. if the user hasn't
explicitly enabled it in jail.local). So this will need to be
announced.
* If it is still enabled (due to jail.local), this solution alone
(without (2) or (3)) will not fix the problem.

2. Add "sshd_backend = systemd" like upstream, so that the sshd jail
will use the systemd backend.

A possible side effect after an upgrade from stable: this will
break for users who do not use systemd (but contrary to the default
"backend = systemd" issue, this should not be a silent breakage,
because fail2ban should be able to detect that the systemd logs
are not available at all - not tested, though).

3. Recommend the rsyslog package (or "rsyslog | system-log-daemon").
This would ensure that any backend will work, but would add another
daemon and additional log files (note that rsyslog is OK, but I don't
know whether the other log daemons are compatible with fail2ban's
default rules).

Moreover, I don't know why you removed the

banaction = nftables
banaction_allports = nftables[type=allports]

from [DEFAULT]. This was about a "switch from iptables to nftables"
as said at

https://github.com/fail2ban/fail2ban/discussions/3575

Indeed, iptables is not always installed by default, while nftables
seems to be installed by the Debian installer (in any case, iptables
recommends nftables). So, I suppose that these lines would still be
necessary.

About the other services that log to the journal via syslog, things
like "postfix_backend = systemd" (as done in paths-arch.conf and
paths-opensuse.conf) may be useful, but since the associated jails are
not enabled by default in Debian, this will change nothing by default.

Salut Vincent, Merci pour ce retour!

Could you please propose a PR ? I didn't find the time to fix this
lately (and i don't use

Processed: Opencascade transition starts now

Processing control commands:

> severity -1 serious
Bug #1071283 [freecad] src:freecad: FTBFS with opencascade 7.8.1
Severity set to 'serious' from 'important'

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

Bug#1070677: fail2ban fails: "Failed during configuration: Have not found any log file for sshd jail"

2024-05-24 Thread Vincent Lefevre

On 2024-05-07 08:35:28 +0200, Sylvestre Ledru wrote:
> 
> Le 07/05/2024 à 03:57, Vincent Lefevre a écrit :
> > On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:
> > > May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 
> > > fail2ban[557228]: ERROR   Failed during configuration: 
> > > Have not found any log file for sshd jail
> > I suppose that this is because sshd no longer uses the systemd
> > backend. This is wrong. If I understand correctly, the point of
> > 
> > https://github.com/fail2ban/fail2ban/issues/3292#issuecomment-2078361360
> > 
> > is to no longer use the systemd backend for all jails, but for
> > sshd only. So "backend = systemd" has been removed from DEFAULT,
> > but the above comment also points to
> > 
> > https://github.com/fail2ban/fail2ban/commit/85a4881a9a818b6a746109f74980919296eedad0
> > 
> > which adds for DEFAULT in paths-debian.conf:
> > 
> > 
> > banaction = nftables
> > banaction_allports = nftables[type=allports]
> > 
> > sshd_backend = systemd
> > 
> > 
> > But paths-debian.conf has not changed in the fail2ban 1.1.0-1 package.
> > 
> ok, thanks.
> 
> Any idea what the fix should be? I am a bit lost in this conversation :/

For the sshd issue (mainly this bug), upstream changed 2 visible
things in the above commit:

* It changed default's "backend = systemd" to "sshd_backend = systemd"
  with the reason:

remove default backend (systemd) - too dangerous for all jails,
because it's hardly to find an error if some jail mistakenly start
to monitor journal instead of logfile (even if it exists), but will
silently find nothing

  Indeed, using systemd as the backend for all jails by default may
  yield silent breakage for services that do not use syslog for logging
  (this is not like this had already been the default backend).

* It disabled the sshd jail by default.

What you did in

https://salsa.debian.org/python-team/packages/fail2ban/-/commit/c03b1a832132f8033a6c698650daba9c48e22c62

is that the following lines are removed.

[DEFAULT]
banaction = nftables
banaction_allports = nftables[type=allports]
backend = systemd

(leaving the sshd jail enabled, contrary to upstream's Debian files).

Since the sshd jail is still enabled but its backend is now the
default backend, it will use a syslog log file (/var/log/auth.log
if this has not changed), which doesn't exist if rsyslog is not
installed. Said otherwise, the following bugs are back:

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

(you fixed them in

https://salsa.debian.org/python-team/packages/fail2ban/-/commit/e634fa863e2d8035181e9e03476ae6dd56044fe6

on 2024-01-02 by the "backend = systemd", but reverted them
in c03b1a832132f8033a6c698650daba9c48e22c62).

There are several (non-exclusive) solutions:

1. Do not enable the sshd jail by default, following upstream's
decision, and let the user decide whether he should change the
backend for sshd when he enables the sshd jail.

The side effects after an upgrade:
  * The sshd jail may no longer be enabled (i.e. if the user hasn't
explicitly enabled it in jail.local). So this will need to be
announced.
  * If it is still enabled (due to jail.local), this solution alone
(without (2) or (3)) will not fix the problem.

2. Add "sshd_backend = systemd" like upstream, so that the sshd jail
will use the systemd backend.

A possible side effect after an upgrade from stable: this will
break for users who do not use systemd (but contrary to the default
"backend = systemd" issue, this should not be a silent breakage,
because fail2ban should be able to detect that the systemd logs
are not available at all - not tested, though).

3. Recommend the rsyslog package (or "rsyslog | system-log-daemon").
This would ensure that any backend will work, but would add another
daemon and additional log files (note that rsyslog is OK, but I don't
know whether the other log daemons are compatible with fail2ban's
default rules).

Moreover, I don't know why you removed the

banaction = nftables
banaction_allports = nftables[type=allports]

from [DEFAULT]. This was about a "switch from iptables to nftables"
as said at

  https://github.com/fail2ban/fail2ban/discussions/3575

Indeed, iptables is not always installed by default, while nftables
seems to be installed by the Debian installer (in any case, iptables
recommends nftables). So, I suppose that these lines would still be
necessary.

About the other services that log to the journal via syslog, things
like "postfix_backend = systemd" (as done in paths-arch.conf and
paths-opensuse.conf) may be useful, but since the associated jails are
not enabled by default in Debian, this will change nothing by default.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML -

Bug#1071737: r-cran-data.table: autopkgtest regression on armhf

2024-05-24 Thread Graham Inggs

Source: r-cran-data.table
Version: 1.15.4+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

r-cran-data.table's autopkgtest has regressed on armhf [1].  I've
copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-data.table/unstable/armhf/


103s Test 2226.3 ran without errors but failed check that x equals y:
103s > x = DT[, prod(x, na.rm = TRUE), g]
103s g V1 [Key= Types=int,dou Classes=int,i64]
103s 1: 1 
103s 2: 2 
103s 3: 3 -8
103s > y = data.table(g = 1:3, V1 = as.integer64(c(NA,
"9223372036854775807", -8L)))
103s g V1 [Key= Types=int,dou Classes=int,i64]
103s 1: 1 
103s 2: 2 9223372036854775807
103s 3: 3 -8
103s Column 'V1': 'is.NA' value mismatch: 2 in current 1 in target
104s
104s Fri May 10 10:48:14 2024 endian==little, sizeof(long double)==8,
longdouble.digits==, sizeof(pointer)==4, TZ==unset,
Sys.timezone()=='Etc/UTC',
Sys.getlocale()=='LC_CTYPE=C.UTF-8;LC_NUMERIC=C;LC_TIME=C.UTF-8;LC_COLLATE=C.UTF-8;LC_MONETARY=C.UTF-8;LC_MESSAGES=C.UTF-8;LC_PAPER=C.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=C.UTF-8;LC_IDENTIFICATION=C',
l10n_info()=='MBCS=TRUE; UTF-8=TRUE; Latin-1=FALSE; codeset=UTF-8',
getDTthreads()=='OpenMP version (_OPENMP)==201511;
omp_get_num_procs()==16; R_DATATABLE_NUM_PROCS_PERCENT==unset (default
50); R_DATATABLE_NUM_THREADS==unset; R_DATATABLE_THROTTLE==unset
(default 1024); omp_get_thread_limit()==2147483647;
omp_get_max_threads()==16; OMP_THREAD_LIMIT==unset;
OMP_NUM_THREADS==unset; RestoreAfterFork==true; data.table is using 8
threads with throttle==1024. See ?setDTthreads.', zlibVersion()==1.3
ZLIB_VERSION==1.3
104s Error: 1 error(s) out of 9678. Search tests/tests.Rraw.bz2 for
test number(s) 2226.3. Duration: 30.5s elapsed (31.4s cpu).
104s Execution halted

Processed: notfound 1068190 in telegram-desktop/4.14.9+ds-1, notfound 1070302 in telegram-desktop/4.14.9+ds-1

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

> notfound 1068190 telegram-desktop/4.14.9+ds-1
Bug #1068190 {Done: Andrey Rakhmatullin } 
[src:telegram-desktop] telegram-desktop: FTBFS with abseil 20230802: 
(.text+0x270): undefined reference to 
`absl::debian3::base_internal::ThrowStdOutOfRange(char const*)'
No longer marked as found in versions telegram-desktop/4.14.9+ds-1.
> notfound 1070302 telegram-desktop/4.14.9+ds-1
Bug #1070302 {Done: Andrey Rakhmatullin } [telegram-desktop] 
Not installable (depends on removed libabsl20220623t64)
No longer marked as found in versions telegram-desktop/4.14.9+ds-1.
> thanks
Stopping processing here.

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

Bug#1071037: marked as done (v4l2loopback-dkms: module fails to build for i386: ERROR: modpost: "__moddi3" undefined!)

Your message dated Fri, 24 May 2024 11:39:52 +
with message-id 
and subject line Bug#1071037: fixed in v4l2loopback 0.13.2-1
has caused the Debian Bug report #1071037,
regarding v4l2loopback-dkms: module fails to build for i386: ERROR: modpost: 
"__moddi3" undefined!
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.)


-- 
1071037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: v4l2loopback-dkms
Version: 0.13.1-1
Severity: serious

DKMS make.log for v4l2loopback-0.13.1 for kernel 6.7.12-686-pae (i686)
Mon May 13 09:57:13 UTC 2024

++ To sign the  module, you must set KBUILD_SIGN_KEY/KBUILD_SIGN_CERT to 
point to the signing key/certificate!
++ For your convenience, we try to read these variables as 
'mok_signing_key' resp. 'mok_certificate' from /etc/dkms/framework.conf

++ If your certificate requires a password, pass it via the KBUILD_SIGN_PIN 
env-var!
++ E.g. using 'export KBUILD_SIGN_PIN; read -s -p "Passphrase for signing 
key : " KBUILD_SIGN_PIN; sudo --preserve-env=KBUILD_SIGN_PIN make sign'

Building v4l2-loopback driver...
make -C /lib/modules/6.7.12-686-pae/build 
M=/var/lib/dkms/v4l2loopback/0.13.1/build KCPPFLAGS="" modules
make[1]: Entering directory '/usr/src/linux-headers-6.7.12-686-pae'
  CC [M]  /var/lib/dkms/v4l2loopback/0.13.1/build/v4l2loopback.o
  MODPOST /var/lib/dkms/v4l2loopback/0.13.1/build/Module.symvers
ERROR: modpost: "__moddi3" 
[/var/lib/dkms/v4l2loopback/0.13.1/build/v4l2loopback.ko] undefined!
make[3]: *** 
[/usr/src/linux-headers-6.7.12-common/scripts/Makefile.modpost:145: 
/var/lib/dkms/v4l2loopback/0.13.1/build/Module.symvers] Error 1
make[2]: *** [/usr/src/linux-headers-6.7.12-common/Makefile:1888: modpost] 
Error 2
make[1]: *** [/usr/src/linux-headers-6.7.12-common/Makefile:246: __sub-make] 
Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.7.12-686-pae'
make: *** [Makefile:53: v4l2loopback.ko] Error 2


This probably affects more 32-bit architectures ...

IIRC gcc generates a __moddi3 function call for
(long long) a % (long long) b
(or a similar operation on long long) on architectures without native
support for long long. The symbol is provided by libgcc_s but for
obvious reasons the kernel cannot be linked agaist that library.

This seems to be a regression from the v4l2loopback-dkms +
linux-headers-* combination in bookworm.

This problem does not appear during the autopkgtest since that is
restricted to amd64 and arm64 (which is probably a copy+paste mistake as
the commit references bbswitch-dkms which is only useful on platforms
with the proprietary nvidia driver and thus restricted to these
architectures).


Andreas
--- End Message ---
--- Begin Message ---
Source: v4l2loopback
Source-Version: 0.13.2-1
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
v4l2loopback package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 24 May 2024 12:58:14 +0200
Source: v4l2loopback
Architecture: source
Version: 0.13.2-1
Distribution: unstable
Urgency: medium
Maintainer: IOhannes m zmölnig (Debian/GNU) 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1071037
Changes:
 v4l2loopback (0.13.2-1) unstable; urgency=medium
 .
   * New upstream version 0.13.2 (Closes: #1071037)
 + Drop patches applied ustream
   * Update copyright information
 + Re-generate d/copyright_hints
   * Bump standards version to 4.7.0
Checksums-Sha1:
 268f0aff5e97f140330bdaed41af74d7a01cf021 2375 v4l2loopback_0.13.2-1.dsc
 81a127ca0895c430ef67db89619f5348763a32e9 84819 v4l2loopback_0.13.2.orig.tar.gz
 6b31457e6ba5fcca51238e01f4673aa877ab6c75 9396 
v4l2loopback_0.13.2-1.debian.tar.xz
Checksums-Sha256:
 a133920eeda553cc11855a3888735caf4c5730c6196b4890d13210bd286569fa 2375 
v4l2loopback_0.13.2-1.dsc

Bug#1071735: libxmlrpc-util-dev and libxmlrpc-util4 have an undeclared file conflict

2024-05-24 Thread Helmut Grohne

Package: libxmlrpc-util4,libxmlrpc-util-dev
Version: 1.59.03-2+b1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libxmlrpc-core-c3-dev libxmlrpc-core-c3t64

libxmlrpc-util-dev and libxmlrpc-util4 have an undeclared file conflict.
This may result in an unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/libxmlrpc_util.a
 * /usr/lib/x86_64-linux-gnu/libxmlrpc_util.so
are contained in the packages
 * libxmlrpc-core-c3-dev
   * 1.33.14-11 as present in bookworm
   * 1.33.14-9 as present in bullseye
 * libxmlrpc-util-dev/1.59.03-2+b1 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libxmlrpc_util.a
 * /usr/lib/x86_64-linux-gnu/libxmlrpc_util.so
 * /usr/lib/x86_64-linux-gnu/pkgconfig/xmlrpc_util.pc
are contained in the packages
 * libxmlrpc-core-c3-dev/1.59.03-1+b1 as present in trixie
 * libxmlrpc-util-dev/1.59.03-2+b1 as present in unstable

The files
 * /usr/lib/x86_64-linux-gnu/libxmlrpc_util.so.4
 * /usr/lib/x86_64-linux-gnu/libxmlrpc_util.so.4.59
are contained in the packages
 * libxmlrpc-core-c3t64/1.59.03-1+b1 as present in trixie
 * libxmlrpc-util4/1.59.03-2+b1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Processed: libxmlrpc-util-dev and libxmlrpc-util4 have an undeclared file conflict

Processing control commands:

> affects -1 + libxmlrpc-core-c3-dev libxmlrpc-core-c3t64
Bug #1071735 [libxmlrpc-util4,libxmlrpc-util-dev] libxmlrpc-util-dev and 
libxmlrpc-util4 have an undeclared file conflict
Added indication that 1071735 affects libxmlrpc-core-c3-dev and 
libxmlrpc-core-c3t64

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

Bug#1071734: libsingular4m4n0 has an undeclared file conflict

2024-05-24 Thread Helmut Grohne

Package: libsingular4m4n0
Version: 1:4.4.0+ds-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libsingular4m3n0t64

libsingular4m4n0 has an undeclared file conflict. This may result in an
unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/libsingular-factory-4.4.0.so
 * /usr/lib/x86_64-linux-gnu/libsingular-omalloc-4.4.0+ds+0.9.6.so
 * /usr/lib/x86_64-linux-gnu/libsingular-polys-4.4.0.so
 * /usr/lib/x86_64-linux-gnu/libsingular-resources-4.4.0.so
 * /usr/lib/x86_64-linux-gnu/libsingular-Singular-4.4.0.so
are contained in the packages
 * libsingular4m3n0t64/1:4.4.0+ds-1 as present in trixie|unstable
 * libsingular4m4n0/1:4.4.0+ds-3 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Processed: libsingular4m4n0 has an undeclared file conflict