Bug#1076614: libcamljava-ocaml-dev lost its OCaml Depends+Provides
Package: libcamljava-ocaml-dev Version: 0.3-3 Severity: serious Package: libcamljava-ocaml-dev Version: 0.3-2+b1 Provides: libcamljava-ocaml-dev-o0rt3 Depends: ocaml-nox-4.05.0, default-jdk These are now gone (except for the default-jdk).
Bug#1076026: elpa: FTBFS with mpich as default MPI on i386: FAIL validate_complex_2stage_banded_default.sh (exit status: 15)
On Tue, Jul 09, 2024 at 07:41:11PM +0200, Sebastian Ramacher wrote: > Source: elpa > Version: 2022.11.001-3 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org >... > GetSockInterfaceAddr(369)..: gethostbyname failed, x86-conova-02 > (errno 4) > Fatal error in internal_Init: Other MPI error, error stack: > internal_Init(48301)...: MPI_Init(argc=(nil), argv=(nil)) failed >... Regarding this error that seems to happen with elpa and mpi4py (and arpack?) on some buildds only: Is it possible that mpich has a problem when no IPV4 is available? I have no idea if I am looking at the right place, but I wonder whether something like for example src/mpi/romio/mpl/src/sock/mpl_sockaddr.c:static int af_type = AF_INET; is the problem? cu Adrian
Bug#1076407: rust-oo7: autopkgtest regression
Source: rust-oo7
Version: 0.3.3-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-oo7/48952368/log.gz
...
147s error: You can't enable both async-std & tokio features at once
147s --> src/lib.rs:5:1
147s |
147s 5 | compile_error!("You can't enable both async-std & tokio features at
once");
147s |
^^
147s
147s error[E0659]: `generate_private_key` is ambiguous
147s --> src/key.rs:43:27
147s|
147s 43 | Self::new(crypto::generate_private_key().to_vec())
147s| ambiguous name
147s|
147s= note: ambiguous because of multiple glob imports of a name in the
same module
...
604s autopkgtest [22:53:55]: summary
604s rust-oo7:@ FAIL non-zero exit status 101
604s librust-oo7-dev:async-std FLAKY non-zero exit status 101
604s librust-oo7-dev:default PASS
604s librust-oo7-dev:local_tests FLAKY non-zero exit status 101
604s librust-oo7-dev:native_crypto FLAKY non-zero exit status 101
604s librust-oo7-dev:openssl_crypto FLAKY non-zero exit status 101
604s librust-oo7-dev:tokio FLAKY non-zero exit status 101
604s librust-oo7-dev:tracing FLAKY non-zero exit status 101
604s librust-oo7-dev:unstable FLAKY non-zero exit status 101
604s librust-oo7-dev: FLAKY non-zero exit status 101
Bug#1076234: (no subject)
On Sun, Jul 14, 2024 at 02:18:13PM +0300, Adrian Bunk wrote: >... > lammps built with the rebuilt lammps, >... This was meant to say: lammps did build with the rebuilt mpi4py cu Adrian
Bug#1076234: (no subject)
Control: reassign -1 src:mpi4py Control: notfixed 1075980 3.1.6-2 Control: fixed 1075980 3.1.6-6 Control: forcemerge 1075980 -1 Control: affcts 1075980 src:lammps On Sat, Jul 13, 2024 at 07:28:54PM +0200, Drew Parsons wrote: > Subject: Re: lammps: FTBFS with mpich as default MPI provider on armel, > armhf: Fatal error in internal_Comm_set_errhandler: Invalid communicator > Followup-For: Bug #1076234 > Package: lammps > Control: tags -1 ftbfs > > This looks like a bug in libfakeroot rather than lammps. The libfakeroot message is a red herring, it's also in precious successful builds. lammps built with the rebuilt lammps, the "Invalid communicator" error message likely indicated that something using openmpi was trying to communicate with something using mpich. cu Adrian
Bug#1076306: rust-hypothesis: autopkgtest failure
Source: rust-hypothesis Version: 0.11.5-3 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-hypothesis/48932500/log.gz ... 182s 182s running 5 tests 182s test add_and_delete_annotation ... FAILED 182s test create_and_leave_group ... FAILED 182s test search_annotations ... FAILED 182s test update_group ... FAILED 182s test update_annotation ... FAILED 182s 182s failures: 182s 182s add_and_delete_annotation stdout 182s Error: path not found 182s 182s Caused by: 182s path not found 182s 182s Location: 182s tests/cli.rs:33:5 182s 182s create_and_leave_group stdout 182s Error: path not found 182s 182s Caused by: 182s path not found 182s 182s Location: 182s tests/cli.rs:177:5 182s 182s search_annotations stdout 182s Error: path not found 182s 182s Caused by: 182s path not found 182s 182s Location: 182s tests/cli.rs:114:5 182s 182s update_group stdout 182s Error: environment variable not found 182s 182s Caused by: 182s environment variable not found 182s 182s Location: 182s tests/cli.rs:213:20 182s 182s update_annotation stdout 182s Error: path not found 182s 182s Caused by: 182s path not found 182s 182s Location: 182s tests/cli.rs:69:5 182s 182s 182s failures: 182s add_and_delete_annotation 182s create_and_leave_group 182s search_annotations 182s update_annotation 182s update_group 182s 182s test result: FAILED. 0 passed; 5 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s 182s 182s error: test failed, to rerun pass `--test cli` 182s autopkgtest [15:18:48]: test rust-hypothesis-0.11:@: ---] 183s autopkgtest [15:18:49]: test rust-hypothesis-0.11:@: - - - - - - - - - - results - - - - - - - - - - 183s rust-hypothesis-0.11:@ FAIL non-zero exit status 101 ... 358s autopkgtest [15:21:44]: summary 358s rust-hypothesis-0.11:@ FAIL non-zero exit status 101 358s rust-hypothesis-0.11: PASS 358s rust-hypothesis-0.11:default FAIL non-zero exit status 101 358s rust-hypothesis-0.11:cli FAIL non-zero exit status 101
Bug#1076289: skimage FTBFS on mips64el: test failures
Source: skimage
Version: 0.23.2-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Ole Streicher
https://buildd.debian.org/status/logs.php?pkg=skimage=mips64el
...
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_periodic_reference[float16]
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_periodic_reference[float32]
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_periodic_reference[float64]
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_fixed_reference[float32]
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_fixed_reference[float64]
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_free_reference[float32]
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_free_reference[float64]
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_RGB[float32]
FAILED
skimage/segmentation/tests/test_active_contour_model.py::test_RGB[float64]
FAILED skimage/segmentation/tests/test_active_contour_model.py::test_end_points
FAILED skimage/transform/tests/test_geometric.py::test_estimate_affine_3d[False]
FAILED skimage/transform/tests/test_geometric.py::test_estimate_affine_3d[True]
FAILED
skimage/transform/tests/test_thin_plate_splines.py::TestThinPlateSplineTransform::test_call_on_SRC
FAILED
skimage/transform/tests/test_thin_plate_splines.py::TestThinPlateSplineTransform::test_rotate
= 14 failed, 8628 passed, 120 skipped, 17 xfailed, 12 xpassed in 613.12s
(0:10:13) =
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.12/build; python3.12 -m pytest
dh_auto_test: error: pybuild --test -i python{version} -p "3.11 3.12" returned
exit code 13
make: *** [debian/rules:31: binary-arch] Error 25
Bug#1076281: quickemu is not installable on armel/armhf
Package: quickemu Version: 4.9.2-1 Severity: serious https://tracker.debian.org/pkg/quickemu ... Issues preventing migration: ∙ ∙ quickemu/armel has unsatisfiable dependency ∙ ∙ quickemu/armhf has unsatisfiable dependency The following packages have unmet dependencies: quickemu : Depends: libtss2-tcti-swtpm0 but it is not installable This should be libtss2-tcti-swtpm0t64 instead.
Bug#1076280: python3-meep: Missing dependency on python3-matplotlib
Package: python3-meep Version: 1.25.0-2 Severity: serious $ python3 Python 3.11.2 (main, May 2 2024, 11:59:08) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import meep Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/meep/__init__.py", line 4242, in from .simulation import ( File "/usr/lib/python3/dist-packages/meep/simulation.py", line 44, in from matplotlib.axes import Axes ModuleNotFoundError: No module named 'matplotlib' >>> $ This was caught by the autopkgtest.
Bug#1076279: pcb-rnd: Package dependencies must be librnd4t64, not librnd4
Source: pcb-rnd Version: 3.1.5-1 Severity: serious X-Debbugs-Cc: Bdale Garbee Issues preventing migration: ∙ ∙ pcb-rnd-auto/armel has unsatisfiable dependency ∙ ∙ pcb-rnd-export/armel has unsatisfiable dependency ∙ ∙ pcb-rnd-import-net/armel has unsatisfiable dependency ∙ ∙ pcb-rnd-lib-io/armel has unsatisfiable dependency ∙ ∙ pcb-rnd-auto/armhf has unsatisfiable dependency ∙ ∙ pcb-rnd-export/armhf has unsatisfiable dependency ∙ ∙ pcb-rnd-import-net/armhf has unsatisfiable dependency ∙ ∙ pcb-rnd-lib-io/armhf has unsatisfiable dependency librnd4t64 provides librnd4 only on the architectures where no ABI change was done for 64bit time_t.
Bug#1076272: libdolfin-dev-common: binary-all package encoding default MPI in cmake files
Package: libdolfin-dev-common
Version: 2019.2.0~legacy20240219.1c52e83-9
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Alastair McKinstry
Control: affects -1 src:dolfinx-mpc src:mshr
/usr/share/dolfin/cmake/DOLFINTargets.cmake: INTERFACE_INCLUDE_DIRECTORIES
"/usr/lib/python3/dist-packages/ffc/backends/ufc;/usr/include/eigen3;/usr/include/hdf5/openmpi;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/openmpi/include;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/openmpi/include/openmpi"
/usr/share/dolfin/cmake/DOLFINTargets.cmake: INTERFACE_LINK_LIBRARIES
"Boost::boost;Boost::timer;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/hdf5/openmpi/libhdf5.so;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/libcrypto.so;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/libcurl.so;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/libsz.so;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/libz.so;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/libdl.a;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/libm.so;SLEPC::slepc;PETSC::petsc;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/openmpi/lib/libmpi_cxx.so;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/openmpi/lib/libmpi.so"
/usr/share/dolfin/cmake/DOLFINTargets.cmake:
INTERFACE_SYSTEM_INCLUDE_DIRECTORIES
"/usr/lib/python3/dist-packages/ffc/backends/ufc;/usr/include/eigen3;/usr/include/hdf5/openmpi;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/openmpi/include;/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/openmpi/include/openmpi"
The package must become binary-any if it encodes the MPI used
at build time (which does now differ between 64bit and 32bit
architectures).
Bug#1076204: python3-bjdata: C extension silently not built with recent numpy
Package: python3-bjdata Version: 0.2.6-2 Severity: serious Tags: patch Forwarded: https://github.com/fangq/pybj/commit/a46355a0b0df0bec1817b04368a5a573358645ef X-Debbugs-Cc: Stefano Rivera https://buildd.debian.org/status/fetch.php?pkg=pybj=amd64=0.2.6-2%2Bb1=1720780666=0 ... 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/usr/include/python3.12 -c src/decoder.c -o build/temp.linux-x86_64-cpython-312/src/decoder.o -std=c99 -DUSE__BJDATA src/decoder.c:20:10: fatal error: numpy/arrayobject.h: No such file or directory 20 | #include | ^ compilation terminated. ...
Bug#1076148: libpmix2t64: libpmix.so.2: cannot open shared object file: No such file or directory
Package: libpmix2t64
Version: 5.0.3-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:dolfinx-mpc
https://buildd.debian.org/status/fetch.php?pkg=dolfinx-mpc=amd64=0.8.0.post1-4%2Bb1=1720703948=0
...
[x86-csail-01:562901] mca_base_component_repository_open: unable to open
mca_pmix_ext3x: libpmix.so.2: cannot open shared object file: No such file or
directory (ignored)
...
This needs updating to 2.12.3:
$ cat debian/libpmix2t64.links
/usr/lib/${DEB_HOST_MULTIARCH}/pmix2/lib/libpmix.so.2.13.2
/usr/lib/${DEB_HOST_MULTIARCH}/libpmix.so.2
/usr/lib/${DEB_HOST_MULTIARCH}/pmix2/lib/libpmix.so.2.13.2
/usr/lib/${DEB_HOST_MULTIARCH}/libpmix.so.2.13.2
$
Bug#1076119: neuron-dev should depend on mpi-default-dev, not libopenmpi-dev
Package: neuron-dev Version: 8.2.2-6 Severity: serious neuron builds with mpi-default-dev, but neuron-dev depends on mpi-default-dev. This is now wrong on 32bit architectures, which have switched from openmpi to mpich ass default. Please change the dependency of neuron-dev to mpi-default-dev.
Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"
On Tue, Jul 09, 2024 at 10:34:43AM -0500, Dirk Eddelbuettel wrote: > > Adrian, Hi Dirk, > Will the patch to configure.ac, with the build system as it is, ensure > autoconf is called or should I do that manually and hence also patch > configure? just add the patch. The autoreconf sequence is enabled by default since debhelper compat 10, and the package uses compat 13. > Dirk cu Adrian
Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"
Control: tags -1 patch
On Mon, Jul 08, 2024 at 03:30:17PM -0500, Dirk Eddelbuettel wrote:
>
> On 8 July 2024 at 22:09, Sebastian Ramacher wrote:
> | Source: rmpi
> | Version: 0.7-2-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=rmpi=armel=0.7-2-1%2Bb2=1720427935=0
> |
> | checking if pkg-config knows about OpenMPI... no
> | 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 mpi.h... no
> | configure: error: "Cannot find mpi.h header file"
> | ERROR: configuration failed for package ‘Rmpi’
> | * removing ‘/<>/debian/r-cran-rmpi/usr/lib/R/site-library/Rmpi’
> | dh_auto_install: error: R CMD INSTALL -l
> /<>/debian/r-cran-rmpi/usr/lib/R/site-library --clean
> --no-test-load . "--built-timestamp='Mon, 08 Jul 2024 08:38:43 +'"
> returned exit code 1
> | make: *** [debian/rules:7: binary-arch] Error 25
>
> :-/
>
> R no linger supports i386 (and other 32 bt arches) upstream.
Neither does Open MPI, and the current transition to MPICH on 32bit is
the relevant change that broke it.
The good news is that rmpi does support MPICH, it only uses a very
manual way when trying to find it - and that fails.
The attached patch adds a pkg-config search to configure.ac
(similar to what was already added for Open MPI above).
> Dirk
cu
Adrian
Description: Try to find mpich with pkg-config if pkg-config did not find openmpi
Author: Adrian Bunk
--- rmpi-0.7-2.orig/configure.ac
+++ rmpi-0.7-2/configure.ac
@@ -96,6 +96,11 @@ if test -z "$MPI_ROOT" ; then
fi
if test -z "$MPI_ROOT" ; then
+ #Use pkg-config to find mpich
+ PKG_CHECK_MODULES([MPICH],[mpich],[MPITYPE="MPICH" MPI_ROOT="NONEED"],[:])
+fi
+
+if test -z "$MPI_ROOT" ; then
for d in /opt/lib /usr/lib /usr /usr/lib/x86_64-linux-gnu/openmpi \
/usr/local/lib /usr/local /usr/lib64/mpi/gcc/openmpi; do
if test -f $d/include/mpi.h && test -d $d/lib/openmpi; then
@@ -303,7 +308,12 @@ case "$MPITYPE" in
PKG_LIBS="-L${MPI_LIBPATH} -lmpi -llam ${MPI_LIBS}"
;;
MPICH)
-PKG_LIBS="-L${MPI_LIBPATH} -lmpich -lmpl -lopa ${MPI_LIBS}"
+if test "$MPI_ROOT" = "NONEED"; then
+ PKG_CPPFLAGS="${MPICH_CFLAGS}"
+ PKG_LIBS="${MPICH_LIBS}"
+else
+ PKG_LIBS="-L${MPI_LIBPATH} -lmpich -lmpl -lopa ${MPI_LIBS}"
+fi
;;
MPICH2)
PKG_LIBS="-L${MPI_LIBPATH} -lmpich -lmpl -lopa ${MPI_LIBS}"
Bug#1075985: libfftw3-mpi3 might be misbuilt with MPICH as default
Package: libfftw3-mpi3
Version: 3.3.10-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Alastair McKinstry
https://buildd.debian.org/status/fetch.php?pkg=fftw3=i386=3.3.10-1%2Bb3=1720426229=0
...
./configure --enable-single --build i686-linux-gnu F77="gfortran -ff2c"
--prefix=/usr --enable-shared --enable-threads --enable-openmp --enable-mpi
--libdir=\${prefix}/lib/i386-linux-gnu MPILIBS="" --enable-sse --enable-avx
...
dh_shlibdeps -a
dpkg-shlibdeps: warning: symbol MPI_Comm_split used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_dup used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Bcast used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_size used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Alltoall used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_free used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Allreduce used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Abort used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_rank used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Alltoallv used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: 4 other similar warnings have been skipped (use -v to
see them all)
dpkg-shlibdeps: warning: symbol MPI_Sendrecv used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Alltoallv used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_rank used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Abort used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_f2c used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Send used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Recv used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Bcast used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_size used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_dup used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: 4 other similar warnings have been skipped (use -v to
see them all)
dpkg-shlibdeps: warning: symbol MPI_Alltoallv used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Abort used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_rank used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_f2c used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Send used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Sendrecv used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Recv used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_split used by
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_dup used by
Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8
Control: forwarded -1 https://gitlab.com/plastimatch/plastimatch/-/commit/a1a6f4da5681735544db1239ddd3d01066ce10d8 Control: tags -1 patch On Fri, Jul 05, 2024 at 11:19:57AM +0200, Mathieu Malaterre wrote: > Source: plastimatch > Version: 1.9.4+dfsg.1-2 > Severity: serious > Tags: ftbfs > > /<>/src/plastimatch/base/dcmtk_rtss.cxx: In member > function ‘void Dcmtk_rt_study::rtss_save(const char*)’: > /<>/src/plastimatch/base/dcmtk_rtss.cxx:475:46: error: > ‘DCM_ROIObservationLabel’ was not declared in this scope; did you mean > ‘DCM_ObservationNumber’? > 475 | rtroio_item->putAndInsertString (DCM_ROIObservationLabel, > | ^~~ > | DCM_ObservationNumber > > https://people.debian.org/~emollier/transitions/dcmtk/plastimatch_dcmtk.build.xz > > It has been retired: > > % cat dcmdata/include/dcmtk/dcmdata/dcdeftag.h | grep 3006 | grep 85 > #define DCM_RETIRED_ROIObservationLabel DcmTagKey(0x3006, 0x0085) The commit above (applied to src/plastimatch/base/dcmtk_rtss.cxx) firxes the build. cu Adrian
Bug#1075965: libmpich-dev: libucx-dev dependency must not be unconditional
Package: libmpich-dev Version: 4.2.0-7 Severity: serious Tags: ftbfs X-Debbugs-Cc: Alastair McKinstry hpcc build-depends on: - mpi-default-dev:armhf mpi-default-dev depends on: - libmpich-dev:armhf libmpich-dev depends on missing: - libucx-dev:armhf Before it was dropped by accident, the libucx-dev followed the build dependency: libucx-dev [amd64 ppc64el arm64] BTW: Unrelated (perhaps for experimental): Should libucx-dev also be used on riscv64, where it is now available?
Bug#1075916: libdcmtk-dev: Removed dependencies are required for a CMake target
On Mon, Jul 08, 2024 at 08:23:57AM +0200, Mathieu Malaterre wrote: > Control: reassign -1 liborthancframework-dev > > On Sun, Jul 7, 2024 at 9:48 PM Adrian Bunk wrote: > > > > Package: libdcmtk-dev > > Version: 3.6.8-5 > > Severity: serious > > Tags: ftbfs > > Control: affects -1 src:orthanc-neuro > > > > https://buildd.debian.org/status/logs.php?pkg=orthanc-neuro=1.1%2Bdfsg-1%2Bb1 > > > > ... > > [ 90%] Linking CXX shared library libOrthancNeuro.so > > /usr/bin/cmake -E cmake_link_script CMakeFiles/OrthancNeuro.dir/link.txt > > --verbose=1 > > /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. > > -fstack-protector-strong -fstack-clash-protection -Wformat > > -Werror=format-security -fcf-protection -DNDEBUG -Wdate-time > > -D_FORTIFY_SOURCE=2 -Wall -Wno-long-long -Wno-variadic-macros -Wl,-z,relro > > -Wl,-z,now -Wl,--no-undefined -Wl,--as-needed > > -Wl,--version-script=/<>/Resources/Orthanc/Plugins/VersionScriptPlugins.map > > -shared -Wl,-soname,libOrthancNeuro.so.1.1 -o libOrthancNeuro.so.1.1 > > CMakeFiles/OrthancNeuro.dir/Sources/Plugin/Plugin.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Plugin/PluginFrameDecoder.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/BufferReader.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/CSAHeader.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/CSATag.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/DicomInstancesCollection.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/IDicomFrameDecoder.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/InputDicomInstance.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/NeuroToolbox.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/NiftiWriter.cpp.o > > CMakeFiles/OrthancNeuro.dir/Sources/Framework/Slice.cpp.o > > CMakeFiles/OrthancNeuro.dir/AUTOGENERATED/EmbeddedResources.cpp.o > > CMakeFiles/OrthancNeuro.dir/Resources/Orthanc/Plugins/OrthancPluginCppWrapper.cpp.o > > -lpthread -lrt -ldl -Wl,-Bstatic -lOrthancFramework -Wl,-Bdynamic > > -ldcmdata -ldcmjpls -ldcmimage -ldcmjpeg -lofstd -lboost_filesystem > > -lboost_iostreams -lboost_locale -lboost_regex -lboost_thread -lpugixml > > -luuid -ljsoncpp -lpng -ljpeg -lz -lniftiio -lznz -lrt -ldl -Wl,-Bstatic > > -lOrthancFramework -Wl,-Bdynamic -ldcmdata -ldcmjpls -ldcmimage -ldcmjpeg > > -lofstd -lboost_filesystem -lboost_iostreams -lboost_locale -lboost_regex > > -lboost_thread -lpugixml -luuid -ljsoncpp -lpng -ljpeg -lz -lniftiio -lznz > > /usr/bin/ld: cannot find -lpng: No such file or directory > > /usr/bin/ld: cannot find -ljpeg: No such file or directory > > /usr/bin/ld: cannot find -lpng: No such file or directory > > /usr/bin/ld: cannot find -ljpeg: No such file or directory > > collect2: error: ld returned 1 exit status > > make[3]: *** [CMakeFiles/OrthancNeuro.dir/build.make:300: > > libOrthancNeuro.so.1.1] Error 1 > > > > > > > > dcmtk (3.6.8-4) experimental; urgency=medium > > ... > > * d/control: Reduce number of dependencies for -dev package > > > > > > That's problematic when the CMake files require them for some target: > > /usr/lib/x86_64-linux-gnu/cmake/dcmtk/DCMTKTargets.cmake: > > INTERFACE_LINK_LIBRARIES > > "DCMTK::oflog;DCMTK::dcmdata;DCMTK::dcmimgle;/usr/lib/x86_64-linux-gnu/libtiff.so;/usr/lib/x86_64-linux-gnu/libjpeg.so;/usr/lib/x86_64-linux-gnu/libpng.so" > > > > Here is what I have no my side: > > % grep tiff /usr/lib/x86_64-linux-gnu/cmake/dcmtk/DCMTKTargets.cmake > -> nothing > > since I manually simplified it to: > > [...] > INTERFACE_LINK_LIBRARIES "DCMTK::oflog;DCMTK::dcmdata;DCMTK::dcmimgle" > [...] I see your point that orthanc-neuro is the bigger problem here, I am less sure how many of the 3 packages involved are considered buggy. > Rebuilding orthanc-neuro with this new cmake file *still* triggers the > exact same symptoms. I suspect it is dues to orthanc-neuro d/rules: > > [...] > "-DORTHANC_FRAMEWORK_ADDITIONAL_LIBRARIES=dcmdata [...] png jpeg > [...] > > Fundamentally I believe the real linking error should occur with the > static libs: > > % nm /usr/lib/gcc/x86_64-linux-gnu/13/../../../../lib/libOrthancFramework.a >... Dependencies for static linking are a mess, we do not usually have them in place since static linking is not recommended in most cases. orthanc-neuro builds and links with the shared library when I remove the -DORTHANC_FRAMEWORK_USE_SHARED:BOOL=OFF, is there any reason why this would not work? > Thanks, cu Adrian
Bug#1074483: dcmtk: CVE-2024-27628
Control: tags -1 patch
On Sat, Jun 29, 2024 at 04:44:43PM +0200, Salvatore Bonaccorso wrote:
>...
> The following vulnerability was published for dcmtk.
>
> CVE-2024-27628[0]:
> | Buffer Overflow vulnerability in DCMTK v.3.6.8 allows an attacker to
> | execute arbitrary code via the EctEnhancedCT method component.
>
>
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2024-27628
> https://www.cve.org/CVERecord?id=CVE-2024-27628
> [1] https://support.dcmtk.org/redmine/issues/1108
> [2]
> https://github.com/DCMTK/dcmtk/commit/ec52e99e1e33fc39810560421c0833b02da567b3
>...
Attached is this patch for 3.6.8 (no conflicts during rebasing).
The new test fails without the fix and passes with the fix,
no regressions during the build test.
The actual code fix is pretty small (and not ABI breaking),
most of the patch is test code.
cu
Adrian
>From 855ee5eacad12b4ef39d36a78c9c24d038c4a231 Mon Sep 17 00:00:00 2001
From: Michael Onken
Date: Tue, 20 Feb 2024 10:50:28 +0100
Subject: Fixed possible overflows when allocating memory.
Thanks to GitHub user "bananabr" (Daniel Berredo) for the report and
suggested patch.
---
dcmect/libsrc/enhanced_ct.cc | 14 +-
dcmect/tests/CMakeLists.txt | 1 +
dcmect/tests/Makefile.dep| 151 +++
dcmect/tests/Makefile.in | 4 +-
dcmect/tests/t_overflow.cc | 362 +++
dcmect/tests/tests.cc| 3 +-
6 files changed, 531 insertions(+), 4 deletions(-)
create mode 100644 dcmect/tests/t_overflow.cc
diff --git a/dcmect/libsrc/enhanced_ct.cc b/dcmect/libsrc/enhanced_ct.cc
index 619374290..47d6335f0 100644
--- a/dcmect/libsrc/enhanced_ct.cc
+++ b/dcmect/libsrc/enhanced_ct.cc
@@ -24,6 +24,7 @@
#include "dcmtk/dcmect/types.h"
#include "dcmtk/dcmfg/concatenationcreator.h"
#include "dcmtk/dcmfg/concatenationloader.h"
+#include "dcmtk/dcmfg/fgtypes.h"
#include "dcmtk/dcmiod/iodutil.h"
#include "dcmtk/dcmiod/modimagepixel.h"
@@ -100,8 +101,19 @@ struct EctEnhancedCT::WriteVisitor
m_CT.getRows(rows);
m_CT.getColumns(cols);
const size_t numFrames = m_CT.m_Frames.size();
+if (numFrames > 2147483647)
+{
+DCMECT_ERROR("More than 2147483647 frames provided");
+return FG_EC_PixelDataTooLarge;
+}
+const size_t numPixelsFrame = OFstatic_cast(size_t, rows) * OFstatic_cast(size_t, cols);
const size_t numBytesFrame = m_CT.m_Frames[0]->length;
-const size_t numPixelsFrame = rows * cols;
+if (numBytesFrame != numPixelsFrame * 2)
+{
+DCMECT_ERROR("Invalid number of bytes per frame: Expected " << numPixelsFrame * 2 << " but got "
+ << numBytesFrame << " frame pixel data");
+return ECT_InvalidPixelInfo;
+}
// Creates the correct pixel data element, based on the image pixel module used.
DcmPixelData* pixData = new DcmPixelData(DCM_PixelData);
OFCondition result;
diff --git a/dcmect/tests/CMakeLists.txt b/dcmect/tests/CMakeLists.txt
index 5d66b1145..032553414 100644
--- a/dcmect/tests/CMakeLists.txt
+++ b/dcmect/tests/CMakeLists.txt
@@ -2,6 +2,7 @@
DCMTK_ADD_EXECUTABLE(dcmect_tests
tests.cc
t_huge_concat.cc
+ t_overflow.cc
t_roundtrip.cc
)
diff --git a/dcmect/tests/Makefile.dep b/dcmect/tests/Makefile.dep
index 9d26f581c..dfb50b812 100644
--- a/dcmect/tests/Makefile.dep
+++ b/dcmect/tests/Makefile.dep
@@ -192,6 +192,157 @@ t_huge_concat.o: t_huge_concat.cc \
../../dcmfg/include/dcmtk/dcmfg/fgrealworldvaluemapping.h \
../../dcmiod/include/dcmtk/dcmiod/iodcontentitemmacro.h \
../../dcmfg/include/dcmtk/dcmfg/fgtemporalposition.h
+t_overflow.o: t_overflow.cc ../../config/include/dcmtk/config/osconfig.h \
+ ../include/dcmtk/dcmect/enhanced_ct.h ../include/dcmtk/dcmect/def.h \
+ ../../ofstd/include/dcmtk/ofstd/ofexport.h \
+ ../include/dcmtk/dcmect/types.h ../../oflog/include/dcmtk/oflog/oflog.h \
+ ../../oflog/include/dcmtk/oflog/logger.h \
+ ../../oflog/include/dcmtk/oflog/config.h \
+ ../../ofstd/include/dcmtk/ofstd/ofdefine.h \
+ ../../ofstd/include/dcmtk/ofstd/ofcast.h \
+ ../../ofstd/include/dcmtk/ofstd/ofstdinc.h \
+ ../../oflog/include/dcmtk/oflog/config/defines.h \
+ ../../oflog/include/dcmtk/oflog/helpers/threadcf.h \
+ ../../oflog/include/dcmtk/oflog/loglevel.h \
+ ../../ofstd/include/dcmtk/ofstd/ofvector.h \
+ ../../ofstd/include/dcmtk/ofstd/oftypes.h \
+ ../../ofstd/include/dcmtk/ofstd/ofstream.h \
+ ../../oflog/include/dcmtk/oflog/tstring.h \
+ ../../ofstd/include/dcmtk/ofstd/ofstring.h \
+ ../../oflog/include/dcmtk/oflog/tchar.h \
+ ../../oflog/include/dcmtk/oflog/spi/apndatch.h \
+ ../../oflog/include/dcmtk/oflog/appender.h \
+ ../../ofstd/include/dcmtk/ofstd/ofmem.h \
+ ../../ofstd/include/dcmtk/ofstd/ofutil.h \
+
Bug#1028172: libmpich-dev lost dependencies needed for pkg-config
Control: found -1 4.2.0-6 Control: affects -1 src:hpcc On Tue, Jan 10, 2023 at 12:39:07PM +, Debian Bug Tracking System wrote: >... > Maintainer: Debian Science Maintainers > > Changed-By: Alastair McKinstry > Closes: 1028172 > Changes: > mpich (4.0.2-3) unstable; urgency=medium > . >* Standards-Version: 4.6.1 >* Add Deps to libmpich-dev needed for pkg-config. Closes: #1028172 >... This change was apparently lost at some point: Package: libmpich-dev Version: 4.2.0-6 Depends: gfortran | fortran-compiler, g++, libmpich12 (= 4.2.0-6), gfortran-13 | gfortran-mod-15, mpich (= 4.2.0-6) cu Adrian
Bug#1075917: dcmtk: autopkgtest regression
Source: dcmtk Version: 3.6.8-5 Severity: serious Tags: ftbfs Issues preventing migration: ∙ ∙ autopkgtest for dcmtk/3.6.8-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻) ... ... 29s autopkgtest [03:11:53]: test run-unit-test: [--- 30s cp: cannot stat '/usr/share/libdcmtk17/dicom.dic': No such file or directory 30s autopkgtest [03:11:54]: test run-unit-test: ---] 30s autopkgtest [03:11:54]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - 30s run-unit-testFAIL non-zero exit status 1 ...
Bug#1075916: libdcmtk-dev: Removed dependencies are required for a CMake target
Package: libdcmtk-dev Version: 3.6.8-5 Severity: serious Tags: ftbfs Control: affects -1 src:orthanc-neuro https://buildd.debian.org/status/logs.php?pkg=orthanc-neuro=1.1%2Bdfsg-1%2Bb1 ... [ 90%] Linking CXX shared library libOrthancNeuro.so /usr/bin/cmake -E cmake_link_script CMakeFiles/OrthancNeuro.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-long-long -Wno-variadic-macros -Wl,-z,relro -Wl,-z,now -Wl,--no-undefined -Wl,--as-needed -Wl,--version-script=/<>/Resources/Orthanc/Plugins/VersionScriptPlugins.map -shared -Wl,-soname,libOrthancNeuro.so.1.1 -o libOrthancNeuro.so.1.1 CMakeFiles/OrthancNeuro.dir/Sources/Plugin/Plugin.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Plugin/PluginFrameDecoder.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/BufferReader.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/CSAHeader.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/CSATag.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/DicomInstancesCollection.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/IDicomFrameDecoder.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/InputDicomInstance.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/NeuroToolbox.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/NiftiWriter.cpp.o CMakeFiles/OrthancNeuro.dir/Sources/Framework/Slice.cpp.o CMakeFiles/OrthancNeuro.dir/AUTOGENERATED/EmbeddedResources.cpp.o CMakeFiles/OrthancNeuro.dir/Resources/Orthanc/Plugins/OrthancPluginCppWrapper.cpp.o -lpthread -lrt -ldl -Wl,-Bstatic -lOrthancFramework -Wl,-Bdynamic -ldcmdata -ldcmjpls -ldcmimage -ldcmjpeg -lofstd -lboost_filesystem -lboost_iostreams -lboost_locale -lboost_regex -lboost_thread -lpugixml -luuid -ljsoncpp -lpng -ljpeg -lz -lniftiio -lznz -lrt -ldl -Wl,-Bstatic -lOrthancFramework -Wl,-Bdynamic -ldcmdata -ldcmjpls -ldcmimage -ldcmjpeg -lofstd -lboost_filesystem -lboost_iostreams -lboost_locale -lboost_regex -lboost_thread -lpugixml -luuid -ljsoncpp -lpng -ljpeg -lz -lniftiio -lznz /usr/bin/ld: cannot find -lpng: No such file or directory /usr/bin/ld: cannot find -ljpeg: No such file or directory /usr/bin/ld: cannot find -lpng: No such file or directory /usr/bin/ld: cannot find -ljpeg: No such file or directory collect2: error: ld returned 1 exit status make[3]: *** [CMakeFiles/OrthancNeuro.dir/build.make:300: libOrthancNeuro.so.1.1] Error 1 dcmtk (3.6.8-4) experimental; urgency=medium ... * d/control: Reduce number of dependencies for -dev package That's problematic when the CMake files require them for some target: /usr/lib/x86_64-linux-gnu/cmake/dcmtk/DCMTKTargets.cmake: INTERFACE_LINK_LIBRARIES "DCMTK::oflog;DCMTK::dcmdata;DCMTK::dcmimgle;/usr/lib/x86_64-linux-gnu/libtiff.so;/usr/lib/x86_64-linux-gnu/libjpeg.so;/usr/lib/x86_64-linux-gnu/libpng.so"
Bug#1074563: mysql-workbench FTBFS with libxml2 2.12
Source: mysql-workbench Version: 8.0.32+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=mysql-workbench=8.0.32%2Bdfsg-2%2Bb3 ... In file included from /<>/generated/grts/structs.db.mgmt.h:31, from /<>/library/cdbc/src/driver_manager.h:33, from /<>/library/cdbc/src/driver_manager.cpp:24: /<>/library/grt/src/grt.h:2481:76: warning: identifier ‘requires’ is a keyword in C++20 [-Wc++20-compat] 2481 | void load_metaclasses(const std::string , std::list *requires = 0); | ^~~~ /<>/library/grt/src/grt.h:2115:59: error: ‘xmlNodePtr’ has not been declared 2115 | static MetaClass *from_xml(const std::string , xmlNodePtr node); | ^~ /<>/library/grt/src/grt.h:2153:19: error: ‘xmlNodePtr’ has not been declared 2153 | void load_xml(xmlNodePtr node); | ^~ /<>/library/grt/src/grt.h:2154:30: error: ‘xmlNodePtr’ has not been declared 2154 | void load_attribute_list(xmlNodePtr node, const std::string = ""); | ^~ /<>/library/grt/src/grt.h:2534:5: error: ‘xmlDocPtr’ does not name a type 2534 | xmlDocPtr load_xml(const std::string ); | ^ /<>/library/grt/src/grt.h:2535:27: error: ‘xmlDocPtr’ has not been declared 2535 | void get_xml_metainfo(xmlDocPtr doc, std::string _ret, std::string _ret); | ^ /<>/library/grt/src/grt.h:2536:30: error: ‘xmlDocPtr’ has not been declared 2536 | ValueRef unserialize_xml(xmlDocPtr doc, const std::string _path); | ^ ... This might be fixed in 8.0.33 (untested): https://github.com/mysql/mysql-workbench/commit/805c249e2bd5598cb965dbc692bfa479cc86a581
Bug#1074562: python-cogent: binary-any FTBFS
Source: python-cogent Version: 2024.5.7a1+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=python-cogent=2024.5.7a1%2Bdfsg-1 ... debian/rules override_dh_sphinxdoc make[1]: Entering directory '/<>' dh_sphinxdoc dh_sphinxdoc: warning: Sphinx documentation not found sed -i 's%https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.4/require.min.js%file:///usr/share/javascript/requirejs/require.min.js%' `find /<>/debian/python-cogent-doc/usr/share/doc/python-cogent-doc/html/ -type f -name "*.html"` find: ‘/<>/debian/python-cogent-doc/usr/share/doc/python-cogent-doc/html/’: No such file or directory sed: no input files make[1]: *** [debian/rules:44: override_dh_sphinxdoc] Error 4
Bug#1073561: openbabel: FTBFS: failing tests test_tautomer_2[27]
On Mon, Jun 17, 2024 at 04:58:46PM +0300, Andrius Merkys wrote: > Source: openbabel > Version: 3.1.1+dfsg-9 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > > Hi, > > openbabel FTBFS both in unstable (if a fix for #1073327 is applied) and > testing with the following: > > 99% tests passed, 2 tests failed out of 229 > > Total Test time (real) = 317.34 sec > > The following tests FAILED: > 149 - test_tautomer_22 (Subprocess aborted) > 154 - test_tautomer_27 (Subprocess aborted) > Errors while running CTest > > It is not clear when the FTBFS first started happening as these tests do not > seem to be covered by openbabel's autopkgtest. I just tried, and it built for me. Does it still fail for you? > Andrius cu Adrian
Bug#1073455: [Debichem-devel] Bug#1073455: openstructure: FTBFS: TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'
Control: retitle -1 openstructure FTBFS with scipy 1.12
Control: tags -1 patch
On Tue, Jun 25, 2024 at 05:29:20PM +0300, Andrius Merkys wrote:
> control: forwarded -1 openstructure-us...@maillist.unibas.ch
>
> On 2024-06-16 16:08, Lucas Nussbaum wrote:
> > ==
> > ERROR: testSpearmanCorrel (__main__.TestTable.testSpearmanCorrel)
> > --
> > Traceback (most recent call last):
> >File "/<>/modules/base/tests/test_table.py", line 1668, in
> > testSpearmanCorrel
> > self.assertAlmostEqual(tab.SpearmanCorrel('second','third'),
> > -0.316227766)
> >File "/usr/lib/python3.11/unittest/case.py", line 904, in
> > assertAlmostEqual
> > diff = abs(first - second)
> > ~~^~~~
> > TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'
>
> This failure seems to have been caused by an API change in scipy. I have
> reported the issue upstream. A simple fix would be to skip this test
> entirely via a patch. In the meantime let us wait for upstream's response.
This has now been fixed upstream:
https://git.scicore.unibas.ch/schwede/openstructure/-/commit/15a499485ede152b6d432b7c91f1084e9e11bd8f
> Andrius
cu
Adrian
Bug#1061601: openstructure: FTBFS with Python 3.12 as default
Control: reassign -1 python3.12 Control: affects -1 src:openstructure Control: close -1 3.12.2-1 On Sat, Jan 27, 2024 at 09:28:06AM +0200, Graham Inggs wrote: > Source: openstructure > Version: 2.5.0-1 > Severity: important > Tags: ftbfs patch > User: debian-pyt...@lists.debian.org > Usertags: python3.12 > > Hi Maintainer > > openstructure FTBFS with Python 3.12 as the default version (i.e. with > python3-defaults/3.12.1-1 from experimental). I've copied what I hope > is the relevant part of the log below. > > Python 3.12 now returns 5 instead of 0 when all tests in a unit test > are skipped. This is the case for test_sec_struct.py when > debian/patches/skip-dssp-tests.patch is applied. >... This was fixed in Python 3.12.2: https://github.com/python/cpython/issues/113661 cu Adrian
Bug#1074321: createrepo-c FTBFS: error: implicit declaration of function ‘xmlCheckUTF8’
Source: createrepo-c Version: 0.17.3-4 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/rpm-software-management/createrepo_c/pull/402 https://buildd.debian.org/status/logs.php?pkg=createrepo-c=0.17.3-4%2Bb2 ... /<>/src/sqlite.c: In function ‘cr_sqlite3_bind_text’: /<>/src/sqlite.c:76:16: error: implicit declaration of function ‘xmlCheckUTF8’ [-Werror=implicit-function-declaration] 76 | } else if (xmlCheckUTF8((const unsigned char *) orig_content) |^~~~ ...
Bug#1074222: pycorrfit FTBFS with Python 3.12 as default
On Wed, Jun 26, 2024 at 06:18:35PM +0800, Bo YU wrote:
> Hi,
> On Mon, Jun 24, 2024 at 09:40:02PM +0300, Adrian Bunk wrote:
> > Source: pycorrfit
> > Version: 1.1.7+dfsg-2
> > Severity: serious
> > Tags: ftbfs trixie sid
> >
> >self.run_command('egg_info')
> > File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
> > 318, in run_command
> >self.distribution.run_command(command)
> > File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
> > run_command
> >super().run_command(command)
> > File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
> > 987, in run_command
> >cmd_obj.ensure_finalized()
> > File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
> > 111, in ensure_finalized
> >self.finalize_options()
> > File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py", line
> > 225, in finalize_options
> >parsed_version = packaging.version.Version(self.egg_version)
> > ^^^
> > File
> > "/usr/lib/python3/dist-packages/setuptools/_vendor/packaging/version.py",
> > line 198, in __init__
> >raise InvalidVersion(f"Invalid version: '{version}'")
> > setuptools.extern.packaging.version.InvalidVersion: Invalid version:
> > 'unknown'
> > E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1:
> > /usr/bin/python3 setup.py build
> > dh_auto_build: error: pybuild --build -i python{version} -p 3.12 returned
> > exit code 13
> > make[1]: *** [debian/rules:49: override_dh_auto_build] Error 25
>
> I can not reproduce it now locally:
>...
> So could we rebuild it again?
Still fails on the buildd:
https://buildd.debian.org/status/fetch.php?pkg=pycorrfit=amd64=1.1.7%2Bdfsg-2%2Bb2=1719400031=0
Based on the error message, I wouldn't be surprised if the +b2 from the
binNMU version would be part of the problem.
> Regards,
cu
Adrian
Bug#1074258: fontforge FTBFS with gettext 0.22.5-1
Source: fontforge Version: 1:20230101~dfsg-1.1 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/fontforge/fontforge/pull/5330 https://buildd.debian.org/status/fetch.php?pkg=fontforge=s390x=1%3A20230101~dfsg-1.1%2Bb1=1719301120=0 ... FAILED: po/fr.mo /<>/build/nox/po/fr.mo cd "/<>/build/nox/po" && /usr/bin/msgfmt --check -o "/<>/build/nox/po/fr.mo" "/<>/po/fr.po" /<>/po/fr.po:294: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 3, the argument size specifier is invalid. /<>/po/fr.po:305: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 4, the argument size specifier is invalid. /<>/po/fr.po:7435: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:19927: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:19935: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:19970: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:19986: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:20459: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:21045: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:21443: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:21772: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:24553: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /<>/po/fr.po:24564: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 2, the argument size specifier is invalid. /usr/bin/msgfmt: found 13 fatal errors ...
Bug#1074224: crossfire FTBFS with Python 3.12 as default
Source: crossfire
Version: 1.75.0-6
Severity: serious
Tags: ftbfs
Forwarded:
https://sourceforge.net/p/crossfire/crossfire-server/ci/472dd26ac74419baa0e6373cb04e095437e994c6/
https://buildd.debian.org/status/fetch.php?pkg=crossfire=arm64=1.75.0-6%2Bb3=1719233376=0
...
cfpython_archetype.c:136:5: note: (near initialization for
‘Crossfire_ArchetypeType.tp_vectorcall_offset’)
cjson.c: In function ‘encode_unicode’:
cjson.c:700:9: error: implicit declaration of function ‘PyUnicode_AS_UNICODE’;
did you mean ‘PyUnicode_AsUCS4’? [-Werror=implicit-function-declaration]
700 | s = PyUnicode_AS_UNICODE(unicode);
| ^~~~
| PyUnicode_AsUCS4
cjson.c:700:7: warning: assignment to ‘Py_UNICODE *’ {aka ‘unsigned int *’}
from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
700 | s = PyUnicode_AS_UNICODE(unicode);
| ^
cjson.c:701:12: error: implicit declaration of function ‘PyUnicode_GET_SIZE’;
did you mean ‘PyDict_GET_SIZE’? [-Werror=implicit-function-declaration]
701 | size = PyUnicode_GET_SIZE(unicode);
|^~
|PyDict_GET_SIZE
...
Bug#1074222: pycorrfit FTBFS with Python 3.12 as default
Source: pycorrfit
Version: 1.1.7+dfsg-2
Severity: serious
Tags: ftbfs trixie sid
https://buildd.debian.org/status/logs.php?pkg=pycorrfit=1.1.7%2Bdfsg-2%2Bb2
...
running egg_info
/usr/lib/python3/dist-packages/setuptools/command/egg_info.py:131:
SetuptoolsDeprecationWarning: Invalid version: 'unknown'.
!!
Version 'unknown' is not valid according to PEP 440.
Please make sure to specify a valid version for your package.
Also note that future releases of setuptools may halt the build process
if an invalid version is given.
This deprecation is overdue, please update your project and remove
deprecated
calls to avoid build errors in the future.
See https://peps.python.org/pep-0440/ for details.
!!
return _normalization.best_effort_version(tagged)
Traceback (most recent call last):
File "/<>/setup.py", line 54, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py",
line 131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318,
in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
65, in run
self.build_package_data()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
161, in build_package_data
for target, srcfile in self._get_package_data_output_mapping():
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
153, in _get_package_data_output_mapping
for package, src_dir, build_dir, filenames in self.data_files:
^^^
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
74, in __getattr__
self.data_files = self._get_data_files()
^^
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
86, in _get_data_files
self.analyze_manifest()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
183, in analyze_manifest
self.run_command('egg_info')
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318,
in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
987, in run_command
cmd_obj.ensure_finalized()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111,
in ensure_finalized
self.finalize_options()
File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py", line
225, in finalize_options
parsed_version = packaging.version.Version(self.egg_version)
^^^
File
"/usr/lib/python3/dist-packages/setuptools/_vendor/packaging/version.py", line
198, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
setuptools.extern.packaging.version.InvalidVersion: Invalid version: 'unknown'
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p 3.12 returned exit
code 13
make[1]: *** [debian/rules:49: override_dh_auto_build] Error 25
Bug#1074216: kitty FTBFS with Python 3.12 as default
Source: kitty
Version: 0.35.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=kitty=0.35.1-1%2Bb1
...
==
FAIL: test_ssh_leading_data (kitty_tests.ssh.SSHKitten.test_ssh_leading_data)
(sh='python3')
--
Traceback (most recent call last):
File "/<>/kitty/launcher/../../kitty_tests/ssh.py", line 167, in
test_ssh_leading_data
self.ae(pty.screen_contents(), 'UNTAR_DONE\nld:before_tarfile')
pty =
script = 'print("ld:" + leading_data.decode("ascii")); raise SystemExit(0);'
self =
sh = 'python3'
tdir = '/tmp/tmpj2ma30as'
AssertionError: 'bootstrap.py:214: DeprecationWarning: Pyt[180 chars]file' !=
'UNTAR_DONE\nld:before_tarfile'
- bootstrap.py:214: DeprecationWarning: Python 3.14 will, by default, filter
extra
- cted tar archives and reject files or modify their metadata. Use the filter
argu
- ment to control this behavior.
UNTAR_DONE
ld:before_tarfile
--
Ran 144 tests in 68.976s
FAILED (failures=1, skipped=2)
[31mError[39m: Some tests failed!
make[1]: *** [debian/rules:60: override_dh_auto_test] Error 1
Bug#1074147: simgrid FTBFS with ns3 3.42
Source: simgrid Version: 3.35-1.1 Severity: serious Tags: ftbfs patch Forwarded: https://framagit.org/simgrid/simgrid/-/commit/d94c8f645e5e2d9dca54ed65403a165408e95ef8 https://buildd.debian.org/status/logs.php?pkg=simgrid=3.35-1.1%2Bb2 ... In file included from /usr/include/ns3/core-module.h:88, from /<>/src/kernel/resource/models/network_ns3.cpp:20: /usr/include/ns3/timer-impl.h: In function ‘ns3::internal::TimerImpl* ns3::internal::MakeTimerImpl(U (*)(Ts ...))’: /usr/include/ns3/timer-impl.h:105:77: error: template argument 1 is invalid 105 | struct FnTimerImpl : public TimerImplX&...> | ^ /usr/include/ns3/timer-impl.h:112:38: error: ‘remove_cvref_t’ in namespace ‘std’ does not name a template type 112 | void SetArguments(const std::remove_cvref_t&... args) override | ^~ /usr/include/ns3/timer-impl.h:112:33: note: ‘std::remove_cvref_t’ is only available from C++20 onwards ...
Bug#1074145: numexpr FTBFS with more than 8 cores
Source: numexpr
Version: 2.10.1-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/pydata/numexpr/issues/490
https://buildd.debian.org/status/fetch.php?pkg=numexpr=loong64=2.10.1-1=1719162095=0
https://buildd.debian.org/status/fetch.php?pkg=numexpr=powerpc=2.10.1-1=1719162022=0
...
==
ERROR: test_max_threads_unset
(numexpr.tests.test_numexpr.test_threading_config.test_max_threads_unset)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.11_numexpr/build/numexpr/tests/test_numexpr.py",
line 1134, in test_max_threads_unset
subprocess.check_call([sys.executable, '-c', script])
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3.11', '-c', "import
os\nif 'NUMEXPR_MAX_THREADS' in os.environ:
os.environ.pop('NUMEXPR_MAX_THREADS')\nif 'OMP_NUM_THREADS' in os.environ:
os.environ.pop('OMP_NUM_THREADS')\nimport numexpr\nassert(numexpr.nthreads <=
8)\nexit(0)"]' returned non-zero exit status 1.
--
Ran 5538 tests in 7.326s
FAILED (errors=1)
...
Bug#1073997: giada FTBFS with RtAudio 6
Source: giada Version: 0.22.0-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=giada=0.22.0-4%2Bb2 ... /<>/src/core/kernelAudio.cpp: In member function ‘int giada::m::KernelAudio::openDevice(const giada::m::Conf::Data&)’: /<>/src/core/kernelAudio.cpp:182:16: error: ‘RtAudioError’ does not name a type; did you mean ‘RtAudioErrorType’? 182 | catch (RtAudioError& e) |^~~~ |RtAudioErrorType ...
Bug#950372: closed by Debian FTP Masters (reply to Alex Myczko ) (Bug#950372: fixed in radare2 5.9.0+dfsg-1)
On Thu, Apr 25, 2024 at 02:54:32PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:radare2 package: > > #950372: Is radare2 suitable for stable Debian releases? >... > radare2 (5.9.0+dfsg-1) unstable; urgency=medium > . >* New upstream version. (Closes: #1034862, #1060127, #950372) >... > It is understandable (and normal for most software) that upstream > is not able or willing to provide security support for the old > version shipped in stable distribution releases. > > But below seems to be upstream actively encouraging exploiting > the version in stable. > > AFAIK Debian in general tries to avoid shipping software when upstream > strongly objects to it, or is openly hostile towards Debian. > > <-- snip --> > > https://rada.re/con/2019/ > > PwnDebian > > Since the very begining of radare development we had people complaining of > bugs because they were using the 3-4 year old version shipped in their > distro. We tried to work with everyone who ships builds of r2 to always get > updates and merge back their patches upstream so everyone gets benefit out of > it. > > But that has been not enough. In github/radare2 we can check out most of > known/used Linux and BSD distros and the shipped r2 version, and it's pretty > clear that Debian/Ubuntu stopped updating those packages long time ago > (3.2.1). Yes, the 0.9.6 drama is over. > > The aim of this competition is to publish a working exploit for radare2 on > Debian stable (nowadays, unstable keeps the same version). To show that > debian-security and backporting patches is not solving enough when > distributing such state-of-the-art packages. > > In order to win this competition. We will accept only 1 working exploit (the > first one to submit it) for radare2-3.2.1 (built for x86-64 debian/stable). > Additional points will be given for writing some notes or presenting at r2con > the way the vuln was found and how the exploit was developed. Hi Alex, has there been any change in the attitude radare2 upstream has towards distributions? cu Adrian
Bug#1073259: libyojson-ocaml-dev should depend on yojson-tools
Package: libyojson-ocaml-dev Version: 2.2.1-1 Severity: serious Tags: ftbfs Control: affects -1 src:botch https://buildd.debian.org/status/fetch.php?pkg=botch=ppc64el=0.24-3%2Bb1=1718448612=0 ... + ydump ./tools/native.sh: 512: ydump: not found ... Packages (build) depending on libyojson-ocaml-dev and users upgrading to trixie might see breakage when depending on or installing libyojson-ocaml-dev no longer provides the ydump tool. There is likely no good reason against libyojson-ocaml-dev depending on yojson-tools.
Bug#1072828: texlive-binaries upgrade breaks therion build
On Sun, Jun 09, 2024 at 12:02:02AM +0200, Preuße, Hilmar wrote: > On 08.06.2024 16:09, Adrian Bunk wrote: > > Hi, Hi Hilmar, >... > Hence I tend to say this is something specific for sbuild environments, > which could have lower priority than "serious". all testing I did for the below statement was plain dpkg-buildpackage in a chroot. > > Downgrading texlive-binaries to 2023.20230311.66589-9 OR > > installing texlive-fonts-recommended works around this issue. > > Why not simply adding texlive-fonts-recommended to BD (which carries the > Type1 fonts of logo10) and then solve the issue? >... Because that doesn't fix whatever the bug is, which might also affect other packages or users. a minimal example inside therion-6.2.1/thbook/ after a failed build seems to be TEXINPUTS="/<>/build/thbook;." /usr/bin/pdftex --output-dir=/<>/build/thbook thbook.tex Did anything break or change regarding --output-dir ? In the working case with the old version the generated file is in debian/.debhelper/generated/_source/home/.texlive2023/texmf-var/fonts/pk/ljfour/public/knuth-lib/logo10.720pk > H. cu Adrian
Bug#1072828: texlive-binaries upgrade breaks therion build
Package: texlive-binaries
Version: 2024.20240313.70630+ds-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:therion
https://buildd.debian.org/status/fetch.php?pkg=therion=amd64=6.2.1-1%2Bb1=1717847632=0
...
FAILED: thbook/thbook.pdf /<>/build/thbook/thbook.pdf
cd /<>/thbook && /usr/bin/cmake -E env FORCE_SOURCE_DATE=1
TEXINPUTS="/<>/build/thbook;." /usr/bin/pdftex
--output-dir=/<>/build/thbook
\\def\\outputsize{0}\\def\\reproducible{}\\input\ thbook.tex && /usr/bin/cmake
-E env FORCE_SOURCE_DATE=1 TEXINPUTS="/<>/build/thbook;."
/usr/bin/pdftex --output-dir=/<>/build/thbook
\\def\\outputsize{0}\\def\\reproducible{}\\input\ thbook.tex && /usr/bin/cmake
-E env FORCE_SOURCE_DATE=1 TEXINPUTS="/<>/build/thbook;."
/usr/bin/pdftex --output-dir=/<>/build/thbook
\\def\\outputsize{0}\\def\\reproducible{}\\input\ thbook.tex
This is pdfTeX, Version 3.141592653-2.6-1.40.26 (TeX Live 2025/dev/Debian)
(preloaded format=pdftex)
restricted \write18 enabled.
entering extended mode
(./thbook.tex No glyph to unicode mapping found! (./etc/supp-mis.tex
loading : Context Support Macros / Miscellaneous (2004.10.26)
) (./etc/supp-pdf.tex
loading : Context Support Macros / PDF
) (./etc/optarg.tex) (./etc/verbatim.tex) (./ch00.tex [1{/var/lib/texmf/fonts/m
ap/pdftex/updmap/pdftex.map} <./pic/thbook.jpg>]
(/<>/build/thbook/version.tex) [2]
Warning: re-run to input a newly generated TOC file [3] [4]) (./ch01.tex
[5 <./pic/ageom.pdf>] [6] [7] [MP to PDF] (./mp/schema.1) [8]) (./ch02.tex
[9] [10 <./pic/agrippa.jpg>]
Overfull \hbox (9.55724pt too wide) in paragraph at lines 96--99
[]\tt [.MM[.DD[@HH[:MM[:SS[.SS]] [- [.MM[.DD[@HH[:MM[:SS[.SS]]
][]
[11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]
Overfull \hbox (2.61252pt too wide) in paragraph at lines 824--857
[]\tt ice-pillar[]\rm , []\tt ice-stalactite[]\rm , []\tt ice-stalagmite[]\rm
, []\tt map-connection[]$[]$\rm , []\tt paleo-material[]\rm ,
Overfull \hbox (4.79291pt too wide) in paragraph at lines 824--857
[]\tt photo[]\rm , []\tt root[]\rm , []\tt seed-germination[]\rm , []\tt sink[
]\rm , []\tt spring[]$[]$\rm , []\tt tree-trunk[]\rm , []\tt u[]$[]$\rm , []\tt
vegetable-debris[]\rm ,
[23] [24] [25]
Overfull \hbox (0.4216pt too wide) in paragraph at lines 1015--1031
[]\it passages: []\tt wall[]\rm , []\tt con-tour[]\rm , []\tt slope[]$[]$\rm ,
[]\tt floor-step[]\rm , []\tt pit[]\rm , []\tt pitch[] \rm (syn-onym of pit),
[]\tt ceiling-
Overfull \hbox (0.65195pt too wide) in paragraph at lines 1032--1044
[]\it passage fills: []\tt flow-stone[]\rm , []\tt moon-milk[]\rm , []\tt rock
-border[]$[]$\rm , []\tt rock-edge[]$[]$\rm , []\tt water-flow[]\rm , []\tt aby
ss-
Overfull \hbox (1.1684pt too wide) in paragraph at lines 1045--1053
[]\it equipment: []\tt fixed-ladder[]\rm , []\tt handrail[]\rm , []\tt rope[]\
rm , []\tt rope-ladder[]\rm , []\tt steps[]\rm , []\tt via-ferrata[]\rm , []\tt
walk-
[MP to PDF] (./mp/xsect.1) [26] [27] [28] [29] [30] [31] [32] [33] [34]
[35] [36] [37] [38] [39] [40] [41] [42] [43] [44]) (./ch03.tex [45] [46 <./pic/
herakl.pdf>] [47] [48] [49]
Overfull \hbox (3.98236pt too wide) in paragraph at lines 294--294
[]\tt fonts-setup
[50] [51] [52] [MP to PDF] (./mp/page.1) [53 <./pic/page.pdf>] [54] [55]
[56] [57] [58]
Overfull \hbox (1.67323pt too wide) in paragraph at lines 718--720
[][][]\tt wall-source [] $\mit .$ \rm set source d
ata for pas-sage wall mod-
[59] [60] [61] [62]) (./ch04.tex [63] [64] [65 <./pic/database.pdf>] [66])
(./ch05.tex [67] [68 <./pic/thom.jpg>] [69] [70] [71] [72] [73] [74] [75]
[76] [77]) (./ch06.tex [78] [79] [80] [81] [82] [83] [84] [85] [86] [87]
[88] [89] [90] [91] [92] [93]) (./ch07.tex Warning: skipping the case studies)
[94]
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 logo10
mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600;
nonstopmode; input logo10
This is METAFONT, Version 2.71828182 (TeX Live 2025/dev/Debian) (preloaded
base=mf)
(/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo10.mf
(/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo.mf [77]
[69] [84] [65] [70] [80] [83] [79] [78]) )
Font metrics written on /<>/build/thbook/log
o10.tfm.
Output written on /<>/build/thbook/logo10.60
0gf (9 characters, 1748 bytes).
Transcript written on /<>/build/thbook/logo1
0.log.
mktexpk: `mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600; nonstopmode; input
logo10' failed to make logo10.600pk.
kpathsea: Appending font creation commands to
/<>/build/thbook/missfont.log.
)
(\end occurred when \ifeof on line 10 was incomplete)
(see the transcript file for additional information)
!pdfTeX error: /usr/bin/pdftex (file logo10): Font logo10 at 600 not found
==> Fatal error occurred, no output PDF file produced!
...
Downgrading texlive-binaries to 2023.20230311.66589-9 OR
installing texlive-fonts-recommended works around this issue.
Bug#1072824: odin FTBFS with VTK 9.3.0
Source: odin Version: 2.0.5-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=odin=amd64=2.0.5-5%2Bb2=1717847424=0 ... checking for main in -lvtkIOLegacy-7.1... no checking for main in -lvtkIOLegacy-7.0... no checking for main in -lvtkIOLegacy-6.3... no checking for main in -lvtkIOLegacy-6.2... no checking for main in -lvtkIOLegacy-6.1... no checking for main in -lvtkIOLegacy-6.0... no checking for main in -lvtkIOLegacy-9.0... no checking for main in -lvtkIOLegacy-9.1... no checking for main in -lvtkIO... no checking for main in -lvtkRendering... no checking for main in -lvtkGraphics... no checking for main in -lvtkFiltering... no checking for main in -lvtkCommon... no checking for vtkStructuredPoints.h... no checking for vtkArrowSource.h... no configure: error: VTK library missing
Bug#1072823: liggghts FTBFS with VTK 9.3.0
Source: liggghts Version: 3.8.0+repack1-9.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=liggghts=amd64=3.8.0%2Brepack1-9.1%2Bb2=1717846024=0 ... /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtp(vtkSmartPointer, int, const char*)’: /<>/src/dump_vtk.cpp:170:18: error: ‘class vtkXMLPPolyDataWriter’ has no member named ‘SetInput’; did you mean ‘GetInput’? 170 | pwriter->SetInput(data); | ^~~~ | GetInput /<>/src/dump_vtk.cpp:187:17: error: ‘class vtkXMLPolyDataWriter’ has no member named ‘SetInput’; did you mean ‘GetInput’? 187 | writer->SetInput(data); | ^~~~ | GetInput /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtu(vtkSmartPointer, int, const char*)’: /<>/src/dump_vtk.cpp:209:18: error: ‘class vtkXMLPUnstructuredGridWriter’ has no member named ‘SetInput’; did you mean ‘GetInput’? 209 | pwriter->SetInput(data); | ^~~~ | GetInput /<>/src/dump_vtk.cpp:226:17: error: ‘class vtkXMLUnstructuredGridWriter’ has no member named ‘SetInput’; did you mean ‘GetInput’? 226 | writer->SetInput(data); | ^~~~ | GetInput /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtr(vtkSmartPointer, int, const char*)’: /<>/src/dump_vtk.cpp:280:43: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 280 | pwriter->SetInputConnection(data->GetProducerPort()); | ^~~ /<>/src/dump_vtk.cpp:297:42: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 297 | writer->SetInputConnection(data->GetProducerPort()); | ^~~ /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtk_unstructured_grid(vtkSmartPointer, int, const char*, char*)’: /<>/src/dump_vtk.cpp:322:42: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 322 | writer->SetInputConnection(data->GetProducerPort()); | ^~~ /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtk_rectilinear_grid(vtkSmartPointer, int, const char*, char*)’: /<>/src/dump_vtk.cpp:347:42: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 347 | writer->SetInputConnection(data->GetProducerPort()); | ^~~ /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtk_poly(vtkSmartPointer, int, const char*, char*)’: /<>/src/dump_vtk.cpp:372:42: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 372 | writer->SetInputConnection(data->GetProducerPort()); | ^~~ ...
Bug#1072822: gdcm FTBFS with VTK 9.3.0
Source: gdcm Version: 3.0.24-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=gdcm=amd64=3.0.24-1%2Bb2=1717845766=0 ... -- Building Utilities/VTK as a VTK 9 Module CMake Error at /usr/lib/x86_64-linux-gnu/cmake/vtk-9.3/vtkModule.cmake:2121 (message): The `SPDX_DESTINATION` must not be an absolute path. Use `CMAKE_INSTALL_PREFIX` to keep everything in a single installation prefix. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/vtk-9.3/vtkModule.cmake:2667 (_vtk_module_check_destinations) CMakeLists.txt:696 (vtk_module_build) -- Configuring incomplete, errors occurred!
Bug#1072821: wireshark: binNMUs revert t64 transition
Source: wireshark Version: 4.2.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=wireshark=amd64=4.2.5-1%2Bb1=1717834351=0 ... Description: libwireshark-dev - network packet dissection library -- development files libwireshark17 - network packet dissection library -- shared library libwiretap-dev - network packet capture library -- development files libwiretap14 - network packet capture library -- shared library libwsutil-dev - network packet dissection utilities library -- development files libwsutil15 - network packet dissection utilities library -- shared library tshark - network traffic analyzer - console version wireshark - network traffic analyzer - graphical interface wireshark-common - network traffic analyzer - common files wireshark-dev - network traffic analyzer - development tools Changes: wireshark (4.2.5-1+b1) sid; urgency=low, binary-only=yes . * Binary-only non-maintainer upload for amd64; no source changes. * Rebuild against Qt 6.6.2. ... debian/rules: ... ifneq ($(filter noble unstable testing trixie UNRELEASED,$(DEB_DISTRIBUTION)),) sed "$(CONTROL_IN_SED_CMD)" debian/control.t64.in > debian/control else sed "$(CONTROL_IN_SED_CMD)" debian/control.in > debian/control ... sid != unstable
Bug#1072390: python3-requirements: Breaks+Replaces must be (<< 0.9.0-0.3~)
Package: python3-requirements Version: 0.9.0-0.3 Severity: serious X-Debbugs-Cc: Gavin Lai (賴建宇) , Alexandre Detiste , SZ Lin (林上智) ... Unpacking python3-requirements (0.9.0-0.3) ... dpkg: error processing archive /tmp/apt-dpkg-install-QTQFZ9/47-python3-requirements_0.9.0-0.3_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/requirements/__init__.py', which is also in package python3-requirement-parser 0.9.0-0.2 ...
Bug#1070256: closed by Debian FTP Masters (reply to Alec Leamas ) (Bug#1070256: fixed in libcxx-serial 1.2.1-6)
On Wed, May 29, 2024 at 05:15:45PM +0200, Alec Leamas wrote: >... > I can see the build log, but have problems reproducing the problem. In > short, I do > > $ export DEB_BUILD_OPTIONS=nobench nocheck parallel=2 > $ dpkg-buildpackage --sanitize-env -us -uc -B -rfakeroot > > which configures and builds successfully. > > Attaching the build log. Have you any hint about what's going on? $ export DEB_BUILD_OPTIONS=nobench nocheck parallel=2 $ echo $DEB_BUILD_OPTIONS nobench $ export DEB_BUILD_OPTIONS="nobench nocheck parallel=2" $ echo $DEB_BUILD_OPTIONS nobench nocheck parallel=2 $ > Cheers! > --alec cu Adrian
Bug#1071759: firebird4.0 FTBFS with libre2-dev 20240501
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#1070256: closed by Debian FTP Masters (reply to Alec Leamas ) (Bug#1070256: fixed in libcxx-serial 1.2.1-6)
Control: reopen -1 On Sun, May 12, 2024 at 07:09:07PM +, Debian Bug Tracking System wrote: >... > Changes: > libcxx-serial (1.2.1-6) trixie; urgency=medium > . >* Avoid crash when running with nocheck profile. Closes: #1070256 >... 1.2.1-7 does still FTBFS: https://buildd.debian.org/status/fetch.php?pkg=libcxx-serial=sh4=1.2.1-7=1715548569=0 ifeq (,$(findstring nocheck,$(DEB_BUILD_PROFILES))) ENABLE_TESTS := ON else ENABLE_TESTS := OFF endif This should be DEB_BUILD_OPTIONS, not DEB_BUILD_PROFILES. cu Adrian
Bug#1064938: isospec - maintainer does not access email from ftp-master
Hi Bastian, The Debichem Group maintains ~ 140 packages with this maintainer address at lists.alioth.debian.org. Was this any misconfiguration on the debian.org side, or is/was this any issue at alioth-lists.debian.net, or what else might have gone wrong here? Thanks Adrian On Tue, Feb 27, 2024 at 11:23:14PM +0100, Bastian Blank wrote: > Package: isospec > Severity: serious > > - Forwarded message from debichem-devel-ow...@alioth-lists.debian.net > - > > From: debichem-devel-ow...@alioth-lists.debian.net > To: ftpmas...@ftp-master.debian.org > Subject: Processing of isospec_2.2.1-4.1~exp2_source.changes > > You are not allowed to post to this mailing list From: a domain which > publishes a DMARC policy of reject or quarantine, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > debichem-devel-ow...@alioth-lists.debian.net. > > > Date: Sat, 24 Feb 2024 02:03:38 + > From: Debian FTP Masters > To: debichem-de...@lists.alioth.debian.org > Subject: Processing of isospec_2.2.1-4.1~exp2_source.changes > > isospec_2.2.1-4.1~exp2_source.changes uploaded successfully to localhost > along with the files: > isospec_2.2.1-4.1~exp2.dsc > isospec_2.2.1-4.1~exp2.debian.tar.xz > isospec_2.2.1-4.1~exp2_source.buildinfo > > Greetings, > > Your Debian queue daemon (running on host usper.debian.org) > > > > - End forwarded message - > > -- > Hailing frequencies open, Captain.
Bug#1059133: dogecoin: FTBFS: error: invalid ‘static_cast’ from type ‘boost::detail::function::function_buffer_members::obj_ptr_t’ {aka ‘void*’} to type ‘void (*)(bool, const CBlockIndex*)’
Control: reassign -1 libboost1.83-dev 1.83.0-2.1 Control: retitle -1 libboost1.83-dev: Please add upstream fix needed for dogecoin Control: affects -1 src:dogecoin Control: tags -1 patch Control: forwarded -1 https://github.com/boostorg/function/pull/47 On Tue, Jan 09, 2024 at 06:37:44PM -0500, Chad Jacob Milios wrote: > Please see https://github.com/boostorg/function/pull/47 and let us know if > that minor modification helps you out. Yes, it does. cu Adrian
Bug#1028634: closed by Sergio Durigan Junior (Re: Bug#1028634: tiledarray: FTBFS: Could not find a package configuration file provided by "blaspp")
On Wed, Jan 24, 2024 at 08:09:03PM +, Debian Bug Tracking System wrote: >... > Date: Wed, 24 Jan 2024 14:59:30 -0500 > From: Sergio Durigan Junior > To: 1028634-cl...@bugs.debian.org > Subject: Re: Bug#1028634: tiledarray: FTBFS: Could not find a package > configuration file provided by "blaspp" > > On Tuesday, January 24 2023, Adrian Bunk wrote: > > > On Fri, Jan 13, 2023 at 11:59:48PM +0100, Sebastian Ramacher wrote: > >> Source: tiledarray > >> Version: 1.0.0-1 > >> Severity: serious > >> Tags: ftbfs > >>... > >> blasppConfig.cmake > >> blaspp-config.cmake > >> > >> Add the installation prefix of "blaspp" to CMAKE_PREFIX_PATH or set > >> "blaspp_DIR" to a directory containing one of the above files. If > >> "blaspp" > >> provides a separate development package or SDK, be sure it has been > >> installed. > >> Call Stack (most recent call first): > >> /usr/lib/cmake/BTAS/btas-config.cmake:104 (find_dependency) > >> cmake/modules/FindOrFetchBTAS.cmake:1 (find_package) > >> CMakeLists.txt:279 (include) > > > > This looks like a problem in libbtas-dev (unpackaged dependency blaspp?). > > The package is building correctly now. Closing the bug. >... It does still FTBFS: https://buildd.debian.org/status/logs.php?pkg=tiledarray=1.0.0-1 cu Adrian
Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev
On Thu, May 23, 2024 at 09:34:48AM +0200, Uwe Steinmann wrote: > Thanks Adrian! > > Quite strange. It does have a build depend on cppzmq-dev ... No, it does not: https://tracker.debian.org/media/packages/h/horizon-eda/control-2.6.0-2 >... > So I restarted from ground in pbuilder and > 1. copied >horizon-eda_2.6.0-3.debian.tar.xz, >... 2.6.0-3 is not in the archive. cu Adrian
Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev
Source: horizon-eda Version: 2.6.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=horizon-eda=2.6.0-2 ... Has header "zmq.hpp" : NO ../meson.build:46:8: ERROR: Problem encountered: cppzmq not found I haven't checked whether this is the only missing build dependency. BTW: The build dependency on libzmq5 looks wrong and is already covered by the build dependency on libzmq3-dev, please remove libzmq5 since this will break with the next soname change of libzmq.
Bug#1071452: dnsdbq FTBFS on 32bit with 64bit time_t
Source: dnsdbq
Version: 2.6.6-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=dnsdbq=2.6.6-1
...
time.c: In function ‘timeval_str’:
time.c:83:36: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 3 has type ‘__suseconds64_t’ {aka ‘long long int’} [-Werror=format=]
83 | sprintf(dst, ".%03ld", src->tv_usec % 1000);
|^ ~~~
|||
|long int __suseconds64_t
{aka long long int}
|%03lld
time.c:85:36: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 3 has type ‘__suseconds64_t’ {aka ‘long long int’} [-Werror=format=]
85 | sprintf(dst, ".%06ld", src->tv_usec % 100);
|^ ~~
|||
|long int __suseconds64_t
{aka long long int}
|%06lld
cc1: all warnings being treated as errors
make[1]: *** [Makefile:76: time.o] Error 1
Bug#1071277: petsc4py: binary-all FTBFS
Source: petsc4py Version: 3.20.5-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=petsc4py=sid ... debian/rules execute_after_dh_auto_build-indep make[1]: Entering directory '/<>' PYTHONPATH=/<>/.pybuild/cpython3_3.11_petsc4py_real3.20/build http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/source build/html # HTML generator Running Sphinx v7.2.6 Using PETSC inventory from https://petsc.org/release/objects.inv making output directory... done [autosummary] generating autosummary for: citing.rst, demo/demo.rst, demo/poisson2d/poisson2d.rst, documentation_standards.rst, index.rst, install.rst, overview.rst, petsc_options.rst, petsc_python_types.rst, reference.rst WARNING: [autosummary] failed to import petsc4py. Possible hints: * ValueError: not enough values to unpack (expected 2, got 1) * ModuleNotFoundError: No module named 'petsc4py' * KeyError: 'petsc4py' Extension error (sphinx.ext.autosummary): Handler for event 'builder-inited' threw an exception (exception: no module named petsc4py) make[1]: *** [debian/rules:78: execute_after_dh_auto_build-indep] Error 2
Bug#1071193: libqt6core6t64/experimental breaks ABI
On Wed, May 15, 2024 at 11:27:25PM +0300, Adrian Bunk wrote: > Package: libqt6core6t64 > Version: 6.6.2+dfsg-7 > Severity: serious > Tags: ftbfs > Control: affects -1 libqt6core5compat6 src:kf6-kwallet > > https://buildd.debian.org/status/logs.php?pkg=kf6-kwallet=6.0.0-1 > > ... > Get:32 https://deb.debian.org/debian experimental/main arm64 libqt6core6t64 > arm64 6.6.2+dfsg-7 [1579 kB] > ... > Get:291 https://deb.debian.org/debian unstable/main arm64 libqt6core5compat6 > arm64 6.4.2-4+b2 [126 kB] > ... > /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined > reference to `QUtf16::convertToUnicode(QByteArrayView, > QStringConverterBase::State*, DataEndianness)@Qt_6' > /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined > reference to `QUtf16::convertFromUnicode(QStringView, > QStringConverterBase::State*, DataEndianness)@Qt_6' > /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined > reference to `QUtf32::convertToUnicode(QByteArrayView, > QStringConverterBase::State*, DataEndianness)@Qt_6' > /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined > reference to `QUtf8::convertFromUnicode(QStringView)@Qt_6' > /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined > reference to `QUtf32::convertFromUnicode(QStringView, > QStringConverterBase::State*, DataEndianness)@Qt_6' > /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined > reference to `QUtf8::convertFromUnicode(QStringView, > QStringConverterBase::State*)@Qt_6' > /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined > reference to `QUtf8::convertToUnicode(QChar*, QByteArrayView)@Qt_6' > /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined > reference to `QUtf8::convertToUnicode(QByteArrayView, > QStringConverterBase::State*)@Qt_6' > collect2: error: ld returned 1 exit status > > > This is due to: > https://salsa.debian.org/qt-kde-team/qt6/qt6-base/-/commit/b1d2e462c65933b577ec49b4e4156ec8ad426b26 Apparently the symbols were moved to PRIVATE_API: _ZN5QUtf816convertToUnicodeE14QByteArrayViewPN20QStringConverterBase5StateE@@Qt_6_PRIVATE_API _ZN5QUtf816convertToUnicodeEPDs14QByteArrayView@@Qt_6_PRIVATE_API _ZN6QUtf1616convertToUnicodeE14QByteArrayViewPN20QStringConverterBase5StateE14DataEndianness@@Qt_6_PRIVATE_API _ZN6QUtf3216convertToUnicodeE14QByteArrayViewPN20QStringConverterBase5StateE14DataEndianness@@Qt_6_PRIVATE_API _ZN5QUtf818convertFromUnicodeE11QStringView@@Qt_6_PRIVATE_API _ZN5QUtf818convertFromUnicodeE11QStringViewPN20QStringConverterBase5StateE@@Qt_6_PRIVATE_API _ZN6QUtf1618convertFromUnicodeE11QStringViewPN20QStringConverterBase5StateE14DataEndianness@@Qt_6_PRIVATE_API _ZN6QUtf3218convertFromUnicodeE11QStringViewPN20QStringConverterBase5StateE14DataEndianness@@Qt_6_PRIVATE_API This is an upstream(?) ABI break, but since libqt6core5compat6 seems to be the only affected package something like Breaks: libqt6core5compat6 (<< 6.6) might be the best available option to avoid issues when upgrading from bookworm. cu Adrian
Bug#1071193: libqt6core6t64/experimental breaks ABI
Package: libqt6core6t64 Version: 6.6.2+dfsg-7 Severity: serious Tags: ftbfs Control: affects -1 libqt6core5compat6 src:kf6-kwallet https://buildd.debian.org/status/logs.php?pkg=kf6-kwallet=6.0.0-1 ... Get:32 https://deb.debian.org/debian experimental/main arm64 libqt6core6t64 arm64 6.6.2+dfsg-7 [1579 kB] ... Get:291 https://deb.debian.org/debian unstable/main arm64 libqt6core5compat6 arm64 6.4.2-4+b2 [126 kB] ... /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined reference to `QUtf16::convertToUnicode(QByteArrayView, QStringConverterBase::State*, DataEndianness)@Qt_6' /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined reference to `QUtf16::convertFromUnicode(QStringView, QStringConverterBase::State*, DataEndianness)@Qt_6' /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined reference to `QUtf32::convertToUnicode(QByteArrayView, QStringConverterBase::State*, DataEndianness)@Qt_6' /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined reference to `QUtf8::convertFromUnicode(QStringView)@Qt_6' /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined reference to `QUtf32::convertFromUnicode(QStringView, QStringConverterBase::State*, DataEndianness)@Qt_6' /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined reference to `QUtf8::convertFromUnicode(QStringView, QStringConverterBase::State*)@Qt_6' /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined reference to `QUtf8::convertToUnicode(QChar*, QByteArrayView)@Qt_6' /usr/bin/ld: /lib/aarch64-linux-gnu/libQt6Core5Compat.so.6: undefined reference to `QUtf8::convertToUnicode(QByteArrayView, QStringConverterBase::State*)@Qt_6' collect2: error: ld returned 1 exit status This is due to: https://salsa.debian.org/qt-kde-team/qt6/qt6-base/-/commit/b1d2e462c65933b577ec49b4e4156ec8ad426b26
Bug#1071191: elfkickers attempts to write to /usr/local during the build
Source: elfkickers Version: 0+git20240221+ds-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Gürkan Myczko https://buildd.debian.org/status/logs.php?pkg=elfkickers=0%2Bgit20240221%2Bds-1 ... dh_auto_install --destdir=debian/elfkickers/ -a make -j4 install DESTDIR=/<>/elfkickers-0\+git20240221\+ds/debian/elfkickers AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' mkdir -p /usr/local/bin cp bin/* /usr/local/bin/. cp: cannot create regular file '/usr/local/bin/./ebfc': Permission denied cp: cannot create regular file '/usr/local/bin/./elfls': Permission denied cp: cannot create regular file '/usr/local/bin/./elftoc': Permission denied cp: cannot create regular file '/usr/local/bin/./infect': Permission denied cp: cannot create regular file '/usr/local/bin/./objres': Permission denied cp: cannot create regular file '/usr/local/bin/./rebind': Permission denied cp: cannot create regular file '/usr/local/bin/./sstrip': Permission denied make[1]: *** [Makefile:28: install] Error 1
Bug#1071138: falkon/experimental FTBFS: missing build dependencies
Source: falkon Version: 24.04.80-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=falkon=24.04.80-2 ... CMake Error at CMakeLists.txt:108 (find_package): By not providing "FindKF6I18n.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "KF6I18n", but CMake did not find one. Could not find a package configuration file provided by "KF6I18n" with any of the following names: KF6I18nConfig.cmake kf6i18n-config.cmake Add the installation prefix of "KF6I18n" to CMAKE_PREFIX_PATH or set "KF6I18n_DIR" to a directory containing one of the above files. If "KF6I18n" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! This is likely a missing build dependency on libkf6i18n-dev (untested). Looking at CMakeLists.txt, there are also optional dependencies where packages are now available in experimental.
Bug#1071137: pytorch-audio FTBFS with pytorch 2.1.2
Source: pytorch-audio Version: 0.13.1-1 Severity: serious Tags: ftbfs trixie sid patch Forwarded: https://github.com/pytorch/audio/commit/d1cc1da6a4d6cb2fa44eda457c141aa2ac73e11a https://buildd.debian.org/status/logs.php?pkg=pytorch-audio=0.13.1-1%2Bb3 ... In file included from /usr/include/torch/csrc/api/include/torch/types.h:3, from /usr/include/torch/script.h:3, from /<>/torchaudio/csrc/rnnt/compute_alphas.cpp:1: /usr/include/ATen/ATen.h:4:2: error: #error C++17 or later compatible compiler is required to use ATen. 4 | #error C++17 or later compatible compiler is required to use ATen. | ^ ...
Bug#1071133: firebird4.0: binary-all FTBFS
Source: firebird4.0 Version: 4.0.4.3010.ds6-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=firebird4.0=all ... dh_lintian sed -i -e "s/TRIPLET/x86_64-linux-gnu/g" \ debian/libib-util/usr/share/lintian/overrides/libib-util sed: can't read debian/libib-util/usr/share/lintian/overrides/libib-util: No such file or directory make[1]: *** [debian/rules:185: override_dh_lintian] Error 2
Bug#1071132: ovito accesses the internet during the build
Source: ovito
Version: 3.10.5~ds-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=ovito=all=3.10.5~ds-1=1713769268=0
...
Running Sphinx v7.2.6
loading intersphinx inventory from
https://ovito.org/docs/current/python/objects.inv...
loading intersphinx inventory from
https://docs.scipy.org/doc/scipy/objects.inv...
Warning, treated as error:
failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://ovito.org/docs/current/python/objects.inv' not
fetchable due to :
HTTPSConnectionPool(host='ovito.org', port=443): Max retries exceeded with url:
/docs/current/python/objects.inv (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution'))
...
Bug#1071131: pytorch-geometric FTBFS (several reasons)
Source: pytorch-geometric Version: 2.3.1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=pytorch-geometric=all
Bug#1058130: closed by Debian FTP Masters (reply to Ulises Vitulli ) (Bug#1058130: fixed in python-nmea2 1.19.0-1)
Control: reopen -1
On Mon, Feb 12, 2024 at 10:57:03PM +, Debian Bug Tracking System wrote:
>...
> python-nmea2 (1.19.0-1) unstable; urgency=medium
> .
>* New upstream release (Closes: #1058130).
>...
> Relevant part (hopefully):
> > fakeroot debian/rules clean
> > dh clean --with python3 --buildsystem=pybuild
> >dh_auto_clean -O--buildsystem=pybuild
> > I: pybuild base:310: python3.12 setup.py clean
> > Traceback (most recent call last):
> > File "/<>/setup.py", line 3, in
> > import imp
> > ModuleNotFoundError: No module named 'imp'
> > E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> > python3.12 setup.py clean
> > dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> > returned exit code 13
> > make: *** [debian/rules:7: clean] Error 25
>...
The fix is not included in 1.19.0-2:
https://buildd.debian.org/status/fetch.php?pkg=python-nmea2=all=1.19.0-2=1715629490=0
cu
Adrian
Bug#1070854: clc-intercal FTBFS: dpkg-genbuildinfo: error: binary build with no binary artifacts found
On Tue, May 14, 2024 at 11:16:28AM +0100, Mark Brown wrote: > On Fri, May 10, 2024 at 05:25:35PM +0300, Adrian Bunk wrote: > > > chmod +x `pwd`/debian/clc-intercal/usr/bin/* > > dpkg-genbuildinfo --build=any > > -O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo > > dpkg-genbuildinfo: error: binary build with no binary artifacts found; > > .buildinfo is meaningless > > dpkg-buildpackage: error: dpkg-genbuildinfo --build=any > > -O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo subprocess returned exit > > status 25 > > I can't reproduce this, and nothing about the build I'm seeing in the > log looks meaningfully different to what I get when I build locally. I can reproduce it with dpkg-buildpackage -B > AFAICT there are .so files being installed among the various perl things > and dpkg-genbuildinfo runs happily. ... build-arch: build-indep: build-stamp ... # Build architecture-dependent files here. binary-arch: build install # We have nothing to do by default. # Build architecture-independent files here. binary-indep: build install ... This looks wrong for a package that builds no Architecture: all packages. cu Adrian
Bug#1071081: phpunit-environment/experimental FTBFS: Error: Call to undefined method SebastianBergmann\Environment\Runtime::getRawBinary()
Source: phpunit-environment Version: 7.1.0-1 Severity: serious Tags: ftbfs Forwarded: https://github.com/sebastianbergmann/environment/commit/ff8e9b0dc10315e13f3a7951eec6b227e66997e7 https://buildd.debian.org/status/fetch.php?pkg=phpunit-environment=all=7.1.0-1=1715633007=0 ... There was 1 error: 1) SebastianBergmann\Environment\RuntimeTest::testRawBinaryCanBeRetrieved Error: Call to undefined method SebastianBergmann\Environment\Runtime::getRawBinary() /<>/tests/RuntimeTest.php:48 ERRORS! Tests: 22, Assertions: 13, Errors: 1, Skipped: 8. make[1]: *** [debian/rules:12: override_dh_auto_test] Error 2
Bug#1063004: synfig: NMU diff for 64-bit time_t transition
On Sat, Feb 24, 2024 at 12:41:14PM -0800, Steve Langasek wrote: > Control: tags -1 - pending > Control: severity -1 serious > > Unfortunately, it appears synfig ftbfs in unstable and experimental: > > [...] > checking for Magick++ >= 6.4.2... configure: error: *** Unable to find > Magick++ > cd synfig-core && tail -v -n \+0 config.log > [...] > > > (https://buildd.debian.org/status/fetch.php?pkg=synfig=amd64=1.5.1%2Bdfsg-3.1%7Eexp1=1707063449=0) > > Therefore we will not be able to NMU this. Marking the bug serious as the > mass NMUs are imminent within a few days and this becomes a serious bug once > the toolchain changes land. This is due to experimental using a different dependency resolver than unstable, and graphicsmagick-libmagick-dev-compat also providing libmagick++-dev An upload to unstable will likely build fine, but technically it would in any case be more correct to Build-Depends: libmagick++-dev (>= 7:6.4.2) cu Adrian
Bug#1071075: python-easydev accesses the internet during the build
Source: python-easydev
Version: 0.13.2+dfsg1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-easydev=all=0.13.2%2Bdfsg1-1=1714380640=0
...
=== FAILURES ===
__ test_isurl __
def test_isurl():
> assert isurl_reachable("www.google.com") == True
E AssertionError: assert False == True
E+ where False = isurl_reachable('www.google.com')
test/test_url.py:7: AssertionError
=== short test summary info
FAILED test/test_url.py::test_isurl - AssertionError: assert False == True
= 1 failed, 56 passed in 2.36s =
...
Bug#1071039: iptux FTBFS on 32bit with 64bit time_t
Source: iptux
Version: 0.9.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=iptux=0.9.1-1
...
FAILED: src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o
c++ -Isrc/iptux-core/libiptux-core.so.0.9.1.p -Isrc/iptux-core
-I../src/iptux-core -Isrc -I../src -Isrc/api -I../src/api
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
-I/usr/include/sysprof-6 -I/usr/include/jsoncpp -I/usr/include/sigc++-2.0
-I/usr/lib/arm-linux-gnueabihf/sigc++-2.0/include -fdiagnostics-color=always
-D_GLIBCXX_ASSERTIONS=1 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c++14
-Werror=format -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o -MF
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o.d -o
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o -c
../src/iptux-core/internal/SendFileData.cpp
../src/iptux-core/internal/SendFileData.cpp: In member function ‘void
iptux::SendFileData::SendDirFiles()’:
../src/iptux-core/internal/SendFileData.cpp:205:16: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 8 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
205 |":%s:%.9" PRIx64 ":%lx:%lx=%lx:%lx=%lx:", dirname,
|^~~~
../src/iptux-core/internal/SendFileData.cpp:205:16: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 10 has type ‘__time64_t’
{aka ‘long long int’} [-Werror=format=]
205 |":%s:%.9" PRIx64 ":%lx:%lx=%lx:%lx=%lx:", dirname,
|^~~~
../src/iptux-core/internal/SendFileData.cpp:243:36: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 6 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
243 |":.:0:%lx:%lx=%lx:%lx=%lx:", IPMSG_FILE_RETPARENT,
| ~~^
||
|long unsigned int
| %llx
../src/iptux-core/internal/SendFileData.cpp:243:44: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 8 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
243 |":.:0:%lx:%lx=%lx:%lx=%lx:", IPMSG_FILE_RETPARENT,
| ~~^
||
|long unsigned int
| %llx
../src/iptux-core/internal/SendFileData.cpp:264:32: warning: cast between
incompatible function types from ‘int (*)(DIR*)’ to ‘GFunc’ {aka ‘void
(*)(void*, void*)’} [-Wcast-function-type]
264 | g_queue_foreach(, GFunc(closedir), NULL);
|^~~
cc1plus: some warnings being treated as errors
...
FAILED: src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o
c++ -Isrc/iptux-core/libiptux-core.so.0.9.1.p -Isrc/iptux-core
-I../src/iptux-core -Isrc -I../src -Isrc/api -I../src/api
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
-I/usr/include/sysprof-6 -I/usr/include/jsoncpp -I/usr/include/sigc++-2.0
-I/usr/lib/arm-linux-gnueabihf/sigc++-2.0/include -fdiagnostics-color=always
-D_GLIBCXX_ASSERTIONS=1 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c++14
-Werror=format -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o -MF
src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o.d -o
src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o -c
../src/iptux-core/internal/TcpData.cpp
../src/iptux-core/internal/TcpData.cpp: In member function ‘void
iptux::TcpData::RecvSublayer(uint32_t)’:
../src/iptux-core/internal/TcpData.cpp:146:35: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 7 has type ‘time_t’ {aka
‘long long int’} [-Werror=format=]
146 | snprintf(path, MAX_PATHLEN, "%s" PIC_PATH "/%" PRIx32 "-%" PRIx32
"-%lx",
|
^~~~
147 |g_get_user_cache_dir(), inAddrToUint32(pal->ipv4()),
count++,
148 |time(NULL));
|~~
||
|time_t {aka long long int}
Bug#1066629: ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration]
On Sat, Apr 13, 2024 at 01:59:28AM +0300, Peter Pentchev wrote: >... > I will probably upload a new ucspi-tcp version in a couple of days. Any update on this? > G'luck, > Peter Thanks Adrian
Bug#1070956: octave-fits FTBFS with Octave 9.1.0
Source: octave-fits Version: 1.0.7-7 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/fetch.php?pkg=octave-fits=amd64=1.0.7-7%2Bb4=1715454563=0 ... g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/octave-9.1.0/octave/.. -I/usr/include/octave-9.1.0/octave -pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall save_fits_image_multi_ext.cc -o /tmp/oct-bxJQR8.o save_fits_image_multi_ext.cc: In function ‘octave_value_list Fsave_fits_image_multi_ext(const octave_value_list&, int)’: save_fits_image_multi_ext.cc:140:60: error: passing ‘const NDArray’ as ‘this’ argument discards qualifiers [-fpermissive] 140 | double * datap = const_cast( image.fortran_vec() ); | ~^~ In file included from /usr/include/octave-9.1.0/octave/../octave/Array-util.h:31, from /usr/include/octave-9.1.0/octave/../octave/MSparse.h:31, from /usr/include/octave-9.1.0/octave/../octave/MatrixType.h:33, from /usr/include/octave-9.1.0/octave/../octave/mx-base.h:33, from /usr/include/octave-9.1.0/octave/../octave/Matrix.h:34, from /usr/include/octave-9.1.0/octave/../octave/oct.h:33, from save_fits_image_multi_ext.cc:19: /usr/include/octave-9.1.0/octave/../octave/Array.h:666:20: note: in call to ‘T* Array::fortran_vec() [with T = double; Alloc = std::allocator]’ 666 | OCTARRAY_API T * fortran_vec (); |^~~ save_fits_image.cc: In function ‘octave_value_list Fsave_fits_image(const octave_value_list&, int)’: save_fits_image.cc:132:58: error: passing ‘const NDArray’ as ‘this’ argument discards qualifiers [-fpermissive] 132 | double * datap = const_cast( image.fortran_vec() ); | ~^~ In file included from /usr/include/octave-9.1.0/octave/../octave/Array-util.h:31, from /usr/include/octave-9.1.0/octave/../octave/MSparse.h:31, from /usr/include/octave-9.1.0/octave/../octave/MatrixType.h:33, from /usr/include/octave-9.1.0/octave/../octave/mx-base.h:33, from /usr/include/octave-9.1.0/octave/../octave/Matrix.h:34, from /usr/include/octave-9.1.0/octave/../octave/oct.h:33, from save_fits_image.cc:19: /usr/include/octave-9.1.0/octave/../octave/Array.h:666:20: note: in call to ‘T* Array::fortran_vec() [with T = double; Alloc = std::allocator]’ 666 | OCTARRAY_API T * fortran_vec (); |^~~ make[1]: *** [Makefile:9: save_fits_image_multi_ext.oct] Error 1
Bug#1070912: libuv1: latest upload reverts time_t transition
Source: libuv1 Version: 1.48.0-2 Severity: serious The latest upload reverts the the time_t transition rename from libuv1 to libuv1t64.
Bug#1070872: libm.a lost fmod + fmodf on i386 + m68k
Package: libc6-dev Version: 2.38-7 Severity: serious Tags: ftbfs Control: affects -1 src:zsh https://buildd.debian.org/status/logs.php?pkg=zsh=5.9-6%2Bb1 ... gcc -static -o zsh main.o `cat stamp-modobjs` -lpcre2-8 -lgdbm -lcap -lncursesw -ltinfo -ltinfo -lrt -lm -lc ... ./obj-static/Src/../../Src/math.c:1260:(.text+0x1d8e): undefined reference to `fmod' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:228: zsh] Error 1 $ objdump -t /usr/lib/i386-linux-gnu/libm.a | grep fmod w_fmodl_compat.o: file format elf32-i386 w_fmod_compat.o: file format elf32-i386 w_fmodf_compat.o: file format elf32-i386 e_fmodl.o: file format elf32-i386 g F .text 0013 __ieee754_fmodl w_fmodl.o: file format elf32-i386 g F .text 0085 __fmodl *UND* __ieee754_fmodl wF .text 0085 fmodf64x wF .text 0085 fmodl e_fmod.o: file format elf32-i386 g F .text 0013 __ieee754_fmod w_fmod.o: file format elf32-i386 e_fmodf.o: file format elf32-i386 g F .text 0013 __ieee754_fmodf w_fmodf.o: file format elf32-i386 e_fmodf128.o: file format elf32-i386 g F .text 0c9b __ieee754_fmodf128 *UND* __ieee754_fmodf128 *UND* __ieee754_fmodf128 w_fmodf128.o: file format elf32-i386 g F .text 0237 __fmodf128 *UND* __ieee754_fmodf128 wF .text 0237 fmodf128 $ With 2.37-13 this is instead: $ objdump -t /usr/lib/i386-linux-gnu/libm.a | grep fmod w_fmodl_compat.o: file format elf32-i386 w_fmod_compat.o: file format elf32-i386 w_fmodf_compat.o: file format elf32-i386 e_fmodl.o: file format elf32-i386 g F .text 0013 __ieee754_fmodl w_fmodl.o: file format elf32-i386 g F .text 0085 __fmodl *UND* __ieee754_fmodl wF .text 0085 fmodf64x wF .text 0085 fmodl e_fmod.o: file format elf32-i386 g F .text 0013 __ieee754_fmod w_fmod.o: file format elf32-i386 g F .text 006b __fmod *UND* __ieee754_fmod wF .text 006b fmodf32x wF .text 006b fmodf64 wF .text 006b fmod e_fmodf.o: file format elf32-i386 g F .text 0013 __ieee754_fmodf w_fmodf.o: file format elf32-i386 g F .text 0063 __fmodf *UND* __ieee754_fmodf wF .text 0063 fmodf32 wF .text 0063 fmodf e_fmodf128.o: file format elf32-i386 g F .text 0cc5 __ieee754_fmodf128 *UND* __ieee754_fmodf128 *UND* __ieee754_fmodf128 w_fmodf128.o: file format elf32-i386 g F .text 0237 __fmodf128 *UND* __ieee754_fmodf128 wF .text 0237 fmodf128 $
Bug#1070853: strace: test failures on 32bit with 64bit time_t
Control: retitle -1 strace: test failures on 32bit The tests also fail on i386, so do not seem to be related to time_t. cu Adrian
Bug#1070865: webkit2gtk/experimental FTBFS on big endian
Source: webkit2gtk Version: 2.45.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=webkit2gtk=2.45.1-1 ... In file included from /<>/Source/ThirdParty/skia/include/private/base/SkAPI.h:11, from /<>/Source/ThirdParty/skia/include/private/base/SkAssert.h:11, from /<>/Source/ThirdParty/skia/src/base/SkArenaAlloc.h:11, from /<>/Source/ThirdParty/skia/src/base/SkArenaAlloc.cpp:8: /<>/Source/ThirdParty/skia/include/private/base/SkLoadUserConfig.h:57:6: error: #error "The Skia team is not endian-savvy enough to support big-endian CPUs." 57 | #error "The Skia team is not endian-savvy enough to support big-endian CPUs." | ^ /<>/Source/ThirdParty/skia/include/private/base/SkLoadUserConfig.h:58:6: error: #error "If you still want to use Skia," 58 | #error "If you still want to use Skia," | ^ /<>/Source/ThirdParty/skia/include/private/base/SkLoadUserConfig.h:59:6: error: #error "please define I_ACKNOWLEDGE_SKIA_DOES_NOT_SUPPORT_BIG_ENDIAN." 59 | #error "please define I_ACKNOWLEDGE_SKIA_DOES_NOT_SUPPORT_BIG_ENDIAN." | ^ ...
Bug#1070854: clc-intercal FTBFS: dpkg-genbuildinfo: error: binary build with no binary artifacts found
Source: clc-intercal Version: 1:1.00-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=clc-intercal=1%3A1.00-1 ... chmod +x `pwd`/debian/clc-intercal/usr/bin/* dpkg-genbuildinfo --build=any -O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo dpkg-genbuildinfo: error: binary build with no binary artifacts found; .buildinfo is meaningless dpkg-buildpackage: error: dpkg-genbuildinfo --build=any -O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo subprocess returned exit status 25
Bug#1070853: strace: test failures on 32bit with 64bit time_t
Source: strace
Version: 6.8-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=strace=armhf=6.8-1=1715348223=0
https://buildd.debian.org/status/fetch.php?pkg=strace=armel=6.8-1=1715346678=0
https://buildd.debian.org/status/fetch.php?pkg=strace=powerpc=6.8-1=1715349316=0
...
FAIL: strace-k.test
PASS: umovestr_cached.test
FAIL: strace-k-with-depth-limit.test
FAIL: strace-k-demangle.test
PASS: strace-DD.test
FAIL: strace-k-p.test
PASS: strace--tips-full.test
PASS: qual_fault-syscall.test
PASS: qual_fault.test
PASS: filtering_syscall-syntax.test
PASS: looping_threads.test
==
strace 6.8: tests/test-suite.log
==
# TOTAL: 1350
# PASS: 1057
# SKIP: 289
# XFAIL: 0
# FAIL: 4
# XPASS: 0
# ERROR: 0
...
FAIL: strace-k
==
+ ../src/strace -V
+ TIMEOUT=timeout -k 5 -s XCPU 1500
+ timeout -k 5 -s XCPU 1500 true
+ [ 1 -eq 0 ]
+ exec timeout -k 5 -s XCPU 1500 ../../tests/strace-k.test
+ : 0
+ : -k
+ : --stack-trace
+ :
+ [ -f /proc/self/maps ]
+ check_prog grep
+ type grep
+ check_prog readlink
+ type readlink
+ check_prog sed
+ type sed
+ check_prog tr
+ type tr
+ command -v sed
+ path_to_sed=/usr/bin/sed
+ [ -x /usr/bin/sed ]
+ readlink -ev -- /usr/bin/sed
+ path_to_sed=/usr/bin/sed
+ /usr/bin/sed -n s/^[^/]\+[[:space:]]\(\/.*\)$/\1/p /proc/self/maps
+ grep -F -x -e /usr/bin/sed
+ run_prog ../stack-fcall
+ [ 1 -eq 0 ]
+ args=../stack-fcall
+ ../stack-fcall
+ [ x0 = x1 ]
+ run_strace -e chdir -k ../stack-fcall
+
+ args=-e chdir -k ../stack-fcall
+ ../../src/strace -o log -e chdir -k ../stack-fcall
+ expected=../../../tests/strace-k.expected
+ awk_script_common=
/^[^ ]/ {
if (out != "")
print out
syscall = gensub(/^([[:alnum:]_]+)\(.*/, "\\1", 1)
signal = gensub(/^--- ([A-Z]+) .*/, "\\1", 1)
if (syscall != $0) {
out = syscall
stop = 0
} else if (signal != $0) {
out = signal
stop = 0
} else {
out = ""
}
}
/^ > too many stack frames/ {
out = out " _too_many_stack_frames_"
stop = 1
}
+ awk_script_symbol=
/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) / && !stop {
sym = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) .*$/, "\\1", 1)
out = out " " sym
if (sym == "main")
stop = 1
}
+ awk_script_source=
/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) \[0x[a-f0-9]+\] ([^:]+):([0-9]+)$/ && !stop {
sym = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) .*$/, "\\1", 1)
if (sym == "main" || sym ~ /f[0-9]/) {
file = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) \[0x[a-f0-9]+\]
([^:]+):([0-9]+)$/, "\\2", 1)
line = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) \[0x[a-f0-9]+\]
([^:]+):([0-9]+)$/, "\\3", 1)
sub(".*/", "", file)
out = out " " sym "<" file ":" line ">"
if (sym == "main")
stop = 1
}
}
+ [ --stack-trace = --stack-trace ]
+ awk_script=
/^[^ ]/ {
if (out != "")
print out
syscall = gensub(/^([[:alnum:]_]+)\(.*/, "\\1", 1)
signal = gensub(/^--- ([A-Z]+) .*/, "\\1", 1)
if (syscall != $0) {
out = syscall
stop = 0
} else if (signal != $0) {
out = signal
stop = 0
} else {
out = ""
}
}
/^ > too many stack frames/ {
out = out " _too_many_stack_frames_"
stop = 1
}
/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) / && !stop {
sym = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) .*$/, "\\1", 1)
out = out " " sym
if (sym == "main")
stop = 1
}
+ awk
/^[^ ]/ {
if (out != "")
print out
syscall = gensub(/^([[:alnum:]_]+)\(.*/, "\\1", 1)
signal = gensub(/^--- ([A-Z]+) .*/, "\\1", 1)
if (syscall != $0) {
out = syscall
stop = 0
} else if (signal != $0) {
out = signal
stop = 0
} else {
out = ""
}
}
/^ > too many stack frames/ {
out = out " _too_many_stack_frames_"
stop = 1
}
/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) / && !stop {
sym = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) .*$/, "\\1", 1)
out = out " " sym
if (sym == "main")
stop = 1
}
log
+ LC_ALL=C grep -E -x -f ../../../tests/strace-k.expected
+ cat ../../../tests/strace-k.expected
+ cat out
+ cat
Failed pattern of expected output:
^chdir (__kernel_vsyscall )?(__)?chdir f3 f2 f1 f0 main
^SIGURG (__kernel_vsyscall )?(__)?kill f3 f2 f1 f0 main
Actual output:
chdir chdir f3
SIGURG kill f3
+ pattern=
+ pattern=No DWARF information found
+ [ -n No DWARF information found ]
+ LC_ALL=C grep -x > No DWARF information found
+ dump_log_and_fail_with ../../src/strace -e chdir -k ../stack-fcall
Bug#1070838: xine-lib-1.2 FTBFS with glibc 2.38
Source: xine-lib-1.2 Version: 1.2.13+hg20230710-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=xine-lib-1.2=1.2.13%2Bhg20230710-2%2Bb6 ... dh_makeshlibs -a dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libxine2-bin/DEBIAN/symbols doesn't match completely debian/libxine2-bin.symbols --- debian/libxine2-bin.symbols (libxine2-bin_1.2.13+hg20230710-2+b6_amd64) +++ dpkg-gensymbolsgeNc6J 2024-05-10 10:16:36.253605552 + @@ -404,8 +404,8 @@ xine_post_wire@Base 1.2.0 xine_post_wire_audio_port@Base 1.2.0 xine_post_wire_video_port@Base 1.2.0 - xine_private_strlcat@Base 1.2.9 - xine_private_strlcpy@Base 1.2.9 +#MISSING: 1.2.13+hg20230710-2+b6# xine_private_strlcat@Base 1.2.9 +#MISSING: 1.2.13+hg20230710-2+b6# xine_private_strlcpy@Base 1.2.9 xine_profiler_allocate_slot@Base 1.2.0 xine_profiler_init@Base 1.2.0 xine_profiler_print_results@Base 1.2.0 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:43: binary-arch] Error 25
Bug#1064516: Debdifffs for ruby-rack DSA
Hi,
attached are debdiffs for a ruby-rack DSA,
with the same fixes as in sid and buster.
cu
Adrian
diffstat for ruby-rack-2.1.4 ruby-rack-2.1.4
changelog | 10 +
patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch | 51
++
patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch | 46
+
patches/0003-Fixing-ReDoS-in-header-parsing.patch | 30 +
patches/series |3
5 files changed, 140 insertions(+)
diff -Nru ruby-rack-2.1.4/debian/changelog ruby-rack-2.1.4/debian/changelog
--- ruby-rack-2.1.4/debian/changelog2023-06-08 00:52:23.0 +0300
+++ ruby-rack-2.1.4/debian/changelog2024-05-02 23:46:12.0 +0300
@@ -1,3 +1,13 @@
+ruby-rack (2.1.4-3+deb11u2) bullseye-security; urgency=medium
+
+ * Non-maintainer upload.
+ * CVE-2024-25126: ReDoS in Content Type header parsing
+ * CVE-2024-26141: Reject Range headers which are too large
+ * CVE-2024-26146: ReDoS in Accept header parsing
+ * Closes: #1064516
+
+ -- Adrian Bunk Thu, 02 May 2024 23:46:12 +0300
+
ruby-rack (2.1.4-3+deb11u1) bullseye-security; urgency=high
* Add patch to restrict broken mime parsing.
diff -Nru
ruby-rack-2.1.4/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
ruby-rack-2.1.4/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
---
ruby-rack-2.1.4/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
1970-01-01 02:00:00.0 +0200
+++
ruby-rack-2.1.4/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
2024-05-02 23:46:12.0 +0300
@@ -0,0 +1,51 @@
+From bad2b5be29349b285e08d343f060f7c18065d416 Mon Sep 17 00:00:00 2001
+From: Jean Boussier
+Date: Wed, 6 Dec 2023 18:32:19 +0100
+Subject: Avoid 2nd degree polynomial regexp in MediaType
+
+---
+ lib/rack/media_type.rb | 13 +
+ 1 file changed, 9 insertions(+), 4 deletions(-)
+
+diff --git a/lib/rack/media_type.rb b/lib/rack/media_type.rb
+index 41937c99..7fc1e39d 100644
+--- a/lib/rack/media_type.rb
b/lib/rack/media_type.rb
+@@ -4,7 +4,7 @@ module Rack
+ # Rack::MediaType parse media type and parameters out of content_type string
+
+ class MediaType
+-SPLIT_PATTERN = %r{\s*[;,]\s*}
++SPLIT_PATTERN = /[;,]/
+
+ class << self
+ # The media type (type/subtype) portion of the CONTENT_TYPE header
+@@ -15,7 +15,11 @@ module Rack
+ # http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7
+ def type(content_type)
+ return nil unless content_type
+-content_type.split(SPLIT_PATTERN, 2).first.tap &:downcase!
++if type = content_type.split(SPLIT_PATTERN, 2).first
++ type.rstrip!
++ type.downcase!
++ type
++end
+ end
+
+ # The media type parameters provided in CONTENT_TYPE as a Hash, or
+@@ -27,9 +31,10 @@ module Rack
+ return {} if content_type.nil?
+
+ content_type.split(SPLIT_PATTERN)[1..-1].each_with_object({}) do |s,
hsh|
++ s.strip!
+ k, v = s.split('=', 2)
+-
+- hsh[k.tap(&:downcase!)] = strip_doublequotes(v)
++ k.downcase!
++ hsh[k] = strip_doublequotes(v)
+ end
+ end
+
+--
+2.30.2
+
diff -Nru
ruby-rack-2.1.4/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
ruby-rack-2.1.4/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
---
ruby-rack-2.1.4/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
1970-01-01 02:00:00.0 +0200
+++
ruby-rack-2.1.4/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
2024-05-02 23:46:12.0 +0300
@@ -0,0 +1,46 @@
+From ef52af28b6ac43789fd8fc05df098b56f220f0fa Mon Sep 17 00:00:00 2001
+From: Aaron Patterson
+Date: Tue, 13 Feb 2024 13:34:34 -0800
+Subject: Return an empty array when ranges are too large
+
+If the sum of the requested ranges is larger than the file itself,
+return an empty array. In other words, refuse to respond with any bytes.
+
+[CVE-2024-26141]
+---
+ lib/rack/utils.rb | 3 +++
+ test/spec_utils.rb | 4
+ 2 files changed, 7 insertions(+)
+
+diff --git a/lib/rack/utils.rb b/lib/rack/utils.rb
+index 16457f90..87c2a946 100644
+--- a/lib/rack/utils.rb
b/lib/rack/utils.rb
+@@ -382,6 +382,9 @@ module Rack
+ end
+ ranges << (r0..r1) if r0 <= r1
+ end
++
++ return [] if ranges.map(&:size).sum > size
++
+ ranges
+ end
+ module_function :get_byte_ranges
+diff --git a/test/spec_utils.rb b/test/spec_utils.rb
+index 5fd92241..67b77b0d 100644
+--- a/test/spec_utils.rb
b/test/spec_utils.rb
+@@ -548,6 +548,10 @@ describe Rack::Utils, "cookies" do
+ end
+
+ describe Rack::Utils, "byte_range" do
++ it "returns
Bug#1070720: tpm2-tss: test/unit/tcti-spidev failure on 32bit with 64bit time_t
Source: tpm2-tss Version: 4.1.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=tpm2-tss=4.1.0-1 ... SKIP: test/unit/tcti-libtpms WARNING:test:test/unit/tcti-libtpms.c:1793:main() _FILE_OFFSET == 64 would produce cmocka errors. SKIP test/unit/tcti-libtpms (exit status: 77) SKIP: test/unit/tcti-device === WARNING:tests:test/unit/tcti-device.c:454:main() _FILE_OFFSET == 64 would produce cmocka errors. SKIP test/unit/tcti-device (exit status: 77) SKIP: test/unit/tcti-pcap = WARNING:tests:test/unit/tcti-pcap.c:736:main() _FILE_OFFSET == 64 would produce cmocka errors. SKIP test/unit/tcti-pcap (exit status: 77) FAIL: test/unit/tcti-spidev === [==] tests: Running 1 test(s). [ RUN ] tcti_spi_init_test ERROR:tcti:src/tss2-tcti/tcti-spidev.c:48:platform_spi_acquire() SPI acquire failed: Bad file descriptor ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:164:spi_tpm_helper_log_register_access() READ register 0xd40f00 (4 bytes) failed in transaction start ERROR:tcti:src/tss2-tcti/tcti-spidev.c:68:platform_spi_release() SPI release failed: Bad file descriptor ERROR:tcti:src/tss2-tcti/tcti-spidev.c:48:platform_spi_acquire() SPI acquire failed: Bad file descriptor ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:164:spi_tpm_helper_log_register_access() READ register 0xd40f00 (4 bytes) failed in transaction start ERROR:tcti:src/tss2-tcti/tcti-spidev.c:68:platform_spi_release() SPI release failed: Bad file descriptor ERROR:tcti:src/tss2-tcti/tcti-spidev.c:48:platform_spi_acquire() SPI acquire failed: Bad file descriptor ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:164:spi_tpm_helper_log_register_access() READ register 0xd40f00 (4 bytes) failed in transaction start ERROR:tcti:src/tss2-tcti/tcti-spidev.c:68:platform_spi_release() SPI release failed: Bad file descriptor ... ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:164:spi_tpm_helper_log_register_access() READ register 0xd40f00 (4 bytes) failed in transaction start ERROR:tcti:src/tss2-tcti/tcti-spidev.c:68:platform_spi_release() SPI release failed: Bad file descriptor ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:728:Tss2_Tcti_Spi_Helper_Init() Probing TPM failed [ ERROR ] --- 0xa000a != 0 [ LINE ] --- test/unit/tcti-spidev.c:200: error: Failure! [ FAILED ] tcti_spi_init_test [==] tests: 1 test(s) run. [ PASSED ] 0 test(s). [ FAILED ] tests: 1 test(s), listed below: [ FAILED ] tcti_spi_init_test 1 FAILED TEST(S) FAIL test/unit/tcti-spidev (exit status: 1) SKIP: test/unit/fapi-io === WARNING:tests:test/unit/fapi-io.c:370:main() _FILE_OFFSET == 64 would produce cmocka errors. SKIP test/unit/fapi-io (exit status: 77) Testsuite summary for tpm2-tss 4.1.0 # TOTAL: 61 # PASS: 56 # SKIP: 4 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to https://github.com/tpm2-software/tpm2-tss/issues make[3]: *** [Makefile:33547: test-suite.log] Error 1
Bug#1070498: libvirt attempts to write to $HOME during the build
Source: libvirt Version: 10.3.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libvirt=amd64=10.3.0-1=1714824148=0 ... 53) completion-command... In '/<>/tests/virshtestdata/completion-command.out': Offset 6 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 54) completion-command-complete ... In '/<>/tests/virshtestdata/completion-command-complete.out': Offset 6 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 55) completion-args ... In '/<>/tests/virshtestdata/completion-args.out': Offset 47 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 56) completion-arg-partial... In '/<>/tests/virshtestdata/completion-arg-partial.out': Offset 26 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 57) completion-arg-full-bool ... In '/<>/tests/virshtestdata/completion-arg-full-bool.out': Offset 7 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 58) completion-arg-full-bool-next ... In '/<>/tests/virshtestdata/completion-arg-full-bool-next.out': Offset 47 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 59) completion-arg-full-string... In '/<>/tests/virshtestdata/completion-arg-full-string.out': Offset 10 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 60) completion-arg-full-string-next ... In '/<>/tests/virshtestdata/completion-arg-full-string-next.out': Offset 47 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 61) completion-arg-full-argv ... In '/<>/tests/virshtestdata/completion-arg-full-argv.out': Offset 10 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 62) completion-arg-full-argv-next ... In '/<>/tests/virshtestdata/completion-arg-full-argv-next.out': Offset 6 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 63) completion-argv-multiple ... In '/<>/tests/virshtestdata/completion-argv-multiple.out': Offset 5 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 64) completion-argv-multiple-next ... In '/<>/tests/virshtestdata/completion-argv-multiple-next.out': Offset 268 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 65) completion-argv-multiple-positional ... In '/<>/tests/virshtestdata/completion-argv-multiple-positional.out': Offset 5 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 66) completion-argv-multiple-positional-next ... In '/<>/tests/virshtestdata/completion-argv-multiple-positional-next.out': Offset 268 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ] ... FAILED 67) completion-arg-positional-empty ... In '/<>/tests/virshtestdata/completion-arg-positional-empty.out': Offset 19 Expect [] Actual [error: Failed to create '/home/buildd/.cache/libvirt/virsh': Permission denied ]
Bug#1070497: webrtc-audio-processing/experimental FTBFS with gcc 13
Source: webrtc-audio-processing Version: 1.0-0.2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/webrtc-audio-processing.html https://buildd.debian.org/status/fetch.php?pkg=webrtc-audio-processing=riscv64=1.0-0.2=1706028598=0 ... FAILED: webrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p/transient_file_utils.cc.o c++ -Iwebrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p -Iwebrtc/modules/audio_processing -I../webrtc/modules/audio_processing -Iwebrtc -I../webrtc -I/usr/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DWEBRTC_LIBRARY_IMPL -DWEBRTC_ENABLE_SYMBOL_EXPORT -DNDEBUG -DWEBRTC_POSIX -DWEBRTC_LINUX -DWEBRTC_THREAD_RR -DWEBRTC_APM_DEBUG_DUMP=0 -MD -MQ webrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p/transient_file_utils.cc.o -MF webrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p/transient_file_utils.cc.o.d -o webrtc/modules/audio_processing/libwebrtc-audio-processing-1.so.0.p/transient_file_utils.cc.o -c ../webrtc/modules/audio_processing/transient/file_utils.cc In file included from ../webrtc/modules/audio_processing/transient/file_utils.cc:11: ../webrtc/modules/audio_processing/transient/file_utils.h:36:35: error: ‘uint8_t’ does not name a type 36 | int ConvertByteArrayToFloat(const uint8_t bytes[4], float* out); | ^~~ ../webrtc/modules/audio_processing/transient/file_utils.h:17:1: note: ‘uint8_t’ is defined in header ‘’; did you forget to ‘#include ’? 16 | #include "rtc_base/system/file_wrapper.h" +++ |+#include 17 | ../webrtc/modules/audio_processing/transient/file_utils.h:41:36: error: ‘uint8_t’ does not name a type 41 | int ConvertByteArrayToDouble(const uint8_t bytes[8], double* out); |^~~ ../webrtc/modules/audio_processing/transient/file_utils.h:41:36: note: ‘uint8_t’ is defined in header ‘’; did you forget to ‘#include ’? ../webrtc/modules/audio_processing/transient/file_utils.h:46:42: error: ‘uint8_t’ has not been declared 46 | int ConvertFloatToByteArray(float value, uint8_t out_bytes[4]); | ^~~ ../webrtc/modules/audio_processing/transient/file_utils.h:51:44: error: ‘uint8_t’ has not been declared 51 | int ConvertDoubleToByteArray(double value, uint8_t out_bytes[8]); |^~~ ...
Bug#1070491: rust-pipewire FTBFS on 32bit with 64bit time_t
Source: rust-pipewire
Version: 0.8.0-4
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=rust-pipewire=0.8.0-4
...
error[E0308]: mismatched types
--> src/thread_loop.rs:142:43
|
142 | nix::sys::time::TimeSpec::new(abstime.tv_sec, abstime.tv_nsec)
| - ^^ expected `i64`,
found `i32`
| |
| arguments to this function are incorrect
|
note: associated function defined here
--> /usr/share/cargo/registry/nix-0.27.1/src/sys/time.rs:339:18
|
339 | pub const fn new(seconds: time_t, nanoseconds: timespec_tv_nsec_t) ->
Self {
| ^^^
help: you can convert an `i32` to an `i64`
|
142 | nix::sys::time::TimeSpec::new(abstime.tv_sec.into(),
abstime.tv_nsec)
| +++
error[E0308]: mismatched types
--> src/thread_loop.rs:152:25
|
152 | tv_sec: abstime.tv_sec(),
| expected `i32`, found `i64`
For more information about this error, try `rustc --explain E0308`.
error: could not compile `pipewire` (lib) due to 2 previous errors
...
Bug#1070489: rust-hypothesis FTBFS: test failures
Source: rust-hypothesis
Version: 0.11.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=rust-hypothesis=0.11.1-1
https://buildd.debian.org/status/logs.php?pkg=rust-hypothesis=0.11.1-2
...
Running
`/<>/target/x86_64-unknown-linux-gnu/release/deps/cli-60d293523176a82c
--test-threads=1 --skip it_works --skip make --skip sync --skip tag_filter`
running 5 tests
test add_and_delete_annotation ... FAILED
test create_and_leave_group ... FAILED
test search_annotations ... FAILED
test update_annotation ... FAILED
test update_group ... FAILED
failures:
add_and_delete_annotation stdout
Error: path not found
Caused by:
path not found
Location:
tests/cli.rs:33:5
create_and_leave_group stdout
Error: path not found
Caused by:
path not found
Location:
tests/cli.rs:177:5
search_annotations stdout
Error: path not found
Caused by:
path not found
Location:
tests/cli.rs:114:5
update_annotation stdout
Error: path not found
Caused by:
path not found
Location:
tests/cli.rs:69:5
update_group stdout
thread 'update_group' panicked at 'assertion failed: group_id.is_ok()',
tests/cli.rs:218:5
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
2: core::panicking::panic
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5
3: cli::update_group
at ./tests/cli.rs:218:5
4: cli::update_group::{{closure}}
at ./tests/cli.rs:212:22
5: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
add_and_delete_annotation
create_and_leave_group
search_annotations
update_annotation
update_group
test result: FAILED. 0 passed; 5 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.04s
error: test failed, to rerun pass `--test cli`
Doc-tests hypothesis
Running `rustdoc --edition=2021 --crate-type lib --crate-name hypothesis
--test /<>/src/lib.rs --target x86_64-unknown-linux-gnu -L
dependency=/<>/target/x86_64-unknown-linux-gnu/release/deps -L
dependency=/<>/target/release/deps -L
native=/<>/target/x86_64-unknown-linux-gnu/release/build/ring-21217903804af83c/out
--test-args --test-threads=1 --test-args --skip --test-args it_works
--test-args --skip --test-args make --test-args --skip --test-args sync
--test-args --skip --test-args tag_filter --extern
assert_cmd=/<>/target/x86_64-unknown-linux-gnu/release/deps/libassert_cmd-134b03450b103fd5.rlib
--extern
chrono=/<>/target/x86_64-unknown-linux-gnu/release/deps/libchrono-366b82fe4c132a7f.rlib
--extern
clap=/<>/target/x86_64-unknown-linux-gnu/release/deps/libclap-0253bc5809b2cb30.rlib
--extern
clap_complete=/<>/target/x86_64-unknown-linux-gnu/release/deps/libclap_complete-e7897de87192b73b.rlib
--extern
color_eyre=/<>/target/x86_64-unknown-linux-gnu/release/deps/libcolor_eyre-9811652bc2e783d9.rlib
--extern
derive_builder=/<>/target/x86_64-unknown-linux-gnu/release/deps/libderive_builder-b3eb91696292575e.rlib
--extern
dotenv=/<>/target/x86_64-unknown-linux-gnu/release/deps/libdotenv-9f37bf59e8da3298.rlib
--extern
eyre=/<>/target/x86_64-unknown-linux-gnu/release/deps/libeyre-913f1aee7266adfa.rlib
--extern
futures=/<>/target/x86_64-unknown-linux-gnu/release/deps/libfutures-badab9fb8631b2a1.rlib
--extern
hypothesis=/<>/target/x86_64-unknown-linux-gnu/release/deps/libhypothesis-12767b8516e42793.rlib
--extern
predicates=/<>/target/x86_64-unknown-linux-gnu/release/deps/libpredicates-53aab59c9f2a01ff.rlib
--extern
reqwest=/<>/target/x86_64-unknown-linux-gnu/release/deps/libreqwest-1c860df583615e4b.rlib
--extern
serde=/<>/target/x86_64-unknown-linux-gnu/release/deps/libserde-c2f81dc8b529eb86.rlib
--extern
serde_json=/<>/target/x86_64-unknown-linux-gnu/release/deps/libserde_json-86e653e5692938d9.rlib
--extern
thiserror=/<>/target/x86_64-unknown-linux-gnu/release/deps/libthiserror-a30286b97953be04.rlib
--extern
tokio=/<>/target/x86_64-unknown-linux-gnu/release/deps/libtokio-f2e0886742c2d315.rlib
--extern
url=/<>/target/x86_64-unknown-linux-gnu/release/deps/liburl-a6463baef11a8609.rlib
-C embed-bitcode=no --cfg 'feature="clap"' --cfg 'feature="clap_complete"'
--cfg 'feature="cli"' --cfg 'feature="color-eyre"' --cfg 'feature="default"'
--cfg 'feature="eyre"' --error-format human`
running 18 tests
test src/annotations.rs - annotations::InputAnnotation (line 27) ... ok
test src/lib.rs - (line 44) - compile ... ok
test src/lib.rs - Hypothesis::create_annotation (line 213) ... FAILED
test src/lib.rs -
Bug#1064516: ruby-rack: diff for NMU version 2.2.7-1.1
Control: tags 1064516 + patch
Control: tags 1064516 + pending
Dear maintainer,
I've prepared an NMU for ruby-rack (versioned as 2.2.7-1.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
cu
Adrian
diffstat for ruby-rack-2.2.7 ruby-rack-2.2.7
changelog | 10 +
patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch | 51 ++
patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch | 46 +
patches/0003-Fixing-ReDoS-in-header-parsing.patch | 30 +
patches/series |3
5 files changed, 140 insertions(+)
diff -Nru ruby-rack-2.2.7/debian/changelog ruby-rack-2.2.7/debian/changelog
--- ruby-rack-2.2.7/debian/changelog 2023-07-10 17:32:41.0 +0300
+++ ruby-rack-2.2.7/debian/changelog 2024-05-02 22:55:26.0 +0300
@@ -1,3 +1,13 @@
+ruby-rack (2.2.7-1.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * CVE-2024-25126: ReDoS in Content Type header parsing
+ * CVE-2024-26141: Reject Range headers which are too large
+ * CVE-2024-26146: ReDoS in Accept header parsing
+ * Closes: #1064516
+
+ -- Adrian Bunk Thu, 02 May 2024 22:55:26 +0300
+
ruby-rack (2.2.7-1) unstable; urgency=medium
* Team Upload
diff -Nru ruby-rack-2.2.7/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch ruby-rack-2.2.7/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
--- ruby-rack-2.2.7/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch 1970-01-01 02:00:00.0 +0200
+++ ruby-rack-2.2.7/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch 2024-05-02 22:55:26.0 +0300
@@ -0,0 +1,51 @@
+From e5c0e03f70624433d7132a5eb039f5f04787d20c Mon Sep 17 00:00:00 2001
+From: Jean Boussier
+Date: Wed, 6 Dec 2023 18:32:19 +0100
+Subject: Avoid 2nd degree polynomial regexp in MediaType
+
+---
+ lib/rack/media_type.rb | 13 +
+ 1 file changed, 9 insertions(+), 4 deletions(-)
+
+diff --git a/lib/rack/media_type.rb b/lib/rack/media_type.rb
+index 41937c99..7fc1e39d 100644
+--- a/lib/rack/media_type.rb
b/lib/rack/media_type.rb
+@@ -4,7 +4,7 @@ module Rack
+ # Rack::MediaType parse media type and parameters out of content_type string
+
+ class MediaType
+-SPLIT_PATTERN = %r{\s*[;,]\s*}
++SPLIT_PATTERN = /[;,]/
+
+ class << self
+ # The media type (type/subtype) portion of the CONTENT_TYPE header
+@@ -15,7 +15,11 @@ module Rack
+ # http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7
+ def type(content_type)
+ return nil unless content_type
+-content_type.split(SPLIT_PATTERN, 2).first.tap &:downcase!
++if type = content_type.split(SPLIT_PATTERN, 2).first
++ type.rstrip!
++ type.downcase!
++ type
++end
+ end
+
+ # The media type parameters provided in CONTENT_TYPE as a Hash, or
+@@ -27,9 +31,10 @@ module Rack
+ return {} if content_type.nil?
+
+ content_type.split(SPLIT_PATTERN)[1..-1].each_with_object({}) do |s, hsh|
++ s.strip!
+ k, v = s.split('=', 2)
+-
+- hsh[k.tap(&:downcase!)] = strip_doublequotes(v)
++ k.downcase!
++ hsh[k] = strip_doublequotes(v)
+ end
+ end
+
+--
+2.30.2
+
diff -Nru ruby-rack-2.2.7/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch ruby-rack-2.2.7/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
--- ruby-rack-2.2.7/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch 1970-01-01 02:00:00.0 +0200
+++ ruby-rack-2.2.7/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch 2024-05-02 22:55:26.0 +0300
@@ -0,0 +1,46 @@
+From e4a334bba45d1f66499973d65ba4db2679129153 Mon Sep 17 00:00:00 2001
+From: Aaron Patterson
+Date: Tue, 13 Feb 2024 13:34:34 -0800
+Subject: Return an empty array when ranges are too large
+
+If the sum of the requested ranges is larger than the file itself,
+return an empty array. In other words, refuse to respond with any bytes.
+
+[CVE-2024-26141]
+---
+ lib/rack/utils.rb | 3 +++
+ test/spec_utils.rb | 4
+ 2 files changed, 7 insertions(+)
+
+diff --git a/lib/rack/utils.rb b/lib/rack/utils.rb
+index c8e61ea1..72700503 100644
+--- a/lib/rack/utils.rb
b/lib/rack/utils.rb
+@@ -380,6 +380,9 @@ module Rack
+ end
+ ranges << (r0..r1) if r0 <= r1
+ end
++
++ return [] if ranges.map(&:size).sum > size
++
+ ranges
+ end
+
+diff --git a/test/spec_utils.rb b/test/spec_utils.rb
+index 90676258..6b069914 100644
+--- a/test/spec_utils.rb
b/test/spec_utils.rb
+@@ -590,6 +590,10 @@ describe Rack::Utils, "cookies" do
+ end
+
+ describe Rack::Utils, "byte_range" do
++ it "returns
Bug#1070022: libretro-beetle-psx FTBFS on mips64el with -Werror=implicit-function-declaration
Source: libretro-beetle-psx Version: 0.9.38.6+git20151019-3 Severity: serious Tags: ftbfs patch trixie sid https://buildd.debian.org/status/fetch.php?pkg=libretro-beetle-psx=mips64el=0.9.38.6%2Bgit20151019-3%2Bb1=1714231581=0 ... libretro-common/rthreads/rthreads.c: In function ‘scond_wait_timeout’: libretro-common/rthreads/rthreads.c:410:4: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration] 410 |gettimeofday(, NULL); |^~~~ cc1: some warnings being treated as errors make[2]: *** [Makefile:264: libretro-common/rthreads/rthreads.o] Error 1
Bug#1070021: libretro-beetle-pce-fast FTBFS on mips64el with -Werror=implicit-function-declaration
Source: libretro-beetle-pce-fast Version: 0.9.38.7+git20160609-2 Severity: serious Tags: ftbfs patch trixie sid Forwarded: https://github.com/libretro/libretro-common/commit/20a43ba79fe6b4ec094b3b20b7bc88f4cfe916fa https://buildd.debian.org/status/fetch.php?pkg=libretro-beetle-pce-fast=mips64el=0.9.38.7%2Bgit20160609-2%2Bb1=1714231411=0 ... libretro-common/rthreads/rthreads.c: In function ‘scond_wait_timeout’: libretro-common/rthreads/rthreads.c:423:4: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration] 423 |gettimeofday(, NULL); |^~~~ cc1: some warnings being treated as errors make[2]: *** [Makefile:332: libretro-common/rthreads/rthreads.o] Error 1
Bug#1070002: rust-alsa FTBFS on 32bit with 64bit time_t
Source: rust-alsa
Version: 0.8.1-3
Severity: serious
Tags: ftbfs
Control: affects -1 src:rust-cpal
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/rust-alsa.html
https://buildd.debian.org/status/fetch.php?pkg=rust-cpal=armhf=0.15.2-3%2Bb1=1714250098=0
...
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> /usr/share/cargo/registry/alsa-0.8.1/src/pcm.rs:1113:21
|
1113 | let mut h = timespec {tv_sec: 0, tv_nsec: 0};
|
|
= note: ... and other private field `__pad` that was not provided
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> /usr/share/cargo/registry/alsa-0.8.1/src/pcm.rs:1119:21
|
1119 | let mut h = timespec {tv_sec: 0, tv_nsec: 0};
|
|
= note: ... and other private field `__pad` that was not provided
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> /usr/share/cargo/registry/alsa-0.8.1/src/pcm.rs:1125:21
|
1125 | let mut h = timespec {tv_sec: 0, tv_nsec: 0};
|
|
= note: ... and other private field `__pad` that was not provided
error: could not compile `alsa` due to 3 previous errors
...
Bug#1070001: rust-net2 FTBFS on 32bit with 64bit time_t
Source: rust-net2 Version: 0.2.37-1 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/fetch.php?pkg=rust-net2=armhf=0.2.37-1%2Bb1=1714277125=0 ... error[E0308]: mismatched types --> src/ext.rs:902:22 | 902 | tv_usec: (d % 1000) as suseconds_t, | ^ expected `i64`, found `i32` For more information about this error, try `rustc --explain E0308`. error: could not compile `net2` due to previous error ...
Bug#1070000: rust-time-0.1 FTBFS on 32bit with 64bit time_t
Source: rust-time-0.1
Version: 0.1.44-2
Severity: serious
Tags: ftbfs trixie sid
https://buildd.debian.org/status/fetch.php?pkg=rust-time-0.1=armhf=0.1.44-2%2Bb1=1714295931=0
...
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> src/sys.rs:521:26
|
521 | let mut tv = libc::timespec { tv_sec: 0, tv_nsec: 0 };
| ^^
|
= note: ... and other private field `__pad` that was not provided
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> src/sys.rs:527:26
|
527 | let mut ts = libc::timespec { tv_sec: 0, tv_nsec: 0 };
| ^^
|
= note: ... and other private field `__pad` that was not provided
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> src/sys.rs:555:24
|
555 | t: libc::timespec {
|^^
|
= note: ... and other private field `__pad` that was not provided
error: could not compile `time` due to 3 previous errors
...
Bug#1069999: rust-unix-socket FTBFS on 32bit with 64bit time_t
Source: rust-unix-socket Version: 0.5.0-2 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/fetch.php?pkg=rust-unix-socket=armhf=0.5.0-2%2Bb1=1714298139=0 ... error[E0308]: mismatched types --> src/lib.rs:122:30 | 122 | tv_usec: usecs, | ^ expected `i64`, found `i32` For more information about this error, try `rustc --explain E0308`. warning: `unix_socket` (lib) generated 31 warnings error: could not compile `unix_socket` due to previous error; 31 warnings emitted ...
Bug#1069998: rust-datetime FTBFS on 32bit with 64bit time_t
Source: rust-datetime
Version: 0.5.2-5
Severity: serious
Tags: ftbfs trixie sid
Control: affects -1 src:rust-zoneinfo-compiled
https://buildd.debian.org/status/fetch.php?pkg=rust-datetime=armhf=0.5.2-5%2Bb1=1714252645=0
...
error: cannot construct `timespec` with struct literal syntax due to private
fields
--> src/system.rs:74:18
|
74 | let mut tv = libc::timespec { tv_sec: 0, tv_nsec: 0 };
| ^^
|
= note: ... and other private field `__pad` that was not provided
...
Bug#1069993: rust-filetime FTBFS on 32bit with 64bit time_t
Source: rust-filetime Version: 0.2.22-1 Severity: serious Tags: ftbfs Control: affects -1 src:rust-notify src:rust-async-tar src:rust-cargo-util src:rust-cp-r https://buildd.debian.org/status/fetch.php?pkg=rust-filetime=armhf=0.2.22-1%2Bb1=1714259218=0 ... error[E0308]: mismatched types --> src/unix/utimes.rs:117:18 | 117 | tv_usec: (ft.nanoseconds() / 1000) as libc::suseconds_t, | ^^ expected `i64`, found `i32` For more information about this error, try `rustc --explain E0308`. error: could not compile `filetime` due to previous error ...
Bug#1069992: rust-socket2 FTBFS on 32bit with 64bit time_t
Source: rust-socket2 Version: 0.5.5-1 Severity: serious Tags: ftbfs Control: affects -1 src:rust-quinn-udp src:rust-oauth2 src:rust-nispor src:rust-netlink-proto src:rust-nb-connect src:rust-debbugs src:rust-dns-lookup src:rust-erbium-net src:rust-ethtool src:rust-genetlink src:rust-git2-curl src:rust-hyper-tls src:rust-mozim src:rust-mptcp-pm src:rust-curl https://buildd.debian.org/status/fetch.php?pkg=rust-socket2=armhf=0.5.5-1%2Bb1=1714293496=0 ... error[E0308]: mismatched types --> src/sys/unix.rs:1137:22 | 1137 | tv_usec: duration.subsec_micros() as libc::suseconds_t, | ^ expected `i64`, found `i32` For more information about this error, try `rustc --explain E0308`. error: could not compile `socket2` due to previous error ...
Bug#1069980: haskell-futhark FTBFS: Missing build dependency on alex
Source: haskell-futhark Version: 0.25.15-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=haskell-futhark=0.25.15-1 ... CallStack (from HasCallStack): withMetadata, called at libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in Cabal-3.8.1.0:Distribution.Simple.Utils Error: hlibrary.setup: The program 'alex' is required but it could not be ...
Bug#1069834: sccache FTBFS with itoa != 0.3.4
Source: sccache Version: 0.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sccache=0.8.0-1 ... test test_rust_cargo_cmd_readonly_preemtive_block ... FAILED failures: test_rust_cargo_cmd_readonly_preemtive_block stdout Error: Unexpected failure. code=101 stderr=`` error: failed to select a version for the requirement `itoa = \"^0.3.4\"` (locked to 0.3.4) candidate versions found which didn\'t match: 1.0.9 location searched: directory source `/<>/debian/cargo_registry` (which is replacing registry `crates-io`) required by package `test-crate v0.1.0 (/<>/tests/test-crate)` perhaps a crate was updated and forgotten to be re-vendored? ``` ``` command=`cd "tests/test-crate" && CARGO_INCREMENTAL="0" CARGO_TARGET_DIR="/<>/debian/sccache_test_rust_cargoG4h5iT/cargo" RUSTC_WRAPPER="/<>/target/x86_64-unknown-linux-gnu/release/sccache" TEST_ENV_VAR="1" "/usr/bin/cargo" "build" "--color=never"` code=101 stdout="" stderr=``` error: failed to select a version for the requirement `itoa = \"^0.3.4\"` (locked to 0.3.4) candidate versions found which didn\'t match: 1.0.9 location searched: directory source `/<>/debian/cargo_registry` (which is replacing registry `crates-io`) required by package `test-crate v0.1.0 (/<>/tests/test-crate)` perhaps a crate was updated and forgotten to be re-vendored? ``` Stack backtrace: 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: failures: test_rust_cargo_cmd_readonly_preemtive_block test result: FAILED. 2 passed; 1 failed; 5 ignored; 0 measured; 0 filtered out; finished in 11.18s error: test failed, to rerun pass `--test sccache_cargo` dh_auto_test: error: env DEB_BUILDDIR= /<>/debian/dh-cargo/bin/cargo test returned exit code 101 make[1]: *** [debian/rules:29: override_dh_auto_test] Error 25
Bug#1069685: haskell-language-c-quote: Missing build dependency on alex
Source: haskell-language-c-quote Version: 0.13.0.1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Debian Haskell Group , Kari Pahula https://buildd.debian.org/status/logs.php?pkg=haskell-language-c-quote=0.13.0.1-1 ... Error: hlibrary.setup: The program 'alex' version >=3 is required but it could not be found. ...
Bug#1069309: xfractint FTBFS: error: implicit declaration of function
Source: xfractint Version: 20.4.10-4 Severity: serious Tags: ftbfs X-Debbugs-Cc: Petter Reinholdtsen https://buildd.debian.org/status/logs.php?pkg=xfractint=20.4.10-4 ... /usr/bin/gcc -I../headers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I./headers -DXFRACT -DNOBSTRING -g -DBIG_ANSI_C -DLINUX -fno-builtin -fcommon -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o 3d.o 3d.c 3d.c: In function ‘longvmultpersp’: 3d.c:290:20: error: implicit declaration of function ‘multiply’ [-Werror=implicit-function-declaration] 290 | tmp[j] += multiply(s[i],m[i][j],bitshift); |^~~~ 3d.c:318:20: error: implicit declaration of function ‘divide’ [-Werror=implicit-function-declaration] 318 | tmpview[0] = divide(lview[0],denom,bitshift); |^~ cc1: some warnings being treated as errors make[3]: *** [: 3d.o] Error 1
